Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamJE CHERCHE UN MPTOOL POUR UN DISK DUR SSD DE MODEL YESTOR
I will answer in English for technical precision.
You should not search for a generic “YESTOR MPTool” only by SSD brand name. For Yeestor/YeeStor-based SSDs, the correct tool is chosen by the controller model and often also by the NAND flash type. Publicly listed Yeestor SSD tools I could verify are for YS9082HC, YS9082HP, YS9083XT, and YS9085N; I could not verify a public YS9086 MPTool listing in the main USBDev Yeestor repository. (usbdev.ru)
If your SSD shows YS9086BB-1 in BIOS or Device Manager, community repair reports suggest that this often means the drive has fallen into a ROM/service mode, and in several cases the actual recovery family used was YS9082HP, not a separate public YS9086 tool. That is a community-based inference, not an official Yeestor statement. (clubedohardware.com.br)
An MPTool is a mass-production/service firmware tool used to reinitialize or recover SSDs based on a specific controller family. USBDev’s Yeestor pages list these as production/service flashers for particular controller models, not as universal tools for all Yeestor SSDs. (usbdev.ru)
With Yeestor controllers, the retail SSD label is often much less important than:
YS9086BB-1 most likely meansI found multiple community cases where a failing SATA SSD was detected as YS9086BB-1, while recovery work was performed with YS9082HP tools and firmware families such as HPS2818B. One USBDev comment explicitly reports a controller marked YS9082HP being detected by Windows as YS9086BB-1 SCSI Disk Device. This strongly suggests that YS9086BB-1 is often a ROM-mode identity string rather than the true commercial model name. Again, that conclusion is based on field reports, not official vendor documentation. (clubedohardware.com.br)
Community repair logs show that using the wrong Yeestor package or the wrong flash profile can produce errors such as:
In practical engineering terms, this happens because the MPTool package carries assumptions about:
The most useful Yeestor-specific identification utility I found is sg_flash_id. USBDev describes it as a flash-ID reader for Yeestor/SiliconGo YS908x SSD controllers. It is intended to identify the flash-memory configuration, requires administrator rights, and works best with the SSD connected to a SATA controller; some USB-SATA bridges are also supported. Importantly, USBDev states that sg_flash_id does not work when the SSD is already in ROM MODE`. (usbdev.ru)
That last point matters: if your drive already appears only as YS9086BB-1, normal flash-ID detection may fail, and you may need to identify the controller directly from the PCB markings instead. (usbdev.ru)
As of the public listings I checked, the main Yeestor/SiliconGo SSD-repair ecosystem visible on USBDev includes:
sg_flash_id)The most recent relevant public additions I verified include:
A practical trend is that Yeestor recovery knowledge is still largely community-driven, with a lot of troubleshooting happening in repair forums rather than through polished manufacturer support channels. (clubedohardware.com.br)
If by “YESTOR model” you mean the SSD currently identifies as YS9086BB-1, the most likely public tool family to investigate first is YS9082HP, not a generic “YESTOR9086 tool.” Community cases repeatedly connect YS9086BB-1 with YS9082HP recovery workflows. (clubedohardware.com.br)
Examples of verified public YS9082HP packages include:
YS9082HP_MPToolV8.00.00.00.012_FW210520_release_B37&B47.rarYS9082HP_MPToolV8.00.00.01.014_HPS2704A_ALL_FLASH.rarYS9082HP_MPToolV8.00.00.01.025_HPS2704M_release_N38B.rarYS9082HP_MPToolV8.00.00.01.033_HPS2818B_ALL_FLASH.rarN48R-9082HP.rarDo not confuse MPTool with ViUpDateTool. USBDev describes ViUpDateTool as a utility for modifying:
There is an important ethical issue here: tools such as ViUpDateTool can modify identification fields and clear SMART-related state. In engineering practice, using such functions for legitimate lab recovery is one thing; using them to make a worn SSD appear healthier for resale would be deceptive. That concern follows directly from the tool capabilities described on USBDev. (usbdev.ru)
From a safety and data-handling standpoint, you should treat any MPTool operation as potentially destructive to the existing logical structure of the SSD. Community recovery workflows commonly end with reinitializing the disk and creating a new volume after flashing, which is consistent with a recovery/reprovisioning process rather than data-preserving repair. (usbdev.ru)
sg_flash_id with admin rights and direct SATA if possible. (usbdev.ru)YS9086BB-1sg_flash_id may not work according to USBDev.I could verify a public Yeestor tool ecosystem, but I could not verify an official public YS9086 MPTool listing in the main USBDev Yeestor repository. Therefore, any claim that there is a standard downloadable “YS9086 MPTool” should be treated cautiously unless it comes with a confirmed controller/NAND match. (usbdev.ru)
Also, many successful recoveries described online are based on community experimentation, not factory service manuals. That means results vary widely, especially when NAND is partially degraded. (clubedohardware.com.br)
To identify your exact tool, send:
sg_flash_id output. (usbdev.ru)If you want, I can then help you determine whether your SSD is most likely:
The short engineering answer is: there is no single generic MPTool for “YESTOR SSD.” The public evidence points to choosing the tool by controller + NAND, and if your SSD shows YS9086BB-1, the best-supported public lead is often the YS9082HP MPTool family, not a separate public YS9086 package. I could verify public Yeestor tool listings for YS9082HC, YS9082HP, YS9083XT, and YS9085N, plus sg_flash_id and ViUpDateTool, but not a public YS9086 entry in the main repository. (usbdev.ru)
If you send me a photo of the SSD board or the exact text shown on the controller chip, I can help you pinpoint the most likely MPTool package.