Database Develop

[GUIDE] Nook Color Installation Guide for CM7/CM9/CM10/CM10.1/CM10.2/CM11 on SD

Now that CM10 (JellyBean) is in Alpha release (and now Beta and nightlies) for the Nook Color (see post here), I was requested to issue some up-to-date installation instructions to put it on SD.
These instructions are based on using Verygreen's original size-agnostic SD image and installer which is explained here. I have modified his image so that it works for both CM9 (ics) and CM10 (jb) and attached it below (generic-sdcard... etc). It also is still valid for CM7.
The CM10.1, CM10.2 and CM11 are official and on the CM site, get latest nightly here (you can get the CM7 ROMs at that site too). You can get the gapps zips here. CM10 needs gapps-jb-20121011 and CM10.1 needs gapps-jb-20130812 and CM10.2 needs gapps-jb-20130813 and CM11 needs gapps-kk and CM7 needs a gapps-gb version.
Installing a ROM the first time
Download the ROM, gapp and image files and temporarily store them on your PC. Unzip the image zip (generic-sdcard... attached below) and you should end up with a 300MB .img file that will be used to make the SD. Leave the other two files zipped.
EDIT: (2/18/15) - If you want to install the newer versions of CM11 with a newly burned SD you must start with the Snapshot version M11. There is something in the newer CM11 zips that causes the installation to not work. Once you have M11 working you can upgrade to the newer versions. See bowguy's post in this thread here: http://forum.xda-developers.com/showthread.php?p=56782698.
EDIT: (6/8/14) - Updated image to rev8c to fix a minor script error that prevented installation of CM11 post 5/15 and removed a couple of gapp apps that interfered with installing kitkat gapps. This version may be used on all versions of CM. If you already made a prior rev8 SD, just use the uRecRam rev8c rar to update the SD as described below.
EDIT: (12/10/13) - Updated image to rev8b to create a larger /system to accommodate the larger CM11 and kitkat gapps for 8 and 16GB SDs. If you are installing CM11 to an 8 or 16GB SD, I recommend you start fresh with this version so that a larger /system is created. If you are on a 32GB or larger SD, then the prior rev8a is ok. And CM11 cannot be run on a smaller than 8GB SD.
EDIT: (12/9/13) - Updated the image again to rev8a to fix a permissions issue when installing the KitKat gapps. If you already made a rev8 SD, just use the uRecRam rev8a rar to update the SD as described below.
EDIT: (12/6/13) - I just updated the image file to rev8 to make it compatible with CM11 and to make the boot partition 400MB instead of 300MB to accommodate the larger CM and gapps zips. And this version still works properly on all previous CM versions. But, if installing CM7, it is best to use rev7 or earlier.
EDIT: (8/28/13) - I just updated the image file to rev7 to make it compatible with CM10.2. This version still works properly on all previous CM versions. If you were having trouble with the installer not creating the partitions or installing ROMs because of a poor SD, rev7 also has the revised kernel that is more tolerant of poor SD cards and seems to install smoother than rev5 or earlier versions. Also as of the 4/14/13 version of CM10, this same fix is included in the ROM kernel to help it run better with poor cards. Big thanks to bytte and steven676 for providing this new kernel.
For those users that want to upgrade their existing SD without reburning with the new image, I have also attached an archive of the updated boot file needed to upgrade. Just extract the file (uRecRam) and copy it to your existing SD boot partition, replacing the file that is there. Then you can update your earlier CM10.1 installation with CM10.2. You must update the gapps too. You can also do the same for rev8a, rev8b and rev8c, but the boot partition will remain 300MB unless updating a rev8 SD.
In Windows use Win32diskimager or WinImage to burn the image file to your SD (Sandisk Class 4 is the recommended brand). Win32diskimager is free on the web and WinImage is shareware but can be used free to burn images to SD. Be sure to use an external card reader rather than any built in reader in your PC. The built in reader may work but many have found them to be problematic for burning bootable SDs. And it is best to run the programs in administrator mode. In WinImage use the "Restore Virtual Disk Image to physical drive" rather than "write disk". In Linux or OSX, use the "dd" command to burn the image to SD.
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). If you get an error message about access denied, it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
Once the SD is burned, temporarily remove the SD from the PC and then reinsert in your PC. Then copy the two other zip files (CM ROM zip and gapps zip) to the SD. Make sure the CM zip begins with cm- and the gapps zip begins the gapps- and both end in .zip. (Don't worry that the SD is now smaller than its original size. That is part of the process in making the SD usable as a bootable SD capable of running CM).
Take the SD out of the PC and insert it into your powered off Nook Color. Power on the Nook and the SD will take over. It will show a little penguin and a bunch of scrolling text. It will first partition the SD into those partitions necessary to run a ROM. Then it will install CM followed by installing gapps. It will then power down. Power it back up and it should boot to your new CM. Follow the on-screen instructions to set up the Google apps.
If you get stuck on any of the steps or you just want more information on installation, you can look at Taosaur's excellent blog on installing CM7 to SD. The principle is the same, just substitute CM9 or CM10 for CM7 in his blog and use the files from above. See his blog here.
Adding some tools
If you want to read some tips about how to make your SD install work a little better, look at my tips thread linked in my signature. In particular look at the tips in section B in my second post of that thread.
I recommend that all users add the Alternate CWM for SD as explained in section B5 of my tips thread referenced above. That allows you to clear the dalvik-cache or fix permissions if you need to after a ROM install. It also has the added benefit of allowing you to make a Nandroid backup of the installation. But heed the warning that you CANNOT flash ROMs to SD with it. You must use the verygreen script installer as explained in the next section. You can get the Alternate CWM for SD here and installation is very simple.
I also recommend that all users install my sdboot script from item B4 of my tips thread so they can use the CMUpdater, GooManager or CyanDelta to update their devices while the SD is still in their Nook as described later.
Click to expand...
Click to collapse
Updating to a new ROM
If you want to later flash an updated CM ROM or gapps zip, put the updated zip file(s) on the boot partition like you did originally and boot. But you need to be sure they are named properly or the installer script will not recognize them. They need to begin with cm-, update-, diiff_, or gapps and end in .zip. After the first tiny flash of the screen, hold the "n" button. The boot menu will come up and you can select the SD recovery and finish booting. The zip(s) will be automatically installed by the SD recovery (the script installer, a little penguin with scrolling text). Or, if you use sdboot as described later, you can just use the power off menu to select reboot and then choose recovery. It should boot automatically to SD recovery so the script installer can install the file you copied to sdboot.
Ordinarily if you are updating the same ROM (eg, CM10 over a CM10) you do not need to wipe anything. But sometimes if the ROM does not boot properly, you may want to clear dalvik-cache with the Alternate CWM for SD that I talked about earlier. If you are installing a different ROM (eg, CM10 over CM9 or CM7) you should either re-burn the SD or wipe system, data and cache with the Alternate CWM for SD. If you re-burn, the SD will be clean, but you will also lose all files in your SDCARD partition (including any backups that you may have put there).
Using CMUpdater, GooManager, or CyanDelta on SD installs
You can use these tools as long as you have your Nook set up properly. For most SD users there is no easy way to copy a zip from the sdcard partition to the boot partition while the card is still in the Nook. And if you take the card out to put it in your PC, you can access the boot partition but not the sdcard partition where the file is stored. The solution is to go to my tips thread linked in my signature and look at item B4. It tells you how to install a script that mounts the boot partition as 'sdboot' under your root directory. Just use a file manager to copy the file from SDCARD to /sdboot. Then use the power off menu to boot to recovery. The script installer will install it as long as it is named properly as described above.
CM has a new feature (CMUpdater) that makes it easy to download and install updated CM 10 ROMs for those users on emmc. Just go to settings, about tablet, CyanogenMod updates, and follow the prompts. But for SD users you need to be careful, as it may try update your emmc when you are wanting it to update the SD. It will boot to the SD recovery and do nothing, but the next time you manually boot to CWM or TWRP on emmc, it will install it on emmc. You can still use CMUpdater to download the zip, but when it finishes and asks if you want it installed, you have to choose cancel. The ROM zip is downloaded to /sdcard/cmupdater. You need to copy that file to your boot partition (sdboot) and boot to SD recovery and the script installer will install it.
With GooManager you download a small zip that only has the changed files in it and you flash that. And that works on SD installs as long as you use the script installer. Just copy the diff_ file to the boot partition (sdboot) and boot to SD recovery. With GooManager you can choose which directory you want to download to, so you can tell it to directly download to sdboot. No need to copy later. GooManager does not currently host the CM10 zips. But they do host the Paranoid Android zips.
With CyanDelta, you use an app installed from Play Store. That app reads, modifies and stores your current ROM zip on your SD for future use. Then, when an update is available, it downloads a small (about 5-10MB) delta file from their site and modifies and renames that stored zip so it has the changes in it. So what you flash is your complete previous ROM zip that has the changed files inserted into it, replacing the ones that were changed. You can use that modified ROM zip with the SD install. Just be sure to only download the delta and let the app modify the zip. Do not let it proceed with installation. The newly modified ROM zip will be in /sdcard/CyanDelta (with the new date). Copy that to the boot partition (sdboot) and boot to SD recovery. The only issue I see is, as part of their modifying they have obviously reduced the compression level of the zip and the normal 150MB zip becomes 250MB. That means you need that much space on your boot partition. If you used my new image file to make your SD in the first place, it should fit since I increased the boot partition size to 300MB.
-------
For questions or comments on the installation procedure comment on this thread. For comments or questions on the CM9/CM10 ROMs comment in the CM9/CM10 Discussion thread here or the CM10 General Discussion & Q&A thread here.
EDIT 1 and 2 removed

Thank you for the sdcard workaround. Worked perfectly.
Sent from my SCH-I510 using xda app-developers app

Thanks! (I was one of the 42)

ICS File Question
Hi.
I'm busy downloading the various files to make my SD card and I have a question. Are both ICS and JB gapps zip in one file or are they in different files? I found the gapp file but can't locate the ICS file and where is the image file found? I was able to download and am now using the CM 7. Not sure why I'm having this problem with the CM 10.
Thank you from a confused grandmother

Patty Ann said:
Hi.
I'm busy downloading the various files to make my SD card and I have a question. Are both ICS and JB gapps zip in one file or are they in different files? I found the gapp file but can't locate the ICS file and where is the image file found? I was able to download and am now using the CM 7. Not sure why I'm having this problem with the CM 10.
Thank you from a confused grandmother
Click to expand...
Click to collapse
Both gapp files are located at goo.im. They are separate files, one named gapps-ics-..., and one named gapps-jb-... . And the image file is the one attached to the first post in this thread. It begins with generic-sdcard-... .

leapinlar said:
... As a temporary workaround until I can modify the image file to correctly set the vold.fstab, users must manually set it. You must use root explorer or some other root file manager to manually edit the vold.fstab file. With root explorer go to /system/etc and look for that file. Using root explorer edit the file. Look for "sdcard1 auto" (without the quotes) and change to "sdcard1 4". Save the file and reboot. It should then properly see partition 4 on the SD as SDCARD.
Click to expand...
Click to collapse
This worked fine, thanks.(Didn't solve the rebooting into emmc issue, as I'd hoped it would, however.) I knew something was whacked when my brand new 32GB card was only showing a few hundred MB of /sdcard space, and the /boot files were showing up in the /sdcard folder....
But you might consider including a quick note for those of us morons who didn't think before making the edit, that any data we'd already acquired/downloaded would vanish in the process. Fortunately, it can be found in the /boot folder. Now if only I didn't have to reboot the desktop into Linux just to move it over....

tonestertm said:
This worked fine, thanks.(Didn't solve the rebooting into emmc issue, as I'd hoped it would, however.) I knew something was whacked when my brand new 32GB card was only showing a few hundred MB of /sdcard space, and the /boot files were showing up in the /sdcard folder....
But you might consider including a quick note for those of us morons who didn't think before making the edit, that any data we'd already acquired/downloaded would vanish in the process. Fortunately, it can be found in the /boot folder. Now if only I didn't have to reboot the desktop into Linux just to move it over....
Click to expand...
Click to collapse
You don't have to boot to Linux to look at the boot partition and sdcard at the same time. There are two ways to do it. First use my modified NookColorUMS app in my tips thread. It lets you mount both partitions using CM9 or CM10 mass storage option on your PC. Or use my sdboot unit.d script also listed in my tips thread. It lets you see the boot partition directly on the Nook.
As far as the rebooting to emmc issue. That has been a problem for a long time with SD installs (especially running CWM from SD and telling it to reboot). To get around it, don't say to reboot. Power off first, then power back on and it will boot to SD.

Thanks for the tips. I've actually been using SDboot since you very first posted it; for some reason I didn't realize that I was actually looking at /boot when exploring to there - just thought it was some sort of shortcut or something. Another learning experience - Yay! And I'd read about NookColorUMS in your thread a while back but just forgot about it. I think I'd better make a regular stop in your tips thread like, once a month, just to keep up and refreshed. Many, many useful things in there.
I wanted to go back and install a full rev 5 image and put CM10 on a different card, plus had some other data from yet another card that I wanted to migrate in, so I just ended up doing all that anyway, before I came back here and saw your suggestions. Thanks, anyway! Hopefully it will help someone else, now or in the future.
Don't want to drift too far, but Cyanoboot is not CWM, correct? I've never seen a reboot from sd to emmc in the last 15 months, except after nasty crashes. This was a first for me. Seems like it might just be a flag issue? I'm pretty sure I remember a setting (and a discussion of what file it was in) where you could actually choose your preferred "reboot to" location, but haven't found it in CM10 yet.

tonestertm said:
Don't want to drift too far, but Cyanoboot is not CWM, correct? I've never seen a reboot from sd to emmc in the last 15 months, except after nasty crashes. This was a first for me. Seems like it might just be a flag issue? I'm pretty sure I remember a setting (and a discussion of what file it was in) where you could actually choose your preferred "reboot to" location, but haven't found it in CM10 yet.
Click to expand...
Click to collapse
You are right, Cyanoboot is the bootloader and is different than CWM. Most of the time I have reboot issues to emmc is coming from an SD mounted CWM. For some reason when you tell it to reboot, the device thinks there is no SD installed (you can tell that by Cyanoboot showing E0 in the upper left corner, and when it does boot to the rom on emmc, there is no sdcard mounted.) It looks like for now CM10 has that same issue. You are also right CM7 and CM9 did not have that issue.
That flag you are talking about is in /rom and Cyanoboot looks for it when it loads. Look in the Cyanoboot thread to learn about it. But if the nook thinks there is no SD present, it cannot boot to it.

Installation problem
I have downloaded the generic-sd image and written to my 16gig sd card with win32imagewriter. I downloaded CM10 and the jb gapps files. When I try to copy the CM10 zip file to the card I get an error message saying I need 40mb more room.
What am I doing wrong?

Donn240 said:
I have downloaded the generic-sd image and written to my 16gig sd card with win32imagewriter. I downloaded CM10 and the jb gapps files. When I try to copy the CM10 zip file to the card I get an error message saying I need 40mb more room.
What am I doing wrong?
Click to expand...
Click to collapse
Are you sure you used my rev 5 of the generic SD image? By the symptoms it sounds like you used an older version.

Installation problem
Yes, I used the Rev5 file attached to the bottom of your OP.
leapinlar said:
Are you sure you used my rev 5 of the generic SD image? By the symptoms it sounds like you used an older version.
Click to expand...
Click to collapse

Donn240 said:
Yes, I used the Rev5 file attached to the bottom of your OP.
Click to expand...
Click to collapse
You may have had the old version on there before you burned it. You need to take the SD out of the PC once it is burned and reinsert so the PC knows it has the new version on it. I just modified my instructions above to indicate that should be done.

Thanks for your help. I deleted all the older files related to this from my PC and downloaded fresh files, re-burned the image, and copied the CM and app files to the SDcard. Everything seems to be working as it should.
Thanks for the great work!
leapinlar said:
You may have had the old version on there before you burned it. You need to take out of the PC and reinsert so the PC knows it has the new version on it.
Click to expand...
Click to collapse
---------- Post added at 03:49 PM ---------- Previous post was at 03:27 PM ----------
now it loads to the setup screen and gives me the message that setup has stopped.
QUOTE=Donn240;33137031]Thanks for your help. I deleted all the older files related to this from my PC and downloaded fresh files, re-burned the image, and copied the CM and app files to the SDcard. Everything seems to be working as it should.
Thanks for the great work![/QUOTE]

