Get the OnePlus 6 early at a pop-up event in your city →
FORUMS
Remove All Ads from XDA

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

1,790 posts
Thanks Meter: 44,424
 
By topjohnwu, Recognized Developer / Recognized Contributor on 7th June 2017, 10:36 PM
Post Reply Email Thread
Yesterday, 11:26 PM |#5691  
yochananmarqos's Avatar
Senior Member
Thanks Meter: 1,929
 
Donate to Me
More
Quote:
Originally Posted by FlavioV

Wrong. Magisk only patches the boot image. You'd only lose root if you flash a non-rooted rom afterwards.

It's even mentioned in the main thread (I can't do a proper quote because the thread is locked):

The only reason why you'd lose root flashing any ROM would be if it wasn't using an AnyKernel2 kernel. Flashing a stock boot.img would also remove Magisk.

Sent from my Nexus 6P using XDA Labs
 
 
Today, 07:03 AM |#5692  
nathanchance's Avatar
Recognized Developer / Recognized Contributor
Flag Mesa, AZ
Thanks Meter: 43,961
 
More
I will mention that certain A/B devices like the Pixel and Pixel 2 do require Magisk to be flashed after the kernel since the kernel itself is hexpatched not to skip initramfs so it's not a universal rule, it's device specific. I know that doesn't apply to this specific scenario but I don't want my users stumbling upon this and thinking they don't need to flash Magisk after my kernel lol.

Sent from my Pixel 2 XL using XDA Labs
The Following 6 Users Say Thank You to nathanchance For This Useful Post: [ View ]
Today, 01:03 PM |#5693  
Junior Member
Thanks Meter: 0
 
More
Hello guys, I have install magisk 16.4 and magisk manager 5.7.0 (115).

My problem is the check safetynet ok.
ctsprofile: false
basicintegrity: false
log:
05-22 12:08:29.300 520 520 I Magisk : ** Initializing Magisk
05-22 12:08:29.302 520 520 I Magisk : * Creating /sbin overlay
05-22 12:08:29.303 520 520 I Magisk : * Mounting mirrors
05-22 12:08:29.304 520 520 I Magisk : mount: /sbin/.core/mirror/system <- /dev/block/bootdevice/by-name/system
05-22 12:08:29.304 520 520 I Magisk : mount: /sbin/.core/mirror/vendor <- /dev/block/bootdevice/by-name/vendor
05-22 12:08:29.304 520 520 I Magisk : bind_mount: /sbin/.core/mirror/bin <- /data/adb/magisk
05-22 12:08:29.304 520 520 I Magisk : * Setting up internal busybox
05-22 12:08:29.347 523 523 I Magisk : Magisk v16.4(1642) daemon started
05-22 12:08:29.349 523 531 I Magisk : ** post-fs-data mode running
05-22 12:08:29.349 523 531 I Magisk : Create /data/adb/magisk.img with size 64M
05-22 12:08:29.365 523 531 I Magisk : * Mounting /data/adb/magisk.img
05-22 12:08:29.537 523 531 I Magisk : * Running post-fs-data.d scripts
05-22 12:08:29.537 523 531 I Magisk : * Running module post-fs-data scripts
05-22 12:08:29.537 523 531 I Magisk : * Loading modules
05-22 12:08:29.537 523 549 I Magisk : * Starting MagiskHide
05-22 12:08:29.537 523 549 I Magisk : hide_utils: Hiding sensitive props
05-22 12:08:29.537 523 549 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
05-22 12:08:29.537 523 549 I Magisk : hide_list add: [com.google.android.gms.unstable]
05-22 12:08:29.548 523 549 I Magisk : proc_monitor: init ns=mnt:[4026531840]
05-22 12:08:29.835 523 585 I Magisk : ** late_start service mode running
05-22 12:08:29.835 523 585 I Magisk : * Running service.d scripts
05-22 12:08:29.835 523 585 I Magisk : * Running module service scripts
05-22 12:08:34.850 523 549 I Magisk : proc_monitor: zygote ns=mnt:[4026532980] zygote64 ns=mnt:[4026532981]
05-22 12:10:16.755 523 4249 E Magisk : sqlite3 open failure: unable to open database file
05-22 12:10:37.734 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=5006 ns=mnt:[4026533048])
05-22 12:11:06.782 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6757 ns=mnt:[4026533022])
05-22 12:12:11.681 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=8289 ns=mnt:[4026533093])
05-22 12:15:49.698 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=10829 ns=mnt:[4026533123])
05-22 12:22:21.601 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=14412 ns=mnt:[4026533131])
05-22 12:23:23.729 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=16075 ns=mnt:[4026533135])
05-22 12:39:04.373 523 549 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=22475 ns=mnt:[4026533181]

For me is first test to using Magisk for Pokemon Go.

thanks.
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