BackDoorLock hack - prevents silent updates

[Itsukki]

So, should this in theory avoid a PW1 on 5.6.1.1 to upgrade?

I just don't want to loose my custom screensavers, again.

[knc1]

Originally Posted by Itsukki

So, should this in theory avoid a PW1 on 5.6.1.1 to upgrade?

I just don't want to loose my custom screensavers, again.

We do not know for certain yet.

You have probably noticed that you can downgrade your PW1, see:
https://www.mobileread.com/forums/sho...d.php?t=263411

[GoSharks]

Originally Posted by Geralt

This happened to me again yesterday. The minute I had connected to wi-fi.


and this worked again


It's safe to say that backdoor lock doesn't work, at least on my PW2.
My FV now after this sneaky update is 5.6.5.

FYI- It apperars to be confirmed that BackDoorLock no longer works on PW2...

[Dexmaster]

I had few silent updates (two even with BackDoorLock in locked state) and currently have FW 5.6.2.1 on my PW2.

I've had some time thinking how should I make everything work, tried few methods then, remembered old one and it works for now.

I mostly stay in airplane mode, but I've checked and find out that the system created a file 'update.bin.tmp.partial', then:
1) I hastly switched airplane mode on;
2) Checked back door lock, it's still in locked state, no help there;
3) Removed 'update.bin.tmp.partial' file and created a folder with the same name;
4) Switched airplane mode off, to check wifi and folder has not disappeared;
5) Checked even after restart this method persists;
6) I'm waiting what happens next but for now I'm hopeful;
7) Profit! no OTA updates even after hours of Cloud browsing and stuff.

P.S. If there would be any changes, I'll try loging mentioning them when they'll happen.

[knc1]

Originally Posted by Dexmaster

I had few silent updates (two even with BackDoorLock in locked state) and currently have FW 5.6.2.1 on my PW2.

I've had some time thinking how should I make everything work, tried few methods then, remembered old one and it works for now.

I mostly stay in airplane mode, but I've checked and find out that the system created a file 'update.bin.tmp.partial', then:
1) I hastly switched airplane mode on;
2) Checked back door lock, it's still in locked state, no help there;
3) Removed 'update.bin.tmp.partial' file and created a folder with the same name;
4) Switched airplane mode off, to check wifi and folder has not disappeared;
5) Checked even after restart this method persists;
6) I'm waiting what happens next but for now I'm hopeful;
7) Profit! no OTA updates even after hours of Cloud browsing and stuff.

P.S. If there would be any changes, I'll try loging mentioning them when they'll happen.

Please keep us advised if the above (continues to) work(s) with 5.6.2.1

= = = =

I am pretty sure that the currently posted BDL will not protect against or control a download file of that name.
Perhaps the author will return long enough to update the version 12 that is currently posted.

[odamizu]

Originally Posted by Dexmaster

...
3) Removed 'update.bin.tmp.partial' file and created a folder with the same name;
4) Switched airplane mode off, to check wifi and folder has not disappeared;
5) Checked even after restart this method persists;
6) I'm waiting what happens next but for now I'm hopeful;
7) Profit! no OTA updates even after hours of Cloud browsing and stuff.

Am I understanding correctly that if you place an empty folder named "update.bin.tmp.partial" on your Kindle's root directory and it does not disappear, then it will likely block OTA updates?

I have 5.6.5 on a Voyage. I am happy to put this folder on my Voyage and report back on whether it persists and blocks future updates (which may be a while since 5.6.5 just came out) if this is helpful.

P.S. My Voyage is not jailbroken. If this is only for jailbroken devices, then nevermind.

[knc1]

Originally Posted by odamizu

Am I understanding correctly that if you place an empty folder named "update.bin.tmp.partial" on your Kindle's root directory and it does not disappear, then it will likely block OTA updates?

Yes.

Originally Posted by odamizu

I have 5.6.5 on a Voyage. I am happy to put this folder on my Voyage and report back on whether it persists and blocks future updates (which may be a while since 5.6.5 just came out) if this is helpful.

Thanks!
but it may be awhile before a newer firmware is released.

Originally Posted by odamizu

P.S. My Voyage is not jailbroken. If this is only for jailbroken devices, then nevermind.

JB not required.

It **might** work with any 5.6.x version of the firmware (the sub-series that started ignoring our BDL).
If we can gather enough information from user's reports ....

[odamizu]

Okay, will do.

P.S. update.bin.tmp.partial survives reboot on 5.6.5

[knc1]

Super!
Either it isn't looking for anything at all, or that is a special "ignore me" name pattern.

[Dexmaster]

Two days and no OTA updates, to test it backwards I even removed a folder, and file was created when I connected to wifi, so this method is working. And this was not my idea, I read it here some time ago. (but I'm not sure it could be any other post)

[eschwartz]

Fascinating. We had word that newer firmwares had "fixed" this trick. Has Amazon "broken" it again?

[knc1]

Originally Posted by eschwartz

Fascinating. We had word that newer firmwares had "fixed" this trick. Has Amazon "broken" it again?

That is what we are trying to determine, FOR: PW-2, 5.6.5
It may be different, different models/firmwares.

[thatworkshop]

Originally Posted by eschwartz

Fascinating. We had word that newer firmwares had "fixed" this trick. Has Amazon "broken" it again?

Oh man... Amazon has really made things complex from the sound of it. I've never had a device later than Kindle Touch (for a few days had PW which I returned as it wasn't my taste.) I'm kind of glad I don't have to deal with this much "nonsensical closed-sourceness and closed-ness"!

[knc1]

Happy 500!

[odamizu]

Originally Posted by knc1

That is what we are trying to determine, FOR: PW-2, 5.6.5
It may be different, different models/firmwares.

I can confirm update.bin.tmp.partial survives reboot on Voyage 5.6.5, but I won't be able to confirm whether it successfully blocks updates until a new update comes out (which could be a while).

Originally Posted by Dexmaster

Two days and no OTA updates, to test it backwards I even removed a folder, and file was created when I connected to wifi, so this method is working ...

:

Dexmaster, you're on PW2 5.6.2.1, yes?