I bought this phone yesterday, Rooted this morning before work, Voodoo backed it up, and updated to the newest update,
Now when I try to Restore root everything looks grand except Superuser says the su binary is not found.
The su binary is located in /system/bin I believe or xbin but none the less its there. some apps can access root while other cannot..
Any Ideas anyone can give me besides rooting once again, Not an option at work.
Thanks in advanced,
If not let me know and Ill Root again once I'm home, Just looking to play on the slow day.
It's been my experience that on this particular phone Voodoo OTA Root Keeper isn't effective. Simply save the SuperSU.zip on your external SD card and reflash via custom recovery after updating..
The only thing simple is the belief in simplicity.
Haven't Bootloader unlocked yet, used the moto2failgo, or how ever it was to root this morning, so this is what it will be once again once I get home, Thanks for the response, Makes my wonder, the only App that continues to function with root access (aside from Voodoo its self) is Titanium Backup, I am wondering if this is because it has its own busybox and i had not install busybox prior to the update, and cannot now due to lost root.
Related
Okay, first off, I have searched. For the last 3 hours I have searched!!
I foolishly used Razorclaws one-button root method and it worked, However everything after that point has been an utter failure. I tried to flash recovery, and nothing. I tried using CWM, and nothing. I open Super User and it just closes. I don't know what else to do. Yes, I saw post 275 in the razorclaw thread, but when I put in the command list, it tells me it doesn't recognize the command. I previously had a Nook Color and had the easy adb installed. I don't know if this is my problem. I have a B70 transformer, I just want to unroot. I tried the Super User update fixer, nothing. The Transformer is running fine, I get force closes on some apps. I just want to return to stock. Any help will be greatly appreciated.
I unrooted it. But the superuser apk remains in the app drawer. Is there any harm that can be done by having it? I would like to 'successfully' root and flash a rom, but judging from my inability to flash recovery using the one-button method I will wait. I would love to overclock this beast!
You can delete this thread, I apologize for wasting time and resources!
have you tried rebooting and then re-rooting?
how did you unroot ?
Sent from my tf101 using xda premium 1.54Ghz
To get rid of Super user app and binary
http://forum.xda-developers.com/showpost.php?p=19505946&postcount=221
Also if you want to try again and get SU working you can try this
http://forum.xda-developers.com/showthread.php?p=19555429
Thanks for the replies
I did not reboot and reroot, I did have to download the SDK in order to use the adb functions. I used the info provided by doaist to remove su permissions, I suppose. When I checked through the razorclaw app, and terminal. I was not given su access. So, I assumed I didn't have su permission.
And as soon as I try to get into the adb shell and type 'su' it says 'permission denied' , I don't know what else to do to remove it.
Thanks for your input guys, it means a lot.
Okay, so I redownloaded said apps, and I am now performing a backup. Which rom should I use? Which rom will allow me to retain stock functionality , and which OC kernal should I use. Is there a rom that has both?
When flashing recovery, does it go to the emmc or the extrernal sd???
woundedworld said:
When flashing recovery, does it go to the emmc or the extrernal sd???
Click to expand...
Click to collapse
External micro sd card
Hi,
I rotted my phone on 2.3.5 and followed manual upgrade process to get 2.3.6 and indeed it worked fine with keeping root.
Of late, when ever I run TitaniumBackup it give me warning as
"Your ROM is rooted but SU binary has non-optimal access rights, which may cause problems
Titanium Backup Pro can fix this problem automatically in many cases. Do you want to proceed? "
When I say "Yes. do it", it gives me message as
"Access rights on "SU" binary was succesfully corrected from "0:0:[4755]" to "0:0:6755" " and asks to restart for apply changes.
Once it restarted it didn't seems to apply changes and asks me same question when I re-open TB.
I understand it has something with access rights files but not sure how to fix this. [we moved SU to diff path to keep root, is that causing issues?] Can someone help me.
Thank you.
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Shaliuno said:
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Click to expand...
Click to collapse
I think so, used below method.
go to /system/bin/
open in text editor – mount_ext3.sh
add the 3 following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
I did used ES File explorer to perform this. I also read posts mentioning the problem because of ES, how ever I performed this earlier even before complaints and never had problem as it stayed Rooted, so left as it is.
I also installed SU updated from market as I had problems with updating SU binaries.
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Shaliuno said:
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Click to expand...
Click to collapse
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
sazhagianambi said:
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
Click to expand...
Click to collapse
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Thank you!
jimbridgman said:
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Click to expand...
Click to collapse
Thank you Jim for clearing up, may be I should setup ignore warning then.
Shaliuno said:
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Click to expand...
Click to collapse
TB can and has messed up backups, frozen apps come unfrozen at the worst times, it has a minimal busybox, it has broken root before, it is just more of a headache than anything else... there are several apps that will give much better results.
For freezing apps, try modaco's eazy freezy
For backups, use ROM manager, way more successfull, and VERY stable and tested, and the backups it uses are the same that most manufactures deliver in the fxz and updates, since they are saved in img files, and they can be restored from a default recovery if you really are stuck, and can not even get into it on boot...
For busybox, there are two really good ones, I personally use busybox installer from JRummy16, also the one from Stephen (stericson) is really good too, and I have used it, but had an issue with a version several versions ago, and switched.
I am not bashing TB in any way, so no flames, if you like it.... This is just my experience and I have been using android since 1.4-1.5 version, and I have seen a lot of things....
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
In terminal, does "which su" and "which busybox" return anything?
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
You probably have 2 versions and one is not does not have the su id set.
sent while running with scissors
gee one said:
In terminal, does "which su" and "which busybox" return anything?
Click to expand...
Click to collapse
I tried running it in "Android Terminal Emulator" but for some reason it doesn't work anymore, it loads and then auto closes... so I did it in "System Tuner"s terminal emulator.
I ran both and got "Failed to run: Error running exec(). Command: [which, su] Working Dierctory:null Environment: null"
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
Click to expand...
Click to collapse
for both of these i get "No such file or directory"
I honestly have no idea what is going on because this last week I used it as a netbook while travelling Korea and for the 4 months prior I haven't been able to access the internet regularly so I haven't been playing around with CWM, flashing new roms, etc. I think the newest apps I've installed were mixi (like Facebook, but Japanese), Skype, and Temple Run, none of which require root access.
shadowmonk36 said:
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
Click to expand...
Click to collapse
Don't do the wipe yet, just use Recovery to reinstall the same ROM and it may help. It maybe related to kernel or /system/bin or /system/xbin (or even etc).
I tried reflashing the most recent Revolver Honeycomb update (3. 11.1) but it didn't help, still have the problem.
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Thing O Doom said:
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Click to expand...
Click to collapse
I will give that a try, as soon as I can find the superuser.zip file in question. I googled for it, and looked on XDA but I can't seem to locate it. Could you help point me in the right direction?
I re-thought about what tingtan said and I realized that just an update wouldn't necessarily have everything needed so I found the most recent full ROM and flashed it followed by the update and it looks like things are fixed.
I'd still like a link to that superuser.zip file for the future, but now I can backup and I might try playing with ICS now.
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Thing O Doom said:
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Click to expand...
Click to collapse
Thanks, that is the one I found but since you were talking about SuperSU I wasn't sure if it was correct. I will also give SuperSU a try, but after I reflash everything (it broke again shortly after I got my titanium backup done).
I was originally rooted by using invisiblek's original "stock" root, which contained some Sprint stuff, so I opted to do a clean start from a stock Verizon rom, but to save time I rooted using the adb script method from GS3DebugFSRoot http://forum.xda-developers.com/showthread.php?t=1792342 instead of Root66, which requires a 1.5 GB image download then must be flashed through Odin.
I did this to avoid some of the strange app behaviors from the rooted "Sprint" rom, but after rooting through adb with an automated script, some root apps don't function properly, even though they're getting root permission.
After doing some research and restoring my sprint NAND backup several times to compare, the main things I noticed are:
1. After rooting through adb, the Superuser.apk app is installed in /data/app (which is a user app location) as opposed to /system/app in the case of the flashable root method.
2. Superuser.apk is called com.noshufou.android.su-1.apk instead
3. Superuser.apk from a flashed rom has these permissions (seen using root-expl)
rwsr-sr-x, but the adb method file xxxxxx.su-1.apk has these permissions rwxrwxr-x
4. The owner of the file is "root" when flashed through Odin, but "system" when rooted with adb.
Otherwise, the su binary itself is ok, it is a newer version and larger in size compared to the flashed versions, but it has the right permissions and is located correctly in /system/xbin.
I tried deleting the xxxxx.su-1.apk in /data/app and copying Superuser.apk to /system/app, to make it a system app, reset permissions and "owner" and "group" to root, but lost root after rebooting, so had to start back from my NAND backup again.
Does anyone know how to make Superuser a system app in the /system/app folder without losing root?
Also, I'm not sure this is the cause, but Titanium Backup has a hard time detecting root every time I start it, and has to be restarted multiple times, which wasn't a problem when flashed root w/ Odin, and most importantly, DroidWall is not blocking ANYTHING, whether it's in whitelist or blacklist mode, which it did when I used Odin to flash a rooted rom. I've tried everything, bu to no availe, can a dev that might have an idea what is going on here, help me with this and point me in the right direction to look for what to fix to get DroidWall to work, and if that is causing these issues, to get Superuser installed in the right folder?
Thank you
Nvm, I can't seem to find it again, I know I saw it somewhere though. If this was the OG Droid or Droid 2 I could tell you how to adb push no problem, but it's my first Samsung device. I don't know if anything is different, and I don't wanna be responsible for a brick :S
I somehow have managed to lose root access. I have superuser installed but the prompt to give root access to apps does not appear anymore.
I tried to do a factory reset, which was a huge mistake as I had changed the dpi and the launcher failed to start after reset. I tried rerooting using sparkym3s auto rooting tool, but no luck.
I now have the device somewhat operational again after installing apex launcher, but several apps show up as incompatible in the market that used to work before.
How can I regain root?
Factory reset clears the /data partition (you should've just renistalled the Superuser app, possibly a different version, or use and run SuperSU), where your installed apps and data are stored, so it will only delete the Superuser app for managing su access, but the su binary itself should remain on the /system partition. Check for it it /system/xbin/su
What's the problem with sparkym3's method anyway?
Thank you for replying.
After installing supersu it appears i have somewhat regained root access.
I can now change dpi with LCD Density Modder.
However, titanium backup, and several other apps dont get root access, and I dont get a prompt asking for access either.
Rootchecker shows that I dont have root access.
When I run the supersu app, it wants to update, i click ok, but i get error message "installation failed. There is nothing in the supersu log or apps tabs.
The su binary is in /system/xbin/su.
Should I un-root and then re-root perhaps?
I have messed around with this thing so much now, that I would prefer to wipe the entire storage and start completely fresh. Is this possible?
According to this topic I had rooted my infinity but now I did a wipe from boot (volume down + power on) so I lost all my apps including superuser app. My answer is: have I got root yet? Or have I lost only superuser app?
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 2
maanebedotten said:
I have messed around with this thing so much now, that I would prefer to wipe the entire storage and start completely fresh. Is this possible?
Click to expand...
Click to collapse
Try a few variants of what you've mentioned, if this doesn't help, you can try re-flashing firmware from the bootloader level.
mouse100 said:
According to this topic I had rooted my infinity but now I did a wipe from boot (volume down + power on) so I lost all my apps including superuser app. My answer is: have I got root yet? Or have I lost only superuser app?
Click to expand...
Click to collapse
Just install Superuser from the Playstore and see for yourself before asking You should have your root access back.