Many OnePlus One owners still love their phone and have no need to upgrade outside of having a relatively current version of Android for security and stability. OnePlus has released a handful of new models since the original One release, and updates, although pretty delayed, were still coming to get the official shipping OS up to snuff. Sure, OnePlus and Cyanogen parted ways in 2015 and OnePlus developed OxygenOS as the mainstay OS for all their US phones.
This uneasy but stable situation all changed when Cyanogen announced they were shutting=down in December 2016. I snagged the last build and posted it for download on this post.
- You need to know what you are doing with adb, flashing recovery, etc. If you work this and don’t know what you are doing, you will kill your phone.
- Android Pay and other services that rely on SafetyNet will not work on the unsigned build.
- You’ll get Android 7.1.1 and it is actually quite stable, but it still is a nightly build.
Here are the download links:
There are lots of sites listing the countries of the world, but nothing that provides a quick list view for insert for use in application development. Here is one I just did based off the current list towards the end of 2016.
|Antigua and Barbuda|
|Bosnia and Herzegovina|
|Central African Republic|
|Cocos (Keeling) Islands|
|Congo, Republic of (Brazzaville)|
|Democratic Republic of the Congo (Kinshasa)|
|East Timor (Timor-Leste)|
|Iran (Islamic Republic of)|
|Korea, Democratic People’s Rep. (North Korea)|
|Korea, Republic of (South Korea)|
|Lao, People’s Democratic Republic|
|Macedonia, Rep. of|
|Micronesia, Federal States of|
|Moldova, Republic of|
|Northern Mariana Islands|
|Papua New Guinea|
|Saint Kitts and Nevis|
|Saint Vincent and the Grenadines|
|Sao Tome and Principe|
|Slovakia (Slovak Republic)|
|Syria, Syrian Arab Republic|
|Taiwan (Republic of China)|
|Tanzania; officially the United Republic of Tanzania|
|Timor-Leste (East Timor)|
|Trinidad and Tobago|
|Turks and Caicos Islands|
|United Arab Emirates|
|Vatican City State (Holy See)|
|Virgin Islands (British)|
|Virgin Islands (U.S.)|
|Wallis and Futuna Islands|
I had a heck of a time getting the AT&T Software Update OTA going on my wife’s Samsung Galaxy S5 (SAMSUNG-SM-G900A). Apparently, on AT&T images, they put a check in place on the software update to limit/inhibit multiple checks based on a timeframe. The phone did not have enough storage space on the device memory to handle the download on the first check, so we moved apps and data around to clear 3gb or so for the 2gb or so download of Android 6 and then wanted to start the update. But, you cannot just go in and run the software update again and trigger the update. There is no way to restart the updater application either to get it to recognize we had space this time. Frustrating.
Anyway, thankfully, I found this in the AT&T forums that suggests messing with the device date to get around this. I guess AT&T uses local device time to limit the request again to initiate the software update. If you take your phone off automatic date and time settings and kick the device ahead a day, the software update application resident on the phone will validate that the update can now happen. We moved the device date from Saturday to Sunday and we got the download going.
Crazy they inhibit updates in this manner, but fooling the date and time seems to do the trick.
Posting this purely for my own benefit so when I ask people if they want a sandwich when I go to Golden Gate Deli, I can point them here since there is nothing accurate on the web currently for their sandwich menu.