Donn240 said:
now it loads to the setup screen and gives me the message that setup has stopped.
Click to expand...
Click to collapse
You mean the Google app setup screen? It boots ok to CM10, just does not complete the setup? Not sure how to help you with that. Did you setup wifi as part of setup, or did you not get that far?
And you used the JB version of gapps? Should start with gapps-jb...

Used jb apps. It loaded CM10, gave a massage that google framework was not found, did not get to wifi setup.
leapinlar said:
You mean the Google app setup screen? It boots ok to CM10, just does not complete the setup? Not sure how to help you with that. Did you setup wifi as part of setup, or did you not get that far?
And you used the JB version of gapps? Should start with gapps-jb...
Click to expand...
Click to collapse

Donn240 said:
Used jb apps. It loaded CM10, gave a massage that google framework was not found, did not get to wifi setup.
Click to expand...
Click to collapse
The only thing I can think of is a bad download of the JB gapps and they only partly installed. Did the installer zip get removed from the boot partition?

Thanks for your patience in helping me. After all that, I deleted all the related files from my PC and downloaded fresh image, CM10 and apps files.
I wrote the image to the sdcard and copied the other two over. Lo and behold, everything worked perfectly.
Thanks again for your help.
Donn240 said:
Used jb apps. It loaded CM10, gave a massage that google framework was not found, did not get to wifi setup.
Click to expand...
Click to collapse

