41 replies to this topic

[DavidB]

Hi.

For some time my USB HDD WD 500 GB died.
I bought a Kingston DataTraveler Ultimate G3 64GB USB 3.0 flashdrive/stick.

Chip Genius:

 

I need help flipping the removable bit, so I can use more than one visible partition in Windows (any version, any computer).

Before posting I searched and found this old topic: http://reboot.pro/to...ipping-the-bit/
I read it but it didn't helped me much.
Following this http://www.rmprepusb...usb-flash-drive I found this:

 

Unfortunately, as you can see, no utils available.

Any ideas..?

Thank you.

Regards,
David

[steve6375]

Did you try the link I gave in the RMPrepUSB article and click on the Phison tab?

http://usb-fix.blogs...k/p/phison.html

 

Maybe one of these will work with your Phison PS2251 controller?

WARNING: Use the wrong one and you will brick your Flash drive!

[DavidB]

Thank you, Steve.

 

Unfortunately all the links are showing a 404 error in russian language when I click on them...

[steve6375]

oh yeah....!

Try http://flashboot.ru/files/phison/

There are two that mention PS2251-03

[Wonko the Sane]

Also (just in case):

http://www.usbdev.ru/

http://www.usbdev.ru/files/phison/

 

Wonko

[DavidB]

Than you too, Wonko.

 

I have tried some of these tools, for example FixedDisk and MPAll but either say "failed" or doesn't appear to do something.

[Wonko the Sane]

I have tried some of these tools, for example FixedDisk and MPAll but either say "failed" or doesn't appear to do something.

Sure the steps are:

1. identify correctly the controller (tricky, but can be done )
2. find the "right" utility for it (finding an utility is easy, finding the "right" one is VERY tricky )
3. understand how (the heck) the found "right" utility works (tricky AND risky , but usually it can be done)

 

ChipGenius in some cases may mis-recognize a controller, you should double and triple check with other tools, namely Flash Drive Information Extractor and ChipEasy:

http://www.usbdev.ru/  <- content of pages is not that bad in Google Translate, take some time reading the "start" page

http://www.usbdev.ru/files/

http://www.usbdev.ru/?wpfb_dl=3966 <- Latest ChipEasy

http://www.usbdev.ru/?wpfb_dl=2566 <- Flash Drive Information Extractor

 

Consider how releases of this kind of tools are often partial and sometimes you can find some useful info on a previous version, unfortunately you will probably have to test more than a few of these tools before finding one that (hopefully) detects and work on that stick.

 

Namely the:

http://www.usbdev.ru/files/phison/

Phison Fixed Disk - a tiny utility to change the type of the device between a removable (USB-FDD) and fixed (USB-HDD). Operates in the following modes: mode3,7,21. I think the controller supports a wide range, and tested with PS2251-01 PS2251-03.
Phison Fixed Disk v1.0.0.3; FixedDisk_v1003.rar ; Size: 103,783 bytes
Interface: English (english)

 

 

is reported as having been tested on a PS2251-03, so it is well possible that the chip has been not detected properly by ChipGenius.

 

Wonko

[steve6375]

Maybe worth trying on XP 32-bit system?

[Wonko the Sane]

Maybe worth trying on XP 32-bit system?

Yes  usually any of these tools are intended to be used EXCLUSIVELY on XP and on 32 bit, good reminder.

 

Wonko

[DavidB]

I was/am working only on Windows XP SP3 x86.

 

 

ChipEasy 1.6 Beta 3 from that link says my language isn't simplified Chinese and wants me to download the 1.5.6 english version.

1.5.6 shows:
 

Logical drive : E:\ Capacity: 58.6G
Device ID : VID = 0951 PID = 1697
Device SN : 0018F30C9F63BEA1E127D27C
Device version : PMAP

Device vendor : Kingston
Device model : DT Ultimate G3
Protocol : USB2.0
Max power : 300mA

Partition type : FAT32 Device active : OK
Aligned state : 4032 KB, Have been Aligned

Controller : Phison
Controller model: PS2251-03
Flash Vendor : Toshiba, Type: MLC, Process: 19nm, Page: 16K
Flash ID : 98DE9493
Score : 70 (Normal Score >= 30)
Firmware : 01.11.10 FW Date: 2014.03.11

Tools : http://www.upan.cc/tools/mass/Phison/
OS Version : Microsoft Windows XP Professional Service Pack 3
Update Status : The current version is the latest version!

usbflashinfo shows:
 

Volume: E:
Controller: Phison 2303 (2251-03)
Possible Memory Chip(s):
Toshiba TH58TEG8DDJBASC
Toshiba TH58TEG8DDJBA8C
Toshiba TH58TEG8CDJBA8C
Memory Type: MLC
Flash ID: 98DE9493 7650
Chip F/W: 01.11.10
Firmware Date: 2014-03-11
ID_BLK Ver.: 1.2.76.0
MP Ver.: MPALL v3.30.00
VID: 0951
PID: 1697
Manufacturer: Kingston
Product: DT Ultimate G3
Query Vendor ID: Kingston
Query Product ID: DT Ultimate G3
Query Product Revision: PMAP
Physical Disk Capacity: 62948114432 Bytes
Windows Disk Capacity: 62914592768 Bytes
Internal Tags: 2Q6N-U74A
File System: FAT32
Relative Offset: 4032 KB
USB Version: 3.00 in 2.00 port
Declared Power: 300 mA
ContMeas ID: 6732-01-00
Microsoft Windows XP SP3
------------------------------------
http://www.antspec.com/usbflashinfo/
Program Version: 8.0.0.550

