mbirth/wiki.mbirth.de
1
0
Fork 0
mirror of https://github.com/mbirth/wiki.git synced 2024-11-09 13:16:45 +00:00
Code Issues Releases Wiki Activity

New page about OTA versions.

Browse Source
This commit is contained in:
Markus Birth 2017-09-17 20:51:02 +02:00
parent e7b4db69e6
commit 015505b16b
Signed by: mbirth
GPG Key ID: A9928D7A098C3A9A
3 changed files with 106 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
css/custom.sass
View File

@ -49,6 +49,9 @@ abbr, acronym
#comments #comments
clear: both clear: both
td
white-space: nowrap
$noteclassic: #99d $noteclassic: #99d
$noteimportant: #ff0 $noteimportant: #ff0
$notewarning: #d99 $notewarning: #d99

58
know-how/hardware/blackberry-keyone/_posts/2017-09-17-bb-keyone-ota-updates-for-different-variants.md
View File

@ -3,7 +3,7 @@ title: BlackBerry KEYone OTA updates for different variants
layout: default layout: default
language: en language: en
created: 2017-09-15 20:32:10 +0200 created: 2017-09-15 20:32:10 +0200
updated: 2017-09-17 13:32:42 +0200 updated: 2017-09-17 20:49:36 +0200
toc: false toc: false
tags: tags:
- know-how - know-how
@ -132,44 +132,16 @@ which I rewrote and improved. My version can be found here:
<https://github.com/mbirth/tcl_ota_check> <https://github.com/mbirth/tcl_ota_check>
After downloading or cloning the repository, edit the `tclcheck_all.py` and change the `fc.fv` For convenience, I put up a matrix [here]({% post_url 2017-09-17-bb-keyone-variants-ota-matrix %}).
variable to your current firmware version. Let's assume you have a UK BBB100-2, so your PRD would
be `PRD-63117-003` and as of September 2017, your firmware version would be `AAM481`. So change the
line with `fc.fv` to:
fc.fv = "AAM481" Let's say we have a UK BBB100-2. The PRD would be PRD-63117-003 and as of September 2017, we'd run
firmware version `AAM481`. However, that's the July patch, not the September patch.
Also change the `fc.mode` line to: But we can see from the matrix, that other variants already got the August patch (`AAN358`) and the
`PRD-63117-034` even is on the September patch already (`AAO472`). However, the `-034` never ran
fc.mode = fc.MODE_OTA version `AAM481`. So we have to get our device to `AAN358` first to be able to patch it to
`AAO472`. For that, we can use any variant that has our current version `AAM481` and `AAN358`, e.g.
Now run the script. You'll get an output like this: `PRD-63117-011`.
~~~
List of latest OTA (from AAM481) firmware by PRD:
...
PRD-63117-003 failed. (No update available.)
PRD-63117-011: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (QWERTZ BBB100-2 (Germany))
PRD-63117-015: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (BBB100-2 (NL, Belgium))
PRD-63117-019: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (BBB100-2)
PRD-63117-023: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (AZERTY BBB100-2 (Belgium))
PRD-63117-025 failed. (No data for requested CUREF/FV combination.)
PRD-63117-027: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (QWERTY BBB100-2 (UAE))
PRD-63117-028: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (BBB100-2)
PRD-63117-029: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (BBB100-2)
PRD-63117-034 failed. (No data for requested CUREF/FV combination.)
PRD-63117-036 failed. (No data for requested CUREF/FV combination.)
PRD-63117-037 failed. (No data for requested CUREF/FV combination.)
PRD-63117-041: AAM481 ⇨ AAN358 d819919187b46793abeaeff60dd6deee17baac4b (BBB100-2)
PRD-63117-042 failed. (No data for requested CUREF/FV combination.)
PRD-63117-703 failed. (No data for requested CUREF/FV combination.)
PRD-63117-704 failed. (No data for requested CUREF/FV combination.)
PRD-63117-717 failed. (No data for requested CUREF/FV combination.)
...
~~~
As you can see, our `PRD-63117-003` variant doesn't have the update yet, but other variants have.
Just pick one, let's say `PRD-63117-011`.
Doing the actual update Doing the actual update
@ -193,12 +165,12 @@ Your phone will reboot and install the update. It'll boot up to the new version.
<p><div class="notetip" markdown="1"> <p><div class="notetip" markdown="1">
In the case of the `PRD-63117-003` variant and assuming a time of mid-September 2017, the just In the case of the `PRD-63117-003` variant and assuming a time of mid-September 2017, the just
installed `AAN358` isn't the latest version. There's a newer `AAO472` version available. So change installed `AAN358` isn't the latest version for this model. There's a newer `AAO472` version
the `fc.fv` line in the `tclcheck_all.py` to `AAN358` and run it again. You'll find out that only available as you can see from the [matrix]({% post_url 2017-09-17-bb-keyone-variants-ota-matrix %}).
the variant `PRD-63117-034` is currently getting the OTA update to `AAO472`. Enter that into the But only the variant `PRD-63117-034` is currently getting the OTA update to `AAO472`. Enter that
*Emulated CU Reference* field in the *Updates* app, change the *Emulated current version* to the into the *Emulated CU Reference* field in the *Updates* app, change the *Emulated current version*
just installed `AAN358` and tap <kbd>START TEST</kbd> again. It'll show the second update and let you to the just installed `AAN358` and tap <kbd>START TEST</kbd> again. It'll show the second update
install that. and let you install that.
(If the updater started to download the previous update file again, remove it like explained in (If the updater started to download the previous update file again, remove it like explained in
the *Cleanup* section.) the *Cleanup* section.)

