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.
Related
OK...I'm a first time poster to the Kindle Fire forum and I'm having issues. I'm a little above average with my Android knowledge. I've flashed CM9 onto three Toucpads and have been fooling with my phones for a few years. HOWEVER, I'm completely stumped. Here's what's happening and what I've done.
1) I downloaded Kindle Fire Utility to root. It all went fine, as far as I could tell.
2) I downloaded the aokp_otter_build-M5>0xD34D build for CM9
3) I downloaded the gapps-ics-20120429-signed zip
4) Booted into the TWRP recovery
5) Made a backup of the stock Kindle
6) Flashed the CM9 zip and the Gapps zip. Everything seemed fine with the TWRP. Never used it before. Very familiar with CWM and seemed similar
7 Rebooted.
The Kindle Fire logo came up and then went to a blank screen. It boot-looped (is that a verb?) five or six times. While I went surfing to find answers it looped once more and came up to this screen with a pissed off looking unicorn and the Team Kang logo. It's stuck there and won't go past. The screen is still animated. The battery is not dead. I've read dozens of posts where the first suggestion is to charge the Kindle. That's not the problem. I've restarted the Kindle a hundred times and nothing.
Here's what I've tried:
1) Every combination of holding down the power button/pressing the power button combination. Nothing.
2) Downloaded the Kindle Unbrick Utility. The computer isn't recognizing the Kindle, so this isn't doing any good. I've tried all of the six different UI buttons. Nothing.
3) I went back to the Kindle Fire Utility and reinstalled the drivers and then opened the CMD window. As I expected, it's telling me "waiting for device" and doing nothing.
I have no idea where to go from here. There's got to be a way for me to get this thing to be recognized on my computer. Please help. Any advice would be greatly appreciated. Thanks! -Jeff
It's like deja vu...
http://forum.xda-developers.com/showthread.php?t=1658205
Even the description of the bootanimation is eerily the same.
I think my assessment of his problem would apply to you as well. If you want to skip most of the discussion, my post is at (or very near) the end.
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
jeffjoleen said:
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1550999
Probably wouldn't hurt for you to look this over either...
http://forum.xda-developers.com/showthread.php?t=1552547
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Thepooch said:
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
Click to expand...
Click to collapse
Honestly...don't remember if I did a full wipe of dalvik. I assumed I would have, but really don't remember. No...I don't get the yellow triangle and my kindle fire logo color is white "kindle" with a yellow "fire". I used the kindle fire utility and I think that installs the twrp by default. I don't have CWM installed. Wish I did. I'm comfortable with it. I just can't get to any kind of a recovery screen.
soupmagnet said:
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Click to expand...
Click to collapse
Yes...the KFU went fine, I think. I was able to access twrp and created my backup before I flashed the ICS. The Kindle logo has the white "kindle" and yellow "fire". Pauses for a few seconds or two...screen goes black...then that damned pink unicorn shows up and stays there. The unicorn screen is animated. I can power it down from there and start over without any problem. Any ideas?
without a bootloader you wont have access to recovery regardless of twrp/cwm
One other thing that I'm not sure matters, but when I do power it off and back on, I head the little "bong" on my computer telling me that a new device has been plugged in. I go to the device manager and under the "Other" category it shows "Amazon" with the yellow triangle the black exclamation point symbol.
Reinstall your drivers
Thepooch said:
without a bootloader you wont have access to recovery regardless of twrp/cwm
Click to expand...
Click to collapse
I guess that's where I am a little confused with definitions. I understand about the twrp and cmw recovery set ups. What exactly is a bootloader? Thanks for not laughing...
Thepooch said:
Reinstall your drivers
Click to expand...
Click to collapse
Through the Kindle Fire Utility? If so, I've done that several times. Would trying a different computer and installing them there make any difference?
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
First, read this...
http://forum.xda-developers.com/showpost.php?p=23747567
You need to make sure your drivers are in order so you can change the bootmode to 5001 and reboot. A custom bootloader will let you do this easily but considering you don't have one you need to use adb instead.
Code:
adb shell
idme bootmode 5001
adb reboot
Thepooch said:
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
Click to expand...
Click to collapse
So, without a functioning bootloader I won't even be able to get to the twrp to access my back up I made. Nice. Just bought this damn thing yesterday. I'm kinda missing the one-click jailbreak software from my old iphone a few years back!
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
I just read through the basic instructions. I'll grab a usb thumbdrive and give it a shot. Thx
good luck hope you get through this is the not so fun side of rooting
Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks. It answered some of my questions. I guess it helped me relax a little, too. I know this is a problem that can be fixed. Just need to dig in an try each suggestion until I find one that works.
I believe im having the "5 second bootloop" problem, no idea why since my KF was never rooted, flashed, or modified in any way. I plugged the Micro B in the KF (KF was off) and then plugged the Type-A end into my PC, the KF turned on in like 10 seconds (maybe less) and it isn't doing the bootloop anymore which i guess is a good thing but its been like 10 minutes and it still just says kindle fire (with a green light on the bottom). What should I do from here for my specific situation? Any help would be great! Thanks in advance!
edit: just wanted to add that before when i would plug it in, it would keep rebooting and usually not even get to the slide to unlock screen, but sometimes it would and then instantly reboot again.
First off...what bootloader do you have installed?
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Untraumatized said:
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Click to expand...
Click to collapse
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Untraumatized said:
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Click to expand...
Click to collapse
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Untraumatized said:
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Click to expand...
Click to collapse
you still there buddy? lol, i unplugged it and ya that worked, so now im at TWRP, just because it seems like a good idea i am backing up the things that were already checkmarked when i clicked backup
but now im afraid to continue without help, what step am i at exactly now? lol
EDIT: stuck at the end of the backup, been stuck there a while, will probably try to turn it off in a few minutes or so... anybody have some advice?
How about a little more information about what it is you intend to accomplish with your device?
soupmagnet said:
How about a little more information about what it is you intend to accomplish with your device?
Click to expand...
Click to collapse
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Untraumatized said:
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Click to expand...
Click to collapse
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Untraumatized said:
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Click to expand...
Click to collapse
well i managed to fix it by just factory resetting it with no help AT ALL
Very likely the factory reset had nothing to do with it. Just simply having it plugged in via USB may have given it enough time to charge. Questions of this nature are best handled in q & a not in development.
Untraumatized said:
well i managed to fix it by just factory resetting it with no help AT ALL
Click to expand...
Click to collapse
I'm sorry for not sitting at my computer, waiting with baited breath for you to respond, so I can devote all of my attention to your problem. I hope you can forgive me.
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Untraumatized said:
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Click to expand...
Click to collapse
Correct me if im wrong but you can't delete posts....but this thread should not be in Android Dev section, it should be in Q and A... Not to be mean or anything I am going to report this thread so it can be moved to the right section (to help the mods out)
OP, First This Thread Is In The Wrong Place. And It Appears To Me Users Where Trying To Help, On Limited Information. But You Figure It Out On Your Own Great.
Thank You And Thread Closed.
The Problem I am having seems to be a Infinite boot logo after Undoing a custom Otter jelly bean KF rom. I went through the motions of ADB KFU booting into recovery. I factory restored, wiped and attempted to install my back up of the stock kindle fire rom. wiped caches, and then let it do its "boot up" how ever it did not move past that point, and has been stuck at the "kindle fire" logo screen.
Is there anyway to fix what I probably broke?
KFU Utility vers 0.9.6
TWRP vers 2.4.4
OS version Windows 8 X64
Kindle fire Rom version 6.2.1
Otter jelly bean was 4.2.1 a release sometime in February is the closest I can get. I can't exactly roll back now can I?
Any other information I forgot or neglected to supply on first post was unintentional. First time I have ever had a problem.
Thanks in advance
~ Zach
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
jakeyablosky said:
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
leroy329 said:
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
Click to expand...
Click to collapse
I think you're having the same problem I'm having. If you look at my post regarding stuck at logo that I posted yesterday see if it's the same.
What is your logo doing? Does it stay bright or does it turn on and blink and then fade?
Based on what I've read we need them to get them into fastboot and then side load TWRP and FFF and start again.
I think what we've done is removed or cleared too much in TWRP and our bootloaders are broken, but I could be talking out of my you know what.
Good luck to you and I will follow your thread and you may want to follow mine.
The only thing I can think of is getting a Factory Cable and reset you Kindle Fire
Sent from my Nexus 7 using xda app-developers app
Leroy,
I think Jakey has it.
I was just about ready to pitch this thing in the trash and I decided to plug in my factory cable one last time and run KFU.
For whatever reason I decided to select the root option again even though it said status offline and it rerooted my device.
My logo is now white/blue and I think I can get a rom back onto it.
You may want to hit Skorpn up for a cable, he shipped it super fast and it's great work.
Leroy,
Since it seems you are having the same problem I was and replies are pretty slow in here these days (I'm sure most people are tired of repeat posts like mine), I thought I would post precisely what I did to fix mine.
I too had the infinite boot logo that stayed bright and tried everything from KFU, to unbrick tool, to Soupkit, nothing seemed to work. I bought a factory cable from Skorpn, but didn't really understand how to use it. I think there is so much information here and many various ways to get things fixed it takes awhile to digest it.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
Device said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Again, Skorpn was awesome to work with and sent the cable to me quickly.
Good luck to you!
Hi Everyone
As a new user here, thanks in advance for any help that you can give me.
I've got a KF2, running 10.4.1 (I think, or maybe 10.4.3) - it's rooted, but generally stock apart from that (no TWRP).
It was left with something playing and the battery ran down to nothing yesterday. Initially it would charge, sometimes with the red light on and sometimes not, but then it would start up and as soon as it got to the lock screen it would give a low battery noise and shut down.
After leaving it plugged in overnight it is now charged but it is getting stuck on the animated kindle fire boot logo.
If I plug it into my PC it is detected in windows and I can connect to it with ADB with no obvious errors on logcat. Easy options like clearing the dalvik cache don't fix anything (only AmazonPlatform and atlasframework get recreated in the dalvik cache before it sets into doing nothing).
Searching the forum here, there are lots of different avenues discussed for "stuck at boot logo" problems - I'd appreciate some pointers on the most sensible things to try.
Thanks
Try a system restore with kindle fire first aid.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hello, it seems that you face the same issue as I met last week with KF2 that I got for free. The KF2 got a boot problem after a low bat event and nobody was able to get him back. I seems thats the same issue. While I wasn't able to establish adb i used fastboot with a homebuild factory cable. (Forget KFfirst aid) Take a look on this thread: http://forum.xda-developers.com/showthread.php?t=2698935 - After formating cash and userdata user let him charging for a while on the pc usb port. Next day he returned booting showing a untouched KF2 with factory setup. Rootet him and gave him a CM11. Grate tablet for free. Take care, after formating cash and user he doesn't came back imidiatly Let him for some hours in the fastboot screen blinking his green led on screen. Next day he came back booting. My suspicion is a sw bug regarding low battery events. After cash and userdata format he need to develop valid boot conditions regarding the battery or other stuff. Who knows... But after the procedure he came back without further flaws.
Send via Tapatalk - HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
Thanks for the assistance guys. Sorry for not coming back sooner - I couldn't get my password to work this morning!
I tried restoring to 10.2.3 using KF first aide - after sitting in fastboot for ages downloading the images it flashed ok and then went back to the empty battery screen after it restarted. It stayed like that for so long I thought it was still broken, but eventually it booted back into the kindle launcher.
As I was going from 10.4 back to 10.2.3 I wiped the cache and userdata. Used ADB to get as much data off it as I could first - could I have safely used any of the KF first aide backups on it first?
One weird bit - I've rooted using bin4ry/qemu and used KF First Aide to disable OTA and install google play, maps etc, and now location services don't seem to work any more. Maps, Chrome, Silk, BBC Weather - they all give the location icon in the notification bar but then can't get a location fix.
This is why I don't use Amazon os... Seems like small things like this happen because we either forget to put something on the device that is needed or the os just breaks something like this out of nowhere. In my opinion its easier to avoid these kinda problems altogether by flashing cm but that's just my take, if you want amazon os then keep it. That sounded grouchier than I intended.
Sent from my Amazon Kindle Fire HD using Tapatalk
Stunts513, yes, AOS stucks out of nothing and your gone. On that way a got a kindle for free that entered in a boot loop after a low bat event and even USB recovery doesn't worked worked out by failing and access. Only fastboot and a CM makes that tablet working for real
Send from HTC Sensation - Android 4.4.3 - CM11 - Kitkat
Hi there. My fire TV is rooted and has the following installed:
clockwork mod custom recovery
51.1.4.0_514006420 updated 10/30/2014 Custom rom
I was initially experiencing strange behaviour with my external hard drive converting to a read only drive after a while for no apparent reason so decided to do a factory restore
I tried to factory restore the device but for some reason after the factory restore and watching the funny cartoon on set up the device said I only had 2.5gb of hard drive space left of the 5.5 gb available so I decided to try formatting the data on the clockwork mod restore but it still didn't work so I then formatted the sd but as soon as I did this I thought that can't be right as surely the recovery image is on that but it was too late. After it rebooted the fire TV no longer works. It just hangs on the White amazon logo. I've tried the "ALT-PRNT SCREEN-I" option to try get it to restore but with no luck, it just constantly stays on the White amazon logo so I'm kinda thinking I've totally wiped the fire TV and have therefore bricked it. It does respond to "control-alt-delete" but that just reboots the device.
Can anyone advise if this is indeed the case so I don't waste any of my time trying to fix this. I can't return the product as I purchased it on a recent holiday to usa and I'm from uk so a bit gutted.
Many thanks in advance
Paul1672
Sounds like you wiped your /system. If so, then yes you are soft bricked.
I have soft bricked this unit before and managed to restore it but that was before I installed the clockwork mod and custom rom.
If it is soft bricked surely I would be able to restore it still? I have tried several times to get it to return to the clockwork mod restore using the "ALT-PRINTSCREEN-i" method but all I get is the constant white Amazon logo. It feels like I've totally wiped the entire system including all sign of clockwork mod
Can anyone advise if I have indeed totally messed it up or is there any hope for me?
Paul
Anybody got any advice or opinion be it good or bad?
Before I bin the unit
Paul
Paul1672 said:
Anybody got any advice or opinion be it good or bad?
Before I bin the unit
Paul
Click to expand...
Click to collapse
Yes, I have some advice. Don't do that crap again. Be smart. And I'm a bit curious, you talk about an external harddrive and you then talk about wiping the SD card. You mean the /sdcard directory in the AFTV? Seriously? If that is the case, I have some better advice for you. Don't tinker with stuff you don't understand.
So I can assume from your reply I have indeed wiped the entire system and there is in fact no way to repair/restore the device? Totally agree with all you said and I did realise my error literally as soon as I did it a harsh lesson learnt I think and believe me it's not one I will be repeating.
Was just hoping I may be lucky and find someone who has a way of solving my issue but it appears not
Paul
Hi
What's your suggestion or advice be to resolve the problem that was presented.
Cheers
nyder said:
Yes, I have some advice. Don't do that crap again. Be smart. And I'm a bit curious, you talk about an external harddrive and you then talk about wiping the SD card. You mean the /sdcard directory in the AFTV? Seriously? If that is the case, I have some better advice for you. Don't tinker with stuff you don't understand.
Click to expand...
Click to collapse
Paul1672 said:
So I can assume from your reply I have indeed wiped the entire system and there is in fact no way to repair/restore the device? Totally agree with all you said and I did realise my error literally as soon as I did it a harsh lesson learnt I think and believe me it's not one I will be repeating.
Was just hoping I may be lucky and find someone who has a way of solving my issue but it appears not
Paul
Click to expand...
Click to collapse
Naw, you didn't brick you device. Sorry, was in some sort of mood when posted.
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
That link gives information. You need to get into recovery mode and a factory restore. If the factory restore doesn't work, then just use the same firmware you had before you deleted the stuff. You can put any firmware on a usb stick and read it from that.
Most of this has been covered in the various threads, I suggest you browse thru them, lots of good stuff.
good luck, and sorry I didn't include this in my last post, i should of.
Are u sure mate? I've tried the Alt-prntscreen-I method without any success. The fire tv won't boot into the clockwork mod recovery at all and I'm wondering if I've formatted it somehow. I guess until I get into the restore screen I can't do a thing I did have clockwork mod installed and a custom rom, wud that make a difference as I did indeed format the fire tv sd partition.
Appreciate your help
Paul
Paul1672 said:
Are u sure mate? I've tried the Alt-prntscreen-I method without any success. The fire tv won't boot into the clockwork mod recovery at all and I'm wondering if I've formatted it somehow. I guess until I get into the restore screen I can't do a thing I did have clockwork mod installed and a custom rom, wud that make a difference as I did indeed format the fire tv sd partition.
Appreciate your help
Paul
Click to expand...
Click to collapse
You should be able to get to a recovery screen from what you did, I would think, unless maybe if you deleted everything from the root directory, not the sdcard directory. I am not an expert on that though. It's our thanksgiving holiday here in the states, so the peeps that know might not be around.
Sorry I can't be more helpful then that.
You copy your recovery.img to the sdcard only as an interim step for flashing. It then gets stored in a separate partition that CWM won't wipe. If you have done the changes you mention from CWM, then CWM is still present on the device. I had to get in to my system with the alt-prtscreen-I method as well, and it took a few tries, spamming the keeps after unplugging and replugging the device. Also if you are using a k400 or some other keyboard with a FN key you may have to push that as well to make sure it gets the proper key sequence. I'm fairly confident your device is only softbricked and can be recovered. you may need to adb sideload or copy a zip to usb to load the firmware, but it should be doable.
well, I've tried constantly rebooting and pressing alt-printscreen-I simultaneously for the last half hour with no luck wotsoever all I get is the constant white amazon logo. in fact, the logo appears as soon as I connect the power lead and just hangs there until I either remove the lead or press control-alt-delete at which point the device reboots.
something tells me I've done something a lot more serious than just wipe the sd partition but I'm a little surprised if clockwork mod would allow it.
kinda giving up now as I have soft bricked the device before but that was before I installed clockwork mod and it went to factory restore just fine doing the alt-printscreen-i method that time.
thanks for all the advice guys. I really do appreciate any help I have had. I'm willing to try anything to try get this unit to work. the way I see it, I have nothing to lose right now. just seems strange the unit no longer shows any sign of changing from the constant white amazon logo. there's definitely no sign of the colourful amazon logo that usually appears at some point during the boot process which kinda gives me the impression I've somehow completely wiped the whole system.
is that even possible guys?
If you are saying that ctrl-alt-del reboots your box then the alt -sysrq-i should get you to recovery. Try using a wired keyboard and maybe a different keyboard than you have been using.
Ive tried a wired keyboard and now when I press ALT-PRNTSCREEN-i the fire tv just reboots. I've followed the guide that is in a previous reply which I have been able to do on a previous unrelated soft brick I managed but this time each time I do the ALT-PRINTSCREEN-i combo it just reboots and nothing else. Just a white AMAZON logo. I have done the method like 5 times and still no joy
Paul1672 said:
Ive tried a wired keyboard and now when I press ALT-PRNTSCREEN-i the fire tv just reboots. I've followed the guide that is in a previous reply which I have been able to do on a previous unrelated soft brick I managed but this time each time I do the ALT-PRINTSCREEN-i combo it just reboots and nothing else. Just a white AMAZON logo. I have done the method like 5 times and still no joy
Click to expand...
Click to collapse
Call Amazon and play stupid saying it just hangs at the logo, I did that once and they send me a replacement free of charge.
Wish I could but i purchased it whilst on holiday in Florida and I'm from the uk
Anybody got any more advice? It seems really strange that I can't get the factory reset to work. Still stuck on the White Amazon logo which boots instantly as soon s I power the device. I've managed to get the device to power cycle using ALT-PRNTSCREEN-i method bit it's does it going on 20 times with absolutely no sign of the failed update screen so it looks like the device just doesn't have anything on it. Is it possible I've somehow completely wiped the clockwork mod recovery? And if I have shud the device revert back to factory restore or may I of wiped that too?
Paul1672 said:
Anybody got any more advice? It seems really strange that I can't get the factory reset to work. Still stuck on the White Amazon logo which boots instantly as soon s I power the device. I've managed to get the device to power cycle using ALT-PRNTSCREEN-i method bit it's does it going on 20 times with absolutely no sign of the failed update screen so it looks like the device just doesn't have anything on it. Is it possible I've somehow completely wiped the clockwork mod recovery? And if I have shud the device revert back to factory restore or may I of wiped that too?
Click to expand...
Click to collapse
no its not possible that you wiped recovery from what you did in cwm.. its located on a different partition, if you cant connect via ADB or cant get recovery to load your out of luck.. so did you install the newest prerooted rom? what about the boot menu?
I had the following pre-rooted rom installed:
51.1.4.0_514006420 updated
Sounds like I've messed it up then
Paul1672 said:
I had the following pre-rooted rom installed:
51.1.4.0_514006420 updated
Sounds like I've messed it up then
Click to expand...
Click to collapse
no need for the boot menu on that update iirc. i think you need to just keep trying to get to recovery, i think its still there.. the key command is just not registering.. keep trying i guess.