[Magisk] pndwal:
Haha... I thought someone might bring up these things! 🙃

Of course the main point was always the need to tarball image files...

Seems the members issues stem from Odin flashing being incompatible with raw .img files... and I gave examples of differing extraction / tarballing / patching / flashing procedures that should work...

I actually read such claims but didn't repeat them as the need is far from clearly established as far as I can see (and Sammy users can always rename files if needed or if they wish)...

This may well be important as you say at least for some Odin versions. (Again, Sammy users may know better.) However many instructions don't indicate a need to use partition names, eg

https://forum.gsmhosting.com/vbb/f777/how-flash-custom-kernel-using-odin-download-2574060/

and

https://medium.com/@oliviaroborts/odin-download-to-flash-custom-kernel-on-galaxy-device-e53d3eac744f

And official TWRP instructions simply say "select the tar file that you downloaded (twrp-3.7.0_9-0-hlte.img.tar etc) and flash the device" so it seems Odin is smart enough to recognise this as a recovery image despite not including "recovery" in filename...

https://twrp.me/samsung/samsunggalaxynote3internationalexynos.html

Here's a guide that bears out the fact that Odin builds at least since 3.11 (May 2016) do "file analysis" to determine partition/image type and flashes files named differently to the correct partition (rather than using file names):

https://droidtechknow.com/how-to/twrp/install-twrp-recovery-on-samsung/

In this example TWRP.tar is detected as containing "Single download recovery.img" and flashed correctly as such per output log:

Well yes, but specifically for Sammy devices launched w/ SAR+ (ie SAR or 2SI) booting...

Members device launched w/ Android 4.3 (Jelly Bean), upgradable to stock 5.0 (Lollipop), and John does say "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section"...

I began giving advice based on pre A9 Android and guides make it clear that flashing Magisk patched AP binary alone is fine for these devices... Also, older devices didn't have vbmeta partitions, and only AP binary anyway... BL and CP binaries were seperated out more recently...

Once the member indicated device runs a custom AOSP build however (we still don't know if this is an A10+ however... Nb. legacy ramdisk devices don't convert to legacy SAR w/ A9 running version but necessarily become 2SI w/ updates to A10 RV incl. custom ROMs), I did point the possibility of some of John's cautions for SAR+ devices applying per:

... Of course flashing only the available boot.img (after patching and tarballing by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing) is quite different from John's prescribed method for A9+/SAR+ LV (launch version) devices of flashing the complete AP binary (after patching) along with other binaries anyway!... It's akin to flashing a discreet boot image w/ fastboot...

Guides indicate this method works fine for older Sammy devices however...

... Please let me know if I'm missing something obvious though... I may well be wide of the mark as I have no practical experience with Odin and have only done cursory searches... 🙂 PW