Related
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
So here is my issue. Last week I formated my ROM, so for a while it was stuck in internal flashed CWM 5.5.0.4 Than I flashed some restore file which fixed that issue.
However I was dumb enough to exit the internal CWM before flashing any Andoird OS zip meaning it has no Os inside. Since restart it gave me B&N factory reset option. I did. Than it gets stuck just past account log in info. No surprise because there is nothing on the EMMC.
Now I was able to boot CWM from SD, but when I try to install any zip file it says Aborted. Also there is never enough room left on my SD after I image the CWM image file.
So here is my question one. How can I actually have enough space to copy the Stock OS zip and flash it.
Most importantly I did have internal CWM 5.5.0.4 inside. Now when I hit B&N reset I am assuming it got wiped. Is there a way to access that internal CWM if not.
AirplaneCrazy said:
Now I was able to boot CWM from SD, but when I try to install any zip file it says Aborted. Also there is never enough room left on my SD after I image the CWM image file.
So here is my question one. How can I actually have enough space to copy the Stock OS zip and flash it.
Click to expand...
Click to collapse
You can resize the partition of the SD card (after you flash CWM on it) using a partition manager, that will give you full access to all of it, or format the SD card and put these files onto an SD card.
So I able to boot on sd card, but when I try to flash anything this is the message I get. So once again I am stuck at best on CWM because it's not letting me install anything.
That (status 0) error sometimes is solved by mounting /system manually.
~ Veronica
Those two zip files will also do nothing. The former is the zip file to root, which will do nothing if you really have no stock os installed. The latter I'm not sure about but again I don't think its something that can be flashed without an OS already installed. Try flashing cm7 or another rom.
Sent from my Xoom using Tapatalk
edit: now that I've looked at my files on my computer, the latter is not a flashable zip file for clockworkmod. Its the cwm image for burning to sd card.
You gotta do some reading man if you're going to be flashing stuff; don't just try to flash any zip file you see.
Did you try bypassing the registration screen?
http://www.youtube.com/watch?v=sAASnHPn4PM
Cubanluke88 said:
Those two zip files will also do nothing. The former is the zip file to root, which will do nothing if you really have no stock os installed. The latter I'm not sure about but again I don't think its something that can be flashed without an OS already installed. Try flashing cm7 or another rom.
Sent from my Xoom using Tapatalk
edit: now that I've looked at my files on my computer, the latter is not a flashable zip file for clockworkmod. Its the cwm image for burning to sd card.
You gotta do some reading man if you're going to be flashing stuff; don't just try to flash any zip file you see.
Click to expand...
Click to collapse
Yes that's what I thought. Problem is after I write the Boot.rmg for SD CWM 5.5.0.4 there isn't enough space left to put the Os.zip on the SD. Tried a CWM SD I used to flash my Nook Color which does leave me enough room, but with that Nook Tablet just boots up normalls
AirplaneCrazy said:
Tried a CWM SD I used to flash my Nook Color which does leave me enough room, but with that Nook Tablet just boots up normalls
Click to expand...
Click to collapse
DO NOT USE STUFF FROM OTHER DEVICES UNLESS IT IS STATED IT WILL WORK FOR YOUR DEVICE
Theres no harm here but going down that path is a very very bad idea. The devices are different.
So I finally managed to find the right SD CWM Boot that allows me to boot in CWM and leaves me enough room to put ROM zip and what not in the card after imaging.
So I tried flashing Nook Tablet stock os and here is the message I get.
E:Eoor in/sdcard/nookcolor_1_4_1_signed.zip
(Status 0)
Installation Abroted.
As a last resort I flashed CM9 which does finish the installation, but than when I restart it shows the black B&N screen saying device must reset and I am back to square one.
So now I am good with botting inside CWM. Just need help with successfully flashing the Nook Stock zip.
By the way me personally can't stand Nook Stock OS. I use a CM7 Mirage on my Nook Color. This is for a friend who I convinced to use Cyanogenmod on his Nook Tablet. He doesn't like CM, so I am trying to get him back to his stock os.
AirplaneCrazy said:
E:Eoor in/sdcard/nookcolor_1_4_1_signed.zip
(Status 0)
Installation Abroted.
Click to expand...
Click to collapse
This is for a nook tablet yes? Why are you using a nook color zip file?
Tried Nook Tablet zip too with no success. The color one was just for trial.
Maybe I need just a plain all stock.zip customized for installation via CWM. Here is the message I get when I tried to flash the nook tablet update zip
Found links for Stock Nook Tablet zip, but none were downloadable.
E:Can't open /sdcard/nooktablet_1_4_2_update.zip
(bad)
Installation Aborted.
First of all is you friend's nook tablet 8GB or 16GB model?
Second you haven't read my FAQ, so you haven't read enough and you're confused in the way a custom rom and B&N stock update.zips are flashed.
A custom rom you can install from cwm > install .zip from sdcard or if it's a backup folder a.k.a recovery rom (as Albert call it) you can restore it from backup & restore option in cwm; but if it's a B&N stock update.zip you flash it "as is" in a different way, you have to format a sdcard with fat32 file system and set primary partition to "active" then you can flash the .zip from the sdcard. There is no need of cwm BUT there is need of stock original recovery as their update.zip requires their stock recovery to work.
Read my thread how-to restore internal partitions with 'dd' command for more information about flash stock/custom recovery and flash B&N stock update.zip for an out-of-the-box nook which means start from scratch: rooting, bla bla bla.
If you dont want to start from scratch then grab a custom stock rom from development section and flash it in cwm. Albert, cobrato and i have posted them.
Third this is not Q&A, wrong section to post. There is a sticky about it.
~ Veronica
Sent from my Nook Tablet using xda premium
Well that's the problem. I flashed Nook CM7 and CM9. Than when I start it loads B&N factory reset instead. Than I flashed B&N Stock in CWM. Still when I start it shows a screen saying Nook must be reset. Than right after account log in it shows the contact customer support screen.
It's a Nook Tablet 16GB versioj
AirplaneCrazy said:
Well that's the problem. I flashed Nook CM7 and CM9. Than when I start it loads B&N factory reset instead. Than I flashed B&N Stock in CWM. Still when I start it shows a screen saying Nook must be reset. Than right after account log in it shows the contact customer support screen.
It's a Nook Tablet 16GB version
Click to expand...
Click to collapse
okay it sounds like you have "tried" to get your NT back into happy mode... but its still a sick puppy. sometimes you have to do the fix two times in a row. . and did you do a 'wipe / reset, wipe / reset" before and after ? . . .umm, take it back to the store and tell them you gotta turkey ?
AirplaneCrazy said:
Well that's the problem. I flashed Nook CM7 and CM9. Than when I start it loads B&N factory reset instead. Than I flashed B&N Stock in CWM. Still when I start it shows a screen saying Nook must be reset. Than right after account log in it shows the contact customer support screen.
It's a Nook Tablet 16GB versioj
Click to expand...
Click to collapse
Hmmm ok , then something got corrupted , I think I have read about other user having this same problem but I don't recall for a resolution. You will have to try restoring the partitions referred to the boot process first as I'm not sure if it's the factory partition that got corrupted.
I'll post useful links for you to read to know how to proceed later
~ Veronica
Sent from my NookTablet using xda premium
Okay so I had been messing with the Nook Tablet for months now and I haven't been able to make any progress. Basically same issue. I can flash zip through CWM, but than I get pass no where beyond register B&N page and of course the registration fails.
Can anyone help?
AirplaneCrazy said:
Okay so I had been messing with the Nook Tablet for months now and I haven't been able to make any progress. Basically same issue. I can flash zip through CWM, but than I get pass no where beyond register B&N page and of course the registration fails.
Can anyone help?
Click to expand...
Click to collapse
Try the un-brick method that @soshite posted in development section. Its in page #2.
~ Veronica
Sent from my Cappy powered with Jelly Bean using Tapatalk 2
[See post http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for the new version of this post with updated links/pointers to Succulent's recent CM10.1 builds as well as CWM/TWRP recovery tool compilation].
[Caveat emptor: adopt/follow this guide at your own risk].
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc).
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows. If you are going to use this card for backing up your NT, keep in mind that each backup will require at least 600MB (for a barebone stock or CM config) and size the partition accordingly.
Obtain and copy to the SD card the following files:
MLO, u-boot.bin, and flashing_boot.img in SD_boot.zip obtained from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/
either one of the two recovery program image files: cwm_6012_sd.img (ClockworkMod Recovery (aka CWM)) in CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, or twrp_2220_sd.img (TeamWin Recovery Project (aka TWRP)) in CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958, rename it to recovery.img. If you want to try out (or use) both, name your alternate choice altboot.img.
the file cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
the file gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select either SDC Recovery (or Alternate Boot depending on which recovery tool you want to use).
Select Backup to backup your current NT config (/boot, /recovery, /system, and /data). Before proceeding to next step, see note (ii) near the end of this post.
Select Wipe data & factory reset.
Select install zip from SD card and install cm-10 zip file.
Select install zip from SD card and install gapps zip file.
Select power of and remove SD card from NT and power NT on again using the power button (alternatively you can just remove SD card and select reboot).
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored)
A few additional points worth noting:
Installing CM10 ROM and gapps will override your NT's BN-provided boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using backup process in step #5 above, safekeep the backup data on your PC/Laptop and better yet archive it on CD/DVD. Your media files in the NT media partition BN allocates for user should be intact.
To play it safe you should do the above in 2 phases: steps 1 through 5, then exit recovery and remove and mount SD card on PC to verify that backup data got newly created; then insert SD card and continue steps 6 through 9.
CWM and TWRP use different backup archive formats, so keep this in mind if you decide to switch. Furthermore, CWM has changed its archive format going from release 5.x to 6.x, so I think it would be prudent to save a copy of the recovery program together with the backup data it generated. (FWIW I prefer the tar/zip compatible backup data structure TWRP uses (which CWM 5.x had also used) over the BLOb structure which CWM 6.x use -- but YMMV).
To restore from backup data, boot into SD card and select from boot menu the same recovery program that was used to create the backup data, then select the particular backup dataset (indexed by date/time) you want to reinstall on your NT.
I would advise against blindly using other functions of the CWM and TWRP without looking up info and researching to understand what they really do.
See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
My thanks to all the developers who collective work created this wonderful ROM as well as the tools and info I made use of to install it. IMHO this ROM helps make the Nook Tablet one of the best-value tablets for the money (at least at the moment).
great post...fwiw here's my experience to get two NT16's up and running (I started with an old CM7 on both of them).
Backup nook with titanium backup on existing 32GB card.
Take screenshots for replacements
Reset nook to stock (1.4.2) and update to latest (1.4.3) with a fresh SD Card with repart.img copied to root (my red 2GB card):
http://raywaldo.com/2012/06/make-unbrick-repartition-image/
http://www.youtube.com/watch?v=Nu6e4m62tFc
c. 1.4.3 can be downloaded from B&N site directly. (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
Create a CWM SD Card (ideally 4GB SanDisk) as per these instructions - http://raywaldo.com/2012/05/root-nook-tablet-with-cwm-sdcard/
Copy CM7 BETA and compatible GAPPS onto this card or another blank one. You can get the files from here: http://forum.xda-developers.com/showthread.php?t=1481826 and http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Boot into this CWM Card, wipe data/wipe cache and dalvik cache. Install zip from sdcard (either current or pop in the new one). Choose cm-7 beta first, then gapps. Remove sd card. Reboot. Wait a while for it to set itself up.
Go into settings/applications and clear the cache for google market/play.
You now have CM7 installed and can setup the basics (google, wifi etc..)
Insert your 32GB (or 16 or 8 or whatever) Sandisk SD Card (it should ideally have the Titanium Backup folder from step 1, any media you want in Music and Movies folder and the CM10 and gapps zip in the downloads folder -- and that's it!)
Once mounted, download Goo Manager from the google play store and run it, accepting superuser requests.
Choose settings menu and "Install OpenRecoveryScript" and it should install openrecovery twrp recovery manager. Once it has installed and informed you of success, reboot into recovery (this is important), upon reboot hold the "n" and choose internal emmc recovery from the menu.
You will now find yourself in TWRP. From the install menu, add the CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode and then the gapps-jb-20121011-signed.zip and swipe to confirm flash. This is it. Fingers Crossed!
NOTE: On one NT 16 (I have two), step 12 DID NOT WORK. It wouldn't install the CM10...zip -- and simply rebooted itself or hung...so I powered off, and rebooted to the CWM Card in #6..and used CWM to wipe caches etc… and then installed the two zips...and voila.
hope it helps.
digixmax said:
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
Click to expand...
Click to collapse
How do you feel about it now that you've installed it internally? I took the plunge as well today, but I'm not sure it's runs any better internally than it does from the sd card. Having said that, it runs so incredibly well from the card, so it's really hard to beat, but still... I'm actually having more issues with the internal install than the sd version.
I had had enough of the stock reader (that I'm actually pretty fond of) not remembering my place in sideloaded books, so I didn't feel I had anything to loose and am glad I made the install though. Installed once makes it easier to reinstall when an even better build comes along.
I made the switch since the stock ROM was so barebone and clumsy I virtually never use it since I had the NT, and the rooted stock ROM is just marginally better -- I found out there are so many apps I 've been using on CM10 that are simply not available for BN's (Android) Gingerbread. I also like the fact that I can now reboot (if ever needed) untethered.
I think performance-wise it runs about the same as it was running on SD, if it's better then it's not yet noticeable.
What kind of issues are you having with your new setup?
Some apps misbehaved. Didn't install properly or gave error messages. I decided to re flash and this this second install hasn't had any issues at all. Same files from the same card.
It is nice to have it internally and be able to switch sd cards should I want to.
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2 and SwiftKey
I ran into a problem with v12/08: when I connect the NT to the PC I do not get the “USB connected” notification with option to “turn on the USB storage”, and thus cannot access neither the emmc media partition nor the sdcard. The problem exists with both CM10 running on emmc and running on sdcard. Furthermore when running on sdcard, hitting “storage” in “settings” results in a force-close of “settings”.
I am curious if anyone else has the same problem, or I am just missing some setup setting somewhere.
In the meantime, I am back to running another ROM off SD.
Those storage setting issue I had with the 1118 build but not with later ones. Connection to PC work fine but I don't think I need to do the turn on USB thing. No PC nearby at the moment
Edit: I am now near a PC, and I do get the "touch to turn on USB" or words to that effect. So it works as it should..
Sent from my Nook Tablet using Tapatalk 2 and SwiftKey
Thanks, I've tried reinstalling a couple of times (as well as installing a different ROM) without success.
I found the answer to my problem: I was used to getting the full-screen alert “USB mass storage” (upon insertion of tethered USB cable), and didn’t notice the tiny alert “USB connected” on the status bar (which when pulled down would in turn launch the “USB mass storage” alert).
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Cm7 is a gingerbread rom, it can be flashed by cwm 5 and 6 both. But cm10 is jellybean and must be flashed with cwm 6 only (or twrp) . And once you have cm7, you get cyanoboot (2nd bootloader) which is necessary to load cwm6, whether its internally flashed recovery or SD card recovery.
If you still have your bootable SD card, boot into recovery and check the version (cwm 5 most likely) , then do the longer, but simpler method - stock > cm7 > flash cwm6 internal and boot into it from cyanoboot > cm10.
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
...
I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Click to expand...
Click to collapse
Yes, you can use this process to go directly from stock or rooted stock to CM10 -- I used it to go from rooted 1.4.3 directly to CM10. With SD-based flash, there is no need to go the circuitous multi-stage flashing process.
And if you use Succulent's CM10 builds from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/ his ROM zip files all include emmc recovery so you don't even have to separately flash recovery as you would have with other ROMs. I think his approach, in addition to being convenient, has the benefit of avoiding intermediate states where there is potential incompatibility between ROM and recovery versions (which I think is conducive to causing bootloop).
Of course if for some reason you later prefer a different version of recovery than the one he includes (CWM 6.0.2.5) you can always reflash your particular choice of recovery by itself.
FWIW I am running Succulent's cm-10-20121225-acclaim-HD.zip (GCC 4.6) at the moment and it works great.
Dean1650 said:
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Click to expand...
Click to collapse
Everything that gets flashed via recovery (either CWM or TWRP) comes in zip archive form, and this applies to ROM, gapps, as well as recovery itself. (If you ever want to flash recovery, the simplest way is to get a recovery zip file, such as one of those with keyword emmc from http://forum.xda-developers.com/showthread.php?t=1640958, and flash it from SD using the process in the first post, just as you would flash a ROM build or gapps).
If you are curious about what gets installed and where, just open (but don't extract) the to-be-flashed zip file (e.g., using winrar/winzip/7-zip): everything except the META-INF folder is what get installed, and the updater-script file in META-INF\com\google\android\ (which you can open using a text editor like notepad) contains installation script detailing where (i.e., which partition on the NT) various components of the zip file get installed.
Typical ROM builds zip contain boot.img which gets installed on /boot partition, and a bunch of system files and apps to be installed on /system partition. Succulent's ROM builds also include recovery which gets installed on /recovery partition. Finally gapps apps get installed on /system as well.
Really, really appreciate this OP, the replies, and the knowledge. VERY helpful. Wont do this til the 1st and will let you know the results... Again, THANKs
Sent from my SAMSUNG-SGH-I317 using xda premium
Well your method worked flawlessly. I had a few minor operator errors but it went just as you explained. I did, however, have a fatal bug in the rom. Not sure who to report it to, but while messing around in settings I tried to change the color of the clock in the status bar. It totally blew away systemui. I tried everything I knew of to restart and recover but had to resort to wipe/factory reset. Could not figure out what data file got corrupted. That in turn made me have to flash the gapps again because none of the Google apps worked including play store. The net result is to add 1 more step to your method. BEFORE messsing with settings, and after the initial setup is complete, boot to recovery and do another backup..I forgot to mention I flashed 20121231, which is the latest release. Thank you so much for your knowledge and reseach. STOCK ROOTED TO CM10 RELEASED.
Sent from my SAMSUNG-SGH-I317 using xda premium
Stuck on backup in CWM 6.0.1.2
My 16gbNT is currently running Team_B CM7. I'm trying to install Kuzma30's CM10.1 from a SD card. Following the instructions from this OP. While trying to perform my backup the process gets about 3/4 of the way through and then sticks at the file named "generic11.lda". It doesn't continue after that and I have left it alone for a considerable amount of time. Any idea what's causing the stick? I've tried it about three or four times with occasionally sticking at different files but it is still about 3/4 of the way through. Backup will not finish.
Any help is greatly appreciated.
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Backup success, Install failure
digixmax said:
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Click to expand...
Click to collapse
Backup successful! Thanks button pressed. Now on the install I used CWM 6.0.1.2 and I'm not allowed to complete the install. It aborts installation and gives the following error:
"Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10.1-20130102-UNOFFICIAL-acclaim.zip
(Status 7)
Installation aborted."
Any ideas?
Your guide is quite clear but somehow it is not working for me. I have a fresh NT 8GB with stock 1.2 on it.
I obtained the 6 files you mention:
- u-boot.bin
- MLO
- flashing_boot.img
- recovery.img (= cwm_6012_sd.img)
- gapps-jb-20121011-signed.zip
- cm-10-20121231-NOOKTABLET-acclaim-HD.zip (from: http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/)
I copied them to a 16GB 10x SD card and placed the SD card in my NT.
The problem is that whatever I do, it always boots the stock os and never into Cyanoboot. I know I have to connect the NT to my computer with USB and wait for it to boot, but even then it only load the stock OS.
Am I doing something wrong here?
Help much appreciated!
I am a little familiar with rooting and flagging cm add I did it flawlessly on my nexus I just bought a nook tablet 8gb (wad told it was new hd and didn't know a thing about nooks and fell for it) but it is the older regular nook tablet. It was already rooted and had cm7 installed. I don't know what method was used bit it does power directly into cm7. I am used to jelly bean and I don't like going back to GB. I've researched fora few days on differences with this tablet but I've not found much. Does anyone have s link to a stable version of the acclaim cm10? What doi need to do too flash the new rom without raising my chances of brick. Do I just go to recovery and delete all data then install rom from sd? Do I have to flash a new kernel? Or can I flash a faster one(that's another reason for wantingcm10 mine freezes alot) if I can flash one does anyone have links to the rom and a comparable kernel? That you so much in advanced!
Wrong subforum methinks...
Try cm10.2, usual full wipe and install via CWM.
It's now supported via cmupdater for automatic updates
chachi said:
Try the cm10.2 in the thread, full wipe and install via CWM.
It's now supported via cmupdater for automatic updates
Click to expand...
Click to collapse
ok now i have a bigger problem... I didnt reformat the SD card but I removed it and deleted unneeded things there was a clockworkmod file but i didnt touch it and there was no .zip file but after I did that nothing would word EVERYTHING force closed so I held power botton and hit "reboot" well when I did that it rebooted into the nook operating system... How did this happen? is it unrooted? can I get back to CM7 or did i delete it on accident? ANYBODY PLEASE HELP i just bought this and its actually my daughters birthday gift and I dont have the money to buy anything else so I have to find a way to get this working before her bday
Sounds like you had cm7 on SD not internal...
Do a clean install to internal
Hi,
I loaded CM 11 and was working fine. I tapped on the CMD update APP and it checked for updates and tablet rebooted and touch screen failed to work. I tried reinstall, wiped everything etc. I tried cm10 again and no luck. Not sure what to do at this point.
You might consider trying the Unbrick method posted at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ to see if you can get your NT back to stock ROM and operational.
will try that thanks. Will I have to root again?
I loaded factory with success. However the touch screen still dead.
It's a long shot, but perhaps you can try to burn of Succulent's CM10 or CM11 SD-based ROM images from https://iamafanof.wordpress.com/category/nook-tablet-2/ (e.g., cm_acclaim_11.0_29SEP2014_HD_SDC_IMG from https://iamafanof.wordpress.com/201...droid-4-4-4-for-nook-tablet-sdcimg-xxsep2014/) and see if your NT would run CM ROM on SD.
Also, while the device was still running CM, did you by any chance change the Touch Screen mode using the Touch Screen FW Flasher app?
digixmax said:
It's a long shot, but perhaps you can try to burn of Succulent's CM10 or CM11 SD-based ROM images from https://iamafanof.wordpress.com/category/nook-tablet-2/ (e.g., cm_acclaim_11.0_29SEP2014_HD_SDC_IMG from https://iamafanof.wordpress.com/201...droid-4-4-4-for-nook-tablet-sdcimg-xxsep2014/) and see if your NT would run CM ROM on SD.
Also, while the device was still running CM, did you by any chance change the Touch Screen mode using the Touch Screen FW Flasher app?
Click to expand...
Click to collapse
I did hit a flasher app but I think it was for the ROM update. Anyway I did what you said, everything loads fine but touch screen is dead. So weird was working after cm10 update to CM11 and then I hit rom update in the apps and everything turned to garbage after that.
fw flasher app many fixes no solution no touchscreen
On my nook tablet I had lolipop set up and running well. Then after many years of not pushing the screen flasher app something came over me and I pushed it. Bad mistake. I have tried every fix I could find. I have flashed most cm roms that work with 10 touch. Tried the sd card boot rom, als cm9 ,10. 10.1 10.2, 11 and b&n stock .img.
With every new flash everything sets up perfectly except no touch screen response, the first page is perfect otherwise.
Any other ideas would be greatly appreciated.
chainsawchef said:
On my nook tablet I had lolipop set up and running well. Then after many years of not pushing the screen flasher app something came over me and I pushed it. Bad mistake. I have tried every fix I could find. I have flashed most cm roms that work with 10 touch. Tried the sd card boot rom, als cm9 ,10. 10.1 10.2, 11 and b&n stock .img.
With every new flash everything sets up perfectly except no touch screen response, the first page is perfect otherwise.
Any other ideas would be greatly appreciated.
Click to expand...
Click to collapse
Yea super annoying, I never had software screw up hardware like this. Everything loads fine just cant use touch screen
How I restored touch to my Nook tablet touch screen.
bigdog100 said:
Yea super annoying, I never had software screw up hardware like this. Everything loads fine just cant use touch screen
Click to expand...
Click to collapse
How I restored touch to my Nook tablet touch screen.
(can't post links since I am a new user)
Google and Download:
cm 10.201212NookTabletAcclaim-HDSDC.img
9-20120815 acclaim-restorefw .zip
emcc cm10.0 zip with correct gapps
Format sd card w/ sd formater
burn to card cm 10.201212 Nook Tablet Acclaim - HD SDC .img
boot nook with new card
after boot to non responsive screen, power off nook
connect nook to pc
and place on an internal folder(I used My Files/Documets) an emcc cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip (restore to two touch)
power off (with no sd card in nook)
make sure to boot nook into INTERNALrecovery flash:
cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip
wipe and factory reset
wipe cache and Dalvick
advaced fix pemissions
Reboot nook
My recovery is cmw v6.0.3.0
chainsawchef24 said:
How I restored touch to my Nook tablet touch screen.
(can't post links since I am a new user)
Google and Download:
cm 10.201212NookTabletAcclaim-HDSDC.img
9-20120815 acclaim-restorefw .zip
emcc cm10.0 zip with correct gapps
Format sd card w/ sd formater
burn to card cm 10.201212 Nook Tablet Acclaim - HD SDC .img
boot nook with new card
after boot to non responsive screen, power off nook
connect nook to pc
and place on an internal folder(I used My Files/Documets) an emcc cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip (restore to two touch)
power off (with no sd card in nook)
make sure to boot nook into INTERNALrecovery flash:
cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip
wipe and factory reset
wipe cache and Dalvick
advaced fix pemissions
Reboot nook
My recovery is cmw v6.0.3.0
Click to expand...
Click to collapse
ok gonna give it a shot but google will not pull up cm 10.201212NookTabletAcclaim-HDSDC.img i even broke it down, must be old version and cycmogen site doesnt show
bigdog100 said:
ok gonna give it a shot but google will not pull up cm 10.201212NookTabletAcclaim-HDSDC.img i even broke it down, must be old version and cycmogen site doesnt show
Click to expand...
Click to collapse
It is an old version when I was done I was running cm9 and my touchscreen is working. Just have to upgrade to cm12 . Add this to your search iamafanof.wordpress should help.
Good Luck
chainsawchef24 said:
It is an old version when I was done I was running cm9 and my touchscreen is working. Just have to upgrade to cm12 . Add this to your search iamafanof.wordpress should help.
Good Luck
Click to expand...
Click to collapse
still cant find it
bigdog100 said:
still cant find it
Click to expand...
Click to collapse
add https://
iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
9-20120815 acclaim-restorefw .zip look for this near the bottom of the page.
add https://
iamafanof.wordpress.com/?s=cm+10.0cm
cm 10.201212NookTabletAcclaim-HDSDC.img
cm-9-20120815-acclaim-restorefw.zip got the zip file but cannot find the .IMG
bigdog100 said:
cm-9-20120815-acclaim-restorefw.zip got the zip file but cannot find the .IMG
Click to expand...
Click to collapse
here is the download link sorry I left off 31 from the end earlier.
add- https
://docs.google.com/file/d/0B0pqBNpVw4UUZ3VRLXVWN0VDWHc/edit
I also have a nook tablet with non responsive touch screen. Occasionally it will activate the power off button but nothing else. I always thought it was a hardware failure of the FT5406ee8 touch chip. I have also tried booting CM roms that should have 10 touch capability and no go.
Don't know what to do other than trash it.