FORUMS
Remove All Ads from XDA

[BETA][2018.4.29] Magisk v16.4 (1642)

1,790 posts
Thanks Meter: 44,455
 
By topjohnwu, Recognized Developer / Recognized Contributor on 7th June 2017, 10:36 PM
Post Reply Email Thread
8th June 2017, 03:49 AM |#21  
Senior Member
Thanks Meter: 660
 
More
Quote:
Originally Posted by Black_Focus_X

Maybe i am blind but where is tge magisk manager v5.0?

Sent from my SM-G930F using XDA-Developers Legacy app

It's inside the zip..

Sent from my MI 5 using Tapatalk
The Following 6 Users Say Thank You to teddy0209 For This Useful Post: [ View ] Gift teddy0209 Ad-Free
 
 
8th June 2017, 04:31 AM |#22  
Deic's Avatar
Senior Member
Flag Madrid
Thanks Meter: 962
 
Donate to Me
More
Quote:
Originally Posted by Deic

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

the "--daemon" argument doesn't exist /facepalm, I guess the new daemon is "magisk --post-fs" or IDK...

BTW in a reboot Magisk and MagiskSU worked magiskally, but didn't mount system files of modules, in /dev is only com.topjohnwu.magisk folder (a empty folder)..

magisk_debug.log

---EDIT---
more issues:
• post-fs-data.sh scripts of modules aren't running..
• Scripts aren't running if not correct permissions
8th June 2017, 05:44 AM |#23  
MitoTakatori's Avatar
Senior Member
Flag Quezon City
Thanks Meter: 465
 
More
Hi guys. So this is my report regarding Magisk v13:

Device: SM-G935FD
ROM: SuperMan-Rom V2.5.0 by @Tkkg1994
Kernel: Outsider Kernel V2.2.1 by @kylothow

So I followed the steps in OP regarding on how to update and encountered the same error/s that were reported here.

But dirty flashing goes well. Will there be any problems when dirty flash is done?
8th June 2017, 06:52 AM |#24  
Deic's Avatar
Senior Member
Flag Madrid
Thanks Meter: 962
 
Donate to Me
More
• Magisk Hide doesn't work until enable/disable twice from the manager

magiskhide_debug.log

in this case break Magisk and root, is the first time after of many times.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2017-06-08-07-48-15-129_com.topjohnwu.magisk.png
Views:	2262
Size:	80.7 KB
ID:	4174720  
8th June 2017, 07:08 AM |#25  
Senior Member
Flag Keszthely, Hungary
Thanks Meter: 60
 
Donate to Me
More
For me on the latest open beta OxygenOS on the OnePlus 3 everything works well and even better than on Magisk 12.
Tried both on the stock kernel and on RenderKernel.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20170608-080635.png
Views:	2106
Size:	145.5 KB
ID:	4174726  
The Following User Says Thank You to BolintsMiki For This Useful Post: [ View ] Gift BolintsMiki Ad-Free
8th June 2017, 07:20 AM |#26  
Member
Thanks Meter: 4
 
More
I tried to install the new beta version and twrp said it was an invalid zip. So I extracted the APK out and tried again. It still didn't work, so I reinstalled the unofficial 13.17606 and installed the new official beta magisk manager you have to uninstall the the unofficial magisk manager 13.17606 because the new magisk manager will not install over the old one. But I have root can pass the safety net and can install mods that I couldn't before with the unofficial magisk manager.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2017-06-07-23-16-16.png
Views:	1936
Size:	92.0 KB
ID:	4174730  
8th June 2017, 07:31 AM |#27  
Member
Thanks Meter: 4
 
More
This one shows the passed safety net
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2017-06-07-23-27-56.png
Views:	1972
Size:	90.4 KB
ID:	4174735  
8th June 2017, 07:57 AM |#28  
kantjer's Avatar
Recognized Contributor
Thanks Meter: 28,661
 
More
Quote:
Originally Posted by Deic

Code:
D/Magisk: client: connect fail, try launching new daemon process
E/Magisk: start daemon failed with 111: Connection refused
magisk_debug.log

I'm having the same error on today's build
My build made yesterday works fine.
8th June 2017, 08:25 AM |#29  
aLexzkter's Avatar
Senior Member
Thanks Meter: 163
 
More
Does this version have conflicts with Busybox?
8th June 2017, 08:39 AM |#30  
Didgeridoohan's Avatar
Recognized Contributor
Flag Gothenburg
Thanks Meter: 4,337
 
Donate to Me
More
Quote:
Originally Posted by aLexzkter

Does this version have conflicts with Busybox?

From v13 there's not gonna be any bundled busybox anymore. So no, it shouldn't conflict.
8th June 2017, 08:49 AM |#31  
Deic's Avatar
Senior Member
Flag Madrid
Thanks Meter: 962
 
Donate to Me
More
Quote:
Originally Posted by Didgeridoohan

From v13 there's not gonna be any bundled busybox anymore. So no, it shouldn't conflict.

Really there is:
/data/app/com.topjohnwu.magisk-1/lib/arm/libbusybox.so
/data/app/com.topjohnwu.magisk/busybox/busybox (is the same file as libbusybox.so)

But are used only by Magisk Manager, aren't in path variable, so there isn't conflict
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes