Need Help Pls: Kindle Touch restart/reboot Malfunction

[falltree]

Originally Posted by knc1

DO NOT DO THE "ERASEALL"
Regardless of how temping it might be.

，it's quite a temptation to ERASE ALL if it's a windows system.

[falltree]

Originally Posted by ixtab

You need to compile the u-boot binary first. See the link to the instructions that I posted earlier... Or wait for some kind soul to do that for you.

That said, before you - possibly - completely toast the device: have you thought about sending it back to Amazon and getting a replacement?

Have no clue how to compile binary file, but thanks anyway, maybe I'll try it later and continue trying to debrick it. The good thing is my KT is still half-working as long as I don't reboot it.

Coz I don't live in US, I guess it's unlikely to sending my KT back to amazon, sadly the service/replacement/maintainance policy here is not as good and convinient as what amazon US provides.

[falltree]

Originally Posted by ixtab

You need to compile the u-boot binary first. See the link to the instructions that I posted earlier... Or wait for some kind soul to do that for you.

That said, before you - possibly - completely toast the device: have you thought about sending it back to Amazon and getting a replacement?

Hello again, ixtab,

I searched the thread https://www.mobileread.com/forums/sho...d.php?t=170929
and found that you and eureka provided a u-boot-bist file and a u-boot with fastboot file(page 49 or 50) at adi23's case which he reflashed his u-boot after erase all partitions, and he saved his KT with the files above.

Is that possible these files or just one of them I can use it to have my KT debricked without compiling my own u-boot binaries? And if it's true, what should I do to flash u-boot. Adi23 didn't describe the command in his post.

Thanks again.

[ixtab]

Originally Posted by falltree

Hello again, ixtab,

I searched the thread https://www.mobileread.com/forums/sho...d.php?t=170929
and found that you and eureka provided a u-boot-bist file and a u-boot with fastboot file(page 49 or 50) at adi23's case which he reflashed his u-boot after erase all partitions, and he saved his KT with the files above.

Is that possible these files or just one of them I can use it to have my KT debricked without compiling my own u-boot binaries? And if it's true, what should I do to flash u-boot. Adi23 didn't describe the command in his post.

Thanks again.

No, you can't use the files that were posted there. They are both meant for different things. That said, I'm attaching a standard u-boot (imx50_yoshi_config), compiled straight from the original sources.

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).

[falltree]

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.

[knc1]

These are the only interesting bits that I see:

700101:000056 charger: Stop charging as battery is full
700101:000059 kernel: I papyrus:TempExceeded:temp=36:

Probably not a normal message.

700101:000125 dropbear[1074]: Child connection from 192.168.15.1:54388
700101:000133 dropbear[1074]: password auth succeeded for 'root' from 192.168.15.1:54388

You where able to ssh into the device.

700101:000133 dropbear[1075]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directory
700101:000133 dropbear[1075]: lastlog_openseek: /var/log/lastlog is not a file or directory!

This is not part of the new /var/local that was just re-formatted.
Questionable.

700101:000159 kernel: I papyrus:TempExceeded:temp=35:
700101:000259 kernel: I papyrus:TempExceeded:temp=35:

No way should the battery be 95 degrees F (35 degrees C) -
How hot is the location you have your Kindle?

Put that little sucker in your refrigerator for a few hours - see if it completes booting.

Also - you posted an *.rar archive -
Does this mean you are one of the "Windows Handicapped" users?

If so.:
Always check the line endings of any file you modify !
Always ensure that any file transfer is done in **binary** mode !

[NiLuJe]

I haven't checked the logs, but I'm assuming that's a boot in diags, because my dropbear build from USBnetwork doesn't support lastlog, and looks for its hostkeys somewhere else .

[falltree]

Originally Posted by knc1

These are the only interesting bits that I see:

700101:000056 charger: Stop charging as battery is full
700101:000059 kernel: I papyrus:TempExceeded:temp=36:

Probably not a normal message.

700101:000125 dropbear[1074]: Child connection from 192.168.15.1:54388
700101:000133 dropbear[1074]: password auth succeeded for 'root' from 192.168.15.1:54388

You where able to ssh into the device.

700101:000133 dropbear[1075]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directory
700101:000133 dropbear[1075]: lastlog_openseek: /var/log/lastlog is not a file or directory!

This is not part of the new /var/local that was just re-formatted.
Questionable.

700101:000159 kernel: I papyrus:TempExceeded:temp=35:
700101:000259 kernel: I papyrus:TempExceeded:temp=35:

No way should the battery be 95 degrees F (35 degrees C) -
How hot is the location you have your Kindle?

Put that little sucker in your refrigerator for a few hours - see if it completes booting.

Also - you posted an *.rar archive -
Does this mean you are one of the "Windows Handicapped" users?

If so.:
Always check the line endings of any file you modify !
Always ensure that any file transfer is done in **binary** mode !

Thanks for the post.
Yes, This might not be a normal message as I booted it up from mfgtool to diags, I thought it could be a boot log of diags. But there's no other way I can access the boot log when it failed to reboot.
I didn't feel hot from my KT or the battery, it's just the room temperature around 27 degree C or 30 at most I guess. It doesn't seems to be 35 degree C, I didn't know anything about it, and I'll keep it in mind to make it gets cooler.

And I am a Windows user, I know very little about Linux, that's why I am here asking help from your expertise. I transfer the .rar just because when i was uploading it with the original name(messages), the forum told me that it's invalid, so I zipped it in Winrar and upload it again. I'm sorry if I did anything wrong or did not follow the forum policies.

[knc1]

Originally Posted by falltree

.
And I am a Windows user, I know very little about Linux, that's why I am here asking help from your expertise. I transfer the .rar just because when i was uploading it with the original name(messages), the forum told me that it's invalid, so I zipped it in Winrar and upload it again. I'm sorry if I did anything wrong or did not follow the forum policies.

Nothing done wrong -

Just looking for why you are having the problem you are having, hence the two reminders of the most often cause of problems encountered by users of Windows.

So the device is working 'normally' without any change from your first post.

Other than it is booting to diags.
Because you told it to with the idme command?

So now try the same thing, only use mfgtool to tell it to boot to 'main'.
Just like ixtab gave you directions for.
See if that has changed.

PS: You may have to use the newest version of KUBRICK to reformat the user storage partition - and lose everything you have transferred to the device (and any ENABLE_DIAGS file on it).