Help! Bricked my Kindle Fire - Kindle Fire Q&A, Help & Troubleshooting

I attempted to root my Kindle Fire (which was running 6.2.2) using the Kindle Fire Utility v0.9.5. KFU appeared to run successfully and my Kindle was fine (started up OK). But, when I ran Root Check Pro, it showed KFU didn't succeed with rooting. I thought maybe KFU was unsuccessful because KFU v0.9.5 works on Fire firmware 6.3 and up (and not on 6.2.2).
Then, I tried to update the Fire firmware to 6.3.1 from the Amazon site, thinking I'd run KFU v0.9.5 again after the firmware update. I didn't think to uninstall any of the KFU installed rooting software (like superuser or TWRP) before trying the update because the root was unsuccessful.
My Fire started the update but stopped almost immediately and got stuck at the TWRP yellow-triangle logo. Also, my laptop (running Window 7) won't recognize the Fire when I plug it in with a USB cable.
When I set my laptop Device Manager to show hidden devices, "Android Phone" appears as a device. When I expand it, I see "Android ABD Interface". The Android Phone device displays for a few seconds and then disappears. If I shutdown my Kindle Fire and power it on again, the device manager does the same thing.
[FYI - I successfully rooted another Fire (though it was running 6.3) using KFU v9.0.5 on this same laptop so the Kindle Fire drivers for Windows were installed.]
Because of this behavior, none of the unbricking, KFU, or ABD utilities/commands are getting through to the my Fire. The Kindle Fire Unbricking utility, for example, will start but almost immediatley close the Windows Command window.
I don't know what to do when your laptop won't recoginize the Fire as a connected device. Is there any thing else I can try? I'd appreciate any help with this I can get!!

Go here
...and download FFF1.4
Mount your sdcard in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"

If you get things working and decide you want to root again I would highly suggest side loading the superuser.apk. Root Check Pro might have discovered no root because the su.apk was missing (just a thought). This is an issue with KFU. I've rooted 4 kindles and not once has it installed the su.apk.

I also had to side load superuser and Google Play. Here is a great link on this forum to help with that:
http://forum.xda-developers.com/showpost.php?p=24312196&postcount=17

Soupmagnet - thanks so much for the reply!
One question >> how do I 'mount the SD card in recovery'?
Long press on the Fire power button does nothing - doesn't launch TWRP in recovery mode. Entering commands in a Command window from my laptop isn't getting through to my Fire. And, as I mention above, the Kindle Fire device won't stay available in my laptop Device Manager for more than a split second.

morgan4k said:
Soupmagnet - thanks so much for the reply!
One question >> how do I 'mount the SD card in recovery'?
Long press on the Fire power button does nothing - doesn't launch TWRP in recovery mode. Entering commands in a Command window from my laptop isn't getting through to my Fire. And, as I mention above, the Kindle Fire device won't stay available in my laptop Device Manager for more than a split second.
Click to expand...
Click to collapse
This is a tricky situation because you need to replace your device drivers, but you can't replace your drivers if you don't have access to them. I haven't come across a situation like this before last night so I wouldn't know how to fix your device manager issues.
You could however, try a different computer (easiest), OR create a bootable Linux LiveUSB thumb drive to boot from your laptop and set up the environment for issuing adb/fastboot commands. IMO, that would probably be the best route considering Linux's overall stability but it would definitely be the trickiest.
There are tutorials here for setting up Linux to use adb and fastboot and I'll add them as soon as I find them.
Setting Linux up for adb and fastboot can be tricky but there are plenty of Linux users here that can help with that.
Once you get everything set up, (re)install TWRP and continue wth the previously posted tutorial.
[Edit:] Actually, I have a better idea if you're using the LiveUSB and you wouldn't need to set up adb and fastboot.

Thanks for a great summary! Unfortunately even after sideloading superuser.apk, I still have read-only rights on / and the system directories under it that (would) allow me to copy over vending.apk. Yes, I am superuser when I try.
I have no problems becoming superuser, and OTA Rootkeeper works to switch back and forth.
The three things that do not work are write access to /system/app in order to switch out vendor.apk, mounting a drive as read/write, and from my PC am unable to use the adb remount command. All see outcomes of the same permissions issues.
Anyone seen this, and found the cause?
Thanks.

Are you positive your rooted download root checker verify root if you get red writing your not rooted

Related

Device not recognized on ADB?

I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913
The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.
in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...
I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>
Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk
I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb
Its seems i should give up
Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Push push push it
tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks
Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.
Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device
Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?
Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.
The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.

