yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] Tizoc:
what worked for me oddly enough, I installed HTC Sync... and updated the Android SDK by running the SDK Setup.

Then I followed the guide at androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html (Sorry I can't make links yet apparently.) what with booting it via holding the optical trackball in, etc etc...

The other thing I did was used a 2GB MicroSD from Micro Center.. my 8GB did not work but the 2GB did. it could be that because the 2GB was formatted as FAT instead of FAT32 that it worked, but that is merely speculation. Sorry I couldn't narrow it down further but these three things together and the directions in the link worked like a charm first time.

Best of Luck to you all!
[Droid Incredible Android Development] tdavis42:
I am having the same problems of Daemon disconnecting and here is a Google help page I found concerning "ADB server didn't ACK" because that is the error we get way before it freezes. Here is the link to Google I have yet to try this concerning port 5037 but please report back if you get the Daemon freeze fixed.
[Droid Incredible Android Development] larsdennert:
What we need are people who HAVE got it working comparing notes not people who HAVEN'T. I guess we could eliminate all paths to failure and only the path to success would remain but wouldn't it be easier the other way? I know. The other threads all say "I got it" but don't describe their setup properly.
[Droid Incredible Android Development] heavensblade23:
Couple observations:

-AFAIK, everyone that has the 16GB ADATA Class 6 has been able to root. I haven't heard anyone NOT being able to root using that card. It worked on the first try for me.

-Of the people that couldn't get into adb, 3 were able to get it working by clicking their SD card in and out over and over again. (This puts wear on the spring so you might not want to do this)
[Droid Incredible Android Development] E30kid:
Androidforums has a thread about this. They have info from people who successfully rooted.

http://androidforums.com/all-things-root-incredible/98599-success-trend-thread.html

It's not too comprehensive, but it is something.
[Droid Incredible Android Development] pozer69:
just curious what brands were the sd cards?
[Droid Incredible Android Development] blw1230:
Well I'm here with everyone else. Tried everything from about I could find. Nada.
[Droid Incredible Android Development] Captchunk:
I have used two different 2gb SanDisk cards and an 8gb Class 6 Transcend and none of them have worked. And, lowpoint of the day: trying for half and hour with the first method of just keeping the usb cable plugged in the whole time before realizing that the usb cable was only plugged into the phone not the computer. FML. :o

Congrats to anyone else that gets root, but hopefully we'll pinpoint what the rest of us need to do.
[Droid Incredible Android Development] jitajt:
"Nothing I try gets ADB to connect in Recovery"

I am noticing a few things as I am trying to root my DI, first when the phone is on it shows as Android composite ADB interface (under android phone) in my device manager and I can send it adb commands and it responds, (permission denied responses of course) then I put it into bootloader, (Vol down + power) it shows up as android bootloader interface (under android phone) but when i go into recovery (Vol down then power) it shows up under disk drives as HTC Android phone USB device. and it shows two of them. my theory is because it isnt showing up as an adb interface while in recovery no matter what I do it will never accept adb commands. if anyone else can take a look and see what it says in your device manager at these different stages we might get it narrowed down
[Droid Incredible Android Development] blw1230:
Since a lot of people, including myself are having some problems, does anyone know who close we are to "one click root" like we saw with the evo?
[Droid Incredible Android Development] larsdennert:
Someone mentioned setting the interface on the phone to htc sync. Little good it did me.
[Droid Incredible Android Development] rynosaur:
What you're experiencing is completely normal. As I understand it, the NAND/SPL boots recovery with adb's permissions open to UID (0)/superuser, and then recovery is programmed/patched to quickly clamp down on adb to prevent root access. Obviously, SPL does not allow adb commands. What happens in this "race" condition is you are trying to exploit a tiny gap between the handover of control from SPL to recovery. Some say it is as little as 50ms, which I'm sure you know is 1/50th of a second: a very short time indeed. Apparently, the recovery's been patched to check SDcard status before it blocks adb console access, and if one's sd-card takes a long time to check there's even more time to sneak an adb console command in and gain root console access.

I doubt highly that you would even see Window's Device Manager react quickly enough to ADB's access opening and closing to even witness it happening. Perhaps there is a log which could be triggered and viewed in Windows or Linux to watch the devices change IDs and permissions? That might help us get timing down and/or write a really good script to sense, report and react to that brief window's interval.
[Droid Incredible Android Development] heavensblade23:
it's definitely not 50ms if people can hit the window reliably in certain circumstances
[Droid Incredible Android Development] rynosaur:
Like I said (or meant), certain sdcards seem to lengthen the window reliably and considerably. For some reason 16gb is a magic number, although success rates aren't dominated by class2s and class6s aren't exempt from the benefit. We need someone who knows flash technology really well to explain.
[Droid Incredible Android Development] psmafia:
I don't know about 16gb because I have a sandisk class 2 16gb that won't work. For people who have been successful what does your device manger show while connected in recovery? Do you get two disk drives? I think that might be my problem.
[Droid Incredible Android Development] jitajt:
people in the other thread stated that when they are in recovery it shows up as android device 1.0 or it doesn't show up at all. so I don't think this is normal,
[Droid Incredible Android Development] rynosaur:
That's right, it shows up as ADB because their exploit attempts are successful whereas ours are not. In other words, if you see anything BUT "ADB..." in recovery, you have failed. I'm about to document this in a video if I have enough light in here for my G1 ;)
[Droid Incredible Android Development] jitajt:
"Nothing I try gets ADB to connect in Recovery"

