Hi,
First, I'm a noob with some experience!
I know how to root my phone with Magisk and I helped Jen to root the LG G4 Vigor (H731) for Videotron/Telus. She was working on the H735 if I'm not mistaken but it worked for mine too since it's the same phone without the same name. It was with SuperSu, I don't think Magisk was out at this time.
Well... at that time I bought Busybox Pro... I don't know why except everyone had it!!
I'd really like some explanation. I searched for at least 4 days, 1-4 hours per day and it was a LOTS of different things! I'm really confused about the difference between Busybox and Magisk, expect Magisk is SystemLess.
I can install "add-ons" with Magisk like Xposed!!
I really don't know what I can do with Busybox except installing "things" but are those "things" are like a module in Magisk/Xposed?
P.S. I know that if I install Xposed in Magisk, it become systemless like Magisk!
And! I know that I can install Busybox from Magisk! But I bought the Busybox Pro app from Google Play Store.
Can someone tell me all those differences? I'm really messed up and really need help +++ I think a good explanation could help lots of others than me.
Thank you VERY much!!!
Busybox is just a set of tools that some apps/programs/processes/etc use. Magisk actually has its own internal Busybox that it uses for a lot of things, but it's not exposed to the rest of your system, which is why you need to install a separate Busybox if something about your setup needs it. It used to be more common that a separate Busybox installation was needed, but nowadays not so much, since most apps that need it already come with their own version of it to ensure compatibility. You can read more about what Busybox is at https://www.busybox.net.
I actually had the same question. I've rooted a few of my devices already. And years back I've also bought some apps via Play-Store. But a lot of these apps seems to be dated and not maintained annymore.
For instance I've bought a few apps from JRummy back then, from which I still use Busybox and Rootchecker nowadays. But this bussybox seemed to be quite dated when looking to the last update moment.
I'm using Magisk now and I was thinking going to use it's integrated Busybox too. Can it just work next to each other? Or do I need to unstall the JRummy Bussybox before?
Didgeridoohan said:
Busybox is just a set of tools that some apps/programs/processes/etc use. Magisk actually has its own internal Busybox that it uses for a lot of things, but it's not exposed to the rest of your system, which is why you need to install a separate Busybox if something about your setup needs it. It used to be more common that a separate Busybox installation was needed, but nowadays not so much, since most apps that need it already come with their own version of it to ensure compatibility. You can read more about what Busybox is at https://www.busybox.net.
Click to expand...
Click to collapse
You can activate and use busybox by typing or copy and paste the busybox magisk location. Such as
/data/adb/magisk/busybox xz -d /storage/emulated/0/Download/root.img.xz
This is the busybox command to decompress xz archive.. as long as your root with busybox no need to install unless an application requires it.
Related
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.
Intro
Expose your su to standard location /system/xbin/su systemless-ly.
Though it helps grant root permission to some apps, this trick breaks safetynet.
Just made a simple module try to solve the /sbin/su not detectable problem. This module will look for existing su binary, and create a link as /magisk/su_xbin_bind/system/xbin/su pointing to the real su. The link will also be mounted as /system/xbin/su systemless-ly later.
Installation
Flash it in Magisk manager or through recovery, then reboot. You will find a link /system/xbin/su. All the work is done systemless-ly.
Uninstallation
Open Magisk Manager, go to Modules, disable or uninstall the module called "Su xbin_bind". Then it will disappear after reboot.
su-xbin-bind on github
Changelog
v1.2 20170417
Add Magisk v12 support.
v1.1 20170323
- make it compatible with Magisk v11.5/11.6
Update 20170228
- Since a little syntax error in the mounting script from Magisk v11.0-v11.5, mounting links systemless-ly won't success. Hence we choose to copy but not to link the su binary for v11.0-v11.5. Don't worry, both methods are systemless.
Reserved.
Hi, will this not make safetynet fail?
kartikb said:
Hi, will this not make safetynet fail?
Click to expand...
Click to collapse
It will obviously. Because su is exposed to /system/xbin/su and will be detected.
laggardkernel said:
It will obviously. Because su is exposed to /system/xbin/su and will be detected.
Click to expand...
Click to collapse
Wouldn't magiskhide unmount that and therefore pass safetynet?
I used your module to fix TiBackup freeze when restorins apps.
TiBackup troubleshooting (http://www.titaniumtrack.com/kb/tit...l#tb-hangs-while-freezing-apps-restoring-apps) reports that this issue is connected with wrong su permissions in /system/bin and /system/xbin. Since these are not available due to systemless root, I though that your module would represent an elegant fix... and it did!
Thanks!
leonardus_magnus said:
I used your module to fix TiBackup freeze when restorins apps.
TiBackup troubleshooting (http://www.titaniumtrack.com/kb/tit...#tb-hangs-while-freezing-apps-restoring-apps) reports that this issue is connected with wrong su permissions in /system/bin and /system/xbin. Since these are not available due to systemless root, I though that your module would represent an elegant fix... and it did!
Thanks!
Click to expand...
Click to collapse
Does ur safety net fail with this module?
Xennet said:
Does ur safety net fail with this module?
Click to expand...
Click to collapse
Oh c'mon, you cannot be serious... On Xda forums you have threads with hundreds of pages and I would admit you did not read all of them... but your answer has already been replied on post n. 4 in this page... I can' believe it...
leonardus_magnus said:
Oh c'mon, you cannot be serious... On Xda forums you have threads with hundreds of pages and I would admit you did not read all of them... but your answer has already been replied on post n. 4 in this page... I can' believe it...
Click to expand...
Click to collapse
Yah i saw it lol....
But magisk usually dismounts xbin folder...
Then it unusual to get it detected unless it is physically present der...
So just wanted to confirm it before flashing...
Xennet said:
Yah i saw it lol....
But magisk usually dismounts xbin folder...
Then it unusual to get it detected unless it is physically present der...
So just wanted to confirm it before flashing...
Click to expand...
Click to collapse
Ok safety net not passed on my device... but it's not an issue at all for me...
Unfortunately, doesn't fix the Titanium Backup issue (freezing or restoring app) for me on Galaxy S6 Android 6.0. This also broke SafetyNet for me, even after uninstalling the module from Xposed and rebooted.
chaoscreater said:
Unfortunately, doesn't fix the Titanium Backup issue (freezing or restoring app) for me on Galaxy S6 Android 6.0. This also broke SafetyNet for me, even after uninstalling the module from Xposed and rebooted.
Click to expand...
Click to collapse
If you mean you are using xposed, obviously safetynet will be broken. MagiskHide couldn't hide xposed.
This module tries to fix the su detectable problem. If your titanium backup could get root permission after installing the module, it means the module worked.
My TB is working fine, but I have another app that can't detect it, will give it a test run, thanks for your work!
HI! Just a quick feedback: this module works with Helium Backup that now correctly asks for root permission! :good:
Thank you!
Thanks for the module!! It was the key for me getting Termux su working ?
Hello, I flashed this without error and titanium backup as well as ES file explorer both report I do not have root. Magisk v12 states i do have root.
nevermind...i realized Magisk SU isn't installed as it didn't auto install. I had installed phh's superuser r266-2.
proceeded to rewipe and reflash everything.
Nexus 6P
[ROM][6P][7.1.2_r8]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[05/09/17]
ex 4.09
Magisk v13 beta
no issues and all superuser root requests appear.
Big big BIG THANK YOU to you. Fixed the most important app for custom ROMs- Kernel adiutor:highfive: (Both play store:good: and modded versions:laugh and secure settings tasker plugin
Please update the script for the new template v4 for Magisk v13!
:good:
If *enabled* in magisk 13, titanium backup can't get root.
I had to disable it.
Hi,
Work with Magisk Version 13.3 ???
Hello,
First off, I am using a Oneplus 5 device running 7.1.1 Nougat.
I followed this guide to root my phone with Magisk 13.2 https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I am able to download apps that require root, and grant them said root access.
However when trying to give AdAway Systemless root access (In preferences) the checkbox is greyed out and unusable.
So far so bad.
When trying to install BusyBox, and try to select a different install path (/su/xbin or /su/bin) I get the error message : "Systemless root is not configured, please choose another install location"
If I go into Magisk Manager both BusyBox and AdAway are Granted Root access, and when checking settings, Hosts Systemless is activated.
Am I simply blind and have I missed a step? On the Magisk Manager Homescreen, it says I have the latest version installed, and MAGIKSU is also validated.
Help please? I'm confused. D:
For AdAway you shouldn't have to bother with the systemless option. Just enable Systemless hosts in the Magisk Manager.
You could also use a Magisk module. There's a great one called Unified Hosts Adblocker. Unfortunately there's a bug in the Manager at the moment that makes it crash when downloading modules. They can be installed manually though (there's a download in the thread).
For busybox you've got a great installer here: https://forum.xda-developers.com/showthread.php?t=2239421
It'll install as a Magisk module when flashed in recovery.
Hello,
I've followed your suggestion and manually installed Unified Hosts Adblocker. I'm assuming it will update on it's own when required? As it has no interface. (Also, I am still getting ads, is this normal? xD)
So installing AdAway won't trigger SafetyNet as long as I have "Hosts Systemless" checked right?
I have also flashed the BusyBox installer from the link you gave me. It shows up on Magisk Modules, however it hasn't created a busybox icon in my applist. (Again, no interface? Is this installed correctly?)
Furthermore, I've looked around a bit, and is it true I currently can not expect to run Xposed Framework on Nougat?
Thank you for your current answers, in the hopes of further ones.
With the hosts module you'll have to run it manually. Use a terminal emulator and type su followed by hosts and then follow the instructions. The m option is included in all the others... Don't forget to enable systemless hosts or it won't work. More about how you use the module in the thread.
There's no interface for the busybox installation, no. There's no need really...
---------- Post added at 17:27 ---------- Previous post was at 17:26 ----------
Oh yeah. No Xposed for Nougat.
Thanks for your help, it's been of great assistance and sets my mind to rest that nothing really went wrong with my installation of Magisk. I'll keep an eye out for the Manager updates that'll fix the downloads.
I was once again just wondering about the updating of busybox, but I'll just assume that if I get a "Update busybox" from any app, I'll come back to the post you directed me to and update it that way.
You didn't answer my pondering about Xposed, but once again I'll just assume what I found is true and the developer currently hasn't had time to update it yet, and it may take a while.
Thank you for your time and the peace of mind you've procured me.
Didgeridoohan said:
Oh yeah. No Xposed for Nougat.
Click to expand...
Click to collapse
:laugh:
I'm new to Magisk, and one thing I'm confused about is the role of the various systemless modules.
1. Essentially, is there anything that I *can't* do normally with Magisk (that I would be able to do if it were rooted any other way) that I *have to* have a module for?
For example, when you have modules to have systemless hosts or systemless Busybox - does that mean that when you use Magisk, you *can't* install or work with these things without those modules, or does it mean that you still could do it normally, but the modules just give you an option to do it without actually modifying anything?
2. If the answer is that I can still do everything normally, but the modules just give me the *option* to do it without actually modifying /system, then why does it matter?
For example, I've never minded having an adblock application actually modify the hosts file when I've rooted in the past before Magisk, so what advantage is there to redirecting them to a fake hosts file? If anything, I would think it increases the chance that something will go wrong or that there will be an incompatibility somewhere along the way.
Everything that Magisk does systemlessly can be done in the old and normal way of modifying system files.
The main advantage for me to use Magisk modules is that all the modifications are still there after a system update (since they'll be in the Magisk image which is kept in /data/adb). I won't have to redo them like I used to before Magisk...
For those that care about updating their device through an OTA, systemless modifications will also make sure that will still work, sort of. You'll still have to keep a stock recovery and restore your stock boot image before updating, but with newer devices that's getting a lot easier. More details here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Didgeridoohan said:
Everything that Magisk does systemlessly can be done in the old and normal way of modifying system files.
The main advantage for me to use Magisk modules is that all the modifications are still there after a system update (since they'll be in the Magisk image which is kept in /data/adb). I won't have to redo them like I used to before Magisk...
For those that care about updating their device through an OTA, systemless modifications will also make sure that will still work, sort of. You'll still have to keep a stock recovery and restore your stock boot image before updating, but with newer devices that's getting a lot easier. More details here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Gotcha! It's not obvious for people new to Magisk whether using a systemless root forces you to do everything in a systemless manner afterwards or not, so I really appreciate your clarifying this.
Haphim said:
Gotcha! It's not obvious for people new to Magisk whether using a systemless root forces you to do everything in a systemless manner afterwards or not, so I really appreciate your clarifying this.
Click to expand...
Click to collapse
No worries. Just want to point out that systemless root isn't Magisk specific. SuperSU and phh's superuser are two examples of root solutions that were systemless long before MagiskSU was a thing...
I used SuperSu many, many years ago and figured I would give it a try an old e5 Plus that's been collecting dust in a junk drawer. Using Platform Tools, TWRP and a SuperSu zip the whole process took maybe 10 minutes.
I noticed that all of the guides here use Magisk and they look fairly complicated for the average user. Is there a reason why it's favored over SuperSu? Now that I'm rooted, can I use Magisk and all of its features (modules, etc)?
SuperSU is more easily detected by banking apps, Netflix, Disney+, Google Pay etc. As it modifies the system partition while Magisk is a system-less root.
dbohnine said:
Now that I'm rooted, can I use Magisk and all of its features (modules, etc)?
Click to expand...
Click to collapse
I think you can install Magisk using the SuperSU root. But anyway if you want to use Magisk features, you will need to install Magisk.