Related
Hello!
I am use this Tutorial to rooting my Hero: http://forum.xda-developers.com/showthread.php?t=543571
How i can unrooting my Hero? I think, its possible, because the boot.img dont replaced with a other rom...
I found this Command *thanks!*:
* adb shell mount /system
* adb shell rm /system/app/Superuser.apk (if you have it)
* adb push su /system/bin/
* reboot
Click to expand...
Click to collapse
.. the problem is, i havent the original su
Can someone upload the original su?
Do I need to change the rights?
*from Tutorial*
adb shell chmod 4755 /system/bin/su
Click to expand...
Click to collapse
Big Thanks! Nice Community!
*sorry, my english is very bad >.< xD*
My advice would be, keep reading. Page 5 or 6 IIRR has Dayzee's guide which is what I used to root mine, but IIRR she tells you how to unroot again
If you did a Nandroid backup first you could just restore from that?
@ak1ra1nblack: I dont found..
@badgaz: I haven't a backup...
I need the original su file and the original rights for
adb shell chmod 4755 /system/bin/su
Thanks!
Ok, Close please ~~
tur0kx said:
Ok, Close please ~~
Click to expand...
Click to collapse
did you manage to unroot it! IF so share with us the complete steps and link to original su file!
If someone can provide us with an original SU file or a changed back one (Maybe enlightener can help?) then I'll add it in the guide - I don't have it in there yet, though there is code to remove superuser.apk and repush it if it goes wrong which might be what the other poster was thinking about. I do think rooting state can be reversed if you did this method, so lets see if we can get an unrooted SU (or do we just have to remove su file altogether to be virgin again?)
Hugs to all - Dayzee
I just checked.
I restored my nandroid backup.
I booted the cm-recovery mounted /system.
and now in /system/bin there is no su.
I expected this already.
To unroot removing su and SuperUser.apk should be enough.
BR
phlo
Ok is there somebody that could please clarify on the specific steps to unroot the phone?
I don't like to guess at all with these kind of things for obvious reasons
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
tur0kx said:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
That is nice, should be in the wiki.
How about unrooting by flashing back backed up .img files? Witch file to restore? How?
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
/data/local/tmp/root
Click to expand...
Click to collapse
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
sammd301 said:
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Click to expand...
Click to collapse
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
raitchison said:
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
Click to expand...
Click to collapse
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
gbarayah said:
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
Click to expand...
Click to collapse
right now...neither method works not the "visionary r14 or ADB/RAGE/GFREE" I wouldn't mind using either method, the problem is that ADB/Rage/GFREE METHOD keep giving this error message "mkdir failed for /system/xbin, File exists" which I have done a ton of research and still can find a fixed,
sammd301 said:
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
Click to expand...
Click to collapse
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
ON YOUR PHONE:
1. Launch Terminal Emulator
2. Execute /data/local/tmp/rage
3. Wait for the message: "Forked #### childs."
4. Menu > Reset Term - Terminal Emulator will exit.
5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Click to expand...
Click to collapse
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Right now I going to try to use this command to fix the error and if it doesn't work, I will then try to flash a custom and see how that goes...Update will be posted as I go along....thanks for the kind help....
raitchison said:
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Click to expand...
Click to collapse
I will attempt to flash ClockWorkmod, once I try out "ianmcquinn" suggesting in trying to fix the rooting error...thanks for the help
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Yes I used the wiki instruction to gain temporary root on the phone and proceeded to tryout the above command...I got mostly error with the command below is what I en-counted as I enter the command....
# /data/local/tmp/busybox killall rage
No error here just # prompt
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
No error again just # prompt
# rm -rf /system/xbin
Error "rm failed for -rf, Read-only file system"
# mkdir /system/xbin
Error "mkdir failed for /system/xbin, File exists"
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
Error "cp: can't stat '/system/xbin/busybox': Not a directory"
# chmod 4755 /system/xbin/busybox
Error "Unable to chmod /system/xbin/busybox: Not a directory"
# /system/xbin/busybox --install -s /system/bin
Error "/system/xbin/busybox: not found"
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
Error "cp: not found"
# cp /sdcard/su /system/bin/su
Error "cp: not found"
# chmod 4755 /system/bin/su
Error "Unable to chmod /system/bin/su: No such file or directory
I am now going to attempt the Clockwork custom rom flash..
Folks victory is mine....No, VICTORY IS OURS, I sincerely like to thank all of you all, who replied with helpful suggesting...especially the following members "raitchison" from West Hill, CA and "ianmcquinn" a true senior member of xda-developer.
This is what I did to finally get the phone rooted....
I took "Raitchison" advice by trying to use flash_image to flash ClockWorkMod recovery... but during the process I could not get pass copying file to the phone root system folder usind android terminal emulator ...so I input this command "chmod 777/system" to gain write access to the folder...after doing that I manually moved busybox file to system folder and attempted a rooting the phone using the rooting instruction from the HTC G2/DESIRE Z wiki site...at...
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
And this time around, everything went as normal after rooting the phone I open root required app and Wa La...no error message...
Guys I once again wants thank you all for the support....I also looked forward to help out others facing the same issue...so if anyone has encounter the same or similar issue please feel free to post here and I will response....
Can any one help me I am trying to close this thread...How do I go about doing it....thanks
There is no need to close the thread, if anyone has a similar problem and finds it via search they can come in here and bring the discussion back up, otherwise if there is no activity it will naturally fall to the bottom of the thread list.
It works for me I just did it yday using visionary and gfree all on my phone weird that it doesn't work for you?
Sent from my Liquid Metal using XDA Premium App
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
You can root using this toolkit http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Mojochief said:
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
Click to expand...
Click to collapse
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
EDIT: All that file does, is copy su and Superuser.apk to your device and set the appropriate permissions.
You can root using this toolkit http://forum.xda-developers.com/show....php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Thanks I'll try it, but I'm actually not a big fan of one click thingies where you don't know what you're doing.
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
Click to expand...
Click to collapse
Thank you I really prefer that over toolkits!
Mojochief said:
Thank you I really prefer that over toolkits!
Click to expand...
Click to collapse
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
Click to expand...
Click to collapse
Just tried it and it worked just fine
And thank you for the explanation!
So actually you could do it w/out booting cwm just with fastboot+adb right?
Mojochief said:
[snip]
So actually you could do it w/out booting cwm just with fastboot+adb right?
Click to expand...
Click to collapse
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
Click to expand...
Click to collapse
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Mojochief said:
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Click to expand...
Click to collapse
Yes, you can use another insecure boot image, but it needs to be a 4.0.4 compatible kernel. Older ones won't work.
Sent from my Galaxy Nexus using Tapatalk
I'm a stock kind of guy. If I want to change things like launchers or whatever I can do it myself once I get root. Plus I like quickoffice and a lot of ROMs like to remove it. Here's what I did.
You can download the stock firmware from samfirmware.com. Flash using Odin. Do this if you want to return to stock 2.3.5. If you are an AT&T customer, you can get the 2.3.6 OTA at this point. I'm still working on pulling the OTA for non AT&T customers.
If you can't get the OTA because you have a custom recovery flashed, see the bottom of this post for the stock recovery. Unrar it and flash using the PDA mode in Odin.
Once you're on 2.3.6, flash CWM from this thread http://forum.xda-developers.com/showthread.php?t=1458153
At this point, there is no need whatsoever to find an exploit in the system in order to try to "root" this phone. CWM provides root access using adb.
Boot into CWM by holding the down volume and the power button. At this point your phone already has root. The only things missing are to push the su and busybox binaries and the superuser.apk. Go into mounts and storage and mount /system
Since I'm lazy, I downloaded DooMLoRD's rooting script here http://forum.xda-developers.com/showthread.php?t=1321582. Note the script does not work on our phone and we don't need the zerg exploit. All we need are the binaries and a way to push them to our phone. DooMLoRD also handily includes an adb shell
In the same folder as runme.bat, make runme2.bat in notepad and paste in the following:
Code:
@echo --- creating temporary directory
@files\adb shell "cd /data/local && mkdir tmp"
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/ && rm *"
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@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 "cd /data/local/tmp/; rm *"
@echo ALL DONE!!!
@pause
One more final note, after you reboot, update the superuser apk from Google Play. Reboot again before trying to update su or it will fail. Update busybox with the stericson app if you want but it's not necessary.
This method will work on stock 2.3.5 as well. To unroot, just open an adb shell and delete busybox, su, and superuser.apk
Hi Nardholio,
One quick clarifying question: if I flash back to stock 2.3.5 using Kies, will all my apps and personal data get wiped?
Thanks!
I've only had this phone for 2 days, but it looks like Kies will only flash a version you already have (that's not an upgrade) if you force it to initialize the phone. So yes. Hopefully someone will pull the stock recovery in a flashable package for us eventually. If you really want to do this and save your data in the meantime, flash a rooted 2.3.5 ROM (or if you installed CWM on top of non-rooted stock 2.3.5 you could use this same script to root it), then back up your data with Titanium to a safe place (external SD) before wiping the phone and getting the OTA.
Note, installing CWM doesn't appear to increase your flash counter so if you're currently on stock 2.3.5 and for some reason can't OTA to 2.3.6 AND you want to save your data and you care about your flash counter, rooting your 2.3.5 to save your apps seems to be the way to go.
Nardholio said:
I think you have to be an AT&T customer to get this.
Click to expand...
Click to collapse
So it's not enough to have the AT&T version of the phone, you actually have to have a valid AT&T SIM as well? About phone shows 2.3.5 and my phone is just telling me I'm up to date.
worked like a charm! thanks! this was the one thing that annoyed me, having to downgrade to be able to have root. i prefer to have 2.3.6 mainly because of the ability to have video chat on google talk.
Ahhhh, I wish I'd seen this thread before I flashed a custom kernal. Now I'm running ardatdat on the stock rom.
roothorick said:
So it's not enough to have the AT&T version of the phone, you actually have to have a valid AT&T SIM as well? About phone shows 2.3.5 and my phone is just telling me I'm up to date.
Click to expand...
Click to collapse
I have the same problem. Hoping someone will post a stock or rooted 2.3.6 ROM, or ICS will come out soon.
oldnoob said:
I have the same problem. Hoping someone will post a stock or rooted 2.3.6 ROM, or ICS will come out soon.
Click to expand...
Click to collapse
is there a way to create a flashable rom from a nandroid backup? or can someone flash another persons nandroid backup? i can go back to untouched stock and do a backup and post it if it could be used...
I'm sure there's a way to do it, I just don't know how. At this point it might be better to just wait for ICS to drop.
Wat does it matter having a certain build number? As long as everything works fine who cares
Sent from my SAMSUNG-SGH-I927 using XDA
http://db.tt/LbIu6LTv
Try this one, it's called megatron root. It's the only root that worked on lg thrill on gingerbread maybe it will work here.
Sent from my HTC One X using xda premium
deleted post
Will flashing CWMR prohibit the OTA ICS Update?
Nardholio said:
I'm a stock kind of guy. If I want to change things like launchers or whatever I can do it myself once I get root. Plus I like quickoffice and a lot of ROMs like to remove it. Here's what I did.
You can download the stock firmware from samfirmware.com. Flash using Odin. Do this if you want to return to stock 2.3.5. If you are an AT&T customer, you can get the 2.3.6 OTA at this point. I'm still working on pulling the OTA for non AT&T customers.
If you can't get the OTA because you have a custom recovery flashed, see the bottom of this post for the stock recovery. Unrar it and flash using the PDA mode in Odin.
Once you're on 2.3.6, flash CWM from this thread http://forum.xda-developers.com/showthread.php?t=1458153
At this point, there is no need whatsoever to find an exploit in the system in order to try to "root" this phone. CWM provides root access using adb.
Boot into CWM by holding the down volume and the power button. At this point your phone already has root. The only things missing are to push the su and busybox binaries and the superuser.apk. Go into mounts and storage and mount /system
Since I'm lazy, I downloaded DooMLoRD's rooting script here http://forum.xda-developers.com/showthread.php?t=1321582. Note the script does not work on our phone and we don't need the zerg exploit. All we need are the binaries and a way to push them to our phone. DooMLoRD also handily includes an adb shell
In the same folder as runme.bat, make runme2.bat in notepad and paste in the following:
Code:
@echo --- creating temporary directory
@files\adb shell "cd /data/local && mkdir tmp"
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/ && rm *"
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@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 "cd /data/local/tmp/; rm *"
@echo ALL DONE!!!
@pause
One more final note, after you reboot, update the superuser apk from Google Play. Reboot again before trying to update su or it will fail. Update busybox with the stericson app if you want but it's not necessary.
This method will work on stock 2.3.5 as well. To unroot, just open an adb shell and delete busybox, su, and superuser.apk
Click to expand...
Click to collapse
Thanks for all of your info.
I have gotten myself back to bone stock ATT 2.3.5 using samfirmware and then Kies updater to wipe and reload and then used the OTA updater to get me to 2.3.6. As far as the OTA system says, I am up to date. The problem is I can't use Titanium Backup to get all my apps back if I am not rooted or use this flashable CWMR you linked to. (or any other apps that depend on root.
I have no technical issues with doing this but I am scared that I will have to start over, and go back square one when the ICS drops if i have CWMR on my system. What do you think about this? Should I wait here with stock 2.3.6 and just check the OTA updater every 24 hours or go ahead and flash CWMR?
Thanks,
Mac
macwhite1 said:
Thanks for all of your info.
I have gotten myself back to bone stock ATT 2.3.5 using samfirmware and then Kies updater to wipe and reload and then used the OTA updater to get me to 2.3.6. As far as the OTA system says, I am up to date. The problem is I can't use Titanium Backup to get all my apps back if I am not rooted or use this flashable CWMR you linked to. (or any other apps that depend on root.
I have no technical issues with doing this but I am scared that I will have to start over, and go back square one when the ICS drops if i have CWMR on my system. What do you think about this? Should I wait here with stock 2.3.6 and just check the OTA updater every 24 hours or go ahead and flash CWMR?
Thanks,
Mac
Click to expand...
Click to collapse
You might as well just wait should be any day now. That way you could get the update when it is available.
Sent from my SAMSUNG-SGH-I927R using xda app-developers app
You should be able to flash the stock recovery on top of CWM and you'll be good to go for OTAs, although there isn't much point in *just* flashing CWM if you aren't going to deviate from stock otherwise.
One more thing, I found an even easier root method. If you download the CWM flashable version of superuser from http://androidsu.com/superuser/ and flash CWM, and then flash Superuser, bam, instant root!
Hi I have used odin and CWMR_recovery.tar.md5 flashed ok, but how do I flash superuser apk etc. I have the file runme2.bat ?? but how do I use it ?
This bit for me is unclear, can anyone assist and make this bit a little clearer for "simple is as simple does."
Thanks
pgunning1 said:
Hi I have used odin and CWMR_recovery.tar.md5 flashed ok, but how do I flash superuser apk etc. I have the file runme2.bat ?? but how do I use it ?
This bit for me is unclear, can anyone assist and make this bit a little clearer for "simple is as simple does."
Thanks
Click to expand...
Click to collapse
You dont flash an apk file you only flash zip files. if you go into the ROM zip/system/app just drop the superuser apk into there and then flash that rom. When you boot up the apk file you put in the ROM will turn into an app on your phones app drawer. Or you could just install superuser in market.:fingers-crossed:
Thanks for the quick reply, Ive just installed superuser and busybox and supersu ? superuser installed as did the other two, superuser opens but busybox says it cannot install as root is not complete/accessible. the flash of cmw by odin went ok and have rebooted no probs, I have not change operating system just trying to root 2.3.6 gingerbread ! any help appreciated so close yet so far LOL
ATB
pgunning1 said:
Thanks for the quick reply, Ive just installed superuser and busybox and supersu ? superuser installed as did the other two, superuser opens but busybox says it cannot install as root is not complete/accessible. the flash of cmw by odin went ok and have rebooted no probs, I have not change operating system just trying to root 2.3.6 gingerbread ! any help appreciated so close yet so far LOL
ATB
Click to expand...
Click to collapse
just by installing superuser doesnt root your phone, you have to flash the zip file to root your phone.
With Android 4.2.x I was able to install SuperSU binary right after flashing the factory image using fastboot, without flashing any custom recovery. I simply boot CWM recovery:
Code:
fastboot boot recovery-clockwork-6.0.3.5-maguro.img
... mounting /system and pushing the su executable with the right permissions:
Code:
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
With Andoird 4.3, after installing the su executable (taken from the .zip file, latest version) SuperSU Pro complains about no SU binary installed :crying:
How can I fix this? Thank you.
Just flash the zip and be happy. Remind you'll need the version 1.45 minimun
Sent from my Galaxy Nexus using xda app-developers app
"no SU binary installed" means mobile is not rooted,try to root your device with latest version of SuperSu with TWRP Recovery,you can find alot of tutorials if you search