yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] jonnybueno:
Ok, here's what i did...

1. open ONE command window

2. run from cmd window

adb reboot recovery

3. once in recovery run from cmd window

adb shell

4. if you get

error: device not found

then unplug your usb cable and plug it back in. repeat step 3 as necessary

5. if you dont get shell in 5 tries, press volume up+power to get text in recovery then hit power to reboot

6. as your phone is reboot keep pressing up and then enter in your command window to repeatedly run 'adb reboot recovery' from your history. your phone should reboot soon after you see the white 'HTC Incredible' splash screen

7. repeat steps 3 through 6. I've done this several times and it always works for me by the 4th try

8. if you get shell running, and you see move on to step 9

- exec '/system/bin/sh' failed: No such file or directory (2) -

\

9. press volume up+power on your phone for recovery interface then choose apply update.zip from sdcard

10. do these steps as described by http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery

#
Download the following three files:

*
http://www.unrevoked.com/incredible/payload-update.zip
*
http://www.shadowmite.com/temp/payload-update.zip (until further notice, use this link instead)
*
http://www.unrevoked.com/incredible/ota.zip
*
http://www.unrevoked.com/incredible/busybox
*
Keep these three files in the folder you'll be working with.

#
Press volume-up and power at the same time

*
A menu should appear.

#
Select update.zip by pressing power.

*
It should fail.

#
On the host, run adb push busybox /sdcard/busybox
#
On the host, run adb push ota.zip /sdcard/update.zip
#
On the host, prepare at your command prompt but do not press enter: adb push payload-update.zip /sdcard/update.zip
#
Select update.zip at the menu again by pressing power. Approximately half a second after it starts, press enter to run the second command!

*
If the timing was right, it should verify the legitimate update, but update with our hack, printing a message like “unrEVOked for Incredible”. Congratulations!

10. before rebooting, run

adb shell
su
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su

11. pull battery, dont reboot. you should now be as rooted as i am.

you can now run terminal with root prompt, but good luck using root apps.

some details on my setup:

POS acer laptop with core 2 duo and 4gb of ram.Windows7. moto droid usb cable and 16gb class 2 card. limited linux and windows knowledge.
[Droid Incredible Android Development] whiplash000:
In case any of you are wondering, the discussion is going on (moderated, so you probably can't post) on ##incredibleroot on freenode.

Here's a video one of them (lucky bastards) posted showing how he did it:

http://www.youtube.com/watch?v=Z8mheIkQ-1o

From what people are telling me, they seriously have NO idea why this works, and who it works for seems to be TOTALLY random...
[Droid Incredible Android Development] syrguy1969:
Let me ask this...as a total noobie to rooting and Android in general, in reading this thread I get mixed ideas about this root attempt.

I understand the devs are working on IRC and doing things we may not have seen mentioned here yet, but here goes.....

Boiling all this down, is this a strong source of developing the 'every-man's' root, or it this looking more like a fluke that may not help us 'non-dev' users?

Thanks for all info on this!!
[Droid Incredible Android Development] seitz:
I was #2 root, and it seems to be related to the size/make of the SD card.
[Droid Incredible Android Development] tcberg2010:
Is this permanent root or do you lose root when u restart phone as everyone is reporting?
[Droid Incredible Android Development] whiplash000:
Then by all means, share with us your make/model of SD card! :)

I tried my:

Sandisk 8gb microSD

Kingston 2gb microSD

And both didn't work.
[Droid Incredible Android Development] rynosaur:
You numbered your steps 9, 10, then 9 (again). Does this mean custom commands have to be issued within Unrevoked's directions, or AFTER then? Thanks.
[Droid Incredible Android Development] sethman408:
Sweet.. this seems to have fixed the permanency issues.

I can now adb shell and run su after reboot

Root explorer is working!!!!!!!!!
[Droid Incredible Android Development] jonnybueno:
I have root persistent through reboots. I can run adb shell with su when phone is on, but when trying to run shell from recovery i have to do that process over again

sorry, watching newborn while XDAing... fixed
[Droid Incredible Android Development] jonnybueno:
credit goes to user ozzeh on freenode who gave me those commands last night.
[Droid Incredible Android Development] sethman408:
Getting it to stick was my only problem...! Bring the recovery images!

