• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root No drivers!

varaonaid

varaonaid

Android Enthusiast
Hello,

Been trying to root for awhile now reading through different methods, tricks, etc and to be honest, my head is spinning from all the different info. However, in trying so many different things, I did seem to come up with a true issue that I can actually pin down...I don't have any drivers installed for the DInc. I tried the edit method for the .inf file in the sdk and tried to manually update the drivers (device manager says there aren't any drivers installed for it at all) and it just simply doesn't see any drivers there.

I'm kind of lost. Installed HTC Sync and uninstalled and reinstalled three times. What am I missing (other than drivers, of course) to get this installed? Where/how can I get the drivers and actually install them?

I'm running Win 7 x64.

Thanks in advance.
Rae
 
For what it's worth, HTC Sync fails on my computer as well. The phone fails to find it on the PC even though it's open and set. This is getting really frustrating.
 
this is what i did:

run the sdk. if you get that error message, cancel out of it and make you way to the settings selection to your left. click on the check box for the "force...." now the sdk should proceed without erroring out. once it finishes go to "available packages" selection (i think thats what it was called) click the "plus" box. you will then get a drop down of many different packages. scroll to the bottom and select "drivers v3..." (something like that). install them. once they are installed, they will be placed into your sdk folder.

now when you plug your phone in and are booted up in the white screen (after holding vol down and power) go into device manager, find you phone. should be labeled "android 1.0" and update the driver. manually point it to the driver folder in your sdk folder. let it do its thing. now when you go into the recovery screen (witht eh red triangle) it will install drivers again, let it do its thing again. once it says "installed" then try your adb shell command, and you should be good.

fyi, i am on win7 64bit too. htc sync is not needed. once i did this driver thing i rooted my phone first shot, and also did a friends phone first shot. the drivers are crucial, and seems to be a very neglected part of the process for rooting the inc. at least in the processes i have read.

anywho, good luck! hope that helps
 
MrGoodCat said:
this is what i did:

run the sdk. if you get that error message, cancel out of it and make you way to the settings selection to your left. click on the check box for the "force...." now the sdk should proceed without erroring out. once it finishes go to "available packages" selection (i think thats what it was called) click the "plus" box. you will then get a drop down of many different packages. scroll to the bottom and select "drivers v3..." (something like that). install them. once they are installed, they will be placed into your sdk folder.

now when you plug your phone in and are booted up in the white screen (after holding vol down and power) go into device manager, find you phone. should be labeled "android 1.0" and update the driver. manually point it to the driver folder in your sdk folder. let it do its thing. now when you go into the recovery screen (witht eh red triangle) it will install drivers again, let it do its thing again. once it says "installed" then try your adb shell command, and you should be good.

fyi, i am on win7 64bit too. htc sync is not needed. once i did this driver thing i rooted my phone first shot, and also did a friends phone first shot. the drivers are crucial, and seems to be a very neglected part of the process for rooting the inc. at least in the processes i have read.

anywho, good luck! hope that helps
Click to expand...

Thanks for the replies. I inadvertently stumbled upon part of this but will try the full process. I did a very similar process to what you described with downloading the usb drivers from the sdk program. But they wouldn't install no matter what I did. I tried the edit and tried pointing them directly to the folder and it would say that no drivers were found at all. But I managed to find one of the updated or hacked driver files and it installed without trouble. So I at least finally have a working driver. Still can't get into the adb shell so it's driving me crazy. I'll uninstall htc sync since it basically seems to cause problems down the line anyway and try your trick of letting the drivers install again. Cross fingers, right?

But again, thanks for the tips!
 
i had htc sync installed when i rooted my phone, and it was uninstalled when i rooted my friends phone. i think it only really matters (needs to be uninstalled) for doing the reflash tool.

as far as drivers go. when you manually pointed to the driver folder, did you make sure to point to the main driver folder and unselect the "include sub folders" box? since i am 64bit as well i thought maybe i needed to point to the "amd64" folder but i simply edited the driver file in the main folder and pointed to only that one. if you have the right drivers it should say "android bootloader device" or something with "bootloader" in it. did you get that to show up?

as for the sd card, i used a REALLY old 1gb card, back when 1gb was the shiz. there isn't even a brand name on it or class number. maybe try different sd cards as well.

