yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] frazor:
Hi all, having a slightly unusual/specific problem... Am running Amaces last AOSP build (aosp_ovation-ota-N2G48H.181223) with pico gapps installed. If i set up the device with my google account all is fine, and more specifically I can watch content on YouTube Kids. if I set it up with one of my children's accounts (which are Google Family Link accounts), initially its OK, but at around 2-3 mins of watching the content the video goes black (audio keeps running). No amount of rebooting, cache clearing of the app or reinstalling of the app seems to make any difference. Anyone got any ideas?
[Nook HD, HD+ Android Development] twiztid_:
Have you tried an older version of Android?

I absolutely cannot get Crunchyroll to play on anything but Lollipop. On Marshmallow or higher it will work fine for about 30 seconds, but then it gives me an error about playback. I've tried multiple different builds across M/N/O, even using the LowRam build.prop patch, but only L has actually worked.
[Nook HD, HD+ Android Development] frazor:
OK, this is where the tale starts to unfold.... I have. I have 2 Nook HD+'s I'm trying to do this with. One is running Amaces Lollipop build, and its working just fine so far (the above scenario I described seems to not be a problem on this device) but when I try to replicate this exact same setup, using the same steps and builds on the other device - it does what I describe above. So I have one device working just fine on an older build, and one device thats not playing ball and I'm determined to find the solution for.
[Nook HD, HD+ Android Development] Zippy Dufus:
Check/compare the detailed hardware specs on each device.

A long time ago during the original ROM development for this device, there were two different variants with one of them being susceptible to being bricked with the FTRIM command. I believe that [MENTION=4473900]amaces[/MENTION] came up with a special patch to avoid this issue.

Try searching these forums for more details. I don't remember how to tell them apart. My device is the type that was in danger.
[Nook HD, HD+ Android Development] mikeataol:
I have side by side on my desk a 16GB and a 32GB Nook HD+.

the 32GB unit absolutely refuses to use f2fs for /data . all kinds of bad happens if I try.

I have removed and rebuilt the partitions (sdparted) , tried several times before giving up. runs normally using ext4.

if you are using f2fs , I'd give a try using ext4
[Nook HD, HD+ Android Development] Merazomo:
I've been using this version of Inos for a very long time now: 7.1.2 NJH47F 181223. Are newer versions of Inos or aosp a lot better than when my (7.1.2 NJH47F 181223) version came out?

My Nook HD+ started giving me digitizer issues, so I got lucky on eBay by winning 2 supposedly "dead, not booting, broken" Nook HD+ tablets for $35 that actually had 2 good LCDs, 2 good motherboards, and 1 good battery.

My Nook HD+ is working great again; however, every time I update Magisk v18.1/Manager v7.1.1 to something newer, my Spectrum App stops working (crashes whenever I open it).

I got lucky I had a TWRP backup of 7.1.2 NJH47F 181223 with Magisk v18.1/Manager v7.1.1 to go back to. If newer versions of Inos/aosp are "a lot" more stable and superior in every way, I suppose I'm going to have to update at some point.
[Nook HD, HD+ Android Development] Zippy Dufus:
My comment was only to note that if you have two "identical" NookHD that behave differently, check to see if they are indeed the same. Different production runs of the Nook may have different hardware components.

See here for details: http://https://undocumented.software/wiki_dump/EMMC_Bugs.html

Maybe perform some diffs on other "files" in /sys
[Nook HD, HD+ Android Development] frazor:
Using ext4 on both (tried to change as little as possible from stock to begin with) so its not that... but the plot indeed thickens... Like you I indeed have a 16Gb and a 32Gb an I hadn't realised they were slightly different. And its the 32Gb one thats not playing nice. :(
[Nook HD, HD+ Android Development] Nolfer:
Try not using 1080p. Stick to 720p. If it goes black, skip to next video, and then back to the video and set it to 720p fast
[Nook HD, HD+ Android Development] grcd:
I am sorry to possibly ask something that is well known and documented, but I want to make sure I don't do anything stupid. I have the Nook HD+ (9") tablet which I have a very old CM version installed on. I want to update it to a more stable release as the current one it has has all sorts of problems (weird GPU graphical glitches, especially when turning on, rotating, pulling down notifications bar, etc.), random reboots and general instability.

In another guide the general advice is this:

. For Nook HDplus:

Copy

1. NookHDplus-CWM-6046-for-internal-memory-rev0-(07-13-14).zip,

2. cm-11-####-ovation.zip,

and

