logo elektroda
logo elektroda
X
logo elektroda

Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions

Fidox1988 19356 17
Best answers

Which Phison MPALL version and what additional files or tools are needed to reflash an unresponsive Verbatim Store 'n' Go 32 GB flash drive?

First try Phison Format & Restore v3.21.0.0; if that does not help, use Phison MPALL v5.03.0A-DL07, but you must match the binary files to the exact flash memory chip or the process can fail completely [#18053546] To reflash it, first identify the controller and NAND type with tools like ChipGenius or Flash Drive Information, and if possible read the markings on the chip itself [#18054491] In this thread the controller was identified as PS2251-07, with NAND 3D TLC / TC58TFG8T22TA0D and flash ID 983C98B37671 [#18054491][#18058209][#18058009] A package for this type included MPParamEdit_F1_90, STTOOL_F1_90_v200_00_SZ, and MPALL_F1_9000_v389_0C [#18058208]
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 18053542
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    Hello.
    The Verbatim STORE 'N' GO 32 GB flash drive has died, it cannot be formatted in any way. Which version of MPALL to use and what else is needed to reflash it?

    Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions
  • ADVERTISEMENT
  • Helpful post
    #2 18053546
    procsa
    Level 31  
    Posts: 1777
    Help: 173
    Rate: 363
    First, try to use "Phison Format & Restore v3.21.0.0", if it doesn't help, you will need to use "Phison MPALL v5.03.0A-DL07", but you will need to match the binary files well, otherwise you will fail completely ....
  • ADVERTISEMENT
  • #3 18053656
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    Thanks :) So far it has started using Phison Format & Restore v3.24.0.0. He's acting a little weird. Uploading a folder with photos (780 files 713MB) average 2.5-2.7 MB / s, uploading a RAR archive ~ 700MB for the first time in a second 3/4 of the bar and stands showing zero transfer. the second time it flew nicely showing about 130MB / s and 99% hung for a long time. USB 3.0 pendrive inserted into USB 2.0 (Antivirus off) and ISO 4GB shows that it copies 150 MB / s but from 1/4 it starts to drop and at half it has about 10 MB / s ending falling all the time to 5 MB / s

    Ps. I remember earlier that when I managed to start it, after a few cycles it poured out again
  • #4 18053663
    kaleron

    HDD and data recovery specialist
    Posts: 7031
    Help: 957
    Rate: 2316
    Because you're out of memory, and even if you restart it, you're about to have another failure. It's not magic - it's physics.
    Company Account:
    Kaleron sp. z o. o.
    Hirszfelda 4/18, Jelcz-Laskowice, 55-231 | Tel.: 713XXXXXX (Show) | Company Website: https://kaleron.pl
  • #5 18053670
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    Can you say more about this? Interestingly, the flash drive is new (since the purchase, problems began after the third use), unfortunately, the option to return it under warranty is out due to the lack of proof of purchase. I'm more concerned with how to check, for example, memory?
  • Helpful post
    #6 18053706
    kaleron

    HDD and data recovery specialist
    Posts: 7031
    Help: 957
    Rate: 2316
    We go down with the size of the transistor, so the insulator of the floating gate is getting thinner and does not create such a potential barrier to effectively prevent the escape of electrons. We pack more and more bits into smaller and smaller transistors, so we have to distinguish more and more charge levels. As a consequence, the difference in the content of the floating gate at the level of 100 electrons translates into a bit error. Smaller transistors are also more densely packed - this translates into problems related to electrical induction. In addition, we produce multi-layer systems, which means that we have to struggle with heat dissipation from the center of the systems, and induction does not only apply to neighbors in 2D, but also in the top-down system. The systems overheat especially during write and erase operations that require voltages approx. 20 V. As a consequence, the service life of new circuits is much lower than that of old ones. At the moment, the entire information storage logic in NAND chips is based on much more extensive and advanced correction codes than it was 10 years ago. If you are also unlucky and come across a manufacturing defect, you buy a corpse that is unusable from new.
    Company Account:
    Kaleron sp. z o. o.
    Hirszfelda 4/18, Jelcz-Laskowice, 55-231 | Tel.: 713XXXXXX (Show) | Company Website: https://kaleron.pl
  • ADVERTISEMENT
  • #7 18053961
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    I understand, I'm not surprised by this fact. Now or to flash it? (more in the form of experience)
  • #8 18054029
    kaleron

    HDD and data recovery specialist
    Posts: 7031
    Help: 957
    Rate: 2316
    In the form of experience yes, in the form of repair - 0 trust, as in the carrier. If it succeeds, you can use it at most as a floppy disk to transfer data from computer A to computer B.
    Company Account:
    Kaleron sp. z o. o.
    Hirszfelda 4/18, Jelcz-Laskowice, 55-231 | Tel.: 713XXXXXX (Show) | Company Website: https://kaleron.pl
  • #9 18054098
    procsa
    Level 31  
    Posts: 1777
    Help: 173
    Rate: 363
    You have to go to these cool Russian sites and match the binary files to the memory chip, everything is described there, how you want to play :)
  • #10 18054174
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    It's just that as such, it would be useful to carry things between computers :) I'm wandering around the "Russian" world and I don't know how to handle these binary files....

    https://www.usbdev.ru/files/phison/ps2307fw/
  • ADVERTISEMENT
  • #11 18054491
    procsa
    Level 31  
    Posts: 1777
    Help: 173
    Rate: 363
    You need to read what memory you have exactly, like toshiba tlc, we already know the controller "PS2251-07", see the "Flash Drive Information" program and compare it with what ChipGenius showed you, and it's best to check what is written on the bone.

    Eat this.
  • #12 18054854
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    And both programs as if they did not show the type of memory?

    Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions
  • #13 18056663
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    I took it apart :) The controller, the memory and the sticker that was on the memory:

    Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions

    Ps. There was a small error on my part earlier. The flash drive is USB 2.0...

    I even found its specs for those interested

    Verbatim Store'n'go 32GB
    Producent code: 98697
    Connecting to a computer: USB 2.0
    Capacity: 32GB
    Read speed [MB/s]: 10
    Write speed [MB/s]: 4

    What a shit....
  • #14 18057604
    pidar
    Mass storage specialist
    Posts: 11335
    Help: 1568
    Rate: 3554
    There is a tool for this in the attachment NAND 3D TLC .
    Attachments:
    • ST-TOOL 9000 v3.7F.92 mod.zip (7.55 MB) You must be logged in to download this attachment.
  • #15 18058009
    procsa
    Level 31  
    Posts: 1777
    Help: 173
    Rate: 363
    flash ID : 983C98B37671 , both programs show the same thing, but looking at the forum, something like yours has already happened.... HERE and HERE
  • #16 18058208
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    pidar wrote:
    There is a tool for this in the attachment NAND 3D TLC .


    Unfortunately, there is no such thing in the package. Is only:

    MPParamEdit_F1_90
    STTOOL_F1_90_v200_00_SZ
    MPALL_F1_9000_v389_0C (in the ISP_INFO folder)
  • #17 18058209
    pidar
    Mass storage specialist
    Posts: 11335
    Help: 1568
    Rate: 3554
    Fidox1988 wrote:
    STTOOL_F1_90_v200_00_SZ

    It doesn't display anything :?: :D
    " TC58TFG8T22TA0D -Gen2.0x98.0x3C,0x98.0xB3.0x76.0x71"
  • #18 18058239
    Fidox1988
    Level 6  
    Posts: 16
    Rate: 32
    Please STTOOL_F1_90_v200_00_SZ
    Reflashing Unresponsive Verbatim STORE 'N' GO 32 GB Flash Drive: Suitable MPALL Versions
    :D

    (He reads minds... 8-O )

