Open mattfbacon opened 6 months ago
Hi. As I mentioned in the README under known issues this whole repo is not working as I initially intended: It needs to have a "boot.img" present in the "out" directory. So I usually run my build twice. First with magisk disabled (in device.mk) and then with it enabled. That should fix the build error. I forgot to mention this in the README. Sorry for that. Regardless of that in the end you still need to replace the "boot.img" in the resulting zip file with the one from the "out" directory.
This whole ordeal is due to two problems I encountered: 1) I cannot time the build process "after" the building of "boot.img" (or make it dependent of it) 2) I cannot change the contents of the packaging step to use the "boot.img" directly from the "out" directory as it uses the one from the "intermediate" directory.
If you or someone else happens to know a way to work around these problems I'd be happy if you could share it with me.
wkr ADT
EDIT: Nope. It's not this problem. See my next post.
Wait a minute...
OS_VERSION [14.0.0]
I don't think magisk is ready for A14 yet.
EDIT: Or maybe I need to update to 27.0 (although nothing about A14 is mentioned in the changelogs) I'll not be able to to that for now but you can try to set the variable MAGISK_VERSION to 27.0 in your BoardConfig.mk and place the official 27.0.apk inside the vendor/magisk folder. Hopefully the internal layout didn't change too much between 26.4 and 27.0.
Same error with 27.0.
I was able to trace the output up to line 250 of boot_patch.sh where it invokes ./magiskboot, then to https://github.com/topjohnwu/Magisk/blob/33b7b8b297291b26e3b4928355bd17b458361d25/native/src/boot/bootimg.cpp#L887. At this point I don't know why it prints /bin/bash: line 1: /boot: Is a directory
since I don't see any invocation of bash and I also don't see any place where this function tries to use "/boot"
which is passed in the name
parameter as a filesystem path.
Try to trace it with https://github.com/topjohnwu/Magisk/blob/2c6adbc69ba0e5dce09cd13c6d9aca5de30efe76/native/src/boot/bootimg.cpp (It's the tag used for 27.0)
Anyway, are you able to install magisk the "usual" way (install apk, modify boot.img within magisk manager, flash boot.img)?
(It's the tag used for 27.0)
Dang it, you're right, I always do that.
Are you able to install magisk the usual way
Well the magisk app part works fine with no errors but installing the patched image puts my phone into a boot loop. I might be using the wrong boot.img though.
OK, my understanding is that /boot
is only used as the name of the signed image. So I really don't understand why it is getting an error from being interpreted as a filesystem path, when it should never have been used as a path to begin with.
I get this error from running
m
:This causes the build to fail. Any ideas what the issue is?