[ROM][AOSP 4.2.2] CyanogenMod 10.1 Official

Status
Not open for further replies.
Search This thread

mdmower

Senior Member
Sep 14, 2011
826
1,044

Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2

Contents
This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
Post 2 - Restoring a non-functioning radio
Post 3 - Frequently asked questions and workarounds for common problems

Introduction
This is CyanogenMod 10.1 (cm-10.1) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.2.2. Usage of this ROM indicates that you understand...
  1. the warranty on your device is void;
  2. the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
  3. there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).

Preparations and Installation
Get your phone ready for a new ROM
  1. You must have an unlocked bootloader or be S-OFF (read here for instructions)
  2. Before leaving your stock based ROM, turn on all GPS location services:
    Settings > Location > (all three location services) = On
  3. Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
  4. Install a custom recovery: CWM or TWRP
  5. Make a backup of your current ROM in recovery - DO THIS!
Install CyanogenMod
  1. Perform the factory reset function in recovery and wipe the /system partition
  2. Flash the CyanogenMod zip and optionally flash the GApps version corresponding to CM 10.1.x
  3. If you are S-OFF, you're done; reboot and enjoy
  4. If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands:
    Code:
    adb reboot-bootloader
    fastboot flash boot boot.img
    fastboot reboot

Updating to a new build
  1. Make a backup of your current build in recovery
  2. Install the new build
  3. If you are S-OFF, reboot
    If you are not S-OFF, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.

Special notes about connecting to Verizon's network
Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
  1. Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
  2. SIM card added: the first couple times you boot the phone you may get a notice, "SIM card added". Do not hit restart, just hit the back button and the notice will go away.
  3. Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.

Official Downloads
Official builds are available at download.cyanogenmod.org/?device=fireball
Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
If your display flickers noticeably after an hour or so of usage, discontinue use of these official releases (see below for unofficial releases that do not exhibit this issue). This issue affects about half of the fireball user base (rough estimate based on forum replies). These builds use linux kernel 3.4 which was never released by HTC for the fireball, so the board files are assembled as best possible with what little we have for reference. If your device suffers from this problem, you may notice the flickering persists for a few hours after restoring another ROM, but it should eventually subside. The developer(s) are not responsible for damaged devices as a result of running these builds. Stick with a stock-based ROM if you're uncomfortable with this.

Unofficial Builds
These builds are not endorsed by CyanogenMod. They are my personal builds.

Most recent builds: goo.im
Archive/Mirror: mediafire.com

goo.im folder structure: visit the page to read release-specific notes
  • mdm-releases - Recommended for users that have flickering panels on official builds. Based on CM 10.1.2 stable using linux kernel 3.0
  • kernels - Enhanced kernels for use only in CM
  • cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
  • cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases

GApps
Download the GApps version corresponding to CyanogenMod 10.1.x

Reporting Issues and Getting Help
Policy on bug reports:
  1. You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
  2. logcat or GTFO
If these steps are not taken, your report will be ignored.

How to gather helpful data for troubleshooting
How to use the issue tracker

Getting help
There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.

Change Log
CyanogenMod BBQLog

fireball-specific changes:
  • 20130725 - fix blank MMS messages from iPhone 5 users
  • 20130723 - fix low in-call volume and raise speaker volume max
  • 20130721 - fix signal strength reporting zero on some GSM networks
  • 20130715 - fix front facing camera face detect crash, fix dim screen on wake
  • 20130628 - wake-on-volume fixed
  • 20130622 - camcorder can now record in all resolutions
  • 20130619 - finishing touches to battery parameters; charging should properly reach 100% now
  • 20130618a - stereo audio fixed
  • 20130618 - fix charging and battery level indicator
  • 20130616 - kernel 3.4 introduced, updated adreno driver blobs from Qualcomm
    ---- break all teh things ----
  • 20130504 - wake-on-volume fixed; flash and shutter synchronized better in camera
  • 20130424 - encryption of /data partition is now supported, read post 3 for instructions!
  • 20130306 - fix for selecting bands crashes com.android.phone, SMS/MMS behavior changes
  • 20130303 - camcorder video focus improvements (still loses focus, but should be better)
  • 20130226 - all resolutions save without restarting camcorder application
  • 20130223 - all resolutions available in camcorder (with quirks)
  • 20130221 - secure adb, experimental microphone noise suppression fix (amluto)
  • 20130217 - camcorder saves videos correctly
  • 20130209 - gooManager OTA support, camera focus fixed, notification led fixed
  • 20130207 - fixed audio applications freezing phone, sending mms messages should not return invalid destination, battery charging LED can be disabled
  • 20130204 - removed non-effective VZW APNs, enabled MTP support
  • 20130131 - experimental VZW APN configuration
  • 20130128 - initial Release

