yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] jdmba:
Anyone actually in contact?!?!?

While this thread is now pretty much ... well ... not entirely useful, due to its size; does anyone know the Unrevoked team? There is some good stuff buried in this thread (such as better ways to deal with the race condition; and clearer ways to apply su), but the unrevoked wiki hasn't changed one bit.

While they may not care what the paeons here say (I mean, they did crack it, and I am sure they want to finish packaging), I don't know if they actually KNOW of some of the advances made in the middle of this overgrown thread.

Anyone know if they are watching/reading and/or if there is a way to contact them to let them know?
[Droid Incredible Android Development] heavensblade23:
Yes, people from IRC are watching. No one has updated the wiki though.
[Droid Incredible Android Development] TNS201:
How can you change this option?

thanks
[Droid Incredible Android Development] rynosaur:
My guess is they're working on a more iron-clad method instead of trying to change the drapes on the titanic, so to speak--not that I don't appreciate their hours of work or the many contributors who gave us add-on tips. Of course, if any method had worked for me, my attitude would probably be: where's my Froyo??, not god, this is clunky. I blame no one but HTC and VZ for this, curses!!! ;)
[Droid Incredible Android Development] jitajt:
yes I have it set to ask every time, while I have the phone on and connected adb works fine (i send and receive responses) but once it goes into recovery it shows up as two disk drives. I tried it on a virgin windows 7 professional (no extra drivers installed at all) and I put the usb drivers over from my laptop and put it in bootloader, installed drivers after I pointed it in the right direction, went to recovery and it picked it up as two disk drives again. it just will not pick it up as an adb interface. it could be the cable (using the one that came with it) or it could be my phone. I am out of ideas and I think I will just wait until an AIO package rolls out.
[Droid Incredible Android Development] YMAA:
I just got it working!

What worked for me was following the instructions on androidforums which I found linked here. What worked for me was Method 1, a modified version of you_eeeeeediot's original instructions. Also, I found I had to use the free Sandisk 2GB SD card I got from Verizon to get the best results. The Sandisk 16GB Class 2 I use 24/7 I only got to work once.

What also helped was the suggestion by Heavensblade to wait just a little longer to push the payload. Make sure it says it's checking the signature before pushing. And if you mess up, you have to reformat the SD card and try again from scratch. At least, I had to.

I was on Windows 7 x64 when I did this, btw.
[Droid Incredible Android Development] pozer69:
It can't be an sd card issue then. I have the same exact sd card and I can't get it to work..."free Sandisk 2GB SD card I got from Verizon"
[Droid Incredible Android Development] fikal1:
busybox error

adb push busybox /sdcard/busybox
adb shell
$ su
# export PATH=$PATH:/system/bin
# cd /system/xbin (((or /system/bin I personally always use xbin)))
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# rm /sdcard/busybox

When I enter # cat /sdcard/busybox > busybox I get the error cannot create busybox: read-only file system.

I have entered the permissions after getting root and am not sure what I am doing wrong.
[Droid Incredible Android Development] R1lover:
I agree, it's not a card issue, it's all about making sure you have all the proper drivers installed and working properly.

It's pretty simple.... after making sure all the drivers are working as they should, I can run root in about 2 minutes and repeat it every single time without error.

Start with the latest sdk & usb drivers from google... them make sure and edit the driver file for the incredible... then make sure you see an android 1.0 driver and that it installs correctly. If you see an htc driver it's not going to work right.

to test your drivers put the phone in debug mode and type adb devices... it should show the phone and not show "offline" if it does show "offline" then you have a driver issue.
[Droid Incredible Android Development] maxyoda:
Worked on the first try (thanks to post 201)

