What to do when your USB drivers are wrong (win7/64)....

[Guest tech_fox]

i have tried what you said by running administrator uninstall all 5 usb 0955 drvier

do a reinstall and update composite usb driver to nivida android composite usb the printscreen below shows seems to be correct however adb still refuse to regonise my devices :(

Read my words very carefully. Do not use "NVIDIA android composite device" but use "USB Composite Device". A mistake easily made if you are in a hurry.

[Guest tech_fox]

Whoops arad85 and I are stumbling over each others feet!

However our conclusions are the same.

[Guest bear807]

Try again, but don't do this. You need Composite USB Driver (have a look at my USBDeview below)

i guess this is correct :(

adb still says no devices connected ;)

[Guest arad85]

Whoops arad85 and I are stumbling over each others feet!

What's the going rate for IT consultancy on Christmas Eve? :(

[Guest tech_fox]

What's the going rate for IT consultancy on Christmas Eve? :(

What about Xmas day and Boxing day? However I suspect I won't be allowed near the computer! ;)

[Guest bear807]

i guess i just got to give up on this :(

is hopeless thanks for everyone who help

just simple dunno where went wrong despite i follow all the instrustion

try to fix it for afternoon but still nothing comes up.................

[Guest arad85]

i guess this is correct :(

adb still says no devices connected ;)

I assume drive F: doesn't show up in explorer? What does Device Manager look like now?

Try force updating the Android Composite USB Interface with Pauls driver....

[Guest bear807]

I assume drive F: doesn't show up in explorer? What does Device Manager look like now?

Try force updating the Android Composite USB Interface with Pauls driver....

the hardware manager shows up the usb harmony drive

i try to force update using pauls usb drive and select have disk, do i point to a .inf file?

it updated it but still do not show up in adb

[Guest arad85]

the hardware manager shows up the usb harmony drive

i try to force update using pauls usb drive and select have disk, do i point to a .inf file?

it updated it but still do not show up in adb

When you force update, you select the directory the inf file is in. You did press the "Have Disk..." button didn't you (accessed through the "Let me pick..." option in the picture below. If you entered the directory in the "Browse for..." and then pressed Next on the screen below, it will have the wrong driver.

[Guest bear807]

When you force update, you select the directory the inf file is in. You did press the "Have Disk..." button didn't you (accessed through the "Let me pick..." option in the picture below. If you entered the directory in the "Browse for..." and then pressed Next on the screen below, it will have the wrong driver.

yea i selected pick me than the screen has a have disk option and i select that one and than it will only let me select a .inf file so i choose "android_winusb.inf" and than proceed on

[Guest tech_fox]

i guess this is correct :(

adb still says no devices connected ;)

Something is still not right with your USBDeview readout. Compare it to arad85's readout.

I suggest a complete uninstall again of the drivers associated with the Vega and reinstall very carefully from scratch.

After you have uninstalled and disconnected the Vega, open the device manager, expand the "disk drive" and "Universal Serial Bus controllers" entries and watch as you plug in the Vega (with it powered on and in USB debug mode). Things will happen fast but try to note what happens and report back.

Keep happy. I am sure we are close.

PS Whoops again arad85. I am off to lunch for a while.

Edited December 24, 2010 by tech_fox

[Guest bear807]

Something is still not right with your USBDeview readout. Compare it to arad85's readout.

I suggest a complete uninstall again of the drivers associated with the Vega and reinstall very carefully from scratch.

After you have uninstalled and disconnected the Vega, open the device manager, expand the "disk drive" and "Universal Serial Bus controllers" entries and watch as you plug in the Vega (with it powered on and in USB debug mode). Things will happen fast but try to note what happens and report back.

Keep happy. I am sure we are close.

PS Whoops again arad85. I am off to lunch for a while.

thank you all im going for lunch too :(

i have tried it in disk drive it has nivida tegra 2 usb drive comes up

usb composite device

and android adb composite interfrace hmmmmmm

[Guest tech_fox]

thank you all im going for lunch too :(

i have tried it in disk drive it has nivida tegra 2 usb drive comes up

usb composite device

and android adb composite interfrace hmmmmmm

Please see post 41 in this forum - I think at the top of previous page 2. Do you get those entries as listed there? There location is important e.g. under "Disk drives", "Android Phone" and "Universal Serial Bus controllers".

If so what does USBDeview now show?

[Guest griff_dai]

If I understand your question correctly you intend to update your Vega using the ROM image from the "myadventvega" site. If this is the case you must use the USB driver from that site first to enable that update. I would keep these files in a separate folder from the MODACO files to avoid confusion.

Having done the official ROM update then follow Pauls instructions and use his USB drivers for his update. Note to reach his driver you will have to do two extraction processes as his drivers are a zipped file inside a zipped file!

If you have a normal installation you will be using Pauls drivers to update the "NVIDIA Harmony" entry. If it is slightly abnormal follow arad85's guide in this forum to update "Android Debug Bridge Interface" entry. If you are really unfortunate to have neither entry then see some of my earlier posts in this forum. Also post 580 on page 29 of the MODACO Add on ROM forum might be helpful.

I keep intending to write a comprhensive guide to all these USB and installtion problems but others like arad85 have already started so it would be a duplicated effort.

Ok have unzipped the USB from myadventvega, will follow that route explained ^here^

[Guest Tezza_uk]

Help, I can't get anywhere with my Vega, I can't get past the USB installation, can't see any any device in Device Manager, I installed the USB view program but all it finds is one port with the same vendor ID and and product ID you have stated, this has the drive letter F on it and is the mass storage side of things, I don't get 3 like you stated in your instructions..

I have tried this on 2 PC's one is a desktop with vista 64 and the other is a laptop with vista 32.

EC vers is 1.9

Kernal is 2.6.32.9_P10_V1.09_20110211_DIX

Build is Harmony 2.2 FRF91 20110211.101539

Thanks..

Tezza..

[Guest sugar0]

What if my computer can't view my POV MOBII 10" and won't go in ootloader mode also ? It's seems to be invisible! help! :(

[Guest sugar0]

well now i was able to install the official USB drivers from POV with this guide http://downloads.pointofview-online.com/Dr...instuctions.pdf ... now how can i install the usb drivers from modaco ?? i keep getting this error http://img1.uploadscreenshot.com/images/or...412484-orig.png

PS: in can see the devices i "DEVICE MANAGER" only when in bootloader mode, not when it's ON android

Edited March 9, 2011 by sugar0

[Guest shirecom]

Should have shown up as an Unknown Device then in that case. You could always rescan for hardware changes by selecting your computer and selecting "Scan for hardware changes"

It should show up then...

Mine is not showing the adb debug. It only shows Nvidia tegra device. I have to use the one from the myadventvega site to flash tofinal 1.09

Now I can't get rid of it.

[Guest BillBong]

I'm having problems with the ADB drivers on a Vista/64 system.

I've installed the Advent System/USB drivers as a first step and that works fine. I get as far as installing the unzipped MCR/USB drivers through the "add legacy hardware" option and it goes through the process of installing the drivers across but then I get a message saying the software has installed but there may be a problem and the hardware won't start - "code 10" - with a yellow triangle against the entry on the device manager list. I've tried uninstalling/deleting several times but it always come back to this "code 10" error.

I've got it working OK on a XP machine without any issues so I'm using this to flash the ROM at the moment but I use the Vista PC on a more regular basis so really want to get it working on this. I've seen a lot of issues with Vista/64 installs - is it something that just can't be done?

[Guest montydog]

I want to flash R8-vga-update to my POV Mobii but am having the same issues as BillBong.

Used USBdeview to uninstall suspect drivers but still my POV Mobii does not register when plugged into either a Win7 32 desktop or an XP laptop

when in USB debugging mode.

At least BilllBong can get XP to recognize the device when plugged in.

I have used APX driver to update to the 1.9 firmware release but I am completely stymied in trying to use the ADB composite driver and even in having my PC's recognize the device when plugged - bit of repetition there!

[Guest simonta]

When you say "does not register" what do you mean? Do you mean there is NO device at all?

You know that the POV Mobii USB port is in host mode by default?

[Guest TAZMANUK]

adb-windows.exe is adb. Paul just renamed it as he supports 3 platforms with the one release (windows, linux, mac). In the above example, I've assumed you've renamed adb-windows.exe to adb.exe. I'll explicitly state that now... (am updating the first post to show an alternative way of figuring out which driver is installed as some people don't have the same driver as mine showing up).

HI

I am a newbie tried and followed the usb connections tried the file from advent to update firmware says device not found press enter.

however following this guide ive managed to put paul r8 rom on how do i find out if advent hasnt already updated my vega firmware already hence not updating as it allowed me to put pauls r8 rom on it ok very confused now

[Guest FrownBreaker]

......I have used APX driver to update to the 1.9 firmware release but I am completely stymied in trying to use the ADB composite driver and even in having my PC's recognize the device when plugged - bit of repetition there!

Me too! I've tried on 3 Win7 32 bit machines and the USB mass storage works and I managed to flash the latest stock 1.9 roms. But no luck with ADB. I remember setting up ADB for modding my San Francisco that that worked ok.

What I've found so far

- Using a super speed cable and the NEC USB card gives be a blue screen (on Win7 32 bit) as soon as i turn on USB debugging on the Vega

-I've used the USB tool mentioned here to remove the mass storage driver for the device linked to the Vega (based on the vendor ID details

-USB debugging is ON and the Vega is 100% battery and AC powered

-Vega set to stay on under settings

-USB connected and ADB server started fine but no devices lists with adb devices

-Latest Andriod SDK and JDK (SE) -plus updated ADB drivers from Google (optional item after installing the SDK)

-Several hours of trying, the USB cable works for mass storage and flashing stock in recovery

-I've checked the MD5s of all the files I've downloaded

-I've uninstalled the Tegra drivers (All of them based on Vendor ID) and reinstalled forcing the version recommended here.

-Will try again at work, I got 2 Vega's one for a friend at work so will try again there using XP

-The machines at home are AMD based Asus motherboards with Win7 ultimate patched with all updates.

-Oh I'm on the latest stock ROM 109 reports as such on the About device page of the Advent.

Ready the threads I've tried all the obvious things

-USB works for data

-I've check debugging is on for USB

-Recovery mode works for flashing stock ROM

-Device manager shows "Android Debug Bridge Interface" as working -note is not the ADB composite device. Hardware IDs for this are USB\VID_0955&PID_7100&REV_9999&MI_01 and USB\VID_0955&PID_7100&MI_01

-USBDview reports

0000.0013.0002.003.000.000.000.000.000 USB Mass Storage Device Mass Storage No Yes No No G: 06/04/2011 06:39:17 N/A 0955 7100 99.99 08 06 50 7&1d97c6f5&0 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device USB Mass Storage Device 6.1.7600.16385 USB\VID_0955&PID_7100&MI_00\6&269928c1&4&0000

0000.0013.0002.003.000.000.000.000.000 Android Debug Bridge Interface Vendor Specific No No No No 06/04/2011 07:56:06 N/A 0955 7100 99.99 ff 42 01 WinUSB NVIDIA Boot Recovery WinUsb.sys USB @oem32.inf,%providername%;NVIDIA Corporation Android Debug Bridge Interface USB\VID_0955&PID_7100&MI_01\6&269928c1&4&0001

Port_#0003.Hub_#0006 NVIDIA Tegra 2 USB Device Unknown Yes Yes No No G: 0270308341408417 06/04/2011 06:39:16 06/04/2011 07:58:16 0955 7100 99.99 00 00 00 6&269928c1&4 usbccgp Microsoft USB Generic Parent Driver usbccgp.sys USB @usb.inf,%generic.mfg%;(Standard USB Host Controller) 500 mA USB Composite Device 6.1.7600.16385 USB\VID_0955&PID_7100270308341408417

Notice the firmware Rev shows as 99.99 ?!!

Ready this http://tegradeveloper.nvidia.com/tegra/for...cant-see-device says "Signs that Windows is using the wrong driver: * The Device Manager lists "Android Debug Bridge Interface" instead of "Android Composite ADB Interface" or "Android ADB Interface". * The device is listed under "Universal Serial Bus controllers" rather than under "Android Phone".

So stuck with the common problem of the ADB not working via USB is there a link for how to use the wifi ADB? I assume it just the IP address of the Vega? Not sure how I'd find that on the Vega as the Wifi at work is DHCP and do not have access tot the router to link the Vega's MAC with an allocated IP address.

D:\android-sdk\platform-tools>adb devices

List of devices attached

D:\android-sdk\platform-tools> :D

Edited April 6, 2011 by FrownBreaker

[Guest doireabu]

Guys some help plz

Managed to download the drivers, got the device coming up as composite adb interface.

Problem is when i run the command install-windows.bat i get the following:

Waiting for device... ensure usb debugging is enabled bla bla bla

Any help much appreciated

Brendan

[Guest Stevonator]

Wow absolutely WOW!

You are a magic man :o!

Only different thing I had to your screenshots was that my Android Debug Bridge, before I had updated it was called Nvidia Harmony. But I updated it exactly the way you said to and it works like a charm :D Thank you so much for taking the time to create this tutorial :mellow:

S