yashsingh1/xdaforums huggingface dataset:
[Magisk] TheC92:
[MENTION=4470081]topjohnwu[/MENTION]

failed...

Nexus 7 (2013) Wi-Fi

LOS-14.1-170606

TWRP-3.1.1-0

Installing zip file '/sdcard/1022/All/Magisk-v13.0(1777d9f).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Segmentation fault
Archive: /sdcard/1022/All/Magisk-v13.0(1777d9f).zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/magisk
inflating: arm/magiskboot
inflating: arm64/magisk
inflating: arm64/magiskboot
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/boot_patch.sh
inflating: common/init.magisk.rc
inflating: common/magisk.apk
inflating: x64/magisk
inflating: x64/magiskboot
inflating: x86/magisk
inflating: x86/magiskboot
************************
* Magisk v13.0(1777d9f) Installer
************************
- Mounting /system(ro), /cache, /data
- Device platform: arm
- Constructing environment
- Creating /data/magisk.img
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/data/magisk.img: 11/4096 files (0.0% non-contiguous), 1294/16384 blocks
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/tmp/boottmp/kernel
- Unpacking boot image
No boot image magic found!
MagiskBoot v13.0 (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/tmp/boottmp/kernel]

! Unable to unpack boot image
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 3 second(s).
Error installing zip file '/sdcard/1022/All/Magisk-v13.0(1777d9f).zip'
Updating partition details...
I:Data backup size is 5699MB, free: 3270MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
[Magisk] m0_onriver:
sticking to magisk 12.0 ?
[Magisk] vitekrus777:
[MENTION=4470081]topjohnwu[/MENTION] When installing the latest version of beta in the recovery error 1. The installer can not find the boot.

The log is attached.
[Magisk] justjr:
Use twrp 3.1 instead of 3.1.1, I had same issue, read someone posted this and it worked.
[MENTION=4470081]topjohnwu[/MENTION] I believe this is best to be posted on OP, and also wonder why does not work on latest twrp
[Magisk] vitekrus777:
[MENTION=1782316]Justi[/MENTION]r No sense. The change of the recovery did not help. It's not in recovery

Log attached.
[Magisk] Bryanx86:
Latest beta works on ABC rom for flounder, thank you! No issues, safety net passes couldn't upload debug log so here is a link in drive https://drive.google.com/file/d/0BwW3SiFEkHP-MkdFYmhOZ3hYb1E/view?usp=drivesdk
[Magisk] xu3sno:
Just reporting Magisk v13.0 (1777d9f) works like a charm on Redmi 1S/W (armani) running Mokee's ROM MK71.2-201606120131-NIGHTLY as it's happened on previous beta.

So simple, MagiskSU ok > enable Magisk Hide > Superuser access Disable > SafetyNet checked Success. : cool:

Thanks dev.

Have a great Monday.
[Magisk] adekboreanaz:
Hmm, strange after installed v.13 playing game was suffering much, but after changed to v.12 it's back to smooth ?
[Magisk] Didgeridoohan:
There's already automatic check for updates, both for the Manager and Magisk. In the current code (not yet officially released) there's even an option to let the Manager automatically check for updates in the beta channel.

You could use ADB to dump the partition (Google it) or extract the file from your ROM/firmware package.
[Magisk] DudeThatsErin:
I have attached my logs. On a pixel XL here and the install failed when trying to flash via Twrp. I was trying to do it and elementalx.
[Magisk] DudeThatsErin:
Oops double posted.
[Magisk] guest4711:
Your log says that system cannot be mounted while flashing. Try to mount (r/w) it manually from TWRP before flashing.
[Magisk] Didgeridoohan:
There's no official Pixel support yet... It's only recently that [MENTION=4470081]topjohnwu[/MENTION] have acquired a Pixel to develop on.

Meanwhile you can use the unofficial build by [MENTION=2461994]goodwin_c[/MENTION].
[Magisk] Ramshu97:
Perfectly working on mi5s miui 7.8.31.eu version
[Magisk] DudeThatsErin:
I think it has to do with the below quote... cause doing that did nothing.

None of those work on O. I thought since it was O this would work for the Pixel.. but I forgot about the Nexus devices. OOPS!

Ugh. I'm so impatient.
[Magisk] topjohnwu:
2017.9.6 Magisk v14.0 (1440)

There is also a beta for v14.0. The code is 100% identical to the stable release, but this is built with the debug flag on.

Useful for reporting bugs and issues :)

For the complete release notes, please check here
[Magisk] OldDroid:
REMOVED

