Method to install root for Honeycomb

[chhaggerty]

Check this thread for updated and improved information, many thanks to j4mm3r

http://xdaforums.com/showthread.php?t=953110




Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:

1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2

Extract the above files using your favourite program

Using adb, install all three files to /data/local:

adb push su /data/local
adb push Superuser.apk /data/local
adb push busybox /data/local

Use adb remount to open the /system directory

adb remount

Use adb shell to move files

adb shell
cd /data/local
cat Superuser.apk > /system/app/Superuser.apk
cat su > /system/bin/su
cat busybox /system/xbin/busybox

Symlink su and set permissions:

ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su

Typing su should now work

su
su: access granted, courtesy of www.magicdroidapps.com

Install busybox

exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,

su
busybox --install -s /system/xbin

That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.

Good Luck

 

[HotShotAzn]

really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.

 

[anbradle]

I tried this on the 2gb sd image got root. But after I rebooted root was gone.

 

[Homer_S_xda]

I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?

Homer

 

[chhaggerty]

I tried this on the 2gb sd image got root. But after I rebooted root was gone.

Check your steps, especially permissions and the symlink. Works consistently on reboot for me.

 

[chhaggerty]

I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?

Homer

I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin

 

[jtbnet]

It wouldn't work for me without installing in /system/bin and using a symlink to /system/xbin

It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...

root@android:/system/bin # echo $PATH
echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
root@android:/system/bin # ls -l su
ls -l su
su: No such file or directory
root@android:/system/bin # ls -l /system/xbin/su*
ls -l /system/xbin/su*
-rwSr-sr-t root root 76232 2011-02-04 09:08 su
-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic
-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new
-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org

 

[NuroSlam]

Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. First download the following files:

1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2.

Good Luck[/B]

i might take credit for gaining root, but the rest is all you

 

[nswenson]

Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.

Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.

Thanks again!
Nathan

 

[chhaggerty]

Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.

Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.

Thanks again!
Nathan

Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.

 

[jleecong]

Just a suggestion...

Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.

 

[anbradle]

You were right I tried again and now I am rooted after reboot. Thanks

 

[xboxexpert]

Just a suggestion...

Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.

Okay...

 

[slugbug2010]

I am running HC (v2) off a 8gb sd card.

So do I just do these steps to gain root or do I need to partition the sd card first?

Thanks

 

[j4mm3r]

Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".

Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.

You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.

So my advice is to be really careful and understand what you are doing if you decide to install this.

I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.

EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.

 

[NuroSlam]

Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".

Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.

You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.

So my advice is to be really careful and understand what you are doing if you decide to install this.

I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.

EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.

agreed, i was just going for root myslef

 

[jtbnet]

I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.

EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.

In

http://howto.ccroms.net/android_project/build/mod/root

I would have though that the purpose of the changes, specifically;

LOCAL_FORCE_STATIC_EXECUTABLE := true

LOCAL_STATIC_LIBRARIES := libc

Were what should resolve the _mktemp not found?

 

[chhaggerty]

Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".

Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.

You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.

So my advice is to be really careful and understand what you are doing if you decide to install this.

I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.

EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.

Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.

 

[Mikey]

So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?

Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey

 

[NuroSlam]

So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?

Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey

yes, at the stands, its just root access. granted i had my own reasons for this