Related
Hi everyone,
i've bought a SCLCD Nexus S (GT-i9023).
I've tried to get the device recognized by the Google Android USB driver packaged with the Android SDK r10.
But the android_winusb.inf file provided with the USB drivers version r4 doesnt mention the Nexus S :
Code:
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
Having a look at Windows devices manager, i've added my Nexus S device identifier ton the .inf file :
Code:
;
;Google NexusS
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
With this i've been able to use fastboot and unlocked my phone.
But when im trying to use ADB, my device is not listed as connected. So i've modified the previous lines by these one:
Code:
;
;Google NexusS
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&MI_01
But it doesn't change anything :x
Do you succeed in using the Google Android USB drivers
With wich Nexus S version ?
Does it have ever worked ?
Go Google go !!! This device is month old
Hi folks,
final answer, to make the GT-i9023 works with Google Android USB drivers you got to edit the "android_winusb.inf" file located in the "extras\google\usb_driver" dir of your Android SDK installation to add the following line to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
Code:
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
If this is not working, you got to :
* go to the Windows devices manager and uninstall the driver for every Nexus S sub-devices as describe in the attachment
* wait for windows to ask for installing the new devices using your new .inf file
* restart adb : adb kill-server & adb start-server
Should be working fine then
Still cannot recognize my i0923
I was trying to write a recovery image to my nexus s (i9023 with SCLCD), and have successfully installed the usb driver for my nexus s, but both fastboot and adb just cannot recognize the device. When I typed
Code:
fastboot devices
and
Code:
adb devices
, nothing shows up. Is there anything that I can do to fix this? Thanks!
I solved the previous problem
I browsed your guide to unlock nexus s and found someone suggested in the reply to copy AdbWinApi.dll and AdbWinUsbApi.dll from platform-tools directory to tools directory, then it worked.
Hope someone sees this and it will work for them.
Thanks for this, now my Nexus S bootloader is unlocked.
( no need for Pdanet program or other crazy solutions)
one more Trick
i did all the above and it didn't work but i added an another trick that worked
C:\Program Files (x86)\Android\android-sdk\tools>adb devices
List of devices attached
....
no devices were found , though SNS was found in Device manager ,
to fastboot unlock , i did the below command
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe -s YOUR_SERIAL_NUMBER oem unlock
...
OKAY [ 38.590s]
finished. total time: 38.590s
and it worked , give it a try if you faced drivers issues
NEWBIE HERE. I have the i9020T. Will any of these fixes work for this one? And I'm a little confused on where to start. Where do I type all these commands?
jrocka01 said:
NEWBIE HERE. I have the i9020T. Will any of these fixes work for this one? And I'm a little confused on where to start. Where do I type all these commands?
Click to expand...
Click to collapse
Have you found your answer?
If not, try this link.
http://forum.xda-developers.com/showthread.php?t=895545 - AllGamer has put the process step by step very clearly, and this thread is specifically for i9020T for Gingerbread 2.3.3, I am pretty sure it is same for 2.3.4 as well.
If you want to know where to type all these and all, pm me and I will get you some answers.
If you don't want to get into typing a lots of commands, you can't get away with it completely, but try doing what vincentleung says, put those two files into the directory, it worked for me as well.
creativedevil said:
Have you found your answer?
If not, try this link.
http://forum.xda-developers.com/showthread.php?t=895545 - AllGamer has put the process step by step very clearly, and this thread is specifically for i9020T for Gingerbread 2.3.3, I am pretty sure it is same for 2.3.4 as well.
If you want to know where to type all these and all, pm me and I will get you some answers.
If you don't want to get into typing a lots of commands, you can't get away with it completely, but try doing what vincentleung says, put those two files into the directory, it worked for me as well.
Click to expand...
Click to collapse
I've lost USB connectivity so this won't work. Do you know of a way to do it OTA?
Might be obvious but is there a chance you can root your device using improper drivers?
Needed to do the exact same thing on my brand new Vidéotron Nexus S this week-end.
I added these lines:
Code:
; Google Nexus S
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&MI_01
My Nexus S required the following lines:-
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
Note the change of ID from 4E20 to 6860
1st one works for recovery, second is for ADB
Device is running Koush ICS (CM9 Alpha 12)...
Not sure if that's why they are different.
Update: after installing the driver make sure to change the folder in cmd to \android-sdk\platform-tools and then run fastboot, as that's where fastboot.exe is (newly).
kursk said:
Hi folks,
final answer, to make the GT-i9023 works with Google Android USB drivers you got to edit the "android_winusb.inf" file located in the "extras\google\usb_driver" dir of your Android SDK installation to add the following line to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
Code:
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
If this is not working, you got to :
* go to the Windows devices manager and uninstall the driver for every Nexus S sub-devices as describe in the attachment
* wait for windows to ask for installing the new devices using your new .inf file
* restart adb : adb kill-server & adb start-server
Should be working fine then
Click to expand...
Click to collapse
thank u for this guide...it really saved my rest this night
worked for me!
TrickyEarlobe said:
My Nexus S required the following lines:-
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
Note the change of ID from 4E20 to 6860
1st one works for recovery, second is for ADB
Device is running Koush ICS (CM9 Alpha 12)...
Not sure if that's why they are different.
Click to expand...
Click to collapse
Worked for me! Thanks! Just had to go next to device manager and select the file for the driver.
Thanks
sampainho said:
Worked for me! Thanks! Just had to go next to device manager and select the file for the driver.
Thanks
Click to expand...
Click to collapse
Does this work for the NS4G as well? I can't find a forum post similar to this and I've been trying for hours to get my drivers correct.
Jyro275 said:
Does this work for the NS4G as well? I can't find a forum post similar to this and I've been trying for hours to get my drivers correct.
Click to expand...
Click to collapse
It should work, you must add the correct lines inti the .inf file. To find the correct strings, check the properties of the unknown device in the Windows hardware manager.
I'm also having problems with finding a driver. Going to try this when I get home.
Verstuurd vanaaf miene Oneplus One mit CM11-M11
kursk said:
Hi folks,
final answer, to make the GT-i9023 works with Google Android USB drivers you got to edit the "android_winusb.inf" file located in the "extras\google\usb_driver" dir of your Android SDK installation to add the following line to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
Code:
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
If this is not working, you got to :
* go to the Windows devices manager and uninstall the driver for every Nexus S sub-devices as describe in the attachment
* wait for windows to ask for installing the new devices using your new .inf file
* restart adb : adb kill-server & adb start-server
Should be working fine then
Click to expand...
Click to collapse
This worked! I want to kiss you!:good::good::good::good::good::good::good:
Im having trouble rooting my kindle fire. I have windows 7 and when i get to the step on opening the device manager and updating the driver for the kindle my computer wont let me because it says that it doesnt support x64. Can somebody help me?!!?
I'm on windows 7 64 bit and I don't have this problem can u right click and open as administrator or something like that.
I was having the same issue make sure it is applied under both the X86 and X64 parts of android_winusb.inf, then it should install but to use it I had to hit f8 at startup to disable driver signature enforcement. Hope this helps
When you added entries to the android_winusb.inf file, did you add the code to both sections?
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
...
Code:
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
...
YES I DID.
I found the rooting thread in the dev area- and I'm trying the step to create the usb file in the .android folder. He says to run "adb update usb" to get it to create- but when I run that- it spits out all the available commands/switches that can be run with adb (like a help file).. Is that the wrong command? I can't seem to get the usb file to create.
edit: nevermind got it- had to install all the android 4.0 stuff- I had unchecked it before and only installed dev tools and usb driver
Hi,
Im new here (just got my kindle today) and I noticed the lack of guides/tutorials on how to:
1. Root the device.
2. Install recovery.
3. Install Google Apps.
- 4. Install CM7.
So here is the guide
DISCLAIMER: I do not accept any responsibility for your device due to the usage of this guide. I also do not accept any reponsibility for your device spontanusly combusting/being bricked/broken or anything else that renders you device useless.
So thats the disclaimer and the introduction out of the way, here comes the guide. If you have any questions feel free to post in this thread.
1. Make sure you are on a latest firmware (I was on 6.2)
2. Download Kindle Fire Utility from the following thread:
http://forum.xda-developers.com/showthread.php?t=1399889
3. Once that has downloaded, extract the zip file.
4. Go into the drivers folder and run install drivers.bat (or something along them lines)
5. Once the drivers have been installed, unplug and replug your device. (If the screen comes up about mounting the SD Card you can press disconnect.)
6. Run the bat file in the main directory.
7. The tool should now popup. Once it has popped up select option 3 (Press 3 and ENTER)
8. Your Kindle will now root itself, once that has finished it is time to install recovery. (You can skip the next section if you don't want to install recovery, can't be bothered on anything to that effect. However, I recomend that you do it because if you break your kindle you can restore to a working version also if you want to try out Ice Cream Sandwich or CM7 then you can do.)
9. Once that has finished, go back to the main menu and press 0 then ENTER. If ADB Rooted at the bottom changes from NO to YES then you can continue if not go back to step 7 or post below.
10. From the main menu select option 5 (Press 5 then ENTER).
11. Now your Kindle will install recovery, this may look confusing as a lot of stuff is going on. Once it is installed your kindle should boot with a yellow triangle and press power to boot recovery. There is two things that could happen here:
(1. It doesn't boot and stays stuck on that screen [I had this problem as well, see troubleshooting below. Number One tip: DONT PANIC!]
2. It boots succesfully).
12. If you have concluded that it boots succesfully, switch off your kindle and reboot it. When you get to the yellow triangle screen hold down the power button until it turns AMBER.
13. The Kindle should now switch off and go into the TWRP recovery. You should now be presented with a LANDSCAPE touch based menu.
14. From this recovery menu you are now going to create a backup of your system as it is now. Touch using your finger the BACKUP button. Then select BACKUP NOW. It should then come up with a progress bar saying Backup system. Once this has completed press the Main Menu button.
15. Now select Reboot. (If you would like to install CM7 or ICS follow the steps in the relevant thread. Mainly copy the update.zip to your SDCARD, Enter Recovery, Goto Install and then install the zip.)
16. Then select System
17. The kindle fire will now boot into the Android operating system.
18. From this point onward you can decide to either stay with root or install google apps. If you are choosing to install google apps carry on with the guide, if not you can stop at this point enjoy your rooted kindle fire.
19. Reboot back into the Kindle Fire's OS.
20. Open up Kindle Fire Utility (If it isnt already open)
21. And then from the main menu select option 6 then option 2.
22. This will now install the google apps (Google Market.etc)
23. Enjoy your new Kindle Fire Experience.
Troubleshooting
HELP! IM STUCK ON THIS STUPID YELLOW TRIANGLE WITH A FIRE SYMBOL IN IT!
First, calm down It is hopefully not the end of the world and hopefully not the end of your device.
1. Check that windows picks up your device.
2. If not, switch it off at the bottom and reboot your PC.
3. Once rebooted, switch the kindle back on.
4. You should now be at the yellow triangle (If not and it boots yipee you are fine)
5. If your kindle is picked up by the PC open up the Kindle Fire Utility and select Option 1 followed by Option 1 again. Your kindle should boot now, if not post below it may be due to the FASTBOOT/RECOVERY MODE device ID not being in the drivers. (Simple Fix)
6. If this doesn't work try the following:
Enter the Kindle Fire Utilities tools folder. Shift + Right Click the folder and select Open Command Window Here.
7. Then type in FASTBOOT DEVICES.
8. If a device shows up then that is correct, if not post below.
9. You now need to go into the fire fire thread and download the following image.
http://forum.xda-developers.com/showthread.php?t=1369405
10. Place the image into the tools folder of the Kindle Fire Utility.
11. In the command prompt window type:
12. fastboot flash bootloader u-boot.bin
13. Your device should now boot, if not post below
Enjoy your Kindle Fire
Regards,
XperiaPlayer
This is exactly what I was looking for. Very detailed instructions- this will be a great help to myself and others. Ive rooted phones, but rooting the Kindle is a little intimating. Thanks.,
Sent from my Kindle Fire using xda premium
thanks for the guide!
i'm having some trouble though. when i attempt to install the drivers, i get the message "can not find the file specified" i get the same error when i try to do pretty much anything with the utility itself. any ideas what might be going on?
I am stuck at the screen with the yellow triangle
I have followed the troubleshooting guide
My device is picked up by windows in that there is a “other devices, kindle with a yellow triangle in the device manage window
I have rebooted my pc
When I open Kindle fire utility the utility simply says waiting for device
I reboot the device back into a yellow triangle and utility says waiting for device
I have edited the drivers adb_usb to include the following line
“0x18D1”
I have downloaded the u-boot file and placed it in the tools folder
When I open the cmd promt and type Fastboot devices no devices are listed
** SOLVED*** Stupidity, I had the drivers for the device in the wrong folder thats why Windows was not recognizing it properly
Fairtrade128 said:
thanks for the guide!
i'm having some trouble though. when i attempt to install the drivers, i get the message "can not find the file specified" i get the same error when i try to do pretty much anything with the utility itself. any ideas what might be going on?
Click to expand...
Click to collapse
getting the same thing... the batch file calls
tools\x86\devcon update drivers\android_winusb.inf "USB\VID_1949&PID_0006&REV_0216"
tools\x86\devcon update drivers\android_winusb.inf "USB\VID_1949&PID_0006&REV_0216&MI_01"
tools\x64\devcon update drivers\android_winusb.inf "USB\VID_1949&PID_0006&REV_0216"
tools\x64\devcon update drivers\android_winusb.inf "USB\VID_1949&PID_0006&REV_0216&MI_01"
Click to expand...
Click to collapse
but the files are not in those locations...
\Kindle Fire Utility\tools\x86\devcon.exe
that's all that's in the x86 and x64 folders. there are no devcon update drivers folders.
what can we do to fix that?
thanks
take a look here...
http://forum.xda-developers.com/showthread.php?t=1399889&page=27
This is what I had to do to get it going.
Newbie question. I have a rooted Fire running 6.2.1. Whats the benefits of using TWRP
hi there again,
thanks for that info...
so i already have a rooted android phone, so i didn't seem to have to do some of those steps.
i had the .android folder already, i did have to add 0x18D1 to that file, i only had that first line.
however, before that, when i went to go manually update the drivers, windows kept saying i had the best driver already for the kindle. (i was trying to update the driver for the Kindle device that was under "Portable Devices", i hope that's right)
i proceeded to the next step and started run.bat and did the root command. it looked to work, but then pressing '0' and refreshing it still says "no" under ADB rooted. tried to root again and same thing, still 0 status.
any suggestions on where i go from here?
thanks
someone please help. i did everything and i'm stuck at the yellow triangle screen. i guess i'm in fastboot?
i did the step where it said to shift+right click the tools folder and open the cmd prompt and type in FASTBOOT DEVICES, and a bunch of text comes up. i'm not sure if its recognizing it or not.
what should it say when i type that in if it recognizes it?
thanks to anyone who helps!
I am stuck at the yellow triangle as well. I can't seem to get the drivers to work once at the triangle. The Kindle shows up as an unknown device
Need help...
I'm stuck on the triangle screen and my computer does not recognize my kindle fire.I got to the step where it says to open the CMD and type FASTBOOT DEVICES. i get a list of commands: and options:
Where do i go from here? is this a good sign that i at least see this info? any help would be greatly appreciated. Thanks.
UPDATE:
I've also dropped the img from the fire fire fire thread and all i get is waiting for device in the CMD
GOT IT TO REBOOT!!!! DON'T KNOW HOW BUT I DID! Maybe just patience...whew
OK, at the yellow triangle (Seems to be a common problem however is very irritating because you think your device is broke ) you should try to install the drivers. If they don't install this is because the correct ID is not in them. I am attaching a copy of the android_winusb.inf with the new ID in them. Copy that file to your driver folder and REPLACE the one that is already there. Now try to install your drivers again and windows should pick up your Fire.
Another way to fix it is to install the drivers then open Kindle Fire Utility. Select Option 0 or 1 then NORMAL BOOT MODE (Normal (4000)). This should boot it.
Looks like I cant attach an .inf file. Replace the contents of android_winusb.inf with the following:
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
;
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
;
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Click to expand...
Click to collapse
Getting extremely frustrated here
After choosing option 3, it goes through and roots and at the end it says root was installed successfully. But it still says No for ADB Rooted. I don't know what else to do here but I'm about to tear my hair out.
Thanks for this! I used a combination of this and the youtube video on page 29 of the Kindle Fire Utility thread (up to the point where the fire showed up when I did adb devices) and it worked perfectly! One thing though....
sengokubattosai said:
After choosing option 3, it goes through and roots and at the end it says root was installed successfully. But it still says No for ADB Rooted. I don't know what else to do here but I'm about to tear my hair out.
Click to expand...
Click to collapse
I was never able to get ADB Rooted to say yes. I just used root checker to make sure it was rooted before installing the recovery. It worked fine for me.
i just checked root checker and yeah, it does say i'm rooted even though ADB Rooted always said no. i guess i can continue with the rest of the guide now.
fyi, here's where you can download root checker
http://forum.xda-developers.com/showthread.php?t=927629
XperiaPlayer said:
Looks like I cant attach an .inf file. Replace the contents of android_winusb.inf with the following:
Click to expand...
Click to collapse
Post it as an .txt file? the user can always rename the file.
Also, replacing the whole contents may cause problems for users that have other devices. Just change the Kindle fire sections.
My of KF is rooted will this work just to put twrp on it
Sent from my Kindle Fire using xda premium
I have the same situation.
I am stucked on the triangle screen. I've tried all the troubleshooting guide and nothing helped me. I am still stucked on the triangles.
I need some help please
Figured out my issue as well. It all stemmed from using this guide:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
This particular guide doesn't install the drivers needed when the kindle is in the recovery mode. It will only show up as "unknown device". Worse is that I couldn't uninstall the driver because Windows didn't know which driver to uninstall.
I tried using the drivers in the drivers folder in Kindle_Fire_Utility_v7 but Windows reported that it was the same driver already installed. What I finally had to do was use a completely separate Windows machine that did not have the Android SDK installed. Start from scratch with the correct drivers and finally the new Windows box recognized the kindle in recovery mode. I sent the reboot command and once the Kindle was booted back to normal I connected it to the machine with the bad drivers. The Kindle now showed up correctly in device manager and I was able to uninstall the drivers and reinstall the correct drivers. Once I did that the Kindle now shows up correctly in both production mode and recovery mode.
I hope that helps someone. To recap, my drivers were bad and as far as I can tell there is no way to uninstall the bad drivers while the kindle has the yellow exclamation point. You have to use a new virgin machine to get the Kindle back up and running.
Anyone that spends any time on these forums can attest that this has been an ongoing problem for quite some time, and as long as I've been here, there hasn't been any concrete solution that users can rally around.
A while back, I bought a used laptop for the purpose of running Linux. Mac doesn't have good support for dual booting and there are certain unavoidable issues when running on a VM - but, I digress. This laptop came with Windows XP, and while I have no real purpose for it, I decided to keep in on there, just in case. Recently, I decided to see how hard it really was to get ADB to connect in Windows. I've found, while it isn't really that difficult, I can see why there are so many people having trouble with it. A lot of the information out there regarding this topic is kind of all over the place and none of it really helps users to understand why they're being instructed to do these things. So when something doesn't work exactly like a tutorial says it should, many people are left wondering what to do next and then go on to try other things they don't understand, while all at the same time accomplishing nothing. I created the SoupKit to try and alleviate some of the problem, and while it has been moderately successful in doing so, there are still many for whom it is out of the question. So...the purpose of this thread is to talk about what I have learned from this process and open a discussion on how to apply what I've learned to coming up with a solution that will work for everyone.
That being said...
I'm using the Kindle Fire Utility's 'install_drivers.bat' as an example because it seems to be the the goto choice for many users and it is a much better solution than installing the entire Android SDK, but there are some caveats...so keep reading.
The very first problem I ran into when trying to get ADB to work in Windows was the unsigned driver issue. There are many tutorials out there for installing unsigned drivers and disabling signature checking for each of the different operating systems but I found that even disabling signature checking alone didn't do much good. In the case of the Kindle Fire Utility, drivers are installed via the Windows Driver Package Installation Wizard (dpinst.exe), so disabling signature checking for the system alone may have no effect. The solution I found from the Microsoft's Dev center library, is to run the driver install package with the "Legacy Mode" (/lm) switch on.
In the KFU's 'install_drivers.bat', there are two lines used to envoke the 'dpinst.exe', one for 32bit and one for 64bit machines:
Code:
::We are 32bit, lets run 32bit installer.
[B]start .\drivers\dpinst32.exe [/B]
) ELSE (
::We are 64bit, lets run 32bit installer.
[B]start .\drivers\dpinst64.exe[/B]
before Legacy Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To enable Legacy Mode and disable signature checking for the dpinst.exe, those lines should be edited like so:
Code:
::We are 32bit, lets run 32bit installer.
[B]start .\drivers\dpinst32.exe /lm[/B]
) ELSE (
::We are 64bit, lets run 32bit installer.
[B]start .\drivers\dpinst64.exe /lm[/B]
after Legacy Mode
Considering the fact that Microsoft doesn't like to update too much, that fix should work across all Windows operating systems. (if not, let me know)
The next problem I ran into was that the KFU's 'install_drivers.bat' didn't create the '.android' folder in the User directory where the 'adb_usb.ini' should go. I'm not quite sure why...I barely know anything about Windows batch scripting, but from what I can tell, this should work:
Code:
if not EXIST %userprofile%\.android\ ( mkdir %userprofile%\.android\ )
copy drivers\kindle\adb_usb.ini %userprofile%\.android\adb_usb.ini
...which is basically saying, "If the '.android' folder doesn't exist in the User directory, create it, then copy the 'adb_usb.ini' file to it." The '%userprofile%', I'm guessing, is a Windows batch global variable that represents the current user's home directory, much like "$HOME" in Linux. Why that didn't work for me or for a lot of users I've seen, I couldn't say, but I was able to create the directory via the command line very easily (apparently you can't create directories in Explorer that start with a "." ). When you open a command prompt in Windows, it should start from the User directory (C:\Documents and Settings\Username) by default. With that being the case, anyone can ensure the directory is created with the following command:
Code:
mkdir .android
Copying the 'adb_usb.ini' to the .android folder is pretty straightforward and can be done via the command line or Windows Explorer.
Now here's where things gets a little tricky...hardware IDs.
Not really tricky, but it is clearly the source of many of the problems users are experiencing. For every ROM, bootloader, and (as of late) recovery build, the hardware IDs that are listed for that build may vary. Why is this important? Because KFU's 'android_winusb.inf' only accommodates a small number of hardware IDs, and depending on your build, you could be left out.
When you plug your device into the USB, something should show up in the Device Manager. You can check the hardware ID listed for your device in the state that it's in by looking at the device's properties in the Device manager.
From there (speaking from a Windows XP perspective) you should be able to click on the details tab and select "Hardware Ids" from the drop-down menu.
In the 'android_winusb.inf' that comes with the KFU, there are hardware ID's already listed...
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
...
...
...but you'll need to add the hardware ID for whatever your device is reporting in the particular state that it's in. So using the image posted earlier as an example, you would have to add the following:
Code:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0216&MI_01
A couple of things to note when doing this:
If you're using a custom ROM, chances are it can be in one of three states; Android (ADB) debugging, UMS & MTP. Do not add the hardware ID for MTP or UMS (UMS is when the stock Kindle Fire shows the black screen with a USB cable and the "disconnect" button). Doing so will most likely break your ability to mount your sdcard to USB.
If you've already installed the drivers before editing the 'android_winusb.inf' to accommodate the new hardware IDs, you may need to manually uninstall the drivers and remove the 'android_winusb' folder from yourWINDOWS directory and reboot. The exact location of this folder may vary between different versions of Windows, but I couldn't say for sure. I can, however, explain where it is in Windows XP and hopefully you can find it on your own OS and reply to this post if the location is different.
In the WINDOWS directory under "system32', I found a hidden folder called 'DRVSTORE' (you may have to enable showing of hidden folders). In that folder, you should see something similar to the following (assuming you have already run the 'install_drivers.bat'):
Just delete that folder, reboot, edit the 'android_winusb.inf' that comes with KFU and run the 'install_drivers.bat' again.
With this information, anyone should be able to get ADB working in Windows with little or no problem. Obviously, each Windows version is different, so if you see something that is different in your OS, please reply to this post so I can edit it accordingly.
P.S. With that being said, I decided to gather a bunch of the most popular ROM's and recovery's hardware IDs and created a more comprehensive list that should work in 90% of all situations (if you have a hardware ID that is different, post it so we can add it to the list):
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_00
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_00
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0216&MI_01
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_00
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_00
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0216&MI_01
I hope this helps people to figure out what's going on and how to get ADB working properly. If anyone has any questions or has something to add PLEASE let us know so I can edit this post accordingly. Also, if you have found this informative, or if it helps you in figuring out how to get things working, please consider hitting the thanks button. Your appreciation is MUCH appreciated. Thank you.
Credit goes to kinfauns for spotting this problem ages ago. I'm surprised it is so constantly overlooked.
Wow, I actually took the time and read all of that! Thank you, I personally didn't need it, (thank god) but I'm sure many newcomers will find this very useful.
Fantastic job Soupmagnet as always. Windows xp is by far the hardest out of all the windows variants to get adb going properly. You have touched on some very good points here especially when it comes to the hardware id changes per system and or state. Most the time I can fiddle around enough to get xp to accept an unsigned install but usually that is not without the extra bloat of jdk and sdk. From there is still a series of twists to get the proper effect, then when you upgrade your kindle to a different os once again you revisit the nightmare. Thank you for putting this together because even though xp is an aging os people will continue to use it because they have no other option. With each and every Android advancement for the Kindle Fire I have amassed a long list of changes to the win_usb.inf which may not all be perfect but it functions, I would be happy to see that you get my copy in case there are some differences to be added to your list. Thank you again for your hard work and effort.
KFU still doesn't pick up my device (waiting on device)
justin111 said:
KFU still doesn't pick up my device (waiting on device)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2182450
I believe your device IDs need correction. At least for my device to work I had to make the following changes to my android_winusb.inf:
yours :
Code:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_00
mine :
Code:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Note the difference? Mine follows the same structure as the rest of the file, which never has the &MI_XX with the SingleAdbInterface line, and also does not ever have &REV_XXXX anywhere. After doing this, my device is not only properly recognized by device manager (which your mod allowed) it is also working with ADB (which your mod did not allow, as it would show "offline" - so at least on my XP machine, your changes did not actually get the driver installed properly. But, thanks for the guide, it helped me get this working, as I just got this KF for doing some PC work for my dad...
I copied the IDs as I saw them in the ROMs I tested. As I said before, different builds can have different IDs, so I appreciate you bringing a new one to my attention so it can be added to the list. Thank you.
So some comments:
In Win7 64bit home premium, when I first ran KFU 9.6 back in August some time, I didn't have much trouble installing the driver.
I first let Windows install the correct driver for the original, unmodded kindle. I then proceeded to either roll back the driver or uninstall the driver. At this point, I ran the drivers installer from KFU without any problem, and it correctly installed them, as far as I can remember.
I also have (for as long as I can remember) had the .android folder in the place it is designated. I obviously have it there now, and I didn't have to do any fancy stuff.
Now as far as the DRVSTORE goes, I found in in the same place you had it; It only had the folders included in the picture.
Thanks for your list of Device IDs. I will continue to see if mine match up, and update as necessary. Maybe put a list of what ROMs these came from?
So I am going to run KFU clean with everything that you have here. I am going to delete the drv folder, but should I also go ahead and delete .android folder?
This definitely needs to be stickied! :good:
Try to search your computer for 'android_winusb.inf' hidden somewhere in the WINDOWS directory and let me know if you find anything.
[Edit:] Oh, and there's no reason to delete the '.android' folder
soupmagnet said:
Try to search your computer for 'android_winusb.inf' hidden somewhere in the WINDOWS directory and let me know if you find anything.
[Edit:] Oh, and there's no reason to delete the '.android' folder
Click to expand...
Click to collapse
here is what pops up.
Apparently the folder you need to delete is in DriverStore instead of DRVSTORE.
[Edit:] I should add, that you don't delete DRVSTORE or DriverStore, only the folder that contains 'android_winusb.inf'.
soupmagnet said:
Apparently the folder you need to delete is in DriverStore instead of DRVSTORE.
[Edit:] I should add, that you don't delete DRVSTORE or DriverStore, only the folder that contains 'android_winusb.inf'.
Click to expand...
Click to collapse
Here's where it is located for me. Is there a way to delete a folder from cmd? When I select delete (with administrator priviledges) it still says that I can't perform the action because I need administrator priviledges. Do you know a way around this? Obviously I have the administrator priviledges.
--edit--
Sorry. I guess I didn't include the pic. Here you go!
Was stuck in recovery for ages until I found this thread, thanks! My device mgr H/W IDs were "USB\VID_1949&PID_0008&MI_00" and "USB\VID_1949&PID_0008&REV_0216&MI_00". Finally got the driver to install by adding these three lines to the ini file. Wouldn't work with just the two lines for me.
;Kindle Fire HD 8.9
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0008
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0008&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0008&REV_0216&MI_00
Kindle Fire otter device shows as USB\VID_1949&PID_0005 and can't get drivers to work
I know this is an old thread, but just got around to wanting to reset my Kindle back to factory default and just use it as a reader, KitKat just runs too slow on it. Main problem is getting the drives installed and the device recognized. I've been all over the xda forum, but just can't get it to work.
Device is rooted with N2A Kitkat on it, and twrp 2.6.3 (mainly because I couldn't get the drivers to consistently work). I followed the normal factory reset instructions, got the update-kindle-6.3.4_D01E_4120720.bin, but this version of TWRP cannot read the update.zip file, gets the unknown command error. Running Win7 x86 on PC.
Further reading indicated that I need to go back to twrp 2.2.2.1 to get the update.zip recognized. So that is when I pulled the 0.9.9 version of the Kindle Fire Utility, made all the changes you recommend here and tried to install the drivers. Tried all sorts of different methods based on other posts, but still no luck.
The only thing I see as different is that when normal booted and plugged in, my device shows up as USB\VID_1949&PID_0005 instead of one of the standard PID numbers in the winusb file. I used pnputil to delete all of the android drivers except the one for my Samsung S4 phone, rebooted so everything was clean, then went through the driver install again with the new lines added.
USB\VID_1949&PID_0005
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0005
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216
Device shows up as Android Compostie ADB Interface, but no luck connecting to device in File manager or adb.
When I looked at the resulting file under win\system32\driverstore\filerepository, the contents does not include anything for the PID_0005:
[Amazon.NTx86]
Kindle/Recovery ADB Mode | Gen1 = USB_Install, USB\VID_1949&PID_0006&REV_0216&MI_01
Kindle ADB Mode | Gen2 = USB_Install, USB\VID_1949&PID_000A&REV_0216&MI_01
Recovery ADB Mode | Gen2 = USB_Install, USB\VID_18D1&PID_6868&REV_0216&MI_01
N2A ADB Mode / Kindle ADB Mode | HD 7 = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
Kindle ADB Mode | HD 8.9 = USB_Install, USB\VID_1949&PID_0008&REV_0216&MI_01
Kindle Orange Fastboot Mode | Gen1 = USB_Install, USB\VID_1949&PID_0006&REV_0100
Kindle Blue Fastboot Mode | Gen1 = USB_Install, USB\VID_18D1&PID_0100&REV_0100
Kindle Fastboot Mode | Gen2 = USB_Install, USB\VID_1949&PID_000A&REV_0100
Fastboot Mode | HD 7 = USB_Install, USB\VID_1949&PID_0007&REV_0100
Fastboot Mode | HD 8.9 = USB_Install, USB\VID_1949&PID_0008&REV_0100
Recovery ADB Mode | HDs = USB_Install, USB\VID_18D1&PID_D001&REV_0216
Recovery ADB Mode | Gen1 44 = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
If I boot device into TWRP and connect, it installs the driver correctly via the popup, with Recovery ADB Mode | Gen1 44 and device shows as Kindle Fire with Hardware ID PID_004.
Any ideas you have would be greatly appreciated!!!
wnardone said:
I know this is an old thread, but just got around to wanting to reset my Kindle back to factory default and just use it as a reader, KitKat just runs too slow on it. Main problem is getting the drives installed and the device recognized. I've been all over the xda forum, but just can't get it to work.
Device is rooted with N2A Kitkat on it, and twrp 2.6.3 (mainly because I couldn't get the drivers to consistently work). I followed the normal factory reset instructions, got the update-kindle-6.3.4_D01E_4120720.bin, but this version of TWRP cannot read the update.zip file, gets the unknown command error. Running Win7 x86 on PC.
Further reading indicated that I need to go back to twrp 2.2.2.1 to get the update.zip recognized. So that is when I pulled the 0.9.9 version of the Kindle Fire Utility, made all the changes you recommend here and tried to install the drivers. Tried all sorts of different methods based on other posts, but still no luck.
The only thing I see as different is that when normal booted and plugged in, my device shows up as USB\VID_1949&PID_0005 instead of one of the standard PID numbers in the winusb file. I used pnputil to delete all of the android drivers except the one for my Samsung S4 phone, rebooted so everything was clean, then went through the driver install again with the new lines added.
USB\VID_1949&PID_0005
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0005
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216
Device shows up as Android Compostie ADB Interface, but no luck connecting to device in File manager or adb.
When I looked at the resulting file under win\system32\driverstore\filerepository, the contents does not include anything for the PID_0005:
[Amazon.NTx86]
Kindle/Recovery ADB Mode | Gen1 = USB_Install, USB\VID_1949&PID_0006&REV_0216&MI_01
Kindle ADB Mode | Gen2 = USB_Install, USB\VID_1949&PID_000A&REV_0216&MI_01
Recovery ADB Mode | Gen2 = USB_Install, USB\VID_18D1&PID_6868&REV_0216&MI_01
N2A ADB Mode / Kindle ADB Mode | HD 7 = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
Kindle ADB Mode | HD 8.9 = USB_Install, USB\VID_1949&PID_0008&REV_0216&MI_01
Kindle Orange Fastboot Mode | Gen1 = USB_Install, USB\VID_1949&PID_0006&REV_0100
Kindle Blue Fastboot Mode | Gen1 = USB_Install, USB\VID_18D1&PID_0100&REV_0100
Kindle Fastboot Mode | Gen2 = USB_Install, USB\VID_1949&PID_000A&REV_0100
Fastboot Mode | HD 7 = USB_Install, USB\VID_1949&PID_0007&REV_0100
Fastboot Mode | HD 8.9 = USB_Install, USB\VID_1949&PID_0008&REV_0100
Recovery ADB Mode | HDs = USB_Install, USB\VID_18D1&PID_D001&REV_0216
Recovery ADB Mode | Gen1 44 = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
If I boot device into TWRP and connect, it installs the driver correctly via the popup, with Recovery ADB Mode | Gen1 44 and device shows as Kindle Fire with Hardware ID PID_004.
Any ideas you have would be greatly appreciated!!!
Click to expand...
Click to collapse
How To revert to Stock 6.3.4 Rom (2015)
Sent from my XT912 using Tapatalk
Sent from my SM-G900V using XDA Free mobile app
As the title states, MTP and ADB are not working on my Nexus 4. MTP - phone doesn't show up in my computer. adb devices gives a blank list
Here are some things I tried:
I tried reinstalling device drivers
I tried using different USB cables
I plugged a different phone (HTC m7) into my computer (running windows 8.1 Pro), ADB and MTP work with that phone
Plugged my phone into a different computer, nothing works. But ADB and MTP work for the m7.
Neither MTP nor ADB work in recovery mode (TWRP 2.8.5.2). No fastboot, either.
Situation happened since CM11 and remained after clean wipe to C12.1
Phone charges fine, so USB connector (as a whole, at least) isn't borked yet
So.. any ideas?
Try to look at the google USB drivers .INI file. My last encounter with this file, is that there is no definition for the nexus 4 in the .ini file. So you may try to create a new entry for the nexus 4 and then copy the correct values for the PID and VID values from the device manager /nexus 4 or equivalent tab. Right click and go to hardware details or so.
Then update the drivers as normal from the device manager and navigate to the location of the .INI file and choose the adb boot loader interface.
prince93 said:
Try to look at the google USB drivers .INI file. My last encounter with this file, is that there is no definition for the nexus 4 in the .ini file. So you may try to create a new entry for the nexus 4 and then copy the correct values for the PID and VID values from the device manager /nexus 4 or equivalent tab. Right click and go to hardware details or so.
Then update the drivers as normal from the device manager and navigate to the location of the .INI file and choose the adb boot loader interface.
Click to expand...
Click to collapse
OK, i looked at the INF file. Amongst the Google Nexus devices listed, there is no Nexus 4 specifically but there is this
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\[B]VID_18D1&PID_4EE2&MI_01[/B]
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE7
The one in bold seems to match with what I see when I plug in my phone and look at device manager.
Another thing is very strange - only when I switch from MTP to PTP mode, then my Nexus 4 shows up in my computer, and ADB works! But this is still weird and want a proper solution.
c00ller said:
OK, i looked at the INF file. Amongst the Google Nexus devices listed, there is no Nexus 4 specifically but there is this
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\[B]VID_18D1&PID_4EE2&MI_01[/B]
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE7
The one in bold seems to match with what I see when I plug in my phone and look at device manager.
Another thing is very strange - only when I switch from MTP to PTP mode, then my Nexus 4 shows up in my computer, and ADB works! But this is still weird and want a proper solution.
Click to expand...
Click to collapse
Well you can try to add a new entry for nexus 4 (copy and paste from nexus 7 entry for example and replace the hardware I'd values with the ones you see in the device manager). Second make sure you have adb enabled in developer options. Third choose to update the driver in the device manager for your nexus 4 entry (or android phone). Click through choosing manual drivers and so on until you are required to navigate to the .INI file. Once you get there you will have to choose adb boot loader interface and complete the process. From there you should be able to communicate with your device over adb.
So, after a bunch of Googling and trying other things, this is the solution that worked for me: http://forum.xda-developers.com/showpost.php?p=41712600&postcount=11
I also had ClockworkMod Universal ADB driver installed and had to manually uninstall that. When Google asked for new drivers, I pointed it to the ones I downloaded from Google. Hope this might help others in the future...