Database Users

New CM9 Nightly Builds for TF101

Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.

So who wants to be the Guinea pig? I'm already running that KANG that was posted up earlier this weekend. I may try it after I charge up.

yea...guinea pig here....goes through boot animation and then system ui and trebuchet (the launcher) fc...i would say stay away until some official announcement is made

Yeah. It doesn't even boot up probably. :-(... going back to stock
Sent from my Galaxy Nexus using XDA App

You have to start somewhere.
Now at least we have an official CM9 branch, which means someone is working on it

brzgw said:
Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.
Click to expand...
Click to collapse
ehm where from?
Edit: http://download.cyanogenmod.com/?device=tf101
Found IT ^_^

I got launcher force closes when i had an overclocked kernel with a stock rom. Gonna check this out a little later.
Sent from my Transformer TF101 using Tapatalk

I'm surprised that this news seems to be not generating much buzz here. Not knocking any of the other devs, because most of them do amazing work, but CM is the bee's knees. When those nightlies get semi-mature, I'll be running them and never look back. They've never done me wrong before. Any device I've ever had that was supported, was the best ROM available for my needs. YMMV, of course.

I think when its own thread is created youll see the buzz, cm rocks lol
Sent from my R800i using xda premium

I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet

shadrach47 said:
I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet
Click to expand...
Click to collapse
Yep, same here, even with wipe dalvik and fix permissions, FC´s :S
Let us wait for a new update....

Alas, I ran across this on get.cm also. Got excited and then had the FC issues like everyone else. At least it is a step in the right direction.

Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S

Was just about to try flashing it until I saw how many people were unsuccessful. Oh well, guess I'll wait until an official release.

ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.

shadrach47 said:
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.
Click to expand...
Click to collapse
Ok got it to work again, had to use Super Wipe Lite from http://forum.xda-developers.com/showthread.php?t=1245892
after running the script flashed latest revolver and got wifi backup....

Same here, will try your suggestion below.
Edit: Had to run the wipe zip, reflash and boot into current rom and the restore a backup to get it working again. PITA But it works.
ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse

CM rocks

lollazzo said:
CM rocks
Click to expand...
Click to collapse
i would like to see MIUI V4 on tab, as it will be easier to port than 2.x was ^_^

New official CM9 nightly on get.cm. It boots!!! Gonna test it and report back in a bit.
EDIT1: Wifi works and was able to log into my Google account. Currently restoring my Titanium Backup and will test a bit more after that. Also, camera makes the tablet reboot on first launch, but works after that. Odd. More info to come.
EDIT2: Face unlock is there, but doesn't recognize my face, so I can't test it out. It couldn't recognize my face on my Nexus S 4G either. Maybe my face is just derped up. Anyway, there is nothing that I could tell that is broken. Even the MicroSD mounted with no issue. I don't have a keyboard dock to test it out, otherwise I would. Games and videos both work fine.

[Q] Re: "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]"

Regarding the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]" at
http://forum.xda-developers.com/showthread.php?t=1448186
The link to the downloads that the primary post refers to - http://techerrata.com/browse/nook/racks - hosts many files.
I am getting a new Nook Color and would like to know if http://techerrata.com/file/nook/racks/Mirage_CM7_ICS_CM9_DualbootSD.img.zip includes the latest updates; if not, which update files to download - and are they cumulative, or do I have to install each one in succession?
I searched for this info elsewhere and came up with nothing. Many thanks to anyone who would care to help.

Looks like .img is dated 3/04, so I'd do img and only add the latest CM7 and ICS, or Miui. The updates must be added to the "sdcard" partition of the sdhc card.
Smiley

Thanks - that does help. I'm still a little fuzzy, though, on whether I should download both OpenGL and non-OpenGL, both MIUI ICS and MIUI GB, and if I really do have to flash gapps after the rom.

Not sure about the others but the OpenGL and nonOpen Gl is an either or choice. The non seems to be the more stable.

mycenae said:
Thanks - that does help. I'm still a little fuzzy, though, on whether I should download both OpenGL and non-OpenGL, both MIUI ICS and MIUI GB, and if I really do have to flash gapps after the rom.
Click to expand...
Click to collapse
Either MIUI replaces the Mirage 7.2 primary boot. The secondary boot can be either OpenGL or non-OpenGL. You have to reflash gapps everytime you update the ROMs.

shumash said:
Either MIUI replaces the Mirage 7.2 primary boot. The secondary boot can be either OpenGL or non-OpenGL. You have to reflash gapps everytime you update the ROMs.
Click to expand...
Click to collapse
Clarity is golden and scintillating. Thanks to you all. Now I've got to decide which ROMs are best for me. I see MIUI has a guest mode. Is something like that available in Mirage?

