yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] seanzer:
So, it seems like the key to the hack is getting the adb drivers to load while the phone is in recovery.

I've been wondering though.. how much of this is the computer's fault and how much is dependent on the DINC? Basically.. can we force the drivers to load from the computer?

Is it possible that this is just a random occurrence and it doesn't really matter what sd card or what we do with the USB?

I have NOT been successful with my incredible (Hboot v0.77) using either a 4gb class 4 sdcard and the 2gb sandisk that came with the phone. I've tried all the methods in this forum for a couple days now.. I'm going to catch up on sleep.

edit: i've tried using ubuntu 32bit and windows 7 32bit.
[Droid Incredible Android Development] elborak:
No, the key is to get the phone to not shut down the adb server while in recovery. The host side has nothing to do with it, it's all timing on the phone side.

I tried at least 50 times on one SD card, no go. I tried at least 25 on another, no go. Found a third I'd forgotten I had, hit it the first try. Since then I've been 3/6 in getting adb in recovery on this 3rd card.

So while not a statistical certainty, clearly there are timing/race issues involved with the boot process on the Incredible which are sensitive to exact SD card being used. Not saying that it's the only variable, but it's clearly one of them and likely the easiest one to control.

So I'd advise to not waste your time playing with different hosts/drivers/USB cables etc. Be persistent and try every microSD card you can get your hands on.
[Droid Incredible Android Development] TNS201:
What seemed to work for me 4 times now was loading bootloader by pressing power + optical button with no USB plugged in. Then starting my adb shell loop. Then go to the screen where you choose recovery and have recovery selected and right as you press power to select recovery immediately plug in your USB cable into the phone. I usually have it 1/2 way plugged in so I just push it in to click it in. This is no guarantee for me either, but usually after several tries and battery pulls later I get it. I think the proper timing is either exactly the same time you press power, or just slightly after. I also noticed on my last shot I didn't have my SD card in, so I pushed it in at the white incredible screen and then I waited for like 30seconds to a minute or so before I saw exec '/system/bin/sh' failed: No such file or directory (2) -, so it didn't do it the second I got into recovery like some people get.

I do thnk you are right about the driver loading or it might just be the phone being detected. I noticed I could hear the noises windows makes like when you plug or unplug a usb device. Hearing that over and over and at certain times when booting and in bootloader.
[Droid Incredible Android Development] CaptainTaco:
The most reliable steps so far for me have been you_eeeeeeidiots method, paring you associate the "Android 1.0" device with the android_winusb.inf driver (Should install if you edited the inf file). Other methods have worked for me on and off, but you_eeeeeediots method worked every time for me.

you_eeeeeeidiots method
[Droid Incredible Android Development] HolyGrail:
So far so good Captain, I think I hit a snag tho.

on this step

# busybox --install -s /system/xbin

it gives me

# busybox --install -s /system/xbin

busybox: not found

is this normal?

Also after this, how can test it so you know you installed it right?

Thanks for the help man. :)
[Droid Incredible Android Development] rynosaur:
you need to:

cd /
ls busybox*

If the adb/the phone comes back with busybox from "/", ie root directory, then you can install from the root directory with that command. If not, then you'll have to exit shell and "adb push ./busybox* ./" If your busybox came with an extension, it'll show up with "ls" command then you need to append that to the "busybox(?) install -s /system/xbin" command.

I believe the phone will have to be rebooted for .ash to be updated to include busybox in its command path, at which point you can run any busybox command from anywhere in a Terminal Emulator or even adb shell.
[Droid Incredible Android Development] fikal1:
MetaMorph

Now that I have busybox and superuser correctly installed. I downloaded MetaMorph and seems to crash on the check. I am guessing it is too soon for MetaMorph. Am I correct?
[Droid Incredible Android Development] veli69:
I dunno I hear my computer connect to the device found after the phone is in recovery. I think this is my problem..
[Droid Incredible Android Development] TNS201:
Even if it did work, it would be a bad idea to do something like that now because you could easily brick your phone with it. Since we don't have the ability to make and restore backups of our phones, **** could hit the fan.
[Droid Incredible Android Development] gonella:
hero

