Kindle 3.1 software for Kindle 2, 2i, & DX (under construction)

[ctlw83]

Hi all,

I have a Kindle 2 with the B002 serial number. A long, long time ago I used one of the hacks to upgrade to 3.2.1 . I definitely do not have the update_restore-os.bin to restore back to stock and had just tried to use the TTS yesterday, only to discover that the volume controls do not work, probably due to the nature of how the hack worked, combining the 2 and 3 firmwares.

Are there any ideas on how I can either correct this or upgrade to a newer firmware that will resolve this?

I've done some poking around here on the forums but, maybe I haven't been using the right search terms.

[hawhill]

I don't think there's an easy path to a newer version - and no guarantee that it would bring volume control (btw., why should it? Amazon didn't start supporting K2 even in more recent K3 firmware versions).

You would have to downgrade (needing the restore image), then upgrade again to a newer K3 version. Which you would have to find or create in the first place.

As for correcting the issue - maybe you can script Launchpad to provide an alternative volume control?

[ctlw83]

Hmmm

Maybe the best bet will be to downgrade back to 2.5.8 then. However, being that I don't have the backup file for my K2, having done the upgrade years ago, I'm kind of stuck there.

I've actually tried to run some kind of custom ereader installer on it in the past as well but, the hybrid versions didn't allow it to work. Which makes sense because developers are not going to assume that a K2 would be running K3 firmware.

[ctlw83]

If anyone has tips/experience/tools that they can share to assist me with the downgrade, please PM me. I don't think there is any way to resolve the volume issue minus the downgrade.

[knc1]

One question before you start - -
Did the volume buttons ever work on this device?

- - - - - -

I have notice in my (very small) collection of K2 devices that the volume buttons are first to break - mechanically.

[ctlw83]

Originally Posted by knc1

One question before you start - -
Did the volume buttons ever work on this device?

- - - - - -

I have notice in my (very small) collection of K2 devices that the volume buttons are first to break - mechanically.

I knew that question was coming and I can honestly say that I don't know. I might have tested the TTS at some point but, I cannot definitively answer yes or no. I want to lean toward yes but, that would be pure guesswork and speculation.

It would be interesting to hear from some others running the version 3 firmware if the buttons work for them. However, it would make perfect sense that due to the different positioning of the buttons between Kindle 2 and Kindle 3, the firmware might not be able to handle it.

I would also like to ask, what would people suggest doing with my Kindle 2 if I can successfully downgrade in terms of hacks/tweaks that aren't related to upgrading firmware?

[knc1]

Originally Posted by ctlw83

I would also like to ask, what would people suggest doing with my Kindle 2 if I can successfully downgrade in terms of hacks/tweaks that aren't related to upgrading firmware?

KUAL was intended to work on the K2 -
But there are very few active users of the K2 these days, so you might have to do some experimenting.

Anything listed for the DX or DXG that does not depend on the screen size should also work on the K2 (the DX(G) are just large screen K2 devices).

- - - - - -

It is probably not the physical button locations -

but if they where definitively working before the shift to 3.x firmware, then it could be only that the firmware's representation of the buttons changed (and would have to be adapted in the Frankenstein firmware).

[ctlw83]

True, but the question in that case is if I am willing to learn enough to play with the firmware and find the necessary file to tweak.

I mean, I'm sure I could figure it out but, not sure if I'd want to invest the time...

[knc1]

Which version of the kindle updater did you use?
(Maybe you posted a thank-you in this thread when you did it - list your own posts and see where it occurred in the context of the development.)

Reason: The first post change log says that a problem with TTS (I.E: Audio) had been fixed in the more recent versions.

Perhaps all you need to do is update to the most recent version 1.0 Frankenstein firmware.

When you follow the download link in the O.P. you will also find a link to the sources (which might tell you if the button names/keywords where changed or needed to be changed and also read the comments on that release page).

[ctlw83]

I wasn't on the forums when I had used the frankenfirmware. It was so long ago that I would have no idea which version I used.

How easy would it be to update to the newer version if I am not in the original 2.5.8 firmware? What would the process be?

Would I simply run the software on a 3.x.x kindle to output new files or would something else need to be done?

[knc1]

I have no idea, but someone else here may be able to help (or maybe it is in the package's readme.txt file).

[ctlw83]

I'll give it a try, I mean, in theory the Kindle 2 has already been "prepped" for the upgrade before. So, even if I don't have the necessary backup file to downgrade, I may be able to "re-upgrade" using the newer package.

It's just a theory though.

I did try to run the prep package on the Kindle 2 but, it wouldn't take.

Update:

No luck. My wife's kindle was jailbroken back when I originally did the hack. However, she is running 3.4 and it won't run the update file to generate/copy the filesystem. So, that isn't going to work. Drat!

Further update: I was able to undo the old jailbreak on my Kindle using the standard kindle jailbreak uninstall and then was able to re-apply the latest version. The U007 showed up but, that is normal per the jailbreak. However, I don't see any etc folder or anything. My guess is it still worked but, of course, none of this fixes my issue...

[knc1]

I was just guessing and maybe we learned something by the fact that nothing changed about the problem.
- - - -
Out of ideas here, maybe re-installing the original 2.5.8 will be the only answer.

[ctlw83]

Originally Posted by knc1

I was just guessing and maybe we learned something by the fact that nothing changed about the problem.
- - - -
Out of ideas here, maybe re-installing the original 2.5.8 will be the only answer.

Which brings us back to the original issue of not being able to do that because I don't have the original recovery file.

[knc1]

Originally Posted by ctlw83

Which brings us back to the original issue of not being able to do that because I don't have the original recovery file.

Correct, I was trying to find a work-around to the original issue and failed.

Perhaps you will get lucky and some reader can PM you a link to the file image you need (which can't be posted here, since it contains copyrighted materials).