残页

Upload installion log? And use [this](https://github.com/topjohnwu/Magisk/issues/5607#issuecomment-1072389939) to grab kernel log? I have commented out the code that patchs the kernel.

> When magisk app is patching the image? there is nothing out the ordinary here. Click the "save" button in the "patching image" page after "Done!" is shown.

[second-ulefone.zip](https://github.com/topjohnwu/Magisk/files/9539597/second-ulefone.zip) Does this image boot?

I just unpacked and repacked the boot.img, so it's likely some bugs within the unpacking/repacking routine and cause the repacked image to be corrupted. 🤔 I'm not good at image...

> Unpacked and repacked with magiskboot? Yes

Re-download the unpatched image and repack it with `KEEPVERITY=true KEEPFORCEENCRYPT=true PATCHVBMETAFLAG=true RECOVERYMODE=false` [new-boot-n.zip](https://github.com/topjohnwu/Magisk/files/9690733/new-boot-n.zip) (with `-n` option) [new-boot-c.zip](https://github.com/topjohnwu/Magisk/files/9690736/new-boot-c.zip) (with no `-n` option) @noraj Can you test if these images boot?

So the bug seems to be in gzip compression/decompression routine 🤔

Extracted the kernel from both images via `magiskboot unpack -n`, recompressed kernel is 6KB larger than the original one, but I can decompress it so it is a good gzip....

[zopfli-boot.zip](https://github.com/topjohnwu/Magisk/files/9757044/zopfli-boot.zip) And how about this? I'm trying Zopfli for better compression rate to see what will happen if the recompressed kernel/ramdisk are not larger. ``` # ./magiskboot unpack new-boot-n.img Parsing...

have you unlocked the bootloader?