Renate

You have to force it into 9008 mode, using EDL cable, EDL test points or defeating the flash memory.

You need to try more loaders, it won't pick the right one for you. It says: `Error: Invalid data size received in image header` But it actually means: `Error: Invalid...

Try these. On failure, reset and go to fresh EDL mode. The state of the device is iffy after failure. ``` lenovo_motorola/0000000000720000_1bebe3863a6781db_fhprg_edlauth.bin lenovo_motorola/000a50e100720000_1bebe3863a6781db_fhprg_edlauth.bin qualcomm/factory/sd765/0000000000720000_1bebe3863a6781db_fhprg.bin qualcomm/factory/sdm662/0014d0e100000000_d40eee56f3194665_FHPRG.bin xiaomi/0010a0e100720000_1bebe3863a6781db_fhprg.bin xiaomi/001360e100720000_1bebe3863a6781db_fhprg_redmi9t.bin xiaomi/0014d0e100000000_1bebe3863a6781db_fhprg.bin xiaomi/EDLAuth/0000000000720000_1bebe3863a6781db_fhprg_edlauth_peek.bin xiaomi/EDLAuth/000950e100720000_1bebe3863a6781db_fhprg_edlauth.bin...

"Only nop and sig tag" is success. That is your loader. Unfortunately, since this uses authorization you have to either use some option here or else use a Xiaomi tool...

In the event of total primary storage Qualcomm processors go to 9008 (or sometimes 900e). You may be using the test points wrong. The must be shorted during the instant...

Try qualcomm/factory/sdm662/0014d0e100000000_d40eee56f3194665_FHPRG.bin The actual hash of this is "one baby", 1bebe... and it handles 001b80e1 SM_DIVAR.

I can't see what it's doing and the error message is less than intelligible. Power reset and try again, maybe with more verbosity. If you are rooted and can pull...

That's strange. Apparently it did not like the cert chain. I think we're talking USB noise/corruption here. Try another box, another OS, another port, another cable.

Well, Xiaomi already makes it suspicious. I don't see any HWID or OEM or model limitations in the certs It doesn't seem to like the hashes/signature/certs chain somewhere.

Can you get the sbl/xbl out of an update or off the device?