3. pa_gapps-modular-micro-4.4.2-20140426a-signed.zip

Which I translate to:

0. Wipe (Data? All?)

1. Install (new) recovery

2. install (new) rom

3. (optional) install micro gapps [or use aptoide, etc.]

I also have the following:

twrp-3.0.1-0-ovation.zip which I understand is the most recent and best operating recovery for the Ovation (Nook HD+)

and these three ROMS:

lnos_ovation-ota-NJH47F.181223

lineage-14.1-20191130-UNOFFICIAL-ovation

lineage-14.1-20171216-UNOFFICIAL-ovation

If my understanding is correct, the 2019 is the most recent -- with the NJH... one being from December 2018 -- a year older. However, I have heard lots of good things about the 2017 build.

Can anyone clarify

(a) the installation process

(b) which lineage OS ROM is the most 'stable' on this device for general lightweight use?

My main use is going to be reading PDF EPUB and other documents, with some very rare use of the browser, and perhaps note taking apps.

Thank you in advance!
[Nook HD, HD+ Android Development] mikeataol:
Yes, That TWRP should be fine.

I tend to use [MENTION=4473900]amaces[/MENTION] AOSP builds, which are trimmed down, more lightweight version than the LineageOS ones.

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778

I have run aosp_ovation-ota-N2G48H.181223.zip for a long time on several ovations.

Here's the key to installing...

install TWRP

reboot to recovery

Install rom

REBOOT TO RECOVERY

Install Gapps

REBOOT to recovery

Install Magisk if root is needed.

I have found the REBOOT TO RECOVERY repeats have been necessary for a long time, and I rarely have any issues installing.

Good luck
[Nook HD, HD+ Android Development] grcd:
Many thanks for this tip! I had just downloaded and installed the most recent version of LineageOS (from December 2019) but again it was very very unstable -- even worse than the very unstable CM I was using previously: frequent boot-loops, graphical glitches, and general instability as such.

I was not rebooting at every step when installing, so that could be one of the reasons. I will now try to do that with the ROM you recommended.

(1) Is Gapps necessary if I don't plan to install too many apps? Would the system be more stable/fast without it?

(2) Do I have to re-install TWRP (I have the recommended version 3.0.1-0 now) or not?
[Nook HD, HD+ Android Development] mikeataol:
It will absolutely will be faster if you can live without gapps.

No need to reinstall the recovery /TWRP if it has installed once and is working as intended.

Cheers.
[Nook HD, HD+ Android Development] frazor:
Does anyone know of a custom ROM specifically for the 32Gb BN Nook HD+?

So far in my experimentation the 16Gb is fairly solid with all the ROM's I've tried (foibles aside), but the 32Gb is largely not - all sorts of quirks from not being add additional users, black screens on video playback (but not always initially), locks, reboots, etc. So I'm guessing the blobs/drivers being widely used match the 16Gb version, but not the 32Gb version?
[Nook HD, HD+ Android Development] LBurdick43:
I'm likely wrong so don't quote me, but I'm fairly certain the issues stem from different eMMC chip variants used between the 16Gb and 32Gb models.
[Nook HD, HD+ Android Development] mikeataol:
for reasons unknown to me, both my 16Gb and 32Gb units degrade over time.

What used to be a great release seems to be wonky even after repartitioning.

