CyanogenMod #200 SIM problem - Blade General

I installed CM Nightly #200 today & after installing it the SIM card doesn't work. Removed & put it back still doesn't work. Went back to #179 & still doesn't work. Please help!!!

I have the same problem, I installed the 201 and without SIM

200, 199 same problem - NO SIGNAL
and totally laggy, slow... both

You can't use CM 179+. ZTE libraries are missing from the current builds. For the time being, the last usable Nightly is 179.

Jackal331 said:
You can't use CM 179+. ZTE libraries are missing from the current builds. For the time being, the last usable Nightly is 179.
Click to expand...
Click to collapse
What's the status now. Did anyone try the latest ones.

Yes, since 206 (or 205 dont rememeber) you can use it again, I suggest you wait until 207 is out - it will have updated kernel.

Presently on #209. No issues so far.
And even it isn't freezing at higher CPU frequencies. Very nice.
Sent from my Blade using XDA App

Related

gen2 and reflash to cyanogenmod 7,0 ??

so, ive did the upgrade to gen2, and installed 7.0.3 cyanogenmod..
BUT the resets when i charge it, is annoying and i belive that wasnt an issue at 7.0.0? or was it??
can i reflash it back to the 7.0 now? or what about the 7.0.2? is that any better??
also- my phone is gettin slow... i really dont know why..
got like 4 giga available space at sd, and all apps are moved to sd..
Use the latest nightly (N100) and full wipe and flash.
The bug is fixed in later releases after stable.
oki. i will dl and flash it now..
is there gonna be a new cyanogenmod stable flash soon?
ps- many thanks!!
also--- what IS nightly builds anyway?
are they all different or are they finished roms?, but lets say 99 has the reset error and the 100 is the one that fixes it..
is the 87 or whatever build pre100 not as good as the latest 100 in today case?
Not that I know of.
They're usually experimental, but for the Blade they're probably as stable as Froyo ROM's.
They're like all the latest changes the CM team have made to the ROM.
Possibly, however N100 could have another bug instead (although this is not the case).
Refer to this for more info: http://wiki.modaco.com/index.php/ZTE_Blade_CyanogenMod
a new bug.. i like having an gps, so i use Sygic, and when i turn on Sygig, it makes the phone reboots..
so ill guess... hmm.. reset when charging or having a gps...??
any fix for this one?
EDIT...
just started up a compassapp that uses gps as well, found my location, went back in and started Sygic and starts up fine and no reboot..
lol... some things are random..
CM7 should reboot once when using GPS and then be fine.
many thanks!!
all good today..

[Q] CM7 7.0.3 Last Stable?

I've been running 7.0.2 off my SD for many months - quite happy though I would like the deep sleep and some of the new USB features. Has there been an updated stable version beyond 7.0.3? I remember seeing a 7.1.X on one of these threads.
Also - if I update the CM7 version, will my current data/apps remain intact?
Thanks
Polar
There is a 7.1 RC but the nightlys are pretty much stable these days.
You shouldn't lose any data but make sure to back up
---
- Sent from my LG Optimus V using Tapatalk
My friend, run the newest nightly, you will be glad you did! It even has the OverClock kernel built in! Plus the boot up speed has increased significantly. And more...................
Wipe Cache and Dalvik Cache--Install nightly
Be sure to get the nook tweaks app from Dalingrin, from the market!
http://download.cyanogenmod.com/?device=encore
Install nightly #150, you can download it from Rom Manager. Make sure it includes Google Apps too.
Colchiro said:
Install nightly #150, you can download it from Rom Manager. Make sure it includes Google Apps too.
Click to expand...
Click to collapse
If all the nightlies are pretty much stable, why not just tell him to install the latest nightly?
I think it's a toss up. The old stable builds aren't exactly perfect but I also don't think that the. 32 kernel is perfect yet either. We are still a ways away from a really polished CM7 for NC, I think. The recent builds are faster though.
I was very happy with Nightly 134 but changed to a later nightlies and had various problems. Luckily found a source that carried 134, reinstalled it and have been once again extremely satisfied.
Thank you everyone for the replys. I've been very hesitant to change what works since I use my nook and BT keyboard for work, business trips. I've looked but, can't seem to find - how do I clear the "Cache and Dalvik Cache? Going to try a nightly soon and hope my data is retained. I've used Titanium backup just in case.
Thanks
Just test out different builds. For me, I'm still running the RC1 from the tutorial a while back in the general section. I haven't had any problems besides the occasional problem with not waking up once every 5 days or so?
The best is to just get it the way you want it, and stop messing with it. Use it.
Based on this thread, I went from the last stable....to the newest nightly...(157 at the time)....all is well BUT, my Hulu + app now says the device is no longer supported..I've uninstalled and reinstalled from a backup, but ....nada....any ideas? (sorry for hijack)
Yoke
Edit: Update: I went backwards downgrading to 7.0.3, still had the 'device not supported' on hulu plus, so I started over from scratch, reformatted my SD card and reinstalled the latest nightly, restored apps from titanium backup and everything works fine...something must just have gotten corrupt. Hulu plus really does work nice in the nook color. So does netflix.
Yoke

