Stephan

Thanks, this looks fairly simple! What use cases do you have in mind for this?

> It can be more complex actually, I haven't messed with switching to AArch64 and ELF64 yet, so it's still capable of booting AArch32 images only. Right, I think this...

> The ELF library from LK is designed to load (and boot) images that matches the current LK's architecture only (using compile-time macros), in our case, AArch32 ELF32 images. Thus...

I'm not sure it matters since the header is effectively empty. There is probably a lot of garbage in qcom's LK but it's probably not worth fixing it all.

> (Mine's a Samsung Galaxy S4) We don't have support for any Samsung Galaxy S4 in lk2nd at the moment?

Are you sure that your tablet actually allows flashing custom software? This sounds a bit like a carrier-locked device that is bootloader-locked.

You can check if `fastboot oem lk_log && fastboot get_staged log.txt` works to get a log. This command should only be supported by lk2nd. It might be that the display...

> @Minecrell interestingly, when I startup lk2nd on my xt1607 harpia it says `BOARD_ID - `. Wasn't sure if that was interesting/important or not. At the moment, the code is...

> > At the moment, the code is not designed to handle multiple board-ids in one device tree. Can you post the lk_log from that harpia (`fastboot oem lk_log &&...

@craigcomstock I added one additional harpia board-id (`0x4D 0x81B0`) for @tchx84. I think it would be good to only add the ones that we have actually verified to work (many...