Awesome!
Hi, noob here.
Had a hard time figuring out the instructions at first, namely finding the correct image file. It took me several tries but I finally got the penguin!
Thanks a lot :good:

I am getting this windows message when trying to burn the image to my SD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried it on a clean boot of Windows with nothing running but WinImage.
I installed and run WinImage in administrator.
Can anyone help?
Thanks

[RECOVERY] TWRP 2.6.3.0 for gt-P311X

With the help of Dees_Troy, helicopter88, MrHyde03 and the various other guides & great folks out there, I compiled TWRP 2.6.3.0 for the gt-p3113. This is for the US-version wi-fi with the IR port, but I'm told it may also work for the wifi-only (3110) version as well.
Files are here for the time being: one .img for a straight dd within an adb shell and the other (.md5) is ODIN-flashable.
https://www.dropbox.com/sh/my09xxmhwo8bcy1/zT80nlWBOj?m
There's a recovery-flashable .zip file there as well (thanks webdroidmt!)
I've also included the stock recovery image from Samsung's 4.2.2 release if you would like to flash back for some reason.
Standard disclaimers apply: I'm not responsible if this bricks your device or causes harm in any way.
Other than that, enjoy, test and let me know your experience!
Changelog from TWRP:
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Old thread & discussion here:
http://forum.xda-developers.com/showthread.php?t=2168845