Please unpin this thread.

UPDATE: 7.1 "stable" is OK but personally I prefer nightlies.
They are not stable! In fact RC1 boot loops! Please flash the latest nightly and google apps going forward!
Nightlies available here:
http://download.cyanogenmod.com/?type=nightly&device=speedy
Change log and link to nightlies here as well:
http://cm-nightlies.appspot.com/?device=speedy
Gapps here:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip
1) Copy zips to sd card
2) Backup with ti backup
3) Flash latest clockwork recovery through rom manager
4) Reboot into clockwork recover and run backup from clockwork recovery (aka nandroid)
5) mount usb storage in clockwork recovery and copy ti backups and clockwork recovery backup to your computer. Also copy any other important files on the sdcard (Especially pictures in the DCIM folder).
6) Copy nightly and gapps zips file to phone's sdcard
7) Wipe cache, wipe dalvik cache (under advanced), wipe battery stats
8) Install zips from sd card in this order:
a) CM_Speedyxxx.zip
b) googleapps 828-signed.zip
c) newtalk.zip
9) Reboot phone and wait 10 minutes phone should be in cm7 and working.
10) verify you can open market.
11) If you have problems try starting back at step 7 in clockwork and wipe data/factory reset
Questions/problems should be posted here:
http://forum.xda-developers.com/showthread.php?t=1001578
Optimal settings for CM7 on Sprint here (work in progress):
http://forum.xda-developers.com/showthread.php?t=1262313
These builds may be marked as Rc1 and stable but they are way old and NOT stable.
Before you ask, as of right now the nightlies are the most stable version of CM7 being release right now.
bump.
Please sticky this.
I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.
linuxman008 said:
I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.
Click to expand...
Click to collapse
Pointless. Just like flashing RC1.
VICODAN said:
Pointless. Just like flashing RC1.
Click to expand...
Click to collapse
Eh, I use mikshift anyway, but when It came out, it was the only rom I had on my sd card, and I needed to make a phone call, so I was forced to make it work. That method saved my life, or at least made it so I could get a ride home, other than that, I wouldn't use it.
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)
You don't have to pay for the nightlies, don't know if you are aware of the mirror for the nightlies, but no pay there. Only have to pay if you want to download thru rom manager. Just thought i'd point thay out
Sent from my PG06100 using Tapatalk
linuxman008 said:
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)
Click to expand...
Click to collapse
perhaps you missed this thread
http://forum.xda-developers.com/showthread.php?t=1001578
....
cm7 never charges for anything - even with all the crazy amounts of bandwidth they use...
Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?
sdk234 said:
Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?
Click to expand...
Click to collapse
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
VICODAN said:
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
You're 100% sure CM7.1 has bugs? Have you used 7.1?
I'm using update-cm-7.1.0-Speedy-signed.zip, released 10/9, without issue. OC'd to 1.5 gHz, using ScaryKernel 3.
jesusice said:
You're 100% sure CM7.1 has bugs? Have you used 7.1?
Click to expand...
Click to collapse
Keyboard shortcuts.
Bug.
VICODAN said:
Keyboard shortcuts.
Bug.
Click to expand...
Click to collapse
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.
jesusice said:
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.
Click to expand...
Click to collapse
You remember that bug when you opened the keyboard and pressed e and it opened email? The one that was only fixable on a reboot?
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".
VICODAN said:
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
VICODAN said:
You remember that bug when you opened
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".
Click to expand...
Click to collapse
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.
jesusice said:
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.
Click to expand...
Click to collapse
Changed the thread title, updated OP.
VICODAN said:
Changed the thread title, updated OP.
Click to expand...
Click to collapse
Works for me
The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.
Philpot85 said:
The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.
Click to expand...
Click to collapse
You could always try a nightly?
Why is the latest 7.1.0 stable for Speedy not posted on Cyanogen Mirror Network? I grabbed it elsewhere not long after it came out, but seems weird that it still does not show up there.

