Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
This version is a release candidate, but you will 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Captivate, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official posthttp://forum.cyanogenmod.com/topic/...-the-samsung-captivate-v710-rc1-26-june-2011/CyanogenMod:
Latest Version: update-cm-7.1.0-RC1-Captivate-signed.zip
Download: Link
Mirror: Link
MD5sum: 0c32e6e5a37078e95154349fb69f3bb6Google Apps addon:
Version: gapps-gb-20110613
Mirror: Link
Mirror: Link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
I'm confused.
Interesting, gonna try this one out.
Sweet sauce!
Sent from my SGH-I897 using XDA Premium App
Can I flash it with ATT GB Bootloader?
ninjuh said:
I'm confused.
Click to expand...
Click to collapse
Me too. How is this different from the other CM7 thread?
doctahjeph said:
Me too. How is this different from the other CM7 thread?
Click to expand...
Click to collapse
nevermind I think I just answered my own question. another question though? are the nightlies pre RC1? that is how it is shown with the changelog with 40 being before RC1. So 41 will be post RC1?
doctahjeph said:
Me too. How is this different from the other CM7 thread?
Click to expand...
Click to collapse
This one is RC1
doctahjeph said:
nevermind I think I just answered my own question. another question though? are the nightlies pre RC1? that is how it is shown with the changelog with 40 being before RC1. So 41 will be post RC1?
Click to expand...
Click to collapse
the difference between RC and nightlies is RC is considered (mostly) stable and users are allowed to post issues/bugs to the issue tracker. nightlies will never be allowed to post, but even RC1 users can. nightlies will continue to be built between stable releases (there will continue being nightlies after RC1/before RC2... and after RC2/before RC3--if there is an RC3--until the final stable build is released) until there is no longer a use for nightlies.
Jemack said:
This one is RC1
Click to expand...
Click to collapse
yeah I figured it out.
Kaik541 said:
the difference between RC and nightlies is RC is considered (mostly) stable and users are allowed to post issues/bugs to the issue tracker. nightlies will never be allowed to post, but even RC1 users can. nightlies will continue to be built between stable releases (there will continue being nightlies after RC1/before RC2... and after RC2/before RC3--if there is an RC3--until the final stable build is released) until there is no longer a use for nightlies.
Click to expand...
Click to collapse
word that is what I figured. Thanks!!
What about CM7 issues like battery drain?
Nightly #33 was on my captivate yesterday, #40 this morning, RC7.1.0 tonight, and by tomorrow, ... back to the nightlies. Stable for an instant.
(All these rom flashes... are like tears... in the rain...)
And I thought I was going to sleep. Silly me
Sent from my Captivate
OP says to flash from ClockworkMod Recovery: Does it matter what version?
OP does not mention what boot loaders should be used. Are the new AT&T I897 GB loaders okay to use?
Thanks!
I was on the nightlies and was using Froyo Bootloaders. I think you can use One-Click to go back to Elclair and see how it goes.
Wow great work, this is a mile stone
For our device.
Thanks
Sent from my GT-I9000 using XDA App
arffer said:
OP says to flash from ClockworkMod Recovery: Does it matter what version?
OP does not mention what boot loaders should be used. Are the new AT&T I897 GB loaders okay to use?
Thanks!
Click to expand...
Click to collapse
wiki instructions clearly say to flash from Froyo, and those are the instructions to use
don't forget to backup /efs folder everyone. this fried my efs folder on the first install and i had to recover it from backup. working great now though with no /efs issues.
Edit: Not saying the rom did it or anything. Sometimes efs just gets rubbed the wrong way during a rom install and jacks up your imei.
Flashing from a froyo-based rom okay?
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
PonsAsinorem said:
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
Click to expand...
Click to collapse
Don't mind me...I forgot I was in the Omni boards and not my local device sub-forum
lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Entropy512 said:
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Click to expand...
Click to collapse
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
I've been flashing OmniROM on my Note II since the very first day only using TWRP. Before that not a single nightly zip of CM 10.1/2, PA or PAC was a problem.
Sent from my GT-N7100 using Tapatalk
lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
Today I installed OMNI ROM 4.4.2 on Galaxy Note with CM 10.1 + CWM (6.0. ...)
- it works Ok.
Generally I followed the "Installing Omni on your device" instruction at docs.omnirom.org
- excluding TWRP installing
- I downloaded Google Apps for Android 4.4 from CyanogenMod site (gapps-kk-20140105-signed.zip)
Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
Only thing I can think of is TWRP is out of date and needs updating for that device, or there are updated TWRP builds and you're not running one.
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
What does that have to do with this thread?
libm compiles just fine as it is in omni - if it didn't, then none of our nightlies would build
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
dibblebill said:
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
Click to expand...
Click to collapse
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
lozohcum said:
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
Click to expand...
Click to collapse
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
dibblebill said:
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
Click to expand...
Click to collapse
No problem. Thanks for replying, it helped me.
Once the first build is finished I'm going to change recovery.
lozohcum said:
No problem. Thanks for replying, it helped me.
Click to expand...
Click to collapse
If setting up the local_manifest gives issues, let me know- I can try to sort one out for you. I've replaced packages like Calculator, but never the recovery.
AOSPA 5.0 For FALCON
INSTRUCTIONS
DOWNLOAD ROM
INSTALL GAPPS
DOWNLOAD BOOT ANIMATION FIX [Thank you KRize]
REBOOT TO RECOVERY
WIPE DATA/FACTORY RESET (If coming from another rom or stock)
WIPE CACHE
WIPE DALVIK CACHE
FLASH ROM, then GAPPS, then BOOT Fix, then MMS fix.
REBOOT
CUSTOM KERNELS MAY BREAK ROOT, SIMPLY RE-FLASH SUPERSU
XDA:DevDB Information
AOSPA 5.0, ROM for the Moto G
Contributors
Lucas Eugene, Seraph08
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Testing
Created 2015-03-04
Last Updated 2015-03-04
Notes Regarding cdma variant
This build does not support cdma devices as of now. Calls, sms, data won't work. Rest everything is fine
Screenshots
I Have xt1033 dual Sim
Lucas Eugene said:
Screenshots
Click to expand...
Click to collapse
Dual Sim Support?
Why 5.0 and not 5.0.2?
Thanks for the build and sorry for any stupidity said!
And why is the kernel 3months old? Sorry for this question but it is not normal
moralesnery said:
Why 5.0 and not 5.0.2?
Thanks for the build and sorry for any stupidity said!
Click to expand...
Click to collapse
It's 5.0.2
jonas210678 said:
And why is the kernel 3months old? Sorry for this question but it is not normal
Click to expand...
Click to collapse
The ss opus of the first build the new one has kernel of March 02
possible to make some scrennshots please? (homescreen, app drawer, parameters, etc...)
bilatche said:
possible to make some scrennshots please? (homescreen, app drawer, parameters, etc...)
Click to expand...
Click to collapse
It's the same as aoosp 5.0.2 with cm themes
WHy is this posted in general section? please move it to android dev
srisurya95 said:
WHy is this posted in general section? please move it to android dev
Click to expand...
Click to collapse
This is a share of a rom. And according to xda rules it's supposed to be in the gen section
But I think I'll build one myself with the cdma fix and upload it
srisurya95 said:
WHy is this posted in general section? please move it to android dev
Click to expand...
Click to collapse
Cause it's not his rom, it's built by Seraph08 a personal friend of mine
You can find more of Seraph08's builds on AF in Moto G CDMA ATR section
Installation Instructions:
1. Download CM21.1 Nightlies from: GET.CM
2. Download GAPPS from: LINK
3. Place on SD card(internal storage)
4. Reboot to recovery, Install XXX-bacon.zip, Install gapps.zip
5. Reboot and enjoy
Changelog
If you want to know the bleeding edge of what is being worked on/Merged
1. CM Gerrit
3. CM Google+
UPDATES
1. Bugs anyone?
2. Third party kernels are not supported by CM, try them out but YMMV.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lets try and keep this thread clean. Please use search, there is no need for the same question being asked and answered every few pages.
XDA:DevDB Information
CyanogenMod 12.1, ROM for the ONEPLUS ONE
Contributors
eak1080
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Built In
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-04-18
Last Updated 2015-04-17
Thank you. Looking fwd to flashing this
eak1080 said:
Download CM21.1 Nightlies
Click to expand...
Click to collapse
Whaou !!!!!
In on first page
Will monitor this and try sometime later. [emoji1]
kholdstare21 said:
Will monitor this and try sometime later. [emoji1]
Click to expand...
Click to collapse
It's as ready to go as cm12 is. It feels just as stable to me. YMMV but it's far more stable than the early cm 12 nightlies.
tiny4579 said:
It's as ready to go as cm12 is. It feels just as stable to me. YMMV but it's far more stable than the early cm 12 nightlies.
Click to expand...
Click to collapse
I have to agree - fast and rock steady! The only thing I can't find is how to scramble the pin numbers on the lock screen and how to not have to hit the enter arrow...
Smooth as ever. Love the animation
Sent from my A0001 using Tapatalk
Why do they include the older 330 radio instead of the 341 from oxygen ?
Because that's THEIR radio
1. Download CM21.1 Nightlies from: GET.CM
2. Download GAPPS from: LINK
3. Place on SD card(internal storage)
4. Reboot to recovery, Install XXX-bacon.zip, Install gapps.zip
5. Reboot and enjoy
Click to expand...
Click to collapse
So dirty flash will work?
iamkrazee said:
So dirty flash will work?
Click to expand...
Click to collapse
Yes, but if you experience issues you should do a full wipe.
Dirty flash over the last CM12 nightly, along with system / cache and dalvik (LOL) cache wipe, SLIM zero gapps, latest stable SuperSU release and Boeffla kernel latest beta. All seems fine so far.
I dirty flashed from previous nighly and now my OPO is in a bootloop.
Wiped cache/dalvik/system to no avail
Now I'm trying a full wipe, but I'm not really happy, don't have daily backups.
Igazine said:
I dirty flashed from previous nighly and now my OPO is in a bootloop.
Wiped cache/dalvik/system to no avail
Now I'm trying a full wipe, but I'm not really happy, don't have daily backups.
Click to expand...
Click to collapse
Install 5.1 gapps, should fix it
how do I activate heads up notifications? I can't find an option
eak1080 said:
1. Download CM21.1 Nightlies from: ...
Click to expand...
Click to collapse
Finally CM21.1 is out! How long will we have to wait for CM21s?
Has anyone dirty flashed from CraZY_BoY^ unofficials?
Any problems at all?
Dirty flashed from cm12 nightly + flash gapps 5.1. No problems.
Hey guys, does it need flashing SuperSU? I'm going to dirty flash from unofficial 12.1
Stek90 said:
Hey guys, does it need flashing SuperSU? I'm going to dirty flash from unofficial 12.1
Click to expand...
Click to collapse
no......
First I want to say I didn't build this rom, or have anything to do with Mokee Open Source. Any bug reports or feature requests should be directed to Mokee developers.
I only started this thread to provide a link to the roms, as they are not available on xda until now, and a lot of users may not be aware they are still around.
Personally I have found this rom to be very stable, with some nice features.
Links:
Mokee Official Site
Mokee on Google+
Changelog
Bug Tracker
Official Rom Releases
http://download.mokeedev.com/?device=i9100
Recommended Gapps
Open Gapps
Warning(particularly for MM builds): If you try to flash gapps, you will probably find it won't fit on the stock /system partition. In this case you will need to repatition - Repartitioning guide.
Make sure you choose a pit file that increases /system and not just /data(eg, I91001GB_4GB.pit)
Alternatively use Lanchon's re-pitting tool if you want to avoid losing your data
If you want to donate to Mokee and make their life a bit easier(donations will go towards bandwidth etc),
you can donate HERE
Instructions
1. Wipe data/factory reset(from KK compatible recovery)
2. Format /system
3. Flash rom
4. Flash gapps(optional)
5. Flash isorec recovery(for MM, see below), you only need to do this once
6. Reboot
Credits
- Mokee Developers
- CyanogenMod
- AOSP
- SlimRoms
- OmniRoms
Note: Now that Marshmallow(6.x.x) has been released, a warning for anyone flashing these latest nightlies. The kernel(isorec CM kernel) comes bundled with CM recovery, which is more or less useless. If you want a working recovery, you will need to flash the rom, followed by gapps(if you want play store), followed by an isorec recovery from HERE
Be sure to flash either CWM or TWRP for i9100. It is obvious from the name of the file.
And read about Isorec if you are not sure.
Thank you to @Troubadour666 for the Youtube review
Thank you @noppy22 for starting this thread. I had been downloading the ROM from G+ but the added benefit of a thread here on xda means that you have fellow S2 users to discuss problems etc with. Thank you again mate.
downloading....
thx for share
Thank you for the rom....downloading :good:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Drhedphuk said:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Click to expand...
Click to collapse
Mokee has already got my twrp recovery as I supplied it to them back in june 2015
@arnab Thank you.
Drhedphuk said:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Click to expand...
Click to collapse
I've only run it with stock kernel. The only thing I changed(with Kernel Audiutor) was i/o scheduler to row. I suspect any cm12.1 compatible kernel will work. I might give one of Lanchons trim kernels a go in the next day or so
Edit: I tried the last trim/twrp kernel and got bootloop on 160102 build....
noppy22 said:
I've only run it with stock kernel. The only thing I changed(with Kernel Audiutor) was i/o scheduler to row. I suspect any cm12.1 compatible kernel will work. I might give one of Lanchons trim kernels a go in the next day or so
Click to expand...
Click to collapse
Hi mate, I tried Lanchons isoRec kernel when flashing and it bootlooped. Xposed failed to flash for me too.
Thanks for getting back to me.
Drhedphuk said:
Hi mate, I tried Lanchons isoRec kernel when flashing and it bootlooped. Xposed failed to flash for me too.
Thanks for getting back to me.
Click to expand...
Click to collapse
I just edited my post, lol. Not sure whether maybe an AOSP kernel like DragonKernel might work, I'll upgrade tomorrow and give it a go...
Hi,
in one pass, rom + open pico gapps + xpose v79 sdk22 flashed ok
Troubadour666 said:
Hi,
in one pass, rom + open pico gapps + xpose v79 sdk22 flashed ok
Click to expand...
Click to collapse
Xpose will not flash for me.
OK, I tried the latest build(12/01) with DragonKernel(30/11), and got to optimizing apps, then bootloop. So, stock kernel seems the only option for now...
noppy22 said:
OK, I tried the latest build(12/01) with DragonKernel(30/11), and got to optimizing apps, then bootloop. So, stock kernel seems the only option for now...
Click to expand...
Click to collapse
You tried "ripping-out" arnab's kernel from his latest DU and put it over this ROM?
:good:
souler456 said:
You tried "ripping-out" arnab's kernel from his latest DU and put it over this ROM?
:good:
Click to expand...
Click to collapse
Well, no. The reports of freezing with his last release stopped me from trying that. BTW the GeneSys kernel(.tar) that was released is the same as the kernel in DU 9.8, but for me the DragonKernel I tried is the last "AOSP" kernel I found to be stable
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
089man said:
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
Click to expand...
Click to collapse
It's basically Cyanogen 12.1 with a couple of extra features like wakelock blocker. My own opinion, I think it is a lot smoother than stock Cyanogen.
To correct my earlier post. I reflashed the Rom and flashed xposed during the flash process and it flashed without any problems.
089man said:
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
Click to expand...
Click to collapse
I added some screenshots in the OP. Hope this gives you an idea of features....
noppy22 said:
I just edited my post, lol. Not sure whether maybe an AOSP kernel like DragonKernel might work, I'll upgrade tomorrow and give it a go...
Click to expand...
Click to collapse
Great ROM! I repartitioned my phone using 1/4G pit and this ROM works very nice. Thanks devs!
Xposed may not be installed in MoKee RELEASE version cuz they said they odexed the ROM.
Sent from my GT-I9100 using XDA Free mobile app