Root Can somone explain the drivers?

[r1dePrkCty]

What do you guys mean by "make sure the drivers work"? How do i check to see they are working properly? Or where do i even get these drivers from?

 

[cp1]

If you can use adb to talk to the phone then your drivers work.

USB Driver for Windows | Android Developers

 

[andreezy]

CP, Seriously?

I can use the adb to upload boot anims, etc... therefore it's "talking to the phone"

That being said... the drivers ARE NOT LOADING for many of us when trying the recovery mode.

 

[PossumK]

I think that's the point of the SD card tricks when booting into recovery mode, to get the phone into a mode where the computer can access it with adb. Without successfully implementing the trick/exploit and getting to this stage, the drivers won't load.

 

[MrGoodCat]

What do you guys mean by "make sure the drivers work"? How do i check to see they are working properly? Or where do i even get these drivers from?

uh yeah, this drove my f'ing insane. the instructions i used mentioned nothing about drivers. followed the 10min video, still no mention. not sure why someone would not mention that. kinda important to make the communication between your comp and the phone...it'd be like giving you the keys to a ferrari in the middle of the desert with an empty tank of gas....

anywho, now that thats off my chest...follow the 10 min youtube vid, but insert a few other steps as follows:

when he says don't worry about the sdk getting an error after install, well yeah, stop there. close the error window then the next pop up window. now go to settings and click the box "force...etc." you may need to restart the setup sdk, i forget. it should now NOT error out. under "available packages" click the plus symbol and then scroll to the bottom as i recall and select the "drivers rev3" thingy. install it.

ok now there are some other instructions here:
http://androidforums.com/all-things...-sd-card-let-me-tell-you-how-you-can-too.html
follow the steps on editing the .inf file...add the info as it states then save the file, blah blah blah. just follow that though, not the rest of the guide.

ok now here is where i can't give you a straight forward explanation...sorry. the drivers may install just fine as you follow the rest of the 10 min vid. for me i f'ed up a few times before figuring this driver thing out. so if you f'ed up too, do what i did....

now that the drivers are installed and you have modified the .inf file, we need to update the driver. with the phone plugged in hit vol- and power to get to white screen. computer should make the bloop noise. go to device manager and find the phone. mine was under "other devices" and labeled as "android 1.0" right click and update it. manually point it to the driver .inf file you modified. (point to its folder excluding sub folders). it should update it to "something BOOTLOADER something". good

now i killed the phone and rebooted my comp. when you get it restarted follow the 10 min vid, excluding the optical +power part. when i entered recovery mode i let it install the drivers, took about 20 seconds. once it finished i entered "adb shell" in the command prompt, hit enter and first shot got it to work.

hope that helps everyone a little...what a freaking nightmare. if you take anything away from this it should be "drivers are important" haha. sometimes following instructions doesn't work, knowing how things work can help you solve the problem, in this case the computer was not correctly connecting with the phone via bad drivers.

 

[Piiman]

uh yeah, this drove my f'ing insane. the instructions i used mentioned nothing about drivers. followed the 10min video, still no mention. not sure why someone would not mention that. kinda important to make the communication between your comp and the phone...it'd be like giving you the keys to a ferrari in the middle of the desert with an empty tank of gas....

No kidding in the 10 minute video the guy even says if you get errors about installing drivers to not worry about it. WTF?

 

[Piiman]

now i killed the phone and rebooted my comp. when you get it restarted follow the 10 min vid, excluding the optical +power part. when i entered recovery mode i let it install the drivers, took about 20 seconds. once it finished i entered "adb shell" in the command prompt, hit enter and first shot got it to work.

.

That's the weird part for me. At that point the driver is in error code 28. Now is it like that becasue I didn't get root? or is it a messed up driver?

when you got to that point is it the same device you have working in the first steps. I believe it 's called "ADB composite blah blah" device (sorry not at PC now)

Thanks

 

[lgldrgdlr]

There is no need for a modified driver file. Just make sure you have the driver package installed from the sdk. I also only installed the packages relevant to 2.1. Not sure if that's what helped me or not. Oh, and I don't have HTC sync installed. I can reproduce root 100% of the time.

 

[MrGoodCat]

That's the weird part for me. At that point the driver is in error code 28. Now is it like that becasue I didn't get root? or is it a messed up driver?

