03-03-2012, 08:33 AM | #31 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Your USB drive partition might be damaged, but it *should* be reformatted and repopulated with factory default files if it cannot be mounted, during startup (even in diags mode) if you read the startup scripts.
Does SSH still work? You could try running the factory_restore script others have used, as mentioned in the "Select Boot" thread. If your /mnt/us is not mounted, you can mount it manually with: mount -o rw,offset=8192 /dev/mmcblk0p4 /mnt/us Or you can do this on a host linux PC: sudo ifconfig usb0 192.168.15.201 nc -l 5555 < mmcblk0p1.img and then on the kindle: nc 192.168.15.201 5555 | dd of=/dev/mmcblk0p1 bs=4K It can take up to 30 minutes to write that large mmcblk0p1 image to mmc. You have many options you can try, if you are patient and persistent, and want to invest the time to learn how to fix it. Of course, these new kindles are so inexpensive that it would be a better use of your time to just buy a new one, but then were is the fun in that? It just feels better to fix it yourself, and you learn stuff while doing this. Even the failed attempts teach you something. Last edited by geekmaster; 03-04-2012 at 12:40 AM. |
03-03-2012, 09:36 AM | #32 |
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
On the kindle that would rather be
Code:
nc 192.168.15.201 5555 | dd of=/dev/mmcblk0p1 bs=4K Code:
ssh root@KINDLE dd of=/dev/mmcblk0p1 bs=4k < mmcblk0p1.img |
03-03-2012, 09:47 AM | #33 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
And of course, the: root@KINDLE can be trimmed back to a single "shortcut" name with a "host identity" stanza in your ~/.ssh/config Which would also allow you to speed up the authentication process by setting a single key for ssh client to use, rather than trying everything it can get its hands on. |
|
03-03-2012, 10:45 AM | #34 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
P.S. Don't you just love it when even "too simple to bother testing" things cannot be trusted unless you actually TEST them, and I am all too often in a hurry and skip that important step? Thanks for the quick feedback before I added to the confusion when people tried using my information posted above. Last edited by geekmaster; 03-03-2012 at 10:53 AM. |
|
03-03-2012, 11:05 AM | #35 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
A few embarssing, public, typos, just lets the world know there is a human posting. |
|
03-03-2012, 11:25 AM | #36 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Last edited by geekmaster; 03-03-2012 at 11:27 AM. |
|
03-03-2012, 12:03 PM | #37 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
|
03-04-2012, 12:12 AM | #38 |
Enthusiast
Posts: 26
Karma: 10
Join Date: Feb 2012
Device: Kindle Touch
|
Guys, thank you all very much, and particularly to you Geekmaster, for taking so much time to work out these repair techniques and to help the likes of me, whose technical knowledge would never be at the required level.
Yes, it is easy and relatively cheap to just buy a new Kindle, but you are correct that there's no fun in that, and one definitely will not learn anything that way. Now to my Kindle again: SSH is still working, so I have tried as a first instance to run the /usr/sbin/factory_reset script. Here's the result: Code:
[root@[192_168_15_244] sbin]# ./factory_reset ./factory_reset: source: line 3: can't open '/etc/upstart/shutdown_modes' Next I tried to mount /mnt/us to see if the system image file could be accessed that way. Bingo - it worked! From there, I was able to run the dd command, seemingly without problems: Code:
[root@[192_168_15_244] us]# dd if=/mnt/us/mmcblk0p1.img of=/dev/mmcblk0p1 bs=4K 89600+0 records in 89600+0 records out 367001600 bytes (350.0MB) copied, 201.749597 seconds, 1.7MB/s Anyway, with the above completed, it seems I'm still not out of the woods yet. I'm not getting the "Your Kindle needs repair" screen any more, but the device is stuck on the tree logo and won't boot from there. Going back into diags and trying once again to run the factory_reset command via SSH gives the same error as before. This is a pretty stubborn brick considering it was all caused by a simple firmware update... |
03-04-2012, 12:36 AM | #39 | ||
Enthusiast
Posts: 26
Karma: 10
Join Date: Feb 2012
Device: Kindle Touch
|
Quote:
Quote:
Code:
[root@[192_168_15_244] sbin]# nc 192.168.15.201 | dd of=/dev/mmcblk0p1 bs=4K BusyBox v1.17.1 (2011-11-03 11:08:48 PDT) multi-call binary. Usage: nc [IPADDR PORT] Open a pipe to IP:PORT 0+0 records in 0+0 records out 0 bytes (0B) copied, 0.048217 seconds, 0B/s Anything else I can overwrite or perhaps delete so it gets re-built automatically? I recall you mentioned that (the automatic re-building) in one of your posts in another thread. |
||
03-04-2012, 12:42 AM | #40 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
nc 192.168.15.201 5555 | dd of=/dev/mmcblk0p1 bs=4K Sorry about the confusion. You can see that this was discussed in the preceeding posts above, so you could have figured out the solution by reading them. nc and netcat are the same command. I had on ongoing email discussion with avian @ the lopht (its author), back in the day... About needing to mount the USB drive yourself, you should try deleting /var/local/system/mntus.params, and then reboot. Perhaps it was corrupted by installing a hack intended for a kindle 4 (or by some other cause). Deleting it will make the startup scripts rebuild it. It contains information telling the system WHERE the usb drive is located and how to mount it. Last edited by geekmaster; 03-04-2012 at 12:45 AM. |
|
03-04-2012, 12:54 AM | #41 |
Enthusiast
Posts: 26
Karma: 10
Join Date: Feb 2012
Device: Kindle Touch
|
I have just connected my wife's "healthy" Kindle via SSH to see what the story may be with the "can't open '/etc/upstart/shutdown_modes'"
But there is no such file in that directory: Code:
[root@[192_168_15_244] upstart]# ls battery-diags display functions poll_daemons wan bundlefuncs firsttime init.sh prereg zforce diags framework makexconfig userstore |
03-04-2012, 12:55 AM | #42 | |
Enthusiast
Posts: 26
Karma: 10
Join Date: Feb 2012
Device: Kindle Touch
|
Quote:
|
|
03-04-2012, 01:01 AM | #43 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Perhaps you could run the factory restore from the main partition, but putting it in RUNME.sh with my data.tar.gz, then with ENABLE_DIAGS deleted from the usb drive, reboot to main.
I have noticed some script problems with dasmoover's image too. I got a supposedly "factory fresh" image from another user. At some point I need to compare it to dasmoover's image. Perhaps the scripts on the main partition will work better, when run from RUNME.sh. |
03-04-2012, 01:11 AM | #44 |
Enthusiast
Posts: 26
Karma: 10
Join Date: Feb 2012
Device: Kindle Touch
|
OK, so having deleted /var/local/system/mntus.params the Kindle now reboots - back to that dreaded "...needs repair..." screen.
So whatever may be causing the problem has not been fixed by overwriting the system folder with mmcblk0p1.img I suppose in this state it is not likely to be possible to launch the Amazon firmware update process again? Seeing that's what screwed it up in the first place, maybe if it were to complete properly this time, it would then work. Alternatively what would be the easiest way to copy a complete drive image of healthy Kindle to the /us partition and from there try to overwrite everything on the bad one? Considering the /us is formatted in fat32, is it possible to preserve permissions correctly if one were to use dd? |
03-04-2012, 01:59 AM | #45 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
From diags SSH, try: dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K then reformat. And does your mmcblk0p1 have a good image on it? You can copy that from the usb drive (exported in diags) to /dev/mmcblk0p1. If you can mount the usb drive manually, it should be okay. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Bricked Kindle Touch | zkat | Kindle Developer's Corner | 69 | 03-07-2012 04:08 PM |
Kindle Touch bricked without USB | rastik | Kindle Developer's Corner | 57 | 01-22-2012 08:32 PM |
Touch Any idea as to the next update of the Touch firmware? | TonyToews | Kobo Reader | 0 | 01-12-2012 08:30 PM |
Kindle Touch bricked? | LittleLui | Kindle Developer's Corner | 4 | 12-30-2011 03:18 PM |
Firmware Update Kindle bricked after 2.5 update | MePerson | Amazon Kindle | 8 | 06-30-2010 11:37 AM |