Database Users

Stuck on Splash Screen

I tried to install TWRP last night. I had the img file in the same directory as fastboot, but I received an error message saying "Fastboot not found" I had followed the instructions on the TeamWin site for the Kindle. When I gave up and unplugged my Fire, it appeared fine, but then I rebooted and ever since I've been stuck on the "kindle fire" splash screen. I checked to make sure the drivers are still installed from when I rooted, they are, but my computer won't recognize my fire. I also just tried the new Kindle Fire Utility, running it with admin priveledges and I get message that Fastboot is offline and pressing 1 for Normal just tells me "Waiting for Device..... then The system cannot find the path specified". I also held the power button for 20 seconds to totally shut down and restarted, didn't help. Am I hosed?

Sounds like you are in fastboot (I can be wrong) first make sure you have fastboot installed on your computer (Guide: Link ) next is when its on the kindle splash screen run - fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img

Thank you. I may be getting closer. That did something. I saw the teamwin logo, and now I'm on the yellow triangle. I am not unplugging my Fire yet. Is there a next step? I'll continue researching, but if you can help, I'd really appreciate it

good then your basically done. Just hold the power button down when you start up the kindle until it changes colors and then you will be in recovery mode, then just hit reboot in recovery mode and your good to go.
Also the yellow triangle is the bootloader firefirefire which is bundled with TWRP 2.0

Thank you. I found the answers here: http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222. Rebooting my PC didn't do the trick, I actually had to shut it down for a few minutes and then I followed those instructions. All good and Twrp is verified as installed. Thanks again.

sweet, glad you got it all worked out.

Just did my first nanoid backup Takes up about 500 megs, but now I have the piece of mind! What we need now are some really good roms to choose. Maybe a replacement for Amazon video so we don't have to temp unroot! I think I've been spoiled by my EVO 3D

Endless TWRP boot prevention

Every time I install a new zip, I have to reset the IDME boot to 4000 before I can use the device again in Android. What can I do to prevent this?

I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...

podspi said:
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
Click to expand...
Click to collapse
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?

ontwowheels said:
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
Click to expand...
Click to collapse
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.

furtom said:
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
Click to expand...
Click to collapse
Thanks....I currently have this and TWRP installed via the KFUtility.

Can also verify I have avoided this by always powering down and not rebooting into recovery. At least with the 4 zips I have flashed.

install clockworkmod touch recovery
twrp never fixed the reboot option.
Sent from my HTC Glacier using xda premium

Fix TWRP boot loop
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.

citizenandroid said:
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
Click to expand...
Click to collapse
Thank you for this! I've been looking through the forums trying to find something that would work. ADB won't launch for me, something I need to look into, but this worked. Thank! :]

[Q] KF auto shutdown, an android bot with exclamation mark appeared

