MobileRead Forums - View Single Post - Onyx Boox Kon-Tiki 2 (Nova3 platform)

Renate · 08-04-2022, 01:51 PM

It could be encrypted without you even doing anything.
There's lots of things that I've never done a deep dive into, that's one.

I have done similar things with corrupted hard disks.
In the best of all possible worlds (thank you, Dr. Pangloss) the blocks are contiguous.
You can scan the raw blocks looking for file headers and try to assemble continugous blocks.

I've usually just made ad-hoc tools to search. The usual tools I use are designed for sane sized files. Searching 32 GB with less than 40 GB memory is not currently possible. I should make it possible though. Of course you could break your big file into smaller chunks.

Code:

E:\>findtext m.img dm-verity /x30 /y50
E:\m.img
01DA501B                     drivers/md/dm-verity-target.c
01DDB144                     drivers/md/dm-verity-fec.c
01E11A5A                                dm-verity enforcing
01EC577A                                dm-verity device corrupted

In any case, if you want to recover your stuff, you should either archive userdata or else scan it now, before you write more files that will overwrite the old ones.

08-04-2022, 01:51 PM	#146
Renate Onyx-maniac Posts: 4,002 Karma: 18026955 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	It could be encrypted without you even doing anything. There's lots of things that I've never done a deep dive into, that's one. I have done similar things with corrupted hard disks. In the best of all possible worlds (thank you, Dr. Pangloss) the blocks are contiguous. You can scan the raw blocks looking for file headers and try to assemble continugous blocks. I've usually just made ad-hoc tools to search. The usual tools I use are designed for sane sized files. Searching 32 GB with less than 40 GB memory is not currently possible. I should make it possible though. Of course you could break your big file into smaller chunks. Code: E:\>findtext m.img dm-verity /x30 /y50 E:\m.img 01DA501B drivers/md/dm-verity-target.c 01DDB144 drivers/md/dm-verity-fec.c 01E11A5A dm-verity enforcing 01EC577A dm-verity device corrupted In any case, if you want to recover your stuff, you should either archive userdata or else scan it now, before you write more files that will overwrite the old ones.