Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamDescription: [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
• 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.
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”).
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.
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.
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.
• 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).
Low-level sequence with STTool V3.81_12_MOD:
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”.
• 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.
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).
• 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.
• 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.
Your USB key is locked by the Phison PS2251-19 firmware. Consumer-level tricks (diskpart, registry) cannot clear it.
