I updated SU last night and used the app to push the file and now I can't get root access.
Anyone gotta fix?
Did you set the permissions correctly on the binary?
You need to give more detail otherwise.
Sent from my HTC Desire using Tapatalk
How about you tutor me on how to set the permissions correctly ... if you don't mind.
I used the app to try and update. It would not update successfully through the app so it put a .zip file in /sdcard so I moved to external, to flash and I get a bad file error from CWR
Which app are you trying to update from and which zip are you trying to flash with cwm?
Sent from my HTC Desire using Tapatalk
SuperUser ChainsDD
When trying to update binary I get a error msg that state unable to update. There is a .zip file placed on your sdcard flash thru recovery to update. That is not word for word but close enuff
Brenardo said:
SuperUser ChainsDD
When trying to update binary I get a error msg that state unable to update. There is a .zip file placed on your sdcard flash thru recovery to update. That is not word for word but close enuff
Click to expand...
Click to collapse
Well, assuming you didn't replace the boot image, you should be able to remount with "adb remount", I suggest you follow my rooting guide from that line, which will also help you with permissions etc.
Sent from my HTC Desire using Tapatalk
just to be clear I am already rooted and have no problems with root until I try to update SU.
Uninstall update and restore nandroid back to root with no problems ..
Brenardo said:
just to be clear I am already rooted and have no problems with root until I try to update SU.
Uninstall update and restore nandroid back to root with no problems ..
Click to expand...
Click to collapse
Well, either don't update su, or follow my guide as suggested but replace my superuser files with your updated ones.
Sent from my HTC Desire using Tapatalk
I just wonder why the update will not work
i have this exact same problem. it wasnt working so i updated through the market and it worked for one app and then it wouldnt at all. i tried updating the binary like Brenardo but i get the same error and in CWM it says its a bad file
Same here really annoying.
Sent from my MB860 using XDA Premium App
The problem is the su installed by SuperUser app is not compatible with the Xoom. All you have to do is do a terminal session or use adb with the "adb shell" command which will get you to:
$
type "su" and hit the enter key and it should give you back:
#
If it doesn't, and you get the following:
reloc_library[1315]: 2756 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
The 1315 and 2756 might not be the exact numbers since I didn't note down the exact numbers before I looked up how to root a Android device when one has lost root.
See post #340 in the following thread for the fix:
http://forum.xda-developers.com/showthread.php?t=1117004
This is the previous version of the su binary that was modified to work on the XOOM which is version 2.3.1-ef, hopefully there will be a modified version of 2.3.1-efg available soon.
So the zip file that is put on the SD card is the file that we need to push?
Almighty1 said:
The problem is the su installed by SuperUser app is not compatible with the Xoom. All you have to do is do a terminal session or use adb with the "adb shell" command which will get you to:
$
type "su" and hit the enter key and it should give you back:
#
If it doesn't, and you get the following:
reloc_library[1315]: 2756 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
The 1315 and 2756 might not be the exact numbers since I didn't note down the exact numbers before I looked up how to root a Android device when one has lost root.
See post #340 in the following thread for the fix:
http://forum.xda-developers.com/showthread.php?t=1117004
This is the previous version of the su binary that was modified to work on the XOOM which is version 2.3.1-ef, hopefully there will be a modified version of 2.3.1-efg available soon.
Click to expand...
Click to collapse
But it has been working up until yesterday when it asked to update
Sent from my MB860 using XDA Premium App
Seadub2 said:
But it has been working up until yesterday when it asked to update
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Consider that some updates are incompatible or just bad. I am not allowing the update. I have disabled auto update. My current superuser is just fine, thank you.
Brenardo said:
So the zip file that is put on the SD card is the file that we need to push?
Click to expand...
Click to collapse
No, unzip the zipfile and you will get a file called su which is what you need to push. The zipfile is only for convenience and also so you will know if the file is corrupted or not when you download.
Seadub2 said:
But it has been working up until yesterday when it asked to update
Click to expand...
Click to collapse
The only reason it worked is because Superuser app (the graphical program in the GUI) and su binary which resides in /system/bin are two different things altogether. Previously, the newest su binary was version 2.3.1-ef so Superuser app will not prompt you to update the su binary as it's the same version as what you already have on your device. When the new Superuser came out, after you open Superuser the first time after the new version it's installed, it prompted and told you that a new version of the su binary is available and if you declined it, you wouldn't have the problem. If you accepted it, it basically replaced the existing su binary and replaced it with the new one which is version 2.3.1-efg. No different than if you had Honeycomb 3.1 installed, it would not update unless the number is greater than 3.1.
The latest superuser 2.3.6.3 update can update the su binary to 2.3.2-efgh now which does update automatically and work correctly on the Xoom.
Almighty1 said:
The only reason it worked is because Superuser app (the graphical program in the GUI) and su binary which resides in /system/bin are two different things altogether. Previously, the newest su binary was version 2.3.1-ef so Superuser app will not prompt you to update the su binary as it's the same version as what you already have on your device. When the new Superuser came out, after you open Superuser the first time after the new version it's installed, it prompted and told you that a new version of the su binary is available and if you declined it, you wouldn't have the problem. If you accepted it, it basically replaced the existing su binary and replaced it with the new one which is version 2.3.1-efg. No different than if you had Honeycomb 3.1 installed, it would not update unless the number is greater than 3.1.
Click to expand...
Click to collapse
Thanks for info
tutech said:
The latest superuser 2.3.6.3 update can update the su binary to 2.3.2-efgh now which does update automatically and work correctly on the Xoom.
Click to expand...
Click to collapse
Thanks for the pointer. When 2.3.6.3 came out and I installed it, it did prompt with the su binary update but I cancelled it while I updated the su binary on my Motorola Droid. So when I saw your post, I went into the SuperUser app and went to settings and clicked on check for Su binary update, it said checking failed so I basically copied the updated su from my Motorola Droid and it works.
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Liam1987 said:
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
Make sure your using the latest version of the Superuser app, another option would be to try using SuperSU as an alternative to the Superuser app. Also is root access functioning normally for you?
Sent from my SCH-I535 using xda premium
Hi and thanks for the reply.
Yes superuser is up to date and I've tried supersu. Root seems to be functioning as I can open apps that require root access.
But when I try to restore missing apps via titanium backup, I get a msg saying "restore finished, 'x' elements failed". X being the number of apps I try to restore
Sent from my SCH-I535 using xda app-developers app
Check to see if the root apps are granted root access.
chevyowner said:
Check to see if the root apps are granted root access.
Click to expand...
Click to collapse
When I open SuperSU, it has a list of apps with superuser status. Is that what you mean? I can run root apps and as far as I can tell they're functioning, with the exception of when I try restoring apps with Titanium Backup
Also, right after I flashed CM10.1, I made a backup right away. Not sure if it means anything, but If I wipe/reset and restore the CM10.1 backup, and the first thing I do is try updating the binary in Superuser, it reads "checking installed version: 9 com.Android.Settings", until I open SuperSU and "update binary". Then if I go to Superuser, it'll say "checking installed version: 1.41:Superuser" as I imagine it should. But at this point I still run into "making sure new su works..fail!"
Superuser has no problem updating when I'm on my rooted stock. I'm sure I messed up somewhere along the way while flashing CM10.1, I just don't know where