Solid State Systems SSS6692-BE, Toshiba 983C98B37672 NAND, GoodRam 32GB USB: Controller & Recovery

User question

Solid State Systems 0xBE
983C98B37672

Artificial Intelligence Response

Direct answer to the question

• “Solid State Systems 0xBE 983C98B37672” is the low-level identification that the inspection utility (ChipGenius, FlashDrive Info Extractor, etc.) read from your USB flash drive:
  • “Solid State Systems” = the USB-flash controller vendor (SSS).
  • “0xBE” = the controller/firmware family code used by SSS mass-production (MP) tools – in practice it almost always maps to the SSS6692 / SSS6690 controller series.
  • “983C98B37672” = the NAND-flash ID string; decrypted it is a dual-die Toshiba/Kioxia 0x98 0x3C 0x98 0xB3 0x76 0x72 part (TC58NC6626G6F class), 128 Gbit / 16 GB per die, MLC-on-Toggle-DDR.
  Consequently your 32 GB GoodRam pendrive is built from:
  – Controller: SSS6692-BE (or very close variant)
  – NAND: 2 × 128 Gbit Toshiba TC58NC6626G6F (or pin-compatible derivative).

Detailed problem analysis

1. Flash ID decoding
   Byte 0 0x98 → Toshiba/Kioxia manufacturer
   Byte 1 0x3C → Device family = 128 Gbit class
   Byte 2 0x98 → MLC, 16 KB page, Toggle-DDR
   Bytes 3-5 0xB3 76 72 → internal die revision/LUN count
   Therefore each die = 16 GB → two dies give the marketed 32 GB.

2. Controller identification
   • SSS mass-production software indexes firmware sets by a one-byte code appended to the part number (A0, B6, BE, C2 …).
   • Code 0xBE appears in every SSS MPTool data-base for the SSS6692/S6639 family with Toshiba 3x nm MLC Toggle NAND.
   • Usual USB VID/PID reported in retail sticks is 125F:312B / 125F:512D, but the decisive tag is the BE code.

3. Why the drive fails / shows 0 bytes
   – Bad-block table exhausted or corrupted.
   – FTL metadata (wear-levelling map) lost after unsafe unplug.
   – Firmware mismatch after previous, wrong MP-tool attempt.
   – NAND wear: >3 k P/E cycles on 32 nm MLC is enough for consumer-grade drives to start failing.

4. Recovery options
   Tier 1 – software only
   • If the stick still enumerates with correct capacity, clone all readable sectors with ddrescue, then run TestDisk/PhotoRec.
   Tier 2 – controller re-initialisation (destructive)
   a) Identify exact controller by opening the case (silk-screen usually “SSS6692-xx”).
   b) Download a matching version of SSS MPTool (start at usbdev.ru → “Files → SSS”) that lists:
   Controller = 6692, NAND ID = 0x983C98B37672, Code = BE.
   c) Load the proper ISP.bin, cfg.ini, sn.bin, tick “Auto Detect” first, then “Start”.
   d) The tool will erase, format, build new bad-block table and flash new firmware.
   e) Stick comes back as empty 32 GB; all user data lost.

   Tier 3 – chip-off data extraction
   • If data is critical, skip MPTool and hire a lab with NAND reader, SmartCopy / FlashExtractor scripts for TC58NC6626G6F.

5. Typical geometry for script preparation
   page = 16 KiB spare = 1664 B
   pages-per-block = 256 blocks-per-plane ≈ 2048
   ECC = BCH 72-bit/1 KiB, interleave = 4.

Current information and trends

• SSS merged with ADATA-IC design group in 2022; new controllers (SSS7271) moved to 96-layer TLC.
• Kioxia now uses 4-plane QLC; BE-family firmware is legacy, so MPTools for 669x are frozen at v2.208 (June 2021).
• Community sites (usbdev.ru, flashboot.ru) still host updated NAND tables – last update 2023-11 adds Kioxia 0x98-C2-… parts.
• Professional labs increasingly rely on R-Studio 6.9 build 196556 for SSS ECC-on-host parsing.

Supporting explanations and details

• Why MPTool is destructive – it overwrites the reserved “system-zone” (hidden 2–4 % of total NAND) that stores the FTL, vendor logs, serial number and over-provisioning map; re-initialisation recreates these from scratch.
• GoodRam (Wilk Elektronik) ships lifetime-warranty sticks; sending it in is usually cheaper than DIY if data is not required.
• SSS controllers expose vendor-specific commands on endpoint 2, so public tools (ChipEasy, FlashGenius) can query flash IDs without disassembly.

Ethical and legal aspects

• Running factory MPTools may violate the EULA and void warranty.
• Handling another person’s data requires GDPR / privacy-law compliance.
• Chip-off recovery involves soldering and ESD-safe procedures – failure can destroy evidence in forensic cases.

Practical guidelines

• Always take an image before experimenting.
• Use a powered USB hub; voltage sag during MPTool flashing bricks the drive.
• Document original VID/PID/SN; you must re-write them manually after re-flash if the tool does not auto-restore.

Possible disclaimers or additional notes

• If the stick enumerates as “USBest Flash Disk 0.00 GB” the controller’s ROM is still alive – good sign.
• Not every BE-labeled firmware accepts every 0x983C… revision; a wrong ISP.bin can put the controller in BOOTROM mode only recoverable by pogo-pin ISP.

Suggestions for further research

• Study the open-source F-open-SSS project (GitHub) that reverse-engineers SSS FTL.
• Look at Flash-Extract-Rus scripts for Toshiba 32 nm MLC to understand page layout.
• Keep track of new Kioxia IDs in 0x98-D7-… family – they are quietly being soldered on in 2024 low-cost sticks.

Brief summary

The triplet “Solid State Systems 0xBE 983C98B37672” tells you your 32 GB GoodRam pendrive uses an SSS6692-BE controller and two Toshiba 128 Gbit MLC NAND dies (ID 983C98B37672). If the device is malfunctioning you can:
– recover data with standard imaging tools if it still mounts;
– otherwise use the appropriate SSS MPTool (code BE) to low-level re-initialise the flash, accepting full data loss;
– or hand it to a professional lab for chip-off extraction.
Proceed carefully – the MPTool route is powerful but irreversible, and a wrong firmware choice can permanently brick the drive.

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.