8000 Request: DJI RC 2 / RC331 Firehose programmer — QCS5430, eMMC, PK_HASH 4d3b79c7 · Issue #166 · bkerler/Loaders · GitHub
[go: up one dir, main page]

Skip to content

Request: DJI RC 2 / RC331 Firehose programmer — QCS5430, eMMC, PK_HASH 4d3b79c7 #166

Open

Description

@Jayjay3623

I am recovering my own DJI RC 2 (RC331 / KATMAI-IDP), which stopped booting after an experimental system flash. Original stock partition backups are available. The controller responds to Sahara identification over USB 05c6:9008, but I do not have a verified compatible Firehose programmer.

Read from this controller:

  • HWID: 0020f0e101a80000
  • MSM ID: 0020f0e1
  • OEM ID: 01a8
  • Model ID: 0000
  • Platform: QCS5430 / Kodiak family
  • Storage: eMMC
  • OEM PK hash (SHA384):
4d3b79c7cd869227091b30af8d9b884a80f60aedece7a515300db391f8cd5a5da1def5a798e8f7f1d7fbb4a0c9dc496e

The outer DJI Root CA certificate in the saved original XBL hashes to the same value. Authentication-enable fuses have not been read, and no candidate loader has been uploaded, so I am not claiming an observed signature rejection.

Does anyone have a legitimately shareable RC331-compatible programmer, or a public service-package source containing one? A source URL, file SHA256, supported hardware IDs and successful Sahara/Firehose log would help verify it. I am looking for an actual EDL programmer rather than an OTA firmware .bin, Android rescue APK, or fastboot image.

Generic Xiaomi/Oplus/Samsung candidates inspected so far have different OEM roots; the published Action 5 Pro/RedMagic method targets a different processor. The aim is to read the live partition layout first and preserve calibration, RPMB and device-specific data before restoring stock.

Device serial numbers, account information and private backups are intentionally omitted. Thanks for any leads.

Activity

  1. Jayjay3623 commented on Nov 5, 2026

    @Jayjay3623
    Author

    Diagnostic update: only ELF headers and non-executable hash/signature metadata have now been transferred; no complete programmer or executable segment was sent, and no flash/erase commands were issued.

    The original DJI XBL metadata progresses to a request for its first code segment (offset 0x3000), where the probe stops. A copy differing by exactly one bit in the ECDSA signature disconnects/re-enumerates immediately after metadata; the unchanged original then progresses again. Offline ECDSA/SHA384 verification passes for the original and fails for that control. This is strong evidence of signature validation on this path, though authentication fuses were not read. Three non-DJI programmer candidates also disconnected at the metadata stage.

    The stock XBL contains XBLRamDump/Sahara code, but it is not a demonstrated Firehose programmer. We still need a legitimately shareable RC331-compatible signed programmer or a verified stock recovery procedure. The saved stock partitions are a partial backup, not a full-device backup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0