Re: TWRP 2.4.4.0 for gt-P3113
Thank you very much. I will test it. Right after nandroid.
Edit: internal SD appears blank when trying to install.
Sent from my GT-P3110 using xda app-developers app

Working great for me. Backed up and flashed with it. Not a single problem yet. :good:

Joe, good to see your thread in dev. I always use ext SD for both flashing zips, as well as backup/restore. However, just checked internal SD and as mentioned above, it comes up empty. It won't find any folders with zips or TWRP backups.
Aside from that and the clock continuously being 1 hour off for EST, it's working great for me. Have installed 4 or 5 different zips and have done 2 backups and restores.
Thanks,
Mike T

Glad you got it goin bud. Enjoy!

your internal SD card is located at /DATA/MEDIA within TWRP for the 3113. We talked about this in the other thread, but here's the bad part...If you WIPE DATA/FACTORY RESET it WIPES your internal card. So if you're a purely external SD guy your good to go but if you have any media data internally, say goodnight.

I use TWRP on other devices and they leave /data/media alone when doing a factory reset. TF101 and Galaxy Nexus.

It's located at /data/media for just about all android I believe, but it's never wiped with a wipe data/factory reset. Unless TWRP was not properly configured, you'll be alright.

who's brave enough to test it? I'm about 5 hours away from being able to myself but I switched back to CWR after reading that in the other thread. Problem is, you have to BU to computer because a nandroid wouldn't bring back the data if it in fact does get wiped. I only doubt this because TWRP does not locate the Touchpad or Skyrocket media data in /data/media. I just don't want to F up my daughter's TAB!

