Quote:
Originally Posted by MadMAXXX
I extract the rootfs.img out of the german 5.6.5 (link in previous post) with the most recent kindletool for linux x86 on a VM and also for MinGW. Both kindletool version extract the rootfs.img. (If you extract in linux its called rootfs.img and if you extract in Windows (MinGW) its called fwo_rootfs.img)
But still the same problem i got at beginning! Its not possible to open the rootfs.img. I tryed to mount in DAEMON Tools and to unpack with WinRAR, 7Zip and IsoBuster with no success. The error i get is always the same "unknown format or demaged file"
|
You lost me on that one.
I thought you wanted to recover your erased Kindle.
That does not require that you "open" the rootfs.img file, it is "ready to go" (onto mmcblk0p1) - that is why it is called an "image".
The purpose of using an unmodified image of the system is to get a "known good" system written to flash.
One that can be read back and compared to the image file if problems are suspected.
But if you must, I guess you must . . . .
(One useful thing you might want to do is jailbreak the image before flashing.)
On Linux VM, do:
Code:
sudo mkdir /mnt/tmp-p1 (the name does not matter)
sudo mount /path/to/rootfs.img /mnt/tmp-p1
Note that the mount command is allowed to determine for itself that this is a loop mount and the file type of the image file (ext3).
You may or may not get a warning about the missing /lost&found (I.E: /mnt/tmp-p1/lost&found) directory.
Remember:
The image is mounted read-write -- you can screw it up before flashing it.
You must umount it when your done with it, repeat: MUST.
The ext3 driver will take care of flushing buffers for you (there is no 'safely remove' command for this loop mount).
You failed to mention **which** flavor of Linux (which distribution, name and version) you have running in your VM.
It may make a difference and I can not see over your shoulder.
You have also failed to mention **HOW** you get your PW-3 into fastboot mode.
That may make a difference also.
BIG NOTE: the rootfs.img is too large for the Kindle implementation of fastboot to transfer.
Which is why you must run the Kindle in 'diags' system to flash rootfs.img.
Ah, but you don't (yet) have a 'diags' kernel and root filesystem - so we will have to follow a procedure that I don't find documented in the 'simple debricking' thread.
You have not mentioned flashing the main kernel (which is also in the Update that you unpacked).
You have not mentioned flashing the u-boot image (which is also in the Update that you unpacked) - but you should not need that, since you have the Kindle running fastboot.
Bigger Note:
Post back here when done playing with the above since the 'main' rootfs.img file will be the
LAST thing you have to flash,
not the first or only.