Renate

Please post the md5 (md5sum) of the two prog_firehose_xxx so we can see if they should be added somewhere.

@pckotzer @bkerler Please add this to the collection, it is completely Qualcomm with no OEM or HWID. It should work on some newer models like: ``` SC_KODIAK_CHROME SC_KODIAK_WINDOWS SCP_MAKENA SDX_OLYMPIC...

Try XDA. No, really.

I don't see that hash anywhere, but a Snapdragon 410 is a bit older. Might it not have Secure Boot enabled? Many of the qualcomm/factory/msm???? seem to support the MSM8216...

Many of the loaders refer to MSM8216. Post the sbl.img, please.

That sbl1.mbn is actually an ELF file and signed by Samsung so: ``` d282db63 7345f047 7b6026de 54061686 c6db4dfe 6ff2a4ff 54d142cf e67f97bd ``` There are actually 18 certificates in this file!...

emmc_appsboot.mbn is a 32 bit ELF file signed with 18 Samsung certs. The other two are some sort of raw binary data files.

The emmc_appsboot.mbn has the same hash as the sbl1 and different from what Sahara said. So, either your device is not Secure Boot or else there are more PK hashes...

If you run that with full debug you can see when the PK hash comes over. You can see that it's 32 bytes (64 hexits, 256 bits), but there are...

I don't know what state you're in. I don't know what command you used. I don't know what the result was.