hi guys, im sorry if this issue has been solved before, but ive looked everywhere, used the search button. googled my face off, and STILL cannot find a solution to my problem... i rooted my fire with the 5th gen super tool, and was running cm12.1 on it for a while with no problems. i went away for a week, and left my kindle at home. when i got back, the battery was dead, and when i plugged it in it wouldnt get past the "amazon" logo, and it just loops the amazon logo repeatedly. i have tried booting into recovery, i have tried numerous "unbrick tools" etc, but i dont even think my computer is recognizing my fire. i had all the device drivers correctly installed because it was working fine, and now i cant figure this out at all. any help would be greatly appreciated.
justin926 said:
hi guys, im sorry if this issue has been solved before, but ive looked everywhere, used the search button. googled my face off, and STILL cannot find a solution to my problem... i rooted my fire with the 5th gen super tool, and was running cm12.1 on it for a while with no problems. i went away for a week, and left my kindle at home. when i got back, the battery was dead, and when i plugged it in it wouldnt get past the "amazon" logo, and it just loops the amazon logo repeatedly. i have tried booting into recovery, i have tried numerous "unbrick tools" etc, but i dont even think my computer is recognizing my fire. i had all the device drivers correctly installed because it was working fine, and now i cant figure this out at all. any help would be greatly appreciated.
Click to expand...
Click to collapse
If the device is bootlooping​ at the Amazon logo your only realistic recourse is to reload FireOS (same build that was previously installed or higher) from the recovery menu. Even that is dubious; if the bootup process is not progressing far enough to start whatever ROM is in system partition the device is toast.
Keep working on trying to establish communication while in stock recovery. See below for possible hints/tips. Also try a different cable and USB port on your computer.
https://forum.xda-developers.com/am...n-fire-2015-tips-tricks-t3214544/post63072252
Related
I have a stock KFHD 7" that is stuck in the boot loop. I have a factory cable and am trying to complete the process outlined here: http://forum.xda-developers.com/showthread.php?t=1951254
The problem is that the Kindle shows it is in fastboot and withing 2-5 seconds shuts down. In that 2-5 seconds I can see it in the Device Manager but it then disappears as it shuts down. It should be charged as it has been plugged in for 4-5 hours. Any ideas what I can try to fix the problem?
FYI... I already received a replacement Kindle from Amazon. They did not seem to want this one back so I thought I would try to get it working.
Try Kindle Fire First Aide....backup all partitions from new kindle into kindlebackup folder and then on old device put restore from kindlebackup folder.....it should work even to the worst of bricks, trust me I know because this kindle I'm using now was bricked to the point where partitioning would fail as soon as it booted up.
stolen from my drunk kindle by Tapatalk 4
Just curious, did this happen after trying to flash 2nd boot loader? I am just curious since your device shuts off after going into fast boot, seems almost like a boot loader malfunction. Usually when I see this problem of fast boot shutting off it also follows with "my PC starts detecting an omap4470 device" but you said yours will still boot into boot loops normally so this is weird. At least its not detecting an omap4470 device.
Thought I'd mention u can try what south956 mentioned, but personally I have my doubts if fast boot won't stay on more than a few seconds, it would take a lot longer than that to reflash the system image since its a few hundred mb. I suggest flashing the boot(aka the kernel) and maybe the boot loader, but if it shuts off in the middle of the boot loader flash you would most likely have a fancy doorstop. Until I know more I would follow south956's instructions and see how it goes, because as I said your situation is a bit weird to me.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
south956 said:
Try Kindle Fire First Aide....backup all partitions from new kindle into kindlebackup folder and then on old device put restore from kindlebackup folder.....it should work even to the worst of bricks, trust me I know because this kindle I'm using now was bricked to the point where partitioning would fail as soon as it booted up.
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
Thanks, I'll look into Kindle Fire First Aide
stunts513 said:
Just curious, did this happen after trying to flash 2nd boot loader? I am just curious since your device shuts off after going into fast boot, seems almost like a boot loader malfunction. Usually when I see this problem of fast boot shutting off it also follows with "my PC starts detecting an omap4470 device" but you said yours will still boot into boot loops normally so this is weird. At least its not detecting an omap4470 device.
Thought I'd mention u can try what south956 mentioned, but personally I have my doubts if fast boot won't stay on more than a few seconds, it would take a lot longer than that to reflash the system image since its a few hundred mb. I suggest flashing the boot(aka the kernel) and maybe the boot loader, but if it shuts off in the middle of the boot loader flash you would most likely have a fancy doorstop. Until I know more I would follow south956's instructions and see how it goes, because as I said your situation is a bit weird to me.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The kindle was original from the factory and I had not tried to install anything or root it. I'll see what I can do with Kindle First Aid and then look into just trying to flash the boot. I'm not holding my breath since it will not stay on for long.
Try the boot like stunts says of anything try extracting your new kindle's boot and transfer it to your old, I did this to my bricked from my new
stolen from my drunk kindle by Tapatalk 4
Thanks for the help guys, but I'm throwing in the towel. I just can't keep the kindle on long enough to get anything accomplished.
Yea this is one of those situations where I would use Linux to try to fix your problem, it loads up devices a lot faster than windows, because it just loads up a module as soon as then device is connected. Because of the faster response time it might be possible to flash. This thread seems very similar to another thread I have been helping with, except his shows up as a omap4470 device about 5 seconds after fast boot comes up then disappears. If your interested in taking a look here's the link:
http://forum.xda-developers.com/showthread.php?t=2314715
The thing that's weird in these situation is I think the boot loader partition might be screwed up, which is what would cause fast boot to not want to stay running, from what I understand fast boot mode is stored in the bootloader. So since u already have another kindle, then I guess this isn't as risky, because if u brick it you already have another. What I was saying in the other thread is to try and flash the bootloader in Linux before the device shuts off, now this is risky because if it shuts off mid-flash u have a nice paperweight. Luckily though the bootloader is very small, think its around 8mb, so as long as you are on USB 2.0, then it should flash rather quickly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
im having the same problem as op but in my case the kindle shows as malfunctioning when connected win10 cant even get it to show in device manager. constantly connecting and disconnecting as it loops
Hey guys!
So I have ran into an issue, I just got a brand new Amazon Kindle Fire HD 7", it has the 1.5 GHZ processor.. ect. Anyways, so I wanted to install some system updates and I didn't want to allow it to do that because I was afraid I would loose my ability to root, so I shutoff the device. Well like an idiot, it booted back up and displayed the message again, saying it was updating, I did it a second time, powered the device down, and now I am stuck after the Amazon boot logo, basically I just get a lit black screen. However I can access the adb interface, only issue is that the device is unauthorized.. (Something else I didn't think of). I tried to enter fastboot but it just says waiting for device.
So is my only option left is to get a Fastboot cable? What mode is the device stuck in? It's not bricked right since there wasn't any custom anything installed, just an interrupted system update. Should I attempt to get a replacement from Amazon?
Thanks a ton,
Matt
If you get a fastboot cable, you can forcefully restore the O.S....but you're covered under warranty so you can return it
Hi Guys,
So first I'll apologise incase someone has posted a way around this and I haven't found it, so it would be great to direct me to the right page or something.
So I have rooted and installed cyogenmod with what I believe was KitKat OS. It was working fine, however I went into the settings and saw that CM had an update and so I updated it. It updated the OS to Lollipop, but nothing was working everything crashed, so I went to settings and performed a system restore, however from here on I just get a weird boot loop.
So I turn the Kindle on, get the orange logo, the blue logo, the teamwin screen, this then flashes black, comes back on, flashes black etc. It never gets past the teamwin screen.
I have a fastboot cable, which puts the kindle into fastboot mode, but I don't know what to do with it any more as I have a Mac know and so running OS X not Windows. I have used VirtualBox to have Windows on here but not sure if that will work?
Any help would be appreciated, thanks!
Hello and good morning.
I am writing here, because I have a big problem. My Kindle Fire HD (first Generation) does not start any more. After an update (Cyanogenmod tate) I only get the yellow Kindle fire logo. And after few seconds the Kindle starts again. Then - after about five minutes - everything is dead. But if I do a reset I get the same situation. Unfortunately I get no connection to my device via the computer (tried Windows 7 64 bit and Ubuntu). With adb devices I cannot detect my Kindle. Is there a possibility to get into fastboot to install CWR etc.?
Help me, please
Herbert
So to clarify, the first time the logo comes up it freezes and then resets itself, followed after about 5 minutes the kindle just shuts itself off?? Also, you ask about getting into fastboot to install CWM. Do you not have a recovery installed? Such as CWM or TWRP?
I installed TWRP version 2.6
But I also cannot boot into the recovery (Power on & Vol +). Then nothing happens. I actually have ordered a fastboot-cable. Maybe I have success with this cable. Otherwise it is finished for me.
Yea try booting into recovery and flashing the system images to get back to stock. That's all i can think of since i'm not entirely sure what happened, either you got a bad download or your kindle just flipped out and essentially bricked itself.
The story goes:
Last week I rooted my Kindle Fire. I used a YouTube tutorial and successfully achieved root. The YouTuber also recommended installing TWRP, so I thought heck, why not, and went ahead and did it.
That's where everything went wrong.
I decided to unroot my Kindle, which went fine, until I got to uninstalling TWRP. I heard the only way to get rid of it was to flash the stock ROM, so I did. When I flashed it, I got an error, and my Kindle just shut off. When I try to turn it back on, it will power up and show the screen with the Amazon logo on it and that's it. Tried again and again, and yet it stays on that Amazon screen and doesn't move.
Any ideas?
Thanks in advance.
I am having the same issue. Updated kindle fire 6 hd 4th gen to 5.0, downgraded to 4.5.3. Installed king root, rooted device, installed flashify, flashed twrp, rebooted. Now I am stuck loading. If plugged into a computer loads to the amazon logo, shuts down, loads to the logo repeat.
I have tried to fast boot by correcting drivers in device manager for the mtp whatever and constantly spamming the fast boot string.
I have used adb to see if a device ever loads and it doesn't.
Windows makes teh sound that a new device is connected for about 15 seconds then will make the noise that a device has been disconnected as the fire reboots.