I shall be donating now!
[Droid Incredible Android Development] rynosaur:
NP, thank you for bringing this solution to the forum. I wasn't going to root before you explained how to set su permissions up for good (hopefully) :D
[Droid Incredible Android Development] sethman408:
Drocap2 works like a charm too!
[Droid Incredible Android Development] jonnybueno:
it seems we are still quite aways off from having usable root though. permissions are off and I can't get busybox setup or superuser.apk installed. none of my root apps work right now and the best thing i can do right now is run a root shell in terminal on the phone or adb...

I've quit tinkering with root for the time being due to my lack of knowledge on linux permissions.
[Droid Incredible Android Development] you_eeeeeediot:
I have to second this. It's a great start though.
[Droid Incredible Android Development] suzook:
damn..no matter how many times i try...i cant get adb in recovery. WTF?
[Droid Incredible Android Development] sethman408:
Drocap2 and root explorer are working great for me.. havnt tried busybox install yet...
[Droid Incredible Android Development] you_eeeeeediot:
C:\>adb shell

$ su

# /sdcard/busybox --install

/sdcard/busybox: permission denied
[Droid Incredible Android Development] jonnybueno:
I can't:( get root explorer to actually mod anything in /system. Even after mounting as rw.

+1, ditto
[Droid Incredible Android Development] Hatman41:
IRC

I am getting Unresolved freenode:6667 ...freenode is the server?

***EDIT****

Bahh I found out the problem....verizon blocks IRC...is why I cannot connect...but I also had the wrong server port. I changed it to 7000 and it still was blocked.
[Droid Incredible Android Development] WoZeR:
Do i need to worry if windows is reporting that Android 1.0 driver is not found. This pops up when im in boot loader/Fastboot mode.
[Droid Incredible Android Development] Ohsaka:
Figured it out...
[Droid Incredible Android Development] sethman408:
Read a few posts back.. the getting it to persist after reboot has already been fixed.
[Droid Incredible Android Development] Ohsaka:
Here is another one taken from my other friend's Sprint EVO... Yes its a macbook we used to do the rooting...
[Droid Incredible Android Development] Ohsaka:
Figures... Oh well, I have to get back to real work now... Congrats Incredible owners!

Now that I have used Swype, I am willing to give up a physical keyboard for my phone. I may consider the Incredible...
[Droid Incredible Android Development] you_eeeeeediot:
Actually, managed to get busybox installed sort of.

C:\>adb push busybox /sdcard/busybox

C:\>adb shell

$ su

# mkdir /data/local/bin

# cat /sdcard/busybox /data/local/bin/busybox

# chmod 777 /data/local/bin/busybox

# /data/local/bin/busybox --install

All of the utils are installed there, I guess if I could get RW to the /system mount I could create all of the symbolic links inside of /system/bin.
[Droid Incredible Android Development] WoZeR:
I had to hack the inf again to include the bootloader driver.

In the android_winusb.inf make sure to have the following under [Google.NTx86] and [Google.NTamd64]

;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
[Droid Incredible Android Development] rynosaur:
Thank god our camera isn't smack in the middle of the phone like it is on the EVO, that's gonna cause a lot of scratched EVO lenses! ;)
[Droid Incredible Android Development] determinato_1969:
SUCCESS!!! I has root.

Thanks to the guys in the IRC channel for all the help. Who do I donate to?
[Droid Incredible Android Development] b00sted:
w w w.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery

look at the bottom of the page ;)
[Droid Incredible Android Development] WoZeR:
What do you have on your sdcard. Someone said it might have to do with the sdcard.
[Droid Incredible Android Development] JaydenR:
So far it seems you need a class 6 card for this to work.
[Droid Incredible Android Development] you_eeeeeediot:
I've got a Sandisk 8GB, class 2
[Droid Incredible Android Development] WoZeR:
Do you have a bunch of files on the card or is it mostly empty?
[Droid Incredible Android Development] you_eeeeeediot:
Some files on there, a couple of nandroid backups from my Nexus. Nothing relevant really. I'd be surprised if its SD card related..

Did you try my previous tip?

- Turn off phone

- Unplug USB cable

- Hold Optical track/Button, Press Power

- When in menu, hit Power (to boot FASTBOOT)