yeah I get what you are saying but before they got root it didn't show up at all in device manager, I don't have root and it is showing up as disk drives, thats not normal for a phone that was able to be rooted. mine shouldn't be showing anything in device manager before root while in recovery mode. I am going to reflash to the stock ROM and try again and if that doesn't work I will try to flash to the hboot 0.79 ROM and try again.
[Droid Incredible Android Development] R1lover:
Make sure you have the latest sdk and usb drivers from google.... also make the needed edit to the driver file for windows.... after that if your drivers are working properly you will be rooted in 5 minutes.
[Droid Incredible Android Development] Tizoc:
1 8GB Micro SD Card Microcenter store brand SDHC marked on it FAT32 Formatted = no go

1 8GB Micro SD Card SanDisk Branded FAT32 SDHC Marked = no go

1 2GB Micro SD Card Microcenter store brand no-SDHC mark formatted as FAT = winner!
[Droid Incredible Android Development] PeteyNice:
What is the "needed edit"?
[Droid Incredible Android Development] Tizoc:
I did not need to edit any inf files for the record..

Though I did install HTC Sync, THEN update my USB drivers (through the SDK Setup.exe from the android SDK) then pick the usb driver for your device in device manager.
[Droid Incredible Android Development] theoneownz:
I must say Finnally after looking everywhere and trying so much i found my issue stopping booting into recovery... I knew something was wrong with the windows drivers for adb. My issue had nothing to do with which card i was using but rather windows driver...

I uninstalled the driver related to ADB installed by SDK from device manager. Started SDK and deleted usb driver update3

Reinstalled driver only (not 1 package is required other then the usb for sdk) after complete, open directory sdk/usb_drivers/ double click on android_winusb.inf and add entries below

Save the file. With phone on enter debug mode and confirm driver installed properly by doing

open cmd

change to directory using cd root of tools folder exsample cd c:\Users\Home\Desktop\sdk\tools Enter

type adb devices

should load htc000000 ect.. now follow the boot process everyone is attempting to enter recovery mode

Hope this helps some of you out

*update

comeleted steps

adb push busybox /sdcard/busybox

adb push ota.zip /sdcard/update.zip

adb push payload-update.zip /sdcard/update.zip

adb shell

su

/system/bin/cat /system/bin/sh > /system/bin/su

/system/bin/chmod 4777 /system/bin/su
[Droid Incredible Android Development] zeke1988:
failed 9 times with 4GB class 6 card. but rooted with a 1GB Nokia sdcard.
[Droid Incredible Android Development] Drukan:
The card MATTERS!

just thought id share..

Same info as all other users posted, post OTA hboot 77, etc

i tried for HOURS (using the 16G card from my Moto Droid)

then tried a few more hours with the 2G i got with my INC.

finally i tried the card i had in my storm1, (i had given it to my girl, so soon as she got here tnite i stole it back!)

First try!!! its a Kingston 4 gig Class 4 SDHC.

Apparently the card matters... but it also seems to be phne specific... everyone gets it with differnt cards..??!??
[Droid Incredible Android Development] sylent101:
could you elaborate..like uhh step by step? lol i know the problem is with the drivers i figured it out hours ago but i dont know how to go about fixing it
[Droid Incredible Android Development] aaronjb:
Same thing for me as well!
[Droid Incredible Android Development] Xystence:
I am having the same issue where ive updated everything, tried everything listed so far. When I go into recovery my system quickly shows a device "Android 1.0" which I believe is the ADB driver itself as not being installed. I have tried the drive edit and windows still will not install this driver.
[Droid Incredible Android Development] vzw:
Tried that

Here is what I get:

c:\android sdk\tools>.\adb kill-server

c:\android sdk\tools>.\adb star-server

adb server is out of date. Killing...

* daemon started successfully *

c:\android sdk\tools>

Ok I have been trying I even tried your method still getting the " adb server is out of date."

