As I noted here, Superuser may be ok, too, but it still needs confirmation. Also, Voodoo Rootkeeper backups should be refreshed. But this is simply collating a small number of stories, it would be nice if more people confirmed those setups work.
For those with 'partial' root after JB update - regain root!
- Thread starter thenrz
- Start date
-
- Tags
- prime restore root root tf201
As I noted here, Superuser may be ok, too, but it still needs confirmation. Also, Voodoo Rootkeeper backups should be refreshed. But this is simply collating a small number of stories, it would be nice if more people confirmed those setups work.
Superuser itself is just fine. SuperSU's OTA protection is better if you buy the pro version. I have heard Voodoo has made the same updates to ensure better OTA protection, but I am going on what I have seen and know works... I re-made a Voodoo su backup before the JB update (as I always do) temp unrooted, and still was unable to restore root automatically.
I cant regain root because it no longer is recognized by my pc. I have tried to everything and there is no way
I was rooted using ViperMod. I took the JB OTA, thinking rootkeeper would work. Wound up with the partial root issue (some apps worked, i.e. Anti, Network Spoofer, Root Explorer, but root checker and the Linux Installer for Backtrack gave no root errors), so I tried the method in the OP.
I got through step 3. Step 4 gave me a permission denied error, so I used Root Explorer to turn on all permissions for /data/local/tmp. At that point, adb push claimed to have worked through step 6, but I noticed my Prime had frozen. Before I went any further, I decided to hard reboot (hold down power button), to be sure everything was running proper before I started in with shell commands.
Upon reboot, it now sticks at the initial splash screen. I can vol-down & get to the bootloader there, giving me the 4 standard options. Recovery gives me the dead-looking Andy with exclamation mark (I assume because I don't have a backup image, which yes, I know, was stupid not to have. Hindsight.). The OS option says it's starting from a cold boot, but freezes there and does nothing else. I can access fastboot, and at least the reboot command seems to work, but I haven't tried anything else, as I'm not familiar with fastboot, and have no idea where to go from there. I'm hoping against hope I don't have to use the wipe action, as I have a lot of time and data invested in the thing.
I'm also able to vol-up and have APX recognized on my Win7 machine, but I admittedly have no idea what to do with that.
If anyone could help me here, especially if it would include NOT wiping my Prime, I would be forever grateful. Thank you in advance for any advice.
I got through step 3. Step 4 gave me a permission denied error, so I used Root Explorer to turn on all permissions for /data/local/tmp. At that point, adb push claimed to have worked through step 6, but I noticed my Prime had frozen. Before I went any further, I decided to hard reboot (hold down power button), to be sure everything was running proper before I started in with shell commands.
Upon reboot, it now sticks at the initial splash screen. I can vol-down & get to the bootloader there, giving me the 4 standard options. Recovery gives me the dead-looking Andy with exclamation mark (I assume because I don't have a backup image, which yes, I know, was stupid not to have. Hindsight.). The OS option says it's starting from a cold boot, but freezes there and does nothing else. I can access fastboot, and at least the reboot command seems to work, but I haven't tried anything else, as I'm not familiar with fastboot, and have no idea where to go from there. I'm hoping against hope I don't have to use the wipe action, as I have a lot of time and data invested in the thing.
I'm also able to vol-up and have APX recognized on my Win7 machine, but I admittedly have no idea what to do with that.
If anyone could help me here, especially if it would include NOT wiping my Prime, I would be forever grateful. Thank you in advance for any advice.
I cant figure out the scripting to su through su backup to do anything interesting but id...
I do have two batch scripts that will give me the info i need to give you steps back to root (if possible). Will post later in morning.
anyone figured out the root cause yet
this happened to me too, but some apps still get root (ConnectBOT, TiBu) and others don't like busybox and, oddly, SuperUser (I can't update the SU binary automatically).
Anyone figured out a root cause.
this happened to me too, but some apps still get root (ConnectBOT, TiBu) and others don't like busybox and, oddly, SuperUser (I can't update the SU binary automatically).
Anyone figured out a root cause.
I had a working root after JB update, but I lost it after factory reset. I still have /system/bin/su, /system/app/Superuser.apk and /system/xbin/busybox with correct permissions. I don't have a copy or link of busybox in /system/bin, though.
If I try to run su from a terminal directly on the Prime, it says "Permission denied". However, I can run su through adb and have # prompt. The version reported by su is 3.0.3.2.
Before I proceed with OP's method I have a few quesions:
1. I'm a bit worried about versions of files you have provided. They have all different sizes and dates than files on my Prime:
2. Just of curiosity, why do you use
instead of simply
and similarly:
instead of
I only guess that the last command is necessary because I'm running the su shell that needs replacing, is it correct?
If I try to run su from a terminal directly on the Prime, it says "Permission denied". However, I can run su through adb and have # prompt. The version reported by su is 3.0.3.2.
Before I proceed with OP's method I have a few quesions:
1. I'm a bit worried about versions of files you have provided. They have all different sizes and dates than files on my Prime:
- su my: = 22364, 2012/09/28, yours = 380532, 29/02/2008
- busybox: my = 2005736, 2012/03/06, yours = 1085140, 9/08/2012
- Superuser.apk: my = 843503, 6/03/2012, yours = 1468798, 29/02/2008
2. Just of curiosity, why do you use
Code:
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apkinstead of simply
Code:
cp /data/local/tmp/Superuser.apk /system/app/Superuser.apkand similarly:
Code:
busybox rm /system/bin/su
busybox cp /data/local/tmp/su /system/bininstead of
Code:
cp /data/local/tmp/su /system/binI only guess that the last command is necessary because I'm running the su shell that needs replacing, is it correct?
Last edited:
Oh well, wasn't patient enough to wait for an answer and simply copied the OPs su into my /system/bin using busybox. I already had Superuser and busybox, so this was the only thing I did. I have my root back!
I noticed that a normal 'cp' does not preserve permissions, and I couldn't change permissions of the copy. It kept saying "bad mode". Weird behaviour... Busybox kept permissions.
I made a copy of my new su into a different directory under /system. This way I should be able to recover it after each update/factory reset.
I noticed that a normal 'cp' does not preserve permissions, and I couldn't change permissions of the copy. It kept saying "bad mode". Weird behaviour... Busybox kept permissions.
I made a copy of my new su into a different directory under /system. This way I should be able to recover it after each update/factory reset.
Is there no one here who has any suggestions for me? I'm desperate here, folks. I really don't want to lose the data and pictures I have on the thing by doing a wipe. I've already posted my situation in the Prime Q&A thread, with no replies. I'm begging the community here for help. Please, y'all, any help would be more than appreciated.
I installed SuperSU before the jb update and still got partial root in some apps (i could not su in terminal but tb and others kept root).
Then i noticed i could no longer turn on bluetooth :-\ i tried the regain root as the OP and i got full root back.
After securing the su binary i did a factory reset hoping bluetooth would start working but no dice :'( still rooted but same problem..
Anyone else got this after the upgrade and/or got a solution?
Sent from my Transformer Prime TF201
Then i noticed i could no longer turn on bluetooth :-\ i tried the regain root as the OP and i got full root back.
After securing the su binary i did a factory reset hoping bluetooth would start working but no dice :'( still rooted but same problem..
Anyone else got this after the upgrade and/or got a solution?
Sent from my Transformer Prime TF201
Before this solution I have working su command in adb. After I dont have root and su command in adb doesnt work 
I have every file in good directories but it esnt work
Wysyłane z mojego Transformer Prime TF201 za pomocą Tapatalk 2
---------- Post added at 05:33 PM ---------- Previous post was at 04:46 PM ----------
Pls help me. Before it was partial root. Adblock work for me. Su command in adb works. I do everything like instruction from first page said. I have su-backup from ota rootkeeper on my sdcard. Su in /system/bin busybox in /system/bin and /xbin and two peruser.apk in /system/app. Pls sameone help me
Wysyłane z mojego Transformer Prime TF201 za pomocą Tapatalk 2
I have every file in good directories but it esnt work Wysyłane z mojego Transformer Prime TF201 za pomocą Tapatalk 2
---------- Post added at 05:33 PM ---------- Previous post was at 04:46 PM ----------
Pls help me. Before it was partial root. Adblock work for me. Su command in adb works. I do everything like instruction from first page said. I have su-backup from ota rootkeeper on my sdcard. Su in /system/bin busybox in /system/bin and /xbin and two peruser.apk in /system/app. Pls sameone help me
Wysyłane z mojego Transformer Prime TF201 za pomocą Tapatalk 2
Thanks to the OP, this thread should be a sticky...
I had upgraded from ICS rooted to JB when it was fisrt released, JB was then running rooted and I was all happy. My TFP has been running great, but after reading all those posts about a fresh wipe and how fast it was I decided to give it a shot. Mind you it was running fine before the wipe, I just wanted to see if there was any difference. So I backed up everything on titanium and such, Wiped it, and ran the OTA voodoo rootkeeper and I lost root? I was pissed at my self and I need root to use my TFP at work with our ISA proxy.
So I read this post and gave it a shot, 20min later I was again rooted on a freshly wiped JB. Man I am even ahppoer with JB, I thought it was quick before, now it flys!!!
Thanks again OP and a mod should really sticky this, Hint Hint...
I had upgraded from ICS rooted to JB when it was fisrt released, JB was then running rooted and I was all happy. My TFP has been running great, but after reading all those posts about a fresh wipe and how fast it was I decided to give it a shot. Mind you it was running fine before the wipe, I just wanted to see if there was any difference. So I backed up everything on titanium and such, Wiped it, and ran the OTA voodoo rootkeeper and I lost root? I was pissed at my self and I need root to use my TFP at work with our ISA proxy.
So I read this post and gave it a shot, 20min later I was again rooted on a freshly wiped JB. Man I am even ahppoer with JB, I thought it was quick before, now it flys!!!
Thanks again OP and a mod should really sticky this, Hint Hint...
This will only work if you can access a root prompt (#) in adb shell! THIS WAS DONE AFTER DOING A WIPE FROM THE VOLUME DOWN MENU WHEN BOOTING THE PRIME! I do not know if this will work without the wipe, but it very well may. Maybe someone more knowledgeable can chime in here.
It may be possible to restore from a su-backup if you have a su binary still in /system/bin or xbin. Even if you can't access a root prompt (#) by just typing su, read starting at page 6. Places to look for a su-backup include /system/ /system/usr/we-need-root/ and /system/bin/
I have a batch script in the works that will determine if you can re-root and take the appropriate steps to do so if possible.
I had to do a voldown wipe after my update to JB. My prime would reboot after 5-10 seconds into the homescreen after boot. After wiping, I thought for sure my root was screwed until a new exploit was found.
I accessed my device through adb, and realized that I could invoke a root prompt using the su command at the $ prompt. Using ES file explorer, I could see su in /system/bin/ but no su-backup or superuser.apk in /system/app/.
I tried simply installing superuser from the market, but it did not work. The busybox installer would not work, either.
ATTACHED ARE THE EXACT THREE FILES I USED. I do not know if using different version will affect the process!
Here is what worked for me:
1. adb shell
2. su
(# - you should see this now! This will not work without this specific prompt!)
3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
5. adb push C:\(location of attached files)\su /data/local/tmp
6. adb push C:\(location of attached files)\busybox /data/local/tmp
7. Access the adb shell again, and type su
8. chmod 644 /data/local/tmp/superuser.apk
9. chmod 755 /data/local/tmp/busybox
10. chmod 6755 /data/local/tmp/su
11. mount -o remount,rw /system
12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
14a. Chmod 755 /system/bin/busybox
14b. Chmod 755 /system/xbin/busybox
15. Reserved
16. busybox rm /system/bin/su
17. busybox cp /data/local/tmp/su /system/bin
18. type su once again to assure you still have access to the # prompt
18a. Chmod 644 /system/app/superuser.apk
18b. mount -o remount,ro /system
19. type exit, and exit again, returning to the regular windows command prompt.
20. type 'adb reboot' (without quotes)
NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
21. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt!
22. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
23. Get SuperSU from the market. It seems to be the safest method to keep root with JB...
ALSO! Make sure to keep a backup root with voodoo or super su after completing this guide! I have lost root (VERY WELL may have been my own fault... too much poking around) Anyway, better safe than sorry!!!
Thanks to daymz from the debugfs thread in development for the basic instructions of what needed to be done!! And also thanks to all before me who got us root in the first place!
I will answer questions to the best of my ability. I am not a developer and do not try to present myself as so... I can tinker with the best, and after losing root, I set out to see if I could figure it out!
Changes made as per tsmt971
Hi all.
Been reading through the thread and been unable to get root. I think the reason is because, although I had root and an unlocked bootloader on ICS I couldn't get the OTA update to JB. I had to do it manually. When I did I did a full wipe and install. Although I did run Rootkeeper before wiping on installing the JB Stock Rom and loading the RootKeeper app it gave no options to update. I stupidly (with hindsight) thought it would perform the back up in the cloud, clearly it must have done it locally, on my Prime, which I then wiped. Doh!
So, I 've accepted I won't get root on my JB install.
However, the reason I want to root is to install a custom ROM. So, my question is can I do a full wipe and install the ICS Stock ROM, root that and then simply install a JB Custom ROM. Or will this not work??
Many thanks in advance.
Been reading through the thread and been unable to get root. I think the reason is because, although I had root and an unlocked bootloader on ICS I couldn't get the OTA update to JB. I had to do it manually. When I did I did a full wipe and install. Although I did run Rootkeeper before wiping on installing the JB Stock Rom and loading the RootKeeper app it gave no options to update. I stupidly (with hindsight) thought it would perform the back up in the cloud, clearly it must have done it locally, on my Prime, which I then wiped. Doh!
So, I 've accepted I won't get root on my JB install.
However, the reason I want to root is to install a custom ROM. So, my question is can I do a full wipe and install the ICS Stock ROM, root that and then simply install a JB Custom ROM. Or will this not work??
Many thanks in advance.
I'd like to thank everybody on this thread
When I initially upgraded my rooted (but stock) Prime to JB I lost Root, the guide on page 1 got root back.
I have now upgraded to the new JB released this week, I lost root again, and regained it, again using the guide on page 1.
The initial JB upgrade was easier as I just followed the guide changing s for S and C for c where required. I had the # after typing su in an adb shell.
This recent upgrade (update) was a little more long winded, I did not have the # prompt. I did however have a su-backup in the /system/usr/we-need-root/ folder. I got the # prompt and re-rooted.
Thanks guys
When I initially upgraded my rooted (but stock) Prime to JB I lost Root, the guide on page 1 got root back.
I have now upgraded to the new JB released this week, I lost root again, and regained it, again using the guide on page 1.
The initial JB upgrade was easier as I just followed the guide changing s for S and C for c where required. I had the # after typing su in an adb shell.
This recent upgrade (update) was a little more long winded, I did not have the # prompt. I did however have a su-backup in the /system/usr/we-need-root/ folder. I got the # prompt and re-rooted.
Thanks guys
How do you know if you have partial root? Rootkeeper has everything ticked by Adaway kept quitting because it couldn't get SU permission and a Root checker from the market says I don't have root. I take it this method should work for me then?
Thanks.
Thanks.
are you on unlocked bootloader? then you could use urkel's_fresh_start_1.0 choose the fresh root you will loose nothing but gain root. it worked for me. i am on stock jb unlocked bootloader and rooted again in 10 min. and did not loose anythink. only had to install busybox again
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29This will only work if you can access a root prompt (#) in adb shell! THIS WAS DONE AFTER DOING A WIPE FROM THE VOLUME DOWN MENU WHEN BOOTING THE PRIME! I do not know if this will work without the wipe, but it very well may. Maybe someone more knowledgeable can chime in here.
It may be possible to restore from a su-backup if you have a su binary still in /system/bin or xbin. Even if you can't access a root prompt (#) by just typing su, read starting at page 6. Places to look for a su-backup include /system/ /system/usr/we-need-root/ and /system/bin/
I have a batch script in the works that will determine if you can re-root and take the appropriate steps to do so if possible.
I had to do a voldown wipe after my update to JB. My prime would reboot after 5-10 seconds into the homescreen after boot. After wiping, I thought for sure my root was screwed until a new exploit was found.
I accessed my device through adb, and realized that I could invoke a root prompt using the su command at the $ prompt. Using ES file explorer, I could see su in /system/bin/ but no su-backup or superuser.apk in /system/app/.
I tried simply installing superuser from the market, but it did not work. The busybox installer would not work, either.
ATTACHED ARE THE EXACT THREE FILES I USED. I do not know if using different version will affect the process!
Here is what worked for me:
1. adb shell
2. su
(# - you should see this now! This will not work without this specific prompt!)
3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
5. adb push C:\(location of attached files)\su /data/local/tmp
6. adb push C:\(location of attached files)\busybox /data/local/tmp
7. Access the adb shell again, and type su
8. chmod 644 /data/local/tmp/superuser.apk
9. chmod 755 /data/local/tmp/busybox
10. chmod 6755 /data/local/tmp/su
11. mount -o remount,rw /system
12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
14a. Chmod 755 /system/bin/busybox
14b. Chmod 755 /system/xbin/busybox
15. Reserved
16. busybox rm /system/bin/su
17. busybox cp /data/local/tmp/su /system/bin
18. type su once again to assure you still have access to the # prompt
18a. Chmod 644 /system/app/superuser.apk
18b. mount -o remount,ro /system
19. type exit, and exit again, returning to the regular windows command prompt.
20. type 'adb reboot' (without quotes)
NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
21. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt!
22. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
23. Get SuperSU from the market. It seems to be the safest method to keep root with JB...
ALSO! Make sure to keep a backup root with voodoo or super su after completing this guide! I have lost root (VERY WELL may have been my own fault... too much poking around) Anyway, better safe than sorry!!!
Thanks to daymz from the debugfs thread in development for the basic instructions of what needed to be done!! And also thanks to all before me who got us root in the first place!
I will answer questions to the best of my ability. I am not a developer and do not try to present myself as so... I can tinker with the best, and after losing root, I set out to see if I could figure it out!
Changes made as per tsmt9715I have fellow this method and it was failed at step 16 in my case because of the permission issue but I managed to make it move and regained the root. The details of the issue as below.
Step 16 failed because step 13, 14 which will copy busybox to /system/bin and /system/xbin with a wrong executive permission.
To correct in my case: after step 13, 14 follow those steps below:
- chmod 755 /system/bin/busybox
- chmod 755 /system/xbin/busybox
- skip step 15
- continue steps 16, 17, 18
- chmod 644 /system/app/Superuser.apk
- continue step 19, 20, 21, 22
Then you will get your root back, it worked in my case. Good luck guys.
To the OP, please verify and update those steps if necessary.4I just figured something out. I found a su-backup in /system/usr/we-need-root . I have lost root again since making this guide. My permissions were screwed up on su. I was able to restore root by doing the following:
Code:adb shell: $ cd /system/usr/we-need-root $./su-backup; su (that is a semicolon immediately after the ./su-backup) # mount -o remount,rw /system (do what needs to be done) #exit ...
su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.
Code:Required su-backup permissions for manual root restore $ ls -l /system/usr/we-need-root/su-backup -rwsr-sr-x root ...
basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.1
As far as I know, unless someone is keeping a HUGE secret.
I should mention the unlocker from ASUS but i don't know if anyone has tried it on JellyBean1Same Boat:
shell@android:/system/xbin $ ls -l
ls -l
-rwxr-xr-x root shell 497964 2012-09-26 21:25 busybox
-rwxr-xr-x root shell 59760 2012-09-27 11:18 dexdump
-rwx------ root root 5380 2012-09-27 11:18 ps3bttest
-rwxr-xr-x root shell 23592 2012-09-27 11:18 rfcomm
-rwxr-xr-x root shell 380532 2012-09-26 21:04 su
This is my output when I type SU
shell@android:/system/xbin $ su
su
1|shell@android:/system/xbin $
