I just try to install the 20151103 and it said incompatible and failed, and now I try to install 20151104 successfully but halt at "Google".What do you mean incompatible? I'm running it on my N9LTE without a single problem.
I just try to install the 20151103 and it said incompatible and failed, and now I try to install 20151104 successfully but halt at "Google".What do you mean incompatible? I'm running it on my N9LTE without a single problem.
But where did it said it? Can you be a bit more specific like...I just try to install the 20151103 and it said incompatible and failed, and now I try to install 20151104 successfully but halt at "Google".
I use TWRP.But where did it said it? Can you be a bit more specific like...
What recovery are we talking about? TWRP or CyanogenMod?
What was the real message without "your filter"? It's just that I want to help you out but you're making it too hard with just the "incompatible" stuff that you're mentioning![]()
Well... I would need more info to help you solve that problem. My N9 was the one that was used to do all the tests to bring up official flounder_lte CM nightlies and all the tests went OK.I use TWRP.
I can't reproduce the problem, but when I flash CM12.1 on it, it stop me and said the rom is incompatible. But when I flash back the stock rom and done several flashing (stock <-> CM) it is all ok but stuck at "google". Now I turn back to stock rom and rooted it.
@erioho It just has occurred to me that maybe you were using unofficial TWRP for flounder_lte instead of the official TWRP for flounder. Could that be it?Well... I would need more info to help you solve that problem. My N9 was the one that was used to do all the tests to bring up official flounder_lte CM nightlies and all the tests went OK.
If you plan to flash CM12.1 some time again don't hesitate to come back and request for help if you need to. After all, that is what XDA is all about![]()
Official cm doesn't take feature requests. Its built from official cm source so if it's not in CyanogenMod, its not going to be in this build either.Sorry of this is stupid, but where can I request a feature? The actual feature request part of the thread looks not maintained.
Will try it this afternoon when I'm back home!Looks like CM 13 nightlies are up for flounder and flounder LTE.
First try on flounder...dont boot....Looks like CM 13 nightlies are up for flounder and flounder LTE.
Seems i must update the bootloader, first i must load my accu...Please use TWRP 2.8.7.0. Must be at bootloader 3.48.0.0135 and have flashed the latest MRA58N vendor image
You need to update bootloader and vendor images.First try on flounder...dont boot....
Mayby i must update the bootloader i am on 3.44.1.0123, i see the new factory images have 3.48.0.0135
Update: here: http://forum.xda-developers.com/nexus-9/development/rom-t3219572 (Vanilla-ish AOSP 6.0.0_r2 ROM) bshiznit write:
Seems i must update the bootloader, first i must load my accu...
Try it later
So might anyone have a step by step (proven) sequence wipes & flashes for updating from the latest CM 12.1 nightly to the new CM 13 nightly? I mean would I flash the vendor and bootloader images via adb first, and then the CM 13 zip, and then gapps, or is there a more appropriate order of things in this case?You need to update bootloader and vendor images.
Sent from my Nexus 6P using Tapatalk
That's what I'd do.So might anyone have a step by step (proven) sequence wipes & flashes for updating from the latest CM 12.1 nightly to the new CM 13 nightly? I mean would I flash the vendor and bootloader images via adb first, and then the CM 13 zip, and then gapps, or is there a more appropriate order of things in this case?
I went from fresh stock 6.0.1 via fastboot, then via TWRP I flashed CM 13, followed by OpenGApps Pico and FED Patcher. Flawless.So might anyone have a step by step (proven) sequence wipes & flashes for updating from the latest CM 12.1 nightly to the new CM 13 nightly? I mean would I flash the vendor and bootloader images via adb first, and then the CM 13 zip, and then gapps, or is there a more appropriate order of things in this case?
Try using the aosp keyboard.It's certainly not a big deal, but I've noticed that the new emojis aren't in this ROM. Is that specific to a certain gapps package?
Sent from my Nexus 9 using Tapatalk
That did the trick! Thanks!Try using the aosp keyboard.
You need to flash the latest bootloader and vendor.img (drivers and such), at the minimum.So from what people are saying you can't update from CM12.1 to CM13?
Only clean install going via stock ROM?