yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ General] ipdev:
More WiFi info under the cm13 thread.

http://xdaforums.com/showthread.php?t=3239269

Keep in mind it is for cm13 though.
[Nook HD, HD+ General] woldranger:
What are the main advantages of going back to an older version like CM11? I didn't realise that there were still significant stability issues with CM12 - oops!

Could anyone point me to a solid tutorial for installing either CM 11 or 12 (at the mo I think I'd give CM12 a shot and if it's still buggy, I'll try CM11) as pretty much everything I've seen requires me to either already have a custom recovery or to be rooted - my HD+ is completely stock.
[Nook HD, HD+ General] digixmax:
Use the guide in the OP of this thread for CM12, and this guide for CM11.
[Nook HD, HD+ General] woldranger:
I managed to get CM12 running (had to try a couple of sd cards) though I flashed the GAPPS zip when I did the install but there's nothing there. I've since tried to flash the GAPPS in TWRP but I couldn't mount the first card, so formatted the second one and flashed the GAPPS zip.
[Nook HD, HD+ General] PeteInSequim:
I've always chosen to leave the system partition unmodified. I'm not aware that CM-12.1 has an associated update service at all.

I've exercised [MENTION=4473900]amaces[/MENTION] version cm-12.1-20151018-UNOFFICIAL since it was posted last October with never a problem other than the unexpected restarts on shutdown. I don't know why some consider it to be buggy. I've also tried his version cm_ovation-ota-MMB29V.160314 with very good results, but not yet heavily exercised. Again though, the restart problem is present but isn't that also the case with CM-11?
[Nook HD, HD+ General] baytee:
Thanks Pete, I may re-do mine with CM12 then. Maybe you could also answer a couple other questions I posted in the main forum. It's here:

You already confirmed the restart upon shutdown problem isn't just me. But I had a question about the Nook app install. Also I've had problems with stock browser (the one with the blue globe icon) crashing & taking me back to the "desktop". I also noticed that sometimes it won't charge unless I have the tablet turned on. Maybe some of these weird problems have to do with the nightly I'm using though.? Or are these issues typical and that's just as good as it gets using CM ? Over and over I see people saying nightlies are usually as stable (and sometimes more so) than "M" builds.

Also, the links to NotreDame from your PDF, take you to a selection of a newer TWRP, 3.0 so I suppose I'll use that. But your CM link takes me to NotreDame page where it shows only two CM files, cm_ovation-ota-LMY48Y.151218.zip and cm_ovation-ota-MHC19J.160401.zip do you recommend one of these, or the one at the "obsolete" link in your PDF?
[Nook HD, HD+ General] tedrogers61:
Just a point of note, for me the micro SD was not bootable unless I did each step (Win 10) in turn and APPLY each time. So, create fat32 primary > APPLY, set active > APPLY. It just wouldn't boot to sd card otherwise.

Apart from this, really great stuff. Finally managed to convince the Mrs that her Nook is a pile of poop, and she needs something else on it.

Plus, I had an urge to tinker! :cowboy:
[Nook HD, HD+ General] desertandroid:
Successful CM12 Installation

I wanted to say thanks to Pete for putting together his excellent CM12 installation guide for the Nook HD+. I appreciate his hard work for the benefit of others.

I experienced no problems during the installation. One month later, I’m extremely happy with the performance of the Nook. I don’t experience buggy, unstable performance as others have noted. My Nook with CM12 has shown me how useful a tablet can be!
[Nook HD, HD+ General] bubbelech:
Long time since I've used my Nook HD last time, decided to upgrade as per the PDF manual on first page.

Backed up my ROM, wiped all data, went on to install TWRP but getting the following message:

This package is for device: hummingbird; this device is .

Error in /external_sd/twrp-3.0.1-0-hummingbird.zip (Status 7)

Installation aborted.

As you can see I am using the twrp 3.0.1-0 (the one you get from the link in PDF).

Any ideas anyone? Thanks!

update:

will try another TWRP archive (from the PDF) maybe this will work.

update 2:

guess this is related to havin EMMC CWM-based recovery V6.0.4.6 installed?

update 3:

installed CM12.1 zip without installing the recovery, seems to have booted up fine, optimized the apps. Will see if there will be any errors.
[Nook HD, HD+ General] PeteInSequim:
If I had to guess (and in this case I do) I'd say the ancient CWM you are using has conflicts with the modern TWRP 3.0.1.0 zip file, and this will probably never be fixed.

The new files offered by [MENTION=4473900]amaces[/MENTION] are now all Marshmallow-oriented. Look instead through the pages of his "obsolete" folder for "cm-12.1-20151018-UNOFFICIAL-hummingbird.zip" and "twrp-2.8.7.4-hummingbird-zip, which CWM should install properly.

Better yet try his latest Marshmallow and TWRP 3.0.1.0 versions in the "hummingbird" folder. For this you must create a new bootable microSD card using these files provided by [MENTION=5672278]belfastraven[/MENTION] and the downloaded zip files "cm_hummingbird-ota-MHC19Q.160407.zip" and "twrp-3.0.1-0-hummingbird.zip". These versions may advance by the time you happen to do this. The procedure is the same as described in the .pdf guide for CM-12.1, except with the new files.

And use a current GApps file for the ARM platform, Android 6.0 from http://opengapps.org/.
[Nook HD, HD+ General] bubbelech:
Absolute champion!

This is what I was thinking too, something to do with the recovery as the tablet hasn't been used in pretty much more than a year :eek:

I ran out of courage for today, but I'll definitely try the above tomorrow as I have missed GAPPS (oh me) which I obviously will need.

Thanks again, I'll post an update tomorrow in case this might help someone.
[Nook HD, HD+ General] PeteInSequim:
As usual I'm only guessing; is your Nook HD the 8 gB model?

Presuming you are using the files from [MENTION=5672278]belfastraven[/MENTION] to build your bootable microSD card and wiped the system partition before flashing I'd say repeat the procedure (including system wipe) using the pico version of Open GApps. Afterwards you can individually add only the apps you want from the Play Store instead of lugging around the full load or even the mini load.
[Nook HD, HD+ General] dmsims:
Pete

thank you - that worked (I thought I had done something wrong!)
[Nook HD, HD+ General] MrPresident:
write up was super professional!
[Nook HD, HD+ General] BexarTex:
Just joined to specifically thank OP for the guide. This post has rejuvenated my Nook HD+!
[Nook HD, HD+ General] tuffluck:
i'm a little confused. i already did this to get to an older cm11 version of kitkat 4.4. what exactly do i need to download to go to the current stable 6.0 build, and do i need to follow the instructions to start from the sdcard? if i go to cm website and click on ovation, i see "current nightly" and "current nightly recovery" but then the list of previous versions the most recent one is from 2014, so i'm just not certain what i'm supposed to download, nor am i certain about the current gapps that work, or if there are any other required files. lastly even CM's site itself states the directions for installing CM on the nook hd+ is incomplete, so i'm not sure what the actual directions should be.

thanks for any help.
[Nook HD, HD+ General] ipdev:
What version of recovery do you have installed? (twrp / cwm)

(Should move to cm13 thread)

http://xdaforums.com/showthread.php?t=3239269

(Link from cm13 op)

https://m.box.com/shared_item/https://notredame.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww

No official builds yet but, cm works great. Haven't had much experience with aosp, currently trying the aosp_ovation-ota-MOB30J.160503 build.

Sent from my SM-T330
[Nook HD, HD+ General] PeteInSequim:
There's a recently added paragraph at the top of the first page of this thread that hints how to install Marshmallow. The procedure is the same as described in the attached PDF for Lollipop but of course with different downloads. You must use a late model TWRP recovery utility instead of the older TWRP or CWM suggested for Lollipop.

Here's a summary of download sources:

Marshmallow and TWRP 3.0.1.0 zip files provided by [MENTION=4473900]amaces[/MENTION] for Hummingbird (Nook HD) or Ovation (Nook HD+). I suggest the cm versions over the AOSP versions, currently cm_hummingbird-ota-MOB30D.160422.zip or cm_ovation-ota-MOB30D.160422.zip.

For GApps, choose one of the ARM 6.0 offerings here. I suggest Pico or Nano.

Build a bootable microSD card with files provided by [MENTION=5672278]belfastraven[/MENTION]. I suggest her method 1 which assembles a boot loader rather than dealing with an image file. When your microSD card is ready, copy the Marshmallow, TWRP, and Open GApps zip files to it and you are ready to go.
[Nook HD, HD+ General] cabbieBot:
This thread is delightfully charming :) You old dudes rock. This was my first rooted Nook, as long as we are sharing our background . . .

