DA files or loaders from the beginning of the secure boot theme are signed and assigned to the processor.
That is, if you have a VIVO device with a processor for example MSM8937, all the devices with the same processor from the same company, which is VIVO, will operate normally on the same loader.
Another example, if you have a Realme device with MT6789 processor, if you find any device that is supported on any device, you will enter the Kimovil website and see the list that
It carries the same handler and performs normally according to the handler from the device in which the specific model is present.
In another case, it is possible that there is more than a release for the processor itself, a camera tool can show you this topic for media-tech processors. So, you will enter gsmarena and find the device written MT6762, MT6765G or MT6762H, and you will find the tools that recognized the processor as MT6765, but a camera tool analyzes the SW version and HW version and they have an excellent database that looks exactly the processor for example MT6771C / MT6771 C / V and so on.
This point will help you to get out all the devices that are with the same healer correctly .. When you search Kimovil, because it requires the right therapist with the same revision. This information can be very short for you if you find a certain device in the tool list and in other devices with the same processors that are not present, you can try it on other available devices that carry the same SoC.
The topic includes all processors whether MT-K, QLM, or UNISOC.
The only exception is Samsung and Alcatel (TCL)…. Because their files are signed according to the device, the protection version or the bit revision. So, for example, loader A042F BIT 3 is not a hypothet with A042F Bit 4 device, another example, the loader T505N BIT 4 is not a hyperbot with a T505N Bit 5 device, but it appreciates all the least protections, because with each protection a new signature key is added to check while keeping the old keys.
Of course, in general if Media-Tech and we use PL AUTH for example, but it does not apply in case of exploit designated as the hole of the potrom, for example, because in this case it all follows the manufacturer’s approach to the processor and not the OEM itself. Therefore, we will consider that the issue regarding Samsung is fixed on the basis above for Qualcomm devices that do not have any gap specific to the processor and any device that allows them to have loaders from JDM or DEBUG EMERGENCY specific for the device and the release. And they added it, except Exynos and MT-K, which have gaps specific to the healer, it makes the work a little different.