Broken JB? Not sure where to start.

[Thac0]

Blarg. I've got a PW2 (PW2IL) running 5.4.5.1. I believe it was jailbroken a while ago (pre 5.5) then updated to 5.4.5.1. I had two Paperwhites at the time, it's possible one wasn't jailbroken. I no longer have the second device to check though.

It's was connected to a network for months, and hasn't received an OTA update. I've got it in airplane mode now though, just in case.

I looked at both directions for 5.4 jailbreak thread and the <5.8.8 thread.

Odd thing though, I don't have update.bin.tmp.partial, a jailbreak file in my /documents directory, or a /mrpackages directory.

I'm guessing from what I've read I just need to factory reset my device and then downgrade to 5.4.3.2 (by not ejecting/disconnecting before restarting) and proceed with the 5.4.3.2 jailbreak instructions?

Also, is there anything odd about not getting an OTA? Is there anything worth testing or pulling from my device before I factory reset?

[Cinisajoy]

Your jailbreak should have held.
Reinstall MRPI and all the hacks you had on it.

[knc1]

Originally Posted by Thac0

Blarg. I've got a PW2 (PW2IL) running 5.4.5.1. I believe it was jailbroken a while ago (pre 5.5) then updated to 5.4.5.1. I had two Paperwhites at the time, it's possible one wasn't jailbroken. I no longer have the second device to check though.

It's was connected to a network for months, and hasn't received an OTA update. I've got it in airplane mode now though, just in case.

I looked at both directions for 5.4 jailbreak thread and the <5.8.8 thread.

Odd thing though, I don't have update.bin.tmp.partial, a jailbreak file in my /documents directory, or a /mrpackages directory.

I'm guessing from what I've read I just need to factory reset my device and then downgrade to 5.4.3.2 (by not ejecting/disconnecting before restarting) and proceed with the 5.4.3.2 jailbreak instructions?

Also, is there anything odd about not getting an OTA? Is there anything worth testing or pulling from my device before I factory reset?

Follow the <5.8.8 directions, completely, exactly as written.
They will direct you to another thread at the proper point and remind you to return.

Why not try the "test" package attached to the <5.8.8 post?

It is not unusual for older devices to fail to update OTA - Don't complain, its a feature not a bug.

[Thac0]

Originally Posted by Cinisajoy

Your jailbreak should have held.
Reinstall MRPI and all the hacks you had on it.

Looks like it was this.

Originally Posted by knc1

Why not try the "test" package attached to the <5.8.8 post?

I didn't have a /mrpackages directory, so I figured I'd ask first. I started by making /mrpackages and attempting the ;log mrpi command, but it failed. On Cinisajoy's suggestion I proceeded with installing KUAL and MRPI as if I were jailbroken (I had forgotten KUAL was an app and not an added extension of the OS). The test worked through KUAL.

