Verbatim Store n Go 1GB stopped working, installs wrong driver whenplugged in.

  • Thread starter Thread starter mcv
  • Start date Start date
M

mcv

Hi,
When I plugged the drive in "Verbatim Store n Go 1GB" after adding some
files to it from another computer, as I have done many times, XP went
and installed the drive as something else using different drivers!
Now I have uninstalled it, rebooted, inserted the drive again and same
result!
It now see's it as a "USBest USB2FlashStorage USB Device".
Whats going on??
How do I get it back to normal?
It shows up in my computer, but when I try to open it, it says "please
insert a disk in drive f:".
Drive shows up as zero size.
Thanks for reading, any info would be great!
 
mcv said:
Hi,
When I plugged the drive in "Verbatim Store n Go 1GB" after adding some
files to it from another computer, as I have done many times, XP went
and installed the drive as something else using different drivers!
Now I have uninstalled it, rebooted, inserted the drive again and same
result!
It now see's it as a "USBest USB2FlashStorage USB Device".
Whats going on??
How do I get it back to normal?
It shows up in my computer, but when I try to open it, it says "please
insert a disk in drive f:".
Drive shows up as zero size.
Thanks for reading, any info would be great!

A person here, managed to blast a flash device, by accidently overwriting
sector zero. That instantly turned it into USBest USB2FlashStorage.
Now, if it claims to be a CDROM and is read-only, I don't know
if it is going to be that easy to repair sector zero.

http://forum.hddguru.com/usb-flash-overwritten-first-512-bytes-with-t8400.html

Repair recipe here. No guarantees of course. I had loads of fun, trying to
use the Transcendusa.com and could not get any information on this
utility. In Google, I found one post in German, where someone used
the program to reformat their USB stick to full capacity. There is
otherwise, little mention of it.

http://www.cdfreaks.com/reviews/Traxdata-EZ-Drive-USB-2_0-Flash-Drive---Twister-512MB/Recovery.html

---> http://www.transcendusa.com/Support/DLCenter/Software/recovery_1002.exe

Is there valuable data on it ? Or can you afford to try potentially
destructive procedures on it ?

HTH,
Paul
 
Hi,
Thanks for the reply!
Nothin valuable I have the original data still.
Just gonna have a look at the pages you mentioned, see if I can fix it.
Thanks mate!
 
No joy.
Just wish a could find the receipt take it back.

But since a can't...
Is there a way to change the info shown by USBView.exe?
Like change the:
idVendor: 0x1307
idProduct: 0x0163

back to the original? or is there more to it?

So XP installs the proper driver, then I might be in with a chance?
 
mcv said:
No joy.
Just wish a could find the receipt take it back.

But since a can't...
Is there a way to change the info shown by USBView.exe?
Like change the:
idVendor: 0x1307
idProduct: 0x0163

back to the original? or is there more to it?

So XP installs the proper driver, then I might be in with a chance?

This is from the usb.ids file I have on disk.

1307 Dikom
0163 512MB USB Flash Drive

It would appear they've been bought out (the chip maker, that is).
This is the latest version of the usb.ids from
http://www.linux-usb.org/usb.ids

1307 Transcend Information, Inc.
0163 512MB USB Flash Drive <---
1169 TS2GJF210 JetFlash 210 2GB

Now, the first observation, is your Verbatim product is 1GB,
and the declaration here is 512MB. It is always possible the
controller chip, supports larger flash chips. (The designs tend
to be two chips - controller and flash.)

You'll also notice that Verbatim is not in the
USB list. While chips do have the option to have
their enumeration information changed (or for
additional info to be used to distinguish them),
it could be that the 1307 0163 is "normal" for
the product. I don't know of a way to prove that
though. With flash memory, I suppose if they were
really clever, all the enum could be stored on the
flash itself. I don't know anything about that
industry at all, in terms of design practices.

One thing that is strange, is if Verbatim offers
a limited lifetime warranty, then why would they
need a sales slip ? Are they worried about
counterfeits ? You'd think it would be a simple
matter of sending it to them, and them deciding
whether to fix it or not.

