Request Samsung SM-T530NU APQ8026 EDL Firehose Programmer — Specific HWID and PK_HASH*

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
embedded-iot

Research direction

The issue identifies the device, chipset, HWID, and PK_HASH, but does not name files, tests, or an entry point in the repository. Start by reading the repository’s loader inventory and contribution guidance to see how device-specific programmers are identified and documented. Done means locating a compatible Samsung-signed programmer or a reliable lead for finding it; the issue requests recovery guidance, not a code change.

Written by the indexing model from the issue text.

Description

Hello,

I'm searching for a compatible Qualcomm EDL programmer for a Samsung Galaxy Tab 4 SM-T530NU (2014), currently detected in Qualcomm 9008 mode.

  • Chipset: APQ8026 / MSM8x26
  • HWID: 008040E100000000
  • PK_HASH: 2037EF02C3A43BE4A39ACFAC9CA63678B27367F166FD448FFDA86C557921C915

We've examined numerous generic MSM8x26 programmers without finding a compatible Samsung-signed loader.

We confirmed that the SHA-256 of four concatenated Samsung root certificates extracted from the device's original boot firmware matches its PK_HASH exactly.

Does anyone have a compatible Samsung-signed Firehose, NPRG, or MPRG programmer for this model or hardware/signing combination?

The goal is strictly read-only eMMC USERDATA recovery to retrieve personal photographs. We must avoid flashing, formatting, or erasing the storage.

Any compatible binary, archive reference, or suggestion for locating the original Samsung programmer would be appreciated.

Thank you.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bkerler/Loaders

All issues in bkerler/Loaders

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.