Read the OP in RACKS thread
The files to setup the CM7/CM9 SD card need to be modified so if you download eyeballer or samians updated you need to follow the directions here to have them work. I've had good luck with the non open GL builds the open GL builds would freeze up once or twice a day.

wmuflyer said:
The files to setup the CM7/CM9 SD card need to be modified so if you download eyeballer or samians updated you need to follow the directions here to have them work. I've had good luck with the non open GL builds the open GL builds would freeze up once or twice a day.
Click to expand...
Click to collapse
I've been using the openGL eyeballer builds since I got my NC about a month ago. Issues are no worse than any other custom ROM I've ever used. DL goomanager from the market and you can update to the nightlies every day (without any fuss). It's a bit slow, but considering that this thing was $90 (my cost) and 800mhz, I'm not complaining. I mostly just use it for books, email, chat, light games, and web browsing.

I am running the Dualboot Mirage CM7 / ICS CM9 Image. It was working well, but after the battery fell below operational threshold the nook will not charge or boot at all, it just displays the charge icon whenever I try to start it.
Right now I cannot use the nook at all.
Your call, you may not have any issues, but as awesome as the build is, if you have the same problem I do your nook will become useless.
Sorry I can't be of more help.
Larry

lrome53 said:
I am running the Dualboot Mirage CM7 / ICS CM9 Image. It was working well, but after the battery fell below operational threshold the nook will not charge or boot at all, it just displays the charge icon whenever I try to start it.
Right now I cannot use the nook at all.
Your call, you may not have any issues, but as awesome as the build is, if you have the same problem I do your nook will become useless.
Sorry I can't be of more help.
Larry
Click to expand...
Click to collapse
This is the third thread you have asked the same question. DON'T DO THAT!
You've posted the same question on so many threads, you don't even know you have been answered. You have three responses on this thread. Two of them asking you for more information that you have not responded to.
http://forum.xda-developers.com/showthread.php?p=25507975

Which ROM for me?

I have an old Nook Color sitting on the shelf and decided it is time to do something with it. I want to know which ROM is the most stable with all hardware working (CM 10, 10.1, ASOP, other?). I plan to use it for games, web browsing, and maybe watching videos. Any suggestions would be appreciated.
I do plan to run from an SD card if that makes a difference.

jbass350z said:
I have an old Nook Color sitting on the shelf and decided it is time to do something with it. I want to know which ROM is the most stable with all hardware working (CM 10, 10.1, ASOP, other?). I plan to use it for games, web browsing, and maybe watching videos. Any suggestions would be appreciated.
Click to expand...
Click to collapse
If you want stability the most, the MiRaGe CM7 is your best bet. If you need/want a more recent Android, pick the stable CM10 or mateorod's AOSP (which are quite responsive in the Nook even being Android 4.2 ).
I do plan to run from an SD card if that makes a difference.
Click to expand...
Click to collapse
Should not be a problem to run any of the above from a SD card.

aperezdc said:
If you want stability the most, the MiRaGe CM7 is your best bet. If you need/want a more recent Android, pick the stable CM10 or mateorod's AOSP (which are quite responsive in the Nook even being Android 4.2 ).
Should not be a problem to run any of the above from a SD card.
Click to expand...
Click to collapse
Same question as op so I'll tag along here. So why would I want mirage cm7 over cm10? What exactly doesn't work right/isn't stable in cm10?

lexluthor said:
Same question as op so I'll tag along here. So why would I want mirage cm7 over cm10? What exactly doesn't work right/isn't stable in cm10?
Click to expand...
Click to collapse
CM7 is just fast and stable, period. CM10 can be laggy and unstable at times.
Sent from my Galaxy Tab 2 using XDA Premium

I also recommend Mirage ROM. I'm running it and it's crazy fast, especially overclocked to 1.2GHz, animations disabled. I can watch HD YouTube videos with no lagg at all.

I am trying out Mirage CM7 off an SD card and it seems like it will be ideal.
Should I try to install it to internal memory or is there really no point? Are there up to date instructions for installing to internal memory?
If I do decide to just keeping running Mirage CM7 off the SD card, can I still use the internal memory to store/play movies while running Mirage CM7? It appears in estrongs, so I wouldn't see why that wouldn't work.
Is overclocking to 1.2 required to watch youtube in HD?

lexluthor said:
I am trying out Mirage CM7 off an SD card and it seems like it will be ideal.
Should I try to install it to internal memory or is there really no point? Are there up to date instructions for installing to internal memory?
If I do decide to just keeping running Mirage CM7 off the SD card, can I still use the internal memory to store/play movies while running Mirage CM7? It appears in estrongs, so I wouldn't see why that wouldn't work.
Is overclocking to 1.2 required to watch youtube in HD?
Click to expand...
Click to collapse
Yeah I'd say it's worth it to install to internal SD. Overclocking to 1.2GHz helps a lot with video playback. If you're at stock 800MHz, it lags occasionally. The TI OMAP 3621 has a rated frequency of 1GHz, so if you're worried, just put it to 1GHz clock speed max.

