Database Info

[ROM] CyanogenMod-7 for Inspire & Desire HD: V7.0.3 (05/06/2011)

CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
cyanogen said:
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (howto).
INSTRUCTIONS:
- First time flashing CM 7 to your Desire HD (or coming from another ROM)?
1. Root your device and install ClockworkMod 3 Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Latest version: 7.0.3-DesireHD - 05/06/2011
Download: update-cm-7.0.3-DesireHD-signed.zip
Also available for download via ROM Manager
MD5Sum: 0bf02583cd1bf31021de17210ec56f37
cyanogen said:
The 7.0.3 update is *ONLY* for people using 7.0.2* stable builds. You'll hose your system if you install it on a nightly from the last week (2.3.4/GRJ22).
Click to expand...
Click to collapse
Google Addon: 20110307 Universal
Download: http://goo-inside.me/google-apps/
RC3 fixes DSP drain issue, thank's to hrkfdn and mad-murdock
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!

Thank you Kali and the entire CM team!!!!
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.

so is this better than 14?

Thanks Kali!
Currently running RC2, and everything is working very well. Running the stock radio, and HSUPA is obviously working with a Speed test of 2.1 mbps up. The issues with the proximity sensor I had experienced with earlier nightlies has been cleared up as well. I have ran all day at 1401 MHZ, and battery life has been fine. The ROM feels smooth, and I just posted a Quadrant score of 2250, for those that are interested in that sort of thing.
I've ran every other ROM out there, including the new ones based on the leaked HTC Gingerbread build. No other ROM feels as smooth as CM on my Inspire.
I did do a full wipe (including Dalvik) before I installed RC 2, which may account for the complete absence of troubling issues. The only thing worth noting is that you need to reboot the system after the initial setup BEFORE you connect to wireless. Not everyone has reported this issue, but I have had to do this every time I run a fresh install of CM.

So flash Tom and Google addon. There is no sound or GPS fix needed, correct? Haven't flashed cm7 since #11 so was excited to see this post.
Sent from my Inspire 4G using XDA App

Yep - the audio/gps fix is already included in RC2. :-D

the dsp fix version 5 still requires you to run google voice dialer to initialise the fix, otherwise the command returns the aic3254 status ON. fix is still broken.

close! I'll wait for the battery drain fix then jump aboard

fwayfarer said:
the dsp fix version 5 still requires you to run google voice dialer to initialise the fix, otherwise the command returns the aic3254 status ON. fix is still broken.
Click to expand...
Click to collapse
I'm aware that a true DSP fix is in process and not yet implemented; Blaine was asking about the audio/gps fix we had to flash on the pre-12 nightly builds.

palletguru said:
I'm aware that a true DSP fix is in process and not yet implemented; Blaine was asking about the audio/gps fix we had to flash on the pre-12 nightly builds.
Click to expand...
Click to collapse
the fix states,
Version 5 no longer requires Google's voice search or voice dialer to be used once after every reboot to correctly initialize the fix
Click to expand...
Click to collapse
this is what i was referring to, and it is NOT true. you MUST still run the google voice dialer to initialize the fix, or it will still pull 200+ mA, and the dsp chip will NOT turn off. sorry for the confusion.

Great to know, appreciate the input. Downloading now
Sent from my Desire HD using XDA App

I would like to give this a shot. I love CM7 on my Nexus One. RC1 just didn't seem smooth on my inspire.
Sent from my Desire HD using XDA App

How is this thread any different than the other CM7 thread that's been up for a while?

symonc said:
How is this thread any different than the other CM7 thread that's been up for a while?
Click to expand...
Click to collapse
The other thread is dedicated to the discussion of the nightlies.
Sent from my Desire HD using Tapatalk

flashed, and with the screen being off most of the time in a little over an hour i went from full to 85%, thatsd a litttle too much so i will wait until a proper battery fix is released and then happily flash this again as i liked it alot

big deal breaker is no group sms or one that i can figure out. also deleting threads one at a time or delete all. no way to select which ones

wish there was calibration settings for the keyboard recognition and the g-sensor like the stock rom has.

After flashing this i cant seem to get a GPS lock It finds maybe 3 and thats it. Is there a fix for this? (Telus DHD)

This rom is great BUT, i cant mount my sd cards. Every time it tells me the sd card is damaged. I've tried 4 different cards. They all dont mount.
EDIT: I flashed back to Revolution and sd cards work fine so its definitely a ROM issue.

equlizer said:
After flashing this i cant seem to get a GPS lock It finds maybe 3 and thats it. Is there a fix for this? (Telus DHD)
Click to expand...
Click to collapse
the fix should be included. you say it does find up to three satellites?

The CyanogenMod 9 User Thread.

The fourm is becoming to full with CM9 related threads. Just to help cut down on the same threads. Here will be the unofficial thread to talk about CM9. As Tbalden, and Kornyone asked us NOT to talk about bugs on the main thread. But to report issues to. http://code.google.com/p/teamds/issues/list
I see some users are using it, but we should get ALL. So come here to complain about anything CM9!

kornyone said:
CyanogenMod 9 is a free, community built distribution of Android 4.0 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
This is an alpha release, but you should find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an alpha, with most critical functionality working.
Working with Senior CyanogenMod team members, I brought TBalden into the project. TBalden has brought his large amount of Doubleshot experience to CyanogenMod Doubleshot porting, and together we have created (in very short order) a stable Alpha. TBalden created a team for maintenance of the Doubleshot with CyanogenMod going forward, "TeamDS".
INSTRUCTIONS:
- Upgrading from previous Doubleshot CM9 Alpha?
1. It should be safe to flash the Alpha5 zip on top of previous alphas. DO backup your phone in case something goes wrong, but a wipe shouldn't be necessary coming from CM9 Alpha1.
NOTE that the install wipes /system, so you may find you need to reflash gapps.
- First time flashing CM 9 to your MyTouch4g Slide (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager.
2. Do a Nandroid backup!
3. WIPE
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Follow instructions above. CM upgrade from CM7 Alpha1 will likely incur weird issues.
HOW TO REPORT BUGS OR PROBLEMS?
- Was your problem a hard reboot? Get us the file "/proc/last_kmsg".
- Was your problem a soft reboot or a "boot loop"? Run "adb logcat" and get the full output.
- Pastebin links preferred.
- For now, please leave comments in the forums. TBalden and I will will be monitoring for activity as we continue to fix known issues.
- Join #TeamDS on Freenode to talk to us directly.
Direct download URL: http://www.jeago.com/doubleshot/cm-9-alpha6-doubleshot-signed.zip
Alpha6 MD5: f9f0e4d95d7802e6ccb3b938b69ef7e0 . Build date 20120723.
(hosted by Jeagoss of CyanogenMod, thanks!)
You can find the latest CyanogenMod GAPPS CyanogenMod Wiki. Bottom of page, "CyanogenMod 9" GAPPS (latest works as of writing).
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
As of Alpha4, Doubleshot source (device and kernel) has official open source CyanogenMod repos, with Gerrit access (https://review.cyanogenmod.com)
----- CHANGES -----
Alpha6 Changelog (from Alpha5)
- Updated kernel base to v3.0.36 from upstream AOSP branch.
- Updated keylayout. TAB now mapped to ALT+TAB, www./.com functions properly.
- Camera is no longer crashing (in our testing). This is from an upstream CM frameworks change.
- Bluetooth wake lock is "fixed". When paired with handsfree audio, etc, and in standby, deep sleep works as expected.
- Bluetooth tethering is functional, though not 100% yet.
- Upstream changes in CyanogenMod. See http://review.cyanogenmod.com/#/q/status:merged,n,z for info on these Upstream changes.
Please note that camera and bluetooth functionality are still a work in progress. In testing, we find more compatibility, less crashing, less power consumption overall. If you find steps to reproduce crashing, etc, please capture logs.
The current buglist:
- If you use Face Unlock, I have experienced an issue where sometimes the screen will go "dark" when attempting to unlock the phone, requiring a battery reset. This is infrequent, but only Face Unlock causes this problem.
- Recording in camcorder @ 1080 doesn't work. (Other modes are fine, we have not removed 1080p from options yet).
- Lights issues (more than one):
-- Function keys on physical keyboard do not light up (CAPS/ALT), but the buttons work.
-- Backlight on keyboard works most of the time, but can randomly go dark.
- Random battery statistics issues. Not all people have this issue, it seems specific to the battery you use.
- Google+ Hangouts do not work right now.
- Very occasional radio (4g and sometimes bluetooth/wifi) dropoff/reset. Some have reports a SIM card message requesting power reset, which can be cleared by hitting back. Other times, turning data on/off resolves issue.
Please note flashing someone else's kernel may ruin your experience with this rom and I advise against it. This rom was a joint effort between kornyone & tbalden. A LOT of core works for msm8660 was put in by many CM Team members, and much of our work is based on their: toastcfh, Kali-, Kmobs, Bumblebee, cretin45, and all of the rest of CM!
You can get all of the Doubleshot source from the following URLs:
https://github.com/CyanogenMod/android_device_htc_doubleshot/
https://github.com/CyanogenMod/htc-kernel-doubleshot
https://github.com/TeamDS/vendor_htc_doubleshot
CyanogenMod source is available from CyanogenMod Github
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
http://code.google.com/p/teamds/issues/list
(Added 5/11) Join us on freenode, #TeamDS, if you would like to chat about this rom or provide help with fixes.
(Added 5/14) Updated to Alpha2.
(Added 5/23) Updated to Alpha3
(Added 6/8) Updated to Alpha4
(Added 6/27) Updated to Alpha5
(Added 7/23) Updated to Alpha6
(Added 7/26) Added Bug tracker http://code.google.com/p/teamds/issues/list
Click to expand...
Click to collapse
Sent from my Bulletproof_Doubleshot using Tapatalk 2

Alpha 6 Bug List:
Battery Drain with the new Linux 3.0.36 Kernel.
::Most Devs aren't using the 3.0.36 Kernel. They're back porting certain features. Like Faux http://rootzwiki.com/topic/31344-kernel004ap3315ghz-uvcifsutf-8powerhallinux-3x-hybridaug-01/ ::
WiFi Issues: Dropping in and out.
Most People are going back to Alpha 5 ATM. If your camera worked on A5. Then you should use it.

AgentCherryColla said:
The fourm is becoming to full with CM9 related threads. Just to help cut down on the same threads. Here will be the unofficial thread to talk about CM9. As Tbalden, and Kornyone asked us NOT to talk about bugs on the main thread. But to report issues to. http://code.google.com/p/teamds/issues/list
I see some users are using it, but we should get ALL. So come here to complain about anything CM9!
Click to expand...
Click to collapse
Does it matter how minor the bugs are or if they're incredibly random? I made a post yesterday to mention a few small glitches with CM9 but I don't want to report them if no one else might be seeing what I saw with my phone.
I can understand reporting an issue if it's possible to replicate it but if it's random in nature like mine is, how can it be addressed if only one person is seeing it?

Any and all bugs. Since this is a user thread, we can report anything.
Sent from my Bulletproof_Doubleshot using Tapatalk 2

Battery drain and random wifi-related reboots.
Sent from Spaceball One.

AgentCherryColla said:
Alpha 6 Bug List:
Battery Drain with the new Linux 3.0.36 Kernel.
::Most Devs aren't using the 3.0.36 Kernel. They're back porting certain features. Like Faux http://rootzwiki.com/topic/31344-kernel004ap3315ghz-uvcifsutf-8powerhallinux-3x-hybridaug-01/ ::
WiFi Issues: Dropping in and out.
Very, Very Slow USB speeds.
Most People are going back to Alpha 5 ATM. If your camera worked on A5. Then you should use it.
Click to expand...
Click to collapse
Sent from my Bulletproof_Doubleshot using Tapatalk 2

Hey guys,
Today i had complete data dropout on Alpha 6. Tried everything i could think of including fixing permissions, several reboots (through cyano & by removing battery), reconnecting to APN's, airplane mode & back, etc and could just not get it to work. It would look like it connected to 3G every once in a while but it would stay like that for less than a second and then go back to all white bars.
Finally flashed back to a nandroid of Alpha 6 from before I flashed the A6 Kernel and my data came back.

RUGGNATION said:
Hey guys,
Today i had complete data dropout on Alpha 6. Tried everything i could think of including fixing permissions, several reboots (through cyano & by removing battery), reconnecting to APN's, airplane mode & back, etc and could just not get it to work. It would look like it connected to 3G every once in a while but it would stay like that for less than a second and then go back to all white bars.
Finally flashed back to a nandroid of Alpha 6 from before I flashed the A6 Kernel and my data came back.
Click to expand...
Click to collapse
Mine too on Friday. I wiped cache and dalvik and it seemed to help.
Hastily spouted for your befuddlement

I'm on A5, and left my phone charging for 24 hours. Then calibrated it. Stellar battery.
Sent from my myTouch_4G_Slide using Tapatalk 2

AgentCherryColla said:
Sent from my Bulletproof_Doubleshot using Tapatalk 2
Click to expand...
Click to collapse
How do I get the official? Because I downloaded everything from here and followed every step and on bout phone it says not official cm9..help?
Sent from my myTouch_4G_Slide using xda premium

fozzy501 said:
How do I get the official? Because I downloaded everything from here and followed every step and on bout phone it says not official cm9..help?
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
There isnt an official cm9 build yet. Unless its not edited to show so in the ROM info. Its public and blah blah with " official cm support" but whatever
Sent from my myTouch_4G_Slide using Tapatalk 2

Wifi not working for me on Cyagenmod 9 alpha 6
Hopefully this is the right place to post this. I'm very new to flashing custom ROMs, but I am an experienced Linux admin so I'm not a total noob. I flashed cyagenmod 9 alpha 6 and everything seems to be working well except I don't have any wifi. If I try to enable wifi, it just hangs.
I launched the terminal application and ran /system/bin/ifconfig and it didn't return anything. I wonder if I need to install kernel modules or update radio or something.
Could someone point me in the right direction or help me debug this?
Thanks,
Tim

If you are S-On, did you pull the boot.img from the rom zip and use fastboot to transfer it to the phone?
http://forum.xda-developers.com/showthread.php?t=1508556

Yes, I am S-On, and I have transferred the boot.img from the rom zip to my phone using fastboot. I just did it again just to be sure and I still have the same issue.
QUOTE=txmtb;30627497]If you are S-On, did you pull the boot.img from the rom zip and use fastboot to transfer it to the phone?
http://forum.xda-developers.com/showthread.php?t=1508556[/QUOTE]

Ooo okay.and my phone of course if 4g but on the bar it says its 3g or an H wat does that mean and how do I gt my 4g back?
Sent from my myTouch_4G_Slide using xda premium

fozzy501 said:
Ooo okay.and my phone of course if 4g but on the bar it says its 3g or an H wat does that mean and how do I gt my 4g back?
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
H = T-Mobile 4G
H = HSPA
The 4g but is just an icon. When it flips back and forth between 3g and H instead of staying H/4G you are seeing the device kick into that faster protocol as needed and throttling back when it isn't needed.
Hastily spouted for your befuddlement

I'm running CM9_A6 but with Alpha 5's kernel. You can flash it in a nice update.zip by wildchild right here. I'm getting the same battery life I got with stock, GB sense, etc. I'd also recommend the Anker 1900 mah battery (x2) with charger for $30 for a few extra hours of battery life. It's well worth it:cyclops:
---------- Post added at 05:50 AM ---------- Previous post was at 05:33 AM ----------
Coug76 said:
H = T-Mobile 4G
H = HSPA
The 4g but is just an icon. When it flips back and forth between 3g and H instead of staying H/4G you are seeing the device kick into that faster protocol as needed and throttling back when it isn't needed.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
yup... it's flipping from UTMS (lower power/speed) to HSPA(in most cases HSPA+) to save battery, network congestion, etc. As you said... they are just icons located in framework-res.apk... You can change 'em to say 5G lol! I did a few mods for some ICS themes on CM7 for HTC Vision. I should redo some for CM9. Basically, just change the H to H+, H to 4G, E to 2G, etc... I could redo them if anyone's interested. It's nothing too complicated: extract and decompile apk, edit pngs via photoshop, replace images, recompile and sign:silly: I really need to play around with ICSeseses framework some. ALOT has changed since GB. I wish I had as much time as I had hoped when I first got the DS. Work, home, life has kept me way more busy than I'd like lol! Well... getting off track here. My bad

tgoodaire said:
Yes, I am S-On, and I have transferred the boot.img from the rom zip to my phone using fastboot. I just did it again just to be sure and I still have the same issue.
QUOTE=txmtb;30627497]If you are S-On, did you pull the boot.img from the rom zip and use fastboot to transfer it to the phone?
http://forum.xda-developers.com/showthread.php?t=1508556
Click to expand...
Click to collapse
[/QUOTE]
You need to flash the boot.img right before 1st boot. Or wire trick S-Off. The weekend is coming up, and it's a fun little project.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

