Hi fellow xda-members,
I recently wiped my One XL 32GB with the HBOOT Factory Reset,
didnt know that it wipes the internal storage aswell...
Needless to say that I work with the phone and the data is priceless...
I already tried to pipe the whole mmcblk0 via netcat, which worked fine.
All but the FAT 25GB partition are getting recognised via testdisk.
Did 2 dd's, so I got 2 raw-images of mmcblk0 and mmcblk0p36.
None of the recovery tools (Recuva, testdisk, @active, pc inspector recovery, etc.) did find any files.
The Partition wasnt formatted and also wasnt mounted yet, there should be no changes made from android since the wipe.
If I open the mmcblk0p36 via hex editor, its complete null.
The mmcblk0 image has random data all over the whole area,
but also mostly null (estimated 80-90% null). The internal memory was almost full,
about 22/25GB, so there are 3 options:
1.:The HBOOT Factory Reset doesnt delete just the FAT, but also nulls the whole data. (Which would be weird, because the reset took 3-5 seconds, I doubt it can null 25gigs in 5 seconds ;D)
2.:The chip has a kind of "fast-wipe" option, which makes it possible to null 25gb in 5 seconds, never seen this before, but who knows
3.:The data wasnt nulled, but dd doesnt read 1:1, which would be also weird.
Is there any app/commandline tool for android to directly check
whats on the specific part of the internal storage?
Or are there ways to access the memory directly to get
a exact image of the internal storage for recovery other than "dd if=/dev/block/mmcblk0"?
If none of the above, is there a chip-recovery expert that can recover the files with jtag/advanced hardware?
Thanks for all replys
criestr
I recently wiped my One XL 32GB with the HBOOT Factory Reset,
didnt know that it wipes the internal storage aswell...
Needless to say that I work with the phone and the data is priceless...
I already tried to pipe the whole mmcblk0 via netcat, which worked fine.
All but the FAT 25GB partition are getting recognised via testdisk.
Did 2 dd's, so I got 2 raw-images of mmcblk0 and mmcblk0p36.
None of the recovery tools (Recuva, testdisk, @active, pc inspector recovery, etc.) did find any files.
The Partition wasnt formatted and also wasnt mounted yet, there should be no changes made from android since the wipe.
If I open the mmcblk0p36 via hex editor, its complete null.
The mmcblk0 image has random data all over the whole area,
but also mostly null (estimated 80-90% null). The internal memory was almost full,
about 22/25GB, so there are 3 options:
1.:The HBOOT Factory Reset doesnt delete just the FAT, but also nulls the whole data. (Which would be weird, because the reset took 3-5 seconds, I doubt it can null 25gigs in 5 seconds ;D)
2.:The chip has a kind of "fast-wipe" option, which makes it possible to null 25gb in 5 seconds, never seen this before, but who knows
3.:The data wasnt nulled, but dd doesnt read 1:1, which would be also weird.
Is there any app/commandline tool for android to directly check
whats on the specific part of the internal storage?
Or are there ways to access the memory directly to get
a exact image of the internal storage for recovery other than "dd if=/dev/block/mmcblk0"?
If none of the above, is there a chip-recovery expert that can recover the files with jtag/advanced hardware?
Thanks for all replys
criestr
Aucun commentaire:
Enregistrer un commentaire