Renate
Renate
There are no loaders here with that hash. It's possible that you may never find a loader for this.
It looks like they have a loader for your hash. I don't know if it need authorization and that umi is a response.
Please quote the HWID and hash for your device.
Well, it read the first sector ok and acked. Then it "Timed out". Was that on read or write or what? Who knows.
For some reason it missed the ACK and kept on looking for it. Was this on Linux or Windows with WinUsb or the Com port driver?
You don't need to redact the PK_HASH. There is nothing secret about it. Also, it's probably 4352b3bfeac440ca b3fc0a181be897f5 7ceed6cfe7729d61 752add407fa6e1be e86fe4a27eaed96a 83f9972f707af1d8
The Qualcomm SoCs are the same. The OEMs are different, but the fact that they are using the same PK_HASH indicates that they are not dissimilar.
OEM and model are just footnotes as far as Sahara and Firehose are concerned. Authentication for Secure Boot only cares about PK_HASH and certs.
Yup, you are right. It's just most of the loaders I've run into haven't had those fields set in the last cert. Heck, in Sahara 3.1 you can't even read...
@codiflow Thanks for the hash. It's incompatible with the 3 loaders you had in your first post. ``` prog_firehose_lite.elf- Qualcomm factory signed d9357db88795b5a8 afaebfd9ab08a569 cc8e519f6c689723 759f4e6915ca3466 e98b5a3282678bdf 63673d8517bb0c5b prog_firehose_ddr_001970E1.elf -...