Official MIUI V5 for ME860 and MB860

Hello XDA,
(I'm posting this link here because I don't have enough posts to reply to the [ROM] MIUI v5 3.7.19 English thread.)
I was browsing the English MIUI website today and found that the Motorola Atrix 4G was listed as a supported device! :victory:
Official ROM package: http://en.miui.com/download-48.html
Kernel update package: https://www.dropbox.com/sh/s1am14hv1463bse/kcTzU7sneq or do it yourself instructions: http://forum.xda-developers.com/showpost.php?p=50270128&postcount=35
Basic soft keyboard: http://storage.evozi.com/apk/dl/13/...ard.apk?h=2w9QQkC1civRGTlZnZ_1kw&t=1393030263 (you'll need this, or another soft keyboard APK of your choice, because this ROM does not come with a soft keyboard!)
Google Apps package: http://forum.xda-developers.com/showthread.php?t=2482592 (search for "gapps core" on that page)
It's meant for the international version (ME860) but I think it should work it works on the US version (MB860) just fine.
Cheers.
sunaku said:
Hello XDA,
(I'm posting this link here because I don't have enough posts to reply to the [ROM] MIUI v5 3.7.19 English thread.)
I was browsing the English MIUI website today and found that the Motorola Atrix 4G was listed as a supported device! :victory:
Here is the link: http://en.miui.com/download-48.html
It's meant for the international version (ME860) but I think it should work on the US version (MB860) just fine.
Cheers.
Click to expand...
Click to collapse
I'll definitely try this one out. I love MIUI.
interesting... will have to give it a try and see what works and doesn't
prince_of_darkness666 said:
interesting... will have to give it a try and see what works and doesn't
Click to expand...
Click to collapse
Most of it seems to work, camera works, 1080P works on it, not sure about the Flash. Here is the status pages.
There is also an update on the updates page to 4.1.10 but I am not on WiFi. But all seems to work so far for me, I just can't figure out how to get the play store to work.
Also, it looks like it's actually for the MB not the ME.
Just a quick question since I'm a little lost. Miui is actually based on Android like CM right? So wouldn't it have the same bugs as cm 10.1? Like flash not working perfectly and stuff like that?
Sent from my MB860 using XDA Premium 4 mobile app
prince_of_darkness666 said:
Just a quick question since I'm a little lost. Miui is actually based on Android like CM right? So wouldn't it have the same bugs as cm 10.1? Like flash not working perfectly and stuff like that?
Sent from my MB860 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My Flash seems to not work, unless you auto focus, it won't trigger on it's own.
Edit, Correction, my horrible explanation of this, if Focus is set to auto in settings, it will Flash with Automatic Flash when it needs it. the Flash Seems to be extremely strong though.
Downloading now
will post results :laugh::good:
Hi guys everything apparently works fine however I am unable to install gapps so I can't actually test apps because of no playstore
restarts
i installed it and my phone started to restart every time i turn it on, i have the atrix 4g from at&t (MB860)
works but...
this rom is a hit and miss restarts a minute or so whenever I go in settings. random reboots. would not recommend for daily use. tested on at&t atrix 4g. kernel version 3.1.10 dec 11.
jammin20 said:
this rom is a hit and miss restarts a minute or so whenever I go in settings. random reboots. would not recommend for daily use. tested on at&t atrix 4g. kernel version 3.1.10 dec 11.
Click to expand...
Click to collapse
hi i never had any random reboots at all it was only the gapps problem
Taking a quick look at the source code of the kernel I noticed that the gpu is overclocked at 600mhz, could that be the cause of the reboots? I haven't got any reboot yet and I'm not a kernel expert so I can't assure that...
You can find the source code of the kernel here: https://github.com/shminer/android_kernel_motorola_olympus-jz
Reiki21 said:
Taking a quick look at the source code of the kernel I noticed that the gpu is overclocked at 600mhz, could that be the cause of the reboots? I haven't got any reboot yet and I'm not a kernel expert so I can't assure that...
You can find the source code of the kernel here: https://github.com/shminer/android_kernel_motorola_olympus-jz
Click to expand...
Click to collapse
Nope, GPU is at 300Mhz.
I see, my bad. Thought it was by looking at tegra2_clocks.c and tegra2_dvfs.c :|
A bit offtopic but what application are you using to see the gpu frequency?
Reiki21 said:
I see, my bad. Thought it was by looking at tegra2_clocks.c and tegra2_dvfs.c :|
A bit offtopic but what application are you using to see the gpu frequency?
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=2600452
I tried the 4.1.24 release of this ROM (filename: miui_me860_santajin_4.1.24_2d6ed01966_4.2.zip) and it flashes correctly using ClockworkMod.
However, during first boot (after it optimizes 122 Android apps) it repeatedly shows the MIUI logo and pulses the LED with a red color.
Is this what is known as a "boot loop"?
Red light pulse usually means low battery. Try turning the phone off and connecting the wall charger for a few hours and then wipe and flash again
Sent from my MB860 using XDA Premium 4 mobile app
prince_of_darkness666 said:
Red light pulse usually means low battery. Try turning the phone off and connecting the wall charger for a few hours and then wipe and flash again
Click to expand...
Click to collapse
Thanks! I tried your suggestion and the red LED does not pulse anymore. :good:
But it still gets stuck in the boot loop after "optimizing" 122 Android apps.
Update: I did "reset factory user data" in CWM and now I get past the boot loop! :highfive:
Glad to hear you got it working
Sent from my MB860 using XDA Premium 4 mobile app
Now that MIUI was working, the next thing I needed was Google apps --- particularly the Play Store so I could install more apps.
I tried gapps packages from MIUI v5 ROM for Atrix 4G and epinter's CM 10.1 but they both had problems, such as the Play Store would force close.
Finally, I tried the gapps package from MIUI for Atrix HD (yeah, I know, it's a different phone) and it worked! :victory:

CyanogenMod 11.0 Stable Released - what is working, what is not?

They just released CyanogenMod 11.0 M6. However it really is the "Stable" C11.0 since they stopped calling "Stable" Releases "Stable". Now there are just the Milestone Releases every 2-4 weeks.
Read all about it: http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
Here you can download the newest Stable (a.k.a. M6): http://download.cyanogenmod.org/?type=snapshot&device=ovation
Please post in this thread what works and what does not.
Cheers,
sb
I'm running the M4 right now.
Just install M6 via cwm recovery? Or do I need to do anything specific?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
---------- Post added at 08:24 AM ---------- Previous post was at 08:15 AM ----------
Also is ART working in this?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
Yes and yes.
Installed CM11 M6
I just installed the M6. Everything was running great until I had to plug in the charger. Now I am also getting the screen flicker. I did not clear the caches and I am using ART. As for ART I have not noticed that it is any faster than dalvik. I will probably switch back to test.
extrem0 said:
Yes and yes.
Click to expand...
Click to collapse
Yes and yes what? Please more details?!
Automan4966 said:
I just installed the M6. Everything was running great until I had to plug in the charger. Now I am also getting the screen flicker. I did not clear the caches and I am using ART. As for ART I have not noticed that it is any faster than dalvik. I will probably switch back to test.
Click to expand...
Click to collapse
Which method did you use for flashing? Link please
CM11 M6
sirbender42 said:
Which method did you use for flashing? Link please
Click to expand...
Click to collapse
I had a working CM10.2 so I downloaded the cwm-recovery-ovation-6.zip from the first post in the EMMC CM11 Install - updated 1/18 thread in the developers forum to my Nooks download folder. Then I downloaded the M6 snapshot from the get ovation builds link on the same page to my downloads folder. Finally I got the latest Google apps signed zip. All 3 downloaded to my Nook downloads folder. I then booted the Nook with a cwm that I had from installing 10.2 and flashed the newer cwm-recovery-ovation-6.zip to my internal emmc memory. Rebooted into the new recovery and flashed the cm11 m6 to internal emmc. Then flashed the google apps rebooted from recovery to cm11.
EMMC C11 Install - updated 1/18 thread http://forum.xda-developers.com/showthread.php?t=2600572
Latest Google apps http://www.google.com/url?sa=t&rct=...T134JI&usg=AFQjCNF5-cVMwChR1F7kICnKoFUjZ83OWg
I followed the For upgrades from CM10.x basic instructions on that page.
I find that the M builds aren't all that stable, even though they are considered to be. I haven't tried on a Nook yet, but on the Galaxy Nexus, the latest M6 constantly freezes my default launcher (Trebuchet) and I'm not the only one with this problem either (there are more similar cases on the CyanogenMod forum.)
HiddenG said:
I find that the M builds aren't all that stable, even though they are considered to be. I haven't tried on a Nook yet, but on the Galaxy Nexus, the latest M6 constantly freezes my default launcher (Trebuchet) and I'm not the only one with this problem either (there are more similar cases on the CyanogenMod forum.)
Click to expand...
Click to collapse
Well, the Nook HD+ has a fairly reproducible bug. About 30% of the time I swipe down the notification bar it crashes the currently running app and freezes the screen (black screen). After about 10 sec. you are back on the homescreen.
Strange that this wasn't catched in the most basic stability tests.
This bug even appears without pulling down the notification area. Sometimes the screen just turns black and freezes for 10 sec. After that you are back on the home screen. Very annoying. Luckily this doesn't happen very often. Unluckily it is very difficult to reproduce...and thus to fix I assume.
Alternative?
sirbender42 said:
Well, the Nook HD+ has a fairly reproducible bug. About 30% of the time I swipe down the notification bar it crashes the currently running app and freezes the screen (black screen). After about 10 sec. you are back on the homescreen.
This bug even appears without pulling down the notification area. Sometimes the screen just turns black and freezes for 10 sec. After that you are back on the home screen..
Click to expand...
Click to collapse
I've got the bug too...
Is there any KitKat ROM for the Nook HD+ that's stable? and does not have these "hiccups"? I'm getting no touch sensitivity during these lock screen resets, and have to restart via the physical button.
Well I have using the M4 build, and apart from a some rare crashes, it has been rock solid.
I think I will stick with for now, and not risk getting the bugs that you guys are reporting in M6. Also, I have it set up just right for my needs and would hate to start from scratch if I install to M6.
Palmahnic said:
I've got the bug too...
Is there any KitKat ROM for the Nook HD+ that's stable? and does not have these "hiccups"? I'm getting no touch sensitivity during these lock screen resets, and have to restart via the physical button.
Click to expand...
Click to collapse
Strange. I can always use the tablet after the hiccup just as before.
I would suggest you install the latest nightly. Since the bug is so obvious, they probably have already fixed it.
sirbender42 said:
Strange. I can always use the tablet after the hiccup just as before.
I would suggest you install the latest nightly. Since the bug is so obvious, they probably have already fixed it.
Click to expand...
Click to collapse
Not yet
Darrian said:
Not yet
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/63867/
In the next nightly this will be fixed (assuming this is the bug we have).
Update: Here is the Ovation Nightly Changelog: http://www.cmxlog.com/11/ovation
A couple of Cyanogenmod bug reports related to this issue have new comments saying that the problem is no longer happening.
https://jira.cyanogenmod.org/browse/CYAN-4047
https://jira.cyanogenmod.org/browse/CYAN-4091
I haven't tested it yet.
Hey guys, why do you think there are no nightlies for ovation anymore?
lerkin said:
Hey guys, why do you think there are no nightlies for ovation anymore?
Click to expand...
Click to collapse
The answer is in the CM11 thread. One of the users there reported there was some kind of glitch in the building process.
Sent from my BN NookHD+ using XDA Premium HD app
I put M6 on my HD for a while. I really missed all the Trebuchet tweaks that are available with 10.1 and 10.2 so I went back to 10.2.1 for now.
Sent from my BN Nook HD using XDA Free mobile app

Categories

Resources