Quote:
Originally Posted by aesop
Thank you.
Stupid me - forgot the of= part... 
I'd love to say this solved everything but it didn't.
Now, it looks like I've bricked it... 
This happened during flash
Code:
[root@kindle us]# dd if=mmcblk0p1.img of=/dev/mmcblk0p1 bs=4
EXT3-fs error (device mmcblk0p1): ext3_lookup: deleted inode referenced: 1713
Aborting journal on device mmcblk0p1.
Remounting filesystem read-only
- - - - -
If there is anything left that could be tried - I'm all ears...:|
Thanks. |
Just more PEBKAC
http://zstag.deviantart.com/art/PEBKAC-162278715
/dev/mmcblk0p1 is the physical (raw) backing store for the Kindle's "main" mode file system (Kindles are "dual system boot" devices).
You can't replace the root file system while it is in use (you where in the 'main' mode system above).
So boot into the Kindle's "diag" mode (which uses /dev/mmcblk0p2 as the root file system) when you want to replace the "main" mode file system.
Note 1: bs=4096 not 4
You will wear out your flash chip doing 1,000 times the required erase/re-program cycles.
Note 2: The 'main' mode image file is bigger than fast boot can handle, that is why you have to copy it with dd while running in 'diag' mode.