• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The PRS Complete Rooting Guide

I had used 4 different microSD cards, nothing, they were all different brands and sizes. Finally went to walmart and got one of the PNY 2gig cards, couldn't get into adb shell in recovery, and on about the 30th try it finally worked. I had stood up to go get another computer to try to use, and when I looked down it worked, I had tried hundreds of times with all the other cards, it seems that PNY is a brand that helps, if you're having trouble try it, it's only $10 for the 2G and worth it since it seems that it's the card that has worked for quite a few people.
 
stanfna said:
I FINALLY got it to work!!

I tried every little trick and here is what I noticed.

- unplug your phone from your USB cable
- turn your phone on normally...like you would every day. so you can use it.
- then don't power it down...just pull the battery out
- then press the optical jotstick & power button
- then follow the rest of the instructions listed in previous posts

i think for some reason...rebooting the phone into recovery from various states does not work (it did not for me). i think when you just kill the phone from it's normal state and then boot into recovery it works (it did for me).

i hope this helps!!!
Click to expand...
DUDE!!!! I've been trying EVERYTHING for the past few days, and this worked for me!! I finally got the "exec '/system/bin/sh' failed: No such file or directory (2) -" to come up! I followed your instructions, however, once I was in the first menu, I just let the phone set there for a few minutes, and then I selected the recovery menu, hit power and PRESTO!! I recommend anyone having trouble to try this!!
 
How about a sticky thread to track all the various methods that have worked?

That way it will be alot easier for people who STILL cannot root to check for new methods
 
I finally got mine to work as well..

I think the key is definately the card you have in the phone when booting into recovery mode. I had a crappy PNY 2GB that's I've had forever. Seen several others having luck with PNY 2GB from WalMart. Doesn't seem to matter how much is on the card. It worked when completely blank.

Method:
1. Optical + Power
2. Boot Menu
3. Select Recovery mode and about 1 second later I plug in the USB cable

After about 5-10 seconds into the recovery mode, the adb shell command will give you the message such that you can continue the process.

I tried 3-4 other cards, only this one seemed to work. Plugging the cable in after hitting recovery mode seemed to help also. Had it 100% repeatable.
 
So I rooted but forgot the step to make it stick after reboot. And now i'm unable to get the phone to install the file update file again, just tried like 50 times in a row. Im able to get the error: device not found and able to push busybox ota.zip su and Superuser.apk to the sdcard root. but when I try to

adb push payload-update.zip /sdcard/update.zip and power button on
"Apply:update.zip" (within in a half a second of course) It just will not take.

Anyone else experiencing this? Am I missing something simple?

Ive tried 7 different data cards as well. Just cant replicate it.
 
Trying for about 4 hours now. I have tried two different sd cards, just about every method I've seen and a few different forums and no root. Looks like I'll be waiting for a different way to root.
 
I've tried every method myself, but i noticed that while in the h-boot screen the PC does the USB detection but does the WindowsVista/7 USB drivers failed sound, like it can't determine what it is.

could this be why i can't get into ADB shell?

I have a 4GB PNY Class 4 card