88
know-how/hardware/blackberry-keyone/_posts/2017-09-17-bb-keyone-variants-ota-matrix.md Normal file
View File

@ -0,0 +1,88 @@
---
title: BlackBerry KEYone variant's OTA updates
layout: default
language: en
created: 2017-09-17 20:35:18 +0200
updated: 2017-09-17 20:35:18 +0200
toc: false
tags:
- know-how
- hardware
- blackberry
- keyone
- ota
- updates
- firmware
---
<p><div class="noteimportant" markdown="1">
Note that firmwares are only compatible between the same model. So when trying to update a device
from version `AAL093`, make sure to emulate the correct model. If you have the BBB100-1, you have
to use `PRD-63116-001`. If you have the BBB100-2, use `PRD-63117-003`.
For other BBB100 models, make sure the 6 digits in the middle of the PRD number match.
However, since the OTA updates check the device before installing, there should be no risk of
bricking your device should you manage to download the wrong update.
</div></p>
BBB100-1 (PRD-63116) firmwares
==============================
<div style="overflow-x: scroll;" markdown="1">
| PRD-63116-001 | | AAL093 | | | AAL964 | | | | AAN355 | | AAN517 | | AAO472 |
| PRD-63116-003 | AAK399 | | AAL483 | | | | AAM625 | | | | AAN517 | | |
| PRD-63116-005 | AAK399 | | AAL483 | | | | AAM625 | | | | AAN517 | | |
| PRD-63116-007 | AAK399 | | AAL483 | | | | AAM625 | | | | | | |
| PRD-63116-009 | | | | AAL619 | | AAM481 | | | | AAN358 | | | |
| PRD-63116-010 | | | | AAL619 | | AAM481 | | | | AAN358 | | | |
| PRD-63116-013 | | | | AAL619 | | AAM481 | | | | AAN358 | | | |
| PRD-63116-017 | | | | | | AAM481 | | | | | | | |
| PRD-63116-020 | | | | | | AAM481 | | | | AAN358 | | | |
| PRD-63116-021 | | | | AAL619 | | AAM481 | | | | AAN358 | | | |
| PRD-63116-023 | | | | | | AAM481 | | | | AAN358 | | | |
| PRD-63116-024 | | | | | | AAM481 | | | | AAN358 | | | |
| PRD-63116-027 | | | | | | | | AAN057 | | | | | |
| PRD-63116-033 | | | | | | AAM481 | | | | | | | |
| PRD-63116-036 | | | | | | | | | | | | AAN596 | |
</div>
BBB100-2 (PRD-63117) firmwares
==============================
<div style="overflow-x: scroll;" markdown="1">
| PRD-63117-003 | AAK624 | AAK879 | AAL093 | AAL682 | AAM481 | | |
| PRD-63117-011 | AAK624 | AAK879 | | AAL682 | AAM481 | AAN358 | |
| PRD-63117-015 | | AAK879 | | AAL682 | AAM481 | AAN358 | |
| PRD-63117-019 | | | | | AAM481 | AAN358 | |
| PRD-63117-023 | | AAK879 | | | AAM481 | AAN358 | |
| PRD-63117-025 | | | | AAL682 | | AAN358 | |
| PRD-63117-027 | | AAK879 | | | AAM481 | AAN358 | |
| PRD-63117-028 | | AAK879 | | | AAM481 | AAN358 | |
| PRD-63117-029 | | | | AAL682 | AAM481 | AAN358 | |
| PRD-63117-034 | | | | | | AAN358 | AAO472 |
| PRD-63117-036 | | | | | | AAN358 | |
| PRD-63117-037 | | | | | | AAN358 | |
| PRD-63117-041 | | | | | AAM481 | AAN358 | |
| PRD-63117-042 | | | | | | AAN358 | |
</div>
Other firmwares
===============
<div style="overflow-x: scroll;" markdown="1">
| PRD-63118-003 | | AAM286 | | | | | AAN982 | | |
| PRD-63734-001 | | | | | AAM999 | | | AAO273 | AAO472 |
| PRD-63734-002 | | | | | AAM999 | | | AAO273 | AAO472 |
| PRD-63763-001 | AAL964 | | AAM625 | | | AAN358 | | | AAO472 |
| PRD-63764-001 | | | | AAM693 | | AAN358 | | | |
</div>
* `AAK831`, `AAL655` --- no OTA, use an Autoloader if available