Database Users

Wont boot

So I used TWRP to install CM7
I ran backup 1st
I installed CM7
I wipe the cache and dalvik cache
I rebooted
Everything worked
Well I wanted to test the backup and load that back on, it said it was complete, but I my kindle keeps restarting to TWRP whenever I restart.
Can someone help me out here?
Thanks

Could be a corrupted backup. Try re flashing CM7 and see if it boots. If you want to go back to stock if the back is corrupt twrp has that option to download the stock update.zip.

Nevermind I found the steps
How to solve boot loop issue on Kindle Fire TWRP 2.0?
Plug in USB cable to Kindle Fire on TWRP Recovery mode.
Bring up Command Prompt.
Key in adb shell.
Key in idme bootmode 4000.
Finally, key in reboot.
That’s it.

^^ This post saved my Kindle. Thank you 4000 times!

Yeah came across that looking for help.

six3onei said:
So I used TWRP to install CM7
I ran backup 1st
I installed CM7
I wipe the cache and dalvik cache
I rebooted
Everything worked
Well I wanted to test the backup and load that back on, it said it was complete, but I my kindle keeps restarting to TWRP whenever I restart.
Can someone help me out here?
Thanks
Click to expand...
Click to collapse
This was one of the main reasons that I made this guide
http://forum.xda-developers.com/showthread.php?t=1417234

[Q] TWRP is no longer on KF?

I did a restore using TWRP, I flashed back to stock root, no rom or anything. Restore went fine, but my device rebooted and started to do an update, I don't know what it was updating but I tried to stop it by turning it off. I shut it off, restarted and it continued to install an update, I got the KF splash screen. It finished and my KF loaded up fine, still have Burrito-Root and SU. But for some reason that Fire logo doesn't come up anymore, so I can't get into TWRP recovery? How did I lose recovery if I just restored a backup?
Do I have TWRP just need to fix something? Or do I have install TWRP all over again? If so, what's the easiest way to do that?
Thanks guys...

I would say using a gscript is probably the easiest way. Check out the dev section.
Sent from my Kindle Fire using xda premium

Sounds like ur backup was not 6.2.2 and it flashed an update after u restored it? Just reinstall fff n twrp (or cwm lol)
Sent from my Kindle Fire using xda premium

I just returned my other fire back to non root by just putting 6.2.2 back onto it. In the process rebooted fff uninstalled and so did twrp. Just reroot reinstall fff and then reinstall twrp.
Sent from my Kindle Fire using Tapatalk

Thanks guys. FireFire was still installed but didnt show. I had to use KindleFireTools and just flashed TWRP again.

Rooted, But no Rom/Fireware!

I rooted my Kindle Fire the other day.
After root, I did a Factory Reset from within the Kindle Fire original firmware.
But now device only boots into TWRP. Pressing the power button (letting go while light is still green) does not allow device to boot into Stock Firmware. Device boots itself into TWRP
How do I get the Stock Firmware back?

Nevermind...
I use KFU to boot the device into Normal mode. Which seems to have resolved the issue. So sorry for the useless post.

So are you still rooted after factory reset and may i ask why you decided to factory reset.
Sent from my SGH-T959 using xda premium

try flash rom. install update.zip from sdcard. choose ROM from sub forum Kindle Development

Custom ROM loaded! (Advice for noobs like me)

Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.

I also recommend not restoring system data from titanium backup when changing roms. I did that when downgrading from a cm10.1 rom to a cm10 rom and it just got stuck at the cm splash screen until I did a factory reset.
Sent from my Amazon Kindle Fire using Tapatalk HD

Robb Flynn said:
Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
Click to expand...
Click to collapse
Good job. Glad it worked out for you.
A note about solution #1:
The problem in this case isn't so much the drivers, as many (including I) had once believed. The problem is the stock bootloader itself. From what I understand, fastboot shouldn't require drivers to work properly anyway. I'm guessing, the stock bootloader (Kindle Fire logo) isn't the same bootloader the device had in it's infancy and this is causing some very confusing problems for a lot of new users.
For one, the command "fastboot devices" will never show a device connected in fastboot mode. And, when you send any other fastboot command, you'll see it hang at "<waiting for device>", indefinitely. * The solution for this, is to send the command with the device shut down completely and then turn the device back on (this is why it worked in your case). Then, as the device boots up again, fastboot will detect the device and continue with whatever process was waiting for the device. KFU uses the same fastboot commands to check if a device is connected (fastboot devices) and install FFF and TWRP (fastboot flash...), therefore the solution is still the same.
That's not to say the bootloader is always the problem. The stock boot animation can easily be confused with the stock bootloader splash screen, but that's another subject altogether.
I hope this helps to clear up some confusion as to what is actually happening when fastboot doesn't seem to be working properly.

Once you've installed your apps and got your KF running smoothly with your new ROM, reboot into TWRP and do a backup. I usually backup Data only. I keep the ROM and the GAPPS on my KF's SDcard so if I ever need to reinstall, I can do a clean wipe (the caches, factory reset, system), install the ROM and GAPPS, and restore my Data from backup.
I also recommend backing up Data regularly and testing your Data backups.

I strongly recommend twa_priv's CM10.1 rom. I use it 2 Kindle Fire's that my kids have.
Today he added hashcode's new Kernal tweaks, and the battery drain in standby (deep sleep) is unbelievable now! My daughter's Fire is getting about -15 drain when sleeping now, it was getting about -35 before todays update, and honestly I thought that was pretty good. Now ita amazing.
(I use battery monitor widget from 3c to check battery drain)

[Q] bootloop into TWRP, no download mode, recoveries have failed...

I searched for my particular issue and haven't found a solution that works yet so here goes. any help with this issue would be greatly appreciated.
I've painted myself into corners before tinkering with this phone and always found a way out but this time I'm stumped.
HOW I BROKE MY PHONE:
1) had latest CM 11 nightly installed but wanted to try the OTA.
2) In TWRP I restored a back up of my stock rooted software.
3) Unfroze bloat in titanium back up.
4) Checked on phone for OTA, received notification, and began download
5) On completion of download I initiated the update.
6) It booted to recovery (TWRP) and every time I rebooted, or started the phone from powered down it always goes into TWRP.
7) I attempted a factory reset and restoration of my stock back up- same result. It booted straight into recovery.
8) I factory reset and installed cm11 fresh from the SD card- same result
9) Here's my real screw up: since neither installing a fresh ROM or restoring my stock recovery weren't working I went for the nuclear option, I decided to format everything and use the LG Flash tool to get this puppy back up and running.
10) Only to discover I can't get into Download mode and while the G2 is "seen" by my PC it's listed under "other devices."
Dear kind and wise individual who's read my tale of woe. What might my next step be? I've considered attempting to sideload a ROM with TWRP in sideload mode, but I'm afraid I'd just have the same result as when I tried reinstalling CM11 from the SD card.

this
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Many thanks! I'll give this a try.