CyanogenMod is a free, community built, after-market firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Downloads
Latest Build REMOVED BY VECTUS(2/8/2014)
Latest GappsHERE(choose the latest version)
Latest CWM HERE(courtesy of jfbs)
Features
-Has Mods to improve Speed
-Has OC up to 1.5ghz(higher coming Soon!!!)
-Has battery life Tweak
-Wifi Tethering
-Beats Audio(...Awesome...)
-Active Display(Pocket Mode)
-Root Browser(jrummy16)
-Google Chrome Browser
-zipaligned
-MORE COMING SOON!!!!!!!!
Baseband
(Courtesy of jfbs)
Flash in CWM recovery. Wipe cache and Dalvik-cache before installing.
T679UVLG3 2012 July
md5sum 61efc2e31fd0885dc0f948f84f94574f
T679UVLK2 2012 November
md5sum 0c0175d46e3fc4c9f11ee3352af85442
Instructions
(Taken from jfbs's thread ,Thanks)
Before you install CM-11.0: Preparation (First three are optional. If you want to start fresh, these can be skipped)[1]
Install AppBak from Play Store, run it and save a list of all your apps.
Install SMS Backup and Restore from Play Store, run it and backup your SMS history.
Install Call Logs Backup and Restore from Play Store, run it and backup your call log history.
Boot into recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
- First time flashing CM11 to your Galaxy Exhibit (or coming from another ROM)?
Reboot into at least ClockworkMod Recovery 6.0.4.4 using 3-button-combo, or TWRP 2.6.3.0
Create a Nandroid Backup!
CWM: WIPE dalvik-cache, format: data, system, and cache. TWRP: WIPE dalvik-cache, data, system, and cache.
Install the ROM
Optionally install KK Google Apps. You must flash gapps after every upgrade to CM11.0 since /system is formatted, wiping your previous add-ons [1]
Reboot
After you setup your Google account, reinstall the three apps from Play Store in order to restore most of your apps, call log and SMS history.
Upgrading from another version?
- Upgrading from CM10.2?
Create a Nandroid Backup!
CWM: WIPE dalvik-cache and format cache. TWRP: WIPE dalvik-cache and cache.
Install the ROM
Optionally install KK Google Apps
Reboot
- Upgrading from CM10/10.1?
Create a Nandroid Backup!
CWM: WIPE dalvik-cache and format cache. TWRP: WIPE dalvik-cache and cache.
Install the ROM
Optionally install KK Google Apps
Reboot
- Upgrading from CM7/CM9?
Create a Nandroid Backup!
CWM: WIPE dalvik-cache, format: data and cache. TWRP: WIPE dalvik-cache, data, and cache.
Install the ROM
Optionally install KK Google Apps
Reboot
After you setup your Google account, reinstall the three apps from Play Store in order to restore most of your apps, call log and SMS history.
- Upgrading from another build of CM11?
Create a Nandroid Backup!
CWM: WIPE dalvik-cache and format cache. TWRP: WIPE dalvik-cache and cache.
Install the ROM
Additional Notes(Read before installing this rom)
-Install the latest cwm before installing this rom
-Formatting sdcard0 after backing up data and before installing rom may help with issues
Changelog
2/8/14
-Initial Build
Issues with this Rom
-You can make videos but to watch them use a 3rd party app
If you find any bugs let me know
Credits
arco68
jocala
pawitp for layout and install directions
AriesVE DevConnection Team
alviteri
LegacyXperia
cars1189
CyanogenMod Team
xda community
jfbs
...Awesome...
Smartguy044
[email protected]
Google
Jrummy16
Kernel Source
HERE(courtesy of jfbs and adc)
Please Test this ROM and post your opinions and any bugs. I will be adding more features soon and will try fixing any bugs.
Reopened.
hmm, didn't even notice it got updated...
can't try this rom yet until maybe next week since i need to use my phone and don't want to mess with it right now
hopefully bumping this will get the attention for some other users
http://forum.cyanogenmod.com/topic/72611-can-i-get-cyanogenmod-on-my-device/
You should submit this Rom for official support, it runs quite smoothly.
Sent from my SGH-T399 using XDA Premium 4 mobile app
From the moderator
Until some issues are worked out this THREAD IS CLOSED
~~~ oka1
So I'm working on wiping my phone and starting from scratch. I'm going to be using:
*Lineage -14.1
*[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
*AddonSU - 14.1 arm-signed
*[KERNEL][Kenzo][LineageOS] FrancoKernel - r6
*[MOD] Disable throttling when battery low
I'm just not sure which order to install everything. I assume the OS gets installed first, followed by Gapps. Then do I install the Kernel, MOD, and SU? Any reboots inbetween, or install them all at the same time while in recovery?
What works for me always is ROM, Gapps, kernel, root.
I asked about this a while ago and was told by a dev that most custom kernels resist the loss of root if you flash root and then the kernel, but it just makes more sense to me to flash the kernel first so that SuperSU or Magisk work on a clean kernel.
dahawthorne said:
What works for me always is ROM, Gapps, kernel, root.
I asked about this a while ago and was told by a dev that most custom kernels resist the loss of root if you flash root and then the kernel, but it just makes more sense to me to flash the kernel first so that SuperSU or Magisk work on a clean kernel.
Click to expand...
Click to collapse
Pretty much nailed it right there! That's what I do as well!
blueblade123 said:
So I'm working on wiping my phone and starting from scratch. I'm going to be using:
*Lineage -14.1
*[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
*AddonSU - 14.1 arm-signed
*[KERNEL][Kenzo][LineageOS] FrancoKernel - r6
*[MOD] Disable throttling when battery low
I'm just not sure which order to install everything. I assume the OS gets installed first, followed by Gapps. Then do I install the Kernel, MOD, and SU? Any reboots inbetween, or install them all at the same time while in recovery?
Click to expand...
Click to collapse
For Clean Flash:
1.) Go to "Wipe" and then Swipe to Factory Reset
2.) After thats done go to "Advanced Wipe"
3.) Tick Dalvik/Art Cache, System, Data and Cache ONLY!! and then "Swipe to Wipe"
4.) Flash Rom and Gapps
5.) Kernel
6.) Then anything else you might install such as Magisk / Super SU, MOD )
All at the same time in Recovery!
Sent from my shamu using XDA Labs
dahawthorne said:
What works for me always is ROM, Gapps, kernel, root.
I asked about this a while ago and was told by a dev that most custom kernels resist the loss of root if you flash root and then the kernel, but it just makes more sense to me to flash the kernel first so that SuperSU or Magisk work on a clean kernel.
Click to expand...
Click to collapse
Do you usually wipe Dalvik/cache before and after flash or just after
minilandl said:
Do you usually wipe Dalvik/cache before and after flash or just after
Click to expand...
Click to collapse
A more technically-experienced member may be able to give you a definitive answer on which is best, if it makes any difference at all, but I normally do it only after flashing the ROM and before installing Magisk. For a total advanced wipe, of course, obviously I do all four partitions beforehand.
blueblade123 said:
*Lineage -14.1
*[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
*AddonSU - 14.1 arm-signed
*[KERNEL][Kenzo][LineageOS] FrancoKernel - r6
*[MOD] Disable throttling when battery low
Click to expand...
Click to collapse
For some starting advice/my recommendations:
Instead of Bean GApps, use OpenGApps; they provide newer GApps that aren't months outdated and work fine
Use Magisk for SU/root unless you have a specific reason for AddonSU
Make sure you grab the latest FrancoKernel (I think r73?)
As for flash order:
Wpe everything
Reboot to Recovery
ROM
GApps
Reboot to Recovery
Kernel
Magisk
Reboot to System
As to what I usually do for a really clean install (likely overkill):
Reboot to Bootloader
Wipe everything (fastboot erase all)
Do flash-base.sh from latest factory image (this reflashes modem partitions; this is required after erase all)
Boot to Recovery
Wipe everything from TWRP
Reboot to Recovery
Wipe everything again from TWRP (old habit from when the first wipe didn't actually get rid of everything on older devices)
fstrim Data, Cache, System, and Firmware partitions
Reboot to Recovery
ROM
GApps (I don't use GApps, but if I did, this is when they are to be flashed)
Reboot to Recovery
Wipe everything except System from TWRP
Format Data and Cache to F2FS
fstrim Data and Cache partitions
Reboot to Recovery
Kernel
Magisk
Reboot to System
Do set-up and copy files over to device
Reboot to Recovery
Wipe Dalvik Cache (I guess the button in TWRP would work; I do rm -Rf /data/dalvik-cache)
Use filesystem tools to check and repair partitions (e2fsck for ext4 being System and Firmware partitions, and fsck.f2fs for F2FS being Data and Cache partitions)
fstrim Data, Cache, System, and Firmware partitions
Reboot to System
No, Beans GApps is a better choice.
It only gives the apps that are truly essential.
It doesn't check to see if you're clean flashing a ROM before placing Google Camera in /system.
It's smaller. With OpenGApps you have to download the Stock package at nearly 800MB and exclude a bunch of apps to approximate the full Beans GApps package.
The apps are updated through the Play Store, thus the fact Beans doesn't update his package daily like OpenGApps isn't relevant.
Strephon Alkhalikoi said:
No, Beans GApps is a better choice.
It only gives the apps that are truly essential.
It doesn't check to see if you're clean flashing a ROM before placing Google Camera in /system.
It's smaller. With OpenGApps you have to download the Stock package at nearly 800MB and exclude a bunch of apps to approximate the full Beans GApps package.
The apps are updated through the Play Store, thus the fact Beans doesn't update his package daily like OpenGApps isn't relevant.
Click to expand...
Click to collapse
1. OpenGApps offers multiple packages. If you want the bare-minimum, I don't believe you can limit the apps any further than Pico. If you want Google Search, then Nano is the next step up. Then you have Micro, Mini, and Full, along with Stock and Super. Paired with a gapps-config.txt file, you can have whatever apps you want installed if none of those packages suit your needs, or just grab the smallest package and grab additional stuff from Play Store.
2. I'm not too familiar with a situation where that would be good, but you can use a gapps-config.txt file to force Google Camera and ignore a non-clean install
3. Pico is a little over 100MB, and there's several other options for pre-included packages up until the stock package. If downloading the larger Open GApps package isn't feasible, then a smaller package with the apps from Play Store would work right? Both Bean Gapps and Open GApps are GApps; you're downloading the same amount of data for apps either way regardless, the difference being whether they're included in the package, or you get them from Play Store.
4. I suppose that's a good point, but if I'm doing a clean install of a ROM and GApps, I wouldn't want to have to update all the GApps packages right after a clean flash.
My experience with Open GApps has been great over the years I've used them. I've tried Bean GApps a few times in the past and it also worked fine up until the June full package that was released broken (which gives the impression Bean Gapps are blind-released; although I guess OpenGApps does this as well).
@espionage724: Beans' full GApps package includes the Google Camera. The smallest OpenGApps package that includes the Google Camera is the stock package. In order to emulate what Beans' provides, you have to use the stock package and you have to create a .gapps-config file. When installed, the OpenGApps script looks at the .gapps-config file and by default excludes any items that are listed in that file, such as the items below.
ExchangeGoogle
GoogleNow
TagGoogle
CloudPrint
Docs
Drive
Fitness
Keep
NewsWidget
Books
Movies
NewsStand
Sheets
Slides
Duo
The preceding list is the apps that must be excluded from the install in order to approximate the Beans' full GApps package. Now how do I know this? When Beans was having issues with his GApps package in June I used OpenGApps stock to update the Google apps, and the list above was the list of items that I ended up removing. Once the issues with his GApps package were resolved, I went back to using his.
The above is a rebuttal to point 1 you made.
2. The OpenGApps installer script will not install the Google Camera even if you specifically include it in the .gapps-config. This is done to avoid force closes and other strangeness. According to the OpenGApps wiki...
Experience has shown us that users who install this application FOR THE FIRST TIME during a 'Clean install' GApps installation almost never have issues or problems with these apps. However, there have been several reports of users experiencing FCs or other strange behavior when they have tried to install these apps later (with GApps), after their device has been set up.
To ensure the best possible user experience, Open GApps will only allow this application to be installed FOR THE FIRST TIME as part of a 'Clean' install (data wiped) installation. Updates to an existing System (Open GApps) installation will also install fine, plus you can still freely update these apps from the Play Store and have the Open GApps installer update them later with the next Open GApps update.
Click to expand...
Click to collapse
-- https://github.com/opengapps/opengapps/wiki/FAQ
3. This has nothing to do with the fact that the minimum size OpenGApps package needed to install all the Google apps found in Beans' full GApps package is the stock package. That said, if we ever do run low on space in /system, the smaller packages (e.g. Micro, the smallest package I recommend using) are certainly an option since most Google apps can be downloaded from the Play Store. The Google Camera however may not be available in the Play Store, depending on the ROM, meaning it would have to be sideloaded.
4. While I'm in agreement about not having to update the packages immediately, at the same time it simply does not matter. The Google apps update frequently enough that trying to keep up with it by repeatedly installing GApps packages is a waste of energy. So I only update when the ROM itself is updated. If that means I have older versions of Google apps in /system, then that's fine by me. The apps will get updated.
Prior to the Nexus 6 I exclusively used OpenGApps and never had an issue. With the Nexus 6 I used the recommended GApps for Pure Nexus, and except for June have had no issues. Obviously, which one you want to use is up to you, but I'll let you know right now that it took about two weeks for OpenGApps to get their Android 8 packages to finish installing without requiring a hard reboot. The impression I get is that what happened with both OpenGApps and Beans full GApps was a one-off aberration.
Hi guys
heres what happened
I flash my device via spf flash tool to stock MM
then flash TWRP_boot_root_s228 then
copy CM13-2016-09-26 build & tron kernel
then I put my device via recovery mode then
flash the cm13 restarted all good then
flashed the tron kernel, all good again
here's the tricky part:
after I install facebook via google play store as soon as it as it is finished installing. there's several apps that stopped working like trebuchet, package installer, calculator and several more and when I check the settings several apps contains 0 bytes, none whatsoever. what am I doing wrong, I have been flashing several times ends up same result.
btw I wipe dalvik cache, system,data,cache,internal storage before flashing.
pls help me guys
There is no need of wiping internal storage
And
The problem you are facing can be solved by changing the rom
Simply download a random Custom Rom and gapps then flash them through your recovery -> this time just wipe dalvik, cache, system and data only.
I faced same problem once and i found solution through this step
I recently got this phone and first thing i tried to do is install new ROM, but everytime i boot into it i get Google Services Framework crash, android.process.media crash, and probably some other ones as well i couldn't see because of overlapping error messages.
I didn't do a "dirty install" - everything except internal storage was wiped, then fresh rom install, gapp install and cache wipe then reboot.
When i don't install gapps, i can boot into system but still android.process.media keeps crashing, and random applications i can open usually crash as well.
Did anyone encounter similiar problem?
I suspect you need to format not just wipe before you flash.
If flashing a custom rom other than miui -
download a new updated package of open gapps with the right android version for rom arm64bit package. I usually go micro.
Flash directly after rom before rebooting. A miui rom has gapps built in obviously so no need to flash
Sounds like you encounter strange issues because data was not wiped.
Try the LOS installation instructions step by step with any ROM you are going to use. Works for me.
Good luck!
Hello, the purpose of this guide is to show how to retain functionality after doing a factory reset on every ROM.
The problem is that the preinstalled gapps may not be working (login not possible), even after enabling and setting autostart in MiAssistant. Therefore some guides (e.g. this newest one) recommend flashing a working ROM, setting up GApps and afterwards flashing a new ROM without any wipe.
But those who simply want to factory reset can be helped with this guide. This also may make the intermediate step of GApps installaion unnecessary.
microG replaces Google Play Services, Framework and LocationProvider, ALL other GApps are working as expected afterwards.
In TWRP backup your current installation (important if any bootloop occurs)
Factory Reset, Reboot, do basic setup (device name, etc) and select language in MoreLocale if needed
Download, Flash and Wipe Cache + Dalvik Afterwards:
Magisk ONLY if you have a unpatched boot.img meaning no previous supersu installation (to obtain root while passing safety net)
-if the installation of Magisk failed please perform another Factory Reset before continuing (otherwise NanoDroid won't install correctly)-
OTHERWISE SuperSU and Xposed Framework (link for Android 6, SDK23)
NanoDroid fdroid (fdroid plus modified play store)
NanoDroid microG (migroG plus removes unneccessary Google stuff)
NanoDroid patcher to allow signature spoofing not working on odexed roms, we solve that with (Magisk-)Xposed-FakeGapps
Reboot, launch fdroid, let it update its repository and install FakeGapps, XposedInstaller (+ if installed, in Magisk XposedFramework)
In Xposed download XposedGmsCoreUnifiedNlp and enable all installed Modules
In Mi Assistant enable all apps to auto start
Restart, then login into Google to see if that works, otherwise check if Xposed modules are enabled and working, restart and try again, if still not working try disabling and reenabling the concerned app (e.g. Play Store)
Furthermore a selftest can be done in microG settings and you can check if Nlp is working in a Maps App of your choice
Unnecessary Apps CAN be frozen (recommended with AirFrozen) or uninstalled (only if 100% sure and backuped)
Q&A:
Contacts Sync is not working / crashing: Try reinstalling the Google Sync Adapters with the flashable zip from here, set the additional permissions in App Settings