Skip to main content

Updating OnePlusOne from 11S to 12S. (OnePlus One - India Version )

Updating OnePlus One from 11S to 12S. 

Downloads Required

Before we start.

  1. Ensure the OnePlus One is fully charged atleast 80%
  2. Verify that the phone is running on stock recovery and stock ROM.
  3. Back up if required, I did not back-up as all the data on my phone is stored on cloud. But the data was not affected by the Upgrade.

Initial Steps to update Android 5.0.2 based Cyanogen OS 12S ROM on OnePlus One using stock recovery.

  1. Download the official CM12S ROM for OnePlus One “cm-12.0-YNG1TAS0YL-bacon-signed.zip”
  2. Copy the downloaded file to the root folder of your phone’s internal storage. (0/ Drive)

Flashing the OTA via Stock Cyanogen recovery

  1. Power off your device.
  2. Reboot into stock recovery – Press and hold Power and Volume Down and release them when the OnePlus logo appears on screen.
  3. Choose Apply Update.
  4. Select Choose from internal storage.
  5. Select 0/ which is the internal storage.
  6. Choose the file cm-12.0-YNG1TAS0YL-bacon-signed.zip, which you downloaded earlier and let the installation begin.
  7. Wait until the ROM is flashed and then you will be seeing the Android Bot.
  8. After the installation is over, return to main page and perform wipe cache partition.
  9. Then hit Reboot system now.
 https://www.youtube.com/watch?v=vsV21r2Bq7I
 https://www.youtube.com/watch?v=c1bB13zN0q0
 http://www.ibtimes.co.uk/oneplus-one-gets-android-5-0-2-ota-update-via-cyanogen-os-12s-how-install-1496464
 http://www.latintimes.com/oneplus-one-update-manually-install-cyanogenmod-os-12-cm12-tutorial-309788
​
Labels:

Comments

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n
2 comments
Read more

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa
Post a Comment
Read more