Root Driver issues

[irishpride]

I know I'm not alone here with the ADB driver issue. Everytime I connect my phone while in bootloader, it comes up as Android 1.0. I've tried everything I can think of. I'm not a complete noob when it comes to rooting phones, I've done it to every phone I've had, even going back to the WinMo days.

If anyone has some advice of tips on how they got it working, anything would be much appreciated. By the way, I'm using Windows XP. Thanks.

 

[snowzach]

Read this...
xda-developers - View Single Post - Unrevoked team: Incredible Root process

1. Download the Android Drivers (part of the SDK)
2. Edit android_winusb.inf and add:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Under the Google.NTx86 Section and the Google.NTamd64 section
3. Try to re-install the driver...

 

[contagous]

Read this...
xda-developers - View Single Post - Unrevoked team: Incredible Root process

1. Download the Android Drivers (part of the SDK)
2. Edit android_winusb.inf and add:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Under the Google.NTx86 Section and the Google.NTamd64 section
3. Try to re-install the driver...

I've done this and still have issues, can't catch the adb recovery at all, i'm on Vista 32

 

[sylent101]

Ditto..

 

[DiegoMejia]

I know I'm not alone here with the ADB driver issue. Everytime I connect my phone while in bootloader, it comes up as Android 1.0. I've tried everything I can think of. I'm not a complete noob when it comes to rooting phones, I've done it to every phone I've had, even going back to the WinMo days.

If anyone has some advice of tips on how they got it working, anything would be much appreciated. By the way, I'm using Windows XP. Thanks.

do you have htcsync installed? it should be in your phone if you havent installed it, if not just get it from my 10min video guide

 

[cantare]

Why is HTC sync necessary? Won't installing that application overwrite the Google sdk drivers with HTC's?

Or does this whole recovery shell thing depend on having some weird hybrid mix of Google Sdk and HTC drivers running concurrently? I can just see something random like that being the answer.

 

[mags]

