Hi XDA Community,
Your forums have helped me in the past and I spent some time scouring the posts before posting this one as I couldn't find anything that was specific to my issue. Since this is my first post, I thought that I would save a ping pong of responses, by being fairly expansive on what the problem is and what I have tried; thus hoping to pinpoint my issue a little quicker.
Device Details:
---------------------
Model Number: GT-I9100
Android Version: 4.0.3
Kernel Version: [email protected] #3
Build Number: IML74K.XWLP3
ROM Firmware: Samsung-Updates.com-GT-I9100_O2U_1_20120326173406_jiut50pyip.zip (via Samsung Kies)
Rooting Method / Kernel: Odin3v185 / CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Summary
--------------
Since the beginning of July 2012, I successfully upgraded from Gingerbread v2.3.6 to ICS v4.0.3 using Samsung Kies then initiated root privileges by using the CF-Root Kernel via Odin (versions shown above) - All has been working fine 100%.....
However, it appears that I seem to have lost my SU permissions and may have disabled my root access, even though my device was rooted and I would appreciate any assistance from anyone who might have time to shed some light on the situation.
Behaviour of Apps I have tried that require root
-------------------------------------------------------------------
SuperSU
SuperSU Pro v0.96 lists in the 'Apps' tab (denoted by a green # symbol) that I have granted all relevant Apps that require SU privileges. This includes AdFree, BusyBox Pro, Root Checker Basic, Root Explorer, SetCPU, Terminal Emulator, Titanium Backup, Triangle Away.
Terminal Emulator
Terminal Emulator displays the following and when I enter the su command at the prompt, I just see a carriage return with a grey block. In other words, I do not see the # symbol denoting I have su privileges.
a/local/bin:$PATH
[email protected]:/ $su
Root Explorer
Root Explorer no longer displays a directory listing and simply displays a pop up from SuperSU after tapping on Root Explorer, "Root Explorer has been granted superuser permission for an interactive shell." then the following message from Root Explorer itself:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on."
Root Checker Basic
Apart from the App stating "Please wait for Root Check to be complete. Systems appears to be running very slow" after tapping on the [Verify Root Access] button. It never seems to provide an output after a few minutes waiting. My conclusion is that it cannot get su permissions.
BusyBox Pro
SuperSU displays the message that Titanium Backup has been given root access, however I get the following message:
"Asking for root rights..."
Then after a few minutes I receive this most enlightening output:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and includes BusyBox and try again.
This attempt was made using the "/system/xbin/su" command."
I read somewhere that Titanium Backup uses it's own BusyBox installation and not the system wide BusyBox package so I went in to the Titanium Backup preferences and selected 'Troubleshooting settings' then chose 'Force system BusyBox' to see if my issue was a BusyBox specific problem. Again, it failed so not sure if it is BusyBox or my SU permissions that have somehow got corrupted or been disabled.
Additional Information
-------------------------------
Using 'ES File Explorer', I can confirm that the following file's exist at the appropriate location paths:
/system/xbin/su
/system/xbin/busybox
Conclusion so far
-------------------------
It appears that on the face of it that I have lost my root permissions, so I removed apps from SuperSU, then uninstalled the App (e.g. Root Explorer, Terminal Emulator et al.); then performed the rooting procedure again via ODIN and the CF-Root kernel. The process itself worked flawlessly and so after it rebooted, I installed the Apps in question from the Google Play Store again and they prompted to be granted SuperSU privileges. Unfortunately, the same issues arose where it appears that it cannot communicate with either the su command or BusyBox to do what it requires.
Does anyone have any ideas as the phone is fine apart from this and although performing a Titanium Backup backup around two weeks ago, I would sooner not have to wipe everything if I can help it. I wonder if it is an update that somehow confused things...Either way, I cannot use Titanium Backup to backup/restore due to it requiring SU/root permissions, of which I do not seemingly have anymore.
Any ideas please as I am scratching my head and have gone blurry eyed at spending hours viewing various forums and posts?
follow this steps:
1. Unroot your phone with the unroot method here
2. To be sure, unroot again with the method here
3. ROOT your phone again using Any of the Rooting methods in the links provided in step 1 or 2.
Good luck
ICS 4.0.3 Lost su permissions even though device was rooted - Resolved
:good: Issue Resolved :good:
Many thanks for contributing to my issue. I had come across the post before in your links and although the directions were not completely related, there was a section pertaining to a zip file that I must have missed.
Conclusion
----------------
As can be read in the post, I was unsure if my issue related to losing root, a possible corrupt su file itself or BusyBox. As you will see on the link below, Busy Box actually creates hundreds of symbolic links (symlinks) and due to my perhaps overzelous approach to wanting a quick fix; I must have inadvertently created too many links with different versions of Busy Box and therefore when an App that was correctly added and granted SU permissions within SuperSU, when it then communicated with Busy Box / su to authenticate; I can only imagine it got confused and was lost with all the dead symlinks. The net result was that although SuperSU stated that it had granted permissions to the Apps requiring root, it never got to communicate with the su file contained within /system/xbin. I hope that makes sense, well at least I am pretty sure that is what happened.
Solution
------------
Firstly, I cleared all entries contained within SuperSU and therefore removing all Apps from being granted with root access (they didn't have it anyway at the moment).
I saved the zip file contained at the following link on to my external SD card and choosing to 'install zip from sd card' within the CWM Recovery (Volume Up + Power + Home button); effectively this uninstalls Busy Box completely from your device, including hundreds of symlink files - including many which in my instance was causing issues with Apps that required root to function correctly.
Busy Box Uninstaller v1.0 here
I restarted my device and downloaded Busy Box from Google Play Store and when I opened Root Explorer and the other aforementioned Apps shown in this post, they prompted to be granted root permissions (SuperSU) and voila....it worked ! :good:
I hope this may help other droid users experiencing similar symptoms.
Related
I installed Z4 mod and ran it and it says my g-tab is rooted. I have read that custom ROMS are pre-rooted. In my limited linux experience - being root gives you total control over the machine. I ran Terminal Emulator and cd / to get me to the top of the file structure. I tried to mkdir test and I was denied because the file system is read only. Next I went into the system folder because a lot of stuff in there looks familiar. I again tried mkdir test and was denied because the file system is read only. It would seem that to be root I would need a password and Z4 didn't offer to give me one or let me set it. Thinking further, I wonder if the file system is mounted for read only and that is why I can't create a new directory. When I am running the rom (Vegan) I can write there (understanding that I am writing to the sdcard that is mounted - presumably with RW access. So, what is all this rooting talk about then? What is the purpose of being root if you still do not have access to the file system?
You need Superuser.apk, as well. Think of Superuser as similar to Windows UAC, and rooting as making yourself an administrator. Even though you have root (admin) access, UAC (Supeuser.apk) still needs to let you through.
You also need "root aware" apps. Perfect example is Titanium Backup and that's usually my "litmus test" for verifying if I really have root or not on a device.
yup, in my limited rooting experience (droid1 and gtablet), after the process, there was always a new icon in the app tray entitled "superuser". i didnt have to install it separately, it showed up after the rooting process. if you don't have the superuser app, im betting the root process was unsuccessful.
my memory tells me i had some problems with z4root rooting my tablet, and i had to do it a few times before it actually worked. that was back in december tho, so i dont know if the current version of z4 is different than the one i used, and if so, if kinks were worked out...
so yeah, i probably helped none.
I always though z4root and Superuser were kind of a package deal.
I use them on my Cowon D3, as Cowon completely locks down their recovery process. boo to that.
rodzero,
With z4root you install it first. Then, you install a file manager program like "Root
Explorer" and when it comes up you click to "Allow" it. After that, you can go in
through Root Explorer and create and change R/O to R/W as needed. Same same
with Titanium Backup, once you have "allowed" it you can do what you need
to with the program.
Rev
More Investigation.
Thanks for the fast responses! I do have Superuser installed and it pops up from time to time when an app wants su access. Using terminal emulator, I worked my way into and what do I find but su! I ran su and got was granted su rights in the terminal. I felt pretty smug so I headed into the etc folder thinking I would make a simple change to the hosts file just to see if I could do it. I'm used to using nano in Ubuntu but no nano here. I tried vi (which I really don't know how to use) and I got some strange display but I don't think it was an editor. So, for the sake of closing the loop - if I wanted to edit the hosts file and add a new host - how would I do it. The Terminal Emulator now seems to be in the list to be granted su whenever I type it in. I know how to move around the file system. What kind of text editor would I invoke to actually alter the file? OK.... I went and downloaded TED and worked my way back to the hosts file, added a line but TED doesn't have su rights to save the file. So it looks like su exists but I don't see how to run an app in su mode except for terminal where I can invoke it by a text command. What's the missing piece to get TED to ask for su access?
Just a guess, but TED need to ask for elevation of privileges. It's probably an app issue.
Device: Verizon Samsung Fascinate
Model: SCH-I500
Hardware verison I500.04
Firmware verison: 2.2.2
Baseband verison S:i500.04 V.ED05
Kernel verison 2.5.32.9
Build number SCH-I500.ED05
Background:
I am a simple root user who does not whish to flash any ROMs or custom mods. I just want root access to the phone. Until ED05, the SuperOneClick tool has done for the job for me every time. Verizon was kind enough to force ED05 down to me even though I declined it a about 5 days ago. I woke a couple days ago to my apps stating that root was not working. Boy was I pleased! Anyway, I promptly grabbed the lastest verison of SuperOneClick and fired it off and it said I was already rooted and asked I wanted to do it anway so I said sure, make it so Number One. But even after rerunning the root without errors, and rebooting multiple times, the applications don't think I'm rooted and the unroot process hangs when I try that. Since root is not working, I cannot take a backup via my Titanium Backup and I've never been able to use any of the CW stuff to take a backup image prior to flashing thanks to the nerfing of that process. I don't not want to lose any of my app data or SD card data in the process of rerooting and I want to be in a state that allows for very quick and easy "cleanup" of the phone in case I need to return it. I'm very nervous about trying any of the ODIN methods and losing my data or bricking the phone. Can someone please provide some detailed instructions on what the best steps are to meet my requirements?
Requirements:
1) No loss of current app data or SD card data.
2) Very low risk procedure
3) Simple procedure
4) Phone is a state that allows for quick and easy reversion to "clean" state without having to restore data from backups.
5) No custom mods/ROMs - official verizon releases preferred with Titanium Backup used to "freeze" unwanted bloatware.
ashesofthefall said:
Device: Verizon Samsung Fascinate
Model: SCH-I500
Hardware verison I500.04
Firmware verison: 2.2.2
Baseband verison S:i500.04 V.ED05
Kernel verison 2.5.32.9
Build number SCH-I500.ED05
Background:
I am a simple root user who does not whish to flash any ROMs or custom mods. I just want root access to the phone. Until ED05, the SuperOneClick tool has done for the job for me every time. Verizon was kind enough to force ED05 down to me even though I declined it a about 5 days ago. I woke a couple days ago to my apps stating that root was not working. Boy was I pleased! Anyway, I promptly grabbed the lastest verison of SuperOneClick and fired it off and it said I was already rooted and asked I wanted to do it anway so I said sure, make it so Number One. But even after rerunning the root without errors, and rebooting multiple times, the applications don't think I'm rooted and the unroot process hangs when I try that. Since root is not working, I cannot take a backup via my Titanium Backup and I've never been able to use any of the CW stuff to take a backup image prior to flashing thanks to the nerfing of that process. I don't not want to lose any of my app data or SD card data in the process of rerooting and I want to be in a state that allows for very quick and easy "cleanup" of the phone in case I need to return it. I'm very nervous about trying any of the ODIN methods and losing my data or bricking the phone. Can someone please provide some detailed instructions on what the best steps are to meet my requirements?
Requirements:
1) No loss of current app data or SD card data.
2) Very low risk procedure
3) Simple procedure
4) Phone is a state that allows for quick and easy reversion to "clean" state without having to restore data from backups.
5) No custom mods/ROMs - official verizon releases preferred with Titanium Backup used to "freeze" unwanted bloatware.
Click to expand...
Click to collapse
You can try this. http://forum.xda-developers.com/showthread.php?t=1045048 (Ignore that it says MOD, it only installs root )
(Sorry, this uses Odin, but I find it the easiest way, if your not sure then post and I'll try to answer your question, and it only installs root. Apps like SuperOneClick no longer work correctly).
Get Odin, the Samsung Drivers for SCH-I500, and this recovery: http://www.mediafire.com/?6x5utoca59et7o9. Put the su.zip on your SD card.
Install the Samsung Drivers. Power off the phone, remove the battery, plug in your phone into your computer while holding the volume down button and use Odin to install the CWM Recovery (click the PDA button and select the CWM recovery all.tar, then hit start). Once that is done, replace the battery, boot your phone by holding down power, volume down and up at the same time. Your phone will boot into CWM. Install the su.zip in CWM and reboot the phone. The kernel will remove CWM at boot so there will be no sign of it but after that your root should come back.
It worked fine for me.
That did work, thank you. I still don't quite understand what all the different pit, recovery, zip and tar files do and what exactly happens when you use the different files with Odin. Can you point to me to a "Odin and CWR for Dummies" or something that lays all this out in simple terms? I've read through the master rooting and recovery threads a few times but I still don't grasp exactly what the different pieces do and what they overwrite and when. For example, how would I go about quickly removing the root stuff from my phone now without losing all my settings and data?
It worked for me fine the other day also. And yes I was on Ed05
Sent from my SCH-I500 using Tapatalk
I was able to root 2 updates ago with SOC but just got around to re rooting after ED05 installed.
Didn't work...most annoying. lol
Checking with Root Checker and I get the following output.
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.1 - Added clear log to menu in log tab, More languages, Bugfixes is installed!
Standard su binary location: ls -l /system/bin/su:
-rwxr-xr-x root shell 26264 2010-10-16 22:04 su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root shell 26264 2011-08-15 18:46 su
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
SU binary not found or not operating properly
Any help?
jiminigrist said:
I was able to root 2 updates ago with SOC but just got around to re rooting after ED05 installed.
Didn't work...most annoying. lol
Checking with Root Checker and I get the following output.
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.1 - Added clear log to menu in log tab, More languages, Bugfixes is installed!
Standard su binary location: ls -l /system/bin/su:
-rwxr-xr-x root shell 26264 2010-10-16 22:04 su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root shell 26264 2011-08-15 18:46 su
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
SU binary not found or not operating properly
Any help?
Click to expand...
Click to collapse
The easiest way to root would be to use ODIN and flash CWM (via PDA, always)..
Then go into CWM then install the SuperUser+BusyBox.zip
I have 2.2.2 as well and the latest superoneclick did not work, but the old 1.5.5 version did work.
hey, hmm, i am new at this forum but i been rooting phones for a long time, well to make the story short, i have a samsung fascinate and i updated it to GB well after the update everything was working fine now that i want to install custom rom, or cw, trying to use odin, my computer won't recognize my phone, i installed the driver and everything but when i plug in my phone i and try to put it on download mode it shows a USB error, please can someone help i have search everywhere and can't find a solution,,, thanks thou,
Conflicts? LG P769 rooted V18. Binary update fails, su reports "The ap su (processom.noshufou.android.su has stopped unexpectedly)" then crashes. Until resolved and certain that su will preserve root would like to prevent ph from forcing update. Have read several methods one is to freeze a couple of scripts w/Titanium, another to delete 24MB ip folder 10e>10g in cache and alter Google Framework. Not sure which is the safest or easiest with apps I already have. That's two requests which will be greatly appreciated: One to resolve su binary fail w/possible app conflicts the other to simply stop OTA until I understand Andoid and the apps better.
Installed: SuperSU (non-pro- no survival mode) , Superuser Elite(over vs from Bin4ry), Smanager Elite, OTA Root Keeper, Titanium BU Pro
btw- No response from ph running Bin4ry? Go to redmondpie com "how-to-set-up-android-adb-and-fastboot-on-windows-tutorial" Only way it worked for me. Followed the directions and was able to view my device in command box prior to executing v18.
note: When editing the string as described, redmondpie, +be sure not to wipe out any part of existing script+ (hit end , blue box turns white). Copied and pasted extracted bin4ry "stuf' in a folder labled Andoid-adb set up in adb environment. Root executed from there first try after dozens of failures w/other methods.
>>not sure if I have valid root restore tools should OTA (already in cache) executes<< >>Meanwhile, which method to prevent OTA execution<<
notes from apps
root checker basic verifies root; voodoo all boxes checked, protected su copy available but note "using both su and SupersSU take care keeping app and su bu consistent" (should not be issue since not the pro vs of SuperSU - no ota survival). edit just started to rept "sys running very slow-pls wait for r-ckr to cmplete.
Superuser elite v3.1.3(46) (downloaded over Bin4ry incl vs) shows no apps, no log, o entries Binary updater fails, "The ap su (processom.noshufou.android.su has stopped unexpectedly" then crashes. "bu written to sd card"black box flashes to say su has been granted superuser permission interactive shell access; access timeout aps not remembered set to 0; auto response set to prompt; ghost mode off; ...
SU updater reports "sigs ok"
SuperSU v0.96: all green # today (but not yesterday); superuser enabled; surv mode not avail (not pro);
Titanium BU Pro root ccess ok, busybox 1.19.4-titanium from ap ; sqlite- yes 3.7.6.-titan incl; All green checks on overview pg; has quite a few red line entries, probably hven't left ph on long enough for bu to complete
; active data pofile- sys rom 1.03gb ; internal 1.93/1.46 free note down from 1.7 when new.
Smanager reports root access Can this app delete cached ota update zip?
Did I err in downloading elite vs of Superuser over the copy already inserted by Binr4y? Thanks.
As title, I'm trying to root a development board running 4.2.2. I do have root access and put busybox and su, but my problem is that whenever I start apps that require root access, superuser never gives me prompt asking whether root access is allow (yes, my setting in Superuser is to prompt for every apps that require root), as a result, the app would not run reporting that my device is not rooted. As an example, when I trying to run droidvncserver, it would tell me "could not start server", but if I start it as root on a shell, it would run and start server, this leads me to think that droidvncserver is not requesting root access or Superuser does not know that droidvncserver needs root access. I'm pretty sure I'm missing something in my system, but what is it. All this works on a rooted phone, but not on the development board. I've read through some of the rooting script for other phones, mostly include remounting /system as rw and put busybox and su onto the system, and that's what I've done on the board, but there's just no connection between those root-require apps and superuser. Anyone knows what I'm doing wrong/missing?
my method here will give you a permanent rooted shell and will give you read-only system root which is useful for using root apps to backup data or freeze system apps--works just like real root without being able to delete system contents--freezing apps however works like a charm and should reduce the need for rw root anyway
FOLLOW DIRECTIONS EXACTLY--I WILL NOT RESPOND TO STUPID QUESTIONS--PROBABLY WON'T RESPOND TO ANY QUESTIONS BECAUSE MY DIRECTIONS ARE PERFECT, WORK PERFECTLY WHEN FOLLOWED, AND ARE EASY TO READ. FOLLOW ALL STEPS EXACTLY. IF IT DIDN'T WORK, IT IS BECAUSE OF YOUR ERROR
This works best from a factory reset device, but will work from a already used device but all other root apps and superuser apps must have their data deleted and be uninstalled first
1) make sure device is at least 50% charged--doesn't matter most of the time; better safe than sorry
install latest superuser apk
http://www.mediafire.com/file/dx854fsys5pvxjh/SuperSU.apk
install dirty cow root apk (croowt) [comes from this post https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
http://www.mediafire.com/file/1hbey829hc7676a/CRooWt.apk
make sure usb debugging is activated in developer settings and make sure you have accepted the debugging access prompt on the phone for the computer you will use
make sure you have an external sdcard installed--the smaller the better for this first time
2) open dirty cow root apk
choose "get root"
choose "method 1"
hit "ok"
choose "ok"
app will direct you to unmount and remount sdcard, choose "ok" and it will take you to storage settings
unmount sdcard
remount sdcard
when finished proceed to step 3
3) open superuser
do not update su binary
go to settings and make the default action "grant"
remove any and all apps from superuser log including the croowt app
3) THIS MUST BE DONE FROM A REAL TERMINAL ON A PC--TERMINAL EMULATORS WILL NOT WORK FOR THIS STEP
from a working pc with adb setup, preferrably linux, input commands exactly as listed
adb shell
su
setprop persist.sys.k P816A06
reboot
5) once rebooted, open dirty cow root apk again
choose get root
choose "method 2"
hit "ok"
choose "ok"
if app asks you to open with a browser, choose one, and choose "always"
screen will go black, systemui will crash and then reboot
6) once systemui is back up and running
you now have read-only root
you can now freeze system apps or backup your data using apps that require root
Your shell will be permanently rooted when accessed from a computer using adb--this will last forever unless you undo the setprop
Your system however will only be temp, read-only rooted until the phone is rebooted.
If you wish to have your temp, read-only root reactivated, all you have to do is repeat step 5 and that is it.
You can do this over and over again.
GIVE STAYBOOGY SOME PROPS FOR MAKING YOUR LIFE WITH THIS PHONE BETTER
Does this only work to back up or freeze applications?
poseidon207 said:
Does this only work to back up or freeze applications?
Click to expand...
Click to collapse
ACTUALLY READ the first sentence of OP
I don't see how freezing system apps would negate the need for a real root method? Is this "Read-Only" root method working with lucky patcher or Kernel Auditor?
Can this be used to bypass the subscription check for tethering? I assume not since system isn't writeable.
Does this method work in the ZTE Maven 3 (Z835)?
I'm doing it wrong, probably
First of all, thank you so much for doing this. I've been following that other thread since it was new, and you've put far more effort into this than the phone or most of us deserve.
I've gotten stuck trying to run Dirty Cow. I have USB Debugging enabled, adb installed on my Linux computer which recognizes my Maven (i.e. I've allowed access on the phone), etc. It eventually goes from "Checking vulnerability" to "Your device is not vulnerable" and I'm unable to proceed to the "Get root" step. What am I doing wrong? Might be some recent system update? Probably less effort to just buy a Galaxy.
Please be gentle. I know I'm a noob.
z812 root
I previously rooted my maven with kingroot and the dirtycow exploit.sh file and today I was overwhelming the device by running multible windows and apps and the phone rebooted and root was still intact....haven't rebooted it again yet but I shall.