when you got to that point is it the same device you have working in the first steps. I believe it 's called "ADB composite blah blah" device (sorry not at PC now)

Thanks

i followed the video initially to the t. it didn't work for me, tried the loop.bat still nothing, tried a TON of times. when on the white screen (phone, where you select recovery) my comp recognized it as "android 1.0" under other devices and when i switched into recovery mode i could here my computer make the "disconnect bloop two times (almost jumbled together). and then nothing would show up in the device manager. kinda thought something was up, but the video said not to worry, so i didn't (initially). got frustrated and then red a post somewhere here about somebody mentioning to download the drivers. so i did that.

still wasn't working for my, tried a couple times. so then i recalled reading in that link about adding the htc incredible lines of text, so i figured why not, can't hurt. did that. then when i got onto the white screen i updated the "android 1.0" driver to the modified inf file. then booted down my phone and comp.

then i started up cmd got it ready, got my phone into the white screen, then threw the phone into recovery. once i did that i got the bubble popping up saying it was installing drivers, i thought to myself, "hmmm, i have a feeling its going to work now, haha" waited for the bubble to finish, then i typed in "adb shell" hit enter, and immediately got it to work. i probably let it sit in recovery for 30-45 seconds before i even entered in the "adb shell". i was kinda under the impression it had to be entered immediately upon entering recovery, but that is not true.

i am not sure what the device name switched too upon entering recovery, never checked. but when in the white screen before i believe it was "ADB Bootloader...something" (i think)

hope that explains it a little better

 

[HTCLUVR]

As with most of us i have tried 3 different memory cards and still can't get adb into recovery. when i do adb devices it does not return any serial number. Does this mean my drivers are not correct? I have added in the terminology to the .inf file under usb drivers. I have tried installing HTC Sync but have since uninstalled it. Not sure what to try next.

 

[lgldrgdlr]

when i do adb devices it does not return any serial number.

Is this with the phone booted normally, debugging enabled? Or when you're in recovery?

 

[HTCLUVR]

Is this with the phone booted normally, debugging enabled? Or when you're in recovery?

i finally got it to recognize the device with the adb devices command and booted normally with debugging on. I just can't get it to recognize the phone while in recovery.

When i boot the phone normally with debugging on I can "adb devices" and it shows the serial. But when i have it in recovery and "adb devices" no serials are returned.

 

[lgldrgdlr]

Try the sd card trick. With the sd in the phone, but not clicked in, boot into the bootloader. When you click to go into recovery, as soon as you hear the usb disconnect sound, push your sd in. I can get recognized in recovery 9 out of 10 times.

Run the loop.bat file while you do this so you get instant feedback.


Sent from my ADR6300 using Tapatalk

 

[HTCLUVR]

Try the sd card trick. With the sd in the phone, but not clicked in, boot into the bootloader. When you click to go into recovery, as soon as you hear the usb disconnect sound, push your sd in. I can get recognized in recovery 9 out of 10 times.

Run the loop.bat file while you do this so you get instant feedback.


Sent from my ADR6300 using Tapatalk

Thanks that did the trick! Finally Root and wifi tethering!!! can't wait for NAND access.

 

[lgldrgdlr]

Congrats.



Sent from my ADR6300 using Tapatalk

 

[r1dePrkCty]

Thanks for all the help guys. I got my drivers to be all set up where it is Android phone and then htc bootloader or whatever but as soon as i enter recovery mode it disappears from device manager so i know its not gonna work as soon as i see that

 

[mb01]

i've tried many of the methods for rooting. when trying yours everything seems to work up until actually going into recovery. ever since the first attempt i never had a bubble pop up about installing drivers, device manager shows my phone as the 2 disk drives and adb devices command doesnt list my phone. any ideas what the problem could be? im using a windows 7 desktop and have the 2gb sd that came with the phone.

 

[lgldrgdlr]

i've tried many of the methods for rooting. when trying yours everything seems to work up until actually going into recovery. ever since the first attempt i never had a bubble pop up about installing drivers, device manager shows my phone as the 2 disk drives and adb devices command doesnt list my phone. any ideas what the problem could be? im using a windows 7 desktop and have the 2gb sd that came with the phone.

Don't worry about driver bubbles, device manager etc. If you're able to do adb devices and get a serial returned when booted normally, your drivers are fine. Just try, try again. . . or wait till there's an easier method.

 

