Quote:
Originally Posted by j.p.s
That has always been true, that advice is frequently given, and seems to be seldom heeded. It has very often paid off, sometimes after a few months, and sometimes only after years.
|
Yep, that's what I always recommend people to stick to, but I've never been in the position to actually have to follow it myself.
Not being able to stop the upgrades myself makes me feel so... insecure!
Quote:
I'm not sure what you mean.
Some jailbreaks depend on an exact model and version. Those were sometimes the release version, but others times the version was after many updates. The last few years some jailbreaks would work for a range of firmwares on a range of models. I once had to do a firmware update to jailbreak, but that almost never happens. (And the firmware I had to update to was already old.)
In any case the newer firmwares are getting more and more locked down.
|
You have actually answered to me nevertheless.
What I was asking was this: in the past when I jailbreaked my kindles, I read procedures that said: do this and this and this, but they were said to be valid only if I applied them as soon as I got my kindle, that is applicable to a kindle with a factory firmware; if I had let the kindle to update, the vulnerability exploited by the jailbreak was fixed and not exploitable anymore.
But based on what you say, I understand that there are also jailbreak (maybe like this watchthis! one) that do work also on non-factory firmware, provided they are <=5.14.2.
So it's not granted that if I update to, let's say, 5.15.1 now, one day somebody will find a jb procedure that works on this fw "non factory"... but of course, as we were saying above, the less we update the fw, the more likely is a newly found jb to work