81 replies to this topic

[arad85]

There have been so many people who have had problems with this, I thought I'd try and write a how-to to get them right with pictures.

Caveat: this has been done on a system that has already had non working and working USB drivers on, so some of the options may be slightly different.

You will know when you have the wrong drivers installed when you have

• Turned debugging on on the Vega (Settings->Applications->Development->USB Debugging ticked)
  
• You have the device connected via USB
  
• You have downloaded Pauls ROM and unzipped it, opened a command prompt at that directory
  
• added 23/12/10 you have copied adb-windows.exe to adb.exe
  
• You see the following (or something mentioning server started) at the command prompt

We now have to replace a single driver in the system. To do this, you need to bring up the Device Manager. Open Control Panel



select Hardware and Sound to give you



and select Device Manager. Once in Device manager, you should see Universal Serial Bus controllers with a small triangle to the left. Click that to display the list:



The one you want to update the driver for is "Android Debug Bridge". If you see this device or know which one you want to update as you've found it somewhere else, please skip to the line below with the words END OF YOU ONLY NEED TO DO THIS IF YOU CAN'T FIGURE OUT WHICH DEVICE TO UPDATE highlighted. If you can't see this device, or can't figure out which device to update, you will need to follow the instructions that follow.

BEGINNING OF YOU ONLY NEED TO DO THIS IF YOU CAN'T FIGURE OUT WHICH DEVICE TO UPDATE SECTION
Some people don't see this device and can't find which device they need to update. There is a way to figure out which device needs updating (or at l;east this should work). Firstly, you will need a free tool USBDeview available from http://www.nirsoft.n...vices_view.html. It is free and is a standalone program (so doesn't need installing onto your system). Run that, and you are presented with all the USB drivers that are installed in your system. Here is mine with the Vega disconnected (apologies for the size, but I don't have a webhost I can get to display full sized images - the information is readable though).



I have sorted on VendorID (column 12 - just click on the column header). You can see there are 3 USB drivers in the system for this device. The drivers all have the same VendorID and ProductID which means they are for a single device (Nvidia is vendor ID 0955). You can see there is a "Composite USB device" and a "USB mass storage device" and there should be a third. It's name will be different to the one shown in my photo, but it will have the same VendorID and ProductID (columns 12 and 13 in my picture). It is this device you need to update the drivers for. To find it, you will have to search for it in the other collapsed device categories in the Device Manager window. Then update that device instead of the "Android Debug Bridge Interface" below.
END OF YOU ONLY NEED TO DO THIS IF YOU CAN'T FIGURE OUT WHICH DEVICE TO UPDATE SECTION

Select the Android Debug Bridge Interface and right click to give:




Select update driver to give:



and select "Browse my computer for driver software" to give:



The important thing to do now is not let the computer try and find the correct driver, but to pick one yourself. To do this you should have:

• Downloaded Pauls rom with driver
  
• Unzipped (right click, unzip) this to a directory
  
• Entered into the directory to see a usbdriver directory
  
• Entered that directory and unzipped the zip file that is in there.

This will put the USB drivers in the directory: <wherever-you-have-put-the-download>\usbdriver\usb_driver

Clicking on "Let me pick" will bring you to:



Now the important part, you have to tell it where to find the drivers. Click "Have Disk" and browse to the directory: <wherever-you-have-put-the-download>\usbdriver\usb_driver (you can see that my <wherever-you-have-put-the-download> is Z:\vega\modaco\r4-default)



The system should present you with the next screen.



Select the "Android Composite ADB Interface" and click Next.

The system should go away and think for a while and present you with:



Click Clsoe and the device manager should refresh and you should now have Android Phone at the top of the Device Manager



You can check this is working by going back to the command prompt you had at the start and you should see:



The important thing to do is to force it to find the files you have downloaded. If you let it search automatically, it WILL find the wrong driver.

Hope this helps

Edited by arad85, 23 December 2010 - 05:54 PM.

[rvdgeer]

Wow, great!
Thanks!
Added a link to this topic in the step by step update guide

[deadite66]

the trouble i had in Win7 x64 was that the debug bridge had disappeared.

