Related
Superuser.apk is force closing on me. I can run TiBu and Wireless Tether (both of which require root access), so I know I have root access, but when I try to open the superuser.apk, or when I install / upgrade an app I get a FC from the superuser.apk.
Where I am:
-ATT Atrix, stock / bootloader locked with 4.5.91 applied through USB over stock / bootloader locked / rooted 4.1.83
-Did the preinstall root method from briefmobile after the 4.5.91 update
-Updated the superuser.apk from the market
-Rebooted a number of times
At this point the phone is running fine, and I need it for work so I want to stay away from a potential brick, but I have gone through custom ROM's on previous phone (ATT Captivate). The FC is really more of an annoyance, and I'd like to make sure that if / when I decide to go the custom ROM route my su is working as it should.
Any thoughts / suggestions?
OK, I read a bit more and tried to clear the data on the superuser app. Now, after a reboot, TiBu can't even get root access because the app FC's when I open TiBu.
Help?!
sjroberts98 said:
OK, I read a bit more and tried to clear the data on the superuser app. Now, after a reboot, TiBu can't even get root access because the app FC's when I open TiBu.
Help?!
Click to expand...
Click to collapse
Have you tried unrooting, factory reset, and then rooting yet?...
No, haven't tried that. To unroot, should I just uninstall the superuser.apk? I don't think I've seen an unroot script for 4.5.91 yet.
Thanks for the tip, I'll try that once I figure out the best way to unroot.
OK, it appears to be resolved.
What I did:
-uninstall the superuser.apk through Manage Applications
-download the preinstall file from the XDA forum post (versus the file from briefmobile.com)
-re-ran the same steps
-rebooted
All appears to be working now. My guess is that it was user error (read: I did something wrong the first time).
Nevermind...
Sup guys. This place seems a little dead without any new rom releases lol. Just went to the market to check for some new apps and updates and saw that superuser was available for update.
Kinda weird but I did it and opened the new app. It has a slightly different interface, something like the new market except without the lags. Then it told me that I had to do some updates and I just allowed it blah blah blah. It installed some new software and a custom busybox.
I find that the v6 supercharger works better with this busybox and the other new root stuff lol.
Go check it out!
Sent from my Milestone XT720 using XDA App
You must paying attention we have cm7 just wasting space in the forms.
Sent from my XT720 using XDA Premium App
I upgraded to 3.0 and saw all kinds of problems. Couldn't update the binaries for some reason and lost all permissions and could get su access back. Reverted in TB to okd su and ut was fine. Since then chains updated it again and everything works fine now. Just an fyi.
@Mchlbenner Like your new avatar. Funny.
Thanks
Sent from my XT720 using XDA Premium App
Hey, since we have these new ROMs going and there was some issues before with the Superuser.apk updating the binaries, Chains has created and update fix in the market also. You update the superuser app and then it either works or says the binary didn't update or the app itself couldn't update. Just go to the Update Fix app install and run it and then try to reinstall the Superuser.apk.
If you are flashing in between ROMs daily then I wouldn't worry about it until you settle on one, but if you do find one you like and want to run it for some time, then you'll probably have to eventually update it and this is how.
Woodrube said:
Hey, since we have these new ROMs going and there was some issues before with the Superuser.apk updating the binaries, Chains has created and update fix in the market also. You update the superuser app and then it either works or says the binary didn't update or the app itself couldn't update. Just go to the Update Fix app install and run it and then try to reinstall the Superuser.apk.
If you are flashing in between ROMs daily then I wouldn't worry about it until you settle on one, but if you do find one you like and want to run it for some time, then you'll probably have to eventually update it and this is how.
Click to expand...
Click to collapse
You can also get the latest as an update.zip at AndroidSU.com
This APK root method is currently based on the busybox exploit that rhcp0112345 found, so thanks to him. I currently do not have a donation link in the app for him, but I will add one if he sends me the link and anybody can jump over to his original post if they would like.
This is an interim step of this app as I have been trying to finish a more complicated root method, since this one is most likely to get patched shortly. Also, in future updates I will be adding an unroot method as well as possible rootkeeper type functionality and depending on feedback I may add a quick install for the unlock tool.
The steps are similar to the PC version except it only requires a button press to perform the step.
1. Install this app (SparkyRoot)
2. Click step 1, Exploit (will move the files around and replace the busybox file)
3. Click step 2, Open up the ASUS App Backup tool and backup an app (you can use this one, its small)
4. Return to this app and Click step 3 Install SuperUser (will install the SuperUser app)
5. Click step 4, Cleanup (will cleanup all of the temporary files and revert the busybox file)
6. Profit???
UPDATE: 3/3/2012 - v1.1 - enhancements
Added a button for opening the backup app.
Updated SuperUser app to the latest version (you would have gotten a market update anyway)
Added indicators for if the su binary is there and if it has the proper read/execute permissions
Added indicator for if the SuperUser app is installed
UPDATE: 3/5/2012 - v1.2 - minor update
Added donation link for rhcp0112345
He also requested that I put his link in this thread so here are those
(TF101) http://forum.xda-developers.com/showthread.php?t=1515470
(TF201) http://forum.xda-developers.com/showthread.php?t=1518429
UPDATE: 3/18/2012 - v1.3 – enhancement/fix
Fixed issue where if you have never opened the app backup tool before the rooting would fail due to not accepting the terms of service
Added an unroot option (the current method requires superuser installed so that it can grant this app permission to unroot)
From comments below, it appears that there may be an issue with checking you root access in correlation to Root Checker and BusyBox. I have never installed either of these apps on my device and have never seen the issue. To help clear some of this up I have added a check into my app that will tell you if the files are all set up properly, with proper permissions.
Also, make sure the SuperUser app is running in the background so that it can give root access to apps that you specify (if it is not running, your device will appear to not be rooted).
If you are having any issues, and you are using these apps, I would recommend that you uninstall them prior to rooting and then reinstall them after you have finished running the app to root the device and then reboot the device.
FYI
This root app has been confirmed working on certain versions of the ASUS Transformer (TF101), Transformer Prime (TF201), Transformer (TF300) Devices.
This includes
v9.4.2.15 for the TF201
v9.2.1.11 for the TF101
v9.4.3.17 for the TF300
This method (as it is currently implemented) no longer works with:
v9.4.2.21 for the TF201
v9.2.1.17 for the TF101
v9.4.3.26 for the TF300
To root on one of these non-supported ROM versions, please use this new root tool I have created.
http://forum.xda-developers.com/showthread.php?t=1706588
Nice!!
Sent from my SPH-D710 using xda premium
I just rooted the other night..lol. great work though. ill save it in my android tools folder for just in case anything voodoo fails on next update. thanks man! I was constantly checking this section since I posted on your thread n you said you might make an apk form of rooting. thanks again!
will try on my tf101 later today
rhcp0112345 stated his root-method would work on the tf101 too, so I hope your apk does too!
Orkeren said:
will try on my tf101 later today
rhcp0112345 stated his root-method would work on the tf101 too, so I hope your apk does too!
Click to expand...
Click to collapse
Yes, this should work for the tf101, I think the exploit was actually first found on that device and then confirmed on the prime later.
I have a TF101 with stock ICS installed from Asus website. Can I install this apk through adb since I only have access to a Mac computer now? Thanks!
mj56gt said:
I have a TF101 with stock ICS installed from Asus website. Can I install this apk through adb since I only have access to a Mac computer now? Thanks!
Click to expand...
Click to collapse
Yes, you should be able to, or just download it strait from your web browser on your tablet.
Well I can confirm it working
Sent from my Transformer TF101 using xda premium
I wasn't going to root just yet but if it's as easy as this then I guess I'm convinced. It also means I can run the ezoverclock just released too. What a good day this turned out to be
Thank you!
Orkeren said:
Well I can confirm it working
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
How to verify whether the TH101 is rooted in the end? Thanks!
mj56gt said:
How to verify whether the TH101 is rooted in the end? Thanks!
Click to expand...
Click to collapse
I have an app I purchased for my phone (there is a free version) called Root Uninstaller Pro. I installed that and it asked for Superuser permissions - you only get these if rooted and Superuser is installed
Superuser verifies that Root Uninstaller Pro has superuser permissions
I can't believe how easy this was Thanks again dev
mj56gt said:
How to verify whether the TH101 is rooted in the end? Thanks!
Click to expand...
Click to collapse
just download the free app called root checker. plus download voodoo OTA rootkeeper to save n backup your root file. so it can be restored after an Over the Air update.
demandarin said:
just download the free app called root checker. plus download voodoo OTA rootkeeper to save n backup your root file. so it can be restored after an Over the Air update.
Click to expand...
Click to collapse
YES!!! Success! Really easy, and a lot of fun... Thanks a lot, rhcp0112345 and sparkym3 for the wonderful tool, demandarin and TremF for the quick help!
mj56gt said:
How to verify whether the TH101 is rooted in the end? Thanks!
Click to expand...
Click to collapse
I have been making a few changes tonight:
1. button to launch the backup app (instead of searching for the icon)
2. indicator of if the su file exists with correct permissions
3. indicator of if the SuperUser app is installed
These should take care of showing you if it has successfully rooted. I will update the OP with the new version once I am done.
Followed all steps and didnt get rooted. Busybox and titanium said no root access after tryin this app.
mine did that too until i used the root checker tool. then titanium and root explorer gave me root access.
try that.
i just cant seem to get CWM on this thing
upsbeast said:
Followed all steps and didnt get rooted. Busybox and titanium said no root access after tryin this app.
Click to expand...
Click to collapse
I have updated the app to do the checks to see if everything is set up correctly. Would you try with the new version and let me know your results.
CHANGES: 3/3/2012
Added a button for opening the backup app.
Updated SuperUser app to the latest version (you would have gotten a market update anyway)
Added indicators for if the su binary is there and if it has the proper read/execute permissions.
Added indicator for if the SuperUser app is installed
upsbeast said:
Followed all steps and didnt get rooted. Busybox and titanium said no root access after tryin this app.
Click to expand...
Click to collapse
Stuffed around for a while after installing this app and tried to confirm root access. Seemed that some apps reckoned I had root and some not so much.
Went to market and installed 'Busybox' by STEPHEN (STERICCSON) and root was perfect after this. Even 'Voodoo OTA RootKeeper' was happy after installing Busybox.
Edit: Forgot to mention. I have a TF201 running Android 4.03, Build 9.4.2.15
Thanks for sharing another way of rooting. I do love Viperboy's work. However, vipertime installed it's own version of busybox, and somehow caused the Asus backup application failing to function. It's always nice to know that there's another way to root.
And Please, do add on an Unroot option, and it'll be all perfect.
Has anyone who updated to Jelly bean tried this method here to obtain root?
http://forum.xda-developers.com/showthread.php?t=1886460
Tried may times. Does not work. Permission denied.
Yuhfhrh said:
Has anyone who updated to Jelly bean tried this method here to obtain root?
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
no luck. did not work
Figured it was worth a try, sorry guys
I was just about to post and see if anyone knew how to root, guess we will just have to wait and see.
Yuhfhrh said:
Has anyone who updated to Jelly bean tried this method here to obtain root?
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Not for me.
My su-backup is just sitting there in /system/ mocking me.
Scumbag Inc. said:
My su-backup is just sitting there in /system/ mocking me.
Click to expand...
Click to collapse
Yup, they reset permissions on /system, /system/bin, and /system/xbin. The backup will need to be in a location that they don't explicitly reset permissions for during an update. For anybody who is curious, you can pop open the dlpkgfile and look at updater-script in the directory META-INF\com\google\android\. At the very end of the file you can see all of the permissions that get reset.
sparkym3 said:
Yup, they reset permissions on /system, /system/bin, and /system/xbin. The backup will need to be in a location that they don't explicitly reset permissions for during an update. For anybody who is curious, you can pop open the dlpkgfile and look at updater-script in the directory META-INF\com\google\android\. At the very end of the file you can see all of the permissions that get reset.
Click to expand...
Click to collapse
Not sure what you are getting at here. Does what you said mean they can move the file to another folder that does not have permissions changed prior to the update and keep root? or does it need to be in system to work?
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!
there must be a way!
Check the root thread in the development forum. Somebody in there has a method for regaining full root for the folks who were lucky enough to have partial root like you after the update. Can't test it myself but it sounds promising.
-S
Sent from my Galaxy Nexus using xda premium
whycali said:
Not sure what you are getting at here. Does what you said mean they can move the file to another folder that does not have permissions changed prior to the update and keep root? or does it need to be in system to work?
Click to expand...
Click to collapse
Yes, that is what i'm saying and the latest version of the voodoo app has changed the location.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------
clouds5 said:
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!
there must be a way!
Click to expand...
Click to collapse
Uninstall and then reinstall the superuser app from the market. Then run the superuser app. This should be the only thing that needs to be done.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
sparkym3 said:
Yes, that is what i'm saying and the latest version of the voodoo app has changed the location.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------
Uninstall and then reinstall the superuser app from the market. Then run the superuser app. This should be the only thing that needs to be done.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I was i nthe same position and i played around with adb shell su and both root methods.. finally it worked. I am not sure if it was when I chomd the su file in the xbin folder or not.
I am waiting for somebody to post a guide on how to keep the root before the update. I have Voodoo OTA and superuser, they seem to be up to date. But it seems to me many others where on the same boat and lost the root... and reading this thread I have no clue what needs to be done to keep it.
piokon said:
I am waiting for somebody to post a guide on how to keep the root before the update. I have Voodoo OTA and superuser, they seem to be up to date. But it seems to me many others where on the same boat and lost the root... and reading this thread I have no clue what needs to be done to keep it.
Click to expand...
Click to collapse
i had the same setup like you and no root after the update
piokon said:
I am waiting for somebody to post a guide on how to keep the root before the update. I have Voodoo OTA and superuser, they seem to be up to date. But it seems to me many others where on the same boat and lost the root... and reading this thread I have no clue what needs to be done to keep it.
Click to expand...
Click to collapse
If you backed up before voodoo was update with the new location (or you OTAed to .30 since the last backup), it is possible that you may lose root.
To be safe you may want to delete and re-backup the root from within voodoo before you update.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
sparkym3 said:
If you backed up before voodoo was update with the new location (or you OTAed to .30 since the last backup), it is possible that you may lose root.
To be safe you may want to delete and re-backup the root from within voodoo before you update.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Could you be more clear on that? Voodoo OTA Rootkeeper v.2.0.3 does not have an option for "deleting the root". There is a "delete su backup" button, and "temp. un-root" one. Could you clarify which of those should be used and in what order? And can others confirm that this method will keep the root after the Jelly Bean OTA update - or is it still a hit or miss?
piokon said:
Could you be more clear on that? Voodoo OTA Rootkeeper v.2.0.3 does not have an option for "deleting the root". There is a "delete su backup" button, and "temp. un-root" one. Could you clarify which of those should be used and in what order? And can others confirm that this method will keep the root after the Jelly Bean OTA update - or is it still a hit or miss?
Click to expand...
Click to collapse
does anyone know if you can use the Asus unlock tool if JB is rooted?
chuunarusamurai said:
does anyone know if you can use the Asus unlock tool if JB is rooted?
Click to expand...
Click to collapse
I lost root with the update but just unlocked 2 min ago because the update is junk so i cant confirm the rooted unlock but it worked on jb at least
jamesh1979 said:
it worked on jb at least
Click to expand...
Click to collapse
Good to know. I just want my root back. I'm starting to freak out!
1. If I do unlock, is it possible to gain root? If so, how?
2. Is anyone working on a ROM based on our JB FW?
I have tried to update my Xperia Z tablet (Wi-Fi Xperia Tablet Z SGP311) but it fails each time. Bootloader is locked, and it is rooted. SuperSU(in survival mode) and the voodoo OTA root keeper are on.
Not sure why it wont flash to 4.2.2 (current stock 4.1.1 rooted).
Also Wondering if I should even bother updating to 4.2.2 this way or try the flashtool kernel workaround doomlord has?
Hello, i've the same problem with my SGP321. SuperSu in survivalmode and rootkeeper installed too.
Sent from my Xperia Tab Z using Tapatalk 4 beta.
Someone else had issues with update not installing, and someone asked if any system files have been modified?
If you do the OTA update only (as you stated), you dont need the OTA rootkeeper, just superuser ticked with survival mode, and SU installed as a system app (in settings menu). Maybe SU and OTA keeper conflicting, maybe OTA modify system files?
If you decide to install SU as system app, it might take several attempts, and several power downs. When I did it, it did not seem to be working, and tooks loads of reboots and attempts
Aid777 said:
Someone else had issues with update not installing, and someone asked if any system files have been modified?
If you do the OTA update only (as you stated), you dont need the OTA rootkeeper, just superuser ticked with survival mode, and SU installed as a system app (in settings menu). Maybe SU and OTA keeper conflicting, maybe OTA modify system files?
If you decide to install SU as system app, it might take several attempts, and several power downs. When I did it, it did not seem to be working, and tooks loads of reboots and attempts
Click to expand...
Click to collapse
Well I told voodo to remove its backup and uninstalled it. SuperSU is now a system app with survival mode on. Tried it again and same thing it gets about a quarter done installing then stops. Anyway to check to see if there's an error log?
Oh and I don't believe I messed with anything in the system files
Rainami said:
Well I told voodo to remove its backup and uninstalled it. SuperSU is now a system app with survival mode on. Tried it again and same thing it gets about a quarter done installing then stops. Anyway to check to see if there's an error log?
Oh and I don't believe I messed with anything in the system files
Click to expand...
Click to collapse
Do you have xposed framework installed?
WythDryden said:
Do you have xposed framework installed?
Click to expand...
Click to collapse
nope, was considering doing that tho
I'm in the same boat. Stock 4.1.2 rooted with su as system app and survival mode on, but nothing else. Install fails every time. Sgp312
I had the same problem. The cause was a modified /system/apps folder. As a solution i copied the missing files from a FTF-File back.
If for example facebook.apk is missing the update will fail.
Oh wow, didn't consider that getting rid of some of the bloat would count. Go figure Facebook would **** it up for me. I don't have a computer anymore at home so I guess I'll start figuring how to get back what I got rid of.
..could anyone upload that system/apps/ folder? In the meantime I guess I can try pulling the ones from the zip of the Japanese stock ROM posted around here..
I can't find any way of extracting a .sin in android
Never mind. Copying the missing files out of the Japanese zip worked and I'm successfully updated!
thanks ill have to do the same it seems, yeah i belive I nailed a good lot of the bloatware :/
My have found my issue I updated youtube with an official but not from the stock app. Now I cant seem to downgrade from the apk from the global ftf. Any help on why root explorer would crash the tablet when trying to reinstall it?
Rainami said:
My have found my issue I updated youtube with an official but not from the stock app. Now I cant seem to downgrade from the apk from the global ftf. Any help on why root explorer would crash the tablet when trying to reinstall it?
Click to expand...
Click to collapse
Does it crash when reinstalling or when running the app?
Sent from my SGP312 using XDA Premium HD app
jonathanp said:
Does it crash when reinstalling or when running the app?
Sent from my SGP312 using XDA Premium HD app
Click to expand...
Click to collapse
Yes it does, I try to reinstall and it eather says fail, or crashes the tablet. But the youtube app works for some reason?
I can't update via OTA. I have everything, i deleted Chrome but i reinstall and still fails.
Enviado desde mi GT-I9100 usando Tapatalk 2
DOOMF1GHTER said:
I can't update via OTA. I have everything, i deleted Chrome but i reinstall and still fails.
Enviado desde mi GT-I9100 usando Tapatalk 2
Click to expand...
Click to collapse
Your best bet is to copy the entire system/app from stock over to your device. Also uninstall xposed framework or any other mods
WythDryden said:
Your best bet is to copy the entire system/app from stock over to your device. Also uninstall xposed framework or any other mods
Click to expand...
Click to collapse
What is xposed framework? I have no mods. Only ad Block.
Thanks
I did a factory reset, install nothing else but the root (super SU, obviously) and I still can't install the update via OTA. Any ideas?
Enviado desde mi SGP311 usando Tapatalk 4
WythDryden said:
Your best bet is to copy the entire system/app from stock over to your device. Also uninstall xposed framework or any other mods
Click to expand...
Click to collapse
attempted this, used ADB to remount the system as r/w and was copying over the first of the files fine with push but as soon as it hits the lockscreen.apk it crashes the tablet. Then have to go do the command line fu to get the darn thing remounted. And did it again. Any suggestions?
Rainami said:
attempted this, used ADB to remount the system as r/w and was copying over the first of the files fine with push but as soon as it hits the lockscreen.apk it crashes the tablet. Then have to go do the command line fu to get the darn thing remounted. And did it again. Any suggestions?
Click to expand...
Click to collapse
Hmm, not sure. I did it all from within the tablet using solid explorer. I compared the two folders and just copied over the apks that were missing.