Just wanted to share that I lost root with installing this OTA update. I used the Photon Torpedo method and still have the scripts, I can get root on console but unless I'm already root if i run "su" I get permission denied. The permission denied is in the log for superuser however the prompt doesn't show up.
I probably won't have time to dig into this further until the weekend but wanted to have a thread for others who are wondering..
stever5 said:
Just wanted to share that I lost root with installing this OTA update. I used the Photon Torpedo method and still have the scripts, I can get root on console but unless I'm already root if i run "su" I get permission denied. The permission denied is in the log for superuser however the prompt doesn't show up.
I probably won't have time to dig into this further until the weekend but wanted to have a thread for others who are wondering..
Click to expand...
Click to collapse
You are suppose to lose root when you apply an official OTA root. Just re-root it using the Photon Torpedo method. I am confused where you are lost at.
ericdabbs said:
You are suppose to lose root when you apply an official OTA root. Just re-root it using the Photon Torpedo method. I am confused where you are lost at.
Click to expand...
Click to collapse
$ /system/bin/su
Permission denied
$ su
Permission denied
rerun (I don't have ADB to copy/paste on this computer):
$ cd /data/tmp
$ ./photon-torpedo.sh
.... the usual... end result..
[email protected]:/data/tmp# ./install-su.sh
[email protected]:/data/tmp#
Note: no errors, also did this manually to make sure..
exit / rerun terminal (or anything else requiring root)
$ su
Permission denied
Those steps worked on previous updates however don't work with this update. Not having ADB I'm unable to type a lot of commands easily to diagnose further..
I used the one click root and have no issues at this point. SU running ok
- Installed Update
- Ran Torpedo like before
- Root Access
Case Closed
Update superuser
Sent from my MB855 using XDA App
$ cd /data/tmp
$ ./photon-torpedo.sh
[email protected]:/data/tmp# /system/bin/mount -o remount,rw /system
[email protected]:/data/tmp# chmod 4775 /system/bin/su
Do this if updating superuser fails
what's new in this version? work with the unlocked bootloader
I know with the previous OTA update, we had to flash back to stock, or some people were having issues with it. Is that the case with this one as well? I have a feeling I answered my own question, but I am not sure I am correct on the above information. So if anyone has any info, I'd really appreciate it. Thanks.
Related
Okay, so I've noticed that this rooting method is a little unconventional. It works through a compromised Fota.pkg which has setuid on /system/bin/sh as root. This is not a very safe, as any application that runs sh will gain root access to your system. Scary... :S Anyway, in order to fix this we need to take a few steps.
It is important that you do these in order, otherwise you may lose root access
Install a proper SU with whitelist
1. Download http://bit.ly/aWgALL
2. Unzip the system folder.
3.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push system/bin/su /sdcard/su
adb push system/app/Superuser.apk /sdcard/Superuser.apk
adb shell dd if=/sdcard/su of=/system/bin/su
adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
adb shell chmod 6777 /system/bin/su
adb shell chmod 644 /system/app/Superuser.apk
4. Reboot your phone.
Fix sh to not setuid to root
1.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell chmod 0755 /system/bin/sh
Properly install busybox
1. Here, it's easier to look for the busybox installer app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
chai_archer said:
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
Click to expand...
Click to collapse
If you followed the root guide you can put it in the step 4 folder.
Then hit windows key + r and in the box type CMD
A console window comes up.
in the console window type cd <path.to.your.step.4.folder>
then go from there.
zephyrix said:
Properly install busybox
1. Here, it's easier to look for the busybox app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
Click to expand...
Click to collapse
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
bcool15 said:
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
Click to expand...
Click to collapse
yep.
if you check the superuser app it should already be there.
zephyrix said:
yep.
if you check the superuser app it should already be there.
Click to expand...
Click to collapse
all i see in superuser app is titanium backup pro
that's strange. does busybox report that it's installed?
zephyrix said:
that's strange. does busybox report that it's installed?
Click to expand...
Click to collapse
nope it doesnt
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
unknown13x said:
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
Click to expand...
Click to collapse
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
bcool15 said:
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
Click to expand...
Click to collapse
use "su" to get root access... allow when the Superuser Whitelist notification pops up.
it worked for me....followed the steps, after i downloaded the busybox app i opened it and a box popped up "Superuser Request", it had discription of the busybox app and then asked whether to allow or deny the request....i then checked the superuser app and was able to see the busybox app in thr....
can anyone confirm if these steps were added in the new root method? please
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
root in adb
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
th4r said:
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
Click to expand...
Click to collapse
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Here are the answers....
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
No they were not. The reason is that many of the rooting steps rely on a setuid "sh"
gfgodoy said:
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
Click to expand...
Click to collapse
Yes
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
So what? The uid for the shell application launched after invoking "adb shell" is not going to match any of the installed applications anyways. The thing is that Superuser.apk installs a mechanism by which the user (human) can detect when an application is requesting root access. Based upon the nature of the application you may or may not want to grant root access. That is the whole point.
th4r said:
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
Click to expand...
Click to collapse
Oh yeah? I just use "su" whenever I want root access... and I didnt have to write any scripts to enable/disable it.
k1ckn1ck said:
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Click to expand...
Click to collapse
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
j4mm3r said:
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
Click to expand...
Click to collapse
easy now, it's a fair question, would be nice to be able to run cleaning scripts on a protected system. no need to be a prick
in answer to the question though, once the batch starts adb shell, it won't continue till that process ends
I did some googling for some comandline tools that might allow sending keystrokes to a process, but nothing easy appeared, looks like your only option is to use a linux friendly notepad to create some shell scripts you can execute from the sdcard. i.e. on device
su
chmod 755 /sdcard/myscript.sh
./sdcard/myscript.sh
easiest way to do scripts on a secured root IMO
Check this thread for updated and improved information, many thanks to j4mm3r
http://forum.xda-developers.com/showthread.php?t=953110
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2
Extract the above files using your favourite program
Using adb, install all three files to /data/local:
adb push su /data/local
adb push Superuser.apk /data/local
adb push busybox /data/local
Use adb remount to open the /system directory
adb remount
Use adb shell to move files
adb shell
cd /data/local
cat Superuser.apk > /system/app/Superuser.apk
cat su > /system/bin/su
cat busybox /system/xbin/busybox
Symlink su and set permissions:
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
Typing su should now work
su
su: access granted, courtesy of www.magicdroidapps.com
Install busybox
exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,
su
busybox --install -s /system/xbin
That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.
Good Luck
really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
anbradle said:
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
Click to expand...
Click to collapse
Check your steps, especially permissions and the symlink. Works consistently on reboot for me.
Homer_S_xda said:
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
Click to expand...
Click to collapse
I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin
chhaggerty said:
It wouldn't work for me without installing in /system/bin and using a symlink to /system/xbin
Click to expand...
Click to collapse
It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...
[email protected]:/system/bin # echo $PATH
echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
[email protected]:/system/bin # ls -l su
ls -l su
su: No such file or directory
[email protected]:/system/bin # ls -l /system/xbin/su*
ls -l /system/xbin/su*
-rwSr-sr-t root root 76232 2011-02-04 09:08 su
-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic
-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new
-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org
chhaggerty said:
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2.
Good Luck[/B]
Click to expand...
Click to collapse
i might take credit for gaining root, but the rest is all you
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
nswenson said:
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
Click to expand...
Click to collapse
Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
You were right I tried again and now I am rooted after reboot. Thanks
jleecong said:
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
Click to expand...
Click to collapse
Okay...
I am running HC (v2) off a 8gb sd card.
So do I just do these steps to gain root or do I need to partition the sd card first?
Thanks
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
agreed, i was just going for root myslef
j4mm3r said:
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
In
http://howto.ccroms.net/android_project/build/mod/root
I would have though that the purpose of the changes, specifically;
LOCAL_FORCE_STATIC_EXECUTABLE := true
LOCAL_STATIC_LIBRARIES := libc
Were what should resolve the _mktemp not found?
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Mikey1022 said:
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Click to expand...
Click to collapse
yes, at the stands, its just root access. granted i had my own reasons for this
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked for me
Does anyone know if the built in "OTA Root keeper" in SuperSU works too?
Sent from my Galaxy Nexus using Tapatalk 2
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked fine for me. FYI if you are using EZOverclock.apk freeze or remove it.
Scumbag Inc. said:
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Click to expand...
Click to collapse
Currently (to the best of my knowledge), the only way they could have root on the TF300 with JB was to restore root using both SuperSU and OTA Rootkeeper. There haven't been any new exploits as far as I know.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
Rootkeeper did not work for me. The only apps I was using that required root were Titanium Backup and Samba Fileshare, plus obviously Super User and Busy Box. Anyway I can't use them now, with no root after updating to 4.1.1 despite Rootkeeper.
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Rooted, stock, locked bootloader.
My Transformer Prime just finished the update successfully!
Took several minutes to do whatever it does.
Lost root when updated, but Voodoo OTA RootKeeper restored root.
Nice to have JB on my Prime and Nexus 7.
Darkseider said:
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Click to expand...
Click to collapse
I checked and I have no /system/su_backup file, despite OTA RootKeeper telling me it was there before I installed the JB OTA. I wonder if my doing a cold boot before installing the OTA somehow erased the su_backup? I wish I had copied it somewhere else.
So I Do Have Su Backup File in sys but it doesnt work any thoughts? root keeper says it works but doesnt acually work
Updateing now.
I just erased and recreated my su backup with Voodo's OTA Rootkeeper.
back in a minute.
-------------
EDIT:
no dice.
installs .
restores the su binary at /system/bin/su
but it does not work.
-------------
Update got root access though adb using the backup su binary at /system/usr/we-need-root/su-backup
i just used the full path at the commad line...
copied the binary to /system/bin/su
more later.
-------------
Update:
got root working using
Root MANY ANDROID! [Upd: 20.09.2012]
I use linux so i just followed the steps in the batch file ( following the GOTO jumps for normal install) .
Problems:
this is the script i followed. it is in the zip at the link.
These are the command i used from the file. on linux i just replaced the stuff\adb.exe part with adb at the command line.
The files would not push to /data/local/tmp directly so i pushed the files to /sdcard/tmp then used adb shell and su'ed to cp (mv gave errors) them to /data/local/tmp
Code:
:START
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /data/local/tmp/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /data/local/tmp/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /data/local/tmp/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /data/local/tmp/busybox
When i launched the backup app from adb it did not appear to ever stop. so i closed it after about 5 minutes and rebooted then continued.
Code:
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device!
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
The busybox binary did not work so i just used regular commands at adb shell prompt. Some of the commands required me to su first.
Code:
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
I had no issues. restored root perfectly
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Edit: I did not temp unroot b4 update. Maybe my problem?
Sent from my DROID RAZR using xda app-developers app
Shinare said:
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Click to expand...
Click to collapse
If i remember correctly from one of the previous updates, updating using a file is what caused voodoo to not be able to restore the root.
I had to wait until they found a new exploit to get it back.
x-web said:
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Click to expand...
Click to collapse
I appreciate you pointing this out but here's the problem I'm running into. "mount: permission denied"
I can't su because I don't have root.
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Something strange is going on here, i restored root with OTA root keeper, everything worked well and when i check status it states that my device is rooted and root permission granted.
Titanium Backup works perfectly as well, but other apps like Gesture Control are unable to get root access and when i run a root checker app it says that I dont have proper root access. Is there a way to fix this? Or is my root lost? I still have some hope as it works fine with TB
Stuff i'm still able to do:
-Temp unroot/reroot with OTA root keeper
-delete SU backup and make a new one
-Use Titanium Backup
-Use any root explorer i've tested so far, i can also access /data folder!
-Use Terminal emulator
-Also the file system/bin/SU is present.
What i cant do:
-app: gesture control
-update my SU binary with superuser app
-update my busybox using BusyBox free from play store
there must be a way!
Damn pissing on my sunny day. I want to see JB but am afraid of what problems it will cause. Thanks to all that posted saying OTA worked I hope it works for me too.
iamhcg said:
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Click to expand...
Click to collapse
I did the same and can confirm that I successfully restored root.
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
franky_402 said:
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
This procedure worked for my TF201 with partial root after updating to 4.1.1. The only issue was step 11, the forced update of Superuser's su binary. The message was “Making sure new su works..." but the result after several minutes was still "Waiting....". Should I rerun the forced su update? Despite this Vodoo OTA Rootkeeper did restore root without problem and Root Checker says thumbs up.
At this point, is there anything to do like switching to SuperSU that would make the root more future-proof?
Thank You! I have been trying to regain root after jellybean ota on my Motorola Atrix HD for the last week and a half. Finally success . I cant thank you enough!
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
You should be able to switch to a different root app. Never used this method but I have switched from superuser to supersu. Install superuser and run the binary update. Should tell you your binary is out of date with the name of the binary for the other root app. Update and reboot, then go back to superuser and check the binary update again. If it says it's up to date, uninstall the old root app and move superuser to /system/app. Reboot and you're good to go!
Sent from my Atrix HD MAXX
i think i tried that. istalling and uninstalling and subdstituting su and supersu. was not updating no matter what. also my adb push was not working so i copy pasted the su with my laptop while in adb shell. also updated su binary while in shell. it was already a system app from my previous attempts. anyway im good now
any one get it to work with no root/first time root? my prime wouldnt update via ota once on ics so i had to use the sd card update method to update. and from then on i never rooted again i then updated to jb and until 2 days ago i wanted to reroot but noticed there was no root method for jb yet. voodo root keeper just has super user app installed and ./system supports root protection both checked.
I'm in the same situation as fcortes626, I had to upgrade via sdcard method, and voodoo root keeper didn't maintain the root. I can't find any su backup in my filesystem.
I wonder if we can downgrade using the sd card update then root and go on from there........?
Sent from my SGH-T999 using xda app-developers app
I'm new here but have been messing around with android for awhile. I spent all afternoon searching for an answer but haven't been able to find anything. I had rooted my prime but not unlocked it while it was on ics, I used ota rootkeeper to keep root when I upgraded to jb but i think when asus sent out another update i forgot to save root. I still have su in /system/bin and superuser installed but it won't prompt me to give any programs root access. I typed in su in a terminal emulator and it said permission denied. so my question is, how do I get root back without unlocking?
Does this thread help ? http://forum.xda-developers.com/showthread.php?t=1911261&highlight=partial+root
I was able to get root back back doing something similar. Somehow the permissions got messed up for su. I went into adb and got root permission through CD/ system then ./usr/we-need-root/su-backup; su. Then I pushed new su, busybox, and superuser.apk files and fixed the permissions and changed the owner of su using chown and chmod.
peterk-1 said:
Does this thread help ? http://forum.xda-developers.com/showthread.php?t=1911261&highlight=partial+root
Click to expand...
Click to collapse