mbirth/tcl_ota_check
1
0
Fork 0
mirror of https://github.com/mbirth/tcl_ota_check.git synced 2024-11-09 22:06:47 +00:00
Code Issues Releases Wiki Activity
47 Commits 2 Branches 0 Tags 277 KiB
Python 100%
e8d2e8f396
Go to file
Markus Birth e8d2e8f396
Today's OTAs.
2017-09-23 15:20:06 +02:00
.gitignore add OS version to header name 2017-09-07 12:54:17 -04:00
prds.txt Today's OTAs. 2017-09-23 15:20:06 +02:00
README.md More explanation in README. 2017-09-17 20:51:50 +02:00
tclcheck_all.py Added latest OTA version to prds.txt, modified new OTA check to use that 2017-09-19 17:12:01 +02:00
tclcheck_allfull.py Added latest OTA version to prds.txt, modified new OTA check to use that 2017-09-19 17:12:01 +02:00
tclcheck_allota.py Added latest OTA version to prds.txt, modified new OTA check to use that 2017-09-19 17:12:01 +02:00
tclcheck.py add OS version to header name 2017-09-07 12:54:17 -04:00
tcllib.py Throw human readable exception for 404 errors. 2017-09-12 21:39:37 +02:00

README.md

TCL OTA Check

This is a Python script originally created by thurask (original GIST) to check for update files for a BlackBerry KEYone phone. It tries to emulate the requests done by the "Updater" app or the "Mobile Q Loader" firmware updater.

What is a FOTA/OTA?

(F)OTA = (Firmware) Over-the-Air

OTAs are differential(!) updates for a specific firmware version to a newer one. To install it, you must have the correct initial firmware installed. Otherwise, the updater script will fail and abort the update.

How to find available OTA updates

After downloading or cloning the repository, edit the tclcheck_all.py and change the fc.fv 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"

Also change the fc.mode line to:

fc.mode = fc.MODE_OTA

Now run the script. You'll get an output like this:

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.

You can use this info, to install the update for a different variant. Just make sure to use a variant that has the same model number (63117 = BBB100-2).