Smi Mass Production Tool Setting Password
Production Tool Novi
Fix corrupted SMI USB flash drives.Download SMI Mass Production Tool and format SMI with SM2355EN chip controller.Learn how to repair SM3255EN chip controller. SMI MPTool V2.03 for SM3255EN Recovery - Flash Drive Repair.
Anyone familiar with repairing corrupt USB drives using their respective mass production tools? This could get very technical. Crosspost from r/AskReddit
I'd rather not go into details on why it has come to this. I know, I'm stupid, I shouldn't have meddled, I'm an asshole, etc... But the thing is, it's not trash. It's recognized by the tools and windows (except when trying to access it in windows, it says there's nothing there.) Therefore I refuse to throw it away when I know it can still be fixed. So on to the details.
I have a 2GB SMI (Silicon Motion) USB drive. The details of the hardware, due to corruption, are as follows:
NOTES: Some of the above information is incorrect. The below information (if my memory serves me correctly) is from before the corruption :
The changes made above are:
Device Name (80% sure)
PID (100% sure)
Serial Number (not sure, but it did start with 'AA04012')
Revision (100% sure)
Chip Part-Number (100% sure)
Product Vendor (99% sure)
Evidently, in between the time the USB became corrupt and my attempts at correcting it, things have changed inside the firmware.
I have 3 SMI Mass Production tools gathered from here. One for 090c/1000 and two for 090c/3000.
Other software I have that might be of use are:
RMPrepUSB
SMI UFD Utility
SourceUSB
EASEUS Partition Master
USB Flash Media Pack 2011
Smi Mass Production Tool V 2.03.23 V5
I've found some Russian and Chinese sites that seem to specialize in this stuff, but I don't speak either of those languages.
EDIT: If you need anymore information, let me know.
EDIT 2: Good News!! It took a long time, but evidently I found the right tool (Test_SM32x_J0323) on some Chinese website. It was indeed the firmware. I had to do a low-level firmware deletion (absolutely nothing on the USB. Not even identification info, except for maybe the first 8 bytes), then patch it using the 'default.ini' file that came with the software. These are some very complex tools that should not be used by people who don't know what the hell they're doing. I think I've just developed an interest in USB production/development. The next time a USB device 'fails' on me, I'm gonna look into doing the same thing.
EDIT 3: Scratch that... It seems I've borked it somehow. 'My Computer' doesn't recognize it, but Disk Management does. Only problem is, in Disk Management, it won't let me 'initialize' the drive. I have the firmware set correctly, but apparently I'm supposed to specify where exactly the first writable block/sector is on the drive... Another problem is, the software I used to correct the firmware problem won't even recognize it now. ChipGenius can recognize it, and it shows the right info. I'm lost....