Related
DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !
Hi,
I'm rooted yet cannot mount system folders as r/w. I am definitely rooted (confirmed by using su command in terminal and the fact apps that require root are working) and noticed this issue when trying to install busybox pro.
It warned me that there was an existing busybox in /sbin and would remove it before trying to install in system/xbin but the installation failed.
I tried to remove busybox from /sbin but the folder would not mount as r/w in root explorer OR solid explorer.
I managed to remove the file in TWRP recovery though.
Weirdly, I've been using titanium backup to uninstall system apps without any issues.
How can I fix this? Repair permissions int wrp?
I presume you followed the same instructions as I. I am on the 621 and currently have the same issue (also rooted). But on my end it is actually worse. I cannot mount the system partition in TWRP either (I mean I can mount it but when I try to delete or move a file I get error messages), and something happened to my download manager (which basically means that for the time being I cannot download apps from Google Play or from the internet, etc). I have a good download manager apk, but when I try to install it it asks me if I want to update the existing app, and the operation fails - I have to try and find a 3rd party alternative for the time being). It is kind of a problem.
(to update, I have very limited r/w permissions in TWRP. If I get lucky I can make small changes.)
WastedJoker said:
How can I fix this? Repair permissions int wrp?
Click to expand...
Click to collapse
I don't think so. I tried this, and I eventually was able to view/attempt to edit file permissions inside of X-plore file explorer (don't know if it is a coincidence, but I first had that success opening X-plore in 'mount system r/w' mode after changing the i/o scheduler to cfq). Anyways, it consistently shows all 755/644 permissions, so the permissions are not being re-written upon boot from what I can gather. But if I try to edit permissions or copy files to System folders, I still got error messages to the effect of "you cannot do this,' even though it is a root file explorer and the system partition is purportedly mounted as r/w.
Try flashing this in recovery: SonyRICDefeat by dosomder.
CubicU07 said:
Try flashing this in recovery: SonyRICDefeat by dosomder.
Click to expand...
Click to collapse
Thank you for this. Has anyone ever tried this on the Z3TC? Mine is running smoothly enough such that I am reluctant to fix what isn't broken. It seems that early issues I had with freezes, TWRP, etc, probably had to do with my SD card and the Android media scanner.
I've tried it on the Z3TC SGP621. Thus the recommendation.
CubicU07 said:
Try flashing this in recovery: SonyRICDefeat by dosomder.
Click to expand...
Click to collapse
I have the exact issue in lollipop and I have tried flashing RICDefeat and I get errors.
Sorry for the Hijack :/
Use my RICDefeat from here and run it from terminal. Works only if you are rooted. Afterwards you should have r/w access.
lowtraxx said:
Use my RICDefeat from here and run it from terminal. Works only if you are rooted. Afterwards you should have r/w access.
Click to expand...
Click to collapse
Do you thing that your zip can be used on a Z1C?
Envoyé de mon D5503 en utilisant Tapatalk
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, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
icy201 said:
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
Click to expand...
Click to collapse
download root checker from the play store and make sure that u have root access on your device
messi2050 said:
download root checker from the play store and make sure that u have root access on your device
Click to expand...
Click to collapse
It says i have properly installed root access. Something fishy is going on with my root and my system.
icy201 said:
It says i have properly installed root access. Something fishy is going on with my root and my system.
Click to expand...
Click to collapse
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
messi2050 said:
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
Click to expand...
Click to collapse
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
icy201 said:
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
Click to expand...
Click to collapse
Your device does not have twrp/cwm port ?
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
These are the only possible solutions ive been able to find that do kinda make sense.
"It's because you need a boot.img with r.o secure=0 in the build prop" i went and looked and my file says r.o secure=1 that would explain why my system will not mount as r/w.
Another post i found said -
"I've found the source of the problem asking in the MIUI forums, the boot image will not accept a modified /system.
You have to use the adb interface: adb devices then adb disable-verity.
Disclaimer: I'm not responsible for any damage caused by these operations."
The second solution seems more reasonable and alot easier to do. My question now is: will one or both of these solutions possibly fix both my problems? And the second solution disabling verify should that be okay to do without messing up my device? I do have that recovery i could flash but dont wanna do anything that might make the phone not boot into recovery.
icy201 said:
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
Click to expand...
Click to collapse
Yes that's normal , your problem is because of a buggy root
messi2050 said:
Yes that's normal , your problem is because of a buggy root
Click to expand...
Click to collapse
I just remembered something. I think i know what bugged it. I was trying to do an ota update for my device and it wouldnt let me. I found another app by chainfire called flashfire. I tried to flash the ota update and i had the option "inject supersu" enabled even though i already had supersu installed and everything else i needed for root. I guess doing that messed up all my su files ect.. But how do i fix it? I cant uninstall root cause my /system folder is locked into r/o. If i press full unroot in supersu it will remove the app (although it takes a while!) but all the files needed for root stay.
Guess there just no fixing this phone. Someone really hacked it good i guess, problem is still there and nothing can fix it...
Update - thread can be closed
Problem fixed, to fix the problems i was having i had to download the stock system files for my device and flash them, after that just installed the latest supersu 2.78 zip and remount problem is fixed.
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).