[HOW-TO] Installing CM10.x Internally on Nook Tablet

[alphad2an]

It's because the chrmhoffmann recovery.img is compiled for emmc, not sd-card.

You should be able to use the recovery.img contained inside the zip file for Succulent's CM11 SD-based ROM: e.g, cm_acclaim_11.0_07FEB2014_HD_SDC.zip (iamafanof.wordpress.com/2014/01/01/cm11-0-kitkat-android-4-4-2-for-nook-tablet-sdcxxx-01jan2013 ).

Also, a more up-to-date version of PA-Gapps can be found at goo.im/devs/paranoidandroid/roms/gapps-mini.

Thanks that did the trick.

 

[blisside]

updathe the limks

could you please update the links

---------- Post added at 04:30 PM ---------- Previous post was at 04:19 PM ----------

could you please update the links to the files

 

[digixmax]

Installing CM10.x Internally on Nook Tablet

[Caveat emptor: adopt/follow this guide at your own risk].

The following is the process using SD-based recovery to install CM10.x internally (i.e., on emmc) on a Nook Tablet running stock ROM. (To flash CM11 see http://xdaforums.com/showthread.php?t=2692403).

1. 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
   
2. Obtain and copy to the SD card the following files:
   • first MLO, then next u-boot.bin, flashing_boot.img and recovery.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
     
   • the flashable_CWM_6.0.2.x_chrmhoffmann.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery provided by Chris Hoffmann at http://goo.im/devs/chrmhoffmann/cm10.1 (linked in his first post of the XDA Official CM10.2 thread http://xdaforums.com/showthread.php?t=2388520).
     
   • the zip file of CM10.x ROM build of your choice – e.g., from http://download.cyanogenmod.org/?device=acclaim.
     
   • the zip file of the Gapps package (corresponding to the particular chosen CM10.x release) from http://wiki.cyanogenmod.org/w/Google_Apps
3. 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.
   
4. Select SDC Recovery.
   
5. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
   
6. Select Wipe data & factory reset.
   
7. Select install zip from SD card and install flashable CWM recovery zip file.
   
8. Select install zip from SD card and install CM10.x zip file.
   
9. Select install zip from SD card and install Gapps zip file.
   
10. 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 on your NT your apps will be auto-downloaded (but their settings will not be auto-restored).

Notes

• If the Nook fails to boot off SD -- the two most common symptoms of failed SD boot and their likely causes are:
  • The NT boots straight to stock -- most likely the boot partition's type and/or flag are not correctly set, or the NT cannot find the MLO in the boot partition (make sure that MLO is the very first file to be copied to the freshly made /boot partition).
  • The NT screen stays dark for seemingly a long time then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. When in doubt, compare the size of the two copies of the files in bytes.
• Installing CM ROM and Gapps will override your NT's current boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to previous ROM if desired. See my post at http://xdaforums.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
  Also, I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
• Skip steps 2(b) and 7 if using Succulent's CM10.x ROM (as his ROM zip file already contains emmc recovery.img).
• The "boot/reboot to black screen" is a known and AFAIK unresolved issue for 10.1 and 10.2.x. Its frequency of occurrence varies with users (30-40% in my case), and some users have reported (just as you seemed to have also experienced) that given more elapsed time the boot/reboot would eventually complete. See http://xdaforums.com/showthread.php?t=2388520&highlight=black+screen&page=23 for brief discussions of this issue as well as the "sputtering boot animation issue".

My thanks to all the developers who collective work created the wonderful CM ROM for the NT as well as the tools and info I made use of to install it.

 

[omegacore]

So my backup step seems to have locked up while making FAULT_SUMMARY_com.android.browser_2012-03-03_19:58:58_PST.zip

Not sure what to do.

 

[digixmax]

So my backup step seems to have locked up while making FAULT_SUMMARY_com.android.browser_2012-03-03_19:58:58_PST.zip

Not sure what to do.

FWIW the few times when my CWM back-up hung mid-stream it was because of insufficient backup space. The backup space required for my NT ranges from ~600MB when it was relatively new running stock ROM to 1.8GB nowadays running CM11 with a couple of dozen apps.

 

[nmyshkin]

I flashed CM 10.2.1 a few days ago on my 16 GB NT according to post #163 (thank you digixmax!!!!) and it all seemed to go well. I also backed up the stock 1.43 before the change.

It all seemed fine until my first reboot a day later when all I got was a back screen after "Loading (emmc)...". I tried a couple of times. I eventually put in the SDcard I used to flash hoping it would boot from there but I got the red "booti" message. Meanwhile the battery was rapidly draining so not knowing what to do I plugged it in to charge for awhile. I eventually got it to boot but really by accident as I thought it was just a black screen again but when I touched the "N" button it was all there!

Then the screen lock started not coming on. Now it only works manually from the power button regardless of what combination of settings I try. I originally had issues with seeing the internal 1 GB on my PC but seem to have resolved that by clearing away all the old B&N folders, setting the NT for MTP and enabling USB debugging. Now I can see the contents of the partition.

Booting is unnerving. After "the flash" when leaving the "N" screen, the cyanoboot screen comes along and the the cyanogen mod boot screen with the rotating arrow. The arrow starts and stops. Reminds me of an old Win XP machine having trouble and the little moving indicator on the screen starting and stopping. Never a good sign, the IT guys used to tell me.

Today it never got past there on a reboot so I flashed the flash_fix_recovery_bootloop.zip file from the SDcard and that seemed to "solve" the problem.

I've checked the MD5 checksums on the files I used and they are fine, but I am thinking I need to do this whole thing over again.

If I do, is there anything I should know? I assume I restore the backup (stock 1.43) from the SDcard. Any additional steps (things to clear/wipe)? I'm thinking I might repartition after that. Then can I just repeat the instructions in post #163?

Thanks for any and all help!

 

[digixmax]

...
It all seemed fine until my first reboot a day later when all I got was a back screen after "Loading (emmc)...".
...
Booting is unnerving. After "the flash" when leaving the "N" screen, the cyanoboot screen comes along and the the cyanogen mod boot screen with the rotating arrow. The arrow starts and stops. Reminds me of an old Win XP machine having trouble and the little moving indicator on the screen starting and stopping.
...
If I do, is there anything I should know? I assume I restore the backup (stock 1.43) from the SDcard. Any additional steps (things to clear/wipe)? I'm thinking I might repartition after that. Then can I just repeat the instructions in post #163?

The "boot/reboot to black screen" is a known and AFAIK unresolved issue for 10.1 and 10.2.x. Its occurrence frequency varies with users (30-40% in my case), and some users have reported (just as you seemed to have also experienced) that given more elapsed time the boot/reboot would eventually complete. See http://xdaforums.com/showthread.php?t=2388520&highlight=black+screen&page=23 for brief discussions of this issue as well as the "sputtering boot animation issue".

If this issue bothers you then you might consider trying CM11 as the issue seems to have gone away in CM11 later builds (e.g., snapshots M4 through M7). CM11 of course has its own quirks ...

You do not need to restore to stock ROM to re-flash CM10 or to update to CM11 (see http://xdaforums.com/showthread.php?t=2670589 on pointers/tips on how to update to CM11).

Finally, you should recharge your NT when its battery level is down to 25-30% range, as I've found the CM10/11 battery readings somewhat inaccurate/unreliable and consequently the NT in low battery can go dead suddenly.

 

[nmyshkin]

Thanks for your helpful responses. I guess one approach is to minimize rebooting...

Is the lock-screen problem also a known issue with CM 10.21? I've read posts for other hardware that seem to indicate that. I'm wondering how the sleep interval and the screen timeout modes interact. Do you know what the three times in the screen timeout modes are for? (Fade, off, sleep?)

Sent from my CM 10.21 NT

 

[digixmax]

...
Is the lock-screen problem also a known issue with CM 10.21? I've read posts for other hardware that seem to indicate that. I'm wondering how the sleep interval and the screen timeout modes interact. Do you know what the three times in the screen timeout modes are for? (Fade, off, sleep?)

I don't recall having any problem with lock-screen in CM10.x.

With recent CM11 builds, my NT sometimes fails to auto-lock when going asleep and wakes up in a home-screen in lieu of lock-screen; at other times it exits to lock-screen while in the middle of navigating some app!!!

 

[nmyshkin]

I don't recall having any problem with lock-screen in CM10.x.

OK, so it's me with the lock screen issue. Sounds like a reinstall might be worth the few minutes it will take to do it. I haven't put anything on the device yet during this "shakedown" so it's no big deal. In fact, my local B&N apparently will still repartition so I'm thinking I will go back to stock and let them do their thing, then flash CM 10.2.1 again. I can follow the repartition directions in other threads here but the whole USB/ADB driver and settings issue is not working out for me. I had the same trouble with my NST. Wireless ADB is no problem and what I'm used to, but that won't work for the repartition regimen.

Thanks again for your help and for all the really clear guides you've written.

 

[digixmax]

...
In fact, my local B&N apparently will still repartition so I'm thinking I will go back to stock and let them do their thing, then flash CM 10.2.1 again. I can follow the repartition directions in other threads here but the whole USB/ADB driver and settings issue is not working out for me. I had the same trouble with my NST. Wireless ADB is no problem and what I'm used to, but that won't work for the repartition regimen.
...

I think avoiding the risk of bricking your NT during a DIY re-partitioning is more than worth the effort of restoring your NT to stock so as to let BN doing the re-partitioning.

 

[nmyshkin]

Repartitioner's Remorse.....almost

I think avoiding the risk of bricking your NT during a DIY re-partitioning is more than worth the effort of restoring your NT to stock so as to let BN doing the re-partitioning.

I restored the original backup of the stock system and off I went to B&N where some nice young man who knew what he was doing (university town--lots of tech-savvy young people needing part-time work) proceded to deregister my NT in preparation for repartitioning (so said the instructions). Everything looked fine until a little Android appeared on the screen (uh-oh) and a thin blue line advanced below it.

We gaped. Fortunately I had already spun a story about getting the tablet on ebay (true), the seller not even deregistering it (true), it turning out to be a 16 GB model rather than the 8 GB model listed (true), at which point I added, as another tech-savvy young man came over to join in the gape-fest, "well, who knows what the original owner did to it...."

The little Android went away and the device rebooted into the stock operating system again. Then the repartitioning process went forward as I held my breath. Five minutes later it was done. Voila! 8 GB of internal side-load storage!

I had forgotten about the internal CWM recovery, obviously.

A new EMMC install of CM 10.2.1 with a freshly prepared SDcard went quickly but booting was a mess. I got to the "turning on Wi-Fi screen" on the first try (after stuttering arrows) and it just sat there. A forced shut-down was followed by a series of failed boot attempts (the "black" screen). Finally I reflashed the ROM in desperation and went through the exact same madness!

Gave up, rebooted and let it sit to sulk while I fixed dinner. 30 min. later I touched the "N" button and there was the welcome screen and everything went through without a hitch.

WHEW.

 

[fullboogie]

I know this is an old thread, but many many thanks to everyone who has contributed to this, as well as the OP. I had rooted and installed CM7 years ago, and finally brought my old Nook out of the dark ages with CM10. Love it, particularly since it now closely resembles my HD+ now.

 

[G0ldengirl68]

I so appreciate the chance to upgrade my NOOK Tablet BNTV205A. I used your instruction Digimax, plus a lot of help from nmyshkin. Everything works, it takes patience, a lot of patience, and re-reading the direction (for me anyway as I tend to charge ahead full-speed without making sure I have the details).

Mine was really persnickety in that when I touch the screen, nothing happened. So I had to decide to wait to see if it was just slow, or just needed another tap. When I got to the "install the 3 files" it was so hard.

I did go with the CM11, I didn't mention that earlier. I really just wanted to thank Digimax here, and let folks know it did work, although I have a few glitches. I attribute them to the fact that the Nook Tablet I have is I think one of the first Nook made. I bought it is 2011 (late Fall of). I used it only for reading on a program called Overdrive (you can check out library books digitally) plus I bought about 200 books from Barnes and Noble. Great reader.

I wanted the upgrade though because Overdrive upgraded it's program, and it no longer was compatible with the Nook. Also, what support B&N did have was taken away, zero support for Apps on my Version.

Anyway, I may start making a list of the things that aren't working and see if anyone has any "fixes" for them.

In the install of the CM11, I might be able to help someone else, I've done it a few times now, and see where I went wrong and remedied that by simply trying again, following Digimax instructions