BackDoorLock hack - prevents silent updates

[knc1]

Sorry about the confusion I added.

[Dexmaster]

Originally Posted by odamizu

Dexmaster, you're on PW2 5.6.2.1, yes?

Yes, PW2 5.6.2.1 exactly, also to be precise it's PW2 4Gb (Japanese version) but firmware is the same for all PW2 so it won't matter 4Gb or 2Gb.

And I can confirm that folder 'update.bin.tmp.partial' survives restarts, web surfing and kindle synchronization just fine.

[peca89]

I can confirm that directory "update.bin.tmp.partial" created in Kindle root survives reboot on PW3 running 5.6.1.1 (out-of-the-box firmware, non-jailbroken)

I tried web and store browsing for few minutes and nothing happened. Directory stayed there and no new files were created.

[Brynwall]

My root survived the 5.6.5 update, but somehow they snuck in past the backdoor lock that I had set...

Am I doing something wrong to lock the OTA updates that Amazon keeps slipping past the lock?

[Brynwall]

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.

Awesome! Thanks for the info! I'm going to do the same thing to my PW2 and go one step further and lock the folder down. haha

I verified that the folder did survive on 5.6.5 after a reboot and after I locked the folder down.

[tigran]

I made a stupid mistake. I have reset my Kindle Keyboard to Factory Defaults, forgetting that I have manually edited /etc/updater.conf to set the minimum battery level to an impossible value (like 150% or such) so that no updates happen ever again. But now I want to install jailbreak (factory reset seems to have wiped it out) and I cannot because it complains "Your battery level is too low to install the update safely".

So, is there any way to override the minimum battery level setting in /etc/updater.conf and install the jailbreak somehow? I tried rebooting while usb cable was plugged in and it did not help --- the update was silently ignored.

Any ideas?

[knc1]

Sounds like an impossible situation.

Start over, install a complete, working, image with Kubrick.

[tigran]

knc1, thank you, I didn't realize that there is a possible solution because I never heard of Kubrick. I will study the instructions and follow them to "debrick" my Kindle 3. Thanks again!

[roger64]

Hi

While I am waiting for the 5.6.5. jailbreak, I have a question. I intend of course to install this very useful hack (thanks for it) as soon as possible.

After that, I plan to use my PW3 with Koreader. Koreader allows you to perform OTA incremental updates. Will this hack block the Koreader updates as well as the Kindle updates?

[knc1]

Originally Posted by roger64

- - - -
After that, I plan to use my PW3 with Koreader. Koreader allows you to perform OTA incremental updates. Will this hack block the Koreader updates as well as the Kindle updates?

Amazon "pushes" OTA updates without the user's consent, KOReader does not. So they really aren't the "Amazon Style" of forced OTA updates.

According to the directions, this backdoorlock does not block manually started, by the end user, updates.

[roger64]

Originally Posted by knc1

Amazon "pushes" OTA updates without the user's consent, KOReader does not. So they really aren't the "Amazon Style" of forced OTA updates.

According to the directions, this backdoorlock does not block manually started, by the end user, updates.

Of course, the Koreader way is better: you check when you wish to update, you are told there is -or not - an update available (stable or develop channel) and you go for if you wish.

Thanks for your reply.

[knc1]

Originally Posted by roger64

Of course, the Koreader way is better: you check when you wish to update, you are told there is -or not - an update available (stable or develop channel) and you go for if you wish.

Thanks for your reply.

Hmm...
Reads like you answered your own question better than I did.

This BackDoor Lock works with (or against) the Amazon automatic updater.
KOReader does not use the Amazon automatic updater, it provides its own update controls.

= = = =

In fact, given a moment or two to think about it - IIRC:
I think that KOReader's start-up on a Kindle device stops the Framework daemon.
And it is the Framework daemon that handles the forced updates.

[NiLuJe]

@knc1: That particular choice is left to the user's discretion. If launched through @chrox's applet, it's perfectly integrated into the framework, so everything runs as usual. And if launched through KUAL, there are two distinct launch buttons, once which kills the framework, and one that doesn't .

On recent devices, unless you work with large PDFs, keeping the framework running should be okay.

[roger64]

Originally Posted by knc1

Hmm...
Reads like you answered your own question better than I did.

No no, I only know the Kobo/Koreader part but I prepare myself intensively for the other.

@Niluje

Merci

[knc1]

Originally Posted by NiLuJe

- - - -

On recent devices, unless you work with large PDFs, keeping the framework running should be okay.

Do you mean the devices with 512Mbyte of RAM ?

There should be a way to dump the RAM size.
There are a lot of eips commands used in those factory diagnostic logs, I'll take a look.

Otherwise, we can fondle meminfo:

cat /proc/meminfo
MemTotal:        3346944 kB
MemFree:          641216 kB
Buffers:          494236 kB
Cached:          1385272 kB
SwapCached:            0 kB

= = = = =

(That is not a Kindle, but it is the same Kernel version.)