• 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'm very new to Android phones and even newer to rooting but I want to do it anyway :P

I saw on youtube that there are a bunch of very simple techniques to root other Android phones (just download a file and run it). Will something like this or something easier than whatever the process is right now appear soon? Also, if I plan on switching out my sd card for a different one in the future, can I simply copy over the files from the old one to the new one or is there a different process?

It is a bit unknown exactly where the rooting process will go from here. The Unrevoked team has mentioned a few times that they are releasing tools for the NAND lock (the lock that prevents you from uninstalling system files from a phone that has been normally booted). In doing this, they mentioned that you need to have your device already rooted and that they will be releasing something to make this process "easier"

Its pretty much a waiting game now as no one outside of the unrevoked circle really knows what this "easier" method entails.

I suggest taking a look at their twitter page from time to time for some updates:

Unrevoked (unrevoked) on Twitter
 
I've never unlocked or rooted a phone and have limited linux experience. I read the instructions and followed them and voila - wireless tethering!

This is the best set of instructions I've seen. I spent a couple hours trying to make earlier versions from others work and had no luck getting the recovery to work. The method here worked great. I used method #2, btw. The loop.bat was a very easy way to see if you got it.

Got through the root, then hit a snag for Wireless Tethering.

I had an issue with not being able to see my SD card as a drive. However, in Device Manager, I could see 2 HTC Android Phone USB Devices listed under Disk Drives (XP SP3). I double-clicked on them, chose the Volumes tab, then Hit populate. This let me find which one was the SD card, versus phone mem. I backed out to Device Manager and right-clicked to Uninstall that device, then Chose Action (top menu) and Scan for Hardware Changes to re-detect then I was able to see it again.

Once I did that, I had no problem getting it rolling. Works like a charm.

Thanks for a great run-down.
 
can anyone help?
when i type in this command
ln -s /system/bin/su /system/xbin/su
i get permission denied can anyone tell me what to do?
 
you are getting that error and you are root? if you do an

ls -a -l /system/xbin

do you see an item called "su" ?

If you do, do an

rm /system/xbin/su

and then try again
 
you are getting that error and you are root? if you do an

ls -a -l /system/xbin

do you see an item called "su" ?

If you do, do an

rm /system/xbin/su

and then try again

No Im trying to get root I can't remove Su from xbin because it isn't there yet.
Everything worked fine until I got up to this step in the ten minute video
 
Finally got it yesterday after 5 days of trying. Wound up using the PNY 2GB card from Walmart and worked on my first try. Love tethering the ipad so the kids can watch netflix in the car.
 
No Im trying to get root I can't remove Su from xbin because it isn't there yet.
Everything worked fine until I got up to this step in the ten minute video

Well technically by this point in the process, you are the root user, or at least should be or many of the commands previous to this wouldn't have worked.

After you do the payload push, you should have opened adb shell again and typed in :

su

to become the root account. This could be one reason that you are unable to create the symbolic link. Another thing you want to make sure you did is to apply the proper permissions to the /system/bin/su with

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

Other than those two steps, I dont really see any other reason why permissions would be denied to you. Make sure that in the ADB client you are seeing

#

at the console and not

$
 
Well technically by this point in the process, you are the root user, or at least should be or many of the commands previous to this wouldn't have worked.

After you do the payload push, you should have opened adb shell again and typed in :

su

to become the root account. This could be one reason that you are unable to create the symbolic link. Another thing you want to make sure you did is to apply the proper permissions to the /system/bin/su with

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

Other than those two steps, I dont really see any other reason why permissions would be denied to you. Make sure that in the ADB client you are seeing

#

at the console and not

$

Okay thanks for writing ill check that out to see if it works.
 
Thanks to everyone that made this possible!

I took me a few attempts but I finally got root on my Incredible.

Has anyone attempted to get OpenVPN installed and working? That is my main goal today! I see quite a few apps on the market place but not sure if we can get a TAP driver?
 