[trevor432990]

Good job Arad we need a few more guides like that as it is much easier to understand when you use screenshots.

[arad85]

deadite66, on Dec 22 2010, 14:45, said:

the trouble i had in Win7 x64 was that the debug bridge had disappeared.

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...

[T4ylor]

trevor432990, on Dec 22 2010, 14:49, said:

Good job Arad we need a few more guides like that as it is much easier to understand when you use screenshots.

I agree with you there trevor432990. Could just do with the same now for USB host and vega bootscreen mods then I would feel alot more confident in doing them.

[tech_fox]

Well done in producing a guide with pictures. I had just started to do the same so now I will abort. My plan was to produce a guide showing what should normally happen (e.g. NVIDIA Harmony showing up) and then cover options for when it doesn't go to plan as in my case and that of several others.

One update I should like to mention. Like deadlite66 the "Android Debug Bridge Interface" or the "Other Devices - NVIDIA harmony" entries did not appear in my devices manager despite several forced rescans and unplugging/plugging in of Vega. My solution  was to use USBDeview which I have detailed in post 580 page 29 of the MODACO ROM forum.

Perhaps this guide could be expanded to cover this possibility.

[arad85]

tech_fox, on Dec 22 2010, 21:37, said:

Perhaps this guide could be expanded to cover this possibility.

If you can reproduce it, please add... I can switch between drivers all day long and all I get is above....

[warriorscot]

Someone asked to mention the workaround for using a virtual machine to do this. Its better to get the drivers working in windows but this works and it is actually easier to implement if you are struggling.

Virtual Machines allow you to have a completely self contained OS running directly on your desktop which you can then use normally as if it was a discrete machine or integrate into your user interface in windows anything you like. Its a simple thing to set up and can be useful in a number of scenarios especially where you need some flexibility but only have one machine. In this case it is useful because Linux machines don't need updated drivers or when using WinXP they are easier to specify drivers. When you are done you can keep the virtual machine or get rid of it and uninstall the software.

Only real requirements is that the computer you are running on isn't desperately slow, it has a decent amount of RAM(2Gb or more is nice but you can get away with a little less) and some hard drive space (5 to 20Gb depending on how generous you are).

It requires only two things to get started software wise, both are free.
1. http://www.vmware.com/products/player/ Vmware player
2. http://www.ubuntu.com/ Linux is the best bet but windows XP would also work. And any linux distro would work many use small filesize versions of linux as it makes for a small virtual machine that needs very little power to run after all you are only doing it for the drivers and terminal but I can verify 100% Ubuntu works with no messing around.

Once you have VMware Player installed and a copy of the live CD/install disk on your hard drive you need to open up VMware player.
It will open up with its standard welcome screen where you just need to select the "Create a new virtual machine option".

Then select the  option to install from an disk iso image(which you downloaded) and hit next.

Then pick whatever OS you are installing from the list provided and where you want to store it. Doesn't matter where you store it as long as it has enough free space. I use one of my storage drives for it but like I said it doesn't really matter you can delete it after you are done if you like. Hit next again and tell it how much space it is allowed to use, this is a maximum value it might not use that much space just make sure you have enough free space on the drive to cover it. After that just hit next then if everything looks ok on the next page(a summary of what you are doing) just hit finish and it will create the machine(you can tweak the virtual hardware on this page if you like but it should be automatic).

After you have done that it goes on to install Ubuntu on the virtual machine as if it would on a normal desktop and you can view it in a window on your desktop. If you have any problems with this look on an Ubuntu wiki for installation instructions but it is all very straight forward.

Once all installed and you have the desktop for the virtual machine in nice VMplayer window just copy and paste the custom rom folder into your directory in Ubuntu.

Then connect the Vega in Debug mode like you would in windows. Then on VMware Player for to Virtual Machine>Removable Devices>Nvidia Harmony(or similar) then select the Connect(Disconnect to Host) option which will basically plug it into the virtual machine in a virtual usb port.

Once that is done its connected to the VM OS and you open up a terminal, navigate to your custom rom folder then simply use the command sh install-linux.sh or bash install-linux.sh and it will install. Nice and easy no hassle at least for me.