[Q] Kindle stuck at static Kindle Fire logo

Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Sounds like it's stuck in fastboot bootmode to this noob. I had the same problem at one point and used command line to fix with the simple bootmode switching commands - can't recall if I used fastboot or adb tools..but either should work. And if I'm reading your post right, you've tried these so this is likely above my meager skill level, heh. You are handling it better than I did, I might add.
If I may point out where you went wrong:
Mattamus Prime said:
After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
Click to expand...
Click to collapse
There are apps in the Google Play store that will temporarily remove your root status so you are able to use services that detect and shut down when root is detected. OTArootkeeper.apk is one that I've heard of.
And don't ever chose to lose fff once you have that as this is your lifeline to unbricking.
Hopefully someone with better chops than I on this will post up - continue with your patient reading and take a little comfort that this is most probably fixable.
First off, I applaud you for trying to figure out and fix the problem yourself using the guides available. Thank you. The information you provided will go a long way to getting the help you need.
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Once you have done that and you still can't change your bootmode, try using recovery to flash a custom rom. It's possible the stock boot image you have has been corrupted. You can use the "mount" function in recovery to push another rom to your sdcard. If that works you can stick with a custom rom like MoDaCo. It's the same stock stock interface with Google apps and services installed and you don't have to worry about OTA updates. OTA Rootkeeper will let you easily switch between "rooted" and "unrooted" so you can take advantage of Amazon's VOD.
And if you still want pure stock you can d/l a new copy of the update and try again.
Thanks for the suggestion. I did try OTA Rootkeeper, but when I went into my Instant VOD, it still had the buttons grayed out. I tried temp unroot, reboot Kindle, and still grayed out, so I assumed Rootkeeper wasn't working for me, thus, the looking for the unroot tutorials.
A little bit of extra information, when I hook up my Kindle Fire, my drivers says Android Composite ADB Interface. When I try to switch to Fastboot to have it switch to Android ADB Interface, it doesn't switch. It just stays as Composite.
Thanks again.
soupmagnet said:
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Click to expand...
Click to collapse
I followed the advice in the Beginners Guide, uninstalled whatever drivers I had, rebooted my comp, then installed the ones that came with the KFU download.
Are there any other drivers I should be looking for?
Also, a little bit of more information, I tried switching to Fastboot through KFU, received some messages to the effect of "system/some file name file not found (2)", (I apologize for not being specific, typing from memory), it then reboots my Kindle Fire, then I execute the commands:
fastboot getvar product
After that, it just says <waiting for device>
In fact, after any command I do in cmd, I get that message. So I believe it may be a driver issue, like was suggested, or my Kindle isn't far enough into the boot process to be found.
It definitely sounds like a driver issue. Keep working on your drivers.
If that doesn't work, you can try it on a different computer OR set up a Linux LiveUSB for issuing adb/fastboot commands.
FIX for Kindle stuck on logo
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
MattamusPrime said:
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Click to expand...
Click to collapse
K_Krish said:
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
Click to expand...
Click to collapse
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
me too
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
I am stuck at the very same place you are. I was in an endless bootloop after trying to flas back to the Stock Amazon ROM using TWRP. Once i got the drivers sorted out and ADB could see my device i used KFU to "Install permanent Root with Superuser". The KF went to reboot into fastboot and the screen said "waiting for device" for about ten minutes. Now the KF is stuck at the white and orange "kindle Fire" boot logo. Windows will no longer see the KF as an android device. It only shows up as an "unknown device" in the device manager.
Try this
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Ok, I dont know, how to fix this (as I was not in this situation). Try following the steps - Download update.zip through KFU. Connect your Kindle to PC and install the android driver. If your PC detects the kindle copy update.zip file to kindle and try to install that.
sounds like a job for this http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Im in the same boat you are. I have tried everything stuck on same logo device is recognized in devices as android phone and adb interface but cannot connect to unbrick utility or KFU and doesnt show as a drive either. tried to search devices in cmd using fastboot commands and nothing shows either. I decided to purchase a factory cable today on ebay. Keeping my fingers crossed because after reading everything I could find I think it is my only option.
No, your problem is as "simple" as fixing your drivers so the computer can communicate with the device through adb and fastboot. KFU relies on those two tools to do pretty much anything. Unfortunately, Windows is stupid and is not very effective when dealing with certain USB devices.
In order to, say, install TWRP, you need adb to change the bootmode to accept fastboot commands, and use fastboot commands to overwrite the recovery partition. In the process of going between different boot modes, Windows had a hissy fit and decides not to communicate with the device at all. Hence the need to fix/reinstall the drivers. It doesn't always work out that way and you get stuck where you are right now. A factory cable will put you in fastboot, but it wont make Windows communicate with the device. You can continue to fight with Windows drivers and hope to get lucky, or you could try other, more effective options...
http://forum.xda-developers.com/showpost.php?p=30629067
omg .... I survived a bricking. Soupkit saved me!!!
Somewhere on the many tabs I have open, as I frantically search for ways to unbrick my Kindle fire... I run into " SoupKit" for Linux ... install it... mess around with the Bootloader .. change it to 4002 I believe the value was ... my Kindle that I've been working on for literally 6 hrs is back on! ... now on the figuring out how to root it / remove demo software. SOUPKIT!
E]

