Magisk Compatible phh's SuperUser
This thread is obsolete, please check Magisk OP for MagiskSU
Files removed to prevent confusion
Official thread to phh's SuperUser: phh's SuperUser/ OpenSource SELinux-capable SuperUser
Requirements
Magisk is required to be installed on your device!
Magisk - The Universal Systemless InterfaceFeatures
phh's 100% open source root
Packed with my own sepolicy-injection tools, which support live patching to work on small boot image devices
Magisk compatible, no boot image modifications are required
su.d support (place scripts in /magisk/phh/su.d)
Instructions
You can install/update phh's SuperUser in Magisk Manager's Download section
If you have no root in the first place, please flash the zip in the attachment through custom recovery
A root solution is part of a proper Magisk installation.
After phh's SuperUser is installed, please install the SuperUser manager Application through the Play Store
phh's SuperUser Manager
Source
https://github.com/topjohnwu/sepolicy-inject (sepolicy-tools)
https://github.com/topjohnwu/Superuser (Magisk repo source)
https://github.com/Magisk-Modules-Repo/phh-superuser (Magisk repo source)
Changelog
Changelog
topjohnwu r2
- Fix binary out-of-date issue
topjohnwu r1
- Forked from phh main repo, improved daemon launching
- Fixed Samsung no-suid issue
r266-2
- Preserve /sbin binaries to prevent issues
r266
- Allow priv-app to start root
- Allow audioserver to execute from memory (for Call Recorder)
- (Magisk) Change path to /sbin, now same as official phh
r259
- Initial release on Magisk repo
This still wont disable running purenexus rom.
joeyddr said:
This still wont disable running purenexus rom.
Click to expand...
Click to collapse
+1 on stock debloated nexus 6
Magisk V1 + systemless xposed work with Android Pay.
You have stated in your Magisk thread that Android Pay won't work with Xposed enabled, old method is still needed.
Want to update you that I have used your Magisk V1 and your version of systemless Xposed with Andoid Pay for payment on 9 August and it work. Phone is Oneplus 3. I only use Magisk to unmount root. Never have to disable Xposed or reboot phone.
K I installed magisk v2 and phh su v2...unmounted root and tried to buy coffee at Starbucks... No luck! Got the usual message when device is rooted. I am stock Nexus 6p no mods and AP worked yesterday before installing magisk and phh
This is crazy
orthonovum said:
K I installed magisk v2 and phh su v2...unmounted root and tried to buy coffee at Starbucks... No luck! Got the usual message when device is rooted. I am stock Nexus 6p no mods and AP worked yesterday before installing magisk and phh
This is crazy
Click to expand...
Click to collapse
Are you using Xposed?
One of my testers tried and Xposed won't work.
Like where you live there's no AP here
I'm trying to find a way to hide root from a streaming app. I can't get root disabled (pressing 'disable' does nothing) (stock debloated nexus 6), that's why i was trying to get it to work with SuperSU.
BTW: the try with SuperUser did not make any logs, just FYI.
ThomasC1970 said:
You have stated in your Magisk thread that Android Pay won't work with Xposed enabled, old method is still needed.
Want to update you that I have used your Magisk V1 and your version of systemless Xposed with Andoid Pay for payment on 9 August and it work. Phone is Oneplus 3. I only use Magisk to unmount root. Never have to disable Xposed or reboot phone.
Click to expand...
Click to collapse
Thanks for your feedback!
I hate that I cannot use Android Pay myself.
No tester report the same result. I'm lost
topjohnwu said:
Are you using Xposed?
One of my testers tried and Xposed won't work.
Click to expand...
Click to collapse
is there currently or will there be a way to have this so that when Android Pay is opened, both xposed and root disable temporarily X number of minutes?
The log in cache says disabling for 5 minutes , but it stays mounted. It also takes away root for apps like root explorer and busy box. I can open a terminal and su fine safety net fails, so it seems it half disables root on purenexus but never fully unmounts as df shoes the partition still mounted. Root comes back to all apps after 5 minutes
steveo17 said:
is there currently or will there be a way to have this so that when Android Pay is opened, both xposed and root disable temporarily X number of minutes?
Click to expand...
Click to collapse
Nope, Xposed cannot be disabled temporary. May you try with only phh's root and no Xposed? Thanks!!
android:targetSdkVersion="24"
Could this be the reason of Magick's Manager not showing in Marshmallow?
Sent from my OnePlus One using XDA Labs
topjohnwu said:
Nope, Xposed cannot be disabled temporary. May you try with only phh's root and no Xposed? Thanks!!
Click to expand...
Click to collapse
ah i didnt realize that a reboot was needed for xposed.
rgawenda said:
android:targetSdkVersion="24"
Could this be the reason of Magick's Manager not showing in Marshmallow?
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
Nah, the min SDK is set to 21 so it should show up in Marshmallow.
topjohnwu said:
Are you using Xposed?
One of my testers tried and Xposed won't work.
Click to expand...
Click to collapse
No Xposed. just a clean unrooted system and this morning flashed TWRP->magiskV2->phh.zip->installed phh superuser from app store->went to starbucks->disabled root using magisk manager->tapped phone to POS terminal and phone tried to pay (got the vibration and AP showed on screen) but payment failed with the Unable to verify this device message.
Yesterday at 6:45pm Pacific time I used AP without issues
joeyddr said:
The log in cache says disabling for 5 minutes , but it stays mounted. It also takes away root for apps like root explorer and busy box. I can open a terminal and su fine safety net fails, so it seems it half disables root on purenexus but never fully unmounts as df shoes the partition still mounted. Root comes back to all apps after 5 minutes
Click to expand...
Click to collapse
I get the same behavior on PureNexus
chrisc93 said:
I get the same behavior on PureNexus
Click to expand...
Click to collapse
May you give me the output of the following command after disabling root on PureNexus?
Code:
adb shell which su
joeyddr said:
The log in cache says disabling for 5 minutes , but it stays mounted. It also takes away root for apps like root explorer and busy box. I can open a terminal and su fine safety net fails, so it seems it half disables root on purenexus but never fully unmounts as df shoes the partition still mounted. Root comes back to all apps after 5 minutes
Click to expand...
Click to collapse
chrisc93 said:
I get the same behavior on PureNexus
Click to expand...
Click to collapse
@topjohnwu here's a logcat dump from my Nexus 5x running the latest Chroma rom, from the moment I hit the "Disable Root" button in the new Magisk Manager
Code:
08-09 09:34:51.652 19739 19739 D su : starting daemon client 10201 10201
08-09 09:34:51.663 19741 19741 D su : connecting client 19738
08-09 09:34:51.678 19743 19743 D su : remote pid: 19738
08-09 09:34:51.690 19744 19744 D su : remote pts_slave:
08-09 09:34:51.703 19745 19745 D su : remote uid: 10201
08-09 09:34:51.714 19746 19746 D su : remote req pid: 18133
08-09 09:34:51.721 19747 19747 D su : remote args: 1
08-09 09:34:51.728 19751 19751 D su : su invoked.
08-09 09:34:51.733 19749 19749 D su : waiting for child exit
08-09 09:34:51.739 19752 19752 W su : hacks: Testing (com.keramidas.TitaniumBackup:0:10054)
08-09 09:34:51.764 19753 19753 D su : db allowed
08-09 09:34:51.776 19754 19754 W su : hacks: Testing (com.keramidas.TitaniumBackup:10201), 44451
08-09 09:34:51.792 19756 19756 D su : 10201 /magisk/phh/su executing 0 /system/bin/sh using binary /system/bin/sh : sh
08-09 09:34:51.822 19759 19759 I init : type=1400 audit(0.0:6447): avc: denied { execute_no_trans } for path="/sbin/magic_mask.sh" dev="rootfs" ino=9569 scontext=u:r:init:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1
08-09 09:34:51.832 19759 19759 I magic_mask.sh: type=1400 audit(0.0:6448): avc: denied { setenforce } for scontext=u:r:init:s0 tcontext=u:object_r:kernel:s0 tclass=security permissive=1
08-09 09:34:51.832 352 352 W auditd : type=1404 audit(0.0:6449): enforcing=0 old_enforcing=1 auid=4294967295 ses=4294967295
08-09 09:34:51.838 19760 19760 E su : unable to read int: 0
08-09 09:34:51.839 19761 19761 E su : unable to read int: 0
08-09 09:34:51.835 19762 19762 I getprop : type=1400 audit(0.0:6450): avc: denied { write } for path="pipe:[178468]" dev="pipefs" ino=178468 scontext=u:r:toolbox:s0 tcontext=u:r:init:s0 tclass=fifo_file permissive=1
08-09 09:34:51.842 19762 19762 I getprop : type=1400 audit(0.0:6451): avc: denied { getattr } for path="pipe:[178468]" dev="pipefs" ino=178468 scontext=u:r:toolbox:s0 tcontext=u:r:init:s0 tclass=fifo_file permissive=1
08-09 09:34:51.845 19759 19759 I magic_mask.sh: type=1400 audit(0.0:6452): avc: denied { append } for name="magisk.log" dev="mmcblk0p40" ino=15 scontext=u:r:init:s0 tcontext=u:object_r:cache_file:s0 tclass=file permissive=1
08-09 09:34:51.860 19763 19763 I Magisk : Temp unroot for 60 seconds
08-09 09:34:51.858 19759 19759 I magic_mask.sh: type=1400 audit(0.0:6453): avc: denied { execute } for name="busybox" dev="mmcblk0p45" ino=212578 scontext=u:r:init:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=1
08-09 09:34:51.858 19764 19764 I magic_mask.sh: type=1400 audit(0.0:6454): avc: denied { execute_no_trans } for path="/data/busybox/busybox" dev="mmcblk0p45" ino=212578 scontext=u:r:init:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=1
08-09 09:34:51.902 19764 19764 I killall : type=1400 audit(0.0:6455): avc: denied { signal } for scontext=u:r:init:s0 tcontext=u:r:su_daemon:s0 tclass=process permissive=1
08-09 09:34:52.227 479 479 I SELinux : SELinux: Loaded service_contexts from /service_contexts.
08-09 09:34:52.229 479 479 I SELinux : avc: received setenforce notice (enforcing=0)
08-09 09:34:52.232 479 479 I SELinux : avc: received setenforce notice (enforcing=1)
Like the PN users above, it results in a half-unrooted state; apps like Titanium Backup can't obtain root, but the superuser daemons are still running:
Code:
[email protected]:/ # getprop | grep magis
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[magisk.phhsu]: [0]
[magisk.post-fs-data]: [1]
[magisk.timeout]: [60]
[email protected]:/ # ps | grep phh
u0_a112 17151 540 1477496 43768 SyS_epoll_ 7fa11841b4 S me.phh.superuser
[email protected]:/ # which su
/system/xbin/su
Just flashed this on my 6P. When I disable root, it allows me to add a card on Android Pay, so I assume it's also going to work payments. I can't test it right now, but will report back when I have the chance. Looks promising though!
Sent from my Nexus 6P using Tapatalk
Related
Okay, I must admit I'm stuck.
Long story short I wanted to bring back double tap to wake to shamu, found the code that enables it in the power_shamu.c, and it works, but only if SELinux is set to permissive. I'm constantly getting:
Code:
09-11 10:21:06.128 885 885 I PowerManagerSer: type=1400 audit(0.0:424): avc: denied { write } for name="tsp" dev="sysfs" ino=14209 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs_mmi_touch:s0 tclass=file permissive=1
09-11 10:21:06.128 885 885 I PowerManagerSer: type=1400 audit(0.0:425): avc: denied { open } for path="/sys/devices/f9966000.i2c/i2c-1/1-004a/tsp" dev="sysfs" ino=14209 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs_mmi_touch:s0 tclass=file permissive=1
(permissive is 1 now, but it fails when it's 0)
I've tried to use 'audit2allow', and it recommended me changes to the 'system_server.te':
Code:
allow system_server sysfs_mmi_touch:dir search;
Built it, flashed it, but nothing changed.
I used kernel adiutor to set d2w on my N6.
or you can google selinux mode changer apk, then download and install it, then open the app and change to permissive.
simms22 said:
or you can google selinux mode changer apk, then download and install it, then open the app and change to permissive.
Click to expand...
Click to collapse
I changed to permissive through adb to check it if it works. No, I'm looking for a solution to make it work as I build AOSP. That's why I was looking for someone who understands the obscure mindset of SELinux.
Just my 2 cents here, no expert in SeLinux but you probably need to add write access to :file (and maybe :dir). So maybe it should be like this:
system_server sysfs_mmi_touch:file write
system_server sysfs_mmi_touch:file read //maybe
system_server sysfs_mmi_touch:file open
GOOD LUCK
Thanks a lot, @danielt021! Actually it was what I was trying to do, but since when I did it, nothing happened, it only could mean that I was doing something wrong. And I was doing something wrong, I was only flashing system, without boot. Now I've flashed boot, and it is working. I have double tap to wake that can be switched on/off in Display Settings, while Enfoced. Thanks again.
I'm on a Moto G5 Plus stock systemlessly rooted with custom kernel.
I noticed in the Magisk logs that the app was unable to write to /magisk/.core/hidelist -- That's because the subfolder simply wasn't there. The exact error was pretty obvious in the logs: fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory
So I created a new folder and set the permissions on it to rwxr-xr-x
Now when I set my list of apps to hide, it sticks on reboot.
I'm not sure why it doesn't get created in the first place. Other modules seem to be downloaded and written to /magisk just fine. Oh well. Hope this helps out some other people.
Thanks. Guess this works.
Can you please elaborate?
dunderball said:
I'm on a Moto G5 Plus stock systemlessly rooted with custom kernel.
I noticed in the Magisk logs that the app was unable to write to /magisk/.core/hidelist -- That's because the subfolder simply wasn't there. The exact error was pretty obvious in the logs: fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory
So I created a new folder and set the permissions on it to rwxr-xr-x
Now when I set my list of apps to hide, it sticks on reboot.
I'm not sure why it doesn't get created in the first place. Other modules seem to be downloaded and written to /magisk just fine. Oh well. Hope this helps out some other people.
Click to expand...
Click to collapse
Hi,
Can you please elaborate the steps. Sorry, I'm a noob. Where to create a new folder? How to set the permissions on it? to rwxr-xr-x ?
Thanks.
Clarification: "hidelist" is not a folder but a file (under /sbin/.core/img/.core) containing the apps and processes added to the MagiskHide list. The default permissions for the file is rw-rw-rw (666).
Not sure why a folder worked for the OP...
@sghegde87 If you can't get MagiskHide to work and you see the above mentioned errors, use a root capable file explorer and navigate to /sbin/.core/img/.core (make sure the setting to view hidden files and folders is enabled, or you won't see the .core directories). Create an empty file named hidelist (no extension) and then give it the above mentioned permission (666). In most file explorers you can do this by long-pressing the file and go to "details" or similar. Depends on the file explorer... I always recommend FX File Explorer.
Thanks for the quick response but..
Didgeridoohan said:
Clarification: "hidelist" is not a folder but a file (under /sbin/.core/img/.core) containing the apps and processes added to the MagiskHide list. The default permissions for the file is rw-rw-rw (666).
Not sure why a folder worked for the OP...
@sghegde87 If you can't get MagiskHide to work and you see the above mentioned errors, use a root capable file explorer and navigate to /sbin/.core/img/.core (make sure the setting to view hidden files and folders is enabled, or you won't see the .core directories). Create an empty file named hidelist (no extension) and then give it the above mentioned permission (666). In most file explorers you can do this by long-pressing the file and go to "details" or similar. Depends on the file explorer... I always recommend FX File Explorer.
Click to expand...
Click to collapse
@Didgeridoohan:- Thank you for the quick reply and detailed description. Here is what happened:- There is already a file name 'hidelist' in /sbin/.core/img/.core directory. So, I deleted it and created a new one and set the permission to 666.
I added all the apps that has to be magiskhide. I checked this hidelist file and it is updated accordingly after I tick the apps in Magisk manager.
However, after reboot, again, the apps preference is reset.. All hide settings are reset. Below is the Log file from Magisk after reboot if that helps.
Any idea what might be causing this issue?
Device:- Lenovo P2 with Stock rom_S251 - Rooted via Magisk.
Code:
02-14 15:51:58.289 437 437 I Magisk : Magisk v16.0(1600) daemon started
02-14 15:51:58.298 437 442 I Magisk : ** post-fs mode running
02-14 15:52:01.565 437 682 I Magisk : ** post-fs-data mode running
02-14 21:22:01.571 437 682 I Magisk : * Creating /sbin overlay
02-14 21:22:01.572 437 682 I Magisk : * Mounting mirrors
02-14 21:22:01.573 437 682 I Magisk : mount: /sbin/.core/mirror/system
02-14 21:22:01.573 437 682 I Magisk : link: /sbin/.core/mirror/vendor
02-14 21:22:01.574 437 682 I Magisk : bind_mount: /sbin/.core/mirror/bin
02-14 21:22:01.574 437 682 I Magisk : * Setting up internal busybox
02-14 21:22:01.586 437 682 I Magisk : * Mounting /data/adb/magisk.img
02-14 21:22:01.598 437 682 E Magisk : mount /dev/block/loop0->/sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.598 437 682 E Magisk : umount /sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.608 437 682 I Magisk : Resize /data/adb/magisk.img to -1854921600M
02-14 21:22:01.637 437 682 I Magisk : Create /data/adb/tmp.img with size -1854921600M
02-14 21:22:01.660 437 682 E Magisk : mount /dev/block/loop0->/dev/source failed with 22: Invalid argument
02-14 21:22:01.670 437 682 E Magisk : mount /dev/block/loop1->/sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.670 437 682 I Magisk : * Running post-fs-data.d scripts
02-14 21:22:01.671 437 682 I Magisk : * Running module post-fs-data scripts
02-14 21:22:01.671 437 682 I Magisk : * Loading modules
02-14 21:22:01.671 437 695 I Magisk : * Starting MagiskHide
02-14 21:22:01.671 437 695 I Magisk : hide_utils: Hiding sensitive props
02-14 21:22:01.671 437 695 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
02-14 21:22:01.671 437 695 I Magisk : hide_list add: [com.google.android.gms.unstable]
02-14 21:22:01.691 437 695 I Magisk : proc_monitor: init ns=mnt:[4026531840]
02-14 21:22:01.813 437 755 I Magisk : ** late_start service mode running
02-14 21:22:01.814 437 755 I Magisk : * Running service.d scripts
02-14 21:22:01.814 437 755 I Magisk : * Running module service scripts
02-14 21:22:03.538 437 695 I Magisk : proc_monitor: zygote ns=mnt:[4026533676] zygote64 ns=mnt:[4026533675]
03-06 12:56:00.383 437 695 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4625 ns=mnt:[4026533848])
03-06 12:56:24.289 437 695 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6244 ns=mnt:[4026533862])
sghegde87 said:
@Didgeridoohan:- Thank you for the quick reply and detailed description. Here is what happened:- There is already a file name 'hidelist' in /sbin/.core/img/.core directory. So, I deleted it and created a new one and set the permission to 666.
I added all the apps that has to be magiskhide. I checked this hidelist file and it is updated accordingly after I tick the apps in Magisk manager.
However, after reboot, again, the apps preference is reset.. All hide settings are reset. Below is the Log file from Magisk after reboot if that helps.
Any idea what might be causing this issue?
Device:- Lenovo P2 with Stock rom_S251 - Rooted via Magisk
Click to expand...
Click to collapse
All I can say is that you've got some kind of loop mount issue...
What's the output when you run the mount command in a terminal emulator?
Yes you are right.
Didgeridoohan said:
All I can say is that you've got some kind of loop mount issue...
What's the output when you run the mount command in a terminal emulator?
Click to expand...
Click to collapse
Yep. It's a mount issue. The problem was F2FS data partition. I formatted it to EXT4 and everything is working just fine. Magisk works as expected only on EXT4 format type in Lenovo P2 stock ROM.
Thanks for the comment though!
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
hidelist deleted
It's not working on my Nexus 7 2013 deb tablet. Rebooting deletes hidelist. Please help. Thanks
jhford said:
It's not working on my Nexus 7 2013 deb tablet. Rebooting deletes hidelist. Please help. Thanks
Click to expand...
Click to collapse
This workaround was for devices with f2fs issues, in late 2017. Your device don't use f2fs (normally) and much use happened with Magisk since (the hidelist file is no longer used, as an example).
100% sure you've got something else going on (unless you're on a really old Magisk release).
Didgeridoohan said:
This workaround was for devices with f2fs issues, in late 2017. Your device don't use f2fs (normally) and much use happened with Magisk since (the hidelist file is no longer used, as an example).
100% sure you've got something else going on (unless you're on a really old Magisk release).
Click to expand...
Click to collapse
My problem is that the Spectrum TV app will not run on a rooted device. So, I use Magisk Hide, but Safetynet fails on each reboot. So, the temporary fix is to untick Hide in Settings, reboot, retick hide, rerun Safetynet, which always passes, and Spectrum TV app also works. PITA. Do you know of a permanent solution?
Thanks
jhford said:
My problem is that the Spectrum TV app will not run on a rooted device. So, I use Magisk Hide, but Safetynet fails on each reboot. So, the temporary fix is to untick Hide in Settings, reboot, retick hide, rerun Safetynet, which always passes, and Spectrum TV app also works. PITA. Do you know of a permanent solution?
Thanks
Click to expand...
Click to collapse
That just means things aren't working as intended on your device. More info is needed:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Didgeridoohan said:
That just means things aren't working as intended on your device. More info is needed:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Click to expand...
Click to collapse
My Magisk log is attached.
jhford said:
My Magisk log is attached.
Click to expand...
Click to collapse
Update. I uninstalled Magisk manager and installed the Canary version, but the problem remains. Neither Safetynet nor Magisk Hide work unless I do the following: disable Magisk Hide, reboot, and enable Magisk Hide. I'm glad it works, at least, but the rebooting is a PITA.
I updated magisk 15.1 to magisk 18.0 but now the root is not detected as there is no prompt dialog in any apps that tries to access root privilege.
I updated using magisk manager 6.1.0(recommended method). Root didn't work.Then I tried uninstalling and flashing from TWRP.Nothing happens.
So I completely uninstalled and rolled back to magisk 15.1.
That works but I want to use a module that requires magisk >15.3 . So I need that update.
When app tries to access root log reports error
Magisk : write failed with 32: Broken pipe
Complete Log:
02-03 23:08:23.891 2032 2032 I Magisk : * Creating /sbin overlay
02-03 23:08:23.957 2034 2034 I Magisk : Magisk v18.0(18000) daemon started
02-03 23:08:23.968 2034 2035 I Magisk : ** post-fs-data mode running
02-03 23:08:23.968 2034 2035 I Magisk : * Initializing Magisk environment
02-03 23:08:24.018 2034 2035 I Magisk : * Mounting mirrors
02-03 23:08:24.020 2034 2035 I Magisk : mount: /sbin/.magisk/mirror/system
02-03 23:08:24.020 2034 2035 I Magisk : link: /sbin/.magisk/mirror/vendor
02-03 23:08:24.020 2034 2035 I Magisk : bind_mount: /sbin/.magisk/mirror/bin
02-03 23:08:24.021 2034 2035 I Magisk : * Setting up internal busybox
02-03 23:08:24.265 2040 2040 I Magisk : Magisk v18.0(18000) logger started
02-03 23:08:24.416 2034 2035 I Magisk : * Mounting /data/adb/magisk.img
02-03 23:08:24.469 2034 2035 I Magisk : * Running post-fs-data.d scripts
02-03 23:08:24.469 2034 2035 I Magisk : * Running module post-fs-data scripts
02-03 23:08:24.469 2034 2035 I Magisk : * Loading modules
02-03 23:08:24.547 2034 2055 I Magisk : * Starting MagiskHide
02-03 23:08:24.547 2034 2055 I Magisk : hide_utils: Hiding sensitive props
02-03 23:08:24.547 2034 2055 I Magisk : hide_list add: [com.google.android.gms.unstable]
02-03 23:08:24.644 2034 2055 I Magisk : hide_list rm: [com.google.android.gms.unstable]
02-03 23:08:24.700 2034 2055 I Magisk : hide_list add: [com.google.android.gms/.droidguard.DroidGuardService]
02-03 23:08:25.421 2034 2222 I Magisk : ** late_start service mode running
02-03 23:08:25.422 2034 2222 I Magisk : * Running service.d scripts
02-03 23:08:25.426 2034 2222 I Magisk : * Running module service scripts
02-03 23:09:13.944 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[5087] ns=[4026533771]
02-03 23:09:45.854 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[6240] ns=[4026533760]
02-03 23:10:09.865 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[8455] ns=[4026533737]
02-03 23:12:59.931 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12427] ns=[4026533693]
02-03 23:13:10.484 12566 12566 E Magisk : write failed with 32: Broken pipe
02-03 23:13:34.599 12704 12704 E Magisk : write failed with 32: Broken pipe
02-03 23:13:47.188 13294 13294 W Magisk : su: request rejected (10160->0)
try removing magisk from battery optimization in android settings, then rebooting??
all the permission are given also updated to latest one STILL NOT WORKING
miura19882 said:
try removing magisk from battery optimization in android settings, then rebooting??
Click to expand...
Click to collapse
updated magisk manager to 7.0 and magisk to 18.1. Same issue
Also app is put in not optimized list in battery optimization
and in performance optimization app is allowed to run in background, allow the system to wake up and allowed to be awakened by other application.
No idea what your device is, so can't say if this is applicable or not, but make sure that the Manager isn't installed to external/adoptable storage. That has been known to cause quite a few issues...
mine wont work either on pixel 2 xl, coming from 18.0
downloads the apk for 7.0.0, says it needs additional setup and then fails. i flashed 18.1 so that is working, its just the manager thats giving me problems.
fixxxer0 said:
mine wont work either on pixel 2 xl, coming from 18.0
downloads the apk for 7.0.0, says it needs additional setup and then fails. i flashed 18.1 so that is working, its just the manager thats giving me problems.
Click to expand...
Click to collapse
same things happened on my oneplus 6t... after install magisk manager 7.0.0, it need addition setup but setup fails, when flashed 18.1 in magisk, it wrote unable to unpack boot
yathomasi said:
updated magisk manager to 7.0 and magisk to 18.1. Same issue
Also app is put in not optimized list in battery optimization
and in performance optimization app is allowed to run in background, allow the system to wake up and allowed to be awakened by other application.
Click to expand...
Click to collapse
Just make sure there is an exception under power saving in the battery settings
ArlenCheng said:
same things happened on my oneplus 6t... after install magisk manager 7.0.0, it need addition setup but setup fails, when flashed 18.1 in magisk, it wrote unable to unpack boot
Click to expand...
Click to collapse
not sure what happened, but it seems to have fixed itself?
i did remove the old manager, and remove all my modules, and several reboots... cant say exactly which one fixed the problem.
miura19882 said:
Just make sure there is an exception under power saving in the battery settings
Click to expand...
Click to collapse
OMG, IT WORKS! AFTER SETTINGS, IT CAN DIRECT BOOT IMAGE!:fingers-crossed:
yathomasi said:
updated magisk manager to 7.0 and magisk to 18.1. Same issue
Also app is put in not optimized list in battery optimization
and in performance optimization app is allowed to run in background, allow the system to wake up and allowed to be awakened by other application.
Click to expand...
Click to collapse
ArlenCheng said:
OMG, IT WORKS! AFTER SETTINGS, IT CAN DIRECT BOOT IMAGE!:fingers-crossed:
Click to expand...
Click to collapse
Sweet happy it worked out for you
Thank you so much !!! it worked for me too !!!! :highfive::victory::laugh::good:
miura19882 said:
Just make sure there is an exception under power saving in the battery settings
Click to expand...
Click to collapse
I don't find options for power saving and to put the app on exception on battery settings in my phone running Android Nougat
It's only for Oreo
hey fellas check this out:
if you have root but magisk is not prompting, under settings choose to hide magisk manager by repacking it with a random package name.
this fixed for me.
x_berzerker said:
hey fellas check this out:
if you have root but magisk is not prompting, under settings choose to hide magisk manager by repacking it with a random package name.
this fixed for me.
Click to expand...
Click to collapse
Did this, disabled the battery optimisation, rebooted a couple of times; still doesn't work (magisk 19.3, magisk manager 7.3.2, htc desire 820, stock android 6.0.1)
miura19882 said:
try removing magisk from battery optimization in android settings, then rebooting??
Click to expand...
Click to collapse
This worked for me as well!
I know its a bit late but I had the same problem and I fixed it by enabling the "Display pop-up windows while running in the background" option in the app settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im having the same problem but none of the suggested fixed here have worked. any further suggestions????
DarkAndBlue said:
I know its a bit late but I had the same problem and I fixed it by enabling the "Display pop-up windows while running in the background" option in the app settings.
Click to expand...
Click to collapse
That one fixed it for me on Android 9.
Im on 4.2.2 android
Installed it via patched boot img on adb
Facing same issue
I dont see any battery settings on settings app
Trying to uninstall and install app,just same
Help plz
now where the *beep* did this come from... I'm logging into my phone with ssh (magisk rooted, magisk sshd module installed, ssh pubkeys installed in the right places - in short "it used to work fine"), but all I get now is this output:
[email protected]:~> ssh [email protected]
X11 forwarding request failed on channel 0
/system/bin/sh: Permission denied
Connection to s8 closed.
where what why the f*ck
any ideas?
Hi everyone, looking for some guidance on magisk hide. I've searched for days but nothing yet, I'll try my best to explain my problem then I'll list my device and ROM etc after. So I've rooted my phone, installed magisk, updated everything within magisk, magisk hide works and hides my root from banking Netflix etc, modules install without a hitch and work fine BUT... When ever I try to hide magisk manager itself (different name etc) I get the error message "hide magisk failed." My logs show nothing related to it so no error codes or reasons it could be being blocked. I checked out John wus Twitter he had a post a while back explaining that Google play protect is blocking the installation and to disable it then enable it after magisk repacks. Most people there said it worked for them, but it isn't working for me. Things I've tried:
Uninstall magisk through the app and reinstall (twrp)
Unroot phone and reroot through twrp
Update OS
Wipe phone, downgrade OS reroot
Disable Google play through play store
Disable all Google services using service disabler app
Disable all Google services and miui security
Updated magisk to canary
Downgraded magisk to 19.4 (now back on latest build)
Deleted the magisk files in root browser
Renamed magisk files through twrp and through root browser
There may be a couple of other things I've tried Ive been at it for days lol. I'm hoping I'm just being really stupid and missing something and it's an easy fix, but googling it brings up mainly older posts, the fixes I find don't work for me, or people assume I'm asking about 'magisk hide' rather than 'hide magisk'. I would really appreciate any help people could give. Thank you
Phone details:
Redmi note 8 pro Global
Miui global 10.4.1 (pggmixm)
Android version 9
Security patch 2019-9-1
Magisk
20.2
Manager
7.4.1
(Canary)
You're mixing up the terminology a bit, which might explain why some have a hard time understanding what you're asking for. You're trying to hide the Manager, not Magisk.
Another thing you could try is if it's SELinux causing issues. Set it to permissive and try again (and don't forget to set it back to enforcing again afterwards). If it still fails, you'll need to provide at least a logcat showing when things go wrong.
Ah brilliant thanks I'll try that now n let u know yeah I thought I might be getting something wrong, it usually just works firs time so I've never actually had to actually look into how it works etc lol
Solved!
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
m4rkj4y said:
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
Click to expand...
Click to collapse
We're always learning on XDA [emoji4]
I'm always happy to learn, I usually get so mad with getting something wrong I overlook the simple things lol
m4rkj4y said:
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
Click to expand...
Click to collapse
I have the same problem in note 8 pro. Could you provide the details how to solve the problem? Many thx
m4rkj4y said:
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
Click to expand...
Click to collapse
Have you solved the problem?
Teach me please
log:
--------- beginning of main
--------- beginning of system
03-19 18:48:48.508 456 456 I Magisk : Magisk v20.3(20300) daemon started
03-19 18:48:48.508 456 456 I Magisk : * Device API level: 28
03-19 18:48:58.498 456 457 I Magisk : ** post-fs-data mode running
03-19 18:48:58.500 456 457 I Magisk : * Initializing Magisk environment
03-19 18:48:58.515 456 457 E Magisk : su: cannot find manager
03-19 18:48:58.516 456 457 I Magisk : * Mounting mirrors
03-19 18:48:58.518 456 457 I Magisk : mount: /sbin/.magisk/mirror/vendor
03-19 18:48:58.518 456 457 I Magisk : mount: /sbin/.magisk/mirror/data
03-19 18:48:58.518 456 457 I Magisk : link: /sbin/.magisk/mirror/system
03-19 18:48:58.518 456 457 I Magisk : link: /sbin/.magisk/mirror/product
03-19 18:48:58.518 456 457 I Magisk : * Setting up internal busybox
03-19 18:48:58.528 456 457 I Magisk : * Running post-fs-data.d scripts
03-19 18:48:58.530 456 457 I Magisk : * Running module post-fs-data scripts
03-19 18:48:58.530 456 457 I Magisk : * Loading modules
03-19 18:48:58.535 456 466 I Magisk : * Starting MagiskHide
03-19 18:48:58.535 456 466 I Magisk : hide_policy: Hiding sensitive props
03-19 18:48:58.535 456 466 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
03-19 18:48:58.538 456 466 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
03-19 18:48:59.178 456 738 I Magisk : ** late_start service mode running
03-19 18:48:59.179 456 738 I Magisk : * Running service.d scripts
03-19 18:48:59.186 456 738 I Magisk : * Running module service scripts
03-19 18:49:07.765 456 2144 I Magisk : ** boot_complete triggered
03-19 18:49:07.816 2159 2159 I Magisk : apk_install: /data/magisk.apk
03-19 18:49:26.698 456 466 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[5699] UID=[10010]
03-19 18:49:30.324 6360 6360 I Magisk : apk_install: Success
03-19 18:49:44.754 456 466 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[8515] UID=[10010]
Work
Hide magisk manager App
1.Set Selinux permissive.
Open terminal type
su
setenforce 0
2.Force close magisk manager from settings
3.Open magisk manager and go to settings click on hide magisk manager and put any name then ok ..and wait
Spiderlll said:
Hide magisk manager App
1.Set Selinux permissive.
Open terminal type
su
setenforce 0
2.Force close magisk manager from settings
3.Open magisk manager and go to settings click on hide magisk manager and put any name then ok ..and wait
Click to expand...
Click to collapse
Great! Works for me! :good:
How to Change SeLinux Mod
I have the same problem.Can't Hide Magisk manager.
I don't know how to change the SeLinux Mod.Can you help me ?
Download app Terminal from play store and follow the previous steps
Hi sir
Same problem the magisk manager hiding package name process is not working evenif the device selinux setted to permissive
How to fix.
dlnraja said:
Hi sir
Same problem the magisk manager hiding package name process is not working evenif the device selinux setted to permissive
How to fix.
Click to expand...
Click to collapse
Did you check whether your Google play protect feature is turned off? That was my issue. Apparently it stops Magisk Manager from repackaging itself. Once in sorted that out, it works! Golden!
Not working in Mi 8 Lite, Android 10, Ver: 20.4
Changing Selinux didn't help for me it was still giving error though i find a way you can disable play protect and try , it worked for me afterwards you can enable it again.
shackled said:
Did you check whether your Google play protect feature is turned off? That was my issue. Apparently it stops Magisk Manager from repackaging itself. Once in sorted that out, it works! Golden!
Click to expand...
Click to collapse
This one works for me
shackled said:
Did you check whether your Google play protect feature is turned off? That was my issue. Apparently it stops Magisk Manager from repackaging itself. Once in sorted that out, it works! Golden!
Click to expand...
Click to collapse
That's it! That point should be included in the basic install procedure.
Thanks
I have changed selinux to permissive , Disabled play protect, but still getting the error. I am using realme 3 pro. Please help.