The original "Nook" e-ink wifi+3G :D Something funny was discovered about it, and it seemed to defy all common sense security in the universe because it actually booted off an sd image if present. That was nuts. And then every Nook since then has followed suit, lucky for us.

I came CM13 a test run on my Ovation but gotta downgrade . . . fun playing around with it though, and I appreciate the hard work. I absolutely love that you made that PDF :D
[Nook HD, HD+ General] hereusethis:
I'm stumbling along

So I stumbled through a combination of your great pdf and these updated instructions. I grabbed the following from your links for my Ovation:

- ova-sd_card-rec (had trouble with a non-booting HD; had to go down to a 2gb/class2 card) for a bootable card

- cm_ovation-ota-MOB30J.160530.zip (marshmallow)

- twrp-3.0.1-0-ovation.zip (twrp)

- open_gapps-arm-6.0-nano-20160608.zip

and

- open_gapps-arm-6.0-pico-20160610.zip

I've Marshmallow all loaded up. When I tried to flash Gapps nano I got a message that there wasn't room in system for it (?). So I tried clearing davlik and rebooting. I got the same message. So then I downloaded pico and tried to flash that via twrp. It took a couple tries -- I think I had to mount the sd card maybe? It was late.

That seemed to work, but when I boot into Android, I was met with the message that the google apps wizard unexpectedly closed. It would then start up and close again. I thought maybe this was because I didn't have a wifi connection so I was able to "ignore" the message and access wifi setting at the top of the screen. I then was able to add a new user and a google account from there. That seemed to work fine -- I had play store access and was able to install gmail and send a message. Hooray. But when I tried to download chrome it failed with an "Error retrieving information from server" message.

