I have tried 2-3 different Kernel 3.0 ICS roms. I get stuck in a boot loop. It reboots a few times from the recovery screen, then I get a second of the boot animation a few times before it reboots until it ultimately just sits on the boot animation screen.
The roms appear to install fine.
I have tried powering off and rebooting from recovery after rom install.
I do wipe. I have tried wiping davlik afterwards.
I have tried both recoveries.(Now stuck with clockwork )
I have tried doing it while charging and off the charger.
I can install CM7 roms just fine.
How exactly are you stuck on CWM? And which version of it? Also, what version of TWRP did you try?
I tried loading twrp back on, and I got into it once from the adb commands but I rebooted and it went right back into clockwork, haven't seen twrp since. I believe its version 5.1 or.2 of clockwork, and I tried installing rom from twrp 2.0(first time), didn't get a chance to try from 2.2 as I haven't been able to get back into twrp.
Use smirkits scripts to change your cwmr to twrp http://forum.xda-developers.com/showthread.php?t=1500935 you can have only 1 recovery 1 overwrites the other
Thepooch said:
Use smirkits scripts to change your cwmr to twrp http://forum.xda-developers.com/showthread.php?t=1500935 you can have only 1 recovery 1 overwrites the other
Click to expand...
Click to collapse
Would the recovery type be causing my issue with the cm9 roms causing my Kindle to go into a boot loop?
macpat83 said:
Would the recovery type be causing my issue with the cm9 roms causing my Kindle to go into a boot loop?
Click to expand...
Click to collapse
Shouldn't be causing a boot loop, but a dangerous version of CWMR was released a while back which causes permanent damage.
EDIT: Also, if I remember correctly, older CWMR versions had problems installing ICS ROMs. This could be your issue.
most CM9 devs recommend using TWRP 2.1.x versions. So see if installing TWRP as the recovery makes it fine for you
Related
Hi everyone,
I've been flashing a few different ROMs to my phone lately and have been booting into ClockworkMod Recovery 2.5.1.2 no problem for about a week. However the other day after installing redemptive revolution, I attempted to boot into recovery again only to be taken to the Fastboot on my device. I tried a number of different fixes including updating my Hboot to .92 and fixing my permissions but nothing would work, I kept being cycled into the HTC boot menus whenever I would attempt to boot into recovery. I managed to work around the issue by flashing an alternate recovery image (RA_GNM Recovery v1.8.1) which allowed me access to mount my sd card again and reinstall a different rom. Any ideas what is happening? It would be nice to have access to CM Recovery 2.5.1.2 again. Thanks!
You "should" be able to just run unrevoked again and it should install CWM for you.
g00s3y said:
You "should" be able to just run unrevoked again and it should install CWM for you.
Click to expand...
Click to collapse
Worked like a charm! Thanks!
Using "CWM-based Recovery v5.0.2.7 FULL".
I can't get my device to boot. I'm running the previous version of Energy's ROM (not most recent). However, I can get into recovery and fastboot easily.
All I have tried is to factory reset, wipe caches, and re-install Energy, but it still will not boot. It's gotten close - can see the splashscreen, but no further.
Battery is at 100.
What do I need to do get this baby going again!
P.S. The original problem is that I let the battery drain too low for it to fully boot.
Always read the OP for the ROM before you flash...
http://forum.xda-developers.com/showthread.php?t=1528024
NRGZ28 said:
...
How to Flash this ROM:
- Root your device
- Install TWRP custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
Click to expand...
Click to collapse
The 3.0 Kernel discussions also mention the the symptoms you will encounter if you do not follow instructions...
http://forum.xda-developers.com/showthread.php?t=1591869
Hashcode said:
PLEASE use TWRP to flash this ROM. You will probably bootloop if you don't. If you experience a really long boot animation, double check your recovery (change if necessary) and try it again.
Click to expand...
Click to collapse
Oddly enough I used TWRP to flash. Somehow it reverted me back to CWM. I don't have a clue.
It's currently trying very hard to boot. Once I get there what should be my first steps?
If it doesn't boot, should I try and push TWRP through fastboot?
Edit: pushed TWRP (latest). Wiped and reinstalled. Still won't get past boot animation.
Can I transfer a new ROM file using fastboot or will I need to use 'fastboot update' to install a different ROM?
Should I try reverting to stock image?
Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Possible solution
mayuri1 said:
Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Click to expand...
Click to collapse
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
rocketfans14 said:
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
Click to expand...
Click to collapse
I tried telling it to boot normal during that screen. Still goes to TWRP.
Sent from my PantechP8010 using XDA Free mobile app
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM