[ROM] CyanogenMod 11 [OFFICIAL] [NIGHTLIES] [M5]
- Thread starter eak1080
- Start date
-
- Tags
- cm 10.2 cm 11 nexus 7 nexus 7 2012
You are our device maintainer then ?
I'm just a CyanogenMod member with a working Nexus 7
If you still have a working Nexus 7, would you mind taking a look at why CM12 source does not boot, since 5.0.1 ? At your own pace of cause.
Do we really need to wait for Google, to release new binaries ?
No, you probably need to pick this patch: http://review.cyanogenmod.org/#/c/81561/If you still have a working Nexus 7, would you mind taking a look at why CM12 source does not boot, since 5.0.1 ? At your own pace of cause.
Do we really need to wait for Google, to release new binaries ?
This is all over various Android news sites already.
Thanks for posting. I tried it again because it worked for you guys and this time it worked for me. I updated TWRP (was on the previous version) and downloaded the zips again. The md5 matched on the old zips, so I don't know what the deal was.
Had the same issue on a dirty flash. It took about 10 minutes on first boot and has been quick ever since. Not sure what was going on first boot.
I'm using gapps lp @todivefor and what I have found out is that if you hold the power button and restart the boot screen things go much quicker @pizzaboy192
I created a new thread for CM 12.0 at http://forum.xda-developers.com/nexus-7/orig-development/official-cyanogenmod-12-0-t2996413
Did the dirty flash work out for you?
I've seen other reports that the new ROMs take a *long* time to boot the first time, be patient.
I was impatient and dirty flashed LollerPop from a different thread here on XDA over the CM11 Nightlies and it took about 8 minutes to do the first boot. Everything is currently running 100% and haven't seen a single issue. The tablet still likes to lag compared to my wife's HP Touchpad, but I can't complain. I use my tablet on and off for small things and it seems to last about a week on a charge with maybe an hour of usage every day (If that). I've also noticed that the "Soft Brick on low battery" bug is gone from CM12 which I had issues with on CM11. Usually I'd be out my tablet for a day while it was trying to charge back up enough to boot, but that seems to be gone (Probably a change in how it handles low battery that is a bit more graceful than "Run until completely dead")
Not sure if this thread is dead or not, but I have a quick question that I cannot seem to find in a search here. I haven't updated my N& since the 20141130 build and have tried to update it to 20150212 and 20150304 but each time I do, it won't boot properly. I get the Google screen and then when it should show the bootloader image all I get is a black screen. I can go back to the 20141130 build, but I'd like to update. Any thoughts? Thanks in advance :good:
There's no full f2fs version of cm12, as far as I know. It officially supports data & cache f2fs. And you should ask in cm12 thread, not cm11.[emoji4]
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
282CyanogenMod 11 Android 4.4 KitKat
Nexus 7 3G Thread
Installation Instructions:
1. Download 11 Nightlies from: GET.CM
Download M5 LINK
2.Download GAPPS from: LINK
I would use BANKS GAPPS
3. Place on SD card(internal storage)
4. Reboot to recovery, Install XXX-grouper.zip, Install gapps.zip
5. Reboot and enjoy
Changelog
If you want to know the bleeding edge of what is being worked on/Merged
1. Nexus 7 Gerrit
3. CM Google+
UPDATES
1. CM 11 M5 is rock solid
2. Third party kernels are not supported by CM, try them out but YMMV.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lets try and keep this thread clean. Please use search, there is no need for the same question being asked and answered every few pages.30
At this point both CWM and TWRP boil down to some kind of GUI that drives some basic command line utilities such as tar and dd for backup and use primarily AOSP code for installing zips. The hard part is coming up with the correct commands for wiping and backup/restore. It's hardly rocket science. Neither should scare you. Writing code is an art, not a science. Maybe I don't follow all the standard naming conventions or use all of the preferred methods for C/C++ but that doesn't make it poor code and we're continually improving our code base.
Personally the only thing that scares me about recovery are the builds of CWM that random people build using koush's web-based recovery builder. You have people that know nothing about compiling, source code, or recovery using it and sometimes the results can be pretty non-functional.
TWRP is fully open source, so if there's something that you don't like you can download the source, change it, and submit your changes upstream. TWRP is technically not supported by the CM team, but that doesn't make it a bad recovery and if you need recovery-related support then you can certainly come to us. Thanks to landstander I actually have a Nexus 7 in my hand that I can use as a testbed to troubleshoot issues.
Now, I have no idea why this thread turned into a discussion of what recovery is better when the discussion in this thread should be focused on CM10.1. I would suggest that people get back to discussing the ROM and not the various recoveries that are available.2001/01/2013 Nightly: http://www.mediafire.com/?tqt0wccocgx7d0g
a5c11c07cebe711901e8ca177f885571 cm-10.1-20130101-NIGHTLY-grouper.zip
Feel free to mirror.
Took longer than I thought as usually I upload to goo.im, but I had some problems with that today.1615
Grouper M builds have to be approved by me at the moment. I was on vacation during the M11 and M10 approval time period so I couldn't do that.
I have no plans to miss this month's M build.