Known Issues
Official Builds
  1. Display flickers and gets worse the longer the phone is on (may not occur depending on specific panel in your phone) - if you experience this issue, discontinue use of the CyanogenMod nightlies until the bug is fixed
  2. Screen-on delay is long
  3. Audio pauses briefly during screen on/off events
  4. High pitch background noise in camcorder recordings
  5. Touch to focus doesn't work
  6. Flash crashes camera application
  7. The first few times the phone boots there may be a "SIM card added" notice
    Workaround in post 3

Unofficial MDM Builds
  1. Moving between 1x and LTE networks sometimes requires toggling airplane mode to get data working
  2. Camcorder does not stay focused
  3. Music lock-screen widgets sometimes flicker when you turn on the screen; the controls are still active though
  4. The first few times the phone boots there may be a "SIM card added" notice - Workaround in post 3

Known Issues that will not be fixed
  1. OTG mounting of USB sticks - Likely no hardware support
  2. FM Radio - Likely no hardware support
  3. MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
    Workaround in post 3

Development Information
CyanogenMod 10.1 builds using linux kernel 3.0 were becoming very stable before DxO Labs made a DMCA take-down request on a camera auto-focus library: libDxOAF.so. CyanogenMod had to pull official support for this device until builds could be offered that do not include this library. Kernel 3.4 no longer depends on the auto-focus routines in that library, so development efforts have gone into getting evita, fireball, jewel, and ville running well on it. Official nightlies are currently available for fireball, based on kernel 3.4, but there are a number of issues to be resolved (see above). Since HTC has not released an official jellybean ROM for this phone, there is no recent kernel source that could provide hints about how to fix these issues. If you have kernel development experience, your help would be greatly appreciated in fixing up the board files: android_kernel_htc_msm8960/arch/arm/mach-msm/htc.

The following trees are needed to build CyanogenMod 10.1 based on kernel 3.4:
  1. CyanogenMod/android_device_htc_fireball
  2. CyanogenMod/android_device_htc_s4-common
  3. CyanogenMod/android_device_htc_msm8960-common
  4. CyanogenMod/android_kernel_htc_msm8960
Use the extract-files.sh script in the fireball device tree while running an official cm-10.1 build to pull necessary proprietary files into vendor/htc.

The following trees are needed to build unofficial CyanogenMod 10.1.2 based on kernel 3.0 (a.k.a. mdm-releases):
  1. mdmower/android_device_htc_fireball - branch cm-10.1-FbR
  2. mdmower/android_device_htc_msm8960-common - branch cm-10.1-FbR
  3. mdmower/android_kernel_htc_msm8960 - branch cm-10.1-FbR
  4. mdmower/android_frameworks_base - branch cm-10.1-FbR
  5. mdmower/android_frameworks_opt_telephony - branch cm-10.1-FbR
  6. mdmower/android_apps_Settings - branch cm-10.1-FbR
Use the extract-files.sh script in the fireball device tree while running an unofficial mdm build to pull necessary proprietary files into vendor/htc.

Credits
The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
 

