FORUMS
Remove All Ads from XDA

 View Poll Results: Do you like CM13

Yes. It is awesome and works well on my device.
 
115 Vote(s)
47.33%
Yes. But it still needs to be worked on.
 
69 Vote(s)
28.40%
No. I've tried it but I've reverted.
 
13 Vote(s)
5.35%
No. Won't upgrade until it becomes better/stable
 
18 Vote(s)
7.41%
Haven't seen how it looks like/haven't bothered
 
28 Vote(s)
11.52%

[GUIDE][NOOB-FRIENDLY]Want to update to CM13? Read this first!

4,021 posts
Thanks Meter: 8,377
 
By Saber, Recognized Contributor on 13th February 2016, 04:08 AM
Post Reply Email Thread
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.
  1. 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).
  2. 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.
  3. Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
  4. 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.
  5. Flash the CM13 zip.
  6. (Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
  7. (Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
  8. 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/gala...-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/andr...aring-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
  1. Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
  2. If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
  3. Reboot your phone into Cyanogen recovery
  4. Select apply update from ADB sideload
  5. In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
  6. Select open command line menu here
  7. Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
  8. Cyanogen recovery should begin flashing TWRP recovery
  9. 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.
  1. Put your phone into download mode (Power key, home button, Volume Down button)
  2. Connect your phone to your PC
  3. 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
  4. Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/show...56&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.
  5. Select the CM12.1 kernel as PDA (or AP)
  6. Make sure you untick auto-reboot
  7. Start the flash.
  8. Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
  9. Get into recovery mode (Volume Up, Power Key, Home button)
  10. 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/show...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.
  1. Go into settings>about phone>system updates
  2. If there is a new build available, press the download button. The OTA updater will now download the update to your phone
  3. 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
  4. Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
  5. 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.
  1. Download Cyandelta from the google play store
  2. 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.
  3. 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.
  4. When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
  5. 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.
  1. 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!
  2. 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.
  3. Flash the CM13 zip
  4. Wipe cache
  5. 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
The Following 76 Users Say Thank You to Saber For This Useful Post: [ View ] Gift Saber Ad-Free
13th February 2016, 04:11 AM |#2  
Saber's Avatar
OP Recognized Contributor
Flag Melbourne
Thanks Meter: 8,377
 
Donate to Me
More
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.
The Following 33 Users Say Thank You to Saber For This Useful Post: [ View ] Gift Saber Ad-Free
13th February 2016, 04:11 AM |#3  
Saber's Avatar
OP Recognized Contributor
Flag Melbourne
Thanks Meter: 8,377
 
Donate to Me
More
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
The Following 17 Users Say Thank You to Saber For This Useful Post: [ View ] Gift Saber Ad-Free
13th February 2016, 04:13 AM |#4  
Saber's Avatar
OP Recognized Contributor
Flag Melbourne
Thanks Meter: 8,377
 
Donate to Me
More
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!)
The Following 21 Users Say Thank You to Saber For This Useful Post: [ View ] Gift Saber Ad-Free
13th February 2016, 05:03 AM |#5  
Junior Member
Thanks Meter: 2
 
More
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 ?
The Following 2 Users Say Thank You to rolves1899 For This Useful Post: [ View ] Gift rolves1899 Ad-Free
13th February 2016, 05:05 AM |#6  
Saber's Avatar
OP Recognized Contributor
Flag Melbourne
Thanks Meter: 8,377
 
Donate to Me
More
Quote:
Originally Posted by rolves1899

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 ?

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
The Following 3 Users Say Thank You to Saber For This Useful Post: [ View ] Gift Saber Ad-Free
13th February 2016, 05:10 AM |#7  
Junior Member
Thanks Meter: 2
 
More
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
13th February 2016, 06:15 AM |#8  
Draky50110's Avatar
Senior Member
Flag Cherbourg-Octeville
Thanks Meter: 145
 
More
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
13th February 2016, 06:26 AM |#9  
Account currently disabled
Flag Sydney
Thanks Meter: 965
 
More
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/d...yandelta&hl=en
The Following User Says Thank You to stylemessiah For This Useful Post: [ View ] Gift stylemessiah Ad-Free
13th February 2016, 06:42 AM |#10  
Saber's Avatar
OP Recognized Contributor
Flag Melbourne
Thanks Meter: 8,377
 
Donate to Me
More
Quote:
Originally Posted by Draky50110

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

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
The Following 4 Users Say Thank You to Saber For This Useful Post: [ View ] Gift Saber Ad-Free
13th February 2016, 06:44 AM |#11  
Saber's Avatar
OP Recognized Contributor
Flag Melbourne
Thanks Meter: 8,377
 
Donate to Me
More
Quote:
Originally Posted by stylemessiah

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/d...yandelta&hl=en

Thanks, will add this to the guide soon.

gsstudios
Post Reply Subscribe to Thread

Tags
android 6.0, android marshmallow, cm13, i9100, noob friendly

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes