Jakub K.

> How did you initially root it? > > It's got an MTK Dimensity 9000 SoC, so likely they've done something weird, as usual. > > Going to need the...

> I assume you mean that you patched and flashed init_boot.img? You would need to patch and fastboot boot that, not boot.img. > > Interestingly looks like it found the...

> I can't download it because it says it's in your Trash. Oh, sorry, my mistake... Try it once again please, I updated the link.

> What was the output from the dump command? That .img is empty (all zeros). 🤔 This was the output ``` :/data/data/com.termux/files/home # dd if=/dev/block/sdc39 of=/sdcard/init_boot.img 16384+0 records in 16384+0...

> If you dump init_boot from "fastboot enhanced" or whatever does that produce a normal .img? Not actually. I cannot even see init_boot there. Those are all the images it...

> Can you give me a dump while booted of boot.img? > > `dd if=/dev/block/sdc37 of=/sdcard/boot.img` I guess you mean dump of that boot.img file? Because if I dump that...

Mhm, that's some weird stuff going on on this MTK CPU it seems. THe question is if we or you can do something about it. 🤔

> Only thing I can think of is if init_boot seems invalid fallback to using boot, but it'll really mess up the script and that's frustrating because it shouldn't be...

> Another idea would need a larger rewrite/refactor and involve Magisk be aware of what partition it's installed into and have Direct Install maintain that. Mhm, It would be great,...

> Getting off topic, but for a fun device-specific hack/workaround you could try pointing the by-name/init_boot symlinks at the by-name/boot symlinks and see if it gets Direct Install working. If...