( it could be that I tend to shut them down by hard powering them off and I'm killling the emmc? )

lately I've loaded the Unlegacy Android last version for Ovation and they both have seemed fine.

I have also avoided f2fs.

https://builds.unlegacy-android.org/aosp-7.1/
[Nook HD, HD+ Android Development] jelabarre59:
I tried that aosp-7.1 image for my Nook Tablet (the CWM boot screen says it's a 16GB model), and it worked ONCE. Then when I tried to install OpenGapps (7.0 pico) it said it was the wrong revision (obviously). So I downloaded the 7.1 OpenGapps-pico, it said there wasn't enough space. This is with ***PICO***, mind you. I went back to a 7.0 flash image (aosp_acclaim-ota-NBD90Z.161020.zip) which had reported as 7.0 the last time I had flashed it, and it took the OpenGapps 7.0-pico package.

NOW if I try to flash the very same 7.1 package that worked one other time, it NOW tells me there's not enough space. I've used TWRP to wipe ALL partitions in the tablet, still fails. And if I try the 7.0 image, which flashes OK, then the 7.0 Gapps insists it's now 7.1.2. (????)

I need to outright delete all the partitions on this, and have the newer image re-create them from scratch. At one tome I had an image that would do this, but I can't find it anymore, nor can I find a reference to it. Additionally, the tablet refuses to boot off of the SD card (I was trying an older CWM/acclaim image, written to the SD card from TWO different machines, neither worked).
[Nook HD, HD+ Android Development] Zippy Dufus:
Interesting.

I still regularly use my 16GB Nook HD+ and my ancient Nook Tablet.

The tablets works are working well but the HD+ had degraded. I recently largely resolved the HD+ degradation by reformatting all partitions and re-installing the ROM.

My other suggestion is to forget about installing gapps. Instead, for the few key apps you really need, download the apk or grab the Titanium backup apk from a different device and install them directly.

The only issue with this is that some apps require the google services to be install to function.
[Nook HD, HD+ Android Development] Rapier216:
Question re: redoing partitions...

Hi Zippy,

If I may ask... how did you reformat all the partitions?

I'm not into programming but I can get myself in trouble easy enough :) I have flashed my HD+ several times.

Currently it has CyanoBoot, as I used to have CM1x. versions, but the last time I flashed I used lineage 14.1 (7.1.2) and I've had random issues. Basically, I think I've flashed so many times that it doesn't even know what it is :eek:

I'd like to see if there's a way to just wipe everything and start over with a clean slate and clean install (AOSP seems to be the recommended version?).

If I can get step-by-step instructions for reformatting and installing an AOSP image, it'd make me feel a lot better about keeping my HD+ :D

Thank you very much, I appreciate any help you can offer.

Rapier216
[Nook HD, HD+ Android Development] AlexanderF69:
Downgrade to Kitkat 4.4.4 for a stable Nook HD

To all those struggling with the various Various AOSP and Lineage builds, please consider downgrading to CM Kitkat 4.4.4 builds posted by secretwolf98. I found both the AOSP and Lineage builds of later Android versions posted by amaces and others to be very unstable and slow, particularly with respect to wifi stability. About a month ago, I downgraded to secretwolf98's 4.4.4 CM build again and my Nook HD has been running solidly and zippily ever since. Sure certain apps won't run on kitkat, but that is the price to pay for a stable, fast device. See the first post in following threads to get the downloads.

Nook HD+ https://xdaforums.com/nook-hd/general/rom-lineageos-11-t3668779

Nook HD https://xdaforums.com/nook-hd/development/rom-lineageos-11-t3665351

Good luck!
[Nook HD, HD+ Android Development] Zippy Dufus:
I have TWRP 3.0.1-0 as my recovery and simply go to Wipe -> Advanced Wipe and checked Dalvik / Art Cache, Data, Internal Storage, Cache and System. Then chose Swipe to Wipe.

After that, I reinstalled the ROM (the one in my signature).
[Nook HD, HD+ Android Development] Rapier216:
Hi Zippy.

Ok, I tried that one time (but it may have been on the phone that I'm also working on) but will try again.

Have a great week :)
[Nook HD, HD+ Android Development] jelabarre59:
That's not sufficient. Right now the Nook Tablet is telling me the internal storage is 1G in size (it's a 16G tablet). So it's trying to shoehorn everything into the user data partition, rather than the entire system storage.

Thus why I need something to delete the partitions, not just wipe them (which would still leave the problematic partition layout).

---------- Post added at 01:45 AM ---------- Previous post was at 01:24 AM ----------

Tried that one, you can't get anywhere with it because it's repeatedly reports "the process android.process.acore has stopped". As soon as you confirm the error, it immediately comes back up. There is NO time to do anything with the tablet under that build.

There's why I say I need to absolutely remove all partitions (not just wipe the existing ones) and start over, because right now the whole storage layout on the tablet is wrong. If I can't even flash a "pico" Gapps without it saying it's out of space, then the layout is fubar. And yes, since I'm trying to use it as a Calendar display for Google Calendar, I most likely need the Gapps core.
[Nook HD, HD+ Android Development] mikeataol:
if you have working adb and a pc its not that hard.

You would definitely want to print out your current layout, and then u would have to recreate as close as possible what the real layout should be.

you might try this first

theres an ovation repit which may or may not work to reset you to stock

"just rename REPIT to this and flash:

lanchon-repit-XXXXXXXX-factory=448M-system=672M-cache=464M+wipe-data=13184M-hummingbird.zip

lanchon-repit-XXXXXXXX-factory=448M-system=672M-cache=464M+wipe-data=13184M-ovation.zip"

https://github.com/Lanchon/REPIT/issues/59

https://xdaforums.com/nook-hd/help/...lternative-t3844912/post77673299#post77673299
[Nook HD, HD+ Android Development] jelabarre59:
I need to set this aside for a bit, I was getting too aggravated by it. But I also remember I have a second Nook Tablet (around the same age) that has a bad screen. That unit had already been re-configured with the different partition layout, even though the CM version is a few years old now. So maybe swap the good screen to a device that has the right layout already.

The devices I'd really like to upgrade would be the couple of XO Tablets I have. There isn't a pre-existing image, so I'd have to figure out how to either pull the original image and customize it (clean out the cruft and disable the Sugar UI) or build a new image (I don't even know how to do that yet). But that's a topic for a different forum.
[Nook HD, HD+ Android Development] Merazomo:
I went back to the last version of Marshmallow that supports my Nook HDMI adapter; arcade emulation purposes, I've turned my Nook HD+ into an occasional gaming station. Marshmallow has been a lot smoother than Nougat, it seems the newer the OS, the more my Nook struggles; that's to be expected. I gave KitKat a go, but the few times I tried to play flash video or install apps like Firefox Focus, my Nook HD+ either crashed or said the app was incompatible.