The build as it sits is certainly geared toward someone using their tablet with an external SD card. Having shot myself in the foot so many times in the past, I've just made a habit of backing stuff up there.
I've nuked encryption and gone back to stock and will be testing from that angle.

PS - not sure if it matters but I'm running CM10.1 nightlies. Oh and CMUPDATER doesn't work with this TWRP, it just boots to recovery instead of running the install script. I'm guessing until you can install this straight from GOO it might be a little undercooked.

That's an understatement....
I can't really figure out where the best location for internal storage would be on 10.1. The TWRP guys suggested /data/media, which is what it's currently set to, but that doesn't seem to be right. The fstab supplied on the CM git is not current with the times either.
I'll keep playing around. Any suggestions are welcome.

Joe, was just playing around with the TWRP v2.3.2.3 that forum member aidfarh compiled for P31xx and it allows installing zips and backup/restore from both internal and external SD card. Also, if you do a factory reset, it does not wipe the files on the internal SD card.
What I noticed, is that when performing the factory reset, it says it's wiping data but NOT wiping data/media. Any ideas if something has changed in TWRP source from 2.3.x.x to 2.4.xx? Thanks again for your efforts on this.
EDIT: We must have been posting at the same time. Would it be of any help to "take a look inside" the 2.3 version I mentioned above from aidfarh? I believe the 2.3.x.x versions were the first optimized for 4.2/CM 10.1.
Mike T

That would be ideal, but those settings come from the build environment (BoardConfig.mk, mostly), and is unique to the device. The trick is to pull those files from the CM repo and build against that. You also need to tweak the fstab somewhat, which differs within the GTab2 line.
Essentially, you sync and build a working CM for your device, then replace the built-in recovery with the TWRP repo. Then, it's a matter of tweaking the settings for the device so the recovery builds with the proper partition mappings, etc. When CM10.1 moved to multi-user, the internal sdcard was relocated to /data/media (or something), which suggests that TWRP should be smart enough to wipe all but that location.

I'm trying Joe, thought it could be helpful. I wish I had a better skill level on this stuff. Fortunately for me, I only need external SD card capability but I'm sure you'd like to get it right.
EDITING for your edit: Yeah, in the 2.3.2.3 build it seems that TWRP is acting as it should. Hopefully, you can get it figured out. Thanks. Btw, thanks for the explanation.
Mike T

Original post updated - several changes & new 2.4.4.0 posted to the DropBox share = includes .img, odin .tar.md5 and recovery-flashable .zip. Preserves /data/media in wipe and can mount/backup internal or external sdcard.

Works great Joe. Was able to install zips from internal/external, also able to backup/restore from both internal/external. Did a factory wipe and internal sd card data was preserved. Those functions are now working as they should.
Thanks for sticking with it, it's appreciated. I also found a theme that aside from one minor graphics glitch, looks and works great. It's the Eyecandy theme from XDA member Pimpmaneaton that he made for the Kindle Fire. The small graphic glitch is with the internal/external radio buttons, there's a slight discoloration on the button not selected. Not a deal breaker for me.
Mike T

This new built work great. I prefer TWRP than CWM, it's much easier to use plus I can move backup back and forth to my computer to save space.

You're the man, thanks for all the hard work.

Re: TWRP 2.4.4.0 for gt-P3113
Flashing meow. Its nice having the same recovery and ROM on two different devices.

sdcard not mounted - milaq's CM11 - 1/18

I have been using milaq's cm11 nightlies, after first week of Jan14 my sdcard1 (another partition on TP) stop showing on file explorer.
However, when I installed invisiblek nightlie (ofcos with 3.4 kernel cwm), start showing the sdcard1 partition.
based on my analysis milaq's 'init.tenderloin.rc' file do not have entries to mount the sdcard1.
Appreciate any kind of help.

[email protected] said:
I have been using milaq's cm11 nightlies, after first week of Jan14 my sdcard1 (another partition on TP) stop showing on file explorer.
However, when I installed invisiblek nightlie (ofcos with 3.4 kernel cwm), start showing the sdcard1 partition.
based on my analysis milaq's 'init.tenderloin.rc' file do not have entries to mount the sdcard1.
Appreciate any kind of help.
Click to expand...
Click to collapse
Did you post this twice?
Please review the many posts on this topic in Milaq's CM11 thread. This issue has been discussed ad nauseam.

[email protected] said:
I have been using milaq's cm11 nightlies, after first week of Jan14 my sdcard1 (another partition on TP) stop showing on file explorer.
However, when I installed invisiblek nightlie (ofcos with 3.4 kernel cwm), start showing the sdcard1 partition.
based on my analysis milaq's 'init.tenderloin.rc' file do not have entries to mount the sdcard1.
Appreciate any kind of help.
Click to expand...
Click to collapse
Milaq has removed (deprecated) the use of the external_sd (sdcard1) partition. It was created for the touchpad as a way of sharing a partition with WebOS and it is no longer needed. Use WebOS Tailor to resize your old partition down to a couple of megs and add all that extra space to data. You will never miss having it.

