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
Related
Hi, I rooted my Vribrant, both ways (manually and with one click root). I installed terminal emulator. I tried the su command to check if I am root. The # appears normally. However I tried deleting a file with Root explorer, inside the system folder, and when I get back it's still there. I also tried deleting it manually from Terminal EMulator with these commands:
su
cd system/apps
rm Swype.apk
and I get this:
rm failed for Swype.apk, Read-only file system
I also tried:
su rm Swype.apk
and this is returned:
Permission denied.....
I also tried the exact same thing from adb shell (which I had to allow in superuser permissions program), but it gave me the exact same results. What's wrong? Am I doing something wrong? Thanks
In root explorer, try hitting the r/w button at the top and see if that works.
Sent from my SGH-T959 using XDA App
I know about the button. The strange thing is that inside system folder it grands me r/w permissions, and no matter how many times a press the r/o button it doesn't change. Still gives the results I said. However, besides root Explorer what's wrong with terminal emulator and adb?
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
rbirg said:
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes both methods installed the "Superuser Permission" app.
I7oobie said:
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
It does normally.
linuxmotion said:
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
Click to expand...
Click to collapse
I tried the first method but it didn't work. When I entered adb root, it said "adbd cannot run as root in production builds". I searched a bit and found that I must have a rooted kernel for this to work. (I guess it's different from the root method I tried in "how to root vibrant").
Anyway the second way worked, where i replaced mntblock3 with stl9 for my phone. I tried the rm command and it worked! However as soon as I exited terminal, I couldn't delete other files. I had to retype the command. I can't do this everytime I need access in System folder. Why is this happenning? Does this have something to do with the fact that root explorer cannot change r/w to r/o mode while in system folder?
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Moved to Q&A, please post in the correct section.
s15274n said:
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Click to expand...
Click to collapse
No it didn't work. I also installed the latest version of SuperUser 2.3.6.1. But without a difference unfortunately.
What works for me, is installing sgs tools, and whenever I want to do write operations on system folder, run the appropriate script from sgs and then use root explorer......
Although I think there's something wrong? Why doesn't the mount r/w button work in root explorer, and why do I have to remount the file system through SGS tools, every time for it to work?
makes no sense to me either. Have you uninstalled RE and the installed it back granting root once reinstalled?
Yes several times.....
I am giving up. I just have to go through the whole process every time. I found some other people having this issue. I am on stock JI6 firmware. Maybe when I read a little bit more I will flash a custom rom.
Download and install Super Manager. Pretty handy program to use for Root users.
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
msnuser111 said:
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
Click to expand...
Click to collapse
At least I am not the only one with this problem.... haha
I forgot to mention that I use Root Explorer version 2.12.2
When I try a custom Rom I will post the results....
^ why not get the update, .4 is the most recent build. Do you have an illegal copy?
It's not only root explorer. It happens with other file explorers too like android mate and super manager... Inside system folder whatever, I do doesn't happen unless I unmount and remount like before
I finally got my NookColor to sideload apps via ADB. The first thing I did was install Root Explorer and I rebooted the NC.
However, using Root Explorer, I do not have access to the cache or data directories. The response that I get is "Mounted as r/o" and "Your phone doesn't appear to be rooted. ..."
Did I miss something in the process and I'm not really rooted?
Also, I've noticed that the command adb remount gives back an error message as well.
Any thoughts?
Thanks!
See http://forum.xda-developers.com/showthread.php?t=857636
Assuming that you've already install the SuperUser apk
You need to push the su file into /data/local
use the following ADB commands:
Code:
adb push su /data/local/
Then
Code:
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
Use the su file from the attachment in the thread below
http://forum.xda-developers.com/showthread.php?t=665974
Thank you, Sapienta.
I noticed the Superuser comes down as a zip and the instructions say to boot into recovery mode and flash ... does that translate to renaming the zip to apk and installing via adb (as I've done with other apps)? Or do I need to figure out how to do the recovery boot/flash?
Ya sorry about that. I should've been more clear. Ignore everything from that page just download the attachment. You need to push the "su" file into /data/local and then chmod it to 6755 per the instructions from the first link I post and you're good to go.
EDIT NVM, I got it
Well, actually, you were quite clear the first time, I had just forgotten about the first link. But now, when I try to install the file (after renaming the zip to apk) via ADB I get an error message that says file does not contain AndroidManifest.xml. But I know the file is there ... I can see it when I view it with 7Zip. So, I guess I'm being dense today, but what am I missing?
indeana said:
Well, actually, you were quite clear the first time, I had just forgotten about the first link. But now, when I try to install the file (after renaming the zip to apk) via ADB I get an error message that says file does not contain AndroidManifest.xml. But I know the file is there ... I can see it when I view it with 7Zip. So, I guess I'm being dense today, but what am I missing?
Click to expand...
Click to collapse
Inside of the zip file there should be two files, a file called "su" without an extension and the Superuser.apk.
You'll want to push the su (the file is actually a raw binary) to your NC using the steps provided. You'll also want to install the Superuser.apk after pushing the su binary.
Thank you, antoniouslj. Yesterday I installed SU first and then pushed su but Root Explorer kept erroring out. So just to be sure I'm clear, the steps would be done in this order:
1. Push su -->
adb push su /data/local/
2. Change permissions -->
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
3. Install Superuser
Then do I adb Root Explorer or should Root Explorer be installed before I do the steps above?
indeana said:
Thank you, antoniouslj. Yesterday I installed SU first and then pushed su but Root Explorer kept erroring out. So just to be sure I'm clear, the steps would be done in this order:
1. Push su -->
adb push su /data/local/
2. Change permissions -->
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
3. Install Superuser
Then do I adb Root Explorer or should Root Explorer be installed before I do the steps above?
Click to expand...
Click to collapse
That's exactly what I did and it worked great for me. I also had Root Explorer installed prior to installing SU.
Still Struggling!
So ... I still can't get this to work. Do I need to install an alternative launcher (like ADW) first and then do this process?
indeana said:
So ... I still can't get this to work. Do I need to install an alternative launcher (like ADW) first and then do this process?
Click to expand...
Click to collapse
No... what part of the process are you getting stuck on?
I do the three steps like we talked about earlier (and exactly in that order--except I exit out of the shell before I issue the adb install superuser.apk command) and I reboot the Nook. Turn the Nook back on and open Root Explorer, but then RE tells me that there are issues with Superuser and to close RE and restart the RE app. So I do. But it repeats the same process. (I've removed everything so I don't remember the exact language. When I open SU there is no way for me to add an app (that I know of anyway) including looking at the settings. So that's where I'm stuck. And if I can't get root access, then apps like SetCPU and Quickboot won't run successfully.
indeana said:
I do the three steps like we talked about earlier (and exactly in that order--except I exit out of the shell before I issue the adb install superuser.apk command) and I reboot the Nook. Turn the Nook back on and open Root Explorer, but then RE tells me that there are issues with Superuser and to close RE and restart the RE app. So I do. But it repeats the same process. (I've removed everything so I don't remember the exact language. When I open SU there is no way for me to add an app (that I know of anyway) including looking at the settings. So that's where I'm stuck. And if I can't get root access, then apps like SetCPU and Quickboot won't run successfully.
Click to expand...
Click to collapse
Grab another version of RE. I'm finding that version matters when trying to sideload apps.
EUREKA!!!
Thanks to everyone for your help! I finally figured it out. Just as I was about to take the last suggestion of finding and downloading another version of RE, I found and downloaded another version of Superuser (version 4). The new SU version extracts from the zip differently but I was finally able to push and modify per the earlier instructions, installed the new SU version, rebooted, started RE, added it to the SU Whitelist and BAM Root Explorer is working just as I expected it to. SetCPU and Quickboot also seems to be working.
Once again, thank you! You were all GREAT!!!
indeana said:
Thanks to everyone for your help! I finally figured it out. Just as I was about to take the last suggestion of finding and downloading another version of RE, I found and downloaded another version of Superuser (version 4). The new SU version extracts from the zip differently but I was finally able to push and modify per the earlier instructions, installed the new SU version, rebooted, started RE, added it to the SU Whitelist and BAM Root Explorer is working just as I expected it to. SetCPU and Quickboot also seems to be working.
Once again, thank you! You were all GREAT!!!
Click to expand...
Click to collapse
Nevermind...I got mine going, too.
Can someone knowledgeable please submit a detailed post, which instructs how to remove any files added during the Root Process, as well as any other file permission changes or modifications of any other type?
I see many half assed posts in these forums made by unqualified members, which are nothing but a waste of time and clutter this great resource. I would appreciate it if this post could be addressed by those who truly understand this process.
The file that was used to Root the SCH-i905 from Verizon was the one attached to this post.
Thanks in advance! This could be a great learning tool if answered properly.
Can some one please respond? Or is it that everyone is too scared to post helpful information?
Well, since no one was of any assistance, I was forced to piece together information and come to an understanding of how this works, and how to fully reverse what was done by this Root Update.
To begin, I would like to mention, that removing Superuser.apk from the /system/app folder, along with 'su' from the /system/bin folder, will negate your Root Access, and put you back to your default levels of access. This will prevent Mobile Device Management Solutions, such as AirWatch, Zenprise, or MobileIron from detecting your device as being compromised.
I was not successful in removing these two files via the ADB shell, however I was successful when using a Terminal Emulator App on the Device itself.
1.) I began by installing a free Terminal Emulator from the Android Market.
2.) Launched the Terminal Emulator and typed 'su' , then pressed Enter to gain Root Shell Privileges.
3.) From the Root Shell, I typed the following commands to remount the '/System' Directory to gain Read/Write Access.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
4.) I typed the following commands to remove 'Superuser.apk' and 'su'.
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
5.) Type the following command to remount the '/System' Directory back to Read Only.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
6.) Sync your device with Google under Settings / Accounts & Sync.
7.) Reboot your device, and you are good to go.
It might be a good practice to perform a Factory Reset on your device after doing this, however this is not completely necessary. I tested the Air-Watch Agent installation after performing the procedure mentioned above, and the Air-Watch console no longer detected my device as being compromised.
I will add that on my sch-i905 I found the bin directory under system not under system/app. For me, replacing cd /system/app/bin with cd /system/bin did the trick but the rest worked a treat - thanks for the post!
Thanks for pointing out my typo. I corrected the path in my Post.
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
tbcpn said:
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Stock Recovery isn't required to Root the device. However, if you wish to install CWM via ROM Manager from the Android Market, Root Permissions are required.
If you use an ODIN Flash of CWM, there is no need for Root Permissions because you are flashing via ODIN.
The stock recovery zip file that you referenced in the other post should be fine.
Just use ODIN to Flash back to Stock Recovery and use the process that I mentioned to remove Root Permissions and Super User, and you should be all set to return your device after a Factory Wipe.
Cheers!
~Scott~ said:
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Scott,
I'm sorry for just seeing your post. I'm sure that you figured it out by now. You need to gain Root Access to your device again to remove Super User. You are in a Catch22.
If you are using an SCH-I905, Root your device, then download Script Manager from the Android Market.
Run this very simple Bash Script that I wrote to remove Root and Super User.
Paste this into notepad and save it as Unroot.sh then run with Script Manager.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Be sure to run the Script as Root from within Script Manager. The app will kind of freeze up as soon as it runs, which is normal. This will certainly take care of your problem.
Thanks for your post of stockrec in a different post. You saved me a month ago with that one.
Cheers!
Will Samsung know if I rooted my GT 10.1 LTE after using these commands, and sending in for warranty?
Does anyone know how often airwatch checks for the root? anyway to bypass the checks?
Is this the same for the US Cellular 4G Tablet? I have been reading and all that I have found was WiFi only files. Which if I were to root with those I lose the 4G radio.
Perfect.. Just what I need. Thanks
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.
Here's my situation...I had 2 rezounds...One perfectly OK, rooted and Titanium backed up, but my kids poured milk into it...yaay. The 2nd rezound which was my wife's seems to have something physically wrong with it where I can't connect to it with fastboot (but adb works ok when the phone is fully booted), which means I can't dev unlock it, or apply most of the root methods out there...
So I decided to try some other things...
I downloaded the Cydia Impactor...
Drop Su didn't work
but,
start telnetd as root on port 22 did work!
so I then went in and remounted /system as RW
and copied su to /system/bin and the Superuser.apk to /bin/apps.
I then performed a echo ro.kernel.qemu=1 >/data/local.prop.
Now when I reboot, I get the root shell if I adb in to my phone...
But, on the screen only the status bar at the top comes up and if I try to swipe down, I get
"Unfortunately, System UI has stopped".
After this, I went into adb shell and noticed the su was gone from /system/bin...So this time I pushed it to /system/xbin, changed to root owner and chmod'd it to 06755..I removed the local.prop since I think that was causing the problem with the launch screen.
After rebooting, the Rezound had deleteed the su again, but the launcher comes up OK.
So I'm thinking, maybe I need to name the su something else...nope that won't work.
I guess for now I can be happy I can get temp root...
1. Run Cydia Impactor and select start telnetd as root on port 22.
2. copy su to /system/xbin and chmod 06755 /system/xbin/su
3. Run Titanium backup, and allow SU access.
works until phone reboot when su is removed by something.
Any ideas for next steps anyone?
Thanks,
Scott