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

picree · 08-13-2016, 08:45 AM

See here for conflicting information on update.bin.tmp.partial

knc1 · 08-13-2016, 08:52 AM

Quote:

Originally Posted by picree

See here for conflicting information on update.bin.tmp.partial

Out of date information - you just linked to a 2 year old post.

picree · 08-13-2016, 09:23 AM

Quote:

Originally Posted by knc1

Out of date information - you just linked to a 2 year old post.

Well, OK. There are probably many 2-year old posts not out of date. At some point it's difficult to know what is and isn't...

knc1 · 08-13-2016, 09:34 AM

Quote:

Originally Posted by picree

Well, OK. There are probably many 2-year old posts not out of date. At some point it's difficult to know what is and isn't...

Well, the later information found that it was only a few versions of 5.6.x that could over-ride it.

And there are later test reports to be found, each reporting the firmware version that could not over-ride it.

So currently, it is the 'best recommendation' to be made in general for 5.6, 5.7, and 5.8.

Now that we have an easy way to downgrade a Kindle and a way to pick any Amazon firmware release for a device . . . .
It would be possible for someone (with a lot of time on their hands) to test if it works on all models, all firmware versions.

knc1 · 08-13-2016, 09:59 AM

Quote:

Originally Posted by wodan15

- - - - -
@knc1 I did both changing the name and backdoorlock...I hope it works.
Again...sorry for being dumb

That is reasonable -
It doesn't take much space or effort to create an empty directory.

And of course, there is no (practical) way to know if it protects 5.8.2 until Amazon broadcasts 5.8.3

nasser · 08-13-2016, 11:01 AM

Quote:

Originally Posted by wodan15

Hello everybody.
Confirmed working extensions for now :
KUAL.cfg
MRInstaller
backdoorlock
explorer
galculator
gargoyle
gawk
gnash
helper
imageviewer
kindlenotes
kindlereminder
kindletask
kterm
leafpad
morris
rgbpaint
rotations
skipstone
usbnet

@wodan.. I can also confirm that most of these are working on my KT3(W) too.
I see that you've left out KOReader.. Did you try installing it? It didn't work for me.

nasser · 08-13-2016, 11:09 AM

Quote:

Originally Posted by picree

I saw that but I also read (I think on the Wiki page...which i can't find now) that the folder name trick no longer works on >5.6 because "Amazon figured us out..." or something like that. So it's confusing if that folder trick works or not. Do you have to make the folder read-only or something? It's easy enough to add so...I will but now I'm not convinced one way or the other it works.

Yes. I too have seen that wiki post about the folder trick no longer working.
When I JB'd my PW3, by mistake I created a file update.bin.tmp.partial. Later I observed that it had started growing! After I deleted it, and created the folder, I no longer saw the file being downloaded. So it looks like the folder trick is working, after all.

knc1 · 08-13-2016, 11:24 AM

Hmm...
So create a file of 512 bytes of zeros (or as few as one) as that name.
The dumb software will 'continue' to append the OTA file to it.
Which of course will fail to install because the signed checksum will fail.

That will leave you with a nice copy of the OTA file (which you will probably have to un-delete from USB storage) once you trim your dummy header off of it.

knc1 · 08-13-2016, 12:28 PM

Quote:

Does the color really affect the device behaviour?

Only as an artifact.
When Lab126 're-designs' something, it does not always stop at the dye in the plastic.

See the K4-black and K4-silver for example.

That is why we have 'reserved' color indicating letters in our nickname table.
Just in case it someday makes more of a difference than appearance.

(Already I have questions about the KT3, White vs Black - enough so that I ordered one to find out for myself)

nasser · 08-13-2016, 01:41 PM

Quote:

Originally Posted by wodan15

...
Having that in mind i wonder why you say "most"?
Shouldn't it be the same?
...

Because I haven't installed some of the stuff in your list... like gawk, gnash, skipstone

Quote:

Originally Posted by wodan15

...
Does the color really affect the device behaviour?
*severeheadscratching*
...

Of course not! But the white bevel does give a different look

nasser · 08-13-2016, 01:44 PM

Quote:

Originally Posted by knc1

...
(Already I have questions about the KT3, White vs Black - enough so that I ordered one to find out for myself)
...

Then you need to change your profile info ("Nothing KV or newer..")

knc1 · 08-13-2016, 02:12 PM

Quote:

Originally Posted by nasser

Then you need to change your profile info ("Nothing KV or newer..")

It is back-ordered, I have at least a month to make the change.

But I did promise myself to: "Never send Amazon money, never, ever, again" -
About six devices ago now.

Sukarn · 08-13-2016, 03:00 PM

Quote:

Originally Posted by wodan15

Sorry @sukran the quote didn't show up.

That's okay, really. I already said I can't find any fault with you when you were only trying to help :-)

