Database Users

[Solved] Strange rebooting problem

My kindle fire is rooted and TWRP installed.
All has been fine since this was done, almost a month ago.
Suddenly, the fire keeps rebooting. Further, everytime it reboots, it gets stuck at the yellow triangle with the orange colored button.
I then have to turn it off and on and during the green button phase:
fastboot oem idme bootmode 4000
and then
fastboot reboot
Work fine. The fire reboots and goes to the "Kindle Fire" logo.
But immediately when the lock screen appears, the fire powers down again. To add insult to injury, it always reboots and gets stuck at the triangle.
I can only connect to the fire during the very limitted time it comes up from a hard power down and the light is green. About 10 seconds. Enough time for the fastboot commands above, but little else.
I cannot enter TWRP recovery mode, either. If I push the green button and it turns to orange, trying to go into recovery, it just hangs with the yellow triangle.
I don't think TWRP is responsible for the reboots, however. Nothing has changed with it since I installed it a few weeks ago. I never managed to get it into recovery mode, but I let it be for a while since it was booting into the system. (I was waiting for CM9 to be ready before I tackled it)
This may have been a mistake as now I have no way to interface with the device, but that's the situation.
The only thing I changed recently was intsall Titanium Backup, but I can't imagine how that would case the reboot problem? I did set it to auto backup, could that be it? (not that I can do anything about it if it was)
I also saw around that some people were having problems with constant reboots in Dec. due to WiFi issues, but supposedly update 6.2.1, which I have, fixed the issue.
Anyway, I'm quite ready to chuck stock for CM7 if that will fix it, but I don't know how to get there from here. Any help would be appreciated.
Oh, and I should mention that I am running linux, not windows, so utilities for windows won't help. Has to be a manual solution.
Tom

sound like a battery issue - tried to charge with the wall-charger for an hour or so to get it stable ?
if it will help you there is also a kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653

b63 said:
sound like a battery issue - tried to charge with the wall-charger for an hour or so to get it stable ?
Click to expand...
Click to collapse
I thought of that! I did leave it plugged in overnight, last night, but I am not wholly sure the KF will recharge when not turned on.
if it will help you there is also a kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I can't believe I missed that! Thanks so much. Maybe it will help, I'll let you know.
Tom

I cannot explain this, but I reinstalled TWRP with the utility and now all is well.
The battery is, in fact, fully charged, so that wasn't the issue.
Seems to have been connected to my boched instillation of TWRP, thought I can't imagine how or why it would take almost a month ot manifest itself.
Strange, but I'm glad it's working. Thanks for pointing out the KFU for linux!
Tom

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Ha! I believe I figured it out.
Amazon pushed out 6.2.2 and that broke root again. Working on the fix...
Damn, I thought I had it set up not to update.
Will fix OP with solved, thanks.

[Solved!]Kindle Fire Stuck On Yellow Triangle But Not Recognized By Computer

I rooted my Kindle Fire and installed CM9 on it using TWRP 2.0. I updated CM9 to CM9 Alpha but realized that I liked CM9 better. I then tried to flash MIUI 4.0.3 to my Kindle to see how that would work and got it to work but didn't like that either. I booted back into TWRP and then attempted to restore. Once I my restored it I hit the reboot system button and my Kindle got stuck on the yellow triangle. I unplugged and plugged it and attempted most if not all the suggestions by various threads. The problem is that every time I plug my Kindle into my computer while it is off it displays the yellow triangle and is only recognized for 10 seconds. After it disappears it reappears for 5 more seconds and then completely disappears. I attempted to use KFU to reboot it in normal 4000 by having KFU open plugging in my Kindle and quickly hitting the reboot in normal 4000 mode. KFU said that it told the Kindle to reboot in normal mode but when it started up again it stayed on the yellow triangle. I am really frantic as I love and use this tablet every day! Any help is appreciated!

bricked?
it seems like i keep finding people with the same problem as me that noone wants to help ;; this is madness

When you were connected to KFU and attempted to put it in normal bootmode did you attempt a hard reset when it said "Waiting for device...."? Sometimes the KF hangs and needs a 20 second hard reset

Try this using Ubuntu linux booted from a stick. Worked for me when nothing else would.
http://forum.xda-developers.com/showthread.php?t=1430038