Which root method is the easiest? Thanks.

GAPY427 said:
Which root method is the easiest? Thanks.
Click to expand...
Click to collapse
If you are using a non-stock rock (CM, PA, AOSP, etc), then you don't need to do anything — those come with root enabled by default, and Superuser preinstalled.

sagirfahmid3 said:
Yeah I'd say it's worth it to install to internal SD. Overclocking to 1.2GHz helps a lot with video playback. If you're at stock 800MHz, it lags occasionally. The TI OMAP 3621 has a rated frequency of 1GHz, so if you're worried, just put it to 1GHz clock speed max.
Click to expand...
Click to collapse
I found the instructions for internal install. Went perfectly. Seems like no reason not to do that. I guess if I have 8 failed boots in a row, my CM7 install will get wiped and stock will come back? I guess that's not too likely.
Mirage CM7 had an 1100MHz and 1200MHz choice in the settings, so I just set it at 1100MHz to be a little safe.
Seems to be working great.

aperezdc said:
If you are using a non-stock rock (CM, PA, AOSP, etc), then you don't need to do anything — those come with root enabled by default, and Superuser preinstalled.
Click to expand...
Click to collapse
I brought my Nook back to factory stock, i.e., I have no root access. Are you saying you can download the ROM on the external SD and it will work?

lexluthor said:
I found the instructions for internal install. Went perfectly. Seems like no reason not to do that. I guess if I have 8 failed boots in a row, my CM7 install will get wiped and stock will come back? I guess that's not too likely.
Mirage CM7 had an 1100MHz and 1200MHz choice in the settings, so I just set it at 1100MHz to be a little safe.
Seems to be working great.
Click to expand...
Click to collapse
Only if you left stock recovery on internal memory. If you replaced it with CWM or TWRP, the 8 failed boots does not work.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
Only if you left stock recovery on internal memory. If you replaced it with CWM or TWRP, the 8 failed boots does not work.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Cool, then I'm good. I flashed CWM.
Should have talked my wife into letting me do this earlier.

lexluthor said:
I found the instructions for internal install. Went perfectly. Seems like no reason not to do that. I guess if I have 8 failed boots in a row, my CM7 install will get wiped and stock will come back? I guess that's not too likely.
Mirage CM7 had an 1100MHz and 1200MHz choice in the settings, so I just set it at 1100MHz to be a little safe.
Seems to be working great.
Click to expand...
Click to collapse
Could you please point me to the internal install instructions? Thanks.

GAPY427 said:
Could you please point me to the internal install instructions? Thanks.
Click to expand...
Click to collapse
I used this.
http://forum.xda-developers.com/showthread.php?t=1030227
It was really simple. I did one extra step of installing the Mirage CM7 kernel right after the ROM (added step 11.1a). I used the CWM method.
Let me know if you get stuck.

GAPY427 said:
I brought my Nook back to factory stock, i.e., I have no root access. Are you saying you can download the ROM on the external SD and it will work?
Click to expand...
Click to collapse
You can get root in three different ways,
If you are using the stock ROM, and what you want to do is rooting it, you can follow the instructions from this page in CyanogenMod wiki
If you want to keep the stock ROM in the internal memory, but want to install another ROM (for example, CyanogenMod), you can follow the instructions in this thread. You won't have root when booting the stock ROM in the internal memory, but you will when booting CM from the SD card. (Of course you can also root the stock ROM using the instructions from the previous item, and both ROMs would be rooted.)
If you do not want to keep the stock ROM, you can install another ROM in the internal memory, for example following this guide for CM7/CM10. (There is also instructions for installing CM in the wiki page I linked above).

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

[Q] When will we get L?

How soon can we expect to get "L" ? Will it be CM12?
I wonder what the cute name is, how about Lemon drop?

I can guarantee you it will be no earlier than when ever cm12(or what ever the cyanogenmod team calls it) comes out.
But also, dont forget that the nook color is a 4 year old device, pretty old by tablet and android standards. Im still surprised that they got cm 11 working okay-ish on it(kudos to the development team, amazingly you are still keeping this old tablet alive). And also dont forget that android L completely ditched the dalvik runtime, leaving only the ART runtime for all devices. The last time I checked the development page for the nook, didnt they have issues with ART, something ram related maybe? They are working with a single core 512 Mb s of ram tablet, even cheap tablets nowadays come with a dual core cpu, and at the minimum 512 Mb(most likely 1 Gb at this point) of ram. The nook may be able to run android L, but it could possibly get too laggy for any real use, unless if the development team can get it stable again at higher cpu speeds.

