02-04-2013, 01:39 PM | #1096 | |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
Quote:
|
|
02-04-2013, 01:41 PM | #1097 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
|
|
02-04-2013, 01:56 PM | #1098 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
We must be patient with noobs even with our extensive published resources in plain sight, when even the best of us fail to find stuff that is "hiding in plain sight" at times. Searching the sheer quantity of useful information published here is a chore even WITH the indexes and thread prefixes and sticky threads, but BEFORE we had them it was even more difficult to find things. If anybody has suggestions for better ways to help find things here, please speak up! Last edited by geekmaster; 02-04-2013 at 02:04 PM. |
|
02-04-2013, 02:08 PM | #1099 |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Hmmm... I just noticed something odd with the standalone version:
booting to fastboot, then: fastboot setvar bootmode diags fastboot reboot does not work with the standalone one. The device stays in a "non-working" fastboot mode. With the "original" fastboot.bin, everything works as expected. This is reproducible. Any thoughts? (My guess is that the standalone version can't set the bootmode anymore, or can't properly reboot, maybe because the relevant parts have been "patched out" to save space). |
02-04-2013, 02:19 PM | #1100 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
The main reason for the existence of this standalone uboot with integrated fastboot is for users who have an erased or corrupted uboot bist in their mmc, so even a stripped down version with no bootmode support still has its place in our collection of debricking tools. Thanks for finding this before I replaced the one in the MfgTool profiles. Now I will add it as a fourth profile instead... |
|
02-04-2013, 02:38 PM | #1101 | |
Enthusiast
Posts: 39
Karma: 10000
Join Date: Feb 2013
Location: Romania, Bucharest
Device: Kindle Touch software Version 5.1.2
|
Quote:
fastboot setvar bootmode diags was published : waitning for device and ai waiteddd.... so much and I disconeted the device.. I should update the kindle unknown driver with this posted? Thx |
|
02-04-2013, 10:45 PM | #1102 | |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
Quote:
Hold power button for reboot after setvar. Or don't set bootmode at all and use diags.bin U-Boot image for booting diags. |
|
02-05-2013, 07:39 AM | #1103 |
Connoisseur
Posts: 99
Karma: 30196
Join Date: Dec 2011
Device: Kindle Touch
|
I'd like to say a huge thanks to ixtab! With the instructions he provided I downgraded my KT to the previous firmware version and updated back smoothly.
(Don't ask why I needed to do that. Short answer is - I wanted to understand all the things to do that to clean up my device from all the mess (unneeded hacks/changes). And..the last but not least: it's all about an experience you get learning the new stuff! ^_^ |
02-07-2013, 05:11 AM | #1104 |
Junior Member
Posts: 5
Karma: 25256
Join Date: Feb 2013
Device: Kindle Touch
|
Kindle Touch bricked with write-protected flash
Hi everybody,
I have a KT which bricked after rechargin from depleted battery. Synptoms are the TREE screen (withouth progress bar) and after a minute followed by blank/black flashing screen to the TREE screen and so on. I can switch between fastboot/diags modes using MfgTool, but fastboot flashing or even erasing has no effect. In fact (by switching to diags mode and activating USB Mass Storage Device) even an erased user partition shows the old data. Even FORMATTING and FILLING USB MSD has no effect, the old data is somehow recovered after rebooting the KT!!! Not mentioning SSH, which returns 'connection refused' (after 30s) even after flashing mmcblk0p2_ssh.img!!! Also, activating the MOVINAND test in DIAGS mode returns FAIL (but maybe it fails even in non-bricked kindles). Any help greately appreciated, thank you |
02-07-2013, 06:49 AM | #1105 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
If you erase the user partition, rebooting REPOPULATES it with default files. Did you expect it to stay empty after reformatting? |
|
02-07-2013, 07:16 AM | #1106 | ||
Junior Member
Posts: 5
Karma: 25256
Join Date: Feb 2013
Device: Kindle Touch
|
Quote:
Code:
dd if=/dev/zero of=/dev/mmcblk0p3 I know about fastboot being something made for android ported to KT, so not everything may work or report an OK while not working (e.g.: flashing a large 128MB main .img). Quote:
I also did a Code:
dd if=/dev/urandom of=/cygdrive/f/randfile Yes I know it sounds very strange, unfortunately these are the symptoms. |
||
02-07-2013, 07:40 AM | #1107 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
More info: Kindle_Touch_Hacking#Partitions. |
|
02-07-2013, 12:23 PM | #1108 | |
Junior Member
Posts: 5
Karma: 25256
Join Date: Feb 2013
Device: Kindle Touch
|
Quote:
Also the 'bootmode' variable is unchaged, but I succeed to get diags via MfgTool: Code:
C:\fastboot>fastboot setvar bootmode diags setting 'bootmode' to 'diags'... bootmode diags: finished. total time: 0.000s C:\fastboot>fastboot getvar bootmode bootmode: main finished. total time: -0.000s |
|
02-08-2013, 05:36 AM | #1109 |
Junior Member
Posts: 5
Karma: 25256
Join Date: Feb 2013
Device: Kindle Touch
|
I think i found someone with my same probleme here at "Kindle Touch: Bricked and readonly filesystem". Unfortunately no solution...
|
02-08-2013, 03:29 PM | #1110 |
Junior Member
Posts: 5
Karma: 25256
Join Date: Feb 2013
Device: Kindle Touch
|
I'm getting crazy: tried the "mount nfs" method like described in this thread, also tried the "D) Disable diagnostics" way used by Duokan: no way...
I should find a way to unprotect the internal moviNand flash somehow (since I think it's something more deep than just a read-only filesystem mount). |
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 |