[Q] Problems with FFF & KFU. Device not recognized

Hello-
Quick background. I have a Kindle Fire with the CM9-Reloaded ROM installed. All was going well for a few weeks until my Kindle stopped connecting to the internet. I figured it was just a bug and wanted to reinstall the ROM or choose a different one.
I have FFF v1.4 (with the blue logo) installed. When I get to the screen that allows me to choose "Normal Boot", "Recovery", or "Reset Boot Mode" I choose the "Recovery" to go into TWRP; however, this doesn't happen. It puts me back into a loop to the same screen to choose again. I can do this over and over again and I'm still not able to get into recovery to get to TWRP.
I decided to see if I could use the Kindle Fire Utility to get to TWPR that way. Before everyone asks, my drivers are all updated and functioning properly. I uninstalled and reinstalled just to double check. When the Kindle is plugged in, I can go to the device manager and see my Kindle there. The problem is that KFU says I'm offline and I can get to any of the menus. When I plug in my Kindle I do get the little "bong" that tells me my computer recognized it.
Also, went to my laptop and downloaded the KFU and installed everything. Same result as with my desktop.
What else can I try? I have a factory cable, but I really don't know much about how to use it. I simply followed step by step instructions to root this when I originally got it. Any suggestions? I'd really just like to put this Kindle back to stock, re-root, and try it all over again to eliminate any potential issues in the future. Thanks in advance for your help.
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
same boat
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Dasanko said:
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
Click to expand...
Click to collapse
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
jeffjoleen said:
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
Click to expand...
Click to collapse
By it not working, do you mean that it reboots normally?
"fastboot getvar product" to get the KF to stick with fastboot mode when it's loading the bootloader.
"fastboot flash recovery twrp.img" very important to double check the file hash to make sure it's not corrupt.
"fastboot reboot" only in case it doesn't automatically reboot on its own.
EDIT: Keep in mind fastboot mode uses a different set of drivers, so you may have to install those as well (included in KFU, along the ADB ones).
---------- Post added at 06:57 PM ---------- Previous post was at 06:49 PM ----------
Justugh said:
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Click to expand...
Click to collapse
Please don't hijack other people's threads, start your own here on Q&A. Otherwise, handling with two completely different issues in the same place gets awfully confusing. Also, read this: http://forum.xda-developers.com/showthread.php?t=1552547

[Q] Broke Kindle Fire's Ability to Mount