Hi!
My kindle fire was rooted and was running perfectly.
I'm using stock ROM, ver 6.2.2 (i freezed OTA via titanium backup)
GOLauncher EX
clockworkmod
Yesterday, i modified something: enabled google 2-step verification, unfrost amazon MP3, installed GOcalendar with transparent theme.... and my KF worked fine.
Then, i freezed amazon MP3, uninstalled GOcalendar
Suddently, my KF shut down, auto reboot, and a green android bot with orange triangle exclamation mark appreared (looked like http://www.ihelplounge.com/.a/6a0120a619c18e970c014e5f758855970c-pi)
Ok, fine, i accessed boot recovery (CWM) and restored my previous backup.
When it's done and went to lockscreen, my KF auto shut down again and this http://www.ihelplounge.com/.a/6a0120a619c18e970c014e5f758855970c-pi popped out again
What the hell? i thought restore would fix and bring my KF back to my backup..??
went to CWM, cleared cache, dalvik cache and then reboot in fastboot mode
This time, my KF bricked. It stucked at recovery yellow triangle, and i couldnt access CWM. Even worse, after that, i couldnt even turn my KF on
So, i connected it to my PC and thanks god, i could access CWM. Followed this art http://forum.xda-developers.com/showthread.php?t=1411026 , now my KF is working.
My questions: what did i do? what was the problem? why my KF auto shut down? what is the android with exclamation mark screen?
Just want to avoid this next time.
Thanks u guys, u're awesome

Sounds like it was trying to update to the new OTA 6.3. That's what mine did. I had to do some adb work and install TWRP and then it upgraded. Kindle Fire Utility has been updated so hopefully it should be able to help you.

thanks bahlsie and sorry for the loooong post, just want to make it clear
I thought bad luck happened when i defrosted and freezed amazon MP3
i blocked OTA so why my KF knew about v6.3?
after all, i reset and everything's now fine

Didn't work for me
androiddevice said:
after all, i reset and everything's now fine
Click to expand...
Click to collapse
I had the same issue and the same on-screen picture (with exclaim sign), but unfortunately the reset did not do me any good.
The only thing that help was reflashing to the 3/19 Energy ROM.

[KFU]Kindle Fire Utility[Guide]Rooting Your Kindle fire/Stuck on logo?

Disclaimer: Just in case something does happen to your kindle it isnt my fault, but I can help you but I am not responsible for none of it.. hope ya got the extended warranty like I did.
EXTRA: BTW I bricked my phone once and metropcs was suppose to void it but they didnt know what it was so 1+ for me...
Alright guys I am going to start this off from the middle of the rooting process, the adb part, you guys know how most of you have a emulator5554 pop up? Well I have did a ton of research and if you have BlueStacks or a simular application installed I suggest you uninstall it if you want to root your kindle, its what I did, also when I rooted my Kindle I flashed TWRP in, please do not flash TWRP until you get the go ahead around the forums because people have been reporting that they cant get into recovery so just use ClockWorkMod for now,
[Stuck in logo] Are you stuck on the "Kindle Fire" logo? [Stuck in logo]
Well if you got stuck in your kindle fire logo from using KFU you might be able to press 1 and get into bootmode and start your kindle in normal mode even if the Boot Status and ADB status says Offline and Unknown, and your kindle should boot right into normal mode and your saved .
Dont forget to donate to me so I can buy some goodies: [email protected]

You are a fricken life saver!
I installed KFU, but then decided to ensure that TWRP was up to date on the KF, but whilst it was upgrading the version it got stuck on the load screen. Also it was registering as offline in KFU.
Following your instructions (Boot mode -> Normal Mode) did the trick!

Dysanovic said:
You are a fricken life saver!
I installed KFU, but then decided to ensure that TWRP was up to date on the KF, but whilst it was upgrading the version it got stuck on the load screen. Also it was registering as offline in KFU.
Following your instructions (Boot mode -> Normal Mode) did the trick!
Click to expand...
Click to collapse
No problem....

I just get < waiting for device > ... I assume this means I'm still going nowhere? Is there a simple way to get out of this mess?

Thank you
thank you very much :good::good:
I was scared because my kindle was stuck on the logo, but your trick did it !!

I've proven myself an expert at bricking a Kindle Fire

installed MIUI on my KF using TWRP a few days back. went well, played around with it, then decided to go back to stock.
Wiped caches and flashed update.zip (stock rom for KF) and all appeared to have gone well..... BUT..... the battery was/is apparently too low for the device to charge (but wait, it gets better)...
when the device fires up I get the white/orange kf logo animation, then when boots I see the homescreen (without the notification/toolbar at top (just bookshelves,standard icons and bottom row of icons).... as soon as that appears I get forceclose messages for
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but the device (after just a couple of seconds) just goes back to the white/orange logo animation and starts the boot process all over... whether I click force close or not it just restarts the nasty process).
in the brief time Im able to have it on I cant get the kindle fire utility to recognize it so I can get TWRP back on the device to try to re-flash stock.
probably just a paper weight now Im guessing, so I'll either take over my wifes KF or get a new one, but thought I'd mention my experience here to see if anyone has seen/heard of this before and as a warning to other noobs who know just enough to be dangerous like me!
Thanks all.

Have you tried charging it? Just plug it in with the stock charger and let it sit overnight. Then try the re-flash.

Let it charge, then just flash a new rom.

left plugged in with AC charger all night... the force closes just happen over and over and because it doesnt fully boot (Im guessing) I cant get to point where I can use kf utility to get twrp back on to handle boot. i think trying to flash with such a low battery made the flash go horribly wrong and thats the cause of the force closes??? I wish it had hardware buttons like my galaxy s!

Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP

The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.

vbdss said:
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
Click to expand...
Click to collapse
Thanks... KFU doesnt recognize the device at all during the 'boot loop-like' process it runs through before the 2 force closes and the eventual automatic reboot..... I followed your steps and it just kept showing waiting for device and the KF goes through the boot > force close > restart process.... its like ground hog day.
Thanks though, I appreciate the response/help.

shobon said:
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
Click to expand...
Click to collapse
Yeah, I see your point... but the force closes and the fact that it never shows the menus / top notification bar and icons, etc. and that seemingly, the KF os never loads fully keeps me from getting to a point where the windows drivers recognize the device and then allows me to get KFU to work with the device.
sort of stuck but not technically a brick I guess.

There is no such thing like KF never loads fully.
Or it loads or not. FCs is something that happened on the install of the rom
You have TWRP and cant fastboot?
Try to redo the steps to install TWRP and install FFF 1.4a by hashcode

He doesn't have FFF or TWRP anymore, as he flashed Amazon's stock update.zip
Your only solutions are either the USB trick (cracking open the KF's case and shorting specific pins) or getting a factory cable (recommended) to force the KF into fastboot mode, from which you can flash FFF and TWRP, then boot into TWRP and fix the mess.

Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.

Thanks, Dasanko, I'll do a search for the cable and see where to buy it and will go that route. Thanks again all.

FastBoot
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)

vbdss said:
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Click to expand...
Click to collapse
Np, it's just it doesn't flash just over the system, but also overwrites the recovery and bootloader with their crappy stock ones.

darkjz said:
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
Click to expand...
Click to collapse
I like this approach and think it MIGHT yield some results (but what do I know- I caused this afterall!).... Im going to let it stay in its little reboot / force close loop and have KFU sitting at FFF (waiting for device).... then if it looks like this works (how will I know exactly? the boot process will change how exactly (what should I look for, basically)) then I will do same with KFU and TWRP installation option do its thing. Thanks.

Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app

freefaling said:
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Encouraging!.... what exactly did you do to get it to work for you - if you recall... i've just had it spinning through the loop with KFU sitting at waiting for device -- no results though... so seems pointless for me so far.

Little bit of info as to why/what is causing the issues discussed here:
The stock bin backs up data during the restore process and than restores it back along with the ROM (those of you familiar will already see the issue here but I'll continue); problem of course being there that if you restore data from a ROM like CM9 to the gingerbread based/neutered stock OS (or even to CM7 for that matter), it is going to cause all sorts of headaches with force closes and stuff just plain not working.
In short, for those considering trying to return to stock please remember to wipe data before attempting to flash the bin (at least until someone decides there's enough of a demand to make a cleaner return to stock method).
As for the OP, do what was suggested with the factory cable and you should be set; good luck.
Edit: the above posts regarding factory reset might work to as that will delete data but you would have to be able to get to that part of the settings menu, which depending on what's force closing may or may not be possible.

Your exactly right Sblood86 many are slipping on this bannana peel here lately trying to revert back to stock some with even more dire consequences not just a literal shock to it completely changing systems but also how data is rehandled. Could be a better option for some to do full wipes and flash something near stock like modaco to prevent this mishap.

This entire thread is ridiculous.