CyanogenMod Installer

Common questions

• Why flash CyanogenMod?
  • There are many reasons to consider for flashing your device. Check out our Why Mod? page for more info!
• Do I need to root my phone before installing?
  • No. You can have a rooted phone, or not. The installer doesn’t care. However, to be in a supported configuration, you need to be running a stock ROM.
• Do I need to unlock my bootloader first?
  • No, you don’t. If your bootloader is locked, we’ll unlock it for you.
• Can I install if I’m running a custom ROM?
  • Provided the installer can identify your phone correctly, it doesn’t matter which ROM you’re running. Again, to be in a fully supported configuration, you should be running a stock ROM. If you’re already running a custom ROM, you probably know what you’re doing.
• What build type of CyanogenMod is installed with the installer?
  • The installer uses a stable snapshot build unique to the installer. These are stable builds designed to provide all core features and functionality of the device.
• How do I get updates?
  • Updates are done via Settings > About phone > System Updates. When a new snapshot build is avaialable, your will also receive a notification. Devices flashed via the installer will only get updates when a new stable snapshot build is available.
• Can I update to a nightly build?
  • If you are feeling adventurous, sure. You will need to go to device page and download the zip file for your device. Save the zip to your SDCARD and you can install via Recovery. You may need to wipe cache and data after installing via recovery.
• How do I get back to stock?
  • You may perform a full backup from recovery, after flashing recovery (you will have to do this manually, at the moment) and then copy it off the device, if you don’t have an external sdcard. If you’ve already run the installer, you will have to find stock images and flash them using fastboot or Odin.

Before you start

• Back up your data!
• Back up your data. Did I say this already? Backups made in recovery are not safe unless they are made to a true external sdcard. If you want to go back to stock, make preparations for doing so before running the installer.
• Use a high-quality USB cable. A cable that works for charging won’t necessarily work reliably for data transfer. The OEM cable that came with your phone should be a good choice, but if the connector has been stressed often enough almost any cable can become unreliable.
• Don’t move your phone while installing. After you click ‘Install’, unless you need to unlock your bootloader or interact with the phone for some reason, leave it on a level surface with as little strain on the USB cable as possible until the install is complete.
• Charge your battery. Don’t attempt the install with a partially drained battery.
• Don’t use a USB hub. Plug your cable directly into a port on the workstation.
• Disable any anti-virus software for the duration of the install.

Supported Devices

