I have a Kindle Fire HDX 8.9 3rd gen that I rooted running the 4.5.5.1. It popped up a message saying I should upgrade to 4.5.5.2, and dumbly I allowed it. Now it boots up to the "Fire System Recovery" menu, allowing me to "Reboot your Kindle" or "Reset to Factory Defaults". Both options ultimately lead back to this menu. I assume this was caused by the root.
I attempted to use the KFHD recovery tool from here: http://forum.xda-developers.com/showthread.php?t=2011126
But it sticks on the "waiting for devices". When I reboot the kindle while connected to my Win10 PC, the PC recognizes a device for about 15 seconds, then disconnects. As mentioned, the recovery tool never recognizes the device.
I'm in over my head, how do I get the kindle up and running again?
Jozer99 said:
I have a Kindle Fire HDX 8.9 3rd gen that I rooted running the 4.5.5.1. It popped up a message saying I should upgrade to 4.5.5.2, and dumbly I allowed it. Now it boots up to the "Fire System Recovery" menu, allowing me to "Reboot your Kindle" or "Reset to Factory Defaults". Both options ultimately lead back to this menu. I assume this was caused by the root.
I attempted to use the KFHD recovery tool from here: http://forum.xda-developers.com/showthread.php?t=2011126
But it sticks on the "waiting for devices". When I reboot the kindle while connected to my Win10 PC, the PC recognizes a device for about 15 seconds, then disconnects. As mentioned, the recovery tool never recognizes the device.
I'm in over my head, how do I get the kindle up and running again?
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Ah, thank you for pointing that out. I didn't find a similar tool for the HDX on XDA, does one exist?
On my windows 10 computer, the Kindle briefly shows up to ADB as "0123456789ABCDEF UNAUTHORIZED" and I can't run any commands on it.
I'm trying to get a 32 bit windows 7 machine up and running, since most of these tutorials seemed to be aimed at older OSes.
Is there any hope?
Ok, I got a Windows 7 32 Bit machine running and installed with Android SDK, fastboot, and ADB. As I mentioned previously, my kindle is only "detected" by my computer for about 30 seconds before it disappears. The same is true on the Windows 7 box, unfortunately. When I run "adb devices" while the device shows up, it comes up with "0123456789ABCDEF unauthorized". When I run fastboot devices, it doesn't find anything.
How can I get my device detected properly?
How can I get the kindle to stop in ADB/fastboot mode so I have more than 30 seconds to try things?
Related
First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.
Lyrekz said:
First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.
Click to expand...
Click to collapse
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?
kinfauns said:
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?
Click to expand...
Click to collapse
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.
Lyrekz said:
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.
Click to expand...
Click to collapse
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
kinfauns said:
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
First of all. thank you for the help. And now my Kindle is stuck on the Kindle Fire screen.
Mine is stuck here too..been 3 days.. ordered the factory cable.. hopefully that works.
One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium
Readyreadyready
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
soupmagnet said:
One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
larmores said:
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1096 using XDA Labs
I've attempted to root my kindle fire with the kindle fire utility and it wasn't 100% successful.
Im stuck on the kindle fire screen where it's booting up and it's on an endless cycle whether
plugged into the computer, or charging through the outlet. It's also completely unrecognized
when I do plug it into my laptop. Any help would be greatly appreciated to unbrick it.
Important: When the battery wasn't dead it just stayed at the kindle fire and recognized.
But using Kindle Fire Utility and a few other unbricking programs could not find the device.
uh yeah a usb drive, pedrive universal usb creator and this http://forum.xda-developers.com/showthread.php?t=1850038
I had a similar experience today rooting my friends kindle fire... The kf utility kept giving me a error, something about removing a root check. And it just kept booting into recovery so on boot up where twrp gives you the 3 options... Normal boot, recovery, or change bootmode I just selected change bootmode and it booted right on up and worked fine...root is good and alls was well every since... Not saying this will solve your problem but just figured I'd share incase... Goodluck!
Sent from my Galaxy Nexus using xda app-developers app
Here is what I did to fix mine
Hello,
First things first, did you have ADB installed correctly?
I had the same issue that you are having now and I was freaking out.
I was sure my kindle was bricked and my wife was going to be pizzed at me.
After about 2 hours of searching the forums, I found out that getting stuck at the kindle logo screen is pretty common.
When you are stuck at this screen you are stuck in "fast boot"
Here is what I did to fix mine.
Mine was having the exact same issue as yours.
I could not get my PC to recognize my kindle at all and I was stuck at the logo screen.
1. Unplug kindle from PC
2. Hold down power button for 30 seconds until it powers off
3. Plug kindle into PC and power it on
4. More than likely PC will still not recognize it
5. Open Kindle Fire Utility program and choose Option 1 for boot menu
6. Then press 1 again to tell kindle to boot normally and press enter
7. The KFU should say something like "kindle is being told to boot normally"
8. Once kindle reboots, you should be good to go
9. PC should recognize kindle now
I would say once this is done, uninstall your drivers for kindle and reboot your PC
Once PC is back up, reinstall the ADB drivers and try KFU again.
As a side note, ADB would not work on my PC which is running XP
I was able to use KFU on my wife's PC which is running windows 7 and I know have root access.
I am currently running JandyCane on my kindle
All I am left with is "Waiting for device" in kindle fire utility..
try this
Greymooses said:
All I am left with is "Waiting for device" in kindle fire utility..
Click to expand...
Click to collapse
OK, what happened when you plugged it back into your PC did it recognize it?
Can you uninstall the drivers for it and then reinstall the drivers for it?
What OS are you running?
I don't use Windows so I couldn't say for sure whether this works or not, but it's worth a try.
http://forum.xda-developers.com/showthread.php?p=30681311
I have a Kindle Fire 2. I received it in this state and do not know exactly what was done previously.
On power up, it goes to the Kindle Fire logo, then to a blank screen. All I can do here is hold down power to power it off.
I have a factory original cable. Connecting to a PC, it goes to a fastboot screen with a green/red traffic light with the green light flashing. If I use a PC that previously had a Kindle Fire connected, the device is recognized. However, I get "device not found" or similar when attempting to use any options on the Kindle Fire Unbrick Utility 1.1, or Kindle Fire Utility.
On a PC that did not have a Kindle Fire previously connected, device manager sees it as an unknown device (or rather a particular non-Kindle device--don't have it here it with me and will update with that info if it is relevant). I have loaded drivers using ADB but the PC does not recognize it as a Kindle. As I expected, neither utility recognizes the connected Kindle here either.
Any advice on where to go from here? The hurdle seems to be just getting the PC talking to the Kindle and I'm not sure how to proceed.
I got the same problem, any helps
Sorry, I never got it working. It's collecting dust at the moment.
Kobusama said:
I have a Kindle Fire 2. I received it in this state and do not know exactly what was done previously.
On power up, it goes to the Kindle Fire logo, then to a blank screen. All I can do here is hold down power to power it off.
I have a factory original cable. Connecting to a PC, it goes to a fastboot screen with a green/red traffic light with the green light flashing. If I use a PC that previously had a Kindle Fire connected, the device is recognized. However, I get "device not found" or similar when attempting to use any options on the Kindle Fire Unbrick Utility 1.1, or Kindle Fire Utility.
On a PC that did not have a Kindle Fire previously connected, device manager sees it as an unknown device (or rather a particular non-Kindle device--don't have it here it with me and will update with that info if it is relevant). I have loaded drivers using ADB but the PC does not recognize it as a Kindle. As I expected, neither utility recognizes the connected Kindle here either.
Any advice on where to go from here? The hurdle seems to be just getting the PC talking to the Kindle and I'm not sure how to proceed.
Click to expand...
Click to collapse
Kindle Fire Unbrick Utility 1.1, and Kindle Fire Utility are for the Kindle Fire 1 only
This is my second time rooting my Gen1 Kindle Fire. (The first time was very successful but stupid me, I went back to factory settings for no good reason).
From KF's updated software (6.3.2) I used Kindle Fire Utility 0.9.9, to install TWRP 2.6 and other google apps. I loaded TWRP and cleared cache etc. I then installed the new CM 10.1 SGT 7 rom. When i rebooted the KF, i didnt get the option to boot into twrp. What happens now is, it shows the orange Kindle Fire boot screen, and then continues to the CM10.1 boot screen. I may have installed CM10 over the KF software somehow. Now, my PC recognizes it as a Kindle Fire when I plug in the USB but there's an error in the device manager. Basically, KFU doesn't recognize it's a Kindle anymore. When I try to reboot it in recovery mode, it just does a regular reboot. Nothing about my KF looks like there's twrp installed in the background. I can't access it no matter what.
I tried sideloading Google Play and installing the TWRP Manager app but that doesn't do anything at all. I feel like my KF is going to be stuck like this forever. Any way to hard reset everything without TWRP? I have the proper "update.zip" file on the sdcard but I can't access any way to Wipe it and Install it.
Just so you know, the kindle isn't bricked it just seems like it's permanently stuck the way it is and my PC won't recognize its harddrive via USB.
Any suggestions?
Still no replies huh? Damn.
So when I turn on my kindle fire, the orange Kindle Fire logo shows up for a few seconds THEN the CyanogenMod boot screen comes up. I never get the option to boot into TWRP.
When I plug my KF into my PC, the Kindle Fire drivers get an error so i change it into an Android ADB Composite device. It still won't recognized the device properly. When I open up the console and try "adb devices" nothing shows as connected. I've installed the SDK and changed the files but it's the same thing. All that to say, the KFU no longer recognizes when the KF is plugged in.
MikeyNooch said:
Still no replies huh? Damn.
So when I turn on my kindle fire, the orange Kindle Fire logo shows up for a few seconds THEN the CyanogenMod boot screen comes up. I never get the option to boot into TWRP.
When I plug my KF into my PC, the Kindle Fire drivers get an error so i change it into an Android ADB Composite device. It still won't recognized the device properly. When I open up the console and try "adb devices" nothing shows as connected. I've installed the SDK and changed the files but it's the same thing. All that to say, the KFU no longer recognizes when the KF is plugged in.
Click to expand...
Click to collapse
try again with ver 9.6
[HELP] Unbricking Kindle Fire HD7" with Fastboot Cable; pc won't recognize Kindle
Lemme start from the beginning. (I've made numerous threads before I had a fastboot and commentors kept asking questions that I've answered in the post so I'm gonna try to be detailed as possible)
Before I had a fastboot cable
I flashed a ROM onto my Kindle Fire (Cyanogen 13). Didn't like it so I thought a recover to factory settings would work. It didn't and it got stuck on the TWRP screen. Stuck on TWRP meaning that it's literally stuck on the blue TWRP screen. It doesn't get to the main menu or anything. I scoured the internet for solutions and some (which didn't mention a special cable) I tried but it ultimately failed because the program (can't list every single one but one I do remember is Kindle Fire Unbrick Utility), could NOT find my Kindle Fire. Also, Kindle Fire could not be found under "this PC" but when I plugged it in, it made the ding sound and could be found under ""Device Managers". I started reading steps about using a fastboot cable and was led to believe if you use one, your PC should recognize Kindle, therefor programs to unbrick should find the Kindle.
Got my fastboot cable today
I ordered one from Amazon and when I plug my Kindle in with cable, it turns on saying "fastboot kindle fire". I was excited to get this fixed finally. I followed a YouTube video's instruction (of a channel that I can count on) Tekify's Unbrick Kindle Fire. I did all the installing ADB drivers and what not but once I plugged the Kindle in and then opened the Unbrick program (this one Unbrick Utility). I pressed "1" on my keyboard to wipe everything on device. But once I pressed enter it sat on <waiting for device>. I checked under Device Managers and under Other Devices, Tate was there. But I couldn't find the Kindle under "This PC" still.
I've already researched this specific issue and people said to go to Tate's properties and update driver software. Then browse your PC for the Kindle under "This PC" but can't because Kindle doesn't show up under there. I know this is a Bible's worth of words but I really want to get this tablet FIXED!
CrustyLube said:
Lemme start from the beginning. (I've made numerous threads before I had a fastboot and commentors kept asking questions that I've answered in the post so I'm gonna try to be detailed as possible)
Before I had a fastboot cable
I flashed a ROM onto my Kindle Fire (Cyanogen 13). Didn't like it so I thought a recover to factory settings would work. It didn't and it got stuck on the TWRP screen. Stuck on TWRP meaning that it's literally stuck on the blue TWRP screen. It doesn't get to the main menu or anything. I scoured the internet for solutions and some (which didn't mention a special cable) I tried but it ultimately failed because the program (can't list every single one but one I do remember is Kindle Fire Unbrick Utility), could NOT find my Kindle Fire. Also, Kindle Fire could not be found under "this PC" but when I plugged it in, it made the ding sound and could be found under ""Device Managers". I started reading steps about using a fastboot cable and was led to believe if you use one, your PC should recognize Kindle, therefor programs to unbrick should find the Kindle.
Got my fastboot cable today
I ordered one from Amazon and when I plug my Kindle in with cable, it turns on saying "fastboot kindle fire". I was excited to get this fixed finally. I followed a YouTube video's instruction (of a channel that I can count on) Tekify's Unbrick Kindle Fire. I did all the installing ADB drivers and what not but once I plugged the Kindle in and then opened the Unbrick program (this one Unbrick Utility). I pressed "1" on my keyboard to wipe everything on device. But once I pressed enter it sat on <waiting for device>. I checked under Device Managers and under Other Devices, Tate was there. But I couldn't find the Kindle under "This PC" still.
I've already researched this specific issue and people said to go to Tate's properties and update driver software. Then browse your PC for the Kindle under "This PC" but can't because Kindle doesn't show up under there. I know this is a Bible's worth of words but I really want to get this tablet FIXED!
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1096 using XDA Labs