Related
Hi peeps. ..
Really need someone to help here. I've sold my xoom and need to delete all my info off it. I've tried to do it the the normal way of just wipe data but when it reboots into recovery mode it just says..
Entering Android Recovery Mode
Reading ODM fuse: 1
And thats it, its just stuck there.
Now I bought it second hand and was told it had been rooted and flashed with a kernel that allowed you to alter the CPU.
My question is how do I get rid of my data and get it booting into this recovey mode?
I've installed Rom Manger from the market and tried installing CWM but it just gets stuck again on the dual core screen.
Mine is a UK 3G model.
Any advice, suggestions would be most welcome. It does boot fine into android 3.01.
I need to get this posted out today, hence the wipe.
Thanks,
Steve
Get the UK img files and reflash it back to stock through fastboot.
Grab the stock images here http://forum.xda-developers.com/showthread.php?t=1049485
Extract the images and run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
I was using a CM9 Nightlies. My company requires us to encrypt our phone.
Now that I was trying to update my phone to the latest version of CM9, I found I couldn't mount /sdcard in CWM recovery...
Is there anyway either to de-encrypt the phone without full-wipe or mount encrypted /sdcard in CWM?
By encrypting your phone you are unable to mount /sdcard currently(stock recovery can flash through it) and the only way you could do it is a full wipe or mounting a "fake" sdcard(idk how to, sorry)
So in short, you pretty much need to full wipe to update
Sent from my ice cream powered Nexus S
I'm running CWM with AOKP and recently encrypted for work policies and now that I want to upgrade and flash a new ROM it is stating that the sd card is unable to be mounted, even after a full wipe in CWM. What is needed? I don't mind wiping but would rather not lose what was on my sd card (titanium backups, etc)
Thanks in advance!
You need to do it within android. Did you do a cwm backup before wiping?
yes, I have a nandroid but it will not restore due to the inability to mount sd storage. Actually it can't even load the option to restore from a nandroid.
Good, now let's hope that actually helps. Unsure if anyone else has tried, but maybe it'll let you flash a new ROM and decrypt it through there. Worst case scenario you end up in the same position as now and you'll have to do an sd wipe, unless someone else knows different. As on the Nexus S the sdcard is seperate to the /data partition (unlike the GN), it flashing a fastboot image shouldn't erase it.
Try to flash a ROM via fastboot images which you can find here. Select your phone and choose an ICS fastboot image (not full ROM, update, etc - must be fastboot). You'll want to download the appropriate image and store it on your computer, then extract the archive until you end up with several files and another archive. You want to have boot.img, system.img and userdata.img ready. Use the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash system system.img
[try to boot - if fails, continue]
fastboot flash data userdata.img
The last one should be correct, but maybe it is userdata. Havn't actually tried that one myself - it may not even be necessary (try booting it without this first, if it doesn't work you may need to do this). You can also use the fastboot -w update method but i wouldn't recommend it this time just so we know exactly what is being flashed. After this, boot into android and hope it asks you for decryption information.
edit: also, if those commands don't work, you'll need to flash the contained radio.img and recovery.img files too. It might be picky.
Thanks for the advice. If I flash the stock image via fastboot it sounds like I will lose root and custom recovery since it flashes the bootloader, correct? Will this also wipe my sd card?
If so I may just try to format my sd card in Android so that will be all that I lose versus having to reroot and install CWM again.
Thanks again for your time and info. Very helpful.
*Thanked*
katmandu421 said:
Thanks for the advice. If I flash the stock image via fastboot it sounds like I will lose root and custom recovery since it flashes the bootloader, correct? Will this also wipe my sd card?
If so I may just try to format my sd card in Android so that will be all that I lose versus having to reroot and install CWM again.
Thanks again for your time and info. Very helpful.
*Thanked*
Click to expand...
Click to collapse
You will lose all you data, it will be as if you just bought it, your SD card is NOT wiped
You will only lose recovery as a result of the stock rom script
Oh and you only have to flash boot.img, system.img and userdata.img
Sent from my ice cream powered Nexus S
Thanks guys. Got it flashed to stock and booted (had to use fastboot flash userdata userdata.img, btw) but I did not get any prompt to enter encryption password, and I now have no usb storage showing. I don't even get the "unmounted" icon like I had before. Not sure whats going on.
Any thoughts?
EDIT: I even tried all of these commands as well after I read somewhere it is the bootloader preventing the encrypted sd card from being read
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Still unable to mount sd card. Man this sucks. Can't use my camera and many apps are kinda hosed without sd card support.
EDIT 2: I tried going into recovery just to see what was there (power on + volume up, then selecting "Recovery" and I got the android with the exclamation point. I guess that means there is no custom recovery anymore which is good but I thought there was a white screen that went into checking for update.zips automatically when you select the stock recovery.
MuthaF$%er...
I just got a pop up stating that the sd card was in an unsupported format and that I should reformat it. I did and all looks good now, but am unrooted and no recovery...dammit.
Guess I should've done that the other day before going through all the fast boot steps. Lost my data either way. Oh well, most was in the cloud anyways.
Thanks again for all the help. Now I know how to use fastboot at least
So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.
Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!
No one? :/
Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that
You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
sara_ said:
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
Click to expand...
Click to collapse
Fastboot flash recovery, then try using adb commands to boot into recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Droidriven said:
Fastboot flash recovery, then try using adb commands to booting recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Click to expand...
Click to collapse
Thank you so much. I was able to install the ROM via flash recovery, it was pretty easy. THANKS A LOT!!