Problems with ADB after official 1.04 update?

[Guest 5c00ter]

The Windows drivers in my bundle have the following:

Which seems to match? How strange... weird it doesn't show up to Windows at all when it's clearly appearing in Linux? :P

P

Attached lsusb output.

Extracts below:

Bus 002 Device 014: ID 0955:7100 NVidia Corp. 

Device Descriptor:

  bLength				18

  bDescriptorType		 1

  bcdUSB			   2.00

  bDeviceClass			0 (Defined at Interface level)

  bDeviceSubClass		 0 

  bDeviceProtocol		 0 

  bMaxPacketSize0		64

  idVendor		   0x0955 NVidia Corp.

  idProduct		  0x7100 

  bcdDevice		   99.99

  iManufacturer		   1 NVIDIA

  iProduct				2 NVIDIA Harmony

  iSerial				 3 17141187405fd3d7

  bNumConfigurations	  1

lsusb

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 005 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 002 Device 014: ID 0955:7100 NVidia Corp. 

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 05a9:2640 OmniVision Technologies, Inc. OV2640 Webcam

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Shall I try again, going back to 1.04?

lsusb_output_with_102_image.txt

Edited November 25, 2010 by 5c00ter

[Guest 5c00ter]

Just to clarify, nothing appearing under 'Android Phone' category in Device Manager?

P

Nothing relating to the bridge interface. Only the Composite ADB interface

Edited November 25, 2010 by 5c00ter

[Guest Paul]

Er what? The Composite ADB interface is the ADB device? :P

P

[Guest terdbin]

Er what? The Composite ADB interface is the ADB device? :P

P

Yes I had this in windows, however the install batch file still failed.

The fact that it fails in Linux, should mean it's driver independent?

[Guest Paul]

There is no driver in linux per se, it uses the Vendor ID, which is showing up correctly.

I assume if you do 'adb-linux devices' in Linux nothing shows?

P

[Guest terdbin]

There is no driver in linux per se, it uses the Vendor ID, which is showing up correctly.

I assume if you do 'adb-linux devices' in Linux nothing shows?

P

is that the exact command? as i get not command found

[Guest 5c00ter]

Does this give any clues?

./adb-linux devices


List of devices attached 

????????????	no permissions

I've now re-installed the 1.04 image. I'll try again with the r2 custom rom.

[Guest Paul]

Yes it does!

Try running it as root!

P

[Guest simon.n.jonez]

does this have anything to do with why i cant get adb working,or any ideas what it is

[Guest Pyr0x64]

does this have anything to do with why i cant get adb working,or any ideas what it is

yes, that is what you need to install the new driver for

[Guest 5c00ter]

Yes it does!

Try running it as root!

P

I'm afraid, it's exactly the same result with sudo.

Does it work under your linux system? if so, what are you running / kernel version? any dependencies required for adb-linux?

[Guest simon.n.jonez]

yes, that is what you need to install the new driver for

i cant get any driver to install for it

[Guest gadget_tech]

DELETED.

Edited October 21, 2017 by gadget_tech
DELETED.

[Guest Pyr0x64]

i cant get any driver to install for it

are you using the ones from the "r1-tegrausbdrivers-modaco.zip" file included with the r2 update?

i simply extracted them to a folder on the desktop.

right clicked on the device > update driver software > browse my computer... showed it the usb_driver folder, ignored the warning about signed drivers and told it to install anyway and it was done

[Guest terdbin]

I couldnt find the following "Android Debug Bridge Interface" to start with until I performed the follow:

I connect the Advent Vega to a Windows PC not in debug mode and then once connected select debug mode on the Advent Vega.

The found hardware box appeared and displayed the following 'Nvidia Harmony'

I selected the driver supplied within the 'r2 custom rom' and it started installing and the name changed to "Android Debug Bridge Interface"

Then installed the new ROM as per forum listing.

Hope this helps, let me know?

Were you on version 1.04?

[Guest gadget_tech]

terdbin said:

DELETED.

Edited October 21, 2017 by gadget_tech
DELETED.

[Guest StarmanUK]

are you using the ones from the "r1-tegrausbdrivers-modaco.zip" file included with the r2 update?

i simply extracted them to a folder on the desktop.

right clicked on the device > update driver software > browse my computer... showed it the usb_driver folder, ignored the warning about signed drivers and told it to install anyway and it was done

I don't even have the ADB device listed under Win7 X64 with USB Debugging enabled :|

[Guest terdbin]

Yes upgraded before hand, taken from myadventvega.co.uk

Windows7?

I did the same as you, but it shows up in device mgr in android group as a conposite device... confused

[Guest Pyr0x64]

I don't even have the ADB device listed under Win7 X64 with USB Debugging enabled :|

it may be called a nvidia harmony, or an android composite device if you don't have the driver installed

either under other devices like simon's post, or something in the USB section?

is there anything with an exclamation mark next to it?

Edited November 25, 2010 by Pyr0x64

[Guest ramkiller]

I managed to get this to work by using a windows XP VM

Windows 7 64x was a no go

[Guest captainsensible]

Windows 7 x86 worked for me... x64 also just would not work

[Guest debs626]

Just got this to work for me, I re downloaded the r2 again. I may have had a corrupt file or something the first time round. Worth a try :P

Edit, just found the bbc iplayer flash problem agian :D gggrrrrrrrrrr

Edited November 25, 2010 by debs626

[Guest terdbin]

ok, found the problem, i think.

the steps above (switch on usb debugging while connecting) should find a new device called nvidia harmony - install the custom driver for this, shoudl result in an android group in the devf mgr.

the install-windows.bat script is wrong... it contains linux formatted commands. edit it and find './' and replace it with one space ' '

save and run new bat, worked for me!

[Guest StarmanUK]

it may be called a nvidia harmony, or an android composite device if you don't have the driver installed

either under other devices like simon's post, or something in the USB section?

is there anything with an exclamation mark next to it?

Ok - I located a USB Mass Storage Device on a Win7 32bit machine - under bus reported device description it states NVidia Harmony but when I try the Have Disc approach it states that android_winusb.inf is not a suitable driver.

Edited November 25, 2010 by StarmanUK

[Guest 5c00ter]

Just got this to work for me, I re downloaded the r2 again. I may have had a corrupt file or something the first time round. Worth a try :P

Edit, just found the bbc iplayer flash problem agian :D gggrrrrrrrrrr

Yep me too. I was very happy after the battle getting 1.04 + r2 installed. I tried the manual "hack" provided by Paul, got then got an error, insufficient storage.

Edited November 25, 2010 by 5c00ter