All I see are .bin files.

[devphenom1]

I do not see a boot.img or system.img. I am using an at&t radiant max with the bootloader unlocked. What other files would boot.img be hidden in?

[zeugensativas]

i was able to patch .bin in magisk without errors
Couldnt test the patched boot image cause my phone blocks custom binaries but you could test that

Dump ALL partitions in Brommode and see what comes out ^^

python mtk rl out

[devphenom1]

Should boot.img from any device with the same chipset work? My phone has the mt6833

[devphenom1]

how about https://forum.xda-developers.com/t/at-t-radiant-core-tinno-u304aa-modding-discussion.4181963/post-84624775

you could try bypass secureboot use the scatterfile from xda and use SP tool?

but however send the link to dropbox and we will see

MT6833 Dimensity 700 5G (7 nm) is the entire chipset name for my device

[jiaaluo]

Just chiming in to this discussion, I have a Cricket Dream 5g which is a clone of the at&t radiant max that devphenom1 has I tried using MTKclient but it seems it isn't detecting the preloader.

[jiaaluo]

magisk_patched-23016_8s0i8.zip
you could try this patched boot image remember to flash blank vbmeta

[jiaaluo]

also @devphenom1 i suggest not switching active boot slots you get stuck in a preloader loop that i can't seem to get out of