Request: Firehose loader for Qualcomm QCS5430 (TurboX C5430P) — PK_HASH 53c01497
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- devtools
Research direction
Start by checking the repository’s loader catalog and the EDL loader-matching workflow; the issue names no files or tests. The requested TurboX C5430P BSP loader is not provided, so first determine whether it can be obtained. Done means adding a loader that matches the supplied PK_HASH and works for the device; the issue reports existing loaders fail with a mismatch.
Written by the indexing model from the issue text.
Description
I am looking for a prog_firehose_ddr.elf for the following device:
Device: Thundercomm TurboX C5430P SOM (Qualcomm QCS5430 / SM7325)
EDL Sahara identifiers:
HWID: 0x0020f0e1022f0088
MSM_ID: 0x0020f0e1
OEM_ID: 0x022f
MODEL_ID: 0x0088
PK_HASH: 53c014971a6e7df503ce0c0c72f752bacc367157db104dc50bd949c4b6b2d1d45c09849e8e816e6bb1ea62a26744a639
Serial: 0xad1d920e
The device has locked fastboot and secure boot. The generic Kodiak/SM7325 loaders from Armbian qcombin repo do not match (different PK_HASH).
The loader likely ships inside Thundercomm's TurboX C5430P Android BSP (FlatBuild package). If anyone has access to this BSP and can share the prog_firehose_ddr.elf, it would be greatly appreciated.
All EDL tools and matching loaders tested so far fail with "No such device" after Sahara upload — confirmed PK_HASH mismatch.
- Dominant language
- Python
- Stars
- 555
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bkerler/Loaders
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ida-arbeitszeit/workers-control#1578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws-samples/sample-per-model-bedrock#898 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
intake mcp-intake needs-human-review priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Ikalus1988/MisakaNet#5041 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100