Unknown USB Device (Device Descriptor Request Failed) No Drive Letter

Data recovery can be expensive.
If your prepare for drive failure then your set.

Speaking of which.... Which type are you thinking of?

1. Using any of the free ones, many of which I've already tried Recovered .txt Files Have Scrambled Code and Meta Data in Contents.

or

2. Do you speak of seekwritt abilities to rescue text files which Linux seems unable to properly convert into readable text?

Noninvasive said:

The small note within, is the same size as the English note which was supposed to be there.
Can anyone translate this note? https://mega.nz/file/Zo1mgRZQ#Gd781M...6GxdpmHnbcysOU

If you know of any data recovery service which can properly rescue these correctly sized and paragraphed text files (though their character-set is garbled and or brokenly-encoded; possibly due to DOS recovery incompatibilities (based on:

"Í!¸
LÍ!This program cannot be run in DOS mode.
$ ÝôÙ™|šŠ™|šŠ™|šŠ‡.Š˜|šŠ‡.Š˜|šŠRich™"

which was inserted by recovery software into some of the text files during Linux based recovery).

That looks like a joke, because we're talking about money. It's not a joke. Lazesoft Recovery suite really did that ... at least twice.

Does number 2 exist?
- If not -- why pay?

For free backup images the software typically fails with an error message on drives with significant problems.

You can try: Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.

Macrium Software | It's our Business to protect your data
Backup and Restore with Macrium Reflect

Also an overnight copy and paste can be attempted.


Seagate has a pay service where the end user ships the drive for file recovery.

Do you have a link for the copy and past? Searching engine gave the wrong reflection of the term as it refers to data recovery. That's what I'd like, for it to "read and copy exact contents of drive back into accessible file format. No attempting to 'reassemble' that which supposedly was perfectly assembled already but simply had its bit switch turned to "deleted and ready for writing' status".

If it's been deleted, then all it does it mark all the deleted files as "deleted" though they are still there. This status really is saying "write over this if you want to". Thus, the files should be there in perfect order if we could identify the switch that says "This area is ready for writing" and have it simply undo that status with an "overnight copy and paste" as you said. It's actually two UBSs not the D - overnight may be a bit much. If you know of something that does that, I would like a link. Like I said, searches for "copy past data recovery" were not relevant.

These USBs don't have "problems", I only moved one to the other and then mistakenly deleted the new copy thinking it was the 1st copy and had been accidentally "copied" instead of "cut/moved". Then I began a file transfer onto one of them, but canceled it quickly when I realized they' were both mistakenly blank. Almost all the data was recovered in perfect condition (photos, audiobooks, pdfs -- perfect) ---- thus we can assume the data remains. Only TXT files, RTFs, and DOCs were harmed in the making of this reproduction.

I've got a HD in which Sea Tools long generic displayed fail.
HD Sentinel displayed performance 100%, Health 9% = critical
1712 bad sectors
Estimated remaining lifetime 9 days.


HD Tune full error scan displayed 1 bad block which was the first block.

Crystal disk displayed: caution

This HD is still working.
Copy and paste to another drive could be attempted overnight if there were important files.
There are none.
A clean install was performed months ago.

Copy and paste are copies of the users folders.

Oh, I thought you meant some form of dat recovery which literally copies the drive bits over directly instead of trying to "reconstruct" things. I can copy past the D contents, not from the deleted USBs though those are recovery-copies (attempted reconstructions). If these things worked according to my simpleton assumptions, they would be easily duplicated from a simple "read and duplicate". Instead, they write them in fragments in the 1 st pla ce, and some how make it unclear how those fragments connect -- so only a predeleted file (read as: "network of fragments") can be read.

Unknown to me, is why those existing fragments can no longer be properly reconstructed as per normal read/writing procedures; unless they are img, audio, video, etc. -which suffer no problem on reconstruction. Why the simplest form, txt, is the one form the data wrecks can not read and reconstruct is a mysterry.

I simpleman-guess all the recovery softwares are failing in this area (as if they all copy pasted each others code leaving the txt-recovery fault within). I will continue to believe that... unless it becomes clear why txt is truly "more vulnerable to corruption-upon-deletion than any other format" (I have heard it said; I do not believe).