[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)

Status
Not open for further replies.

topjohnwu

Senior Recognized Developer / Recognized Contribut
Jan 31, 2012
1,849
60,700
0
Taipei
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
 
Last edited:

Deic

Senior Member
Feb 4, 2012
540
982
0
Madrid
www.xiaomiadictos.com
Samsung Galaxy Note 5
N920TUVU4EQE1
Stock boot or Modded
TWRP Latest 3.1
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)
 
Last edited:

vsc0705

Member
Feb 4, 2011
16
12
0
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
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에서 보냄
 
  • Like
Reactions: MrZentroRethKid

abacate123

Senior Member
Feb 22, 2015
1,266
1,800
153
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..
Hmm, thanks for the report then. Mine is aosp and everything on this build works great, as always. :)
 

aLexzkter

Senior Member
Sep 21, 2010
648
173
73
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
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.
 

vsc0705

Member
Feb 4, 2011
16
12
0
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에서 보냄
 

Rakuu

Senior Member
Jun 16, 2014
2,410
818
0
Houston
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
 

Attachments

  • Like
Reactions: ikjadoon

Deic

Senior Member
Feb 4, 2012
540
982
0
Madrid
www.xiaomiadictos.com
Same problem here.
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
 

Attachments

Last edited:
Status
Not open for further replies.