CM11 blue bootloop after flashing GApps? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

After a lot of reading and research, I got root/twrp/cm11 on my new kindle. It originally was on 7.4.7, but I thought I had to downgrade. After forgetting to turn off OTA updates it upgraded to 7.4.6.
I don't know if this is a factor, but after I got CM11 running, I tried to flash the corresponding GApps in TWRP. After flashing I got stuck in the blue bootloop. I reflashed the ROM and got it working again, but I'm without the play store. Any tips?

Make sure you flashed the right gapps, and when you came from amazon is to cm make sure you had first factory reset and wiped system, then flashed cm11 then gapps, and then reboot and see what happens. If you do that it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Make sure you flashed the right gapps, and when you came from amazon is to cm make sure you had first factory reset and wiped system, then flashed cm11 then gapps, and then reboot and see what happens. If you do that it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Can't remember if I did the factory reset, but I wipe the cache, etc after flashing every time.
Can I just go into TWRP and factory reset, then reflash CM again? Or do I need to start over and reflash the 2nd bootloader again?
Thanks for your help, I'm new to the Android/rooting world.

Just factory reset and wipe system then reflash cm then gapps and reboot. That should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Worked like a charm! Thanks for your help!
If I don't see superuser, do I need to run bin4ry's root again or am I rooted and I just don't see it?

Cm is already rooted, its built into the os, look. Under settings u will see a superuser section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Related

[HELP] can't get hashcode's CM 10.1 to boot ....

Hello all.
I recently started modifying my 2 Kindle fire HD 7". I tried to install Hashcode's latest rom. Everything seems to go fine, but in the end the rom is stuck at the cyanogen loading logo.
I followed the following steps :
1 / brick my kindle
2 / Buy a factory cable, go to fastboot, use Kindle First aide to restore my kindle to rooted 7.2.3
3 / Follow Hashcode's steps to install TWRP
4 / My kindle can now boot normally, or in recovery. Copy the 2 latest roms from hashcode and gapps on the memory.
5 / in recovery, wipe -> cache , davlik cache, then system
6 / install the latest rom
7 / Re-wipe cache and davlik cache
8 / reboot system.
right after reboot, I see the cyanogen spinning logo for a while.
Then "optimizing aplications xx/58"
Then reboot.
Cyanogen logo again, for a while
Then, sometime, the lock screen very briefly shows up. For a short second. And before I can do anything, it reboots again.
I tried both 514 and latest build from hashcode. They both behave the same way.
Sadly, I did not save an amazon rom on the SDCARD (silly me) so I can't try to go back to amazon stock. Unless I restore the whole thing from kffirstaide, but it's taking so long I'd really like an alternative.
Funny thing is, on my first kindle (I have 2) I had the same problem 2 or 3 time. I fiddled with it a bit, I think I re-installed the rom without wiping anything, and it worked. And I am very happy with the rom.
But I have been trying to do the same with the 2nd one for 2 days, and nothing seems to work.
So, did this happen to anyone before ?
What are the exact steps I should take to flash a rom : what should and shouldn't be wiped, in what order ?
Is it possible that TWRP was incorrectly installed ?
Also, I can't seem to either mount usb storage when in recovery, or make sideload works. Did anybody manage that with a KFHD7 ? How ? It could allow me to try amazon stock rom without restrating the whole process ...
Thanks in advance for any help.
kaceps said:
Hello all.
I recently started modifying my 2 Kindle fire HD 7". I tried to install Hashcode's latest rom. Everything seems to go fine, but in the end the rom is stuck at the cyanogen loading logo.
I followed the following steps :
1 / brick my kindle
2 / Buy a factory cable, go to fastboot, use Kindle First aide to restore my kindle to rooted 7.2.3
3 / Follow Hashcode's steps to install TWRP
4 / My kindle can now boot normally, or in recovery. Copy the 2 latest roms from hashcode and gapps on the memory.
5 / in recovery, wipe -> cache , davlik cache, then system
6 / install the latest rom
7 / Re-wipe cache and davlik cache
8 / reboot system.
right after reboot, I see the cyanogen spinning logo for a while.
Then "optimizing aplications xx/58"
Then reboot.
Cyanogen logo again, for a while
Then, sometime, the lock screen very briefly shows up. For a short second. And before I can do anything, it reboots again.
I tried both 514 and latest build from hashcode. They both behave the same way.
Sadly, I did not save an amazon rom on the SDCARD (silly me) so I can't try to go back to amazon stock. Unless I restore the whole thing from kffirstaide, but it's taking so long I'd really like an alternative.
Funny thing is, on my first kindle (I have 2) I had the same problem 2 or 3 time. I fiddled with it a bit, I think I re-installed the rom without wiping anything, and it worked. And I am very happy with the rom.
But I have been trying to do the same with the 2nd one for 2 days, and nothing seems to work.
So, did this happen to anyone before ?
What are the exact steps I should take to flash a rom : what should and shouldn't be wiped, in what order ?
Is it possible that TWRP was incorrectly installed ?
Also, I can't seem to either mount usb storage when in recovery, or make sideload works. Did anybody manage that with a KFHD7 ? How ? It could allow me to try amazon stock rom without restrating the whole process ...
Thanks in advance for any help.
Click to expand...
Click to collapse
I personally never had this happen to me but it seems you forgot to flash gapps and the rom seperately. If you need a backup of the amazon os I have one because, I switch every 15min to check performance. I can give you a twrp backup it will work though. Also what guide did you use because I think you should have used this one http://forum.xda-developers.com/showthread.php?t=2271909 I used to root and install CM10. I encounter the same problem when trying to mount to the computer in twrp, its an issue, but not the main problem. Is it a problem currently or is it working? But use that guide and tell me how it works for you.
I flashed ONLY the rom ... the gapps where on the memory for later flashing.
But guesss what, I just randomly succeded.
Here is what I did
- Wipe cache / davlik cache / system / factory reset (in that order)
- Flash EVERYTHING at the same time. Meaning a rom (the 514 from hashcode) gapps, and the 2 zip for acid audio. I put them all in install before flashing.
- Do NOT re-wipe anything after flash. Just reboot
And it worked ...

