I have TWRP install on my device, and I tried installing Magisk and SuperSU to root it, but neither would install. I don't want to say what my device is because I don't want answers based on my device. I've heard that rooting is all about getting a SU file into a root directory, and I want to try that before getting any other help with rooting my device.
TWRP has a root file explorer I can use to move files into root directories (I also tested it by moving one file into /system, restarting my phone into Android, then restarting it back to TWRP, with the file still being there), I guess the file wasn't being interfered with and stayed where and the way it was. To root my device, what files do I have to place in what root directories?
YousufSSyed said:
I have TWRP install on my device, and I tried installing Magisk and SuperSU to root it, but neither would install. I don't want to say what my device is because I don't want answers based on my device. I've heard that rooting is all about getting a SU file into a root directory, and I want to try that before getting any other help with rooting my device.
TWRP has a root file explorer I can use to move files into root directories (I also tested it by moving one file into /system, restarting my phone into Android, then restarting it back to TWRP, with the file still being there), I guess the file wasn't being interfered with and stayed where and the way it was. To root my device, what files do I have to place in what root directories?
Click to expand...
Click to collapse
Bro the newest root methods patch the boot img of your phone placing files for root is deprecated and if magisk isn't patching your boot img on your device the issue is not with magisk a screenshot of what twrp shows when you try to flash magisk would help out and why would u want supersu its deprecated
([emoji3590]09-09-18[emoji813])
YousufSSyed said:
.. I don't want to say what my device is because I don't want answers based on my device...
Click to expand...
Click to collapse
Because Samsung, Google, Motorola and the other manufacturers do things differently, the steps for rooting will vary from one device to another.
Sent from my Rockchip RK3288 Chromebook using XDA Labs
I should've mentioned that I don't have much experience with tampering android (if I didn't make that clear with my lack of knowledge). I didn't know supersu is deprecated, I'm trying to root my Galaxy S8 950U on Pie, and yes I've heard it's extremely difficult / impossible although I did manage to get TWRP on it. Is there a way to root my device with the TWRP explorer, if possible?
YousufSSyed said:
I should've mentioned that I don't have much experience with tampering android (if I didn't make that clear with my lack of knowledge). I didn't know supersu is deprecated, I'm trying to root my Galaxy S8 950U on Pie, and yes I've heard it's extremely difficult / impossible although I did manage to get TWRP on it. Is there a way to root my device with the TWRP explorer, if possible?
Click to expand...
Click to collapse
Edit:
Looks like your best option is to follow
https://www.google.com/amp/s/forum....msung-galaxy-s8-root-snapdragon-t3659305/amp/
Sent from my PH-1 using XDA Labs
---------- Post added at 01:58 AM ---------- Previous post was at 01:40 AM ----------
The complexity of the previous root method suggests to me that you not going to find an easy solution.
I think you should start a thread in the
https://www.google.com/amp/s/forum.xda-developers.com/galaxy-s8/help
Describe how you got TWRP, or share link to instructions you followed.
Then perhaps others S8 owners can help with the next steps.
Sent from my PH-1 using XDA Labs
Related
Hi everybody. I learned so much from this forum (and also from others) in one year and tried to share my knowledge to those who try to learn like me.
Now i would like to share one of my experiences. i dont know if someone wrote about this, yet i could not find anywhere in this forum. When we share a "port" for example "s4 keyboard for s3", we say that we need root access in order to use this port. But when i think, if this apk files replace themselves with the original ones and rom thinks that they are the originals, why should we need root access? Of course we need recovery to flash them but do we absolutely need root? And i flashed 3 separate ports (keyboard, launcher and callrecord) into a fresh installed 4.3 MK6 stock rom without root and they worked... and still do... (scripts have to delete odex files automatically)
Installing a recovery will increase the binary counter and since your binary is up why not rooting right? But those who dont want to root their phone but still want to use the visuality, can install a recovery and flash the ports without rooting... Tested and proven...
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
alex.sg said:
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
Click to expand...
Click to collapse
If editing apps from rom then yes. But if you are flashing them through recovery you dont need root access for read and write permitions. Script also does that itself. Thats what im talking about
Galaxy S3 tapatalk 2 ile
Before you read this trough : This is not a question about how to root my phone or add root access to an app. This is about how I can add root acess to my phone. I mean like ading root acess to a phone where no root is yet released. If anyone knows a github repo with the commits of adding root to the phone, please tell me. Thanks!
CTXz said:
Before you read this trough : This is not a question about how to root my phone or add root access to an app. This is about how I can add root acess to my phone. I mean like ading root acess to a phone where no root is yet released. If anyone knows a github repo with the commits of adding root to the phone, please tell me. Thanks!
Click to expand...
Click to collapse
you don't want to root device (for example: kingo root, Iroot, etc) u want to compile su file or what??
Paget96 said:
you don't want to root device (for example: kingo root, Iroot, etc) u want to compile su file or what??
Click to expand...
Click to collapse
I currently don't look to compile for a specific device but I want it as basic knowledge when it comes to the case of a new device that has no root yet.
CTXz said:
Before you read this trough : This is not a question about how to root my phone or add root access to an app. This is about how I can add root acess to my phone. I mean like ading root acess to a phone where no root is yet released. If anyone knows a github repo with the commits of adding root to the phone, please tell me. Thanks!
Click to expand...
Click to collapse
"How I can add root access to my phone" = root your phone? There's not much difference between the two sentences. Unless you mean adding the root path to the device without installing SuperSU or any other SU app?
popthosegaskets said:
"How I can add root access to my phone" = root your phone? There's not much difference between the two sentences. Unless you mean adding the root path to the device without installing SuperSU or any other SU app?
Click to expand...
Click to collapse
Look. You have a phone that doesn't have root access. So what I would do is go to xda, find a root IMG to flash on my phone and then flash it. That would give me root access to the phone. The thing is, if there is no flashable IMG I would develop one by myself. Now I can't find any tutorials or sources of how to build a image like that.
Sent from my SM-G800F using XDA Free mobile app
1. Such methods would depend on your phone, not all phones go through .img file flash.
2. Usually I would associate .img files as kernel. So I assume you want to flash a custom kernel?
3. If you indeed want to flash a custom kernel, you still need root on the ROM before the custom kernel can have root access.
CTXz said:
Look. You have a phone that doesn't have root access. So what I would do is go to xda, find a root IMG to flash on my phone and then flash it. That would give me root access to the phone. The thing is, if there is no flashable IMG I would develop one by myself. Now I can't find any tutorials or sources of how to build a image like that.
Sent from my SM-G800F using XDA Free mobile app
Click to expand...
Click to collapse
There are several steps to go about to developing a rooting procedure for a device when none has been released yet. The first key step would be to identify whether the device has a looked bootloader. If it does then you will need to resort to an exploit to gain root access rather then flashing a pre-rooted boot.img for example unless you can figure you a way of bypassing the img signature check which in many cases using an exploit is easier. A good basic place to start looking for exploits is here. You will then have to do research on how to exploit the security flaw which involves knowledge of Assembly, C, and Linux. If the bootloader is unlocked you can attempt to make a superboot or autoroot type boot.img which I would suggest taking an existing .img of those types and disasembling them to learn how they were created. Let me know if you still have any questions.
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
Hello,
So my my root explorer is not working
I tried both root methods with magisk the boot.img and the twrp method currently rooted with the boot.img method and I've also tried reinstalling the miui ROM still didn't work
So if anyone can help.
Thank you!
I'll provide some screenshots
Walther6 said:
Hello,
So my my root explorer is not working
I tried both root methods with magisk the boot.img and the twrp method currently rooted with the boot.img method and I've also tried reinstalling the miui ROM still didn't work
So if anyone can help.
Thank you!
I'll provide some screenshots
Click to expand...
Click to collapse
The system partition is read only from Android 10 and above. You can no longer modify system files from a root explorer. There may be already a solution somewhere but idk where...
Oh, that's unfortunate I'll just try to find a solution it's obviously not a life to death situation I'm just trying to change my boot animation
Raiz said:
The system partition is read only from Android 10 and above. You can no longer modify system files from a root explorer. There may be already a solution somewhere but idk where...
Click to expand...
Click to collapse
Well think I found an solution.
Some guy on discord helped me out by using some script I'll link the post
https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/
Solid Explorer is still working fine with Android 12. Majority of other Root Explorer apps no longer work, which used to work fine with earlier Android versions. I would advise to try Solid Explorer app.
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).