yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] Joe92T:
So that nand unlock really did jack squat for me then and i need to still wait for the easy root method?

I was hoping if the nand unlock worked i could jus go into adb shell while in android and do flash_image recovery and have the new clockwork put on my phone which would in turn let me root / give me root
[Droid Incredible Android Development] aaronjb:
I'm rooted and the tool still didn't work. No biggie, though - not much to be gained for me from a (longer) temporary NAND unlock.
[Droid Incredible Android Development] reagianicparable:
I can't get the recovery to flash either. Making me pretty mad.
[Droid Incredible Android Development] johnnybags:
you should ask for a refund.
[Droid Incredible Android Development] Shadowmite:
The new unrevoked.com reflash tool is out, one click root and recovery. no sd method's required. Mod's please close this thread ending with this post if you can...
[Droid Incredible Android Development] edstreiff:
Yeah same here and I cant get it to work for the life of me, I am using windows XP and PowerShell to do the looping but so far no luck I have tried it 72 times now and still nothing. I will try a windows 7 machine later at home but I don't see how the OS of my machine would impact the Incredible but I supoose its worth a try thanks for responding to my question
[Droid Incredible Android Development] fallingup:
guys, im a droid user so i have no use for this, just wanted to say congrats and what a clever way to root!
[Droid Incredible Android Development] dincodee:
Nope i am on windows 7 as well and still cant get it to work.
[Droid Incredible Android Development] k.electron:
Congratulations. This is great news.

I would like to know some stuff:

1. Is it possible to revert phone back to absolute stock state like it had never been messed with after this? just in case people want to go back to stock for official updates and what not?

2. Has anyone started cooking roms for the phone now?

P.S is there a wiki page with instructions for windows 7?

Thanks.
[Droid Incredible Android Development] TNS201:
For those who got it, when did you start your batch?

Sometimes when I start the batch it freezes the DOS window.

Do you wait till recovery comes up or before where the screen says incredible?

I am using Win XP, but will try windows 7 later.
[Droid Incredible Android Development] edstreiff:
Now as it comes up do you wait to see the actual verizon logo or do you run the common at the very second that it would have shown the logo?
[Droid Incredible Android Development] Ohsaka:
Don't recovery and normal boot use different images? Maybe try mounting normal boot image filesystem and chmoding su to 777 before reboot... (no incredible here)
[Droid Incredible Android Development] AetherNex:
I didn't hit it the moment the HTC quietly brilliant screen changed, but once I saw the VZW animation start. I've tried it a few times since the root seems temporary, and each time I did it the animation seemed to be at different points, but it worked each time. I do know that I usually hit enter for the command no more than halfway through the animation each time though.
[Droid Incredible Android Development] rynosaur:
I haven't gotten my Inc yet so I can't say for sure, but trying the command too early shouldn't have an effect, the idea is to ask as early as possible, i.e., as soon as the SPL starts adb-server.

That's a good idea, is chmod included in the stock recovery command console?
[Droid Incredible Android Development] sethman408:
I have no problem performing the procedure. I've done it 4 times now.

my only problem is that it is not perm. after reboot i have no SU.
[Droid Incredible Android Development] stanfna:
can you help us out and count how many seconds from the moment you see the white HTC screen until you click to execute the adb reboot recovery command?

I changed my boot screen. so i never see the VZW logo.

Thanks!!!!
[Droid Incredible Android Development] AetherNex:
I've already tried this and chmod is not included. It seems that very little is included in the stock recovery command console...
[Droid Incredible Android Development] AetherNex:
After the "quietly brilliant" screen goes away it's maybe 2 seconds later. This is by no means a scientific method, and may not be accurate at all, it just worked for me repeatedly and thought I'd share.
[Droid Incredible Android Development] stanfna:
thanks...but I do not get the quietly brilliant screen...just the first HTC screen. how long do you wait after you first see the white HTC Incredible screen?
[Droid Incredible Android Development] ricardovj:
It worked half way?!

