06-12-2012, 10:18 AM | #361 | |
Member
Posts: 13
Karma: 10
Join Date: Jun 2012
Device: Kindle Touch
|
Quote:
So diags kernel is different to main kernel, and I would need a matching diags kernel. In the first post it links to download the Kindle "Forensic" Images from http://pastebin.com/Wdw4L7yT in this pastebin page, there's only diags_kernel-5.0.0: http://www.mediafire.com/?wxv0eat6lcz6mx6 and mmcblk0p2_ssh-5.1.0: http://www.mediafire.com/?un3qrdfblfyl1d0 So these two won't match. In the pastepin page there're other two kernel-5.0.0 kernel-5.0.4 not sure if they are main or diags kernel. And in download page http://gitbrew.org/~dasmoover/kindle/touch/forensic/ there're kernel-kt-5.0.0.img.gz kernel-kt-5.0.4.img.gz are these main or diags kernel? There're also mmcblk0p2_ssh-kt-5.0.1.img.gz and mmcblk0p2_ssh-kt-5.1.0.img.gz So could you point out for me which diags kernel and diags img files should I use? Best Regards, |
|
06-12-2012, 10:36 AM | #362 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
In the pastebin page, these two are a matched pair:
mmcblk0p1-5.1.0 main_kernel-5.1.0 The files at: http://gitbrew.org/~dasmoover/kindle/touch/forensic/ Are matched pairs for the v5.0.0 "diag" partition. Which should be "good enough". Although those kernels are not marked, I seem to recall they are the "diag" kernels. Note that "0p1" indicates the "main" partition and "0p2" indicates the "diag" partition. - - - - *nix nit: The Linux kernel build used by the Kindles is a "modular" build. Many of the features and drivers are not "built-in" but reside in loadable modules. The kernel code version and the module code version must match for things to work correctly. Since the kernel is in the "kernel image" and the modules are in the "system image" those versions must match (to ensure the internal code versions match). Last edited by knc1; 06-12-2012 at 10:53 AM. Reason: I felt like it. |
Advert | |
|
06-12-2012, 10:43 AM | #363 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
5.0.0 through 5.0.3 used the 5.0.0 kernel I think. The kernel did not get updated by amazon until 5.0.4 as I recall...
Also, do not confuse main kernel with diags kernel... |
06-12-2012, 11:28 AM | #364 | |
Member
Posts: 13
Karma: 10
Join Date: Jun 2012
Device: Kindle Touch
|
Thanks guys.
Tried the kernel-kt-5.0.0.img.gz and diags mmcblk0p2-kt-5.0.0.img in page http://gitbrew.org/~dasmoover/kindle/touch/forensic/ still no luck on diags mode, it reboots, two white screen then black, then back to the tree screen. Either my Kindle Touch is broken too much or the kernel in that page kernel-kt-5.0.0.img.gz is not a diags kernel. Quote:
http://pastebin.com/Wdw4L7yT diags_kernel-5.0.0: http://www.mediafire.com/?wxv0eat6lcz6mx6 still no diags mode = = Last edited by rynax; 06-12-2012 at 11:32 AM. |
|
06-12-2012, 11:36 AM | #365 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
The diags kernels have "diags" in the filename, and the main kernels do NOT have diags in the filename (just like fastboot help shows).
You need a compatible version of the diags kernel for your diags partition. Flashing a main kernel to onto the diags kernel will not work. And you need an ENABLE_DIAGS file. Do you have one? Did you try booting to diags with MfgTool? |
Advert | |
|
06-12-2012, 10:43 PM | #366 | |
Member
Posts: 13
Karma: 10
Join Date: Jun 2012
Device: Kindle Touch
|
Quote:
ok I realised that I would have to flash the diags kernel to diags_kernel. diags_kernel-5.0.0.img.tgz unzipped and flashed to diags_kernel mmcblk0p2-kt-5.0.0.img to diags Same thing. Tried MfgTool to boot into diags mode, it says operation successful but the device still goes to the tree screen. |
|
06-14-2012, 04:49 AM | #367 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Start USB downloader mode with "magic key". Start fastboot mode with MfgTool. Flash diags partition and diags kernel with fastboot. Flash main kernel with fastboot. Boot to diags. Flash main partition using diags SSH "dd" command. Erase mmcblk0p3 using diags SSH "dd" command. Set main boot mode with idme command. reboot. It should work. It worked for many people. See the "success reports" list in the "simple debricking" thread. Details for above steps are provided in the "small debricking guide for noobs". Find in in master index/tools index. It is a PDF file... |
|
06-15-2012, 04:16 AM | #368 | |
Member
Posts: 13
Karma: 10
Join Date: Jun 2012
Device: Kindle Touch
|
Quote:
do you need a main kernel in "kernel" or a diags kernel in "diags_kernel" or both to be able to go into diags mode? |
|
06-15-2012, 07:07 AM | #369 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Same principle as setting up your PC as "dual boot", to boot either Linux or Windows. You can boot Linux and use it to fix Windows; You can boot Windows and use it to break Linux. Earlier Kindles also are setup as a "Dual Boot" computer. It those they boot either the regular system or a memory resident system. An embedded Linux version of being able to boot your "rescue" system from your LiveCD. - - - *nix nit: The inode file systems used by *nix systems have a very strong separation between the file system naming (directory) system and the file system data storage system. This allows a file that is open and in use to be deleted and replaced without disturbing the programs that have it (the old one) open and in use. The "delete and replace" name in the directory is separate from the "delete and replace" of the data. On a system without constrained media storage size, not a problem to have two copies (old and new) of a file present at the same time. On a system with highly constrained storage size (a small, fixed size, flash memory) this behavior when updating will cause you to run out of room in a hurry. So the practice in the embedded Linux world is to have two bootable systems, where the one running is used to update the one that is not running. I.E: None of the files being replaced or changed are open and running. That lets both the name and the data storage of a file to be deleted and replaced without using double of the storage area. Windows does not work like that. They do things their way. In Windows, you'll eventually get a "system restart required" message. If you watch the progress message while your *nix package manager does a system update, you will see (if required) a four step sequence:
|
|
06-15-2012, 09:52 AM | #370 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Technical Details: Spoiler:
|
|
06-16-2012, 03:26 AM | #371 | |
Member
Posts: 13
Karma: 10
Join Date: Jun 2012
Device: Kindle Touch
|
Quote:
Quote " Also, you should keep the kernel versions matching the one that amazon shipped with whatever version of boot partitions you use." I guess the boot partition is referring to the partition 1 for normal mode and partition 2 for diags mode? Is there diags_kernel image file that is not 5.0.0? Last edited by rynax; 06-16-2012 at 03:53 AM. |
|
06-16-2012, 10:41 AM | #372 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
The simple debricking instructions were written when the kernels had not changed since introduction of those kindle models. Starting with 5.0.4 and 4.1.0, there are new kernels, so it became important to either flash boot partitions that match your kernels. Rather than have people try to figure out whether or not they need to flash a kernel, the process is so fast it is simpler to tell people to always do it. The point is that if you have a main kernel that is not compatible with the main partition, you will have problems in main or diags, depending on which partition has an incompatible (mismatched) kernel. You can download a 5.1.0 diags kernel and partition. For main, it is easier to downgrade to 5.0.0, then install whatever firmware upgrades you want. Beware that if you have wireless on, amazon may push an OTA upgrade to your device. |
|
06-17-2012, 04:06 AM | #373 |
Junior Member
Posts: 3
Karma: 10
Join Date: Jun 2012
Device: K4NT
|
Debricking failed
I have a K4NT that is bricked and I was unsuccessful to unbrick it based on this thread and silver 18 guide.
What I was able to do : - Use MgfTool - Use FastBoot mode to flash diags and main kernel - Boot to diags - Go to usb device mode to copy the mmcblkop1 partition to /mnt/us - SSH in diags mode by using usb network - write mmcblk0p1 using dd (seems to be successfull according to the dd output) - zeroed mmcbll0p3 - set boot target to main with idme What didn't work : - seems stuck at the rebooting stage (nothing happens, even after a long time like 10 minutes) Others info that may help : - All the images used for flashing and dd are from here, as given in the first post - I was running 4.1.0 before it was bricked. - If the ENABLE_DIAGS is present, rebooting it from the diags mode will put it back in diags mode as expected. - Using MgfTool and trying to boot to diags succeds - Using MgfTool and trying to boot to main, fails. My guess : There is something wrong with my main. Either there may be something wrong with the mmblck0p1 image or with the kernel (I've tried dowloading them again and redid the process, without improvment). Or there is some incompability because I was in 4.1.0 and try restoring to 4.0.1. I am loss at how to go forward. Any ideas regarding further steps and things to try are warmly appreciated. |
06-17-2012, 07:09 AM | #374 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
All of those images are in a compressed format.
The formats used all have internal checksums, the un-archiver(s) would have given a warning when un-compressing them if they where incomplete or damaged in transit... Sorry, but I have to ask... You did un-archive them before using the files, correct? Where did you get the two (2) different kernels you flashed? Was one of the kernels in that *.tar.gz archive? Edit: Answered my own question, that *.tar.gz only contains a single file, the image file. (A harmless mis-packaging by the poster.) Last edited by knc1; 06-17-2012 at 07:42 AM. |
06-17-2012, 07:58 AM | #375 | ||
Junior Member
Posts: 3
Karma: 10
Join Date: Jun 2012
Device: K4NT
|
Quote:
Quote:
The archive containing the kernel was kernel-k4-4.0.1.img.gz, and not kernel-k4-4.0.1.img.tar.gz, and it contained only kernel-4.0.1.img when I extracted it |
||
Tags |
debricking |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Which one Nook simple touch or Kobo mini? | capuchino71 | Which one should I buy? | 18 | 07-12-2013 05:09 PM |
Sell Kindle Keyboard 3G, Nook Simple Touch | austinmitchell | Flea Market | 5 | 03-01-2013 11:34 AM |
I have some questions about K4 touch debricking | drjonvargas | Kindle Developer's Corner | 4 | 04-22-2012 03:46 PM |
kindle touch simple debricking for help | non_fox | Amazon Kindle | 4 | 04-18-2012 08:32 PM |
Troubleshooting simple kindle touch (and k4nt) debricking method | geekmaster | Amazon Kindle | 0 | 03-02-2012 10:31 PM |