I tried to reboot to see if that would straighten things out, only to find my desktop had the same message about the Google setup wizard not working.

So, I'm wondering if anyone has any suggestions or thoughts about what I did wrong.

Also, why wouldn't nano fit? I'm assuming nano version has chrome built in -- maybe that would have avoided the chrome issue (though the non-responding google account wizard may still have been a problem).

Thanks!

Anyway, thoughts or pointers to obvious mistakes on my part would be appreciated.

-
[Nook HD, HD+ General] PeteInSequim:
I and others have noticed this problem when flashing the combination of cm_ovation-ota-MOB30J.160519.zip with open_gapps-arm-6.0-nano-20160522.zip . The problem then was the unusually large size of the Marshmallow image (about 285 megabytes on the Ovation), which left less than needed space for nano gapps. This was solved by using pico gapps instead.

I notice that cm_ovation-ota-MOB30J.160530.zip is slightly larger even than the 160519 release, so suspect you had the same problem with nano gapps. I'd be surprised if this would occur with pico gapp.

Most post-installation apps occupy space in the data partition, but much of gapps are installed in the system partition. Perhaps some partition damage occurred with the multiple tries. I would wipe everything and start over using pico gapps.

Please let us know what you try, and the results.
[Nook HD, HD+ General] hereusethis:
Thanks, that did it. I rebooted a couple times, but didn't wipe. So yeah, I think you're right about corruption. A wipe, plus a fresh try at Pico got me up and running. This is a pretty sweet setup for the nook, assuming that you don't try to use it like a flagship 3gb RAM octo-core phone and have a zillion apps open at one time. :o

One mildly odd thing and one question:

Odd: When I use the power button to sleep the Nook it is finicky about working. Sometimes it sleeps, sometimes it doesn't. And when it does sleep, the power button won't always bring it out. Sometimes I have to plug in a power cable to get it to respond. Otherwise the button works fine, and worked fine in stock nook form -- it's only when I've used it to invoke sleep. Anyone seen this? I have one of those "smart"/magnetic cases that I used to use. I just tried that and it seems to work for sleep/wake so maybe that's my workaround.

Question: USB Host Switcher -- that's the OTG bit, yes? (I'm waiting for a female to female gender-changer adapter so I can't tell for sure). Once I have that, is there anything else I need to flash or install to get this working? My plan is to use this to move files between nook and flash drive. I'm guessing I can use ES Explorer to view the otg flash drive, but please yell of there's something else I need to plan for.

Thanks for all your help! :highfive:
[Nook HD, HD+ General] lmacmil:
What were you using before this install? The stock ROM? An earlier CM version? If so, which one? And what has Marshmallow done for your Nook that was lacking in the prior ROM? I have an HD running the latest CM11 nightly. I'm contemplating an upgrade but am unsure if I want to do Lollipop first or jump right to MM.
[Nook HD, HD+ General] ohidunno:
stable guide website?

I've been following this thread for many months; hoping to use your guide to rejuvenate a relative's NOOK HD+. I've read through the guide many times. I understand both the concept and have no doubt I'd be able to follow the 5 steps. The only reason I've held off these last 6 months is because of my relative's reticence.