So after only 4 reboots I got adb running in recovery, I followed the instructions and I got to the last step successfully, seeing the message:

“unrEVOked for Incredible”

But then I reboot and I don't have root... :(

Did I miss anything?
[Droid Incredible Android Development] krelvinaz:
Yes it is, it is in /system/bin

When you get root in recovery, PATH is set to /sbin.

You can do

PATH=/sbin:/system/bin

and you will then be able to chmod etc.. without using the path to get to it.

Someone above said chmod su... that was tried and it didn't last past the reboot. Also tried a number of other things with the same results. Root in recovery, lost in reboot.

I've done this now more than 10 times in 2 tries or less not using the script.

Until they get a payload that lasts though, not much point to it except for removing CityID... They will get it... patience...

Should be soon.
[Droid Incredible Android Development] xcsdm:
yes it is as /system/bin/chmod

I always type the command

export PATH=$PATH:/system/bin

Then all the "normal" commands are in the path for you to use easily

XC
[Droid Incredible Android Development] AetherNex:
Oops, I must've missed it there. Sorry for the mis-information.
[Droid Incredible Android Development] whiplash000:
So... just to confirm, once you get su installed with 777 permissions, does it stick? ...Because I'm still stuck on getting the recovery mode to have adb running. Waiting for the verizon logo doesn't seem to work. Sending the command the instant the shell comes up doesn't work. How does that have an effect on the presence of a process after reboot anyway?
[Droid Incredible Android Development] AetherNex:
Oh, it's approximately 4-5 seconds after that screen disappears.
[Droid Incredible Android Development] asdelling:
First, THANKS FOR THE ROOT! I'M READY....I'M READY....I'M READY....I'M READY....I'M READY....

But.... I get...

Load in Recovery and Get Message: "e: can't open/cache/recovery/command" and Adb isn't running...

Anyone have same issue / resolution?

I have tried running adb reboot recovery at different intervals during boot... Nada...

Tried Reinstalling Adb Drivers... Nada...

Tried Formatting Phone / Cache... Zipo...
[Droid Incredible Android Development] whiplash000:
If adb is running in recovery mode, should I see the '/sh' message instantly or after a few seconds of "error: device not found"?
[Droid Incredible Android Development] jdmba:
Super Basic Question

This question is super basic, and hopefully someone will be kind enough to answer, as I am not truly familiar with the inner working of the android subsystem.

The first step in the rooting instructions (and yes, I will NOT be rooting at this preliminary stage), is "On the host, run adb shell in a loop; On Linux, syntax will be something like while true; do adb shell; done"

I have not the slightest idea what that means. Is there some kind of command line on my Incredible that I don't know about?

Any guidance on this very basic step is appreciated; largely because any step-by-step root instructions will likely ALSO assume people know what that means.

Thanks!
[Droid Incredible Android Development] sethman408:
I wouldnt worry about it right now. If you cant figure out this step then i highly suggest you wait till an easier procedure is made.
[Droid Incredible Android Development] sethman408:
There has to be something that runs on boot and replaces su with the original.
[Droid Incredible Android Development] jdmba:
... the joys of posting a question on a forum

Yes - thank you; To avoid such a reply I had addressed those points and said that I would wait until there was an easier procedure but noted that any easier procedure would ALSO assume people knew how to do this step.

If anyone can actually answer the question, it would be appreciated. Thanks
[Droid Incredible Android Development] sethman408:
i believe the goal of an easier procedure is to solve the issues with this step.

For this to work adb shell has to run at just the perfect time during loading of the recovery mode to get into the right mode to allow rooting. this loops adb shell over and over again very fast to try to get it at just the right time. this command is for linux. in windows you will need to do it with a batch file.
[Droid Incredible Android Development] j1000:
Congratulations on root.

Two questions

1. Is this permanent from what I reading it doesn't look like it is.

