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.
I really would like to now if it is possible, in any way, to run Kindle Fire Utility on Windows XP. I've tried several times but it still says: ADB status; Offline. And yes I installed the drivers but I don't think they worked correctly. Any help would be greatly appreciated!
Yes, I did KFU with Windows XP on a comptuer that's about 8years old. The drivers should still work, but I found you can't do the auto-install fo the drivers,
Download and Install KFU, extract and move to the directory in the directions (I think it's c:\KFU)
Plug in your kindle and point it to the drivers in the KFU folder.
(NOTE: I can't remember the name off the top fo my head as I'm not at my PC, but it did require me to download a file when I pointed it to the drivers when it was in fastboot. to get it to work once in Fastboot, they were easily found and downloaded)
Note2: I had to use the command line to get it out of fastboot as It was stuck in a boot-loop for a few min while I found the thread.
Yep, I used XP.
You have to manually install the drivers.
Search Youtube for nat3mil - he has a vid showing how to manually install the drivers.
Badgerino said:
Yep, I used XP.
You have to manually install the drivers.
Search Youtube for nat3mil - he has a vid showing how to manually install the drivers.
Click to expand...
Click to collapse
I know how to install the drivers. The problem is KFU saying my KF is offline.
TheZeldaLova said:
I know how to install the drivers. The problem is KFU saying my KF is offline.
Click to expand...
Click to collapse
Because you didn't install the drivers correctly.
Sent from my Galaxy Nexus using Tapatalk 2
be sure you don't have any other android device drivers installed.
josepho1997 said:
The drivers that came with KFU didn't work for me when I manually installed the drivers, on XP, so I used different drivers for it. Just find different drivers and follow their instructions.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
OK, I'll try that. Thank you very much.
yes, but not easily...
I successfully accomplished it yesterday. After reading how easy it was I figured I would give it a try.
Three hours later I had it successfully completed.
My problem was, you guessed it, DRIVERS! My Laptop is running XP Pro SP3 and I have had multiple android devices attached to it. I removed and installed drivers several time never with any luck.
So I borrowed my daughters netbook and started with that. I installed the drivers and opened KFU. It recognized my kindle right off so I chose menu option 2 It blew through it until it got to installing FFF (best I could tell ) and froze rebooting at the KINDLEFire logo. I left it alone for about 45 minutes hoping it would continue on it own...but no luck.
After waiting I shut down KFU and unplugged my kindle. I held the power button for about 30 seconds to shut it down and waited 5 minutes before restarting it. No luck, it booted to the logo and hung. I repeated this process about a dozen time with no luck.
Getting concerned at this point but not panicking yet, I plugged it into the netbook again, started KFU and rebooted the kindle. The whole time it booted I kept pressing the power button repeatedly while telling KFU to recheck the connection. After about 5 minute of this it recognized it, I reran option 2 and it completed.
So, yes it worked.
Cen5
Uninstalling drivers
akalostangel said:
be sure you don't have any other android device drivers installed.
Click to expand...
Click to collapse
Do you know how I can find all of the android drivers on my computer to uninstall?
ok so my buddy just bought a kindle fire and asked me to go to town on it and make it "look good". i'm new to the whole kindle fire method of doing things. my wife has a nook tablet running cm7, and i have my SGSII skyrocket running cm9. i'm familiar with most things in the rooting process, but not too familiar with twrp ( but understand what it is).
the problem i am having is getting KFU to recognize the KF. i have read the KFFB and all associated threads, i have used the forum search, google, and even youtube but no luck. i have tried 3 different computers and only one of them actually showed the proper device info in device manager. the first laptop is running 64 bit windows 7, ran the install_drivers.bat and everything said it was good but no matter how many times i uninstalled and reinstalled the drivers the KF will not show up. the results did not change whether it was manually installed or not (possibly due to my samsung drivers causing a problem), laptop 2 is running the same configuration, and still the same problems. the 3rd laptop is running 32bit xp and with a manual install the drivers installed and the abd composite driver showed up on device manager under android phone.
so when i plug the KF in the computer recognizes it but when i try to run KFU nothing happens. i tried to run the install_drivers.bat but it comes back as installed fail - unsigned drivers.
so after hours of searching and reading i'm at a loss. is there anything else that i can do?
ok well i got KFU to work on laptop #1. i uninstalled my samsung drivers and all other android drivers i could find, ran the install driver.bat and it worked. seems my drivers from my phone were causing the device manager to not install the KF drivers properly. now to flash away!!!!
Hi everyone, I've been trying to root my Kindle Fire 6.3.1 for a few days now and I don't seem to find a solution for it.
Yesterday I tried rooting on my boyfriend's computer, which has Windows 7. I don't think the drivers were installed properly because it said Android Phone > Android ADB Interface in the Device Manager. I clicked the "run.bat" file in the KFU folder but it said ADB Status: Offline and Boot Status: Unknown.
Now I'm trying to root it on my computer, a Windows XP SP3 machine. When I double click on the install_drivers.bat file I get a language error, which is why I tried installing the drivers manually. Now when I go to Device Manager it says Android Phone > Android Composite ADB Interface. However, I still get the ADB Status as offline and the Boot Status is also unknown.
I have tried re-installing the drivers manually about 3 times now, I've rebooted my computer and Kindle every time.
I would really appreciate it if someone could help me with this. I won't have access to my boyfriend's Win7 computer for a few days, so help with WinXP is what I'm looking for right now. Any ideas or suggestions are welcomed.
The answer to your question can be found here:
http://forum.xda-developers.com/showpost.php?p=23747567
Hint: second post
KindleTrish said:
Hi everyone, I've been trying to root my Kindle Fire 6.3.1 for a few days now and I don't seem to find a solution for it.
Yesterday I tried rooting on my boyfriend's computer, which has Windows 7. I don't think the drivers were installed properly because it said Android Phone > Android ADB Interface in the Device Manager. I clicked the "run.bat" file in the KFU folder but it said ADB Status: Offline and Boot Status: Unknown.
Now I'm trying to root it on my computer, a Windows XP SP3 machine. When I double click on the install_drivers.bat file I get a language error, which is why I tried installing the drivers manually. Now when I go to Device Manager it says Android Phone > Android Composite ADB Interface. However, I still get the ADB Status as offline and the Boot Status is also unknown.
I have tried re-installing the drivers manually about 3 times now, I've rebooted my computer and Kindle every time.
I would really appreciate it if someone could help me with this. I won't have access to my boyfriend's Win7 computer for a few days, so help with WinXP is what I'm looking for right now. Any ideas or suggestions are welcomed.
Click to expand...
Click to collapse
Also your way better off on the windows 7 machine drivers simply install better
So, I've found an array of guides both on and off the forums and I've followed a host of them. I am trying to obtain root and Superuser via Kindle Fire Utility. I've installed the drivers a number of ways including through the Android SDK, KFU and by unplugging and plugging it back in. Apparently the drivers are installed correctly because when I check in the device manager, the Kindle is listed as Android Phone and then under the dropdown as Android ADB Interface. However, no matter what I do, when I run the run.bat file in KFU the device is listed as offline and whenever I try to do the adb list the Kindle isn't showing up there either. I believe it is because I get a syntax error whenever I launch KFU before the actual KFU screen up saying that the location C:\User\.android doesn't exist. So, I'll list all the steps that I can remember I've done over the past 16 hours or so.
1) Downloaded the Android SDK and Java JDK (I think it's called...either way, I have updated JRE and DK)
2) Unplugged the Kindle Fire which is firmware 6.3.1 which was listed as Kindle in device manager and ran the install_drivers.bat file.
3) Confirmed via device manager that the fire is actually listed as Android ADB Interface
4) Did an adb kill
5) Deleted drivers once confirmed KFU couldn't find the device online
6) Reinstalled drivers via the KFU drivers folder
7) Repeated steps 3-5 then reinstalled the drivers via the Android SDK provided USB driver file
8) Repeated steps 3-5
And now I'm at a loss, I have no idea what else to do. I've rooted multiple phones as well as gotten homebrew running on Wii's and PSP's but this one is stumping me. Any advice or assistance would be greatly appreciated. Also, please don't kneejerk response and send me back to the thread explaining how to get the drivers running via KFU because I've done every step of that to no avail and I honestly believe the problem lies somewhere in the syntax error I get referring to the lack of a C:\User\.android folder.
Thanks in advance for your help
That's because your drivers are incorrect it should be android adb composite interface... sounds like your using xp and its the complete worst for driver installs...
my suggestion is this build your own little system with this http://forum.xda-developers.com/showthread.php?t=1850038 then do the task manually all you need to do is have twrp and fff the rest is entirely obsolete if you intend to just flash a rom anyway.. for the purposes of learning what to do and how to do it read these http://forum.xda-developers.com/showthread.php?t=1552547 http://forum.xda-developers.com/showthread.php?t=1638452 they will give you some needed insight.. jcase`s manual rooting tutorial can be found here but like i said flash a rom all roms are rooted http://forum.xda-developers.com/showthread.php?t=1568340
Thank you for the response, I am not using XP, I am using Windows 7 Home Premium.
I don't have Linux although I suppose I could use a USB drive or USB Hard drive to dual boot with Linux. Thanks again, I'll have to wait until my brother brings the Kindle back over to try this, until then I'll look over it all.
ok well usually running the install.bat for the drivers on windows 7 is enough but for some it isnt regardless drivers are you main issue and you certainly dont want to have any issues with them in the process it will only produce very bad results..
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
also your syntax error can be causing the issues as you say you need that .android folder to make it work...
post #2 has a ton of info on the driver thing http://forum.xda-developers.com/showthread.php?t=1552547