Hey I'm a brand new member so I apologize in advance if my problem has been solved already, however, I could not find anything on any of the threads. Okay so I am severely confused right now. I have had my Kindle Fire for almost a year now and this problem has never occurred. Ever since I got my Kindle I have been experimenting on it. I rooted it and have flashed many different custom roms. I had been using TWRP Recovery 2.0 for a long time and when I found out that it was outdated I updated it to the new 2.2.1.1 version...Everything seemed to be working perfectly until I tried mounting USB storage in the new TWRP...It did not work. My computer wouldn't recognize it. I kind of just let this slide since I figured I wouldn't need to mount USB storage in TWRP unless it was an emergency. A while later I switched back to the Kindle's stock rom. That's when I noticed that it would not mount...Not only was TWRP not mounting, but it was my Kindle altogether. I deleted all drivers that had any thing to do with Android from my computer. After restarting both my computer and my Kindle I tried mounting again...Nothing. The drivers weren't even reinstalling. To test wether this was a problem with my computer or my Kindle I got my brother's Kindle Fire (Never had any tweaking done to it) and mounted USB storage. It installed the drivers and mounted just fine. I then plugged my Kindle back in and it mounted just fine also. I thought I had solved the issue, but about an hour later I tried mounting my Kindle again and nothing happened. My brother's Kindle will mount (Actually there are a total of four Kindles in my house all of which have not been tweaked except for mine) but mine won't do anything. As a last resort I deleted EVERYTHING with TWRP and flashed the Kindle Fire 6.3.1 update.zip. My Kindle is now true factory default (no root, custom recovery, etc...). I thougt for sure this would work but IT STILL WON'T MOUNT USB STORAGE!!! When I plug my Kindle in and go to "Devices and Printers" it recognizes my device as a "Kindle" but I just cannot get it to mount! I am now stuck with a Kindle that cannot be re-rooted or anything due to the fact that it cannot be recognized with ADB. Sorry for the long post...I am just trying to give as much information as possible. By the way I am running Windows 7 and my Kindle is the only one that will not mount which makes this problem have nothing to do with drivers or my computer. Any help is appreciated. Thanks.
Wheww okay well try a factory reset this will wipe your sdcard as well. It should resolve most your problems. There are multiple things that can cause this to happen but one thing that really comes to mind. Are you ejecting your kindle before hitting the disconnect button? Just a wild guess but failing to do so can cause this disorder the very next time you plug it in. Something that could resolve minor sdcard issues is
Code:
fastboot oem format
don't let this make you to crazy yet RC soupmagnet should be releasing something very soon that will solve the majority of SD card mount problems hint hint . You will need to reroot and flash a custom ROM on it to have success though. So if nothing works hang tight and stay tuned.
This might help
http://forum.xda-developers.com/showthread.php?p=33109015#post33109015
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Nihilian said:
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Click to expand...
Click to collapse
Have you installed your adb drivers?
soupmagnet said:
Have you installed your adb drivers?
Click to expand...
Click to collapse
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Nihilian said:
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Click to expand...
Click to collapse
I don't use Windows so I couldn't tell what's normal for that OS.
Use the tutorial here to confirm your drivers are installed properly. Then Shift + right-click on your KFU "tools" folder with adb.exe and fastboot.exe, and select "Open command window here". Enter your adb or fastboot commands there and see how it goes. Start with "adb devices" to see if you are connected. If not, reinstall your drivers and try again.
Some ROMs have different product IDs than the stock OS so you may want to look into that if you are using a custom ROM, and edit your androidwinusb.inf accordingly. I know some JB roms have a PID of 0004 instead of 0006.
If for some reason Windows refuses to cooperate, you could always set up a Linux LiveUSB and get it done a lot easier.
Okay so I've been fiddling around with stuff. I completely uninstalled all Android drivers again then restarted my PC and Kindle. This time I plugged my Kindle in and it installed the correct drivers. It mounted USB just fine. When I tried reinstalling the ADB drivers that came with Kindle Fire Utility it erased the Kindle's normal drivers, so now it won't mount anymore...at least I know that it is a driver problem and that my Kindle doesn't need to be repartitioned. I'm really getting sick of Windows and its annoying drivers...Any ideas on how to get all the drivers to work? If not I think I might just install Ubuntu and screw the need for drivers.
Sent from my M886 using xda app-developers app
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Thepooch said:
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Click to expand...
Click to collapse
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Nihilian said:
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Click to expand...
Click to collapse
I downloaded the lates kindle fire utility and I enabled debugging, I can see my files but when I run the utility file the adb says offline. I cannot figure it out. : (

"adb devices" cant finy my Kindle Fire 2...

I have here Kindle Fire rev. 2.
I want to root it.
I downloaded Kindle Fire ADB drivers.exe , and installet it.
Run cmd.exe goto adb Folder type "adb devices" and adb server cant finy my kindle...
My Smartphone is Visable in ADB.
i have here 3 Win 7 PC´s and Win8 Notebook (all x64 OS) . I Try´d it on other PC, dnot work. I installed extra win 7 32 bit, but still dnot work.
ADB ist 100% enable in Kindle Settings Menu.
Can anyone Help me ?
avathor said:
I have here Kindle Fire rev. 2.
I want to root it.
I downloaded Kindle Fire ADB drivers.exe , and installet it.
Run cmd.exe goto adb Folder type "adb devices" and adb server cant finy my kindle...
My Smartphone is Visable in ADB.
i have here 3 Win 7 PC´s and Win8 Notebook (all x64 OS) . I Try´d it on other PC, dnot work. I installed extra win 7 32 bit, but still dnot work.
ADB ist 100% enable in Kindle Settings Menu.
Can anyone Help me ?
Click to expand...
Click to collapse
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
bryanchapman9999 said:
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
Click to expand...
Click to collapse
I downloaded the SDK and it didn't have a 'adt bundle' in the contents but i ran sdk manager and I had already added the link you mentioned and I also had already added the extras you mentioned earlier from a article I read and Nothing so I stumbled across this article and it had a few extra steps so I thought to give it a try only problem is, When I go to my device manager to uninstall the kindle drivers i don't have that option to uninstall a 'kindle' driver rite below it there's a android adb interface and i have the option there to uninstall but before I did so I wanted to post here what's going on with me. I wonder if it worked for the person who started the post?
bryanchapman9999 said:
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
Click to expand...
Click to collapse
Worked perfectly and allowed me to root using the other guide in the forum.
Posted using my Kindle Fire 2.
Are you using the adb from the latest sdk?
I couldn't get adb to recognise my kf2 until I used the latest adb.exe
I rooted my both kindle´s before a week.
no idea why the other driver did not work.
The Driver from http://kindle-sdk.s3.amazonaws.com/addon.xml work perfectly.
I had this same issue until I updated the driver with the latest. I don't have it in front of me, but when I looked at it, it's dated approx Dec 8th 2012 in Device Manager. Update the driver to the latest and you should be good to go.
know that if you install the drivers after connect your kindle it can mess it up, if you go into device manager and uninstall the drivers after you've disconnected you're kindle and install them then reconnect it, it should work.
I think I know what's wrong...Your using windowzzzzzzzzzzzzzzzzzzzzzzzz...
powerpoint45 said:
I think I know what's wrong...Your using windowzzzzzzzzzzzzzzzzzzzzzzzz...
Click to expand...
Click to collapse
Powerpoint is so right here, If you use any linux distribution, it's going to be much easier to get your kindle connected to adb.
Do we even have a q&a or general section for this device? Bought, rooted and turned into a tablet today
Sent from my KFOT using Tapatalk 2
new adb files
cupidstunt said:
Are you using the adb from the latest sdk?
I couldn't get adb to recognise my kf2 until I used the latest adb.exe
Click to expand...
Click to collapse
That must have been my problem. I ended up moving to my Xubuntu machine to get it to work. I think my adb was from November,
Joe
rooting kindle fire 2 (10.3.1)
bryanchapman9999 said:
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
Click to expand...
Click to collapse
Thanks for the steps to install adb drivers worked prefectly
can you also kind me how to install custom recovery on kindle fire 2 (10.3.1) and cm10.1
@indus76:
You may want to look at these threads:
http://forum.xda-developers.com/showthread.php?t=2100963
for flashing the second bootloader and TWRP recovery
and
http://forum.xda-developers.com/showthread.php?t=2209995
for flashing CyanogenMod
Good luck!
This probly isnt the right place for this but I have been to so many areas and so many websites that I am crosseyed now. I managed to root my kindle the other day and was attempting to install a mod on it. At this point I cant even remember which site I was on to share the steps I took. Needless to say, I messed up and now the kindle boots to to the logo for a few seconds, shuts off and boots back to the logo, over and over. I'm not very good at all this but not completely stupid either. I'm simply ready to pull my hair out. I have installed Android SDK and am having trouble getting the correct drivers for my kindle apparently. Its a kindle fire hd 2012. I went through all the trouble of installing the sdk and got to the part with the addons and manually putting in the amazon site, only to read on and discover its no longer supported so I can not get the different kindle fire definitions. In my device manager, it shows kindle fire and expanded shows Android ADB Interface (no composite.. does it matter?). I have verified that abd is installed and working, but doing a devices command, doesnt show any devices. It executes without errors, just doesnt list anything. I have a fastboot cable and it does currently say Fastboot on the kindle when I plug it in.. thats all it says tho, is it supposed to go any further then those words?
I have tried so many suggestions on here to get it to see my kindle to no avail. I follow tutorials, that seem to link to other tutorials because the previous ones had prerequisites and THOSE have links for downloads that no longer work and so I do a side load of a webpage trying to find the missing download I need and THOSE pages end up leading me somewhere else or going a different route then the previous tutorial took me and I just CAN'T get anywhere with this! It shouldnt be this hard (and I'm venting at this point so I apologize). Does anyone have an UPDATED (2018) tutorial for getting my kindle back to where it will boot up... assuming my computer will ever see it (windows 7 btw). Thanks in advance.

Categories

Resources