08-18-2012, 02:19 AM | #1 |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
Unbriking Kindle DX
Hi.
My Kindle DX (US cdma ver.2009) now doesn't want to boot. In serial console i can see this log (below). As i understand system partition is damaged somehow (kinit: init not found!) What can i do to try to repair? As i undersatan need to use Load MMC0 over USB storage (with rootfs.img/rootfs.tar.gz) i have password (with KindleDiagnosticTool) or maybe it is possible to browse/fix FS only by commands from console? (i can't type anything from hyperterminal now) Can somebody help me with getting this image from DX US? Plz help Thanks! bootLOG: Spoiler:
Starting kernel ... Spoiler:
Last edited by dreams; 08-19-2012 at 02:16 PM. Reason: added spoilers - moderator |
08-18-2012, 02:26 AM | #2 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Please put that kernel message log inside of 'SPOILER' '/SPOILER' tags using [ and ] in place of the ' shown in this sentence.
|
Advert | |
|
08-18-2012, 03:56 AM | #3 |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
unbriking kindle dx
also when i'm trying to update via recovery menu (U - update on userstore)
console says: ERROR: OTA version not supported. ERROR:Could not unbundle /mnt-us/update2.bin this is last 2.5.8.bin from amazon site (any previous like 2.3.3 also not working) Why is this? Thanks for ANY help! LOG: Spoiler:
|
08-18-2012, 07:26 AM | #4 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Take a look at the first log you posted (and while looking at it, edit in some spoiler tags).
See the message from U-Boot that it could not read the environment variables? See the message that it had to use the secondary kernel? Either something over-wrote the start of your mmcblk0 (the raw device, before the partition table) or you had erase block failures the eMMC controller could not correct. |
08-19-2012, 05:35 AM | #5 | |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
Quote:
So do you think that overwriting rootfs (with previous formatting) with 3. Load MMC0 over USB storage will not help me? Maybe i can try to overwrite mmcblk0 with dump (if someone can provide it) also? (NB:anyway can someone give me the rootfs.img for DX b004 plz??) Will 4. Erase MMC0 or I. Initialize Partition Table (fdisk) and format FAT help me somehow (if i'll had needed dumps from someone)? Maybe formatting will exclude bad blocks (if they're the source of errors)? Thanks for support. p.s. sorry for dumbness but i can't find edit button to add [SPOILER] for my first message. |
|
Advert | |
|
08-19-2012, 10:10 AM | #6 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
I am not familiar with the DX machine.
I do not know what you have done that got you into whatever situation you are in. I do not know where you can get recovery images for a DX machine. It should be obvious from the title that: 4. Erase MMC0 Is not going to improve your current situation. Once you do that, if it does what it says, then the only firmware on the machine will be the iROM code (a very low level firmware loading command processor). The Freescale ATK can still "talk" to your DX once you do that. So could the K3Flasher if you modified the code to include the i.MX31 related things rather than the i.MX35 stuff for the K3. - - - - Try looking for th edit button again, after you have made a few more posts. I think the system has a minimum of ten posts required before it turns on the edit button for a person. |
08-19-2012, 10:40 AM | #7 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Erasing MMC0 will also erase the bootloader. That is about as bricked as you can get. Not a good idea, and never necessary. You can flash without erasing.
|
08-19-2012, 01:13 PM | #8 | |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
Quote:
only recovery one is possible now. By log i see that it has no access to rootfs, so i think to try to overwrite it with image (if someone can provide it) As i understand (with help command) Uboot has no capabilities of browsing and diagnosting file systems.. Maybe i can upload and run some apps via loady/bootm cmds.. Also i have an idea of using 3.21 unofficial packet for Kindle DX http://www.reddit.com/r/kindle/comme...stall_kindle_3 x_on_kindle_2_and_dx/ It seems overwrites rootfs with its update.. Did anybody with DX US prepared/used this 3.21 update? That is the main problem for me.. Anybody with DX US here?? Plz help! I can provide some instructions/packages from other forum to make backup images (if jailbreak is installed). Someday this backup can be necessary for DX US owners! thanks! |
|
08-20-2012, 08:49 AM | #9 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
EDIT: I see that your first post says CDMA, which would be the white DX. I suppose I could extract firmware images with dd when I get some time. Last edited by geekmaster; 08-20-2012 at 09:30 AM. |
|
08-20-2012, 09:26 AM | #10 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
It seems strange that you don't have a left over backup image or two on hand from when you tested those "instructions/packages".
|
08-20-2012, 11:00 AM | #11 | |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
Quote:
It could be great if you do this images! as i understand with somth like: "dd if=/dev/mmcblk0 of=/mnt/us/mmcblk0_7688.dmp bs=512 count=7688" "dd if=/dev/mmcblk0p1 of=/mnt/us/mmcblk0p1.dmp" then as i undersatnd i need to "3. Load MMC0 over USB storage" it will show me 3 parttions sdx1=400mb, sdx2=24mb, sdx3=3Gb and "mkfs.ext3 /dev/sdX2" "dd if=/path/to/mmcblk0p1.dmp of=/dev/sdX1 bs=1MiB" and reboot maybe i need to format sdx1 also to verify bad blocks? is it ext3? Big ThankS! p.s. 2knc1: i start to learn all this only after DX crash.. |
|
08-20-2012, 11:11 AM | #12 |
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
hm, you should be able to fix it with only with the "Load MMC0 over USB storage" option (if it is fixable and not a hardware defect).
That said, I'm not sure how the filesystems are laid out on the KDX b004. I guess from the sizes that sdx1 is rootfs, sdx2 is /var/... and the third one is the user store. From the logs you have posted, the initramfs can not mount the root file system. So don't concentrate on the rest of the partitions yet, but rather check the root file system. Can you mount it on the host machine? Before messing with it, I would suggest to make a full dump of everything, i.e. the full block device (not just single partitions). And try to run e2fsck on the root file system then. |
08-20-2012, 01:16 PM | #13 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Not if your DX is running Linux. You have to pay attention to the device names and naming conventions, those are not arbitrary, they mean things. sd<anything> Scsi Device - /dev/sd<whatever> is a device holding a file system. mmc<whatever> - this is a storage device, almost always flash, that has a "high level", embedded, controller that accepts "disk drive" commands. Disk drives do: "Read,Write,Seek, ..." MTD - Memory Technology Devices (here: flash) do: "Read, Erase, Re-program, ..." "Flash" :: eeprom (electrically erasable programmable read only memory) Add an embedded device controller to a MTD storage part == a MMC storage part != file system With that $0.05 tour of naming conventions, you should now be able to read the above "dd" command and explain how and why you are about to trash the system storage if you use it as written. No. The controller of the underlying device manages the bad erase blocks (the underlaying device has "erase block" not "storage sectors" - the mmc controller is faking that). It is using EEC to detect/correct and/or detect and retire the erase blocks in use at the storage media level. The file system level should never see "bad blocks". So how did you test what you are intending to post? |
|
08-20-2012, 03:43 PM | #14 | |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
Quote:
http://yifan.lu/2011/04/02/recoverin...rupt-kindle-2/ and other forum too (commands were near the same) both sources had confirm this working for em. Also I did post it here to verify and asking of where i'm wrong or right.. |
|
08-20-2012, 03:46 PM | #15 | |
Member
Posts: 10
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
|
Quote:
http://yifan.lu/2011/04/02/recoverin...rupt-kindle-2/ and other forum too (commands were near the same) both sources had confirm this working for em. Also I did post it here to verify and asking of where i'm wrong or right.. p.s if you mean only about sdX name is wrong sure i will replace it with real name; else i didn't understand clear what did you mean.. thanks |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Touch unbriking troubles | aguzman | Kindle Developer's Corner | 9 | 09-06-2012 07:23 AM |
$0.01 in Kindle Store: Interactive Sudoku for Kindle 2 and Kindle DX - Volume 1 | Xia | Deals and Resources (No Self-Promotion or Affiliate Links) | 2 | 11-07-2009 10:06 AM |