Worked example of the k3flasher unbricking a K3 to a 3.0.2 via Linux Mint
I grabbed the source from the top-post of this thread.
did a
make
grabbed the two debricking images for the the 3.0.2 image.
mmcblk0p1-3.0.2-factory.img and k3w-kernel-factory.img
Used Wine to handle ATK install.
located my
mx35to2_mmc.bin via
locate mx35to2_mmc.bin
(you could use
find or w/e) it was obviously in a subdir of my .wine folder
change directory to the build folder and copied mx35to2_mmc.bin to that folder too for ease of use.
cd /usr/local/src/k3flasher
cp ~/.wine/or/whatever/blah/mx35to2_mmc.bin ./
Do the same for the debricking images...
then: read the README.!!
jumped to:
Quote:
---snip---
root# ./k3flasher ./mx35to2_mmc.bin info
W: cannot find device (is it in USB loader mode? are you root?) - waiting for it..
---snip---
Each second, a new dot will appear. There is no timeout, so if you want
to abort, hit CTRL-C.
|
sudo ./k3flasher ./mx35to2_mmc.bin info
reset kindle, holding down -vol
output of kindle info: We are in usbdownloader mode. Great.
Flash the 3.0.2 Kernel then...
sudo ./k3flasher ./mx35to2_mmc.bin program kernel ./k3w-kernel-factory.img
Quote:
I: flashed 0x00200000 (=2097152) bytes
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00200000 (=2097152) bytes to address 0x0f7c1000, 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
...
Snip
|
takes very little time
now the rootfs (this will take a couple of hours)
sudo ./k3flasher ./mx35to2_mmc.bin program rootfs ./mmcblk0p1-3.0.2-factory.img
Quote:
: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00200000 (=2097152) bytes to address 0x103c1000, waiting for completion...
I: wrote 0x00200000 (=2097152) bytes, waiting for completion...
I: flashed 0x00010000 (=65536) bytes
I: flashed 0x00020000 (=131072) bytes
...
Snip
...
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00007000 (=28672) bytes to address 0x28dc1000, waiting for completion...
I: wrote 0x00007000 (=28672) bytes, waiting for completion...
I: flashing of 0x00007000 (=28672) bytes complete
(and we are done a few hours later)
|
Each write cycle is worth 2Mb. so 300 Mb = 150 loops...
each cycle takes about 30 seconds. so 4MB per minute.
681.6Mb = ~341 loops = 170.4 minutes = 2.84 hours
keep waiting... when it's done - reboot.
EDIT: IF it complains after the reboot (mine did) just reboot it again. sorted.
Thanks for this great application. It has saved countless time and is much appreciated by all, vocally or not.