How to manually root. Download and unzip the SuperOneClick zip file and...
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
shawnbuck said:
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Click to expand...
Click to collapse
Could you? I have this same problem trying to root on my mac.
Sent from my MB860 using XDA App
I basically have this:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v1 /sdcard/
./adbmac push su-v2 /sdcard/
./adbmac push busybox /sdcard/
./adbmac push Superuser.apk /sdcard/
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
./adbmac remount
./adbmac shell
(the following 3 steps may fail which is OK)
# mv /system/bin/su /system/bin/su.bak
# mv /system/xbin/su /system/xbin/su.bak
# mv /system/xbin/busybox /system/xbin/busybox.bak
# busybox cp /sdcard/su-v* /system/xbin
# cd /system/xbin
(try to execute both su-v*, whichever works keep and renamed to su. For this example we'll assume su-v2 is the correct su)
# rm /system/xbin/su-v1
# mv /system/xbin/su-v2 /system/xbin/su
# busybox cp /sdcard/Superuser.apk /system/app
# busybox cp /sdcard/busybox /system/xbin
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# busybox ln -s /system/xbin/su /system/bin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
In this steps you put up previously, you missed remount the /system partition rw.
Also, what OS & software are you guys using? I'm curious to find out what is causing this problem, so we can correct it in SuperOneClick.
Ubuntu 10.10 x64
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# mount -o remount,rw -t yaffs2 /system
Click to expand...
Click to collapse
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# busybox mv /data/local/tmp/su /system/xbin
Click to expand...
Click to collapse
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
gdanko said:
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Whoops, that slipped by. In any case, you can check what /system is mounted on by checking /etc/mtab.
Still getting permission denied when I type su
How are you using su directly?
Also, have you installed superuser and root checker from the market?
Add these steps to the end:
# chmod 06755 /system/xbin/su
# chmod 0755 /system/xbin/busybox
# reboot
When the phone is up, adb shell back in
Unlock the phone
Type su in the console
Accept the Superuser prompt
I am now rooted
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
I've noticed that the phone doesn't like when you call reboot from the terminal on it.
Also, put the instructions in the first post for anyone in the future.
gdanko said:
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
Click to expand...
Click to collapse
Perfect, thanks!
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
agentdr8 said:
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
Click to expand...
Click to collapse
I can confirm this, typing `chmod 06755` doesn't work for me.
Is there a reason we need to set the sgid bit as well?
Probably doesn't need setgid but I left it since it was part of the original instructions.
try with acer liquid mini failed
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
busybox 'permission denied'
what should i do? i am using ubuntu 10.10..thanks for your help...
I have an LG Optimus V, which I am trying to root.
My desktop is a Linux Mint 10 LXDE system, and I think ADB is set up properly, because it has been working fine with my nook color.
I was following directions here: http://forum.xda-developers.com/showthread.php?t=935312
When I try to use SUperOneClick, it freezes up at detecting device (I have debugging enabled, and took the sd out.) Since that wasn't working, I tried to root the device manually, following these instructions:
Code:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
When I try to do the step "busybox chmod +x..." I get a permission denied error. I am running as root on my linux box, but obviously just as a regular user in adb. Is there a chmod command I am missing?
Edit: Trying to get more info here: http://forum.xda-developers.com/showthread.php?p=12467368#post12467368
hello at all
i have a little problem. i buyed a used x10i with older firmware but rooted. first of all i only have debian linux 6 64bit and an virtual windows xp. could update to newest firmware 2.1.1.a.0.6 with seus on virtualbox (i did the "repair"). then the root was gone. so i tryed out every version of superoneclick on virtual windows but not working, it freezes everytime. also tried z4mod and flashtool, not working
so i tried manual with adb (i have installed android sdk). i used the binaries from superoneclick 1.9.5. i think the best is when i post my cmd-session:
(i have to replace the shell-prompt from debian with [debian]$, because the forum says me this is an external link...)
Code:
[debian]$ adb push psneuter /data/local/tmp
1635 KB/s (585731 bytes in 0.349s)
[debian]$ adb push su-v1 /sdcard/
430 KB/s (26256 bytes in 0.059s)
[debian]$ adb push su-v2 /sdcard/
579 KB/s (26264 bytes in 0.044s)
[debian]$ adb push su-v3 /sdcard/
437 KB/s (26324 bytes in 0.058s)
[debian]$ adb push Superuser.apk /sdcard/
2063 KB/s (196521 bytes in 0.092s)
[debian]$ adb shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
property service neutered.
killing adbd. (should restart in a second or two)
[debian]$ adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
# mv /system/bin/su /system/bin/su.bak
# mv /system/xbin/su /system/xbin/su.bak
# busybox cp /sdcard/su-v* /system/xbin
# cd /system/xbin
# busybox chmod +x su-v*
# su-v1
reloc_library[1245]: 3712 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
# exit
[debian]$ adb shell
# su-v2
# exit
# su-v3
# exit
# rm /system/xbin/su-v1
# rm /system/xbin/su-v2
# mv /system/xbin/su-v3 /system/xbin/su
# busybox cp /sdcard/Superuser.apk /system/app
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# su
# exit
# reboot
[debian]$ adb shell
$ su
Permission denied
$
you can see i get a rootshell and mount system, copy su and everything, but when i reboot everything is gone. if i don't reboot and check with "root-checker" it says me that i don't have root access.
what i'm doing wrong? i'm a noob in "hacking" phones but have some knowledge with linux&shells
thanks a lot for some help
could solve it: was using superoneclick on a windows-pc from my friend.works great.. but still iterested in a linux-only solution because i want to develop a shell-script for rooting for linux users
Okay, So I am working on a project for my work. We need to locate and test a tablet to sell to a client. The client needs it rooted. So We got in this Pipo M1. Nice unit for the price. I rooted it via VonDroid-Root and changed the default storage location from the ROM to the internal storage. I let the battery die on it to test battery life, now it will not charge. Two chargers and it never seems to detect a charger, and will not charge. Just boots, shuts down, and repeats. Anyone have any thoughts or Ideas?
Here is the Root script that I ran on it.
Code:
echo off
cls
echo *---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
echo --- Plug in your device, make sure debugging is enabled in Developer Options
echo --- This script will now copy files over to your N101 II
echo.
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo --- Reboot 1/3 - Press Space Bar once the device has rebooted
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo --- Reboot 2/3 - Press Space Bar once the device has rebooted
pause
adb shell id
echo --- If the ID shows as 0/root then continue, otherwise CTRL+C to cancel and start over
pause
adb remount
adb push su /system/bin/su
adb shell chown root.shell /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown root.shell /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
echo --- Installing SuperSU
adb shell chown root.root /system/app/SuperSU.apk
adb shell chmod 0644 /system/app/SuperSU.apk
adb push RootExplorer.apk /system/app/RootExplorer.apk
adb shell chown root.root /system/app/RootExplorer.apk
adb shell chmod 0644 /system/app/RootExplorer.apk
echo Completing Root
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo echo --- Reboot 3/3 - Your N101 II should now be rooted
pause
echo on
I tried the firewire / temproot method I used on 4.3 but temproot failed?
Code:
c:\Users\Fuzzy\Desktop\Misc One Max\Firewater>adb reboot
c:\Users\Fuzzy\Desktop\Misc One Max\Firewater>adb wait-for-device push firewater
/data/local/tmp
7227 KB/s (4522136 bytes in 0.611s)
c:\Users\Fuzzy\Desktop\Misc One Max\Firewater>adb push temproot /data/local/tmp
7440 KB/s (68576 bytes in 0.009s)
c:\Users\Fuzzy\Desktop\Misc One Max\Firewater>adb shell
[email protected]:/ $ chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/temproot
[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/temproot
/data/local/tmp/temproot
run_root_shell, thanks fi01 - https://github.com/android-rooting-tools/android_run_root_shell
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
1|[email protected]:/ $
What am I doing wrong?
Is there a working method for temp root
to satisfy firewater's need?
----------->
Used Sunshine successfully.