Attachments

  • Screenshot_2013-01-27-20-35-24.jpg
    Screenshot_2013-01-27-20-35-24.jpg
    17.1 KB · Views: 5,685
  • Screenshot_2013-02-27-17-47-26.jpg
    Screenshot_2013-02-27-17-47-26.jpg
    25.4 KB · Views: 4,093
  • cm_image.png
    cm_image.png
    9.4 KB · Views: 96,412
Last edited:

mdmower

Senior Member
Sep 14, 2011
826
1,044
Restoring a borked radio

In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.

Downloads
  1. Stock ROM
  2. recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391

Instructions
  1. From your preferred recovery, run the factory reset option
  2. Follow the directions in this thread to install the stock ROM
  3. Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
  4. Reboot to the bootloader
  5. Flash the stock recovery:
    Code:
    fastboot flash recovery recovery_signed.img
    fastboot reboot-bootloader
  6. Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
  7. Let the phone reset and boot up
  8. Allow network connectivity to be restored (make a test call)
  9. Turn on all GPS location services: Settings > Location > (all three location services) = On
  10. Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
  11. Reboot to the bootloader
  12. Flash your preferred recovery: CWM or TWRP
    (If you just want to run this stock ROM, you can stop here)
  13. From your preferred recovery, run the factory reset option
  14. Restore your ROM backup and wipe cache again before rebooting
 
Last edited:

mdmower

Senior Member
Sep 14, 2011
826
1,044
FAQ and Workarounds

The solution to many problems
Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!

Stuck at the HTC boot screen (solution by Aldo101t)
If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
Code:
fastboot flash boot boot.img
Enable USB debugging or access Developer Options
Settings > About phone > tap 'Build number' 7 times

Screen flicker
If after leaving the phone on for a few hours you notice the screen flickering rapidly, it is advised that you stop running the offical builds and restore a stock based image or one of the unofficial CyanogenMod 10.1 mdm-releases. You may still notice flickering for an hour or two after switching to a different ROM, but it should eventually subside.

"SIM card added" or "Waiting on... activation" notice every time the phone boots
SIM card added notice: do not hit restart, just hit back and the notice will go away
Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).

"What mobile network settings should I use?"
Verizon Wireless users in the U.S.
Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
  • Network mode = LTE/CDMA/EvDo
  • CDMA subscription = RUIM/SIM
Do you have suggestions for other carriers and/or other countries? Let me know what settings work for you, as well as necessary edits to build.prop.

Missing menu button in applications (solutions by blazingwolf and somerandomname1)
Option 1: Re-associate the recent apps button: Settings > System > Hardware keys > Enable custom actions > App switch key
Option 2: Use action overflow: Settings -> System -> Hardware keys > Show action overflow

Text messages from 6250 with message VZWNM: # (solutions by Linch89, MJL99, and slacka-vt)
See this thread and this post.

ext_sd doesn't show files on the MicroSD
ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.

Examples:
ES File Explorer: Settings > Path Settings: Home Directory = /storage/
Root Explorer: Preferences > General Preferences: Home Folder = /storage/

ADB reports device offline
After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.

Sound is distorted when DSP presets and/or bass boost are enabled or
Gapless music playback doesn't work
Set lpa.decode=false in build.prop:
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
exit
adb reboot
To revert this change later, perform the same steps above, but swap true and false in the sed line.

MicroSD will not mount as a mass storage drive when connected to the computer
UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
Settings > Storage > (menu) USB computer connection > MTP

Windows and Mac recognize MTP devices automatically.
Linux requires a bit more work, here's the quick instructions:
  1. edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
    Code:
    SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
  2. install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
    Code:
    sudo add-apt-repository ppa:langdalepl/gvfs-mtp
    sudo apt-get update
    sudo apt-get upgrade
    sudo apt-get install gvfs
  3. Restart your computer
Phone number, MIN, and PRL do not show in phone status or
MMS messages don't send: "Invalid destination"
Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.

"I'm running RC1 or RC2 and I refuse to update!"
At least apply this small update package to fix low power audio and update the RIL to comply with changes to Verizon's network.

