Related
Hello all,
So, I recently rooted my Epic 4G using the following thread as a guide: http://forum.xda-developers.com/showthread.php?t=770388
The root worked great, but ClockwordMod isn't quite working as planned.
If I boot the phone holding Power+VolDown+Camera it boots into ClockwordMod, but if I use ROM Manager to try and reboot into ClockworkMod and backup my current ROM, it just takes me to the stock Android recovery screen.
Any ideas as to why this is happening?
Help would be greatly appreciated!
Also, when I download ClockworkMod through ROM Manager, it creates an update.zip on the root of my SD Card, but when I try flashing it, it won't go through.
Also tried manually entering Clockwork and flashing it there, and it went through, but ROM Manager still doesn't work.
You need the recovery redirector. The easiest way to get it is to run the one-click root and recovery or install a rom with the redirector in it.
The other way is to download the one-click zip and unzip it on your sdcard. Copy the files below from the one-click to the same place on your phone.
/system/bin/recovery
/system/bin/recoveryfiles/
/system/bin/recoveryres/
Then type the following commands into a terminal program.
busybox chmod -R 0755 /system/bin/recoveryfiles/*
busybox chmod -R 0755 /system/bin/recoveryres/*
chmod 0755 /system/bin/recovery
sync
DiGi760 said:
You need the recovery redirector. The easiest way to get it is to run the one-click root and recovery or install a rom with the redirector in it.
The other way is to download the one-click zip and unzip it on your sdcard. Copy the files below from the one-click to the same place on your phone.
/system/bin/recovery
/system/bin/recoveryfiles/
/system/bin/recoveryres/
Then type the following commands into a terminal program.
busybox chmod -R 0755 /system/bin/recoveryfiles/*
busybox chmod -R 0755 /system/bin/recoveryres/*
chmod 0755 /system/bin/recovery
sync
Click to expand...
Click to collapse
Followed the second part of what you suggested (manually copying the files, since the one-click script didn't work when I first rooted), and it still boots into the Android recovery.
After rebooting I verified the files were still in /system/bin and they were.
Although, looking at that script, it first checks that the OS version is Froyo.
Is the fact that I'm still on stock (rooted) Eclair the problem?
which one click root program yall talking about ... im stuck here to
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.
I'm learning how to manually root my Galaxy Nexus. As far as I know I only need to issue these commands:
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
My question is fairly simple: is http://androidsu.com/ the official home of SuperUser app and where the su executable come from? I've noticed that it's included in the .zip package, but I'm just curious about who made the su command and where I can download the most updated version of it.
EDIT: For example, the /system/bin/su executable from SuperUser has an has of DE0F874A357C3FB1CD8372C99FA19FFAEF16FBD4, while the one in /system/xbin included in the SuperSU zip is 22824F80E2301AA3C7FD82252125AEC3AE249E5D. So why the differs?
Superuser & SuperSU are made by 2 different developers, hence the difference. androidsu.com is the home of ChansDD's Superuser . Chainfires's SuperSu can be found right here on XDA
Actually, permissions for the apk is 0644.
Sent from my i9250
I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 2.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2014-06-29 14:30 su -> /system/xbin/su
Analysis: File: su is a symbolic link pointing to another file: /system/xbin/su
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 348160 2014-06-29 14:30 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-T989 device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn
Wrong forum, US variants have their own fora. Your thread belongs here, I've asked mods to move it. Sit tight until they do.
Karetus said:
I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Click to expand...
Click to collapse
You need to download the su zip and flash it in recovery.
Lokke9191 said:
You need to download the su zip and flash it in recovery.
Click to expand...
Click to collapse
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
KJ said:
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
Click to expand...
Click to collapse
Would you happen to have a link available? Or will any version do the trick?
Karetus said:
Would you happen to have a link available? Or will any version do the trick?
Click to expand...
Click to collapse
You should not use any version. Use the one I attached.