Hello, welcome to the beta Magisk thread! First check the main thread before starting.
I expect users reporting to at least have basic debug skills, this thread is heavily moderated so refrain from spamming with "useless" reports!
Latest Magisk Beta: v16.7 (code: 1671)
Bundled Magisk Manager: v5.8.3
Release Note | Changelogs | Download
If you need a clean start, use the uninstaller in the main thread to uninstall any verison of Magisk installation
Symptoms and Diagnose Procedure:
Installing Magisk fails:
If you're flashing in TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
If you're installing in MagiskManager: Choose to save logs after installation and upload
I want to report a Magisk bug:
Magisk logs are placed in /cache/magisk.log
If you face any issue, please upload /cache/magisk.log
Starting from v16.6, /data/adb/magisk_debug.log is NOT USED anymore!
Magisk Manager is crashing:
Grab LOGCAT (NOT magisk logs) when the crash occurs, upload the logs and report how to reproduce
SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
If it worked in previous versions, please at least upload /cache/magisk.log
Please do NOT SPAM the forum with these kind of issues! It is NOT a priority to fix
Donation
I spent endless hours to create Magisk. If you like my work, feel free to donate.
https://www.paypal.me/topjohnwu
reserved
great !!
Sent from my SM-G9350 using Tapatalk
I was just about to compile latest build once android studio finished updating! This is very exciting!
Samsung Galaxy Note 5
N920TUVU4EQE1
Stock boot or Modded
TWRP Latest 3.1
JonathanRAZ said:
Samsung Galaxy Note 5
N920TUVU4EQE1
Stock boot or Modded
TWRP Latest 3.1
Click to expand...
Click to collapse
Did you not know read? is the first line else..
Symptoms and Diagnose Procedure:
Flashing the zip in custom recovery fails:
Most likely your device's boot image is not supported
Upload the recovery logs (pull file in /tmp/recovery.log, or select "Advanced > Copy Log" in TWRP and upload)
Click to expand...
Click to collapse
Deic said:
Did you not know read? is the first line else..
Click to expand...
Click to collapse
No i dont and i forgot to upload it so
After full uninstall using 170608 uninstaller, Magisk 13 installing failed. But install 12 version and dirty flash 13 version, it seems working.
And i don't know if you know this problem, magiskhide doesn't work with MIUI Nougat roms..
Logs attached.
Thanks
vsc0705 said:
And i don't know if you know this problem, magiskhide doesn't work with MIUI Nougat roms.
Click to expand...
Click to collapse
About the miui part, are you talking specifically about the safetynet? If yes, have you tried that module already? (just asking since I don't own a xiaomi device, I'm not sure if the module will work with v13 tho):
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
abacate123 said:
About the miui part, are you talking specifically about the safetynet? If yes, have you tried that module already? (just asking since I don't own a xiaomi device, I'm not sure if the module will work with v13 tho):
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Click to expand...
Click to collapse
On miui nougat, magiskhide completly not work not only safetynet.
Even magiskhide is activated, apps can request root permission and grant.
I already tried that module..
나의 Redmi Note 4X 의 Tapatalk에서 보냄
vsc0705 said:
On miui nougat, magiskhide completly not work not only safetynet.
Even magiskhide is activated, apps can request root permission and grant.
I already tried that module..
Click to expand...
Click to collapse
Hmm, thanks for the report then. Mine is aosp and everything on this build works great, as always.
Code:
D/Magisk: client: connect fail, try launching new daemon process
E/Magisk: start daemon failed with 111: Connection refused
magisk_debug.log
vsc0705 said:
After full uninstall using 170608 uninstaller, Magisk 13 installing failed. But install 12 version and dirty flash 13 version, it seems working.
And i don't know if you know this problem, magiskhide doesn't work with MIUI Nougat roms..
Logs attached.
Thanks
Click to expand...
Click to collapse
Same here on a Meizu M2 Note running LineageOS 14.1
If you clean flash a rom and then try flashing the V13 it fails.
I flashed v12 and then dirty flashed v13 and it worked.
In my case, on LOS based roms and AOSP based roms like RR, AOSPEXTENDED, magsikhide works perfectly.
I think this is related with kernel..
It seems magisk can't detect running apps.
But if it is possible i wanna use magiskhide with stock miui rom.[emoji1]
나의 Redmi Note 4X 의 Tapatalk에서 보냄
Samsung Galaxy Note 5
Deic said:
magisk_debug.log
Click to expand...
Click to collapse
Same problem here.
aLexzkter said:
Same here on a Meizu M2 Note running LineageOS 14.1
If you clean flash a rom and then try flashing the V13 it fails.
I flashed v12 and then dirty flashed v13 and it worked.
Click to expand...
Click to collapse
Same here. Oneplus one running unofficial LineageOS
Interesting situation, I tried all combinations of flashing and couldn't get it to work, I was on unofficial v13 fine, and official 12 worked as well, 13 wasn't.
I decided to try and get what logs I could, and out of curiosity tried `su` in terminal emulator from the phone and got a "connection refused" error from sudaemon, so I opened an ad shell and to my surprise had root in that shell! So I ran su for kicks and opened magisk manager again, and all was well! It said I had v13 installed, etc, very odd, not sure what to make of it.
I'm on a Nexus 6p, dirty unicorns 11.4 weekly and flash kernel. Magisk log attached which shows the connection refused errors and then it working after I run su from adb.
Sent from my Nexus 6P using XDA Labs
Captain_Throwback said:
Same problem here.
Click to expand...
Click to collapse
I did a script in post-fs-data.d that runs su daemon if is not running and didn't work... I see what when flash v13 the first time and immediately boot you launch Magisk Manager fastly, you have got root, but after the apk is reinstalled automatically and lost root.
Code:
--------- beginning of main
D/Magisk ( 248): client: connect fail, try launching new daemon process
I/Magisk ( 249): Magisk v13.0(0980cb6) daemon started
D/Magisk ( 249): sepol: Starting large patch thread
I/Magisk ( 249): ** post-fs mode running
I/Magisk ( 249): ** post-fs-data mode running
D/Magisk ( 249): resetprop: Initializing...
I/Magisk ( 249): * Mounting /data/magisk.img
I/Magisk ( 249): * Running post-fs-data.d scripts
I/Magisk ( 249): post-fs-data.d: exec [su-daemon.sh]
I/Magisk ( 249): * Loading modules
I/Magisk ( 249): custom-module: constructing magic mount structure
I/Magisk ( 249): Fdroid-Priv: loading [system.prop]
D/Magisk ( 249): resetprop: Load prop file [/magisk/Fdroid-Priv/system.prop]
I/Magisk ( 249): Fdroid-Priv: constructing magic mount structure
I/Magisk ( 249): EmojiOne-systemless: constructing magic mount structure
I/Magisk ( 249): Greenify4Magisk: constructing magic mount structure
--------- beginning of system
D/Magisk ( 336): client: connect fail, try launching new daemon process
I/Magisk ( 343): Magisk v13.0(0980cb6) daemon started
D/Magisk ( 343): sepol: Starting large patch thread
I/Magisk ( 343): ** late_start service mode running
D/Magisk ( 343): su: request from client: 11
D/Magisk ( 343): su: request from uid=[10334] (#1)
D/Magisk ( 343): su: collector started
D/Magisk ( 343): su: wait_result waiting for 3433
D/Magisk ( 3433): su: child process started
D/Magisk ( 3433): su: argc=[2]
D/Magisk ( 3433): su: argv[0]=[su]
D/Magisk ( 3433): su: argv[1]=[-v]
D/Magisk ( 3433): su: cwd=[/]
D/Magisk ( 3433): su: pts_slave=[]
D/Magisk ( 343): su: return code to client: 0
D/Magisk ( 343): su: request from client: 12
D/Magisk ( 343): su: request from uid=[10334] (#1)
D/Magisk ( 343): su: wait_result waiting for 3437
D/Magisk ( 3437): su: child process started
D/Magisk ( 3437): su: argc=[1]
D/Magisk ( 3437): su: argv[0]=[su]
D/Magisk ( 3437): su: cwd=[/]
D/Magisk ( 3437): su: pts_slave=[]
D/Magisk ( 343): su: Client killed unexpectedly
D/Magisk ( 343): su: return code to client: 0
D/Magisk ( 343): su: request from client: 11
D/Magisk ( 343): su: request from uid=[10030] (#1)
D/Magisk ( 343): su_db: query policy=[2]
D/Magisk ( 343): su: wait_result waiting for 3676
D/Magisk ( 3676): su: child process started
D/Magisk ( 3676): su: argc=[3]
D/Magisk ( 3676): su: argv[0]=[su]
D/Magisk ( 3676): su: argv[1]=[-c]
D/Magisk ( 3676): su: argv[2]=[/system/bin/sh]
D/Magisk ( 3676): su: cwd=[/]
D/Magisk ( 3676): su: pts_slave=[]
E/Magisk ( 3673): read failed with 25: Not a typewriter
D/Magisk ( 6949): client: connect fail, try launching new daemon process
E/Magisk ( 6949): start daemon failed with 111: Connection refused
D/Magisk ( 6951): client: connect fail, try launching new daemon process
E/Magisk ( 6951): start daemon failed with 111: Connection refused
D/Magisk ( 6960): client: connect fail, try launching new daemon process
E/Magisk ( 6960): start daemon failed with 111: Connection refused
D/Magisk ( 7025): client: connect fail, try launching new daemon process
E/Magisk ( 7025): start daemon failed with 111: Connection refused
D/Magisk ( 7126): client: connect fail, try launching new daemon process
E/Magisk ( 7126): start daemon failed with 111: Connection refused
D/Magisk ( 7210): client: connect fail, try launching new daemon process
E/Magisk ( 7210): start daemon failed with 111: Connection refused
D/Magisk (10872): client: connect fail, try launching new daemon process
E/Magisk (10872): start daemon failed with 111: Connection refused
D/Magisk (10904): client: connect fail, try launching new daemon process
E/Magisk (10904): start daemon failed with 111: Connection refused
D/Magisk (11046): client: connect fail, try launching new daemon process
E/Magisk (11046): start daemon failed with 111: Connection refused
D/Magisk (11097): client: connect fail, try launching new daemon process
E/Magisk (11097): start daemon failed with 111: Connection refused
D/Magisk (12571): client: connect fail, try launching new daemon process
E/Magisk (12571): start daemon failed with 111: Connection refused
D/Magisk (12576): client: connect fail, try launching new daemon process
E/Magisk (12576): start daemon failed with 111: Connection refused
Maybe i am blind but where is tge magisk manager v5.0?
Sent from my SM-G930F using XDA-Developers Legacy app
Related
Hey Guys,
what is SafetyNet for? And does my MagiskHide doesnt work, cause I dont pass the SafetyNet-Check properly.
My Rooted-Satus is confirmed and I checked all Trouble-Shooting-Tips for passing SafetyNet-Check. No difference after Update Magisk to v14.0.
I have an Honor 8 FRD-L09 on B389 and Android 7.0. Maybe someone can help me. That would be awesome!
My log-file before Update:
Code:
--------- beginning of main
I( 339: 339) Magisk v13.6(1360) daemon started
I( 339: 342) ** post-fs mode running
I( 339: 519) ** post-fs-data mode running
I( 339: 519) * Mounting mirrors
I( 339: 519) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system
I( 339: 519) mount: /dev/block/bootdevice/by-name/vendor -> /dev/magisk/mirror/vendor
I( 339: 519) * Mounting /data/magisk.img
I( 339: 519) * Running post-fs-data.d scripts
I( 339: 519) * Running module post-fs-data scripts
I( 339: 519) * Loading modules
I( 339: 534) * Starting MagiskHide
I( 339: 534) hide_utils: Hiding sensitive props
I( 339: 534) hide_list add: [com.google.android.gms.unstable]
I( 339: 534) proc_monitor: init ns=mnt:[4026531840]
I( 339: 569) ** late_start service mode running
I( 339: 569) * Running service.d scripts
I( 339: 569) * Running module service scripts
I( 339: 534) proc_monitor: zygote ns=mnt:[4026532963] zygote64 ns=mnt:[4026532955]
Safetynet is Google's "root detection system" that blocks the ability to use certain apps if it detects you have root access. It is incorporated into apps like Android Pay, Mario Run by Nintendo, Pokemon Go, a few banking apps, etc.
paed808 said:
Safetynet is Google's "root detection system" that blocks the ability to use certain apps if it detects you have root access. It is incorporated into apps like Android Pay, Mario Run by Nintendo, Pokemon Go, a few banking apps, etc.
Click to expand...
Click to collapse
So I have to pass thatcheck to use MaskHide. I have some banking apps, that doesnt work with my root. Even woithout root just unlocked bootloader they dont work.
Yes, you need to pass safetynet. You could try this module. "Universal Safetynet Fix". Maybe it'll help.
Also, don't install xposed if you want to pass safetynet.
paed808 said:
Yes, you need to pass safetynet. You could try this module. "Universal Safetynet Fix". Maybe it'll help.
Also, don't install xposed if you want to pass safetynet.
Click to expand...
Click to collapse
Universal Safetynet Fix didnt work. And I dont have installed xposed. That sucks.
Blenderhead69 said:
Universal Safetynet Fix didnt work. And I dont have installed xposed. That sucks.
Click to expand...
Click to collapse
Use beta version, stable is oudated
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
used that one. didnt work.
SchweGELBin said:
If in Safety Net stands like me:
basicIntegrity Passed
ctsProfile Failed
evalrype basic
Check this post.
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
Download Zip (Direct dowoad)
Add Zip as module in Magisk
Reboot
Finish
Maybe another thing is, if u fail is EdXposed.
There just download the Canary Version in the App.
Click to expand...
Click to collapse
Or better yet, how about visiting the actual XDA thread instead of websites that just try to generate traffic off of other peoples work:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
I recently upgraded from Magisk 12 to the latest 15 and found that the last 2 versions (1531 and 1540) seem to have compatibility issue with Xposed (89.2-sdk23-topjohnwu). With any of these 2 versions, Xposed Installer always show "installed but inactive" and none of the installed modules are enabled. Version 1530, however, works fine. Magisk Manager always show Magisk is installed successfully for all 3 versions. Root and SafetyNet (without Xposed) are successful too.
I've tried many advice but none of them fix this problem. Of course, I can stay in 1530 but I fear that I'm unable to try future versions.
My phone is a Xperia X Compact running Marshmallow stock ROM, kernel patched with TA PoC.
Magisk log:
Code:
02-13 11:52:29.367 4146 4146 I Magisk : Magisk v15.4(1540) daemon started
02-13 11:52:29.367 4146 4154 I Magisk : * Starting MagiskHide
02-13 11:52:29.368 4146 4154 I Magisk : hide_utils: Hiding sensitive props
02-13 11:52:29.368 4146 4154 I Magisk : hide_list: [com.google.android.gms.unstable]
02-13 11:52:29.402 4146 4154 I Magisk : proc_monitor: init ns=mnt:[4026531840]
02-13 11:52:30.453 4146 4154 I Magisk : proc_monitor: zygote ns=mnt:[4026535950] zygote64 ns=mnt:[4026535951]
02-13 12:03:26.742 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=9099 ns=mnt:[4026536040])
02-13 12:03:55.977 4146 10987 E Magisk : sqlite3 open failure: unable to open database file
02-13 12:03:55.977 4146 10987 E Magisk : su: cannot find requester
02-13 12:03:55.981 10989 10989 W Magisk : su: request rejected (10230->0)
02-13 12:04:10.040 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=11752 ns=mnt:[4026536015])
02-13 12:04:33.288 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13374 ns=mnt:[4026536031])
02-13 12:04:58.467 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=15340 ns=mnt:[4026536053])
02-13 12:07:11.041 4146 16761 E Magisk : sqlite3 open failure: unable to open database file
02-13 12:07:57.953 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=17502 ns=mnt:[4026536031])
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.
Hello,
it seems like my Magisk Hide option for some reason cannot be saved, if I enable Magisk Hide and go to custom Magisk Hide app list if I select an app and refresh, the app is unselected again. Also, it seems like the Magisk Hide option in the settings menu is also not being saved. I am using Magisk 19.1 and Magisk Manager 7.1.2 because with those versions I have been the most succesful, newest version does not even show Magisk Hide specific app list menu option. Android version is 5.0.1 and I am using Samsung Galaxy S4.
What could be wrong here? I can provide any additional information needed.
That was a bug a while back, but it's since been fixed. Likely after v19.1/v7.1.2 from the sound it it. Nothing to do unless you update...
Didgeridoohan said:
That was a bug a while back, but it's since been fixed. Likely after v19.1/v7.1.2 from the sound it it. Nothing to do unless you update...
Click to expand...
Click to collapse
Thanks so much I've been looking for answer for 2 full days I hope this works!
I have installed v20.0, but now when I select Magisk Hide it does not even show Magisk Hide menu option to select specific apps. What could be the problem?
No need to open another thread... We can continue the discussion here.
If you post your Magisk log it might be easier to help.
Didgeridoohan said:
If you post your Magisk log it might be easier to help.
Click to expand...
Click to collapse
How to get Magisk log?
Here is the log:
--------- beginning of system
--------- beginning of main
I/Magisk ( 280): Magisk v20.0(20000) daemon started
I/Magisk ( 280): * Device API level: 21
I/Magisk ( 280): ** post-fs-data mode running
I/Magisk ( 280): * Initializing Magisk environment
I/Magisk ( 280): * Mounting mirrors
I/Magisk ( 280): mount: /sbin/.magisk/mirror/system
I/Magisk ( 280): mount: /sbin/.magisk/mirror/data
I/Magisk ( 280): link: /sbin/.magisk/mirror/vendor
I/Magisk ( 280): * Setting up internal busybox
I/Magisk ( 280): * Running post-fs-data.d scripts
I/Magisk ( 280): ** late_start service mode running
I/Magisk ( 280): * Running service.d scripts
I/Magisk ( 280): ** boot_complete triggered
If you could install the current Canary debug build and provide that log it would be great. First, there's really no support for old releases and the Canary debug logs are much more verbose.
Canary builds can be found here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
I am using Canary build now, but when I go to logs, it says that the log is empty.
I rooted my Micromax Canvas 6 E485 kernel 3.10.65
with magisk
Root works fine and safety net passes but magiskhide does not hide root from any apps
I turned magisk hide off and on again and rebooted several times... then I flashed the stock rom and magisk at the same time also but nothing works
Then I saw the log and found that proc_monitor was missing after hidelist_init
--------- beginning of main
I/Magisk ( 263): Magisk 20.4(20400) daemon started
I/Magisk ( 263): * Device API level: 22
I/Magisk ( 263): ** post-fs-data mode running
I/Magisk ( 263): * Initializing Magisk environment
E/Magisk ( 263): su: cannot find manager
I/Magisk ( 263): * Mounting mirrors
I/Magisk ( 263): mount: /sbin/.magisk/mirror/system
I/Magisk ( 263): mount: /sbin/.magisk/mirror/data
I/Magisk ( 263): link: /sbin/.magisk/mirror/vendor
I/Magisk ( 263): * Setting up internal busybox
I/Magisk ( 263): * Running post-fs-data.d scripts
I/Magisk ( 263): * Running module post-fs-data scripts
I/Magisk ( 263): * Loading modules
--------- beginning of system
I/Magisk ( 263): ** late_start service mode running
I/Magisk ( 263): * Running service.d scripts
I/Magisk ( 263): * Running module service scripts
I/Magisk ( 263): ** boot_complete triggered
I/Magisk ( 2067): apk_install: /data/magisk.apk
I/Magisk ( 3310): apk_install: pkg: /data/magisk.apk
I/Magisk ( 3310): Success
I/Magisk ( 263): * Starting MagiskHide
I/Magisk ( 263): hide_policy: Hiding sensitive props
I/Magisk ( 263): hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
I/Magisk ( 263): hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
I/Magisk ( 263): hide_list add: [com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup]
Somebody pls fix this issue
Well, if SafetyNet passes that means that MagiskHide is working.
I'm assuming that you have Titanium Backup on the list to test if MagiskHide is working. Or is there another reason? Could TiBu still request superuser access even when on the Hide list?
Is there any specific app that you are having issues with? If so, let us know which one for possible testing.
And lastly, have you made sure to repackage the Magisk Manager with a random package name (in the Manager settings). Usually necessary to hide from troublesome apps.
TB was just an example it happens with each and every app that asks for root access
--------- beginning of main
I/Magisk ( 263): Magisk 20.4(20400) daemon started
I/Magisk ( 263): * Device API level: 22
I/Magisk ( 263): ** post-fs-data mode running
I/Magisk ( 263): * Initializing Magisk environment
E/Magisk ( 263): su: cannot find manager
I/Magisk ( 263): * Mounting mirrors
I/Magisk ( 263): mount: /sbin/.magisk/mirror/system
I/Magisk ( 263): mount: /sbin/.magisk/mirror/data
I/Magisk ( 263): link: /sbin/.magisk/mirror/vendor
I/Magisk ( 263): * Setting up internal busybox
I/Magisk ( 263): * Running post-fs-data.d scripts
I/Magisk ( 263): * Running module post-fs-data scripts
I/Magisk ( 263): * Loading modules
--------- beginning of system
I/Magisk ( 263): ** late_start service mode running
I/Magisk ( 263): * Running service.d scripts
I/Magisk ( 263): * Running module service scripts
I/Magisk ( 263): ** boot_complete triggered
I/Magisk ( 2067): apk_install: /data/magisk.apk
I/Magisk ( 3310): apk_install: pkg: /data/magisk.apk
I/Magisk ( 3310): Success
I/Magisk ( 263): * Starting MagiskHide
I/Magisk ( 263): hide_policy: Hiding sensitive props
I/Magisk ( 263): hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
I/Magisk ( 263): hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
I/Magisk ( 263): hide_list add: [com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup]
I/Magisk ( 263): hide_list add: [com.joeykrim.rootcheck/com.joeykrim.rootcheck]
I/Magisk ( 263): hide_list add: [com.joeykrim.rootcheck/com.joeykrim.rootcheck:adnw]
I/Magisk ( 263): hide_list add: [com.speedsoftware.rootexplorer/com.speedsoftware.rootexplorer]
I/Magisk ( 263): hide_list add: [com.termux/com.termux]
You see I have kept root checker and termux too on the list still it grants root access to these apps
Yes I have already tried to repackage it with different names
I have heard somewhere that proc_monitor identifies which app is running in background to stop its root access but that isn't happening in my case because it doesn't show up when I open the apps I want to hide root with........ Also I have tried checking the catlog with this command
logcat -b events -v raw -t 10
And it doesn't give me any error so the issue is not even with the kind of kernel I have
I think there is something wrong with the way the device boots
Here is my stock boot image
http://www.mediafire.com/file/oijoa1cj4jx47sv/stock.img/file
Edit:Forgot to mention that the device had forceencrypt before so I edited the fstab file and changed forceencrypt to encryptable and thereafter I flashed magisk... the device is decrypted now but the above issue persists
Start by installing the Canary debug release. Easiest way is to install the Canary Manager and then switch to the debug update channel.
That way we might see more of what's going on in the logs, and maybe things will even work.
--------- beginning of main
I/Magisk ( 262): Magisk 2aede977(20407) daemon started
I/Magisk ( 262): * Device API level: 22
D/Magisk ( 262): resetprop: getprop [ro.crypto.state]: [unencrypted]
I/Magisk ( 262): ** post-fs-data mode running
I/Magisk ( 262): * Initializing Magisk environment
I/Magisk ( 262): * Mounting mirrors
I/Magisk ( 262): mount: /sbin/.magisk/mirror/system
I/Magisk ( 262): mount: /sbin/.magisk/mirror/data
I/Magisk ( 262): link: /sbin/.magisk/mirror/vendor
I/Magisk ( 262): * Setting up internal busybox
I/Magisk ( 262): * Running post-fs-data.d scripts
I/Magisk ( 262): bind_mnt: /sbin/.magisk/modules <- /sbin/.magisk/mirror/data/adb/modules
I/Magisk ( 262): * Running module post-fs-data scripts
I/Magisk ( 262): * Loading modules
D/Magisk ( 262): magiskdb: query magiskhide=[1]
I/Magisk ( 262): * Starting MagiskHide
I/Magisk ( 262): hide_policy: Hiding sensitive props
D/Magisk ( 262): resetprop: getprop [ro.debuggable]: [0]
D/Magisk ( 262): resetprop: getprop [ro.secure]: [1]
D/Magisk ( 262): resetprop: getprop [ro.bootmode]: [unknown]
D/Magisk ( 262): hide_list: initialize
I/Magisk ( 262): hide_list init: [com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup]
I/Magisk ( 262): hide_list init: [jackpal.androidterm/jackpal.androidterm]
I/Magisk ( 262): hide_list init: [com.termux/com.termux]
I/Magisk ( 262): hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
I/Magisk ( 262): hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
D/Magisk ( 262): proc_monitor: nothing to monitor, wait for signal
--------- beginning of system
D/Magisk ( 262): proc_monitor: nothing to monitor, wait for signal
I/Magisk ( 262): ** late_start service mode running
I/Magisk ( 262): * Running service.d scripts
I/Magisk ( 262): * Running module service scripts
D/Magisk ( 262): proc_monitor: ptrace zygote PID=[320]
I/Magisk ( 262): ** boot_complete triggered
D/Magisk ( 262): su: request from pid=[5174], client=[10]
D/Magisk ( 262): su: request from uid=[10113]
D/Magisk ( 262): magiskdb: query magiskhide=[1]
D/Magisk ( 262): su: waiting child pid=[5178]
D/Magisk ( 5178): su: fork handler
D/Magisk ( 5178): su: use global namespace
D/Magisk ( 262): su: request from pid=[7012], client=[14]
D/Magisk ( 262): su: request from uid=[10116]
D/Magisk ( 262): magiskdb: query magiskhide=[1]
D/Magisk ( 262): magiskdb: query policy=[2] log=[1] notify=[1]
D/Magisk ( 262): su: waiting child pid=[7017]
D/Magisk ( 7017): su: fork handler
D/Magisk ( 7017): su: pts_slave=[/dev/pts/14]
D/Magisk ( 7017): su: use namespace of pid=[7012]
D/Magisk ( 262): su: return code=[0]
D/Magisk ( 262): su: return code=[1]
D/Magisk ( 262): su: request from pid=[7457], client=[15]
D/Magisk ( 262): su: request from uid=[10116]
D/Magisk ( 262): magiskdb: query magiskhide=[1]
D/Magisk ( 262): magiskdb: query policy=[2] log=[1] notify=[1]
D/Magisk ( 262): su: waiting child pid=[7462]
D/Magisk ( 7462): su: fork handler
D/Magisk ( 7462): su: pts_slave=[/dev/pts/14]
D/Magisk ( 7462): su: use namespace of pid=[7457]
D/Magisk ( 262): su: request from pid=[7605], client=[13]
D/Magisk ( 262): su: request from uid=[10113]
D/Magisk ( 262): magiskdb: query magiskhide=[1]
D/Magisk ( 262): su: waiting child pid=[7607]
D/Magisk ( 7607): su: fork handler
D/Magisk ( 7607): su: use global namespace
this is from the magisk canary(debug) log
also when I type this in terminal I get the following error "operation not permitted" tested both from android and windows with adb shell
[email protected]:/ $ su
[email protected]:/ # magiskhide status
MagiskHide is enabled
[email protected]:/ # magiskhide test
proc_monitor: ptrace zygote PID=[320]
ptrace 320 failed with 1: Operation not permitted
1|[email protected]:/ # magiskhide test
proc_monitor: ptrace zygote PID=[320]
ptrace 320 failed with 1: Operation not permitted
When running "magiskhide test" without su permission it shows
[email protected]:/$ magiskhide test
proc_monitor: nothing to monitor, wait for signal