i will create a issue on your github soon.
[Magisk] nathanchance:
I'm confused, how does Magisk not support file based encryption? I am using an OP5 with FBE and have zero issues. As far as I am aware, the primary issue with Pixels is the A/B partition layout and the boot/recovery partition merge.
[Magisk] Elie.Be:
Hello.. does v14 have two different version?

Why there is a slightly difference between v14 (1400) on this thread.. and the one v.14 on the main thread..

1) 5.54 Mb (this thread) versus 5.53 Mb (main thread)

2) Md5: d8fb47b9a106483118201f152b364510 (5.54)

versus 81eed4fb551da9b3bd9c2dc26e80762f (5.53)

Which one should i flash? Thanks guys..
[Magisk] donmarkoni:
Oh man... Can't you read...? Just three post above yours. :rolleyes:
[Magisk] pendor24:
Hello

version 14 flashed on s7 edge and everything went nickel.

if joined log.

thank you for the hard work.

https://mega.nz/#!e4whmYqQ!jalURGAW0NjMBgxcUobwAMmRUH7husVmRM_zj-sxfv0
[Magisk] Paschfire:
Pls try to search for answers before posting, as topjohnwu just answered your question in the 3rd post above your own.
[Magisk] T.A.R.D.I.S.:
Many thanks

Work fine on S7 edge 7.0 :
[Magisk] Elie.Be:
Ok sorry.. guess i missed it.

btw, i am a girl. Thanks for reply