Worked on the first try following the instructions in post 201. Removed CityID and now have Wifi tethering working. Just tethered my ipad!
[Droid Incredible Android Development] :
woot i was able to get superuser and busy box installed successfully...however metamorph freezes the phone up during the checking process.
[Droid Incredible Android Development] DigitalDementia:
Ok question I get the Android 1.0 bit but it won't let me choose the drivers fails automatically what am I doing wrong? What did you do to get it to work? I choose the folder with the drivers in it is there anywhere specific I need to put the modified file? it says android_winusb it's 4kb and has a notepad type deal and a gear for an icon. (Also if it helps I'm using XP SP3 right now.)
[Droid Incredible Android Development] R1lover:
You will have to follow the root process all over again... the complete process... once you do and gain su access it will work.
[Droid Incredible Android Development] DigitalDementia:
Anyone have any help regarding my post ^up there^ any insight would be greatly appreciated, I know I can't obtain root if my device can't be recognized while being powered off. I can get it recognized while on but off is a no go.
[Droid Incredible Android Development] DigitalDementia:
You guys are killing me >.< where did everyone go?!
[Droid Incredible Android Development] hoovnick:
Ok, don't flame right away, but has anyone here tried this method or anything similar on the Eris? I've tried every set of instructions (as close as possible due to subtle phone differences) listed here and still no adb in recovery. I get the comp to recognize it as a hard disk, but that's about it. All drivers are up to date. Using xp sp2. Any and all ideas would be helpful. Thanks in advance.
[Droid Incredible Android Development] DigitalDementia:
The Eris has already achieved root. In a much more friendly way from what I understand.
[Droid Incredible Android Development] DigitalDementia:
I also don't think this process will work since it was not designed for the Eris nor was this bug found in the Eris root process.
[Droid Incredible Android Development] hoovnick:
Well, the people that had more patience than me achieved root. I however jumped the gun and am stuck with a locked bootloader S-ON. I get the loop to kind of skip sometimes, but that's the only glimmer of hope. Thanks anyway, I'll exit the thread so actual Incredible users can troubleshoot and hopefully all can root. Good luck all!
[Droid Incredible Android Development] giantcrazy:
I was having a similar problem until I followed the instructions in this post:

http://xdaforums.com/showpost.php?p=6779087&postcount=493

Did you try modifying the .inf file? Before I did, it didn't recognize the DI in recovery, afterward, worked like a charm.

Also, not sure if it's necessary, but I also installed the HTC Sync app and got it working before I started.

BTW: Not sure what you mean by 'recognized while off' - when it's off, it's not going to be recognized. After all, it's off! :)
[Droid Incredible Android Development] b00sted:
i haved tried this now 50 times with no luck.. not to sound like a complete idiot but can you expand upon this? like when you have the phone on is it fully on or when it is booting? do you have debugging on? did you wipe ur phone first etc? any help would be great at this point.
[Droid Incredible Android Development] stanfna:
turn the phone on...like...when you are going to use it....like to send an email...browse the web...make a call....whatever. just turn it on and mess around with it for a bit...like the first day you bought it ;-)

no USB cable plugged in. i have debugging on and did not wipe my phone.

once you have your phone as normal...then just pull the battery out. don't turn it off or anything....just flip it over, pull out the battery, stand on one leg, put the battery back in and follow the instructions in previous posts. :D

it is not a fool proof method...just works for me....and some others.

EDIT: sorry if that sounded rude...I am a few beers into the evening! ha ha Cheers!!:D

and good luck!
[Droid Incredible Android Development] libbycm:
More repeatable root method!

So, for those who are still having issues, Centsy over @ androidforums put up this other method for getting adb to run in recovery mode... I failed in all other methods and got it on first try doing this:

This must be the most kludgy hack for root ever, lol, but it works! Got cityID removed, setCPU working (no overclock yet of course) and a few other root aps I like (adfree, etc.)

Getting ADB to run in recovery was a PITA as it was, but getting timing right between when you run update.zip in recovery and push the payload zip is as much of a PITA. Hint here: if you don't get timing right, just push ota.zip again, then try the "install update.zip/push payload.zip" on phone; no need to start all over from beginning. What this looks to be doing is "tricking" recovery into thinking it is loading an official signed update during the verification process, and at just the right moment before it loads it, you do a "swicharoo" with the "hacked" payload so it gets installed instead...

Good luck!
[Droid Incredible Android Development] deadlinguo:
Still trying to get adb shell working.

