Android 4.2.2-based CyanogenMod 10.1 M2 builds now available for two dozen devices

by: AdrianMarch 5, 2013


Just a little over a month after releasing the first milestone 10.1 builds, CyanogenMod has yesterday made a bunch of new M ports available. The M2 releases are up for grabs for over 20 devices (more if you count the different models and configurations), all of which can get a taste of Android 4.2.2 Jelly Bean early. Huzzah!

Unlike manufacturers and carriers, the brilliant CM team continues to spread its love around regardless of the “social status” of phones and tabs. You can therefore flash a 4.2-based port on aristocrats like the Samsung Galaxy S3, Nexus 10 or HTC One X, on the bourgeois Galaxy Tab 2 7.0 and HTC One S, but also on the proletarian Galaxy S and Nexus S.

But here’s the full list of devices receiving CM 10.1 M2 releases:

  • Acer Iconia a700
  • Google Nexus S (crespo, crespo4g)
  • Google Nexus 7 (grouper, tilapia)
  • Google Galaxy Nexus (toro, toroplus, maguro)
  • Google Nexus 4 (mako)
  • Google Nexus 10 (manta)
  • Google Nexus Q (steelhead)
  • Hardkernel Odroid-U2
  • HTC One X (evita)
  • HTC Incredible 4G LTE (fireball)
  • HTC Evo 4G LTE (jewel)
  • HTC One S (ville)
  • LG Nitro HD (p930)
  • LG Optimus LTE (su640)
  • LG Spectrum (vs920)
  • Samsung Galaxy S (captivatemtd, galaxysbmtd, galaxysmtd, epicmtd)
  • Samsung Galaxy SII (i9100g, hercules, skyrocket)
  • Samsung Galaxy SIII (US variants d2att, d2cri, d2mtr, d2spr, d2tmo, d2vzw)
  • Samsung Note (quincytmo, quincyatt)
  • Samsung Galaxy Tab 2 7.0 (p3100, p3110)
  • Samsung Galaxy Tab 2 10.1 (p5100, p5110)

Several other gadgets, including the Kindle Fire, are having M2 ports worked on, so even if you can’t find your device on the above list you shouldn’t fall into despair… yet.

Also, as a quick reminder, let’s mention that M-Series sit somewhere in between nightly builds and RC (release candidates) in the grand scheme of CM ports. Basically, they’re stable enough to be used on a daily basis, but some small kinks might need ironing out before CyanogenMod can call the firmwares final.

If that sounds like something you’d be interested in, start by rooting your device, then back up your data and head on to CM’s servers where you’ll be able to easily identify the new ports by the “cm-10.1-M2” tag. Also, let us know how everything works out, and, if there any bugs to report, this is where you’ll want to “complain”.

  • Harjifangki

    After i update my first M-build CyanogenMod from the built in updater (Settings->about phone->CyanogenMod), do i have to re-flash the newest version of Gapps?

    • Louka Menard

      Yes. Gapps do not update themselves you know!

  • MasterMuffin

    I read “sIII” and screamed like a little girl byt than I read “USA”…. FUUUUUUU exynos >.<

    • Same here, I’m tired of waiting for the release for the international Galaxy SII (with Exynos), though I am still receiving new nightlies…

      • MasterMuffin

        Seriously Samsung, Y U NO like devs anymore :(

  • Thomas Houlberg

    Yes, you’ll have to re-flash gapps. I forgot that part and was met by a flood of errors after booting up.

    • Vasilis Kourtis

      I have’t flashed gapps on my nexus S (from N1 to N2) and had no problem.

      • Shane

        you only have to re-flash gapps if you want the latest gapps updates.

  • I wish I knew how to create ROMs. my Chinese phone running on 4.0.4 and a MediaTek MT6577 processor isn’t close to being supported by CM.

  • WFerreira

    After update, can’t make or receive calls, is no signal or carrier. Bluetooth doesn’t connect and have random reboots. The latest build I can use is nightly 022613, otherwise same problem. :(

    • Drew Rick

      This is useless if you don’t specify your device.

      • WFerreira

        Sorry! I got a At&t Samsung GS2Skyrocket i727.
        Just get it working doing a factor y reset and reinstalled gaaps 030113 and it works fine! I guess was the dirty flash to blame. Stable so far :]

  • How long until the n7100 GNote 2?