Well technically by this point in the process, you are the root user, or at least should be or many of the commands previous to this wouldn't have worked.

After you do the payload push, you should have opened adb shell again and typed in :

su

to become the root account. This could be one reason that you are unable to create the symbolic link. Another thing you want to make sure you did is to apply the proper permissions to the /system/bin/su with

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

Other than those two steps, I dont really see any other reason why permissions would be denied to you. Make sure that in the ADB client you are seeing

#

at the console and not

$

nvm i got it rooted thanks man i guess those commands werent working for me yours did the trick
 
Once I have root, can I easilly get to a shell? Or do I have to go through the entire process again?

I need to get to the shell to make changes for OpenVpn.
 
Once I have root, can I easilly get to a shell? Or do I have to go through the entire process again?

I need to get to the shell to make changes for OpenVpn.

What changes are you trying to make? If you are trying to make changes to the /system partition or anything that lives on the / partition, then you will have to go through the process again up to the payload push so that you can do a "su" and modify files.

Mind you this is all until we get the NAND unlock from the unrevoked guys
 
What changes are you trying to make? If you are trying to make changes to the /system partition or anything that lives on the / partition, then you will have to go through the process again up to the payload push so that you can do a "su" and modify files.

Mind you this is all until we get the NAND unlock from the unrevoked guys

I need to do this:

The following must be done in a root shell:

adb shell
su
mkdir /data/openvpn
dd if=/sdcard/openvpn/openvpn-static of=/data/openvpn/openvpn
chmod 700 /data/openvpn/openvpn

From the following URL:
OpenVPN with Root - xda-developers
 
yep, the you need to go all the way through the process again down to the payload push. Basically anything that requires you to do an "su".
 
yep, the you need to go all the way through the process again down to the payload push. Basically anything that requires you to do an "su".

OK, figured out I can get to the shell with root very easilly!

1. Enable USB Debugging
2. Type "adb shell"
3. Type in "su"
4. The Superuser app will prompt to you allow/deny, select Allow. That's it!
 
OK, figured out I can get to the shell with root very easilly!

1. Enable USB Debugging
2. Type "adb shell"
3. Type in "su"
4. The Superuser app will prompt to you allow/deny, select Allow. That's it!

Kudos! I thought it would modify a system file somewhere but I guess not.
 
Finally got it yesterday after 5 days of trying. Wound up using the PNY 2GB card from Walmart and worked on my first try. Love tethering the ipad so the kids can watch netflix in the car.

yeah after I saw your post I stopped at wally world and bought the same card and it worked on the first try. I have been trying for a week, I tried it again see if I could get it again and no luck until I decide to delete the files that were on the 2gb pny from the first time of rooting and boom it worked again sweet so I removed the face book, peep, twitter, and city id and friends stream, they are all gone widgets too:D
 
C:\sdk\tools>adb shell
$ su
su
# /system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/cat /system/bin/sh > /system/bin/su
# /system/bin/chmod 4777 /system/bin/su
/system/bin/chmod 4777 /system/bin/su
# env
env
ANDROID_ROOT=/system
PATH=/sbin
EXTERNAL_STORAGE=/sdcard
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=9,32768
# export PATH=$PATH:/system/bin
export PATH=$PATH:/system/bin
# cd /system/app
cd /system/app
# cat /sdcard/Superuser.apk > Superuser.apk
cat /sdcard/Superuser.apk > Superuser.apk
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# ls -a -l /system/xbin
ls -a -l /system/xbin
drwxr-xr-x 1 0 2000 2048 May 6 10:32 .
drwxr-xr-x 1 0 0 2048 May 6 10:32 ..
-rwxr-xr-x 1 0 2000 5540 May 6 10:32 crasher
-rwxr-xr-x 1 0 2000 22184 Apr 6 13:42 wireless_modem
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory

So I try this:

# /system/bin/chmod 777 /system/xbin
/system/bin/chmod 777 /system/xbin
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
# /system/bin/chmod 06755 su
/system/bin/chmod 06755 su
# reboot
reboot

