[ROM] CyanogenMod 10.2 Stable for Nook Color
- Thread starter steven676
- Start date
Kernel security patch (and boot failure fix?)
A security bug in the core kernel (CVE-2014-0196) allows users to overflow a buffer via exploiting a race condition in the tty code, allowing privilege escalation (root) by a local attacker.
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p2) contains a patch for this bug. Proof-of-concept code exploiting this vulnerability has been public since last week, so it's recommended that you upgrade as soon as possible.
I've also taken the opportunity to land what might be a fix for the reported boot failures on 10.2.1. Please try this kernel and report back if you have a device that freezes while booting 10.2.1.
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel posted on the CM10.1 thread instead. CM11 nightly users: upgrade to a nightly from May 14 or later to get this fix. See my post on the dev thread for more information.
Hashes for the attached kernel zip:
A security bug in the core kernel (CVE-2014-0196) allows users to overflow a buffer via exploiting a race condition in the tty code, allowing privilege escalation (root) by a local attacker.
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p2) contains a patch for this bug. Proof-of-concept code exploiting this vulnerability has been public since last week, so it's recommended that you upgrade as soon as possible.
I've also taken the opportunity to land what might be a fix for the reported boot failures on 10.2.1. Please try this kernel and report back if you have a device that freezes while booting 10.2.1.
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel posted on the CM10.1 thread instead. CM11 nightly users: upgrade to a nightly from May 14 or later to get this fix. See my post on the dev thread for more information.
Hashes for the attached kernel zip:
Code:
MD5: 0069a877acecc182b0964bc470fb9f67
SHA1: 7aaec9ddff2c954b389bcea938fc7c8197463c67
SHA256: c0b89783f6d17ad9092b2176e5722423b12bc113d902167c1b536f4a206380bb
Last edited:
That prompted me to check a Nook Color with M8G2FA eMMC (kindly provided by pastordl), and well, what do you know, it doesn't boot. (It's also OMAP3630 ES1.2 and ft5x06 touchscreen, manufacture date September 20, 2011.) The kernel update I just posted above does, though -- hopefully that solves your problem too?
More kernel security bug patches!
Two security bugs in the core kernel (CVE-2014-2851 and CVE-2014-3153) allow local attackers to gain elevated privileges (root) through exploiting ping sockets and futexes, respectively. (See my post on the dev thread for more details.)
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p3) contains patches for these bugs. I do not know of public exploit code for these bugs, but with their wide publicity, exploits are certain to exist soon (if they don't already), so it's recommended that you upgrade as soon as possible.
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel posted on the CM10.1 thread instead. CM11 nightly users: upgrade to a nightly from June 6 or later to get this fix.
Hashes for the attached kernel zip:
Two security bugs in the core kernel (CVE-2014-2851 and CVE-2014-3153) allow local attackers to gain elevated privileges (root) through exploiting ping sockets and futexes, respectively. (See my post on the dev thread for more details.)
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p3) contains patches for these bugs. I do not know of public exploit code for these bugs, but with their wide publicity, exploits are certain to exist soon (if they don't already), so it's recommended that you upgrade as soon as possible.
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel posted on the CM10.1 thread instead. CM11 nightly users: upgrade to a nightly from June 6 or later to get this fix.
Hashes for the attached kernel zip:
Code:
MD5: c83fb1fbc765e6e43c52947cf54eb0ea
SHA1: 97a2c02fc4b1b5da5c34275107cb7e6771af654c
SHA256: 71e97199b74968a75d4d9c1c5b0efb34ef9f1a2505831071d6a89418c12a4a42
Last edited:
Today I was throwing on CM10.2 for a friend's Nook Color.
I kept getting a blank screen on boot, your patch instantly fixed it!
Thanks so much.
I kept getting a blank screen on boot, your patch instantly fixed it!
Thanks so much.
I followed the directions to the letter and my daughters nook color is now running CM 10.2. it's running pretty good but a bit slow. Is this normal functionality for Cm 10.2 on the NC? If so, should I now flash it with CM 11 to perhaps speed it up a bit?
Hello everyone,
I've been using Mirage CM 7.2 (from 2012) for ages. In 2012. I also tried CM 10 (20121211-nightly) and it was incredibly slow. Everything was dragging. Since then there was CM 10.2.1 in 2013-11-02 which I didn't try. Regarding CM 11 I heard it's even slowlier.
What would you suggest me? To reinstall latest CM 7.2 from 2014. or try CM 10.2.1 (or one of the close working alternatives)? I hope CM 10 from 2013. is faster than CM 10 from 2012.
I'm using email, YT, TapaTalk, just the usual stuff, few simple apps. But CM 10 from 2012. was even extremely slow on screen rotation.
Thanks a lot, folks!
I've been using Mirage CM 7.2 (from 2012) for ages. In 2012. I also tried CM 10 (20121211-nightly) and it was incredibly slow. Everything was dragging. Since then there was CM 10.2.1 in 2013-11-02 which I didn't try. Regarding CM 11 I heard it's even slowlier.
What would you suggest me? To reinstall latest CM 7.2 from 2014. or try CM 10.2.1 (or one of the close working alternatives)? I hope CM 10 from 2013. is faster than CM 10 from 2012.
I'm using email, YT, TapaTalk, just the usual stuff, few simple apps. But CM 10 from 2012. was even extremely slow on screen rotation.
Thanks a lot, folks!
I'm not sure if this helps, but I do have MROM which was built off of CM10. Here's the link to download:
https://www.dropbox.com/s/we7iilx78bjq54a/MROM-10.1-20131003-encore.zip?dl=0
Thanks but do you happen to have 10.2.1 stable release? Could you upload it to Dropbox (this one got server 503 error: https://download.cyanogenmod.org/get/jenkins/57353/cm-10.2.1-encore.zip)
Thanks.
Just in case anyone has pulled a Nook Color out of a dark place and wants to tinker here is the CM mother-load:
http://techerrata.com/browse/cm/encore/nightly
http://techerrata.com/browse/cm/encore/nightly
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
14The NookieDevs are pleased to announce the CyanogenMod 10.2.1 stable release for the Nook Color!
As the "stable" label suggests, all major features of the hardware work and the release should be suitable for day-to-day use on your Nook Color. As the "stable" label also suggests, updates (if any) will be primarily to fix bugs -- new features and big changes should not be expected.
Highlights: (not news if you've been keeping up with CM10.2 nightlies)
- Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases. (Yes, we went backwards from the last 10.2 nightlies to avoid some rare crashes suspected to be related to the USB/charger port driver.)
- All of the features of CyanogenMod 10.2, based on Android 4.3. All of the changes and bugfixes up to our last CM10.2 nightly (20140119) are included in this stable release.
- Full 2D and 3D graphics acceleration using the GPU, with improved performance over previous releases.
Known issues:
- Current releases of Netflix do not work with CM10.2 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
This release represents the end of active development on CM10.2 -- future efforts will focus on ROMs based on Android 4.4 and later. Critical bugfixes (for security holes, device-bricking bugs, eat-my-data bugs and the like) may be distributed as point releases (CM10.2.1.x); other important bugfixes (if any) will be distributed as patches on top of the 10.2.1 release.
Download:
https://download.cyanogenmod.org/get/jenkins/57353/cm-10.2.1-encore.zip
After flashing the above package, installing the latest kernel patch for CM10.2.1 is strongly recommended.
Code:MD5: b4ad9daaf2335b96455795867dd5e667 SHA1: ae30dbc7946dd67a044dc972c8718628046a0c7c SHA256: 0c35a2ab2592a83fb3b8c376c928ea1f9bb91da996d2928d51c6f9e898c48489
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.2.1 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.2.1 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.2.1 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which historically provided excellent support for its embedded platforms to the open-source hacking community.
XDA:DevDB Information
CyanogenMod 10.2 Stable, ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.2.1
Stable Release Date: 2014-02-01
Created 2014-02-01
Last Updated 2014-06-064Google Apps; other CyanogenMod builds
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
As of 2014/02/01, the latest release for CM10.2 is 20130813, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.2 stable releases. There are other official CyanogenMod builds for Nook Color available:
- CM11 nightly builds -- these experimental builds, based on Android 4.4, contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting.
- CM10.1 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.2, you may find this Android 4.2-based release more (or less!) stable than this Android 4.3-based one.
- Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)43Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions.
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.2.1 stable, "cm_encore-userdebug 4.3.1 JLS36I bf3d49df9c test-keys") seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:I'm having a problem with my Nook Color running CM10.2.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.2 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
- Does the problem occur with a clean install of CM10.2? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
- Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
- Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
- Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
- For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
- For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
- For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
3
That prompted me to check a Nook Color with M8G2FA eMMC (kindly provided by pastordl), and well, what do you know, it doesn't boot. (It's also OMAP3630 ES1.2 and ft5x06 touchscreen, manufacture date September 20, 2011.) The kernel update I just posted above does, though -- hopefully that solves your problem too?