http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

b63 said:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
Click to expand...
Click to collapse
This worked for me after hours working on it last night. Follow all those steps as they make the most sense and actually work compared to all the other threads I've read

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

After having problems with my amazon app, and all my google apps, I figured it was a good time to try and learn how to put a new rom in. So I picked CM9 and tried to no avail. I was getting the same problem as alot of guys on here where it said something about /media. But unlike the others, mine wouldn't load like the others. I also was unable to go back to CM7. I was stuck in TWRP. So I tried my back-up and still nothing. Then thinking maybe I had a bad download I tried another CM9 and nothing. Then I tried MUIU. All three said failure to install. Then after trying the MUIU, my computer quit recognizing my KF and it stopped loading into TWRP and just went straight into yellow triangle. I followed the other threads and added the line under the 1949 in .bit file. I reinstalled the drivers in my newly downloaded KFU. Then tried the adb and nothing works because my computer won't recognize the KFU.

Had the same problem as the op. This solution also worked for me.
Sent from my Transformer TF101 using Tapatalk

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.

Android bootloop after hard reset

Hi everyone, I had my iconia 500 a little forgiven and decided it was time to update, I tried with the market app but I was poor coverage and never could download the update to ICS in this way so I downloaded the update.zip of ICS and installed correctly, very fast and smooth.
The fact is that the tablet was heavily loaded with unnecessary apps and not go deleting one to one wanted to make a HARD RESET. I did as explained on the ACERS web to do but I found an error while it was bootloader and stayed there.
NOW is in a loop when it appears on the screen ANDROID. I have the update.zip on the SD.
I tried to PWR + VOL- and successfully reinstall again, or so it seems, but when it restarts to boot and will definitely be back in the LOOP ANDROID and stay there anymore .. turn it off, turn it on and the same.
What I can do?
I installed the drivers for the tablet to the PC but I do not recognize it, or so I think .. or am i wrong ..
Any idea?
thank u so much!!

disfruta said:
Hi everyone, I had my iconia 500 a little forgiven and decided it was time to update, I tried with the market app but I was poor coverage and never could download the update to ICS in this way so I downloaded the update.zip of ICS and installed correctly, very fast and smooth.
The fact is that the tablet was heavily loaded with unnecessary apps and not go deleting one to one wanted to make a HARD RESET. I did as explained on the ACERS web to do but I found an error while it was bootloader and stayed there.
NOW is in a loop when it appears on the screen ANDROID. I have the update.zip on the SD.
I tried to PWR + VOL- and successfully reinstall again, or so it seems, but when it restarts to boot and will definitely be back in the LOOP ANDROID and stay there anymore .. turn it off, turn it on and the same.
What I can do?
I installed the drivers for the tablet to the PC but I do not recognize it, or so I think .. or am i wrong ..
Any idea?
thank u so much!!
Click to expand...
Click to collapse
Do you have an SBK?

[HELP] HDX 8.9 boot loop after Xpiracy

I have a 8.9 rooted, i have safe strap installed, and i even backed up the device.
I was trying to hack a game and i needed to install Xpiracy on the Xposed framework. I installed and rebooted, than the kindle went into boot loop (kindle logo - kindle is upgrading and repeat) BUT ITS NOT GETTING TO THE SAFESTAP SCREEN so i cant restore it.
I did see the boot loop help form, but was wondering, since i already had safestrap installed and backed up that it might be easier than that process...
Any thoughts?

Bear6009 said:
I have a 8.9 rooted, i have safe strap installed, and i even backed up the device.
I was trying to hack a game and i needed to install Xpiracy on the Xposed framework. I installed and rebooted, than the kindle went into boot loop (kindle logo - kindle is upgrading and repeat) BUT ITS NOT GETTING TO THE SAFESTAP SCREEN so i cant restore it.
I did see the boot loop help form, but was wondering, since i already had safestrap installed and backed up that it might be easier than that process...
Any thoughts?
Click to expand...
Click to collapse
try hold power button for cca 10-15 sec while bootlooping, your kindle should turn off, then turn it on, you should see "recovery - continue" screen - this helped me with boot loop after messing with system apps

Fixed for now
Lol, I just went into adb and issued a reboot command, seems to be working ok...
I was freaking out a little bit! haha
Thanks