Related
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.
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
smokin1337 said:
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
Click to expand...
Click to collapse
good looks bro.. worked perfect!!!!
evod3 said:
good looks bro.. worked perfect!!!!
Click to expand...
Click to collapse
Simply , you should have went to the official xda thread of super su by chain fire and should have flashed the zip. The zips removes the super user and replace it with super su
evo401 said:
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Click to expand...
Click to collapse
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Zeuszoos said:
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
Wrong! Now you cannot grant root access to any app since you don't have the binary.
If you do the 3rd step you will lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store and update the binary then remove the old superuser apk as smokin1337 said. Your steps are lengthy and will never work.
Or just flash the zip file.
Zeuszoos said:
Originally Posted by Zeuszoos
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work. Just make sure that it has Write access to the System partition. Even when in Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
mnomaanw said:
Wrong! Now you cannot grant root access
to any app since you don't have the binary. If you do the 3rd step you will
lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store
and update the binary then remove the old superuser apk as smokin1337 said.
Your steps are lengthy and will never work.
Click to expand...
Click to collapse
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Zeuszoos said:
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Click to expand...
Click to collapse
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
mnomaanw said:
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
Click to expand...
Click to collapse
No problem.
As for mounting it read/write, yes, that does need to be done. I should have included that. Thanks for noting it.
There is a utility that will mount your system partition as writable when you boot it up. It's called "mount r/w" or something like that. It's in the Google Play Market. I think it has an icon of a yellow folder with a lock, or something like that. Most people recommend against doing that and if you don't want to do it that way, as I'm sure you know, root explorer can mount it writable until you tell it not to, or reboot..
hi guys,
i have a wetab, and recently i installed windows 8 on it, and it works so good
since 2 days i liked to try and see how will android be on it but i dont want to format the windows 8
therefor i made an sd card bootable with android 4.0.3 installed on it, it the the project android-x86
in all cases all went well, but i realise that it have superuser.apk , and yes the rom is rooted, BUT
you cant grant access for root, what i mean is
i can open the root explorer, go to system/app delete what ever i want it work, but when i want to change permission
for example i cant it say i must gain root, i open superuser make the response always allow, but no clue, keep denying
everything...and what i saw also in system/app that all the apps permission is set to rwxrwxrwx and it is odexed rom
tried to update superuser...the same story never worked. tried to replace the su and busybox in system/xbin, and superuser.apk in system/app,
and su in system/bin with the latest versions....it didnt boot up lol the android is no longer detected.....and there is noway to go to recovery since it has not.....
so when there is root how i can edit or manage or gain root access ???
and by the way in terminal command
adb shell
root
i got this # so root is available
Lol....no one ?
Sent from my GT-N7100 using XDA Premium HD app
I rooted my strange tablet using Kingo and apparently it was succesful:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-20_zpsurdgzj8p.png
But I have been trying for days to erase a file in /system and I have not been able to do it, I think I have read every relevant thread about this problem but no luck, I tried using ES and changed /system to r/w in the root options but when trying to delete the file all I get is operation failed, the same happens with all the other root explorers and tools. I even tried the solution on this thread: http://forum.xda-developers.com/ascend-p7/help/edit-replace-write-files-set-immutable-t2884172
but still can't delete it.
Also the app root toolkit for android gives me this weird error too:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-06_zps4nrxqiev.png
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-02_zpsa1ycwdwl.png
Do you have an app like root explorer that specifically asks for root permissions? It doesn't matter if you have root if the explorer can't use it
Sent from my Nexus 5 using Tapatalk
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Try installing root explorer and then attempt to delete the file, then it should instantly open a window asking for root. The of course grant the permission. That should always work, but if it doesn't just restart the tablet, if it still doesn't work it must mean you are deleting a file that is in use by the system. Otherwise i have no idea whats wrong
Sent from my Nexus 5 using Tapatalk
Talos91 said:
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Click to expand...
Click to collapse
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
JMink said:
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Rooted my device using kingo root, I didn't intall other recovery.
Bad idea to try and remove system files without a custom recovery and a nandroid backup made and stored in a safe spot. What are you trying to remove?
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Talos91 said:
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Click to expand...
Click to collapse
That is the binary. If you remove it, you wouldn't be rooted. Can you link the thread you are looking at? There's an app made specifically for replacing that su binary with SuperSU and it's binary called Super-SUme, though I believe it is a paid app.
I know it is the binary but according to this guy:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365/page23
(post 223)
""It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.
The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.
$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.
Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency"""
If you rename it, it won't be able to run, and won't require removal.
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Talos91 said:
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Click to expand...
Click to collapse
Seems like the SU binary that Kingroot included is pretty finicky and only works for some things. I've rooted 100s of devices and have never had issues like that. Have seen complaints about other various oddities with Kingroot too. It's nice that it's easy and works on a variety of devices, but if you have only limited control then that kind of defeats part of the purpose of rooting it...
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
With Root Explorer, does it let you set the system to R/W? There's a little button at the top of the app that will say R/O or R/W for Read Only or Read Write. If you don't have R/W to the system, then you are unable to make changes to it.
I just renamed file su and then it became able to be deleted.
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
Connect your android tablet device to your windows computer. Then enable usb debugging on your android tablet. Then open the windows program called cmd. Then do these commands.
Code:
adb root
Code:
adb remount
Code:
adb shell rm /system/sbin/su
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).