2. If it isn't permanent why does it say to install superuser after reboot.

Sorry if these are stupid questions but thanks for any help.
[Droid Incredible Android Development] jdmba:
..

Sethman - Thank you for your reply. I think I am getting closer to my answer by shortening my question to use your advice ... You sai "adb shell has to run at ..." So my 2 questions are (i) how do you run ADB shell and (ii) is ADB shell where I would type in commands?

Thanks
[Droid Incredible Android Development] mmaibl2011:
are you using windows?
[Droid Incredible Android Development] sethman408:
So i think i found the issue... seems the issue is that the su is not in the right place. once in shell after performing the procedure. If i just type su. no problem. If i try to run /system/bin/su then i get permission denied. seems we need to overwrite the original su with the right one
[Droid Incredible Android Development] stanfna:
this would all be done in an MSDOS window.
[Droid Incredible Android Development] mmaibl2011:
Wouldnt this only work in a msdos window if you copied the adb.exe and adbwinapi.dll files to \windows\system? Maybe im wrong, which would be quite possible.
[Droid Incredible Android Development] arcanumal:
Have a friend who is working on the Incredible now. Confirmed that after reboot, the updated permissions stick on su. However, trying to run su from adb shell still results in permission denied.

Note: need to keep the setuid bit, so use chmod 7777
[Droid Incredible Android Development] krelvinaz:
It is a bit complicated... Su is not really Su but rather sh.

To answer the other guy, you need to have the Android SDK installed and working on your workstation before you can even attempt this. If you don't have it and already have it working with the phone you won't be able to try the current process.
[Droid Incredible Android Development] the337:
do most of you, if not all, run linux as your desktop?
[Droid Incredible Android Development] nailbnny:
I suppose you could do it that way, but it would recommend updating your PATH instead. Google "Windows update PATH" if you are interested.

nB
[Droid Incredible Android Development] met152:
Assuming you're running windows, you need to download the Android SDK:

developer.android.com/sdk/index.html

There is a file "adb.exe" located in the \tools folder. That's the file you want to use to loop the "adb shell" command

Create a new .txt document, and paste this into it:

@ECHO OFF
:TOP
adb shell
goto TOP

Save it and rename the file something like "shell.bat"

Open the command prompt (start->run-> cmd)

Run the shell.bat program from the folder where you saved the file.
[Droid Incredible Android Development] DDRBoxman:
For those of you running windows I put together a little adb package with a bat script that loops the adb shell command. You still have to install the adb drivers into windows though.
[Droid Incredible Android Development] whiplash000:
To everyone who got adb going in recovery mode: what was your timing? To be more accurate, maybe you should start from when the phone says "HTC Incredible" and rumbles and count from there, such as RUMBLE0, 1, 2, 3...

That way we can have a better idea of when the perfect moment to run "adb reboot recovery".
[Droid Incredible Android Development] mmaibl2011:
alright when i boot into recovery i get E: Can't open /cache/recovery/command. Is this normal? stupid question i know.
[Droid Incredible Android Development] jdmba:
Thanks

THERE WE GO. Thanks all!
[Droid Incredible Android Development] mmaibl2011:
Well assuming that you saved the android-sdk-windows folder to C: you could alter the code like this

@ECHO OFF

cd C:\android-sdk-windows\tools

:TOP

adb shell

goto TOP

Then you could save it on the desktop and run it from there.
[Droid Incredible Android Development] stanfna:
exactly...this would help tremendously!!!!
[Droid Incredible Android Development] E30kid:
From what I saw yesterday, a lot of people ran Windows 7 for this as well.
[Droid Incredible Android Development] nosidefcp:
would unrevoked team give a go on xperia x10?thanks
[Droid Incredible Android Development] stanfna:
or would it be better to count how long to wait until after the "error: device not found" stops and you see the '$' for the shell?
[Droid Incredible Android Development] Ohsaka:
Here are the permissions on my G1 for su...

# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-sr-x 1 root root 26228 Aug 1 2008 /system/bin/su

Make sure you are matching them...
[Droid Incredible Android Development] whiplash000:
Possibly... I'm of the opinion (after looking over "race condition" on wikipedia) that the timing is really in the millisecond range than the second range... Maybe 100% of the people who were sucessful hit a window that was like 50ms long... since people's boot times vary slightly, it may be a different moment (in terms of what animation is going on) for each phone... in which case... I think I'll wait for a easier method. Especially as people are saying that su doesn't quite stick after reboot.
[Droid Incredible Android Development] 2WheelCowboy:
Awesome work guys. I'm one that's going to wait for everything to get ironed out but very nice to know.
[Droid Incredible Android Development] jonnybueno:
Hey guys, the loop is not necessary.

If you can't get the adb shell to run in recovery, try unplugging and plugging your usb cable back in. If its still not running after about 5 tries, reboot and repeat that process. Im using the history feature in cmd (up + enter ) and "adb reboot recovery" repeatedly when the white HTC incredible splash screen pops up.

That method has worked for me several times but may not work for you with your setup.

Oh btw, I am ota updated.
[Droid Incredible Android Development] humancyborg:
This root adb issue is due to a setting in the default.prop file, if I recall its ro.secure=0 that needs to be set. default.prop is part of the boot.img ramdisk.
[Droid Incredible Android Development] stanfna:
sorry...but can you add a little more detail as to when you pulled the USB cable? for example...you pulled it while the phone was rebooting...or...when it was at the screen with the triangle & !

thanks.
[Droid Incredible Android Development] bobby_bac:
This would be the ultimate hammer (windows):

@ECHO OFF

:TOP

C:\adb reboot recovery

C:\adb shell

GOTO TOP

the only real thing you would need to do is reboot in recovery if you loose the race and occasionally type "exit" if the loop hits the "C:\adb shell" before the "C:\adb reboot recovery" when the phone comes back online normally.

Still no luck however. I did get this:

================================================

** daemon still not runningerror: cannot connect to daemon

error: device not found

** daemon still not runningerror: cannot connect to daemon

error: device not found

** daemon still not runningerror: cannot connect to daemon

error: device not found

error: device not found

** daemon still not runningerror: cannot connect to daemon

error: device not found

** daemon still not runningerror: cannot connect to daemon

error: device not found

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

error: device not found

error: device not found

error: device not found

** daemon still not runningerror: cannot connect to daemon

error: device not found

** daemon still not runningerror: cannot connect to daemon

error: device not found

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

==================================================

and this:

==================================================

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

** daemon still not runningerror: cannot c

error: device not found

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

* daemon not running. starting it now *

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

============================================

This probably has to do with the hammering but I noticed other people got this as well.
[Droid Incredible Android Development] arcanumal:
Try 06755 for chmod permissions on /system/bin/su...
[Droid Incredible Android Development] Ohsaka:
From my G1....

# cat default.prop
cat default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1

I'm still waiting for my friend with the Incredible to get back from lunch, lol.
[Droid Incredible Android Development] sethman408:
Tried this... permissions now match the g1 guy except it says root shell and not root root
[Droid Incredible Android Development] sethman408:
I am in the shell with root right now ... AIM me as dagixxerkid2 or yahoo seth_ag6i if you have anything to try
[Droid Incredible Android Development] madman34:
Been trying for hours now, nada

I have been alternating between my windows and linux machines and get the above same as he did on the windows machine and just nothing on the linux box, so maybe different phones are at different levels of difficulty up to not possible ???
[Droid Incredible Android Development] Ohsaka:
Are you still getting permission denied when you try to run it?

If so, what permissions/ownership does /system/bin/sh have?
[Droid Incredible Android Development] sethman408:
IF any DEVS have anything for me to try I am in my system right now. I can su from the original prompt after shell.. but if i try to /system/bin/su then i get permission denied..