has anyone test in HTC HERO this solution???

thanks:):):):):)
[Droid Incredible Android Development] andrew53517:
Is this the final root process? Or is the unrevoked team currently working on an easier process to root the incredible?

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Incredible Android Development] rynosaur:
Exactly . . . worrying about drivers and when to plug in the cord and how to pull up recovery using what buttons is a waste of time, IMO.

I take your assertions one step further with this theory:

The DI is checking or even just mounting the SDcard on recovery start. What's it checking for or why it delays and why, I haven't the foggiest but there are certain cards/formats (maybe even file loads) that cause a delay in this process and while recovery pauses on this step, console permissions OR the ADB-USB interface is held open so that the client/phone will respond. If we can better understand what in/on the sdcard hangs-up the recovery/SDcard initialization process, we can probably make it iron-clad how and when adb shell access is achieved.

When users are seeing the host side file system suddenly mount two DI storage volumes (sdcard and internal 8gb storage), that means the card initialization and recovery startup process is complete. I am sure that if an enterprising DI-rooted owner did an adb kill-server after getting adb shell, the phone would again offer its storage volumes up to the host OS -- so seeing those two mount is NOT an indicator of host-side failure, it's a normal result of /recovery partition starting up. My guess is the way to solve the rooting process is to really glitch fuseblk, the FS responsible for mounting sdcard volumes on Android devices (just a novice stab in the dark!) :D
[Droid Incredible Android Development] blw1230:
Jesus Christ I hope they're working on an easier method. As soon as they do, I will be donating immediately. I would have already but I can't seem to get root. Anyone have word on developing a "one click" method like what was done with the evo?

edit: In no way, shape or form is my frustration directed at unrevoked. I'm just frustrated with the method/sd card/phone/computer. haha
[Droid Incredible Android Development] deadlinguo:
Running into problems trying to get root permanent.

When I type this command

adb shell

su

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

I get back this error message:

cannot create /system/bin/su: text busy

anyone know what that means?
[Droid Incredible Android Development] andrew53517:
Lmao, it doesn't have to be one-click, but it sure better be a hell of a lot easier than this! Lol, I kept failing at it so I quit for now :( I'm waiting till they make something easier till I try again....or that's what I say for now lol.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Incredible Android Development] doom22:
the 10 minute video to root is actually faily easy, i just got mine rooted in about 20. I ran into a couple problems but it worked out perfect.
[Droid Incredible Android Development] SeanRinVA:
Super bummed...doesn't work for me. I've tried with a Transcend 8GB Class 6 card. I'll try Monday with the shipped 2GB card.
[Droid Incredible Android Development] rynosaur:
Please report your card specs in the Successful root thread then, thanks!
[Droid Incredible Android Development] CaptainTaco:
The rooting of the phone still has some limitations, IE the filesystem is still locked down, and several other areas, keys etc. MetaMorph will fail check, and I agree with another post above in that MetaMorph would probably be a bad idea to run in general at this point.

A good way to test is to try some programs that require root, or possibly that use busybox as well, but don't alter the kernel or flash the recovery, as these options are still unavailable to us until we get some workarounds. TitaniumBackup is a good program to try, as well as RootExplorer. Both these programs utilize root (through SuperUser.apk) as well as BusyBox.
[Droid Incredible Android Development] vzw:
Omg I have been doing this for I don't even know how many hours now... I can't get passed adb shell no matter what I do... I have checked all methods I can get it to list the device right before the last ding going into reovery but it lists it as

HT04GHJ02832 Offline

Then the next ding comes along and gives

List of devices attatched

[ NOTHING HERE ]

Uhg...

just so frustrated.

I have looked at the 10 min video and others on youtube and not one single thing is helping....

I am win 7 premium running cmd in admin mode

