I was hoping to get some assistance on my struggle to gain full root access to my Meizu 5 Pro (Chinese version)
I've followed this https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-change-region-id-to-t3323883/ guide but I'm getting stuck on getting the access. I attached pictures for you to see where I'm at. Where I've hit the wall as it were.
As you'll see on the pics I actually do have root privileges as root permissions are no longer hidden from me and
fastboot screen on the bottom of the screen also shows that the phone is rooted. But the terminal emulator isn't giving access.
I rooted the phone by logging into Flyme account then -> Settings -> Apps -> searched for Flyme app that has "root" in the description. I ran it,
accepted terms, rebooted and root was enabled. This is the vendor-made way of rooting the phone.
What can I try ?
https://www.dropbox.com/s/whx67tkwj07sdtt/IMG_20200124_173423.jpg?dl=0
https://www.dropbox.com/s/jqsbsodlbdkh1ez/IMG_20200124_173223.jpg?dl=0
https://www.dropbox.com/s/h40dz2d4rvh15er/IMG_20200124_173134.jpg?dl=0
https://www.dropbox.com/s/ehp7qwreifjego2/IMG_20200124_210338.jpg?dl=0
https://www.dropbox.com/s/q1a9fains20cx3p/IMG_20200124_173209.jpg?dl=0
https://www.dropbox.com/s/z3hlzrmcpzgfm5d/IMG_20200124_210314.jpg?dl=0
https://www.dropbox.com/s/g504sjryigmzzpk/IMG_20200124_173606.jpg?dl=0
As it appears the phone is rooted but the app tools (SuperSU, terminal emulator, BusyBox) aren't recognizing it.
Related
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.
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?
Hello,
Thank you for the tips form the Leagoo Lead 3 forum: I wasn't able to post there so I do it here;
I don't know how to relate my own tasks to achieve this:
At least I followed steps 1 and 2: Step 1 was never finished: hangs or failed error message:.
With Kingo Root, always ended up with failure message except the last time:
I was able to root successfully;
Before to successfully root with Kingo Root:
- After several trials with steps 1 and 2. I ended up with Lead3 being rooted as displayed on Kingo Root status, But I wasn't able to use su;
- Once Kingo root status was root, I launched mtkdroidtools 2.5.3, freshly reinstalled(ie I renamed my former version installation), Lead3 was correctly detected with green light, No Root button but ADB. I made a backup and installed SuperSu with this tool:
I clicked on ADB. Type adb shell, it gave me # root access inside Lead 3.
But on standalone, Lead 3 stayed as not rooted (default.prop ro.secure=0). Secure mode. Thank you to the Insecure forum: And the guy who explained clearly on one his article, just google 'android insecure mode' and ' Root any Android device - Whiteboard Web'.
- Last trial with Kingo Root: Root was successfull.
And I still don't understand ,,,,
- I checked Lead3, it's rooted. SuperSu, Xposed framework work Ok, and su in the terminaluf.
ps: The device manager shows android device with Alcatel ADB driver. and sometime Android ADB, depending on which tool I used.
NB:
I forgot to mention that during the rooting trial, with adb and terminal, I saw busybox was installed, at leat links in the filesystems I was able to mount -o remount, rw /system and / in order to change default.prop content (sed ,,,,). Strange isn't it ?
Baffled ,,,
But as curiosity is still here and pocket minded, I'll shop more of those phones.
Leagoo Lead 3 is really nice phone. As long long as I can control ...
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Eversmile23 said:
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Click to expand...
Click to collapse
reinstall super su from play store go to settings in super su app and unroot there
selinux enforced means that your kernel is not permissive. has nothing to do with root
I have a Blu life one x2 that I recently repaired a charger on, and rooted using a process I found here, but I don't remember which, I know I downloaded Kindle fire USB drivers with it though, anyhow, I managed to adb/fastboot root with twrp recovery. Now however now I use any app, exception bring super user, which requires root my phone crashes and reboots. I cannot install BusyBox due to this. I tried using es file manager to ensure RW but it only crashes too, and doesn't fix the crash. Note my phone admits it has root access via es and cpu-z ( the CPUid program made for Android instead of PC) I cannot find anything to help so I'm posting this with hope someone will know a fix,
Important to note the following about my device
Blu life one x2
Stock rooted rom
Twrp recovery Iso from adb root
Marshmallow 6.0.1
External 32gb SD formatted as internal
System folder according to BusyBox has 25mb free (cannot install to any of the folders due to crash)
Lucky patcher was the first app I tried and it crashes after granting root access, same with BusyBox as soon as it "checks the system" it crashes it.
Es "root explorer" Grant set RW (crash Android) reboot app main menu (crash Android)
Temp fix revoke ROOT to apps apps run fine (except lucky which now NEEEDS BusyBox)