schleuss.online is one of the many independent Mastodon servers you can use to participate in the fediverse.
This instance has a focus on IT security, general computing, retro video games and game collector discussion. Please, no #NSFW and other 18+ discussion on this instance. See rules for more details

Server stats:

11
active users

#datarecovery

0 posts0 participants0 posts today

Another bad retro diskette! At first glance, this one seemed pretty much gone. None of my disk imaging tools were able to read it. Windows Explorer just crashed.

Only a low level KryoFlux dump managed to uncover the physical cause behind this: A corrupt root directory beyond any chance of repair. Luckily, both the file allocation tables as well as most of the data clusters were still in good shape. I used a hex editor to manually recover all the files from the valid tracks. It worked!

I guess these games are nothing special, but it still made me happy to pull usable data and working files from such a destroyed file system!

Okay, this is a long shot, but maybe someone can help.

I've got a Nokia phone with KaiOS on it (Firefox OS offshoot). It's utter garbage and I would like to switch to a new one.

The one problem is that there's a lot of WhatsApp chats on there that I would like to keep, mostly for sentimental purposes. And since this is a niche OS with a WhatsApp implementation developed specifically for that phone, which lacks all but the most basic features (no WhatsApp web, no calls, no file transfer, and crucially no backups), if I just took the SIM out and stuck it into my new phone, I'd lose all that.

Does anyone have experience with that sort of situation, or with KaiOS in general, and could give me some pointers about manually scraping that data off the phone? I don't have high hopes, but perhaps someone out there knows something.

How to recover data from a failed #sandisk Extreme SSD drive*. The data appears to remain on the drive though it is not available through the OS. Do not format or otherwise modify the disk prior to recovery.

First make sure you have empty storage greater than two times the size of the #sandisk drive.

Remember advertised drive size may not exactly translate across manufacturers. For example, a 1TB #sandisk SSD drive may not fit on a formatted 1TB hard drive.

1. Image the drive using DD or FTK Imager. If you use FTK Imager select DD as the output format. Set the image fragment to 0 to make a single output image file. After the image is made rename the output file to have a DD extension rather than 001.

When you load the drive into Windows it will appear empty due to the firmware bug. Ignore that, the imaging software will grab the drive contents directly.

2. Load the image file into PhotoRec data recovery tool and select free search to search the entire drive. Export the recovered files to the free drive.

The files will not remain in the same folder structure, but at least the files are recovered.

The recovery process will take hours to go through all the sectors on the entire disk image.

FTK Imager: exterro.com/ftk-imager

PhotoRec: cgsecurity.org/wiki/PhotoRec

*I tried this on a single 1TB drive formatted NTFS, that did not have firmware patch applied. Your experience may vary. #forensics #datarecovery #westerndigital #ftkimager #dd #photorec

Exterro logo
ExterroFTK® Imager - ExterroExterro’s Legal Governance, Risk and Compliance (GRC) solutions enable you to address your privacy, compliance, investigation and litigation risks more effectively and at lower costs.