Marshmallow is good enough for me; however, I'm not able to enable "Magisk Hide". I was able to install Magisk without any issues, but the "Magisk Hide" tab just won't stick. Every time I exit Magisk and open it again, the Magisk Hide option has been disabled again. I do remember "Magisk Hide" worked on a version of Nougat I had installed in the past. Does anybody know if it's a partition issue? or a Marshmallow incompatibility? I remember reading comments about F2FS, Ext4, etc. Would a specific partition type affect the Magisk Hide option?
[Nook HD, HD+ Android Development] nmyshkin:
I hope you're still around somewhere :)

Frustrated by my inability to boot a "new" Nook Color from an sdcard, I've returned for a deeper look at an acclaim build of LNOS. My last foray was back in 2017. My notes from then say to flash addonsu-14.1-arm-new.zip to enable root. Unfortunately I did not keep the build I had looked at or even it's number. Now I find that I cannot get root access with the "current" builds no matter what I try, including the official LineageSU addon. So back to the frustration...

Do you have a build number and an addonsu zip that work together? I can find the ROM you reference, but there is no addonsu with the creation date you give.

Edit: and the answer is that the addonsu-14.1-arm.zip created

1

2/11/18 gives root with the build you listed. Perhaps you had a typo there. Anyway, all is good except for running Kodi. That it does

not

want to do.
[Nook HD, HD+ Android Development] Diagon:
Actually, you've both got typos! It's 12.01.18, as listed in the "updated" column, here:

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww

I'm not able to find lnos_acclaim-ota-NJH47F.180211.zip though. At present, in the acclaim directory it's lnos_acclaim-ota-NJH47F.180713.zip
[Nook HD, HD+ Android Development] nmyshkin:
I truly appreciate the work [MENTION=4473900]amaces[/MENTION] has done but I have to say I think those listings are somewhat possessed. My copy shows the date I listed. Whatever, it works. As to the ROM, it's in the "obsolete" folder. Many interesting things are.
[Nook HD, HD+ Android Development] Merazomo:
Did anyone ever find a fix for the bug that makes the notification drawer "not slide down anymore" or even "show up" from the home screen, right after changing the home screen's stock wallpaper on lnos_ovation-ota-NJH47F.181223.zip or aosp_ovation-ota-N2G48H.181223.zip from the stock wallpaper to anything else?

The notification drawer does slide down when doing it from inside an app or the settings app, but it will never work again from the home screen once I change the stock wallpaper; it disappears when sliding it down. I can see the notification drawer for just a split second if I rotate the screen horizontally or vertically when it's not showing up.
[Nook HD, HD+ Android Development] xdause:
So i'm on aosp ovation N2G48H but the screen ocassionally dies with black screen with blacklight on which kills the battery. I searched this thread and don't see any mention of this issue so figure I should ask because I'm close to trying another rom.
[Nook HD, HD+ Android Development] Diagon:
Just for anyone else who is coming this way ...

