yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ General] wayover13:
I followed these directives about a year ago in order to get the CM/Marshmallow (5.1.1) build installed on a couple of Nooks. Things have been working out pretty well with those units. One thing that wasn't clear to me when I did this, though, was whether my devices would end up being rooted: I supposed they would, having had a completely different and custom OS/ROM loaded on them. But I've recently run across an app I'd like to use, and it's one that requires that the device its running on be rooted. The app won't run on my device, so I downloaded a utility to check whether my device is rooted: that app reports that it's not rooted. So, what do I have to do to root my Nook and its CM installation? Thanks
[Nook HD, HD+ General] wayover13:
I worked out a way to get root or superuser priviledges for the app I was trying to run, but it didn't help. It seems that there is supposed to be a root access option under the settings menu, if you've enabled developer options (which I'd already done some time ago--by tapping on the build number 7 times). But there is no root access item under development options on this build, for some reason. Maybe because it's CyanogenOS rather than CyanogenMOD?

In any case, there is a sort of workaround that involves downloading a zip file called SuperSU, then installing that from recovery mode. That's what I did and I now have the otpion to grant superuser or root priviledges to various apps that request it. Unfortunately the target app, even with superuser priviledges, would not run for some reason.

So, why does there seem to be no root access option in this version of CM?
[Nook HD, HD+ General] jgoff1995:
Good job on making 5 easy steps, I did so myself a while ago.
[Nook HD, HD+ General] Craftst3v3vd:
Well Done

good job!
[Nook HD, HD+ General] gascomm:
I've found charging a bit of an issue. orange light shows when plugged in but the battery stats refuses to say it's charging on AC - even with the lightening bolt showing on the status bar icon. I can charge it but am never entirely sure what's going on.

is this a known bug with CM12.1 on the HD+? any incoming fix or workaround available?

unrelated update ...

I let it drain to around 25% whilst testing the battery and iiplayer, chrome web view & modbro caused it to reboot. seems OK when plugged in and charging over 50% but certainly an odd behaviour I've never had on any device.
[Nook HD, HD+ General] piperman7:
Will this give me 6.0 on my Nook HD+ ?

I am currently at 4.4. Also Amazon won't let me watch videos anymore so that was why I was thinking that I needed to upgrade to 6.0.
[Nook HD, HD+ General] Taosaur:
I'm trying this build now, and it seems less glitchy than the latest Marshmallow and Nougat builds, but I don't have root! I don't currently have root and there's no "Root Access" item in the developer options.
[Nook HD, HD+ General] digixmax:
You need to flash Chainfire's UpdateSuperSU zip file available at https://download.chainfire.eu/696/supersu/.
[Nook HD, HD+ General] Taosaur:
Thanks, that did it! Now that I have 12.1 loaded down with apps, it's slowing down a bit. I might have to trim the fat. Then again, if I end up gifting it, they won't have as many apps.
[Nook HD, HD+ General] digixmax:
FWIW I had tried 12.1 for about a month, its performance was very snappy at first but after a couple of weeks slowed down to a crawl, so I ended up going back to 11. I am now on 14.1 and the performance is so far so good.
[Nook HD, HD+ General] i9000usersa:
Can anyone please offer some advice? I was following the instructions on the pdf in OP, but the mini partition tool doesn't give me the option to set the partition as active. The right click option doesn't give me the option in the pop-up menu, and the partition>modify.set active is greyed out. I have formatted to fat32 with default cluster sizes. Any suggestions? Thanks in advance.
[Nook HD, HD+ General] digixmax:
Did you create that partition using the Mini-Partition Tool?

BTW, FWIW I'd suggest you try LN14.1 -- in my experience it performs much, much better than CM12.1
[Nook HD, HD+ General] i9000usersa:
Thanks. I used another micro SD card, and this time instead of deleting the partition and creating a new one, I just formatted it, and then I had the option of setting it as active. So, now it works and I used it to install Lineage OS. Thanks.
[Nook HD, HD+ General] nux7osx:
Ok, So I'm very new to this

Hi,

I'm new to this, I once had a old CM 11 build running off my microSD card, so I could keep my Nook OS yet still run a Rooted OS build off the microSD card.

Does this Guide wipe out the internal storage and flashes directly onto the Nook HD+?

Is this PDF still valid? I was hoping to maybe run I believe the latest non-CM build if possible, what is the latest build? And do I do everything in this guide, except swap out the android build with the one of my choosing? Or do I need to pretty much not follow this guide?

Sorry to be a complete novice on the subject, I haven't rooted anything in over 3 years so far.

Thanks in advance
[Nook HD, HD+ General] digixmax:
The ROMs for which this Guide applies are EMMC-based. There is no SD-based build for CM12/13/14.
[Nook HD, HD+ General] pstelter:
First off...instructions were really spot-on! Thanks!

Second, got up and running on CM12.1 pretty quickly, but could not get the Nook Reader app to install. I found a (potential) solution, however, it requires me to root the device. However, the enable root access is not available in my Developer's options. Tried flashing SuperSU....still no good.

Ok - research shows that root access is a selectable in CM13.1. So I find what I think is a CM13.1 file and give it a try. Turns out it is CM14.1. GApps for 14.1 won't flash - system partition is too small. Have not tried to load with the TWRP.

Questions....

1. How do I get root access on 12.1 either through SuperSU or other means, or

2. The files from [MENTION=4473900]amaces[/MENTION] do not indicate what version of CM they are. Which one is for CM13.1? Should I try an AOSP ROM?, or

3. How do I get GAPss for 7.1 to install?

Thanks for the help!

BTW, I am a complete a complete newbie just poking around trying to see what I can learn. I think the battery is dying on the Nook, so I may be in the market for a new tablet soon. Won't really mind if I brick this device.
[Nook HD, HD+ General] digixmax:
For 12.1 you need to flash UPDATE-SuperSU-v2.46.zip (https://download.chainfire.eu/696/supersu/).

I'd suggest you try the LN14.1 build at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918.

You need to use the smallest, minimalist pico package.
[Nook HD, HD+ General] pstelter:
digixmax - Awesome! Worked LIKE A BOSS! Thanks for the pointers!
[Nook HD, HD+ General] nux7osx:
Ok, I'm confused a bit after reading what to download exactly. I believe this is all I need to download, if anyone can confirm, I'm trying to flash the suggested LN14.1 ROM, latest GApps Pico, etc:

lnos_ovation-ota-NMF26Q.170104.zip

open_gapps-arm-7.1-pico-20170216

My issue is what do I download for Recovery and Bootloader?

I see these in the latest builds where I got LN14.1: twrp-3.0.1-0-ovation.zip and twrp-3.0.3-0-ovation-K3.4.img

Are those the recovery? Which should I get?

And the only boot files I see are the old ones from the PDF: NookHDplus-bootable-CWM-6046-for-emmc-BOOTFILES-rev0-(07.13.14).zip is this still needed to use?

Sorry for the confusion and all.
[Nook HD, HD+ General] digixmax:
If your Nook already runs CM, you should be able to use your current CWM/TWRP recovery to flash twrp-3.0.1-0-ovation.zip (available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778), then reboot into the newly flashed TWRP to perform "wipe /data & factory reset", and then flash the LM and GApps zip files.

If your Nook is still on stock ROM, you should burn the bootable SD-based recovery image in sdcard-reco-ovation.img.xz (available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778) and use the SD-based recovery to flash TWRP as well as LN and GApps zip files.
[Nook HD, HD+ General] nux7osx:
Ok, So I just need these files in total?

sdcard-reco-ovation.img.xz

twrp-3.0.1-0-ovation.zip

lnos_ovation-ota-NMF26Q.170104.zip

open_gapps-arm-7.1-pico-20170216.zip

As for the sdcard-reco-ovation.img.xz file, is this actually a .img I have to rename? And not use twrp-3.0.3-0-ovation.img and use twrp-3.0.1-0-ovation.zip instead?

Oh and I'm at stock Barnes and Noble rom currently. I don't need to use the old boot files from the PDF?

---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------

Sorry was able to extract the files out of the sdcard-reco-ovation.img.xz file.
[Nook HD, HD+ General] digixmax:
Use win32diskimager to write sdcard-reco-ovation.img to SD card, copy the 3 zip files twrp-3.0.1-0-ovation.zip, lnos_ovation-ota-NMF26Q.170104.zip, open_gapps-arm-7.1-pico-20170216.zip to the SD card, insert the SD card into your Nook in power-off state, then power on the Nook to boot it off the SD card.
[Nook HD, HD+ General] nux7osx:
seems like I have two issues. Win32idiskmager when used kills my sdcard and is no longer useable unless i format it, It is no longer a FAT32 active partition, its unallocated.

So i used 7zip to extract the sd-reco files and saved them to my microsd card after formatting it to an active fat32 partition.

I went ahead and copied these boot files to my sdcard:

kernel, ramdisk, u-boot.bin, uImage, and MLO (this was copied over first by itself).

Here's my current file list, MLO was copied first, so not sure if that matters on boot loading exactly, followed the PDF. Please see Attachment

Then I copied the 3 zip files you mentioned. Now I cannot seem to power on my Nook after doing all this with the microsd card inserted.
[Nook HD, HD+ General] digixmax:
Make sure that the SD is correctly formatted as 0x0C FAT32 LBA (see step #1 of https://xdaforums.com/showthread.php?t=2679899).

MLO has to be the first file copied to the freshly formatted. If you still have the same problem see note b) of the post I referenced above.
[Nook HD, HD+ General] blackest_knight:
Hi,

I had the battery go totally flat on my nook hd+ and i ended up getting it back up with no apps, so i flashed a gaaps package but it still didn't get me the play store so i ended up flashing a full gaaps package it said system needed to be cleared so i did that and installed the full gaap package and now i'm stuck at the bootloader.

I'm trying to follow your conversation here

I have

twrp-3.0.1-0-ovation.zip

and am downloading

cm_ovation-ota-LMY48Y.151218.zip

I think i probably need a new gaaps package since the one i have is for 5.0.2cm

Am i on the right track?

ok i managed to get in a pickle i did a factory reset and ended up getting a boot loop

so i made the sd recovery as above

booted with it

did the 3 installs

and after a slow start am now signing in to restore my apps , phew

also smoked my first cig in about a month :)

thank you for all the useful information
[Nook HD, HD+ General] blackest_knight:
I am back up and running using these files

sdcard-reco-ovation.img.xz

twrp-3.0.1-0-ovation.zip

lnos_ovation-ota-NMF26Q.170104.zip

open_gapps-arm-7.1-pico-20170216.zip

I was looking at googles guide to 7.1 and it says you can run 2 apps side by side. I found a post from 2015 which said you had to enable this in developer settings but I can't find the setting.
[Nook HD, HD+ General] blackest_knight:
in trouble again earlier this evening it decided to do something strange with the desktop. I have access to the pull down menu's at the top but the desktop has turned black and only the left triangle is showing up the circle and square are missing meaning i can't do much with it. I guess i can flash it again but it is quite disappointing.
[Nook HD, HD+ General] PeteInSequim:
DrWu, my best guess is that the microSD card is not actually bootable. It can be tricky to arrange this, especially on a Windows system.

You would be far better off now to install a LineageOS version of Nougat built specifically for the Nook HD (Hummingbird). I have not written any instructions for this but I assure you it is far easier than things were back in Lollipop days. It is especially easy if you happen to have a Linux desktop computer to build the microSD card. It can also be done under Windows, but I don't know the details for this.

You will need some files.

Go to https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332708110 and download three files, complements of Andrei Măceș:

lnos-hummingbird-otaNJH4.170813.zip

sdcard-reco-hummingbird.img.xz

twrp-3.0.1-0-hummingbird.zip

Next get the latest gapps for ARM platform, Android 7.1, pico variant. While there also click the red MD5 CHECKSUM link to get the check file.

The procedure is as follows:

1. Build the microSD card using the sdcard-reco-hummingbird.img.xz file. If using a Linux computer, such as Ubuntu, simply opening this compressed image file will bring up a utility to build the bootable card with a recovery image ready to use.

2. Then copy the remaining files (lnos, twrp, and the two files from OpenGapps .org onto the card.

That's it. Boot from the card into the TWRP recovery utility, wipe the tablet, install the zip files, and hope it goes better than before. Be aware that this unofficial version of LineageOS does have a few issues, but its the best available for the old Nooks.

Feel free to PM me if you have difficulty.

Pete
[Nook HD, HD+ General] digixmax:
See the notes at the bottom of this post https://xdaforums.com/showpost.php?p=51043572&postcount=1 for potential causes of SD-boot failures.

You should also try a different card, it needs not be faster (class 4 would be just fine) nor larger (8GB is quite adequate even if you plan to backup your current/future ROM's /system & /data onto SD card).

If you want to try out the newer ROM LN14.1 in lieu of CM11, this process outlined at https://xdaforums.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810 for the HD+ should be adaptable for the HD by swapping in the corresponding TWRP and ROM builds for the HD.
[Nook HD, HD+ General] DrWu:
Brilliant. I only had aspirations to CM but now I'm running LineageOS 14.1 and I are happy camper.

Do you know the difference between a fairy tale and a war story?

Fairy tales always begin with, "Once upon a time ... "

... but war stories always start with, "Now you ain't gonna believe this bull shizzle ... "

Well you ain't gonna believe this but I made my post yesterday afternoon, then stepped out for two hours of outpatient orthopedic surgery. When I came home and found your two replies waiting, I was so jazzed that I fell in on it straightway and did the installs. Then I worked until the wee hours of the morning (getting started on) installing all my pet Android tweaks and apps before I put Dr. Feelgood in the driver's seat. If that doesn't define "geek," I don't know what does.

The files and procedures (updated from the OP) worked flawlessly. My initial booting problem appears to have been the SD card itself. I flashed sdcard-reco-hummingbird.img.xz using Mint's default Disk Image Writer app, then copied the remaining files and tried to boot from it but it was a no-go. So I ditched the 8gb PNY and went to a 4gb Sandisk and, bada-bing, Success!

So I am thankful there are fellow hobbyists like so many here who are so invested in this "movement" yet still willing to share the fruits of their hard work. And thanks to you guys for your willingness to "dumb it down" so even a noob could understand it.
[Nook HD, HD+ General] wayover13:
I used the instructions from the OP a couple years ago to install CWM and TWRP to a couple of Nook HD+es that I have and all went well. I've been using these units regularly in the interim with pretty good results. Now, however, I've encountered a problem with one of the units. After a recent recharging session, the unit has become stuck in some sort of boot loop. The boot process gets as far as the little Android head appearing on-screen with the expanding circle in the background, but will go no further. Additionally, the corner of the device that has the hole in it warms up considerably while the unit sits in that state. I can get into TWRP recovery by rebooting and holding down the requisite buttons, but have so far not discovered any way in doing that to effect some repair.

What I'm wondering, after reading new contributions to this thread, is whether I might be able to remedy the issue I'm experiencing by just installing the newer Marshmallow (Nougat?) version recently referenced? Any input here on whether I might be able to remedy the issue that has cropped up by effectively reinstalling a newer Android ROM to my device? Input will be appreciated.
[Nook HD, HD+ General] PeteInSequim:
I haven't seen your specific issue, but I have seen two examples of these Nooks entering a "Trebuchet has stopped working" loop. No observations about warm areas though.

Both of these situations were fixed by re-rom'ing with the Nougat release mentioned in post #221 earlier in this thread. You will probably have to use the pico variant of Open Gapps to squeeze everything in. In fact I always include with the gapps file a gapps-config file containing the entries shown below, just to save a little more space.

ExchangeGoogle

FaceDetect

FaceUnlock

BasicDreams

Browser

Email

NoiseField

Phasebeam

PhotoPhase

PhotoTable

GoogleTTS
[Nook HD, HD+ General] wayover13:
Thanks for your quick reply, PeteInSequim. Assuming something isn't seriously borked with my hardware, I'd actually been hoping I might be able to further update these Nook HD+es--even though the re-rom'ing (new verb, eh?) would likely hose the settings and data on the unit that's now giving me problems. I would guess that, given that I can get into TWRP recovery, chanced are good that re-rom'ing would succeed--wouldn't you think?

I was looking over post 221 as I wrote my entry earlier today, guessing that it could apply here. You mention there hummingbird but, if memory serves, I would need the ovation files for the HD+, correct? I do run Linux, though not Ubuntu (I'm using Arch/Void/Gentoo these days), so running a utility such as the one mentioned may well work for my scenario. Not quite sure I understand how the referenced sdcard-reco-*.img.xz part of the equation works: does that give you a loop-mounted application, complete with necessary libs, ala the TinyCore method of adding utilities to a running Linux file system? Further input will be appreciated.
[Nook HD, HD+ General] PeteInSequim:
You would need Ovation files, which are available here. Select the Ovation folder and download the .xz file, and the .zip files for lnos and TWRP. You'll also need the latest ARM 7.1 pico file from opengapps.org and I recommend also the md5 checksum file.

You absolutely must wipe the old installation before re-rom'ing (I just though of this word this morning, so not official). So back up anything you want to keep. The new TWRP utility that you will boot to using the new microSD card can manage this for you. In fact I think it can even support OTG if you have a proper transition cable, but I've not actually tried this.

I'd make a very small wager that the new ROM installation will be free of the problem you describe, but no promises.

The referenced file whose name ends in .xz is a compressed image that is conveniently expanded into about 1 gB of image on a bootable microSD card by the Linux utility I mentioned. Windows users must first extract the image, then go through additional procedures to install it onto the card. After installation the card contains all the files needed to make it bootable, and an image of TWRP. And there's plenty of room to add the zip files for Nougat, gapps, and TWRP plus if you wish an MD5 checksum file for gapps and a gapps-config file. Just copy them over, or drag and drop them if you have a GUI.

So when you boot into TWRP from the fully-prepared microSD card everything needed will be on hand and ready to flash. Neat huh?
[Nook HD, HD+ General] wayover13:
I'm still a bit confused about the nature of the file you describe. I've dealt with plenty of .img files in my day, both compressed and not. But from your description it seems to me there must be some additional binary (or utility, as you've called it) included alongside the .img file that then helps you write the image to the card. Have I understood correctly? I guess I'll just have to download it and see how it works, whether associated libs the utility may need are present on my system, and what sorts of permissions issues there might be, if any.

Sounds interesting and a lot simpler than the initial installation of CM. I'll report back once I've tried it.
[Nook HD, HD+ General] PeteInSequim:
It is a built-in feature of the GNU variant of tar. Other variants might require xz-utils to do the same. More information here.
[Nook HD, HD+ General] digixmax:
You can use a disk-image writer program such as win32diskimager to write the sdcard-reco-ovation.img file to the sdcard -- see https://xdaforums.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.

Alternatively, you can unpack the sdcard-reco-ovation.img file using an archive program and copy its content to the bootable partition of the sdcard -- see the steps #1-3 of https://xdaforums.com/showpost.php?p=51043572&postcount=1 (just swap in the sdcard-reco-ovation.img file in place of the verygreen img file). This alternative method is a bit more tedious but enables you to size the sdcard boot partition to be as big as 16GB which can be handy for backing up your Nook's current ROM and Apps onto sdcard.
[Nook HD, HD+ General] wayover13:
Thanks for the additional input. I know all about tar and have used it to create archives and compress/uncompress files/folders for years. I've also dealt with uncompressing .xz files on many occasions. It just seemed to me something more than that was being talked about. Earlier, for example, it was said that "simply opening this compressed image file will bring up a utility to build the bootable card with a recovery image ready to use." Well, I have midnight commander configured to uncompress .xz files when, on highlighting such a file, I hit the "enter" key; nothing more than a display in the terminal of the uncompressed image file's file name is to be seen when I execute those steps on this file. Likewise if I double click on the .xz file in a graphical file manager: that opens a file extraction utility that would allow me to save the uncompressed file somewhere. So, when dealing with this .xz file thus far I'm not seeing anything I could characterize as "a utility to build the bootable card with a recovery image ready to use."

I understand digixmax's description about extracting an image and writing it to a device--something I've also done countless times. Being a Linux user I typically use dd for such tasks. It sounds like the further description about copying content is a good deal like something else I've done numerous times over the years, namely loop-mounting an image file (whether .img or .iso) in order to examine and/or copy its contents elsewhere. Does it seem I am understanding correctly about that?

As the case may be, I'll have to do some more research. The process being described seems to bear a good deal of resemblance to processes I've accomplished many times over the years I've been using Linux and fiddling with tech. But it looks like I'll have to do a bit of translation to transform it into terms and concepts more familiar to me. I was apparently in error in gathering that an automated or semi-automated process for creating the SD card was being described. Of course it would be convenient if that were the case, but I should be perfectly capable of performing this task in a more hands-on fashion as well.