Got it. I've missed that post. thanks
[Magisk] donmarkoni:
Hehe... Yeah, if I did read (your nickname), I would know... :D
[Magisk] HtheB:
Somehow, my Xposed does not work anymore with Magisk 14.0 :(

Any ideas what I can do? It worked with 13.3 before

Edit: Sony Xperia XA (Stock rom) Android 6.0

Edit2: Seems like there is an update within the Magisk Manager for Xposed.

Idea: Maybe adding some notification that there are updates on the module would be nice :p
[Magisk] denzel09:
After last update something has been broken in my side. Previously all worked.

Now i have ctsProfile error and basicIntegrity error
[Magisk] demonoidmaster:
1. Post your logs

2. It does notify you when you open the app
[Magisk] dimm0k:
too giddy for this 1400 release, but don't have my test device with me... can anyone confirm it works on the LGV20?? I know 13.6 did not and did provide logs... just hoping it was fixed.
[Magisk] audiomarko:
Hello, have 14 installed and have a bootloop.mit Xposed modul and some others. (samsung galaxy note edge SM-N915 FY with Ram Kernel.) back to 13.3 and it works again. someone has a solution ..... many thanks in advance
[Magisk] manudhomra:
Good work guys, latest stable build is working awesome. Good luck
[Magisk] Oswald Boelcke:
Just for information: Upgrade/flashing from Magisk v13.3 to v14.0 through Magisk Manager v5.1.1 didn't work. Procedure was conducted by Magisk Manager as advertised but when I tried to open Magisk Manager after the reboot, always FCs of the Manager.

"Work around": Booted into TWRP, flashed Magisk-uninstaller, flashed Magisk v14.0-zip, rebooted into system.

All well afterwards; Magisk Manager v5.3.0 installed and working well.

Remark - and I don't know if it's related: After the flash of Magisk v14.0 my Boeffla Config app didn't recognise my Boeffla kernel anymore i.e. back into recovery, flash the kernel again, and back into system. Now, all working great!

Thanks to @topjohnwu for another job simply done excellently!
[Magisk] HtheB:
Hmm, that's weird, I really didn't get any notifications though.

It's just finished updating, and it seems like it's working after updating Xposed!
[Magisk] demonoidmaster:
Whenever you're flashing a new magisk version over another via twrp always flash your kernel afterwards before rebooting into your rom
[Magisk] fonfox:
With Oneplus 2 Update from Magisk V13.3 to V14.0 works fine and no issues.
[Magisk] demonoidmaster:
If they don't notify you then open magisk and go to settings then do force refresh the repo of modules
[Magisk] HtheB:
ouch... It seems like my Bluetooth and Wifi doesn't work anymore :(

Getting all kinds of errors now:

Bluetooth sharing has stopped

Homenetwork has stopped

Camera common has stopped

where can I find the logs?

Edit: Phone is getting hot as well
[Magisk] demonoidmaster:
Not all kernels are made the same, js

---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------

Open magisk, log, then go to magisk tab, press the lil floppy disk icon & save
[Magisk] HtheB:
Ok, added the log as attachment :(
[Magisk] husky69:
Xperia Z5 (sumire), Android 7.1.2, installed Magisk 14.0 through Magisk app (from 13.3); rebooted successfully, seemed to work flawless;

Then I installed Xposed framework for SDK v25, rebooted - and now I'm stuck at SONY logo screen; device not contactable through adb nor fastboot :( :( :(

Any help appreciated :fingers-crossed:
[Magisk] naboleo:
Can't install v14=> error 1

I:Set page: 'flash_zip'
I:operation_start: 'Flashing'Installation du fichier zip '/sdcard/MagiskManager/Magisk-v14.0.zip'
Vérification des fichiers MD5...
Pas de vérification MD5: aucun fichier MD5 trouvé
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /sdcard/MagiskManager/Magisk-v14.0.zip
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: addon.d/99-magisk.sh
inflating: arm/magisk
inflating: arm/magiskboot
inflating: arm64/magisk
inflating: arm64/magiskboot
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/boot_patch.sh
inflating: common/init.magisk.rc
inflating: common/magisk.apk
inflating: common/util_functions.sh
inflating: x64/magisk
inflating: x64/magiskboot
inflating: x86/magisk
inflating: x86/magiskboot
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm64
- Constructing environment
- Adding addon.d survival script! Unable to detect boot image
- Unmounting partitions
Le processus Updater s'est terminé avec ERREUR: 1

but

Backup_Method: files/boot | /dev/block/sda26 | Size: 24MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/sda26
Display_Name: Boot
Storage_Name: Boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc

typo error in installer with name Boot/boot or worth (V13.3 was ok) ?
[Magisk] guest4711:
See above post: 2017.9.6 Magisk v14.0 (1440)

There is also a beta for v14.0. The code is 100% identical to the stable release, but this is built with the debug flag on.

Useful for reporting bugs and issues :)

For the complete release notes, please check here
[Magisk] HtheB:
Ok, reverting back to 13.3 solved all my problems: Except that now I can't install Xposed since it's the latest version inside the Magisk Manager app and it wont install since it's not 14.0 :(

Does anyone have a Mirror? :( (Xposed SDK 23 arm64 ?)
[Magisk] DodoGTA:
Can you try Magisk v14.0 without Xposed?
[Magisk] HtheB:
Already did, it installs but suddenly gives me all kinds of errors.

Log posted like 3-4 posts above

Edit: I don't get it why older builds are removed at all?

Edit 2: Also, other apps like the Unified hosts Adblock doesn't install as well, since they all rely on newer Magisk versions.

Magisk should really have a version picker like Xposed does...
[Magisk] DodoGTA:
I looked at the log and noticed that Xposed is installed

So, can you remove it and see if the problem disappears?
[Magisk] HtheB:
Will try out tomorrow, just found a mirror of the working Xposed version (for Magisk 13.3) for now.
[Magisk] DawoodSahi:
After updating to v14, I'm not being able to install modules through TWRP, gives some kind of error 1/2. Also if I install xposed v87.2, it gets stuck on the boot screen
[Magisk] FlavioV:
Installed Magisk Manager v5.3.0 first as I got a notification from XDA Labs, then updated Magisk. Got stuck on boot logo after the reboot but rebooted again and it's all good. :good:
[Magisk] husky69:
In case somebody else has similar problems:

fastboot after all was accessible (used wrong key combinations...), and after flashing boot.img from the ROM package system came up again. After application of the Magisk Uninstaller ZIP from OP I re-installed Magisk 13.3 and now everything is back to normal for the moment. :victory:

I think I'll wait for the v14.1 release or so before switching to the next major version after this problems...
[Magisk] Didgeridoohan:
I'd put my money on Xposed being the culprit, not Magisk...
[Magisk] husky69:
Same here.

But for the moment I had enough adventures by trying to recover my phone - I depend on it for my job...
[Magisk] Robotic Earthling:
After I try to install "Emoji One," it does not install and I get some unusual items in the "modules" section (auto_mount, module.prop, system, update). The Emoji One module worked fine on v13.3. Most other modules seem to install fine on this version. Screenshot and logs in attachments. I'm running LineageOS on a kltespr.

EDIT: After uninstalling and reinstalling Magisk, and then installing the newest version of the Emoji One module (v1.311), everything is working fine.
[Magisk] :
Just a disclaimer: for those with Samsung devices with secure boot, this newest update doesn't allow us to use Magisk still. Odin refused to flash due to secure boot recognizing a modified boot image.
[Magisk] parizene:
Installed v14.0 on stock Samsung S8, tried to patch boot image (BL.tar), error occurred:

So it will not work on encrypted Samsung storage?
[Magisk] pendor24:
version 14 flashed on S8 + and it works nickel.

thank you for the work.
[Magisk] parizene:
was it flashed from TWRP?
[Magisk] pendor24:
yes
[Magisk] Dinerve:
I've the exact same thing, these weird modules popped among the others and keep being prompted to update EmojiOne but doesn't install after reboot....

Are these safe to delete/uninstall?

EDIT: These wont uninstall....in spite of doing do and rebooting.

I'm on OOS 4.5.10 on OnePlus 5
[Magisk] R0BiN0705:
make sure to mount system in twrp. I had the same error but this fixed it
[Magisk] Shen Ron:
As usual xposed don't work on new update. Change the extension to log to view it. Samsung Galaxy On5 debloated 6.0.1 touchwiz.
[Magisk] dimm0k:
LGV20 here and having some issues with modules on 14.0. modules worked fine on 13.3, but with 14.0 it boots fine until I load any module. doing so causes my device to hang on the LG logo. I've tried uninstalling Magisk and then straight flashing in TWRP to 14.0, but same thing, it freezes on the boot logo. attached are my magisk logs

EDIT: attaching debug log
[Magisk] eben80:
I'm also having an issue with one module causing the phone not getting past splash screen on my Mi5.

Other modules are working normally but one that uses only post-fs-data is causing this even if installed fresh on v14.0

It worked normally on 13.3

The code in post-fs-data is:

#!/system/bin/sh

echo 1 >> /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
[Magisk] love4chat:
cts profile shows fails for mt moto g5 plus,even with latest v14.0 also
[Magisk] adekboreanaz:
Downloading every module or install is giving Error Processing on Latest Magisk Manager.

On Redmi Note 4 MIUI9 Nougat 7.0

Logs only give this

Clearing repo, re-install magisk keep giving same error
[Magisk] Setialpha:
Manually create the directory /sdcard/MagiskManager
[Magisk] adekboreanaz:
Uninstalling Magisk Give Stock Boot Image backups unavailable on V14, on V13.6 it's fine, and after installing magisk V14 i can't flash module, giving error that Magisk isn't Installed, i attached recovery.log

Damn xda labs i already attach it

https://hastebin.com/ugizubeheg.sql
[Magisk] firdausimbolon:
Finally, it's fixed my prob about lost root after restart. Thanks a lot.
[Magisk] axiel7:
Can someone explain me why I lost root randomly? It's a known bug? Nexus 5X Android Oreo
[Magisk] kastik4:
I have fbe I installed magisk by making a boot.img and i flash it through fastboot. My problem is that magisk.img and some other files and folders does not exist is there any way to make them manually.Here is my magisk log

--------- beginning of main
I( 369: 369) Magisk v14.0(1400) daemon started
I( 369: 371) ** post-fs mode running
--------- beginning of system
I( 369: 426) ** post-fs-data mode running
I( 369: 426) * Mounting mirrors
I( 369: 426) mount: /dev/block/dm-0 -> /dev/magisk/mirror/system
I( 369: 426) mount: /dev/block/dm-1 -> /dev/magisk/mirror/vendor
E( 369: 426) mount /data/magisk->/dev/magisk/mirror/bin failed with 2: No such file or directory
I( 369: 636) ** late_start service mode running
I( 369: 636) * Running service.d scripts
I( 369: 636) * Running module service scripts
I( 369: 7390) * Starting MagiskHide
I( 369: 7390) hide_utils: Hiding sensitive props
E( 369: 7390) fopen: /magisk/.core/hidelist failed with 2: No such file or directory
I( 369: 7390) hide_list add: [com.google.android.gms.unstable]
E( 369: 7390) fopen: /magisk/.core/hidelist failed with 2: No such file or directory
I( 369: 7390) proc_monitor: init ns=mnt:[4026531840]
I( 369: 7390) proc_monitor: zygote ns=mnt:[4026547143] zygote64 ns=mnt:[4026547144]
I( 369: 7390) proc_monitor: com.google.android.gms.unstable (PID=7413 ns=mnt:[4026547178])
I( 7448: 7448) hide_utils: Re-linking /sbin
I( 369: 7390) proc_monitor: com.google.android.gms.unstable (PID=11803 ns=mnt:[4026547181])
[Magisk] goferos:
Could some1 remind me procedure to install I did clean flash now want to install magisk 14 and agni kernel, which first and should I reboot between? Aosp Oreo if that matter
[Magisk] ketansharmar:
First Magisk then Kernel
[Magisk] audiomarko:
so .... 13.3 unrootet ...... 14. flashed .... root available ... runs .... but xposed does not work as under 13.3 ..... Back to 13.3 ... anyway thanks for the great work
[Magisk] 5m4r7ph0n36uru:
Magisk isn't installed as far as I can tell. Thus no root available.
[Magisk] axiel7:
It's uninstall automatically, when I flash the magisk.zip, it detect a magisk patched boot image. It's very strange.

---------- Post added at 01:17 PM ---------- Previous post was at 01:16 PM ----------

Will try it

Enviado desde mi Nexus 5X mediante Tapatalk
[Magisk] -Hope-:
Try flashing the boot.IMG that came with the ROM then flashing the magisk back using twrp this must allow magisk to find a unpatched boot image thus it will patch it and root.
[Magisk] axiel7:
It's detect the magisk image, but it root successful. The problem is that randomly, magisk manager says that I don't have magisk installed and I need to flash de magisk.zip again
[Magisk] -Hope-:
First try to reboot sometimes systemless roots fail to start successfully because they couldn't get every thing mounted correctly.

Try also to disable modules and try a reboot

There is an option called "MagiskCore" in settings this will make the task easier.

If that didn't work please try to flash the boot.img that came with the ROM

Check ROM files for boot.img and flash it.

Note: you may also check magisk's stock boot backup. It maybe found in /data/ in a zip file

Named as stock_boot.img.gz (its a serialed name)

Inside it you will find the stock boot.

Last thing to try is to revert back to an older version.
[Magisk] axiel7:
Thanks! Will try the next time instead of flashing the magisk.zip
[Magisk] mamutal91:
Thanks!
[Magisk] demonoidmaster:
Why do people still try so hard to use xposed with magisk or system based (be it as a module or seperate as a good old system based flashable zip).. Honestly devs should port their xposed modules over to magisk, there's no reason to use something like that, Oreo already launched yet Rovo never got to release a xposed version for Marshmallow, leaving only other devs to get some unofficial versions to work with Marshmallow and stuff.

Harsh reality people, it's time to move on and ask the devs of your favorite xposed modules to move their stuff over
[Magisk] Setialpha:
Xposed != Magisk

You can't just port most Xposed Modules, because that's something *completely* different than Magisk.
[Magisk] lahceneamine:
The fact is that for now, Xposed and Magisk do not operate the same at all.

When (or if) magisk will somehow un the futur hooks & injects ressources, we won't need Xposed anymore.
[Magisk] demonoidmaster:
This is XDA, surely it wouldn't be too hard for some devs to remake their xposed modules into magisk modules, i have faith that they'll all find a way
[Magisk] DenyDarko:
People you do realize this is not an xposed thread plus it modifies so much the system and it probably causes all your magisk issues.

After all, no reason to use magisk when you've already messed up /system partition.
[Magisk] DenyDarko:
You don't need magisk as it's primary feature is systemLESS.

Youu've already touched your system.
[Magisk] Demonsannoyed38:
Hello my friend. Do you mean xposed not working on 14.0 magisk? I've been using xposed on magisk 13.3 since July now and have had no issues. Did want to flash 14.0 through the manager, think I might wait though. Even after updating the magisk manager 1st, I believe there to be conflictions with xposed...yet again, even with the systemless 87.2 revision. Will wait a while. I'm using S7 edge exynos with superman 2.6.0 nougat 7.0 with superkernel with synapse tweaks, purifys sdk 24 systemless and have had no issues with any of the modules that I've installed so far.
[Magisk] Wiciaki:
I'm only trying to say that both of these can't be replaced by each other because Xposed is used for method hooking and Magisk is used for performing undetected file operations.

Whether or not these tamper SafetyNet is another thing. Xposed might be potentially bypassing SafetyNet in the future, too.
[Magisk] mrsover:
Hello. My samsung galaxy note 2 does not wake up after 20 min of sleep. Log attached
[Magisk] k303:
coming from magisk 13.3 on my LG G2 with latest LOS, the phone will refuse booting the system and hangs on LG Logo. Rebooting into TWRP and reflashing the 13.3 zip resolves the problem.

any idea?
[Magisk] de.er:
What Magisk modules are you using? One of them might be acting up, I had the same problem. Uninstall all modules, reboot, update Magisk to v14, should be able to reboot (if not, flash the Magisk uninstall zip in TWRP followed by magisk 14). Install the modules one by one rebooting after every module to see if any of the modules causes the problem. This worked for me, good luck.
[Magisk] audiomarko:
Hello ... had 13.3 and xposed drauf .... functions flawless .... had changed to 14. With Xposed bootloop .... without ... it worked. (Samsung galaxy note edge 6.0.1) am back to 13.3. because no problems with Xposed ..... I'm waiting for solution ... Greeting
[Magisk] smartpr1v4t3:
On my OnePlus3t Stock 4.1.7 i get bootloop with magisk v14

anyone has a idea?