My version of TWRP after installing via amaces' root method and subsequently repeating the procedure from 3d to install the presently newest LNOS ROM, lnos_acclaim-ota-NJH47F.180713.zip, was 3.0.2-0. That had been installed as a zip. (I removed the recovery.img from that zip and confirmed it's the same as the official TWRP image.) The TWRP website's latest is 3.1.1-0, so I tried to install that official image according to one of the methods in these directions. Namely, flashing the new recovery image from the old. That failed on attempted reboot to the recovery. (Black screen, backlight on.) Perhaps it would have worked if I used a different method? I then tried another approach described there: downloading the most recent apk, and installing it. That downloaded the img file I selected (this time, 3.1.0-0), but then kept crashing when I tried to point the app to the location of that .img. So, I fell back on a third method described there. Namely, using a terminal to dd the image:

su - root; dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p3

The image I finally used with dd was amaces' ~/experimental/twrp-3.2.2-0-acclaim.img. That appears to be working. I haven't backed up or restored with it, but I can go into recovery and all the menus are acting sensibly. If I have any trouble, I'll try going back to 3.1.1-0 and dd'ing that in.
[Nook HD, HD+ Android Development] xdause:
not sure where to post this but it seems amaces lnos_ovation-ota-NJH47F.181223.zip won't work with the latest gapps pico. says there is not enough room. Found the repartition thread and got it to work.
[Nook HD, HD+ Android Development] maninalift:
Is it this thread that you used?

https://xdaforums.com/t/nook-hd-hd-...-partitions-without-wiping-your-data.3503615/

I'm experiencing the same problem and about to give REPIT a try
[Nook HD, HD+ Android Development] xdause:
I think so. it's been a while but many apps in ovation is no longer compatible like google voice in android 7.1.2 nougat play store seems to have corrupted had to clear cache/data of play store to get updates back. i'm basically just using this as an ereader as wifi still needs to be reenabled if it gets turned off (read known bugs https://xdaforums.com/t/2021-how-to-install-android-7-1-2-on-a-nook-hd-or-nookhd.4259749/). I'm actually thinking of restoring to stock since the play store seems to be dead. not even sure how to repit back to stock.
[Nook HD, HD+ Android Development] flyingpreacher:
I know this thread is wayyy old now, but for anyone who is interested, I got Marshmallow installed on my Nook HD Plus with GApps and got ROOT!

Here is what I did:

I used cm_ovation-ota-MOB31K.161125.zip from Amaces folder here.

I uploaded the Open GApps zip to Mediafire here. The current ones won't fit because they are too big for the system partition and you will get an error. The SuperSU root zip is here.

I rebooted to TWRP recovery and wiped my system, data, and other partitions clean. Be careful not to wipe your SD card! I changed data and cache to F2FS, then I installed the ROM and GApps zips. I rebooted and then I waited... It takes 4-5 mins for the first boot. I mention that because I don't want anyone to think their Nook HD is stuck.

Once you setup your Nook after the first boot with GApps, reboot to TWRP and install SuperSU. Reboot back into your system. That should be it. You are now rooted!

I hope this helps someone. I was excited about it and I hope you can get excited too. :D
[Nook HD, HD+ Android Development] Sus_i:
My nook hd+ works fine with aosp / lineageOS 14.1

I installed the aosp_ovation-ota-N2G48H.181223.zip and flashed open_gapps-arm-7.1-pico...

and for systemless root I use Magisk. :)
[Nook HD, HD+ Android Development] flyingpreacher:
I could not ever get mine to work as well with LineageOS. I always had wifi problems or graphical glitches. Maybe I will try it again some time. Thanks for the info!
[Nook HD, HD+ Android Development] Sus_i:
Tested both images, but ended up with the aosp build instead of lineage :)
[Nook HD, HD+ Android Development] lavero.burgos:
Hello!. Wondering if you kept the marshmallow rom or could upgrade to nougat. Also, did you run into issues because you changed data and cache to F2FS?

Thank you for the info and the files.
[Nook HD, HD+ Android Development] lavero.burgos:
Hi, do you still have the nook hd+? if so, do you still use the AOSP 7.1 build? can you share the pico gapss that worked for you. Thank you in advance.
[Nook HD, HD+ Android Development] sega dude:
How do I get root working on the hummingbird AOSP 7.1 ROM? I am using the latest Dec 23, 2018 build. I've tried various things I saw on posts in this thread, including flashing the addonsu-phh-arm.zip and installing the phh Superuser app from F-droid. I still did not have root after that. Today I tried using the Magisk app as described in this post, but I couldn't find a "Download Zip Only" option. Any help getting root working on the hummingbird AOSP 7.1 ROM would be greatly appreciated.
[Nook HD, HD+ Android Development] ze7zez:
Change the extension of the Magisk.apk file to Magisk.zip, that you can use it for flashing in TWRP.