Have you seen this app? I find it amazing, it will automatically download differentiated files between your current CM build and the latest build.
It's free from Google Play (but you can donate to the devs from the app) and it is only for CyanogenMod roms.
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Description
Tired of download 200 MB everyday to get your latest CM nightly?
CyanDelta lets you update your CyanogenMod ROM by downloading just a small delta file (about 10 MB) instead of a big full zip file each time. With CyanDelta you can finally update your ROM in just some minutes even with a slow and expensive 2G or 3G connection!
CyanDelta is the perfect replacement of “CM Updater”, “ROM Manager” and “BBQLog”. When a ROM update is available it will notify you and show the changelog between the version you have installed and the new one. If you decide to update, it will delta-download the new version and if you want it will automatically install the new zips via recovery.
Main features:
✓ Security: all downloaded data is digitally signed by us to prevent manomissions.
✓ Recovery zip install: it can automatically reboot to recovery, install the ROM zip and other additional zips (kernel, modem...), wipe dalvik cache and reboot (requires root).
✓ Changelog: if you have a NIGHTLY build, when an update is available, CyanDelta will show you the list of changes between the ROM version you have installed and the new one.
✓ Update notification: when a ROM update is available, CyanDelta will notify you.
✓ High efficiency deltas: it uses the RFC3284 VCDIFF algorithm and some magic to produce really small deltas.
✓ Supports TWRP and CWM-based recovery, but NOT the closed-source ClockworkMod (the name is similar to CWM-based, but it’s a different thing!), since it's locked down by its author to only work with ROM Manager. If you have an unsupported recovery you can just manually install the zips generated by CyanDelta.
✓ Supports all official CyanogenMod ROMs and devices listed in http://get.cm
Click to expand...
Click to collapse
FAQs:
How much small are delta updates?
Typically they are about 10 MB, but it depends on how many changes has been made between the old and the new version. Sometimes it may be low as 5 MB, and sometimes a bit bigger, about 30 MB.
Before start downloading the delta update, you can always see the exact size of the data to be downloaded, so you can decide if download it or not.
What kinds of recovery does CyanDelta support?
CyanDelta supports TWRP recovery and CWM-based open-source recoveries (they are the open-source version of ClockworkMod recovery)
CyanDelta failed to install a zip in recovery on my device!
You probably have the official closed-source ClockworkMod recovery. It’s not supported by CyanDelta because his author has locked it to only work with his proprietary app “ROM Manager”, so we are unable to support it.
If you have that recovery you can replace them with the TWRP recovery (download from here: http://teamw.in/project/twrp2 ) or a CWM-based recovery. Otherwise you can just manually install the zip files generated by CyanDelta.
To use CyanDelta with nightly builds, I must update everyday?
No! It’s not necessary to always update to every new build. You can update only when you want, for example when you see something interesting in the changelog. Currently our server makes deltas between the 40 precedent builds, so for example if you use nightlies, you will always get delta updates unless you have a 40 days old version. If your version becomes too to get delta updates, you will need to download the new full zip from get.cm and import it in CyanDelta.
CyanDelta says “Zip not present in our database, ....”, why?
This may be caused by several reasons:
- if some hours or days ago CyanDelta has always worked fine, it’s almost certanly caused by the server that is rebuilding deltas, it’s the sign that a new update is coming. Just wait some minutes (in exceptional cases it may take some hours) and then reopen CyanDelta, it should show you the update.
- if you have just imported in CyanDelta a zip you just downloaded from get.cm, it might not have been imported yet in our database, wait some minutes or hours and then re-open CyanDelta.
- if you have just imported in CyanDelta a zip that you didn’t downloaded from get.cm, it’s almost certanly a unofficial CyanogenMod build that is not supported by CyanDelta.
- if you have a zip that you didn’t update since a lot of time (40 days for nigthly builds, many months for others), it might not be supported anymore by CyanDelta. This means that you must manually download from get.cm the new zip and import them in CyanDelta.
Can you give me step-by-step instructions to use CyanDelta?
- Install CyanDelta from Google Play.
- Download from CyanogenMod website the .zip file of the ROM you are using.
- 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).
On what devices and what ROMs does CyanDelta works?
CyanDelta works on all ARM devices running CM7, CM9 or CM10. Note that only official CyanogenMod ROMs available in http://get.cm are supported. For the moment CyanDelta doesn’t work on x86 devices because it uses a native ARM binary of xdelta3.
Does CyanDelta works with my recovery?
CyanDelta can automatically install new zips in CWM-based recoveries and TWRP recoveries. If you have an unsupported recovery, you can simply use CyanDelta to download the new updated zip and then install it manually in recovery, it’s in Cyandelta directory. Otherwise you can install the
The official ClockworkMod recovery it’s not supported because it’s closed-source and it’s locked down by his author to only work with ROM Manager (doesn’t support extendedcommand scripts). The CWM-based recoveries are identical to original ClockworkMod, but they are completely open-source and support extendedcommand scripts, so they work with CyanDelta.
Is CyanDelta secure?
CyanDelta has been designed from the beginning with security and safety in mind. If you are connected through a public untrusted network (a public wifi hotspot) it’s a lot more secure than download zips from CyanogenMod website.
When the CyanDelta app on your phone connect to our server to get updates, it downloads a JSON with update infos signed with our RSA 2048 bit key, that contains SHA1 hashes of the delta files downloaded by our server. In this way we have a HTTPS equivalent security, although we use HTTP for efficiency reasons.
When the app generate a new updated zip, it will always check if his hash match with the one written in the signed JSON, so data will not get corrupted.
What happens if something fails while installing zips in recovery using CyanDelta?
Theorically the recovery will simply not install the new zip, so it will not damage anything. However since is impossible to test that in all existing devices, there may be strange bugs in your device that might theorically corrupt your data and make your device unable to boot. Unfortunately we can’t prevent this, so you always use this feature at your own risk.
Before installing a zip with CyanDelta for the first time, we suggest you to do a nandroid backup manually.
What happens if the new ROM I have just installed doesn’t boot or it’s unusable?
We know that you want to always use the latest cutting-edge most experimental and unstable ROM! And we know that sometimes these updates can suddently leave you with an unusable device.
To prevent this, CyanDelta always keep one zip file of a previous version of the ROM you are installing. So if the new ROM doesn’t work, simply go to the recovery, reinstall the old zip et voilà!
Thanks to this, we think it’s reasonably safe to update your ROM even without making a nandroid backup every time before flashing.
Why the generated zips by CyanDelta have different size and MD5 than the official CyanogenMod zips?
Because zip files generated by CyanDelta are decompressed. Since data is stored uncompressed inside these zip files, they are bigger and obviously they have different MD5 too.
We have to do that because delta files generated between two uncompressed zips, are a lot smaller than between two compressed ones.
I don’t trust you! If the MD5 is different than the official CyanogenMod zips, who assures me that you haven’t tampered zips?
The content of our zip files and official ones are exactly the same. You can verify that by comparing the hash of every file inside the zip.
Zips produced by CyanDelta are identical (have the same MD5) for all our users, so everybody can verify if the files have been tampered, and in this case alert the whole community.
Does CyanDelta supports other ROMs apart from CyanogenMod?
Not for that moment, but we are planning to add support for other ROMs too, provided that they are completely free to redistribute by us. We will not accept anything that is based on non-free ROMs released by device manufacturers.
If you are a ROM developer that comply with these conditions and you are interested to make your ROM supported by CyanDelta, please contact us.
Click to expand...
Click to collapse
Looks like must have app for cm and should be integrated in cm.. My opinion
Sent from my XT910 using Tapatalk 2
ROM Manager by Koush uses another delta update solution, so there's little chance that CyanDelta will prevail.
I'd like security aspect to be more pronounced, so that you could be less paranoid about updates being tampered with.
It looks convenient to get system updated. But it's safe?
Sent from my XT910 using xda app-developers app
zhichao22 said:
It looks convenient to get system updated. But it's safe?
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
Why not?
Sent from my XT910 using xda premium
Jack'O said:
Why not?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
testing :good:
Be interesting to hear some detailed feedback on this app. I like the idea of incremental updates instead of totally reinstalling each new rom update.
Sent from my GSM XT910 running AOKP V7 using Xda Premium
I have CM10.1 and installed CyanDelta, I found it easy to use, but for some reason its folder is created on the external sdcard and when it tries to automatically install the update, the recovery doesn't find the update because it searches in the internal sdcard. Now I just use it to download the update and then install it manually.
lukaop said:
I have CM10.1 and installed CyanDelta, I found it easy to use, but for some reason its folder is created on the external sdcard and when it tries to automatically install the update, the recovery doesn't find the update because it searches in the internal sdcard. Now I just use it to download the update and then install it manually.
Click to expand...
Click to collapse
same here, but i can access to the external sdcard so i dont have any problem, works perfectly :good:
What do you mean with that? Is there a way to fix this issue and make CyanDelta really automatic?
Just wait for the next nightly, the internal and external SD cars have been swapped just to tackle this particular issue.
Vatazhka said:
Just wait for the next nightly, the internal and external SD cars have been swapped just to tackle this particular issue.
Click to expand...
Click to collapse
Yup flashed 04-06 here and now the folder shows correct, when a new nightly is released I will try it.
Anyone use cyandelta? I have been trying to use it for the last 2 months but it always comes back with this error during the execution of xdelta. Anything I can do?
Tnks!
Testing.
Right now the app says there is not update available, I will wait a few days to see how it works.
Thank you for the app.
iZak17 said:
Testing.
Right now the app says there is not update available, I will wait a few days to see how it works.
Thank you for the app.
Click to expand...
Click to collapse
I was just trying it out, doesn't work for me since I can't tell it to look on my SDCard.
RedBullet said:
I was just trying it out, doesn't work for me since I can't tell it to look on my SDCard.
Click to expand...
Click to collapse
I'm not using this app any more because for some reason, after download and install the small file made by CyanDelta, I just got bootloops, no matter what, always bootloops.
I'm don't know, maybe is because I use BMM not SS.
Now I'm on CM 11 4.4.2, Not sure if this app can be used with this ROM.
I am using it with CM11 nightlys myself. XT912, SS 3.65. Works great.
Sent from my XT912 using XDA Premium 4 mobile app
:good: Luv the ability to add JBX kernel zip and WIFIAP zip, and have all flash smooth!! xt912 SS 3.65, CM11 12/29 JBX 12/09, Cyandelta as updater, successfully flashed 12/27, 12/29 updates with extra zips, worked perfect both times!! :highfive:
Installed last nightly through CyanDelta, and all the process went perfect. CM team has done a very good work.
Thanks!!
Enviado desde mi XT910 mediante Tapatalk
:laugh: Very sweet, 12/30 flash 7mb download, flawless update!! While download size not an issue, it does kinda "auto"mate the flash process, especially if you flash more then one zip regularly, like JBX or WIFIAP!! :highfive::good:
Related
*** CM9 nightlies have been discontinued.. see: http://forum.xda-developers.com/showthread.php?p=29135522#post29135522 ***
For those who have dabbled in the Nook Color or HP TouchPad scenes you may have seen unofficial CM9 nightlies from me.. so in the same fashion here are the Nook Tablet builds - these should be considered in Alpha status.
***The nightly builds are currently for the 1GB "Acclaim" Nook Tablets ONLY***
I take no credit for the work put in to get nook tablet CM9 running - all the credit there goes to chrmhoffmann, fattire, nemith and countless others I may not even know. Please be sure to thank them for their efforts. I'm just building ROMs from their source code.
I *strongly* recommend everyone look over fattire's guide for building and giving it a try to learn a little about how this all works, it's how I got started on the nook color with these unofficial builds. After clearing with fattire and chrmhoffmann I decided to provide these builds for people who don't have the hardware/ability to build themselves.
These builds are all straight sync with CM source along with the nook tablet device and kernel trees. They are *NOT* tested releases (I don't even have a Nook Tablet) so please be aware that the builds could be broken at any time, and are provided as-is. Please be comfortable with adb and/or using recovery to wipe/restore/nuke at any time.
Builds are sync'd at 9am UTC - they will be available to download approx 15 mins after that.
There is no official "changelog" for nightlies, you can reference the commits in the device tree, kernel tree and main CM gerrit. Note that the CM gerrit shows things that are merged for ALL official devices, not all of these will apply to the Nook Tablet, however, anything not referenced by a device name is also included in these builds.
The only addition I have made to these builds is the inclusion of "Goo Manager" as a system app. More on the reasons for this below...
Downloads
There are a few ways to get the builds:
1) Browse the hosted folder here: http://techerrata.com/browse/nightly_kangs/acclaim
2) Follow @CM_Acclaim on twitter for announcements of the builds as they hit the host (PLEASE NOTE: @CM_Acclaim IS A TWITTER BOT - don't bother tweeting at it)
3) Use the Goo Manager app to receive notifications of new builds and download them directly on your device.
Latest ICS gapps can be found here http://goo-inside.me/gapps or mirrored here http://techerrata.com/browse/gapps
Goo Manager - Notable features
1) Notification of new builds and gapps updates with one click - or auto-check frequency in settings. Goo Manager auto-checks the md5 for every download.
2) Automated flashing of downloaded roms/gapps/other files with TWRP
3) Install TWRP 2.1 with one click (menu - install openscript recovery) - TWRP is still experimental and will overwrite ClockworkMod on emmc.
4) *Incremental updates* (experimental) - if you like to stay on the bleeding edge and flash every night. Incremental updates are diff'd server side so you only download the changed files from the build the night before. These downloads average 30-40mb in size (vs ~120mb for the full rom), so you get faster downloads, updates and less wear on your device's flash memory. Incremental updates ONLY work from the previous night's build to the latest. When you check for updates in Goo Manager it will offer you an incremental if applicable.
Updates
For the latest updates/announcements follow me on twitter, or check back here.
Credit and Thanks
Thanks to chrmhoffmann, fattire, nemith and the rest of the CM acclaim team for making this possible. Thanks to fellow TeamWin members Kevank for providing the hosting and to s0up for the Goo Manager app.
Neat.
This should make things easier.
Again though-- until some changes are added to the 3.0 kernel, if you have a newer 512MB NookTablet, the nightlies won't work and you'll probably come up with a blackscreen and have to reflash. Chrmhoffman's latest 2.6.35 build though should work if you have the newer model and/or want the 2.6.35 kernel w/cm9.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
Warning: This will overwrite the internal storage with CM9. The instructions below assume you have a rooted NT running stock, CM7, or CM9.
Requirements
1GB NT (the 512MB NTs are not yet supported by the 3.0 kernel.)
Software: Rooted stock, CM7, or CM9
A full battery
a formatted SD card in the slot
wifi connection
(something else?)
To install the experimental CM9 w/3.0 kernel on a 1GB NT:
(steps are from memory and are to be refined soon)
Use the Google Play Market or other method to install Goo Manager to your device.
Run Goo Manager. Select the menu, and chose "install openscript recovery". Click through the options to confirm. At some point you may be asked to give Goo Manager superuser permissions.
The above steps should now cause TWRP2 recovery to be installed to your device. (You only need to do steps 1-3 again when you want to update or reinstall the TWRP2 recovery image.)
Now you can browse compatible roms for your device. Under /devs/eyballer/nightly_kangs/acclaim/ you should see some nightly builds. Choose the one you wish to install. Wait for it to download.
Once it's downloaded successfully, you should be able to select the newly downloaded rom from the notification menu, and then request that it be installed. Alternately, you can go to the Flash ROMS menu to flash previously downloaded ROMS.
See elsewhere in this thread for any other update.zips that you may wish to download and install. You can put more than one update.zip in the queue.
When you are ready, select the order and flash selected button on the bottom right.
It is sometimes preferable to wipe the cache/dalvik cache partition when doing an upgrade. You also have the option to automate a backup (not a bad idea). If you are coming from stock BN software or for any other reason wish to clear all user information, you may also wish to wipe the /data. partition. This is not generally recommended as wiping /data will delete your personal information.
When you're done configuring your flash, choose Flash, and then confirm.
If all goes well, there will be a reboot, your choice(s) will be flashed, and then the system will restart into the new CM9. If it doesn't work (very possible, as this is still experimental), post below and let the devs know what went wrong.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
This video has more information about TWRP2 and Goo Manager, although the device discussed is a HP Tablet. Some things like the boot menu will be different, but most other details will apply.
Good luck, and be sure NOT to do this with an 512MB Nook Tablet. If you screw up and do install it, you will need to re-flash a CM9 using 2.6.35.
fattire said:
This should make things easier.
Again though-- if you have a newer 512MB NookTablet, the nightlies won't work.
Click to expand...
Click to collapse
I'm assuming it's because it's using the newer kernel?
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Keithn said:
I'm assuming it's because it's using the newer kernel?
Click to expand...
Click to collapse
Yes, the 3.0 kernel has issues with 512MB-- the kindle fire had the same issues, and if you read the latter few posts in the kernel thread, you can read more about it. Hashcode apparently knows how to fix it, but until then, don't install this on a 512MB NT.
SilentStormer said:
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Click to expand...
Click to collapse
No guarantees. eyeballer is using the latest experimental one from the twrp thread. It has the fix from arcon and has been successfully used by frustro. I of course have not ever run it, so I can't make any claim of success.... this is all experimental.
The builds are nightly, so right now they're about at par with chrmhoffmann's alpha .04 (which of course uses 2.6.35 kernel), but if I'm not mistaken, eyeballer builds 'em fresh every day from the cm9 repos plus whatever changes are made to the kernel and acclaim-specific repositories. That means they can be total crap in the future, and who knows if twrp2 is even any good either...
This is seriously guinea pig territory. So unless and until you're willing to take some risks, you might want to hold out for what others have to say.
I can confirm that this worked for me.
1. Intall goomanager from play.google.com
2. from menu choose install openrecovery script, it downloaded and installed openrecovery-twrp-2.1.4-acclaim.img
3 browse compatible roms, navigate to /devs/eyballer/nightly_kangs/acclaim/ and choose the first one
4 menu home
5 choose download gapps packages and choose gapps-ics-20120429-signed.zip
I had 2 download failures and had to repeat these steps till the download was correctly completed and then main menu flash roms select the 2 zips and I was done
very nice and smooth.
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Do we have to use twrp to install this rom?
meghd00t said:
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Click to expand...
Click to collapse
You're requesting tun.ko and cifs.ko compiled as modules?
Used Goo Manager to flash TWRP, had to pull the SD card and install it for it to mount.
Downloaded the first 900 build (I see there is 2 for some reason)
Clean install including /system wipe
Have had 2 or 3 "sleeps of death"
Screen wouldn't turn on with N button or power button.
Had to hold power for 10+ seconds to do a hard shut down.
Cranked my screen off timer to 10 minutes.
Keep up the great work.
Also Netflix loads and has audio no video but I'm sure you're aware of that.
Two other things I've noticed.
Can confirm the SD card mounts every time so far but the SD card did randomly unmount once.
Lastly, when trying to download Atorrent (for watching Game of Thrones) I get an error saying "Can not install to USB mass storage or SD card"
Sent from my Galaxy Nexus
great share!
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Helltoupee said:
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
While this seems simple to add, it's not. My build system for these unofficial nightlies is completely automated so adding something to changelog would require me to go through the commits and then manually log into goo.im and update the rom info for every build. I don't do that for the devices I own, let alone the ones I don't
I posted links in the OP to all the source that is used to compile so it's up to the user to read and see if they would like to update. Of course as more people start running the builds, the discussion here usually will give you hints as to what's added too.
Updated the OP with another download notification method. We have a twitter system that will send out a tweet for every new build that hits our server with the link to the download and a QR code. You can follow CM_Acclaim for this.
Thank you for the explanation. I completely understand.
Sent from my Galaxy Nexus
Nighty change log blog thing I found for all CM9 builds. Enjoy.
http://changelog.bbqdroid.org/
Sent from my Galaxy Nexus
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
I kinda have a problem :\ I have lines running across half of my screen and its kinda freaking me out.. I'm not pointing fingers but it did happen after I installed this ROM
---------- Post added at 10:58 PM ---------- Previous post was at 10:52 PM ----------
My problem is solved... Oddly enough installing another rom makes the lines go away. I'm sorry for posting for no reason. lol have a great day
The 3.0 kernel still has problems. Hopefully these will be fixed in a later build.
digixmax said:
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
Click to expand...
Click to collapse
Don't try it. My modifications are for kernel 2.6.x version of CM9 not 3.0.x CM9.
I've build a bootable 3.0.x CM9 on sdcard. I wouldn't recommend this build yet due to LCD brightness and no sleep issue. LCD brightness will take 50% of the battery. This build is mainly testing.
I loaded recovery. Downloaded CM9 ics then gapps. When I go to flash roms nook reboots then I get the cynaboot image then nook boots back to cm7. What am I doing wrong?
The problem I was having is that cm7 did not mount my SD card on reboot. Had to load eyeballers first build through cwm. Then once in cm9 I could load through twrp. Running good so far.
I have received a couple of requests for openpdroid patches due to a recent post I made so if anyone wants a patch for their current ROM and don't know how to do it themselves, I would be happy to upload them for you. Please note that some ROM's will error when I run them through the program and will not create the patch. The only ROM I remember specifically is LiquidSmooth but I'm sure there are others. I'm running the latest vanilla 4.3 build from Neo and it works flawlessly. I will add the links for patches that I've already made and any requests will be added as soon as I am able to do so.
For those that do not know what openpdroid is check this link http://www.xda-developers.com/android/openpdroid-brings-an-open-source-privacy-solution/
In my opinion, it is better than the built in privacy manager in cm10.1/10.2 builds and far better than the app permissions option included in some ROMs because when you block an app's permissions, it will most likely force close. Openpdroid either allows you to transmit actual info, send fake data, or block it entirely. Some apps that require internet access like Zedge for example, there is an option in the pdroid manager app at the very bottom that says "force online state" and you will need to enable that so the app can have internet access but you can block everything else.
So all you have to do is...
1. Transfer the zips to your sd card
2. Reboot to recovery and wipe dalvik cache and then flash the update.zip
3. Reboot into your ROM and install pdroid manager from the play store and you're done
Every time you install an app it will have a notification in your statusbar for you to select what you would like the app to have access to.
If you have any problems with the patch you can reboot to recovery and flash the restore.zip or re-flash your ROM without wiping any data.
Here are the zips for cm10.1.2 stable
update: http://www.mediafire.com/download/8kj2vtmzaaf1k2b/cm-10.1.2-vigor-openpdroid-20130913-update.zip
restore: http://www.mediafire.com/download/aljmat376uihswp/cm-10.1.2-vigor-20130913-restore.zip
Zips for cm10.2 9/12 unofficial
update: http://www.mediafire.com/download/c...OFFICIAL-vigor-openpdroid-20130912-update.zip
restore: http://www.mediafire.com/download/s...0130912-UNOFFICIAL-vigor-20130912-restore.zip
THIS IS ONLY FOR AOSP ROMS
I find pdroid to be superior too. Thanks pctech!
Sent from my ADR6425LVW using Tapatalk 4
I was a long time user of pdroid (almost 2 years) until recently I switched to Xprivacy. Same features and more. Yes, for most Pdroid will work fine, but the option to hide running apps list and just typing in a location for spoofed GPS loc turned me over to it. (Type London, England, and it will put the exact GPS long and lat coords)
Also the need not to make a flashable zip (Xprivacy uses the latest Xposed framework).
Thanks though for the flashables if I decide to go back. Saves me time from doing it.
Sent from my ADR6425LVW using xda app-developers 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
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!
I have painted myself into a corner with a Samsung Galaxy S 2. It is my
girlfriend's phone and she wanted to play Pokemon Go. The Android
version there was 4.2 (CyanogenMod) with appropriate Google Apps. It has been
working reasonably well.
Pokemon Go needs to have at least Android 4.4, so an update was due. There was
a CyanogenMod snapshot of 12.1 (Android 5.1) which was installable from within
the old CyanogenMod. I hoped that this would go through well and we did the
upgrade. After the upgrade it indeed had Android 5.1. However, the Google Apps
directly crash, especially the Trebuchet launcher. This means that one cannot
start any apps or use any Google services. Especially the Google Play Store
does not work, it shows the error message [RH-01].
I first thought that we had upgraded to Android 4.4, therefore I installed the
Open GApps nano for 4.4:
(Due to forums policy I am not allowed to hotlink or link to the images.
So this is the best I can do now.)
http ://i.imgur.com/DRHqxNx.jpg
This then (unsurprisingly) failed:
http ://i.imgur.com/qjzrDKw.jpg
At least the error message was really helpful! So then I downloaded Open
GApps nano for 5.1. This then also failed because the GApps that I
have installed together with CyanogenMod years ago were not Open GApps but some
other package:
http ://i.imgur.com/0tI6eEn.jpg
At this point I got uneasy. Her phone turned into a paperweight with a
lockscreen. Since I could not seem to move the GApps forward without flashing
the ROM again, I tried to to so without wiping the data. For this I selected
the update mechanism in Cyanogen Recovery and flashed the Android 5.1
ROM onto the device. After this I tried to install the GApps again. However,
those still fail to install. Here I would guess that the CyanogenMod 12.1
“installer” does not wipe the system partition and leaving remnants of the old
GApps package there.
Since it got late I tried to at least get back to the old state and downloaded
the CyanogenMod with Android 4.2. Trying to flash this failed as the device
type was not picked up correctly:
http ://i.imgur.com/yZ9ilM1.jpg
I do not understand this error. This (or a very similar) version of CyanogenMod
has been present on the device up til yesterday. Why doesn't that work any
more.
A friend of mine suggested to replace the Cyanogen Recovery with the
TWRP. For this I have downloaded the appropriate IMG file from Team Win.
Then using heimdall-frontend on Linux I pulled out the PIT file and put the PIT
file back with the twrp.img file onto the recovery partition. Although the
heimdall-frontend told me that I had a success, there was still the Cyanogen
Recovery.
My current guess is that this phone has hardware which does not allow for a
separate recovery partition unless there is an IsoRec kernel installed. The
CyanogenMod 12.1 should have that, but the recovery is probably the one from
the CyanogenMod 10.1 as the option to update the recovery partition was not
checked when performing the OTA upgrade.
I'm stuck and I have no idea how to get the phone into a working condition. Do
you perhaps have an idea what I could do now?
Hi,
CM12.1 Snapshot unfortunately doesn't have isorec, hence you can not install the twrp .img file.
You can flash this and it will give you isorec kernel:
https://www.androidfilehost.com/?fid=24407100847293132
You will then be able to flash TWRP here:
http://forum.xda-developers.com/devdb/project/dl/?id=17876
Once that's install, reboot back into the recovery and you should have TWRP.
Wipe /system, /cache and /dalvik cache.
Flash ROM then flash gapps, then flash isorec kernel again (because once you flash ROM, you will have overwritten the kernel).
If you can't install gapps and it says you have insufficient space, use opengapps 5.1 pico instead.
gsstudios
I managed to install the IsoRec kernel. Then flashing TWRP worked and I was able to use it. The installation of Android 5.1 has worked, but I still had issues after cleaning up /system. Installing Android 4.2 or 4.4 did not help, it kept crashing either way. 4.2 even had an infinite boot loop.
Then I ended up wiping /data and installed 5.1 and the GApps Pico package. Then everything worked, even Pokémon Go.
Thank you for your help, you saved a phone from being unusable .
I have a smiliar issue. I updated to CM 13.0 as well to newest TWRP. I wanted now to install Open Gapps Pico package but can't flash because of insufficient system space.
Do you have an idea what to do now ?
Achi92131 said:
... but can't flash because of insufficient system space.
Click to expand...
Click to collapse
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Python Guy said:
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Click to expand...
Click to collapse
Thanks Phyton Guy, I will do that.
Tired of failed installed GAPPS ? Different reasons and many many lost time ...
Here is alternative :
1. Install UC Browser
2. Inside , you will find : 9Apps ( the same app as PlayStore )
3. Install 9Apps
- same app as PlayStore
- every app related to Google : working fine.
*** BONUS - install Video Downloader for UC Browser - search Google for this as APK file .
you can download on your phone any video on youtube , inside UC Browser .
That's it ! It's so simple and ...No more Google domination on your Phone !