Phison Fixed Disk shows:

 

 

I click on Get Status:



I click on the first Fixed Disk. After 10 sec it shows:



I click on the second Fixed Disk. After 10 sec it shows:



I click again on Get status:

[steve6375]

Real XP system or VM?

If Real then don't know what else to suggest except look for more utils?

P.S. As some install XP drivers, it is a good idea to reboot/restore each time you test a new one.

[DavidB]

It's real system 100%.
Actually I use it almost all the time. I also have Windows 7 x64 and Linux installed but I use them rarely.

I tried restarting Windows, no change.
Oh, I also tried moving the USB drive into another port. Still no change.

[Wonko the Sane]

...
usbflashinfo shows:

Volume: E:
Controller: Phison 2303 (2251-03)
....
Chip F/W: 01.11.10
Firmware Date: 2014-03-11
....
MP Ver.: MPALL v3.30.00
...

Stupid board , it ATE my post.

It is possible that the device (since the tool sees two LUN's is in mode 7 and not in the "normal" mode 3 or that the fixed disk tool is too old for the newish firmware.

The mentioned 3.30.00 version of the MPALL tool is not on the given page.
If I were you I would try latest version MPALL v3.72.0B and work my way "backwards".


Wonko

[DavidB]

The problem is it doesn't seem to exist any (good) documentation about the parameters from Phison MPALL.

 

So far I tried this (it didn't "kill" my flash drive but I still don't see any difference, good or bad):

 

 

I had to reinsert the flash drive because it was unaccessible after using the tool. But no change...

 

Any idea what I should change there...?

[Wonko the Sane]

I did say how finding out how  a tool works (or fails to) is tricky, didn't I?

 

Be aware that one of the setting pages of that tool may attempt to flash also a (possibly "wrong") firmware.

 

The first thing you should run is the GETINFO tool and make a screenshot or however jolt down what it finds.

Then you should check the MP.INI (or more generally all the .INI that you can find and see what settings are in them.

Then you should experiment with settings, saving them into new .ini's to get the hang of them (sometimes the contents of the.ini file are "more clear" than the actual GUI text).

 

At first sight the file version Phison MPALL v3.71.0A_03 MLC(UP03 64pin):

http://www.usbdev.ru/?wpfb_dl=4388

seems like "more suitable", but cannot say.

 

 

Try - before a new attempt - if by any chance this other tool works Phison ModeConverter:

http://www.usbdev.ru/?wpfb_dl=4085

 

 

Check also the "UP tool" http://www.usbdev.ru/?wpfb_dl=4627 it seems like more "simplified/automatic", but of course you never know for sure.

 

You could also check if - by any chance - your specific model is compatible with these tools here (at least to identify/save current firmware):

https://github.com/a...l/Psychson/wiki

 

Wonko

[DavidB]

I understand.

I tried some tools, including those 3 you mentioned. All show "write failed". As usual, I see no change (good or bad) in how the flash drive works.

[Wonko the Sane]

Check this:
http://flashboot.ru/files/file/398/

after reading this:
http://jeffgraves.me...sb-flash-drive/

Maybe the issue is with the need for a "F1" AND a "F2" tool (whatever F1 and F2 actually mean)


Wonko

[DavidB]

Thank you very much, it helped me a lot

But, sorry to say, there is still a problem: on that site it shows the F1 window with the found UFD in white color and some text.



On my computer in both F1 and F2 it shows in red color with a different text.



I click on Start, the LED blinks a couple of times. I reinsert the UFD, no change.

 

 

LE: looks like I'm not the only one getting this error with these tools. Check the comments on this page: http://www.flashdriv...very-tools.html

Attached Thumbnails

• 
• 
• 

Attached Files

•  MP.ini.gz   354bytes   894 downloads
•  QC.ini.gz   337bytes   847 downloads

[Wonko the Sane]

Yep, definitely you have "issue 2" (again, whatever it is) .
As always happens when talking of these tools, wild guess  but maybe (first screenshot) the actual version MPAll v3.30.00 is actually *needed*.


Wonko

[DavidB]

Well, since I have no choice I will wait until they will release a better tool

I intended to create 3 partitions: a bootable 10 GB Fat32 with GRUB4DOS and Iso's, a 10 GB ext4 partition for a Linux OS and the rest of the drive as a NTFS partition.
For now I created a bootable 50 GB NTFS partition + a 10 GB ext4.
Ya, I know about the problems when using a NTFS partition, especially one that large, but for now I have no choice.

Right now I'm testing the latest GRUB4DOS version (0.4.6a-2014-01-17) to see how the USB 2.0 driver works.
But there is a problem: the geometry of the drive is not detected well after using "usb --init".  The second partition can't be accessed anymore.
Before using the "usb --init" command I can change "root (hd0,1)" + ls + boot the Linux OS.
After using it any attempt to access (with "geometry" command also) it shows "Error 25: disk read error".
Which is weird because, as I understand, loading the USB driver should fix the geometry errors. Instead, it breaks it.

Should I use "geometry --tune" and/or "geometry --sync"...?

[Wonko the Sane]

Right now I'm testing the latest GRUB4DOS version (0.4.6a-2014-01-17) to see how the USB 2.0 driver works.
But there is a problem: the geometry of the drive is not detected well after using "usb --init".  The second partition can't be accessed anymore.
Before using the "usb --init" command I can change "root (hd0,1)" + ls + boot the Linux OS.
After using it any attempt to access (with "geometry" command also) it shows "Error 25: disk read error".
Which is weird because, as I understand, loading the USB driver should fix the geometry errors. Instead, it breaks it.

Should I use "geometry --tune" and/or "geometry --sync"...?

Well, there is not much sense in using the USB driver of Grub4dos on a machine that already has a working USB 2.0 driver in BIOS, as a matter of fact it is likely that the two will interfere AFAICU.

 

I mean, does it work WITHOUT loading the grub4dos USB driver?

 

If it does, leave it alone.

 

Wonko

[steve6375]

Well, there is not much sense in using the USB driver of Grub4dos on a machine that already has a working USB 2.0 driver in BIOS, as a matter of fact it is likely that the two will interfere AFAICU.

 

Actually there is a big advantage. Many BIOSes have buggy USB driver code

1. 137GB bug - sectors past 137GB cannot be accessed

2. very slow - simple  ls /file loop x100   - slow BIOS = over 1 minute,  but 04.6a driver - less than 2 seconds!

 

I would love to use 0.4.6a for E2B, but I have found that

 

1. bugs in recognising  map'ed ISOs  (esp. Joliet ISO9660:1998 format  level 4)

2. bugs in listing files in a map'd ISO (ls sometimes produces garbage)

3. Range of h/w support for usb controllers is not as wide as Plop! driver

4. Problems if more than one USB drive is connected when --init is run

 

I have reported bugs on old site (https://code.google....all/issues/list) and new site (https://github.com/chenall/grub4dos/issues)

 

@DaveB - if you find any issues, please report them on the new site.

 

Use latest version at http://grub4dos.chen...ries/downloads/

[DavidB]

Well, there is not much sense in using the USB driver of Grub4dos on a machine that already has a working USB 2.0 driver in BIOS, as a matter of fact it is likely that the two will interfere AFAICU.

 

I mean, does it work WITHOUT loading the grub4dos USB driver?

 

If it does, leave it alone.

 

Wonko

 

No, it doesn't.

It works in 1.1x.

 

 

 

Actually there is a big advantage. Many BIOSes have buggy USB driver code

1. 137GB bug - sectors past 137GB cannot be accessed

2. very slow - simple  ls /file loop x100   - slow BIOS = over 1 minute,  but 04.6a driver - less than 2 seconds!

 

I would love to use 0.4.6a for E2B, but I have found that

 

1. bugs in recognising  map'ed ISOs  (esp. Joliet ISO9660:1998 format  level 4)

2. bugs in listing files in a map'd ISO (ls sometimes produces garbage)

3. Range of h/w support for usb controllers is not as wide as Plop! driver

4. Problems if more than one USB drive is connected when --init is run

 

I have reported bugs on old site (https://code.google....all/issues/list) and new site (https://github.com/chenall/grub4dos/issues)

 

@DaveB - if you find any issues, please report them on the new site.

 

Use latest version at http://grub4dos.chen...ries/downloads/

 

Thank you for the link, I will test with the latest release.

[Wonko the Sane]

@Steve

I will try retyping it slowly:

Well, there is not much sense in using the USB driver of Grub4dos on a machine that already has a working USB 2.0 driver in BIOS, as a matter of fact it is likely that the two will interfere AFAICU.

 

I mean, does it work WITHOUT loading the grub4dos USB driver?

 

If it does, leave it alone.

 

It seems to me that "a working USB 2.0 driver" means a driver "working" and "working at USB 2.0 speed".

 

In my perverted mind, if the BIOS USB 2.0 driver is working at 1.1 speed, then it is not working, but the number of such motherboards (having USB 2.0 capable chips BUT having a BIOS USB 1.1 speed driver are not that much common anymore).

 

@DavidB

If you have issues with grub4dos internal driver, do try (as Steve mentioned ) PLoP, it is relatively easily chaiinloadable from grub4dos and while somewhat "reducing the range of possibel booting methods" should work fine in your setup.

Also check the specs of your motherboard, it is well possible that different USB ports are connected to a different controller chip/southbridge/whatever, and behave differently).

 

Wonko 

[DavidB]

I tested with 0.4.6a-2014-11-19 version and the problem is gone
In fact with this driver all menu.lst entries seem to work fine.
With Plop more than half of them don't work.

And, yes, I have tested and all the USB ports behave the same way.