@hexaheximal im a bit surprised... basically the whole android development stuff delivers the whole package with proper well designed tools to handle everything, everything designed so that stupid people can handle it, imho there is no damn reason to reimplement that stuff in any way. In the context of what i experienced and heard of, Samsung fucked up that for years now. You are literally the first Person telling me that Samsung did a good job for that on any device whens it comes to having third-party support
mtkclient isn't made by samsung. and it isn't made by mediatek either. and it's not even made *for* samsung devices specifically. it's just a generic tool made by hobbyists that uses exploits (in my case with the galaxy tab a7 lite, it uses the kamakiri exploit) to allow you to flash images to the device etc.
@Jain Also, let's be real: samsung probably wouldn't like mtkclient either since it allows you to break the chain of trust.
The device I have uses Samsung Knox, but saying that the device firmware is trusted on that device is highly misleading at best - using the kamakiri exploit, anyone with physical access to the device can unlock the bootloader and modify the firmware, and if that's not stealthy enough you can flash a new bootloader too.