Hello guys,

i have this USB Flash drive that shows up for like 5 second and then going off. I can see the files but cant save them.. so i looked at the PIN-layout and jumped a spot that wasnt connected.. But i have still the same problem.
I also tryed it with a 2.0 socked but still the same...

I wanted to work on it with the PC3K Flash but they dont have the layout for this case...

Does anyone know where i can buy it? Or does someone hase another solution for this case?

Thank you!

I don't know anyone selling layouts - even the AE sellers appear to have dried up. Have you asked Ace about a layout or just checked the database?

Can you prolong your access time by actively cooling the device ?

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

I had such drives that appeared even less than 5 seconds before dropping and managed to image them using USB Stabilizer.

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

would this YKUSH do the job?
https://multi-com.eu/,details,id_pr,226 ... e-hub.html

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

There's no active monitoring available for it.

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

Yes, possibly, HDDSuperClone supports it.

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

I can add YKUSH support for HDDSUPERCLONE in case it doesn't support it yet. Just let me know when you need it.

Hi,
i think it will be very interesting if it could support R-Studio or UFS Explorer.
Is it possible to support those tools in future?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Klennet supports call external commands or batch on error, you could then have YKUSH do power-cycle.
DMDE supports running custom scripts that can call external commands for error handling, you could then have YKUSH do power-cycle. It may work, I never tried.

I doubt R-Studio will support it since their cooperation with DeepSpar to integrate Stabilizer with R-Studio. UFS, perhaps, don't know, using YKUSH is pretty low tech solution. We simply can not compare YKUSH to DeepSpar's USB Stabilizer, the latter is of course much more than a -power-cycler.

What I did test a few times is medium bad flash drives with YKUSH + some tool that detects drive dropping and then tells YKUSH to power-cycle and then re-establishes handle to the drive VS. USB Stabilizer , Stabilizer always comes out on top, more speed, more stable, more convenient and less Windows interaction (Windows will re-detect the patient drive each time when it's power-cycled by the YKUSH which is incredibly annoying to say the least).

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

The controller of this UFD is SM3267, using Samsung nand flash. I have a pinout, but it is not provided for free

_________________
Auxiliary Tool Used For MonoLith Data Recovery, featuring the industry's most extensive Monolith pinouts
http://flash-matrix.com/

Arch Stanton, Hey, wich one did you use? Can you recomand something?

Lardman, i will give it a try, thx!

I do not understand the question, I told you what I use or not?

USB Stabilizer + some software with disk image function, DMDE, UFS. Then you need to examine how flash drive behaves:

- Get a feel for good reads and time that takes. Take result of that and add 10-20% and use as your read timeout threshold. Anything slower do power-cycle.
- Test a failed sector, so let it fail, do power-cycle and immediate(*) retry after that (**). In my experience the failed block of sectors can often be read after single retry.

(*) - This is important. If you save retries for a second pass, during 2nd pass you'll probably have same trouble reading that block again.
(**) - Retry entire failed block at once! So if you read block of 64 sectors and read fails, do repower, and set up your imager to retry 64 sectors rather than sector by sector retries. Using DMDE for example a way to accomplish this is by using Device I/O parameters and set BPS (bytes per sector) to 32768 and set I/O buffer to 1 sector.

You can do same using YKUSH but it is clumsier as your imager needs to do all handling of anomalies. Then after re-power or power-cycle the imager needs to become aware of fact device is back and create a new handle to it and continue imaging using the new file-handle. You can probably make DMDE work this was as you can run custom scripts to handle I/O errors (not tried yet). Klennet can be configured to run a batch file, you can make batch file to power-cycle using YKUSH after I/O error (not tried myself but I saw some one do it).

Advantage of Stabilizer is that it is handling all interaction with the drive. As an illustration, here I use YKUSH to do power-cycles, slow read or error triggers power-cycle followed by immediate retry. Yellow blocks are failed reads that were read successfully after power-cycle. IOW 'bad' sectors were not really bad sectors but failed due to controller doing stupid stuff.

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

Arch Stanton, Thank you very much for this detailt information! I tryed but didn work... guess i need the pinout.

Didn't work is too little to base some kind of advice or analysis on, bet yeah it not working is always an option ..

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

Arch Stanton, yes im sorry... i finaly will buy a layout to work with it on the Flash. Still thank you very much for your support!