fozzy501 said:
Ooo okay.and my phone of course if 4g but on the bar it says its 3g or an H wat does that mean and how do I gt my 4g back?
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
I've worked for T-Mobile many times. They do not have "True 4G". How I see it, it's faster 3G. CyanogenMod says that T-Mobile is not 4G. That's why it's an H, for HSUPA. T-Mobile says it's 4G, but LTE is legit 4G. LTE has much more faster speeds that HSUPA.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

[OFFICIAL]CM10 Official Nightlies for D2VZW GSIII

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD

So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?

Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.

Do these include google now, if not where can I get it?

ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse

Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium

Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies

WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.

Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2

Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.

ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)

neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk

Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III

TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:

XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III

Can I use TWRP recovery to flash this Rom?

TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.

neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium

Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6

WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.

[ROM][AOSP][DEV][WIP][S4] Unofficial OmniROM 4.4 CLOSED!

Why Omni?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Taken from http://omnirom.org/why-omni/
Screenshots and more info are here
BACKUP YOUR PHONE!!!
* Your warranty was void when you started messing around with your phone.
* These builds are unofficial and are unsupported.
* ONLY YOU AND NO ONE ELSE IS RESPONSIBLE FOR ANYTHING BAD THAT MIGHT RESULT FROM FLASHING THIS ROM!
* Finally Blah Blah Blah good luck!
This ROM probably has the same requirements as any other AOSP 4.4 based rom with the 3.4.x kernel.
Nandroid and then a full wipe.
ROM when its up you can Download Here
PA 0-Day Gapps Get it here
if needed SuperSU 1.75
KNOWN BUGS
Probably whatever is wrong with other KitKat 4.4 roms so...you tell me?
This is based on work done by xHausx for the HTC Evo 4g LTE. You can view the original thread HERE
Thanks
Especially xHausx for the device and common repos and for taking the time to help me get the build process running.
intervigilium for kernel and device repos, because without him most HTC devices would still have Sense
XpLoDWilD, pulser_g2 and all of Team OmniROM
CM for the various repos and for all they've done for the community
XDA:DevDB Information
OmniROM, a ROM for the HTC One S
Contributors
mo976, xHausx
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Abandoned
Created 2013-10-31
Last Updated 2013-12-03

