Chris Renshaw

``` /adb/magisk/magiskboot repack -n boot.img Parsing boot image: [boot.img] HEADER_VER [0] KERNEL_SZ [8578893] RAMDISK_SZ [2341375] SECOND_SZ [0] EXTRA_SZ [0] OS_VERSION [7.1.1] OS_PATCH_LEVEL [2018-05] PAGESIZE [2048] NAME [GQ3056MF1_HCS98] CMDLINE [bootopt=64S3,32N2,64N2 buildvariant=user]...

Only difference was a signature at the end, which I identified as AVBv1. ``` Android Image Kitchen - UnpackImg Script by osm0sis @ xda-developers Supplied image: boot.img Setting up work...

> [patched.img.zip](https://github.com/topjohnwu/Magisk/files/9542983/patched.img.zip) Oh wow, so the magisk_patched-25200_FV2Q6.img inside is 10KB of completely zeros in hex, so something went very wrong with file creation or with your uploading? I didn't see...

Thanks. Yep, those ones look good, properly signed, etc. So it's nothing format-wise that I can see. Just something with magiskinit presumably.

Yep, SuperSU used to have this, and I continue to miss it. 👍

I mean that quote doesn't totally make sense in this context. A launcher "protecting" apps with a biometric prompt is easily circumventable by launching the app directly from Android Settings...

But why? Sounds like people are just using overlay.d poorly/thoughtlessly. You can override things later or in a different .rc for example.

Try with latest v21 Public Beta build please. This may be already fixed.

@evelbodevil that's completely different from this issue, you just need to allow root access to Shell in the Magisk app

May already be fixed upstream from the last Canary? https://github.com/topjohnwu/Magisk/commit/117d1ed0801c0b9fa144d195c0a89cabc488d176