Quote:
Originally Posted by Xaber
I try to flash my kindle.
I use command
Code:
sudo ./k3flasher mx35to2_mmc.bin program rootfs mmcblk0p1.dmp
In result i have
Code:
I: flashed 0x00010000 (=65536) bytes
I: flashed 0x00020000 (=131072) bytes
I: flashed 0x00030000 (=196608) bytes
I: flashed 0x00040000 (=262144) bytes
I: flashed 0x00050000 (=327680) bytes
I: flashed 0x00060000 (=393216) bytes
I: flashed 0x00070000 (=458752) bytes
I: flashed 0x00080000 (=524288) bytes
I: flashed 0x00090000 (=589824) bytes
I: flashed 0x000a0000 (=655360) bytes
I: flashed 0x000b0000 (=720896) bytes
I: flashed 0x000c0000 (=786432) bytes
I: flashed 0x000d0000 (=851968) bytes
I: flashed 0x000e0000 (=917504) bytes
I: flashed 0x000f0000 (=983040) bytes
I: flashed 0x00100000 (=1048576) bytes
I: flashed 0x00110000 (=1114112) bytes
I: flashed 0x00120000 (=1179648) bytes
I: flashed 0x00130000 (=1245184) bytes
I: flashed 0x00140000 (=1310720) bytes
I: flashed 0x00150000 (=1376256) bytes
I: flashed 0x00160000 (=1441792) bytes
I: flashed 0x00170000 (=1507328) bytes
I: flashed 0x00180000 (=1572864) bytes
I: flashed 0x00190000 (=1638400) bytes
I: flashed 0x001a0000 (=1703936) bytes
I: flashed 0x001b0000 (=1769472) bytes
I: flashed 0x001c0000 (=1835008) bytes
I: flashed 0x001d0000 (=1900544) bytes
I: flashed 0x001e0000 (=1966080) bytes
I: flashed 0x001f0000 (=2031616) bytes
I: flashed 0x00200000 (=2097152) bytes
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00200000 (=2097152) bytes to address 0x059c1000, waiting for completion...
I: wrote 0x00200000 (=2097152) bytes, waiting for completion...
I: flashed 0x00010000 (=65536) bytes
I: flashed 0x00020000 (=131072) bytes
I: flashed 0x00030000 (=196608) bytes
I: flashed 0x00040000 (=262144) bytes
I: flashed 0x00050000 (=327680) bytes
I: flashed 0x00060000 (=393216) bytes
I: flashed 0x00070000 (=458752) bytes
I: flashed 0x00080000 (=524288) bytes
I: flashed 0x00090000 (=589824) bytes
I: flashed 0x000a0000 (=655360) bytes
I: flashed 0x000b0000 (=720896) bytes
I: flashed 0x000c0000 (=786432) bytes
I: flashed 0x000d0000 (=851968) bytes
I: flashed 0x000e0000 (=917504) bytes
I: flashed 0x000f0000 (=983040) bytes
I: flashed 0x00100000 (=1048576) bytes
I: flashed 0x00110000 (=1114112) bytes
I: flashed 0x00120000 (=1179648) bytes
I: flashed 0x00130000 (=1245184) bytes
I: flashed 0x00140000 (=1310720) bytes
I: flashed 0x00150000 (=1376256) bytes
I: flashed 0x00160000 (=1441792) bytes
I: flashed 0x00170000 (=1507328) bytes
I: flashed 0x00180000 (=1572864) bytes
I: flashed 0x00190000 (=1638400) bytes
I: flashed 0x001a0000 (=1703936) bytes
I: flashed 0x001b0000 (=1769472) bytes
I: flashed 0x001c0000 (=1835008) bytes
I: flashed 0x001d0000 (=1900544) bytes
I: flashed 0x001e0000 (=1966080) bytes
I: flashed 0x001f0000 (=2031616) bytes
I: flashed 0x00200000 (=2097152) bytes
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00200000 (=2097152) bytes to address 0x05bc1000, waiting for completion...
I: wrote 0x00200000 (=2097152) bytes, waiting for completion...
Again and again! |
Those messages are reporting the progress of each 2Mbyte chunk.
How big is the image? 600Mbytes or something like that?
So expect that message to be repeated 300 times.
The remote (Kindle end) of the software is designed to work with a large number of devices.
To keep it simple, it is written to the lowest common denominator of all those device's features.
Translation: Its slow, its meant to be that way by the author (Freescale), just wait it out.