At the request of a user I am creating this thread to consolidate my tips for the Nook Color that are spread out over several other threads. Check back occasionally as I may add more tips to this post. (Note: This tip post got so large that I had to split it into two posts so that XDA would let me post changes. See the next post in this tread for the continuation.) See the change log in my second post.
Most of these were developed for CyanogenMod versions 7, 9, and 10, but some may work on other ROMs. These tips are in no particular order, except that general tips are in section A and SD tips are in section B.
I know this is a long post (I have been accused by one user of being 'long-winded'), but you do not have to read all of it (unless you want to). Just scan the headings and read those that apply to your issue. I think the most useful tips for users having problems are A8, A9, A10, A11 and A12. For SD users it is item B2, which points to the latest SD image file.
A. GENERAL TIPS THAT WORK ON CM7, CM9, or CM10
A 1. Put some settings in /data to avoid losing them in a ROM flash
Many things can be added to the /data directory to customize how CM operates. By adding the things there, they survive a flash of a new ROM since new ROM flashing usually only effects /system.
You can create a new text file named local.prop and put it into /data. That file can contain anything that normally can be put into build.prop in /system. It is loaded after the build.prop file is loaded so in some cases it can override settings in build.prop.
You can create a new folder in /data/local named userinit.d. In that folder you can place script files that you want to run at boot time. An example of a script that works is the script to make the SD boot partition show up on your system for SD installed CM. That is described later.
You can put a custom boot animation in /data/local and it will override any boot animation that is included with your ROM in /system.
You can set some system properties by putting entries in a folder named /data/property. For example, if you want to skip the boot animation at boot time, create a text file named persist.sys.nobootanimation and place the value 1 in it. Then the animation is turned off. If you want to re-enable it, change the value to 0.
In some of these files it is important to set the permissions correctly in order for them to work. For example, any scripts in the userinit.d folder must have their permission set to execute or they will not execute at boot time.
A 2. Dalvik Cache, what it is, how it works.
Dalvik cache is a method that android uses to speed up operations. There are two dalvik caches. One in /cache (for system apps) and one in /data (for installed apps). Clearing dalvik cache with recovery clears both. Clearing /cache will clear the dalvik cache in /cache but not the one in /data.
In flashing new ROMs, the only one really needing clearing is the one in /cache since only new system apps are installed in a ROM flash. Also only clearing the one in /cache makes it boot faster since the nook does not need to rebuild the one in /data for your installed apps which have not changed.
I have described how the cache works and a tip on how to speed up booting for SD installs here. The tip is repeated in section B3 in the second post of this thread.
A 3. Wiping in preparation of a new ROM flash.
Ordinarily if you are moving from one nightly to another nightly of the same rom, just wipe dalvik cache with Clockworkmod (CWM) Recovery.
If you are moving from one type of rom to another, it is best to do a "wipe data/factory reset". A factory reset wipes /data, /cache and clears any apps you installed to SD. The rest of your media data on emmc or SD is left intact. Since a factory reset clears both /data and /cache, there is no need to separately clear /cache or dalvik-cache. A factory reset means you will lose all settings and installed apps. So, before you do a factory reset, you may want to backup your apps with a program like Titanium Backup so you can restore them later without re-installing. If you have one of the newer Nook Colors with the new partition layout, you need to have version 3.2.0.1 or newer of CWM or the factory reset will not complete properly.
The new rom automatically wipes /system as part of the installation, so you should not have to ordinarily wipe that.
Never wipe /boot. It will remove your stock or CWM recovery and you may end up in a bootloop. Or worse yet, since it removes the boot files, it will not turn on at all unless there is a bootable SD in the SD slot.
When flashing a stock ROM, I have found that for some reason CWM does not wipe clean enough and the new ROM stalls. I have found that I have to flash my format partitions 5, 6, and 7 zip as described in my item A15 below. In fact, anytime you are switching from one kind of ROM to another it might be a good idea to use that zip first.
A 4. Freeze/Block applications
There may be times when you want system installed apps to be removed from your system. Do not just delete them from /system. You may find later that you want them back and also deleting them may cause your system to lock up. You can use third party apps like Titanium Backup Pro (not free) or Gemini Application Manager (free) to freeze/block the apps you don't want. These apps change an entry in a system database that tells the system to ignore those apps. They will not be loaded into memory or listed in your app drawer. With these third party apps you can do this to any app. For CM9/CM10 you can do the same thing for system apps in Settings/Apps. Just open the system app and select disable. You can always enable it later. But this only works for system apps.
A 5. Sleep of Death (SOD) on CM7 and CM9
SOD has been a problem with CM for a long time. If you leave your wifi set to stay on all the time and the device goes into deep sleep, it sometimes will not wake back up. There is apparently some interaction between waking up and wifi that locks it up. The device is on but you cannot get the screen to come back on. The only way to get out of it once it is locked is to hard power off by holding the power button for like 15 seconds and then releasing the power button and pressing again to power back on. For CM7 the work around is a modified wifi kernel module (twlan_drv.ko) in /system/lib/modules. (Get it here). The devs have built in the mods to the CM9 kernel so the revised module is not necessary in CM9.
A 6. ADB on CM9/CM10
For some reason that I do not understand, the device id (which is normally 2080:0002) is changed for CM9/CM10 in Windows. That means the adb composite drivers do not install properly and adb does not work. When you turn on USB debugging and plug your USB cable to your PC, Windows says it is looking for MTP drivers, but is really looking for adb drivers. I have explained how to fix that here.
A 7. Soft Navigation Keys in CM9 in Phone GUI
In both CM7 and standard CM9 the status bar is at the bottom of the screen and has soft navigation keys built in. In CM7 when you change screen density to a higher value, the status bar does not change. However in CM9, when you change density higher than the standard 160 dpi, the GUI switches to the phone mode and puts the status bar at the top like a normal android phone. The downside is that the soft navigation keys normally displayed on the bottom of the screen are suppressed. To get them activated just add a couple of lines to your properties file. See my post here.
A 8. Recovery bootloops
There is sometimes a mysterious bootloop issue where no matter what a user does, the Nook bootloops on booting. This is usually caused by a corrupt or missing recovery itself or by missing or corrupt files in partition 2 (/rom). No matter what the user chooses in the boot menu, it tries to find a working recovery to boot to. If it finds one, it boots to it. If it cannot find a working one, it boots to a blank screen or just a stuck "loading". Even if you put one of the older bootable CWM SDs in the slot, it still gets stuck since those older CWM SDs do not contain normal recovery files, just special bootable files.
There is a flag file in the /rom partition that tells the Nook to boot into recovery. ROM Manager uses that flag file to tell the system to boot to recovery when the user selects that option. And it tries to boot there no matter what the user tells it to do in the boot menu. After it successfully boots into recovery, recovery resets that flag file as it exits normally with the menu choice. So next time it boots it boots normally.
Sometimes that flag never gets reset, usually because there is no working recovery to reset it. So it continues to try to boot to recovery.
And sometimes it could be a missing or corrupted file on your /rom partition. In a folder in /rom (/devconf), several device specific information files are stored. One of those files (DeviceID), is critical to your device booting to a rom. If it is missing or corrupted the Nook will always try to boot to recovery so that it can repair itself. See my description of this problem in item A12 below.
If you boot to a blank screen or a stuck "loading" no matter which option you choose, it usually means a corrupt or missing recovery. If you boot to recovery repeatedly no matter which option you choose, it usually means a corrupted /rom partition.
To fix a corrupted or missing recovery on emmc, use my new CWM recovery SD I have detailed in my item A10 below. This SD has been modified to include the normal recovery files in addition to the special bootable CWM files there so that it can boot into recovery in this kind of failure. Just prepare the SD as described in item A10 below and turn off the Nook and insert the SD. Boot and the new CWM should appear. Sometimes just exiting that CWM immediately with the menu choice will get you out of the loop so you can boot to your ROM. But you probably still need to put a good recovery on emmc. Flash one of the stock recovery versions I have attached to this post below, or the new version of CWM (5.5.0.4) for emmc by Racks, also attached below (thanks Racks for the CWM). I recommend that you flash my stock recovery with CWM 5.5.0.4 as alternate version. That will put stock recovery as the normal recovery and the new CWM as an alternate recovery. That way if the nook decides it needs to repair partition 2, it can (see item A12 below for a description of that). And you can still get to CWM by booting to the alternate choice with the boot menu or holding volume up/down while booting. (The only downside I can think of using this zip is ROM Manager can no longer be used to flash things, it needs CWM as the normal recovery.)
You should probably save the CWM bootable SD for future use. You can use it to nandroid backup to the emmc media partition, factory reset and flash new ROMs to emmc as well as getting out of future bootloops.
To fix the issue of a corrupted /rom partition, go to my partition repair thread here or use the romrestore utility attached to this post. See item A12 for a description of romrestore.
For those interested in the details, the recovery flag file is named BCB and is in the /rom partition (P2). It is not what is contained in the file that makes a difference, it is the file size. If the file is 512 bytes or larger, the Nook will boot normally. If the file is less than 512 bytes or is MISSING or unreadable, it boots to recovery. And the DeviceID file in /rom/devconf is a 17 byte text file containing your 16 digit serial number followed by a linefeed.
A 9. Bootable SD Cards
An SD card must be formatted in a very specific way before the Nook Color will boot from the SD. The first partition must begin exactly on the 63rd sector of the card and the flags properly set.
It is very difficult using normal formatting programs and partition managers to make that happen. That is why devs include burnable images to burn to the cards if they are to be bootable. Examples include eyeballer's bootable CWM card, verygreen's SD installer card, racks' dual boot SD card and my new bootable CWM version 5.5.0.4 in item A10 below. They have the images all set up so that when burned properly the first partition is configured so it can boot.
But even when using these images they do not always work if they are not burned to the card properly. The cards may be readable in the PC, but do not always boot in the Nook. In Windows, most devs recommend using winimage or win32diskimager (here, it's free) run in administrator mode. Also if using winimage, do not select "write disk", select "Restore Virtual Disk Image to physical drive". In Linux or OSX, use the "dd" command. And they recommend using an external USB reader rather than any built in readers in the PC. Sometimes it is just the card you are using causing the problem. And sometimes you can get them to boot if you plug your stock USB cable and powered off Nook into your PC. Wait a few seconds and it might boot.
Don't give up, keep trying. It eventually should work if you have the SD prepared properly.
A 10. New Bootable CWM Recovery SD (v5.5.0.4 and now v6.0.1.2)
I have created a new bootable CWM SD and attached a zip of the image to this post (CWM-5.5.0.4-bootable_SD.zip). It is version 5.5.0.4 and is to be used for flashing/wiping/backing up emmc. To create the SD just unzip the image file and burn it to your SD with win32diskimager (here, it's free). Since it is only 200MB it can be put on a very small SD. Also since it is so small there is no room to make backups there. However, this version of CWM will let you backup to internal (emmc) media storage. But there should be plenty of room to put flashable zips on the SD. If you want the partition larger, after burning just use a partitioning program like Mini-Tool Partition Manager to expand it. This version of the bootable SD uses the new Cyanoboot bootloader, so just let it go and it will automatically boot to CWM. When finished using CWM, be sure to exit using the menu choice so that the recovery flag is reset. When you have exited, either keep the SD for future use or reformat it to use for other purposes. Thanks to Racks for the 5.5.0.4 CWM.
This CWM SD can be used for getting out of some recovery flag bootloops as described in item A8 above.
Just added v6.0.1.2 with a little larger partition (300MB). This version should be used if you want to flash the stock ROM from item A15 below. Otherwise, use either version.
For those users that do not want to use CWM, I have make a bootable SD that has an older version of TWRP here. Newer versions of TWRP will return an error message trying to flash my older zips. The image has also been modified to get you out of some bootloops.
A 11. EMMC partition repair
Several users have complained that they get blank screens and cannot flash new roms to their Nook Color. And sometimes they end up in a recovery bootloop where it will do nothing but boot to recovery no matter what they choose in the boot menu. Sometimes this is due to corrupted partitions.
I have developed some tools to help users repair corrupted partitions on emmc. See my thread here.
A 12. B&N stock automatic repairs (Factory reset to stock via 8 failed boots and automatic partition 2 (/rom) repair)
B&N built in two automatic repair utilities for Nook Color systems that were malfunctioning. First, it has a fail safe system that allows it to repair itself if the user was unable to get it to boot 8 times in a row. Second, it has an automatic partition 2 (/rom) repair utility (romrestore).
But both of these repair functions are only available if you still have the stock recovery on emmc. If the user has replaced that recovery with CWM (or TWRP) recovery they will not work. It is OK if CM has been installed on emmc, it is only a problem if CWM was also installed there wiping out the stock recovery. But I have a solution for that. I have attached a zip to this post that will re-install the stock recovery replacing CWM on emmc. And I just added the partition 2 repair zip to it. Now both stock repairs will work. Just flash the zip with CWM recovery (either from emmc or a bootable CWM SD card). I also added a version that will put stock as the normal recovery and CWM 5.5.0.4 as the alternate recovery. Just select it with the boot menu if you want to use it.
Stock recovery looks very different than CWM. If you boot into it (either using power/n keys during boot or the boot menu choice in cyanogen bootloader), a dialog box pops up asking if you want to do a factory reset to wipe all the data on the device. If you say yes it will wipe /data, /cache, and the media partition. If you say no it will reboot.
8 failed boot reset. An image of the system as it came from the factory is stored on one of the partitions (p3). After the 8 failed boots, the stock recovery software is automatically started and wipes all data (including emmc media storage) and restores the system files to original.
This is really handy for rooted stock users who want to either sell the system or return it to B&N. And it is useful if somehow the user cannot get the system to boot to a bootable SD and they want to start over with the stock ROM.
The procedure to follow if you still have stock recovery on emmc is:
(Paraphrased from a post by Harrybub)
Start with the Nook completely powered off.
Press and hold the power button, the volume up button, and the n button until you see the screen flash. (I have found the best way to do this difficult maneuver is to press n with the thumb of one hand and the power and volume up with the thumb and forefinger of the other hand, griping the top of the device.)
Release all buttons for one second then press and hold only the power button for several seconds until the Nook powers down. (Backlight off) This works best in dim lighting.
Do this again for a total of 8 times in a row.
The last time a screen will come up saying it is clearing your data and installing the factory image (which is stored as factory.zip on partition 3). You will be back to what it was when it came out of the box.
If you mess up the timing and it starts to boot up you will have to power it down again and start over at count one.
Click to expand...
Click to collapse
Of course if you can still flash things using CWM, it is probably easier to just flash a stock zip than to do the 8 failed boot procedure. But I wanted users to understand the process in case it was their only option. See item A15 below for flashing stock ROMs with CWM.
Automatic partition 2 repair utility. This repair utility will automatically repair partition 2 (/rom) if it thinks it is necessary. In partition 2 is a folder (/devconf) that holds vital system configuration files that the Nook needs like serial numbers and boot counts to help it decide to do the 8 failed boots described above. Every time the Nook boots, it checks the integrity of that folder and if it thinks it needs repair, it tries to repair it.
The test that it uses is it looks for a specific file in devconf named DeviceID. It is a text file that contains your 16 digit serial number followed by a linefeed (17 bytes total). On boot, if the that file is corrupted or missing, stock recovery is automatically invoked and runs a zip file named romrestore.zip that is in /boot. That zip looks in partition 3 (/factory) for a file named rombackup.zip. That file is a backup of your devconf folder from partition 2 that was made at system manufacture. If the backup file is found, the repair zip first formats partition 2 and then copies those backed up files from partition 3 back to your partition 2. It then continues the boot process booting to the installed ROM.
Partition 2 repair bootloop. This last repair utility is how some recovery bootloops happen. The user replaces the stock recovery with CWM recovery as part of putting a new ROM on emmc. Then when the system boots, it checks for integrity of partition 2 and if it thinks it needs repair, it tries to boot to stock recovery to do the repair. But stock recovery is no longer there. So it boots to CWM recovery and does nothing. No matter what the user does, it keeps trying to find stock recovery. Hence a bootloop.
There are three ways to get out of this loop.
You can flash a new stock rom on emmc. It will reinstall the stock recovery and repair zip as part of the installation. Then it can find that stock recovery on boot and repair itself. But you have to use a stock zip file that has been modified so that CWM can flash it. See my item A15 below for a link to a version of stock 1.4.3 that has been modified to be CWM flashable.
Or you could flash my stock recovery zip mentioned above. I just modified it to include the repair zip. In fact, you might want to flash my stock recovery zip that has CWM as an alternate recovery. I have included the CM bootloader with it so that you can use the boot menu to get to the alternate CWM. By using the stock recovery as normal recovery, the Nook can repair partition 2 any time it thinks it is necessary. And it is ready any time someone wants to use the 8 failed boot procedure.
Or you can flash one of my versions of the partition 2 repair utility. I have two. Romrestore (CWM flashable) is attached to this post. This romrestore zip is the stock version modified so it is flashable with CWM. It does not recreate the partition, it just repairs the files there. The other version is in my EMMC partition repair thread here and actually recreates the partition before it repairs the files. Once either of these are flashed successfully, and the Nook boots, the system should not find any errors in partition 2 and it should boot normally.
A 13. Nook Color Charging/Battery
The Nook Color charging adapter and cable have been custom made for charging the Nook. First the charging block has the data pins (d+/d-) shorted. Second the charging/USB cable has a special connector on the Nook Color end of the cable. It sort of looks like a standard microUSB connector but it is not. It has been elongated to add a second row of pins behind of the standard microUSB pins. Those extra pins mate with similar extra pins in the connector inside the Nook Color. Among other things, those extra pins give the cable more charging capacity. (For those interested, the pinout has been recently traced by a user and documented here.)
The charging circuitry inside the Nook Color looks for those conditions of the charging block (shorted d+/d-) and the extra pins in the connector. If it finds both of those conditions it allows for full charging capacity of the Nook Color (about 1.9A). The Nook Color will charge quite rapidly at that current. However if it does not find both of those conditions, it will think it is connected to a USB port and limit charging current accordingly (about .5A). This can take a while to fully charge the Nook Color (especially if the screen is on at the same time.) The charging circuitry does this for all ROMs. (Edit: There is also a third possibility. If you use a shorted d+/d- charger and a standard microSD cable it will charge at about half rate (about 1A). Thanks bobtidey for that tip.)
It is possible to use third party charging blocks with the data pins shorted along with the stock cable and you can still get full charging capacity.
But standard microUSB cables work great for data transfer between the Nook Color and your PC. And they can be used for limited charging with the USB port of your PC. Your PC usually limits that to .5A anyway.
Using the stock cable frequently sometimes leads to cable failure issues since the stock cable is so fragile. I got one replaced under warranty by B&N. But I finally bought a spare B&N power charging kit at Office Depot for $25. It included the charging adapter and cable. I have since found that the B&N kits are available online by many vendors. I have seen them as low as $12.95. Do a search for ADP-H01 and you will see many.
Several users have complained of battery problems. Their percentage varies all over the place and the device shuts down unexpectedly. My advise usually is to try a wipe battery stats from CWM. There is a lot of controversy in the community whether that really does anything useful. A few "experts" have said it does nothing and is only a placebo. And it has been removed from newer versions of CWM and TWRP. Another thing to try is to delete the max17042.bin file from /rom. Don't worry, it will get rebuilt on the next boot.
One of the users on this forum (catawalks) ran across an article about use and care of lithium ion batteries. There is a lot of good advice there that is not common knowledge. The user learned that how he was treating his battery was almost guaranteed to make it fail. (He was leaving it discharged for long periods of time then recharging fully and storing again.) You can read the article here (thanks catawalks for the link).
For those having an unusual battery drain while the unit is sleeping and want to find out what is causing it, get BetterBatteryStats here. This app is free if obtained here on XDA but costs on the Play Store. It tracks what are called "wakelocks". Those are applied when specific applications want to keep the Nook awake while it performs tasks in the background. They bring the system temporarily out of deep sleep. Of course your system uses more battery while this happens. Look at the wakelock information this app displays to get an idea what is keeping your Nook awake.
A 14. Skip Oobe (Out-of-Box Experience) for stock Nook Colors
If people are having trouble registering their stock Nook Colors, mateorod discovered a documented procedure where you can skip the registration step including setting up wifi. Just go here and follow the instructions. It even explains how to factory reset so that all data is wiped from the device. Thanks mateorod!
A 15. Flashing stock ROMs with CWM
Ordinarily stock ROM zips downloaded from B&N cannot be flashed to emmc with CWM. You must use the stock recovery to flash them. However, the zip can be modified to make it flashable with CWM. You can get a stock version 1.4.3 zip that I have modified to be flashable with CWM here or DizzyDen's older 1.4.1 stock zips here. The zip files are so large that it is best to use either the 6.0.1.2 CWM or the 2.1.8 TWRP bootable SDs from item A10 above. If you are coming from a CM ROM, I have found that I first need to format my partitions with the format 5-6-7 zip (formats /system, /data and /cache) that I attached to this post. If I just did a wipe with CWM, the stock rom would hang on boot for some reason. (And if you are interested in putting the stock ROM on SD, I have instructions in section B below).
A 16. Swapping Internal and External Media Storage
In CM7 there used to be a setting that would allow users to swap internal and external SDs. This was useful for users that had no external SDs and wanted their apps to use internal memory as SDCARD. Starting with CM9, CM changed it so the setting was no longer in settings, but was moved to the CMParts app. And now the CMParts app has been removed. But users can make manual modifications to activate the swap.
There are two ways to do it. One is to edit /system/build.prop to add this line:
persist.sys.vold.switchexternal=1
The second way is to add a property file to /data/property. That way it sticks with a ROM upgrade. Add this file:
persist.sys.vold.switchexternal
And insert the value 1 (with no carriage return) in the file.
After making one of these edits, just reboot and they should be swapped. To return to normal just change the 1 to 0 and reboot again.
But there is a problem with some early versions of CM10.1 and CM10.2 that prevents this from working properly. It has been fixed in the current builds. But if you are running an older version, you can fix it yourself by editing this line:
ro.vold.switchablepair=/mnt/emmc,/mnt/sdcard
to
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
-----
Go to my next post in this thread for Section B. TIPS THAT APPLY TO THE VERYGREEN SD INSTALL OF CM.
Click to expand...
Click to collapse
-----
If you have questions or comments just respond to the thread.
Change Log and SD Tips
CHANGE LOG
09/22/13 - Added A 16 Swapping Internal and External Media Storage
11/23/12 - Added description in B1 on how to use my SD formatting zips
11/02/12 - Added 1.4.3 Stock ROM modified for verygreen SD installation (B11)
10/29/12 - Added verygreen SD formatting zips to the attachments in post two
10/26/12 - Retitled section B3 "Dual Booting" and added more information
10/23/12 - Updated Alternate CWM for SDs to v6.0.1.2 in item B5 and added a v6.0.1.2 bootable SD to item A10 and attached them both.
10/20/12 - Added information about not powering up after a wiped /boot partition to section A3
10/17/12 - Added link to updated SD installation instructions to section B2 and updated the SD installation image to Rev 5 to fix a CM10 issue
09/16/12 - Split out 'Flashing stock ROMs with CWM' to it's own item A15
08/21/12 - The verygreen SD installation image was updated to Rev 4 to accommodate JB zips and larger /data partitions in section B2
08/10/12 - Added a corrected version of the Alternate CWM for SD installs to section B5
08/09/12 - Added BetterBatteryStats link to section A13 and link to Taosaur's simplified SD installation guide to section B1
08/04/12 - Edited section A8 to clean up and include the latest information about recovery bootloops
08/03/12 - Added a modified version of the stock romrestore utility
07/30/12 - Added description of stock automatic partition 2 repair utility (romrestore) to section A12
07/28/12 - Added Skip Oobe (Out-of-Box Experience) for stock Nook Colors to section A
07/24/12 - Added Nook Color Charging to section A
07/11/12 - Added Factory reset with 8 failed boots to section A
07/08/12 - Added Emmc partition repair to section A, split tips into two posts
06/26/12 - Added How the verygreen SD works to section B
06/16/12 - Updated 'SDboot" to Rev 2 to make it easier to use Goo Manager with verygreen SD installs
06/13/12 - Released Rev 3 of the verygreen image for installing CM to SD, correcting an error introduced in Rev 2
06/10/12 - Described how to get out of some recovery flag bootloops (item A8)
06/03/12 - Added CWM 5.5.0.4 bootable SD
06/01/12 - Added Bootable SD cards
05/28/12 - Softkey patch no longer needed
05/18/12 - Added info about customizing navigation bar in phone gui mode.
05/14/12 - Added Recovery Flag bootloops
05/13/12 - Added warning about needing to use new CWM with newer Nook Colors
05/09/12 - Edited Revised SD Image for CM9 to indicate new script prepared
05/02/12 - Added Verygreen SD vs. Racks dual boot SD
04/30/12 - Added NookColorUMS for CM7 and CM9
04/27/12 - Added Using ROM Manager with SD installs
-----
B. TIPS THAT APPLY TO THE VERYGREEN SD INSTALL OF CM
B 1. Installation of CM on SD vs EMMC
How CM is installed for verygreen SDs is significantly different than for installing to internal memory (emmc).
Emmc (Embedded MultiMedia Card) installs are controlled by an installation script built into the zip itself. The zips are hard coded to install to specific partitions on emmc. CWM recovery is used to install to emmc and CWM turns over installation of the zip to that script built into the zip.
For verygreen SD installs there is no CWM recovery, just verygreen's script built into the boot partition. A properly named install zip (update-... cm-.... diff_... or gapps...) must be copied to the boot partition. Installation is controlled by his special script. It takes over installation of the zip, mostly ignoring the script built into the zip itself. It does not backup gapps or format /system. It just copies the new system files over the top of the existing files. Therefore if gapp or other files not in the zip were already there, they are still there and not modified.
Since the script installer does not format anything before installing a new ROM, sometimes it is a good idea to clear things out first. Or maybe your installation is acting up and you want to start fresh without formatting the whole card and losing your media files. You could use the modified Alternate CWM for SD (see item B5 below) to do it, but not everyone has installed that on their SD. So I have prepared and attached some zips as an alternate (and I think cleaner) way to wipe your SD partitions. They can be flashed with any recovery (on emmc or SD) since they are hard coded to format those partitions on SD that are named in the zip title. They have safety checks built in to make sure that you have your partitioned verygreen SD in the slot before they will attempt to format anything. If you are just installing a fresh nightly and you want to keep your data, just wipe system and cache (but that means you need to re-install gapps too). If you are having operational problems and want to keep the same ROM, just wipe data and cache. Or if you are putting on a completely different ROM, wipe system, data and cache.
If you do somehow get into CWM recovery on emmc, be warned that most things you do with it (like flashing or wiping) will happen to emmc, not the SD (except for those zips I just mentioned above). And if you are using older versions of CWM, it will try to place any nandroid backup files to the boot partition of the SD. There is not room there so it will fail. A work around is to use the new CWM recovery (version 5.5.0.4) that allows you to back up to the emmc media partition. Get a flashable zip to install the new CWM to emmc here or attached to the post above. The TWRP recovery also saves backups to internal storage. Get the latest version here. Or you could flash the stock recovery with CWM 5.5.0.4 as Alternate also attached to the post above.
For more information on SD installs, look at my post here.
For those wanting a simplified guide for installing CM7 to SD go Taosaur's excellent blog here. It also works well if you want to install CM9 or CM10 to SD. Just substitute CM9 or CM10 wherever it says CM7. I also have an updated SD installation instruction thread for CM9 and CM10 linked in my signature.
B 2. Revised verygreen SD image file for CM9/CM10
The original image file created by verygreen is an amazing thing. But for CM9/CM10 it has three problems. First, the boot partition is too small to accommodate the larger CM9 install zips. Second there is a problem of duplication of apps included in CM9 and gapps.And third, the naming standard by CM has changed. It no longer begins with update-. That means the existing install script will no longer recognize or install a new nightly when it is copied to the boot partition. Users must rename the file to start with update- if they want the existing install script to work. I have modified the install script to now also install nightlies if they begin with the new standard (cm-). I also added to the script the ability to recognize the new prefix (diff_) that is used by the new Goo Manager program to make an incremental update to an existing ROM. The new script will continue to recognize and install zips beginning with update- to provide backward compatibility. My modified image/script now fixes all these problems. I updated the image to Rev 5 to make it 300MB to accommodate the larger CM10 and JB gapps zips and to make the /data partitions larger for 8 GB and larger SD cards. You can read more about this here. Updated installation instructions for putting CM9/CM10 on SD have been posted along with the latest image here.
B 3. Setting up dual booting on the Nook Color
Dual booting is a really nice feature of the Nook Color. There are three ways that I know of to accomplish dual booting.
a. Leave emmc with one ROM and put one ROM on SD using verygreen's method. This is the scheme I use and recommend for users. This is the one that most of these tips in section B apply to.
b. Leave emmc with one ROM and use a dual boot SD install by Racks where two ROMs are installed on SD. I have discussed that scheme in section B8 below. Actually this scheme is triple booting because there is one ROM on emmc and two on SD.
c. Put two ROMs on emmc. I do not recommend this method as it means having to repartition emmc and that is risky since glitches might happen during set up. Vital information is stored on partition three and you can totally brick your device if you mess that one up and have not made a backup of it. I do have an emmc partition repair thread linked in my signature to help you repair if it messes up. But many users have used this scheme and seem to like it. If you are going to use it follow Taosaur's excellent thread here.
Use the boot menu to select the system you want to run. If you hold the "n" button just after the first tiny screen flash during boot, you will enter the boot menu which allows you to select the system you want to boot.
Below are some specific tips to make your verygreen dual boot work better.
Using the same SD media partition with emmc and the verygreen SD
By default, all ROMs installed on internal memory (stock, CM7, CM9, etc.) always use the first fat partition on your SD as "sdcard". That usually is partition 1. When ROMs are installed to SD using verygreen's method, the default for that ROM is changed to partition 4 of the SD.
If you want ROMs installed on emmc and installed on SD to use the same SD card for storing your media, you need to modify the emmc installed ROM to also use partition 4 of the SD. Go to /etc when booted to emmc and there will be a file named vold.fstab. Open that file in a text editor and look for a line that has 'sdcard auto' in it (without the quotes) and change it to 'sdcard 4' (and for CM10 it will say 'sdcard1 auto'). Save the modified file and reboot. Now both emmc and SD will use the same media partition on SD to save its data. No need to swap SD cards. Use the boot menu to select which system you want to boot up.
For modifying stock emmc you still modify the vold.fstab file but there are two auto's in that line in the file. Change the first one. If you have not rooted your stock, you will need to use one of the flashable zips I have attached below. One zip modifies stock to use partition 4 on the SD for media storage and the other zip returns it to stock settings. Use CWM to flash these zips. If you do not have CWM on emmc, use the bootable CWM SD I have discussed in item A10 above. Be sure to make the CWM SD on a different SD than your ROM is installed on or you will lose everything there. These zips are only to be used on systems that have stock on emmc.
Speeding up booting by modifying the dalvik cache setting.
The verygreen SD installation is set up to share the cache partition with the ROM on emmc. And since normally part of the dalvik cache is stored on the cache partition, every time you boot from one ROM to the other, the system is forced to rebuild the dalvik cache because the system apps are different for each ROM. I have discussed the dalvik cache in section A2 in my first post of this thread. To speed up booting by eliminating this rebuild, make a change to the dalvik configuration. When booted to the SD, create a local.prop file as I discussed in item A1 above and put this line in it:
dalvik.vm.dexopt-data-only=1
This forces the ROM on SD to store the entire dalvik cache on the /data partition. Then when it boots after being on the other ROM, it does not have to be rebuilt.
B 4. Access to the SD boot partition inside CM
One of the annoyances of the SD install was the need to remove the SD and place it in your PC if you wanted to copy a new install zip to the boot partition for installation of a new ROM. I have developed a script that will mount the boot partition in CM so that you can download the new zip directly to the nook and copy it to the boot partition without removing the SD. See my post here to get the script and learn how to use it.
[Edit 6-16-12:] I just added Rev 2 of the script to my original post. This version adds a symlink so that it shows up in the root directory as 'sdboot' as well as under /data/sdboot. This makes it easier to use Goo Manager to download new ROMs. Just change your download directory in Goo Manager to /sdboot/ and it will download the ROM directly to your boot partition. Before you reboot, I would suggest you look in sdboot to be sure it downloaded successfully.
B 5. Using a modified Alternate CWM recovery for SD installs
Usually CWM recovery cannot be used with SD installs because CWM usually modifies emmc, not the SD. But I have modified a CWM recovery (v6.0.1.2) that can be used as an alternate recovery for SD installations. It can be used to modify the SD for everything CWM does EXCEPT FLASHING NEW ROMs to SD. (If you do try to flash a ROM with it, the ROM ends being installed to emmc.) But you can flash other zips (like gapps) as long as it has a generic installer script (and that is almost all install zips except ROM zips and zips that flash new kernels or new recoveries). For flashing new ROMs zips, continue to copy the install zip to the boot partition like you always have and the script in the boot partition will do the installing for you. This CWM will nandroid backup the SD, wipe dalvik-cache or cache, fix permissions, etc.
I am attaching a file to this post (AlternateCWM-SDInstalls-Rev2-v6.0.1.2.rar) which contains the files you need. To install to your SD card, unrar the file and you will have two files, uAltImg and uAltRam. Insert the SD card into your PC and copy those two files to the boot partition. Put the SD card back into the Nook. Installation finished. You can boot to the Alternate CWM for SD by using the boot menu and selecting SD/Alternate or holding the Volume Up/Down keys together while booting. Note that when the CWM is loaded it has "for SD" appended to the title so you can tell it is for the SD install.
B 6. ROM Manager and SD installs
When you install CM to SD, the app ROM Manager (RM) is installed with it. It should not normally be used with the SD install. It generally is geared toward doing what it does to emmc. If you tell it to install a new CWM recovery, it will install it to emmc (but if you want a new CWM recovery on emmc, go ahead and do it). It will find and download ROMs and gapps for you, but if you tell it to install them, it will try to boot into emmc CWM and install the zip to emmc. But it ends up booting into the verygreen SD recovery instead and doing nothing. Then the next time you boot into CWM recovery on emmc, it will finish the install it wanted to do originally (to emmc).
B 7. NookColorUMS for CM7 and CM9/CM10
One of the more useful apps I had for the SD install was NookColorUMS by Samuel Halff. I have a dual boot setup with CM7 on emmc and CM9 on SD. Before I developed the SDboot mount script in item B4 above, I would boot into CM7, run NookColorUMS and I was able to mount my SD boot partition so my PC could see it. That way I could copy the new ROM zip directly from the PC without taking out the SD card. I don't need to do that anymore since I developed the script. But NookColorUMS was still very useful if the ROM download was done on the PC or for looking at any partition on emmc or SD. Or, in my case, after building a new ROM on Ubuntu, I could copy it directly to the Nook's SD boot partition using UMS.
But NookColorUMS would not work on CM9, first because UMS was not enabled on CM9 and later, after the devs added support for UMS, because the lun file locations on CM9 were different than CM7. I started to play with the coding in NookColorUMS and figured out how to patch it to work on CM9. It worked so well I wanted to share it with the community. I contacted Sam and asked for his permission to post my modified app to XDA. He agreed. Thanks Sam!
The app as developed by Sam works perfectly on CM7. The CM9 patched version works very well, but has one quirk. After you go to settings and enable UMS and plug in your USB cable, the "Turn on USB storage" dialog always pops up. If you want to use NookColorUMS you must dismiss that pop-up by hitting the back key. Then you can mount any partition you want with the app. (If you do select that pop-up button, sdcard and emmc are unmounted in CM and mounted in your PC and you must turn off USB Storage in CM to get sdcard and emmc back on CM.) Once you have finished with the PC (with either version of the app), be sure to use the "eject" command in Windows (right click on the drive) to make sure it has finished any writing it may have been doing to the drive. Then you can use NookColorUMS to finish unmounting the drives.
In order for this to work on CM9 you must be running a recent (4/22 or newer) nightly and enable Mass Storage by going to settings, storage, menu, USB computer connection and select 'mass storage'. If that setting is missing or greyed out, your nightly is too old.
I have attached to this post a rar file that contains both the original app for CM7 and my modified app for CM9. The CM9 version also works great on CM10. Install the appropriate version and enjoy.
B 8. Verygreen SD vs. Racks dual boot SD.
These two versions of SD installations are very different. Many people are confused since Racks' new scheme is so popular now. The verygreen install is what I have been describing in the above paragraphs. Racks has prepared a much different setup. He has an image file that has all the partitions already set up to accept two systems on the SD. And he puts a modified version of CWM on his for backing up and flashing new ROMs to them.
How ROMs are installed is very different between the two systems. The verygreen script in the boot partition installs the ROM, correcting the zip install script so that it installs properly on his SD. With Racks' you use his modified CWM to install specially modified ROMs that Racks has prepared. You have to get the ROMs for flashing from his special web site. He has modified each ROM so that the installation script built into the zip puts the ROM on the partitions on his SD. He has the CM7 ROMs configured to go on his system1 and the CM9 ROMs configured to go on his system2. If you by mistake downloaded a CM ROM from somewhere else and try to flash it with his CWM recovery, it will get put on emmc, since all CM zips are configured to do that by default.
(Edit: Racks now has a thread set up where the user can use one of his scripts to modify the standard ROM or gapp files found on other sites so that they install properly on his setup. Look here.)
B 9. How to upgrade your SD installed CM to a larger SD.
You may have installed CM to SD on a relatively small SD and would like to upgrade it to a larger SD without having to lose everything you have set up on the smaller SD. You can do that with disk imaging software. I will give an example of someone who originally installed to an 8GB SD and wanted to upgrade to a 32GB SD. If your sizes are different, just substitute your sizes in the example below.
Get win32diskimager free from the web. Put your 8GB SD in your card reader and open win32diskimager in Windows. Choose the drive that has your SD in it. In the image file box pick a location on your hard drive and give it a name to save the image to. Then click 'read'. It will read the card and create an 8GB image file where you told it to. When it has finished, eject the 8GB card and insert the 32GB card. Select 'write' in win32diskimager and it will burn a clone of the 8GB card to your 32GB card.
Then get the free Mini-Tool Partition Manager software and use it to expand partition 4 on your SD to fill the rest of the empty space.
You should be able to boot that in your Nook just like you did with the 8GB card and all your apps and data will be intact.
(This should also work on Racks' Dual Boot SD. Just expand partition 7 instead of partition 4. I have not tested this though.)
B 10. How the verygreen SD works.
The verygreen image when first burned to the SD makes a single bootable partition on the SD. It is 117MB for the original verygreen image and 300MB in my latest revised image. It contains four files. MLO and u-boot.bin which are bootloader files and uImage and uRamdisk which are the verygreen installation script files.
The first time it is booted, the verygreen script starts with the penguin on the screen and a bunch of scrolling text. It looks at the SD to see if it has been partitioned yet. If it has not, it partitions it into those additional partitions necessary for installing ROMs. In addition to p1 (boot, fat, primary), it creates p2 (system, ext4, primary), p3 (data, ext4, primary) and p4 (sdcard, fat, primary). The sizes of these partitions are determined by the size of the whole SD with the larger sizes being for the largest cards (SDs larger than 16GB). P1 is either 117MB (original verygreen) or 300MB (my updated version). P2 varies between 300MB and 920MB. P3 varies between 500MB and 1,950 MB. And p4 takes up the remainder of the SD. In case you are wondering about the cache partition, the verygreen install uses the existing cache partition on emmc, which it shares with the ROM there.
After partitioning, it looks for a zip to install. If it does not find one, it stops and tells you to put one on the SD. The next time it boots it does the same checking and, since it is now partitioned, it just looks for an installation zip to install. If it finds one, it installs it, dynamically correcting it to install to and use the partitions on the SD, deletes the install zip, then powers off. The first time it installs a ROM, it renames those uImage and uRamdisk verygreen files to uRecImg and uRecRam and they become the verygreen recovery files. And it copies new MLO, u-boot.bin, uImage, and uRamdisk files from the zip. The new MLO and u-boot.bin are updated versions of the bootloader files which has the new boot menu. uImage and uRamdisk become your ROM kernel and ramdisk. These are what normally will load in the future to start the ROM.
So if you look at the boot partition now in the PC, it has six files in it. The new MLO, u-boot.bin, uImage and uRamdisk from the latest installed ROM zip. And it will have uRecImg and uRecRam which are the renamed original script files that are now your SD recovery.
Now, with the disk partitioned and the ROM installed, ordinarily, after the cyanogenmod or Cyanoboot logo comes up, it boots by default to CM via the uImage and uRamdisk files. If you intercede with the boot menu and tell it to boot to SD recovery, it looks for uRecImg and uRecRam and loads the verygreen recovery. The penguin comes up again and the script does it's checking and looks for a zip to install. If it finds one, it installs it and deletes the file when finished and powers off. If it cannot find one, it just powers off.
So anytime you want to install new ROMs, gapps or other zips, just copy those files to the boot partition and boot to SD recovery and the verygreen script will install them and delete the zips when successful. In the original verygreen script, install zips must be named beginning with update- or gapps-. In my newest revised image and script, they can be named beginning with update-, gapps-, cm- or diff_ and the script will recognize and install them.
B 11. Stock 1.4.3 ROM on verygreen SD
I have some good news for a few users. I have successfully modified the 1.4.3 stock B&N ROM zip to be flashable to a verygreen SD. That means you can put CM on emmc and still have your stock ROM available if you want to boot to it. Or you can just put it away for future use. Then you can use another SD to run a different version of CM on SD.
The modified ROM zip must be installed with CWM or TWRP recovery to the SD. Don't use the verygreen boot partition installer. A newer version of TWRP or CWM recovery (newer than 3.2.0.1) must be used. Those older versions require that you have normal SDs in the slot and you will have your verygreen SD there. The newer versions can find the installation zips on internal memory (emmc media). The recovery can be on emmc, bootable SD or Alternate CWM on your verygreen SD. Version 5.5.0.4 for emmc and version 5.5.0.4 and version 6.0.1.2 of a bootable SD are all attached to my post above.
The ROM zip is hard coded to install to the partitioned verygreen SD. I have built in checks in the installer to make sure you have the verygreen SD in the slot and it has been partitioned. It can even have an old CM ROM on it as the installer will format the system and data partitions on the SD in preparation of putting the stock ROM on it. But anything you have on the SDCARD partition (p4) is left intact.
After flashing the stock ROM, you will have to go through B&N registration just like you would if it were installed to emmc. But be warned if someone else previously registered the device with B&N, you can't register it yourself unless the prior owner has de-registered it. The prior user can de-register it by logging into their B&N account on the web and selecting "erase and de-register" for that device under their account settings. B&N tracks the device by serial number and it will display the same serial number as it would on emmc. If you can't or don't want to register with B&N, see my item A14 above for instructions on how to skip registration. It just means you will not be able to buy books or apps from B&N.
After you have successfully registered the software on SD, you can move the SD to another device with a different serial number and it still works. I'm not sure of the long term implications with B&N of doing that. You may run into trouble when ordering new books or software through their store.
And here is even more good news. I was able to modify GMPOWER's Manual Nooter 5.08.20 zip to also work on the verygreen SD. So now you can have rooted stock on SD. I have contacted GMPOWER and he is ok with me posting a link to a server where I have placed the modified zip. Thanks, GMPOWER.
And I have prepared a zip to add the dalingrin OC kernel and apps2SD support to rooted stock on SD. And I added a zip to block updates even if you choose not to root.
So the procedure to get this working is to prepare a verygreen SD using the image file attached to my SD installation instructions thread here (generic-sdcard...). Then boot it at least once with the SD in the Nook so the SD can partition itself. If you have an existing verygreen SD prepared, you can skip these two steps.
Download and copy the zip files linked below to your internal storage (emmc media). Boot to recovery and insert the prepared verygreen SD into the Nook. Find the ROM zip on internal storage and install it. It will automatically get put on the SD. It will first format the system and data partitions on the SD and then install the ROM. Boot to the SD and the new stock ROM should load.
Follow the directions to register with B&N. Once you have registered you can stop there if you are satisfied with plain stock. Let B&N finish uploading their free books to you before you do anything else. This could take several minutes depending on your internet speed. If you decide to stay with unrooted stock, be warned that if B&N decides to automatically update you to a new version in the future, it may mess up whatever you have installed on emmc. Therefore I recommend that you install the Block Updates zip which blocks OTA updates. If you install Manual Nooter you do not have to install Block Updates separately since it is included in Manual Nooter.
To install Block Updates, Manual Nooter or OC/apps2SD support, install the zips to the SD with recovery just like you did the ROM. If you install Manual Nooter, it has gapps and Market with it so you must register them with Google. And you need root if you want to use the OC and apps2SD support, plus you will need a program like SetCPU to adjust the processor.
You can get the modified 1.4.3 B&N stock ROM zip here, the modified Manual Nooter zip here, the modified OC/apps2SD zip here, and the modified Block Updates zip here (all four modified for verygreen SD installation).
B 12. SD Card Quality
There has been a lot of discussion among Nook Color users about quality of SD cards needed to run a ROM. The consensus has been that SanDisk Class 4 cards work the best. (I have also found that the new SanDisk Ultra Class 10 cards work really well too.) The issue is that the card needs fast random small file read/write ability. And other brand cards, even if rated a higher class, do not fair well with this attribute. The symptoms of a bad card are sluggish performance, apps force closing and general lock-ups. There has been a lot of benchmarking of various brand and speed classes in a thread here.
After I burned your modified Verygreen image file I used EaseUS Partition Master to set the partition to whatever size you need. I then copied the CM9 zip and the gapps zip into the boot directory as well as your modified CMW files. Worked great.
A couple of things I've found recently:
1. To make ADB over USB work with the NC on Linux, I needed to run
Code:
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices
(Found at nookdevs)
2. To modify a stock image so you can flash it from CWM and still have CWM on the emmc, you need to modify one file in the zip: META-INF/com/google/android/updater-script
First change line 1 to
Code:
assert(getprop("ro.product.device") == "zoom2" || getprop("ro.build.product") == "zoom2" || getprop("ro.product.overall.name") == "NOOKcolor" || getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore") ;
Then from the bottom of the file, delete the lines
Code:
package_extract_file("kernel-recovery", "/boot/uRecImg");
and
Code:
package_extract_file("ramdisk-recovery.img", "/boot/uRecRam");
I found the first edit here; the second I figured out for myself after I missed it the first time and needed to re-install CWM.
Hope this is useful to someone.
Thanks for your many posts all over the forum.
I am a noob, and you've helped. I had a question about your post here.
I see you did this in April. Do newer builds of CM9 automatically fix the naming problem with the nightlies?
As far as I know, I downloaded a January version, and then added a nightly, and I think the nightly installed correctly.
Thanks!
I just keep hacking away...
RevTom said:
Thanks for your many posts all over the forum.
I am a noob, and you've helped. I had a question about your post here.
I see you did this in April. Do newer builds of CM9 automatically fix the naming problem with the nightlies?
As far as I know, I downloaded a January version, and then added a nightly, and I think the nightly installed correctly.
Thanks!
I just keep hacking away...
Click to expand...
Click to collapse
Depends on where you get your nightly. If you get it at sphsolutions, it is named properly (update-) and will install with the January edition of the image. If you get it at techerrata, they are named cm- and will not install unless you rename to update- or use my new image.
Sent from my NookColor using Tapatalk
I was able to bring a new nook color out of a boot loop using your CWM (5.5.0.4)! Thanks so much for taking the time do document / post this information and the clear/concise way it is done.
Thanks again.
I have no idea what happened. One day my NC was fine. Next time I tried to use it, it varies from bootloop to a dead screen. On rare occasions it will boot, but I get various gapps throwing me f/c right and left.
Let's see, I'm on an older CM7 nightly from a couple months back ... I believe nightly cm_encore_full-253m.zip.
Anyway, I've tried various things from formatting system, cache, etc ... but all fail. I've tried the New Bootable CWM Recovery SD (A10) as well as the CWM update (A8), but not solving anything. Though the CWM update appears to install, it changes nothing as when I get back into recovery, I'm still on the old 3.2.0.1. I've tried to install 7.2 and though it appears to go through the install process okay (i.e. no errors), when I'm infrequently able to reboot nothing has changed.
I've tried the 8 interrupted boots to no avail ... possibly because the boot process fluctuates from going to recovery or bootlooping or black screen or succeeding ... so the 8 step process just doesn't work.
Its though something (system, emmc, or ???) has corrupted and locked me into where I was without allowing anything new to install or change?
Any other suggestions on what I can do to wipe, go back to factory 1.0.1 stock, and start over? The restore procedures that I have seen require formatting system, cache, etc. but as far as I can tell, noting is actually formatting anything.
I'm usually able to back my way out of any problems, but since I don't know how this issue happened when my NC was fully charged and off ... turning into a battery dead NC for unknown reasons, not sure what next since I'm not making any headway.
cvhovey said:
I have no idea what happened. One day my NC was fine. Next time I tried to use it, it varies from bootloop to a dead screen. On rare occasions it will boot, but I get various gapps throwing me f/c right and left.
Let's see, I'm on an older CM7 nightly from a couple months back ... I believe nightly cm_encore_full-253m.zip.
Anyway, I've tried various things from formatting system, cache, etc ... but all fail. I've tried the New Bootable CWM Recovery SD (A10) as well as the CWM update (A8), but not solving anything. Though the CWM update appears to install, it changes nothing as when I get back into recovery, I'm still on the old 3.2.0.1. I've tried to install 7.2 and though it appears to go through the install process okay (i.e. no errors), when I'm infrequently able to reboot nothing has changed.
I've tried the 8 interrupted boots to no avail ... possibly because the boot process fluctuates from going to recovery or bootlooping or black screen or succeeding ... so the 8 step process just doesn't work.
Its though something (system, emmc, or ???) has corrupted and locked me into where I was without allowing anything new to install or change?
Any other suggestions on what I can do to wipe, go back to factory 1.0.1 stock, and start over? The restore procedures that I have seen require formatting system, cache, etc. but as far as I can tell, noting is actually formatting anything.
I'm usually able to back my way out of any problems, but since I don't know how this issue happened when my NC was fully charged and off ... turning into a battery dead NC for unknown reasons, not sure what next since I'm not making any headway.
Click to expand...
Click to collapse
It really does sound like nothing is taking. You should have been able to go to the new CWM on emmc. But you are still on the old CWM and your formats fail. So, I suspect that one or more of your partitions got corrupted somehow and everything is read only. I do not know a lot about how to fix those. But others here are very adept at that. DizzyDen for one. You might search xda nook color for info on repairing partitions. I know adb is often used for that. Sorry if I'm not much help, but maybe someday when I learn a little more on how to fix them I can help someone.
Sent from my Nook Color running ICS and Tapatalk
Thx ... I'll continue searching and try to find something to fix the partitions.
One question. What is meant by the term " hard shut down "? I take it that refers to shutting system down using power button ? How else would one accomplish this shut down of the NC ? Uggg I'm such a NOOB !
Sent from my SCH-I500 using XDA
icemanwbs said:
One question. What is meant by the term " hard shut down "? I take it that refers to shutting system down using power button ? How else would one accomplish this shut down of the NC ? Uggg I'm such a NOOB !
Sent from my SCH-I500 using XDA
Click to expand...
Click to collapse
Hard powering off means holding the power key for like 15 seconds until the device goes completely off, not just to sleep. A short touch does not turn it off, it just puts it to sleep. If you are in a ROM, the proper way to turn the power completely off is to hold the power button until a menu pops up and you select 'power off'. If you are in CWM you should go to the menu item that says 'reboot' and it will. You want to shut your devices down properly so they finish any tasks they have running before shutting down. It's just like on your PC, you don't unplug the power cord on the PC when it's running, you tell it to shut down with the start menu. Hard powering off is just like pulling the plug on a PC. Sometimes it is necessary if things are locked up, but it is not the preferred way to do it.
Sent from my Nook Color running ICS and Tapatalk
Ahh OK. Gotcha ! Love your guide, been using it since I got my NC
I'm pretty good at android flashing with phone ( Samsung fascinate running ICS 4.0.4 ! )
One more thing, do I need to do anything special now that I have flashed the CWM 5.0.0.4 recovery ?
Thanks a million. People like you make XDA a treat !! :thumbup:
Sent from my SCH-I500 using XDA
icemanwbs said:
One more thing, do I need to do anything special now that I have flashed the CWM 5.0.0.4 recovery ?
Sent from my SCH-I500 using XDA
Click to expand...
Click to collapse
No, just leave it there in case you need it in the future. Any time you tell your nook to go to recovery, it will be there waiting.
Sent from my Nook Color running ICS and Tapatalk
Okay, I'm REALLY a noob at this...
I have tried my hardest to follow the threads about loading CM7 onto my mSD card in order to allow dual-booting stock (via emmc) and CM 7.2 stable via mSD (an 8GB Samsung class 6), but I feel I really f'd things up.
How I got to here:
1. I tried following this thread:
http://forum.xda-developers.com/showthread.php?t=1000957
Got to where it should have run the cm-7.2.0-encore.zip, but wouldn't find it.
2. Tried renaming to update-cm-7.2.0-encore.zip, as well as udpatei-cm-7.2.0-encore.zip.
3. Started reading more (didn't do that at first because it seemed complete enough).
4. Found your posts towards the end saying things have changed and to go to your tips page, so I did.
5. Read that I should use CWM 5.5.0.4-bootable_SD.img instead WITH SDCard-BootFiles-Rev3.
6. Ran Win32DiskImager with CWM 5.5.0.4...img to image the mSD.
7. copied the Rev3 files into the mSD as well as the cm-7.2.0.encore.zip.
8. inserted the mSD into the NookColor.
9. Booted into CWM.
10. selected the cm-7.2.0-encore.zip and said I'm sure.
11. It installed, i rebooted.
12. It looks like it installed onto the emmc as all my old settings are still there (wireless networks, etc.).
13. Immediately started force closing some process apps.
Now what? I feel I'm in a bad place and need to get back to having a stock 1.4.2 NC on the emmc and CM7 (stable) on SD. Maybe I missed a step (as great as the effort has been to get all this automated and setup, I feel it's still not straight forward enough for me ). Any and all help is appreciated.
P.S. Also, Is see CM9 mentioned, but no links as to where to get it for the NC (No encore build either). Is this still beta? If so, I'll stick with CM7 for now.
Thanks again in advance.
corvair64 said:
I have tried my hardest to follow the threads about loading CM7 onto my mSD card in order to allow dual-booting stock (via emmc) and CM 7.2 stable via mSD (an 8GB Samsung class 6), but I feel I really f'd things up.
How I got to here:
1. I tried following this thread:
http://forum.xda-developers.com/showthread.php?t=1000957
Got to where it should have run the cm-7.2.0-encore.zip, but wouldn't find it.
2. Tried renaming to update-cm-7.2.0-encore.zip, as well as udpatei-cm-7.2.0-encore.zip.
3. Started reading more (didn't do that at first because it seemed complete enough).
4. Found your posts towards the end saying things have changed and to go to your tips page, so I did.
5. Read that I should use CWM 5.5.0.4-bootable_SD.img instead WITH SDCard-BootFiles-Rev3.
6. Ran Win32DiskImager with CWM 5.5.0.4...img to image the mSD.
7. copied the Rev3 files into the mSD as well as the cm-7.2.0.encore.zip.
8. inserted the mSD into the NookColor.
9. Booted into CWM.
10. selected the cm-7.2.0-encore.zip and said I'm sure.
11. It installed, i rebooted.
12. It looks like it installed onto the emmc as all my old settings are still there (wireless networks, etc.).
13. Immediately started force closing some process apps.
Now what? I feel I'm in a bad place and need to get back to having a stock 1.4.2 NC on the emmc and CM7 (stable) on SD. Maybe I missed a step (as great as the effort has been to get all this automated and setup, I feel it's still not straight forward enough for me ). Any and all help is appreciated.
P.S. Also, Is see CM9 mentioned, but no links as to where to get it for the NC (No encore build either). Is this still beta? If so, I'll stick with CM7 for now.
Thanks again in advance.
Click to expand...
Click to collapse
Ok, your first mistake was copying the rev 3 boot files to the CWM SD. You should have copied them to the verygreen SD. That way it upgrades the older version to my newest version so it reads the newly named files correctly. And if you wanted CM 7.2 on SD you should have copied that zip there too. (You probably wiped out your verygreen SD to make the CWM SD and that caused your confusion.)
The second mistake was when you used my CWM SD to flash the CM 7.2. It put it on emmc replacing your stock. And if you do that you should have done a factory reset first as the apps as installed on stock do not work well on CM7. That's why you are getting the force closings.
If you want to keep CM7 on emmc, just boot to my CWM card and do a factory reset. That clears out the apps as installed by stock. That also means you will have to install all your apps again. Also you should install gapps. Go to goo.im/gapps and select the latest gingerbread version, download it and flash with my CWM card.
If you are happy with CM7 on emmc, you should flash CWM to your emmc so you don't need my card anymore (see the last paragraph in my item B1 for instructions 'get the flashable version here') Then you can reformat the CWM card to use as a data card for your emmc installed CM 7.2.
If you truly want to return to stock on emmc and CM7.2 on SD, let me know and I will walk you through it. It is a lot more work.
Also CM9 is available but is still in development. If you want that I can direct you to that too.
New question. In settings/battery use.....it shows " PHONE IDLE " 40%....and "CELL STANDBY" 30%.....since obviously we don't need these, how do I get rid of them ??? Lol;
Sent from my SCH-I500 using XDA
icemanwbs said:
New question. In settings/battery use.....it shows " PHONE IDLE " 40%....and "CELL STANDBY" 30%.....since obviously we don't need these, how do I get rid of them ??? Lol;
Sent from my SCH-I500 using XDA
Click to expand...
Click to collapse
You don't need to. Those are false readings. Just leave them there.
Help. I flashed cm9 onto SD card. ( from cm7 ). Said was successful, then when I went to re boot, on boot menu, I chose" SD Card Normal" and now its just stuck there.
OK....I got it to boot into cm9...! . Now screen becomes unresponsive while in use and I have to keep re booting.
Sent from my SCH-I500 using xda app-developers app
icemanwbs said:
Help. I flashed cm9 onto SD card. ( from cm7 ). Said was successful, then when I went to re boot, on boot menu, I chose" SD Card Normal" and now its just stuck there.
OK....I got it to boot into cm9...! . Now screen becomes unresponsive while in use and I have to keep re booting.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Sometimes it is necessary to wipe things when going from CM7 to CM9. That is difficult to do with the SD install. I recommend you go to my item B5 in my tips thread and install the alternate CWM that has been modified to work with SD installs. You can do a factory reset with that and it cleans up the SD. Also wipe system with it. It will not effect emmc. You may want to backup with Titanium Backup first to save your installed apps. Then reinstall the rom and restore your apps with Tibu.
Related
I'm a noob with not enough privilages to post over in the developer's forum, so posting here.
I've successfully imaged and booted to CM7 using verygreen's project:
http://forum.xda-developers.com/showthread.php?t=1000957
Next step was to try adding/installing gapps and using recover. I've tried a few different times doing a few different things, but all end up rebooting (with SD in the NC) to the original boot of the NC, as if out of the box. I get the hand going over to the android and having to "Set Language" and wifi.
Not sure what I'm doing wrong and it looks like others got it to work.
Any help?
Have you actually booted into CM7? The nook boots first to the SD card, so if you can't boot now into CM7 that means that something has changed on the SD card. In other words, on boot the nook looks for something useful (like a bootable OS) on the card and if it can't find it boots to internal (original B&N OS).
So, do a normal power up and see if you boot into CM7 on the sd card. If so, see below about booting in recovery (once you've added the google files). If not, something's amiss with the image on the card.
YOu may be having a problem booting into recovery -- this is pretty common. It can be tricky timing the release of the buttons. Follow the directions on verygreen's post carefully. Push the N button first, then power, count off about 6 seconds and make sure that you see the message before releasing. Took me a few tries to get the recovery screen instead of booting normally.
I can tell you that I've done this a few times and it does indeed work. The only tricky part is timing to button thing when booting into recovery.
Yep, I did boot into CM7... The wallpaper changed and there were new icons, of which I can't remember at the moment.
I know what you are saying about entering recovery mode... I think I got that set. I can see when entering recovery mode, as the penquin icon is shown and then all the messages come up, including expanding the zip files.
My problem is getting the gapps included. I've tried just copying over the gapps zip file and do recovery with that. I've tried copying both the CM7 nightly and the gapps zips and do recovery. I also noticed the instructions:
•Get u-boot.zip file from attachment in this post: http://forum.xda-developers.com/show...&postcount=153
•Unpack the u-boot.bin file and put it onto parttion 1 of the SD card instead of the one there.
•Rename file named uRecImage on the first partition to uRecImg (doh!)
•Get this uRamdisk file, rename it to uRecRam and then put the result to the 1st partition on the uSD card instead of the file with the same name there
I've also done that... still boots to as if it is a brand new, out of the box Nook. I take it that means the SD is messed up. So I'm doing something wrong in how to get the gapps on.
Sounds like the easiest way for you is to start over.
Re-image your card with verygreen's 1.1 from the beginning of his post.
Then download the version of CM7 you want (verygreen's or rc4 or whatever)
add this .zip to the sd card, download gapps and also add this to the sd card.
Insert into nook and boot.
You have to put these zips on the sd card BEFORE you boot into CM7 the first time. This is why you have to re-image.
This is what I did and everything worked great. Skip the gapps login until you have wifi setup of course and everything should be fine.
Yup, sounds like danbutter has it right. I know how frustrating this is, but it really is worth it.
You may have problems prepping your SD card to re-image because of partitioning. One way to start with a really clean slate is to download Paragon Partition Manager (the free addition) and totally wipe all the existing partitions. Windows disk manager won't do it.
robedney said:
You may have problems prepping your SD card to re-image because of partitioning. One way to start with a really clean slate is to download Paragon Partition Manager (the free addition) and totally wipe all the existing partitions. Windows disk manager won't do it.
Click to expand...
Click to collapse
I don't know exactly what it is with this, but I have never had this issue and I have re flashed a couple sd cards many many times playing with this and all I have ever done was select the new image and write it to the card.
Is this something to do with certain card readers or what?
I'm using a five year old HP laptop and its built in card reader.
Just curious
Not a total NooB to Android -- bought and rooted an original droid about a year ago -- but still trying to grok all that is the Nook Color.
Currently I'm running CM7 from the sdcard. I'll blow it to emmc eventually but for now I have some reasons to keep the stock B&N ware available.
I'd really like to have Clockwork Recovery available from my CM7 environment but I haven't been able to make that happen.
Originally just used ROM Manager to try to install it. Seemed to go cleanly but things didn't behave right. Asked here and was told that RM won't install CMWR cleanly.
So I blew everything back to oblivion, rebuilt my CM7 sdcard from the ground up and then pushed CMWR 3.0.1.0 to the sdcard via adb.
But I still don't seem to be able to reach CMWR with the sdcard installed. Using the CM7 reboot menu and selecting Recovery just reboots me right back into CM7.
Powering down then powering up with the power & N key held down takes me to the standard recovery.
Is it possible to boot into recovery on the sdcard? If so, how?
I'm not sure if it's possible to install CM7 and CWM on the SD card together. I know you can have one SD card with each on it. I think this thread will get you a CWM SD image that can create SD cards. What are you trying to accomplish?
Now if you install to EMMC then you can certainly have CM7 and CWM and possible a dual boot setup
adealey said:
Is it possible to boot into recovery on the sdcard? If so, how?
Click to expand...
Click to collapse
Yes. I have my nook set up so that while booting, a boot menu pops up so that within 5 seconds, if I push a button, I can choose four boot options:
1. normal internal memory ROM (for me, that's stock)
2. CWM from internal memory
3. CM7 (with tablet tweaks) from SD card
4. CWM from sdcard (to backup CM7).
If I touch nothing after 5 seconds, it boots up to the internal ROM (although I believe that changing a 1 to a 0 in a text file on the sdcard boot partition can change this)
I'm 99.9% that you can get everything you need to run CM7 and CWM from the sdcard in this thread:
http://forum.xda-developers.com/showthread.php?t=998861
Hextall said:
Yes. I have my nook set up so that while booting, a boot menu pops up so that within 5 seconds, if I push a button, I can choose four boot options:
1. normal internal memory ROM (for me, that's stock)
2. CWM from internal memory
3. CM7 (with tablet tweaks) from SD card
4. CWM from sdcard (to backup CM7).
If I touch nothing after 5 seconds, it boots up to the internal ROM (although I believe that changing a 1 to a 0 in a text file on the sdcard boot partition can change this)
I'm 99.9% that you can get everything you need to run CM7 and CWM from the sdcard in this thread:
http://forum.xda-developers.com/showthread.php?t=998861
Click to expand...
Click to collapse
That's EXACTLY what I want!
I'm plowing through that thread now to try to pick out all the pieces I need to make it happen. Wish me luck!
So I'm booting from a SD card into CM7 7.0.2 currently. I'm using a custom boot file so I can choose to hold down the home screen button if I want to boot into the stock 1.2 OS instead.
I only have this single 2gb SD card to use atm. What would be the proper process to update to the nightly 69 build from here? I need to make sure that when I update, my current SD card is in there and that's where the install is saved to. I had an issue prior where I booted with an alternate SD card (which I no longer have) and it installed to the eMMC. That wasn't fun as I had to do a complete restore.
Thanks!
I am booting from an SD card.
To update, I put the uSD card in the PC and then just copy the new build zip file to the uSD card.
Then I put the card in the Nook, press the N + power button and when I see the "Touch the Future of Reading", count to 4 and release the buttons. Don't count to slow. I noticed one time the TTFOR disappeared and it booted into the Nook software. I just shut it down and did it again.
The Nook will automatically see the new zip file, expand it and load the new build. Once done, it will delete the zip file from the uSD card.
I noticed the newer builds automatically reboot the unit but if yours doesn't, it will stop at "Flushing Cache" and sit there. Leave it alone until the screen goes dark (a couple of minutes) and then reboot it (N + power button). You should get the Android. and about a minute later the CM7 spinning logo.
You are updated. And you don't lose any apps or data either!
If you are overclocking, I would set it back to 800MHz before you do this as a precaution.
Finally, there is an easy way to add overclocking to a new build. You just need the overclock zip file, the new build and WinRAR 3.80. Let me know if you want that info.
Well that worked as you said, thanks! I did have one problem but I fixed it myself. As I mentioned, I have a modified boot file which loads the Nook OS if I hold the N button. So trying to get into recovery or have the CM7 noticed the .zip file by holding Power+N didn't work. Luckily I still had the original u-boot.bin file and was able to copy it back onto the SD card and then I was able to get the update installed.
As to the OC, I assume I'd just put it back on the same way I did with the original.
I've read your post, and a few others but I'm either not understanding (my money is on this one!!!!) or missing a step.
I'm running Nook Color Stock 1.2 on emmc and CM 7 on the SD card.
I've tried using ROM Manager as well as copying the latest nightly to the /boot partition of the SD card.
If I boot into recovery and update the zip from the SD, I always end up over-writing the emmc of the nook, losing stock and all my apps, instead of the CD card being updated.
What am I doing wrong?? Would like to upgrade to the latest nightly. But I don't want to screw up stock (hate having to restore and redownload all the apps every time).
Thanks
No matter what I do, I always end up over-writing the emmc instead of updated the SD card.
phoenix1972 said:
I've read your post, and a few others but I'm either not understanding (my money is on this one!!!!) or missing a step.
I'm running Nook Color Stock 1.2 on emmc and CM 7 on the SD card.
I've tried using ROM Manager as well as copying the latest nightly to the /boot partition of the SD card.
If I boot into recovery and update the zip from the SD, I always end up over-writing the emmc of the nook, losing stock and all my apps, instead of the CD card being updated.
What am I doing wrong?? Would like to upgrade to the latest nightly. But I don't want to screw up stock (hate having to restore and redownload all the apps every time).
Thanks
No matter what I do, I always end up over-writing the emmc instead of updated the SD card.
Click to expand...
Click to collapse
All you have to do is put the update zip on the boot part' of the sd card and boot up the sd install like normal and it'll see the zip and automatically flash it for you.
I've tried using ROM Manager as well as copying the latest nightly to the /boot partition of the SD card.
Click to expand...
Click to collapse
If you're booting CM7 off uSD, you can forget about the "ROM Manager".
phoenix1972 said:
I've read your post, and a few others but I'm either not understanding (my money is on this one!!!!) or missing a step.
I'm running Nook Color Stock 1.2 on emmc and CM 7 on the SD card.
I've tried using ROM Manager as well as copying the latest nightly to the /boot partition of the SD card.
If I boot into recovery and update the zip from the SD, I always end up over-writing the emmc of the nook, losing stock and all my apps, instead of the CD card being updated.
What am I doing wrong?? Would like to upgrade to the latest nightly. But I don't want to screw up stock (hate having to restore and redownload all the apps every time).
Thanks
No matter what I do, I always end up over-writing the emmc instead of updated the SD card.
Click to expand...
Click to collapse
You are probably using the install zip option. You do not do this. You just put the zip on the boot partition, boot into recovery and the reboot. DO NOT flash anything.
Sent from my LG Optimus V using Tapatalk
Let me try to clarify... when they are saying boot into recovery... they aren NOT meaning Clockwork Recovery... they mean using the boot menu (press "n" button when you see the Cyaonogen logo) and selectin boot from SD card and Recovery. That is the SASD rocovery (install) mode and will install the update zip file from the root of the boot partition.
Thanks for clarifying DizzyDen!!! That's the part that I was screwing up
Like I just screwed up the Stock again...but that's alright...live and learn
Updating the latest right now...then I'll be putting stock back on emmc
Thanks again for the clarification
Updating to the latest nightly on CM7 SD installation?
I'm a newbie so please have some patience. I'm trying to do the same thing, update my cm_encore_full-159.zip to cm_encore_full-177.zip. I boot from a microsd card to Android. When I install it I pushed a button during the early boot process and went to a menu. Changed "boot device" from "emmc" to "SD" and "Normal" to "Alternative". When I turn on the Nook Color after it installs, I do nothing and it boots to Android but if I put a button it goes to the menu where I push the volume down button 3 times and I boot to the stock Nook Color. So, if I copy the cm_encore_full-177.zip to my microsd card, go to the menu, change the "emmc" to "SD" and "Normal" to "Alternative, this should update my 159 to 177 without losing any apps, email, etc.? Thanks
themofoman said:
I'm a newbie so please have some patience. I'm trying to do the same thing, update my cm_encore_full-159.zip to cm_encore_full-177.zip. I boot from a microsd card to Android. When I install it I pushed a button during the early boot process and went to a menu. Changed "boot device" from "emmc" to "SD" and "Normal" to "Alternative". When I turn on the Nook Color after it installs, I do nothing and it boots to Android but if I put a button it goes to the menu where I push the volume down button 3 times and I boot to the stock Nook Color. So, if I copy the cm_encore_full-177.zip to my microsd card, go to the menu, change the "emmc" to "SD" and "Normal" to "Alternative, this should update my 159 to 177 without losing any apps, email, etc.? Thanks
Click to expand...
Click to collapse
1. in bold text above... select "Recovery" not Alternative...
2. you either move the SD to your computer to put the update on the boot partition of the SD or you have to mount /dev/block/mmcblk1p1 to a directory (I created /sdcard/boot for this) and push the update to the BOOT partition.
Nook Color How to Update to CM7 Nighthly
Good Day,
What a fantastic website! I am new to the forum. Could you please answer the questions or provide a link to the answers?
1. What utility and procedure would I follow to back up the stock Nook Color partitions in ROM to include the stock Nook Color apps I have installed?
2. What utility and procedure would I follow to back up the apps I have purchased from the Android Market place for CM7 running off the SD card?
3. I have update-cm-7.0.0-encore-signed.zip installed. I want to update to cm_encore_full-177.zip. Do I use win32image to "burn" the new nightly to the SD card? Or, do I drag and drop the new
nightly to the SD card? If yes, on which directory (folder) on the SD card do I place the new nightly build?
Thank you!
atl10spro
Try my best to help.
1. I don't deal with stock, so can't help here.
2. I never intend to run any backup when booting off uSD, can't help.
3. Assuming you're booting off uSD, then just copy the new .zip file (do not rename, do not unzip) into the boot partition (root folder) of the card. Insert it into the NC, boot it into Recovery. When it's in recovery mode, it'll fully automatically do the update then deletes the .zip file, you don't have to do anything, just wait until it shuts itself down then you power it up.
I am running the following - CM7 - nightly build 08022011 on SD - Dalingrin's OC kernel 2.6.32.9 @ 1200MHz NOOKcolor
I am trying to update to a newer nightly build. I have the file downloaded on the SD card but can't get it to update.
Where does the file have to go?
I tried to reboot into recovery mode and that didn't do anything.
Any help would be great.
***I must have been sleepy yesterday as I got it to work now....
removed ./10chars
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
I want to install CM11 onto my external SDcard, not touching the B&N stock OS or rooting it in any way , so as not to void the warranty. #1 is this possible?
I built the SDcard, creating partitions: BOOT (0x0c FAT32 LBA & set Active),SYSTEM, DATA partitions.
I downloaded Succulent's "cm_ovation_11.0_02JUL2014_HD_SDC" file, unzipped it and copied the 6 files from it (MLO first)
Booted the HD+ but it didn't boot to sd,-- only did the normal Nook boot and hung at 99% loading the nook OS.
I then saw something about needing to install CWM Recovery first and boot that, so I located a download for CWM, but found it contains the same files as Succulent's "cm_ovation......" file (MLO, etc.). So if I were to extract that to the BOOT partition, I'd overwrite what I extracted from his zip.
So I'm missing some pieces to the trick....
Try using bokbokan's version and instructions here:
http://forum.xda-developers.com/showthread.php?t=2583952
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Try using bokbokan's version and instructions here:
http://forum.xda-developers.com/showthread.php?t=2583952
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thank you, but I had customized my partitions, and was hoping to stay with them, versus overwriting them with an image someone made that has pre-picked partitions. That is, unless somehow I can resize the partitions he made (and at which point in the process?) On mine I had 4 partitions. the last one was just an NTFS one, 6GB, I was hoping to keep available for just general storage, not necessarily for KitKat's use.
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for pointers on creating CM11 SDcard with customized partition sizing. You should be able to create and maintain a 4th partition (but you'd need to figure out how to mount the partition so as to make it accessible to Android and/or your PC OS).
cm11 boot to sd
Ok, I must be missing some simple step.
In that link Digimax sent me, I believe I followed all steps. I ended up with these files on the BOOT partition (as seen in windows):
The 6 files extracted from sdcard-ovation-cm11.0-v1.img
pa_gapps-modular-mini-4.4.4-20141121-signed
cm-11-20140804-UNOFFICIAL-bok-ovation
a folder called LOST.DIR (not sure what that's from)
I choose "Boot to CWM Recovery" and I first did a backup. Then I selected "Install ZIP" then "Choose zip from sdcard" & I see
/sdcard/
- 0/
- clockworkmod/
That's it. Nothing else. Selecting either one of these displays no zip files. What am I doing wrong? In that post, step 4 it mentions "pair" of zip files. I assume though the 2nd item in the "pair" is the Gapps zip. Cuz for HD+ all I see is one file: cm-11-20140804-UNOFFICIAL-bok-ovation. (it doesn't have "sgt7" in the name anymore.) I assume I don't need the one for the regular HD model.
baytee said:
Ok, I must be missing some simple step.
In that link Digimax sent me, I believe I followed all steps. I ended up with these files on the BOOT partition (as seen in windows):
The 6 files extracted from sdcard-ovation-cm11.0-v1.img
pa_gapps-modular-mini-4.4.4-20141121-signed
cm-11-20140804-UNOFFICIAL-bok-ovation
a folder called LOST.DIR (not sure what that's from)
I choose "Boot to CWM Recovery" and I first did a backup. Then I selected "Install ZIP" then "Choose zip from sdcard" & I see
/sdcard/
- 0/
- clockworkmod/
That's it. Nothing else. Selecting either one of these displays no zip files. What am I doing wrong?
Click to expand...
Click to collapse
It does not appear that you've made any mistake. It's possible that bokbokan's CWM recovery has changed since I wrote up that guide nearly a year ago (and shortly thereafter have gone onto flashing/running CM11 on emmc and thus would have missed any such change).
One possible solution you might consider trying is to download or copy the ROM and Gapps zip files to your HD+ user-media partition, then while in CWM recovery menu select "... zip files from emmc" and browse to where the ROM/Gapps zip files are located.
In that post, step 4 it mentions "pair" of zip files. I assume though the 2nd item in the "pair" is the Gapps zip.
...
Click to expand...
Click to collapse
Yes, that's correct.
bok build install behaves super flaky for me
One possible solution you might consider trying is to download or copy the ROM and Gapps zip files to your HD+ user-media partition, then while in CWM recovery menu select "... zip files from emmc" and browse to where the ROM/Gapps zip files are located.
I got the sdcard to boot after many reboots and had to keep hard powering off (cutting it off) if the NOOK name displayed too long, (where I knew it was going to boot Nook OS) It booted to CWM, I did a backup, then installed the zips (had to put on internal memory as you said, but even this wasn't easy, It gave some weird error I don't recall,maybe about something "has stopped", so I ended up having to copy it from ES File Explorer after booting to Nook OS) Then I repeated the boot trick as mentioned, backed it up, then installed the 2 zips. I rebooted, got walkthrough of 1st time setup. This is where it got weird. Screens would advance on their own, be shifted halfway off the screen, had a long delay or else wouldn't respond to my clicks, would power off (and wouldn't power on until MANY presses of the power button) or reboot on it's own during the setup. I finally got thru setup and then after booting to Android, it would still be very sluggish, and still powering off on it's own and being difficult to turn on. And it continued to be unreliable to boot to Android, sometimes booting to Nook OS still (even though some in forums say once they got it to boot to Android it would forever after.)
Maybe I need to try a different build. Who else has a well-known, reliable? build besides Succulent? (even though with his it wouldn't boot to CWM but hang at 99% forever on Nook OS loading). If there's no others, maybe I'll give his another try since I had some luck getting CWM to boot with the above trick.
baytee said:
...
This is where it got weird. Screens would advance on their own, be shifted halfway off the screen, had a long delay or else wouldn't respond to my clicks, would power off (and wouldn't power on until MANY presses of the power button) or reboot on it's own during the setup. I finally got thru setup and then after booting to Android, it would still be very sluggish, and still powering off on it's own and being difficult to turn on. And it continued to be unreliable to boot to Android, sometimes booting to Nook OS still (even though some in forums say once they got it to boot to Android it would forever after.)
Click to expand...
Click to collapse
What brand and class of SD card are you using to run CM?
...
even though with his it wouldn't boot to CWM but hang at 99% forever on Nook OS loading
...
Click to expand...
Click to collapse
FWIW, every time that I have had the problem of stock ROM boot-up stuck at 99% it was always because the stock ROM got corrupted due to some unexpected errors in the creation/update of the SD-based CM ROM image, and the only way I was able to recover was to restore stock ROM from backup copy.
I have a PNY 16gb class4 (C16G china 1308PW3599P)
The problem of it hanging at 99% only happened with Succulents, not Bokbokans. As far as the Nook OS being corrupt , I have doubts of that since without the SDcard it ALWAYS boots fine to the nook OS.
baytee said:
I have a PNY 16gb class4 (C16G china 1308PW3599P)
The problem of it hanging at 99% only happened with Succulents, not Bokbokans. As far as the Nook OS being corrupt , I have doubts of that since without the SDcard it ALWAYS boots fine to the nook OS.
Click to expand...
Click to collapse
The problem of stock booting to 99% and hanging with an SD inserted has to do with the properties of the SD, not corruption of stock. Stock will always hang if the SD has more than 3 partitions. Most of Bokbokan's SDs are set up to only have 3 just for that reason. I don't know how many the succulent SD has, I would bet more than 3.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
...
Stock will always hang if the SD has more than 3 partitions. Most of Bokbokan's SDs are set up to only have 3 just for that reason. I don't know how many the succulent SD has, I would bet more than 3.
Click to expand...
Click to collapse
Succulent's CM SD image for the HD+ only has 3 partitions.
I WAS creating a 4th partition & was unaware it was an issue so thanks. I was doing customized partition (not using their premade sd image). But my whole goal is booting to sdcard, not to nook os.....and the 99% Id assumed was after it failed to boot to sdcard & instead had gone on to boot nook os. But Just in case it helps me boot CM11 on sdcard, I'll try it with 3. Thanks for that tip.
actually I WAS creating a 4th partition & was unaware it was an issue so thanks. I was doing customized partitions (not using their premade sd image). But my whole goal is booting to sdcard, not to nook os.....and the 99% Id assumed was after it failed to boot to sdcard & instead had gone on to boot nook os. But just in case it helps me boot CM11 on sdcard, I'll try it with 3. Thanks for that tip
baytee said:
actually I WAS creating a 4th partition & was unaware it was an issue so thanks.
Click to expand...
Click to collapse
FWIW, I took succulent's pre-made SD image for CM11 (https://goo.im/devs/succulent/ovation/cyanogenmod/image/cm_ovation_11.0_24DEC2013_HD_SDC_IMG.7z), burned it to a (Sandisk class 4) 8GB SD card. The image has 3 partitions which succulent had sized to fit a 2GB SD card; I added a 4th partition (type: FAT32, name: /media) to fill the leftover space of my 8GB card (and reset the boot (1st) partition's type/flag to ensure that it's still bootable). The resulted CM11 card with the extra 4th partition booted up just fine on my HD+.
So, having an extra 4th partition (or, in general, more than 3 partitions) does not prevent a SD-based CM image for the HD+ from booting successfully -- just as one by virtue of logics would have expected.
digixmax said:
FWIW, I took succulent's pre-made SD image for CM11 (https://goo.im/devs/succulent/ovation/cyanogenmod/image/cm_ovation_11.0_24DEC2013_HD_SDC_IMG.7z), burned it to a (Sandisk class 4) 8GB SD card. The image has 3 partitions which succulent had sized to fit a 2GB SD card; I added a 4th partition (type: FAT32, name: /media) to fill the leftover space of my 8GB card (and reset the boot (1st) partition's type/flag to ensure that it's still bootable). The resulted CM11 card with the extra 4th partition booted up just fine on my HD+.
So, having an extra 4th partition (or, in general, more than 3 partitions) does not prevent a SD-based CM image for the HD+ from booting successfully -- just as one by virtue of logics would have expected.
Click to expand...
Click to collapse
No it does not prevent it from booting to the SD, but it does prevent stock from booting successfully if the SD is inserted in the slot. It will hang at 99%.
Sent from my BN NookHD+ using XDA Premium HD app
Verygreen's CM 11 SD build of 11/29/2014 for the HD+ works very well for me. First boot does take awhile so don't give up too fast.
Sent from my BN NookHD+ using Tapatalk