Quote:
Originally Posted by NiLuJe
The loophole wasn't actually kept secret at all, because there's no actual loophole.
Someone just happened to get a Kindle that slipped a QA step and knew what do to with that fact  . And we got extremely lucky with the way that QA image was packaged (which may, in fact, have been a quick shortcut to make the QA process more streamlined at the time, e.g., release crunch).
It's entirely plausible that this happened to get fixed just because someone at lab126 was in the vicinity of the updater's code for whatever reason, looked at it and went: "well, that's dumb". |
Incidentally, I think the Kindle that had it (a refurb) actually went through the QA process while most others didn't.
Interestingly enough, the diags firmware still passes initial version check so it's not automatically deleted on copy and still allows us to use
Update Your Kindle via menu. I'm guessing there's a second verification check (at least as of 5.13.4) during the actual update install process which results in
UPDATE ERROR: 12.
I tried installing the diags first on a jailbroken PW4 with 5.13.4 which had the
PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC file and downgrade worked on that. Factory reset followed by upgrade to 5.13.4 removed JB and hotfix and after that, diags firmware would no longer install.
On a different note, there are several references to platform bellatrix on 5.13.4 so I do wonder if we're getting new Kindles soon.