@Renate @mark332 I've researched this topic a little more: As we all know the EDL mode is implemented by the PBL (primary bootloader, part of SoC ROM Code). The PBL verifies the digitally-signed SBL/XBL and loads it into internal memory. If verification fails it boots into EDL mode and we need the correct programmer.elf for communication.
But it's very interesting that the mentioned verification process of the SBL/XBL is used to authenticate the programmer.elf, too. Both have the same signature. Going further you will see that even the whole structure of the programmer.elf (up to a certain point) is almost the same as the SBL/XBL. So, it seems that the programmer.elf is a shortened and modified binary derived from the SBL/XBL.
@mark332 For the Moto G6 Plus / XT1926 (evert) your tool loads the programmer.elf within >21.bin< which also can be found in the blankflash.zip for Pie builds on mirrors.lolinet.com. I know from my own experience that the programmer.elf isn't able to communicate with the device. I don't know why it was published and who provided that file. But it's the only file signed with test keys instead of OEM keys. When I was using your tool I replaced the programmer.elf with a working one of https://github.com/bkerler/edl.
During my research the last hours I found out that this programmer.elf from github.com (MD5 matches) is also used in the blankflash.zip for Oreo builds (see link above). I attached it in case you would like to fix the bug.
But it's very interesting that the mentioned verification process of the SBL/XBL is used to authenticate the programmer.elf, too. Both have the same signature. Going further you will see that even the whole structure of the programmer.elf (up to a certain point) is almost the same as the SBL/XBL. So, it seems that the programmer.elf is a shortened and modified binary derived from the SBL/XBL.
@mark332 For the Moto G6 Plus / XT1926 (evert) your tool loads the programmer.elf within >21.bin< which also can be found in the blankflash.zip for Pie builds on mirrors.lolinet.com. I know from my own experience that the programmer.elf isn't able to communicate with the device. I don't know why it was published and who provided that file. But it's the only file signed with test keys instead of OEM keys. When I was using your tool I replaced the programmer.elf with a working one of https://github.com/bkerler/edl.
During my research the last hours I found out that this programmer.elf from github.com (MD5 matches) is also used in the blankflash.zip for Oreo builds (see link above). I attached it in case you would like to fix the bug.
Qualcomm changed the designation of their boards (for only some SoCs or all upcoming ones...?) and either called them SDM??? or MSM????.