GPS doesn't acquire a signal (solution by somerandomname1)
  1. From recovery, make a nandroid backup of CM
  2. Wipe data, cache, and system
  3. Restore a stock-based ROM backup
  4. Enable all location services: Settings > Location > (all three location services) = On
  5. Use a GPS application to get a lock on your position (I use GPS Test)
  6. From recovery, wipe data, cache, and system
  7. Restore CM backup
  8. Wipe cache and Dalvik cache
Internal storage is not accessible by ROM or recovery
This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
  1. Restart the phone to recovery and connect the USB cable to a Windows computer
  2. In recovery, use the mount USB feature:
    • ClockworkMod(-based): mounts and storage > mount USB storage
    • TWRP: Mount > Mount USB Storage
  3. When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
  4. After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
  5. Your /sdcard partition should now be accessible
Encryption (thanks to Slick1123)
Pre-requisites: TWRP 2.6.0.0 or newer

Encryption procedure:
  1. Make a full backup in TWRP
  2. Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
  3. Reboot and let phone battery charge to 100%
  4. Turn on Airplane mode
  5. Settings > Security > Encrypt phone
    Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
Reverting encryption:
  1. Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
  2. Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
  3. Wipe your data partition
  4. Restore your backup
Using the Droid Incredible 4G LTE on non-Verizon carriers
Remove the following lines from build.prop:
Code:
# Carrier definitions
ro.cdma.home.operator.alpha=Verizon
gsm.sim.operator.alpha=Verizon
gsm.operator.alpha=Verizon
ro.cdma.home.operator.numeric=311480
gsm.sim.operator.numeric=311480
gsm.operator.numeric=311480

# Access to Verizon/HTC apps in Play store
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-verizon
 
Last edited:

jose51197

Senior Member
Jan 15, 2012
808
654
26
Cartago
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews

Great im happy to tell i have run this like for 3 days great battery exelent performance and I'll post over clock for this soon

Sent from my Incredible 4G LTE using xda app-developers app
 

blazingwolf

Senior Member
Nov 11, 2006
2,127
405
With this version I have the following issues:

1. Apps don't have menu buttons. I had to change the recent apps button to open/close menus to get menus working.


I am not S-Off as I couldn't get that to work for me but I have the unlocked bootloader.
 
Last edited:

mdmower

Senior Member
Sep 14, 2011
826
1,044
1. Internal sdcard is not mounting correctly. It shows as not mounted in Root Explorer and Gallery, Camera and other apps that need it complain that it is not there. What's interesting is Settings/Storage sees the internal storage.
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.

Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
 

Aldo101t

Senior Member
Mar 9, 2012
5,018
2,200
Pittsburgh
HTC U11
Google Pixel 7 Pro
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.

Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1

just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
 

blazingwolf

Senior Member
Nov 11, 2006
2,127
405
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.

Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1


Yep, sure did.

sdcard should also show sdcard0 when tapped on. It doesn't though it does show the symlink in Root Explorer.
 

jose51197

Senior Member
Jan 15, 2012
808
654
26
Cartago
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews

just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??

Im using another sdcard mod forma this ROM ill upload tomorrow by no ill just attach the file needed for that
Uploaded to drop box since xda app can't do it
http://db.tt/XPJ59Ux0
Sent from my Incredible 4G LTE using xda app-developers app
 
Last edited:

mdmower

Senior Member
Sep 14, 2011
826
1,044
Yep, sure did.

sdcard should also show sdcard0 when tapped on. It doesn't though it does show the symlink in Root Explorer.

Another thing to check is whether you're using the latest recovery version. Changes had to be incorporated when Android 4.2 came out. I have used ClockworkMod 6.0.2.7 for all of my testing, but I assume TWRP 2.3.3.0 should also work (can anyone comment on their experience with TWRP and installing this ROM?).
 

jose51197

Senior Member
Jan 15, 2012
808
654
26
Cartago
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews

Another thing to check is whether you're using the latest recovery version. Changes had to be incorporated when Android 4.2 came out. I have used ClockworkMod 6.0.2.7 for all of my testing, but I assume TWRP 2.3.3.0 should also work (can anyone comment on their experience with TWRP and installing this ROM?).

I usted twrp no problem

Sent from my Incredible 4G LTE using xda app-developers app
 

blazingwolf

Senior Member
Nov 11, 2006
2,127
405
Well, my issue seems to be that my internal sdcard got toasted. Not sure how yet and as of now I have been unable to get it back.
 

mdmower

Senior Member
Sep 14, 2011
826
1,044
Well, my issue seems to be that my internal sdcard got toasted. Not sure how yet and as of now I have been unable to get it back.

Perhaps /system didn't get properly wiped and something from your previous ROM is hanging around. I would reboot to CWM recovery, wipe /sdcard and /system (I hope you made a backup of internal sd like instructed), then re-install cm. After installing CM, wipe /data and /cache.

Also, while in CWM recovery, you can check that internal sd is accessible by first mounting /sdcard, then trying to access it through adb:
Code:
adb shell
cd /sdcard
ls
 

blazingwolf

Senior Member
Nov 11, 2006
2,127
405
Perhaps /system didn't get properly wiped and something from your previous ROM is hanging around. I would reboot to CWM recovery, wipe /sdcard and /system (I hope you made a backup of internal sd like instructed), then re-install cm. After installing CM, wipe /data and /cache.

Also, while in CWM recovery, you can check that internal sd is accessible by first mounting /sdcard, then trying to access it through adb:
Code:
adb shell
cd /sdcard
ls

It won't mount. Tried both CWM and TWRP. They both say unable to mount sdcard.

Still working on it.

