im rooting a friends tbolt, it meets all the requirements, but i dont get root access, busybox installed but no root. any ideas? SU is in the app list but it doesnt work. this process worked flawlessy on my tbolt. and all matched up, and compatible version
T41NT204 said:
im rooting a friends tbolt, it meets all the requirements, but i dont get root access, busybox installed but no root. any ideas? SU is in the app list but it doesnt work. this process worked flawlessy on my tbolt. and all matched up, and compatible version
Click to expand...
Click to collapse
SU is in the app list, as in the App Drawer? You mean SuperUser if that's what you're talking about. SuperUser is the GUI interface to the actual su binary.
The su binary (which should be located in /system/bin on the phone) is the actual file that grants root access rights. Can you confirm that that file has actually been installed and what its permissions are?
Will the SuperUser app let you download/update su? Also, you should be able to install it from CWM under the extras menu if I recall correctly.
My phone's not handy to confirm above, I'm doing by memory, which isn't so great these days, but hopefully this will give you some ideas of what's wrong.
distortedloop said:
SU is in the app list, as in the App Drawer? You mean SuperUser if that's what you're talking about. SuperUser is the GUI interface to the actual su binary.
The su binary (which should be located in /system/bin on the phone) is the actual file that grants root access rights. Can you confirm that that file has actually been installed and what its permissions are?
Will the SuperUser app let you download/update su? Also, you should be able to install it from CWM under the extras menu if I recall correctly.
My phone's not handy to confirm above, I'm doing by memory, which isn't so great these days, but hopefully this will give you some ideas of what's wrong.
Click to expand...
Click to collapse
i cant atm i dont have his phone. SU (superuser) is in the list, and it told me it was up-to-date when i tried updating it.
CWM? thats new to me atm
root checker sees busybox, but reports not rooted.
i have rooted my mobile using this tut forum.xda-developers.com/showthread.php?t=1196808.
and it was successful but few apps like system app remover and linux installer is displaying root not found error!
what should i do to provide root access 4 these apps?
even in Better terminal , if ask for superuser permission the access is denied
Just Try 2 Help..
..Base on TuT "http://forum.xda-developers.com/showthread.php?t=1196808"..
Make sure you've Flash It Correctly First..then Check in about phone the BB version now is 2.1.71..? Then Check if SU already Installed in your phone..
If the SU not yet installed..try again for "Instaling X-Recovery" Step..
aah..try to install a new version Busybox..
I've No Problem after Rooting for Better Terminal, System App Remover and other RooT Apk..
recently bought was what supposed to be new lg g2. discovered it was rooted. have no need for root access at this time. is SuperSU the easiest way to "unroot"? it's already an installed app. thanks
*bump*
I don't know what is the right way. Maybe other people will help you.
mhale14 said:
recently bought was what supposed to be new lg g2. discovered it was rooted. have no need for root access at this time. is SuperSU the easiest way to "unroot"? it's already an installed app. thanks
Click to expand...
Click to collapse
SuperSU app isn't what grants you and/or apps superuser ( aka root ) rights: it's an app that stores in a database the apps you have granted root thus you don't get prompted everytime, It's the Android executable named su.
You at any time can uninstall both. The su binary typically is located in folder /system/xbin and/or folder /system/bin
Hello, sorry for my bad english. My phone is rooted and has TWRP installed. I am using Smali patcher. Masick and twrp installed the latest version. Secure folder version is 1.2.32.1. I cant update it. I couldn't delete it with root file managers. The updated apk file is not installed because I cannot delete it. After doing the patch, I open the secure folder and it does not open for a long time and gives an error. Es file manager root partition does not work because shortly after granting root it says "root permission could not be obtained, function temporarily unavailable." busybox and root browser work fine. Where did I go wrong, what should I do?
Hi everyone. I'm trying to root my Alcatel 1T 7 8067, by using TWRP 3.2.1 and zip SuperSu images, but rooting was unsuccessful.
The last successful root that I got with that method, was on a marshmallow android device (a CATS60), with no issues; but on my recent device (with oreo go), when I try to install supersu by TWRP option "install", it begins to install, and the process log shows apparently an error: "Patching Sepolicy -----Failure, aborting", and when I reboot to system, there is no root access.
As result of those failed attempts, I have tried by installing old versions of supersu with apparent success, but then, when I try to boot the device, it enters into a bootloop.
So I think, that unsuccessful rooting is related to that Sepolicy error ¿Am I right?
I've noticed that there's no SU folder inside /system folder, so, as I understand, it means supersu wasn't installed (I can see that by using the TWRP's file explorer).
So ¿What can I do with that issue?
I've read that Magisk can solve this problem. Following tutorials about, I tried by flashing a magisk patched boot image, but supersu installation issue still continues.
I must say, that I prefer supersu over magisk, because is more familiar to me, but in general what I need, is a system root, a real root access; not a systemless root; and based on my experience, I only can get that with supersu.
@Camilo Gil I don't really understand your point "real root access".
On my Magisk rooted devices I can access any system file and even change it externally and write it back into system.
I used SU previously but as further development has stopped I had to switch anyway.
superSU? do you live in 2010? get rid of that old stuff and use magisk, SupeSu is totally useless in android 7+
bmwdroid said:
@Camilo Gil I don't really understand your point "real root access".
On my Magisk rooted devices I can access any system file and even change it externally and write it back into system.
I used SU previously but as further development has stopped I had to switch anyway.
Click to expand...
Click to collapse
By real root access, I want to mean, that SU binaries are installed on /system folder. As I understand, if that requirement is given, all apps that need root access, can fully work, without any limitations. Recently, I tested magisk, supposedly my device already had root access. Then I installed ES file explorer to give it root access, and it was granted on magisk but root access couldn't be activated in the app. That never happened me before.
As I understand, that's because ES file explorer couldn't find SU binaries, because magisk root method is systemless root.
I hope I would explain myself right.
tutibreaker said:
superSU? do you live in 2010? get rid of that old stuff and use magisk, SupeSu is totally useless in android 7+
Click to expand...
Click to collapse
¡More o less! I live in 2018, or at least that was the last date when I rooted a device (CAT S60, android 6.0). I don't trust on Magisk, just because I couldn't give root access to ES file explorer. That never happened me before. And I know there are many more file explorers; I know that Es file explorer is kinda deprecated, and root explorer works fine; but I want a root access on which any app that needs root access, and that I want to install obviously, can work without any limitation. My firsts impressions of magisk root is that it cannot provide that service.
Now, what you say that supersu is useless, it's worrying to me, because I can't see any other alternative for root access.
¿Why do you say it's useless?
Camilo Gil said:
¡.... I want a root access on which any app that needs root access, and that I want to install obviously, can work without any limitation. My firsts impressions of magisk root is that it cannot provide that service......
Click to expand...
Click to collapse
Yes it can but in a different way.
You're asked once to grant root privileges for each app that needs it and if you let it have root that's it.
Or you grant root temporarily and will be asked every time for this app.
Apps that don't need it don't get it.
You can change your decision afterwards as well.
Btw I use Total Commander with LAN plugin to access my NAS.
bmwdroid said:
Yes it can but in a different way.
You're asked once to grant root privileges for each app that needs it and if you let it have root that's it.
Or you grant root temporarily and will be asked every time for this app.
Apps that don't need it don't get it.
You can change your decision afterwards as well.
Btw I use Total Commander with LAN plugin to access my NAS.
Click to expand...
Click to collapse
With magisk, I grant root access to ES file explorer, but I can't enable it on the app. As I read, that's because ES File Explorer can't find SU folder in system folder (which actually happens on system root), and because of that, some apps like es file explorer, won't detect systemless root or better, to them, systemless root is detected as non root access.
I read that even supersu must be installed as systemless root, because if installed as system root (or what I refer as "real root") on android 7+, causes bootloops. On my particular case, system root causes an endless boot. As I understand, that happens because supersu can't set /system folder to R/W, on android 7+.
On the other hand, I know there are several alternatives to ES file explorer, for instance Root Explorer, Total Commander, etc. But it's just I'm accustomed to it. But also I read that systemless root not only can cause issues with ES File explorer, but also with Viper4android and some other Xposed modules.
PS 1: We should suggest to google, that release an official rooted android version, specially addressed for us, the medium skilled and advanced android users (that normally we like to root android and get the most of it).
PS 2: So finally ¿is there any way to have a working system root access in oreo, or systemless root is the only option?
Camilo Gil said:
... because if installed as system root (or what I refer as "real root") on android 7+, causes bootloops.
Click to expand...
Click to collapse
I can't remember on which LOS version or when I used it the last time before switching to Magisk.
Camilo Gil said:
On my particular case, system root causes an endless boot. As I understand, that happens because supersu can't set /system folder to R/W, on android 7+.
Click to expand...
Click to collapse
Idk
Camilo Gil said:
On the other hand, I know there are several alternatives to ES file explorer,
Click to expand...
Click to collapse
There seem to be several with that name so just tell me it's full correct name and I will install it on my Magisk rooted LOS14.1=Nougat tablet and see if I get problems with it.
Camilo Gil said:
... Viper4android and some other Xposed modules.
Click to expand...
Click to collapse
don't use them so can't tell
Camilo Gil said:
PS 1: We should suggest to google, that release an official rooted android version, specially addressed for us, the medium skilled and advanced android users (that normally we like to root android and get the most of it).....
Click to expand...
Click to collapse
afaik the pure Vanilla is the base from which most custom ROMs are built by the devs and imo most ROMs you can get are not rooted as it's of course a safety hazard.
bmwdroid said:
afaik the pure Vanilla is the base from which most custom ROMs are built by the devs and imo most ROMs you can get are not rooted as it's of course a safety hazard.
Click to expand...
Click to collapse
I know a rooted android is a security and stability hazard of the device. But evidently who wants to root his/her device, is fully warned about its potential consequences. So google could publish a prerooted version, previously warning about its use, warning that its use is exclusively under user responsability, and maybe disclaiming liability for damages. I guess there's no problem if users of that (at the current moment) imaginary OS , are aware of the risk that they are taking by using it. At least, I would use it if could (and as it doesn't exist, it's because I'm trying to root my current one).