Phison GetInfo Explained: Commands, Outputs, and Examples

Extracting SMART and Firmware Data with Phison GetInfo

Overview

Phison GetInfo is a lightweight Windows utility for reading detailed controller, firmware, and SMART information from USB flash drives and SSDs that use Phison controllers. It’s useful for inventorying devices, diagnosing failing flash memory, checking firmware versions, and extracting device metadata even when a volume is unreadable (via ENC files).

What You Can Retrieve

• Controller model and vendor (VID/PID)
• Firmware version and build date
• Serial number and product string
• Capacity and NAND / memory vendor (when available)
• SMART-like health metrics (error counts, program/erase cycles, NAND status)
• Power and LED settings, write-protect status, password/AES flags
• ENC file data (for corrupted drives)

When to Use GetInfo

• You need firmware or SMART data to verify updates or compatibility.
• A flash drive isn’t mounting but you want controller metadata (use ENC).
• Preparing a fleet inventory of USB/SSD devices.
• Troubleshooting suspicious behavior (slow writes, read errors).

Safety and Requirements

• Windows OS (portable executable versions are common).
• The drive must use a Phison controller supported by the GetInfo build you use; older/newer controllers sometimes are unsupported.
• Run with administrative privileges for full device access.
• Back up any important data before running repair/formatter tools — GetInfo itself is read-only if you use only the Read functions.

Step-by-step: Extract SMART & Firmware Data

1. Download and extract GetInfo (portable archive) from a trusted source.
2. Run GetInfo as Administrator.
3. Insert the Phison-based USB/SSD and wait for the tool to detect the device.
4. Select the target device from the device list (VID/PID and capacity help identify it).
5. Click “Read” or the equivalent action to populate fields.
6. Review displayed fields: controller model, FW version, serial number, NAND maker, capacity, SMART counts.
7. If the drive is corrupted and unreadable, load its ENC file (if available) via the ENC/Open option to view stored controller info.

Interpreting Common Fields

• FW Version: Compare against vendor/Phison release notes—mismatched or old firmware can explain instability.
• SMART/Error Counts: Elevated read/erase/program error counters indicate NAND wear or failing blocks.
• Program/Erase (P/E) Cycles: High cycles suggest nearing NAND endurance limits.
• AES/Password Flags: Show whether hardware encryption or a password is enabled.
• Vendor Strings: Identify counterfeit or rebranded sticks when vendor strings don’t match expected manufacturers.

Example Troubleshooting Workflows

• Slow writes + normal SMART: check partitioning, filesystem, and host USB port speeds.
• High error counts or rising P/E cycles: plan data migration and replace device.
• Firmware older than current Phison release: check Phison or OEM for firmware updates; follow vendor update instructions precisely.
• Drive not mounting but GetInfo shows controller: try reading ENC or use low-level recovery tools (avoid writing).

Limitations & Caveats

• Not all Phison controllers are supported by every GetInfo version; you may need a matching older/newer build.
• The tool’s output varies by controller generation—some fields may be blank.
• GetInfo is primarily diagnostic; do not use it as a firmware flasher unless you understand firmware update risks and have official images.
• Obtain tools and firmware only from reputable sources (manufacturer/Phison) to avoid malware or bricked devices.

Quick Checklist Before Acting

• Backup data if drive is readable.
• Record controller model, FW version, serial, SMART counts.
• If replacing device: use serial + model for inventory/RAID/asset records.
• If updating firmware: verify official image and follow vendor instructions; ensure uninterrupted power.

Useful Resources

• Phison support/blog and OEM firmware pages for official firmware updates.
• Device-specific forums and databases for controller/FW mappings and known issues.
• Tools commonly used alongside GetInfo: Phison MPALL/UP tools and manufacturer formatters (use cautiously).

If you want, I can:

• Provide a concise table mapping common Phison controller models to likely compatible GetInfo versions, or
• Walk through interpreting a sample GetInfo output (paste the output here).