06-06-2012, 12:17 PM | #301 | |
THE NOOB
Posts: 701
Karma: 1545649
Join Date: Jan 2012
Location: Italy
Device: Kindle Touch 5.3.2
|
Quote:
|
|
06-06-2012, 12:51 PM | #302 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
(I haven't found the 5.1.0 kernel image (yet) ) I will update my direct linked mirror copy of your guide once you post the new one. About 60 copies of your first version have been downloaded since I posted it. Last edited by knc1; 06-06-2012 at 12:56 PM. |
|
06-06-2012, 01:11 PM | #303 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
It looks like the "forensic images" need some new uploads...
Can somebody send me links to add to the URLs list in the forensic images pastebin link from the first post? Last edited by geekmaster; 06-06-2012 at 01:14 PM. |
06-06-2012, 01:25 PM | #304 |
Member
Posts: 13
Karma: 10
Join Date: Jan 2012
Device: Kindle Touch
|
I'm back with a bricked kindle touch again!
I successfully unbricked my KT just a few hours ago, but now I tried updating it first to 5.1.0 firmware and it showed me an Error 007. It restarted so and booted up again in the main menu so everything was just fine by then. Until I tried updating it to 5.0.3 firmware (I have the .bin lying around here in my HD) and it showed me an Error 006. It rebooted and now it's stuck in the tree with the text: Please wait a moment while your Kindle starts up. So here I am again. What could've gone wrong? It won't even do a hard reset no matter how long you hold it (nor the sometimes required 2nd press after the long hold). And no, I haven't gone through the debricking method just yet. Should I not update it? EDIT: After you've debricked your kindle touch, don't update to 5.0.3. It will debrick it again. I found the solution by updating to 5.0.4 firmware. It's up and running again. Thanks to all those who helped! Last edited by kerotan; 06-06-2012 at 03:03 PM. |
06-06-2012, 01:26 PM | #305 | |
THE NOOB
Posts: 701
Karma: 1545649
Join Date: Jan 2012
Location: Italy
Device: Kindle Touch 5.3.2
|
Quote:
Here's the new link: download link. I also found a direct link in MediaFire: direct link. I added: - how to set IP - how to fix "Your Kindle Needs Repair" if you don't zero mmcblk0p3 - 5.1.0 image link (thanks to Deep!) |
|
06-06-2012, 01:39 PM | #306 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
I think that we are saving amazon from needing to replace hundreds of bricked kindles caused by their firmware updates. |
|
06-06-2012, 02:01 PM | #307 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
http://drpbox.knetconnect.com/k5/Gui...e_Touch_v2.pdf Note: The v5.1.0 (main) image noted in your v2, as posted by Deep, has Dropbear installed (plus Dropbear client and scp). Just in case that info should be mentioned somewhere in these de-brick threads. Last edited by knc1; 06-06-2012 at 02:09 PM. |
|
06-06-2012, 02:16 PM | #308 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
I noticed in the RNDIS part you say "Your PC should see a new drive (another one!!)" -- that should say "device", not "drive". Last edited by geekmaster; 06-06-2012 at 02:19 PM. |
|
06-06-2012, 03:23 PM | #309 | |
Member
Posts: 13
Karma: 10
Join Date: Jan 2012
Device: Kindle Touch
|
I've re-debricked my KT and updated it to 5.0.4 (success) but updating it to 5.1.0 (from 5.0.4) gives me Error 006 (during phase 2/2). I'm currently reading on what to do about it. Some say you have to uninstall hacks but I haven't got any hacks installed on my KT. I'll update as I trod along!
EDIT: reset to factory defaults and updating to 5.1.0 (from 5.0.4) doesn't work for me. EDIT 2: I've successfully updated my KT to 5.1.0 as per ixtab's post here: Quote:
PS Do not give up on your bricked kindle! And don't update your KT to 5.0.3 (after debricked 5.0.0)! If somehow you can't update to 5.1.0 after debricking it, follow ixtab's post above and update normally and all will be fine! Last edited by kerotan; 06-06-2012 at 04:35 PM. |
|
06-07-2012, 06:01 AM | #310 | |
THE NOOB
Posts: 701
Karma: 1545649
Join Date: Jan 2012
Location: Italy
Device: Kindle Touch 5.3.2
|
Quote:
I'll edit it, thanks!! |
|
06-07-2012, 08:08 AM | #311 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Yes.
Unless the start-up scripting erases it (its under the /usr/local sub-tree). Edit: Perhaps that is the real reason for the /opt/factory/rootfs_md5_list I mentioned above. It could be that scripting removes any file not on that list from the filesystem. It has been reported: "... scripting removes the dropbear installation in /usr/local ..." but that might just be an artifact of a more general "approved manifest" system. I.E: /usr/local is the only place where things have been put, to then later be removed by scripting. Some ambitious soul with a KT and a love for reloading the system image would need to check this out for us. If this turns out to be true, then all we have to do when installing things into the image (like SSH) is to also add the md5 of the files to this "approved manifest". Unless that turns out to be a 'signed file' with a detached signature and we end up having to deal with another signed file. I never looked for that possibility. I tried COLOR=GM and this is what I got. Looks like a day of file forensics for me. Last edited by knc1; 06-07-2012 at 08:58 AM. |
06-07-2012, 08:17 AM | #312 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Personally, I would prefer that all of the hacks that *I* want to use are pre-installed, and there was a discussion awhile back about providing an image with NOTHING installed and another one with ALL popular hacks installed. Anyway, it would be better if that main image WITH ssh in it had "_ssh" in its filename like we did with the diags partition image, to eliminate possible confusion. Also, because .bz2 files are not commonly used around here, you NEED to show how to extract it using "tar -j" instead of "tar -z"... Last edited by geekmaster; 06-07-2012 at 08:21 AM. |
|
06-07-2012, 08:29 AM | #313 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Or assumed we knew that since he had to SSH into the Kindle to copy it out, he would have left it in there. About the packaging - It is only a single file, no reason to use tar at all. And gzip is "good enough" (read: "common enough") that our posts to each other can stick with that compressor. About tar - The (GNU) tar will self-detect the compression used, if any. tar --extract --file=whatever.tar.bz2 works without specifing the compression since about version 1.15 or so. Unless you are using the (Busybox) tar - that one should be used as GM posted above. |
|
06-07-2012, 08:33 AM | #314 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
The only safe way to take an image of main is while booted from diags. When booted from main, the system periodically WRITES to the main partition (sad but true). If your open files change on the partition while copying it, that is not good. That is WHY debricking uses diags with SSH...
|
06-07-2012, 08:36 AM | #315 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
I will check the image and see if I can tell if it was copied while files where open (that testing is not a "sure thing" - would be better if Deep told us). |
|
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 |