Topic summary

✨ The discussion revolves around troubleshooting a non-responsive Verbatim STORE 'N' GO 32 GB flash drive that cannot be formatted. Users suggest using "Phison Format & Restore v3.21.0.0" or "Phison MPALL v5.03.0A-DL07" for reflashing, emphasizing the importance of matching binary files to the memory chip. The flash drive exhibits erratic performance during file transfers, raising concerns about its reliability. Users discuss the technical aspects of NAND memory, including the effects of smaller transistors on performance and lifespan. The need for specific tools and programs to identify memory types and manage firmware is highlighted, with references to various software and resources for further assistance.
Generated by the language model.

FAQ

TL;DR: NAND wear is the culprit: erase/write uses ~20 V and "the service life of new circuits is much lower." You can reflash a failing Verbatim 32 GB, but treat it as disposable after recovery. [Elektroda, kaleron, post #18053706]

Why it matters: This FAQ helps Verbatim Store 'n' Go 32 GB owners revive an unresponsive PS2251‑07 stick using Phison tools, while setting realistic reliability expectations.

Quick Facts

What MPALL version should I use for a PS2251‑07 Verbatim Store 'n' Go 32 GB?

Start with Phison Format & Restore v3.21.0.0. If that fails, use Phison MPALL v5.03.0A‑DL07. Match the correct BIN set to the NAND before flashing. This order minimizes risk and mirrors successful recoveries for PS2251‑07. [Elektroda, procsa, post #18053546]

Why are my write speeds erratic after Format & Restore?

NAND physics limit reliability as cells shrink and store more levels. Program and erase need about 20 V, which heats and stresses cells. Threshold drift increases ECC demands and causes stalls under load. As the expert noted, "the service life of new circuits is much lower." Expect instability on worn or weak dies. [Elektroda, kaleron, post #18053706]

Is reflashing a permanent repair?

Treat reflashing as diagnostics or practice, not a lasting fix. After any success, use the stick only for temporary transfers. The advice is "0 trust"; at best, use it like a floppy between PCs. Keep important data elsewhere. [Elektroda, kaleron, post #18054029]

How do I identify the controller and memory to pick the right BIN?

Use Flash Drive Information and ChipGenius to read controller and IDs. Confirm by opening the stick and reading the NAND package marking. In this case, the controller is PS2251‑07. Physical inspection is best when software omits the die type. Record these before selecting firmware. [Elektroda, procsa, post #18054491]

ChipGenius doesn’t show the memory type. What else can I use?

Run STTOOL_F1_90_v200_00_SZ to query the NAND string. It returns identifiers such as TC58TFG8T22TA0D. Use that exact part number to locate compatible BINs and settings. Keep a screenshot to avoid misconfiguration later. [Elektroda, pidar, post #18058209]

What’s the Flash ID on this unit, and why does it matter?

This stick reports Flash ID 983C98B37671. That hex signature helps you find compatible Phison BINs and working cases. Matching by ID reduces trial‑and‑error in MPALL configuration. Note it before you begin reflash work. [Elektroda, procsa, post #18058009]

How risky is using the wrong BIN in MPALL?

Risk is high. You must match the BINs to the exact NAND. A mismatched set can make the drive unusable. As warned, "match the binary files well, otherwise you will fail completely." Double‑check IDs before flashing. [Elektroda, procsa, post #18053546]

Where do I find compatible BINs and guides?

Use the well‑known Russian communities archiving Phison resources. Search by controller (PS2251‑07) and your Flash ID. Threads document which BINs worked with specific NAND parts. Read the walkthroughs before running MPALL. [Elektroda, procsa, post #18054098]

What speeds should I expect from this USB 2.0 model after recovery?

Target the stock spec: about 10 MB/s read and 4 MB/s write. Sustained large‑file copies should align with those figures. Significantly lower rates point to wear or configuration issues. Validate with a single large file test. [Elektroda, Fidox1988, post #18056663]

Windows shows 150 MB/s then drops to 5–10 MB/s. Is that normal?

Yes for this failing stick. Windows first reports buffered bursts, then settles to sustained throughput. Users saw fast starts, hangs at 99%, and mid‑copy stalls. That behavior matches NAND issues on USB 2.0 media. Re‑test with varied files to confirm. [Elektroda, Fidox1988, post #18053656]

Format & Restore works, but the drive fails again after a few cycles. Why?

That suggests defective or exhausted NAND, not a simple file‑system issue. Temporary success followed by failure indicates marginal cells. As succinctly put, "It's not magic - it's physics." Replace the drive for reliable storage. [Elektroda, kaleron, post #18053663]

Is this Verbatim stick USB 3.0 or 2.0?

It is USB 2.0. The owner corrected the initial assumption after checking the hardware. Set expectations and tests to USB 2.0 limits. [Elektroda, Fidox1988, post #18056663]

Which exact utilities were in the referenced package?

The package included MPParamEdit_F1_90, STTOOL_F1_90_v200_00_SZ, and MPALL_F1_9000_v389_0C (under ISP_INFO). Use STTOOL to read the NAND string, then configure MPALL. Keep tool versions consistent during trials. [Elektroda, Fidox1988, post #18058208]

Can Phison Format & Restore alone bring the stick back?

Yes, it restored basic function with v3.24.0.0 in one report. However, write behavior remained unstable afterward. If instability persists, proceed to MPALL with matched BINs. Test only with non‑critical data. [Elektroda, Fidox1988, post #18053656]

How do I reflash this PS2251‑07 safely (quick steps)?

  1. Run Phison Format & Restore v3.21.0.0; if it fails, continue.
  2. Collect controller and NAND details, then find matching BINs for your chip.
  3. Use Phison MPALL v5.03.0A‑DL07 with the matched BINs to reflash. [Elektroda, procsa, post #18053546]
Generated by the language model.
ADVERTISEMENT