Kingston DataTraveler 3.0 VID 0951 PID 1666 Flash Utility for Phison PS2251‑07 PS2319

User question

vid 0951 pid 1666 утилита для прошивки флешки

Artificial Intelligence Response

Direct answer to the question

• The VID 0951 / PID 1666 USB stick is a Kingston DataTraveler 3.0 family device. Most samples with this ID use Phison controllers, typically PS2251‑07 (aka PS2307) in older DT100 G3/G4 units and PS2251‑19 (PS2319) in newer revisions. The correct flashing utilities are Phison’s mass‑production tools (MPALL/UPTool/Sorting Tool), chosen to match the exact controller and firmware on your drive. (usb-ids.gowdy.us)
• First identify the controller with ChipGenius/USBFlashInfo. Then:
  • If controller = PS2251‑07/PS2307 → use Phison MPALL for 2307 (e.g., v5.35.xx) with matching BN07 “burner” + FW07 firmware files. (flashboot.ru)
  • If controller = PS2251‑19 (PS2319) → use the PS2319 service/MP tools (e.g., STTOOL_V381_12 or MPALL v5.35.6x/v6.0.00 with PS2319 support). (flashboot.ru)

Detailed problem analysis

• Why VID/PID isn’t enough
  • 0951:1666 maps to multiple Kingston DataTraveler 3.0 models (DT100 G3/G4/SE9 G2/DT50/Kyson). Kingston reuses this ID across different hardware revisions and flash generations; only the on‑board controller type (Phison PS22xx/PS23xx family) determines the correct MP tool and parameterization. (usb-ids.gowdy.us)
• What controllers are actually seen with 0951:1666 in the field
  • PS2251‑07 (PS2307): Very common in 2013–2018 DT100 G3/G4 units; numerous iFlash/field reports show 0951:1666 with PS2307 and Hynix/Toshiba TLC NAND. Typical firmware lines: “F/W 01.xx.53”, “05.00.50”, “08.03.50”. (flashboot.ru)
  • PS2251‑19 (PS2319): Found in newer DataTraveler 3.0/Kyson‑era sticks also reporting 0951:1666; tools indicate MPALL v5.35.64–v6.0.00 generations and a dedicated PS2319 service package. (flashboot.ru)
• Tool selection logic (Phison)
  • MPALL (Mass Production ALL) is the factory reflash/repair suite for PS2251/PS23xx. Each controller/firmware family needs a matching “burner” (BNxx) and firmware (FWxx) files, sometimes an ID_BLK. Using the wrong combo leads to “No Flash support”, “ct‑isp fail 0x1102”, or bricking. Field threads for PS2307 DT100 G3 show exactly these symptoms when versions don’t match. (reddit.com)
  • For late PS2319, vendors ship a service tool (e.g., STTOOL_V381_12) or MPALL 5.35/6.0 builds with PS2319 device tables. User submissions show PS2319 sticks with 0951:1666 needing these tool branches. (flashboot.ru)
• Boot/ISP (test) mode recovery
  • If the drive isn’t detected in normal mode, Phison controllers can be forced into boot/ISP mode via test pads/“short” method, after which MPALL/DriveCom can talk to the device. This method is documented in Phison research/BadUSB work and community guides; apply only if you understand the risks. (github.com)
• Why a generic “Kingston utility” seldom helps
  • Kingston public support pages provide generic formatting advice, not controller reflash tools. Low‑level repair requires Phison MP tools that are not officially distributed by Kingston. (kingston.com)

Current information and trends

• Hardware drift: Since about 2022, 0951:1666 increasingly appears with PS2319; these need newer toolchains (MPALL 5.35.6x/6.0.00 or PS2319 service tools) rather than the older PS2307 sets common for DT100 G3. (flashboot.ru)
• Community databases (FlashBoot iFlash) continue to log fresh samples tying 0951:1666 to PS2307 and PS2319 with specific NAND IDs and firmware trains, which is why controller detection first is essential. (flashboot.ru)

Supporting explanations and details

