11-08-2012, 05:47 AM | #346 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
|
11-08-2012, 01:52 PM | #347 | |
Junior Member
Posts: 3
Karma: 5792
Join Date: Nov 2012
Device: Kindle K3
|
Quote:
I did the exact same think to my daughters K3 and it now says the same thing each time it tries to re-boot. Have you managed to get it working by now and if so would you , or anybody else, please tell me how, I'm in the dog-house with my daughter over this. :-( |
|
Advert | |
|
11-09-2012, 05:23 AM | #348 |
Junior Member
Posts: 2
Karma: 10
Join Date: Nov 2012
Location: Czech
Device: K3
|
K3 dead ?
Few days ago I was successful in "debricking" K3 WiFi. Today I wasn't so successful. During flashing of 'kernel.bin' I put the address 0x00000000 instead of the correct 0x00041000. It happened after filling the address (howto - 9) and picking MMDC/SD in the dropdown menu (howto - 10). I didn't notice the address changed back to 0x00000000 after the change in dropdown menu.
(I suggest switch order of 9 and 10 in "K3noobdebrickATK" howto). My Kindle looks dead or is it still chance? On 'pastebin' I found 'bootloader' and 'kernel' for FW 3.3. If I found even 'rootfs', could it work again? Do you know where I can find 'rootfs'? How should I correctly apply the 'rootfs' on my Kindle? Do you have any other suggestions, which help at this point? |
11-09-2012, 05:28 AM | #349 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
You can use the mmcblk0 (no p1) image (or at least part of it) to flash at 0x0000000, to restore your bootloader that you damaged... I think hawhill posted instructions for flashing the bootloader somewhere in his "k3flasher" thread... |
|
11-09-2012, 05:35 AM | #350 |
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
Maslan: Start with flashing partitionheader+bootloader to 0x0, plus kernel to the correct location. With a bit of luck, that should fix it already. Would be worse if you flashed the rootfs to 0x0, in that case, the device id section would have been overwritten for sure.
|
Advert | |
|
11-09-2012, 05:57 AM | #351 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
@hawhill: perhaps someday the k3flasher tool could be smarter, and prevent overwriting known ("named") partitions just because a source image file is "too big".
It should have an override flag to ALLOW flashing multiple partitions at once, but that should be an exception and not the default. IMHO... Still, the tool is great as-is, but it COULD be a bit more "noob-friendly" (i.e. safer)... |
11-09-2012, 07:23 AM | #352 |
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
Yep, it started out being not designed for noobs at all, making it extra hard for them to even use it. Now it got a bit more testing I should probably open that up some more, but as you say correctly, I should probably bring some security measures in place.
|
11-09-2012, 10:50 AM | #353 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
The "smarts" could be a wrapper script that checks parameters before calling k3flasher. Even something that simple would be a big help.
|
11-09-2012, 12:03 PM | #354 | |
Junior Member
Posts: 3
Karma: 5792
Join Date: Nov 2012
Device: Kindle K3
|
Quote:
However I managed to get my K3 to boot up by flashing the V3.4 kernal and rootfs and V3.3 partitionheader+bootloader. But it is very unstable and rest assured all the devices ID's have been overwritten as there is now no Mac addy or device ID. So without a way of editing the locations where these exist I reckon its pretty much bunched ! |
|
11-09-2012, 12:07 PM | #355 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
|
|
11-09-2012, 12:12 PM | #356 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Check first in your diags mode menu - see if you can change them there. |
|
11-09-2012, 01:47 PM | #357 | |
Junior Member
Posts: 3
Karma: 5792
Join Date: Nov 2012
Device: Kindle K3
|
Quote:
can you point me to what tools I could use to try to set Mac addy and serial number etc TIA. |
|
11-09-2012, 01:50 PM | #358 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
That "idme" tool.
I have never needed to use it myself, search for the directions here (probably in one of the sticky indexed threads - or try the site search). |
11-10-2012, 01:45 PM | #359 | |
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
Quote:
|
|
11-10-2012, 02:07 PM | #360 | ||
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Quote:
Last edited by geekmaster; 11-10-2012 at 02:09 PM. |
||
Tags |
debrick, debricking, howto, kindle 3 |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Small debricking guide for “noobs” | silver18 | Kindle Developer's Corner | 204 | 03-20-2016 09:35 AM |
[HELP] Unsuccessful debricking K4NT | jber | Kindle Developer's Corner | 12 | 07-08-2012 06:35 AM |
How to debricking My kindel 3. | gzm001 | Kindle Developer's Corner | 5 | 06-27-2012 02:40 PM |
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 |