Tools Software Jailbreak for PW2, PW3, PW3W, KT2, KV, KOA and KT3

[coplate]

Hey, do we still think there is a reliable way to block OTA updates on version 5.8.5.0.2 ( PW 3 )?

If not, do we think it still works in 5.8.1?

I think I can still downgrade to factory 5.7.4, and then re-upgrade to 5.8.1 if I need to.

If not any of the above, does anyone think they know of a way to block OTA updates - I read that the making directory method doesn't work anymore on 5.8.5. Does that still work on 5.8.1?

[knc1]

You read it on the Internet?

- - - -

Your only reliable way is to:
Keep in airplane mode.
or
Firewall the device from connecting to any part of the Amazon network.

Your best chance if not doing either of the above, is follow the directions in the currently maintained jail break (see step #7).

If there are any exceptions known, they will be included there.

Just because an specific exception is not included, does not mean that it does not exist, just that it hasn't been reported where/when I can see it.

- - - -

You can also "dump messages" and search the 'system' document for messages about having posted an update event to the todo list or about attempts to do an update.

- - - -

What is it that you are trying to achieve by keeping the device on old firmware versions?
Perhaps there is an alternate way to achieve your goal(s).

[Antinoos]

Well, I've jailbroken my PW3 after first having upgraded to 5.8.3 (if remembered correctly). That time I used it very often connected to the internet and used the OTA blocking directory method successfully: Up to and including 5.8.5 I've always done offline updates when read in this forum before, that jb really survives with upgrading to that version.

Some time later, after a restart, I ended up with an auto-update to the the then new 5.8.6. Downloaded automagically despite of the blocking dir! Okay, jb survived that time. What a stroke of luck... and from now on I switched Wifi off completely just to make sure...

Gesendet von meinem Google Pixel mit Yabba-Dabba-Talk.

[coplate]

Originally Posted by knc1

What is it that you are trying to achieve by keeping the device on old firmware versions?
Perhaps there is an alternate way to achieve your goal(s).

It's mostly the general fear that there will be an update that will remove the jailbreak glue.

Considering 5.8.9 blocks the ability to downgrade to those factory images, and the update process now handles the directory trick, it seems like a reasonable precaution.

[knc1]

Originally Posted by coplate

It's mostly the general fear that there will be an update that will remove the jailbreak glue.

Considering 5.8.9 blocks the ability to downgrade to those factory images, and the update process now handles the directory trick, it seems like a reasonable precaution.

None of the firmware versions has ever damaged the jailbreak code bridging an OTA update.
None have even tried.

In the USA, it would be a crime for them to do so, since the bridging code lives in a part of the file system that belongs to the device owner.

The attempts to deal with a directory name are not consistent enough to say that all versions of the OTA process handles the directory trick.
Some do make the attempt and the recent versions that try, fail in a very visible to the user way (with a popup panel that says so).

Since there are a few scattered reports that it does not work on some builds of 5.8.5, then you should probably not be running that version and depending on the blocking directory.
But those reports are few and scattered, most likely because we have never collected the build ID along with the version.

[I.hate.reading]

is there any chance that a kindle PW3 with 5.8.8 can be downgraded in the future???

[Antinoos]

Another Point:

I can't confirm the following statement in posting #1 step 8:

• KOA and KT3 owners:

You must use the update_*.bin format package of KUAL and you must use the MrPi installer to install it.

• Other devices:

The archive still contains the previous 'document' style of KUAL, used by just placing the (correct) KUAL document into the /documents folder of USB storage.

As for my KT3 (included that of a friend of mine) this is not (longer) true generally any more (at least since "basic version" 5.8.3 or so). I could jailbreak these devices and treat them like "other devices" in the list, i.e. simply use the "document style" KUAL-KDK-2.0.azw2 file in the document folder without even starting MRPI for this reason. It starts without any problems. The same ist true, btw, for the Vlasovsoft tools etc., they also may be launched alternatively via their respective *.azw2 document.

But of course you may also use the MRPI method. This has a big advantage: You not only have all your hacks in one neat interface - but you can additionally rename the *.kual "document" (empty file, any name possible, just the extension ".kual" matters) to whatever you like. In my case I used "(1) KUAL (Kindle Unified App Launcher).kual" that brings this on top of the alphabetically sorted document list.

HTH.

[Antinoos]

Originally Posted by I.hate.reading

is there any chance that a kindle PW3 with 5.8.8 can be downgraded in the future???

Do you actually believe that crystal balls really work and/or one of the cracks here owns a properly functioning one?

[Cinisajoy]

Originally Posted by I.hate.reading

is there any chance that a kindle PW3 with 5.8.8 can be downgraded in the future???

There is always a chance. But as it stands right now, I wouldn't bet on it happening in the near future. Or the distant future for that matter.

So the chances right now are very slim.

[dhdurgee]

Originally Posted by I.hate.reading

is there any chance that a kindle PW3 with 5.8.8 can be downgraded in the future???

What are you willing to do to accomplish this? You can still do so if you are willing to follow serial jailbreaking methods for any kindle with a serial port. You need the proper hardware and software, but it is otherwise quite straight-forward. Of course opening the kindle to do so voids your warranty. You likewise run the risk of destroying the kindle if you use improper equipment or software.

If you are talking about a closed case software only approach that works as it did with earlier firmware, there is no prospect on the horizon at this point. Only a further vulnerability to be exploited can accomplish this.

Dave

[knc1]

Originally Posted by Antinoos

Another Point:

I can't confirm the following statement in posting #1 step 8:


As for my KT3 (included that of a friend of mine) this is not (longer) true generally any more (at least since "basic version" 5.8.3 or so). I could jailbreak these devices and treat them like "other devices" in the list, i.e. simply use the "document style" KUAL-KDK-2.0.azw2 file in the document folder without even starting MRPI for this reason. It starts without any problems. The same ist true, btw, for the Vlasovsoft tools etc., they also may be launched alternatively via their respective *.azw2 document.

But of course you may also use the MRPI method. This has a big advantage: You not only have all your hacks in one neat interface - but you can additionally rename the *.kual "document" (empty file, any name possible, just the extension ".kual" matters) to whatever you like. In my case I used "(1) KUAL (Kindle Unified App Launcher).kual" that brings this on top of the alphabetically sorted document list.

HTH.

Then you have discovered a firmware specific (version & build) variation.

Amazon policy on the 8th. generation devices was to ship without active document support.

And my KT3 (still on its original 5.8.5) is consistent with that policy.

BUT - -

It is only a single enable/disable flag in the firmware, it may be getting overlooked in some builds.
It is not like they removed all of the code.

And it was still disabled in 5.8.8 (by inspection, not by test execution), if you are running something different ....

[knc1]

Originally Posted by I.hate.reading

is there any chance that a kindle PW3 with 5.8.8 can be downgraded in the future???

Do you have an open channel into the minds of the people at Lab126 I could use?

(Not the first time that was asked in this thread. You might change your nick' to: I_hate_searching.)

[Antinoos]

An educated guess: Could this be a language specific behaviour? As you told, Amazon disabled ALL active documents - not only the non-Amazon ones. Active books are relatively common here in Good Old Germany, disabling them completely therefore wouldn't be a good idea...

Okay, I'm happy that its works. Never change a running system... Despite I use the documents only alternatively to launch KUAL or Vlasovsoft's CoolReader. The *.kual extension is much more flexible.

Gesendet von meinem Google Pixel mit Yabba-Dabba-Talk.

[knc1]

Originally Posted by Antinoos

An educated guess: Could this be a language specific behaviour? As you told, Amazon disabled ALL active documents - not only the non-Amazon ones. Active books are relatively common here in Good Old Germany, disabling them completely therefore wouldn't be a good idea...

Okay, I'm happy that its works. Never change a running system... Despite I use the documents only alternatively to launch KUAL or Vlasovsoft's CoolReader. The *.kual extension is much more flexible.

Gesendet von meinem Google Pixel mit Yabba-Dabba-Talk.

Does Amazon have a download URL that serves Germany?
If so, the build ID of the firmware downloaded will be different than that downloaded from Amazon USA.

I don't recall the firmware version, but once before it was found here that Germany downloads where different.
Not only different, but about 30Mbytes bigger.

[Antinoos]

Sounds possible.

Though the initial factory downgrade version before jailbreaking was of course the international version linked here - all my subsequent upgrades I got either OTA here in Germany or fetched them from the amazon.de website. This could well be the reason why Active Book files work too.

Gesendet von meinem Google Pixel mit Yabba-Dabba-Talk.