Kubrick: Live CD to debrick Kindle 3, 4, and Touch

[xs400]

Originally Posted by knc1

No.
The updates for series 3 firmware are partial, incremental, updates.
You can only go forward, not backward with the Amazon packages.

Check the "Where do I start" sticky thread, follow through to the information on de-bricking, and from there to the K3 recovery images hosted off-site.
(Or just use Kubrick)

Either way will install a very early version of the firmware for you, then you can use the Amazon packages (in the Amazon prescribed order) to advance to the desired version.

Finding prior to current firmware packages - see the FGA thread.

OK, I'm back!
Downgrading seems very complicated.

I was hoping to replace the K3w 3.4 firmware in Kubrick, with the v3.0.2 firmware in the Kubrick CD, but I did not find any guides on how to do this and after unpacking the (3.0.2)mmcblk0p1.zip and Kubrick.iso, I was unable to figure out how to replace the 3.4 firmware files with 3.0.2 firmware files.

I tried reflashing v3.4 using Kubrick, but this time it did not complete the flash (stuck at 0%), it did finish the kernel flash (or so it seems). Luckily, for me the Kindle still works (sort of).

In any case, I (re)installed the jailbreak and a few other hacks. Everything seemed fine till I loaded a few books and before I could install the 'Disable indexing' hack, the screensaver came on and all hell broke loose!

I got "collecting information" and the Kindle tried to reboot and got stuck with the progressbar at approximately 10%. It was off the charger, but I saw the green LED blink a few times. I connected the charger left it connected overnight. This morning I saw it attempt to reboot, but the screen is white and the charging light is orange.

Now, I'm quite sure all this is due to some bug or some corrupt book. I wish I could downgrade to 3.2.1 (seemed like everything was fine with 3.2.1).

@knc1 - any way I could replace the firmware files in the Kubrick CD? TIA.

[aikau]

Originally Posted by DarthSmeg

Edit: Rebooted by holding the power-button for a loooong time, and connected it to a mains-charger. An lo and behold! The Diags menu appeared! Great! One step closer

I am trying kubrick 3.6 and following instructions, it all goes fine (usb id change during stages, checked in alt-f2 screen via lsusb) till "diag mode" which I cannot get - when the cd tool says I should see it, the device boots to normal OS. So I want you to be as precise as you can :-) What was the device running when you started holding the power button, how long is "loooong time"? Thanks!

The actual problem I am trying to solve here is put it into the state when it can upgrade itself. Right now it is running 4.1.2 and it fails to upgrade to 4.1.3 at the very end with U006, even when I put a firmware image to it and start update manually, i.e. no wifi involved. It was not jailbrake.

[xs400]

Originally Posted by aikau

I am trying kubrick 3.6 and following instructions, it all goes fine (usb id change during stages, checked in alt-f2 screen via lsusb) till "diag mode" which I cannot get - when the cd tool says I should see it, the device boots to normal OS. So I want you to be as precise as you can :-) What was the device running when you started holding the power button, how long is "loooong time"? Thanks!

The actual problem I am trying to solve here is put it into the state when it can upgrade itself. Right now it is running 4.1.2 and it fails to upgrade to 4.1.3 at the very end with U006, even when I put a firmware image to it and start update manually, i.e. no wifi involved. It was not jailbrake.

Seems like detecting the state is very quirky. You could try the following:

1. Disable in BIOS all other boot devices, so it will not boot the hard drive
2. If possible try USB 1.1 mode
3. Try another computer/laptop (sometimes some USB ports are by default in USB 2 and others may be USB 3 - the situation is especially strange when not booted into Windows or a regular Linux)

I tried about 3 different laptops and Kubrick worked only on one.

[knc1]

Originally Posted by aikau

- - - - -
Right now it is running 4.1.2 and it fails to upgrade to 4.1.3
- - - - -

Why do you want that update?
There have been document reading problems reported here on 4.1.3

The U006 error code is a general purpose error code with no specific meaning beyond 'error'.

Since you have not Jail Broken the device, the only thing that could have changed the part of the system tree a K4 update is touching, is hardware failure.

You might be much better off to just leave it alone now.

[aikau]

Originally Posted by knc1

Why do you want that update?

I do not really want the update but once it downloads a book from amazon, it also detects an update available and tries updating itself, and it never finishes so it is quite hard to use kindle. And I cannot see how to disable these updates, is there a way? Not using wifi is not an option...

