View Single Post
Old 02-21-2013, 11:01 AM   #68
dsmid
Linux devotee
dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.
 
dsmid's Avatar
 
Posts: 598
Karma: 2069047
Join Date: Feb 2011
Device: Kindle 3, Kindle 4B, Kindle PW2
Thanks for reconsidering.

All that's needed is here: https://www.mobileread.com/forums/sho...37#post2431337

Checking the USB downloader mode (exits when K3 in USB DL mode is detected):
Code:
./k3flasher ./mx35to2_mmc.bin info
Flashing kernel:
Code:
./k3flasher ./mx35to2_mmc.bin program kernel <path_to_kernel_image>
Flashing rootfs:
Code:
./k3flasher ./mx35to2_mmc.bin program rootfs <path_to_rootfs_image> rootfs 1
The last two parameters work only in dpavlin's k3flasher and have this meaning:
rootfs = continuation address (just a place holder in our case)
1 = read before writing, i.e. read the chunk first, compare with the image and write only if there are any differences. This mode should be faster.

Kindle has to be rebooted manually.

If the image size is a problem, I can implement flashing gzipped images.

Last edited by dsmid; 02-21-2013 at 11:12 AM.
dsmid is offline   Reply With Quote