Quote:
Originally Posted by ixtab
I don't really have an idea about what to do with it, but the most sensible thing IMO should be to boot into fastboot mode and then "fastboot flash bootloader u-boot.bin", followed by "fastboot setvar bootmode main" and "fastboot reboot". (adi23 used a serial connection to the kindle to debrick it, which is an entirely different thing again).
However, I repeat it again: I take absolutely no responsibility. In the worst case, this might completely brick your device and leave only serial debricking as an option (if at all). In the best case, it'll work afterwards. In the second-best case, the situation will essentially remain unchanged from what it is now - but then we'd at least know that the culprit most likely wasn't the boot loader. (However, what else it could be: no idea).
|
Thanks for the file, I just flashed it(seems successful) and got no luck
, there is nothing changed, the KT remains the same.
Then I recalled that I should check the boot log. There are 2 files under /var/log, messages, wifichipdbg.log. And I copy the file messages to /mnt/us, then opened it and found something as below:
Line 125 pmic_battery: probe of pmic_battery.1 failed with error -1
Line 212 dropbear[697]: Failed reading '/etc/dropbear/dropbear_dss_host_key', disabling DSS
Line 234 dropbear[830]: Failed reading '/etc/dropbear/dropbear_dss_host_key', disabling DSS
Line
235 dropbear[830]: Failed listening on '22': Error listening: Address family not supported by protocol
And something I am not sure, maybe it's not an error log:
Line 202 VFS: Can't find ext3 filesystem on dev mmcblk0p3.
Line 203 system: I filesystems:createvarlocal:Creating /var/local filesystem:
Line 204 wm8962_process_req
Line 205 kjournald starting. Commit interval 5 seconds
Line 206 EXT3 FS on mmcblk0p3, internal journal
Line 207 EXT3-fs: mounted filesystem with writeback data mode.
here I upload the message, hope you guys can help on locating the problem. Thank you.