Now the programing of rootfs is over, however, my K3g is still unresponsive.
The log of the programing shows:
Code:
$sudo ./k3flasher mx35to2_mmc.bin program rootfs ./mmcblk0p1.img
...
I: flashed 0x001f0000 (=2031616) bytes
I: flashed 0x00200000 (=2097152) bytes
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00200000 (=2097152) bytes to address 0x28bc1000, 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 0x00007000 (=28672) bytes to address 0x28dc1000, waiting for completion...
I: wrote 0x00007000 (=28672) bytes, waiting for completion...
I: flashing of 0x00007000 (=28672) bytes complete
So, I think it does finished the rootfs pushing.
Now, the k3flasher can not connect the device again. The device seems still in USB downlaoder mode:
Code:
$lsusb |grep Free
Bus 002 Device 043: ID 15a2:0030 Freescale Semiconductor, Inc.
$sudo ./keflasher mx35to2_mmc.bin info
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
I: read info
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I guess the battery power is probably exhausted. I'm charging the battery now.
Well, the previous version of my K3 is 3.0.2. Now it seems I just upgrade it to v3.3 directly from 3.0.2, I don't know whether this will cause some problems, I just didn't follow the 'first 3.1 then 3.3' order says by Amazon...