Jump to content

Anyone got good ADB Drivers for G9 80?


Guest MrChips

Recommended Posts

Guest MrChips

I have tried to install the ADB drivers for my new Archos G9 80 using the instructions provided over at Archos. No Joy. Windows still doesn't want to recognize the ADB drivers for my tablet.

Does anyone have a working set of ADB drivers for the G9 80 tablet out there? If so, can you post them, or at least post the correct driver strings to be added to the android_winusb.inf so that ADB will recognize the device?

My most sincere thanks ahead of time for any help you can provide on this! I'm desperate! sad.gif

Rich

Edited by MrChips
Link to comment
Share on other sites

Guest cajl-jbmm

i 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"

"

Link to comment
Share on other sites

Guest MrChips

Thank you cajl-jbmm!

The driver info you gave worked perfectly. My Archos ADB connection is now up and running.

For those that are curious, here are the critical sections/entries for the G9 Archos tablets:

[Google.NTx86]

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01

[Google.NTamd64]

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01

The key part of this that is missing from the drivers posted on the Archos website is the "&PID_1509" which is the identifier specific to the Gen9 tablets. Their version contains the identifiers 1361, 1400 and 1411 which are for their older tablet generations, not the G9's. That's why it doesn't work. Once you add the lines above, it works!

Hope this helps others who are running into problems getting the ADB drivers connected to the G9s. Thanks again to cajl-jbmm!

Rich

Link to comment
Share on other sites

  • 4 weeks later...
Guest centaurus

Thank you cajl-jbmm!

The driver info you gave worked perfectly. My Archos ADB connection is now up and running.

For those that are curious, here are the critical sections/entries for the G9 Archos tablets:

[Google.NTx86]

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01

[Google.NTamd64]

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01

The key part of this that is missing from the drivers posted on the Archos website is the "&PID_1509" which is the identifier specific to the Gen9 tablets. Their version contains the identifiers 1361, 1400 and 1411 which are for their older tablet generations, not the G9's. That's why it doesn't work. Once you add the lines above, it works!

Hope this helps others who are running into problems getting the ADB drivers connected to the G9s. Thanks again to cajl-jbmm!

Rich

Thank you very much for sharing this!

I've got an ARCHOS 101 G9 and the PID for the 80 G9 did not work of course. But I did some research and found the reported PIDs for this device.

So I want to add, that the official PIDs for the ARCHOS 101 G9 are PID_1528 and PID_1529.

(I believe, while the first number is for the usual USB interface (accessing the file system),

the second one is the right one for the ADB interface. Finally it worked with adding the following lines to the standard Google Android USB Driver (*.inf) file:

[Google.NTx86]

...

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1528

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1528&MI_01

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1529

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1529&MI_01

[Google.NTamd64]

...

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1528

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1528&MI_01

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1529

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1529&MI_01

(I am able to debug on Windows 7 with Eclipse ADT Plugin now. Formerly I was "forced" to do it exclusively with a Mac, where no driver for debugging is required (it works out of the box). Although you usually need a special application for accessing the shared files of Android devices on a Mac...)

Regards!

Edited by centaurus
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

hello!

I had some problem with getting adb driver installed on my archos g9 80.

I've recently upgraded to 3.2.77 from 3.2.69.

On both firmwares, after connecting tablet to pc by usb, i did't see other devices in device manager. I tried it on 3 pc's. After connecting my nexus one, other device appears in dev manager, driver successfully installs, and adb devices sees my phone.

While trying to downgrade, tablet tells me : the firmware update is too old for your hardware versions.(221)

I think it's some kind of anti-root feature?huh.gif

All i want is to get rootninja.gif

Is there any way of forcing the tablet to downgrade?

Edited by sazke
Link to comment
Share on other sites

  • 2 weeks later...
Guest Greg_000

Hello everyone,

I can't install the composite adb interface for my G9 80. After enabling USB debugging on the device, updating the PID to 1509 in the inf (below) and installing the driver, the Android Composite ADB Interface device shows this error:

This device cannot start. (Code 10)

devcon.exe shows this:

ROOT\UNKNOWN\0000: Android Composite ADB Interface

so there must be something bad about the driver (?)

I spent many hours last night trying to fix this, went through numerous posts, but no luck. Has anyone come across this and knows how to fix it? I'm using Win7 x64.

Did you use the USB cable that came with the G9? I guess the cable is fine since the pnp driver (under Portable Devices) got added automatically without any problems.

[Google.NTx86]

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01

[Google.NTamd64]

;Archos Gen9

%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509

%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01

Link to comment
Share on other sites

  • 4 weeks later...
Guest Folkert Sikkema

I do have a similar problem with my Archos 80 G9. ADB cannot see any usb

connected devices. My laptop shows the device and I can access the

filesystem on the Archos. But ADB shows nothing.

What should I do with the listed android_winusb.inf file? If I try to update

the driver for the device, Windows 7 x64 says that there is no updated driver

and won't install anything...

Can you help me out?

Thanks in advance and regards, Folkert

Link to comment
Share on other sites

Guest Folkert Sikkema

I do have a similar problem with my Archos 80 G9. ADB cannot see any usb

connected devices. My laptop shows the device and I can access the

filesystem on the Archos. But ADB shows nothing.

What should I do with the listed android_winusb.inf file? If I try to update

the driver for the device, Windows 7 x64 says that there is no updated driver

and won't install anything...

Can you help me out?

Thanks in advance and regards, Folkert

First read more. And some forumthreads have more pages... Read a

lot of tips as "remove al drivers" and "try another usb port" and in the

end, ADB runs fine... I cannot pinpoint on what exact sequence of actions

helped me out, so I cannot really help anyone out here.

Regards, Folkert

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.