yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] :
Best guess is that you somehow managed to get them removed. The correct ones are located in the system.new.dat compressed file within the flashable aosp zip (yup, they match: 258,444 bytes).

It doesn't look like they will be flashed (according to file_contexts anyway) if you manage to lose them... but not 100% certain. Not all files may be installed from the flashable zip.

They also should have been there for you to flash in the first place as getprop is used for a required device check. So that part is confusing, but then again, your playing around with terminal and the root dirs....

Not sure if the recovery version could affect it as wrong recovery likely should cause zip not to be flashed instead of incorrectly flashing.

Conversely, cyanogenmod 11 official creates the link during the install script AFTER the current one is used for device checking (I assume because it wipes it out - I don't really care about looking to it further):

symlink( ... "/system/bin/getprop" ... );
[Nook HD, HD+ Android Development] pchc_lx:
stupid question here, but is there a changelog posted for these releases? I recently got everything set up & working beautifully- and wondering if I should flash the newest 4/22 MOB30D file or leave things alone for a while.

also, a suggested process for truly proper updating / upgrading? easy as flashing the .zip in recovery & rebooting, or is a factory reset needed to be sure, new gapps, wiping etc etc? thanks for any pointers...
[Nook HD, HD+ Android Development] TBueno:
I understand you, when everything's working perfectly, why bother touching it? However, reggressions are very unusual in AMaces' builds, so I tend to flash new builds as soon as they come out just to check if something has been improved even further.

You can simply flash the .zip and let it reboot, there's no need to wipe anything. New GApps are only needed if you're coming from Lollipop (or older)-based builds.

If you can spare a few GBs, do a nandroid backup before flashing and keep it only until you're sure the new build is fine too (it usually is).
[Nook HD, HD+ Android Development] neonleon29:
I've been following amaces work on screen casting for awhile. If you want to read more about what he has to say, see posts #398, #403 & #427 in this thread. From what he said, there is a chance he won't be able to get screen casting to work for CM builds. But it works great on the AOSP builds!
[Nook HD, HD+ Android Development] KostasR:
Hey guys. I completely wiped and installed latest cm13 and Pico gapps (nano weren't fitting) and also supersu beta. The problem is that the device has stuck in boot logo. It looks like it's loading but it is there for 20 minutes or so. I am using Nook HD +. Anyone else has this problem? Will it ever boot?

Sent with my thumbs using Tapatalk 4 VIP
[Nook HD, HD+ Android Development] neutronjeff:
Do you have a bootable SD card backup? What device, what recovery?
[Nook HD, HD+ Android Development] smileyint:
My nook HD has decided to stop working. Battery level inconsistent and always sudden shutdown. I guessing it could be the aging battery after tearing down the device. No battery bloat. Reconnect battery after long wait. Nothing helps...

I buying a new battery in the hope that i can still continue to use my beloved nookHD. Keeping my finger crossed.

Btw, i clean flashed the latest cm the second time and confirmed that the settings pulldown is missing and realised that i cannot change the usb to mtp without third party apps so i downgraded to early April built. Not long the above happened. Game over for now...
[Nook HD, HD+ Android Development] neonleon29:
It shouldn't take 20 minutes to boot. Are you able to get back into your recovery? You should be using TWRP. If you can get back into recovery, do a factory reset. Then flash your ROM and Open GApps. Don't wipe anything after you flash these two files. Reboot the tablet and hopefully your ROM will load. Afterwards, you can go back to your recovery and install supersu. I'm using supersu v2.65 systemmode, which was posted earlier in the thread by Denooker, without any issues.

---------- Post added at 12:37 PM ---------- Previous post was at 12:26 PM ----------

When you try charging your Nook, do you see the amber light where you plug in the charger? Wondering if you try charging it until the amber light turns green and then holding the power button if that would start your Nook up. And if it did, then you could go into your recovery and do a factory reset and go back to your early April build in case something got corrupted when flashing the latest ROM.
[Nook HD, HD+ Android Development] chuimk:
I recently upgraded my son's Nook HD+ (aka ovation) to cm13. Make sure you upgrade TWRP as earlier versions are said to have issues with latest roms, which I did. I then wiped Dalvik cache, system, data and cache (all but internal storage and external SD card). Finally installed cm13, nano gapps (which did install) and latest supersu release, in this order.

It all installed correctly but I had issues. I don't recall exactly but it might have been the same as you, a never ending boot. I tried simply reinstalling without a wipe and couldn't reinstall nano gaps. Wiping system did the trick so I guess that should solve one of your problems.

As things still weren't perfect (and again I can't recall what it was) I decided to do a wipe again, this time including the internal storage. Of course I first backed up whatever I needed from it via USB while running TWRP (I didn't know that functionality existed in TWRP until I did this; pretty useful!). Finally reinstalled all the things again and got the tablet to work as expected. Whew!

Thanks to amaces and co for all your work into extending all of our Nook's useful lives!
[Nook HD, HD+ Android Development] smileyint:
hi

the green led will light even at non 100%. i had restored to earlier built for the settings pulldown functionality. i observed the battery level going crazy before the device turn off again. i hope the battery is the culprit. Thanks
[Nook HD, HD+ Android Development] KostasR:
I decided to put the old twrp version and flash one of the older builds I had in the device. I flashed a January build that worked before, factory reseted, didn't install gapps or anything else. Still device is stuck in the animated blue cm logo :( Maybe it's a bootloader problem? What should I do? Is it bricked?

Sent with my thumbs using Tapatalk 4 VIP
[Nook HD, HD+ Android Development] ieatabiscuit:
Only soft bricked. It is fixable, but it's tedious sometimes. There's a couple things to try to do to fix it still. First and easiest is go ahead and re-update to the latest TWRP (just to make sure we're on the same page).

**THIS WILL WIPE EVERYTHING*

From there have a known good ROM and GApps handy on an SD card (the latest is very functional, I'm using it right now, and it's been great. You use what you prefer though).

Next do the dirty deed of going to advanced wipe, and check EVERYTHING except the SD card option, and swipe for OK, then put /data and /cache to f2fs if you haven't already got that set (it makes things even snappier)

Then now that everything is completely wiped, reflash your ROM and GApps.

This is usually not a needed extent of wiping effort, but in your case it could fix your issue. If it still gives grief, or you suddenly run into strange battery issues then whisper me, and we can take other measures. I'm pretty sure your hardware is fine though, I've done a lot of toying with the partitioning options and with recovering from soft bricking just to make sure I know how well enough to walk others through it (like my daughter lol).

---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------

Step into my office good sir. I have good news, your not going to have to blow up your nook today. There's things to try that can be the cause. First try things with no SD card, or a different one. If you don't use one anyway, then there's other options. I have posted a walkthrough on how to fix exactly your issue a few times in this thread, so I don't want to clutter it with the same thing again. I have had this issue, I have reproduced the issue deliberately, and I have been rid of the issue for quite some time now also. It's just a matter of a partition that handles the battery status information being messed up. To charge the Nook you have to have it completely shut down, and finesse it just right to get that orange light on. IT IS NOT CHARGING IF IT IS NOT ORANGE. Feel free to whisper me with any questions or comments on the subject. I'll help however I can.
[Nook HD, HD+ Android Development] KostasR:
I downloaded the aosp build to my laptop and then copied it to a formatted micro SD. I mounted it to the nook and then I copied the file to it. Flashed again latest twrp and completely wiped once again and flashed the aosp build with no gapps. Finally rebooted. Voila. It was working. Then went back to twrp and flashed latest cm13 and nano gapps. It finally worked! I don't know how this issue occurred. I have been flashing this bad boy since the beginning. Oh well, all turned out good for now...

Thanks everyone

Sent with my thumbs using Tapatalk 4 VIP
[Nook HD, HD+ Android Development] ieatabiscuit:
Glad we didn't have to get into the dirty bits to get it working again. Like I said, sometimes you just have to finesse it to get it to work.
[Nook HD, HD+ Android Development] brenyoka:
Is there a change log for the latest build? I would appreciate even just a brief description of the latest changes each time a new build is compiled. Thanks.
[Nook HD, HD+ Android Development] OldComputerGuy:
Have just flashed the updated cm_ovation-ota-MOB30D.160422, tablet is extremely fast. I still see that HDMI output does not work, blank screen. Will this be addressed in later builds?
[Nook HD, HD+ Android Development] isaacalich8401:
This doesn't seem to have a low battery cut off, at least on my HD+... Got down to 2.35 volts and just decided to shut it down there... Won't charge properly now, hoping to get it back up to its normal voltages. PLEASE FIX THIS!

EDIT: My mistake about it not charging, plugged it into a higher amp charger and it started charging.
[Nook HD, HD+ Android Development] ST Dog:
Minimum allocation based on block size?

I'd have to go look up extfs specs on how symlinks are actually stored in the filesystem. It's been too long since I looked at it (early days of ext3).
[Nook HD, HD+ Android Development] pchc_lx:
whoa, I had never heard of this. ..now i'm tempted to reformat my /data and /cache to f2fs for these speed & battery life improvements. re-formatting would wipe everything and require re-flashing the ROM and GAPPS I assume? so maybe I'll wait for the next build to do it. but sounds very tempting.

random thought, but would f2fs be a preferable filesystem for SD cards as well? currently using extFAT for mine, I believe.
[Nook HD, HD+ Android Development] ieatabiscuit:
Yes you'll need to reflash, and it will wipe what you have already, so back it up. No don't do the SD to f2fs unless you're using it as adopted storage, Windows and other devices might not recognize it, other than that, I would assume it to work well enough though.
[Nook HD, HD+ Android Development] OldComputerGuy:
I have attached a dmesglog containing data when hdmi plugged in. This is an excerpt from the log after the edid info was received:

force_timings monspecs

[78673.075134] panel size 71 by 40

[78690.275451] Current video settings do not support audio.

[78690.281341] asoc: can't open codec hdmi-audio-codec

[78690.848266] init: Service 'media' (pid 154) killed by signal 11

[78690.856597] init: Service 'media' (pid 154) killing any children in process group

Looks like it is pointing to audio over hdmi problem.
[Nook HD, HD+ Android Development] SouthernGeorge:
I'm sorry if this has been addressed before, I searched, but didn't seem to find anything. I've been having this issue where my battery dies super fast. I did a little test a while back. I charged it, left it on in airplane mode and didn't touch it for the entire time. The battery lasted 3 weeks without dying. Which is great. But, if I ever do anything processor intensive (like play a game) then the battery will act normal for a few minutes, and regardless of the current battery percentage, drop to 1% and then my Nook will turn off. If I plug it back in, then it turns on and is around the same percentage as what it was before.

Side note. I turned off my tablet for about 2 years. I turned it back on In February and have been playing with it off an on since then. So I suspect that the battery is shot. But I'm hoping its not a hardware issue.

Anyways, any help would be appreciated! I love the ROM though!
[Nook HD, HD+ Android Development] Velines:
I am unable to install CM13 in combination with GApps nano due to the gapps script telling me there is not enough space available. Checking in TWRP's terminal, around 222MB are free on /system so in theory I should be able to install it, right?

I also tried the pico package which installs fine, but results in setup wizard crashing all the time.

Is there anything I can do? Like resize partitions or something?

Sorry if this already been asked, but I did not find anything. Please link me to the appropriate answer.
[Nook HD, HD+ Android Development] ieatabiscuit:
I've explored battery issues on my ovation, and daughter's hummingbird rather extensively, and explained a process that has so far completely eliminated any battery problems I've known (to include it not charging) on page 59, post 584. If you have any questions about it feel free to PM me.

---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------

Sometimes, after a few factory resets and what not, the /system partition can get cluttered by it being resized by ROMs repeatedly. Try going into advanced wipe options, and resize and repair /system. USUALLY that works. Full wiping partitions with advanced wipe can eventually lead to fals battery readings, and thus charging, and battery life issues that are fixable, but tedious to deal with.
[Nook HD, HD+ Android Development] belfastraven:
I am trying to look into this, but am waiting for an HDMI adapter which should arrive later today, to see if I have made any progress.
[Nook HD, HD+ Android Development] belfastraven:
New 5/03 AOSP rom from experimental

Seems to be fine on hummingbird. On the first couple of boots, it seemed slow to make the network connection-- That problem doesn't seem to be there right now. The local file manager still doesn't work, but Solid File explorer is fine. Multi-colored boot animation is back :)
[Nook HD, HD+ Android Development] ieatabiscuit:
We don't need no local file manager!! We got the Dewy Decimal System to keep our stuff in order!!! Sorry, I couldn't resist the urge to do that.
[Nook HD, HD+ Android Development] sepehr@teh:
I want to install new experimental , on my AOSP . How can I do without installing everything?
[Nook HD, HD+ Android Development] Velines:
Thanks, but unfortunately that didn't work for me. But at least I could re-flash the pico gapps package and it's working now :)
[Nook HD, HD+ Android Development] ieatabiscuit:
Try a dirty flash. If you use xposed, it will need to be reflashed.
[Nook HD, HD+ Android Development] sepehr@teh:
In experimental folder there are two there file for audio. What are they for? And how can I use them ? ( audio.hdmi.ovation.so & audio.primary.ovation.so )
[Nook HD, HD+ Android Development] OldComputerGuy:
They are there for testing of the hdmi problem. They don't fix anything.
[Nook HD, HD+ Android Development] rpadula:
i'm still at official cm11 and planning on make the jump to cm13.

saw there aren't cm13 experimental builds, they will eventually appear again or should i just make the move to AOSP?
[Nook HD, HD+ Android Development] sepehr@teh:
I did dirty flash: Wipe cache + wipe dalvik . Then flash new May version of AOSP :

1- Notification menu , does not work . Shows nothing.

2- wireless doesn't work . Only shows a saved connection.
[Nook HD, HD+ Android Development] ieatabiscuit:
It did that to mine before, not sure why. Try reflashing, if that doesn't work, do a backup of your /data in TWRP, then do a clean install, then restore the /data. I figured that when I did it to mine it was a fluke, not seen much about it happening on here, so I just reflashed, and ignored it.
[Nook HD, HD+ Android Development] sepehr@teh:
I did again . Keep data backup . Wipe ( restore factory settings) . Flash new image , restore backed up data .

.

The problem exists :

Notification menu does not work .

Fortunately, my CMW full backup , saved my Nook HD+ !
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm going to have to leave this one to someone else then. Aside from the full wipe and redoing your tablet from scratch (what I do to mine frequently, so that could be why it cleared up on mine), I really have no idea beyond what we just tried. Sorry I couldn't help further :(
[Nook HD, HD+ Android Development] jaydizman:
I flashed cm 13 then open gapps pico and I'm loving this build. I did however seem to lose root access in the Rom (no supersu) can anyone help with that? Maybe a flashable supersu? Or explain what I may have done wrong.. Thanks ahead of time -hummingbird
[Nook HD, HD+ Android Development] ieatabiscuit:
Enable developer options, go into there, disable root, then enable it again. Nobody knows why this is needed, but it works 100% of the time. Don't flash SuperSU as it will conflict with the built in root.
[Nook HD, HD+ Android Development] jaydizman:
Thanks for the quick response. What would I do after that? Supersu from the market won't install SU binary.. I know I'm missing something
[Nook HD, HD+ Android Development] ieatabiscuit:
It's all handles in house on CM ROMs. No need to do anything further, it will take care of it all for you.

SuperSU's great, but not on CM, it's got it's own SU manager built in. SuperSU is perfect for almost every ROM there is, but it's actually a bad idea to install SuperSU on CM ROMs because of their in house root manager and SuperSU conflicting as they try to handle the same thing at the same time in their own way.
[Nook HD, HD+ Android Development] jaydizman:
Not sure I understand. I know cm based roms usually have su built into the settings this does not. Also installing from the market doesn't install su binary I have apps asking for su permissions and no way to allow it. I've tried turning root off then back on in developer options...
[Nook HD, HD+ Android Development] rpadula:
i flashed the latest aosp and the pico open gapps and says flashing was completed fine.

when i reboot to system nothing google related appears,no play store, no services...
[Nook HD, HD+ Android Development] ajislav:
Did you format /system before flashing?

Chech your free space in /system and then try with nano..

Or older Pico.
[Nook HD, HD+ Android Development] rpadula:
Went for the nano gapps and everthing worked out

Thanks!
[Nook HD, HD+ Android Development] ieatabiscuit:
Turn CM's root control completely off, then turn it completely back on for apps and adb, then restart if it doesn't pick up on it automatically. That's how I've always done it. If that fails, then google a copy of SuperSU.zip and flash it that way, and update that to the latest via the play store. It's a bit of a last-ditch effort though, because unless you make sure the built in root is disabled, then it can make craziness happen. If SuperSU's not installing via the play store though, the flashable version will do the trick. It will then cooperate with the play store to keep it's self up to date. I'm using AOSP myself though, so the latest CM is unknown to me as far as bugs go.
[Nook HD, HD+ Android Development] jaydizman:
Thanks I'll try to track down the correct flashable supersu.zip. Meanwhile I'd like to know if the #su appears in the settings for anyone running this. All my other cm roms it's incorporated in settings..
[Nook HD, HD+ Android Development] ipdev:
Latest beta.

http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip

On ovation (& a few other devices) I have to force the install.

In twrp, use terminal(in advance settings) and type the following. (Only space is between echo & SYSTEMLESS)

echo SYSTEMLESS=false>>/data/.supersu

Then go back to the main menu and install the su zip.

- SuperSU thread.

http://xdaforums.com/showthread.php?p=23427715

- beta thread

http://xdaforums.com/showthread.php?p=55256620

Sent from my SM-T330

(Running 2.71 on everything. android 4.x to 6.x)
[Nook HD, HD+ Android Development] robak1965:
SuperSU System mode zips already to go.

http://xdaforums.com/showthread.php?t=3286120
[Nook HD, HD+ Android Development] sepehr@teh:
New AOSP ver. moved to acclim folder. What that mean then ?

I tried that experimental , it has some issues ( posted few posts before ) , when we expect new one ?

Or we have to go on with Apr 7 ver. ?
[Nook HD, HD+ Android Development] neonleon29:
Not sure if this helps at all with the HDMI issue, but post #628 (pg. 63) from sasmith-129 says HDMI was working in one of the January builds. Maybe someone can compare the latest build with a January build to see what the difference is for HDMI if anyone still has a January build. Zippy Dufus also posted a logcat for HDMI in post #757 (pg. 76).
[Nook HD, HD+ Android Development] belfastraven:
the January builds are posted on Box in the "obsolete" folder, if you, or anyone else wants to try to find one that works. Although I have my adapter now, I have not been succesful in getting HDMI to work on/from any of my devices. I could have a bad adapter, bad cable, etc. and am still trying to run down the problem. KNowing which build worked might at least help eliminate some possible avenues of further investigation.
[Nook HD, HD+ Android Development] OldComputerGuy:
It also worked in CM12, even though the screen was upside down and resolutions were incorrect.
[Nook HD, HD+ Android Development] neonleon29:
Unfortunately I don't have an HDMI adapter to test any of the old January builds to find out which one had HDMI working. Maybe oldcomputerguy or someone else with an adapter can test the January builds in the obsolete folder and post which one works. That would seem to be a good starting point. I also found where amaces fixed the audio issue for HDMI in the Lollipop thread. It was in his 7/21 build. Here is a comment from amaces (post #668 in CM12 thread) about HAL with a link to github. From amaces - "The issue was not so much device-specific, but it had to do with the HAL that we're using. If your Samsung tablet is using a HAL comparable to what we have in https://github.com/airend/android_de...ee/cm-12/audio, then look for something like AUDIO_DEVICE_API_VERSION_*; it may be that you have to restrict it to a lower version, to prevent AudioFlinger from using features that don't work."

Not sure if any of this will help, but figured it can't hurt to post it. amaces also talks about the video inversion being HAL related in post #664. I don't know if he ever fixed the inversion.
[Nook HD, HD+ Android Development] 123421342:
Its incredible that after years and years this device is still being updated, just another reason to always allow bootloader unlocks!

Thanks a lot for this rom, it is working very well
[Nook HD, HD+ Android Development] granny smith:
This is for hummingbird and CM13 builds. I didn't try AOSP. I know the HDMI adapter, HDMI cable, TV and Nook all not damaged because I successfully use the HDMI adapter with CM11 all the time.

The build on 3/14 does not work. According to my TV a resolution of 720x480 is set and the screen is just black instead of showing an image. Builds 2/07 and 2/22 also do not work - the screen shows a garbled distorted image with a resolution of 1080. The garbled image is also inverted - see the attached picture. I have not made my way to the January builds to find a good working build. I'll update when I get a chance to test out the January builds.