K4NT won't boot and can't use diags mode.

[knc1]

Originally Posted by Kafkarudo

Already tried Kubrick, and it goes well until ask me to use the diags menu.Because every time I go to diags, the screen behaves like I said.

I read that post earlier.

What I just wrote was:
**Use the image files shipped on the Kubrick LiveCD**

I.E: Just mount the LiveCD to access the image files.
That allows you full access to the files **without running** the LiveCD.

- - - - - -

PS: Kubrick is just a script wizard that uses the same command line tools you are using manually.
If the process doesn't work for the wizard, it is unlikely to work for you when you do the steps manually.

[Kafkarudo]

Ok, I'm trying to extract the files but it seems that are compressed in a lzm file. Do you know how can I extract lzm from windows? I used squashfs but I get that can't find su

Edit: never mind , I just flash with the files from Kubrick and not result, the diags menu its still broken.

[knc1]

Originally Posted by Kafkarudo

Ok, I'm trying to extract the files but it seems that are compressed in a lzm file. Do you know how can I extract lzm from windows? I used squashfs but I get that can't find su

Edit: never mind , I just flash with the files from Kubrick and not result, the diags menu its still broken.

Then you either did something wrong, or your device has a hardware problem and is now just spare parts.

[Kafkarudo]

is there any chance to fix the main partition without the diags menu?
is there an special order to flash the files?

i can`t been doing anything wrong, is not that hard, put it in fastboot,check with getvar version, then flash kernel kernelfile,flash diags_kernel diagsfile, flash diags_partition partitionfile.
then setvar bootmode diags
reboot.

[knc1]

Originally Posted by Kafkarudo

is there any chance to fix the main partition without the diags menu?
is there an special order to flash the files?

i can`t been doing anything wrong, is not that hard, put it in fastboot,check with getvar version, then flash kernel kernelfile,flash diags_kernel diagsfile, flash diags_partition partitionfile.
then setvar bootmode diags
reboot.

Then that narrows down the problem to either you are the first of thousands of users this did not work for on a good Kindle,
or
Your Kindle is bad.

[Kafkarudo]

If we assume the first, how can it be? help me understand how the kindle works. All the partitions are from the same flash memory? Knowing that the kindle almost start but get stuck, can we assume that is not a hardware failure?

[knc1]

Originally Posted by Kafkarudo

If we assume the first, how can it be? help me understand how the kindle works. All the partitions are from the same flash memory? Knowing that the kindle almost start but get stuck, can we assume that is not a hardware failure?

None of your flashing attempts ever changed the behaver.

We can assume that the hardware writes never happened at the chip level.

(Or the same programming mistake has been made each time.
Such as failure to uncompress an image or other operator error in file handling.)

[Kafkarudo]

But the fastboot gives me an ok when finish writing, is it not confirmation that the writing was good?

[knc1]

Originally Posted by Kafkarudo

But the fastboot gives me an ok when finish writing, is it not confirmation that the writing was good?

No, that means there where no file transfer errors detected.
See: https://www.mobileread.com/forums/sho...49&postcount=3

There are threads here where doing read-back confirmation of what was suppose to be written have been considered (back in the K3 days), but I am pretty sure that the stock fastboot does not do that.

The ultimate source of an answer to this question is the source code (which is published by Amazon).

[siauw]

did you manage to fix the problem? I have same problem too

[Kafkarudo]

no...

[siauw]

too bad.. I think I have to buy a new kindle then