logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Phison PS2251-19 (PS2319) USB DISK 3.0 Write Protection Removal for Toshiba TLC Flash

Ask a question on the Forum

User question

Description: [D:]Dispositif de stockage de masse USB(USB DISK 3.0)
Device Type: Mass Storage Device

Protocal Version: USB 3.20
Current Speed: High Speed
Max Current: 504mA

USB Device ID: VID = 6557 PID = 0031
Serial Number: 07214201F21A0713

Device Name: USB DISK 3.0
Device Revision: 0110

Product Model: USB DISK 3.0
Product Revision: PMAP

Controller Vendor: Phison
Controller Part-Number: PS2251-19(PS2319) - F/W 10.06.5D [2023-05-02]
Flash ID code: 9848980376E4 - Toshiba [TLC]

Lecteur Flash bloqué en écriture ... recherche d'une application pour déblocage

Artificial Intelligence Response

Direct answer to the question

• For a Phison PS2251-19 (PS2319) stick that has switched itself to read-only, the only utilities known to remove the controller-level write-protection are Phison factory tools.
• The most commonly used and currently available package is the community-patched STTOOL V3.81_12_MOD (also called STTool_V381_12_SZ_20210618_MOD) which explicitly supports PS2251-19 / PS2319 and bypasses the OEM whitelist.
• If STTool does not recognise the drive, fall back to the Phison MPALL/MPTool suite ( ≥ v5.03 for PS2319).
• Both tools perform a low-level re-initialisation: all data on the stick will be lost and the operation may fail if the NAND is at end-of-life.

Key points
– Download: flashboot.ru (file ID 697) or usbdev.ru → Phison → STTool V3.81_12_MOD.
– Run the tool as Administrator, preferably on a native USB-2.0 port, and select “Erase / Format” + “Remove write-protection”.
– If the controller reports too many bad blocks, the lock is irreversible and the drive must be replaced.

Detailed problem analysis

  1. Device recap
    • VID/PID = 6557:0031 • Controller = Phison PS2251-19 (PS2319) • FW 10.06.5D (2023-05-02)
    • NAND ID = 0x9848980376E4 → Toshiba 96-L TLC
    • USB 3.2 Gen 1 device but enumerates only at High-Speed (another indicator of “safe/read-only mode”).

  2. Why the stick is locked
    The Phison firmware implements a SMART-like wear-level counter. When:
    – bad-block count > vendor threshold, or
    – uncorrectable ECC events occur, the ROM sets a flag (often in hidden CIS area) that forces the drive into read-only safe-mode. Normal OS commands, Windows registry tweaks or diskpart cannot clear this flag.

  3. Tool selection rationale
    • STTool / ST-TOOL: lightweight, GUI based, includes one-click “Remove WP” for PS2251-xx controllers. The MOD build strips the factory VID/PID whitelist so generic flash drives are accepted.
    • MPALL / MPTool: the factory production environment; deeper access, allows burner-code upload and complete NAND remap. Needs the correct burner file BN19xx.bin and firmware FW19xx.bin.

  4. Expected outcomes
    • Success: controller re-initialised, new logical mapping table written, drive becomes writable and shows full capacity.
    • Failure codes such as 0x72, 0xA0 in MPALL point to exhausted NAND; replacement is the only remedy.

Current information and trends

• Since 2022 Phison introduced “Secure ROM” in late PS2251-19 batches: once the life-time counter trips, the read-only flag is fused and cannot be cleared even by MPALL (confirmed by multiple 2023 forum reports).
• Community-patched STTool remains the first try because it does not need burner/firmware files.
• Ongoing work in data-recovery forums focuses on decrypting the new secure ROM header; no public fix yet (Q2-2024).

Supporting explanations and details

Low-level sequence with STTool V3.81_12_MOD:

  1. Extract the 7-zip archive, run STTool.exe as Administrator.
  2. Insert the USB stick in a USB-2.0 port → appears in slot #1.
  3. Press “Check” → controller info should match PS2251-19.
  4. Tick “Erase” + “Remove Write-Protect”, leave VID/PID default or customise.
  5. Click “START”. Progress bar turns green if finished without error (PASS).