Hmm. Windows wants to format something.
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 49

    Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2

    Contents
    This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
    Post 2 - Restoring a non-functioning radio
    Post 3 - Frequently asked questions and workarounds for common problems

    Introduction
    This is CyanogenMod 10.1 (cm-10.1) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.2.2. Usage of this ROM indicates that you understand...
    1. the warranty on your device is void;
    2. the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
    3. there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).

    Preparations and Installation
    Get your phone ready for a new ROM
    1. You must have an unlocked bootloader or be S-OFF (read here for instructions)
    2. Before leaving your stock based ROM, turn on all GPS location services:
      Settings > Location > (all three location services) = On
    3. Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
    4. Install a custom recovery: CWM or TWRP
    5. Make a backup of your current ROM in recovery - DO THIS!
    Install CyanogenMod
    1. Perform the factory reset function in recovery and wipe the /system partition
    2. Flash the CyanogenMod zip and optionally flash the GApps version corresponding to CM 10.1.x
    3. If you are S-OFF, you're done; reboot and enjoy
    4. If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands:
      Code:
      adb reboot-bootloader
      fastboot flash boot boot.img
      fastboot reboot

    Updating to a new build
    1. Make a backup of your current build in recovery
    2. Install the new build
    3. If you are S-OFF, reboot
      If you are not S-OFF, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
    Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.

    Special notes about connecting to Verizon's network
    Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
    1. Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
    2. SIM card added: the first couple times you boot the phone you may get a notice, "SIM card added". Do not hit restart, just hit the back button and the notice will go away.
    3. Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.

    Official Downloads
    Official builds are available at download.cyanogenmod.org/?device=fireball
    Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
    If your display flickers noticeably after an hour or so of usage, discontinue use of these official releases (see below for unofficial releases that do not exhibit this issue). This issue affects about half of the fireball user base (rough estimate based on forum replies). These builds use linux kernel 3.4 which was never released by HTC for the fireball, so the board files are assembled as best possible with what little we have for reference. If your device suffers from this problem, you may notice the flickering persists for a few hours after restoring another ROM, but it should eventually subside. The developer(s) are not responsible for damaged devices as a result of running these builds. Stick with a stock-based ROM if you're uncomfortable with this.

    Unofficial Builds
    These builds are not endorsed by CyanogenMod. They are my personal builds.

    Most recent builds: goo.im
    Archive/Mirror: mediafire.com

    goo.im folder structure: visit the page to read release-specific notes
    • mdm-releases - Recommended for users that have flickering panels on official builds. Based on CM 10.1.2 stable using linux kernel 3.0
    • kernels - Enhanced kernels for use only in CM
    • cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
    • cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases

    GApps
    Download the GApps version corresponding to CyanogenMod 10.1.x

    Reporting Issues and Getting Help
    Policy on bug reports:
    1. You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
    2. logcat or GTFO
    If these steps are not taken, your report will be ignored.

    How to gather helpful data for troubleshooting
    How to use the issue tracker

    Getting help
    There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.

    Change Log
    CyanogenMod BBQLog

    fireball-specific changes:
    • 20130725 - fix blank MMS messages from iPhone 5 users
    • 20130723 - fix low in-call volume and raise speaker volume max
    • 20130721 - fix signal strength reporting zero on some GSM networks
    • 20130715 - fix front facing camera face detect crash, fix dim screen on wake
    • 20130628 - wake-on-volume fixed
    • 20130622 - camcorder can now record in all resolutions
    • 20130619 - finishing touches to battery parameters; charging should properly reach 100% now
    • 20130618a - stereo audio fixed
    • 20130618 - fix charging and battery level indicator
    • 20130616 - kernel 3.4 introduced, updated adreno driver blobs from Qualcomm
      ---- break all teh things ----
    • 20130504 - wake-on-volume fixed; flash and shutter synchronized better in camera
    • 20130424 - encryption of /data partition is now supported, read post 3 for instructions!
    • 20130306 - fix for selecting bands crashes com.android.phone, SMS/MMS behavior changes
    • 20130303 - camcorder video focus improvements (still loses focus, but should be better)
    • 20130226 - all resolutions save without restarting camcorder application
    • 20130223 - all resolutions available in camcorder (with quirks)
    • 20130221 - secure adb, experimental microphone noise suppression fix (amluto)
    • 20130217 - camcorder saves videos correctly
    • 20130209 - gooManager OTA support, camera focus fixed, notification led fixed
    • 20130207 - fixed audio applications freezing phone, sending mms messages should not return invalid destination, battery charging LED can be disabled
    • 20130204 - removed non-effective VZW APNs, enabled MTP support
    • 20130131 - experimental VZW APN configuration
    • 20130128 - initial Release

    Known Issues
    Official Builds
    1. Display flickers and gets worse the longer the phone is on (may not occur depending on specific panel in your phone) - if you experience this issue, discontinue use of the CyanogenMod nightlies until the bug is fixed
    2. Screen-on delay is long
    3. Audio pauses briefly during screen on/off events
    4. High pitch background noise in camcorder recordings
    5. Touch to focus doesn't work
    6. Flash crashes camera application
    7. The first few times the phone boots there may be a "SIM card added" notice
      Workaround in post 3

    Unofficial MDM Builds
    1. Moving between 1x and LTE networks sometimes requires toggling airplane mode to get data working
    2. Camcorder does not stay focused
    3. Music lock-screen widgets sometimes flicker when you turn on the screen; the controls are still active though
    4. The first few times the phone boots there may be a "SIM card added" notice - Workaround in post 3

    Known Issues that will not be fixed
    1. OTG mounting of USB sticks - Likely no hardware support
    2. FM Radio - Likely no hardware support
    3. MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
      Workaround in post 3

    Development Information
    CyanogenMod 10.1 builds using linux kernel 3.0 were becoming very stable before DxO Labs made a DMCA take-down request on a camera auto-focus library: libDxOAF.so. CyanogenMod had to pull official support for this device until builds could be offered that do not include this library. Kernel 3.4 no longer depends on the auto-focus routines in that library, so development efforts have gone into getting evita, fireball, jewel, and ville running well on it. Official nightlies are currently available for fireball, based on kernel 3.4, but there are a number of issues to be resolved (see above). Since HTC has not released an official jellybean ROM for this phone, there is no recent kernel source that could provide hints about how to fix these issues. If you have kernel development experience, your help would be greatly appreciated in fixing up the board files: android_kernel_htc_msm8960/arch/arm/mach-msm/htc.

    The following trees are needed to build CyanogenMod 10.1 based on kernel 3.4:
    1. CyanogenMod/android_device_htc_fireball
    2. CyanogenMod/android_device_htc_s4-common
    3. CyanogenMod/android_device_htc_msm8960-common
    4. CyanogenMod/android_kernel_htc_msm8960
    Use the extract-files.sh script in the fireball device tree while running an official cm-10.1 build to pull necessary proprietary files into vendor/htc.

    The following trees are needed to build unofficial CyanogenMod 10.1.2 based on kernel 3.0 (a.k.a. mdm-releases):
    1. mdmower/android_device_htc_fireball - branch cm-10.1-FbR
    2. mdmower/android_device_htc_msm8960-common - branch cm-10.1-FbR
    3. mdmower/android_kernel_htc_msm8960 - branch cm-10.1-FbR
    4. mdmower/android_frameworks_base - branch cm-10.1-FbR
    5. mdmower/android_frameworks_opt_telephony - branch cm-10.1-FbR
    6. mdmower/android_apps_Settings - branch cm-10.1-FbR
    Use the extract-files.sh script in the fireball device tree while running an unofficial mdm build to pull necessary proprietary files into vendor/htc.

    Credits
    The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
    19
    Restoring a borked radio

    In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.

    Downloads
    1. Stock ROM
    2. recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391

    Instructions
    1. From your preferred recovery, run the factory reset option
    2. Follow the directions in this thread to install the stock ROM
    3. Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
    4. Reboot to the bootloader
    5. Flash the stock recovery:
      Code:
      fastboot flash recovery recovery_signed.img
      fastboot reboot-bootloader
    6. Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
    7. Let the phone reset and boot up
    8. Allow network connectivity to be restored (make a test call)
    9. Turn on all GPS location services: Settings > Location > (all three location services) = On
    10. Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
    11. Reboot to the bootloader
    12. Flash your preferred recovery: CWM or TWRP
      (If you just want to run this stock ROM, you can stop here)
    13. From your preferred recovery, run the factory reset option
    14. Restore your ROM backup and wipe cache again before rebooting
    18
    13
    FAQ and Workarounds

    The solution to many problems
    Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!

    Stuck at the HTC boot screen (solution by Aldo101t)
    If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
    Code:
    fastboot flash boot boot.img
    Enable USB debugging or access Developer Options
    Settings > About phone > tap 'Build number' 7 times

    Screen flicker
    If after leaving the phone on for a few hours you notice the screen flickering rapidly, it is advised that you stop running the offical builds and restore a stock based image or one of the unofficial CyanogenMod 10.1 mdm-releases. You may still notice flickering for an hour or two after switching to a different ROM, but it should eventually subside.

    "SIM card added" or "Waiting on... activation" notice every time the phone boots
    SIM card added notice: do not hit restart, just hit back and the notice will go away
    Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).

    "What mobile network settings should I use?"
    Verizon Wireless users in the U.S.
    Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
    • Network mode = LTE/CDMA/EvDo
    • CDMA subscription = RUIM/SIM
    Do you have suggestions for other carriers and/or other countries? Let me know what settings work for you, as well as necessary edits to build.prop.

    Missing menu button in applications (solutions by blazingwolf and somerandomname1)
    Option 1: Re-associate the recent apps button: Settings > System > Hardware keys > Enable custom actions > App switch key
    Option 2: Use action overflow: Settings -> System -> Hardware keys > Show action overflow

    Text messages from 6250 with message VZWNM: # (solutions by Linch89, MJL99, and slacka-vt)
    See this thread and this post.

    ext_sd doesn't show files on the MicroSD
    ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.

    Examples:
    ES File Explorer: Settings > Path Settings: Home Directory = /storage/
    Root Explorer: Preferences > General Preferences: Home Folder = /storage/

    ADB reports device offline
    After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.

    Sound is distorted when DSP presets and/or bass boost are enabled or
    Gapless music playback doesn't work
    Set lpa.decode=false in build.prop:
    Step 1) Settings > Developer options > Root access: Apps and ADB
    Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
    Code:
    adb root
    adb remount
    adb shell
    # Make sure you have a # prompt now. If $ prompt, the following will not work.
    sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
    exit
    adb reboot
    To revert this change later, perform the same steps above, but swap true and false in the sed line.

    MicroSD will not mount as a mass storage drive when connected to the computer
    UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
    Settings > Storage > (menu) USB computer connection > MTP

    Windows and Mac recognize MTP devices automatically.
    Linux requires a bit more work, here's the quick instructions:
    1. edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
      Code:
      SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
    2. install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
      Code:
      sudo add-apt-repository ppa:langdalepl/gvfs-mtp
      sudo apt-get update
      sudo apt-get upgrade
      sudo apt-get install gvfs
    3. Restart your computer
    Phone number, MIN, and PRL do not show in phone status or
    MMS messages don't send: "Invalid destination"
    Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.

    "I'm running RC1 or RC2 and I refuse to update!"
    At least apply this small update package to fix low power audio and update the RIL to comply with changes to Verizon's network.

    GPS doesn't acquire a signal (solution by somerandomname1)
    1. From recovery, make a nandroid backup of CM
    2. Wipe data, cache, and system
    3. Restore a stock-based ROM backup
    4. Enable all location services: Settings > Location > (all three location services) = On
    5. Use a GPS application to get a lock on your position (I use GPS Test)
    6. From recovery, wipe data, cache, and system
    7. Restore CM backup
    8. Wipe cache and Dalvik cache
    Internal storage is not accessible by ROM or recovery
    This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
    1. Restart the phone to recovery and connect the USB cable to a Windows computer
    2. In recovery, use the mount USB feature:
      • ClockworkMod(-based): mounts and storage > mount USB storage
      • TWRP: Mount > Mount USB Storage
    3. When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
    4. After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
    5. Your /sdcard partition should now be accessible
    Encryption (thanks to Slick1123)
    Pre-requisites: TWRP 2.6.0.0 or newer

    Encryption procedure:
    1. Make a full backup in TWRP
    2. Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
    3. Reboot and let phone battery charge to 100%
    4. Turn on Airplane mode
    5. Settings > Security > Encrypt phone
      Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
    Reverting encryption:
    1. Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
    2. Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
    3. Wipe your data partition
    4. Restore your backup
    Using the Droid Incredible 4G LTE on non-Verizon carriers
    Remove the following lines from build.prop:
    Code:
    # Carrier definitions
    ro.cdma.home.operator.alpha=Verizon
    gsm.sim.operator.alpha=Verizon
    gsm.operator.alpha=Verizon
    ro.cdma.home.operator.numeric=311480
    gsm.sim.operator.numeric=311480
    gsm.operator.numeric=311480
    
    # Access to Verizon/HTC apps in Play store
    ro.com.google.clientidbase=android-htc
    ro.com.google.clientidbase.yt=android-verizon
    ro.com.google.clientidbase.am=android-verizon
    ro.com.google.clientidbase.gmm=android-htc
    ro.com.google.clientidbase.ms=android-verizon
    11
    Thread cleaned.

    If you have a general issue or one that is not ROM specific to this or not have any technical basis or logcat etc, please search and start a thread in Q&A.

    Some people confuse these dev threads with general support threads, but that is not quite accurate and these issues are sometimes better sorted in the Q&A forum so that threads like this remain development oriented.

    Thanks. :)