Wiki Problems

Материал из CyanogenMod
Перейти к: навигация, поиск

This page is for reporting problems specific to the wiki.

While just about any content on this web site can be improved via direct edits (and we do encourage you to learn to fix things yourself), we understand that not everyone is comfortable editing a wiki. So, if you've identified content that needs to be altered (e.g. bad installation instructions, broken links, incorrect build procedure), report it here. To do so, press the edit button in the tab above. Don't worry-- editing this wiki page is reasonably safe and unlikely to break any other part of the site.

Please describe the issue in reasonable detail and include links to all relevant pages. If you have information that would solve the issue you've identified, please provide it as well. At the end of your report, paste the following code: --~~~~. That's two dashes (-) followed by four tildes (~). This code will automatically be replaced with your name and the date (a "signature") when you submit your edit.

If you are an experienced wiki-editor, you can help fix problems on this page. If you resolve an issue, please remove the report when you're finished. There is no need to post replies or any confirmation that the problem has been fixed. Instead, you can write on a user's Talk page to follow-up on a report.


Bad examples:

I couldn't get my Nexus 7 build working!
Build has broken wifi.

Good examples:

Grouper_Info: The kernel source code is actually located at, not
--Fattire (talk) 07:38, 8 December 2012 (UTC)
Install_CM_for_fireball: The button combination to enter the bootloader is Volume Down + Power, not Mash all buttons rapidly.
--Matt Mower (talk) 16:31, 17 February 2014 (UTC)

Known issues

The following issues have already been reported to the wiki webmaster:

  1. All links to are broken. This is being worked on, but will take time. [Updated 9 Jul 2014]
  2. If not logged in, the language often changes when navigating pages. If you are logged in to an account, your language preference is remembered.
  3. You cannot create an account with a launchpad OpenID

Report wiki issues below


Put new issues at the top! Add your name and a date by appending --~~~~ to the end of your report.

23 JUL 2014 - The wiki translation platform didn't save translations (I only tested in french). --EnderGeek

Template:device_honami 22 JUL 2014 - There is no mention of the C9606 model at all. --Mixahashi

Template:Install_CM_on_Sony It should be noted that if /data cannot be mounted during wipe data/factory reset formatting /data and /media should be selected in order to make it work. --Schwinni (talk) 22:52, 21 July 2014 (UTC)

stevep2007 July 19 2014 - The instructions for the Verizon LG G2 VS980 4.4.2 firmware VS98024A_ doesn't work. ioroot and freegee to support this firmware. So motivate I was to install stock Android I appleid work arounds until I really bricked my phone - but thats all part of the fun. Its restored to stock LG so I can try again.

Install_CM_for_vs980 is no longer valid with android 4.4.2 OTA update. I couldn't find a way to get cyanogenmod installed so I went with another rom instead. I'm sure it's possible just beyond my scope. Thanks --Baurge 15:43 UTC, 12 July 2014

Mondrianwifi Heimdall isn't supported for Samsung Tab Pro 8.4 and has an open issue for it being broken Github Heimdall issue #208. There is no clockworkmod recovery image for the tablet, there is however a TWRP one. --Ekes (talk) 15:52, 8 July 2014 (UTC)

v500 device template is woefully incomplete. --Matt Mower (talk) 18:27, 7 July 2014 (UTC)

All install instructions - there should be a general how-to for backing up and restoring roms using cwm or twrp recovery at the beginning of each device's installation instructions. --Matt Mower (talk) 17:09, 7 July 2014 (UTC)

Install_CM_for_jflte: Started with me installing 10.2.1 for my phone, but in the process I learned 2 things; we should advise users to backup their phone before installing, and we should consider informing them that it's irritating, if not impossible, to switch service to your Cyanogen'd phone on Sprint, so if you want to use it on their network, switch service to the phone before flashing.--Falsefive (talk) 20:32, 25 June 2014 (UTC)

Install_CM_for_tf300t This might be a beginners mistake, but even though the adb part worked, flashing the recovery image with fastboot failed utterly when I tried it with the tablet in the Mobile Dock. Removing it from the dock and connecting the USB cable directly to the tablet solved this.

--Mereel (talk) 20:13, 24 June 2014 (UTC)

Install_CM_for_d2lte: For KitKat installations, a disclaimer is included that ICS bootloaders are not supported. No instructions are given regarding updating to the correct bootloader/firmware. This should be part of the install instructions, as omitting this step will result in incorrect install.--Shrimant Saxena (talk) 17:03, 18 June 2014 (UTC)

Install_CM_for_i9100: for KitKat installations you need a new version of CWM, which is mentioned in the first part of the article, but not in the second.--Uwe Krause (talk) 16:04, 12 June 2014 (UTC)

Install_CM_for_crespo In the description on how to install the chosen image, the path to copy the file to needs to be changed from /sdcard to /storage/sdcard0/ (at least for my device it had to be changed). --BadBen (talk) 21:46, 7 April 2014 (UTC)

Hercules install page (Install_CM_for_hercules) should mention that CM 10.2 won't install using default radio UVMC6 and upgrade to TLMC4. (UI installer does not detect this at all and just fails after factory reset) --Alexandroid (talk) 16:58, 19 May 2014 (UTC)

Install_CM_for_i9100: For mac users some additional steps needed to be done in order to make heimdall work please refer to :

before flashing the image following actions need to be done: 1) sudo chown -R root:wheel /System/Library/Extensions/heimdall.kext 2) the flash command line must be prefixed by sudo (e.g. sudo heimdall flash -kernel zImage)

Install_CM_for_targa: the razr's edge exploit does not work. --Gnuru (talk) 03:03, 16 February 2014 (UTC)

Build_for_dream_sapphire: no folder ~/android/system/vendor/cm and no command get-prebuilts found. (this problem was reported by user Zxd, who mistakenly created a new page instead of posting here)

^^ Comment by mdmower: right, these folders didn't exist for froyo. We need a modified set of build instructions for pre-jellybean devices. --Matt Mower (talk) 23:13, 11 February 2014 (UTC)