[aikau]

Originally Posted by xs400

I tried about 3 different laptops and Kubrick worked only on one.

My laptop is Thinkpad W530. It does boot from dvd just fine and "lsusb" in the booted system tells that kindle is detected correctly at first two stages so I do not think the laptop is the issue here, tried both USB2.0 and USB3.0 ports, works, the USB cable seems to matter though. Which laptop of yours did work eventually?

This is what it looks like in "fastboot" mode (hold "power" button, press "down", release "power", release "down"):
Bus 004 Device 015: ID 15a2:0052 Freescale Semiconductor, Inc. i.MX50 SystemOnChip in RecoveryMode

Is this a fastboot already? "fastboot devices" sees nothing :-/ Should it be kindle's fastboot or the one for android is ok? Fedora 22, fastboot is from its repository and works fine on android devices.

[knc1]

Originally Posted by aikau

I do not really want the update but once it downloads a book from amazon, it also detects an update available and tries updating itself, and it never finishes so it is quite hard to use kindle. And I cannot see how to disable these updates, is there a way? Not using wifi is not an option...

Install backdoor lock after removing any update file on the root of the device.

[aikau]

Originally Posted by knc1

Install backdoor lock after removing any update file on the root of the device.

Do not I need a working diag mode for installing backdoor lock? After some reading I got an impression I need to jailbreak my kindle and this needs that diag mode which I cannot switch into on my device.

[knc1]

Originally Posted by aikau

Do not I need a working diag mode for installing backdoor lock? After some reading I got an impression I need to jailbreak my kindle and this needs that diag mode which I cannot switch into on my device.

Ah, come on now, give me a break.
Reading where? Please give link.

= = = = =

Get yourself a copy, read its directions, try it.
It should 'just work'.
https://www.mobileread.com/forums/sho...d.php?t=225030

That is: the installation of the JB switches to diag mode for you at the proper time.
If it doesn't, post in the K4 jail break thread and we will help you fix it.
(Kubrick does not install a 'diags' image.)
There is a link to the K4 JB thread at the page I linked to above.

[aikau]

Originally Posted by knc1

Ah, come on now, give me a break.
Reading where? Please give link.

This - https://wiki.mobileread.com/wiki/Kindle4NTHacking - says the device should boot into a diag mode.

Originally Posted by knc1

(Kubrick does not install a 'diags' image.)

Ah, I confused diag mode with usb downloader mode. I cannot get either anyway.

Originally Posted by knc1

There is a link to the K4 JB thread at the page I linked to above.

Thanks, let's try there...

[stikonas]

I have Kindle 3 stuck in a boot loop (gets stuck at about 25% of progress bar). Tried to use Kubrick and it finishes in an hour or so. However, that doesn't seem to change anything. It is still stuck in a boot loop.

Any ideas what else I can try (I've already tried factory reset).

[xs400]

Originally Posted by stikonas

I have Kindle 3 stuck in a boot loop (gets stuck at about 25% of progress bar). Tried to use Kubrick and it finishes in an hour or so. However, that doesn't seem to change anything. It is still stuck in a boot loop.

Any ideas what else I can try (I've already tried factory reset).

I have the same problem. I tried using another source of power (Nokia battery), but the Kindle3 doesn't seem to like that. I've ordered another K3 battery from China - still waiting for it to arrive. Will post an update after I put in the new battery.

[knc1]

@stikonas:
@xs400:

Clear the /var/local directory tree.
There is a selection for doing that in Kubrick.

[stikonas]

Originally Posted by knc1

@stikonas:
@xs400:

Clear the /var/local directory tree.
There is a selection for doing that in Kubrick.

Sorry, I can't see option for clearing /var/local for K3 in Kubrick at all. It just flashes kernel and then the whole rootfs.

I've also mounted that squashfs image in livecd to see what is inside. /etc/fstab file in K3 does not have any separate partition for /var or /var/log so if I understand correctly, flashing rootfs (which Kubrick already did) should automatically clear /var/local directory tree. Also, shouldn't factory reset have cleared that too. So I'm confused...

[knc1]

My bad, I lost track that you are working on with a K3 -
If it only spent an hour transferring the image, then it did not transfer the full image.

Currently, we only have a one person help desk operation here (me).
There is a lot to keep track of (lots of Kindle models) and I do make mistakes.