HElp ;)
[Droid Incredible Android Development] syrguy1969:
Will people who have successfully rooted their Incredible please please please answer one question? I have had mixed answers on this, and I would like to know for sure before I try this.

Will rooting by the directions in here (or any others listed in the thread) wipe the phone clean? I have gotten my Inc to a point that I love the setup and don't rally want to start from scratch until I can install + use Titanium backup (from what I can tell that is as close to a WM backup app that we can get to in Android).

Thanks all, your answers will help me decide tonight!!! :D
[Droid Incredible Android Development] rynosaur:
No, rooting done right will not wipe your phone.

Besides, VZ's backup, together with Sense's settings backup, together with Google's app/contacts/calendar cloud pretty much has you covered. In any case, a wipe at this point WILL erase your root, not the other way around, get it?
[Droid Incredible Android Development] mycomputerisjunk:
Nop. I rooted and did not loose anything.
[Droid Incredible Android Development] Solomon2122:
Solomon2122

For anyone having problems getting adb to work while in recovery, I sat down for hours and tried over and over on my 16gb and 2gb SanDisk and never did get it to work, I went to the local walmart and bought a 2gb PNY micro SD card for $9.95 put it in and now every time it works! Thanks goes out to everyone involved in rooting the phone!!!
[Droid Incredible Android Development] elborak:
Agreed. I'm using TitaniumBackup, RootExplorer, & Lamppu; all working well.
[Droid Incredible Android Development] ilinfinityil:
I've asked this in the chat and I'll ask here:

There's 2 races, right? It seems like with all of this SD talk and timing that it's all based on putting load onto the phone at a certain time. Is there any way to force load onto the phone during this period of time? It'd almost guarantee adb recovery access every time the phone was put into recovery mode.
[Droid Incredible Android Development] tatman28:
LMAO.....I got fed up and went to walmart today too and bought that cheap $9.95 2gb PNY micro SD card also. It works everytime!! I almost fell out of my chair when I put it in my phone and 5 minutes later I was golden :)
[Droid Incredible Android Development] rulevoid:
Android Wifi Tether works great with the bin file linked. Even with 2.0.5 pre2. BUT.... Titanium backup says it couldn't acquire root.... any ideas?
[Droid Incredible Android Development] trunksta:
Bout to do the same thing myself... SanDisk cards just suck for this procedure i think. ive tried 5 cards on 2 diff pcs, windows 7 x64, 32, win xp and mac osx every little trick possible.

ill post update if this works :)

edit1: FIRST TRY w/ the $9.98 2gb PNY card... this is the one people!!!!!

edit2: All i did was pull battery with usb plugged in, run my loop, then boot into recovery... did not even put the card in to format or anything, went straight from the package into my phone and boom first try it worked like a charm. even pushing the update was easy. Now ive got superuser installed, but nothing else yet. anyone else out there ripping their hair out over this go spend 10 bucks on a card at walmart and save yourself hours of BS.
[Droid Incredible Android Development] psmafia:
For me sandisk cards only work with the click in and out during boot method. ~1/10 success for me with sandisk 2gb and 16gb, while my 2gb Kingston won't work at all (all class 2).
[Droid Incredible Android Development] syrguy1969:
Thanks for the replies...I didn't think so, but I had heard from a couple others that it does, so I had to ask!
[Droid Incredible Android Development] tcberg2010:
Same thing happened to me with titanium backup. I clicked "having problems" and it downloaded the latest busybox, after that titanium aquired root.

EDIT: sandisk worked for me, took about an hour, but once I got adb in recovery it was cake.
[Droid Incredible Android Development] R1lover:
once the driver is setup on yoru machine IT WILL WORK everytime.... ever with any card lol
[Droid Incredible Android Development] rulevoid:
Thanks! That did the trick.
[Droid Incredible Android Development] elborak:
Absolutely untrue.
[Droid Incredible Android Development] nixon7606:
PNY 2gb

I just went to kmart and purchased the 2gb PNY for 11.99 and it worked!!