I don't understand I have tried different looping methods... Have been working this for so many hours I'm afraid continuing to pull my bat will eventually tweek my connection prongs... There has to be a way to get past this shell.... in to adb command...

Help
[Droid Incredible Android Development] R1lover:
My suggestion is to first get htc sync installed and make sure it installs all the drivers you need to sync with your pc....

then install the latest sdk WITH the latest USB Drivers from google.

After that it should work.... you will need to make one file edit you can find here to a driver for your pc to see the inc in recovery mode.

http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/

Once your in recovery mode, open device manager... at the very top you should see "Android Phone" the driver for this needs to be manually updated to the edited driver you see in the above link.

Once you have that done and you see the "Android Phone" at the top of device manager (while in recovery mode on the phone) IT SHOULD work....

I'm just sharing my personal experiences here.... as I had the same issues and spent over 5 hours trying to figure it all out.... for me it came down to making sure all the drivers installed correctly.
[Droid Incredible Android Development] Xystence:
I have done all this. I edited the driver and everything. Now I am going back and looking and my phone will not connect to HTC sync, I have tried everything I can think of and maybe this is where my issue lies?
[Droid Incredible Android Development] Xystence:
Ok got sync working, let me try what you said above, but when I am in recovery mode I do not see anything called Android Phone. Its not there at all. The USB noise clicks on but I am only seeing the htc android disk drives for the mem card and internal memory listed in device manager. When I am in the bootloader however, there is something called Android 1.0 that I cant get a driver to install for. I tried the edited drivers, it doesnt work.

I also noticed that no matter what I do I cannot get the adb to work at all when I am loaded into my droids OS. I have USB debugging enabled but I am not able to use the devices command or adb reboot recovery. I keep getting permission denied messages.

This all must be linked to my issue.

Anymore advice?
[Droid Incredible Android Development] pozer69:
Double check your USB Debugging. I had mine turned on, then it turned itself off and I was having the same problems in Device Manager:

and.win.dev.mgr.JPG <- No USB Debugging

and.win.dev.mgr2.JPG <- With USB Debugging
[Droid Incredible Android Development] Xystence:
Ok it looks like I got adb working when phone is fully booted, I was able to use the adb reboot recovery command. Now just to get it going when in recovery.
[Droid Incredible Android Development] Xystence:
I got my phone rooted finally. It took me uninstalling everything from HTC all together and it worked.
[Droid Incredible Android Development] pozer69:
So you don't have the HTC software installed at all? Please be more specific so I can figure this out.
[Droid Incredible Android Development] rynosaur:
You certainly don't need HTC Sync Software install to root. It has made the process easier for some, harder for others. You do need a working driver, and HTC Sync seems to leave behind a decent working driver.
[Droid Incredible Android Development] jitajt:
"Nothing I try gets ADB to connect in Recovery"

can you zip up your drivers and post them so we can try it with known drivers that work.
[Droid Incredible Android Development] R1lover:
I will do that, but in the mean time...... many users had since had success with restarting their pc a few times and trying each time.... another method that has worked is using different usb ports on the pc..... as when you plug into a different port it will again search for the proper drivers and re-install them....... give that a shot maybe
[Droid Incredible Android Development] jitajt:
I have done everything under the sun including doing fresh OS install and everytime I get to recovery it shows up as two usb disk drive and installs the default windows drivers automaticaly. it shows up as android 1.0 device while in bootloader but after I go to recovery it doesnt come back with anything but what I said above.
[Droid Incredible Android Development] nikeair:
Same here the only thing I haven't tried yet is getting the 16gb data card. Which will be my next step.
[Droid Incredible Android Development] rynosaur:
I hate to sound like a broken record, but have either of you tried linux?
[Droid Incredible Android Development] antizac:
error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

FFFFFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!
[Droid Incredible Android Development] vzw:
LOL no kidding~!
[Droid Incredible Android Development] antizac:
youre not gonna believe it .. finally got it!! used the method of pushing the sd card in and out while it was booting into recovery.. worked on the first try!

http://xdaforums.com/showpost.php?p=6783235&postcount=542
[Droid Incredible Android Development] vzw:
well its nice to know someone got it that was having as many issues as I was... I have already tried that method over and over... Oh well will keep looking
[Droid Incredible Android Development] pozer69:
when inserting and removing your sd card, do you do it at a relatively fast pace? I find it hard to get my fast stubby fingers in their. Maybe if I had longer nails.

Also, what sd card did you use?
[Droid Incredible Android Development] anarkiss:
I'm on the edge ready to jump off....

I have tried every way that is on these forums... and a million others... and these are my failures

1.(Normal) First Try, and a billion tries after that: (Error: Device not found)

2. SD Card trick: (Error: Device not found)