Code Name	Device	Windows	Mac	Latest installer build
crespo	Google Nexus S	Yes	Yes	11.0-InstallerXNPQ08Q
crespo4g	Google Nexus S 4G	Yes	Yes	10.1-InstallerBeta3
d2att	Samsung Galaxy S III (AT&T)	Yes	Yes	11.0-InstallerXNPQ09Q
d2can	Samsung Galaxy S III (Canadian)	Yes	No	11.0-InstallerXNPQ09Q
d2spr	Samsung Galaxy S III (Sprint)	Yes	Yes	11.0-InstallerXNPQ09O
d2tmo	Samsung Galaxy S III (T-Mobile)	Yes	Yes	11.0-InstallerXNPQ09O
d2usc	Samsung Galaxy S III (US Cellular)	Yes	Yes	11.0-InstallerXNPQ09O
d2cri	Samsung Galaxy S III (Cricket)	Yes	Yes	11.0-InstallerXNPQ09O
deb	Google Nexus 7 2013 (LTE)	Yes	Yes	11.0-InstallerXNPQ25S
flo	Google Nexus 7 2013 (WiFi)	Yes	Yes	11.0-InstallerXNPQ25S
grouper	Google Nexus 7 (WiFi)	Yes	Yes	11.0-InstallerXNPQ25S
hammerhead	Google Nexus 5	No	Yes	11.0-InstallerXNPQ25S
hercules	Samsung Galaxy S II Hercules	Yes	No	10.2-InstallerWPPQ50S
i9100	Samsung Galaxy S II (Intl)	Yes	Yes	10.2-InstallerWPPQ50S
i9300	Samsung Galaxy S III (Intl)	Yes	Yes	11.0-InstallerXNPQ08Q
jfltecan	Samsung Galaxy S4 (Canada)	Yes	Yes	11.0-InstallerXNPQ09O
jfltecri	Samsung Galaxy S4 (Cricket)	Yes	Yes	11.0-InstallerXNPQ09O
jfltecsp	Samsung Galaxy S4 (C Spire)	Yes	Yes	11.0-InstallerXNPQ09O
jfltespr	Samsung Galaxy S4 (Sprint)	Yes	Yes	11.0-InstallerXNPQ09O
jfltetmo	Samsung Galaxy S4 (T-Mobile)	Yes	Yes	11.0-InstallerXNPQ09O
jflteusc	Samsung Galaxy S4 (US Cellular)	Yes	Yes	11.0-InstallerXNPQ09O
jfltexx	Samsung Galaxy S4 (Intl)	Yes	Yes	11.0-InstallerXNPQ09O
l900	Samsung Galaxy Note II (Sprint)	Yes	Yes	10.2-InstallerWPPQ50S
m7att	HTC One (AT&T)	Yes	Yes	11.0-InstallerXNPQ08Q
m7spr	HTC One (Sprint)	Yes	Yes	11.0-InstallerXNPQ08Q
m7tmo	HTC One (T-Mobile)	Yes	Yes	11.0-InstallerXNPQ08Q
m7ul	HTC One (Unlocked)	Yes	Yes	11.0-InstallerXNPQ08Q
maguro	Google Galaxy Nexus (GSM)	Yes	Yes	11.0-InstallerXNPQ25S
mako	Google Nexus 4	Yes	Yes	11.0-InstallerXNPQ25S
manta	Google Nexus 10	Yes	Yes	11.0-InstallerXNPQ25S
n7000	Samsung Galaxy Note (Intl)	Yes	Yes	10.2-InstallerWPPQ50S
n7100	Samsung Galaxy Note II (GSM)	Yes	Yes	10.2-InstallerWPPQ50S
quincyatt	Samsung Galaxy Note (AT&T)	Yes	No	10.1-InstallerBeta3
quincytmo	Samsung Galaxy Note (T-Mobile)	Yes	No	10.1-InstallerBeta3
skyrocket	Samsung Galaxy S II Skyrocket	Yes	No	10.2-InstallerWPPQ50S
t0lte	Samsung Galaxy Note II (GSM LTE)	Yes	Yes	11.0-InstallerXNPQ08Q
t0lteatt	Samsung Galaxy Note II (AT&T)	Yes	Yes	10.2-InstallerWPPQ50S
t0ltetmo	Samsung Galaxy Note II (T-Mobile)	Yes	Yes	10.2-InstallerWPPQ50S
t769	Samsung Galaxy S II (T-Mobile)	Yes	No	10.2-InstallerWPPQ50S
tilapia	Google Nexus 7 (GSM)	Yes	Yes	10.2-InstallerWPPQ50S
toro	Google Galaxy Nexus (Verizon)	Yes	Yes	11.0-InstallerXNPQ25S
toroplus	Google Galaxy Nexus (Sprint)	Yes	Yes	11.0-InstallerXNPQ25S

as of 2014-03-05

The full list of supported ro.product.device values:
crespo
crespo4g
d2att
d2can
d2cri
d2spr
d2tmo
d2usc
deb
flo
grouper
GT-I9100
GT-I9100M
GT-I9100P
GT-I9100T
GT-I9300
GT-N7000
hammerhead
hercules
i9100
i9300
jflte
jfltecan
jfltecri
jfltecsp
jfltespr
jfltetmo
jflteusc
jfltexx
jgedlte
m0
m7
m7att
m7spr
m7tmo
m7ul
m7wls
maguro
mako
manta
n7000
n7100
quincyatt
SGH-I717
SGH-I727
SGH-T769
SGH-T879
SGH-T989
t03g
t0lte
t0lteatt
t0ltecan
t0ltespr
t0ltetmo
tilapia
toro
toroplus

If your device is not on this list, you will see an ‘unsupported device’ message.

Having trouble?

General troubleshooting

Device gets stuck booting at spinning CM logo animation, won’t boot all the way

• The installer lost communication during the install, usually due to a faulty USB cable or intermittent connection. You need to power down the phone, then boot it into recovery mode – different phones have different key combinations to boot into recovery. Search for “recovery mode + your phone model”, or find the manual installation instructions for your device on this wiki. Once you’re in recovery mode, you can either:

1. Perform a factory reset / data wipe manually from the recovery menu, and then reboot the phone, which will allow you to boot successfully.
2. Plug in your phone while it’s in recovery and restart the installer from the beginning and let it run through the install process again. Consider using a new USB cable.