PEOPLE GO GET YOURSELF A PNY 2GB!
[Droid Incredible Android Development] R1lover:
I would take a video and show you.... but it's not that important to me... to waste the time.

I can and have repeated root over 50 times on three different phones with many different cards.... this was all in an attempt to find the issue for all of you... the issue is, once you have the proper drivers installed... it will work every time.

end of story.
[Droid Incredible Android Development] contagous:
and those drivers are? I cant seem to get into adb recovery at all, using any card, im on Vista 32
[Droid Incredible Android Development] rynosaur:
He's talking about a modified form of the ADB Composite driver for Windows released in Android API rel 6 -- part of the whole SDK package that Google now distributes live over the internet using AVG updater, rather than in one big hunk like they used to--not that the old drivers in those old releases work well anymore. The driver modification instructions to insert this stuff in the .inf file using a plain text editor:

32-bit/x86:

;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

64-bit/x64:

;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

just copy and paste that stuff after the Nexus One entries. Note, this will make the driver unsigned, which Win7 really does not like, but I imagine Vista x86 will let you away with several UAC dialog-box sterm warnings ;)
[Droid Incredible Android Development] n0-0ne:
I'm doing this tomorrow, will report back.
[Droid Incredible Android Development] vapehooka:
i can send adb commands all day from the command prompt while in win7 32 but have had zero success with 3days of trying with multi-able cards. And on vista xpsp3 and the ubuntu way all no luck. I have not tried the pny 2 g yet but will tonight and will post my results. I keep getting hard disks after the ! prompt screen. I lose adb composite devices as the white htc screen goes on as it vibrates. on all my windows systems.

.77 bootloader

If someone who has had adb shell success try on a virgin cpu from scratch and note what drivers the installed in the process.

im unsure if the usb trick and or card pull trick is the way we need to try sense others have done without.
[Droid Incredible Android Development] mandroid2010:
i have been trying all day cant get it to work. I wish i knew where to find all the right drivers:confused:
[Droid Incredible Android Development] n0-0ne:
done this, didn't work any different, but do me a favor and tell me what you have in device manager when in recovery mode. if it's only disk drives then we have the same and it's not a drivers issues. I've yet to see anyone mention what is listed in device manager when in recovery, because no matter what driver I have installed it doesn't change anything.
[Droid Incredible Android Development] psmafia:
Then how do you explain the variation in success for different SD cards when working in Linux and Mac which don't need drivers to use adb with Android? I can attest to this using a triple boot laptop and 5 different SD cards, three of which refused to get adb in recovery.

End of story.
[Droid Incredible Android Development] contagous:
Oh i've already tried this, does nothing for me, using Vista 32 couple of different cards
[Droid Incredible Android Development] jonnybueno:
Are you sure??? I have standard sdk drivers installed and things vary for me... Ive never had any trouble getting adb shell to run, but it never works the first time for me. It seems to vary everytime I do it, and the only variable I can think of is my timing.
[Droid Incredible Android Development] ihtfp69:
If you have it working while in recovery, you will see "Android Phone" in your Device Manager. I could never get it working using the HTC sync drivers, only the ones from Google.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Incredible Android Development] vapehooka:
Ok so I got root using this trick so to speak.

When you launch recovery and get the white HTC Screen, quickly remove the SD card and right before the black screen comes up (you will hear the pc beap recognizing usb) put it back in and bang there she was.

followed this from android and worked perfect with a kingston 2 g right at the sound on the black screen push the card back in with spring already pushed in.

bingo
[Droid Incredible Android Development] trunksta:
This is just plain not true. Yes you do need the drivers but the card your using has a BIG effect on it.
[Droid Incredible Android Development] phoenx06:
Sorry for being ignorant on the subject, but I currently have mine rooted, and keeps su after reboot, have wireless-tether working, etc. What I'm wondering, is I keep reading about everyone installing something called busybox. I used the 10 minute video method, and I don't recall doing that. Am I missing out on anything by not doing this? Or did I and I didn't know it?
[Droid Incredible Android Development] contagous:
As far as I know, thats what the 1.bat file you run does for you, he automated it as much as he could.
[Droid Incredible Android Development] dreamersipaq:
A little Clarification