But something is not correct with this. My "Superuser Permissions" app loads up a black screen, "Wireless Tether" says it works but does not actually publish a wireless network, "Titanium Backup" on load pops up a message that says:

BusyBox works but the "su" command does not elevate to root: "whoami" reports "whoami: unknown uid 10090" instead of root/uid 0. I think that your "Superuser Whitelist" system app does not work. Please check with your ROM provider.

I tried clicking the "problems?" button to update BusyBox and it says success, but I just get a repeat of the same message when TiBU re-opens.

What am I doing wrong?
 
So I try this:



But something is not correct with this. My "Superuser Permissions" app loads up a black screen, "Wireless Tether" says it works but does not actually publish a wireless network, "Titanium Backup" on load pops up a message that says:



I tried clicking the "problems?" button to update BusyBox and it says success, but I just get a repeat of the same message when TiBU re-opens.

What am I doing wrong?

I'm having same issues but It did get Titiaium actually started working after it downloaded the busybox.

But Wifi Tether doesn't publish an SSID and if you check the log it can't start the ad hoc network, configure the SSID or load some modules. SU apps says they have permission but nothing I do fixes it.

After you run this
ln -s /system/bin/su /system/xbin/su IF YOU GET ERROR rm /system/xbin/su
And then repeat
ln -s /system/bin/su /system/xbin/su


BTW the SU app is blank and black until something ask for SU permission and then they are listed there. ;)
 
After you run this
ln -s /system/bin/su /system/xbin/su IF YOU GET ERROR rm /system/xbin/su
And then repeat
ln -s /system/bin/su /system/xbin/su

I did that. See my post, the result of it was

Code:
rm: cannot remove '/system/xbin/su': No such file or directory
 
I did that. See my post, the result of it was

Code:
rm: cannot remove '/system/xbin/su': No such file or directory

I have received this error also... I rooted my phone fine with the same files, but last night I was trying to help my roommate with his phone and I got this permission is denied... I searched around and now I'm clueless as to why this is happening. Did some of the files get changed in the links or something? Because I deleted everything and redownloaded everything and tried again.... still the same thing.
 
This error is happening to me as well im not sure what the fix is. I have scoured the internet and found nothing that solves this.

this is shortened for convience...
Code:
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied

UPDATE: FIXED


The instructions told me to remove /system/xbin/su however no file was present.

I tried this multiple times going through the whole reboot process over 5 times and still the error.

i gave up and decide to check out the packages i was downloading.

these differ from the 10 min video files; they actually worked!

I looked in to it and here were the differences.
this payload-update has Superuser.apk already in it.
Also your update script is different in that this code is not in his.

Code:
package_extract_file("su", "/system/bin/su");
set_perm(0, 0, 06755, "/system/bin/su");

package_extract_file("Superuser.apk", "/system/app/Superuser.apk");
set_perm(0, 0, 0644, "/system/app/Superuser.apk");

run_program("/system/bin/toolbox", "dd", "if=/sdcard/busybox", "of=/system/bin/busybox");
run_program("/system/bin/toolbox", "dd", "if=/sdcard/busybox", "of=/sbin/busybox");
set_perm(0, 0, 0755, "/system/bin/busybox");
set_perm(0, 0, 0755, "/sbin/busybox");

run_program("/sbin/busybox", "--install", "/sbin/");

I know this installs busybox and superuser and that is cool but i think this may be where things blow up his code sets permissions of /system/bin/su to 04755 not 06755

actually his does not install superuser.apk at all and this does. Did the payload get updated recently??

This guide payload and instructions seem redundant and have introduced a bug. This should be mentioned in the front and sorted out.
 
n00b question (just got my dinc today) but if I root my phone, will all my settings and installed programs be saved?

I'm assuming no cause when i used windows mobile, any updates erased everything, but there's always a chance I'm wrong since I've never used android before
 
Back
Top Bottom