also when i put it into recovery (black screen with red triangle) i let it sit for about 30 seconds before i even entered in the "adb shell" command

try switching cards (if you can) and try letting it sit in recovery a little bit before trying to access adb shell. don't give up!
 
MrGoodCat said:
i had htc sync installed when i rooted my phone, and it was uninstalled when i rooted my friends phone. i think it only really matters (needs to be uninstalled) for doing the reflash tool.

as far as drivers go. when you manually pointed to the driver folder, did you make sure to point to the main driver folder and unselect the "include sub folders" box? since i am 64bit as well i thought maybe i needed to point to the "amd64" folder but i simply edited the driver file in the main folder and pointed to only that one. if you have the right drivers it should say "android bootloader device" or something with "bootloader" in it. did you get that to show up?

as for the sd card, i used a REALLY old 1gb card, back when 1gb was the shiz. there isn't even a brand name on it or class number. maybe try different sd cards as well.

also when i put it into recovery (black screen with red triangle) i let it sit for about 30 seconds before i even entered in the "adb shell" command

try switching cards (if you can) and try letting it sit in recovery a little bit before trying to access adb shell. don't give up!
Click to expand...

Thanks for the encouragement. Gotta admit I'm getting pretty frustrated about it all. Tried 3 different cards so far (no, don't have the PNY 2gb yet, don't have a walmart close by). Finally got the drivers working - both pda net & the unrevoked works fine. However, strange thing that I noticed...when it goes to black screen, the device manager no longer recognizes it as the android bootloader device but views it as a couple of android usb drives. Is this normal? If not, how do I fix it?

FWIW, tried everything in the "if you can't get root thread" and tried three different cards on two different computers. This is SO frustrating! I've followed all the instructions to the letter. Why so much inconsistency?? :(
 
varaonaid said:
Thanks for the encouragement. Gotta admit I'm getting pretty frustrated about it all. Tried 3 different cards so far (no, don't have the PNY 2gb yet, don't have a walmart close by). Finally got the drivers working - both pda net & the unrevoked works fine. However, strange thing that I noticed...when it goes to black screen, the device manager no longer recognizes it as the android bootloader device but views it as a couple of android usb drives. Is this normal? If not, how do I fix it?

FWIW, tried everything in the "if you can't get root thread" and tried three different cards on two different computers. This is SO frustrating! I've followed all the instructions to the letter. Why so much inconsistency?? :(
Click to expand...

ok, thats the issue of why you can't get it rooted. i don't recall the exact device name when in recovery, but i know that it does not switch to drives. i thought it still said "something bootlaoder something". i would check but i have the custom recovery installed now, an i think it may be different.

when i manually updated the drivers they installed and renamed the phone to the bootloader title. then when i put the phone into recovery it automatically installed drivers again, but i never checked the name of the device at that point. i just let it sit in recovery and finish installing for about 30-45 seconds, then tried adb shell at it worked the first time.

i would try uninstalling/rolling back the drivers, reboot you comp, put your phone into bootloader mode, plug it to computer, manually install drivers again, then try recovery and see if it automatically installs drivers again, if it does that you should be golden. so far all the cards you tried don't matter since the drivers aren't there, so don't rule those out yet. just take it all as a challenge and don't let it frustrate you, you'll get it soon enough
 
yojoe600 said:
install pda net... it has better drivers i think... or use the ones that unrevoked gives you
Click to expand...

Huge +1 on this advice. D/L the unrevoked flash recovery tool, you won't use it until you get root but they have what I believe to be the best drivers and they include an html link in the download package that explains step by step install instructions. The PDAnet drivers also seem to have worked for some people. I had both installed when I got root.
 
OK, so this all makes sense, I just don't know how to get rid of whatever drivers it installed. The first time I plugged it in, it tried to install the drivers (obviously the bootloader one didn't work as I didn't have it yet) but when it went to black screen it installed drivers to see it as a drive. Wondering if perhaps this had been the problem, I started from scratch on a different computer and the exact thing happened (black screen = usb drive drivers automatically installed). What/how do I remove whatever needs to be removed to start this thing over?? Should I try to use the pdanet/unrevoked drivers to update the drivers for the "usb drive" that it sees it as when it's in black screen recovery??

PS. Thanks for the replies and info. :)
 
You must log in or register to reply here.
Back
Top Bottom