Sss6698-bb: Usbdev

Technical Write-Up: SSS6698-BB USB Device

4. Diagnostic and Repair Tools (SSS MPTool)

The SSS6698-BB is notable in the data recovery community because it is programmable using the SSS MPTool (Mass Production Tool).

Unlike some proprietary controllers (like SanDisk or Kingston), SSS controllers are highly accessible for hobbyist repair. If a drive becomes "read-only" or is not recognized by the OS, technicians often use the MPTool to:

  1. Re-flash the Firmware: Restore the controller’s operational code.
  2. Low-Level Format: wipe the drive completely to restore functionality (destroying data in the process).
  3. Configure Parameters: Adjust the type of NAND flash memory being used, allowing technicians to swap memory chips onto the controller board if necessary.

Fixing the "SSS6698-BB USBDev" Issue (Non-Data Recovery Approach)

If you do not need the data and simply want to restore the flash drive to working order, you will need to perform a low-level format or firmware reload using the controller's proprietary factory tool. This process is called "mass production."

Warning: This process will completely erase all data on the NAND chip. Do not proceed if you need to recover files. sss6698-bb usbdev

3. Common Applications

8. Identification (for end users)

ChipGenius (Windows) output example:

Controller Vendor: SSS( Silicon Motion )
Controller Part-Number: SSS6698-BB
Flash ID: 0x45,0xDE,0x94,0x32,0x64,0x12

USB VID/PID often spoofed as 0x090C (SMI) or 0x1000 (SSS).

Frequently Asked Questions (FAQ)

Q: Can I update drivers to fix SSS6698-BB USBDev? A: No. This is a firmware/hardware issue, not a driver issue. No Windows driver update will restore the mass storage function. Technical Write-Up: SSS6698-BB USB Device 4

Q: My drive shows as "SSS6698-BB USBDev" but also has a drive letter. A: That is unusual. It likely means the drive partially enumerated. Try chkdsk X: /f (replace X with drive letter). But back up data first.

Q: Does Linux recognize SSS6698-BB drives better? A: Linux will detect the ROM mode but cannot mount it as a block device. However, lsusb -v may provide additional debug descriptors useful for specialist tools.

Q: Is the SSD6698 the same as SSS6698? A: No. SSD6698 is a different (often fake) labeling. Real SSS6698 controllers say "Solid State System" or "SMI" on the chip. click "Auto Detect". If auto-detect fails

When to Replace the Drive

Not every SSS6698-BB USBDev is repairable. If you encounter the following, the hardware is dead:

In these cases, the cost of professional recovery exceeds the value of a new 64GB flash drive ($10-$15). Buy a replacement from a brand that uses more reliable controllers (e.g., SM3267, IS903).

3. Architecture and Flash Management

The SSS6698-BB implements a simple memory-to-host bridge with the following internal blocks:

The controller uses a simple FAT-compatible translation layer (similar to FTL – Flash Translation Layer) but lacks advanced features like dynamic caches, TRIM, or full random write optimization.

Configuration Steps

  1. Extract the tool to a short path like C:\SSS_MP.
  2. Run SSTool.exe (as Administrator).
  3. Click Setting (Password is usually empty or 320).
  4. Go to the Scan USB tab:
    • Click "Update All" – your SSS6698-BB should appear.
    • If not, manually enter the VID/PID you recorded earlier.
  5. Go to the Parameter tab:
    • Vendor Name: Change to a generic name (e.g., "USB Drive").
    • Product Name: Change to "USB Disk".
    • LED Setting: Leave default.
  6. Go to NAND Setting:
    • Critical: Select the correct NAND type. If unsure, click "Auto Detect". If auto-detect fails, you must know the chip.
  7. Check Low Level Format.
  8. Click OK, then click Start.
  9. Wait 5-15 minutes. The progress bar will turn green.