laspero said:
Milaq has removed (deprecated) the use of the external_sd (sdcard1) partition. It was created for the touchpad as a way of sharing a partition with WebOS and it is no longer needed. Use WebOS Tailor to resize your old partition down to a couple of megs and add all that extra space to data. You will never miss having it.
Click to expand...
Click to collapse
Many thanks to both of you (woodytrain & laspero). :good:
Forget to mention that, I have referred the touchpad in my query.
That's good suggestion! However if I want to have two separate partitions to have well arranged my stuff, would it be possible to get that feature back?
Also, apart from kernel, is there any major difference between milaq & invisiblek rom?

[email protected] said:
Many thanks to both of you (woodytrain & laspero). :good:
Forget to mention that, I have referred the touchpad in my query.
That's good suggestion! However if I want to have two separate partitions to have well arranged my stuff, would it be possible to get that feature back?
Also, apart from kernel, is there any major difference between milaq & invisiblek rom?
Click to expand...
Click to collapse
go ahead and give invisiblek's rom a try. Before you try to install it make sure you have the correct recovery.
You'll need a recovery that has both /data/media support and selinux support.

laspero said:
go ahead and give invisiblek's rom a try. Before you try to install it make sure you have the correct recovery.
You'll need a recovery that has both /data/media support and selinux support.
Click to expand...
Click to collapse
I am already on invisiblek's rom, which is working fine since I started the thread.
I have been using Milaq (sir!) rom since 10.2. So was a bit worried going to invisiblek's (with due respect to invisiblek).
I wanted to know the differences between those two roms. I know one is the kernel.
@woodytrain - I posted the question twice, as after the first one, I thought it would be unnoticed over there. So post this one.

[Q&A] [Nook HD/HD+] EMMC CM11 install - updated 08/17

Q&A for [Nook HD/HD+] EMMC CM11 install - updated 08/17
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Nook HD not charging since CM11 install
This morning I installed the latest CM11 build (M11) on my daughter's Nook HD. Prior to that I was using the stock ROM with no issues. Since installing the ROM the tablet will not charge; rather than showing an orange light the device shows a green light whenever the charger is connected.
It seems possible that my cable has failed at the same time as performing the install, though a little unlikely.
Thank you for your help.

CM11 - TI OMAP drivers going to get updated?
As seen here:
http://forum.xda-developers.com/nook-hd/general/updated-ti-omap-video-driver-sluggish-t2912381
Just curious if we'll see these get rolled in...
Thanks for all the hard work!

I updated my Nook HD+ from CM 11 snapshot 10 to 11 OTA , now there is frequent automatic-touches or ghost-touches on the screen without me touching the screen. Any help?

Newbie Questions - B&N HD+
Hi - i am going to flash my B&N HD+ for the first time. i have been reading the forums and instructions and have few questions.
i want to do this without SD card (i can go buy one but i if not needed, i prefer not to use it). is this possible? in the EMMC thread, i still see that the SD card must be used for the flashing/booting. so essentially, to flash CWM 6046, is it possible to not use SD card? and if so, can someone tell me how to do that?
Thanks
Ali

Ali Khawaja said:
Hi - i am going to flash my B&N HD+ for the first time. i have been reading the forums and instructions and have few questions.
i want to do this without SD card (i can go buy one but i if not needed, i prefer not to use it). is this possible? in the EMMC thread, i still see that the SD card must be used for the flashing/booting. so essentially, to flash CWM 6046, is it possible to not use SD card? and if so, can someone tell me how to do that?
Thanks
Ali
Click to expand...
Click to collapse
No, you must use an SD. There is no other way. And I suggest you use the dummies guide linked in my signature.
Sent from my BN NookHD+ using XDA Premium HD app

NookHDVolumeAdjuster for CM11 or CM10.2 ?
Is there a version of NookHDVolumeAdjuster that runs under CM11 or CM10.2 ? I am using version 1.0 under CM10.1.3. When I tried CM10.2, the sliders were all stuck at the far left. I need the sound higher volume, so I can't upgrade to CM10.2 or CM11. thanks.

Image Links?
Links to the intial sdcard image and recovery image in the original "[Q&A][Nook HD/HD+] EMMC CM11 install - updated 08/17" post are broken (nook.rootshell.ru appears down, from my perspective). Are these available elsewhere?
Thanks.

cmuser2 said:
Links to the intial sdcard image and recovery image in the original "[Q&A][Nook HD/HD+] EMMC CM11 install - updated 08/17" post are broken (nook.rootshell.ru appears down, from my perspective). Are these available elsewhere?
Thanks.
Click to expand...
Click to collapse
You can go to the dummies guide linked in my signature. In post 7 of that thread is everything you need for running CM11 on the HD/HD+.
Sent from my BN NookHD+ using XDA Premium HD app

Excellent ROM, thanks.

Nook HD plus and Gapps error status 6
Good morning,
I was working on flashing my nook last night with
cwm-recovery-ovation-6.zip
cm-20141224-NIGHTLY-ovation.zip
I have tried many different versions of stock, modular-full, modular-mini and gets a status code 6, I have successfully flashed gapps-kk-20140606-signed, but when I try to use it, the playstore just hangs like it is loading. Can someone advise the steps I need to take to successfully install a working version of gapps?
I have tried factory wiping several times and flashing the various versions of GAPPS.
Thanks in advance for any assistance that you provide.
Jim