- Wait 20 seconds (until it tries to load everything it needs)

- Plug USB cable in, wait another 10 seconds for OS to catch up and detect

- Press Volume DOWN, once

- Start your 'adb shell' loop (via batch file posted in the thread)

- Press Power
[Droid Incredible Android Development] yourfriendwayned:
I have a Class 2 16gb hc and no luck
[Droid Incredible Android Development] WoZeR:
Yep, I've tried everything in this thread and nothing works.
[Droid Incredible Android Development] you_eeeeeediot:
Fire up Task Manager and kill every instance of 'adb.exe' running, then start from beginning.
[Droid Incredible Android Development] Ohsaka:
Would adding these two lines to the updater-script inside the payload-update.zip file fix the perm-root problem?

run_program("/system/bin/sh", "-c", "/system/bin/cat /system/bin/sh > /sbin/su");
set_perm(0, 0, 04755, "/sbin/su");
[B]run_program("/system/bin/sh", "-c", "/system/bin/cat /system/bin/sh > /system/bin/su");
set_perm(0, 0, 04755, "/system/bin/su");[/B]

ui_print("Writing su to /system/bin/su...");
package_extract_file("su", "/system/bin/su");

(bold is new)
[Droid Incredible Android Development] WoZeR:
Killed them all and did it again and still didn't work :(
[Droid Incredible Android Development] b00sted:
I feel your pain man, it is killing me that it is up to chance atm to get it lol
[Droid Incredible Android Development] SimonTuffGuy:
Mine as well. Followed the YouTube video posted, followed the instructions posted back a few pages, killed task, etc.

16 GB Class 2 card here as well (from original Droid).
[Droid Incredible Android Development] b00sted:
i am not sure what class my card is (I assume 2) and it is the one that came with the Inc. (2gb)
[Droid Incredible Android Development] pozer69:
Same here. I'm going to format my card and try again, if not then I will run out and but a new card just to try it.

8gb class 2 sandisk (BB Storm)
[Droid Incredible Android Development] klondike152:
I followed this to get ADB running in recovery. I have a 2gb class 2 card,

PS: it only has 100mb on it the rest is free
[Droid Incredible Android Development] polo2883:
So I have been trying for awhile and nothing at all.. I have tried a windows machine and my Macbook Pro and still can get ADB to run in recovery. For the Mac I have on terminal screen running while true; do ./adb shell; done. I have done the fast boot and booted into recovery and it does absolutely nothing.

At one point I do get $ in the terminal running adb shell but then it goes away when it reboots into recovery mode.
[Droid Incredible Android Development] yourfriendwayned:
lucky I cant get it to switch lines in prompt from device not rec.... me and my buddy have been trying for half hour...
[Droid Incredible Android Development] pozer69:
Is this confirmed?
[Droid Incredible Android Development] you_eeeeeediot:
Can't be. I've got a class 2 card and mine rooted fine.
[Droid Incredible Android Development] polo2883:
Look a couple lines above. Someone else used a class 2 and got it to work
[Droid Incredible Android Development] vVv mDaWg:
I don't think that it really has anything to do with the SD card size or class.

I've been trying this on 4 different Incredibles with 6 different SD cards all morning now and for some reason I have just not been lucky enough to get this to work at all.

I still think that it's just by chance that some people are getting it and others are not.
[Droid Incredible Android Development] yourfriendwayned:
its good to know the card doesn't matter but the again I wish I knew how to obtain quicker...
[Droid Incredible Android Development] kjbuente:
I can get adb in recovery, but when I try to push the files to the sd card after having the update.zip fail. I get a permission denied, and the files never get to the sd card.

btw, I used a old 1gb class 2 to get into adb with recovery. My sd card that came with the phone would not work.
[Droid Incredible Android Development] Ffej5647:
I wish i had that kind of luck.....im unlucky :'(
[Droid Incredible Android Development] mixpix405:
I've tried over and over. No luck for me, a computer technician, seasoned Android user and one who has taken advantage of root since day one with is devices... (by no means am I saying I am as smart as anyone here - just saying I'm not new to Android, rooting, or technology in general, especially cmd).

I've rebooted into recovery via 1) adb while phone is on and 2) bootloader