I can get adb devices to find my phone when it's booted up normally, but not when I'm in recovery mode. Does that sound right?
[Droid Incredible Android Development] opcode1300:
did AdFree work out of the box and did you use the superuser permissions?
[Droid Incredible Android Development] ihyln:
Finally figured out what was causing weird issues with permissions and such. Last night after I updated the recovery I swapped SD cards from my girlfriends to mine. Somehow, I was able to copy stuff and keep root persistence but I ran into permissions problems. I stole her SD card and now everything works as it should. I finally have wifi tethering which I wanted for quite some time.
[Droid Incredible Android Development] b00sted:
i think i may cry.. no matter that i do or change this wont happen for me
[Droid Incredible Android Development] jitajt:
I am in the same boat, I am just going to have to wait until they come out with a fool proof method
[Droid Incredible Android Development] evilone1969:
me too :( nothin working, wipe away my tears and wait with the rest :(

thanks to all that are helping with this, nice to finally have a breakthrough of ANY kind :)

/bow
[Droid Incredible Android Development] dnchattan:
I have very likely tried the process over 500 times, probably not far from 1000 times- trying every suggestion here.

My final solution (on first try) was:

1. On a fresh system (dell e6400 laptop), plug in the phone (normal user mode) and install the ANDROID drivers (not htc sync) when prompted for the ADB driver.

2. Start adb loop script

3. Pull the battery, never touched the USB cable

4. Put the battery back in, hold dpad button and press power to boot into HBOOT (0.77 here)

5. Select fastboot

6. Select recovery

7. Immediately begin popping the sd card in and out- just clicking it back and forth is enough. I would focus on keeping a steady pace more than doing it as fast as possible so your fingers don't slip.

8. <insert jaw drop here when the loop reports the exec '/system/bin/sh' failed: No such file or directory (2) message>

9. Select update.zip (VolDn, Power) - fails

10. Push busybox and ota

11. Prep cmd for payload zip, execute 0.5 seconds after "verifying" message appears. (if fail, re-push OTA and try again)

12. Root!

Used a 2GB Kingston Class 2 card.
[Droid Incredible Android Development] Ffej5647:
Same with me :( I just don't care anymore but oh well....who knows when there will be another method though. I tried 5 different cards and 2 different Incredibles...and nothing. So oh well its all over for me until another method comes about.
[Droid Incredible Android Development] busterbrown77:
Ah, and the root issues begin...

Ok, I was able to get the phone rooted, got superuser functioning, and installed busybox.... but i have one big problem, it seems to have done something to the phone. I no longer have ANY notification sounds. only sd card notifications. Ringtones are 50/50, and my settings app crashes constantly... mostly when enabling/disabling mobile network, wifi, bluetooth, and gps.. what can i do to fix this? If anything i just want notification sounds back... HELP

EDIT:

If anyone has issues with ringtones, what happens is the defaults for the htc apps are messed up. fix it by going into apps, messages, and settings, and clearing data or reseting. then go into the messages app, then hit menu, go to settings, and scroll to recieved message and set your preferences...

EDIT 2:

Nope... still not 100% fixed.... audible selection does not work, sent msg notifications do not work period, and will not vibrate when msg is recived... dont get it.... any ideas?
[Droid Incredible Android Development] rgsilvers:
Help for Mac

I totally understand this process.. But I have a mac and cant seem to get the stuff to run on terminal.

are there different commands??

Can somone give me the commands so I can cut and paste them!!

Thanks!!!!
[Droid Incredible Android Development] busterbrown77:
The only big diff is that the mac terminal requires the full path at all times.... lets say you have adb in C:\sdk\

you would type

cd C:\sdk\

then

C:\sdk\adb shell

..... get it?
[Droid Incredible Android Development] onodontbescurred:
finally after 2 days of non stop trying..... the clicking of the sdcard in and out method worked for me with a motorola droid sd card.
[Droid Incredible Android Development] larsdennert:
F#&K I spent hours on this trying every method and nothing then swapped the PNY 2gig card out of my WM phone AND IT WORKED FIRST TIME ALL THE WAY THROUGH. It's either the cards or the Inc does something (stores something) on the card that messes it up. I put the fresh card in while it was off and never let the phone boot normally with it.

Thanks ALL YA.
[Droid Incredible Android Development] DigitalDementia:
Ok everyone, I realize a lot of you are having issues achieving root and so was I until now! Root has been acquired in two tries (I'll explain why two).

The first thing I did was follow the video tutorial here http://androidforums.com/all-things-root-incredible/99437-video-10min-root-complete-guide.html to the T and it failed error: no device detected so I remember seeing a thread involving pushing in and out your SD card so take the steps in the video up until going into recovery when you go into recovery start pushing your SD card in and out relatively fast (approximately every half second maybe a little faster) while doing that I got into ADB shell.

This was using a 2gb transcend SD card on Windows xp out of date comp. Post your results to this method. Also dl the file posted in that thread under video.
[Droid Incredible Android Development] pozer69:
I have read a lot of people with PNY cards have been able to accomplish root, neither of my two SanDisk cards have worked. Anyone with a PNY card and couldn't get this to work?
[Droid Incredible Android Development] pozer69:
Here are some screen shots of my device manager...I have not received root yet.

In the first pic, you can see the Android 1.0 in DM, this is when FastBoot launches.

In the sec pic, Android 1.0 disappears when BootLoader launches and replaces with 2 HDDs
[Droid Incredible Android Development] skaterA223:
I have a 8GB PNY SDHC and i tried all methods, even switch computers...but no luck. i can wait haha
[Droid Incredible Android Development] krelvinaz:
I heard someone with a PNY card that had no success until he used the connection via a hub.

It was a 2gb class 4 card though.
[Droid Incredible Android Development] jitajt:
that is the same exact thing mine is doing, I tried installing win 7 fresh and it still came up with the same thing, I didn't have drivers installed or anything.
[Droid Incredible Android Development] rynosaur:
I keep saying but no one seems to believe me: this is a symptom of failing to gain adb shell in recovery not the cause. Just like quacking doesn't necessarily make you a duck, Windows mounting your int storage&sdcard doesn't necessarily mean windows is f--ing up!

* No drivers --> FAIL --> Windows mounts what it can (storage volumes)

* adb shell process timeout due to bad timing and/or fast sdcard --> FAIL --> Windows mounts what it can (storage volumes)

**As opposed to**

* Driver OK, Timing/SDcard OK --> Success --> Windows Mounts ADB Interface which is now available due to exploit

So don't mistake a symptom for the cause and waste your time! :o
[Droid Incredible Android Development] HolyGrail:
After trying everything, and never getting it to work I figured it out, an most likely what most of the problem some are having. It took a combination of things from other users in the forums. I'm finishing things up, but will post a detail walk through of all the steps it took. :)
[Droid Incredible Android Development] jitajt:
then explain why a lot of people that have root did NOT have anything show up in device manager EXCEPT adb composit interface. and people that can't root the DI has two USB disk devices show up and NO adb composite interface. if what you are saying is true then when in recvery we might have those USB disk devices show up but also have the adb composite interface showing up, but we don't. while the phone is booted up as usual I can use adb to send comands and get responses,(which means I have the correct drivers) but as soon as I go into bootloader adb composite device never shows up again, and in order for anyone to interupt it while it is going from bootlaoder to recovery you have to have it show up as adb composite interface otherwise you can send commands all day and nothing will happen. just like what is happening with everyone else with the same problem. and it has been proven that you don't have to race it, people are achieving root without running loops, and they can waiting 20 seconds after recovery mode to send the adb shell command. and no one said that windows is f*%#kin up in fact I don't read anywhere in here that says windows is f*&^kin up, it is the incredible not mounting correctly while in recovery, maybe it is the cable or it could just be the device. if I am wrong I will admit it.
[Droid Incredible Android Development] gladesmellzgood:
Finally!

I finally got root, I used this guide here from android forums. http://androidforums.com/all-things-root-incredible/98236-incredible-root-video.html

I also have an 8gb A-Data class 6 sd card.

I had to try like 50-100 times lol.
[Droid Incredible Android Development] rynosaur:
I really doubt that people can wait 20 seconds to send the "adb shell" once recovery has loaded and then succeed, every post I've seen indicates that the timing is brief and tight at best, as little as 50ms for response time. This exploit was discovered almost by chance. If we could all boot into recovery and shoot commands at adb at will, the devices would not be locked down beyond key signing and SPL: both of which are vulnerable now to those who have rooted. PLEASE don't take what I've said personally, I'm simply frustrated by many peoples' speculation that is misleading you and me and others like us--and I'm trying to prevent others from having to chase down blind alleys. If Unrevoked developed this process without specially modified drivers/HTC Sync/Crazy card ejection, etc, then you and I should be able to get it done as well. Point-in-case: Linux. Many have achieved root in linux with a very simple driver. Maybe you should try a linux installation or at the very least, a LiveCD. I'm about to go back and check my driver settings, Windows really muddies up this whole process with its layers of drivers and mount points.
[Droid Incredible Android Development] ihtfp69:
I finally go this working. Thanks to everyone for your helpful posts. I have a brand new Incredible with hboot .79 and a 8gb class 4 PNY card. I tried everything and could not get this working. I finally found the trick that worked for me. DO NOT INSTALL HTCSYNC. That is what was preventing me from getting adb working in recovery. A fresh computer using the usb driver supplied by Google and the hack in this thread, allowed me to get adb the first time in recovery. Also, you do not need those adb shell loops. It either works the first time you type adb shell, or it wont work at all. There is not a window or opportunity either. So fast typing wont help. I left my Device Manager up in Windows and saw the phone popup when I got into Recovery. I knew I was golden from there. Thanks everyone!! :D:D
[Droid Incredible Android Development] HolyGrail:
After trying many different ways to no avail, I got it to work this way.

It seems to be a combination of drivers and the sd card.

This is for users who already know most of the steps but still can't access Recovery, and have tried every single method with no success.

1. First thing, in your usb driver folder in your sdk dir, we need to edit the "android_winusb.inf"

Look for and add this under [Google.NTx86] and [Google.NTamd64] lines.

;

;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

and save. (credit goes to onodontbescurred)

2. Plug in the phone, an open device manager. Look for Android, click the drop down menu, right click and update the driver. Follow the steps and point it to "android_winusb.inf" If it asked you to restart just do it.

3. After restart have your phone plugged in go back to the device manager. Leave device manager on for the next steps.

Turn you phone off, with the usb still plugged in. Press and hold the optical Trackball and press power. Once in the menu press power again. Wait 5 seconds. At this time you will see in Android in the device manager just like before. Do step 2 again and update the driver. Yes you have to do this again. Do I know why, no. Does it work, yes. After you do this go ahead and tab down to recovery, wait, then hold down volume up and power, from here reboot the phone. We'll be back in a second.

4. Now from here, ether use another sd card, or copy your intire sdcard to the computer (you can copy everything back later).

5. Now from here your going to have to Take out your sdcard from your phone to Format your sdcard. To do this the right way, your going to have to use a card reader of some sort. The reason being is formatting the card through the phone won't work, because files are put back on by the phone. After you have your sd card in your reader, just right click on it and format it. I'm used the extra free 2gb sd card that came with the phone.

6. Leave the card out and turn off your phone. Then insert the sd card you formated back into the phone.

7. Open up cmd, and restart the loop.

8. Refollow the steps (credit to you_eeeeeediot @ XDA for the new procedure)Press and hold the optical Trackball and press power

Once in the menu press power again

Wait 20 seconds for it to do its bit

Plug USB in and wait another 10 seconds for your computer to detect the phone

press menu down to highlight "recovery"

Press power

wait 20 seconds

the screen should change from "error: device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -"

9. If succesful, you can follow Perunnerseth's instructions here, for working wifi tethering, etc....

http://www.incredibleforum.com/forum...art-added.html

10. Send me a Wonka Bar with a Golden Ticket.