AIM Dagixxerkid2
[Droid Incredible Android Development] Ohsaka:
Cant do IM from work. :(
[Droid Incredible Android Development] arcanumal:
See if /system/bin/chgrp root /system/bin/su works

If not, see if you can find chgrp somewhere else... no Incredible here, also g1 guy
[Droid Incredible Android Development] krelvinaz:
If you look at the contents of the payload... you will see that the su created in /system/bin is really not su but rather a copy of sh

That is why the size is so different.
[Droid Incredible Android Development] sethman408:
looks like -rwxr-xr-x root shell
[Droid Incredible Android Development] Ohsaka:
Here is the content of payload update...

run_program("/system/bin/mount", "-o", "rw,remount", "/", "/");
set_perm(0, 0, 0755, "/sbin");
run_program("/system/bin/sh", "-c", "/system/bin/cat /system/bin/sh > /sbin/su");
set_perm(0, 0, 04755, "/sbin/su");

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

ui_print("su in adb shell if you want to flash image");
ui_print("or reboot for stock permaroot");

Maybe try setting 06755 on both /sbin/su and /system/bin/su
[Droid Incredible Android Development] you_eeeeeediot:
contents of default.prop

cat default.prop

#

# ADDITIONAL_DEFAULT_PROPERTIES

#

ro.secure=1

ro.allow.mock.location=0

ro.debuggable=0

persist.service.adb.enable=0
[Droid Incredible Android Development] sethman408:
chgrp not found.
[Droid Incredible Android Development] krelvinaz:
The devs are doing work on irc not here.

via Tapatalk
[Droid Incredible Android Development] jonnybueno:
pull the usb after running adb shell in recovery if you dont get - exec '/system/bin/sh' failed: No such file or directory (2) -,
[Droid Incredible Android Development] Ohsaka:
Heh, maybe try this....

busybox echo "ro.secure=0" > /default.prop

busybox echo "ro.allow.mock.location=0" >> /default.prop

busybox echo "ro.debuggable=0" >> /default.prop

busybox echo "persist.service.adb.enable=0" >> /default.prop

First line overwrites....following lines append.... (> versus >>)

Run the four command consecutively
[Droid Incredible Android Development] Hero_Over:
glad u guys got root!
[Droid Incredible Android Development] sethman408:
if i just do /sbin/su it works just fine
[Droid Incredible Android Development] humancyborg:
This won't work; default.prop is created by the boot.img ramdisk on boot, editting it post-boot won't make any difference.

You need to dump the boot partition to a boot.img file, unpack it, edit the default.prop, repack it into a boot.img, then flash the new boot.img file to the device. Some of these steps require either an unlocked SPL or a modified recovery including flash_image. All this assumes the boot partition is writable of course.
[Droid Incredible Android Development] m1k3-:
I just can't believe they got it before Jake Day.

./sarcasm
[Droid Incredible Android Development] you_eeeeeediot:
Actually, it is possible to do an offline edit of that file (there is actually a lot more in default.prop), I think the values would need to change to =1 though and not =0)

C:> adb push default.prop /sdcard/newdefault.prop

C:> adb shell

$ su

$ /system/bin/cat /sdcard/newdefault.prop > /default.prop

$ /system/bin/chmod 644 /default.prop

Thats assuming modifying default.prop is the issue.
[Droid Incredible Android Development] sethman408:
So i did a ls -l and the sbin directory has all the permissions.. while the /system/bin is missing some and the sbin is root root while bin is root shell
[Droid Incredible Android Development] Seeknay747:
I was originally successful and got the root message to come up. But when I tried to remove City ID I had that message too.

I tried to redo all the steps and when I get up to this part:

I only get install failed. I cant reproduce the original successful attempt. Should I try wiping?
[Droid Incredible Android Development] you_eeeeeediot:
That's because it is the first directory in the PATH. The one we need is in /system/bin