If STTool shows “Device not supported” → switch to MPALL 5.03 procedure:
• Edit parameters with MPParamEdit_F1.exe → select PS2319, set “Flash type auto-detect”, load supplied BN19 / FW19 files, save.
• Start MPALL_F1_9000_v503_0D.exe, connect stick, click “Start”.

Ethical and legal aspects

• Phison MP/ STTool packages are intended for OEM use; redistribution violates the NDA. Downloading “MOD” builds is tolerated in many countries but remains legally grey.
• Using these tools irreversibly erases user data – obtain explicit consent if you are repairing a customer’s device.
• Be aware of export regulations on cryptographic firmware if you redistribute modified tools.

Practical guidelines

Best practice checklist
✓ Use a desktop PC, rear-panel USB-2.0 port (avoids XHCI power-saving issues).
✓ Disable antivirus during the process (tools use raw-USB access).
✓ Record original VID/PID and serial number; tools may overwrite them.
✓ If the first pass fails, try reducing “Bad Block Limit” in MPALL to 2 % and rerun.
✓ Never interrupt power during low-level format.

Potential challenges and mitigation
• “Drive not enumerated” → short D+ / D– pins for 5 s before plug-in (forces Test-mode).
• Vendor burner file mismatch → search the same date-code as your FW (10.06.x).

Possible disclaimers or additional notes

• There is no guarantee of success; modern TLC NAND often reaches endurance limits long before user notices.
• If the controller entered final read-only mode, only chip-off NAND extraction can recover data.
• Any tool or firmware not explicitly compiled for PS2251-19 may brick the device – proceed at your own risk.

Suggestions for further research

• Monitor forums usbdev.ru, flashboot.ru, elektorda.com for updates on PS2251-19 secure-ROM bypass.
• Investigate open-source projects like openPhison (early 2024 initiative) that aim at generic Phison register access via libusb.
• Follow IEEE IRPS papers on NAND end-of-life indicators to anticipate future controller behaviours.

Brief summary

Your USB key is locked by the Phison PS2251-19 firmware. Consumer-level tricks (diskpart, registry) cannot clear it.

  1. Try STTOOL V3.81_12_MOD (download link file 697 @ flashboot.ru).
  2. If not detected, use Phison MPALL ≥ 5.03 with matching BN19/FW19 files.
  3. Expect full data loss; success depends on remaining NAND health.
  4. If both tools fail with NAND-health errors, the stick is beyond repair – replace it.

User question

after detection in sttool what to do?

Artificial Intelligence Response

Direct answer to the question

  • If STTool has detected your USB drive (Phison PS2251‑19/PS2319), do this:
    • Tick “Erase” and “Remove Write‑Protect”.
    • Leave VID/PID and capacity on “Auto/Default” for the first attempt.
    • Do not tick “Low‑Level Format” on the first pass.
    • Click START, wait for PASS, allow the device to re‑enumerate, then format it in the OS (exFAT or NTFS) and test writes.
  • If it fails, note the exact error and retry on a rear USB 2.0 port with Administrator rights. If it still fails, move to Phison MPALL (same controller family) and attempt a full re‑initialize.

Detailed problem analysis

  • What STTool is doing

    • Erase: clears the FTL (mapping tables) and rebuilds device metadata.
    • Remove Write‑Protect: clears the controller’s WP flag if it is set in firmware/NVRAM.
    • Low‑Level Format (LLF): performs a full NAND scan, re‑maps bad blocks, and can take a long time; use only if the quick pass fails.

  • Recommended first pass (fast and safe)

    • Only “Erase” + “Remove Write‑Protect”.
    • Defaults for VID/PID/strings; do not customize unless you must restore branding.
    • Avoid hubs/docks. Use a direct motherboard port; power stability matters during controller re‑init.

  • What a successful cycle looks like

    • Progress moves through Erase → WP clear → Verify.
    • Status turns green, shows PASS, device disconnects/reconnects once.
    • After Windows/macOS shows the drive, do a normal file‑system format, then test writes.

  • If STTool fails: how to interpret typical symptoms

    • Write‑Protect error remains: controller refused to clear WP (possible secure lock or media‑health trigger).
    • Device Lost / disconnect mid‑run: marginal USB power or flaky cable/port.
    • Stuck at 0–1%: mismatch between tool/firmware build and your controller, or NAND ID not recognized by this build.
    • Capacity error: auto‑detect failed; try again with LLF enabled, or proceed to MPALL.

  • Escalation path

    • Second attempt: run as Administrator, disable antivirus temporarily, switch to a rear USB 2.0 port, try again with “Low‑Level Format” additionally ticked.
    • Next tool: use Phison MPALL for PS2251‑19/PS2319 with the appropriate burner/firmware set for your controller revision. MPALL performs deeper NAND characterization and can succeed where STTool stops.

  • Health and endurance realities

    • If the NAND has exceeded the controller’s bad‑block threshold, the firmware will keep the drive read‑only for data integrity; no consumer tool can safely reverse that.
    • If WP originates from a secure ROM fuse path on newer lots, software WP removal will not persist or will be refused.

