View Single Post
Old 04-22-2012, 03:46 PM   #5
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,069
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
knc1 is correct.

Some areas of /dev/mmcblk0 are WRITE-ONLY (to protect sensitive information) and you can only request information for these areas from a device driver (/proc interface). So even if you copy the entire mmc image from root (which includes the USB drive contents), there are parts of it that will show as all zero, and writing those back to the mmc can damage the data that is hidden in those locations.

You need kernel mode access to read the protected areas.

EDIT: Now that we have kexec that can run a custom linux kernel loaded from the USB drive, you could modify the linux kernel gpl source code (available from amazon) to give you direct access to the hidden mmc contents, potentially allowing you do make an exact image of the entire mmc device, as you suggested.


Last edited by geekmaster; 04-22-2012 at 03:54 PM.
geekmaster is offline   Reply With Quote