[Q] Flashed CM10.2, rebooted to flash SuperUser, now stuck at BL unlocked screen

Hello guys. I need help.
I saw cm10.2 posted at the dev forum and decided to flash. I downloaded the 7-31 image and the latest GApps. I flashed through CWM.
After rebooting, everything was going fine. Basic setup done. I downloaded Titanium backup so I can restore apps, but didn't know that root was removed. At the cm10.2 thread they provided a link for Superuser that you need to flash to gain root access. So I rebooted to recovery and flashed the SU zip file they posted. Then reboot.
Now its stuck at the Bootloader Unlocked warning screen. I can still enter CWM recovery and Fastboot mode. What should I do?
If it helps, AT&T 4.1.1 stock > PACman 4.2.2 > XenonHD 4.2.2 > CM10.2 4.3
Wipe and start from scratch rooting before you try titanium.
Sent from my PACMAN MATRIX HD MAXX
...
How is that no helpful? All he needs to do is root before he trys titanium backup so he has to wipe and do over.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
How is that no helpful? All he needs to do is root before he trys titanium backup so he has to wipe and do over.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Misread what you said. Wasn't very clear. Thought you meant wipe the phone and start over as in go back to stock

Please help!!

I bought my kindle fire HD 7' from ebay it was rooted and running the hellfire 10.2-20130604-unofficial-tate rom. But when I boot in to twrp and try to flash another rom it looks like it does eveything then I reboot and it starts to load then stops on the blue kindle. I have tried all the roms out there even the stock rom none work the only one that works is the hellfire rom. Can someone help me out here. even if its restoring it back stock. I tried the kffirstaid and when I try to connect it fastboot with the drivers installed it won't read it. I will be happy with help to restore it or make another rom work ..Thank you
Try flashing the latest twrp and doing a internal storage wipe. That should solve any issues from selinux and such. Only use twrp builds posted on xda by hashcode, twrp builds on twrp,s site won't work for us.
l00k0ut21 said:
I bought my kindle fire HD 7' from ebay it was rooted and running the hellfire 10.2-20130604-unofficial-tate rom. But when I boot in to twrp and try to flash another rom it looks like it does eveything then I reboot and it starts to load then stops on the blue kindle. I have tried all the roms out there even the stock rom none work the only one that works is the hellfire rom. Can someone help me out here. even if its restoring it back stock. I tried the kffirstaid and when I try to connect it fastboot with the drivers installed it won't read it. I will be happy with help to restore it or make another rom work ..Thank you
Click to expand...
Click to collapse
you need to do a factory reset on twrp then install the new rom and apps .zip folder.