• Typical identification output (examples from field reports)
  • “Controller: Phison PS2251‑07(PS2307) — F/W 08.03.50 [2018‑05‑11]; Flash ID: AD3A1803 (Hynix TLC); VID=0951 PID=1666; Product: DataTraveler 3.0.” (ireepair.com)
  • “Controller: Phison PS2319 — F/W 10.05.5D; MP Ver: MPALL v5.35.64; VID=0951 PID=1666; Manufacturer: Kingston.” (flashboot.ru)
• Firmware version hints
  • iFlash forums note that certain firmware endings (.10/.53 vs .5D/.7D) track different NAND/parameter sets; mismatched tools will fail ISR/flash detect. Use a tool branch matching your displayed FW train. (flashboot.ru)

Ethical and legal aspects

• Warranty and support: Using factory MP tools is unofficial and can void warranty. If the drive is within warranty, replacement via Kingston is the safer route. (kingston.com)
• Supply‑chain trust: MP bundles from third‑party archives may be modified. Validate hashes and scan offline before use; prefer well‑known engineering repositories/community threads that document tool provenance. (flashboot.ru)
• Data privacy: MPALL erases and re‑maps NAND; all data is irrecoverably lost. Use professional data recovery if the contents matter.

Practical guidelines

1) Identify the controller and NAND

• Use USBFlashInfo or ChipGenius with only the target stick connected. Save the full text (Controller, Chip F/W, Flash ID, MP Ver). (ireepair.com) 2) Choose the correct toolchain
• If you see PS2251‑07 / PS2307:
  • Use an MPALL package that lists 2307 support (e.g., “MPALL v5.35.06” class). Ensure matching BN07 (burner) and FW07 files; try sets that correspond to your displayed FW train (01.xx.53, 05.00.50, 08.03.50, etc.). (flashboot.ru)
• If you see PS2251‑19 / PS2319:
  • Use the PS2319 service tool (e.g., STTOOL_V381_12) or MPALL with PS2319 tables (5.35.64/5.35.67/6.0.00, per your MP Ver). These builds are documented for 0951:1666 with PS2319. (flashboot.ru) 3) Preparation
• Connect directly to a reliable USB port (avoid hubs). Close all disk tools. Run MPALL as Administrator. If detection fails in USB 3.x, try a native USB 2.0 port (or vice‑versa) so the device enumerates predictably. 4) If not detected: enter boot/ISP mode (advanced)
• For Phison, short the controller’s boot pads momentarily on plug‑in to force ISP mode, then run MPALL/DriveCom. Only attempt with a proper board view or verified guide; wrong pads can kill the device. (github.com) 5) Configure and run MP
• Load the correct BNxx (ISP/Burner) and FWxx images; leave default timing unless a guide specific to your Flash ID recommends changes.
• Start the process; expect 1–5 minutes. On success, the device will re‑enumerate; partition/format in OS. 6) Post‑check
• Run a quick full‑capacity verification (H2testw/F3). If bad blocks explode or speed collapses again, the NAND is likely worn out—replace the drive.

Possible disclaimers or additional notes

• Not all 0951:1666 sticks are Phison; rare variants exist. If your diagnostic shows a non‑Phison controller, stop and use that vendor’s MP tool instead.
• Some write‑protected states are permanent due to NAND failure; even proper MP tools won’t clear RO mode. Replacement is then the practical solution.

Suggestions for further research

• Provide your exact USBFlashInfo/ChipGenius readout (Controller, Chip F/W, Flash ID, MP Ver). With that, I can point you to a compatible MPALL/parameter set.
• Review current iFlash database entries for your Flash ID to match firmware families and known‑good tool versions. (flashboot.ru)

Brief summary

• 0951:1666 is Kingston DataTraveler 3.0. The right utility depends on the controller:
  • PS2251‑07 (PS2307) → Phison MPALL for 2307 + matching BN07/FW07 set. (flashboot.ru)
  • PS2251‑19 (PS2319) → PS2319 service tool (STTOOL) or MPALL 5.35.6x/6.0.00. (flashboot.ru)
• Identify the controller first with USBFlashInfo/ChipGenius; flashing with a mismatched tool can brick the drive. If data matters or the stick is under warranty, consider professional recovery or RMA instead. (ireepair.com)

If you share the diagnostic output (controller, FW, Flash ID), I’ll tailor exact tool versions and parameters for your unit.

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.