Related
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.
Hi everyone. I'm new at this bands.
I have S5style_i8190XXANC2_v3 instaled on my phone. I tried to install ViperFX but i couldn't do that that because driver instalation fails. It says it's because of busybox not properly instaled or something like that.
What i want to know? how to install busybox correctly? i tried do that with a play store app BusyBox instaler but not solved the problem.
Can anyone help me?
Thanks and sorry for bad english.
pajocos said:
Hi everyone. I'm new at this bands.
I have S5style_i8190XXANC2_v3 instaled on my phone. I tried to install ViperFX but i couldn't do that that because driver instalation fails. It says it's because of busybox not properly instaled or something like that.
What i want to know? how to install busybox correctly? i tried do that with a play store app BusyBox instaler but not solved the problem.
Can anyone help me?
Thanks and sorry for bad english.
Click to expand...
Click to collapse
1)Install busybox installer app https://play.google.com/store/apps/details?id=stericson.busybox
2)Run busybox installer app
3)Install busybox from inside the running app
4)Done :good:
jstath1972 said:
1)Install busybox installer app https://play.google.com/store/apps/details?id=stericson.busybox
2)Run busybox installer app
3)Install busybox from inside the running app
4)Done :good:
Click to expand...
Click to collapse
I tried this to... Still not working.
Hey dude its have allready busybox :
Originally Posted by galaxy mini View Post
V3 is on its way, hope i get it ready and uploaded this week!!
- lighter version
- fixed layout bugs
- kill app with long press backbutton added
- few UI changes
- latest SU and busybox added
http://forum.xda-developers.com/showthread.php?p=52630772&highlight=busybox#post52630772 Post #163
You don't have to install another one. Maybe old version ViperFX? Make sure you use the version for Android 4.x
jstath1972 said:
Check if your phone is still rooted.
Click to expand...
Click to collapse
yes it is. i can use other apps that need's root. I can use greenify for exemple and other app to remove system apps that i don't need. All off them are working. I install the busybox and it's successful. But when I try to install the driver that Viper ask's it says: driver install failed, the busybox found on your device does not work. this usally means you installed the wrong or broken busybox.
jstath1972 said:
Hey dude its have allready busybox :
Originally Posted by galaxy mini View Post
V3 is on its way, hope i get it ready and uploaded this week!!
- lighter version
- fixed layout bugs
- kill app with long press backbutton added
- few UI changes
- latest SU and busybox added
http://forum.xda-developers.com/showthread.php?p=52630772&highlight=busybox#post52630772 Post #163
You don't have to install another one. Maybe old version ViperFX? Make sure you use the version for Android 4.x
Click to expand...
Click to collapse
Yes i'm using that version. but i'll try again.
pajocos said:
yes it is. i can use other apps that need's root. I can use greenify for exemple and other app to remove system apps that i don't need. All off them are working. I install the busybox and it's successful. But when I try to install the driver that Viper ask's it says: driver install failed, the busybox found on your device does not work. this usally means you installed the wrong or broken busybox.
Click to expand...
Click to collapse
Maybe old version ViperFX? Make sure you use the version for Android 4.x
jstath1972 said:
Maybe old version ViperFX? Make sure you use the version for Android 4.x
Click to expand...
Click to collapse
Nope... still not working. I don't know what i'm doing wrong... I really don't want to do this by brute force. That means reinstall rom to see what is going to happen.
I'll try to install previous version from busybox. it can be incompatible or something like that.
Install sd maid app and run it to see if the busybox in your device is ok.
If this app running and don't ask from you to install busybox then it's vipers fault.
jstath1972 said:
Install sd maid app and run it to see if the busybox in your device is ok.
If this app running and don't ask from you to install busybox then it's vipers fault.
Click to expand...
Click to collapse
yup. on geral vision, on busybox it says [Normal] so it must be viper fault... Can you point me any other good equalizer to s3 mini?
pajocos said:
yup. on geral vision, on busybox it says [Normal] so it must be viper fault... Can you point me any other good equalizer to s3 mini?
Click to expand...
Click to collapse
DSP Manager Equalizer for Android is the alternative to viper or you can look at the playstore.
thank you!!!
jstath1972 said:
Install sd maid app and run it to see if the busybox in your device is ok.
If this app running and don't ask from you to install busybox then it's vipers fault.
Click to expand...
Click to collapse
SD Maid doesn't check the devices system busybox.
Use a tool like https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator for that.
Viper Audio for Android devices
Viper Audio for Android devices can be installed without busybox... Just follow instructions...
1. Download v4a . zip
2. Flash using recovery like cmw. After reboot device .
3. Install viper Audio application, now everything done.
4. If you need to check driver status, check in menu...Done... View attachment 2947879
I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc
Do you have a folder called init.d in system/etc?
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not
Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be
Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.
gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1
Universal init.d install it from play store and follow instructions
miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?
trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.
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
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.