jmcease said:
...
I was working on flashing my nook last night with
cwm-recovery-ovation-6.zip
cm-20141224-NIGHTLY-ovation.zip
I have tried many different versions of stock, modular-full, modular-mini and gets a status code 6, I have successfully flashed gapps-kk-20140606-signed, but when I try to use it, the playstore just hangs like it is loading. Can someone advise the steps I need to take to successfully install a working version of gapps?
I have tried factory wiping several times and flashing the various versions of GAPPS.
...
Click to expand...
Click to collapse
I'd suggest that you try resetting the Google Playstore app: go to Settings->Apps->Google Playstore, and do a "force stop" and "clear data" (after which you'll need to re-enter your Google (Gmail) account login/passwd).

CM11 M12 - Device Temperature
Hi all,
After staying around on CM10.2 for a long time due to a few issues with earlier snapshots of CM11, I've decided to upgrade to M12. Finding it runs great on everything I'm doing - definitely smoother performance. One thing I am concerned about is the temperature hike of my tablet, particularly when charged and running a game (in this instance, Terraria). Is anyone finding the back running quite hot? Can feel it on the screen and the left side of the device, but the temperature reading of 32C/90F doesn't seem that bad... it does feel worryingly hot though. Not sure if it's something on my end or a common thing with CM11, but I never had this on any other build.
As a sidenote - do the developers accept donations?

Audio stuttering in Rayman Jungle Run
I just did an SD card install of CM11 on a Nook HD+ and it's been working well (thanks!), except that I've noticed that the audio in Rayman Jungle Run and Rayman Fiesta Run tends to stutter / warble, making it unpleasant to listen to. Youtube and Great Big War Game sound are good. I'm using cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip with its initial sdcard image for ovation (sdcard-cwm-early9.img) from the first post. The micro SD card is Samsung class 6 16GB.
Any ideas on how to fix this?

Swap
Ponow said:
Any ideas on how to fix this?
Click to expand...
Click to collapse
Well, what I did, is I found the thread here that describes how to put B&N's OS v2.2.0 on a bootable microSD card. Once I had that working (it's not like B&N is ever going to update the firmware), I did a backup of the Nook's internal storage, and then installed CM11 on the internal storage.
That should solve your performance issues.
Note: You mention an HD+, but then refer to "Ovation", which is the name for the HD, not the HD+. You may want to edit your message to clarify the situation.

DeanGibson said:
...
Note: You mention an HD+, but then refer to "Ovation", which is the name for the HD, not the HD+. You may want to edit your message to clarify the situation.
Click to expand...
Click to collapse
ovation = HD+, hummingbird = HD.

Brain fart
digixmax said:
ovation = HD+, hummingbird = HD.
Click to expand...
Click to collapse
Oops, since the files I used to install CM11 clearly say ovation.