3. Use 3 different cards and 2 different computers XP and Windows 7: (Error: Device not found)

4. Downloaded drivers and mod .inf file: (Error: Device not found)

anyone else have any ideas? At my wits end.
[Droid Incredible Android Development] martin0285:
I have a shot in the dark idea, maybe completely useless but mights well try....

Use USB Deview to remove anything HTC related on your computer, start again...While in recovery if you are unable to load adb shell, again look back at USB Deview and remove anything HTC related.... Seems everyone is seeing "two disk drives".....If those are removed and windows gets the chance to load adb, you just never know :)
[Droid Incredible Android Development] askwhy:
Things are still looking cloudy, but there has been some progress towards refining and combining the various elements that have led to people's success getting adb in recovery. Consider that:

* Some people have been able to get in without using a 'special' sdcard

* Nobody has reported failure with either of two 'special' sdcards so far

* Some who had success with the 'special' cards had 100% failure prior

While a particular sdcard may not be required, at least two identified sdcards have a clear impact on the ability for people to succeed in getting adb in recovery. Additionally, timing seems to play an important role. Consider that:

* Some have been able to get in without ejecting/reinserting sdcard

* Some who had success ejecting/reinserting sdcard had 100% failure prior

* Some find practice + 'special' sdcard + timing can yield 100% success

So, if you take what we know about the situation, it is reasonable to consider investing in one of the as yet identified 'special' sdcards, and also to consider using the eject/reinsert just before '!' method. Combining both with a little practice and patience seems to have a very high success rate, if not 100%.

Current known 'special' sdcards are cards with no reported failures, and numerous reported successes:

ADATA 16GB Class 6

Kingston 4GB Class 4
[Droid Incredible Android Development] antizac:
I used a pen to push the card in and out.. at a steady pace so it would do a full click every time in and out. .. im using the 2gb card that verizon gave free with the phone.. hope this helps !
[Droid Incredible Android Development] KB Smoka:
I had success with the 2GB Verizon card at two different speeds.....The first time it worked I was going as fast as I could, just popping it in and out. The second time I was popping it in and out every second or so. Pure Luck.
[Droid Incredible Android Development] incredible_rooter:
For two days, I read this and the main rooting thread all the while rebooting and rebooting my DINC. I was as frustrated as you guys. Then someone mentioned something on the main thread that has worked for me repeatedly. Now I have a fully rooted phone with Wireless Tether working perfectly! I'll try and share what is working for me. I have all the same specs as many of you. .77 HBOOT Windows 7 laptop, 2GB SanDisk SD Card, etc etc...

Here's what I did:

1. Remove HTC Sync. You don't need it.

2. In Control Panel, remove anything that has to do with HTC. There was something else installed there, I think it was something like "HTC Driver Updater" or something like that. Don't worry, the USB driver gets left behind and the PC still recognizes the phone.

3. Turn on your phone and do the following:

a. Turn on your WiFi/3G and GPS. Use Car Panel to plan a GPS route. Open the navigator and wait for the voice to start telling you "where to go." Then exit navigation, and close the car panel.

b. Open your browser and look at a few pages.

c. Do a few other routine tasks.

4. Connect the phone to USB and make sure it recognizes it and you can "ADB Devices" in the SDK and see your device. If not, make sure that you have Debugging enabled on the phone. Also, set it in HTC Sync mode, not Disk Drive mode.

5. DISCONNECT THE USB CABLE. (If you don't do this, this method won't work.)

6. This is the step that made the difference for me. Don't turn off the phone, pull the battery.

7. Replace the battery.

8. Hold the joystick button in and power up. Your should be at the fastboot screen.

9. Press power once and wait for the phone to run through it's attempts to load the ".png" files, etc.

10. When you're back to the boot menu, select "Recovery" by pushing the volume down key once. DON'T PUSH POWER YET.

11. Get the USB cable in your hand, ready to insert it into the connector on the phone.

12. AT THE SAME TIME, insert the USB cable into the phone and press the Power button on the phone.

13. Once you're in recovery, try "adb devices" from the computer. You should see your device listed. At this point you're in and you can run the rooting steps from the original post.

14. If you DON'T see your device listed, reboot your phone into normal mode and follow all the steps again. It usually only takes one or two tries for me to get in this way.

I'm not sure why this works. I think all the playing around with navigator and the browser loads some kind of cache with data that is still there when you boot into recovery because you pulled the battery instead of rebooting. This data does something to lengthen the window on the race condition and makes it possible to get ADB running in recovery. At least that's my theory... Who cares as long as it works right? All I know is, if I don't do those things on the phone before I pull the battery, it NEVER works. If I do, it works almost every time. GOOD LUCK!