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 ...
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.
Hi,
I've been trying to root my Argos Bush MyTablet 10.1" running Android 4.4.4 for a while now, but all the rooting methods I have tried didn't work.
Framaroot (The exploit didn't work)
Key Root Master (I don't understand, since it's Indonesian, but some kind of error popped up.)
Root Master (Failed to root.)
iRoot (Failed to root.)
TowelRoot (device not supported. I tried using different modstrings, but they all turned my screen gray and rebooted my device.)
I have no access to a computer.
Argos ac101bu
Hi,
Really struggling to root this tablet. I have spent around 4 days trying.
I first altered the boot.img and set it up for adb.
ro secure = 0
allowmock location = 1
constant usb device = adb
ro debuggable = 1
This stops the "cant use adb root on production builds".
However, when I do adb root, it just says restarting adb as root.
It disconnects and then adb cant see the device, I have checked the drivers and its still there.
The device changes to "class for rk device", I tried lots of different drivers, but nothing seems to work after using "adb root".
I then also altered the system.img and made these changes.
ro factory location = 2 <-- which should use external SD (also added media,rw to permissions).
ro rkadb root = 1
ro secure = 0
I also manually installed SuperSU and set all the correct permssions. chown 0.0 and 06755 (in both xbin and bin).
SU works but SuperSU apk cant see the SU binary for some reason and doesnt show grant permission option. So its bassically useless.
Very frustrating, can anyone help?
EDIT:-
Got it rooted now, adb root still wont work. However I managed to manually root by following SuperSU v1.93 update script. Had to mount system.img in linux and edit that way.
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
tron1275 said:
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
Click to expand...
Click to collapse
Sorry for not answering sooner. I have the custom system image, if you still need it.
Its around 1.6gb, you have to flash it via rockchip flash tools. I also tweaked it some more and added init.d support.
I had rooted Celkon Q 500 with some method, I do not remember exactly. May be Root Genius. For some reason I unrooted using SuperSu. I wanted to re-root. But I am finding it difficult. ( I have not got any OTA update after rooting)One root checker says it is rooted, another says it is not. I can explore files in root explorer of ROM Tool Box Pro I had installed earlier. But I can not reboot through ROM Tool Box Pro. One root checker provided me this information : subinary available via $PATH null null, then in the next line it says : -rwsr -sr -x root root, subinary location is system/bin/su. Second thing it says : I have installed two busybox one at (a) data/local/busybox and another at /system/xbin/busybox. I had tried to un-install and re-install SuperSu and Busybox 2/3 times. Then after opening Supersu I got an erratic message : su binary needs updating and when Itried to update it , it failed several times. One root checker app says ADB root is available, Root Genius says root available. So, I am quite confused. I do not know how to go about it. I will be thankful, if somebody guides me in right direction.:crying: (I also found a root checker app said SELinux enforcing.)
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
Like everyone else, I picked this Azpen A743 up at Microcenter for $20. It was advertised as having 5.1, but came with 6.0.1. I bought it to stream music from my Asus router with samba share drive. Other than that, just plan to use Google News, weather app, and light web browsing. Tried a couple rooting methods but no luck. Reluctantly tried Kingo Root, but it never finished the process. (I've read these devices come preloaded with malware, so some more from kingo root won't hurt). From what I've read and searched, there isn't any custom recovery for this tablet. Anyone know how to root it? I did manage from stock recovery to sideload SuperUser.apk, but it doesn't work.
I have USB debugging on, and bootloader unlocked.
Specs are: Allwinner 1.3 GHz A33 4core
The recovery lists the tablet as:
A33_86v/astar_xr819/astar-xr819
6.0.1/MOB30R/20171221
and firmware version v6.0rc3 (I have found references to OxygenOS for that FW version)
If there is not a root method, is there a way to alter/replace the hosts file? I would like to transfer the hosts file from my phone generated by adaway. I have copied my phone's hosts file and tried:
adb reboot download - reboots to OS, doen't seem to have a download mode, but it would almost have to in order to update the FW
adb reboot bootloader - boots to Azpen screen buring bootup, but just hangs
adb push - system read only
adb shell - cp hosts (read only)
adb shell, then su - SuperUser pops up saying ADB need SU access, grant it but nothing happens. can type, but nothing happens.
from recovery, if I mount /system, then device no longer detected by adb.
Didn't try any fastboot commands, scared of losing data, and I don't see anyway to back up the current FW
Also tried the Phoneixsuit software to install apks, but it didn't work
created my own update.zip - 255 error (or not verified even when using various methods to sign the .zip file-Sign-em, Auto-Sign)
Is there a way to create a .zip or apk that is signed that will copy the hosts file to /etc/hosts?
Any advice or guidance would be appreciated.
Have you had any luck since posting this? I'm trying to root the same device, but no luck so far.
Nope. Somehow managed to push Superuser to it, but still not rooted. SU app pops up asking for SU if "adb shell SU", can grant permission, but still nothing. Can't make permission changes to RW. I finally got fed up and tried flashing the wrong firmware to it, but even that wouldn't work. PhoenixSuit, PhoenixProUSB, PhoenixCard would not work to flash different firmware... and no response from Azpen about lollipop firmware or any firmware for that matter. Won't return emails or answer the phone.
I don't know if by pulling the /system folder ,making changes, then using a tool like Dragonface to build a prerooted image would work or not. Can't really do anything without the right firmware for the device.... and I'm not counting on that happening.
This is a good place for info on A33 info and tools:
http://forum.gsmhosting.com/vbb/f906/
I finally got widgets to update after a month of tinkering.... everyday it tells me the SD card is corrupt... other than all of the above, it is a decent little tablet for the $20.