Related
I thought i'd do this for all those (like me) who had issues installing the Adb driver on their system, causing them to have issues using the UnrEVOked progam to root their phones. These steps worked for me, if they are not strictly correct ill edit this post when someone corrects me, but, like I said, they worked for me after 2 weeks of trying!
Once you have booted into your HBOOT screen your system will try to install the Android 1.0 driver [Image 1] . This is the Adb Driver. If, like me, you have followed all the instructions elsewhere, downloading the SDK and installing that driver does not always work.
Right click on the Android 1.0 and go to Properties then Details
In the Drop Down list select Hardware Ids [Image 2]
you will see something along the lines of:
USB\VID_0bb4&Pid_0c94&Rev_0100
USB\VID_0bb4&Pid_0c94
Click to expand...
Click to collapse
Download the file attached below adb_driver_htc.zip
Unzip and open the file called android_winusb.inf
You are looking for any lines that say
; HTC Desire
Click to expand...
Click to collapse
The file is split into sections for various drivers.
The sections you need are:
[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
; HTC Desire
%CompositeAdbInterface% = USB_Install, USB\VID_0bb4&Pid_0c94
;
;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
Click to expand...
Click to collapse
and
[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
; HTC Desire
%CompositeAdbInterface% = USB_Install, USB\VID_0bb4&Pid_0c94
;
;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
Click to expand...
Click to collapse
Change the lines
; HTC Desire
%CompositeAdbInterface% = USB_Install, USB\VID_0bb4&Pid_0c94
so that the USB\VID_0bb4&Pid_0c94 part of the line matches the Hardware Ids part that we saw in [ Image 2 ]
Now.. I put this at the end of the file just for completeness. I'm not 100% sure if it is needed or not.
; HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0bb4&Pid_0c94&Rev_0100
%CompositeAdbInterface% = USB_Install, USB\VID_0bb4&Pid_0c94
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&Pid_0c94
Click to expand...
Click to collapse
Once you have done this you can now install the working driver.
Right Click again on the Android 1.0 Driver and click Update Driver...
Browse to the directory that you unzipped the drivers too, which also contains your edited .inf file. Device manager should now recognize your driver file and install it.
The Android 1.0 should now change to be Android Composite ADB Interface
If you see this...then it worked! [ Image 4 ]
The Attached zip file is my Edited file that works for me. so please change to suit your Hardware Ids.
Any questions let me know. I'll help where I can
DUDE UR MY GOD ! ... IT WORKED FOR ME ! TY ! I am rooting my legend for first time and i got stuck u c..was scared.ty
dhanu007 said:
DUDE UR MY GOD ! ... IT WORKED FOR ME ! TY ! I am rooting my legend for first time and i got stuck u c..was scared.ty
Click to expand...
Click to collapse
I couldn't agree more! YOU ARE A GOD SEND!!!
You are most welcome!
Very helpful! Thanks!
Wow. I have just learned so much about Hardware ID's and Drivers. This info is priceless. Thank you Thank you Thank you. I owe you a beer.
Sorry I'm coming so late after this has been posted for a while but in taking 4 days to find this I keep getting a message saying that windows encountered an error while trying to install driver. Can someone please help with this? I'm trying to do this on an evo.
This stuff need to be placed in desire index thread. Marvelous job
Where in the world is the Thankyou button. Can't find it. Must be blind. Awesome job dude.
really a very good guide explained beautifully
Thank you very very much !!! I've come across dozens of different tutorials, tips and hack but not success so far with installing adb with my desire, until I put my hands on yours tutorial. It worked after first attempt and now I can connect with adb.
From my side I can add that there is no need to go to HBOOT. In my case, xp was discovering Desire, with debbuging turned on, as Android Phone, with unknown drivers of course, I've just check Hardware ID (for this "unknown" device) and modified android_winusb.inf like you said so and it finally accepted the sh.... inf file
Thank you once more !!!
THANK YOU now off with my un-rooted Eris to get my Thunderbolt! Then the rooting begins with a MUCH faster phone!
will this work on incredible???
I was able to do this for mytouch 4g but when i try to adb shell, the device is not found.
Any help would be most appreciated....
pjw111
Did you use proper PID?
Works on HTC Desire. Thanks
Unfortunately, adb still says that there are no devices attached :-(
Yes; It Worked Fine for HTC Desire, Thanks coriron
ADB worked Also after reboot.
Thank you a million for this sir!
Just saved my life!!!
thx u very much
its great
Nice thread, but doesnt belong in the Dev section.
Hi All, found that SDE menu is already in our firmware. It can be enabled very easily and it's quite safe. A big Thanks! to Calj and Tchoubidou for beta-testing it for me!
Disclaimer: I'm not responsible if you blow your device with this, I'm only using existing Archos commands but this is not an official Archos release. Use at your own risks.
Here is the method:
1) Root your device with Paul's root here. I didn't test it without root, but I'm 99% sure it won't work without root.
2) Unzip the content of the attached zip file to a directory
3) Launch the script enable_sde
4) Remove Paul's root with:
Code:
adb shell rm /data/local.prop
You shouldn't keep Paul's root on your tablet, it messes sound and device sleep.
Reboot into recovery mode, you should have the SDE menu now, you can flash your own kernel+initrd the same way it was done on previous generation.
One trick: the initramfs should be still named initramfs.cpio.gz, but it should be compressed with lzma with current kernel.
*FAQ*
Q: How can I boot straight to SDE instead of going through the recovery boot menu ?
A: There is two ways:
- *edit* Tested and working !
In SDE menu: boot in recovery, select "recovery system" then "Developer Edition Menu", then choose "remove android kernel". You will loose the dual boot menu and the possibility to boot stock firmware (you can reflash it afterwards though, re-enabling the menu at the same time), but your tablet will boot straight to developer edition.
If someone has tested this method, please report to this thread.
*edit*: I tested it on mine finally, this method works perfectly. It will be my recommended method from now on, reboot_into is nice but I'm not sure you can still get to recovery in case of boot loop.
- Use "reboot_into -s sde" command just after booting sde. It will set a flag that will make next boot go straight to sde. You can modify initrd to do that or use an apk to launch a script at boot.
http://www.jbmm.fr/?p=23701
this afternoon il will be use this method on not root tablet
I have just test and it works
with rooted or not rooted tablet ?
cajl said:
with rooted or not rooted tablet ?
Click to expand...
Click to collapse
It was pre-rooted with Paul's.
More information, I found a little issue: while I was busy working on a proper initrd+kernel to allow root with this method, I noticed that boot menu is missing in recovery.
It means that the only way to boot the sde kernel is to do it from command line with this:
/data/local/tmp/abcbox reboot_into sde.
I'll look into recovery scripts to see if they are completely missing or if we could do something to enable the menu. Booting with reboot_into is not practical for daily use.
I confirm that the sde kernel boots though!
sounds good, will be ordering my 80G9 Turbo soon, archos told me they will be available any day now and as soon as I get it, thanks to this I can get working on getting ubuntu running on the G9, since there now is an official Ubuntu for ARM with drivers and all for the OMAP
Impossible to use with no rooted tablet
It ok with just use Paul Root
Sound ik ok after reboot
but how view the SDE ?
letama said:
More information, I found a little issue: while I was busy working on a proper initrd+kernel to allow root with this method, I noticed that boot menu is missing in recovery.
Click to expand...
Click to collapse
In fact, everything is ok!
Talking with Tchoubidou, menu is showing up on his device! I forgot that having my previously hacked init kernel makes the system believe that I don't have any main android kernel and therefore hides boot menu.
cajl, if you want to get rid of my hacked kernel and see the menu, just flash last firmware and menu should appear. You'll loose root but you should have a functional SDE.
I'm uploading soon a rooted build.
Hi,
My adb cant find the 101 G9. I edited the usb ini but still no go.
Any idea on how to fix this? Where do i get the approp. usb # from?
Regards, Ingo
use this
;
; 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
;
;Archos Gen8
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
;
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
;
;Arnova 7
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_140E
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_140E&MI_01
;
;Arnova 7c G2
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_143d
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_143d&MI_01
;
;Arnova 7c
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1433
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1433&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
[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
;
;Archos Gen8
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
;
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
;
;Arnova 7
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_140E
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_140E&MI_01
;
;Arnova 7c G2
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_143d
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_143d&MI_01
;
;Arnova 7c
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1433
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1433&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"
"
What do i do with this? Save as .inf file ,copy it in the usb driver dir and run it?
---------- Post added at 11:52 AM ---------- Previous post was at 11:47 AM ----------
What do i do with this? Save as .inf file ,copy it in the usb driver dir and run it?
Also i have set the archos to debug mode but i still can access the nand and my sd card. Is this ok?
IngoPan said:
What do i do with this? Save as .inf file ,copy it in the usb driver dir and run it?
---------- Post added at 11:52 AM ---------- Previous post was at 11:47 AM ----------
What do i do with this? Save as .inf file ,copy it in the usb driver dir and run it?
Also i have set the archos to debug mode but i still can access the nand and my sd card. Is this ok?
Click to expand...
Click to collapse
Yes, replace existing .inf in driver dir, then on question mark device try to use the driver in the directory. I don't have windows so I can't help on the exact naming, but you need to point explicitly the driver directory, not let windows choose the driver.
And yes, nand and sd are still accessible in development mode. Development just add another usb endpoint on top of existing ones.
letama said:
Yes, replace existing .inf in driver dir, then on question mark device try to use the driver in the directory. I don't have windows so I can't help on the exact naming, but you need to point explicitly the driver directory, not let windows choose the driver.
And yes, nand and sd are still accessible in development mode. Development just add another usb endpoint on top of existing ones.
Click to expand...
Click to collapse
Its with the G8, nothing is working ;( I just noticed i just see "ADB" in the device Manager. But it has this 0x790 adress.
I pointed to the dir:C:\Program Files\Android\android-sdk\extras\google\usb_driver, before i edited android_winusb.inf wih the new Information. No Go.
Any clue?
---------- Post added at 02:23 PM ---------- Previous post was at 01:50 PM ----------
@EDIT:
WORKING now. I had to change the PID,too. No one told me that:
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1529
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1529&MI_01
All fine now.
I seem to get stuck at the step where I run the scrip to enable the SDE menu in recovery. I copied to script vs sd card and I get "device not found" on my G9. Where did you place you script and how did you run it. I'm using adb in OSX. Thnaks.
Does anyone know if I can use hacked wifi tether on my evo4g on a stock Archos 101 G9? Or does my phone AND my tablet both need to be rooted to get to wifi working on the tablet?
AnimatorJoe said:
I seem to get stuck at the step where I run the scrip to enable the SDE menu in recovery. I copied to script vs sd card and I get "device not found" on my G9. Where did you place you script and how did you run it. I'm using adb in OSX. Thnaks.
Click to expand...
Click to collapse
You must launch the script from your mac, not from the device.
If adb is in path, I presume you should run the .sh from shell/console (don't know the exact name on mac). If you can't run it after unzip, try chmod 755 enable_sde.sh first.
I don't have mac so I can't help much more, sorry...
bsg411 said:
Does anyone know if I can use hacked wifi tether on my evo4g on a stock Archos 101 G9? Or does my phone AND my tablet both need to be rooted to get to wifi working on the tablet?
Click to expand...
Click to collapse
EVO 4G should be producing an infrastructure WiFi signal, so the Archos does not need to be rooted or have anything done to it to see your WiFi.
I guess I upgraded to the latest firmware too soon huh ?
Or will this work even if I have the latest firmware on my 80 G9 ?
jadephyre said:
I guess I upgraded to the latest firmware too soon huh ?
Or will this work even if I have the latest firmware on my 80 G9 ?
Click to expand...
Click to collapse
Well, it should work, except if Archos fixed the exploit to get the temp root.
letama said:
Well, it should work, except if Archos fixed the exploit to get the temp root.
Click to expand...
Click to collapse
Just did it last night *after* upgrading to 3.2.78
I can't connect to my Google Glass from my Windows 8 computer. I've tried following the advice at http://stackoverflow.com/questions/...-find-omap4430-driver-not-installed-cant-find and at http://glassdev.blogspot.com/2013/0...howComment=1375418433744#c1348522596744536261 but it doesn't work for me. When I modify the android_winusb.ini file, I can no longer use the file. (If I right-click the file and select Install, Windows gives me an error message saying that the file's been tampered with.) What to try next?
Thanks.
What does the error look like?
Sent from my Nexus 4 using XDA Premium 4 mobile app
I fixed the problem
andyabc said:
What does the error look like?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A while ago someone helped me fix the problem by sending me a driver file. I don't know why I got into trouble the other way I was doing it, but anyway, now it's fixed.
Add the following to android.winusb.inf in the Google Driver folder (../sdk/extras/google/usb_driver/)
Under [Google.NTx86]
Code:
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_00
Under [Google.NTamd64]
Code:
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_00
Manually select that driver file when updating driver will windows will allow you to use that driver for your Glass.
for some reason my kindle fire wont connect to any pc, i tried 4 different pc's im using cm10.1.0.2 what's funny is i had no problem connect with the stock rom and cm10 at first i remove cm10 off cause i was running slow so i uninstalled it and reinstalled it which fix my slow down problem but now have this problem. also the other way i can connect it is through twrp. do anyone know have to fix this problem ? also i have all the drivers instilled too and when i connect it the pc's makes the sound that somethings connect if anyone can help i really appreciate it.
mj360 said:
for some reason my kindle fire wont connect to any pc, i tried 4 different pc's im using cm10.1.0.2 what's funny is i had no problem connect with the stock rom and cm10 at first i remove cm10 off cause i was running slow so i uninstalled it and reinstalled it which fix my slow down problem but now have this problem. also the other way i can connect it is through twrp. do anyone know have to fix this problem ? also i have all the drivers instilled too and when i connect it the pc's makes the sound that somethings connect if anyone can help i really appreciate it.
Click to expand...
Click to collapse
Open android_winusb.ini in KFU`s drivers kindle folder and under [Google.NTx86] ;Kindle Fire and [Google.NTamd64] ;Kindle Fire and add
Code:
%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
%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
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Anything that`s in my list that is not in yours. Then save the file and re-install the driver packaged with KFU then plug your kindle in. It should be detected then.
I've been trying to use LG Flashtool to restore my phone back to stock but it just gets stuck on the "MODEM" step at 10%.
My phone also boots straight to Firmware Update when turned on too rather than just staying at the LG logo if that helps.
Any help is appreciated thanks.
durnal said:
I've been trying to use LG Flashtool to restore my phone back to stock but it just gets stuck on the "MODEM" step at 10%.
My phone also boots straight to Firmware Update when turned on too rather than just staying at the LG logo if that helps.
Any help is appreciated thanks.
Click to expand...
Click to collapse
I am stuck to. Did you find a solution?
memofoda111 said:
i'm with you
Click to expand...
Click to collapse
Look for Google universal USB. There you can specify your devide ID's and so the Smartphone would be recognisiced by LG Mobile Support Tool
herbertkern
Mine stucks on the analizing step %60 and says your phone isnt connected. My phone isnt bricked but i cant go back to stock and i couldnt find the solution. I have gone to stock for several times easily with kdz method but this time lg tool stuck
Theozer1 said:
Mine stucks on the analizing step %60 and says your phone isnt connected. My phone isnt bricked but i cant go back to stock and i couldnt find the solution. I have gone to stock for several times easily with kdz method but this time lg tool stuck
Click to expand...
Click to collapse
I had the same Problem. The phone isn't connected in a form where it is found by the program, even you can save files on the phone. With Google universal usb I could it connect, so that the phone was found by mobile Support tool and flashed the kdz-file without Problems.
herbertkern
herbertkern said:
I had the same Problem. The phone isn't connected in a form where it is found by the program, even you can save files on the phone. With Google universal usb I could it connect, so that the phone was found by mobile Support tool and flashed the kdz-file without Problems.
herbertkern
Click to expand...
Click to collapse
What is google universal usb?
Theozer1 said:
What is google universal usb?
Click to expand...
Click to collapse
just look here:
http://developer.android.com/sdk/win-usb.html
herbertkern said:
just look here:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Where can i download it from and how can i download it? I couldnt understand. Thank you for your help.
Theozer1 said:
Where can i download it from and how can i download it? I couldnt understand. Thank you for your help.
Click to expand...
Click to collapse
Sprichst du deutsch oder english als Muttersprache?
In German I can it explain better. I sent you above the link from where you can download the Driver. Whats the Problem???
herbertkern
herbertkern said:
Sprichst du deutsch oder english als Muttersprache?
In German I can it explain better. I sent you above the link from where you can download the Driver. Whats the Problem???
herbertkern
Click to expand...
Click to collapse
Sorry, my fault. I find the download link now and i am downloading it. And i can just tell my name in deustch Thank you !
herbertkern said:
Sprichst du deutsch oder english als Muttersprache?
In German I can it explain better. I sent you above the link from where you can download the Driver. Whats the Problem???
herbertkern
Click to expand...
Click to collapse
I have one more question. I downloaded a zip file called latest usb driver but i dont know what to do with it
Theozer1 said:
I have one more question. I downloaded a zip file called latest usb driver but i dont know what to do with it
Click to expand...
Click to collapse
What do you think about also reading the explaining text on the site, where you downloaded the Driver???
I speak german, but I did understand what to do. Ist really well explained.
You have to extract the zip file, there you'll find a *.inf -file. Look in the device Manager for unknown device (of Course, after having connected you LG!!). Then look at Details for Hardware ID's and edit the inf file and write the id's found on device Manager.
It's necessary, that your PC recongnize the LG without a yellow triangle. When this ist done, you can Flash the downloaded kdz-file.
But on the site which I sent you the link it is exactlier explained in english than I can do.
herbertkern
It worked ! It sees my device now thx
Theozer1 said:
Can i download the driver using the sdk manager ? my english is worse than you. I am turkish
%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
;Google Nexus S
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E21
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E23
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E24&MI_01
;Google Nexus 7
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E42&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
;Google Nexus Q
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_2C10
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_2C11
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%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
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
;Project Tango (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4D00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D02&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D04&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D06&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D07
[Google.NTamd64]
;Google Nexus One
%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
;Google Nexus S
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E21
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E23
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E24&MI_01
;Google Nexus 7
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E42&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
;Google Nexus Q
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_2C10
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_2C11
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%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
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
;Project Tango (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4D00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D02&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D04&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D06&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4D07
[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 Device"
these are writing in inf file
Click to expand...
Click to collapse
Ok, that another Chose. I thougt, you where english-speaking. I think, you have yet downloaded the Driver, you wrote this before, or not? When not, then just rightclick there where is written "download". Then you can strore the file where you want to do.
herbert
herbertkern said:
What do you think about also reading the explaining text on the site, where you downloaded the Driver???
I speak german, but I did understand what to do. Ist really well explained.
You have to extract the zip file, there you'll find a *.inf -file. Look in the device Manager for unknown device (of Course, after having connected you LG!!). Then look at Details for Hardware ID's and edit the inf file and write the id's found on device Manager.
It's necessary, that your PC recongnize the LG without a yellow triangle. When this ist done, you can Flash the downloaded kdz-file.
But on the site which I sent you the link it is exactlier explained in english than I can do.
herbertkern
Click to expand...
Click to collapse
it Works. thank you so much for your help. you are amazing ! I am on stock now. again, thank you sooooo much. You tried to explain everything against my worst english You spent your time for me so again thank you
Theozer1 said:
it Works. thank you so much for your help. you are amazing ! I am on stock now. again, thank you sooooo much. You tried to explain everything against my worst english You spent your time for me so again thank you
Click to expand...
Click to collapse
Well, very good that you have success. I know the euphorism, I had the same Feeling
herbert