Reserved
NO SD CARD!!!
A fix is being worked on but... NO ETA's

Looks promising. Cant wait to try it.
Thanks for keeping the One S alive.

Gotta try this! Thanks
Sent from my One S using XDA Premium HD app

HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.

nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong

nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
yooouuri said:
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
Click to expand...
Click to collapse
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.

mo976 said:
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
Click to expand...
Click to collapse
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack

Flashalot said:
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Click to expand...
Click to collapse
Well I'm trying anyhow after going through the various dependency files just to double check. I'm hoping it was just a bad build or something so I am pulling down the repo from scratch and hopefully will have a new build in a few hours.
Sent from my One S using XDA Premium 4 mobile app

Looking forward to this
And maybe try the 1.20 radio...

First working build is up try it out let me know!

mo976 said:
First working build is up try it out let me know!
Click to expand...
Click to collapse
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.

nespresso33 said:
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
Click to expand...
Click to collapse
I noticed that but wasnt sure if its a feature or bug...lol it seems to come and go...

If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone

yooouuri said:
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
Click to expand...
Click to collapse
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app

mo976 said:
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/

yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
I will check if that's whats missing. I am not sure how to disable strict mode by default since its a setting. Lock screen delay should be the same as cm since its the same kernel.
Sent from my One S using XDA Premium 4 mobile app

yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.

mo976 said:
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
Click to expand...
Click to collapse
Maby a logcat will give the information you'll need?

yooouuri said:
Maby a logcat will give the information you'll need?
Click to expand...
Click to collapse
I understand what it says but...it may as well be Chinese because I am not any closer. I attached if you want to take a look.

Cyanogenmod 11

Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !

Atlantic_Rim said:
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Click to expand...
Click to collapse
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk

i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Ok thanks for reply !
Then I think I will wait for the official release, because I want a fully functional version for my moto G

Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app

will8578 said:
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I know the great job devs are doing for us before the moto G I had a LG optimus L7 and thanks to cyanogenmod I had kitkat on it.
But as far as this phone just came out, I'm asking myself if it's good to avoid my warranty just to have the same version of android ...
(correct me if I say bad words because I have to train my english :laugh: )

Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app

will8578 said:
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks

i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.

Entropy512 said:
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Click to expand...
Click to collapse
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.

i_rnb said:
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
Click to expand...
Click to collapse
There could be risks if you flash an unofficial build from someone who is not at all working on merging a device into CM - they often cherry pick all sort of stuff that causes incompatibilities with upstream to the point where the product really shouldn't be called CM. (I've seen lots of "CM" kangs that had all sorts of extra crap added beyond just doing what is required for device bringup...)
dhacker, however, is an official CM maintainer for many devices, so his builds are the ones that are "on track" for official inclusion.

OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out

U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app

will8578 said:
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK thanks, then I think I will flash the unofficial ROM when I have time

Atlantic_Rim said:
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
Click to expand...
Click to collapse
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.

Entropy512 said:
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Click to expand...
Click to collapse
Ok thanks for the informations ! After one hour of intense fighting with my computer, I finally unlocked bootloader, rooted, and flashed cyanogenmod I prefer this rom to the stock one, I find it more smooth, and more costumization

i think its ok for daily use. At least i use it everyday.

I posted this question in a couple other places, but no reply.
I have the GPE version of the Moto G, and I want to run the CM11 builds on it.
Will the fact that the GPE version has the ext4 fs on it prevent me from getting these to work?
I know there are recoveries available specifically for the GPE, but will getting the CM11 builds to work be just a matter of changing a few entries in fstab?
And finally, do either of the recoveries allow you ro format /data from either f2fs to ext4 or the other way around?
Thanks/

I've replaced stock Rom (4.4.2 US Global Version) for unofficial CM11 (2014-02-16's release) and for now CM works more stable than stock.
I had few reboots or issue with .flac, in CM's everything is OK, for now of course. Very good stuff even that is only nightly's release.