Thanks for the quick reply! It made me realize that I was indeed comparing the wrong numbers. Using EDL, I dumped boot_a and boot_b (without truncating) and both are exactly 100663296 bytes large, the same as the boot.img I extracted from update.upx and the patched version. Checking the md5sum, boot_b and the extracted boot.img are identical, so that's good I guess.
From what I understand, now I should write the patched boot.img back into boot_b with this command, correct?
edl.exe /u /w /pboot_b magisk_patched.img
Quote:
|
If we're talking about Onyx devices then Motorola Firehose loaders are irrelevant.
|
I am using this loader, as was suggested in the first post of this thread:
https://github.com/bkerler/Loaders/b...g_moto_g52.bin
The other two loaders that had come up in this forum (qualcomm/factory/sdm662/0014d0e100000000_d40eee56f3194665_FHPRG.bin and lenovo_motorola/0000000002e80000_abbcc86fe393b13d_fhprg.bin) fail and result in my tablet disconnecting and reconnecting, so the moto_g52.bin is the only option for me. From what I understood you explained before that this loader is restricted in that it doesn't have read/write access to all partitions. It seems that reading works for all partitions, I haven't tried writing to the device yet though.