Right, it will overwrite the Google drivers (that don't explicitly support the Incredible) with the HTC drivers (that do support the Incredible) which is a good thing.

Honestly though, I never got my Windows drivers working straight to get root in Windows.

I jumped over to my Ubuntu partition and loaded the Android SDK for Linux and had it rooted in 5 minutes. I still can't get ADB started in recovery mode in Windows (although I can use ADB shell on a booted Incredible)

I do think the HTC drivers are the best option right now for most people.

 

[blue45]

Ok first off let me say that I have not rooted my phone, but I know I have the right drivers. Ok and to answer your post about the android 1.0 you have to go to my computer, Hardware, Device manager. Then in the top, the very top as you plug in your phone, you should Android phone. If you do not then you do not have the right driver in there. If you see something like android device or HTC, you need to update the driver and click advanced i will choose driver manually. Then browse to c:\sdk\usb_driver. Make sure you have edited the android_winusb.inf file with those lines from xda.



Find the section labeled [Google.NTx86]. At the end of that section, add the following lines.

;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01

Then find the section [Google.NTamd64]. At the end of that section, add the following lines.

;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01

Again just copy and paste. I have attached pictures to show where these need to go.


All credit goes to this website


Hope this helps. It didnt get me root but i know the drivers and adb shell works right in regular mode at least. I have an 8gb sandisk card. I hear those are very hard to root unfortunately.

 

[cantare]

@mags: Hmm. I've seen a lot of conflicting advice on which set of drivers to use... of course, the Google SDK's are better-behaved once you hack the .inf file with Incredible-specific entries as widely discussed.

EDIT @blue45: If you're going to do that you may as well add another line to both entries:
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
That makes it so Windows doesn't choke when you try the "skating Android" bootloader screen.

But I just did a clean install of these drivers (w/ modded .inf), and no luck--in recovery the dev mgr shows only 2 usb drives mounted, no ADB interface. Which seems to be computerese for "you failed!"

Will try the HTC Sync install next. Wish I could try it on ubuntu, but I have to draw the line at repartitioning my hdd and installing another OS just to get rooted!

EDIT2: Just installed full HTC sync over the Google SDK w/ modified .inf... Android ADB driver is overwritten with a device "My HTC" during normal connection (phone on, debug enabled), but if I start the 'skating Android' bootloader interface, dev mgr shows "Android 1.0" with yellow ? for a sec then reloads the old Google SDK driver. Going to recovery (either via 'abd reboot recovery' command or from the bootloader) just gives the same 2 "HTC Android Phone USB Device" entries under Disk Drives; no ADB device, no root.

 

[blue45]

@mags: Hmm. I've seen a lot of conflicting advice on which set of drivers to use... of course, the Google SDK's are better-behaved once you hack the .inf file with Incredible-specific entries as widely discussed.

But I just did a clean install of these, and no luck--in recovery the dev mgr shows only 2 usb drives mounted, no ADB interface. Which seems to be computerese for "you failed!"

Will try the HTC Sync install next. Wish I could try it on ubuntu, but I have to draw the line at repartitioning my hdd and installing another OS just to get rooted!


EDIT @blue45: If you're going to do that you may as well add another line to both entries:

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

That makes it so Windows doesn't choke when you try the "skating Android" bootloader screen.

Thanks ill that advice and tell you what happens next

 

[contagous]

In my device manager it shows as the following:

When my phone is on and connected It shows as Android Composite ADB Interface. When my phone is at hboot it shows as Android Bootloader Device.


but still cant manage to get into adb recovery via any method, trying to different types of sd cards with or without loop...


Just dunno whats wrong has anyone got it working with Vista 32 yet?

 

[tats_06]

It's not the drivers issue...it's that the adb shell exploit window is so small and it is very hard to catch it. That is why it's not recognizing phone.

 

[cantare]

Yes, it could be that mounting the 2 usb devices is just what Windows does when you fail to catch the ADB shell exploit window. Which is plausible, and suggests it isn't a drivers thing.

But... if you read around the various root forums you'll see posts from people who boot to recovery and just type adb shell once to get in--reproducibly. Their exploit window has got to be big, on the order of several seconds at least!

So the question becomes, what sets these people apart? Could be the SD-card make or formatting details that stretches out the window. I'm reading a lot about success with $10 PNY 2GB cards from Walmart (dunno what class)...wishing I had one of them to try right now, as my kingston and sandisk 2GBers are all FAIL.

 

[blue45]

well i think its that it loads two different drivers when your actually trying to root the device. I mean it loads the adb composite driver in regular start up mode and then it loads the boot loader driver. We need to edit those drivers so they talk better. If we could have it load the composite driver every time it would work everytime as that works before we put the phone into reboot recovery.

 

[irishpride]

When I plug my phone in while in bootloader it says "Android USB Device" and below that "My HTC" in Device Manager. I have installed the drivers through Android SDK several times with the extra info added for the Incredible. I just can't figure out what I'm doing wrong.

For me, root wouldn't really be that important until we were able to flash custom ROMs, overclock, ect, but I need it within a couple of days so I can have wireless tether. Is anyone else getting frustrated? I know I am, I've put somewhere around 10 to 15 hours into this, with absolutely nothing to show for it.

 

[drPheta]

When you're in recovery mode, and ADB shows the error message (in other words you've gained access to the phone to root)... what shows up in Device Manager?

For me:
Normal bootup = "Android Composite ADB Interface"
Bootloader = "Android Bootloader Interface"
Recover = "Android Composite ADB Interface"

How did I get mine to work? I turned off ALL RADIOS, plugged the phone in, cmd>sdk>tools>adb reboot recovery.

Phone rebooted, started "loop.bat" from the command prompt, did the sdcard click in and out till i heard the beep of the USB recognizing a phone, and the error message came up. I'm in.

try that guys.