Database Develop

adaway installation on official rom

Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.

revery0 said:
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
Click to expand...
Click to collapse
I had it many times. AdAway is working very wele. Maybe you have not full rooted phone. Use MyRoM it is full rotted and AdAway is preinstalled and many others additions.

Hey...
First step is normal root. If you are ready you have to delete the immutable.list on system. Then you can use adaway.
Booth ways need busybox! Install it before you try to delete immutable.
Make it with my tool - easy update and adjust (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286) or make it manuelly with your PC and ADB.
adb shell
su
mount -o rw,remount /system
cd system
chattr -R -i *
rm –f /system/set_immutable.list
lsattr (to see if it's still there)
On my device with stock Rom it works well!

Thank you, it works like a charm!!!

revery0 said:
Thank you, it works like a charm!!!
Click to expand...
Click to collapse
No problem...
Wich way you have choosed?

Your script, cause command prompt returned an error when trying to change attributes, the reason was that adb hadnt have su permissions and for some reason supersu didnt prompt me to grant them. But with your script supersu prompt me to give adb su permissions and so i did, after that it worked.
Strange dont you think?

revery0 said:
Your util, cause command prompt returned an error when trying to change attributes, the reason was that wasanted su permiadbwasntions and suidnt proe to give it permissions, but when I tried your script then I got the prompt from supersu and itsusupersudidntsupersu..
Sounds strange dont you think?
Click to expand...
Click to collapse
I dont understand you complete. But my batch is working for you, thats fine

Auto correction on swype keyboard sucks.... I edited the previous post

revery0 said:
Auto correction on swype keyboard sucks.... I edited the previous post
Click to expand...
Click to collapse
yeah it corrects way u dont want it .. just turn off auto and leave options to pick..

[GUIDE][SuperSU]Android Wear system-less root [2.79]

Follow this guide to flash SuperSU on the latest version of android wear for your watch, it should have the same OS compatibility as normal SuperSU and should work all the way upto android 7.1.1
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
adb reboot bootloader
fastboot oem unlock
2.flash TWRP for your device (REQUIRES read only access to system!, will post working builds in post below)
Code:
fastboot flash recovery recoveryname.img
3.Download SuperSU with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.IGNORE SYSTEM NOT INSTALLED Boot watch to system and Now your root apps from 5.1 should work perfect. THERE WILL BE NO SUPER SU APP, IT HAS NOT BEEN PORTED TO ANDROID WEAR
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop.
If you would like to modify system use any Linux distro and unsquash the system then resquash it (will make guide if enough interest)
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Please leave thanks if it helped!

Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name
Will add them to this post
THESE ARE THE ONLY BUILDS THAT WILL WORK UNTIL TWRP IS UPDATED!
I DID NOT CREATE ANY OF THESE BUILDS!
LG G Watch dory (courtesy of @rbox)
LG G watch R lenok

In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?
Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.
Thanks.

First post and Thanks to you!!!
This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.

OfficerJimLahey said:
In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?
Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.
Thanks.
Click to expand...
Click to collapse
Oh I thought it was an older version will edit that as the latest did not work On 5.1.1 wear but I guess it those on 6.0.1

itsthamessenger said:
This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.
Click to expand...
Click to collapse
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?

Xmaster24 said:
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?
Click to expand...
Click to collapse
Yes it is!

itsthamessenger said:
Yes it is!
Click to expand...
Click to collapse
Thanks for the info will add to post

Unless I am missing something, system access is needed for the LG G Watch.
Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:
Code:
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Failure [DELETE_FAILED_INTERNAL_ERROR]
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb install Downloads/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
1087 KB/s (2287614 bytes in 2.053s)
pkg: /data/local/tmp/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
Success
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
127|[email protected]:/ $
Looks like SuperSU is not even bothering with system-less mode:
http://pastebin.com/T7k0cWHv

OfficerJimLahey said:
Unless I am missing something, system access is needed for the LG G Watch.
Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:
Click to expand...
Click to collapse
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info. Link to squashfs twrp above
It is strange though the other poster managed to root without system access.

Xmaster24 said:
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info.
Click to expand...
Click to collapse
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.
Thanks, I will try your TWRP and report back.
UPDATE:
Your TWRP made all the difference:
Code:
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Success
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb shell
[email protected]:/ $ su
[email protected]:/ #
Thank you!

OfficerJimLahey said:
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.
Thanks, I will try your TWRP and report back.
UPDATE:
Your TWRP made all the difference:
Thank you!
Click to expand...
Click to collapse
No problem guess SuperSU those require system access to work it seems to be for SE Linux patching and also the build.prop

Xmaster24 said:
<snip>
4.Boot to system and open Busybox on rails app and install busybox
<snip>
Click to expand...
Click to collapse
Thanks for this guide! Rooted AOK :good:
This Step 4 is to install Busybox on Rails onto the phone? or Watch?

drewski_1 said:
Thanks for this guide! Rooted AOK :good:
This Step 4 is to install Busybox on Rails onto the phone? or Watch?
Click to expand...
Click to collapse
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch

Xmaster24 said:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Click to expand...
Click to collapse
got it. thanks again!!

Highly recommend everyone to get invisiblek's kernel its top notch gets rid of the horrible lag of 6.0.1's kernel And is fully supported by my root method so even better!

Sent from my GT-S5830i using XDA Free mobile app

Where do supersu and busybox get installed
Xmaster24 said:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Click to expand...
Click to collapse
Since the new wear has a read only system, where do the supersu and busybox get installed?

ganovim said:
Since the new wear has a read only system, where do the supersu and busybox get installed?
Click to expand...
Click to collapse
SuperSU is now system less if you haven't been following it recently so system access is not required also bits of supersu are stored in the kernel disk and others just at /data. Busybox is stored with the SU mounted image to /su/xbin once installed via the app

/moved to specific lg g watch thread

make system dir writeable

Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!

groggycl said:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
Click to expand...
Click to collapse
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.

mhrajib said:
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
Click to expand...
Click to collapse
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?

groggycl said:
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
Click to expand...
Click to collapse
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess

mhrajib said:
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
Click to expand...
Click to collapse
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?

groggycl said:
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
Click to expand...
Click to collapse
What kind of error do you get?? Can you do other operations through link2sd??

mhrajib said:
What kind of error do you get?? Can you do other operations through link2sd??
Click to expand...
Click to collapse
the error is the following..
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Thats the error. Tried with titanium backup pro version and it gets stuck "PROCESING" the thing... It uninstall the app I want to move to system app, but then never finishes processing..
I also used a app called mount "/system ro/rw". I grant it superuser permissions and when I hit the "mount /system rw" a message appears that says; "Your device might not be rooted or is it not compatible!"

groggycl said:
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Click to expand...
Click to collapse
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.

leledumbo said:
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
Click to expand...
Click to collapse
I've installed busybox and when I try lsof /system it says "toybox: Unknown command lsof", is there any solution?

How to set /system partition into rw?

can someone make me a flashable zip for making my /system partition mounted into RW on boot?
Newbie here Will appreciate every help thanks

ChanSilvers said:
can someone make me a flashable zip for making my /system partition mounted into RW on boot?
Newbie here Will appreciate every help thanks
Click to expand...
Click to collapse
You need to have root and any terminal installed.
Start terminal and type
Code:
su
mount -o rw,remount /system
It will be remounted RW without any zip flashing and rebooting, realtime.

fehhner said:
You need to have root and any terminal installed.
Start terminal and type
Code:
su
mount -o rw,remount /system
It will be remounted RW without any zip flashing and rebooting, realtime.
Click to expand...
Click to collapse
thanks man! ? I tried that but my phone reboots after i entered the command and my phone is rooted ?

Sorry for the dig up but i am also interrested in this.
I am using an app (NFC Card Emularo) which requires access to /vendor/etc/libnfc-nxp.conf but cannot access it -> the partition is reported to be "read only" by the app. I was able to use the mount command but i am not sure it changes anything since the partition doesnt seem to be writable anyway.
My rig : OnePlus 3T / Oreo (Resurrection Remix OS) / Magisk 16 (also tried 16.2)

Error on remount /system
/system permission can't get full permission

Hi I am using the same app and facing the same problem you have. I have a moto Z 2016 and using the app well, on moto Z2 ,the same problem as you are having. I tried to create file in the dest folder where the app need to modifiy file and success. Still digging into that.

Has anyone been able to solve this? I too use NFC Card Emulator and it's been working fine for a while but then I got the same problem. I don't know what caused it, either an update to the app, LineageOS, Magisk or TWRP. I'm using a OnePlus 5T.

Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.

Didgeridoohan said:
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Click to expand...
Click to collapse
There is an option to generate a Magisk module from the app and that's actually what I used until things broke. After some testing, going back to the March 5 build of LineageOS 15.1 and getting version 3.0.9 of NFC emulator from Aptoide made it work again, but any version 3.1.0 or up doesn't and 3.0.9 does not work on latest LineageOS (March 26 because f that April fools crap). I also tried all the latest LineageOS/TWRP/NFC Emulator on my old Nexus 6P and there, everything works as expected.
So what I get from this is that the fault is either in LineageOS or the app and it's device specific.

An update to this. LineageOS version does not matter as I was able to get NFC Card Emulator version 3.0.9 running on the latest LineageOS. If you download version 3.0.9 from Aptoide it will work once and then stop working, later versions won't work at all. So the best current solution is to use version 3.0.9 of the app and on each reboot after the first install, clear data for the app and it will work again.

Limero said:
An update to this. LineageOS version does not matter as I was able to get NFC Card Emulator version 3.0.9 running on the latest LineageOS. If you download version 3.0.9 from Aptoide it will work once and then stop working, later versions won't work at all. So the best current solution is to use version 3.0.9 of the app and on each reboot after the first install, clear data for the app and it will work again.
Click to expand...
Click to collapse
I can confirm this.
I was having problems with the lastest version of NFC Card Emulator, so I downloaded and installed version 3.0.9 and everything works fine.
Thanks for the tip!

same problems.
I have xiaomi with miui10 beta and magisk with a module installed.
The nfc say to me that the vendor partition is read only and I must reboot the boot everytime

Aight! I think I've found a solution!
DAVIZINHO said:
same problems.
I have xiaomi with miui10 beta and magisk with a module installed.
The nfc say to me that the vendor partition is read only and I must reboot the boot everytime
Click to expand...
Click to collapse
I'm using MI6 with all in one magisk module enabling camera2 api and some other stuff.
Today morning I f**up my phone trying to solve this problem and found a solution, by accident.
Here it is:
Don't install magisk module mentioned above

szaman8666 said:
I'm using MI6 with all in one magisk module enabling camera2 api and some other stuff.
Today morning I f**up my phone trying to solve this problem and found a solution, by accident.
Here it is:
Don't install magisk module mentioned above
Click to expand...
Click to collapse
The problem in my case is that i need the module "magiskhide props config" for pass the safety check.
If i uninstall this module, maybe not works?
I dont know if i can uninstall the module and work, i will try

DAVIZINHO said:
The problem in my case is that i need the module "magiskhide props config" for pass the safety check.
If i uninstall this module, maybe not works?
I dont know if i can uninstall the module and work, i will try
Click to expand...
Click to collapse
Checked the module You've mentioned, Nfc Card Emulator works fine but it may depend on Miui ROM, mine is 8.5.8 beta.

szaman8666 said:
Checked the module You've mentioned, Nfc Card Emulator works fine but it may depend on Miui ROM, mine is 8.5.8 beta.
Click to expand...
Click to collapse
I need this module, if I uninstall not works the safetynet check.
And with this module, nfc card emulator give me the error I use miui 10 beta

Didgeridoohan said:
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Click to expand...
Click to collapse
In theory, if I temporarily disable all of my modules and enable Core Only Mode, would I be able to access the system as RW?

rodken said:
In theory, if I temporarily disable all of my modules and enable Core Only Mode, would I be able to access the system as RW?
Click to expand...
Click to collapse
That is a two and a half year old post you're quoting. A lot have happened in that time...
Core only mode is being removed from Magisk and there are plenty of devices that have permanently ro partitions.
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
So the answer to your question would be a definite maybe.

Didgeridoohan said:
That is a two and a half year old post you're quoting. A lot have happened in that time...
Core only mode is being removed from Magisk and there are plenty of devices that have permanently ro partitions.
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
So the answer to your question would be a definite maybe.
Click to expand...
Click to collapse
im on android 10 DirtyUnicorns and i want to completely replace the media folder with my own mod. how can i do this? im not able to do it on my pixel 3 yet i just did it on my pixel 2 xl running the same ROM.

Hola yo lo único que quiero es montar sistema como lecturas escritura y ya como puedo hacer android 8

Using Link2SD on the R1HD?

Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?

darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201

mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )

darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"

mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.

darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.

mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.

Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.

darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?

dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.