Database Develop

I think I lost busybox? (and possibly root as well)

Ok, so my problems began after I updated to the the HTC ADP 1.6 ROM. I figured after I got it installed, I would just run fix permissions and be off to the races. That didn't work because I kept getting the error "cp: not found" when attempting to copy the script to /system/bin from the sdcard.
On a possibly related note I couldn't load Cyanogen's 1.4 recovery image either (currently using JF's v1.51) because of the error "flash_image: not found."
Doing some googling I found out that the function 'cp' was enabled by busybox. So I figured that maybe during the course of upgrading to 1.6 I lost busybox. I followed the directions here to reinstall:
http://benno.id.au/blog/2007/11/14/android-busybox
So in short, I'm about 1000% sure I messed up somewhere. The question is, at this point is it possible to fix what's wrong, or should I go through the steps to root my phone again? I'd like to avoid the latter if at all possible.
And at this point I'm not even sure that I have root anymore. I ran a script to reboot the phone (which requires su privies) so I guess I do.
Any and all help is appreciated.

http://forum.xda-developers.com/forumdisplay.php?f=507

Minker17 said:
http://forum.xda-developers.com/forumdisplay.php?f=507
Click to expand...
Click to collapse
...and which thread there should I follow?

the.snks said:
Any and all help is appreciated.
Click to expand...
Click to collapse
ADP1 builds do not have busybox or a su binary installed. You can install them yourself if you need the functionality. The "rooted base" in this thread has an already setup Superuser.apk protected su if you are lazy (you'll still have to install busybox though). Also if you use tethering you'll need to replace the kernel.

the.snks said:
...and which thread there should I follow?
Click to expand...
Click to collapse
Please differentiate between forums. You posted a question in the developepent forum. If you are not presenting something that you have developed for the dream/android platform, you should post in another forum. Questions, of course, go in the Q & A forum.

stogchris81 said:
Please differentiate between forums. You posted a question in the developepent forum. If you are not presenting something that you have developed for the dream/android platform, you should post in another forum. Questions, of course, go in the Q & A forum.
Click to expand...
Click to collapse
Gotcha. I don't see how to move or delete this thread.
Mods?

jashsu said:
ADP1 builds do not have busybox or a su binary installed. You can install them yourself if you need the functionality. The "rooted base" in this thread has an already setup Superuser.apk protected su if you are lazy (you'll still have to install busybox though). Also if you use tethering you'll need to replace the kernel.
Click to expand...
Click to collapse
I wasn't completely clear in the first post, I updated to the HTC ADP 1.6 with rooted base. I'm not sure if I eveb need busybox. That was just part of the attempt to install Cyanogen's 1.4 recovery image using the below instructions:
http://forum.xda-developers.com/showthread.php?p=3915123
I kept getting a "flash_image: not found" error. I would just install the CM's new ROM (http://forum.xda-developers.com/showthread.php?t=567610), but that's a no go since I can't get the recovery image loaded.
At this point I don't care anymore if I have to wipe. If I can get CM's recovery image loaded, I can go from there.

jashsu said:
ADP1 builds do not have busybox or a su binary installed. You can install them yourself if you need the functionality. The "rooted base" in this thread has an already setup Superuser.apk protected su if you are lazy (you'll still have to install busybox though). Also if you use tethering you'll need to replace the kernel.
Click to expand...
Click to collapse
Actually, ADP1 builds *do* have "su", it is just limited to root and shell users (i.e., it'll work if you already have root privileges -- switch user to a RESTRICTED user to test file access permissions, or switch from shell to *any* user from adb).

Eff it. I'm going to totally downgrade and then root again using the sticky in this section. This just isn't worth the hassle.
Thank you to everyone that tried to help.
Mods: You can delete this thread.

[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?

Magisk (MagiskSU) - Busybox won't install, says "Systemless root is not configured".

Magisk (MagiskSU) - Busybox won't install, says "Systemless root is not configured".
I've installed/flashed the latest stable Magisk version: v13.2. (Since version v13.1 I believe the bundled busybox included with Magisk was removed because it caused a lot of issues)
I've tried to install BusyBox to "/su/xbin" but it always throws up the error "Systemless root is not configured".

bseos said:
I've installed/flashed the latest stable Magisk version: v13.2. (Since version v13.1 I believe the bundled busybox included with Magisk was removed because it caused a lot of issues)
I've tried to install BusyBox to "/su/xbin" but it always throws up the error "Systemless root is not configured".
Click to expand...
Click to collapse
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421

double_post

abacate123 said:
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
Tried adding it as a module to Magisk however it reports it's not a magisk module "this zip is not a magisk module".
Flashed it with TWRP and it installed in su/xbin. Thanks :good:

abacate123 said:
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
I flashed that zip in my Xperia XA and I'm still having the "systemless root is not configured". I need to install busybox in su/bin or su/xbin/ to make Viper4android work. Can u help me?

https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

aocboe said:
https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
Click to expand...
Click to collapse
But which do I install?

Evedammo said:
But which do I install?
Click to expand...
Click to collapse
Install "Busybox-1.27.1-YDS-ARM.zip" in the Magisk Manager

aocboe said:
Install "Busybox-1.27.1-YDS-ARM.zip" in the Magisk Manager
Click to expand...
Click to collapse
I've installed that. In the magisk modules it doesn't appear I flashed from TWRP, and I'm still having the "systemless root" message in busybox.

Evedammo said:
I've installed that. In the magisk modules it doesn't appear I flashed from TWRP, and I'm still having the "systemless root" message in busybox.
Click to expand...
Click to collapse
If you want to use it as a Magisk module, maybe you should install it from the Magisk Manager instead of flashing from TWRP.
Besides, I didn't catch your meaning. You mean the busybox app notice? Now that busybox is installed, you don't have to mind that notice.

Why are you guys trying to install to /su? Unless you're still on Magisk v12, you shouldn't be using SuperSU...

Rain X
I'm new, so I can't post links, but a youtuber named Rain X may have a solution. I tried his method and it worked for me:good:

Soumy1234 said:
I'm new, so I can't post links, but a youtuber named Rain X may have a solution. I tried his method and it worked for me:good:
Click to expand...
Click to collapse
What method would that be? No, I'm not gonna go hunting for some random Youtuber...
If the aim is to get a functioning busybox up and running, the easiest way is to just install @osm0sis busybox module from the downloads section in the Manager. No other apps needed...

He installed busybox in system/xbin
He made a folder called "Viper4Android" in the "system/priv-app" folder and copied a Viper4Android APK in there
He set the permissions of said APK to -rw-r--r-- (I set to -rwxrwxrwx for good measure)
He went to "system/vendor/etc" ("system/etc" if it's not there) folder, made a copy of the "audio_effects.conf" file
He renamed the "audio_effects.conf" file in the etc folder to "audio_effects.conf.bak"
He pasted the original "audio_effects.conf" file back in the "etc" folder, so now he has a "audio_effects.conf" and a "audio_effects.conf.bak" file in the "etc" folder
He changed the permissions of the "audio_effects.conf" file to "-rw-r--r--"
He rebooted, opened V4A, installed drivers, then rebooted
Hope this helped.

Didgeridoohan said:
What method would that be? No, I'm not gonna go hunting for some random Youtuber...
If the aim is to get a functioning busybox up and running, the easiest way is to just install @osm0sis busybox module from the downloads section in the Manager. No other apps needed...
Click to expand...
Click to collapse
I tried that,but it didn't work for me. If it doesn't work for you, I've already written some instructions on what the YouTuber did... Hope that helps.

Soumy1234 said:
I tried that,but it didn't work for me. If it doesn't work for you, I've already written some instructions on what the YouTuber did... Hope that helps.
Click to expand...
Click to collapse
That busybox module works perfectly for me.
And I'm using Magisk partly because it makes system modifications like V4A systemless. Therefore I would not follow those instructions...
I do have V4A working though, with this Magisk module and by utilising this workaround until the module has been updated. Nice and systemless...
The above mentioned workaround hasn't worked for everyone, but several other ways of getting it to work have been discussed in that thread.

Didgeridoohan said:
That busybox module works perfectly for me.
And I'm using Magisk partly because it makes system modifications like V4A systemless. Therefore I would not follow those instructions...
I do have V4A working though, with this Magisk module and by utilising this workaround until the module has been updated. Nice and systemless...
The above mentioned workaround hasn't worked for everyone, but several other ways of getting it to work have been discussed in that thread.
Click to expand...
Click to collapse
Oh, okay. Can you at least tell me how much the BusyBox zip work for you? I tried installing it through Magisk and TWRP, but it gave some errors.

Soumy1234 said:
Oh, okay. Can you at least tell me how much the BusyBox zip work for you? I tried installing it through Magisk and TWRP, but it gave some errors.
Click to expand...
Click to collapse
You'll need to provide some details for that... After flashing the module in TWRP, can you save the recovery log (Advanced - Copy log) and attach it to a post here.
And I forgot to say, but for the V4A module I linked, I don't even need busybox installed. YMMV...

Didgeridoohan said:
You'll need to provide some details for that... After flashing the module in TWRP, can you save the recovery log (Advanced - Copy log) and attach it to a post here.
And I forgot to say, but for the V4A module I linked, I don't even need busybox installed. YMMV...
Click to expand...
Click to collapse
Funny. It seemed to work this time. The last time I tried it literally said it failed.

Soumy1234 said:
Funny. It seemed to work this time. The last time I tried it literally said it failed.
Click to expand...
Click to collapse
Doesn't look like it succeeded when looking at the log...
What's the error message when you install through the Manager?

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.