BackDoorLock hack - prevents silent updates

[nixkalo]

Thinking out loud:
Since I had to use dnsmaq for the 5.6.5 JB, I looked at what things the kindle was requesting. One of them was

query[A] softwareupdates.amazon.com from 192.168.1.92

And one of the records in /opt/var/local/reg/ServerConfig.db (and sqlite3 file) is:

INSERT INTO "properties" VALUES('dcd','url.dsts','https://softwareupdates.amazon.com/software/inventory');

So, would tweaking with this sqlite3 file help in preventing OTAs?

OTOH, url.dsts appears as a string inside the binary /usr/bin/otav3, and this same binary has, near it, this other string:
/var/local/system/SKIP_UPDATE_CHECK

Could this help?

my .02$
Nix

[knc1]

Originally Posted by sandman7920

If running out of space doesn't brick Kindle, this might be interesting
dd if=/dev/zero of=/mnt/us/file_fs.img bs=2M count=1024
mkfs.vfat /mnt/us/file_fs.img
mount -oloop /mnt/us/file_fs.img /mnt/us/documents
But i am not sure what will happen during usb-export

Always: bs=4096 (the size of an erase block).

Yeah, there is a fuse layer that the user sees over the actual file system (at: /mnt/base-us IIRC)
No telling what the results of a mount on top of that would be.

I highly recommend rescue pack + coward's rescue pack (add-on to RP) - that will give you ssh/telnet into the diags system if the main system chokes up.

And/or a serial port connection.

PS: Maybe not quite so big, so the system has room for bookmarks, annotations, and book indices (all on that same fat-32 file system).

Note: In the (distant) past, people have split the single partition user storage into two (or more) partitions.
Older devices, much older firmwares.
That might be another way to consume the space in a way that the system "thinks' there isn't any room left in the root of the file system.

[AirRaven]

Originally Posted by knc1

I highly recommend rescue pack + coward's rescue pack (add-on to RP) - that will give you ssh/telnet into the diags system if the main system chokes up.

Just curious- are both of these verified as being functional on the Paperwhite 3?

I've been reluctant to do much playing around without CRP installed, but there doesn't seem to be any kind of account out there of it working on the PW3.

[knc1]

Originally Posted by AirRaven

Just curious- are both of these verified as being functional on the Paperwhite 3?

I've been reluctant to do much playing around without CRP installed, but there doesn't seem to be any kind of account out there of it working on the PW3.

I got my PW-3 re-assembled yesterday, I'll give it a try RSN.
Probably tomorrow sometime - more errands to do today (life wins over hobby time).

[NiLuJe]

@AirRaven: Actual reports, I don't think so? But someone provided @knc1 with a diags image from a PW3 or a KV, and he passed it on to me, and AFAICT, it appears to be safe & functional.

That's when my RP/CRP snapshots started to be installable on those devices.

[odamizu]

Originally Posted by odamizu

I have update.bin.tmp.partial folder on my Voyage 5.6.5. (per this post). I've had WiFi on, and so far no forced update. Don't know if it's because update.bin.tmp.partial is blocking it, or Amazon just hasn't gotten to my Voyage yet.

Originally Posted by knc1

That is the only way to test it -
Put the folder in there and hold it up in the air, see if Amazon shoots it down.

Thanks

Is it at all useful to you developers for me to continue this experiment?

[knc1]

Originally Posted by odamizu

Thanks

Is it at all useful to you developers for me to continue this experiment?

Yes.
A lot of people would like to know if this method works on 5.6.5 -
Keep in mind, less than 1% of our users ever bother to register and make a comment.

And as I mentioned above, it may take as much as six weeks for Amazon to finish with the OTA updates (according to a notice I received from them).

If anyone intends to stay on 5.6.5 -

remember to never use the built-in browser - its a webkit/javascript problem with the version shipped in the Kindle.

and note that our build of skipstone has been reported as still working.
I haven't seen any reports (yet) about our build of Mindora.

[eschwartz]

Midori.

The problem with Midori is, last time I tried it, it was just way too much of a burden on my poor Kindle -- I couldn't do anything with it.

Does the PW do any better, or is my KT just stubborn?

[knc1]

Originally Posted by eschwartz

Midori.

The problem with Midori is, last time I tried it, it was just way too much of a burden on my poor Kindle -- I couldn't do anything with it.

Does the PW do any better, or is my KT just stubborn?

Your KT has a slower processor and half as much ram (IIRC).

But as you noted in the first line quoted, my IIRC may not be working.

[eschwartz]

ISTR the Voyage was finally bumped from the traditional 256 MB to 512 MB.

And the PW2 was the first model with the i.MX6

[knc1]

And since we are testing 5.6.5 - then we are not testing a PW-1.

I think my PW-3 has 512 MB ram also - I can check later today.
The el-cheap'o KT-2 may not, but mine is still torn apart, I can't check that.

There was a recent thread about Android on the i.MX6 models that mention how much ram each shipped with.

[guerrilla]

I'm sorry I'm not sure that I got the last two pages of this thread right.
Is a jailbroken PW2 with 5.4.5.1 firmware and BackDoorLock hack installed still safe against silent updates or did Amazon find a way to circumvent it with this OTA they are releasing now?

[knc1]

Originally Posted by guerrilla

I'm sorry I'm not sure that I got the last two pages of this thread right.
Is a jailbroken PW2 with 5.4.5.1 firmware and BackDoorLock hack installed still safe against silent updates or did Amazon find a way to circumvent it with this OTA they are releasing now?

Ah ....

The OTA download is being done by the currently executing version, not the version to be installed in the future.

If your currently executing a firmware version that is not in the 5.6.x series, this backdoor lock is effective.

[guerrilla]

Uh ok. I missed the news about the 5.6.5 jb being out.
So, in order to avoid surprises, it's advisable to hold on and wait to upgrade to 5.6.5 untill BDL will work on 5.6.5, right?

[knc1]

Originally Posted by guerrilla

Uh ok. I missed the news about the 5.6.5 jb being out.
So, in order to avoid surprises, it's advisable to hold on and wait to upgrade to 5.6.5 untill BDL will work on 5.6.5, right?

I would not advise that -
You WANT to update to 5.7.2 because it disables the JB vector in 5.6.5
The only reason for using 5.6.5 is if you need to install the JB on a device that has not already been jailbroken.

BIG NOTE: Be certain you have the most recent JB from the snapshots thread installed before upgrading.

Also: See the BDL alternatives at the bottom of this post:
https://www.mobileread.com/forums/sho...96&postcount=2