Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

How Do I Update Cyanogenmod?


  • This topic is locked This topic is locked
2 replies to this topic

#1 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 26 June 2013 - 06:26 PM

CyanogenMod is ever evolving. There are new builds put out almost every night that contain the changes made to the codebase throughout the day. Because of this, there will always be updates you can install on your device (although, not all of them are in the “stable” category). The CyanogenMod team has made it super easy for people to keep their devices up-to-date since CM 10.0.

You can easily update your device to the latest version (either the bleeding-edge nightly builds or “stable” milestone, release candidate, and/or stable builds – you choose) by going to Settings -> About Phone -> CyanogenMod Updates. This will download the update, reboot into recovery, flash the update, and reboot you back to CM without any additional interaction. All apps are left intact, and no data is lost. Each build is a full release, and there is no need to update to each release to get to the latest one. If you are updating major versions (ie 10.0 to 10.1 or 10.1 to 10.2) please see below for instructions as they can differ a bit from normal updating.

You can also do this manually (which is required if you flash additional things like kernels), by downloading the update to your sdcard (from http://get.cm) and rebooting into recovery to flash the update (and any additional zips - although, if you have the gapps installed from http://goo.im/gapps, there is no need to reflash those).

Contrary to popular belief, there is no need to wipe ANYTHING when you update CM. This includes your cache partition, your dalvik cache, and your battery stats. While wiping these won’t hurt anything, you can increase the time it takes to boot up CM after you install the update. Android is smart enough to manage both your cache and dalvik cache without you intervening, and wiping your battery stats does absolutely nothing to help with your battery life (the file is only used to provide the raw information to provide the stats and graph in Settings -> Battery) – it is actually wiped automatically every time your device is charged to 100%.

How to Update From:

NOTE: It is not recommended to try updating more than one version at a time (eg. CM 10.0 to CM 10.2). Doing so can have unintended side effects and you should plan on things breaking. It is also not recommended to downgrade major versions (10.2 to 10.1). This can lead to bootloops or things breaking. If downgrading, it is highly recommended to perform a Factory Reset/Data Wipe.

See below for a quick explanation of the different builds available from http://get.cm.

Experimental
These builds are not meant for most users. They are typically used as to test a very specific change (usually indicated in the filename). Unless you know what the build is for and what it is supposed to do, it is recommended to not use these.

Nightly
These builds are highly experimental. They are the bleeding edge and it is possible for things to break. These are automated builds that are used to test whether the code added to the code base compiles properly. If it does compile, that’s a result. If it doesn’t compile, that is also a result. The CyanogenMod team releases these builds to the public to allow them to see the progress made. Usually these builds work great and many people use them as “daily drivers”. However, due to the raw nature and the fast-paced development environment of CyanogenMod, things can go wrong. The dev team does not accept official bug reports for these because of the ongoing development.

(More info on nightlies here)

Note: Once a device is no longer supported in the latest CM version, the “nightlies” may turn into “weeklies”, “monthlies”, or “whenever there are changes in the code”.

M Snapshot
The M Snapshot is a milestone build typically released around once a month. These builds are separated from the normal development environment to provide a build that is more likely to be stable. These are the first builds the team wants to get feedback from the masses. Because of this, these are the first builds you are able to submit bug reports on the official CyanogenMod project manager, https://jira.cyanogenmod.org. Make sure you get a logcat (instructions are in the wiki) and you follow the instructions to properly submit a bug report.

Release Candidate
Once the team feels development is at a stable point, the team will put out a release candidate. This is a build that the CM team feels is worthy to be released to the public. However, the public always seems to have a knack to find the bugs that the CM team couldn’t find. As bugs come in, they get fixed and if there were enough things fixed, the CM team will introduce another release candidate until the CM team feels that they are ready for the stable release.

Stable
Once a build has gone through all the development and testing phases, the CM team will release the stable builds. After a stable is released, the team goes back to developing nightlies. It is an ongoing process and will always allow you to see the progress that is being made.



If you have any suggestions for improvements or changes to make this post better, or have an idea for a different topic to be covered in the FAQs subforum, please suggest it here.

#2 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 27 June 2013 - 06:10 PM

Update from 10.0 to 10.1


If you DON'T use the Google Apps addon (gapps), just use the built-in updater located under Settings -> About Phone -> CyanogenMod Updates.

If you DO use gapps, it is recommended you apply the update manually in recovery, because you need to flash an updated gapps package. Google made the Android 4.1 gapps incompatible with Android 4.2, so if you do the normal update, you will lose all your Google support. To update it manually, download the stable version of 10.1 from http://get.cm and the latest gapps for Android 4.2 from http://goo.im/gapps (as of this writing it is the 20130301 zip). Then reboot into recovery and install CM first, then the gapps zip. After that, reboot. There is no need to wipe anything in recovery, including cache and dalvik. If you run into issues with certain Google apps like gmail or youtube, try to uninstall them and then reinstall them from the Play Store.

Once you are up and running on CyanogenMod 10.1, you can use the built-in updater to update to whatever version you want (whether you want to stick with the stable or nightly releases is up to you).

If you use custom addons (like 3rd-party kernels), you need to always update manually. The built-in updater does not provide any way to flash the additional zips. You should only need to flash the gapps package once, because CM will keep the files when updating.



If you have any suggestions for improvements or changes to make this post better, or have an idea for a different topic to be covered in the FAQs subforum, please suggest it here.

#3 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 14 August 2013 - 07:53 PM

Update from 10.1 to 10.2


If you DON'T use the Google Apps addon (gapps), just use the built-in updater located under Settings -> About Phone -> CyanogenMod Updates.

If you DO use gapps, it is recommended you apply the update manually in recovery, because you need to flash an updated gapps package. Google made the Android 4.2 gapps incompatible with Android 4.3, so if you do the normal update, you will lose all your Google support. To update it manually, download CM 10.2 from http://get.cm and the latest gapps for Android 4.3 from http://goo.im/gapps (as of this writing it is the 20130813 zip). Then reboot into recovery and install CM first, then the gapps zip. After that, reboot. There is no need to wipe anything in recovery, including cache and dalvik. You should only need to flash the gapps package once, because CM will keep the files when updating.

Once you are up and running on CyanogenMod 10.2, you can use the built-in updater to keep yourself up-to-date.

If you use custom addons (like 3rd-party kernels), you need to always update manually. The built-in updater does not provide any way to flash the additional zips.

NOTES
  • If you run into issues with certain Google apps like gmail or youtube, try to uninstall them and then reinstall them from the Play Store.
  • If you continue to have issues with Google apps, remove your account and re-add it. Settings -> Google -> your_account -> Menu -> Remove Account
  • If your phone icon doesn't work on your dock and complains that the App is not installed, don't fret. The internal shortcut for the phone app changed due to changes in Android 4.3. Just press and hold on the icon and then fling it off the screen to remove it. Then go to your app drawer, press and hold on the Phone icon and then drag and drop it back on the dock.
  • If you are having trouble with apps detecting root, you need to change Root Access to Apps and ADB under Settings -> Developer Options. If you don't have Developer Options, enable developer mode by tapping on Build Number 7 times under Settings -> About Phone/Tablet. You may need to reboot your device for this to take effect.
  • For those Nexus devices that had the Photosphere camera and the gallery that synced with Picasa/Google+ albums (or the other users who want it on their device, although, photosphere may not work), the new gapps does not contain this combined app anymore (likely due to the fact that CM now contains the new Focal app which has Photosphere-like abilities). You can get the Photosphere camera and Picasa/Google+ syncing gallery back by flashing the Photosphere Camera 4.3 zip from BaNkS. This should be like the gapps package where it only needs to be flashed once. It will remove the stock gallery/camera (along with any modifications CM made to it) and install the Google versions of the apps and it should automatically stay when you do system updates. This will not affect Focal.

If you continue to have issues, it may be that a corrupted database or app is causing the problem. If so, you may need to perform a Factory Reset/Data Wipe to clear up your other issues.



If you have any suggestions for improvements or changes to make this post better, or have an idea for a different topic to be covered in the FAQs subforum, please suggest it here.