You found a bug concerning the CyanogenMod wiki but you don't know how to fix it yourself?
This page is for reporting problems – maybe it's a bad installation instruction or something wrong with the build walkthroughs.
Of course, since this is a wiki, you can try to fix the page yourself.
Note: Fixing Individual Device Settings vs. Fixing Wiki-Wide Templates
- If the problem is with information regarding a device such as the info page, the install instructions, or the build page, try editing the device template for that page, linked at the bottom of every device info page. Modifying these settings will only affect the device in question, although may affect several pages relating to that device.
- If the problem relates to ALL the devices, you may want to look at the template that is used by the device. Modifying a template will change dozens if not hundreds of pages simultaneously for many devices, so only play with these if you know what you are doing!
If you can't fix the problem yourself, describe the problem below thoroughly and include links to where the problem is, as well as what the solution should be. Also add a
--~~~~ at the end of your message to "sign" it. Hopefully someone who's able to look at the problem can fix it.
If you do fix the problem, please remove the report from this page.
- I couldn't get my Nexus 7 build working!
- On the page Grouper_Info, I noticed there was a bad link. The kernel for the source code is actually located at asus_grouper http://www.github.com/cyanogenmod/android_device_asus_grouper, not http://www.github.com/cyanogenmod/baddirectory as reported on the page. --Fattire (talk) 07:38, 8 December 2012 (UTC)
Note: please leave edit time in UTC as far as possible to maintain uniformity.
Report any issues you discover below
Put new issues at the top! And don't forget to add your name and a date by appending
--~~~~ at the end.
Download links for "Sony Ericsson Xperia X10 - es209ra" are not working.
On http://wiki.cyanogenmod.org/w/Install_CM_for_xt925 for Razr HD, missing a link to download clockworkmod recovery, such as: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-188.8.131.52-xt925.img
(although that didn't work on my phone, which is a xt925, and I had to use`fastboot flash modem empty_radio.img` to fix the broken flash which apparently bricked my radio - it wasn't clear to me the only option was unlocking the bootloader first: http://www.droid-life.com/2013/04/08/motorola-razr-hd-razr-m-and-atrix-hd-bootloader-unlock-released/)
Also, step #6, reboot into recovery manually, as no command seem to work (specially not `fastboot boot your_recovery_image.img`)
nook color "encore" installation page "http://wiki.cyanogenmod.org/w/Install_CM_for_encore" there seems to be a section (or two) missing.
i followed the trail from cyanogenmod.org, to devices, to nook color "encore" get cyanogen download. i downloaded the stable version (cm-10.1.3-encore.zip) and followed the link on that page "How to install \ CyanogenMod on the Nook Color".
after the "Setting up uNooter" section, the instructions go from "gaining root access", then to "installing a recovery image". the cm-10 zip is not mentioned.
the "uNooter" and "NooterFiles" partitions on my 16gb sd card were 41.1 and 82.3 mb repectively, 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
- latetodinner, were you able to find a solution to your problem? I was thinking of using fdisk to use that 7.29GB unused partition but I'm not sure if this would affect the root process. Johncruise (talk)
MB886 - Atrix HD: Comment applies to this link: http://wiki.cyanogenmod.org/w/Install_CM_for_mb886
Section titled: Installing recovery using fastboot
Here is the link to CWM Touch Recovery (worked like a charm on Rooted/BootLoader Unlocked/Unlocked Atrix HD):
To install this, I needed to initiate fastboot by pressing vol up + vol dn + pwr on phone. Was not able to do this from within terminal window on pc.
IMO the "xda" link should be included on the above-referenced (cyanogenmod) page for MB886 / Atrix HD - took me awhile to find, so it would save time for folks looking for it.
--User: pjbeee 16:47, 28 November 2013 (UTC)
Barnes & Noble Nook tablet - Unable to install CM Acclaim 10.2.XInstall_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
Sony Xperia SP ('huashan') No downloads are available (http://download.cyanogenmod.org/?type=stable&device=huashan)
I just finished installing CM on an Epic 4G phone and installing CWM only worked by pulling out the battery after the blue progress bar was full. Could someone who understands the maze of templates please add this to the install page? Mark Haferkamp (talk) 20:52, 3 November 2013 (UTC)
Hello, I went through T-Mobile G2: Firmware Downgrade (Gingerbread)to How To Install CyanogenMod Android for HTC G2 / Desire Z ("vision") and there needs be a step at the begining of How to Insstall CM... to delete the PC10IMG.zip before rebooting else it will continue to attempt to reinstall the PC10IMG.zip. It took me reading many tutorials before figuring this out. Greenman76 10/28/2013
hi, in nexus7(2013), wifi doesn't work for me. thanks.user: jordirpz- 19.42- 23 octubre de 2013.spain.
Sony Xperia SP ('huashan') page has one issue. It contains an invalid link in the section 'BUILD CYANOGENMOD YOURSELF'. The proposed link to the Kernel : http://www.github.com/cyanogenmod/sony-kernel-msm8960t leads to a 404 page. Then link to the 'Device' section is OK. --amundain (talk) 13:22, 23 October 2013 (UTC)
Samsung Galaxy S3 LTE (i9305) page (Install_CM_for_i9305) has some issues:
- New Version of ClockWork Mod (), although I cannot deliver the md5.
- New Versions of Heimdall ().
- At step 7 of "Installing a custom recovery on Galaxy S III LTE", "Home & Volume Up & Power until the Samsung splash screen appears" should be added at the end of the sentence.
- Helpful tip for this section: After powering off the device (step 3), first boot the device into download mode, accept the disclaimer and then connect the USB cable.
- At step 3 of "Installing CyanogenMod from recovery", "Home & Volume Up & Power until the Samsung splash screen appears" should be added at the end of the sentence.
GT-P5110 Install page at Install_CM_for_p5110 has out-of-date CWM version 184.108.40.206. ClockworkMod page at ClockworkMod lists 220.127.116.11 as suitable for P5110. The 18.104.22.168 should be mentioned for P5113 users. --Tapiov (talk) 15:06, 27 September 2013 (UTC)
The CWM Recovery File linked in Install_CM_for_d710 appears to be a corrupt archive. The copy I found here seems okay: http://www.mediafire.com/download/u0hs65d1utb3fe4/StockCWM-EL26.tar.md5 --Deathbird (talk) 17:03, 19 September 2013 (UTC)
Install_CM_for_p1 has an incomplete instruction: " need now to manually reboot the phone into ClockworkMod Recovery mode by holding . "
Hello everyone. it took a long time to find the problem. I followed all the instructions and the installation was successful, but i could never boot my phone on cyanogen mod. There was just a black screen and it did reboot every 10s. so i was searching in the internet and found the solution in a blog:
- restart in by pressing voulume down and power button at same time
- select fastboot
- extract boot.img of zip into the same folder like fastboot (adb-Folder) on your computer
- cmd in the fastboot folder > "fastboot flash boot boot.img"
and it worked!
I try to translate in french some pages of this wiki. When I try to save my translation on some message, I have an error.
For example : Translations:About/30/fr
It seams the problem appears when there is an external http link in the translation message (but I'm not sure).
I don't know what to do to fix it.
Any idea / help ?
I tried to log into this wiki with my launchpad OpenID and the wiki would say that using that ID is not allowed. WTF?
I had CM7.1 (unofficial) on samsung captivate. It started having issue that I could not copy or install any thing to its internal sd card. I decided to use following instructions from CM site to upgrade: http://wiki.cyanogenmod.org/w/Install_CM_for_captivatemtd
It uses semaphores CWM zImage. I flashed it fine using heimdall but then on manual reboot it shows ATT world phone screen. I am not sure how to make further progress.
First time I am trying to flash android ROM. Onto ZTE blade V880, I followed instructions of:
but got failure: Assert failed: getprop("ro.product.device") == "blade" || getprop("ro.build.product") == "blade"
--User:yotam 2013/08/28 22:04
Finally, I solved this problem by updating from Gen1 to Gen2, following instructions.
--User:yotam 2013/08/31 23:04
I recently switched my Nexus 4 from stock Android 4.3 to CM 10.1. However, the instructions failed me, because my data partition was encrypted. Unfortunately, CWM Recovery doesn't seem to support encrypted data partitions, so it failed to wipe my data partition. This left my system in an unusable state. I worked around the problem by flashing TWRP to my recovery. In addition to supporting encrypted data partitions, TWRP is touch enabled, and seems to be overall easier to use than ClockWorkMod recovery. Absent some reason that I'm missing, it seems to me that TWRP would be a better recovery to recommend to people by default than CWM. --Simon Ruggier (talk) 05:08, 27 August 2013 (UTC)
The Kernal repository is listed incorrectly as http://www.github.com/cyanogenmod/android_kernel_bn_ovation. It should be http://www.github.com/cyanogenmod/android_kernel_bn_omap.
Bennett Marks 18:18 25 August 2013
Step 6 under "Installing recovery using fastboot" on the "How To Install CyanogenMod Android for Motorola Droid RAZR HD/RAZR HD MAXX (CDMA) ("xt926")" says the following: "Once the flash completes successfully, reboot the device into recovery to verify the installation. This can be done by typing fastboot boot your_recovery_image.img.". This step consistently fails for me with the following error from the fastboot utility: "(bootloader) Command restricted FAILED (remote failure)". The failure itself isn't a big problem in and of itself, but the xt926 apparently counts this as a flash failure and will from then on always boot directly to fastboot mode (fastboot reason: flash failure). You can only perform a normal boot by holding down buttons to bring up the bootloader and selecting it manually. This is a hassle to fix. I had better luck by simply rebooting the phone manually in leiu of step 6. --Whydroidwhy (talk) 03:39, 23 August 2013 (UTC)
Some helpful notes I discovered trying to work with a TMobile SGS4 relating to this page: http://wiki.cyanogenmod.org/w/Install_CM_for_jfltetmo
Do not link to specific versions. RC1 which is even stated to have a bug is linked to (why?) and RC2 is right next to it. Instead link to the official download page at http://www.glassechidna.com.au/products/heimdall/ so that people can get the latest working version, it also has a link to the proper MSVC redistributable.
Ditto for theRecovery image. It'd be great to link to http://www.clockworkmod.com/rommanager/ but there are no anchors in the page, so we should ask for anchors to be put at each line for deep linking.
Step 5 under installing a custom recovery: "heimdall flash --recovery recovery.img --no-reboot" should note:
If you see the error "ERROR: Partition "recovery" does not exist in the specified PIT." then make sure --RECOVERY is in caps as shown "heimdall flash --RECOVERY recovery.img --no-reboot" as it may be case sensitive.
That drove me nuts till I discovered the bit about caps.
Also, it does not seem necessary to hold HOME when holding the volume buttons for download/recovery modes.
n7 2013 (flo),t0lteatt, t0ltetmo, s4 mini, htc one x+ international and the d710 need to be added to the wiki. --White 00:35 16 Aug 2013 UTC.
Page http://wiki.cyanogenmod.org/w/Install_CM_for_i9100 can be improved:
* 'Installing a custom recovery on Galaxy S II' -> '1': on Debian 'heimdall' is available in the repos (# apt-get install 'heimdall-flash')
- 'Installing CyanogenMod from recovery' -> '2': on Debian 'adb' is availaboe in the repos (# apt-get install 'android-tools-adb')
* 'Installing CyanogenMod from recovery' -> '5' / 'superbrick warning': if you're using stock kernel don't do a "wipe data/factory reset", instead continue to step '6' and up to step '9', then boot again to recovery mode and now do the "wipe data/factory reset"
--Die z (talk) 14:29, 16 August 2013 (UTC)
- Modified pages for the 1st and 3rd items. Unsure if we should provide an update to the adb page. --Bassmadrigal (talk) 19:04, 19 August 2013 (UTC)
I was unable to use Heimdall on 64-bit Ubuntu 12.04 when following http://wiki.cyanogenmod.org/w/Install_CM_for_t0lte Both 32 and 64 bit did not work as well as a version built from source. I had to use Windows 7 to install recovery.
Also, "You need now to manually reboot the phone into ClockworkMod Recovery mode by holding ." needs update... to boot into recovery mode hold "Volume Up, Home, Power"--Dizgotti (talk) 17:44, 15 August 2013 (UTC)
- Lolmouse fixed recovery buttons in a previous update --Bassmadrigal (talk) 20:55, 19 August 2013 (UTC)
Flash instructions for Samsung SGH-T989 http://wiki.cyanogenmod.org/w/Install_CM_for_hercules 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.
"Installing from recovery" item 2 refers to adb without having said what it is, what it's for or where it came from. --Monsto (talk) 20:19, 14 August 2013 (UTC)
- I've updated the install instructions link to the adb page before the install step tells you to use it --Bassmadrigal (talk) 20:55, 14 August 2013 (UTC)
On the following page http://wiki.cyanogenmod.org/w/Install_CM_for_glacier under the section "Downgrading to 1.17.531.2" Point 2 Downloading this file (fre3vo) I get an error that this is a virus/linux trojan. Is this due to the nature of the file or is it really infected? --Nick Gover (talk) 16:45, 12 August 2013 (UTC)
In the page http://wiki.cyanogenmod.org/w/Install_CM_for_p3100 under the section "Installing a custom recovery on Galaxy Tab 2 7.0 (GSM)" Point 7 is incomplete (You need now to manually reboot the phone into ClockworkMod Recovery mode by holding .) -- OpenIDUser273 (talk) 22:28, 6 August, 2013 (UTC + 8:00)
When not logged in, it keeps changing wiki language when going from page to another. I dont care about that, but when it goes to language what have been translated or some "right-to-left" language --Niko0o (talk) 10:50, 6 August 2013 (UTC)
On the page 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)
SafeStrap Recovery link is broken in: http://wiki.cyanogenmod.org/w/Install_CM_for_umts_spyder
http://goo.im/devs/Hashcode/umts_spyder/Safestrap-RAZR-D4-BIO-3.11.apk --Dokan (talk) 16:28, 25 July 2013 (UTC)
- You can use this: http://goo.im/devs/Hashcode/targa/Safestrap-RAZR-D4-BIO-3.11.apk --Alessio D. (talk) 21:23, 8 August 2013 (UTC)
on page http://wiki.cyanogenmod.org/w/Install_CM_for_stingray, the following step fails: "Once the flash completes successfully, reboot the device into recovery to verify the installation. This can be done by typing fastboot boot your_recovery_image.img." The image flashes successfully but does not boot. The device reports an error on the screen: "boot command is not allowed on consumer devices". The device does not enter recovery mode and hangs. --Patna (talk) 18:34, 14 July 2013 (UTC)
It seems the wiki page for the HTC Raider 4G (holiday) is missing. There are official CM10.0 nightly (well, weekly) builds available from http://get.cm/?device=holiday --Bassmadrigal (talk) 17:29, 4 July 2013 (UTC)
- confirmed --White 04:12 16 July 2013 (UTC)
- confirmed --White 04:12 16 July 2013 (UTC)
On the template based install instructions pages, 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.
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.
Instructions to obtain adb should only be shown if needed by the other instructions (including mention in template-supplied text).
The file I downloaded from Cyanogen's ClockworkMod Recovery link would not work for my Galaxy note. When I flashed it, I received a message telling me that the firmware upgrade encountered an issue. The file it downloads (recovery-clockwork-22.214.171.124-quincyatt) was 123 KB. The file I downloaded from Clockworkmod.org (recovery-clockwork-126.96.36.199-quincyatt) was 7,912 KB. --Ennuienthusiast (talk) 00:16, 10 June 2013 (UTC)
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 breakfast vibrantmtd at "Prepare Device Specific code" the download of both specific configuration and kernel source fails. it seems that maybe the repository does not exist or appears in a different name. any ideas / instructions will be helpful. thx. --Benk (talk) 22:43, 9 June 2013 (UTC)
On all pages where the user picks the 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)
On Install CM for hallon, it says that holding Vol Up will put the device into fastboot mode. Actually, on hallon (Xperia Neo), it is the menu button. See also http://unlockbootloader.sonymobile.com/fastboot-buttons. --Per Olofsson (talk) 18:07, 6 June 2013 (UTC)
On http://wiki.cyanogenmod.org/w/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. -KMur (talk) 21:40, 4 June 2013 (UTC)
- Obs.: I just succeeded at rooting. I had to download another "motofail_windows.zip" from: http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/ , 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_i9300 - Yesterday I followed all the process exactly step by step. All MD5 checked, all steps carefully followed. But I got a "Initialising protocol... ERROR: Protocol initialisation failed!" while flashing CWM recovery with Heimdall (I certanly don´t know why), so I gave up. Today I tried again and it worked. May be it could be necesary to reboot the phone after the installation of the custom driver and before flashing the CWM Recovery, because it´s the only difference I see from yesterday and today --Elreymon (talk) 13:22, 01 Jun 2013 (UTC)
I had the same problem as Elreymon, rebooted after installing driver, problem solved. Seems like this is the solution, maybe it could get added to the helpful tips on the guide. --GrimEon (talk) 15:44, 9 November 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_p5110 - I have the p5113 and this may be a differnce between the two models. On step 3 the prosess to get into download mode is wrong while the device was off I had to press and hold the power and volume up buttons, then press volume down to accept that I wanted to install a custom os, and then attach the usb cable. Also step 7 does not say what the button combonation is to get into recovery, its hold volume down and power. --TheTaLlesT (talk) 16:28, 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_spyder - Razor Blade links are missing for [Linux]http://batakang.com/ftp/DROID_RAZR/razr_blade_linux.zip and [Mac]http://batakang.com/ftp/DROID_RAZR/razr_blade_mac.zip
--Jesse Buffington (talk) 13:16, 20 May 2013 (UTC)
Install_CM_for_targa the Razr's edge exploit doesn't work for JB. Had to use: http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/ --Jeremy West (not sure how to sign)
On the page http://wiki.cyanogenmod.org/w/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 at gmail dot com May 4 2013
In the page for Live with Walkman (coconut), you need to be more clear on how to use the fastboot mode, which is by turning phone off then pressing volume up while connecting to PC. Also, at that time, 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)
Mac driver is missing in the package that is provided on http://wiki.cyanogenmod.org/w/Install_CM_for_i9300#Installing_a_custom_recovery_on_Galaxy_S_III_.28International.29 This is the download http://cmw.cmfs.me/common/heimdall_v1.4rc1_mac.zip package that needs to add the Mac kernel driver which is this file: /System/Library/Extensions/heimdall.kext/Contents/Info.plist --Hashier (talk) 11:39, 13 March 2013 (UTC)
Missing step - HP touchpad With the instructions at http://wiki.cyanogenmod.org/w/Install_CM_for_tenderloin I have successfully reached step 12 of part 1 and can us MoBoot to get into WebOS or into ClockworkModRecovery. But the next section speaks of using the command "adb" to put the CM zip file on the SDcard. I can't see where the adb command is supposed to run! I checked the video version of the instructions and this isn't covered - on the video version, as soon as MoBoot is running, "Boot CMod" is one of the boot options. It isn't for me!! --Ccomley (talk) 21:41, 24 February 2013 (UTC)
- There is documentation in this wiki about adb and how to use it, but I can make that more linkable in the document I guess --Fattire (talk) 21:50, 26 February 2013 (UTC) UPDATE: It says "See adb documentation for additional help with this step". Was this not there before? If not, we can remove this wiki problem item. --Fattire (talk) 21:52, 26 February 2013 (UTC)
On the "Install CM for tenderloin" page I noticed two things that could be documented.
- After installing the novacom package and booting the TouchPad in USB mode I did not get the novacom (boootie) driver until after I had rebooted my PC.
- 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)
- Installation on an HP Touchpad, Installing CyanogenMod from Recovery
On Windows based system, after completed the steps Installing the ClockWorkMod Recovery using ACMEInstaller3.
There is no
sdcard folder on the Touchpad, and no sdcard can be plugged on the contrary of what is written. By default, as I understand, the
sdard folder corresponds to the root of the Touhpad.
When installing Cyanogen for the first time :
1/ Connect your Touchpad to your computer, enable the Mass Storage Mode, create a
sdccard folder at the Touchpad root.Your folder can have any name, but
sdcard is easier as the ClockWorkMod Recovery asks you for an
2/ Place the CyanogenMod rom .zip file in the
3/ Reboot the Touchpad and follow the steps 4 6 to 9 of the Installing CyanogenMod section. --vitam1970 (talk) 22:00, 23 February 2013 (UTC)
- There is a note that says Some devices do not have removable SD cards. Regardless, there should still be a partition on the device named "/sdcard" that can be used for flashing purposes, even though the contents of /sdcard may actually be in internal storage. -- This should be true for the tenderloin device just like any other. If I recall correctly, the /sdcard maps to the same virtual file system as the /media partition in WebOS. so I'm pretty sure it's there. Also, FWIW the /sdcard partition is NOT the same as the root of the touchpad, which is "/". --Fattire (talk) 21:59, 26 February 2013 (UTC)
Hint for the newbies : Google apps are not packaged with CyanogenMod9 builds. Just have a look at Goo.im to get the .zip approved by developers. Copy the archive in you
sdcard folder on your touchpad, reboot and make a ClockWorkMod update.
--vitam1970 (talk) 22:00, 23 February 2013 (UTC)
There's a bug in the libusb for heimdall (Windows--not sure about other platforms) that has been fixed since the version linked to here was built. (latest version from 2/1/13 available here: https://github.com/Benjamin-Dobell/Heimdall/tree/master/libusbx-1.0/lib/Win32/Release). I know it affects t-mobile S3s...not sure about others. I don't have quite enough confidence to recompile the whole thing and post it here. Also I'm not sure that even the libusb fix has completely fixed the problem--with the latest libusb, heimdall claimed to have successfully flashed the latest clockworkmod, but I was still at the previous version (although the counter incremented....odd). (further discussion at: https://github.com/libusbx/libusbx/issues/78) --Mattjm (talk) 00:20, 9 February 2013 (UTC)
- The installation instructions for the HP Touch Pad lack an important step. The
android_winusb.infincluded in the latest Google USB driver package lacks entries for this device. For me, it worked to add
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&REV_0227&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
after the last lines of the [Google.NTx86] and [Google.NTamd64] sections. Others reported success with
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_6860&REV_0227&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_6860&MI_01
- it doesn't work... I've tried both methods (Heimdall and Odin). Clockwork installs fine, but during the Flash stage (cm-10.1.2-d2att) Recovery Mode always ends with "Status 7"
in nexus 7(2013), wifi doesn't work
Issues Considered fixed
Any issues which were mentioned above previously and are considered "fixed" should be moved here. If someone feels that an issue is not yet fixed, they are free to move it back up, but please leave a comment why you consider it "not fixed".
on Install CM for n7000, at item 7 it says "The device will not reboot, rather will wait for you to reboot it to give enough time to enter recovery with the button combination." It's unclear if the user is supposed to reboot it at this stage, or not. I am assuming that this means the device should be rebooted, but it doesn't specify how this is to be done. I am also assuming that during the reboot, you have to press some unspecified combination of buttons in order to enter recovery mode. Could someone please clarify this? --Anglebracket (talk) 21:09, 7 June 2013 (UTC)
- Previous update by Stanislav Makarenko already corrected this, however, I went through and made the page more accurate for multiple OSs --Bassmadrigal (talk) 20:55, 19 August 2013 (UTC)
Translations:About/30/zh-tw can't save I have already translate the paragraph here i paste hope somebody can help to save==> 有不少(這裡的不少是指好幾百萬個)CM使用者. 事實上, 去看看 及時統計看看這些回報自己是CyanogenMod的使用者統計吧. --Naruto861214 (talk) 05:52, 2 August 2013 (UTC)
My Samsung Galaxy S was broken after doing all the steps at http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
CM started up fine but the modem/network was not detected. I could not call anyone or receive calls/sms. I fixed it by following this great tutorial http://forum.xda-developers.com/showthread.php?p=22555425
So if you have a Galaxy S and have problems with your modem/finding a network, you might want to try the tutorial!
- Maintainer wrote the instructions. The firmware version was probably wrong for the version of CM that you installed.--White 04:05, 16 July 2013 (UTC)
The main Devices page does not work with the non-chrome Android web browser included in CM7, most notably the vendor drop down is not scrollable and trying to select "all" triggers a bug which changes it back to none the moment you hit "search". Basically the main function of the page does not work with the software it links to. --Jd6119059 (talk) 11:27, 30 June 2013 (UTC)
On http://wiki.cyanogenmod.org/index.php?title=Install_CM_for_p3110 , Heimdall requires the X86 version of the C++ redistributable, EVEN IF you're running an X64 system. ---Schweini (talk) 19:34, 1 June 2013 (UTC)
The link to download CM 10.1 RC3 for razr/razr maxx (cdma) is broken giving a 404 not found error. Looking forward to the new download. --amrozack