downgraded my nook from cm12 to cm11 and now am getting "Encryption unsuccessful"

downgraded my nook from cm12 to cm11 and now am getting "Encryption unsuccessful"
i have 2 nook hds and were running lollipop on both units before going back to cm11 the install on my nook hd worked perfectly. however on my wifes nook hd i get an error saying "encryption unsuccessful" when i installed cm11. i used the the lastest available cm11 nightly on both installs and followed the steps. i am at a loss right now as to why my unit works great and im getting an error on my wifes. anyways, i have twrp installed and tried to wipe all data off the the tablet with the advanced wipe and format data functions to try and clear everything off and start again. wondering if ther is a more complete formatting tool that i can use to wipe everything off the tablet and start clean again? any help or direction is appreciated.
thanks everyone!
wigglesrewind said:
i have 2 nook hds and were running lollipop on both units before going back to cm11 the install on my nook hd worked perfectly. however on my wifes nook hd i get an error saying "encryption unsuccessful" when i installed cm11. i used the the lastest available cm11 nightly on both installs and followed the steps. i am at a loss right now as to why my unit works great and im getting an error on my wifes. anyways, i have twrp installed and tried to wipe all data off the the tablet with the advanced wipe and format data functions to try and clear everything off and start again.
Click to expand...
Click to collapse
Which version of recovery did you use to re-flash CM11 on the 3 tablets?
wondering if ther is a more complete formatting tool that i can use to wipe everything off the tablet and start clean again? any help or direction is appreciated.
...
Click to expand...
Click to collapse
You should never wipe any partition other than the /data and /cache partitions (the /system partition automatically gets wiped on flashing a new ROM image). In particular the two partitions /bootdata and /factory which contain factory-installed individual device data must never be reformatted/wiped (without first backing up their content in a restorable form) lest you permanently brick your tablet.
I believe I loaded twrp 2.8.7.4 on both. Thanks for the helpful info. Your greatly appreciated.
wigglesrewind said:
I believe I loaded twrp 2.8.7.4 on both.
Click to expand...
Click to collapse
I'd suggest you try using the older but well-proven recovery for CM11 -- CWM v6.0.4.6.
Sent from my GT-N5110 using XDA Premium HD app
Thanks for the advice. It worked with CWM!

CM12.1 to Fire Nexus Rom?

I have CM 12.1 currently install on my Amazon Fire tablet could I flash Fire Nexus Rom on it or will it end up bricking?
clittlej said:
I have CM 12.1 currently install on my Amazon Fire tablet could I flash Fire Nexus Rom on it or will it end up bricking?
Click to expand...
Click to collapse
Shouldn't be a problem. Include a partial wipe (system/dalvik/cache) as the *first* action in the FlashFire operations sequence. If necessary relocate wipe to the top of the queue (long press and drag) as other actions are added. After flashing Nexus should boot up with your existing apps/data portfolio intact.
In some cases the user/data partition must also be wiped when switching roms. This is particularly true going to/from FireOS. That said, you should be ok transitioning between the Lollipop builds of Nexus and CM on this device.
i have swapped between fire nexus and cm 12.1 and back with no problems, as davey126 said wipe system, davlik and cache and there shouldn't be a problem

Categories

Resources