A screenshot is included as well but just the one because its a right pain.
Other commands I used or are useful for the linux virgins:
cd = Change directory
ls = List Directory equivalent to DIR in windows
cd .. = takes you one directory up
sudo = elevates to super user permisions it shouldn't be needed and after you use it you need to type the password to get the command to execute.
linux auto fills when using the tab key just like windows command prompt

 buntuvega.png   303.06K   61 downloads

Here I am putting in a standard disclaimer as I can't promise it will work it only probably will and its easier than begging or borrowing a different non windows 7 machine. I used Ubuntu in this example but like I said other operating systems will work as long as its not win 7 or Vista. The virtual machine is useful tool for other purposes as well and makes a nice sandbox for working on that you can reset at a click of a mouse with no impact on your normal OS. I'm neither a linux or windows whizz kid just a guy that knows enough to use both on a daily basis there may be a mistake in here if there is let me know.

[deadite66]

don't forget to get working in ubuntu (or any linux dist with udev) you need to add a udev rule.

sudo gedit /etc/udev/rules.d/71-android.rules
paste this
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
save then reboot.

assuming 0955 is the same vendor id for your device.
do lsusb when the vega is connected to check.

[andrewg12345]

Thats a pretty comprehensive guide - well done. we shouldnt really have to go through all this - ADVENT!

[marmankites]

Thanks for the Guide,

What if you are showing as ADB interface etc... But the ADB will not find the device, Mine used to and now does not work on any pc I try

USB Mod, Latest Advent Firmware and Pauls Kitchen + PP all installed

[griff_dai]

fantastic guide!
DSG and Paul should pull all this together as a handy guide for all new Vegan's

[warriorscot]

Quote

don't forget to get working in ubuntu (or any linux dist with udev) you need to add a udev rule.

sudo gedit /etc/udev/rules.d/71-android.rules
paste this
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
save then reboot.

assuming 0955 is the same vendor id for your device.
do lsusb when the vega is connected to check.

I didn't need that to get it working, it either did it automatically or its not needed to flash the rom.  Nice to know it might be needed though.

[bear807]

marmankites, on Dec 23 2010, 12:00, said:

Thanks for the Guide,

What if you are showing as ADB interface etc... But the ADB will not find the device, Mine used to and now does not work on any pc I try

USB Mod, Latest Advent Firmware and Pauls Kitchen + PP all installed

i have done exactly what it is stated above i can see the android device like the last picture but adb could not read my device too????? what i have i done wrong????

[warriorscot]

Does adb work at all? Some people have problems running adb but can still install the custom rom.

[bear807]

warriorscot, on Dec 23 2010, 15:13, said:

Does adb work at all? Some people have problems running adb but can still install the custom rom.

adb shows no device when i type in adb-windows device
is this the correct inf file for usb driver?

android_winusb.inf this is thew one appraently shown up under the r1 zip dile driver

the advent vega is giving me a big headache this is bloodly hard with all the command things

i have manage to have my device found on another xp laptop but when i run adb shell nothing comes up
frustrating!

[warriorscot]

You don't really need to get adb running. Just because you can't get it to run doesn't mean you can't add the custom ROM getting adb running properly has its own set of problems for many people. You just need to have the usb driver installed then open the adb-windows.exe and then the install-windows.bat no messing around in command line its only one way to do it and if its running you can test the drivers are correct but if you run the install batch file and it works then you have the right drivers.

[arad85]

marmankites, on Dec 23 2010, 12:00, said:

Thanks for the Guide,

What if you are showing as ADB interface etc... But the ADB will not find the device, Mine used to and now does not work on any pc I try

USB Mod, Latest Advent Firmware and Pauls Kitchen + PP all installed

It seems that everyone who has been affected by this is running the USB host/slave software. Or am I mistaken?

[arad85]

warriorscot, on Dec 23 2010, 16:06, said:

You don't really need to get adb running. Just because you can't get it to run doesn't mean you can't add the custom ROM getting adb running properly has its own set of problems for many people.

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).