Even though my relative is increasingly frustrated with their tablet's slump in to obsolescence, they are tremulously concerned that their only internet device will return to them as a useless brick. Which is why it's taken me many months to convince them that it'll all work out fine: I have both some foolproof instructions to follow and the support and guidance from others in the same boat. Or I did until the devs moved on and the 5 easy steps skittered off in too many directions to follow. At least too many for this simple pilgrim.

I know it's a lot to ask, and I would fully understand if you have neither the time nor inclination, but could you rework your excellent instructions as something a little more permanent and easier to find? Perhaps within a wordpress site or something similar. With links only to what is regarded as the most stable software.

Something like this would be of great benefit to those thousands like my relative who may not have the spare cash to replace their tablet. And it could be especially useful to those in the UK who have been left high and dry by B&N's decision to drop support for UK customers.

Thanks for your time and for all the effort you put in to the guide.

Thomas
[P3300, MDA Compact III ROM Development] paalkr:
Hi!

I've made some changes to the phone skin and the registry settings to make the SmartDialing more usable, at least in my opinion. I also posted this information in the B&B v3.7 release thread, but since that threat has become so large, it is hard to find just the information you are looking for. So I thought I start a new thread on this issue.

There has been many questions and opinions about the color of the smart dialer included in B&B v3.7. Most of the persons with questions did find the text hard to read, due to the low contrast between the text and the gray background. I tried to tweak the registry settings in HKLM\Software\HTC\SmartDialing to get it better, but the problem was really the dark gray background, so I thought I should try to do something about it. The result is is what you see in the attached screenshots. The registry settings and changed skins is attached.

Copy the BMP's in the zipfile to windows of your device (with a software that can overwrite files in ROM, e.g Resco Explorer or total commander) and import the registry changes (e.g with Resco).

Regards,

PK
[P3300, MDA Compact III ROM Development] thiti1999:
Hi, thanks I'm looking for that.

But I can't sent the registry to Rom. How can I do?
[P3300, MDA Compact III ROM Development] thiti1999:
Dear, sir

Can you cure the promblem for re-dial in Talk buttom or HW buttom. I'm V3.7 in P800w. But the problem. I can't repeat the Talk buttom or HW buttom for redial last number.

Please advise

thanks in advance
[P3300, MDA Compact III ROM Development] Samribi:
Here is a program to import reg keys: http://xdaforums.com/show...&postcount=801
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
Hi all! I'm here again with a new ROM! :cool:

BlissPop for Samsung GALAXY A5​

Currently supported variants

- SM-A500F

- SM-A500FU

Before installing the ROM, you must install TWRP.

→ Full Tutorial for installing TWRP on your Galaxy A5

→ http://xdaforums.com/galaxy-alpha/help/to-port-twrp-to-galaxy-a5-a500fu-t3150843

DISCLAIMER