Device not detected

• Is your device supported? Refer to the supported devices list above.
• Have you installed and run the Android app? It will prepare your device for installation. Run the Android app and follow the instructions.
• Try unplugging your device and plugging it into a different port. Windows will sometimes fail to recognize a device until it’s unplugged and replugged.
• Your USB cable may not be up to par.

‘We couldn’t talk to your phone’

• Disable your anti-virus. No, really, disable your anti-virus. It interferes with the tools we use to write your recovery partition, among other things. Make sure to disable it for long enough that the installer can complete the full installation.
• Plugging the phone into a different USB port and clicking ‘Try Again’ is often sufficient to proceed.
• If you have a USB hub or a docking station, try the installation without it. Unplug from the hub or docking station completely.
• If you get this repeatedly at different stages of the install, you almost certainly have a bad USB cable.
• If the installer doesn’t detect your device after a reboot, and it’s stuck in download mode, it’s generally safe to hold down power or remove the battery (if the phone allows it) to power the phone off. You may attempt the installation again, it may be successful.
• Disable the USB selective suspend setting in the Control Panel. It’s found under Power Options > Advanced Settings > USB settings.

USB not connecting after running the installer

• Some users are unable to see their device connected to their PC after installing CyanogenMod. This is most likely due to drivers not picking up the connected device in Windows.
• Plug your device in to the PC and open Device Manager on your PC.
• Look for unrecognized hardware (yellow triangle) and right click on the device. ‘Select Update driver software…’
• Next select ‘Browse my computer for driver software’
• select ‘Let me pick from a list of device drivers’
• Select ‘Android Device’ from the ‘Select your device’s type from the list below’ (if Android Device doesn’t work, you can also try ADB Interface)
• Select the driver you wish to try and click Next. This will attempt to install the driver.
• Click Finish to complete and check to see if your device is recognized by your PC.
• If these attempts fail, you may want to go to the manufactures website and download any driver utilities they have for your device.

Advanced troubleshooting

‘We couldn’t talk to your phone’ – Samsung devices ONLY

• If you have Kies installed, uninstall it. Reboot, and run the installer again.
  • On a Mac, even after reboot some Samsung kernel extensions may still be loaded. Open a terminal and find them with kextstat | grep -i samsung, then unload with sudo kextunload -b com.whatever.whatever.
• Make sure the USB connection uses PTP mode, not MTP
• If your Samsung device is still unable to communicate after using the general tips above, you can try to manually install the Download Mode driver.

1. Download the zadig file needed to install additional drivers from http://zadig.akeo.ie/
2. Once you have the file, place your phone in Download Mode. This can be achieved by one of the following methods:
   • ADB command (if you use the Android SDK) – adb reboot download
   • Using hardware key buttons. Power device down and use hard key combos to boot up (they vary by Samsung model): Volume Down + Home Button (depends on model) + Power Button. At the Warning!! screen hit the Volume up arrow. If this does not work for your model or you do not have a home button, Google is your friend.
   • Using the installer. The installer usually gives the error message and leaves the device in Download Mode. Leave the device in Download Mode and proceed to follow these instructions
3. With the Samsung device in Download Mode, plug it in to the PC.
4. Run the zadig executable file you downloaded from http://zadig.akeo.ie/
5. In zadig, select Options > List All Devices
6. From the drop down, look for your device to show as ‘Gadget Serial’ or ‘MSM8x60’ and select it.
7. In the drop down next to the green arrow are 3 options: WinUSB, libusbK, and libusb-win32. Try the first option, WinUSB, and click the Replace/Reinstall Driver button.
8. Open Device Manager in Windows. Look under ‘Universal Serial Bus devices’ and see if your device is now recognized by Windows. If not, repeat the previous step trying the one of the other two driver alternatives – libusbK and libusb-win32
9. Once you have a driver installed from zadig, you can reboot the Samsung device. Try the installer again. Now that you have manually applied the driver needed by the CyanogenMod Installer, it should recognize the device and no longer present the ‘We couldn’t talk to your phone’ error message.

• The last resort is to delete any drivers from Device Manager and start fresh. So with your device in download mode, and plugged in to USB, check Device Manager. Look through the USB devices to find your device (it will show up as ‘Gadget Serial’ or ‘MSM8x60’), right click on it and select the Uninstall device driver option to remove the driver. Reboot. Either simply run the installer again, or use Zadig to install the device driver and then run the installer.