I've read this http://forum.xda-developers.com/showthread.php?t=1678055 and tried but after erasing recovery my phone will only boot to the gray LG logo with "fastboot v0.5"
If I fastboot it to flash another recovery (CWM or TWRP) my phone will only boot to recovery no matter what I tried.
Tried the zip file from here http://androidforums.com/esteem-all...ockworkmod-recovery-bootloop.html#post3767889 but still can't boot normally.
Tried flashing different roms while in both recoveries (acura, paranoid android,...), even restore my old ROM backups, but still it boots into recovery.
My 3D and vol+/- buttons seems ok.
Any help?
Just go back to V21E from the res
urrection guide and flash your desired ROM if you are going for CM10.
Then flash the bootloader without flashing the recovery, you already have one and to reboot to it I recommend downloading ROM Manager after installing CM10 and rebooting into recovery with it.
Related
So I tried to flash Magnolia X 1.0 coming from MIUI. After I wiped from MIUI and tried to install Magnolia I got an error. No big deal right? So I figured I would reboot recovery ( clockwork mod ) and try again, if it didn't work I could restore MIUI. When I hit reboot recovery I got stuck in a bootloop, from white htc screen to off. It just looks like it is trying to get to recovery but it is not loading it for some reason. So I decided to boot it into hboot and reflash the recovery, or possibly flash twrp. Now my problem is that the computer is not recognizing the phone, so none of my fastboot or adb commands do anything I just get <waiting for device>. Any ideas?
So right after I made the post I was able to get the drivers to reinstall and was able to re flash the recovery. Tried both CWM and TWRP and neither will boot. With TWRP I can get to the recovery splash screen but then it just goes black. Downloading the RUU now and I am going to try to flash that through the bootloader. Other than that I have no othe ideas...anyone else have any?
Got it...had to relock bootloader and run ruu then extract the stock recovery and flash it. Rebooted into recovery let it sit, then it rebooted back to the bootloader. Re-unlocked bootloader then flashed TWRP and it worked fine. Back up and running again.
All,
I'm rooted and unlocked. The weirdest thing I'm experiencing is that in both the EZ Recovery and Rom Manager, when I select to reboot into recovery, I'm not booting into ClockworkMod. I'm booting into stock recovery I think. The only time it would boot into ClockwordMod is when I flash touch clockwork mod then it would boot into the correct recovery.
Do I need to flash the Touch ClockworkMod every time I want to boot into recovery? Thats annoying.
Please help.
Thanks!
If you boot into stock recovery by selecting reboot recovery then CWM is simply not installed. Are you selecting the correct option in ez recovery to install the recovery?
I'm good now. I was on stock, but was rooted and unlocked. Like I said, it would work if I flash the recovery, but if I reboot into recovery again without flashing it would go back to stock recovery.
Anyways, I've flashed to CleanRom 4.0 and tested rebooting into recovery and sure enough it went to the ClockworkMod Recovery. So looks like I"m good.
It will do that on stock rom unless a couple of files are modified I believe. Doesn't do it on custom roms.
Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks
You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
also it says invalid "boot image header!" in red letters
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
P.Kosunen said:
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
Click to expand...
Click to collapse
Alright thankyou!
I got everything to work again but I still can't flash roms. They just bootloop :S
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
You do know flashing stock again removes root, so it has to be rerooted again ?
aradalien said:
You do know flashing stock again removes root, so it has to be rerooted again ?
Click to expand...
Click to collapse
Yes I am very aware and followed through with root with that outcome.
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
Click to expand...
Click to collapse
CWM doesn't work it. It boots up (Im used cyanogenmod) the cyanogenmod boot animation but just stays there.
P.Kosunen said:
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Click to expand...
Click to collapse
I've flashed twrp too and came out with the same outcome.
stuck in fastboot
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
Exactly i am also facing same problem....
mobile unable to instal firmware...
still i am searching for solution ...
guys plz help me
I thought I am the only one with this problem..After mailing the phone to SC and got it back after 2 months, the phone still looks the same, just like they did nothing to fix it.