I've tried the method of a batch file constantly attempting to get adb shell, while in another window I adb reboot recovery. I never get anything but "error: device not found".

I've also tried the method with no loops, only attempting shell a few times in recovery, unplug phone, replug phone, repeat. Again, device not found.

I'm running Windows7, latest ADB, latest usb_driver download. Edited the driver .inf file for the Incredible, as follows:

[Google.NTx86]

(other devices here)

;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
[Google.NTamd64]

(other devices here)

;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

If anyone could help me out, I'd appreciate it. If not, I'll keep fighting with it, or wait until it gets packaged for failures like me :P

Thanks!
[Droid Incredible Android Development] krelvinaz:
You need to try to load update first (volume down once, and power). After it errors, you can then push the update.zip file.
[Droid Incredible Android Development] determinato_1969:
Not true. I got mine with a class 2.
[Droid Incredible Android Development] vVv mDaWg:
I feel your pain. I'm in the exact same boat as you right now. I've been at this for almost 6 hours now with 4 different Incredibles and absolutely no luck whatsoever. I've got the exact same information in my driver's inf file. I've tried on both Windows 7 and Mac OSX 10.6....

Maybe it's time to give linux a go for the hell of it...
[Droid Incredible Android Development] socalracer:
i followed shreks youtube to the T and it didnt work for me.

1. i get adb devices while the phone is on.

2. i pwr off and then power back on, on pwr on, i can use adb reboot recovery and make it boot to recovery.

3. once in recovery i dont get anything with adb devices

i also tried adb devices repeatedly on boot up, once i get a reply i can do adb recovery and it will boot to recovery, then i repeatedly do adb devices and never get a reply

win 7 x64, 8gb sd card

i have also tried this with the batch loops same thing basically

any ideas???
[Droid Incredible Android Development] you_eeeeeediot:
I didn't even update my .INF, just left the device 'Android 1.0' without the correct driver - so I don't think that makes a difference. Windows 7 x64, pretty much same config as yours. Do you have any other mSD cards kicking around you can try with?
[Droid Incredible Android Development] kjbuente:
Like I said, after letting the apply update.zip fail. I can not push anything to the sd card. I just get permissions denied. I'll try again later.
[Droid Incredible Android Development] AlexanderJohn:
Same boat as you... I've eatin' up a large load of time trying to figure this one out.... there goes my work day :/ ahh the sacrifices we make...
[Droid Incredible Android Development] Dc_striker:
I hope this gets ported to the eris :D
[Droid Incredible Android Development] jonnybueno:
are you guys rebooting into recovery as soon as you possibly can? (should happen when on the white incredible splash screen)

Maybe i'm misinformed, but what does your sdcard have to do with getting adb to run in recovery?
[Droid Incredible Android Development] yourfriendwayned:
so far people may think that the slowness of the card or a process in reading gives it time to do its thing...
[Droid Incredible Android Development] jonnybueno:
and i can see the logic in that insofar as applying the payload... but if you can't get adb shell to run through recovery, no dice. Aren't the adb files stored locally on nand flash? I would feel more inclined to believe that it would be the the computer, usb port, or usb cable that would create the variable that allows some to run shell from recovery. From what I've been reading, people are getting stuck on the first part and not the payload flash...
[Droid Incredible Android Development] r4ph:
rooted!

We were able to root my phone after many hours of trying all the suggestions here....

we used a 16gig class 2 card from a stock droid phone... we had another 16 gig class 2 that was partitioned for apps2sd that did NOT work.

we ended up trying many random things, and found one that worked, but so far have not been able to reproduce using other cards...

The only thing we did to make the adb shell work was to actually pull the sd card while the phone was in the recovery menu. Put it back in, not sure what magic happened, but it allowed us in to the shell after that.
[Droid Incredible Android Development] zebdor44:
Permaroot fix in case anyone doesn't know

This works great for me too! Thanks! I've been trying other ways for hours and no luck! This seems to be a pretty solid way!

Permaroot fix is out here on androidforums: http://androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html

To get permanent root, add these lines of code before rebooting OUT OF adb root recovery:

adb shell
su
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su

I'm having issues though installling the superuser.apk. I can't install directly from phone and when I adb install, it says 'Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]'

