AU6986 VID = 0000 PID = 7777 Repair Fake Flash Drive Solution
Posted by inspectortech on December 12, 2008
FixFakeFlash – solution AU6986 controller identified with VID = 0000 PID = 7777, fake flash drive.
Read About VID PID Repairing Counterfeit Flash Drives – Steps To Succeed before proceeding to solution.
It turns out that the USB drives we bought didn’t even have matching internal hardware – the second USB had the same shell and real & advertised capacity, however the controller came out as being an Alcor AU6986 (using Microsoft’s ‘USBVIEW’ application, I found “idVendor:0×0000” ,“idProduct:0×7777”), and so searching flashb0ot.ru for ‘7777’ led to devices with the same Vendor id ‘0000’ all being from Alcor micro and a link to the application AlcorMP6.18_beta3 AlcorMP6.18_beta3).
Using the application after downloading was simple – open the application while the USB drive is inserted (again – this application has support for up to 16 USB devices at once – maybe the seller had 32 USB drives being frankenflashed between iCreate and Alcor Micro at the one time – efficient, hey?) – and locate the flash drive on the list (usually it’s the first one).
From there, the program supplies heaps of assistance by telling you the REAL capacity of the drive (mine showed up as 4092MB straight away) – all you have to do is left-click the little button where the number should be and select “Auto”.
It takes while, telling you at each stage what’s happening. While I was watching it, a firmware flash of the drive and a low level format went through, but the program came up with some error at the end of the low level format which I ignored – the drive showed up as 4GB in windows after that.
H2testw run before Fix:
The media is likely to be defective.
3.8 GByte OK (8028089 sectors)
3.9 GByte DATA LOST (8280135 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
3.9 GByte corrupted (8280135 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000f4ff7200
H2testw version 1.3
Writing speed: 4.00 MByte/s
Reading speed: 11.3 MByte/s
Look Familiar? =D
Warning: Only 3959 of 3960 MByte tested.
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 3.77 MByte/s
Reading speed: 17.7 MByte/s
SWEET! The drive works – and runs way faster!
Solution Provider: Phoenix 20081113
Reported In at: firstname.lastname@example.org