[Piiman]

i followed the video initially to the t. it didn't work for me, tried the loop.bat still nothing, tried a TON of times. when on the white screen (phone, where you select recovery) my comp recognized it as "android 1.0" under other devices and when i switched into recovery mode i could here my computer make the .

I have this device also but it is in error at this point. Was yours?
I have tried to install the drivers for it also at this point but it doesn't like the drivers in the SDK. If I force it it complains that Windows can't confirm that the drivers are for the hardware.
So My question is did you force the driver install for the ADB composite device that shows up on the fastboot screen (before you boot to recovery)? This same device has no problems loading the driver before I do the VOL + Power turn on or from adb shell when the phone is booted normally.

still wasn't working for my, tried a couple times. so then i recalled reading in that link about adding the htc incredible lines of text, so i figured why not, can't hurt. did that. then when i got onto the white screen i updated the "android 1.0" driver to the modified inf file. then booted down my phone and comp.

Is this the same white screen where you wait for the error before you VOL down to select recovery? If so what device driver are you loading for it? ADB COMPOSITE DEVICE (or whatever it's name is)

then i started up cmd got it ready, got my phone into the white screen, then threw the phone into recovery. once i did that i got the bubble popping up saying it was installing drivers, i thought to myself, "hmmm, i have a feeling its going to work now, haha" waited for the bubble to finish, then i typed in "adb shell" hit enter, and immediately got it to work. i probably let it sit in recovery for 30-45 seconds before i even entered in the "adb shell". i was kinda under the impression it had to be entered immediately upon entering recovery, but that is not true.

i am not sure what the device name switched too upon entering recovery, never checked. but when in the white screen before i believe it was "ADB Bootloader...something" (i think)

hope that explains it a little better

I really want to know what that Android 1.0 device is at the white screen after you force it to update the driver and if it doesn't it automatically or if you force it after windows complains.

Thanks for your time!

 

[Piiman]

There is no need for a modified driver file. Just make sure you have the driver package installed from the sdk. I also only installed the packages relevant to 2.1. Not sure if that's what helped me or not. Oh, and I don't have HTC sync installed. I can reproduce root 100% of the time.

If you didn't modify the INF how did you get the drivers installed?

 

[Piiman]

Thanks for all the help guys. I got my drivers to be all set up where it is Android phone and then htc bootloader or whatever but as soon as i enter recovery mode it disappears from device manager so i know its not gonna work as soon as i see that

I think I almost had it once because I saw it try to load some device drivers for android phone device (or something like that ) it was causing device manager to refresh over and over so I couldn't read it completely. But in the end the devices disappeared and nothing happened :-(

Some one needs to figure out exactly what triggers this and how to figure out the timing on different PC's. Come on someone

 

[lgldrgdlr]

If you didn't modify the INF how did you get the drivers installed?

For the drivers, i just installed the driver package from the sdk, without usb connected to pc, then plugged phone in, with debugging on, into a usb port i hadn't used yet, you'll get the driver bubble pop up, just leave it alone. did the method i posted a few replies up and i can reproduce ~100% of the time.

 

[Piiman]

For the drivers, i just installed the driver package from the sdk, without usb connected to pc, then plugged phone in, with debugging on, into a usb port i hadn't used yet, you'll get the driver bubble pop up, just leave it alone. did the method i posted a few replies up and i can reproduce ~100% of the time.

That makes no sense. If you didn't modify the inf file in the sdk drivers then it wouldn't load them from there. So where do you have drivers? Did you install HTC sync or the VW Access manager?

 

[lgldrgdlr]

If a modified driver file was necessary, I assmue without it the sdk wouldn't work at all with the DInc, no dalvik, adb devices, etc, with the drivers "stock" from the driver package. Since this is not the case, the drivers do not need to be modified. If my line of reasoning is incorrect, please provide some more insight.

No HTC sync or VW Access manager.

 

[Piiman]

If a modified driver file was necessary, I assmue without it the sdk wouldn't work at all with the DInc, no dalvik, adb devices, etc, with the drivers "stock" from the driver package. Since this is not the case, the drivers do not need to be modified. If my line of reasoning is incorrect, please provide some more insight.

No HTC sync or VW Access manager.

You must have some driver loaded up. When you turn on usb debug what device shows up in device manager?