Modifying the raw firmware (often 8051-based code) using a compiler like SDCC to include new features like HID emulation or hidden partition defines.
Sending the modified .bin file back to the controller using a "burner image"—a temporary piece of code that allows the controller to accept new firmware. Risks and Precautions
One of the most common reasons for patching is to implement BadUSB . By embedding a keyboard (HID) payload into the firmware, the USB drive can "type" malicious commands into a host computer at lightning speed the moment it is plugged in. phison ps225109 patched
Applying a patch to your Phison controller is generally done for three primary reasons:
is a versatile micro-controller designed to support various NAND flash types, including 3D TLC and MLC. Its ubiquity makes it a prime target for firmware modding. Under standard retail conditions, the firmware is configured for "Mode 3," acting as a simple mass storage device. However, by applying patches, users can transform the device into a powerful tool for security auditing or data protection. Why Use a Patched Modifying the raw firmware (often 8051-based code) using
Using a utility like DriveCom to extract the existing firmware from the drive for backup.
Flashing a new firmware almost always results in the total loss of all data currently stored on the NAND flash. By embedding a keyboard (HID) payload into the
Patched firmware can create "hidden" or "secure" partitions that are invisible to the operating system unless unlocked via a specific command or password.
If the firmware flash fails, the device may no longer be recognized by the PC. In some cases, you must manually short "Ready/Busy" pins on the controller to force it into "test mode" to attempt a recovery.
For forensic or data-integrity purposes, a patch can be applied to make the drive permanently read-only, preventing any accidental data modification or virus infection. The Patching Process: Key Tools and Concepts