Related
Hello,
I'm trying to install CM 10.1 on my HTC One on T-Mobile. Im using CWM Touch v6.0.3.3. I've tried flashing both the 7/28 and the 7/27 daily builds of CM 10.1 as found on the cyanogenmod website. I selected the T-Mobile version of the software "m7tmo.zip" and tried uploading it, but got the error "status 7". It says "assert device: getprop" and then says a bunch of code about the product names "m7" and "m7tmo". So somehow I think there's a problem with the device and the software matching, even though I'm pretty sure I'm getting it from the official place. Currently I'm using the stock Sense 5 firmware, but I don't have Google Play access because I mistakenly installed the gapps. package (for Android 4.2). Does any one know of CM builds that work right now? And in the short term (and for my own edification), is it possible to download an older version of the gapps package that works with Android 4.1 that I can use?
Thanks for all your help!
Gapps: http://wiki.rootzwiki.com/Google_Apps
Lists Gapps packages by Android build. You should be good to go there.
CM10:
Use TWRP instead of CWM: http://teamw.in/project/twrp2/164
CM10: http://get.cm
Hope this helps.
Sent from my Nexus 10 using Tapatalk HD
Thanks for the link. I'm downloading the older version of GApps now. A little while ago I tried installing the older GApps package straight through ROM Manager but I don't think it worked. I'm still having trouble, except now I can't get into the play store and Drive won't sync, but other google services (gmail, etc) are working. Somehow, trying to install the GApps package via ROM Manager seems to have broken ROM Manager itself - I get an error message when I try to run it... and of course I can't just uninstall because I don't have Google Play access .
As for using TWRM, I tried already, but for some reason I don't see any files come up when I try installing a .zip package. I'm pretty sure I'm in the right spot and yet TWRM only ever shows directories with no files in any of them.
I think it's also worth mentioning that I have S-ON still, and the only methods I've seen to get S-OFF involve downloading apps from the play store which I don't have (ie. some terminal emulator and a different ROM app). I know its possible to do it through a computer but I haven't been able to find good documentation on how to do it.
So I think my troubleshooting flow chart looks something like this:
Fix Play store error > use terminal emulator to turn S-OFF > flash a better recovery file > install ROM of choice (after some more research I think i'll go with SentinelMod, any one use that one?)
Thanks again for the help folks!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5 (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.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A recovery. To install a recovery when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (e.g. here https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img) and flash it with fastboot.
If you have a CM 10.1 or CM 11 installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CWM and flash it.
Once a version is installed (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
THE NEW NIGHTLIES HAVE EMULATED STORAGE ENABLED. YOU LOOSE ALL YOUR DATA. MAKE SURE YOU BACKUP!!!! THE INTERNAL EMMC 1GB PARTITION IS ALSO NOT ACCESSIBLE ANYMORE. COPY THE CONTENT. THE EXTERNAL SDCARD IS NOT USED ANYMORE AS PRIMARY STORAGE. ALL APP DATA ON THE SDCARD WILL BE LOST. I ALSO RECOMMEND TO WIPE.
BACKUP!
RE-PARTITIONING IS NOT MANDATORY. IF YOU WANT TO RECLAIM THE 1GB PARTITION (called media) YOU CAN TRY TO FOLLOW THE RE-PARTITION GUIDE:
https://docs.google.com/document/d/1wSAaAZfQcnvkiHKlbZ7_H1h67m2kx0mq-p3Wjgue3qA/edit?usp=sharing
PLEASE COMMENT ON THE DOCUMENT IF SOMETHING IS NOT CLEAR.
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, chrmhoffmann, and many others that contribute to cyanogenmod and especially this version.
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device. Also many thanks for the L bringup help.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 and L I have copied lots of things from you
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash gapps. It can be found somewhere....
ATTENTION: IT SEEMS THAT DHACKER'S L GAPPS ARE TOO BIG TO FIT INTO THE SYSTEM PARTITION. Try to find a smaller one.
- The SELINUX policies are enforced now.
Known issues:
- system partition is too small for full gapps. use a mini gapp package.
- the touchscreen firmware flasher doesn't work on L. Use CM11 to flash it first.
Recently fixed:
- f2fs
- kernel updated to latest 3.0 stable
- developer settings and setup wizard (if you select backup) crash. that's fixed in nightly from 8-FEB-15.
- device encryption does work now (but who wants to do that? the device is laggy enough already )
- cmupdate / cm recovery: adb reboot recovery and cmupdater and auto install. Hopefully this is fixed now (not in nice way, but...). You need sdcard inserted to make this work (but I guess everybody has that anyway).
Get it from
http://download.cyanogenmod.org/?device=acclaim
Get ENG recovery from here. It allows to adb into recovery even when data is wiped.
File: https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img
md5sum: 6136fc49c5e9a32f115d40d762bb6f2d
Reserved
...
Amazing work Chris, Let the flashing begin.
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
chrmhoffmann said:
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
Click to expand...
Click to collapse
ROM: 78f32eb89778b31a569644b21fc1e8f3
Recovery: d37f29808a682e7806fa7b77dc940453
Installed just fine here, even Netflix works!!
thanks for everyone's hard work.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
billy8362 said:
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/acclaim
Download the latest version, rename it to "recovery.img". Flash it in fastboot.
If you'd rather not go that route, download a flashable of an older version of TWRP, use 7zip to delete the recovery.img in that folder, then move this new TWRP into that folder. Then flash that.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Update:
All ok after i format 10+11 partitions.
chrmhoffmann said:
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Click to expand...
Click to collapse
Too busy to play with my Nook this week. I recall it was having issues with signature verification. I wasn't able to locate a way to disable signature verification.
Pepe.II said:
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Click to expand...
Click to collapse
Same issue here ... used TWRP ... everything seems to work except I don't have an SD card ... which is a deal breaker for this tablet.
UPDATE: Used the wrong GAPPS the first time ... working fine now ... sluggish, but nothing seems to be broken ... and I didn't do a factory reset ... just cache/davlik cache clear then flash
Get ready for Bexus-L
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
sagirfahmid3 said:
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Click to expand...
Click to collapse
jerrygarcia4295 said:
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
Click to expand...
Click to collapse
Google's apps come with Google's playstore, sync services, etc, which add overhead to wi-fi and CPU cycles.
F-droid doesn't have those services. It's pretty much like a Linux package manager--you use it to install and keep track of open source packages.
Besides, I only use my phones and tablets for Kodi and phone calls. I'm not into Google Hangouts or YouTube, etc. I don't take pictures, I don't use the GPS...
IMO, I find Android to be completely useless. I wish there was a completely open source and open hardware Linux running phone. With Linux, you can do whatever you want.
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
jerrygarcia4295 said:
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
Click to expand...
Click to collapse
I haven't installed cm12 on my nook tablet yet, but on other cm12 installs, you have to enable superuser in Settings / Developer options / Root access. Click one of the boxes other than the default "Disabled". If that doesn't work, some folks swear by SuperSU, which you can find in the Play Store
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. 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.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!
Hello!
I want to upgrade my Galaxy S2 to Android 6, but I don't find any gapps packages that fit onto the default system partition. (like the super mini packages on 5.1)
But I don't want to repartition the device, so do you know any gapps packages for MM that I can install onto the default partitions?
Thanks for your help!
EDIT: Will try repartitioning now, sorry for the unnecessary thread!
Wunderharke5000 said:
Hello!
I want to upgrade my Galaxy S2 to Android 6, but I don't find any gapps packages that fit onto the default system partition. (like the super mini packages on 5.1)
But I don't want to repartition the device, so do you know any gapps packages for MM that I can install onto the default partitions?
Thanks for your help!
EDIT: Will try repartitioning now, sorry for the unnecessary thread!
Click to expand...
Click to collapse
Hi there,
while there are some modified gapps packages that may fit on a very small partition size (500MB on our device, but I will not provide the link), it would be best to re-partition to make things easier if you do decide to switch between custom ROMs. Since Android 5.x, gapps package sizes have increased so it has become a necessity to increase the system partition.
Let me know how the re-partitioning went and if you need help, just let me know
gsstudios
Hi,
I tried repartitioning using Odin, but everytime I connected my phone to my computer (drivers installed) it said 'Windows couldn't recognize the device...' with a warning symbole.
So then I tried this: https://github.com/Lanchon/REPIT
But it always failed during flashing with Error 1 (can't remember the specific error message)
Well, I will just stick to 5.1 for now
Heyo, guys. I wanna show u my own ROM based on LineageOS 14.1.
Flash it as u flash another ROMs:
Wipe System, data, caches
Flash ROM
Flash Gapps
Flash SuperSu if u want
For update just do dirty flash.
Hope that u'll like this ROM.
Download link:
AFH
Big thanks to @romilparh who was the first man who helped me with beginning things.
Thanks to @jhalayashraj who taught me some things
Thanks to @amardeep434 who also helped me a lot
Thanks to @danieldmm who also helped me with a lot of things
Also thanks to @TechExhibeo my sensei who can help with ton of problems and advise smth
And thanks @jgcaap for some interesting things on github.
LineageOS
Kernel
Device
Have a good use and thanks
umm.. First?
EDIT: Hey Oleg, nice to see your CM. Will download asap.
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
thank u very much for this awesome rom.
Wow this ROM is awesome! I just saw LineageOS 14.1 for the OnePlus One yesterday. No bugs so far, It seems really stable and a great and probably the best daily driver ROM.
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
i'm not facing any problem with AdAway and viper in 20170109 build.
NeolWhyt said:
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
Click to expand...
Click to collapse
Probably u're doing smth wrong...
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
Doesn't have any problem. All is ok.
Okeys said:
Doesn't have any problem. All is ok.
Click to expand...
Click to collapse
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Sent from my A0001 using Tapatalk
nolsen311 said:
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Click to expand...
Click to collapse
Viper is still included. Just change SELinux mode. I'll change on needed later.
Have a good use
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
f2sf it's supported?
hyper_davide said:
f2sf it's supported?
Click to expand...
Click to collapse
Now not.
ppp99 said:
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
Click to expand...
Click to collapse
All in ext4?
Okeys said:
All in ext4?
Click to expand...
Click to collapse
Just checked, YES.
https://www.androidfilehost.com/?w=files&flid=132556
Thanks so much Okeys! this is the best ROM I could find so far, it works so perfectly!!
Summary of my attempts:
(1)I tried "lineage-14.1-20170130-nightly-bacon-signed.zip" from lineageos
* lower kernel: 3.4.112
* not support system root, need install supersu.
* System APP: "SoundRecorder" and "Screencast" were merged and replaced with "Recorder", I don't like the new "Recorder", the recorder file is much bigger than "SoundRecorder"
(2)I tried "RR-N-v5.8.1-20170131-bacon-Official.zip" from remix
* Same as lineage above
* Support system root option, not need supersu
(3)lineage-14.1-20170126-Okeys-bacon.zip
* new kernel: 3.4.113
* not support system root, need install supersu.
* keep the original "SoundRecorder" and "Screencast"
* The only problem I met is "Left Wipe" doesn't switch to "Google" with Pixel Launcher for Andriod 7.1, but I find a solution and fixed it.
** see my post: https://forum.xda-developers.com/oneplus-one/help/fix-left-wipe-doesnt-switch-to-google-t3549497
Please change to coloros blobs dude
20170202 Bacon Gesture Settings
lineage-14.1-20170202-Okeys-bacon flashed a few minutes ago. Noticed that the Gestures settings no longer allows control over music and camera gestures. They are on by default, and I guess can no longer be turned off.
Hope this helps,
E.