#include
/*
* Your warranty is now void.
* The ROM is under developement and have some bugs.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/

This ROM has some bugs and issues.

So for now I don't recommend you to use this ROM as a daily driver.

• Feel free to report any issue you have on this ROM.

Please don't ask ETAs for other variants.

I'll try to adapt the ROM to other variants when the build I'll be stable. Thanks.

BlissPop Beta Builds​

NOTE: THIS ROM IS MADE FOR GALAXY A5, OBVIOUSLY THIS WILL NOT WORK ON ANY OTHER DEVICE.

• Download link to the latest A500F build (Developement and Updates provided by [MENTION=2533313]faust93[/MENTION]) [BlissPop 4.0.2]

http://xep.8800.org/A5F/BlissPop-v4.0.2-a5lte-UNOFFICIAL-20150927-1524.zip

• Download link to the latest A500FU build (Developement and Updates provided by [MENTION=6446790]mygalaxya[/MENTION]) [BlissPop 4.0.3]

https://www.androidfilehost.com/?fid=24052804347853481

Other useful links:

• SuperSU and Google Apps (flash using TWRP/CWM):

→

https://www.androidfilehost.com/?w=files&flid=40235

• Steps for a Clean Install:

1) Put the .zip file in Internal or External Storage.

2) Reboot in Recovery Mode (Using TWRP/CWM Recovery)

3) Wipe Data, Cache, Dalvik Cache and format /System

4) Install the ROM.

5) Flash the Google Apps and SuperSU.

6) Reboot and Enjoy!

You can watch a video of this ROM here:

https://youtu.be/6ZPxlYqfFYw

Screenshots:

Contributors:

mygalaxya, faust93

Credits

Team Bliss for the ROM.

Version Information:

ROM Status: Beta

ROM OS Version: 5.1.1 Lollipop

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Lollipop Bootloader and Modem.

Based On: BlissPop 4.0.2/4.0.3

Created: 2015-09-25

Last Updated: 2016-02-09
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
Changelog:​

~A500FU~

• *25-09-2015*

* Initial release.

• *26-09-2015*

* Fixed BlankUnblankCheck App FC.

* Attempt to fix sound and RIL issues.

* AudioFX fixed.

• *01-10-2015*

* Updated to BlissPop 4.0.2

* Fixed Wi-Fi and SMS issue.

* Fixed battery Drain issue

* Added performance Mods on Settings.

* Minor improvements

• *10-12-2015*

* Added security patches (for Stagefright 2.0).

* Added security patches status on Settings > About Device

* Removed unecessary libs.

* Patch for "Ghost Touchscreen" issue.

* Improved battery life.

* META-INF scripts updated.

* Proximity sensor when calling fixed.

• *11-02-2015*

* BlissPop 4.0.3

* Wi-Fi issue fixed.

* RIL and sound fixed.

* Updated kernel.

* Minor improvements.

* Wakelocks to improve battery life

~A500F~

• *25-09-2015*

* Initial release.

• *29-09-2015*

* Updated to BlissPop 4.0.2

* Battery Drain issue fixed.

* Kernel modifications.

* Minor other improvements.
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
FAQ Section:

Currently, the ROM has many bugs related to RIL, so some errors like that may occurs. Don't worry, we working on it to fix that.

This option will be enabled when Stable builds will be released.

Make sure you have Wipe all system/data, and if you downloaded the ROM entirely for the variant you use. You can also try to reinstall TWRP.

However if you still can't install the ROM, you may post on the thread to ask some help.

It's not recommended at all to install A500F or A500FU Builds on another variant, (Soft Brick risk)

For now it's not currently possible, know that TouchWiz Apps are using some needed libs to work, this libs are not included on this CM Builds.
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
Posting Rules

• If you don't read the posts made by me and/or if you post rudely, or ask for ETAs/feature request, or if you ask anything which is not related to the CM Build you WILL be called out for it and you'll be reported to a moderator.

• You have been warned. The most important information you need to know are in the first post, and any other informations you looking for can be found by reading my "OP" Posts, or by performing a search using the XDA Search Engine.

So please think before you post. Thank you. :)
[Galaxy A3, A5, A7, A8, A9 Android Development] sopnohinsobuj:
Please upload screenshot & video
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
New A500FU Build with bugs fixes, download link in #1 post. Updated changelog.
[Galaxy A3, A5, A7, A8, A9 Android Development] ahmad89098:
Yess! :D

Another ROM for the Galaxy A5! Thanks [MENTION=6446790]mygalaxya[/MENTION] and [MENTION=330915]Faust[/MENTION]39
[Galaxy A3, A5, A7, A8, A9 Android Development] Nunu1006:
Can I overclock in this ron?

Gesendet von meinem SM-A500FU mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
Yes you can, :)
[Galaxy A3, A5, A7, A8, A9 Android Development] astrit1:
[MENTION=6446790]mygalaxya[/MENTION] Over clocking means getting a higher cpu GHz than normal 1.2ghz and you can't still not do this until a developer unlocks them with a custom kernel am I right ? :)

Gesendet von meinem SM-A500FU mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
I know... But on this ROM you can set minimal and maximal CPU clocks, :)

PS: And no you can't get higher CPU than 1.2GHz, it's an hardware thing
[Galaxy A3, A5, A7, A8, A9 Android Development] Nunu1006:
And what can I make that the performance is better? And gives it another way to set the cpu freq. Over 1.2 GHZ

Gesendet von meinem SM-A500FU mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Android Development] mygalaxya:
Idk, but no you can't set CPU frequency over 1.2GHz because it's an hardware thing.
[Galaxy A3, A5, A7, A8, A9 Android Development] rudysafey:
YAY! Another custom Rom for A5

Downloading A5F now :D i will be reporting bugs and testing on A5F [MENTION=6446790]mygalaxya[/MENTION] :fingers-crossed:
[Galaxy A3, A5, A7, A8, A9 Android Development] fahadasad:
Bugs On A5F Rom BlissPoP :-

can't receive messages

bad in call sound

google play images messed up

AudioFX not Working
[Galaxy A3, A5, A7, A8, A9 Android Development] astrit1:
of course you can do this but first you need a custom kernel which allows this and the dev need to add the other ghz, like on all other device for example s4 mini normal 1.7ghz you can overcloked it to 2.8ghz with f4f kernel