cgsecurity.org

Unfortunately it is late now, I rewrote on pendive after formatting again.

Using type you can add another partition type like FAT32.
Yeah that's just what I did, i added a FAT32 partition and files and folders have been listed. However, I repeat, files in folders could not be recovered when I tried to enter any folder ("No file found, filesystem may be damaged ...

Thanks for your reply Fiona, but as I said I already got the list of my files and folders after selecting "None" at type partition. The problem is that i cannot recover file inside folders, because it shows " No file found, filesystem may be damaged. " So there were files that could be recovered ...

No partition is displayed, quick or deep search is unable to recognize any partition.
Disk: /dev/sdb - 15 GB / 14 GiB - Kingston DataTraveler 2.0

Analysis showed: "Partition sector doesn't have the end mark 0xAA55"

Well I just have the same problem with a Kingston flash drive 16GB. I followed Fiona's instructions and rebuilt the boot sector in FAT32. So I could list my files but just saw their name, because when I try to enter a folder it shows: No file found, filesystem may be damaged.
Why?
Note that the ...

You have to follow instructions. Did you read the guides I have linked?
Now you have to select the path of recovered files; to do so you have to mount another disk (for example external usb disk) or select another free partition of your damaged disk (if eny) where no previous important data is ...

It is written:
1. select a destination to recover files using arrows (you must choice another disk or partition)
2. press "C" to confirm destination
3. press "Q" to quit

Try TestDisk first:
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
http://www.cgsecurity.org/wiki/Undelete ... h_TestDisk (if your data is on NTFS filesystem)

If data is still missing launch PhotoRec:
http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step

If a space portion is overwritten by other data, it is very difficult to recover previous data (the more is overwritten, the more is difficult, unless impossible);
Anyway, did you try to make a first scan with testdisk and photorec?