Related
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
You've got the same issue I do - the kindle keeps trying to apply the new update, and it isn't working, dumping it into recovery mode. I haven't figured out an answer to getting the update successfully applied yet (will work on that tonight), but until that happens, you should be able to remove the update from the sdcard /kindleupdates, and through something like root explorer rename /etc/security/otacerts.zip to something like /etc/security/otacerts.bak (or better yet, move it to the sdcard). That will stop it from redownloading the update and auto-rebooting.
Look Here
Have you looked at this http://forum.xda-developers.com/showthread.php?t=1417234 thread. The video explains the most common fix, and he goes through it step by step.
Also, so you grow a thick skin for posting on this forum, check out this link http://forum.xda-developers.com/showthread.php?t=1633343.
Hope this helps
Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Ok. I just tested it, and had it also confirmed in another thread, but here is one way to get 6.3.1 on when the update fails to apply, putting you into the recovery, force to normal boot, kindle updates, back to recovery loop:
if you have a copy on your device, copy the update to the root of the sdcard volume or download it from amazon. Rename the file update.zip, then reboot into recovery.
Under install, install the update.zip. Once it is done, you'll have 6.3.1 applied. Now, you'll have to both reroot, and reinstall recovery, but since you just did it with KFU a few days ago, it should be pretty quick. Then go move/rename the otacerts.zip file to prevent the next unexpected update.
There might be another way that doesn't blow away recovery, but this worked for me.
Thanks so much for all of the help! It looks like everything is working again. I got 6.3.1 installed (not really sure how that happened but it did!). Also got re-rooted and reinstalled TWRP and did a backup. I renamed the otacerts.zip. There is also a cacerts.bks file in the /etc/security directory... what does that do?
Also... will I ever want/need the updates? I assume renaming the otacerts.zip stops the updates indefinitely. Will this ever be a problem?
Thanks again!
Moving the otacerts.zip prevents the kindle from automatically downloading updates. When a new update has been released, you can download it from amazon's site manually, or put back the cert file to enable the download. Since updates often break root, this method will help keep you rooted until it is known how to root the new versions. As for want/needing them, it'll depend on what changes, but as long as they are rootable, they should generally bring improvements for the device.
The. bks file is a keystore for the certificate authority certs. You shouldn't need to ever touch that file.
powers down
Ok, I've got the exact same issue but one glaring difference. That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Does it actually fully boot into the kindle os? I haven't heard of it trying to apply the update that fast after start up, but not saying that it won't do that.
If using twrp, you can mount the kindle over usb from twrp - mount, and then move the update file out of kindleupdates. That should stop the boot cycle if it is being caused by the update. Another thing to check would be to look at the twrp console and make sure it is complaining about the update failing and not something else.
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
ms6146 said:
Ok, I've got the exact same issue but one glaring difference.
Click to expand...
Click to collapse
That sounds eerily familiar...Where have I seen that before?
That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Click to expand...
Click to collapse
Only kidding...Actually that problem isn't the same at all and is described in detail here: http://forum.xda-developers.com/showthread.php?p=25400963
ms6146 said:
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
Click to expand...
Click to collapse
Formatting your sdcard will erase everything on it. Besides trying to mount your sdcard, what are you trying to accomplish?
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
ms6146 said:
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
Click to expand...
Click to collapse
Your problem can still be fixed, but considering the fact you can't get the computer to recognize your device, you only have a couple of options left:
You could acquire a factory cable which would directly power your device in order to replace the bootloader.
If you don't have the means to acquire a factory cable you need to mount your sdcard in order to transfer FFF1.4 for flashing in recovery. From what I understand in your earlier post, it would in your case, require formatting your sdcard
yellow triangle and restart, please help
Jarden said:
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
Click to expand...
Click to collapse
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
notforever said:
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
I had the same issue - shutdown after a few seconds after boot, then the KF boots back into yellow triangle error.
I was able to get out of this loop by booting into recovery and wiping the cache partition (and the Dalvik cache for good measure) to remove the downloaded update file. After wiping the caches, my KF rebooted normally without issue. I could then us Root Explorer to rename the /etc/security/otacerts.zip file to something else as suggested in an earlier post. I have not had a problem since.
So i did a root yesterday and everything went smoothly, but i noticed that every time i let me kindle go to sleep (a few minutes or so after not doing anything with it, or hitting the power to turn the screen off) it puts me into the twrp screen, and apparently i have to reboot it every time?
How can i stop this? Its really annoying...
My kindle version is 6.3.2
shogunreaper said:
So i did a root yesterday and everything went smoothly, but i noticed that every time i let me kindle go to sleep (a few minutes or so after not doing anything with it, or hitting the power to turn the screen off) it puts me into the twrp screen, and apparently i have to reboot it every time?
How can i stop this? Its really annoying...
My kindle version is 6.3.2
Click to expand...
Click to collapse
Kindle is trying to install 6.3.3, but because you installed TWRP it fails.
just install my pre-rooted 6.3.3 and it will be good.
sd_shadow said:
Kindle is trying to install 6.3.3, but because you installed TWRP it fails.
just install my pre-rooted 6.3.3 and it will be good.
Click to expand...
Click to collapse
Yeah I figured it out thanks
Kindle downloaded an update and it kept trying to install it
all i had to do was delete it from the cache folder.
shogunreaper said:
Yeah I figured it out thanks
Kindle downloaded an update and it kept trying to install it
all i had to do was delete it from the cache folder.
Click to expand...
Click to collapse
The update will keep coming back.
yes, just temp fix, if connected to wifi, update will be tried again at least once a day
I figured, i installed a firewall on there and blocked adcp
When I got home I turned on the FTV and briefly saw an update prompt, ands then I must of accidentally hit the accept button on the remote and the device started to remote and update but I immediately pulled the power cord to prevent the update.
Now I have no idea what to do next. Is there anyway to stop the update when I plug it in ands if not, will I able to get root again?
Thanks for all the help everyone.
madtork said:
When I got home I turned on the FTV and briefly saw an update prompt, ands then I must of accidentally hit the accept button on the remote and the device started to remote and update but I immediately pulled the power cord to prevent the update.
Now I have no idea what to do next. Is there anyway to stop the update when I plug it in ands if not, will I able to get root again?
Thanks for all the help everyone.
Click to expand...
Click to collapse
Do you have cwm recovery? If so you could boot to it and do a factory reset, then be sure to pm disable updates. For now I'd block amazon domains on your router but that's not a 100% guarantee. Aftvnews should have any info you need.
I don't think I installed CMW. Is there anyway to tell at this point, and if it's installed, how do I boot into it? I blocked Amazon updates with my router but recently connected with my phone's hotspot without thinking and it must of downloaded the update then.
Anyone have any other recommendations at this point? If I don't have CWM am I out of luck?
madtork said:
Anyone have any other recommendations at this point? If I don't have CWM am I out of luck?
Click to expand...
Click to collapse
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
AFTVnews.com said:
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
Click to expand...
Click to collapse
That's what I was hoping for. Thanks for the information!
So I connected a keyboard and tried for an hour or better to get this thing into recovery but with no success. I tried the ALT+PRT SCRN+I and it just won't work. It keeps going into the update screen and I keep unplugging the box. If someone can help me get this going I will PAYPAL YOU $20!
Otherwise I am giving this thing away.
madtork said:
So I connected a keyboard and tried for an hour or better to get this thing into recovery but with no success. I tried the ALT+PRT SCRN+I and it just won't work. It keeps going into the update screen and I keep unplugging the box. If someone can help me get this going I will PAYPAL YOU $20!
Otherwise I am giving this thing away.
Click to expand...
Click to collapse
It's thankfully never happened to me but just from reading here, it can be incredibly hard to get to recovery. They're mostly trying to get to cwm (which I believe you don't have?) But in theory I think it should work with stock...
If possible, try a different keyboard. If using a hub then connect it directly. Change your timing (when you actually press the keys) Alter between holding them down the keys and tapping them. And just for the heck of it, try working in the remote at some point (back button and right arrow for 15 seconds performs reset)
Sorry. It sounds silly but many people have needed to get to recovery and no one can definitively say what works for everyone. At least I don't think anyone can??? Good luck
AFTVnews.com said:
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
Click to expand...
Click to collapse
KLit75 said:
It's thankfully never happened to me but just from reading here, it can be incredibly hard to get to recovery. They're mostly trying to get to cwm (which I believe you don't have?) But in theory I think it should work with stock...
If possible, try a different keyboard. If using a hub then connect it directly. Change your timing (when you actually press the keys) Alter between holding them down the keys and tapping them. And just for the heck of it, try working in the remote at some point (back button and right arrow for 15 seconds performs reset)
Sorry. It sounds silly but many people have needed to get to recovery and no one can definitively say what works for everyone. At least I don't think anyone can??? Good luck
Click to expand...
Click to collapse
That's the best reply yet. Your correct, I don't have Clock work recovery. I'll try to add in the remote to the equation. Thank you for your input.
Anyone want a free Amazon FTV? I can't get it into recovery.
I'll take it!
madtork said:
Anyone want a free Amazon FTV? I can't get it into recovery.
Click to expand...
Click to collapse
I'll take it!!!! I dont know how to fix, but will try my damnedest!
Can you email [email protected]?
---------- Post added at 01:04 AM ---------- Previous post was at 01:00 AM ----------
Lowaek said:
I'll take it!!!! I dont know how to fix, but will try my damnedest!
Can you email [email protected]?
Click to expand...
Click to collapse
I will also pay shipping!
So, I'm newly rooted trying to install Google Play Store on my Fire TV
CWM recovery
running 51.1.4.0_514006420 pre-rooted ROM
installed the XPOSED FRAMEWORK and HDXPOSED.APK
rebooted and now it's stuck at the Amazon splash screen. Did I brick it?
Any ideas of what I can do now?
Thanks
detatched said:
So, I'm newly rooted trying to install Google Play Store on my Fire TV
CWM recovery
running 51.1.4.0_514006420 pre-rooted ROM
installed the XPOSED FRAMEWORK and HDXPOSED.APK
rebooted and now it's stuck at the Amazon splash screen. Did I brick it?
Any ideas of what I can do now?
Thanks
Click to expand...
Click to collapse
Try giving more info. I assume it was working fine before you installed xposed? By splash screen you mean just "amazon" white or the colored logo?
I never had any issues with xposed but if theres anything you can add someone might be able to help.
Sorry, yeah it was working fine with Kodi and Llama installed and configured. Streamed the NBA finals game fine. Then I installed and launched those 2 apps and rebooted. Now it's stuck at the Black and white Amazon screen. Not the colored logo. I tried unplugging it and plugging back in but no luck
i can still adb connect to it's ip, but i can't do adb shell or ping it.
detatched said:
Sorry, yeah it was working fine with Kodi and Llama installed and configured. Streamed the NBA finals game fine. Then I installed and launched those 2 apps and rebooted. Now it's stuck at the Black and white Amazon screen. Not the colored logo. I tried unplugging it and plugging back in but no luck
i can still adb connect to it's ip, but i can't do adb shell or ping it.
Click to expand...
Click to collapse
If you can connect adb you should be able to reboot recovery. From there you can do a factory reset. This will wipe data, but root will remain intact (might need to reinstall busybox, not sure.) You can try that or see if anyone else has an easier solution. I'm really puzzled why your stuck. Lots of people using that xposed mod.
KLit75 said:
If you can connect adb you should be able to reboot recovery. From there you can do a factory reset. This will wipe data, but root will remain intact (might need to reinstall busybox, not sure.) You can try that or see if anyone else has an easier solution. I'm really puzzled why your stuck. Lots of people using that xposed mod.
Click to expand...
Click to collapse
I tried that, but nothing happens. It lets me connect to the ip, but it doesn't take any commands. I can't adb shell or even ping it. It's weird, when I try to ping it, the response is from a different ip address that says it is unreachable
fixed
Well after letting it sit unplugged overnight I plugged it back in today and it booted up ok. I finished installing the Play Store and it seems to work fine.
I let it sit on the black and white splash screen for an hour or so last night before unplugging it for the night. I don't know what happened, but glad it's back up and not bricked.
Thanks for the help!
Hello
I have a Fire TV box 2nd gen (not stick).
Yesterday the hdmi signal suddenly showed white noise for 2-3 seconds. Then the menu again. (Then I think it froze, not sure...) I remeber I turned it off, took it from power and tried to boot again. But it did not.
It shows the white amazon logo for a moment, then "no signal" on any TV or HDMI I try.
The white LED is pulsing slowly.
I tried << and UP to change resolution, nothing.
Customer service thinks there is a HDMI-HDCP Problem(?) and white LED means it tries to boot.
Question:
Is there any way to re-set the whole thing, make a clear fresh installation via USB?
Or is this thing a brick now?
(I did many things, turned it off for hours, let it try to boot for 1 hour. Changed HDMI cables and HDMI slots and changed from TV to a beamer ..it just always does the same. I have no idea if the remote really reacts on << [UP] cause there is no light indicator)
What I did not do: Connect via USB to a computer (cant find a old standard USB cable at the moment)
Thanks
Bodo
bodomalo said:
Is there any way to re-set the whole thing, make a clear fresh installation via USB?
Click to expand...
Click to collapse
Take a look into this thread... Maybe you find in this 'unbrick thread' an answer
Sus_i said:
Take a look into this thread... Maybe you find in this 'unbrick thread' an answer
Click to expand...
Click to collapse
I guess that means no....
That thread is too long to read everything, the solution is first from 2016, and the last message 22 pages later from June 2019
bodomalo said:
I guess that means no....
That thread is too long to read everything, the solution is first from 2016, and the last message 22 pages later from June 2019
Click to expand...
Click to collapse
I guess that nobody reads the thread for you
From what I've read, a pulsing light and stuck at amazon logo/black screen is a brick, maybe a hardware failure.
You can place your question in detail in the suggested thread, maybe you get there an answer. Or sell the item on ebay
The exact same thing just happened to me this morning. Worked perfect last night.... then turn it on this morning and nothing... after power cycling just the white Amazon logo then goes black then slow pulsing light. Tried to reset via the remote with the back & forward and held until orange light then it just went back to doing the same thing.
Dominic
I just ran into this issue myself. My 2nd Gen is running a rooted rom and has worked fine for a couple years but tonight we were watching some Hulu and the screen went blank in the middle of a show. I did a power cycle and it boots to the TWRP boot screen, then I get the white amazon logo. After which, the TV loses signal. The device seems to boot for a short while before getting the pulsing white LED.
I can still go into TWRP and access everything so I've performed a full reset which changed nothing. I also downloaded and installed an updated ROM July 4, 2020 - 5.2.7.3_r1 but it responds exactly the same after the update.
Fortunately I have a spare Fire TV 2 (thanks ebay) so I was able to swap things over pretty quick. This also confirmed the power adapter was not the issue as the replacement seems to be working fine with the same adapter. I also tested the original one with a 15.5v, 3.4amp adapter and no change. I feel like maybe the video processor may have burned up at this point.
Still open to any suggestions though.
Hannover2k said:
I just ran into this issue myself. My 2nd Gen is running a rooted rom and has worked fine for a couple years but tonight we were watching some Hulu and the screen went blank in the middle of a show. I did a power cycle and it boots to the TWRP boot screen, then I get the white amazon logo. After which, the TV loses signal. The device seems to boot for a short while before getting the pulsing white LED.
I can still go into TWRP and access everything so I've performed a full reset which changed nothing. I also downloaded and installed an updated ROM July 4, 2020 - 5.2.7.3_r1 but it responds exactly the same after the update.
Fortunately I have a spare Fire TV 2 (thanks ebay) so I was able to swap things over pretty quick. This also confirmed the power adapter was not the issue as the replacement seems to be working fine with the same adapter. I also tested the original one with a 15.5v, 3.4amp adapter and no change. I feel like maybe the video processor may have burned up at this point.
Still open to any suggestions though.
Click to expand...
Click to collapse
Idk if it helps, but I would try a format data in wipe section of TWRP.
Could be that the eMMC died, i.e. at an unknown point, the storage switches to readonly, especially if the eMMC is a samsung chip.
Booting TWRP still works, in that case.
This happend to @Rortiz2 fireTV2 development box, maybe ask him for details.
What kind of errors are in the recovery log?
Sus_i said:
Idk if it helps, but I would try a format data in wipe section of TWRP.
Could be that the eMMC died, i.e. at an unknown point, the storage switches to readonly, especially if the eMMC is a samsung chip.
Booting TWRP still works, in that case.
This happend to @Rortiz2 fireTV2 development box, maybe ask him for details.
What kind of errors are in the recovery log?
Click to expand...
Click to collapse
I don't know how to get to the logs but happy to post if you can tell me.
On another note, I noticed the replacement device, while just recently connected and has also been rooted, tried to download the 5.2.7.4 update today. Typically my rooted devices never updated so this is a new discovery. I pulled the plug on it before it finished downloading but I'm worried I'll loose root if it updates. There's no pre-rooted ROM for 5.2.7.4 yet so I'm afraid to plug the power back in for fear it will update and unroot/brick like the 1st one.
Hannover2k said:
I don't know how to get to the logs but happy to post if you can tell me. .
Click to expand...
Click to collapse
Boot into TWRP, click mount and mount system, start the filemanager (in advanced tab), then go to /tmp, in there should be a recovery.log file, copy this file to your ext. sd or adb pull it to your PC.
Edit your serials in the file and upload it on mega, gdrive or so.
Hannover2k said:
On another note, I noticed the replacement device, while just recently connected and has also been rooted, tried to download the 5.2.7.4 update today. Typically my rooted devices never updated so this is a new discovery. I pulled the plug on it before it finished downloading but I'm worried I'll loose root if it updates. There's no pre-rooted ROM for 5.2.7.4 yet so I'm afraid to plug the power back in for fear it will update and unroot/brick like the 1st one.
Click to expand...
Click to collapse
For the sloane (aka fireTV second gen box), the prerooted rom installer disables the stock recovery, so nothing should happen if you let the ota updater do its thing...
But its best to disable the ota process with that:
Code:
adb shell
su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
exit
exit