Current information and trends

  • For PS2251‑19/PS2319 devices, STTool or MPALL remain the practical service utilities in 2025 for re‑initialization and WP clearing.
  • Newer controller/firmware builds increasingly enforce permanent read‑only on media‑health or security triggers; field bypasses are not generally available. Expect higher failure rates when NAND wear is high and when secure features are enabled.
  • MPALL versions in the 5.x line are commonly used for PS2319; choose a package that explicitly lists your controller/NAND family.

Supporting explanations and details

  • Why not enable Low‑Level Format first? It lengthens the cycle and stresses worn NAND. Start with the minimal, non‑destructive controller reset (Erase + WP clear) to see if the WP is purely logical.
  • Why a rear USB 2.0 port? USB 3.x front‑panel headers and hubs can brown‑out briefly during re‑enumeration; rear ports are typically on the motherboard power plane and more stable for service operations.
  • Post‑repair verification:
    • Format exFAT for cross‑platform use or NTFS for Windows.
    • Run a write/read test (e.g., H2testw/F3) on at least several GB to confirm stability and full capacity.

Ethical and legal aspects

  • These tools erase all data. Ensure you own the device and consent to data destruction.
  • Using manufacturer service utilities and non‑public firmware bundles may violate license terms; proceed at your own risk.
  • For drives that may contain personal data, consider secure disposal if media health is failing rather than forcing write‑enable.

Practical guidelines

  • Environment prep:
    • Close other USB/storage tools; run STTool as Administrator.
    • Disable USB selective suspend (Windows Power Options) during the operation.
    • Avoid long USB cables and hubs.
  • Execution checklist:
    • Detect → tick Erase + Remove WP → START → wait for PASS → re‑plug → OS format → write test.
  • Troubleshooting quick hits:
    • Still WP after PASS: unplug 10–15 s, change port, reboot, and verify again.
    • Repeated FAIL with health‑related messages: proceed to MPALL; if MPALL reports too many bad blocks, the drive is end‑of‑life.
    • No detection: try another PC; if still absent, the controller may be in a fault state requiring ISP/test‑pad access (advanced, not recommended without proper fixtures).

Possible disclaimers or additional notes

  • Using mismatched burner/firmware in MPALL can brick the controller; only use sets known for your controller revision and NAND ID.
  • Enabling LLF on heavily worn NAND can accelerate failure; use once for recovery, not repeatedly.
  • Physical “short to force ISP” techniques risk hardware damage; avoid unless you have board‑level access and experience.

Suggestions for further research

  • Identify your exact controller revision and NAND ID from the STTool log; obtain an MPALL package that lists that combo explicitly.
  • Review community repair notes specific to PS2319 and your NAND vendor/die (e.g., Toshiba/Intel/Micron TLC) to choose correct parameters (bad‑block thresholds, CE/plane config).
  • If data recovery is the true goal, stop here and consult a professional before any erase/LLF operation.

Brief summary

  • After detection in STTool: select Erase + Remove Write‑Protect, leave defaults, click START, wait for PASS, re‑plug, format, and verify writes. If it fails, retry with a stable USB 2.0 port and Administrator rights; then escalate to MPALL. If health or secure WP limits are reported, the device is likely unrecoverable for safe write use.

Ask additional question

Wait...(2min)
Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.
Report illegal content (Article 16 DSA)