These two packages should be able to be used if you have hit the dreaded "reset" button - however I have only tested this on firmware 5.8.9.2. the "Reset" button on that firmware does not remove the jailbreak itself, however it does remove this hotfix. You can use these packages to reinstall that hotfix ( the package currently listed int eh jailbreak thred will also work up to firmware version 5.8.2, this one takes to 5.8.10 and one with theoretically no limit.

Nice choice of name for your collection of special purpose packages.
Use the report "!" button on your own post to send a message to the moderators to get this thread added to the sticky "jailbreak index".
(Our own moderators are gone.)

= = = =

Do I understand this correctly?
Put this package at the top of visible USB storage and use the UYK function to install it?
It depends on only having the device "jail break" - that is, our signature certificate be installed (as in after a "Reset" operation).

Nice choice of name for your collection of special purpose packages.
Use the report "!" button on your own post to send a message to the moderators to get this thread added to the sticky "jailbreak index".
(Our own moderators are gone.)

= = = =

Do I understand this correctly?
Put this package at the top of visible USB storage and use the UYK function to install it?
It depends on only having the device "jail break" - that is, our signature certificate be installed (as in after a "Reset" operation).

Is it too early to describe this in the current jailbreak thread?

The payload of this file is the same as the hotfix step in the current jailbreak thread. The only difference is the header that has the new hardware versions, and the target OTA. I would prefer not to recommend people use this one, if the existing one works for them, but only come to this if they need it for now.

This may change once I can get the other hardware versions and updated "target" into kindletool.

Here is a hotfix build that shoudl work on all currently known touch models, and any software version. As long as the device has been jailbroken.

This is a version of the Hotfix for touch devices that will run on normal software versions ( not just the factory ). I have verified on my PW3 that the jailbreak itself remains through the rest process, but I needed this package to re-install the hotfix.

Here is a hotfix build that shoudl work on all currently known touch models, up to software version 5.8.10. As long as the device has been jailbroken.

This is a version of the Hotfix for touch devices that will run on normal software versions ( not just the factory ). I have verified on my PW3 that the jailbreak itself remains through the rest process, but I needed this package to re-install the hotfix.

Hmm...
A 'model locked' package locked to only work on all possible models.
Tricky.

It was nice of Amazon/Lab126 to unify firmware builds across all touch screen devices.
We can (you just did) do the same for our add-ins. (I don't think Amazon/Lab126 intended to simplify our support efforts.)

I suppose at some later time, we can re-package all of the "essentials" in NiLuJe's snapshots.
They only need to be re-wrapped, none of them have "bit rotted" (yet).

But I guess I need to put recovering a 'factory firmware' for the PW3-32G a little higher on my to do list.
(I am still "wasting" my free time repairing the damage done to my car in an accident last February.)

Hmm...
A 'model locked' package locked to only work on all possible models.
Tricky.

It was nice of Amazon/Lab126 to unify firmware builds across all touch screen devices.
We can (you just did) do the same for our add-ins. (I don't think Amazon/Lab126 intended to simplify our support efforts.)

I suppose at some later time, we can re-package all of the "essentials" in NiLuJe's snapshots.
They only need to be re-wrapped, none of them have "bit rotted" (yet).

But I guess I need to put recovering a 'factory firmware' for the PW3-32G a little higher on my to do list.
(I am still "wasting" my free time repairing the damage done to my car in an accident last February.)

My idea for the pw32Gb has a problem, I get an error "tar format error", so my repackaging didnt work right. I am still going to work on it, I think it was just form using 7-zip on windows to re-tar the files I needed.

My idea for the pw32Gb has a problem, I get an error "tar format error", so my repackaging didnt work right. I am still going to work on it, I think it was just form using 7-zip on windows to re-tar the files I needed.

If you need different versions or 64bit versions for your Windows, a little bit of web searching should turn them up.
The above are old, 32bit versions.

Thanks, I have those, I was just trying to drag and drop into 7zip for easy moving.

I actually just finished installing the Windows 10 Linux subsystem, because I couldn't figure out how to get libraries installed for MinGW kindletool. OS I thought I would just use this new Windows 10 Linux system, and make linux binaries of it.

I re-packaged my update_PW3_5.7.4_with_5.8.2_uboot.bin using linux tar, and it looks like it is working.

I forgot to connect my serial port for logs, but it is in progress right now.

It appears to have installed correctly - operation frankenupdate is a go - now I need to find a guinea pi- sacrif- victi- volunteer, that's the word.

- - - -
I re-packaged my update_PW3_5.7.4_with_5.8.2_uboot.bin using linux tar, and it looks like it is working.
- - - -

Isn't 5.7.4 too old to run a PW3-32?
Or have I lost track of what you are doing?

- - - -

Is the MS-Unix sub-system complete enough to let you mount the rootfs.img file?

If not, do you have VirtualBox for your Win10 system?
If so, I can figure out how to do that with one of my prototype development VM images.
I already have them setup to access the host's filesystem from inside of the VM image, so just 'reaching' out for the un-packed files is possible, I just haven't tried the 'mount' command inside of the VM.

Isn't 5.7.4 too old to run a PW3-32?
Or have I lost track of what you are doing?

The 5.7.4 kernel and uboot are too old to run on the pw3-32 for sure.

I want to test if the 5.7.4 user land is compliant enough to let someone install the jailbreak, then the hotfix, then update to a real version. So I'm testing if playing around with this will break my kindle right now.

If the factory package style package lets us do this, We might as well take advantage of it in the few months before the next factory cycle probably eliminates the option completely.

At the moment, I can't think of why a virtual system can't have more than one user.
So why not do the Kindle hacking collaboration on Amazon's dime system?

Note: I posted the 'public' descriptor link above - but I am accessing the 'same' offer via suseStudio (which is also free). That is a partnership deal between Amazon and Suse that would let me deploy what I build on an EC2 instance.
(1 core, 1G ram, 750 cpu hours / month, ... more)
I have always wanted to use Amazon's (free) S3 distribution system to distribute Kindle jail breaks.

Isn't 5.7.4 too old to run a PW3-32?
Or have I lost track of what you are doing?

- - - -

Is the MS-Unix sub-system complete enough to let you mount the rootfs.img file?

If not, do you have VirtualBox for your Win10 system?
If so, I can figure out how to do that with one of my prototype development VM images.
I already have them setup to access the host's filesystem from inside of the VM image, so just 'reaching' out for the un-packed files is possible, I just haven't tried the 'mount' command inside of the VM.

No, the windows system does not have the "loop" system implemented, so you cannot mount image files in linux. I do have a Ubuntu VMware that I pop into if I need things like this though.