Related
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Nice one, added to Index.
@op, Good job.
Although my tutorial was word by word the same, apart from maybe few spelling mistakes. ;p
Above is required for Stock Rom which is rooted.
On custom and rooted Rom , you don't need to perform above steps as system is write permitted so running ad away normally works fine.
Regards
Yasir
Sent from my HTC Desire X
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
nightcrow said:
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
Click to expand...
Click to collapse
This symlink method(not mine) is present in ad away FAQs. So credit to the app team.
Sent from my HTC Desire X
Nice guide, first time I'm adfree, even after a reboot
did anyone get it working on desire x... mine still shows ads in apps...
I don't know, after all I'm an amateur, but the problem nightcrow described about how stuff goes back to stock after a reboot is something that happens a lot with the DX's - same thing with the bloatware. I had to remove the bloat apps from a rom.zip and flash that to avoid the problem. Seems to me there is some kind of security built in that goes beyond the norm. Otherwise I don't see why apps like Titanium work to remove apps (even after reboot) for example on most other phones, but not the DX.
Meherzad, I followed the instructions posted by nightcrow and it works for me ... try again, reboot and open an app you know normally has ads to check if it works.
Failed first time (forgot to uncheck fast boot:banghead. Reinstalled and did everything again, now works flawlesly.
ok.. working great......
nightcrow said:
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Click to expand...
Click to collapse
have no idea how to write in command prompt
umo4u said:
have no idea how to write in command prompt
Click to expand...
Click to collapse
Windows button+R>Type cmd>enter
It doesn´t works for me...It may wont work because i have superuser v3.2?
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
you can do same in advanced-> execute command (or maybe shell - do not remember the exact naming)
adb was not working for me, too.
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
Why do you need ADB when you have TERMINAL in twrp. Just wondering
Anyhow, ADB will be fixed soon
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
michpan said:
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
Click to expand...
Click to collapse
I think you can turn it on.
If you'll not access recovery... when you need recovery, turn fast boot off...
Sent from my hTC branded muffin
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.
Guys,
I made a post a couple of days ago over on the 5x forums: http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659. With this permissions fix I have Android Pay working without having to enable/disable root in the SuperUser app. Hoping it will work on 6p as well.
Anyone willing to give this a try on the 6p? You would need a stock ROM (or possibly another ROM that previously worked prior to Google's recent change that broke it) with systemless root installed (I'm using 2.67). Basically all you need to do is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
So far this has worked for me and a couple of others on the 5x (both adding cards and making purchases). Let me know if anyone can confirm that this works on the 6p.
jgummeson said:
Guys,
I made a post a couple of days ago over on the 5x forums: http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659. With this permissions fix I have Android Pay working without having to enable/disable root in the SuperUser app. Hoping it will work on 6p as well.
Anyone willing to give this a try on the 6p? You would need a stock ROM (or possibly another ROM that previously worked prior to Google's recent change that broke it) with systemless root installed (I'm using 2.67). Basically all you need to do is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
So far this has worked for me and a couple of others on the 5x (both adding cards and making purchases). Let me know if anyone can confirm that this works on the 6p.
Click to expand...
Click to collapse
I just did it with Root Explorer. I changed the permissions for the /su/bin folder to 751. SafetyNet checks are passing now, but I haven't actually tried to purchase anything.
Worked on pure nexus after setting the permissions as suggested.
yep, purenexus, systemless, updated via terminal emu, works fine as of right now.
Worked with Chroma Rom using Root Explorer to change permissions. SafetyNet checks pass. Haven't set up AP yet . Will try that tomorrow.
Worked for me. Was able to pay for groceries.
Not working for me, used skipsoft toolkit to install systemless root.
Edit: Figured it out, still had the xbin_bind folder. Made a zip backup of it and deleted the original, safetynet passes now.
I've been on Pure Nexus 1/09 build with systemless SuperSU 1.61. Never had Android Pay working.
Without doing a clean install,
flashed busybox in TWRP.
Reboot
Made the permission changes using Root Browser.
Reboot
SafetyNet passes.
Installed Android Pay, added card.
Used on soda machine.
PROFIT!!!
Thank you OP for find!
Sent from my Nexus 6P using Tapatalk
i called google and they said it might actually be a syncing issue and that removing the card completely from your account (login web browser and account settings then remove card).
Se7eN43 said:
I've been on Pure Nexus 1/09 build with systemless SuperSU 1.61. Never had Android Pay working.
Without doing a clean install,
flashed busybox in TWRP.
Reboot
Made the permission changes using Root Browser.
SafetyNet passes.
Installed Android Pay, added card.
Used on soda machine.
PROFIT!!!
Thank you OP for find!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I disabled SuperSU and followed directions. AP accepted my credit card and is set up. Do I leave SuperSU disabled, or can I re-enable?
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
allen099 said:
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
Click to expand...
Click to collapse
Did you delete the /su/xbin_bind folder?
synnyster said:
Did you delete the /su/xbin_bind folder?
Click to expand...
Click to collapse
I did not. I must have missed that step.
EDIT: When I do that, root is no longer detected. The SafetyNet turned green, but Titanium Backup said no root. Sorry, and thanks for the assistance. Any other suggestions?
Are you sure you have systemless root?
100%. I just reinstalled 2.67 via TWRP. I've got it back now. What would you recommend I do? chmod 751 /su/bin/ and remove the xbin_bind folder again? I'm reading on reddit about moving it and symlinking. How were you able to successfully do it? Thanks again!
The contents of xbin_bind are: dexdump, su, wlutil
If deleting that folder also deletes su, then it makes sense as to why root is gone.
allen099 said:
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
Click to expand...
Click to collapse
allen099 said:
100%. I just reinstalled 2.67 via TWRP. I've got it back now. What would you recommend I do? chmod 751 /su/bin/ and remove the xbin_bind folder again? I'm reading on reddit about moving it and symlinking. How were you able to successfully do it? Thanks again!
The contents of xbin_bind are: dexdump, su, wlutil
If deleting that folder also deletes su, then it makes sense as to why root is gone.
Click to expand...
Click to collapse
I'm systemless root with SuperSU 2.66. I deleted xbin_binds after I was rooted. All I did was chmod 751 (I did the same thing via ES File Explorer) and AP works for me.
synnyster said:
I'm systemless root with SuperSU 2.66. I deleted xbin_binds after I was rooted. All I did was chmod 751 (I did the same thing via ES File Explorer) and AP works for me.
Click to expand...
Click to collapse
I'll try again now. Using root explorer. Did you set all files inside of /su/bin to 751? Or just the folder itself.
EDIT: It worked this time! Thanks very much!!
allen099 said:
I'll try again now. Using root explorer. Did you set all files inside of /su/bin to 751? Or just the folder itself.
EDIT: It worked this time! Thanks very much!!
Click to expand...
Click to collapse
Woohoo!
Wow this is amazing. I just made my first android pay purchase on a vending machine. Thanks for finding this method!
Just wish google won't take it from us again though.
For those who are confused, here are my steps for using Android Pay while rooted.
1. I reset my phone to factory defaults by installing all original software.
2. Unlocked the boot loader.
3. Installed TWRP, but kept it read only.
4. Installed Beta Super User 2.67
5. Through Android terminal after entering su and allowing terminal emulator root access:
6. rm -r /su/xbin_bind
7. chmod 751 /su/bin
Android Pay works, root is still active. Thanks all.
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this mod at your own risk there is no warranty or guarantee.
It's a part of google so you can unlock your phone like if your at home it will keep the phone unlocked. This script will disable lock screen service administrator account on boot. The script runs on boot and then exits out of memory. Taking up no cpu power or ram in the background.
I have updated the Magisk Module to work with Magisk 20.4 or higher.
How to install?
Flash in Magisk.
Requirements:
Root
Magisk v20.4 or higher
Delete manual install before installing the Magisk Module "/data/adb/service.d/disablescreenlockservice.sh"
Manual Install, unzip and take the service.sh file and rename it and copy it to "/data/adb/service.d/" and change file permissions to 0755 reboot.
You may not need root, you can just enter the adb command.
adb shell pm disable com.google.android.gms/com.google.android.gms.auth.managed.admin.DeviceAdminReceiver
updated magisk script
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).