Skip to content

About

Samsung rescue & care kit — golden rules, scripts, and a real Galaxy A31 soft-brick rescue case study (Odin flash, SECURE CHECK FAIL debugging)

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

Repository files navigation

🛠️ PhoneRescueToolkit — Samsung Rescue & Care Kit

Built from a real rescue saga (Oct 2026): Galaxy A31 (SM-A315F) soft-bricked during OTA, misidentified as SM-A315G, wrong firmware rejected by hardware security (SECURE CHECK FAIL: param), correct firmware flashed via Odin → phone fully revived. Everything below is tested knowledge, not copied boilerplate.


⚡ THE GOLDEN RULES (learned the hard way)

  1. IDENTIFY THE MODEL FIRST. Read it from the Download Mode screen header (PRODUCT NAME: SM-XXXXX) — never from a blurry photo, never from memory.
    • A315F = international/India • A315G = SEA/LatAm/Australia • A315N = Korea
    • Wrong model firmware = FAIL! (Auth) / SECURE CHECK FAIL: param (phone rejects it, no damage)
  2. BIT VERSION RULE: firmware bit (5th char from end of build name, e.g. DXU5DXJ2) must be ≥ the phone's current bit. Never downgrade. Samsung bricks on rollback.
  3. CSC vs HOME_CSC: plain CSC_* = full wipe (rescue) • HOME_CSC_* = keep data (update). Rescue flash → plain CSC. Never load HOME_CSC into CSC slot.
  4. USERDATA slot stays empty. Checkbox unchecked. No exceptions.
  5. Never trust a battery mid-flash. Charge >50% before flashing, keep on USB the whole time.
  6. Deep-discharged phone (logo flash then black, off, unresponsive): leave on charger 25-40 min, NO button presses, then power. It wakes up.
  7. DATA CANNOT BE RECOVERED AFTER A WIPE on Android 10+ (FBE: keys destroyed in hardware keystore at reset — see 07_CASE_STUDY). Rescue = bring the phone back. Getting data back = backups made BEFORE (scripts in 06_SCRIPTS).

📁 What's in each folder

Folder Contents Status
01_ODIN Odin3 v3.14.4 (works for MTK Samsung; run from its own folder!) ✅ included
02_DRIVERS Samsung USB Driver v1.7.43.0 (install once; adds CDC/Modem for Download Mode) ✅ included
03_ADB platform-tools (adb/fastboot) — for alive phones: backups, info, recovery ⬜ download
04_MTKCLIENT MTK BROM exploit tool — dump partitions BEFORE wiping, unbrick MTK phones ⬜ download
05_FIRMWARE downloaded firmware zips live here, one subfolder per model+CSC ✅ in use
06_SCRIPTS PowerShell helpers (see below) ✅ included
07_CASE_STUDY the full A31 saga: what failed, why, timelines ✅ included

🔽 Missing downloads (2-minute jobs, need working GitHub/network)

Tool Where What it's for
platform-tools https://developer.android.com/tools/releases/platform-tools adb + fastboot (Windows zip) → unzip into 03_ADB
mtkclient https://github.com/MTK-bypass/mtkclient MTK BROM mode: full partition dumps (python mtk rl), unbrick dead-but-not-fried MTK phones. Needs Python + its USB drivers (pip3 install -r requirements.txt)
Frija / SamFirm https://github.com/slackingfred/frija (or samfw.com in a browser) downloads CURRENT official firmware for any model+CSC directly from Samsung servers

🌐 Firmware download recipe (works without any tool)

  1. Open https://samfw.com/firmware/<MODEL> (e.g. SM-A315F)
  2. Pick your region CSC (India = INS) → pick the NEWEST build (Bit = highest)
  3. "Download on Browser" (single full zip ~5-6GB)
  4. Extract into 05_FIRMWARE\<MODEL>_<CSC>_<BUILD>\
  5. Files must match model exactly (BL/AP/CP/CSC all start with same model code)

🚑 RESCUE PROCEDURE (soft-bricked Samsung, screen alive)

1. Phone → Download Mode:
   power off → hold Vol Up + Vol Down → plug USB → release keys → press Vol Up to confirm
2. Plug into PC → check detection:
   powershell: Get-PnpDevice | ? { $_.InstanceId -like '*VID_04E8*' }
   Want: "SAMSUNG Mobile USB Modem" + "CDC Composite Device", Status OK
3. Open 01_ODIN\Odin3_v3.14.4.exe (from its own folder!)
   - ID:COM box must show blue COMx + log "Added!!"
4. Load slots: BL → AP (slow, md5 check) → CP → CSC (plain!)
   Options tab: Auto Reboot ✓, F.Reset Time ✓, everything else OFF
5. START → 6-12 min → green PASS → phone auto-reboots
6. First boot: Samsung logo 2-5 min is normal. Bootloader-unlock warning = press Power to continue.
7. If "FAIL! (Auth)" → wrong MODEL or older BIT. Re-read rule 1 & 2.
8. If phone powers off after flash → battery: charge 25 min, no buttons, then power.

🧰 MAINTENANCE MODE (phone alive — do monthly!)

1. Google Photos backup ON (wifi-only)
2. WhatsApp → Chats → Chat backup → Google Drive → daily
3. Contacts sync ON (Google account)
4. Optional: mtkclient full dump  →  04_MTKCLIENT
   python mtk rl "backup_dir"          # reads ALL partitions incl. userdata (decrypted view
                                       # requires unlocked BL; system partitions fine regardless)
5. Smart Switch backup to PC monthly (apps+settings+data)

🧹 Hygiene

  • One firmware zip per model is enough once extracted; keep the zip as the backup.
  • Never flash a phone's firmware from a message link without checking the model on the device itself.
  • If Download Mode shows SECURE CHECK FAIL: <name> → the phone refused a file BEFORE writing: nothing got damaged. Find the right file, re-flash. This is Samsung security WORKING.

About

Samsung rescue & care kit — golden rules, scripts, and a real Galaxy A31 soft-brick rescue case study (Odin flash, SECURE CHECK FAIL debugging)

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages