{"id":1626,"date":"2016-10-19T22:08:22","date_gmt":"2016-10-19T20:08:22","guid":{"rendered":"http:\/\/eskerahn.dk\/?p=1626"},"modified":"2018-10-17T18:08:15","modified_gmt":"2018-10-17T16:08:15","slug":"blackberry-priv-ota-update-of-unlocked-att-finally-bonus-de-branded","status":"publish","type":"post","link":"https:\/\/eskerahn.dk\/?p=1626","title":{"rendered":"Blackberry Priv OTA update of unlocked AT&#038;T &#8211; FINALLY!  Bonus: DE-bloated!!"},"content":{"rendered":"<p>After many months of negotiations, BB and AT&amp;T have FINALLY found a solution so the users of AT&amp;T branded devices can get the newest updates without being connected to the AT&amp;T network. \ud83d\ude42<\/p>\n<p><a href=\"https:\/\/eskerahn.dk\/?p=1626\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-1627\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/Screenshot_20161019-173127-169x300.png\" alt=\"screenshot_20161019-173127\" width=\"169\" height=\"300\" srcset=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/Screenshot_20161019-173127-169x300.png 169w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/Screenshot_20161019-173127-84x150.png 84w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/Screenshot_20161019-173127-768x1365.png 768w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/Screenshot_20161019-173127-576x1024.png 576w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/Screenshot_20161019-173127.png 1440w\" sizes=\"auto, (max-width: 169px) 100vw, 169px\" \/><\/a><a href=\"https:\/\/eskerahn.dk\/?p=1626\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-1104\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/11\/blackberry-priv-overview1-175x300.jpg\" alt=\"blackberry-priv-overview[1]\" width=\"175\" height=\"300\" srcset=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/11\/blackberry-priv-overview1-175x300.jpg 175w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/11\/blackberry-priv-overview1-88x150.jpg 88w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/11\/blackberry-priv-overview1-597x1024.jpg 597w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/11\/blackberry-priv-overview1.jpg 700w\" sizes=\"auto, (max-width: 175px) 100vw, 175px\" \/><\/a><\/p>\n<p><!--more-->Blackberry have posted an official statement on the case here <a href=\"http:\/\/support.blackberry.com\/kb\/articleDetail?articleNumber=000038204\" target=\"_blank\" rel=\"noopener\">http:\/\/support.blackberry.com\/kb\/articleDetail?articleNumber=000038204<\/a><\/p>\n<p>Previous to get OTA update you had to be connected to the AT&amp;T network (An AT&amp;T sim was NOT enough).<\/p>\n<p>You could (and can still) wipe the phablet and start from scratch with the newest autoloader that can be found here: <a href=\"http:\/\/ca.blackberry.com\/support\/smartphones\/Android-OS-Reload.html\" target=\"_blank\" rel=\"noopener\">http:\/\/ca.blackberry.com\/support\/smartphones\/Android-OS-Reload.html<\/a><\/p>\n<p>&nbsp;<\/p>\n<p>(We can only hope for the Verizon users that they will find a similar solution too soon)<\/p>\n<p>&nbsp;<\/p>\n<p>I wiped the phablet with AAG873 just a few days ago, so being of a curious nature I wiped it again with last months AAG202 (that I luckily kept)<\/p>\n<p>And LOOK AND BEHOLD after AAG202 finished installing, it asked me if I wanted it to update OTA\u00a0 <img src=\"https:\/\/eskerahn.dk\/wordpress\/wp-includes\/images\/smilies\/mrgreen.png\" alt=\":mrgreen:\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" \/><\/p>\n<p>And believe it or not, by accepting this the phablet also gets <del>DE-BRANDED<\/del> DE-BLOATED and is now on AGG8<strong>5<\/strong>3. <span style=\"color: #999999;\">(Generic software on branded hardware)<\/span><br \/>\nThat is <span style=\"text-decoration: underline;\">without<\/span> all the nasty AT&amp;T bloat of AAG8<strong>7<\/strong>3. <a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-389\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\" alt=\"konservativ_woot\" width=\"32\" height=\"27\" \/><\/a><a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-389\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\" alt=\"konservativ_woot\" width=\"32\" height=\"27\" \/><\/a><a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-389\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\" alt=\"konservativ_woot\" width=\"32\" height=\"27\" \/><\/a><a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-389\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\" alt=\"konservativ_woot\" width=\"32\" height=\"27\" \/><\/a><a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-389\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\" alt=\"konservativ_woot\" width=\"32\" height=\"27\" \/><\/a><a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-389\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2010\/07\/konservativ_woot.gif\" alt=\"konservativ_woot\" width=\"32\" height=\"27\" \/><\/a><\/p>\n<p>I felt especially unsafe about &#8220;<em>AT&amp;T Remote Support<\/em>&#8220;. But was not too happy about neither &#8220;<em>Device Health Application<\/em>&#8221; nor &#8220;<em>Enterprise Management Client<\/em>&#8221; &#8211; I had no idea what either of these did or could potentially do&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>This is the bloat I got rid off<\/p>\n<p><a href=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/BlackBerry_Priv_BLOAT_ATandT.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-1657\" src=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/BlackBerry_Priv_BLOAT_ATandT-1024x702.png\" alt=\"blackberry_priv_bloat_atandt\" width=\"640\" height=\"439\" srcset=\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/BlackBerry_Priv_BLOAT_ATandT-1024x702.png 1024w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/BlackBerry_Priv_BLOAT_ATandT-150x103.png 150w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/BlackBerry_Priv_BLOAT_ATandT-300x206.png 300w, https:\/\/eskerahn.dk\/wp-content\/uploads\/2016\/10\/BlackBerry_Priv_BLOAT_ATandT-768x527.png 768w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/p>\n<p>A not complete objective observation is that I feel it got a better stamina as well. Especially less consumption over night is quite visible.<br \/>\nIt COULD be that some of the stuff that could not be disabled (even though not waking the phablet for a lengthy period at a time so it could be seen as visible usage), still pulled it out of DOZE?<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>ADD I<\/strong><\/span><\/p>\n<p>They have updated the post further, with a guide to POLL for it (std. Android), if you do not get it automatically:<\/p>\n<h3 id=\"Additional_InformationHeader\" class=\"article-section-header dropdown-toggle\"><a href=\"http:\/\/support.blackberry.com\/kb\/articleDetail?articleNumber=000038204#Additional_InformationContent\" target=\"_blank\" rel=\"noopener\" data-toggle=\"collapse\">Additional Information<\/a><\/h3>\n<div id=\"Additional_InformationContent\" class=\"collapse in\">\n<div class=\"article-field-content\">\n<p>Should the update not show within the Notification\u00a0shade, perform a manual Check-In. To perform the Check-In, complete the following;<\/p>\n<ol>\n<li>Open the <b>Phone<\/b> app.<\/li>\n<li>Type <b>*#*#CHECKIN#*#* <\/b>(<b>*#*#2432546#*#*<\/b>)\n<ul>\n<li><b>checkin succeeded<\/b> will show within the <b>Notification <\/b>shade when successful<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>ADD II<\/strong><\/span><\/p>\n<p>I noted that T-mobile shares the build number with the generic one on <a href=\"http:\/\/ca.blackberry.com\/support\/smartphones\/Android-OS-Reload.html\" target=\"_blank\" rel=\"noopener\">the download page<\/a> , but neither the filename nor the hash is identical.<br \/>\nSo thought that perhaps the AAG853 I got might not be a totally generic one either&#8230; So tried to apply the generic autoloader of AAG853 (again) and it does (still) NOT fit (my emphasizing).<\/p>\n<p style=\"padding-left: 30px;\">&#8220;Loader is not valid for this device variant, the device <span style=\"color: #ff0000;\">variant detected is <strong>att<\/strong>.<\/span><br \/>\nPlease obtain a loader which supports the device variant above and try again.<br \/>\nPress any key to close this window&#8221;<\/p>\n<p>So the device is NOT made generic, but have only graciously been allowed to fetch unbranded updates OTA (for now?). We thus could risk this not lasting AND we have <strong>no<\/strong> autoloader for the actual version on the device to save for later use&#8230;<\/p>\n<p>Being curious of nature, I also tried to download the tmo-variant and poked into the differences of the two autoloaders for AAG853 we got, and apart from quite different &#8220;oem.img&#8221; (not unexpected), the ONLY differences lies in the two 208 bytes small .sig files (<span style=\"text-decoration: underline;\">sig<\/span>nature I assume). And in the test code in the loaders that check for different device IDs.<\/p>\n<p style=\"padding-left: 30px;\"><span style=\"font-size: 8pt;\">***** DOWNLOADS\\BBRY_QC8992_AUTOLOADER_USER-<strong><span style=\"color: #ff0000;\">NA-TMO<\/span><\/strong>-AAG853\\flashall.bat<\/span><br \/>\n<span style=\"font-size: 8pt;\">set devname=%devname: =%<\/span><br \/>\n<span style=\"font-size: 8pt;\">if not &#8220;%devname%&#8221; == &#8220;<span style=\"color: #ff0000;\"><strong>tmo<\/strong><\/span>&#8221; (<\/span><br \/>\n<span style=\"font-size: 8pt;\">\u00a0GOTO ERRORMSG<\/span><br \/>\n<span style=\"font-size: 8pt;\">***** DOWNLOADS\\BBRY_QC8992_AUTOLOADER_USER-<span style=\"color: #ff0000;\"><strong>COMMON<\/strong><\/span>-AAG853\\flashall.bat<\/span><br \/>\n<span style=\"font-size: 8pt;\">set devname=%devname: =%<\/span><br \/>\n<span style=\"font-size: 8pt;\">if not &#8220;%devname%&#8221; == &#8220;&#8221; (<\/span><br \/>\n<span style=\"font-size: 8pt;\">\u00a0GOTO ERRORMSG<\/span><br \/>\n<span style=\"font-size: 8pt;\">*****<\/span><\/p>\n<p style=\"padding-left: 30px;\"><span style=\"font-size: 8pt;\">***** DOWNLOADS\\BBRY_QC8992_AUTOLOADER_USER-<span style=\"color: #ff0000;\"><strong>NA-TMO<\/strong><\/span>-AAG853\\flashall.sh<\/span><br \/>\n<span style=\"font-size: 8pt;\">read_dev=$(echo ${read_dev} | sed &#8216;s\/[[:space:]]\/\/g&#8217;);<\/span><br \/>\n<span style=\"font-size: 8pt;\">if [ &#8220;<span style=\"color: #ff0000;\"><strong>tmo<\/strong><\/span>&#8221; != &#8220;${read_dev}&#8221; ]; then<\/span><br \/>\n<span style=\"font-size: 8pt;\">if [ &#8220;&#8221; == &#8220;${read_dev}&#8221; ]; then read_dev=common; fi<\/span><br \/>\n<span style=\"font-size: 8pt;\">***** DOWNLOADS\\BBRY_QC8992_AUTOLOADER_USER-<strong><span style=\"color: #ff0000;\">COMMON<\/span><\/strong>-AAG853\\flashall.sh<\/span><br \/>\n<span style=\"font-size: 8pt;\">read_dev=$(echo ${read_dev} | sed &#8216;s\/[[:space:]]\/\/g&#8217;);<\/span><br \/>\n<span style=\"font-size: 8pt;\">if [ &#8220;&#8221; != &#8220;${read_dev}&#8221; ]; then<\/span><br \/>\n<span style=\"font-size: 8pt;\">if [ &#8220;&#8221; == &#8220;${read_dev}&#8221; ]; then read_dev=common; fi<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><strong>ADD III<\/strong><\/p>\n<p>I took the liberty and pushed up an AT&amp;T version AAO486 that is NOT the latest AT&amp;T AAQ289 to the cloud (plus some others).<br \/>\nSee <a href=\"https:\/\/eskerahn.dk\/?p=2110\" target=\"_blank\" rel=\"noopener\">https:\/\/eskerahn.dk\/?p=2110<\/a><br \/>\nAfter installing any AT&amp;T Autoloader, the device WILL be re-bloated, BUT if it has been whitelisted for clean updates by AT&amp;T, it <em>should<\/em> be offered an OTA upgrade to AAQ280, debloating it (I have NOT tested this since AAG202 though, and have not found this confirmed nor refuted).<\/p>\n<p>&nbsp;<\/p>\n<p><strong>ADD IV, 2018-05-22<br \/>\n<\/strong><\/p>\n<p>It is unclear whether the &#8216;white listing&#8217; were a &#8216;one of&#8217; for devices that were already activated on nets outside AT&amp;T at the time back in autumn 2016 it was announced, or if it goes for all AT&amp;T Privs that never have been on AT&amp;T. That is, it is unclear if it is a fixed list made back then, or a rule applied. From a comment below it seems that it could be a fixed list.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After many months of negotiations, BB and AT&amp;T have FINALLY found a solution so the users of AT&amp;T branded devices can get the newest updates without being connected to the AT&amp;T network. \ud83d\ude42<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-1626","post","type-post","status-publish","format-standard","hentry","category-phonesphablets"],"_links":{"self":[{"href":"https:\/\/eskerahn.dk\/index.php?rest_route=\/wp\/v2\/posts\/1626","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/eskerahn.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eskerahn.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eskerahn.dk\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/eskerahn.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1626"}],"version-history":[{"count":8,"href":"https:\/\/eskerahn.dk\/index.php?rest_route=\/wp\/v2\/posts\/1626\/revisions"}],"predecessor-version":[{"id":2641,"href":"https:\/\/eskerahn.dk\/index.php?rest_route=\/wp\/v2\/posts\/1626\/revisions\/2641"}],"wp:attachment":[{"href":"https:\/\/eskerahn.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1626"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eskerahn.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1626"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eskerahn.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1626"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}