Seeing how ;log mrpi failed, but KUAL worked, it looks like I'm missing the survival code. The log file shows I've got 3 keys installed, but I'm not seeing anything to help identify which jailbreak I'm running (which I'm guessing would be in the JB file that looks to have been removed at some point).

Originally Posted by knc1

It is not unusual for older devices to fail to update OTA - Don't complain, its a feature not a bug.

In case this wasn't sarcasm, I wasn't complaining. I was interested about the mechanics. I wasn't certain if I may have had a different OTA block method installed, or if I was just lucky. I created the update.bin.tmp.partial directory regardless as a failsafe.

====

So from here, it looks like I've got an unknown version of a jailbreak. To get to a known state and ensure the survival code is installed, should I run through the full downgrade process (as knc1 suggested) or would the bridge update process be enough?

Edit: In case it matters, I plan on updating to 5.8.8 once I get everything in order.

[knc1]

Originally Posted by Thac0

------
So from here, it looks like I've got an unknown version of a jailbreak. To get to a known state and ensure the survival code is installed, should I run through the full downgrade process (as knc1 suggested) or would the bridge update process be enough?

Not possible -
Amazon provides two certificates, we provide one (which is what is called a JB here for historical reasons).
If the report shows that you have three in total, you have ours.

That signature certificate has never been changed.

If you can't install the "hotfix" (the "survival code link") by putting it in the topmost visible level of USB storage, then try installing it with MrPI.
Since we know from the report that you have our signature certificate installed - MrPI can install it.

I was not being sarcastic - it is an unintended "feature" of the Amazon firmware.
And it would be best that we did not publish the details, they would only fix it.

[Thac0]

Originally Posted by knc1

Not possible -
Amazon provides two certificates, we provide one (which is what is called a JB here for historical reasons).
If the report shows that you have three in total, you have ours.

That signature certificate has never been changed.

*nods* My apologies for not being clear. By unknown version, I didn't mean to suggest that there were different keys. But rather that the process used to drop those keys may have had additional steps (such as installing survival code or modifying settings) that may not have been accomplished by whatever version I had run.

Originally Posted by knc1

If you can't install the "hotfix" (the "survival code link") by putting it in the topmost visible level of USB storage, then try installing it with MrPI.
Since we know from the report that you have our signature certificate installed - MrPI can install it.

I tried installing the linked package via MrPI.

Spoiler:

Downloaded Update_jailbreak_hotfix_1.14.N_install.zip
extracted .zip file.
Moved Update_jailbreak_hotfix_1.14.N_install.bin to /mrpackages on Kindle.
KUAL -> Helper -> Install MR Packages

It seemed to go through ok (restarted) but upon testing ;log mrpi didn't seemed to be recognized with the install_test_dummy in /mrpackages.

Did I install it improperly? Or should I be using the update_jailbreak_bridge_1.14.N_install.bin provided on the first post (as opposed to the archive from the "survival code link") since I'm running >5.4.4.2 but <5.6.1

Originally Posted by knc1

I was not being sarcastic - it is an unintended "feature" of the Amazon firmware.
And it would be best that we did not publish the details, they would only fix it.

*nods* Fair enough. I understand the cat/mouse game that's played.

[knc1]

The device is jail broken.
And since KUAL is working, its requirements are also installed.

Get the "Hotfix" package from the attachment on this post:
https://www.mobileread.com/forums/sh...postcount=1597

Put it in /mrpackages and use KUAL to trigger MrPI.
It will do no harm to install it again, if it is already installed.

That should be all you have to do, as in, your done.
(Other than install whatever add-ins you want to use.)

[Thac0]

Originally Posted by knc1

The device is jail broken.
And since KUAL is working, its requirements are also installed.

Get the "Hotfix" package from the attachment on this post:
https://www.mobileread.com/forums/sh...postcount=1597

Put it in /mrpackages and use KUAL to trigger MrPI.
It will do no harm to install it again, if it is already installed.

That should be all you have to do, as in, your done.
(Other than install whatever add-ins you want to use.)

I did exactly this (and did it again to be sure). After the update, I'm still unable to trigger the ;log mrpi command from the main search bar.

[knc1]

Originally Posted by Thac0

I did exactly this (and did it again to be sure). After the update, I'm still unable to trigger the ;log mrpi command from the main search bar.

Then use KUAL to trigger it.
I don't recall if we tested on that old a firmware version.
It was created to help deal with some problems on 5.8.++
But if you ever update to something recent ...
Then it will probably work from the search bar.
(I wouldn't go more recent than a 5.7.something)

[Thac0]

Oh ok. So I'm good to update then ^-^.

Is there a post that outlines the different firmware versions? I was looking for something that would let me know what improvements were made and what the community would suggest to update to, but I didn't see anything.

Why would you suggest 5.7.x over 5.8.x?

[Cinisajoy]

Originally Posted by Thac0

Oh ok. So I'm good to update then ^-^.

Is there a post that outlines the different firmware versions? I was looking for something that would let me know what improvements were made and what the community would suggest to update to, but I didn't see anything.

Why would you suggest 5.7.x over 5.8.x?

Because 5.8 has unwanted stuff.
Cat/mouse.

[knc1]

Originally Posted by Thac0

Oh ok. So I'm good to update then ^-^.

Is there a post that outlines the different firmware versions? I was looking for something that would let me know what improvements were made and what the community would suggest to update to, but I didn't see anything.

Why would you suggest 5.7.x over 5.8.x?

Typo.
No more recent than 5.8.7 - because you can't JB 5.8.8