THIS IS DRIVER SPOOFING, I DO NOT ASSUME RESPONSIBILITY OF WHAT YOU MAY DO TO YOUR KINDLE, THIS ONLY WORKS WITH KINDLE FIRE'S SUPPORTED BY THE AMAZON DRIVERS, YOU ARE EDITING THEM AND ADDING ID'S, IF YOU DO IT TO A DEVICE NOT SUPPORTED I'M NOT RESPONSIBLE.
First, you obviously need the drivers. You can grab them from here.
Start with a fresh install (uninstall what you have if you do have anything)
Install them, then turn on your ADB on your kindle in your settings>security>Enable adb if your using amazon, or developer options in CM10.1 (click build number 6 times I believe)
Now to Device Manager (Type "Device Manager" in start menu or go to the control panel and find it)
2 Scenarios can happen, You see something that says "Kindle" or something that is an "Unknown device" under the other devices tree
If You see the kindle under "other devices" right click it go to properties, then to details and in the drop down look for "Hardware Ids" In my experience there should be TWO entries, some devices have some more, so if you have "Unknown device" this is a good sign. Like So.
You need to go to "C:\Program files\Amazon.com\Kindle Fire\Drivers\" then open android_usb.inf
(If you have 64 bit windows it'lll be \Program files (x86)\
under the sections "[Amazon.NTx86]" and "[Amazon.NTamd64]"
you need to add new entries for your device something along the lines of
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_6860
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&REV_0216&MI_01
Or sometimes
Code:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216
Make sure all the numbers after "PID_" , "VID_" and "REV_" Match what you see in the Hardware ID's tab. THE ONES IN THE PICTURE ARE FOR A DIFFERENT DEVICE THEREFORE DIFFERENT THEN MY CODE EXAMPLES AND POSSIBLY DIFFERENT FROM YOUR ID'S
After you've added the aforementioned ID's save the file (With admin issues save the file elsewhere and move it over and either overwrite or rename the original)
Now select the device in Device Manager and try to update the drivers from the folder earlier (Amazon.com etc etc) It should work and be recognized.
You may have to do this for the devices different states (Ex. Fastbooot can be different and The stock OS can be different ID's other than the Recovery)
You can always check it with "adb devices" in command prompt
Hopefully this helped, I've had to do it when nothing else worked, kept me from using SoupKit and such and dealing with a whole other mess of problems. Reply If it wasn't clear enough and I'll refine this some more.
Thanks so much for this! I've been banging my head against the wall trying to get adb working again after flashing CM10.1. I did have to update drivers in recovery as well as CM10.1, but NOT fastboot.....just posting my experience.
Related
I've downloaded the motorola driver installation tool and run it, and it acts like everything worked, but windows still says that the drivers are not installed for the phone.
- Charging works (of course)
- Mass storage works (of course)
- "Phone Mode" works (where the PC sees the phone as a phone or modem - or, for this phone, apparently a CD drive?)
- "ADB Interface" does not work (where you have debugging checked and can do cool stuff with your phone)
I understand that since it doesn't I may have to edit the android_winusb.inf file with the info for my phone, and I know where to get its device ID from. I try to mimic the other entries in that file but there are 4 things I need to enter - single adb, composite adb, and two lines for single bootloader. I guess I don't know exactly what to put there. This is what I tried:
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_00
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D&REV_0216
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D
Someone else must have encountered this before. What did you put in that file to make it work? When I tell windows to find a driver for my "Motorola ADB Interface" in the folder C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver ... it just tells me that it can't find any information about my device.
jeez, all this just to be able to tether using pdanet.
http: //www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
I notice that ADB would never load in recovery, while it would load in regular mode.
The driver was never found in Windows, and it was just called" Transformer."
To fix this you need to do a little driver ini edit to include the hardware IDs in the Google USB driver from the SDK.
Here are the steps that you need to follow in order to enable these drivers:
You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
Open the google-usb_driver folder that you will find inside your Android SDK folder.
Open the android_winusb.inf file in notepad or any text editor to edit it.
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
Open a command prompt window and enter this command:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
Choose to view all devices and click ‘Have Disk…’.
Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
Once the drivers have been installed, you should be able to use ADB with your device.
To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB.
Although these instructions were originally written for Toshiba AC100, they should work for any Nviaid Tegra or Tegra 2 based Android device.
Click to expand...
Click to collapse
The hardware device ID used in regular mode is different than the one in recovery enough to cause a problem.
I found that this is for reg mode
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&MI_01
and this worked in receovery
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F
After the edit and following the instructions I was able to use ABD in recovery
Useful and often overlooked tip, Thanks!
Hallo!
I want to to show you how I managed to get an ADB USB Driver, when the hardware vendor doesn't supply such a driver
I only tell you what I did with my device, without any warranty. If you do the same to your device, you do anything on your own risk. Doing these things might end up in a damaged device. When you are not sure what you are doing, do NOT the same to your device. I do not promise anything, I just tell you what I did
I needed a Windows 7 PC whit an installed java JDK 1.7 (If I would not have this, I would download it from java.oracle.com)
.
First Step: I download the Android SDK from here:
http://dl.google.com/android/installer_r21.0.1-windows.exe
I installed the Android sdk on my Win7 Computer by doubleclicking on the installer_r21.0.1-windows.exe and startet the Android SDK Manager.
I took some time to load a ist of available packages, and the I could select
Tools->Android SDK Plattform-tools
Extras->Android Support Library
Extras->Gogle USB Drivers
and I pressed the button 'Install 3 Packages'
A Dialog opened and I checked 'Accept All' and pressed the Button 'Install'. I waited to complete...
Second Step: I checked in the settings of my device:
Developer->USB Debugging
I connected my device via USB to my PC and opened the Device Manager.
I selected my device which was marked with a yellow warning sign. With a right-click on it I got the context menu and choose 'Properties'.
In the 'Details' tab i selected the property 'Hardware Ids' where I found the values (for my device) VID_18D1 and PID_0003.
If you want to do the same, not the values for your device...
Third Step: I opend Windows Explorer and navigated to the folder:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
I opened the file 'android_winusb.inf whit my texteditor and copied the lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E21
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
and changed the copy to those values (if you want to do the same, you must not use my values, but the values you noted in the step before!):
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
So it matched the values I found in the properties of my device (or if you do it, the values from your device).
I saved the changed file.
Forth Step:
In the Device Manager I right clicked on my device and choose 'Update Driver'. In the Driver dialog I selected to 'Browse my computer for driver software' and pressed Next. At the point 'Search for driver software in this location:' I navigated to this folder:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver.
I choose to install this driver software even it is not signed.
After this step my Device was correctly recognized by windows.
If you do the same, you do it on your own risk! I do not recommend you to do the same
Kind regards, Uwe
The drivers that I downloaded from the Alcatel website didn't have the ids for the OneTouch Pixi 7 (9006w), so I modified the Google USB Drivers.
I edited "android_winusb.inf", removing all entries for Google devices and added our device.
Code:
[Google.NTx86]
;Alcatel 9006w
%SingleAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&REV_0225&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&MI_01
[Google.NTamd64]
;Alcatel 9006w
%SingleAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&REV_0225&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&MI_01
I also updated the string section at the end of the file.
Code:
[Strings]
ProviderName = "ALCATEL"
SingleAdbInterface = "Android ADB Interface (ALCATEL 9006w)"
CompositeAdbInterface = "Android Composite ADB Interface (ALCATEL 9006w)"
SingleBootLoaderInterface = "Android Bootloader Interface (ALCATEL 9006w)"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Devices"
Download here.
Double-click "install.cmd" to start the driver installer.
I was able to get this to work in Windows 7 64-bit and Windows 10-64-bit. I have not tested 32-bit or Windows 8.
I had to disable driver signature verification for this to work in Windows 10, I would assume this would also work for Windows 8. Feel free to test and let me know.
I have also included adb and fastboot in the "platform-tools" folder in case anyone doesn't already have them installed.
Error message "Windows cannot find 'adb-interface-driver/dpinst-amd64.exe'. Make sure you typed the file name correctly, and then try again." when I double-click "install.cmd" to start the driver installer. I am running on Windows 10 and have disabled driver signature verification. Any help would be greatly appreciated.
Muxintorq said:
Error message "Windows cannot find 'adb-interface-driver/dpinst-amd64.exe'. Make sure you typed the file name correctly, and then try again." when I double-click "install.cmd" to start the driver installer. I am running on Windows 10 and have disabled driver signature verification. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you ARE NOT running it "As Administrator", and that you are, in fact running an AMD 64 bit CPU and Version of Windows.
Also, some folder locations are protected, and the location you view from the API (What you see/use while using the computer) is not, in fact, the location it says it is... it's in a temporary, protected location in case you change/delete/install something that damages windows. That way, it can prevent the change to the actual operating machine files themselves, and keep users & 3rd party software from damaging Windows or the computer itself. They started that in Vista.
OriginalHardwyre said:
Make sure you ARE NOT running it "As Administrator", and that you are, in fact running an AMD 64 bit CPU and Version of Windows.
Also, some folder locations are protected, and the location you view from the API (What you see/use while using the computer) is not, in fact, the location it says it is... it's in a temporary, protected location in case you change/delete/install something that damages windows. That way, it can prevent the change to the actual operating machine files themselves, and keep users & 3rd party software from damaging Windows or the computer itself. They started that in Vista.
Click to expand...
Click to collapse
Is it required that you have to have a AMD 64 bit CPU or a regular Intel 64 bit CPU will work on this also?
Thanks.
Amd64 basically just means 64-bit, for Intel or amd.
How to modify Amazon's ADB driver for the new 8th gen, 8" Fire, codename "karnak"
I've just attempted to connect ADB to my new, 8", 8th generation Amazon fire, to no avail. It appears that Amazon failed to update the VID & PID for codename "karnak" - aka the 8th gen, 8" Fire - in the drivers, so here's how you add it:
1:/ Download, unZIP and install Amazon's ADB & USB drivers for Fire: https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
2:/ Navigate to: "C:\Program Files (x86)\Amazon.com\Fire_Devices\Drivers"
3:/ Open "android_winusb.inf" in Notepad/Notepad++ etc, and modify thusly:
Locate the section header highlighted in blue, and add the code highlighted in red, save, exit and install/reinstall the drivers using "Device Manager":
(Ignore the code which is green, below, it's simply included to give you some navigational context within the file)
[Amazon.NTx86]
;karnak
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0338
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0338&MI_01
;Otter
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
;jem
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0008&MI_01
Something is wrong i think.
My Fire HD8 comes today. On Windows i see following
USB\VID_1949&PID_0331
and u write this
VID_1949&PID_0338
After i saw this, i changed your "Code files" to PID 0338
But then i got a Popup with Hash is wrong.
TheNox88 said:
Something is wrong i think.
My Fire HD8 comes today. On Windows i see following
USB\VID_1949&PID_0331
and u write this
VID_1949&PID_0338
After i saw this, i changed your "Code files" to PID 0338
But then i got a Popup with Hash is wrong.
Click to expand...
Click to collapse
As you can see, I stated that this is for the 8th gen, 8". Maybe you could check again? I don't offer support, I simply offer my findings as I discover things that fixed my problem. I hope you'll not be discouraged, and will try again God bless you.
This is great, thanks a lot! Can't believe this is not mentioned anywhere else. I only found it after searching for the string "USB\VID_1949&PID_0338"
Question - do we need to add the extra code under the [Amazon.NTamd64] section as well?
mbwf said:
I've just attempted to connect ADB to my new, 8", 8th generation Amazon fire, to no avail. It appears that Amazon failed to update the VID & PID for codename "karnak" - aka the 8th gen, 8" Fire - in the drivers, so here's how you add it:
1:/ Download, unZIP and install Amazon's ADB & USB drivers for Fire: https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
2:/ Navigate to: "C:\Program Files (x86)\Amazon.com\Fire_Devices\Drivers"
3:/ Open "android_winusb.inf" in Notepad/Notepad++ etc, and modify thusly:
Locate the section header highlighted in blue, and add the code highlighted in red, save, exit and install/reinstall the drivers using "Device Manager":
(Ignore the code which is green, below, it's simply included to give you some navigational context within the file)
[Amazon.NTx86]
;karnak
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0338
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0338&MI_01
;Otter
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
;jem
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0008&MI_01
Click to expand...
Click to collapse
Was worth a try, but didn't work on my PC, Surface Pro 3. I added the text you listed, but I get this after trying to update driver:
---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
---------------------------
OK
---------------------------
What steps did you use to install/reinstall the driver using Device Manager? Thanks!