Ok... so all of the people that achieved root. Maybe I'm over thinking this, BUT: When you go between the Bootloader and Recovery, the type of USB connection from the phone to the PC changes. You can tell because you hear the "disconnect" ding followed by the "connect" ding. SO.... this is my train of thought. I ran the SDK, and installed the drivers. Modified the .inf to contain the THREE different types of connections. So when I'm in Bootloader, my Device Manager shows "ADB Bootloader Interface" and when I'm in regularly, it shows "ADB Composite Interface". That said. If I run "adb devices" in regular mode I get a device returned back to me. If I run in Bootloader or Recovery I get nothing. I an starting to think that it's just that ADB does not sense the device unless it's booted. However, Windows does sense it for sure, and it does change the connection type between the "adb bootloader interface" and the two disk drives that we can't access. I'm not sure how a SD card can affect that, but I feel like what we're really racing is the bootloader/recovery bootup to the PC's loading and unloading of drivers. But I have no way to test that. Perhaps the 2GB PNY is so SLOW to read, but the drivers are loaded in Windows BEFORE the INC. is finished booting recovery? Any ideas would be appreciated. I refuse to believe that we can't recreate this on any card. It's just a matter of figuring out what's racing what, and how to use that to our advantage. I also strongly feel like its a connection issue between phone and PC, and somehow the cards are slowing it down. ANY IDEAS?
[Droid Incredible Android Development] b00sted:
batch file just moves stuff to the SD card, it did not setup busybox at all. if you used the video and want busybox installed you need to reroot the phone or least get it into adb recovery again lol

this is what is in the bat file
[Droid Incredible Android Development] contagous:
oh ok, I haven't managed to get the thing rooted yet, was just commenting what i thought, thanks for correcting me :)
[Droid Incredible Android Development] phoenx06:
Hey, update guys. I apparently have busybox up and running now. I did not have to re-root the phone either. I installed Titanium backup from the market and clicked "Problems?" and it put a newer version of busybox onthe sd and Titanium now works.
[Droid Incredible Android Development] elborak:
Yeah, he's full of it. He knows more than the guys who actually found this exploit on the IRC channel (who cannot get it to happen consistently on every card). And he could show us all his magic, but he's not interested.

Yeah... right.
[Droid Incredible Android Development] fenningenarius:
If I root my phone will that enable me to replace the HTC contacts and/or calendar apps with the vanilla android versions?
[Droid Incredible Android Development] seitz:
Does this actually work? I installed a version of this widget and it doesn't show up under the + WIdget menu.
[Droid Incredible Android Development] zeke1988:
i have no idea what driver you guys talking about. i only installed the driver i found inside my Incredible internal storage. its called HTC Sync.
[Droid Incredible Android Development] mejdam:
yep, those are the same ones i loaded and worked just fine. Both on Win7 64bit computer and WinXP 32bit
[Droid Incredible Android Development] CaptainTaco:
TitaniumBackup will install a version of BusyBox on your sdcard for its own purposes, this will not be associated with your PATH and no other application, unless specifically programmed to do so by the developer (Highly unlikely), will be able to use it. In other words, it's fine if the TitaniumBackup is the only App you plan on running that requires busybox. For busybox to be properly installed, and associated with your path, some addition to the /system partition has to be made, be it in the form of hard or soft links to the busybox file. To do this, you must be in recovery for mounting the filesystem outside of recovery is still not an option.
[Droid Incredible Android Development] CaptainTaco:
the HTC sync drivers work for some, but many people had issues with using them and getting adb to work in recovery. Rather than add one more "maybe" factor into the already pretty "maybe" factored rooting process, aka the hit or miss because of your sdcard..., you may just want to use the proper usb3 driver found in the android_SDK. If you don't know what driver that is read this post (post 602)

Yes it may work with using the htc sync driver, but it's probably better to eliminate as many error factors as possible.