Phison Mpall V3720b Ps2251 Flashboot — Repack

After reviving your drive, the “FlashBoot” part of the repack allows you to write a bootable image immediately.

The term "FlashBoot Repack" in this context refers to the process of reprogramming the drive's firmware and flash memory parameters to restore functionality.

Why is this necessary?


Locate a trusted source for the file named MPALL_v3.72.0B_PS2251_FlashBoot_Repack.7z or .zip. Extract to a short path like C:\MPALL_372.

Once the drive is detected by MPAll:

  • Burner File: A burner file (binary firmware) compatible with v3.72.0B is loaded into the buffer.
  • Without the correct driver, MPALL won’t see your drive.

    While this repack is excellent, it’s not always the answer: phison mpall v3720b ps2251 flashboot repack

    | Situation | Better Choice | |------------|----------------| | Your drive uses a Phison PS2251- 68 (common in Sandisk clones) | Phison’s “ST Tool” (ST_2.0.93) | | You only need to fix partition corruption | Windows DiskPart → clean command | | You want to change the USB’s serial number | MPALL can do this, but “Phison SP Tool” is safer | | Your drive has a different controller (e.g., Alcor AU6990) | AlcorMP tool | | You’re on macOS or Linux | Use badblocks + mkfs for low-level; or run MPALL via Windows VM with USB passthrough |


    Some drives come with a hardware write-protect switch. Others get stuck in a software write-protect state after a failed Windows format. The FlashBoot repack includes a “Preformat” mode that ignores write protection and wipes the drive’s system area. After reviving your drive, the “FlashBoot” part of

  • Connect PC and run MPALL as Administrator.
  • Select correct COM/USB entry that MPALL reports for the device.
  • Load the repack package in MPALL’s interface or place it in the expected folder/name per the MPALL build.
  • Start flashing; monitor progress bars and logs.
  • After completion, remove and reinsert device; verify normal USB enumeration and capacity.
  • If flashing fails, review MPALL log, try different loader/firmware, or restore original ROM.