Mobileread
Original "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard
#11  geekmaster 03-03-2012, 08:16 PM
Quote hawhill
@geekmaster: Nice. I think a short note on unmounting should be added. Otherwise, some repair tries might fail - depending on how the device is being restarted. Another thing would be a short information that in the case of dd'ing a backup image no mounting is needed (and might even be harmful).
Agreed. I am trying to keep the amount of typing to an absolute minimum here, for people intimidated by the shell scripts and the linux command line. I recommend a proper shutdown rather than a hard reset whenever possible, so the system has an opportunity to unmount the disks cleanly.

I do not know if it would be better to tell people to always unmount the disk, or just unmount it before doing a hard reset. The problem is that if you document all the corner cases, it begins to look like the posts that this simplified version was meant to replace.

EDIT: Rather than specifically saying to unmount it, I changed the order of restoring, and mount and repair, to eliminate that confusion.
Reply 

#12  Poetcop 03-03-2012, 09:12 PM
Quote geekmaster
You should be able to recover from that "black death" by using MfgTool to get to fastboot mode, then using fastboot to flash mmcblk0p2_ssh.img to the diags partition, then booting diags and exporting the USB drive to copy mmcblk0p1 on it, then starting an SSH shell and using dd to copy the /mnt/us/mmcblk0p1.img to /dev/mmcblk0p1, then finally by running the factory_restore script.
Great stuff, even more concise! Now I know that my priority should definitely be getting the fastboot tool talking to my Kindle in fastboot mode. (currently can't do it because of that problem with it dropping out when unplugged)
Reply 

#13  geekmaster 03-03-2012, 10:57 PM
Quote Poetcop
Great stuff, even more concise! Now I know that my priority should definitely be getting the fastboot tool talking to my Kindle in fastboot mode. (currently can't do it because of that problem with it dropping out when unplugged)
UPDATE: There is now a fastboot tool for windows, so you can set fastboot mode from MfgTool and then run fastboot from windows, with no risk of fastboot mode dropping out. You can download it here:
http://www.mobileread.com/forums/sho....php?p=2001683

I am glad you like it. I added a "generic" verision of it as a "summary" to the top of the first post in this thread.

Regarding dropping out when unplugged, mine does that too. So it would seem that it should not be unplugged then. dasmoover had that problem when moving his kindle between his windows and his linux computers. I do not remember how that was solved, but the complete IRC conversation was placed into a post if you wish to read it to see how he solved that problem. I will go look for it now...

EDIT: Found it. Post #87. Some of my threads are getting rather large. Read this:
http://www.mobileread.com/forums/sho....php?p=1981772

Reply 

#14  Poetcop 03-04-2012, 09:27 AM
That's good reading! But it looks like the solution the two of you came up with was to boot into fastboot from diags mode, and diags mode isn't working for me. So I think I will try getting linux running in a virtual machine to run the fastboot tool, unless someone can get the PC fastboot tool working.

I wonder if things would change if I could charge it all the way. It only seems to want to charge when it's in "plug-me-in" mode - no matter what state it's in with a black screen, and whether wall-charger or computer charging, it always seems close to running out of batteries. Of course this would be easier to investigate if I had a way of querying the battery state - very hard to infer from the limited information given by its behaviour.
Reply 

#15  knc1 03-04-2012, 11:15 AM
Quote Poetcop
That's good reading! But it looks like the solution the two of you came up with was to boot into fastboot from diags mode, and diags mode isn't working for me. So I think I will try getting linux running in a virtual machine to run the fastboot tool, unless someone can get the PC fastboot tool working.

I wonder if things would change if I could charge it all the way. It only seems to want to charge when it's in "plug-me-in" mode - no matter what state it's in with a black screen, and whether wall-charger or computer charging, it always seems close to running out of batteries. Of course this would be easier to investigate if I had a way of querying the battery state - very hard to infer from the limited information given by its behaviour.
The few compile command lines I have seen scattered around the site showed the reference of MaxOSx USB libraries.
Not gonna work on Linux like that, would need the corresponding Linux USB libraries instead.

In advance of the question: No, I don't know which libraries. I have not (yet) tried to build it myself.
Reply 

#16  geekmaster 03-04-2012, 02:35 PM
Quote Poetcop
That's good reading! But it looks like the solution the two of you came up with was to boot into fastboot from diags mode, and diags mode isn't working for me. So I think I will try getting linux running in a virtual machine to run the fastboot tool, unless someone can get the PC fastboot tool working.

I wonder if things would change if I could charge it all the way. It only seems to want to charge when it's in "plug-me-in" mode - no matter what state it's in with a black screen, and whether wall-charger or computer charging, it always seems close to running out of batteries. Of course this would be easier to investigate if I had a way of querying the battery state - very hard to infer from the limited information given by its behaviour.
I compiled fastboot for linux, and that is what I use. I use MfgTool in WinXP in a VM, then use fastboot in the linux host PC (outside the VM). That way the kindle does not get unplugged. It should work fine the other way around too, with linux in the VM and windows on the outside.

I first charge a dead kindle on a wall charger for several hours, then use MfgTool to boot to fastboot mode, and charge it for several more hours, before attempting to flash the diags partition or boot to diags mode.

Fastboot mode contains good battery recharging code. The battery will drain while bricked or while in diags mode. It does not go into sleep mode in those cases, until the battery is discharged. You do not even get a "your kindle needs recharging" until you charge it enough so it CAN boot far enough from the main system partition to detect that it has a low battery.

Just leave it in fastboot mode while bricked, when not using it, and plugged into a wall charger. After debricking, you can rely on main bootmode to do the screensaver sleep thing...
Reply 

#17  muydificil 03-04-2012, 03:06 PM
Hi,

As I had a kindle touch working, I used mfgtool on it in order to boot in diagnostics mode so I could check and compare with the bricked one I already had.

The thing is that the working one no longer works, and seems to be bricked also.

The steps I follow were:

-Start the kindle in recovery mode
-load diagnostics with Mfg tool
-from diagnostics menu start fastboot mode
-check the kindle with yifan lu fastboot only with reading commands. No flashing at all. only "fastbool getvar <varname>" and "fastboot check <partition>"
-disconnect usb

at this point the kindle didn't reboot in normal mode, so I started it up in recovery mode again and with the mfgtool started the kindle with the "kindle main" profile option.

and that's all, never came back to life again,

Is it possible that I could brick a working kindle touch only with the mfgtool program? 'cos it's the only program that has written into the device.
Reply 

#18  geekmaster 03-04-2012, 03:21 PM
Quote muydificil
Hi,

As I had a kindle touch working, I used mfgtool on it in order to boot in diagnostics mode so I could check and compare with the bricked one I already had.

The thing is that the working one no longer works, and seems to be bricked also.

The steps I follow were:

-Start the kindle in recovery mode
-load diagnostics with Mfg tool
-from diagnostics menu start fastboot mode
-check the kindle with yifan lu fastboot only with reading commands. No flashing at all. only "fastbool getvar <varname>" and "fastboot check <partition>"
-disconnect usb

at this point the kindle didn't reboot in normal mode, so I started it up in recovery mode again and with the mfgtool started the kindle with the "kindle main" profile option.

and that's all, never came back to life again,

Is it possible that I could brick a working kindle touch only with the mfgtool program? 'cos it's the only program that has written into the device.
The profiles I provided with MfgTool do not change anything (not even the idme bootmode var). They just select in memory only what mode to boot, then continue the boot process.

The fastboot tool has some known problems, but it should not change anything on mmc (permanent storage) in your kindle unless you do a setvar instead of a getvar, or an erase, or a flash.

It is normal for the fastboot "check" functions to fail, because they check the ORIGINAL flash header CRC32, and partition contents CHANGE when you access the filesystem in them, which makes the partition flash header CRC32 no longer valid.

Beware that fastboot is not able to flash the mmcblk0p1 (main system) partition, which is too large (even when it falsely reports "success"). It can flash mmcblk0p2 (diags), and there is an image available with SSH preinstalled.

You can boot to fastboot to flash the SSH version of diags, then boot to diags to export the USB drive so you can copy stuff from it and write stuff to it, and you can start SSH so you can change stuff inside you kindle from the linux command line (such as writing a backup image file stored on the USB drive to /dev/mmcblk0p1, or copying /dev/zero to /dev/mmcblk0p3 to file a full or damaged /var/local partition (but that will also erase your collections database and user settings such as locale and timezone).

You did not describe doing anything that could damage a working kindle, other than putting it in a mode where the battery cannot charge effectively.

I suggest charging the battery as described in other posts (wall charger, then charge in fastboot mode until fully charged).

A kindle should normally be kept in "normal" main mode, where it will automatically go to screensaver power-save mode. A bricked kindle should be kept in fastboot mode, connected to a wall charger.

At least that is MY opinion (based on information gathered from the posts of others, and from my own personal experience).
Reply 

#19  geekmaster 03-04-2012, 05:35 PM
UPDATE: Added "Successful Debricking Reports" to first post in this thread. I forgot that I helped so many people...

There are enough people in that list to have a "Kindle Brick-Owner's Club" party...

http://www.mobileread.com/forums/sho...d.php?t=170929
Reply 

#20  muydificil 03-04-2012, 06:43 PM
First of all, thanks for your patience as I'm new with all this.

As I told you a have two kindle touch with me, one that was previously working and the other one previously bricked.

I've followed all the steps for debricking my 2nd kindle touch (the previously bricked one), as following.

1.- getting the partition 2 into the kindle with fastboot from yifan lu
2.- restart kindle in main mode
3.- place a copy of the mmcblk0p1.img on the kindle usb disk unit

I guess that up to here it worked fine because I could do the following:

4.- restart in diagnostic mode, and start usbnet service
5.- connect via ssh (user: root pass:mario) ( I used putty.exe in windows)
6.- dd the previous img file into /dev/mmcblk0p1
7.- reboot in main mode
8.- unplug the usb

ok, the thing is that the kindle touch shows on the screen the picture of the guy reading under a tree and it won't start, no matter how do I press the start button, 5sec, 20 sec or whatever.

the funny thing (actually I dont think it's that funny ) is that the other kindle that stopped working (the one of the previous post that I had done nothing weird on it) is in the same screen (tree) and acts exactly the same on the start button pressing. By the way I have that one charging as you told me.

am I missing something here? Is there a way for the kindle touch to return to the side of the living ones from this point?

diagnostics mode shows an 87% of battery charged, but I don't know if I can trust this anymore.

thanks a lot in advance



EDIT: Ok I've realized that I started in the wrong way after using the mfgtool to start with "kindle main" profile, here's what I got wrong,

inmediatly after using mfgtool in "Kindle main" profile for the final restart, the kindle must be unplugged from the usb and to start, only press the turn on buttont briefly, like half a second or so. I tried to reebot the kindle with the turn on button for five seconds and it got stucked in the logo screen.

The bricked kindle gets to the "needs repair" screen, and I don't know what else to do.
Reply 

 « First  « Prev Next »  Last »  (2/139)
Today's Posts | Search this Thread | Login | Register