Hello
I am really struggling with trying to get the KF drivers installed on ANY Windows 7 x64 computer.
I have access to a Windows 7 32-bit computer at work. The drivers from the KFU installed absolutely fine on that without issue, first time.
But at home, I only have Windows 7 or Windows 8 64-bit computers. I have tried searching XDA up and down, edited inf files, tried to manually install drivers, even wasted an hour installing JDK / SDK as suggested on some forums.
Nothing works.
If anyone has come up against this and solved it, I'm all ears.
TIA
Loobster said:
Hello
I am really struggling with trying to get the KF drivers installed on ANY Windows 7 x64 computer.
I have access to a Windows 7 32-bit computer at work. The drivers from the KFU installed absolutely fine on that without issue, first time.
But at home, I only have Windows 7 or Windows 8 64-bit computers. I have tried searching XDA up and down, edited inf files, tried to manually install drivers, even wasted an hour installing JDK / SDK as suggested on some forums.
Nothing works.
If anyone has come up against this and solved it, I'm all ears.
TIA
Click to expand...
Click to collapse
I couldn't help you much on the Windows side of things, but have you looked into creating a Linux LiveUSB and running SoupKit to get ADB and fastboot working?
Loobster said:
Hello
I am really struggling with trying to get the KF drivers installed on ANY Windows 7 x64 computer.
I have access to a Windows 7 32-bit computer at work. The drivers from the KFU installed absolutely fine on that without issue, first time.
But at home, I only have Windows 7 or Windows 8 64-bit computers. I have tried searching XDA up and down, edited inf files, tried to manually install drivers, even wasted an hour installing JDK / SDK as suggested on some forums.
Nothing works.
If anyone has come up against this and solved it, I'm all ears.
TIA
Click to expand...
Click to collapse
This is due to driver signature enforcement on x86-64 versions of Windows 7 & 8.
The way around this is to disable that feature.
This is what you'll need to enter into an administrator cmd session:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Note, that does come with some security risks of course since unsigned drivers can then be installed, but in all honesty if you have your system secured properly otherwise it's not much of an issue.
That will allow the drivers to be installed. Note this is just for Windows 7. Windows 8 is an entirely different beast in how to handle this scenario.
Edit - No that's not a typo in the lines above about the DDISABLE part. It's meant to have both D's there.
Morpheus Phreak said:
This is due to driver signature enforcement on x86-64 versions of Windows 7 & 8.
The way around this is to disable that feature.
This is what you'll need to enter into an administrator cmd session:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Note, that does come with some security risks of course since unsigned drivers can then be installed, but in all honesty if you have your system secured properly otherwise it's not much of an issue.
That will allow the drivers to be installed. Note this is just for Windows 7. Windows 8 is an entirely different beast in how to handle this scenario.
Edit - No that's not a typo in the lines above about the DDISABLE part. It's meant to have both D's there.
Click to expand...
Click to collapse
Thanks Morpheus. I'll try that later. And I am wanting to use my Windows 7 laptop.
I'll feed back if it works or not.
No dice.
I don't think it's that the driver isn't signed, it just says no driver found for the Kindle Fire when I connect it up.
It searches WU and doesn't find anything. Then if I manually try and update the device in device mangler, it tells me there is no driver in the drivers folder in the KFU folder.
I have an image of the drive before I ever connected the KF, and before I installed the KFU.
I wonder if I ghosted back to that image, then turned off unsigned driver blocking, then installed KFU, if it would work.
Loobster said:
I have an image of the drive before I ever connected the KF, and before I installed the KFU.
I wonder if I ghosted back to that image, then turned off unsigned driver blocking, then installed KFU, if it would work.
Click to expand...
Click to collapse
Go ahead and roll it back. Then...
In the install_drivers.bat that comes with KFU (right click, select edit), there is a line that says:
Code:
start .\drivers\dpinst64.exe
Change it to say:
Code:
start .\drivers\dpinst64.exe /lm
(obviously for a 32 bit system you would change the "dpinst32" line)
Save the file and run it with the Kindle Fire unplugged.
Next, open a command window and enter the following (you may have to run the command window as admin):
Code:
mkdir .android
Open your user directory and confirm there is a folder named ".android", then copy the "adb_usb.ini" from the Kindle Fire Utility folder into that ".android" folder. Plug your Kindle in, select "disconnect" and you should be able to send adb commands or use the KFU with no problem.
Nope.
I don't get a 'disconnect' option (I take it I should be seeing that on the Kindle Screen?).
I realize though that I omitted some information (sorry) that may make a difference. The KF I am using to connect at home is one that has already been rooted and has the bootloader and Jellybean installed. I guess I might get the 'disconnect' option if I still had the stock Kindle ROM installed.
I don't know why that would make a difference as to why the driver won't install though. I just get the same thing ..... Windows searches WU, doesn't find a driver, and reports driver not installed on the second Kindle item.
I have one item which is installed properly and called 'Amazon Kindle Fire' and is under 'Portable Devices' in Device Mangler. The one that has no driver is under 'Other Devices' and is also called 'Amazon Kindle Fire'. From what I remember of the installation on 32-bit Windows, it seems that this is the version that relates to ADB.
I am about ready to give up on this nonsense and load up a spare HDD with Windows 7 32-bit just for when I want to root these devices and do general tasks with them. I could just swap the HDD in when I need to. A pain, but I'm losing the will to live with this ridiculous driver issue.
Thanks for your help guys.
Ok, so maybe it's not Windows 7 x64.
I installed 7 x86 on a spare disk in the laptop, and it does EXACTLY the same thing, and I cannot use the KFU.
I have no idea what is different about my work Windows 7 32-bit laptop, but apparently it's the only computer I can get the drivers to install to, and get KFU to work on. I've tried four Windows 7 x64 builds and two Windows 7 x86 builds. Only my laptop at work, works.
<sigh>
Loobster said:
I realize though that I omitted some information (sorry) that may make a difference. The KF I am using to connect at home is one that has already been rooted and has the bootloader and Jellybean installed.
Click to expand...
Click to collapse
Yes, it would've been helpful to know this ahead of time.
Do you know what ROM is installed? Look under "About Tablet" in the Cyanogenmod or AOSP Version.
It's Hashcode's release, of 4.2.2.
Kernel Version
3.0.50+
[email protected] #5
Tue Feb 12 23:04:41 PST 2013
Build Number
full_otter-userdebug 4.2.2 JDQ39 eng.hashcode.20130212.152604 test-keys
Loobster said:
It's Hashcode's release, of 4.2.2.
Kernel Version
3.0.50+
[email protected] #5
Tue Feb 12 23:04:41 PST 2013
Build Number
full_otter-userdebug 4.2.2 JDQ39 eng.hashcode.20130212.152604 test-keys
Click to expand...
Click to collapse
Different ROMs and different recovery builds can have different hardware IDs. When you plug your device into USB, you need to go to the device manager and check the hardware ID of that particular build by right-clicking on the device and selecting properties. Under the details tab, there is a drop down menu...select "Hardware Ids". You should see something similar to the following:
Code:
USB\Vid_1949&Pid_0007&Rev_0216&MI_01
USB\Vid_1949&Pid_0007&MI_01
In the KFU drivers folder, there will be a file called "android_winusb.inf" that needs to be edited to accommodate the hardware ID listed for your particular build. Since you are on a 64bit system, you need to add to the Kindle section under "[Google.NTamd64]". For the above example, you would add the following to the "android_winusb.inf", and save it.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Your hardware ID may be different so pay attention to what you are doing. Then go back to the device properties, select the driver tab and update your drivers. From here you should be able to manually install the "android_winusb.inf" by selecting "choose what drivers to install", "Have disk", or however it's laid out on Win7. You may need to do the same for any new ROM you install and you may need to do it for custom recovery also.
I see.
So when a KF is flashed with a different ROM, it presents to the PC as a different hardware string in device mangler, even though it's the same physical device.
That makes sense now since I've rooted two different KFs on the work laptop without any issue, using the same [or very similar] ROM.
I guess that also means that if I attached a KF with a stock Amazon ROM installed, it may well just work fine. I don't know if it's possible to roll back to the stock Amazon ROM. I did take a backup with TWRP before installing the custom ROM.
I will editing the files with the new hardware IDs on the laptop at home and see what happens.
Thanks!
Loobster said:
I see.
So when a KF is flashed with a different ROM, it presents to the PC as a different hardware string in device mangler, even though it's the same physical device.
That makes sense now since I've rooted two different KFs on the work laptop without any issue, using the same [or very similar] ROM.
I guess that also means that if I attached a KF with a stock Amazon ROM installed, it may well just work fine. I don't know if it's possible to roll back to the stock Amazon ROM. I did take a backup with TWRP before installing the custom ROM.
I will editing the files with the new hardware IDs on the laptop at home and see what happens.
Thanks!
Click to expand...
Click to collapse
Just keep your android_winusb.inf and append new hardware IDs every time you switch to a different ROM or device, then manually install it again.
It worked! Thanks a lot Soupmagnet. KFU sees the KF as online and all is well.
I learned something about driver installation and hardware IDs also.
Hopefully this thread will help others coming up against the same issue.
Had a scare tonight, my KF would not turn on! I thought it had failed right at the point when I had an answer. I did the holding down the power button for 30 seconds things, and it powered on with the next press of the power button.
Thanks again all who contributed to the thread.
I had the same trouble
But here is how I got it working- http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Related
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.
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
You are good to go
Cheers to dudes @ "reviewhorizon.com/2011/11/how-to-root-jailbreak-kindle-fire-using-one-click-solution-superoneclick-also-enable-sideloading-apps/"
Congrats... glad to hear you got things working. It's nice to see a user's first post be a success story rather than a cry for help. I'm guessing KFU's driver installer didn't work for you for some reason and you had to do it this way.
This is going to be a day late and a dollar short in your case, but you might try it this way if there's a next time around...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You don't really have to install the SDK to get these drivers installed. You can get everything you need in the KFU distribution with the .inf and .ini files already edited for you. Good luck.
Device Not Found in ADB
Another way to fix the driver issue.
Uninstall driver from device manger. Select delete driver if the option is available.
Copy the driver file somewhere else on your computer
Delete the driver from the old location.
Attach the Kindle and manually install the driver from the new location.
I'm not sure why this worked for me, but after half a day of trying this worked.
This is what FINALLY worked for me
http://www.jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/
joehlmann said:
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
You are good to go
Cheers to dudes @ "reviewhorizon.com/2011/11/how-to-root-jailbreak-kindle-fire-using-one-click-solution-superoneclick-also-enable-sideloading-apps/"
Click to expand...
Click to collapse
Mine just says Android ADB Interface
Combo of a problem
threed42 said:
Mine just says Android ADB Interface
Click to expand...
Click to collapse
I found that this started to happen to me after some ROMs I was flashing ended up getting stuck on the bootscreen. I am not sure what I did in the process, but I messed up my USB drivers. Now no matter how I configure them. I can't seem to get the device to recognize. Even though both windows devices registers the Kindle, it still won't allow me file system access. No matter which rom I try flashing.. I find that nothing seems to work.
I am trying to now restore individual segments to see if I can atleast get a boot up.. otherwise I am dead in the water.
Any help?
Oh yeah, Fastboot.. works fine.. isn't there a stock image I can just fastboot Upgrade?
John
KF not recognized in PC. Shows up as GT-P1000 instead and sdcard access.
Noob to XDA so forgive if this post is in the wrong area. I am at my wits end.
ADB: KF to PC connectivity lost after ROM install
The Good News, Bad News and Solution Attempts…
The Good News.
I installed the GedeROM CM9 ICS 4 (GedeROM ICS v4.04 CM9 Kernel v3.0.21) to my 1st generation Kindle Fire and it runs great. It is much smoother at running Air for Android with an App that I have been developing. The USB Host works great with my Logitech Wireless Keyboard and Mouse Combo with the OTG USB Dongle and Logitech nano receiver. I want to keep using this ROM as it is very functional for my needs.
The Bad News.
Now, let’s get to the frustrating part. No more drag and drop. After the install, my PC no longer recognizes the it as a Kindle Fire as a drive or sdcard. It recognizes it as a GT-P1000 (Galaxy Tab P1000). Because of this mis-reporting to the PC device manager the KF and sdcard are no longer visible as a drive on the PC for me to browse, drag and drop items.
The Device Manager sees the
---Android Phone > Android ADB Interface
or depending on the driver
---Android Phone > Android Composite ADB Interface
and no where in the Device Manager does it show the Kindle Fire any longer.
The only place the device is listed is in
---Control Panel > Hardware and Printers > GT-P1000(!). (Unknown Device)
Attempted Solutions.
1. Driver Reinsall(s) with and without SDK.
I tried reinstalling the drivers for the KF and this changed it from Android Composite ABD Interface to Android ADB Interface. (no change) I reinstalled the Composite interface and still no KF. I also tried a few different versions of drivers up and down the spectrum trying to get this installed. Including trying to install a GT-P1000 driver from Samsung. Still no luck.
2. Android Debugging
I tried to turn on and off and on etc the Android debugging in Settings > Developer Options > Android Debugging. No Luck.
3. Turn on USB Mass Storage
Unable to do this as the options are simply just not there.
4. Reboots
Countless reboots (PC and KF) and cache wipes with and without the KF attached.
5. Different ROM
I tried a different ROM for Jelly Bean 4.2 and it was successful and recognized as a KF and I could browse to the folders on the sdcard. However this ROM was so striped down that it was not really functional for me as there was no file explorer, market app, or any way to browse to the sdcard to install any app that I could drag and drop into the sdcard in the hopes of installing a file explorer and market app. The issue seems to be with the GedeROM CM9 that I am using.
Am I going to have to try multiple ROMS until something works?
Specs:
Kindle Fire (1st Gen, spring of 2012, original one purchased in December 2011, but suffered screen smash)
GedeROM ICS v4.04 CM9 Kernel v3.0.21
The PC I am using is running Windows 7 Professsional.
kinfauns said:
Congrats... glad to hear you got things working. It's nice to see a user's first post be a success story rather than a cry for help. I'm guessing KFU's driver installer didn't work for you for some reason and you had to do it this way.
This is going to be a day late and a dollar short in your case, but you might try it this way if there's a next time around...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You don't really have to install the SDK to get these drivers installed. You can get everything you need in the KFU distribution with the .inf and .ini files already edited for you. Good luck.
Click to expand...
Click to collapse
Work Around Found... Sort of.
KF_Mike_KF said:
Noob to XDA so forgive if this post is in the wrong area. I am at my wits end.
ADB: KF to PC connectivity lost after ROM install
The Good News, Bad News and Solution Attempts…
The Good News.
I installed the GedeROM CM9 ICS 4 (GedeROM ICS v4.04 CM9 Kernel v3.0.21) to my 1st generation Kindle Fire and it runs great. It is much smoother at running Air for Android with an App that I have been developing. The USB Host works great with my Logitech Wireless Keyboard and Mouse Combo with the OTG USB Dongle and Logitech nano receiver. I want to keep using this ROM as it is very functional for my needs.
The Bad News.
Now, let’s get to the frustrating part. No more drag and drop. After the install, my PC no longer recognizes the it as a Kindle Fire as a drive or sdcard. It recognizes it as a GT-P1000 (Galaxy Tab P1000). Because of this mis-reporting to the PC device manager the KF and sdcard are no longer visible as a drive on the PC for me to browse, drag and drop items.
The Device Manager sees the
---Android Phone > Android ADB Interface
or depending on the driver
---Android Phone > Android Composite ADB Interface
and no where in the Device Manager does it show the Kindle Fire any longer.
The only place the device is listed is in
---Control Panel > Hardware and Printers > GT-P1000(!). (Unknown Device)
Attempted Solutions.
1. Driver Reinsall(s) with and without SDK.
I tried reinstalling the drivers for the KF and this changed it from Android Composite ABD Interface to Android ADB Interface. (no change) I reinstalled the Composite interface and still no KF. I also tried a few different versions of drivers up and down the spectrum trying to get this installed. Including trying to install a GT-P1000 driver from Samsung. Still no luck.
2. Android Debugging
I tried to turn on and off and on etc the Android debugging in Settings > Developer Options > Android Debugging. No Luck.
3. Turn on USB Mass Storage
Unable to do this as the options are simply just not there.
4. Reboots
Countless reboots (PC and KF) and cache wipes with and without the KF attached.
5. Different ROM
I tried a different ROM for Jelly Bean 4.2 and it was successful and recognized as a KF and I could browse to the folders on the sdcard. However this ROM was so striped down that it was not really functional for me as there was no file explorer, market app, or any way to browse to the sdcard to install any app that I could drag and drop into the sdcard in the hopes of installing a file explorer and market app. The issue seems to be with the GedeROM CM9 that I am using.
Am I going to have to try multiple ROMS until something works?
Specs:
Kindle Fire (1st Gen, spring of 2012, original one purchased in December 2011, but suffered screen smash)
GedeROM ICS v4.04 CM9 Kernel v3.0.21
The PC I am using is running Windows 7 Professsional.
Click to expand...
Click to collapse
I have tried several different ROMS today.
I have found that they just dont have the stability and functionality that I like with the version that I am running. SO.... that being said, I found a work around. I can keep the existing ROM in place and if I need to copy something to the SD Card, I can just boot into TWRP and mount the USB drive, make the file copies and then reboot. It's a little annoying, but none so much as not being able to do it at all.
Thanks for the input.
joehlmann said:
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can /"
Click to expand...
Click to collapse
step 3 does not work! windows was unable to install your amazon kindle fire hd!
what shall i do?
This didnt work for me
I dont know why but whenever I try to manually install the driver it pops up with an error saying something on the lines of 'The Folder does not contain a suitable software for your operating system' basically saying there is not software compatible with 32bit. I have been trying to root my kindle fire for 2 days now. I have tried to use SDK and KFU none of them worked. I will attach the errors Im getting!
Someone Help Pleasee
if all eles fails and all you want to do is copy files over try "wifi file explorer" on the playstore. very handy app to have installed just in case
Hey, well now that my Kindle has had a charging problem for quite some time, I sent it out and got a new one for no charge. So now that I have received it, I'm trying to root it, and I notice that Kindle Fire Utility is not connecting to ADB, so I proceed to re-install the drivers. It worked fine before I updated to Windows 8 from Windows 7, but now it just plain won't install. I do have another computer I can use with Vista and have tried, and the drivers will install on, but it detects my Kindle as an Android ADB Interface, not a Kindle. I have installed the drivers multiple times. So my question is how can I get KFU working? Please respond ASAP. Thanks!
EDIT: Resolved with another computer by uninstalling driver software then reinstalling
For anyone wanting to know how to install unsigned drivers shift+ restart, then select troubleshoot, then advanced options, then startup settings, then restart. After reboot select f7 to disable driver signature enforcement it will reboot again, then simply just install the driver.
camason24 said:
Hey, well now that my Kindle has had a charging problem for quite some time, I sent it out and got a new one for no charge. So now that I have received it, I'm trying to root it, and I notice that Kindle Fire Utility is not connecting to ADB, so I proceed to re-install the drivers. It worked fine before I updated to Windows 8 from Windows 7, but now it just plain won't install. I do have another computer I can use with Vista and have tried, and the drivers will install on, but it detects my Kindle as an Android ADB Interface, not a Kindle. I have installed the drivers multiple times. So my question is how can I get KFU working? Please respond ASAP. Thanks!
EDIT: Resolved with another computer by uninstalling driver software then reinstalling
Click to expand...
Click to collapse
No comment on the win8 since I haven't had a chance even looking at it.
On the other computer, it seems the driver installed correctly except that a normally booted up KF should read Android Composite ADB Interface.
W8 and KF - ADB finally recognized it.
I finally got adb to recognize my Kindle Fire on Windows 8. Device Manager still thinks it's a Android ADB Device - but at least ADB works.
[DISCLAIMER - I'm not a windows guru, so anyone who is feel free to adjust, or comment on these instructions to make them better. This worked on my W8 computer - I won't guarentee that it will work on yours...not all W8 installations are the same!!]
Before you preform this - make sure you have the latest Google SDK installed. If you're not computer literate (meaning you can administer your own computer without help) then DON'T do this.
Here's what I did to make it work.
First you will need to set up W8 to install unsigned drivers as suggested by Thepooch in post #2 of this forum.
Windows Key + C - brings up charms
Shift + Restart from the power menu
Select Troubleshoot
Select Advanced Options
Select Startup settings
Select restart
When menu comes up after restart - select F7
W8 puts the Kindle at different addresses that W7, so you'll need to edit two files.
Plug in your Kindle to the computer. Open Device Manager under W8 (you need to be computer literate to complete this. You've been warned!)
If you're Kindle shows up as a Galaxy Nexus then uninstall the drivers. Make sure you're Kindle is identified as a Kindle in the build.prop file on the device. If not, just do a quick reinstall of the OS.zip file and that should reset it.
Plug in the Kindle to the computer - Device Manager should find it as a Kindle Fire
Now right click on the Kindle Fire (should have yellow exclamation marke), open the properties tab.
Click on the Details Tab, select Hardware ID's. The Hardware ID for the Kindle on W8 is different that W7! You need to edit two files to adjust the hardware ID's so ADB will find the Kindle.
Leave the Properties Windows Open.
Go to C:\Users\"Your user folder"\AppData\Local\Android\android-adk\extras\google\usb-driver\
Open android_winusb.inf and insert the following three lines under [Google.NTx86] and [Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01
VERY IMPORTANT: The VID_#### and the PID_#### should MATCH what is displayed in the open Properties windows - check and make sure these numbers match!! Your Hardware ID's could be different!!
Save this file.
Go to c:\users\"Your User Name"\.android
Open adb_usb.ini with notepad.
Key in 0×18D1 (This is the same number you used in the VID_#### and PID_#### from the properties window - make sure it matches!)
Now go back to the properties window.
Select the general tab
Select update driver ....
Select Browse my computer for driver software to locate the driver software manually.
browse to C:\Users\"Your user folder"\AppData\Local\Android\android-adk\extras\google\usb-driver\ - select ok and install the driver
W8 will give you a big, nasty security prompt (only if you've enabled installation of unsigned drivers) - just hit okay.
The driver should install and you should see the Kindle as an Android ADB device now.
Testing Kindle Fire adb USB driver
Bring up command prompt (CMD).
Type adb kill-server then enter.
Type adb devices then enter.
That’s it. You should see Kindle Fire as one of the devices.
You should now be able to use ADB to manage your Kindle.
Hope this helps. Good luck.
i have managed to sucessfully install a 2nd bootloader, TWRP Recovery, and CM10.1 onto my new KFHD with no apparent problems, following Hashcode's guide at http://forum.xda-developers.com/showthread.php?t=2128175.
I had already set up my system to support developing and debugging the KFHD, including the Amazon-specific Kindle Fire USB drivers; when plugged in, the device showed up in Device Manager as a "Kindle" with a "Composite ADB Interface", and `adb devices` detected the device.
After flashing the CM10.1 ROM I can no longer see my device as anything except an MPT USB Device, and `adb devices` says there are no devices attached.
I have tried both the Google USB drivers and the Kindle USB drivers and Windows claims that neither of them is correct for my hardware. When I check Device Manager, it says the attached device is VID_18D1, PID_6860, REV_0100, which doesn't match any of the device descriptors in either of the driver inf files.
Which driver am I supposed to be using now and how can I get it to install properly?
EDIT: I had forgotten to re-enable ADB Debugging on the tablet after flashing; now it is actually called an "Amazon Kindle Fire HD" and has a different device descriptor:
VID_18D1&PID_6861&REV_0261&MI_01
but still no love from ADB.
Thanks.
I'm having the same problem. No connection to ADB, and MTP only exists as a single file when activating the camera toggle. Frustrating to say the least, but not a deal-breaker.
Oh and a friend has the same problem. I know its not helpful, but atleast you're not the only one
That's really odd as adb works fine for me on Haschode's 10.1 Perhaps try reinstalling the drivers, The adb drivers are - click here
You may need to uninstall the old drivers before these work. Also, goes without saying that you need to enable USB debugging on the tablet!
No more Composite ADB driver after installing CM10.1
apd said:
That's really odd as adb works fine for me on Haschode's 10.1 Perhaps try reinstalling the drivers, The adb drivers are - click here
You may need to uninstall the old drivers before these work. Also, goes without saying that you need to enable USB debugging on the tablet!
Click to expand...
Click to collapse
I installed Hashcode CM10.1 for the first time tonight on an KFHD 8.9.
I have the same problem on both Windows and LINUX: loading CM10.1 on an HFHD8.9 tablet. (No ADB)
I use both every single day on both windows and LINUX so have lots and lots of experience.
In windows after installing 2nd boot /twrp and Hashcode zips (8.1.4.zip, or 8.4.1.zip) I have to use some old windows drivers for ADB and fastboot does not work at all. In LINUX, ABD and fastboot work for both Stock Kindle OS and all of Hashcodes Mod'd KindleOS.zips
If I load Hashcode's CM10.1, I have not ADB on Windows or LINUX ADB Devices shows 123456789ABCDE offline
Recovery shows devices = 123456789ABCDE Recovery
I can push files in Recovery but, not if the tablet boots into OS.
If I revert back to any one of the Hashcode KindleOS.zip images all is well at least in LINUX.
This issue is definately related to something driver wise in the CM10.1 OS.
Regards
I saw this same issue
I had this same issue after installing twrp and CM 10.1 as well. I was fortunate to have a second laptop that had not been used for this stuff before, and once i installed the adb drivers on that machine, had no issue connecting to the tablet from that machine. I still could not connect to it from the original machine. My guess would be to uninstall the ADB drivers from the machine you are using to connect, and reinstall. if that doesn't work, hopefully you have a spare machine, otherwise you might need to look at re-imaging you computer. I happen to keep a stock image file of my laptop in case of hard drive failure or other emergency, so it was about 20 minutes, and i was back up and running.
Disclaimer:I am not responsible if using anything I've made or provided suddenly deep-fries your device or causes thermonuclear war leading to alien abductions.
Hey guys!
It's been a while that I've been seeing people having problems to enable USB debugging and setting up the Android SDK to recognize the device. So,I've made a guide to help you enable USB debugging and set up the Android SDK accordingly. So let's begin!
What you'll need:
Windows/Linux/Mac OS X with the Android SDK installed
A Fire Phone
Click to expand...
Click to collapse
Setting up Android SDK and drivers:
At first,make sure you have the Android SDK installed,adb and fastboot working.
Open the SDK manager
Click on "Tools" and then click on "Manage add-on sites"
Click on the "User Defined Sites" tab,click "Add" and paste this URL:https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
Click "Ok". Wait for it to finish. Then,from the repo of Android 4.2.2(API Level 17),select Fire Phone SDK and install it.
Remove any Fire Phone drivers using device manager
Go to the directory of the SDK and find this:
Code:
/add-ons/addon-fire_phone_sdk_addon-amazon-17/tools/KindleDrivers.exe
Run the driver setup and connect the phone having USB debugging enabled. If you don't know how to do this,it's explained below.
Done!
Click to expand...
Click to collapse
Enabling USB debugging:
Go to Settings
Scroll to the Device section and expand the section.
Tap Get info about your Fire.
Tap any item at least 7 times in 5 seconds
Developer options will appear. Set it to On.
Go to developer options and enable USB debugging.
Done!
Click to expand...
Click to collapse
Thanks a lot for reading my guide. If this was useful to you,please hit the thanks button. Feel free to comment,post or report anything. Thanks.
Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:
I am M3 said:
Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:
Click to expand...
Click to collapse
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
Could you try in a Linux distro live CD? It should detect the device without a hitch
Sent from my device running CyanogenMod 11
I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
If you're using Windows here's how I did it on Windows 7. Once you open ADB and reboot it into recovery mode remove it from Device Manager. Reboot you PC if asked. Never unplug or remove your phone through any of this. You may need to remove it a second time from Device Manager after a reboot. It'll eventually show up under Other Devices with the Model Number as the device name (at least mine did). Once it's there then go and update the driver. Tell Windows you want to pick from a list of all the devices. Scroll down until you see Amazon listed on the left side. You'll then see "Android Composite ADB Interface" listed on the right. Choose that. Then it should be recognized again and you can sideload to roll back. Once you roll back you'll probably get a lot of errors but it will work and it will root using the towelroot APK that's posted in the other forum here. I had to have my phone services so I had to do a factory reset on my phone because it broke my phone services. But the roll back process itself was very easy to do once I figured out how to get it recognized again while in recovery mode.
I did what the directions say, but I don't see the fire phone listed in the sdk.
mnknight said:
I did what the directions say, but I don't see the fire phone listed in the sdk.
Click to expand...
Click to collapse
You have to choose the correct driver in Device Manager
On Windows 8/8.1 you may have to activate unsigned drivers
Kindle drivers don't seem to be working for me!
In Windows 8 and newer you have to activate unsigned drivers.
And please choose driver in device manager!
Kindle driver not working for me on windows 7
Kindle driver not working for me on windows 7
Grizzly123 said:
Kindle driver not working for me on windows 7
Click to expand...
Click to collapse
Try using a Linux distro
hey, first sorry for my bad english. isnt my native language.
ich have installed all i need (Windows/Linux/Mac OS X with the Android SDK installed,Android SDK installed,adb and fastboot working[but i dont really know what fastboot working means.])
i have no problem with step 1-5 but i dont understand step 6. i google it but i dont understand. can you please update pictures? that would be very nice.
i have a sec question. my fire phone is netlocked(german). is where still a netlock after install andoid?
again, sry for my bad english :/
thanks for help
munir
Step 6.
In windows device manger, remove all the fire phone devices listed.
Then run the KindleDivers.exe listed in step 7.
When you plug the phone back in windows "should" find and use the right drivers.
Thank you
For reference, the drivers have now moved. The following is an extract from the latest release notes:
* Windows USB drivers have been removed from the tools directory. You may access them from the SDK Manager under Extras.
Click to expand...
Click to collapse
They're installed with the package Extras / Kindle Fire USB Driver and will be located at: android-sdk\extras\amazon\kindle_fire_usb_driver
Other than that, instructions work fine, thanks
hello op, i got as far as step 4, when you mention add the link, mine shows new, everything after step 4 is different. can you please help?
Stuck on recovery
Solved it
Update: in the sdk manager, you must select 'kindle fire usb driver' under 'extras' now, and install that package. Then, you can find it in the sdk dir under sdk/extras/amazon/kindle_fire_usb_driver/KindleDrivers.exe