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!
Related
CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version: http://download.cyanogenmod.com/?device=galaxys2 (for when nightlies are working normally)
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Only for the International version of the Galaxy S2, US versions like the AT&T have their own device specific builds.
Note: sometimes you need to flash twice back to back without a reboot in the middle. The install should take a little time, if it happens very quickly, flash again.
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ROM Manager or ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some modes don't work
- TVout, MHL
- FMRadio
- Issues when using the 2G/3G-Switch
- Volume issues (some report too high, others too low)
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2 - this shows all the
changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: My Notification bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Nice Q&A here. This is a MUST READ before flashing CM7
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager.
Click to expand...
Click to collapse
I have premium rom manager but dont see any cm7 roms in the download section
???
darkevangerion said:
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Click to expand...
Click to collapse
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Thanks for your fast answer.
And thanks for the rom, obviously
EDIT : Hmmm... "Tonight" = "Tomorrow" for European. :/
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Click to expand...
Click to collapse
Thanks.
Why can't i register my device for notification on updates from nightly?
I got rom manager premium
Sent from my GT-I9100 using XDA Premium App
Answered 3 posts above.
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
carda21 said:
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
Click to expand...
Click to collapse
It's strange, it's work fine for me.
Hunteres said:
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
Click to expand...
Click to collapse
Take a look at the #5 post
No official nightly build has been built yet by the build bot......thats the automated rombuilder witch is used to build the roms.....so if no rom is built no rom in rom manager ......
Sent from my GT-I9100 using Tapatalk
i have just tryed installing an app via the market website to my mobile and its working fine for me....
Hello,
Is there any way I can increase vibration intensity? It is fine when I reboot it but after a minute the vibration becomes very weak to the point where I can barely feel it. (When typing and pressing "menu" or "back button" etc
Sent from my GT-I9100 using XDA App
It's a known issue of this ROM.
There is nothing to do for this time.
Cyanogen #1 !
Issue gonna be FIX, by next build's
i just have one question, someone said they used kg1 modem does that actually stay or would cm7 just overwrite it anyway?
since im too noob to post in development section i want to thank you all at teamhacksung for this
Also...why was the stock camera app replaced with one that is worse? (Camcorder is worse.) Its a great rom. But can someone explain this to me?
Sent from my GT-I9100 using XDA App
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
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for nexus 6 (shamu) too.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 6 (aka shamu) it's the CPU's task. Even though the nexus 6's CPU has 4 quite fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 6)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
Thank you for this!
I can easily extend support for more devices. Do you guys know of some that have forceencrypt enabled?
Excellent work.
Hello everybody,
I just released version 6!
In this release, FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
Enjoy
Edit: Confirmed as working for latest Chroma build. (9/18)
Can anyone confirm this working for Chroma? Truly don't want to deal with starting from scratch ...
Hello everybody,
just to let you guys know - I just checked the new marshmallow factory image for shamu (MRA58K) => FED-Patcher should work for this new image too.
Enjoy!
This worked perfect for me just flashed then formatted data and boom I'm unencrypted again thank you op
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
gladiac said:
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
Click to expand...
Click to collapse
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
spunks3 said:
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
Click to expand...
Click to collapse
Yes that should work!
//EDIT: No it does not. It keeps looping after installing SuperSU with the following error:
Code:
avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=104419 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Probably some selinux problem :/. I might dive into this later this week. Sorry.
//EDIT #2: Now that I think about it... Doesn't the SuperSU flashable ZIP take care of the needed policy rules so the error that I posted above does not happen? IMHO it is SuperSU's task to take care of these things.
I might have to retest with the actual SuperSU installer. I had used TWRP's SuperSU installer. Maybe that one is broken somehow...
//EDIT #3: Nope! Supersu definitely does not work. I just tried with BETA-SuperSU-v2.50.zip. The SELinux policy-set that comes with the stock marshmallow factory images lacks the necessary rules to enable SuperSU to work.
However, adding these rules is something FED-Patcher was not designed to do. IMHO the SuperSU flashable ZIP should take care of this.
FYI: Nexus 6 is a QUAD core. Not just 2.
doitright said:
FYI: Nexus 6 is a QUAD core. Not just 2.
Click to expand...
Click to collapse
Thanks, I just fixed it. Shame on me.
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
finesse said:
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
Click to expand...
Click to collapse
Hi @finesse,
FED patcher must be run after installing a rom in order to disable the forced encryption flag. If the rom does not have forced encryption enabled (pretty common on non-stock and non-cm12.1 roms) you do not need to run FED patcher at all. Background: What FED-Patcher does is that it just takes the boot-partition of the currently installed rom and modifies it.
Wiping (in TWRP: "Wipe" - "Factory reset") is essential after backing up if the phone is currently encrypted. Sadly, you cannot simply just disable the encryption. Only formatting the partition (=wiping) will get rid of it.
I hope I could help .
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Will this work on anyother device having Marshmallow... Its a MY6753 device.
or any way to edit you patch and make it work on my device....
gladiac said:
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Click to expand...
Click to collapse
rawdealer said:
You didn't Format the Data It's quite a large button in twrp
Click to expand...
Click to collapse
Emilius said:
OMG, please don't tell anyone
Click to expand...
Click to collapse
rawdealer said:
FORMAT DATA, the extra large button
http://forum.xda-developers.com/and...v8-forceencrypt-disable-t3234422/post63810702
Click to expand...
Click to collapse
haibane said:
Rawdealer, I got it to work lol. Just seemed odd that you had to Format Data instead of doing a full wipe of everything. I'm guessing the Format Data just had to occur after CM was installed.
Click to expand...
Click to collapse
SamS1989 said:
it does not working on my n6 (7.1.1 stock)
what i do :
- flash 7.1.1 factory image
- turned off after the flash, reboot in fastboot
- boot twrp (without flash)
- flashed the V8 fed
- wipe data/cache (in twrp)
and after the reboot the phone stil decrypted
should i do the factory reset from settings or it's good from twrp ?
Click to expand...
Click to collapse
rewrite the instructions in both threads:
flash FED-Patcher.zip
use the Format Data button!!! neither Swipe to Factory Reset! nor Advanced Wipe!
v8 works well for nexus 6 stock 7.1.1, thanks to the op @gladiac and the discoverer @rawdealer, would better someone quote this in the other thread since New members (those with few posts) are not permitted to post to development-related forums
Bump
Thanks for this.
Does FED-Patcher still not work with Nougat?
I tried to use the detailed instructions here:
https://forum.xda-developers.com/nexus-6/general/how-to-disable-force-encryption-nexus-6-t3220273
I am not a pro at any of this, including TWRP.
I downloaded the Factory Image from Google (7.1.1 July for Shamu , Nexus 6)
https://dl.google.com/dl/android/aosp/shamu-n6f27h-factory-718e138f.zip?hl=vi
I unlocked and rooted my N6, flashed TWRP.
I followed all the instructions. When I got to step 8: Flash your ROM, it wouldn't work. I kept getting Zip verification errors in TWRP. I also tried to do it in NRT.
I was told that you can't install a Google factory image via TWRP. I guess the factory image would overwrite the recovery with stock. (my guess)
And when I used NRT, I got a hash mismatch when I tried to flash the factory image it as a ZIP.
NRT would only install the factory image via "Flash Stock and Unroot" which I guess defeats the purpose of this.
So I can go back to those instructions but am unclear which Android ROM to flash at step 8.
Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
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. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.
so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)
New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid
Thanks you for the ROM!
This is This is stable or beta or testing? Thanks
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....
Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.
yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...
New build 18032016 is up on basketbuild and Google shares
Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.
drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF
Official CM13 ROM, by Nikita Pro Android is availabe here:
http://forum.xda-developers.com/g2-mini/development/cyanogenmod-13-0-lg-g2-mini-t3260495
Preamble
Why am I doing this guide?
The main, developer's post has about 100 posts and it's really annoying to find useful information in this mess... The same questions appear all the time (I also had to ask them again). I decided to gather the important things in one place. Besides - ROM is quite unique and differs from others. If I wrote something wrong, tell me, I'll fix it. Sorry for my not perfect English.
I will look at the whole case as a simple user (who I really am! lol).
Stability
It is a subjective topic, so please take it with a pinch o salt. If I would have to rate the stability it will be 4 out of 6 (where 1 is a bricked phone and 6 is the flawless system work). System apps (like Documents or Themes) rarely can crash, but the system reboot fixes it. Generally every day usage is completely fine and you'll never get a random reboot on the go. What users have been reporting are problems with crashing default music player (confirmed by me). I personally noticed, that while using ProPlayer (IMO one of the best music players) songs rarely are randomly muted or skipped. Another thing reported is a signal losing (I haven't experienced it). GPS for me is going like crazy.
Storage mysteries
I don't know, if it's a bug or a feature, but there have been done serious changes to storages' permissions. It's probably an effect of allowing convertion of external SD Card, to internal memory. But let us start from the begginig...
When you'll first boot to the system, you will be asked, if you want to keep your SD Card memory as mass storage device or if you want to format it as internal memory.
1. If you won't format
Apps will be only able to use the internal memory. They will have no permissions to change anything or write to SD Card. It means, that you won't be able to download files to it or even manage it with file manager (even if it will have root permissions!).
You will be able to access internal and external memories from TWRP.
2. If you will format
You won't have access to old internal memory from system (practically it will disapeare), but instead you will gain full access to your SD Card.
Internal and external memories will be still available through TWRP.
Remember to make a backup to your PC, before formatting ;P
TWRP
You will have to flash TWRP 3.0.0 to get full access to SD Card after formatting.
http://forum.xda-developers.com/g2-mini/development/unified-twrp-recovery-3-0-0-lg-g2-mini-t3311316
Super SU
If for some reasons you don't want to use build-in root (for example I really don't like this hash sign on the statusbar), here's what you do:
1. Turn OFF build-in root in Developer Settings (if you don't, you'll get bootloop)
2. Flash Super SU through TWRP with the flashable ZIP from the Official thread (don't use Super SU App for this!) http://forum.xda-developers.com/showthread.php?t=1538053
3. When you boot to system, Super SU with root will be ready.
4. Reboot again to fix the Super SU app (it can crash)
XPosed
XPosed works with official version for SDK 23 arm.
http://forum.xda-developers.com/showthread.php?t=3034811
SELinux
If you want to change it from enforced to permissive, look here
http://forum.xda-developers.com/g2-mini/general/guide-how-to-set-selinux-to-permissive-t3329439
Release information
ROM is being developed on two channels: Nightlies with everyday (beta) updates, and with Release channel (with more stable versions).
Changelog can be found here http://www.cmxlog.com/13/g2m/
If you want to change channel from Nightly to Release - here's the official information what to do:
Update scenario 3: CM 13.0 nightly user
Update steps: Stop. Step away from the phone. Do not flash these builds, you are already on a newer codebase (Android 6.0.1_r22). Attempting to flash these release builds will result in crashes due to attempted database downgrades. Don’t do it.
If you want to swap off nightlies and stick to our release channel, you will have to wipe to take these builds.
Click to expand...
Click to collapse
Source: http://www.cyanogenmod.org/blog/cm-13-0-release-1
Download page: http://download.cyanogenmod.org/?device=g2m
Rest of the information is in the main Nikita's post.
PS
If you think I skipped something important, tell me...