Quote:
Originally Posted by falltree
Thank for your kind response, guys.
I thought the built-in boot loader was damaged before and then I realize that maybe it's not, because when i boot KT up to main via mfgtool, and then select the restart item in the Menu-Setting-Menu-restart, it does seemed to restart and then stuck in the normal startup screen(the tree). Maybe that means the built-in boot loader still working?
|
That screen is actually drawn *before* the reboot occurs - it's the last thing that the device does before actually rebooting.
Quote:
|
If I select D) D) Q) in diags(boot to diags via mfgtool), the screen froze at diags main menu, not stuck in the normal startup screen. I think this is the reason we think about the built-in boot loader was screwed up, it seemed the restart process failed to start.
|
Again, the devices tries to reboot, but since it fails, what you see is the last thing that was on the screen before that - in this case, the diags menu.
One last straw that you could try is to use the "idme" command to set the next bootmode while in diags, i.e.: boot into diags, enable usbnetwork, connect via SSH, and issue "idme -d --bootmode main; reboot". But I'm rather pessimistic that it will make a difference.
And finally, you could boot into fastboot mode, and try to overwrite the bootloader "partition" with a freshly compiled u-boot. Instructions for compiling it are
here. However,
THIS COULD WELL MAKE THINGS EVEN WORSE, and possibly completely brick the device - as far as I know, nobody has ever ventured there. But If you have nothing to lose and are ok to act as a guinea pig, then go for it and report back...
Code:
usage: fastboot [ <option> ] <command>
commands:
getvar <variable> display a bootloader or idme variable
setvar <variable> <value> sets an idme variable
download <filename> download data to memory for use with
future commands
verify <partition> [ <filename> ] verify downloaded data. required if
bootloader is secure
flash <partition> [ <filename> ] flash downloaded data
eraseall wipe the entire flash memory
erase <partition> erase a flash partition
check <partition> crc32 hash test the flash memory
boot [ <filename> ] boot downloaded data
continue exit fastboot and return to
bootloader
reboot reboot the device
powerdown shuts down the device
pass sets LED to green
fail sets LED to red
variables:
version-bootloader (read only) version string for the
bootloader
version (read only) version of fastboot
protocol supported
product (read only) name of the product
serialno (read only) fastboot serial number
secure (read only) if "yes" boot images
must be signed
serial (read write) serial number
accel (read write) accelerometer
calibration data
mac (read write) MAC address
sec (read write) manufacturing code
pcbsn (read write) PCB serial number
bootmode (read write) diags, fastboot,
factory, reset, or main (default)
postmode (read write) slow, factory, or
normal (default)
partitions:
bootloader bootloader, 376KiB
prod overlaps bootloader, 120KiB
bist bist, 256KiB
userdata userdata, 5KiB
userpartition userpartition
mbr master boot record
kernel primary kernel
diags_kernel diags kernel
system main system (root) partition
diags secondary system (diags) partition
data user data
options:
-s <serial number> specify device serial number
-i <vendor id> specify a custom USB vendor id