CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 Lollipop, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
IMPORTANT INFORMATIONS
- Root is now disabled by default on CM12.1. To enable it go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
- Even if I (Lysergic Acid) don't own an i777, I'm maintaining it officially as everything I do for my i9100 gets to the i777 too, so it's fair enough to open a thread for you guys
We'll not support users and answer questions from users which:
- Are running a custom kernel
- Have flashed mods
- Modified system files
- Didn't follow our instructions
- Are unfriendly
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/I777_Info
Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i777
Changelog: http://www.cmxlog.com/12.1/i777
First time installation instructions:
Download CM-12.1-XXXXXXXX-NIGHTLY-i777.zip to your sdcard
Make sure you're using a Kitkat Compatible Recovery
Boot into Recovery
Wipe all your data
Flash CM-12.1-XXXXXXXX-NIGHTLY-i777.zip from sdcard
(Optional)Flash Google Apps.zip from sdcard
Reboot
CM12.1 official nightly builds:
http://download.cyanogenmod.org/?device=i777
Recommended Google Apps:
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Choose Pico version to fit in the /system partition.
If you like my work, consider making a small donation
XDA:DevDB Information
CyanogenMod 12.1, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
Lysergic Acid, rogersb11
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Kitkat Compatible Recovery
Based On: AOSP
Version Information
Status: Nightly
Created 2015-07-04
Last Updated 2015-07-03
Reserved
Hi,
I'm currently running Cyanogenmod version 11-20140402-Unofficial-i777 on my SGH-i777. I'd like to update to this Nightly build. Can I use the instructions in OP to update to this Nightly? (Just want to clarify because your OP clearly says "First Time Installation Instructions" but the process looks the same as any other update.)
CM and kernel details:
CyanogenMod version 11-20140402-Unofficial-i777
Kernel version 3.0.64-RB11-Shift-1.1
Thanks for your work on bringing CM 12.1 to the Galaxy S II!
Flashed 07032015 but stuck at cm logo.
Sent from my i777 using XDA Free mobile app
Great work but IMO this should have never gone official for the i777. The outgoing call bug is a huge bug.
It would never have passed under Entropy/Cody.
Is there a thread on JIRA for the outgoing call bug? I couldn't find one but would like to contribute by scouring the code (and would like to see what others have done so far).
Build cm-12.1-20150704-NIGHTLY-i777 Install fine on my sgh-i777. Phone bug still there. I used Tasker to toggle the speaker on and off for incoming calls and it seemed to work ok. Build ran cool and stable for the short time I had it install. Surprised with the Cyanogen Recovery limitations, seems like it won't install zip files. Had to use Mobile Odin to flash a kernel to get CWM recovery back to restore backup file.
jankypatella said:
Hi,
I'm currently running Cyanogenmod version 11-20140402-Unofficial-i777 on my SGH-i777. I'd like to update to this Nightly build. Can I use the instructions in OP to update to this Nightly? (Just want to clarify because your OP clearly says "First Time Installation Instructions" but the process looks the same as any other update.)
CM and kernel details:
CyanogenMod version 11-20140402-Unofficial-i777
Kernel version 3.0.64-RB11-Shift-1.1
Thanks for your work on bringing CM 12.1 to the Galaxy S II!
Click to expand...
Click to collapse
Yes, just follow that instructions and you'll be fine.
yosmokinman said:
Great work but IMO this should have never gone official for the i777. The outgoing call bug is a huge bug.
It would never have passed under Entropy/Cody.
Click to expand...
Click to collapse
I thought this bug had been fixed, anyway, I don't have this problem on my i9100, that's probably related to the different mic location of the i777. Sadly without the phone I'm not the best to fix this.
Quicksilver13 said:
Build cm-12.1-20150704-NIGHTLY-i777 Install fine on my sgh-i777. Phone bug still there. I used Tasker to toggle the speaker on and off for incoming calls and it seemed to work ok. Build ran cool and stable for the short time I had it install. Surprised with the Cyanogen Recovery limitations, seems like it won't install zip files. Had to use Mobile Odin to flash a kernel to get CWM recovery back to restore backup file.
Click to expand...
Click to collapse
CM recovery installs signed zips only.
^Yeah it's not fixed and really going to be a ***** I think.
i9100 is fine. i777 with the yamahell chip I still think is the problem. Remember Paul from the replicant project? Helped greatly but maybe not so with 5+
The i777 seems to be how many hacks can you stack on top a hack.. ie. hwc
Edit: That Dead show was gooooooooooooood. LA? My emmc was definitely repartitioned.
yosmokinman said:
^Yeah it's not fixed and really going to be a ***** I think.
i9100 is fine. i777 with the yamahell chip I still think is the problem. Remember Paul from the replicant project? Helped greatly but maybe not so with 5+
The i777 seems to be how many hacks can you stack on top a hack.. ie. hwc
Edit: That Dead show was gooooooooooooood. LA? My emmc was definitely repartitioned.
Click to expand...
Click to collapse
I'll look in the differeces of the i777 and try something, but I don't promise anything.
The OTAs are block-based in Lollipop btw, that's why it looked like a repartition, but it was not
Latest nightlies will resize the system according to your pit.
Lysergic Acid said:
CM recovery installs signed zips only.
Click to expand...
Click to collapse
Thanks for the information. I couldn't find much info on CM Recovery. Is it possible to make backups and restore on CM Recovery?
Quicksilver13 said:
Thanks for the information. I couldn't find much info on CM Recovery. Is it possible to make backups and restore on CM Recovery?
Click to expand...
Click to collapse
Sadly not yet, only through adb. CM recovery is very simple indeed, I think it's made for people that don't even use the recovery
Looking forward to trying this and thanks for the ROM. I wonder if the AJNewkirk mic-swap kernels would have any .ko files that would help the call bug?
Lysergic Acid said:
Latest nightlies will resize the system according to your pit.
Click to expand...
Click to collapse
Glad to see that finally make it in. I wouldn't want to have to redo that partitioning again.
Are the scripts setup not to have to reflash gapps after every upgrade yet? (it was an issue on the i9100 thread last week -- not sure if it got resolved or if with the block update there is no way to solve it).
TeutonJon78 said:
Glad to see that finally make it in. I wouldn't want to have to redo that partitioning again.
Are the scripts setup not to have to reflash gapps after every upgrade yet? (it was an issue on the i9100 thread last week -- not sure if it got resolved or if with the block update there is no way to solve it).
Click to expand...
Click to collapse
The block-based OTAs came in to fix the gapps backup, so yes, it works
The phone runs really well on the latest nightly! Multi tasking is smoother than ever before. Unfortunately I lack the skills, but it would be great if someone (CM? @cyril279, @rogersb11, @Lysergic Acid) could re-pack the stock kernel with a custom recovery.
Edit: unbelievably solid as a rock. Thank you to all the devs over the years that have helped keep this device relevant. This latest nightly from CM is like butter on the SII...I even put the OneplusOne and the Nexus4 on the shelf and threw my sim card back into this phone for the last couple days. Loving it.
The slim kernel is essentially the cm kernel, with TWRP 2.8.7.0
So the quickest solution would be to flash:
CM
SLIM kernel
Google apps
Regarding the call-bug @Lysergic Acid, I'd ship you an i777 if you were in the states, but I fear that international shipping makes it cheaper to buy you one than ship one... Are there any particular logs that could help to identify the issue?
-Cyril
erad1 said:
[...] but it would be great if someone (CM? @cyril279, @rogersb11, @Lysergic Acid) could re-pack the stock kernel with a custom recovery.[...]
Click to expand...
Click to collapse
---------- Post added at 09:28 PM ---------- Previous post was at 09:21 PM ----------
dimoochka said:
Is there a thread on JIRA for the outgoing call bug? I couldn't find one but would like to contribute by scouring the code (and would like to see what others have done so far).
Click to expand...
Click to collapse
I don't think that a JIRA issue has been filed on this, but it deserves one, along with logs. Jira is designed to centralize and track the progress and effort of specific issues.
-Cyril
^I really doubt they'll ever touch it.
I still think it's the yamahell **** all over again.
OT thanks for Omni that's my dd and runs as nice as you could expect on this phone. Plus twrp. cm recovery is trash and a dealbreaker till they fix it up a bit.
cyril279 said:
The slim kernel is essentially the cm kernel, with TWRP 2.8.7.0
So the quickest solution would be to flash:
CM
SLIM kernel
Google apps
-Cyril
Click to expand...
Click to collapse
Thanks for the tip Cyril .. Do you have a link for the Slim Kernel?
kingfiras said:
Thanks for the tip Cyril .. Do you have a link for the Slim Kernel?
Click to expand...
Click to collapse
BEWARE:
- Cyril's cm-kernel does NOT currently include the FPbug-fix recently added to CM kernel source.
The kernel that I'm linking to only includes CM commits up through may 2015. I just noticed that CM more recently included the FPbug fix into their source (thanks LA), and my CM kernel does NOT include that (I wasn't paying attention when I switched to the CM kernel source from OMNI). : embarrased :
I'll update and build another within the week.
:: kernel-i777_5.1_TWRP-signed.zip ::
- Kernel source -
Related
WARNING: cm-11.0 nightlies have stopped for this device. While these builds will likely stick around and be usable, they will no longer be updated. See here for cm-12.0 nightlies: http://forum.xda-developers.com/dro...rom-cyanogenmod-12-0-nightlies-droid-t2998065
(Yes, you can dirty flash this over a cm-11.0 build)
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we 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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Other Issues?
Before posting on this thread, make sure of a few things:
Metadata error when flashing? Make sure you have the LATEST ClockworkMod installed. Other recoveries *may* work, but will not be supported here. The reason for this is SELinux. It needs to set metadata on the files and old recoveries (with kernels that do not support SELinux) cannot do this. Make sure your ClockworkMod is at least version 6.0.4.5 or it will fail.
[*]You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
[*]If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
[*]Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
[*]LOGS LOGS LOGS!!!! Use this: https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsImNvbS50b3J0ZWwuc3lzbG9nIl0
Experience issues? As these are nightlies, bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=dlx&type=nightly
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
Useful Links
Unofficial changelog
dlx CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR NIGHTLY BUILDS!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Special thanks to the CM10DNA team too, they've done great work on this device, and I look forward to working with them on official repos!
- Chad0989
- crpalmer
- Flyhalf205
Also to intervigil and all the m7 guys, we share a lot of work with them!
XDA:DevDB Information
CyanogenMod 11.0 Nightlies for the Verizon HTC Droid DNA, ROM for the HTC Droid DNA
Contributors
invisiblek
ROM Firmware Required: CWM 6.0.4.5 or Later
Version Information
Status: Testing
Created 2013-12-07
Last Updated 2014-06-23
mine!
Does this boot? Stable?
Sent from my HTC6435LVW using Tapatalk
Gorilla* said:
Does this boot? Stable?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I would imagine.. I'm going to give it a go while I wait on a rooted version of the new OTA from the guys..... Love me some CM!
All i want for xmas is a kernel from palmer for this rom.
It looks like the same nightly that is 10mb smaller than the previous nightlies and does not boot.
Make a backup first if you're going to try this nightly.
Nicely done. Didn't even realize this was CM11 when I updated.
Gorilla* said:
All i want for xmas is a kernel from palmer for this rom.
Click to expand...
Click to collapse
He's been working on it. He is very careful and does not want to release something that is buggy.
I could've sworn I saw a post asking for 4.4 gapps. Here is the link to the PA gapps that Pio confirmed works on Carbon 4.4
http://forum.xda-developers.com/showthread.php?t=2397942
hrm, it seems the blobs didnt get brought in with it last night....weird
flash this after the rom and you'll be fixed up:
http://invisiblek.org/dlx/blob_fix.zip
investigating...
For whatever reason it doesn't want to flash through recovery, errors me out.
hullbay said:
For whatever reason it doesn't want to flash through recovery, errors me out.
Click to expand...
Click to collapse
update your recovery, latest clockworkmod is recommended
invisiblek said:
update your recovery, latest clockworkmod is recommended
Click to expand...
Click to collapse
I'll give it a shot now, I'm using TWR
Nope.
Using CWMR 6.0.3.1
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
hullbay said:
Nope.
Using CWMR 6.0.3.1
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Just can't win can I? Heh
I'll get a new, official one built. In the meantime, you can use this one that I just built:
http://invisiblek.org/dlx/recovery/recovery-clockworkmod-6.0.4.5-dlx-UNOFFICIAL.img
invisiblek said:
Just can't win can I? Heh
I'll get a new, official one built. In the meantime, you can use this one that I just built:
http://invisiblek.org/dlx/recovery/recovery-clockworkmod-6.0.4.5-dlx-UNOFFICIAL.img
Click to expand...
Click to collapse
What's the difference / reason it's currently failing?
hullbay said:
What's the difference / reason it's currently failing?
Click to expand...
Click to collapse
The old recovery used a kernel that does not support setting SELinux metadata on your files.
The new recovery has a kernel that will.
Today's build seems to be fine for anyone who was wondering. Flashed with twrp beta from the unofficial cm11 thread.
Sent from my HTC6435LVW using Tapatalk 2
@invisiblek
Kindly link to the cwm image which you build in OP or mention that it will work with cwm recovery 6.0.4.4 or later.
Otherwise, users will keep on clogging the thread with rom not flashing etc etc.
It worked sucessfully for unofficial thread cm11 created by me
Tapatalked from TF300T - Omnirom
Where can i find the changelog for 12/7 nightly?
Can this/has anybody tried flashing this using cmupdater?
WARNING: cm-11.0 nightlies have stopped for this device/variant. While these builds will likely stick around and be usable, they will no longer be updated. See here for cm-12.0 nightlies: http://forum.xda-developers.com/ver...m-cyanogenmod-12-0-nightlies-verizon-t2998037
(Yes, you can dirty flash this over a cm-11.0 build)
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we 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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=vs985&type=nightly
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 Nightlies for the Verizon LG G3, ROM for the Verizon LG G3
Contributors
invisiblek, invisiblek
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-11-28
Last Updated 2014-11-28
Sweet! Too bad it's not CM12 quite yet but now we have an official build.
I'm not ready to jump on CM12 yet until some more things are worked out but CM11 official is running great. So nice to be on CM again rather than stock! Thanks for your time & efforts invisiblek.
FYI: The CM updater doesn't play nice with Philz recovery, CWM is fine as expected, have not tried TWRP.
@invisiblek thanks for this, been running it since first posted (unofficial).
quick question, im working on a bug list for all roms for reference, is this just a continuance of the unofficial version? just trying to keep the list accurate.
thanks
bweN diorD said:
@invisiblek thanks for this, been running it since first posted (unofficial).
quick question, im working on a bug list for all roms for reference, is this just a continuance of the unofficial version? just trying to keep the list accurate.
thanks
Click to expand...
Click to collapse
Yes, I've been building my cm-11.0 builds off CM repos since they've been forked.
invisiblek said:
Yes, I've been building my cm-11.0 builds off CM repos since they've been forked.
Click to expand...
Click to collapse
thanks, i have been following, just wanted to verify.
and dam lol were you reading my mind? that was a fast reply
Great to see official nightlies for the Verizon G3!! Can anyone confirm if the blank screen bug still occurs after making a call? That and Bluetooth calling were the only bugs I really had...everything else works fantastic
Life is good...
Big thanks @invisiblek [emoji106]
Do you want logs posted here (when obtained), or directly to you via pm?
annoyingduck said:
Life is good...
Big thanks @invisiblek [emoji106]
Do you want logs posted here (when obtained), or directly to you via pm?
Click to expand...
Click to collapse
Nothing makes me happier than people posting logs along with their bug report in the same post. Then I don't have to sit and guess "wtf was this log for again?"
gparmar76 said:
Great to see official nightlies for the Verizon G3!! Can anyone confirm if the blank screen bug still occurs after making a call? That and Bluetooth calling were the only bugs I really had...everything else works fantastic
Click to expand...
Click to collapse
I've tried to reproduce the screen on bug, but its rather difficult to do it seems. Any time I try to examine it, it doesn't happen. A log of it happening world be amazing.
In call bt audio is fixed. That was the main thing I was holding off officials for.
It doesn't happen all the time for me either...but it does happen...weird issue..I haven't played with the new nightly yet but will very soon...I just played around with the unofficial CM12 build too and it seems to happen on that too...its like the phone doesn't realize you've pulled the phone away from your head after ending a call.
invisiblek said:
Nothing makes me happier than people posting logs along with their bug report in the same post. Then I don't have to sit and guess "wtf was this log for again?"
I've tried to reproduce the screen on bug, but its rather difficult to do it seems. Any time I try to examine it, it doesn't happen. A log of it happening world be amazing.
In call bt audio is fixed. That was the main thing I was holding off officials for.
Click to expand...
Click to collapse
First off, thanks for doing this. Can't wait to rock this. I know how to do logs, but wanted to ask about the qi charging bug. Is that something a logcat wouldn't be able to show? Or you guys know about it but at bottom of list of things to do?
invisiblek said:
Google apps addon:
Download: http://itvends.com/gapps/gapps-kk-20140606-signed.zip
Click to expand...
Click to collapse
I was wondering if there was a reason you chose to link to this particular gapps that's almost six months old, instead of the PAgapps that's updated every few days at least.
Running great!!!
Sent from my LG-VS985 using XDA Free mobile app
---------- Post added at 08:35 PM ---------- Previous post was at 08:04 PM ----------
So far after a few calls I haven't experienced the sensor issue. It happened after every call on liquid smooth. I'll give BT a try in the morning when I leave for work. Just enabled ART and so far so good. New DD for sure.
Sent from my Super Famicom
So far this is running pretty amazing! Thought I had the screen on after call bug, but I could be wrong and mistaking that for yesterday haha as I just placed a call and it seems to be working fine now. The only other issue I had (and this isn't a deal breaker, but I've seen it on here and on cm12, as well as another aosp rom I want to say so I know it's a definite issue), is that occasionally the expandable volumes panel loses its "expand" button on the right hand side, and so the only volume adjustable is the default top one. Changing the panel setting to something else and back to expandable again seemed to fix it for me, otherwise a reboot does as well, but just figured I'd note this in case no one else has. Thanks again for this! I finally got my brother to start rocking this on his phone, which is no easy task and for a nightly build today's seems real solid. Thank you so much for all your hard work @invisiblek!!!
I have to agree with ^^^ for a nightly this is a solid build. I tested BT today. First try it didn't work but on the second try all was good. Haven't had issues with the sensor during calls yet either. I was also having issues with Pandora on liquids ROM but it works fine here. That you!! I look forward to a stable CM12!!!
So if I flash this I can't go back to stock??
---------- Post added at 10:29 AM ---------- Previous post was at 10:19 AM ----------
Also what should be used CWM or TWRP
leeharvey42 said:
So if I flash this I can't go back to stock??
---------- Post added at 10:29 AM ---------- Previous post was at 10:19 AM ----------
Also what should be used CWM or TWRP
Click to expand...
Click to collapse
Please make sure you read every step in the OP and then read every step again before you flash anything. I'm not saying this to be rude, I just want you to be informed as it seems you may be a newer flasher.
1. Yes you can always go back to stock whether with a KDZ/TOT or with a nandroid backup.
2. You can flash this in any custom recovery. If I'm not mistaken we do not have CWM, we have TWRP and Philz.
Let us know if you have any other questions! =)
PS, flashing this does technicially void your warranty.
EDIT - it would appear I am, in fact, mistaken. @invisiblek has a CWM build located in the recovery folder for our device. =)
RPelham said:
Please make sure you read every step in the OP and then read every step again before you flash anything. I'm not saying this to be rude, I just want you to be informed as it seems you may be a newer flasher.
1. Yes you can always go back to stock whether with a KDZ/TOT or with a nandroid backup.
2. You can flash this in any custom recovery. If I'm not mistaken we do not have CWM, we have TWRP and Philz (cwm based).
Let us know if you have any other questions! =)
PS, flashing this does technicially void your warranty.
Click to expand...
Click to collapse
One more question I have not updated ny phone yet should i do it before i flash this or no?
leeharvey42 said:
One more question I have not updated ny phone yet should i do it before i flash this or no?
Click to expand...
Click to collapse
I wouldn't. Flashing a ROM is equivalent to installing a new operating system on your computer. Updating has no impact on the new ROM and you start with a clean slate.
Make sure you back up any data you want to keep and then do a clean wipe (wipe everything except external SD).
How do I put the store back on my phone
---------- Post added at 11:54 AM ---------- Previous post was at 11:46 AM ----------
leeharvey42 said:
How do I put the store back on my phone
Click to expand...
Click to collapse
Got it sorry for my noobness been on iphone for too long
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
THIS IS UNOFFICIAL EXPERIMENTAL BUILDS WHICH CONTAINS CODE TO BE TESTED BEFORE IT IS MERGED INTO CM.
IF YOU WANT OFFICIAL BUILDS THEN CHECK BACK IN A FEW DAYS.
Official will come when the last annoying incall audio bug is squashed
Code:
#include
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.
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Important information:
This thread is for CyanogenMod 12 opensource builds for the LG G3 (D852). The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Instructions:
Your device will need to be rooted and have custom recovery before proceeding. Please check your device forum for instructions.
First time flashing CyanogenMod 12 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps add-on package.
Already on CM12, try a dirty flash.
Reboot into recovery
Make back up <optional>
Wipe cache, system, dalvik-cache
Optional: Install the Google Apps add-on package.
Reboot
Download: CM12 EXPERIMENTAL BUILDS - Check EXPERIMENTAL folder for your device
AndroidFileHost - HERE
BasketBuild - HERE
Goo.im - HERE
Google Apps: Optional add on package that allows Google Play services such as Google Play Store and other Google Apps outside of AOSP based ROMs.
Check THIS post
Changelog:
CyanogenMod Change Log HERE
G3 Specific Change Log HERE
D850 Specific Change Log HERE
AndroidUser00110001 Change Log HERE
invsisblek Change Log HERE
GitHub - Source Code:
GitHub - CyanogenMod
GitHub - AndroidUser00110001
GitHub - invsisblek
Credits:
Thanks to all sent Paypal!!!
CyanogenMod
Thanks to @invisiblek for the work he has done on device trees.
Change Log & Other info
Changelog:
2015-01-12 - In addition to the changes below. This build is currently being built and uploaded.
g3: Get rid of ctrl_interface=/data/misc/wifi/sockets http://review.cyanogenmod.org/#/c/84746/
camera: add 3840x2160 video size http://review.cyanogenmod.org/#/c/84832/
camera: set lge-camera parameter - http://review.cyanogenmod.org/#/c/84833/
2015-01-11 - This build is currently being uploaded.
In addition to the changes from 2015-01-08
Set System prop to allow proper Imsi handling - http://review.cyanogenmod.org/#/c/84293/
selinux: Fix access to the vibrator amplification sysfs - http://review.cyanogenmod.org/#/c/84770/
Camera2: Samsung 4k Camera workaround - http://review.cyanogenmod.org/#/c/83332/
Some changes may have been merged but not in latest nightly.
2015-01-08 - This build is currently being built and will be on servers in about an hour from now.
In addition to the changelog in post #1 the following code has been merged into today's EXPERIMENTAL TEST BUILD
Adjust volume for voice-speaker
Default AT&T G3 APN
d850 cleanup
sepolicy: give radio access to tap2wake node
ProximitySensorManager: disable TapToWake while we have a prox wakelock
Bugs:
Only report bugs for UNOFFICIAL EXPERIMENTAL BUILDS pertaining to new code that is listed above in the changelog. Please report if anything is broken or if fixes actually fix something. THANKS!
For proper technique on reporting bugs:
Read THIS and THIS.
When reporting a bug be as specific as possible.
Make sure you can replicate the bug when coming from a clean install with no other apps installed besides what comes with ROM and GApps.
If you narrowed down a specific app that crashes only on CM ROM then please include app version and all info about app too.
Do not have any modifications done to the Android system besides.
It is very important to read on the proper technique to report a bug. Helps keep thread clean and makes tracking issues easier.
OFFICIAL FOR D855 please
Awesome, glad to see another D852 build! Thanks. Testing it out now!
D855 plz...
gdonanthony said:
OFFICIAL FOR D855 please
Click to expand...
Click to collapse
Kookitza said:
D855 plz...
Click to expand...
Click to collapse
Isn't there CM12 for D855?
sean222 said:
Awesome, glad to see another D852 build! Thanks. Testing it out now!
Click to expand...
Click to collapse
Let me know if it boots or not and what issues it may have please.
What's the difference between this and the other Cyanogenmod 12 for the G3 ?
AndroidUser00110001 said:
Isn't there CM12 for D855?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
Professor Jones said:
What's the difference between this and the other Cyanogenmod 12 for the G3 ?
Click to expand...
Click to collapse
Is there CM12 for the D852?
Kookitza said:
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
Click to expand...
Click to collapse
Me too If there is none than maybe I will build.
AndroidUser00110001 said:
Is there CM12 for the D852?
Click to expand...
Click to collapse
Sorry, I thought this one was for the 855. Nightly means that it gets an update every night ?
AndroidUser00110001 said:
Me too If there is none than maybe I will build.
Click to expand...
Click to collapse
There is one: http://forum.xda-developers.com/lg-g3/development/rom-cyanogenmod-12-t2945191
But it's not nightly...
Plz build for us also.. :fingers-crossed:
AndroidUser00110001 said:
Isn't there CM12 for D855?
Click to expand...
Click to collapse
we need OFFICIAL but its okay i can wait
So is this working? Anyone flash it yet?
AndroidUser00110001 said:
So is this working? Anyone flash it yet?
Click to expand...
Click to collapse
I just finished flashing it on my d852g , so far it's looking good. Wifi ok, LTE ok, bluetooth ok. I flashed gapps micro beta from the 1st post here, I'll report back later!! I gotta tell you, flashing ROM's on this device is soooo much faster that my Asus TF300T tablet
zurny said:
I just finished flashing it on my d852g , so far it's looking good. Wifi ok, LTE ok, bluetooth ok. I flash gapps micro beta from the 1st post here, I'll report back later!! I gotta tell you, flashing ROM's on this device is soooo much faster that my Asus TF300T tablet
Click to expand...
Click to collapse
Thanks! @Cuzz1369 also tested for me and all seems OK for now.
gdonanthony said:
we need OFFICIAL but its okay i can wait
Click to expand...
Click to collapse
https://goo.im/devs/androiduser00110001/ROM/D855/CM12/
Let me know in private if it boots and if anything different is broke when compared to other ROMs you have flashed.
AndroidUser00110001 said:
https://goo.im/devs/androiduser00110001/ROM/D855/CM12/
Let me know in private if it boots and if anything different is broke when compared to other ROMs you have flashed.
Click to expand...
Click to collapse
Flashing NOW!! :victory:
AndroidUser00110001 said:
https://goo.im/devs/androiduser00110001/ROM/D855/CM12/
Let me know in private if it boots and if anything different is broke when compared to other ROMs you have flashed.
Click to expand...
Click to collapse
perfect. found no bug till now
For D855 users that have asked
http://forum.xda-developers.com/lg-g3/development/rom-cyanogenmod-12-unofficial-nightly-t2973522
Now lets get back on topic in this thread
Code:
/*
* 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.
*/
What is AOSP?
AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps.
Anyway to get a working system I added some changes from CodeAurora Forum and CyanogenMod. I added also 3 non-AOSP features for a better user experience (Advanced Reboot, "Clear All" button in Recents and an option to delete screenshots from the notification area) and I'm NOT going to add something other.
Features
Pure AOSP
It's pure AOSP (based on Slim and CAF)
Downloads
Latest Build
GAPPS (Please use the Micro GAPPS Package that's the one working properly)
Link To Download Folder
How To Install
1. Place ROM & Gapps in your SD Card
2. Reboot in Recovery Mode
3. Wipe Data/Factory Reset
4. Wipe Dalvik cache
5. Install the ROM zip
6. Install the GAPPS zip
7. Reboot
8. Profit
P.S: Huge shout out to Team M8 for making this possible, without them i am nothing.
XDA:DevDB Information
AOSPB For Verizon G3, ROM for the Verizon LG G3
Contributors
amirfida, PunkUnity
Source Code: https://github.com/AOSPB
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP + CAF + Some stuff from Slim
Version Information
Status: Testing
Created 2016-03-09
Last Updated 2016-03-11
News: AOSPB haven't updated their code from past couple of days so i won't compile until they update their source. Cheers
This is mine thanks download now
Because this is AOSP will android pay work?
Okay, here's whats not quite working right now
CaptainElwood said:
Because this is AOSP will android pay work?
Click to expand...
Click to collapse
NFC is stuck and causes a wakelock, remove NFC's APK from /system/app, so no, Android Pay does not work
And Baseband is not detected, this is a common issue with newer ROMs on the VS985, ill hunt down CM's commits for this
Probably a gapps issue, but Google Play Services refuses to work for signing in at the first boot, looking for my old gapps now, ill edit this if it was indeed because of the March 10th Gapps
Otherwise, it runs smooth as butter, keep up the good work!
KShion619 said:
Okay, here's whats not quite working right now
NFC is stuck and causes a wakelock, remove NFC's APK from /system/app, so no, Android Pay does not work
And Baseband is not detected, this is a common issue with newer ROMs on the VS985, ill hunt down CM's commits for this
Probably a gapps issue, but Google Play Services refuses to work for signing in at the first boot, looking for my old gapps now, ill edit this if it was indeed because of the March 10th Gapps
Otherwise, it runs smooth as butter, keep up the good work!
Click to expand...
Click to collapse
if you do find that commit please let me know, ill soon upload a new build
amirfida said:
if you do find that commit please let me know, ill soon upload a new build
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/rootdir/etc/init.baseband.sh
I haven't seen your version of g3-common or anything but on most ROMs this winds up being what you need to do
As far as Gapps, it only happens when you install OpenGapps Stock builds, pico runs perfectly
as far as NFC, ill try replacing the apk for it and libs from CM or XenonHD and get those posted if they work
KShion619 said:
https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/rootdir/etc/init.baseband.sh
I haven't seen your version of g3-common or anything but on most ROMs this winds up being what you need to do
As far as Gapps, it only happens when you install OpenGapps Stock builds, pico runs perfectly
as far as NFC, ill try replacing the apk for it and libs from CM or XenonHD and get those posted if they work
Click to expand...
Click to collapse
hey thanks for that i really appreciate it, will mention you in credits for sure
waiting for the workaround, i never really use NFC so never knew that its not working, really appreciate your hard work
Edit: My build uses CM device trees so the file is already the same one, i am testing new build will release it soon
Edit 2: New build has been uploaded compiled with Uber Toolchain
Just curious will Layers themes work on this?
AngryManMLS said:
Just curious will Layers themes work on this?
Click to expand...
Click to collapse
nope it won't... Sorry
amirfida said:
nope it won't... Sorry
Click to expand...
Click to collapse
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
AngryManMLS said:
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
Click to expand...
Click to collapse
You are welcome
Found some odd little issue on the Newest Build, unsure if this one applies to the previous, but the Ringer, regardless of what ringtone is set, does not ring, and Autobrightness does not work, so turning it off is the only way to set brightness, and because you're using CM device trees and kernels, you technically have the proper libs, unless those files are on CM's venders for LG :silly:
KShion619 said:
Found some odd little issue on the Newest Build, unsure if this one applies to the previous, but the Ringer, regardless of what ringtone is set, does not ring, and Autobrightness does not work, so turning it off is the only way to set brightness, and because you're using CM device trees and kernels, you technically have the proper libs, unless those files are on CM's venders for LG :silly:
Click to expand...
Click to collapse
Hey, thanks for pointing out those issues, yes i am using CM kernel and device trees i guess that's the reason brightness is not working properly because even CM had that issue many users reported that, i guess its fixed. Ill build again and see if these issues are fixed and if they are ill post the build. AOSPB guys haven't updated their source from past 17 Days that's the reason i didn't make a new build. Thanks once again
amirfida said:
Hey, thanks for pointing out those issues, yes i am using CM kernel and device trees i guess that's the reason brightness is not working properly because even CM had that issue many users reported that, i guess its fixed. Ill build again and see if these issues are fixed and if they are ill post the build. AOSPB guys haven't updated their source from past 17 Days that's the reason i didn't make a new build. Thanks once again
Click to expand...
Click to collapse
yeah, im mainly referring to the CM vendor trees, im not quite sure if that matters
AngryManMLS said:
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
Click to expand...
Click to collapse
In 6.0 rro was merged. Any aosp or slim rom on 6.0 will work with layers as long as it doesnt have cmte.
As always, you are responsible for your device. Use common sense and make backups
I am just a compiler not a developer but i try to find fixes when I can. That doesnt mean everything will get fixed.
In case anybody wants a pure cm13.0 for the kltesprsports, here it is. Was built from cm13.0 sources, 6.0.1
***Thanks***
CyanogenMod Team
@miked63017 be sure to hit this guys thanks button
Any and all testers of my work!
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT use this unofficial build and ask for support at the official threads.
* Do NOT be rude.
* Respect all users
Installation
flash(odin) unoffical twrp from here = https://androidfilehost.com/user/?w=settings-dev-files&flid=52449
wipe everything except sd card
install cm13.0 from here = https://www.androidfilehost.com/?w=files&flid=52450 new builds will be here when updated!!!!!!!
install gapps from here = http://opengapps.org/?api=6.0&variant=nano reccomend the aroma
XDA:DevDB Information
[6.0.1 marshmallow][UNOFFICAL] CyanogenMod 13.0 for SM-G860P, ROM for the Sprint Samsung Galaxy S 5 sport
Contributors
1991mustang50, miked63017
Source Code: https://github.com/1991mustang50/android_device_samsung_kltesprsports
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: working with issues
Know issues:
Nfc not working
Camera must turn on HDR in camera settings
And you tell me up in bug reports
Created 2016-03-21
Last Updated 2016-03-20
Reserved
Reserved
Works! Thanks for the hard work!
Sent from my SM-G860P using Tapatalk
1991mustang50 said:
As always, you are responsible for your device. Use common sense and make backups
In case anybody wants a pure cm13.0 for the kltesprsports, here it is. Was built from cm13.0 sources, 6.0.1
***Thanks***
CyanogenMod Team @miked63017 be sure to hit this guys thanks button
Any and all testers of my work!
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT use this unofficial build and ask for support at the official threads.
* Do NOT be rude.
* Respect all users
Installation
flash(odin) unoffical twrp from here = https://androidfilehost.com/user/?w=settings-dev-files&flid=52449
wipe everything except sd card
install cm13.0 from here = https://www.androidfilehost.com/?w=files&flid=52450
install gapps from here = http://opengapps.org/?api=6.0&variant=nano reccomend the aroma
XDA:DevDB Information
[6.0.1 marshmallow][UNOFFICAL] CyanogenMod 13.0 for SM-G860P, ROM for the Sprint Samsung Galaxy S 5
Contributors
1991mustang50, miked63017
Source Code: https://github.com/1991mustang50/android_device_samsung_kltesprsports
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-03-21
Last Updated 2016-03-20
Click to expand...
Click to collapse
Thank you so much for the hard work and answering my previous questions. I'll definitely be flashing this and reporting back tomorrow. Question: if I'm on the latest cm12 build currently, can i just flash the new TWRP through Odin over the CWM recovery for the Sport? Or is it required to flash back to the stock firmware?
g4_e said:
Thank you so much for the hard work and answering my previous questions. I'll definitely be flashing this and reporting back tomorrow. Question: if I'm on the latest cm12 build currently, can i just flash the new TWRP through Odin over the CWM recovery for the Sport? Or is it required to flash back to the stock firmware?
Click to expand...
Click to collapse
Just flash twrp through odin
1991mustang50 said:
Just flash twrp through odin
Click to expand...
Click to collapse
OK. Thank you very much for the quick replies. I'll flash tomorrow when I get back from school. :thumbup:
Been working great all day. Haven't hit any bugs and doze is really helping battery life! Thanks again @1991mustang50 for this and TWRP. Will say that TWRP is slow to take a stock backup (not as slow as the CWM we had prior), but it may be because TouchWiz is so heavy. Either way, thanks again. I know the guys that still use this phone daily really appreciate it and so do us that just use it as a toy now!
Good job @1991mustang50, it's a shame I had already given up on the phone and sold it
victor1g said:
Good job @1991mustang50, it's a shame I had already given up on the phone and sold it
Click to expand...
Click to collapse
How much did you get for it, if you don't mind me asking?
New build up same link in op just pulled cm changes!
1991mustang50 said:
New build up same link in op just pulled cm changes!
Click to expand...
Click to collapse
Any chance on making a build for the regular boost mobile one? The one on Mike's is giving me too many issues when it comes to bootloops
atcq28 said:
Any chance on making a build for the regular boost mobile one? The one on Mike's is giving me too many issues when it comes to bootloops
Click to expand...
Click to collapse
I started a build before i left for work if no problems i have new build up for kltespr!
Chief_Nodnarb said:
How much did you get for it, if you don't mind me asking?
Click to expand...
Click to collapse
I sold it for $100 to a cousin. It was in a rough condition around the edges and had call quality issues
Having issues getting data or cell service - I can see sprint under network operators, but haven't been able to get the phone connected. Is anyone else having the same issue and/or found a workaround?
I've flashed TWRP and the ROM and I have to say that so far there have been very few issues. TWRP makes backups very quickly compared to the previous CWM. The ROM has calls, data, SMS, and MMS working perfectly. One minor issue is that if you go into settings and click on carrier settings it will not recognize the SIM card and it will continuously crash the phone application until you reboot. It's a minor issue with an easy fix so dont worry too much about it. I tested Bluetooth which isn't in very good shape. Listening to music from my phone on a wireless headset was constantly cutting out. However I understand it's a beta build and Bluetooth shouldn't be a very big problem for me as I can just use the headphone jack. This next problem I don't think is specifically tied to the ROM however I would like if anyone can give me any ideas for. Basically write access on the external SD is not working as usual but all of the previous fixes you could use aren't working anymore. Any ideas or fix for marshmallow? Overall, the ROM is in great condition for such a new release. Doze works beautifully and battery life is even better than the previous CM12.1 build. I'll be using the ROM more to see if I can tell you about any other issues I may encounter. Thanks so much for the great ROM and TWRP. I'll be looking forward to future builds.
bigfatdude said:
Having issues getting data or cell service - I can see sprint under network operators, but haven't been able to get the phone connected. Is anyone else having the same issue and/or found a workaround?
Click to expand...
Click to collapse
I am not sure why you have this problem others seem ok. If you go back to cm12.1 do u get it back?
atcq28 said:
Any chance on making a build for the regular boost mobile one? The one on Mike's is giving me too many issues when it comes to bootloops
Click to expand...
Click to collapse
Havent forgot i did set up repo for kltespr to build twrp like i am doing forkltesprsports
1991mustang50 said:
Havent forgot i did set up repo for kltespr to build twrp like i am doing forkltesprsports
Click to expand...
Click to collapse
Sweet! Can't wait to try it out
1991mustang50 said:
Havent forgot i did set up repo for kltespr to build twrp like i am doing forkltesprsports
Click to expand...
Click to collapse
That was post to say i didnt setup the repo for kltespr to build twrp which my build enviroment is set up to. So running new build for kltespr now. Should be posted in the morning