can anyone help? :( I've been trying for almost 5 hrs now . . . constantly rebooting the phone with no luck . . .
 
OK Folks ... I was very very busy this weekend. I will be scouring the various threads over the next couple days and updating the thread as needed. Please be patient. I will keep this up to date..

*****Added a 3rd method from Centsy for getting into adb recovery****
 
***************Please I need someones help***************

I need someone who hasnt rooted yet and will be to skip the part that makes it perm. It looks like unrevoked has updated the payload-update.zip to make itself perm without these additional steps. If someone can confirm this it would be appreciated. Please if you are not experienced with linux and a total newb to rooting let someone else try it.

Send me a PM if it persists through reboot without the added steps.
 
As per the first post, to get permanent root after reboot steps are:

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

Once at root (#) prompt in adb recovery

export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su


But the original unrevoked teams updated method gives different method for permissions and superuser; (public:adb_in_recovery [RootWiki]


  • On the host, run adb push Superuser.apk /sdcard/Superuser.apk
  • On the host, run adb shell to bring up a shell on the device.
    • In the device shell, type su to become root.
    • In the device shell, run /system/bin/toolbox dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
    • In the device shell, run /system/bin/chmod 644 /system/app/Superuser.apk
  • Congratulations! You now have a barebones rooted Incredible. Look in the post-hack tasks below for other things you might want to do before you reboot.



Please, Someone clarify because going through all the posts I find there are people who are finding only certain root apps working and asking for Superuser permissions while rest not working. So it is possible that this has something to do with the way we push Superuser and give path/permissions in the system.
 
can someone post the SKU/UPC of the PNY card from walmart that seems to be working? I think I'll swing by today and see if I can get one and I don't think "didn't work to root my incredible" is a valid excuse to return it.
 
topgnat said:
As per the first post, to get permanent root after reboot steps are:

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

Once at root (#) prompt in adb recovery

export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su


But the original unrevoked teams updated method gives different method for permissions and superuser; (public:adb_in_recovery [RootWiki]


  • On the host, run adb push Superuser.apk /sdcard/Superuser.apk
  • On the host, run adb shell to bring up a shell on the device.
    • In the device shell, type su to become root.
    • In the device shell, run /system/bin/toolbox dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
    • In the device shell, run /system/bin/chmod 644 /system/app/Superuser.apk
  • Congratulations! You now have a barebones rooted Incredible. Look in the post-hack tasks below for other things you might want to do before you reboot.



Please, Someone clarify because going through all the posts I find there are people who are finding only certain root apps working and asking for Superuser permissions while rest not working. So it is possible that this has something to do with the way we push Superuser and give path/permissions in the system.
Click to expand...

I think for the actual SU executable, 755 and 777 are the same because you need to have execute permissions. The only difference is 755 does not give write permissions.

I dont think it would matter for the APK file as long as you have read permissions since once you install it, you don't need the file anymore.

I'm just guessing here.
 
Piiman said:
Can someone explain what a "RACE" condition is?
Click to expand...

Here's the wiki article Race condition - Wikipedia, the free encyclopedia

But basically, when you have more than one thing happening at once, it is sometimes hard to predict what will happen.

For example, as the Dinc boots up, lots of things are coming online at the same time (ie. sd card mounting, reading files, etc). The software usually expect things to happen in a certain order, designers usually try to make the design in a way to prevent these kinds of issues. But apparently if you do things in just the right way, you can get access to root. but since its a "fluke" it is hard to know exactly what is going on and thus have a foolproof procedure. instead, you are working backwards and in a sense, reverse engineering the problem.
 
Just a heads up guys. The stock 2gb card that comes with the phone did not work for me no matter how long I let loop work.

However, an old 1gb card I had laying around from my LG Dare works perfectly on the first try, every time. (It is a kingston)

So try different cards, for me, the older slower card works perfectly.

Enjoying root thanks to unrevoked's method and mejdam's 10 minute video. :)
 
Updated with more apps to remove since they need to be removed during adb recovery.

I have not personally removed all the apps listed... Do so at your own risk.

I personally have removed

VVM
FriendStream
Foot prints
and City ID
 
stanfna said:
I FINALLY got it to work!!

I tried every little trick and here is what I noticed.

- unplug your phone from your USB cable
- turn your phone on normally...like you would every day. so you can use it.
- then don't power it down...just pull the battery out
- then press the optical jotstick & power button
- then follow the rest of the instructions listed in previous posts

i think for some reason...rebooting the phone into recovery from various states does not work (it did not for me). i think when you just kill the phone from it's normal state and then boot into recovery it works (it did for me).

i hope this helps!!!
Click to expand...

Used this method and it worked first try. Thanks. :D
 
Got it to work for me finally, what I did was follow method 1, but remove my sdcard, then, once clicking recovery, and RIGHT BEFORE the screen went to the /!\ screen (you will hear a 'disconnect' noise from windows) i clicked in the card.

Note: /system/bin/rm /system/app/com.htc.FriendSteam.widget.apk
should be :
/system/bin/rm /system/app/com.htc.FriendSteamWidget.apk

Also: Anyone know what the *.odex files are? Most of these APK's have odex files with them
 
OMG!...FINALLY GOT IT. I have been trying this since Friday. 2GB PNY sd card and this.....
...remove my sdcard, then, once clicking recovery, and RIGHT BEFORE the screen went to the /!\ screen (you will hear a 'disconnect' noise from windows) i clicked in the card.
Click to expand...
... worked for me.
 
K so ive downloaded some stuff and reboot the phone and have confirmed the phone is working fine and has permaroot. The only things that are left for me to figure out are the following:

1. The update icon is always there near my gps/location icon at the top bar
2. If i go to add a widget, I have a '0.0dip' widget and a 'false' widget....clicking them throws a FC from com.htc.RosieUtility
 
prerunnerseth said:
1. With your phone booted up and plugged in via USB, type adb reboot recovery.
2. Start your adb shell loop (using the while loop or bat file).
3. Click in and out your SD card repeatedly while the phone is booting into recovery (apparently every 0.5 sec will do).
4. Watch for "- exec '/system/bin/sh' failed: No such file or directory (2) -" to appear in your terminal
Click to expand...

method 3 worked for me 2nd try using win 7 64 bit , 2 gig stock card from verizon , i previously followed the 10 min guide posted somewhere in here in a video to downgrade and reset up my environment , idk how much of this helps but i had 2 cmd windows open 1 running the loop and 1 to do the adb reboot recovery , idk about every 0.5 seconds just casually in n out with the sd card enough to see if the loop display is changing then out and back in anything we can do while in root / recovery status to help out ?


sorry forgot to ask , i did all this pree ota where verizon fixed an exchange issue or something for email , after doing root and removing city id & vvm can this ota still be applied / is it recommended.

idk if this will remove root or somehow change the phone back any one know 1 was or another?
 
after in cmd cd\adb\adb tools\adb shell. a $ is all that comes up. running windows 7 64bit. I have gotten the DINC to boot in recovery once and f***** up by not replacing the battery correctly, but I cannot seem to replicate the process what so ever. I have been trying to root for days now with no avail. I also edited my usb drivers, if everybody that has had success with this, please post a valid updated usb driver for the DINC. I am at wits end, and giving it one more chance without waiting for a more stable reliable method to root
 
mickym5 said:
after in cmd cd\adb\adb tools\adb shell. a $ is all that comes up. running windows 7 64bit. I have gotten the DINC to boot in recovery once and f***** up by not replacing the battery correctly, but I cannot seem to replicate the process what so ever. I have been trying to root for days now with no avail. I also edited my usb drivers, if everybody that has had success with this, please post a valid updated usb driver for the DINC. I am at wits end, and giving it one more chance without waiting for a more stable reliable method to root
Click to expand...

idk much so take this for a grain of salt
maybe ur stuck in limbo ? down grade and re try ?
 
You must log in or register to reply here.
Back
Top Bottom