3.4 update coming out tonight...

[diba]

THX, then this the easiest solution for the ones not willing /able to do the version via ssh.
Additional question, does it block the update effort as well or simply make it fail?

[AZImmortal]

If you try to manually update, the update will appear to install but it won't take as long as actually installing the update, and when it's "done" and your Kindle has started back up, you can check your firmware version to see that it hasn't changed. Automatic updates seem to be simply blocked.

[twobob]

I'm reticent to package something that removes access to amazons services.
For obvious reasons.

So either it by hand or as you/AZImmortal suggest above
Glad you got it sorted

[wakajawaka]

Unfortunately I just tried but cannot install updates provider in mine. Maybe it can't be installed in 3.3?

[twobob]

Originally Posted by wakajawaka

Unfortunately I just tried but cannot install updates provider in mine. Maybe it can't be installed in 3.3?

sorry what?

the tin-hat tweak or the 3.4 update?

the quote of mine (for the security nerf) was from a 3.3 kindle.

exactly what are you trying to do?

cheers : ))

EDIT: it REALLY helps if you quote something to refer to...

[wakajawaka]

AZ told me this:

Originally Posted by AZImmortal

This updates provider hack worked for me as of 3.3 (it kept me from updating to 3.4 until disabled it).

So I tried to install it in my kindle 3 wifi with 3.3, jailbreak and localisation mod. It wouldn't install, giving error 8.

[twobob]

Originally Posted by wakajawaka

AZ told me this:

Blah:

So I tried to install it in my kindle 3 wifi with 3.3, jailbreak and localisation mod. It wouldn't install, giving error 8.

Ah! Thanks mate... : ) I vaguely recall this now. much obliged for the update

[diba]

Localisation abvoids update to 3.4 already. Recommend the version via ssh.

[wakajawaka]

Originally Posted by diba

Localisation abvoids update to 3.4 already. Recommend the version via ssh.

I know, and the device is constantly trying to update, rebooting every time it goes idle.

That's what we are trying ti fix. I said it few posts before.

[twobob]

blacklist the update. I seem to recall this can be done somehow for the 3. I don't know how. Niluje might?


here is some alternate options:

Spoiler:

you could also simply hack and slash:

/etc/updater.conf (pictured in full with the extra amend at the end)

I changed:

PHP Code:

# Returns battery in percent. Integer, % sign stripped off
get_batt_percent() {
#    return `gasgauge-info -s | sed 's/\%//'`
    [B]return 14[/B]
} 


as it checks for 15 the update should never install. Totally untested but that is certainly one option (was my first look in the scripts)

you could also block ip's, Amend services, point services to localhost and a whole other list of options.

If you just want to stop OTA updates dead - then this should work. Did I say it was untested?

might want to check it is ACTUALLY 14 and not '14' that needs returning... I'm not sure tbh. I think without the quotes:
[root@kindle /dev]# gasgauge-info -s
95%

Another option would be:

add the entry
127.0.0.1 todo-g7g.amazon.com
to /etc/hosts:
This has other side effects though that may not be desirable.

Probably the easiest is:

Change 15 to 101

# Minimum battery required for an update (percent)
_MIN_BATT=101

: )

Okay testing this now: restarting framework now ! EEk

Well, my kindle didn't explode on a restart with the 101 in place.
And I don't even need to test if that works. because it just has to.

Sorted. there are prettier ways but that would do the job of nerfing the updates anyway

[diba]

post 111 shows a solution for the permanent update effort of the system.

[twobob]

Originally Posted by diba

post 111 shows a solution for the permanent update effort of the system.

Happy days then.

[knc1]

Originally Posted by diba

post 111 shows a solution for the permanent update effort of the system.

Originally Posted by twobob

Happy days then.

@twobob: You wrote post 111


Time for a quick power nap maybe?

[twobob]

Originally Posted by knc1

@twobob: You wrote post 111


Time for a quick power nap maybe?

well. that is another solution.

Yeah too focused on

flashed 0x001d0000 (=1900544) bytes
I: flashed 0x001e0000 (=1966080) bytes
I: flashed 0x001f0000 (=2031616) bytes
I: flashed 0x00200000 (=2097152) bytes
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00200000 (=2097152) bytes to address 0x16fc1000, waiting for completion...
I: wrote 0x00200000 (=2097152) bytes, waiting for completion...
I: flashed 0x00010000 (=65536) bytes
I: flashed 0x00020000 (=131072) bytes
I: flashed 0x00030000 (=196608) bytes
I: flashed 0x00040000 (=262144) bytes
I: flashed 0x00050000 (=327680) bytes
I: flashed 0x00060000 (=393216) bytes
I: flashed 0x00070000 (=458752) bytes
I: flashed 0x00080000 (=524288) bytes
I: flashed 0x00090000 (=589824) bytes
I: flashed 0x000a0000 (=655360) bytes
I: flashed 0x000b0000 (=720896) bytes
I: flashed 0x000c0000 (=786432) bytes
I: flashed 0x000d0000 (=851968) bytes
I: flashed 0x000e0000 (=917504) bytes
I: flashed 0x000f0000 (=983040) bytes

rolling around... bedtime night mate

[wakajawaka]

Ok I have another problem now. Cannot find /etc/updater.conf

nor /usr/bin/process_update

Feel like I must be missing something really obvious :/