I am bit of confused why is phh superuser is needed when you already got magisk and it's superuser n su files . Does merging phh superuser to magisk helps to support app more ..like titanium backup
Related
I used to have the supersu app but i wanted to switch to superuser to i selected the cleanup and switch to other superuser app.
I then installed superuser and attempted to update the binary which failed so i installed the binary manually through recovery.
When i use a root app i get no prompts, if i try temp unroot it doesnt work but if i install super su and install its binary, superuser and all other root apps ask supersu for root access, any help guys?
slyviper1700 said:
I used to have the supersu app but i wanted to switch to superuser to i selected the cleanup and switch to other superuser app.
I then installed superuser and attempted to update the binary which failed so i installed the binary manually through recovery.
When i use a root app i get no prompts, if i try temp unroot it doesnt work but if i install super su and install its binary, superuser and all other root apps ask supersu for root access, any help guys?
Click to expand...
Click to collapse
I would recommend installing SuperSU and the related su binary. From there use terminal emulator to uninstall the related SuperSU files manually, also uninstall the Superuser apk and binary so you'll have a clean slate, then lastly remove the SuperSU su binary, then uninstall the SuperSU apk. Once you have done this I would install the Superuser app (I assume you are talking about Koush's Superuser app and binary), and binary through recovery. After doing this it should allow you to use Superuser. What version of Android are you running? Also keep in mind Koush's Superuser hasn't been updated for a while, which is why for the latest version of Android SuperSU really is the best choice.
Could you give me the steps needed to remove super su and the binary
Sent from my C6603 using XDA Free mobile app
Which is better?
kim said:
Which is better?
Click to expand...
Click to collapse
Magisk
JosephDM said:
Magisk
Click to expand...
Click to collapse
How is it better?
First of all, they are not the same thing, you can even use both.
Magisk is meant to install modules systemless, like Viper4Android, custom hostsfile (like an Adblock) even xposed and many other mods.
If you have other SU like Chainfire SuperSU or phh's Superuser, Magisk will use it. If theres no SU installed Magisk will install MagiskSU.
Magisk can also hide sistem mods from other apps, even SELinux permissive or SU, basically Magisk is like xposed but for other type of system mods and leave /system untouched, so it can be used with Google SafetyNet, Samsung KNOX or other security featured
See more at Magisk forum https://forum.xda-developers.com/apps/magisk
American_Jesus said:
First of all, they are not the same thing, you can even use both.
Magisk is meant to install modules systemless, like Viper4Android, custom hostsfile (like an Adblock) even xposed and many other mods.
If you have other SU like Chainfire SuperSU or phh's Superuser, Magisk will use it. If theres no SU installed Magisk will install MagiskSU.
Magisk can also hide sistem mods from other apps, even SELinux permissive or SU, basically Magisk is like xposed but for other type of system mods and leave /system untouched, so it can be used with Google SafetyNet, Samsung KNOX or other security featured
See more at Magisk forum https://forum.xda-developers.com/apps/magisk
Click to expand...
Click to collapse
Thank you for clarifying sir
I am currently using Lenovo P2 running on Nougat 7.0.0 rooted with PHH's Superuser.
I wanted to switch to SuperSU because Tasker does not ask for and detect any root with PHH's Superuser.
I have searched quite a bit but have only found the way to switch from SuperSU and not to SuperSU.
Unlike in SuperSU, PHH's Superuser does not have any unroot option in the settings.
Any help will be appreciated.
Thanks.
This is a module of Magisk so you can Uninstall from There
Hi
I installed 8.11.29 from xiaomi.eu and got a install and root with magisk. When I try to apply Adaway after having a root permition right, it says it's impossible to apply. With Root Explorer, I have the same problems, neither can I delete files nor add.
With 8.11.15 all program work and Magisk superuser too.
Adaway issue explained
Marian166 said:
Hi
I installed 8.11.29 from xiaomi.eu and got a install and root with magisk. When I try to apply Adaway after having a root permition right, it says it's impossible to apply. With Root Explorer, I have the same problems, neither can I delete files nor add.
With 8.11.15 all program work and Magisk superuser too.
Click to expand...
Click to collapse
Hi,
In Magisk Settings make sure that you have 'Systemless Hosts' set to 'on'. That should solve your problem.
Pepsimaxmjs
Thanks!
And for Root Explorer?
I can't delete or add any files in root folder.
Bloatware remover also not work and can remove apps.
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?