Okay so ChainsDD's Superuser doesnt work on Honeycomb. The reason is a (unnecessary?) hack used by the developer to link properly and use the mktemp function.
To fix this, I downloaded the sources and compiled them again, but this time avoiding the _mktemp hack. Build instructions:
Code:
(get latest CM sources)
# cd <path-to-project-directory>
# repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
# repo sync
(do a generic build)
# source ./build/envsetup.sh
# lunch full-eng
# make
(take a break, this takes a long time)
(fix the su binary)
# cd system/extras/su
# vi su.c
(make the fix, just replace _mktemp with mktemp and remove its declaration)
# mm
(the new su binary should be available in out/target/product/generic/system/xbin)
The fixed binary is attached with this post. Just install Superuser from the market or install it after downloading from ChainsDD's thread (link above). Push the fixed su binary and away you go!!
Code:
# adb push su /system/xbin
# adb shell chmod 4755 /system/xbin/su
Let me know how it goes...
Source Code: https://github.com/j4mm3r/android_system_extras
j4mm3r said:
Okay so ChainsDD's Superuser doesnt work on Honeycomb. The reason is a (unnecessary?) hack used by the developer to link properly and use the mktemp function.
To fix this, I downloaded the sources and compiled them again, but this time avoiding the _mktemp hack. Build instructions:
Code:
(get latest CM sources)
# cd <path-to-project-directory>
# repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
# repo sync
(do a generic build)
# source ./build/envsetup.sh
# lunch full-eng
# make
(take a break, this takes a long time)
(fix the su binary)
# cd system/extras/su
# vi su.c
(make the fix, just replace _mktemp with mktemp and remove its declaration)
# mm
(the new su binary should be available in out/target/product/generic/system/xbin)
The fixed binary is attached with this post. Just install Superuser from the market or install it after downloading from ChainsDD's thread (link above). Push the fixed su binary and away you go!!
Code:
# adb push su /system/xbin
# adb shell chmod 4755 /system/xbin/su
Let me know how it goes...
Source Code: https://github.com/j4mm3r/android_system_extras
Click to expand...
Click to collapse
Works great! My Root is up and working! Thank you!
Updated OP in the other thread to direct people here. Method tested and working perfect. Many thanks to j4mm3r.
How do I make it read/write so I can push the new SU over?
Thanks!
Thank you, gentle sir!
chhaggerty said:
Updated OP in the other thread to direct people here. Many thanks to j4mm3r.
Click to expand...
Click to collapse
Usually this works on the HC image
# adb remount
Or the long form:
# adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
18.4009 said:
How do I make it read/write so I can push the new SU over?
Thanks!
Click to expand...
Click to collapse
j4mm3r said:
Thank you, gentle sir!
Usually this works on the HC image
# adb remount
Or the long form:
# adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
Click to expand...
Click to collapse
Thank you, worked like a charm.
Well, I got the SU pushed over and ran the command to set permissions and rebooted but still no root after reboot.
I just got the nook so I am probably do something wrong.
Stuck on root access issue
Many thanks to those who worked on HoneyComb (HC) v4 on eMMC and the rooting solution.
I have root after first flashing to eMMC and checking with terminal. I downloaded and pushed the new SU and still appear to have root -- according to terminal.
The Superuser app opens just fine, but Root Explorer crashes and Rom Manager/CWR complain about not having elevated rights. I *think* I have the latest version of both.
Note: I have only run the two commands above -- and not the list of commands in the OP.
What am I missing here?
Many thanks,
Landlocked
When I type SU in terminal emulator I get an error stating:
"reloc_library[1315]: 1749 cannot locate _mktemp..."
one way to quickly check if you have it working is to do the following:
- Get to a shell:
# adb shell
(this should give you the "[email protected]:/ #" prompt)
- Become un priviledged:
[email protected]:/ # su 1000
[email protected]:/ $
(the "$" indicates that you are no longer root)
- Try to become root again:
[email protected]:/ $ su
This should open up the Superuser dialog asking you to allow or deny superuser request, which means that its working as expected. If you need more help then join on #nookolor on irc.freenode.net (see http://nookdevs.com/IRC for instructions for IRC). I can help you there.
landlocked said:
Many thanks to those who worked on HoneyComb (HC) v4 on eMMC and the rooting solution.
I have root after first flashing to eMMC and checking with terminal. I downloaded and pushed the new SU and still appear to have root -- according to terminal.
The Superuser app opens just fine, but Root Explorer crashes and Rom Manager/CWR complain about not having elevated rights. I *think* I have the latest version of both.
Note: I have only run the two commands above -- and not the list of commands in the OP.
What am I missing here?
Many thanks,
Landlocked
Click to expand...
Click to collapse
Did you replace the "su" binary with the one in the first post?
When I type SU in terminal emulator I get an error stating:
"reloc_library[1315]: 1749 cannot locate _mktemp..."
Click to expand...
Click to collapse
j4mm3r said:
one way to quickly check if you have it working is to do the following:
- Get to a shell:
# adb shell
(this should give you the "[email protected]:/ #" prompt)
- Become un priviledged:
[email protected]:/ # su 1000
[email protected]:/ $
(the "$" indicates that you are no longer root)
- Try to become root again:
[email protected]:/ $ su
This should open up the Superuser dialog asking you to allow or deny superuser request, which means that its working as expected. If you need more help then join on #nookolor on irc.freenode.net (see http://nookdevs.com/IRC for instructions for IRC). I can help you there.
Click to expand...
Click to collapse
I get this error:
Thanks for the info, J4mm3r. I can switch from root to standard user back to root on the NC just fine. None of the programs that are supposed to ask for root are prompting me -- as they do on my Droid 2.
I downloaded the new SU (above) and pushed it over using the sample commands.
I dont think you have replaced the "su" binary with the one that I posted.
18.4009 said:
I get this error:
Click to expand...
Click to collapse
Sorry, for the clutter, but I have appeared to have made some progress. I used the new SU (above) and repeated the steps in this thread:
http://forum.xda-developers.com/showthread.php?t=941445
Rom Manager now properly asks for for SU permission and installed CWR. Root Explorer still crashes, but that may be a file version issue.
j4mm3r said:
I dont think you have replaced the "su" binary with the one that I posted.
Click to expand...
Click to collapse
Strange I pushed you su over to /system/bin and now I have root
This is working perfectly. Thank you so much. All my root apps work properly now.
thanks j4mm3r for the fix
now we just need a fresh hcv5 rooted image to play with.
landlocked said:
Sorry, for the clutter, but I have appeared to have made some progress. I used the new SU (above) and repeated the steps in this thread:
http://forum.xda-developers.com/showthread.php?t=941445
Rom Manager now properly asks for for SU permission and installed CWR. Root Explorer still crashes, but that may be a file version issue.
Click to expand...
Click to collapse
I did the exact same thing, used new SU and completed the steps in the thread above and just installed busybox from titanium bu. Root Explorer is working fine for me.
j4mm3r you are da man! I have a tear in my eye right now, as I am so happy that this got Superuser working. I had lost root and your fix got it back and also now Superuser is asking for permission on everything I have tried thus far (SetCPU, RootExplorer, Root Check, Quick Boot).
The dev support surrounding HC on the NC is nothing short of spectacular. So many thanks go out to so many dang-smart people out there.
THANKS!!
Glad to be of help...
360Razir said:
j4mm3r you are da man! I have a tear in my eye right now, as I am so happy that this got Superuser working. I had lost root and your fix got it back and also now Superuser is asking for permission on everything I have tried thus far (SetCPU, RootExplorer, Root Check, Quick Boot).
The dev support surrounding HC on the NC is nothing short of spectacular. So many thanks go out to so many dang-smart people out there.
THANKS!!
Click to expand...
Click to collapse
Related
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it [email protected]
I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below
Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
1 Click Root Method
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
Manual Method
cd C:\android-sdk\tools
adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install C:\fascinate\Superuser.apk
This is permanent.
I just updated the files here with the latest su / superuser.apk / busybox
Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/showthread.php?p=8086738#post8086738
Dirrk said:
All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Please let me know if I posted something wrong.
Click to expand...
Click to collapse
does it stick after reboot?
Its supposed to be a temporary root so i doubt it will.
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.
Sent from my SPH-D700 using XDA App
see below.
confirmed root.
Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.
You also have a typo near the end "scard" instead of "sdcard".
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.
And yes this is permanent
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.
Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
cliffr39 said:
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
Click to expand...
Click to collapse
It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
xirnibor said:
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
Click to expand...
Click to collapse
Your USB mode might be set wrong. Flip it to whatever it's not at, and try again.
i forgot this laptop didnt have the updated usb drivers from android sdk, downloading then will try again. i have tried so far with the sdcard mounted and unmounted, while in usb debugging mode. will post after updates
How long do you actually have to wait after the execting the rage.bin file?
itznfb said:
How long do you actually have to wait after the execting the rage.bin file?
Click to expand...
Click to collapse
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
namebrandon said:
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
Click to expand...
Click to collapse
ok... running the rage.bin locked up my device twice but on the third try it worked. another fascinate rooted
xirnibor said:
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
Click to expand...
Click to collapse
su is a file (for our purposes right here, anyway). Unless you explicity specify its path, it needs to be in the same directory you're running the adb command from.
If you installed the Android SDK per guidelines, adb should be in your PATH environment variable, and you should be able to execute it from any directory. If you didn't do that, then for the sake of simplicity, copy all the files referenced in the original steps to your working directory. From your post above, it appears that is c:\downloads\android\android\tools\
I got stuck at cat /sdcard/su > . Is that supposed to be > .? It won't let me enter that...There's not something else that's supposed to be there?
EDIT: I get the same error faspalma
I'm stuck at that point too. cat /sdcard/su > . returns "cannot create .: is a directory"
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Thanks for the info. Just a quick note that on Cyanogenmod 6.1 RC2 (Nexus One), the su binary is actualy at /system/xbin/su rather than /system/bin/su
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Click to expand...
Click to collapse
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
Click to expand...
Click to collapse
For #3, somebody may want to replace system fonts to support other languages than English. I have done that to Android 2.1 phones too.
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
Thank you
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
linux$ adb pull /system/bin/su
Click to expand...
Click to collapse
Thanks Man, this was the part i didn't get and it's working now
PTzero said:
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
Click to expand...
Click to collapse
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
califrag said:
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
Click to expand...
Click to collapse
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
dark79 said:
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
Click to expand...
Click to collapse
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Will this work on just linux or windows?
You can do it on windows using ADB
califrag said:
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Click to expand...
Click to collapse
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
sminker said:
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
Click to expand...
Click to collapse
Make sure to download the 'eclair\froyo' version.
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
sminker said:
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
Click to expand...
Click to collapse
use adb shell and go into /data/data and do an 'ls'
remove any directory there that looks like 'com.noshofou'
i was able to use z4root to get it installed
when I do:
cat /data/local/su > su
I get:
Cannot create su: remote access failed
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Is there any advantage to put the binary into xbin versus bin
discourse said:
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Click to expand...
Click to collapse
I would like a windows walkthrough also
This thread is a collaboration by myself, paxChristos, DooMLorD, & amishxda. Please give credit where credit is due. Thanks.
This method has been confirmed to work on all models of the Xperia PLAY - R800x / R800i / R800a / R800at. Also works perfectly with the Xperia Arc.
WARNING: This doesn't work, however, on the Verizon Wireless R800x v2.3.2. Please update to v2.3.3 before rooting. - confirmed by paxChristos
WARNING #2: Confirmed that this doesn't work with 4.0.2.A.0.62
MAJOR WARNING - ICS (4.x) doesn't work with it & any update to GB (2.3.x) after November 2011 won't either.
paxChristos said:
The exploit used in this toolkit was patched back in November of 2011. No more updates will come from the exploit devs.
Click to expand...
Click to collapse
Thanks to everyone who tested this out for me & confirmed that it worked!
NOTE: Before you attempt to root your phone, please ensure that you have the Android SDK installed. It has the adb binary within it.
Android SDK
http://developer.android.com/sdk/index.html
All needed files have been attached for this process to work correctly.
Note: I didn't create zergRush. I only found the method to implement permanent root after zergRush has done its job.
Automatic Root
1) SuperOneClick
SuperOneClick now has the zergRush method built-in.
Please see the source thread if you have any questions.
Downloads available @ http://shortfuse.org/
Source: http://forum.xda-developers.com/showthread.php?t=803682a
2a) DooMLoRD's Easy Rooting Toolkit [v4] (zergRush Exploit)
This is the one click method that everyone has been asking for & DooMLoRD has answered with this.
DooMLoRD said:
UPDATE: added v4, with newest zergRush binary (21 Nov 2011) and few corrections/additions to script
UPDATE: most companies are patching the exploit in the latest firmwares (Samsung, Motorola, Sony Ericsson, etc)
UPDATE: added v3, with newest zergRush binary (16 Nov 2011) and newer superuser files
UPDATE: added v2, with newest zergRush binary (10 Nov 2011) and newer superuser files
[ support the developers ]
There have now been nearly 440,000 downloads of this easy rooting toolkit for various devices (see list here), and many more if you include variations/different translations, etc that use it.
Don't be a leech, buy me a coffee/beer/etc (and use the "Thanks" button!). Imagine if every user of this tool had donated me even $1...
if you want to support Revolutionary Team (creators of the Exploit which makes this possible ) you can donate to Revolutionary Team's PayPal Donation Link
[ Info ]
(WINDOWS ONLY)
WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES!
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
[ Tested on ]
Tested & Reported to be working on the THESE devices
[ Credits ]
Credits go to all those involved in making this possible!
zergRush Binary from: Revolutionary - zergRush local root
Inspired from: http://forum.xda-developers.com/showthread.php?t=1312859
[ Donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc My PayPal Donation Link
if you want to support Revolutionary Team (creators of the Exploit which makes this possible ) you can donate to Revolutionary Team's PayPal Donation Link
[ Download Links ]
DooMLoRD_v4_ROOT-zergRush-busybox-su.zip <NEW>
DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
DooMLoRD_v1_ROOT-zergRush-busybox-su.zip
[ UnRooting ]
want to unroot? read this
[ Scripts posted by others ]
Rooting script for Linux
Rooting script for MAC OSX
Toolkit for GT-I9000
For Atrix 2
For VIZIO vTab1008
regards,
DooMLoRD
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1319653
My deepest thanks to DooMLoRD for automating & simplifying this process!
2b) amishxda's modified Linux script (based on paxChristos' script // Source: DooMLoRD's Easy Rooting Toolkit)
amishxda said:
Update: Updated as per DooMLoRD's v4.0 script with zergRush binary of 21 Nov 2011 and with makespace which deletes Google Maps if there is not enough space.(< 6MB)
Hello
I am completely new to Android but not at all new to Linux.
I used paxchristos script (ran commands manually though) to root my Sony Ericsson Live with Walkman. (WT19i / Android 2.3.4 / Build 4.0.2.A.0.58)
Source threads used:
http://forum.xda-developers.com/showthread.php?t=1319653
http://forum.xda-developers.com/showthread.php?p=18615502
In an attached file, I fixed/modified/added few things in paxchristos script. Here is the detail:
1) Fixed error in symlinking su. (source/destination were same)
2) Don't delete (and recreate) /data/local/tmp/ directory unnecessarily, just delete its contents
3) Uses dd instead of cp (because DooMLoRD's script does, dont know why!). Update: as per anantshri, dd is used because cp has been known to give errors.
4) If your system already has 'adb' then it uses system 'adb' instead of one in zip-archive.
5) Updated zip archive to contain the latest files from DooMLoRD's archive (paxchristos archive seemed old)
Please try/verify and let me know if I missed something.
Thanks.
Click to expand...
Click to collapse
zergRush_automated_Linux_root.zip
Source: http://forum.xda-developers.com/showthread.php?p=20869699
Original script by paxChristos: http://forum.xda-developers.com/showthread.php?p=18615502#post18615502
Manual Root
3) Noob Friendly Guide
paxChristos has provided me with a very comprehensive guide regarding this process for anyone that absolutely wants a step-by-step layout.
It has been attached to this thread within a 7-zip file. If you would like the faster route, please follow my own instructions.
Download PDF Guide
4) Advanced Android Users (& those that are aiming to be) Guide
Download all required files. Drivers have been provided courtesy of paxChristos for anyone that needs them.
Do the following within a cmd (as administrator) or terminal prompt (through sudo or root user)
Code:
adb shell mkdir /data/local/tmp
adb push zergRush /data/local/tmp
adb chmod 755 /data/local/tmp/zergRush
adb shell
cd /data/local/tmp/
./zergRush
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
Alternate: adb push Superuser.apk /system/app
installed BusyBox (if it doesn't show up on the system already) via any busybox installer market app
Ran SuperUser & verified settings
Code:
adb reboot
Android should be completely rooted!
Automatic Unroot
DooMLoRD's Unrooting Script
DooMLoRD said:
UNROOTING SCRIPT v1.0
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED MY FILES (Easy Rooting Toolkit) FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
[ DISCLAIMER ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK
now that the warning is clear (hopefully) lets get to unrooting
Tested on:
Sony Xperia ARC
so here is the file.. (WINDOWS ONLY)
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME-UNROOT.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) unroot ur device using special script
(2) remove Busybox and assocaited symlinks
(3) remove SU files and assocaiated data
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
if all goes well u will get output LIKE THIS
regards,
DooMLoRD
DooMLoRD_v1_UNROOTING.zip
Click to expand...
Click to collapse
Sources/Acks/Links/Attachments
Sources:
http://forum.xda-developers.com/showthread.php?t=1312082
http://forum.xda-developers.com/showthread.php?t=1296916
http://androidsu.com/superuser/
Acknowledgments:
Ch4lky - Sony Ericsson Xperia fix for zergRush (Revolutionary Team)
ieftm - zergRush (Revolutionary Team)
Revolutionary Team - many thanks to everyone who worked on zergRush
paxChristos - provided debug info to Ch4lky & created the Noob PDF guide
ChainsDD - Superuser & su
DooMLoRD - for the awesome rooting & unrooting scripts
CLShortFuse - SuperOneClick
Cl8rs - identified possibility for Xperia PLAY to use zergRush
XenonMD - confirmed that this works on the R800i
barlw - confirmed that this works on the R800a
Luniticus - confirmed that this works on the R800at
AndroHero - recommended the alternate method for pushing the Superuser.apk to /system/app for working around stability issues
amishxda - for updating paxChristos' script to work on more phones from Linux
Everyone else - who have confirmed that it works on many other phones
Please let me know any new information to smooth out the process. I'll modify this post to ensure it's a smooth one.
zergRush (no longer attaching due to new updates from the devs) - supports a large amount of phones
https://github.com/downloads/revolutionary/zergRush/zergRush.zip
Superuser v3.0.7 apk
http://goo-inside.me/superuser/Superuser-3.0.7-efgh-signed.zip
su v3.0.3.2 binary
http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip
Thanks!!!
Edit: Please PM me if you were a part of discovery, research or one of the tools listed.
Thanks I wasn't trying to be stuck up or anything, just wanted credit.
Awesome...I've been watching the Zerg thread with bated breath and I didn't have to wait long.
i just wish I had my damn usb cable with me right now.
Big thanks to all involved, I will be trying this asap.
Is there a way to un-root? Just curious...
Step-by-literal-step
If you feel like seeing the step by step PDF Guide, go to these : attached to post #1, or:
At dropbox.com: http://db.tt/RaAUnzjW
At Ubuntu one: http://ubuntuone.com/64OujxgkGMv1N2QSoPmXin
or at Filesonic: http://www.filesonic.com/file/2730341354
If you're doing the script rooting in linux, do these things first
1) Download and unzip file (it's below at dropbox.com or ubuntu one; or it's posted in #1 as an attachment)
2) open up terminal
3) type "su"
4) enter your password
4a) if you don't have su set up
4b) type "passwd"
4c) enter you username password (no, there will be no ***s to show that you entered anything, just hit enter when you've inputted your password)
4d) input a password for root (unix) (no, there will be no ***s to show that you entered anything, just hit enter when you've inputted your password)
4e) type "su" and enter your password
5) navigate to location you unzipped the file to (chrome default download is /home/[your username]/Downloads)
6) type "chmod 755 runme-linux"
7) type "cd files"
8) type "chmod 755 adb"
9) type "cd .."
10) type "./runme-linux"
11) type "exit" x2 to exit terminal
12) enjoy your rooted play!
Here's the script (and all applicable files) (totally ripped off DooMLoRD's code, thank him, please, for me), go to these links:
At dropbox.com: http://db.tt/a4H6QFfV
At Ubuntu one: http://ubuntuone.com/7mD63kpsKzGmaou5hcftBV
Here's the linux script code
Code:
#!/bin/bash
#This is DooMLoRD's script for windows. I've ported it to linux
#Somethings to remember
#1) Chmod this file!! ("chmod 777 runme-linux")
#2) Run this script as su in terminal (if you haven't set up your su password run the command "passwd" in terminal, it'll ask you for your username password, and then you'll type in a root password. NOTE: You will not see any changes (i.e. *** representing typed letters) but the password is still being inputted.
#I skipped all of DooMLoRD's info because I'm using VIM and don't feel like rewritting it
echo "--Starting---"
echo "---Killing the adb server to make sure that there are no problems---"
./files/adb kill-server
echo "---Waiting for Device---"
./files/adb wait-for-device
echo "---Cleaning out any previous zergRush attempts---"
./files/adb shell rm -r /data/local/tmp
echo "---Creating temp folder for zergRush---"
./files/adb shell mkdir /data/local/tmp
echo "---Pushing zergRush---"
./files/adb push ./files/zergRush /data/local/tmp/
echo "---Fixing permissions for zergRush---"
./files/adb shell chmod 755 /data/local/tmp/zergRush
echo "---Running zergRush---"
./files/adb shell /data/local/tmp/zergRush
#If it gets stuck here for a long time then try:
#1)disconnect usb cable and reconnect it
#2)toggle "Usb Debugging" (first disable it then reenable it")
echo "---Device found!---"
./files/adb wait-for-device
echo "---Pushing busybox---"
./files/adb push ./files/busybox /data/local/tmp
echo "---Fixing busybox permissions---"
./files/adb shell chmod 755 /data/local/tmp/busybox
echo "---remounting system---"
./files/adb shell /data/local/tmp/busybox mount -o remount,rw /system
echo "---copying busybox to /system/xbin---"
./files/adb push files/busybox /system/xbin
echo "---fixing ownership and permissions---"
./files/adb shell chown root.shell /system/xbin/busybox
./files/adb shell chmod 04755 /system/xbin/busybox
echo "---installing busybox---"
./files/adb shell /system/xbin/busybox --install -s /system/xbin
echo "---cleaning up---"
./files/adb shell rm -r /data/local/tmp/busybox
echo "---pushing SU binary---"
./files/adb push ./files/su /system/bin/su
echo "---correcting ownership and permissions for SU---"
./files/adb shell chown root.shell /system/bin/su
./files/adb shell chmod 06755 /system/bin/su
echo "---correcting symlinks---"
./files/adb shell rm /system/xbin/su
./files/adb shell ln -s /system/bin/su /system/xbin/su
echo "---Pushing Superuser app---"
./files/adb push ./files/Superuser.apk /system/app/
echo "--cleaning---"
./files/adb shell rm -r /data/local/tmp
echo "---rebooting---"
./files/adb reboot
echo "---All done, your Xperia Play has been rooted by DooMLoRD---"
echo "---This script has been ported by paxchristos!!---"
echo "---If have any questions, feel free to email me @ [email protected]"
[Removed walkthrough because it's in the PDF guide. And the PDF guide has pictures. Pretty, pretty pictures of unicorns. Or command line. You decide.]
Thank you to: cl8rs for stumbling up zergRush,
Ch4lky, ieftm, and the Revolutionary team for making (and updating zergRush)
CrimsonSentinal13 for getting us from adb root to phone rooted!
DooMLoRD for doing the script in windows, and giving me something to work off of!
Have fun people, and enjoy!!
Note: With the stock kernal, we cannot overclock, but you can underclock your cpu
Note2: Drivers were added to the first post (Crimsonsentinal13) for sake of keeping everything simpler added drivers for Xperia Play -- to get them to work (if you don't already have them installed, goto device manager, find the SEMC driver (it might show up as android device or unknown device) then update driver, and point it to this zip (unzipped, of course)
Note3: Android SDK Download link: http://developer.android.com/sdk/index.html
Note4: Unrooting?? Who would want to unroot?? One way I unrooted (using my wife's Casio Commando was to uninstall superuser.apk, and the busybox installer (i know, i didn't get rid of everything) but at that point, unless the Verizon/Phone Company employee is a genius, they won't know whether or not you're rooted
Note5: OTA Updates. We don't know what'll happen. If one comes, DENY until we can figure out what'll happen... Most likely, it'll just lose root (hopefully temporarily, we won't know until we get there) but if it bricks all the rooted Plays, I don't want an angry mob with pitchforks at my or Crimsonsentinals13's doorstep
Note6: Updated guide!! Hopefully I fixed all the errors that were in there before (thank you to all the users that pointed them out to me) and added a few things.
Note6B: Somebody had a problem with a busybox installer not downloading from the android market. attached a free one off android market that I used. I only have guesses why this happened (pm setInstallLocation 2...?) but here one is so you have that option as well...
Note6C:I also attached insecure adb. Insecure ADB is COMPLETELY OPTIONAL and should only be downloaded and installed AFTER YOU HAVE ROOT if you want to use root in adb after you reboot. Again COMPLETELY OPTIONAL and you won't necessarily need it.
Note7: As jeffkhlam found out, at no point do you need fastboot. This doesn't unlock the bootloader (no custom roms.)
Note8: If you're having issues doing this, I'll be hopping on and off the thread between 8:00am until about 11:00pm Central Standard Time. If it's not between those hours, please wait, we'll get around to helping you!
Will it work with a locked bootloader
doua27 said:
Will it work with a locked bootloader
Click to expand...
Click to collapse
Yep. My Xperia PLAY is brand new & I got it to work w/o unlocking the bootloader.
I think you forgot the Windows driver you mentioned....
sorry, i was doing it all in linux, and i forgot them they're updating in 5 seconds...
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
CrimsonSentinel13 said:
All needed files have been attached.
Download all required files.
Do the following within a cmd or terminal prompt
Code:
adb shell mkdir /data/local/tmp
adb push zergRush /data/local/tmp
adb chmod 755 /data/local/tmp/zergRush
adb shell
cd /data/local/tmp/
./zergRush
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
installed BusyBox (if it doesn't show up on the system already) via any busybox installer market app
Ran SuperUser & verified settings
Code:
adb reboot
Android should be completely rooted!
Sources:
http://forum.xda-developers.com/showthread.php?t=1312082
http://forum.xda-developers.com/showthread.php?t=1296916
http://androidsu.com/superuser/
Acknowledgments: Ch4lky, ieftm, paxChristos, ChainsDD, Cl8rs
Please let me know any new information to smooth out the process. I'll modify this post to ensure it's a smooth one.
Click to expand...
Click to collapse
So if i do this and root the device but still locked bootloader does that mean that i cant install cyanogenmod?
But can used root applications?
garner said:
So if i do this and root the device but still locked bootloader does that mean that i cant install cyanogenmod?
But can used root applications?
Click to expand...
Click to collapse
Yes that's correct it's only for root apps etc. You need to unlock your bootloader for flashing custom roms and kernels. So no CyanogenMod without unlocking your BL.
Regards Dousan...
Is this is also the correct steps for r800i's ?
I'm on 2.3.3 with my r800i , i won't lose anything using this method, with a locked bootloader, just want/need root access lol
Cl8rs said:
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
Click to expand...
Click to collapse
Same thing here....
CoconutWillie said:
Same thing here....
Click to expand...
Click to collapse
I think he forgot a 'cd' in step 16:
cd /data/local/tmp/zergRush 'enter'
Regards Dousan...
Alright, so after numerous tries i finally got my phone rooted. Big thanks for all the instructions.
Cl8rs said:
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
Click to expand...
Click to collapse
Make sure that /data/local/tmp has permissions to give you full access.
tekken179 said:
Is this is also the correct steps for r800i's ?
I'm on 2.3.3 with my r800i , i won't lose anything using this method, with a locked bootloader, just want/need root access lol
Click to expand...
Click to collapse
I don't know how it works with the R800i. Please try it & let us know how it works.
Dousan said:
I think he forgot a 'cd' in step 16:
cd /data/local/tmp/zergRush 'enter'
Regards Dousan...
Click to expand...
Click to collapse
zergRush isn't a directory, it's a binary. Using the cd command won't work on it.
See the guide I posted, now has info to get past annoying stutters
Anybody stuck at step 16, input the following commands
1) cd /data/local/tmp
2) rm boomsh
3) rm sh
4) continue on with rooting!
Sent from my R800x using XDA App
** This is completely unsupported!!!!!!! **
ALL credit goes to saurik for the root method, Jason A. Donenfeld (zx2c4) for finding the exploit, alpharevx for finding the offsets and initial confirmation on the Transformer Prime and viperboy for finding it and posting it in his thread. I did not research, find, or develop this root method!
Mods, if I've done anything wrong, please feel free to remove this thread.
You will need to know how to use ADB commands, otherwise, use viperMOD PrimeTime!!!!!!!!!!!!!!!!!!!!!!!!.
Downloads:
mempodroid binary
su binary
Root:
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
HOPEFULLY everyone has learned their lesson and will also install Voodoo Rootkeeper as well!!!!!!!!!!!!!!!!!!!! R
Enjoi!!!!!!!!!!!!!!!
** Feb 21 2012 Edit **
Works on 9.4.2.14
** Feb 09 2012 Edit **
Works on 9.4.2.13
** Jan 25 2012 Edit **
Changed the mount command - thanks viperboy!
Added steps to possibly resolve issues with previously rooted systems
Changed a few steps to be a little bit easier.
**Jan 24 2012 Edit **
Some people are reporting issues with this method. I suspect this is due to previously having root or other altered files. A method that has worked for some is to update to 9.4.2.11.1 and then following the above procedures. Please note, this firmware release is unofficial and at this time THERE IS NO DOWNGRADE PATH.
i keep getting permission denied after
adb shell /data/local/mempodroid 0xd9ec 0xaf47 mount -o remount,rw '' /system
i missed a chmod step, add it just now.
run:
adb shell chmod 777 /data/local/mempodroid
and then pick up right where you left off.
as i am not root nor superuser .. i don't even get access
/ $ cd data
~ $ ls
ls: can't open '.': Permission denied
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
insane111 said:
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
Click to expand...
Click to collapse
click on the window, you should be able to continue typing
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
for some odd reason i cant type anything else after on that window..
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
insane111 said:
for some odd reason i cant type anything else after on that window..
Click to expand...
Click to collapse
updating!
10 char
toby77jo said:
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
Click to expand...
Click to collapse
no offense, you may want to just wait for the one click root.
Tairen said:
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
Click to expand...
Click to collapse
updated, should be working now.
hehe that is fine .. not offended
se1000 said:
updated, should be working now.
Click to expand...
Click to collapse
thank you very much sir.. it work...
insane111 said:
thank you very much sir.. it work...
Click to expand...
Click to collapse
NICE!!!!!!!!!!!!!!!!!!!!
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Tairen said:
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Click to expand...
Click to collapse
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
se1000 said:
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
Click to expand...
Click to collapse
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Tairen said:
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Click to expand...
Click to collapse
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
se1000 said:
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
Click to expand...
Click to collapse
Sounds good, will try again and update!
Background: On a rooted device, I installed busybox via the BusyBox Pro app, with the "symlinks" option checked. Afterwards, wifi stopped working, root stopped working, adb stopped working, and a lot of tasks started failing with "sh: applet not found".
The problem: BusyBox Pro 8.0 replaces /system/bin/ash with a symlink to busybox. This was problematic on my device, where /system/bin/sh was a symlink to ash, so now 'sh' is actually calling busybox, and this particular compilation of busybox didn't have 'sh' support compiled in, hence the "sh: applet not found" error everytime anything tried to call sh, which as it happens, is a lot! The bug was fixed quickly with a 8.1 release, but due to suspected caching policies on the Google Store, a lot of people still got the old release even after this was fixed!
Here's how I fixed this:
Prerequisite: You'll need a replacement sh binary. On another device, which was also an ARM device, sh was symlinked to 'mksh', and I just took this. You might want to verify that the binary works on your broken device before completing the final steps below.
Initial Wifi
It's only DHCP that is failing (on the "Obtaining IP address..." step), so go into your Wifi Settings, forget the network, add it again, and change DHCP to "static", manually fill in the appropriate IP info for your network, and you'll be good to go (encrypted network is fine).
Getting a Root terminal
Download KBOX from http://kevinboone.net/kbox.html
In KBox, menu -> more -> preferences, change shell -> "command line" to "/system/bin/ash"
su -s /system/bin/ash
Remounting /system as RW
In theory, all you should need to do is: busybox mount -o remount,rw /system
This didn't work for me, and I got a "permission denied (are you root)" error, I guess because the system was no longer booting properly. I had to redo some of the steps involved in rooting my device, in my case:
On phone:
mkdir /data/local/lib
echo ro.kernel.qemu=1 > /data/local.prop
reboot
(wait for reboot, and get into a root terminal again as per the above)
On PC (from previous files used for rooting my device):
adb push lsm_disabler.ko /data/local/lib/
Oh phone:
insmod /data/local/lib/lsm_disabler.ko
rm /data/local/lib/lsm_disabler.ko
cat > /data/local.prop
From this point, I was able to remount successfully:
mount -o remount,rw /system
Fixing sh
Now on your PC, push the replacement binary to /system/bin, in my case:
adb push mksh /system/bin
On phone:
cd /system/bin
busybox ln -sf sh mksh
Verify now that "./sh" gives you a working terminal.
If all is good:
mount -o remount,ro /system
reboot
All done! Wow, this saved me sending my device back to Japan, since it's still using the stock bootloader and there are now available update.zip's out there. Good luck everyone, feel free to ask questions :>
P.S. I'm going to contact BusyBox Pro's author now with some suggestions to prevent these kind of problems happening in the future.
Deleted.
Deleted.
I rant into the same problem on my Galaxy Tab. Thanks for this, it saved my day!
A little correction to this little thing:
Kinslayer81 said:
On phone:
cd /system/bin
busybox ln -sf sh mksh
Click to expand...
Click to collapse
This worked for me:
cd /system/bin
ln -sf mksh sh
chmod 755 sh
Thank you
Just want to say thanks.
Your Posting helped me out with the Problems on my htc flyer.
I installed BusyBox Pro by Stephen (Stericson) to fix a missing symlinks problem that I had after installing JRummy's Busy Box. I then encountered the applet not found problem and then just reinstalled JRummy's version and it fixed it without having to do anything else.
Kinslayer81 said:
Background: On a rooted device, I installed busybox via the BusyBox Pro app, with the "symlinks" option checked. Afterwards, wifi stopped working, root stopped working, adb stopped working, and a lot of tasks started failing with "sh: applet not found".
The problem: BusyBox Pro 8.0 replaces /system/bin/ash with a symlink to busybox. This was problematic on my device, where /system/bin/sh was a symlink to ash, so now 'sh' is actually calling busybox, and this particular compilation of busybox didn't have 'sh' support compiled in, hence the "sh: applet not found" error everytime anything tried to call sh, which as it happens, is a lot! The bug was fixed quickly with a 8.1 release, but due to suspected caching policies on the Google Store, a lot of people still got the old release even after this was fixed!
Here's how I fixed this:
Prerequisite: You'll need a replacement sh binary. On another device, which was also an ARM device, sh was symlinked to 'mksh', and I just took this. You might want to verify that the binary works on your broken device before completing the final steps below.
Initial Wifi
It's only DHCP that is failing (on the "Obtaining IP address..." step), so go into your Wifi Settings, forget the network, add it again, and change DHCP to "static", manually fill in the appropriate IP info for your network, and you'll be good to go (encrypted network is fine).
Getting a Root terminal
Download KBOX from http://kevinboone.net/kbox.html
In KBox, menu -> more -> preferences, change shell -> "command line" to "/system/bin/ash"
su -s /system/bin/ash
Remounting /system as RW
In theory, all you should need to do is: busybox mount -o remount,rw /system
This didn't work for me, and I got a "permission denied (are you root)" error, I guess because the system was no longer booting properly. I had to redo some of the steps involved in rooting my device, in my case:
On phone:
mkdir /data/local/lib
echo ro.kernel.qemu=1 > /data/local.prop
reboot
(wait for reboot, and get into a root terminal again as per the above)
On PC (from previous files used for rooting my device):
adb push lsm_disabler.ko /data/local/lib/
Oh phone:
insmod /data/local/lib/lsm_disabler.ko
rm /data/local/lib/lsm_disabler.ko
cat > /data/local.prop
From this point, I was able to remount successfully:
mount -o remount,rw /system
Fixing sh
Now on your PC, push the replacement binary to /system/bin, in my case:
adb push mksh /system/bin
On phone:
cd /system/bin
busybox ln -sf sh mksh
Verify now that "./sh" gives you a working terminal.
If all is good:
mount -o remount,ro /system
reboot
All done! Wow, this saved me sending my device back to Japan, since it's still using the stock bootloader and there are now available update.zip's out there. Good luck everyone, feel free to ask questions :>
P.S. I'm going to contact BusyBox Pro's author now with some suggestions to prevent these kind of problems happening in the future.
Click to expand...
Click to collapse
This helped get my wifi back after flashing a kernel.
Hey there,
I've got the same problem.
After reinstalling the ROM everything works fine,
but when I try to install busybox, I get the same failure everytimes.
How can I prevent it?
Do I have to follow the steps above?
And where do I get the sh binary from?
Sorry guys, I'm a little confused and hope you may help me..
Thanks!!
Kbox not open in my ics when I open it its automatically closed
And i want to ask the script su -s /system/bin/ash where i put this script