Any ideas as to why this is happening?
[Droid Incredible Android Development] Seeknay747:
Same problem I had. I got the superuser.zip from the original thread and extracted it. I found the apk file and installed it but its not working. My guess is because it needs those other files that also got extracted. I'm wondering if I can just push those to their respective locations.

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

Sent via the XDA Tapatalk App
[Droid Incredible Android Development] Caelum Bound:
Just wanted to thank JonnyBueno for his step-by-step on post 201, it worked perfectly for me. Got shell after only the second reboot into recovery, no batch file used, applying the hacked update went off without a hitch, and completed the commands to make root persistent through reboot.

Of course, a big thanks to all the Developers that have been (and still are) working day and night on this, and props to UnrEVOked for pulling it off and putting it out there for us to play with!

16gb class 2 sdcard (from Droid) with only about 1gb of free space (non partitioned)

Windows XP SP3
[Droid Incredible Android Development] JPorter900:
Of course we do. Anything else would be... uncivilized.
[Droid Incredible Android Development] vVv mDaWg:
Well I finally managed to get adb started in recovery mode on one out of my four phones after spending almost 7 hours of not stop repeated rebooting.

If it helps, it seemed to work by spamming adb reboot recovery while the phone was booting up with a sandisk 8gb class 2 SD card.

Now I just need to finish the rest of the steps and hope everything goes well... I really wish it were my main phone that managed to get into recovery though. Sadly this one belongs to my mother...
[Droid Incredible Android Development] mattguyver:
I can get logged in, all the steps done right up to the final step where I waif 1/2 a second to send the command. I have tried every timing I can think of but it either fails, or I'm too slow and it starts to do the ota update and I have to start again. Any suggestions?
[Droid Incredible Android Development] socalracer:
running win 7, my issue seems to be this, when the phone is rebooted anytime, windows makes the sound that the usb is there, well first sound seems to recognize it and then after the next one almost 99.9% i can issue an adb cmd from there like reboot recovery or ad shell and it will do it or adb devices, but once i tell it to reboot recovery or even if i manually do it, after the second sound in recovery i can't get anything, adb devices, shell or reboot recovery

possibly its an issue with how fast it boots into recovery, is there any way to delay that?

any suggestions?
[Droid Incredible Android Development] pozer69:
I can't seem to get it to work...I wasted enough time I guess I will just check back to see if there is a definate way to do this. My setup:

2 Windows XP Boxes

2 Linux Boxes

Incredible Pre-launch

Hardware Version 0002

Firmware 2.1-update1

Kernel 2.6.29-cc1c2268

Build/Software 1.22.605.2

When running Linux I receive "no permissions" when the device is on and I try to

adb devices

then when I try to boot to recovery "error: device not found"

When running Windows I can view the HTC info via

adb devices

then when I try to boot to recovery "error: device not found"

I hope that info will help you guys. Great job to everyone working on this.
[Droid Incredible Android Development] heavensblade23:
These instructions worked on the first try for me, but I have that 16GB Class 6 ADATA card that everyone seems to be having luck with:

http://androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html

I'm on Windows 7-x64.
[Droid Incredible Android Development] heavensblade23:
It also worked even though the 'Android 1.0' driver failed to install.
[Droid Incredible Android Development] Seeknay747:
I am successfully rooted and persistent through reboot.

I have a 16GB Class 6 SD Card and was on Windows 7 using the PowerShell While Loop method. It took 4 tries but I got it.

I'll stick around to try and help out if I can.
[Droid Incredible Android Development] suzook:
how do we make a loop command for a mac?
[Droid Incredible Android Development] sethman408:
the new method Worked perfectly dont even need the loop... just run adb shell 30 seconds or so after recovery.
[Droid Incredible Android Development] johnnybags:
while true; do ./adb shell; done
[Droid Incredible Android Development] dreamersipaq:
change group

Hey, can we use the linux change group command to change the "shell" SU to root root, and that way have access to what we need? just thinking out loud.

thanks.
[Droid Incredible Android Development] sethman408:
with you-eediots method you dont even need the loop.
[Droid Incredible Android Development] drew630:
You need to start adb as root to avoid those errors..

sudo ~/android-sdk-linux_86/tools/adb start-server

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

Sent via the XDA Tapatalk App