So I'm on the Latest official 2.2.1 from Motorola/ATT, but I'm having some issues.
My home button doesn't work at all and I can't get it to work despite my efforts. So I think I just need to do a factory reset and delete everything, I think my rooting and mods to my 2.1 soft ware may have messed everything up. Before I try this, will it delete all my text messages and stuff? or should I back them up with that SMS backup program?
Also, i'm having a hard time rooting it with SuperOneClick, it fails to work completely so does anybody know exactly what commands I need to just root via my terminal?
nevermind I figured it out. Here are the commands if anybody is interested:
./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 6755 /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 copied pasted from somewhere else on this site
Have you tried flashing the 2.2 SBF using RSD Lite? I tried that for a different problem and it worked.
Sent from my MB520 using XDA Premium App
Ok I just reflashed it using the stock recovery then I wiped all the data(factory reset). I backed my stuff up first though. I was wrong in my previous post about how to root using terminal. To correctly root you need to follow this guide to the T. http://www.addictivetips.com/mobile/how-to-root-nexus-one-running-android-2-2-1-from-ubuntu-linux/
I just flashed RC2 and it is loading now...
Related
Code below works as far as getting root via adb
But after reboot I get following error:
Code:
? su
link_image[1717]: 2977 missing essential tablesCANNOT LINK EXECUTABLE
Do you know what's missing here?
Code:
./adblinux push psneuter /data/local/tmp
./adblinux push su-v3 /data/local/tmp
./adblinux push busybox /data/local/tmp
./adblinux shell chmod +x /data/local/tmp/psneuter
./adblinux shell chmod +x /data/local/tmp/su-v3
./adblinux shell
$ /data/local/tmp/psneuter
# exit
./adblinux shell
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/stl5 /system
# busybox cp -vaf /data/local/tmp/su-v3 /system/xbin/su
# ls -l /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# ls -l /system/xbin/su
# rm /system/bin/su
# busybox ln -s /system/xbin/su /system/bin/su
# ls -l /system/bin/su
# busybox cp -f /data/local/tmp/busybox /system/xbin
# busybox chown 0.2000 /system/xbin/busybox
# busybox chmod 0755 /system/xbin/busybox
# ls -l /system/xbin/busybox
# exit
./adblinux install -r Superuser.apk
./adblinux reboot
Hi,
I am new here, but advanced linux user
I have already done this succesfully on my X10i - thanks 1st working howto on linux OS
Theres propably mistake with these steps:
./adblinux shell chmod +x /data/local/tmp/psneuter
./adblinux shell chmod +x /data/local/tmp/su-v3
In my case these commands left errors. They have to simply mark these binaries as executable. But chmod +x * doesnt work (dont ask why ) - so I marked them as executables (su,psneuter,busybox) in desktop linux os before transfer and it worked.
The next mistake is in the line:
busybox cp -vaf /data/local/tmp/su-v3 /system/xbin/su
Because busybox is not yet in the system path - so you have to type:
# /data/local/tmp/busybox cp -vaf /data/local/tmp/su-v3 /system/xbin/su
Until
# /data/local/busybox cp -f /data/local/tmp/busybox /system/xbin
You can use busybox directly.
chmod +x doesn't work on android, you have to use chmod 777 or 666 or the like to get it to work properly.
Semperverus said:
chmod +x doesn't work on android, you have to use chmod 777 or 666 or the like to get it to work properly.
Click to expand...
Click to collapse
Or do it on linux GUI and mark as executable before transfer to Android device
Maybe I'm the only one but this is the method I prefer to use to root my phone. I'm not always sure which OS I'll be working with when I have to do this and this one works on all of them as long as you have the Android SDK.
Put the files into your platform-tools folder to make them easy to find.
Not sure if I need this but I'm not responsible for bricks or any other complication, etc, etc.
adb push psneuter /data/local/tmp
adb push bin/su /data/local/tmp
adb shell chmod 6755 /data/local/tmp/psneuter
$ ./data/local/tmp/psneuter
adb shell
# mount -o rw, remount /dev/block/mmcblk0p12 /system
# rm /data/local/tmp/su /system/bin/su
#chmod 6755 /system/bin/su
exit
really? psneuter only works for 1.26 froyo
I used this method on 1.83 when I first got the phone. Might need to look back into this. Someone asked about this method so I posted it.
Sent from my MB860 using XDA Premium App
I always have problems to root official 2.3 with automatic ways, and found that this caused from some adb miscommunication.
So this is how to do it manual, in case automatic ways stacked.
First install adb-sdk and add its path to system variables, so to don't have to go to adb' s path before you can run it.
Then download doomlord' s rooting tool and extract it to drive C:\DoomLordRoot.v3.
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Preparation steps on device:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) uncheck fast boot from settings -> applications
Click to expand...
Click to collapse
Open windows command prompt window and do the above:
Code:
adb push c:\DoomLordRoot.v3\files\zergRush /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
chmod 777 /data/local/tmp/zergRush
./data/local/tmp/zergRush
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\busybox /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit again from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\su /system/bin/su
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit once more from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\Superuser.apk /system/app/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
cd /data/local/tmp/
rm *
reboot
This is basic what the runme.bat file does, just some paths corrected to point to the right locations.
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Oneclickroot v2. 2 did the work for me or something like this
Sent from my U8800
SS said:
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Click to expand...
Click to collapse
This probably means that rooting failed.
What messages you get when you run zergrush?
dancer_69 said:
This probably means that rooting failed.
What messages you get when you run zergrush?
Click to expand...
Click to collapse
I got messages for sending 149, then 189 zerglings, then messages about not being able to mount, find or write to directories.
It seems like it wasn't able to get root access to be able to run its process.
In any case, I just downgraded to the previous release and then used ZergRush, which worked perfectly
don't work.
try this, it works for my B528 rom!
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7
Thanks to nice Kernel exploid found by zx2c4 http://blog.zx2c4.com/749 and sauriks mempodroid https://github.com/saurik/mempodroid its now very easy to root the nexus-s 4.0.3 firmware without unlooking the BL.
You can just follow this howto http://forum.xda-developers.com/showthread.php?t=1461736 but with this offsets kindly provided by saurik: 0xd7cc 0xad27
If you need a clockworkmod just download rom manager from the market and klick install clock work mod.
have fun
Thanks derpeter, I am looking for the related topic for several days!!!
Will try it later, thanks!!!
thank u dear <3
Worked great! Thanks!
Tested and works. Now running stock OTA rooted ICS.
Checked out the link. Though it stated that it is in the transformer prime thread, the adb commands are still the exact same for nexus s?
Yes the same process works you just have to replace the offsets as it says in the first post.
So the process for the Nexus S would be as follows...
Downloads:
mempodroid
su binary
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 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 Android, 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
Click to expand...
Click to collapse
Doesn't work for me. And it's annoying. These are the comands. I had done something bad?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Sergiu>cd C:/
C:\>adb push mempodroid /data/local
adb server is out of date. killing...
* daemon started successfully *
627 KB/s (37273 bytes in 0.058s)
C:\>adb push su /data/local
2426 KB/s (22364 bytes in 0.009s)
C:\>adb shell
[email protected]:/ $ chmod 777 /data/local/mempodroid /data/local/mempodroid 0xd7cc
0xad27 sh
id /data/local/mempodroid 0xd7cc 0xad27 sh <
Unable to chmod 0xd7cc: No such file or directory
10|[email protected]:/ $ chmod 777 /data/local/mempodroid/data/local/mempodroid 0xd7
cc 0xad27 sh
oid/data/local/mempodroid 0xd7cc 0xad27 sh <
Unable to chmod /data/local/mempodroid/data/local/mempodroid: Not a directory
10|[email protected]:/ $ chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
[email protected]:/ $ /data/local/mempodroid 0xd7cc 0xad27 sh
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # cat /data/local/su > /system/xbin/su
cat /data/local/su > /system/xbin/su
[email protected]:/ # chown 0.0 /system/xbin/su
chown 0.0 /system/xbin/su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # rm /data/local/mempodroid
rm /data/local/mempodroid
[email protected]:/ # rm /data/local/su
rm /data/local/su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\>adb reboot
C:\>
Please help me, I find this metod so f...ing good. I have an i9023, never rooted.
sergiu_s said:
Please help me, I find this metod so f...ing good. I have an i9023, never rooted.
Click to expand...
Click to collapse
I also had trouble following the guide, but then discovered this script, which made the whole process completely automatic.
I'm running stock ICS on i9023.
The script doesn't work for me. I tried it even in Linux. I have stock ics 4.0.3
Sent from my Nexus S using xda premium
Mate u just gain a root. # u log in as root
Sent from my Nexus S using Tapatalk
I saw that, (#), but I don't have root privileges in any application. That's my problem.
Sent from my Nexus S using xda premium
I am not an expert in Android but I think to gain access to app as root would have to go via su app did u try superuser app? I would try it myself but my phone is already rooted via clock mod
Sent from my Nexus S using Tapatalk
I was right mate I just read how to . U haven't got superuser installed obviously. Download from the market and should work.
Sent from my Nexus S using Tapatalk
It worked great guys, thanks to the dev's
I installed superuser and it's works. Thanks guys.
Sent from my Nexus S using xda premium
FYI, this no longer works in 4.0.4. Found out the hard way when I forgot to re-enable the save root option in SuperSU after a nandroid.
The guide works perfectly. I have upgraded my I9020T to 4.0.4 from a AWS 4.0.3 WITHOUT wiping data! Thanks so much!
lethalp1mp said:
FYI, this no longer works in 4.0.4. Found out the hard way when I forgot to re-enable the save root option in SuperSU after a nandroid.
Click to expand...
Click to collapse
ya i did the same thing (didnt run voodoo ota before the 4.0.4 OTA)....looks like google patched this exploit...hope another one comes up so i can root 4.0.4 (without wiping)
nolook said:
ya i did the same thing (didnt run voodoo ota before the 4.0.4 OTA)....looks like google patched this exploit...hope another one comes up so i can root 4.0.4 (without wiping)
Click to expand...
Click to collapse
Yeah i'm also waiting for that!
Sent from my GT-P7300 using XDA
I'm trying to automate some things I do after upgrading nightlies using a shell script. The system seems to execute the shell script (shows messages informing granting of root privileges and successful completion of the script), but the script does not seem to run, ie the changes do not occur. Here's the script if it's of any help :
Code:
#!/system/bin/mksh
# Gain root access
su -
# Replace baseband
rm /system/etc/motorola/bp_nvm_default/*
cp /mnt/sdcard/Download/bp_nvm_default/* /system/etc/motorola/bp_nvm_default/
chown root:root /system/etc/motorola/bp_nvm_default/*
chmod 644 /system/etc/motorola/bp_nvm_default/*
# Make Apex Launcher system app
cp /mnt/sdcard/Download/ApexLauncher.apk /system/app/
chown root:root /system/app/ApexLauncher.apk
chmod 644 /system/app/ApexLauncher.apk
# Move Marimba ringtone to phone
cp /mnt/sdcard/Download/Marimba.ogg /system/media/audio/ringtones/
chown root:root /system/media/audio/ringtones/Marimba.ogg
chmod 644 /system/media/audio/ringtones/Marimba.ogg
I'm amazed there are no replies to this thread.
No one ever tried running a shell script on their rooted phone?
S_xda said:
I'm amazed there are no replies to this thread.
No one ever tried running a shell script on their rooted phone?
Click to expand...
Click to collapse
What did you tried to run the script??, use the terminal or the SManager.
SManager works fine to me
Questions go in the Q&A section