Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it possible to check using shell whether or not Cyanogenmod is installed on a device?

In other words, something like uname -a (which tells the system Linux version and architecture).

Can the version be determined as well?

share|improve this question
up vote 5 down vote accepted

I tried to do uname -a on my CM10.1 (Samsung Galaxy S2) on the built-in Terminal app.

It returns:

Linux localhost 3.0.31-CM-g17c7b6e #1 SMP PREEMPT Tue Feb 19 01:11:17 PST 2013 armv71 GNU/Linux

Kernel version: 3.0.31-CM-g17c7b6e
SMP: Symmetric Multi-Processor support
PREEMPT: kernel preemption is enabled
Kernel date: Tue Feb 19 01:11:17 PST 2013
Processor: armv71

share|improve this answer
Can you explain the rest of the output? What is g17c7b6e, PREEMPT? – Kshitiz Sharma Feb 21 '13 at 10:52
@KshitizSharma See my updates. – geffchang Feb 21 '13 at 11:08
Umm, what if Android system is stock but kernel is of CM? Although it is not something we see everyday, I think uname -a might not be perfect but it's quite good! uname -a also might not be best if custom kernel is used and developer decided to tweak the name. – Firelord Jul 2 '15 at 18:20

Another way is to simply go to Settings→About phone, where you should see (depending on your CyanogenMod version) an item "CyanogenMod updates", and (with all CM versions) "CyanogenMod-Version":

About Phone: CM Stats and Kernel version About phone: CM version About phone: CM version (German)

share|improve this answer

In my CM12, I can do:

adb shell getprop | grep -i cyanogenmod

and the result it shows is:

[]: [cyanogenmod]
[ro.cmlegal.url]: []
[ro.error.receiver.system.apps]: [org.cyanogenmod.bugreport]
[ro.rommanager.developerid]: [cyanogenmod]

If you don't see cyanogenmod anywhere then either build.prop is deliberately tweaked to not display CM anywhere, or the device isn't running Cyanogenmod at all.

share|improve this answer
/etc/CHANGES.txt and /etc/CHANGELOG-CM.txt also can be considered. – Firelord Jul 2 '15 at 18:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.