Quote:

Originally Posted by knc1

...create a file of 512 bytes of zeros (or as few as one) as that name.
The dumb software will 'continue' to append the OTA file to it.
Which of course will fail to install because the signed checksum will fail.

That will leave you with a nice copy of the OTA file (which you will probably have to un-delete from USB storage) once you trim your dummy header off of it.

That does assume that you can replace the dummy header with the actual header, i.e. you have the correct header lying around with you elsewhere, because if it's appending data like a pure "wget -c" then it will just start appending from byte 513 by starting a download offset by 512 bytes.

Then, it additionally assumes that when the update fails an integrity check or whatever kind of check they have, the software does not do an "rm update.bin.whatever.the.name.was" followed by attempting the download again at some random point of time in future.
After all, they wouldn't want people to stop receiving updates just because one update at one time was corrupted while being downloaded.

knc1 · 08-13-2016, 03:27 PM

So use only the known part of the header.
You can find it lying around in the KindleTool source code.
And I did comment that you would probably have to un-delete it.

knc1 · 08-13-2016, 04:25 PM

Make a bug report on the KOreader repository site.

OR
clone the repo, make the changes to add KT3 devices, issue a pull request.
(that will probably get it done faster than waiting for NiLuJe to return from holiday.)

It will look just like one of the others (PW3 if 300 dpi, etc).

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
USB OTG Mouse Support and page turn on PW3(possible KV/KOA)	lucida	Kindle Developer's Corner	105	12-07-2024 02:18 PM
PW3 PW3-4, PW3-32, fw-5.8.9.0.1 software jailbreak	knc1	Kindle Developer's Corner	203	01-27-2020 11:53 PM
Will jailbreak survive a 5.9.2.0.1 update on KOA?	tigrisg	Kindle Developer's Corner	1	12-19-2017 05:49 AM
PW3 stuck in "code 2" after software jailbreak attempt from 5.8.10	Varijus	Kindle Developer's Corner	10	12-17-2017 03:08 AM

08-13-2016, 08:45 AM	#916
picree Connoisseur Posts: 93 Karma: 10000 Join Date: Apr 2016 Device: Kindle Oasis KOA FW 5.13.3 JB	See here for conflicting information on update.bin.tmp.partial

08-13-2016, 11:24 AM	#923
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Hmm... So create a file of 512 bytes of zeros (or as few as one) as that name. The dumb software will 'continue' to append the OTA file to it. Which of course will fail to install because the signed checksum will fail. That will leave you with a nice copy of the OTA file (which you will probably have to un-delete from USB storage) once you trim your dummy header off of it.

08-13-2016, 03:27 PM	#929
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	So use only the known part of the header. You can find it lying around in the KindleTool source code. And I did comment that you would probably have to un-delete it.

08-13-2016, 04:25 PM	#930
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Make a bug report on the KOreader repository site. OR clone the repo, make the changes to add KT3 devices, issue a pull request. (that will probably get it done faster than waiting for NiLuJe to return from holiday.) It will look just like one of the others (PW3 if 300 dpi, etc).

Advert

Advert