There are many devices available at that do not have a wiki page. Please add (see this page at the bottom to see how) these devices to the wiki:

  • cdma_droid2we
  • e980
  • expressatt
  • harmony
  • hayabusa
  • i925
  • jordan_plus
  • n5120 (also needs hover description on
  • p720
  • r950
  • s5670

--Flo Edelmann (talk) 15:41, 7 February 2014 (UTC)

Galaxysmtd_Info: Some users (eg. Australian Telstra branded I9000T users) require flashing a 850mhz 3G radio to receive service. The JP9 listed on the info page is (I believe) compatible and could be labelled as such, the UGKG3 radio (used in the captivatemtd) is the latest 850mhz and would be nice if it was listed for download also.

Install_CM_for_galaxysmtd: A short sentence mentioning that flashing a 850mhz radio/modem may be necessary in some regions for the T or M variants in the instructions might save some confusion for those affected also.

I9100_Info: there are several radios for downloading, but it lacks information on:

  1. whether I should choose only one file or all;
  2. what criteria to use for choosing;
  3. whether I should install the radio using heimdall or recoverymod
  4. the hypothesis when I should mind about updating the radio.

--UtilizadorOpenID17 (talk) 12:47, 29 December 2013 (UTC)


  1. after the "Setting up uNooter" section, the instructions go from "gaining root access" to "installing a recovery image". the cm-10 zip is not mentioned.
  2. the "uNooter" and "NooterFiles" partitions on my 16gb sd card were 41.1 and 82.3 mb respectively, so the 165.2 mb cm-10 zip (which i'm assuming would be needed to be included on the sd card) would not have fit.

--User:latetodinner (talk) Tue Nov 12 03:48:30 UTC 2013

Install_CM_for_acclaim: I currently have the most recent stable release of CM 10.1 installed on my nook tablet, made several attempts to install different 10.2.x nightlies and snapshot, but no success. CWM error states there is a problem with the zip and halts the process. Error number given is zero. Is there any change to the installation procedure? Just curious. if I'm doing something wrong, it worked on 10.1, so I'm guessing either the files are corrupted or the procedure has changed.

--User:Prisoner06 10:25, 08 November 2013

Install_CM_for_p1 has an incomplete instruction: " need now to manually reboot the phone into ClockworkMod Recovery mode by holding . " Holding what?

--Yunosh (talk) 09:55, 19 September 2013 (UTC)

Install_CM_for_hercules: instructions are vague and sometimes wrong. "Important Note" states to use Odin, then the entire doc refers to Heimdall, not Odin. "Installing Custom Recovery" item 3 does not work as described.

--Monsto (talk) 20:19, 14 August 2013 (UTC)

Install_CM_for_skyrocket: it would be helpful to include links to info for installing GApps and updating the radio, if necessary. My radio didn't work right until I updated it to UCMC1, since I flashed to CM 10.1 from ICS.

--Silentquasar (talk) 19:43, 2 August 2013 (UTC)

Install_CM_for_acclaim: The instructions for installing CM from stock are non existent. It only describes installing from recovery.

--Charlie Kochenash (talk) 21:26, 2 July 2013 (UTC)

On the template based install instructions pages:

  1. All the parts about "some devices" should be controllable from device template settings (existing or new ones). For instance the initial note about devices without removable SD cards should depend on which of the storage sizes are blank for the device.
  2. The instructions on how to copy the .zip files to the device should use a (new?) property to decide if adb push or drive mount over USB is the way to go. For most devices, just using the Android web browser to download directly to sdcard is also an option.
  3. Instructions to obtain adb should only be shown if needed by the other instructions (including mention in template-supplied text).

--Jd6119059 (talk) 11:06, 30 June 2013 (UTC)


  1. I was unable to get into recovery mode until I rooted the phone with pda.tar.
  2. I was unable to connect with Heimdall from my Windows 7 64 bit machine. Samsung USB Composite Device was not shown in zadig. I ran zadig in XP mode (service pack 3) and was able to update the drivers and connect.

--Ennuienthusiast (talk) 00:16, 10 June 2013 (UTC)

On all device info pages where the user picks a download category (nightly, milestone, RC, or stable), would it be possible to show exactly what version of Android is represented by each?

--Anglebracket (talk) 20:23, 7 June 2013 (UTC)

Install_CM_for_solana: on "Gaining Root with Motofail" Procedure for Windows, step 8: The exploit script on CMD (the run.bat) did not work. I was not able to create the "bug report vibration" demanded by the script at the end of the procedure. I only got the "Silent Mode, Plane Mode, Suspend and Power off" screen vibration and the exploit failed.

EDIT: I just succeeded at rooting. I had to download another "" from: , and run it from a Windows 7 32bit (instead of the 64bit previous) computer. It worked on the third attempt. I did not need to touch the phone, all steps were automated!

--KMur (talk) 02:11, 5 June 2013 (UTC)

Install CM for otter: The instructions for placing the zip file onto the device didn't work for me. "adb push" fails with "Permission denied". So I loaded the zip file using the standard USB drive interface. I put the zip file to the "kindleupdates" directory, but it could be any directory, including the root. I was able to flash it successfully. It turns out the drive seen by the host computer corresponds to the /sdcard directory as seen by the device in the recovery mode.

--Pavel Roskin (talk) 21:20, 28 May 2013 (UTC)

Install_CM_for_satsuma: There is a note that the kernel will not update on 2011 models and that fastboot must be used to flash instead. A guide for flashing with fastboot would be much appreciated.

--Mortenf (talk) 15:27, 28 May 2013 (UTC)

Install_CM_for_targa: the Razr's edge exploit doesn't work for JB. Had to use:

--Jeremy West (not sure how to sign)

Install_CM_for_p1c: it would be helpful to say that the recovery mode for this particular model is to "Simultaneously Hold Home Button, Volume Up, & the Power button, continue to hold all three until the screen flashes "Samsung", then release all buttons."

--AndyCool22, May 4 2013

Install_CM_for_coconut: entering fastboot mode, Windows fails to install driver for "S1Boot Fastboot", causing the fastboot utility to keep waiting for device. In order to fix this, you need to follow the instructions on the linked Sony page to download an inf file and replace the one shipped with SDK, then use that file as source for driver installation.

--RenatoSilva (talk) 23:20, 1 May 2013 (UTC)


  1. After installing the novacom package and booting the TouchPad in USB mode I did not get the novacom (boootie) driver until after I rebooted my PC.
  2. When running the novacom command it simply hangs if you are not running it as administrator. Start the command shell using the "Run as Administrator" option if you do normally run as administrator.

--Wade Satterfield 23:00, 23 February 2013 (UTC)