BrownDog.c said:
How soon can we expect to get "L" ? Will it be CM12?
I wonder what the cute name is, how about Lemon drop?
Click to expand...
Click to collapse
At least way out from http://www.cyanogenmod.org/blog/the-l-is-for-later

dombeef said:
I can guarantee you it will be no earlier than when ever cm12(or what ever the cyanogenmod team calls it) comes out.
But also, dont forget that the nook color is a 4 year old device, pretty old by tablet and android standards. Im still surprised that they got cm 11 working okay-ish on it(kudos to the development team, amazingly you are still keeping this old tablet alive). And also dont forget that android L completely ditched the dalvik runtime, leaving only the ART runtime for all devices. The last time I checked the development page for the nook, didnt they have issues with ART, something ram related maybe? They are working with a single core 512 Mb s of ram tablet, even cheap tablets nowadays come with a dual core cpu, and at the minimum 512 Mb(most likely 1 Gb at this point) of ram. The nook may be able to run android L, but it could possibly get too laggy for any real use, unless if the development team can get it stable again at higher cpu speeds.
Click to expand...
Click to collapse
Are you saying that support for NC is about to end? I had hoped that L would be
tuned for small memory devices like by beloved NC.
What is the best version of CM for the NC? I mostly use it for G news and G mail.

Mirage cm 7.2
Sent from my Samsung Galaxy Rush with Tapatalk.
Devices: Nook Color, Dell XPS 18, Galaxy Rush (All modded)

Mirage
crazynapkinman said:
Mirage cm 7.2
Sent from my Samsung Galaxy Rush with Tapatalk.
Devices: Nook Color, Dell XPS 18, Galaxy Rush (All modded)
Click to expand...
Click to collapse
I gave the MiRaGe image a try but it hangs after a reboot.
I'm currenty at CM11, do I need to downgrade my CWM too?
Or maybe I need to do a full wipe and then try? Pretty annoying... hrumph.

BrownDog.c said:
I gave the MiRaGe image a try but it hangs after a reboot.
I'm currenty at CM11, do I need to downgrade my CWM too?
Or maybe I need to do a full wipe and then try? Pretty annoying... hrumph.
Click to expand...
Click to collapse
If you have CWM v6045 or newer you must downgrade to an older version to install a CM zip older than CM11. V6045 or newer only works for CM11.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
If you have CWM v6045 or newer you must downgrade to an older version to install a CM zip older than CM11. V6045 or newer only works for CM11.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I am using CWM V6.0.4.8. I don't think I want to down grade CWM just
to try out MiRaGe. Could I boot MiRaGe from an SD card? Or would
CWM still be a problem?

BrownDog.c said:
I am using CWM V6.0.4.8. I don't think I want to down grade CWM just
to try out MiRaGe. Could I boot MiRaGe from an SD card? Or would
CWM still be a problem?
Click to expand...
Click to collapse
Yes, you can run mirage from SD or you can also make an older CWM on SD to install the mirage to emmc without touching the internal newer CWM if you desire. Mirage runs fine if installed internally with the older CWM on SD. That way it is there if you want to return to CM11.
Sent from my BN NookHD+ using XDA Premium HD app

> Mirage runs fine if installed internally with the older CWM on SD.
Cool, that is what I want to do. Is there a simple how to make a bootable
SD document someplace?
Thanks for the help!

BrownDog.c said:
> Mirage runs fine if installed internally with the older CWM on SD.
Cool, that is what I want to do. Is there a simple how to make a bootable
SD document someplace?
Thanks for the help!
Click to expand...
Click to collapse
Follow this guide. But get the zip from the mirage thread.
http://forum.xda-developers.com/showthread.php?t=1030227
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Follow this guide. But get the zip from the mirage thread.
http://forum.xda-developers.com/showthread.php?t=1030227
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
That web page says:
"If you want to run CM7/10 from the sdcard.. you're in the wrong place!"

BrownDog.c said:
That web page says:
"If you want to run CM7/10 from the sdcard.. you're in the wrong place!"
Click to expand...
Click to collapse
I thought you meant a bootable CWM SD. If you want an SD that will boot the mirage 7, follow my guide here:
http://forum.xda-developers.com/showthread.php?t=1941858
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
I thought you meant a bootable CWM SD. If you want an SD that will boot the mirage 7, follow my guide here:
http://forum.xda-developers.com/showthread.php?t=1941858
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! That worked well -- once I saw the bit about the zip file needing to
start with "cm"