KT stuck on diagnostic mode boot after Kubrick

kpaxing · 05-17-2021, 02:50 PM

Hello,

I just tried to debrick my KT, was using Kubrick and everything is fine till KT has to boot into diagnostic mode. Then, KT does not boot. Then, finally after one/two days a diagnostic menu appears but does not include enable SSH (Z) option.

It is supposed that Kubrick installed ssh+diag image, is there anybody which understands what is happening here. Why is finally booting with this (seems to be) default diags image?

Thanx in advance

eddie.t.h · 05-18-2021, 05:20 AM

Without connecting to a serial port, you won't know what's going on. Knowing the first generation kt, I bet 99% damage to the Flash memory.

kpaxing · 05-22-2021, 02:24 AM

Thanx eddie.t.h,

I am waiting for a voltage regulator and connect to serial port to see what error is seen there.

kpaxing · 05-25-2021, 05:53 PM

Finally, after waiting again 2 days, KT booted in diagnostic mode and this time Enable USBNet worked and I was able to connect to KT. What I have seen is that seems that userstorage partition is damaged.

Lot of these errors appearing:

700102:022753 invalid access to FAT (entry 0x06af3b89)
700102:022753 FAT: Filesystem error (dev loop0)
700102:022753 invalid access to FAT (entry 0xa2ebdb94)
700102:022753 FAT: Filesystem error (dev loop0)
700102:022753 invalid access to FAT (entry 0x5417d28a)
700102:022753 FAT: Filesystem error (dev loop0)
700102:022753 invalid access to FAT (entry 0x6846fdc4)
700102:022754 FAT: Filesystem error (dev loop0)
...

And also a strange Transport error each time df command is executed:

[root@[192_168_15_244] local]# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 62.2M 53.5M 5.5M 91% /
tmpfs 124.9M 4.0K 124.9M 0% /dev
tmpfs 124.9M 0 124.9M 0% /dev/shm
df: /mnt/us: Transport endpoint is not connected
/dev/loop/0 3.3G 762.3M 2.5G 23% /mnt/base-us
/dev/mmcblk0p3 31.0M 5.7M 23.7M 19% /var/local
[root@[192_168_15_244] local]#

Is anyone seen this kind of error? Is it possible to rebuild this partition?

Thanks in advance,

eddie.t.h · 05-26-2021, 01:33 AM

You can try stopping it while booting and select format and overwrite fat partition. Of course if you have serial port connected.

kpaxing · 05-26-2021, 07:02 PM

eddie,

Finally is working again, I overwrote both P3 and P4 and then reboot and were rebuilt and KT booted correctly.

Used commands from KT:

root@[192_168_15_244] /root]# dd if=/dev/zero of=/dev/mmcblk0p3 count=4096
root@[192_168_15_244] /root]# dd if=/dev/zero of=/dev/mmcblk0p4 count=4096

and then reboot into main with:

[root@[192_168_15_244] /root]# idme -d --bootmode main
[root@[192_168_15_244] /root]# reboot

05-17-2021, 02:50 PM	#1
kpaxing Junior Member Posts: 4 Karma: 10 Join Date: May 2021 Device: KT	KT stuck on diagnostic mode boot after Kubrick Hello, I just tried to debrick my KT, was using Kubrick and everything is fine till KT has to boot into diagnostic mode. Then, KT does not boot. Then, finally after one/two days a diagnostic menu appears but does not include enable SSH (Z) option. It is supposed that Kubrick installed ssh+diag image, is there anybody which understands what is happening here. Why is finally booting with this (seems to be) default diags image? Thanx in advance

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle PaperWhite 1 stuck in Celeste System Diags boot mode	chobile	Kindle Developer's Corner	11	02-14-2021 03:47 PM
KT3 KT3 stuck in diagnostic mode	SKK	Kindle Developer's Corner	25	03-01-2019 04:15 PM
[PW1] stuck on U-boot / USB Download Mode / unbrick attempt	chefchens	Kindle Developer's Corner	16	02-24-2019 02:54 AM
Stuck on Diagnostic mode	Antol	Kindle Fire	2	02-27-2017 12:18 PM
HELP!!! ACCIDENTALLY FASTBOOTED, STUCK IN DIAGNOSTIC MODE	loraduhh	Kindle Developer's Corner	17	05-12-2013 06:10 PM

05-18-2021, 05:20 AM	#2
eddie.t.h Addict Posts: 201 Karma: 123456 Join Date: Jan 2018 Device: Too Much Kindle :-)	Without connecting to a serial port, you won't know what's going on. Knowing the first generation kt, I bet 99% damage to the Flash memory.

05-22-2021, 02:24 AM	#3
kpaxing Junior Member Posts: 4 Karma: 10 Join Date: May 2021 Device: KT	Thanx eddie.t.h, I am waiting for a voltage regulator and connect to serial port to see what error is seen there.

05-25-2021, 05:53 PM	#4
kpaxing Junior Member Posts: 4 Karma: 10 Join Date: May 2021 Device: KT	Finally, after waiting again 2 days, KT booted in diagnostic mode and this time Enable USBNet worked and I was able to connect to KT. What I have seen is that seems that userstorage partition is damaged. Lot of these errors appearing: 700102:022753 invalid access to FAT (entry 0x06af3b89) 700102:022753 FAT: Filesystem error (dev loop0) 700102:022753 invalid access to FAT (entry 0xa2ebdb94) 700102:022753 FAT: Filesystem error (dev loop0) 700102:022753 invalid access to FAT (entry 0x5417d28a) 700102:022753 FAT: Filesystem error (dev loop0) 700102:022753 invalid access to FAT (entry 0x6846fdc4) 700102:022754 FAT: Filesystem error (dev loop0) ... And also a strange Transport error each time df command is executed: [root@[192_168_15_244] local]# df -h Filesystem Size Used Available Use% Mounted on /dev/root 62.2M 53.5M 5.5M 91% / tmpfs 124.9M 4.0K 124.9M 0% /dev tmpfs 124.9M 0 124.9M 0% /dev/shm df: /mnt/us: Transport endpoint is not connected /dev/loop/0 3.3G 762.3M 2.5G 23% /mnt/base-us /dev/mmcblk0p3 31.0M 5.7M 23.7M 19% /var/local [root@[192_168_15_244] local]# Is anyone seen this kind of error? Is it possible to rebuild this partition? Thanks in advance,

05-26-2021, 01:33 AM	#5
eddie.t.h Addict Posts: 201 Karma: 123456 Join Date: Jan 2018 Device: Too Much Kindle :-)	You can try stopping it while booting and select format and overwrite fat partition. Of course if you have serial port connected.

05-26-2021, 07:02 PM	#6
kpaxing Junior Member Posts: 4 Karma: 10 Join Date: May 2021 Device: KT	eddie, Finally is working again, I overwrote both P3 and P4 and then reboot and were rebuilt and KT booted correctly. Used commands from KT: root@[192_168_15_244] /root]# dd if=/dev/zero of=/dev/mmcblk0p3 count=4096 root@[192_168_15_244] /root]# dd if=/dev/zero of=/dev/mmcblk0p4 count=4096 and then reboot into main with: [root@[192_168_15_244] /root]# idme -d --bootmode main [root@[192_168_15_244] /root]# reboot

Advert

Advert