DeanGibson said:
Well, what I did, is I found the thread here that describes how to put B&N's OS v2.2.0 on a bootable microSD card. Once I had that working (it's not like B&N is ever going to update the firmware), I did a backup of the Nook's internal storage, and then installed CM11 on the internal storage.
Click to expand...
Click to collapse
Thanks for taking the time to reply. I would have done an internal install, but when I tried to backup the built-in firmware 2.2.0 using CWM 6.0.4.6 (from the OP), I got an error due to the /system partition being unmounted (I'm recalling this from memory; I hope I got it right). I tried using the mount option in CWM, but that failed too. I then said "screw it with the backup... I'll find another on the web", and then tried to do an emmc install of the latest milestone (M12) from the cyanogenmod download site (using SDCARD CWM-based 6.0.4.6 booted from SD... not internal memory), but the install failed with a "status 7" error (IIRC). I also tried using an earlier microSD image (sdcard-cwm-early7.1.img) and tried to install a backup of stock 2.2.0 firmware that I found from another thread here (thinking that maybe I had borked my own from an attempt at installing recovery CWM), but that finished too quickly (yet no errors), and on reboot it didn't appear to have overwritten my own stock firmware. After these efforts spanning a half dozen or so hours of reading, experimenting, etc., I was able to at least get the SD card install working, so I said screw it, I'll just use SD card. But I would really prefer an internal install as you suggest.
I wasn't able to get CWM to boot from internal memory, only SD card (Samsung 16gb class 6). I didn't try very hard though. Maybe this is the reason I can't do an emmc install or backup? Can you only backup internal memory after having booted from CWM recovery (on internal memory, not SD card)?
I was able to find a post somewhere that related the /system problem to rooting, but I never have rooted my Nook HD+ (manufactured Dec'12).
After reading more about the slow 4kB random write performance on most SD cards, I'm thinking of getting a Sandisk class 4 card, but I'd rather not go there if not necessary.
Thanks again.

Ponow said:
Thanks for taking the time to reply. I would have done an internal install, but when I tried to backup the built-in firmware 2.2.0 using CWM 6.0.4.6 (from the OP), I got an error due to the /system partition being unmounted (I'm recalling this from memory; I hope I got it right). I tried using the mount option in CWM, but that failed too. I then said "screw it with the backup... I'll find another on the web", and then tried to do an emmc install of the latest milestone (M12) from the cyanogenmod download site (using SDCARD CWM-based 6.0.4.6 booted from SD... not internal memory), but the install failed with a "status 7" error (IIRC). I also tried using an earlier microSD image (sdcard-cwm-early7.1.img) and tried to install a backup of stock 2.2.0 firmware that I found from another thread here (thinking that maybe I had borked my own from an attempt at installing recovery CWM), but that finished too quickly (yet no errors), and on reboot it didn't appear to have overwritten my own stock firmware. After these efforts spanning a half dozen or so hours of reading, experimenting, etc., I was able to at least get the SD card install working, so I said screw it, I'll just use SD card. But I would really prefer an internal install as you suggest.
I wasn't able to get CWM to boot from internal memory, only SD card (Samsung 16gb class 6). I didn't try very hard though. Maybe this is the reason I can't do an emmc install or backup? Can you only backup internal memory after having booted from CWM recovery (on internal memory, not SD card)?
...
Click to expand...
Click to collapse
It looks like you used the installation files meant for creating SD-based ROM image
See http://forum.xda-developers.com/showthread.php?t=2679899 or http://forum.xda-developers.com/showpost.php?p=42406126&postcount=7 for info/pointers on EMMC installation.

digixmax said:
It looks like you used the installation files meant for creating SD-based ROM image
See http://forum.xda-developers.com/showthread.php?t=2679899
Click to expand...
Click to collapse
This worked! I now have an emmc install of cm11 M12 from the cyanogenmod site. Since I'm running Ubuntu GNU/Linux, not Windows, I replaced steps 1 to 3 in your instructions in the above link with (at terminal prompt, with microSD card inserted but unmounted):
gunzip emmc-cwm-early3.1.img.gz
sudo dd if=emmc-cwm-early3.1.img of=/dev/sdb
I then mounted the microSD card and copied (as root) the zip files as in your link, all with terminal. The unmounted /system partition error did not appear, and the M12 install went fine! When wiping I had an error related to sd-ext missing, but from some more searching I concluded that it was benign.
Thank you for helping me out. I was starting to give up before the help I've received here. I'm generally really pleased with the performance of cm11 on Nook HD+ so far. I'm not yet noticing much difference between emmc and sd-card installs, performance-wise.
Unfortunately, the earlier performance problem (sound stuttering/warbling in Rayman Jungle Run) is still there using this internal / emmc install vs. the earlier SD-based install of cm11, which suggests that the problem is in cm11 itself. On stock firmware (version 2.2.0 I believe when tested), Rayman Jungle Run ran fine (no sound problems at all). The sound problem may be a slowdown problem, but it's not severe.

Updating Android 6 (CM13) with merged storages (SD as internal)

Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
-UPDATE:
Here are three solutions for updating:
a) The downloaded .zip file has to be moved to /data (if wanted, into some subfolder of your choice. ES-File Explorer needs root for that) Then flash via TWRP.
b) Use flashify, choose copy to safe location (had some FC's afterwards)
c) Use cm-recovery, update via cm-updater (not yet confirmed)

davedophin said:
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
Click to expand...
Click to collapse
1. I don't think so. For this we should need an updated recovery supporting this feature. Furthermore, the feature is not fully ready, imho
2. I don't know. Never had this problem.
Written with my XT1068 using Tapatalk on CM13

On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.

Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk

Dieselhorst said:
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Click to expand...
Click to collapse
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.

Mavireck said:
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Click to expand...
Click to collapse
I believe you when you say Flashify can flash the rom. But as said, it's all way to complicated for the 'average' user. Especially because of the encryption, which causes the sd card to be unseen by, for example, your recovery or your pc. These things have to be solved first!
Written with my XT1068 using Tapatalk on CM13

Sure, that's why I say
This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Click to expand...
Click to collapse
.
I think we should stop debate now because we think the same

Mavireck said:
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Click to expand...
Click to collapse
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!

davedophin said:
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
Click to expand...
Click to collapse
The twrp team is awesome. They will find a fix.
I only tried flashing the ROM but i think you can flash at the same time gapps.

Alright, Flashify works, if you pick the option "copy to safe directory" or similar. "use provided path" doesnt work for me.
But after the update, Nova Launcher keeps crashing and titanium backup doesnt show up on the app drawer anymore, but is still installed and cant be uninstalled to reinstall. pretty weird. So for me, this option doesnt really work either.

I copy the update zip file to \Data\Media\0\twrp and i can update
Anyone knows if the SuperSU 2.60 works in the CM13 Moto G2014???

@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk

bhachech said:
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).

davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I haven't used TB or Nova... CM 13 on Titan is running very well for me. As expected, in these early nightlies, some CM features are not fully implemented but that has not hindered my ability to use it as a daily driver for the past couple of weeks.

davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I use Nova and TB, no problems here

Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk

ygtenos said:
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
I've tried like 4 releases of CM13 so far, never had a problem like that. But I only used builds from december, so I would suggest you go for a newer version, after a backup of course

Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)

So guys, I updated to todays build by moving it to the /data partition and then using twrp. Works like a charm! Thanks everyone for your help!

davedophin said:
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
Click to expand...
Click to collapse
Does not work for me (Moto Thea)