I looked for software on the Verbatim site, like
a recovery program, but don't see anything that
looks interesting.

Paul
 
Paul said:
This is from the usb.ids file I have on disk.

1307 Dikom
0163 512MB USB Flash Drive

It would appear they've been bought out (the chip maker, that is).
This is the latest version of the usb.ids from
http://www.linux-usb.org/usb.ids

1307 Transcend Information, Inc.
0163 512MB USB Flash Drive <---
1169 TS2GJF210 JetFlash 210 2GB

Now, the first observation, is your Verbatim product is 1GB,
and the declaration here is 512MB. It is always possible the
controller chip, supports larger flash chips. (The designs tend
to be two chips - controller and flash.)

You'll also notice that Verbatim is not in the
USB list. While chips do have the option to have
their enumeration information changed (or for
additional info to be used to distinguish them),
it could be that the 1307 0163 is "normal" for
the product. I don't know of a way to prove that
though. With flash memory, I suppose if they were
really clever, all the enum could be stored on the
flash itself. I don't know anything about that
industry at all, in terms of design practices.

One thing that is strange, is if Verbatim offers
a limited lifetime warranty, then why would they
need a sales slip ? Are they worried about
counterfeits ? You'd think it would be a simple
matter of sending it to them, and them deciding
whether to fix it or not.

I looked for software on the Verbatim site, like
a recovery program, but don't see anything that
looks interesting.

Paul

It gets more interesting. There is an actual USBest
and one of their USB flash controller product pages
mentions "customized vid/pid and serial number". So it
could be that there is an actual USBest chip inside
the stick, and its custom ID is changed ? What I cannot
determine, is what it might have been when the stick
was new. (The USB.ids file is an informal record
of enum information. There is one for PCI as well.
The official record is kept sealed, as that way,
companies can work on new products, without them
being announced to the world. It is only after
someone tries a real device and submits an entry
to those files, that the informal file gets updated.)

http://www.usbest.com.tw/EN/index.aspx

The USBest site is hard to navigate. I did find a
product page of sorts, but no datasheets.

I started investigating that website, after I found
some pictures of USB flash sticks and what chips
are used. One of the first pictures I saw, had a
USBest chip in it.

http://www.anandtech.com/printarticle.aspx?i=2549

The datasheet for a USBest chip is a writeoff. There
is nothing of value in here. How very clever of them.
This site archives datasheets, so at least one of
them got loose into the wild. There is no description
of startup, what info the controller gets from
the flash, or anything.

http://www.datasheet4u.com/download.php?id=612845

Paul
 
Hi mate,
Thanks for taking the time with this.
I'm still waiting on Verbatim getting back to me.
If a dont get it replaced i'll open it up and find what chip is actually
in it.
Having a look thru what you came up with.
Thanks
 
Ok, so I just searched Google for about 5 hours trying to figure out how to fix the USBest USB2flashStorage USB problem. What happened is the part of the memory that tells the computer how to access the drive and how big the drive is got corrupted. You need a program called "Super Stick Recovery Tool" made by kingmax. Don't worry that your drive isn't a kingmax drive, it will work anyway because it is just going to completely write over that little part of the drive that got corrupted. just go to "http://www.kingmax.com/en_04_download.asp?usn=2" and download
Super Stick Recovery Tool V1.0.2.19.rar
you can open the rar file with winrar or 7-zip. Inside is
Super Stick Recovery Tool V1.0.2.19.exe. Run it as administrator with the drive plugged in and click "Update"
about 5 minutes later-- Problem solved!

*Warning* This erases everything on the drive, I have no clue how to get data off of it before you do this, but at least you can have a working jump drive rather than a paper weight.

Just so you know, I only tested this on a Verbatim 8 Gb drive that had the exact same problems you described. I tried lots of other tools and they didn't work. Super Stick Recovery Tool Rocks!
 
Back
Top