yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] d9ct:
Thank you for the reply and checking out your testing. What is btsnyc?

I've done some pretty thorough testing around my apartment with different devices and I don't think it's a home network issue. I am 99% sure I've narrowed it to the Nook HD+ not picking up a good signal, many times even when in close proximity to my router.

After some more thought, I'm thinking it is possible I started having this issue prior to CM12 when I had installed SlimKAT for a few weeks. However I had several issues with that build so I could have forgotten about this part, and those multiple issues were why I was eager to try out CM12. If it is true that I was having these issues with both builds, CM12 and SlimKAT, can anyone think of any issues non-ROM specific that may be making my device have such poor WiFi reception?

Maybe I'll have to make a backup and re-install SlimKAT as well as a 10.2 install and do some testing on those separately. 10.2.1 is what I ran for quite a long time prior to the last 1-2 months of trying out these new ROMs, and overall it ran great for me.
[Nook HD, HD+ Android Development] Golf_4711:
Thanks

Hello Hashcode,

thanks for CM12 for my old Nook HD+ ;)

It's cold in Germany and the best time to test your image.

Thanks a lot for your work.

Regards

Golf :cool:

Testfiles:

- cm-12-20150111-UNOFFICIAL-ovation.zip

- gapps-lp-20141109-signed.zip

- OVATION-TWRP-20140822-recovery-AllF2FS.zip
[Nook HD, HD+ Android Development] amaces:
I was itching for a new build too, so I tried the Jan 29th one posted here. Thanks, [MENTION=3651088]Zippy Dufus[/MENTION]! It runs pretty well, at least as well as the Jan 11th build, while having all the goodies merged in between. One major difference is that it looks like the AOSP wpa_supplicant is being used rather than the TI one in [MENTION=4243514]Hashcode[/MENTION]'s build. Everything works as before, didn't have to remove /data/misc/wifi, but instead of the hardware MAC address, I see a faked one, like in the initial CM11 builds.
[Nook HD, HD+ Android Development] sjavvaji:
Thanks. I'm not sure how I missed that post. It seems to have fixed the recent apps bug and made app switching faster. Audio issues still persist though. I'll try clean flashing later. Thanks for the heads up and thanks Zippy Dufus!
[Nook HD, HD+ Android Development] extrem0:
Yeah. Zippy Dufus recent build is good. Didn't try the original one by hashcode, but I found multitasking worse than on cm11. It might need some tweaking. Battery usage appears to be very similar to what I was getting on CM11.

Also, reboot to recovery is working. Someone reported it wasn't.
[Nook HD, HD+ Android Development] SCWells72:
I'm on the original build and reboot to recovery isn't working for me. Is there some easy way to get into recovery without making a bootable SD card? I'd like to flash this newer build but don't have an SD card handy.

EDIT: Never mind. Found an earlier post about this.
[Nook HD, HD+ Android Development] king200:
Change MAC address?

I have 2 HD+. When I install the rom both get the same MAC address. What file do I have to change to make them different.

Difficult to WiFi connect with 2 devices with same address.
[Nook HD, HD+ Android Development] Technosquid:
This is just a drive-by half-answer to the MAC address question... I have no idea if this is the type of fix that works in the current CM12 ROMs but I had the same problem on CM11, and the fix I used was the one described here

[Q] Two Nook HD 7s exhibiting same ID on network

It basically says navigate to /system/etc/firmware/ti-connectivity and delete file wl1271-nvs.bin, reboot, and the system will have generated a new one with a new MAC address. If the same file even exists in the current builds, you may want to make a copy backup of it before deleting it.
[Nook HD, HD+ Android Development] :
Or just re-flash the same or newer rom build.
[Nook HD, HD+ Android Development] leapinlar:
Early in the verygreen CM10 days the same issue arose. He had hard wired in a fake macaddress as an expediency. That meant all builds had the same address and could not be on the same router at the same time. He eventually repaired the code to have it look on the device for the address. Hashcode needs to do the same. Someone needs to put that on his bug list.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Finally I'm on the game

Thanks [MENTION=4243514]Hashcode[/MENTION] [MENTION=3654172]verygreen[/MENTION] for the continuous effort to bring my dead device into life.

Now I'm booting CM12 on hummingbird. I found out the reason why it was causing boot loop on hummingbird. To avoid it

you have to format/bootdata and format/userdata (wipe everything on internal storage. I am glad to show this pics of nook hd with lollipop build.

Currently it is my daily driver and no issues except black thumbnails in overview and poor battery life.

[IMG="HomeScreen Nova Launcher"]https://lh5.googleusercontent.com/-KvBOGHekvFc/VNBtIvykc7I/AAAAAAAAAPM/z8Ks4_Io9q8/w1535-h865-no/DSC03914.JPG[/IMG]

[IMG="Lollipop Easter Egg"]https://lh3.googleusercontent.com/-Tm8VqR4Yxqw/VNBtWvuOtSI/AAAAAAAAAPg/TeLYHdfYxGw/w1535-h865-no/DSC03918.JPG[/IMG]

[IMG="Lock Screen"]https://lh6.googleusercontent.com/-8-Q4AUHexzY/VNBtXV3mzkI/AAAAAAAAAPo/C9AfbeCmUlg/w1535-h865-no/DSC03919.JPG[/IMG]

[IMG="Notifaction Pull Down"]https://lh4.googleusercontent.com/-plCrGJ9lgQM/VNBtIxOMPiI/AAAAAAAAAPQ/DTnEcp9-Vss/w1535-h865-no/DSC03916.JPG[/IMG]

[IMG="Settings"]https://lh4.googleusercontent.com/-HmhXwyaVSMk/VNBtTWW4iPI/AAAAAAAAAPY/Q5QsfIwx36c/w1535-h865-no/DSC03917.JPG[/IMG]

[IMG="About Tablet"]https://lh4.googleusercontent.com/-flX4VxgPwp8/VNBtdd2klFI/AAAAAAAAAPw/wPZkIoIDDZ8/w487-h864-no/DSC03920.JPG[/IMG]

[IMG="CM File Manager"]https://lh6.googleusercontent.com/--srFdSj0Srs/VNBteogV0NI/AAAAAAAAAP4/IRfd3DTtvz8/w1535-h865-no/DSC03924.JPG[/IMG]
[Nook HD, HD+ Android Development] :
I round about copy pasted it into the bug reporter just cause you used my reply of copy pasting alternative to copy pasting which I hadn't copy pasted :)
[Nook HD, HD+ Android Development] king200:
I tried that and it didn't work. I went into my router and observed the Nook HD+ connect and then, when the 2nd HD+ connected, you could not see it. I set each Nook+ to fixed IP and they both worked at half speed.

Somewhere, the boot picks or assigns the IP address but I have to find where.
[Nook HD, HD+ Android Development] ST Dog:
Looks like init.omap4.rc runs something that's supposed to fix the MAC address.

https://github.com/CyanogenMod/android_device_bn_common/commit/e4465f777ba36b36b4da21281cc6fdbde25ec2ef

# Fix wlan MAC addr
start fixmac

Maybe a typo? I was looking for fixmac as called above and all I find is fix-mac.sh

https://github.com/CyanogenMod/android_device_bn_common/blob/cm-10.2/prebuilt/bin/fix-mac.sh
[Nook HD, HD+ Android Development] KevHD+:
Is this mac address problem for Zippy's build or Hashcode's?
[Nook HD, HD+ Android Development] prsa01:
downloading zippy's build

OK, found directions on youtube. Guess it was my popup blocker as much as anything. Are there any of the download links that don't try to add junkware to the download?

Thanks

Noob issue,

Can someone please tell me which link and/or the process needed to download zippy's build. Every "DOWNLOAD" link I try on that page seems to take me to ads, junk, or virus warning sites.

Thanks much!!
[Nook HD, HD+ Android Development] amaces:
Hashcode's Jan 11th build in the OP is fine, and shows the proper BN MAC address. The Jan 29th build made by Zippy reverts it to that generic MAC (00-D2-8B-*), but it's perfectly fine otherwise. It's my daily driver since the MAC issue doesn't seem to impact connectivity in any way, unless you have more than one of these Nooks ;).
[Nook HD, HD+ Android Development] Zippy Dufus:
Sorry everybody!

The site that I used appears to be a particularly obnoxious free file sharing site. Now, even I cannot figure out to download it. POS!!

Below are the checksums if one of you could be good enough to post it somewhere better.

$ sha1sum cm-12-20150129-UNOFFICIAL-ovation.zip

3e21109f81e6855f615b95c619f9b3c7e9229365 cm-12-20150129-UNOFFICIAL-ovation.zip

$ md5sum cm-12-20150129-UNOFFICIAL-ovation.zip

374ff668717a21e177e3480fcc90e5fe cm-12-20150129-UNOFFICIAL-ovation.zip
[Nook HD, HD+ Android Development] prsa01:
Hey,

I didn't mean to have it come off as complaining.

I VERY much appreciate you building and posting it!

But would also appreciate it if someone could post it somewhere that takes less hoops to get it.

Thanks again in advance!!
[Nook HD, HD+ Android Development] ST Dog:
Then perhaps one of Hashcode's patches is missing form Zippy's build.

Since you have Zippy's build can you look for the fix-map script and maybe try manually executing it to put the correct MAC in the nvs file.
[Nook HD, HD+ Android Development] sleepingturtle:
Zippy, why don't you use Mega? It's free and pretty much hassle free. They don't spam with popups.
[Nook HD, HD+ Android Development] amaces:
Simply running /system/bin/fix-mac.sh didn't help. Here's the content of that file on my device (Zippy's build):

#!/system/bin/sh

PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
ORIG_NVS_BIN=/system/etc/firmware/ti-connectivity/wl1271-nvs_127x.bin
NVS_BIN=/system/etc/firmware/ti-connectivity/wl1271-nvs.bin

if [ ! -f "$NVS_BIN" ]; then
mount -o remount,rw /system
cp ${ORIG_NVS_BIN} ${NVS_BIN}
MAC=`cat /rom/devconf/MACAddress | sed 's/\(..\)\(..\)\(..\)\(..\)\(..\)/\1:\2:\3:\4:\5:/'`
chmod 644 ${NVS_BIN}
mount -o remount,ro /system
fi

#fix race condition where wl1271-nvs.bin wasn't ready after a complete wipe
insmod /system/lib/modules/compat.ko
insmod /system/lib/modules/cfg80211.ko
insmod /system/lib/modules/mac80211.ko
insmod /system/lib/modules/wl12xx.ko
insmod /system/lib/modules/wl12xx_sdio.ko

So, no calibrator set nvs_mac $NVS_BIN $MAC, and adding it in didn't help surprisingly. The MD5 of all /system/etc/firmware/ti-connectivity/wl1271-nvs* files remained identical (7fa6e4173b066fd12f9f6c4bef6cfe66). I ended up running calibrator set nvs_mac /system/etc/firmware/ti-connectivity/wl1271-nvs.bin `cat /rom/devconf/MACAddress | sed 's/\(..\)\(..\)\(..\)\(..\)\(..\)/\1:\2:\3:\4:\5:/'` manually, and commented out the cp ${ORIG_NVS_BIN} ${NVS_BIN} line to prevent overwriting my changes. The proper MAC address persists across reboots now.
[Nook HD, HD+ Android Development] ST Dog:
Note the if...fi wrapping that section?

So if the $NVS_BIN file exists it doesn't execute that block.

So, you have to delete the NVS_BIN file first, then run fix-mac.sh so that the block would execute.

Does init.omap4.rc call fix-map correctly so that the file can be rebuilt at boot if it's missing?

Does it by chance try calling fixmac instead?

(I'm not in a position to download any builds right now due to limited internet data availabe)
[Nook HD, HD+ Android Development] amaces:
D'oh, you're totally right, that's why there was no difference unless I ran calibrator set nvs_mac manually. Looks like fixmac references /system/bin/fix-mac.sh properly:

root@ovation:/ # grep -C 3 fix.*mac init.omap4.rc

on post-fs
# Fix wlan MAC addr
start fixmac

setprop ro.radio.noril yes

--
start bootcnt
start install_keybox

service fixmac /system/bin/fix-mac.sh
class core
user root
group root

So, the only thing missing is the calibrator set nvs_mac $NVS_BIN $MAC line, which was removed in CM12. Maybe there was a good reason, and maybe [MENTION=4243514]Hashcode[/MENTION]'s /system/etc/firmware/ti-connectivity/wl1271-nvs_127x.bin was already set to auto detect the HW MAC address somehow. Someone would have to compare the binary blob changes between Jan 11th and Jan 29th.
[Nook HD, HD+ Android Development] skyhawk21:
Been running Hashcodes CM12 unofficial now for a week or so. Anyhow my battery from full charge to 1% only browsing internet whole time and some minimal other apps lasted 7 hours and 35 minutes screen on time with screen brightness around 30-40% on the Nook HD+

This was with WIFI on when screen was on. So the battery actually lasted a little bit longer compared to when the Nook HD+ was brand new with stock ICS 4.04 out of the box over a year ago.

ALPHA Lollipop build does pretty good with battery life, screen time and wifi use. Remember the Nook HD+ has a 6000mah battery. Since having it for over a year the battery of course has degraded over time being discharged and recharged! Yet battery is working like when it did NEW. Also battery has to power a 9" HD screen with 1920x1200 resolution which is a PLS panel. Pretty dam good I think!:good:
[Nook HD, HD+ Android Development] :
So, hashcode's build has different MAC addresses on two nooks and is working correctly?. Since its showing the proper MAC address I'm assuming it is, but just to be sure before I go commenting on the bug report I added or else someone else can. Thanks.
[Nook HD, HD+ Android Development] aoleary:
I had the same problem. I had to flash SuperSU to resolve the issue.

When I installed htis ROM, CWM notified me that I would lose rights if I did not fix it.

I selected Yes - fix it, but root rights were still lost.

When I flashed SuperSU again after, it asked the same thing, however this time I said no, and I had root again.
[Nook HD, HD+ Android Development] Dread This Day:
[MENTION=5875485]keshabbhattarai126[/MENTION] This did nothing for me. Could you please be more specific as to your order? I wipe everything except external SD, and then flash the ROM, then flash GAPPS. Whether I select yes or no for fix root makes no difference, it boots right back into recovery. If I go to reboot now, it gets to cyanoboot, then cuts out. Absolutely angering.
[Nook HD, HD+ Android Development] aoleary:
Do a Data & Cache & Dalvik Cache wipe (the standard wipe one does), install CM12 and GAPPS (LP version linked in original post), reboot Nook and let it go to desktop.

Restart the Nook again and go into Recovery and flash the SuperSU zip file (SuperSU-v3.13) in recovery (no need to wipe anything) and reboot back into CM12 and root should be fixed...
[Nook HD, HD+ Android Development] Dread This Day:
Oooh, yeah, problem is I can't get CM12 to boot, at all. It's been a perplexing nightmare. It just loops.

---------- Post added at 02:18 AM ---------- Previous post was at 02:02 AM ----------

I wipe everything, I mean EVERYTHING except external SD, flash ROM, flash gapps, no profit. Every. Time. I'm beginning to think I'm insane.
[Nook HD, HD+ Android Development] aoleary:
OK. Sorry. I didnt realise that it would not even boot for you :(

No that file wont help it boot..

What recovery are you using to flash CM12? Did you use the CWM SDCARD image (emmc-cwm-early3.1.img) from here: http://xdaforums.com/showthread.php?t=2600572
[Nook HD, HD+ Android Development] Dread This Day:
I'm using EMMC CWM 6.0.4.8
[Nook HD, HD+ Android Development] aoleary:
I have a feeling that that is the 3.0 version of the CWM image (emmc-cwm-early3.0.img).

I would recommend that you rewrite the SDCARD image again as outlined in the thread that I posted and redo the whole process from start again, as the version of your recovery can play a big part in issues during flashing.

I dont have my Nook to hand, but from memory I think I am using CWM 6.0.5.x.
[Nook HD, HD+ Android Development] keshabbhattarai126:
I did factory reset, wipe cache partiton, wipe dalvik cache, format system, format data, format cache, fomat userdata, format bootdata, install zip(cm12, gapps). It said fix root I checked on yes. That's it.

First boot took me straight to recovery. Again I did power off and power on. After cyanoboot it went blank but still backlight was on and few seconds (5 sec) cyangenmod logo apperared. It took almost 15 min to reach homescreen.

--------------------------------------------------------------------------------------------------------ONE LAST THING... Don't go crazy if no success. I didn't succeed in my first nook. Infact it is 2nd nook. So it is wise to say 50% of device still fail to boot cm12. I don't have first nook now. As soon I get it I will try to boot cm12 and give you a feedback. [MENTION=3638259]Dread This Day[/MENTION]
[Nook HD, HD+ Android Development] Dread This Day:
As far as I know, I have the latest recovery for Hummingbird. I also tried making a new SD recovery image, still did not work. I wish Hummingbird was as popular as Ovation, lol. This isn't really getting much attention as far as I can tell.
[Nook HD, HD+ Android Development] redneckmatt:
This is working pretty well on Ovation!

I wasn't able to get it fully operational with the latest TWRP (20141229) due to a format bug, so I backed down to 2.7.something (20140729).

Did a complete wipe (everything but SD card), and it installed great. Had been bouncing from CM11, back to CM10, then to this build from Jan 10th.

Still seem to get the occasional (holdover from CM11) screen bug where it won't unlock, but besides that it's pretty slick.
[Nook HD, HD+ Android Development] aoleary:
Its a pity it doesnt work. Its marked in the original post as valid for Hummingbird also.

Maybe try upgrading your recovery to TWRP? Its not guaranteed it will succeed, but worth a try.
[Nook HD, HD+ Android Development] Dread This Day:
I've never found a build of TWRP for Hummingbird. Ovation gets all of the love. If I had a decent box I'd try to build it myself.
[Nook HD, HD+ Android Development] keshabbhattarai126:
I found TWRP 2.6 for hummingbird

I have downloaded from one of the developer but forgot his name or link. But I do have link to my google drive.

https://drive.google.com/file/d/0B3vAey-4ufbNSTNyNVRnRWpaUW8/view?usp=sharing

It's too risky to use this. If you know how to go back to previous rom in any outrageous condition then you may give a try

again link is https://drive.google.com/file/d/0B3vAey-4ufbNSTNyNVRnRWpaUW8/view?usp=sharing
[Nook HD, HD+ Android Development] Dread This Day:
TWRP is safe to flash. Seems fully operational. I wiped, flashed ROM and GAPPS, and it seems to be looping same as whenni flashed with CWM. Yeah, definitely looping. Ugh. Startingbto hate this tablet. Do not understand what would cause this. TWRP cannot restore backup from external SD, this version anyway. Bummer.
[Nook HD, HD+ Android Development] leapinlar:
Its been so long ago that you posted your original concern. Are you saying the issue is it will only boot to recovery no matter what you do? That usually means you have a corruption in one of your hidden partitions. I recommend the first thing you do is go to my HD/HD+ CWM thread linked in my signature and flash the plain stock zip from item 6 there. Please note you cannot use the newer CWM or TWRP you have been using for CM12. You can get an older version from the same thread. That may fix your issue. If it does not I may be able to make you a repair zip.
[Nook HD, HD+ Android Development] Dread This Day:
Early on in these issues, I had went all the way back to stock and back again. But, I'm going to try again, see what happens. Downloading the files now. So, which recovery would be used for flashing cm12? Oh and yes, only boots to recovery. Cyanoboot logo will appear, then the screen just cuts off.
[Nook HD, HD+ Android Development] leapinlar:
Only boots to recovery or that screen cutting off? You mean it only boots to recovery on an SD and to the cut off screen with no SD?

And if CM12 is like CM11, it needs v6045 or newer.
[Nook HD, HD+ Android Development] Dread This Day:
If I leave it, trying to boot, it will go to cyanoboot, them cut off, then the cyanoboot logo will come up again maybe twice and cut off both times, then recovery will boot. But some times it just boots straight into recovery, and no, not SD recovery, EMMC.
[Nook HD, HD+ Android Development] leapinlar:
The HD/HD+ has a system where it counts the number of failed boots. When it gets to 8, it boots automatically to recovery in an attempt to repair itself. Once in recovery the counter is reset to zero. I think that is what is happening to you. So the issue is not that it goes to recovery, it is the boot failing. And the only way to fix that is to get a ROM on it that will boot properly. I still suggest the plain stock zip.
[Nook HD, HD+ Android Development] Dread This Day:
I'm having issues even flashing back to stock. I get an bad installation error every time I try. I've tried two different. Zips.

---------- Post added at 04:57 PM ---------- Previous post was at 04:50 PM ----------

And my cm11 still boots fine. Also, those errors while flashing stock come from both EMMC and SD recoveries.

Edit: I see why, need older CWM. OKAY, on to that.
[Nook HD, HD+ Android Development] leapinlar:
You really have me confused. I thought it would not boot at all on emmc. Or did you mean the CM11 still flashed from the new CWM fine?
[Nook HD, HD+ Android Development] Dread This Day:
Sorry, I'm confusing myself as well. At that point I had restored a CM11 back up, which booted fine. I was then trying to install stock Barnes and Noble, which was failing because my recovery was too new. So, I've made an SD card that boots "CWM based Recovery v6.0.2.7 - Stock", no more script errors, but now when I try to flash the stock 2.20.zip, it hangs on " opening update package... ", then it reboots after a minute. Lol, I can't even get back to stock, dear lord. This is killing me.

So if CM11 was booting, could that partition still be corrupt? Say, like, if I restored my back up and it was fine, then could it still be corrupted?
[Nook HD, HD+ Android Development] leapinlar:
If your restored CM11 backup booted then what is wrong with your device? Is it just that you can't seem to install CM12? That is a totally different issue.

If CM11 booted, your device is fine.
[Nook HD, HD+ Android Development] Dread This Day:
Installing CM12 is the issue. That's when it loops, when trying to boot.

---------- Post added at 07:30 PM ---------- Previous post was at 06:52 PM ----------

I guess I thought and was hoping you meant that there was a corruption that was easily fixed and I'd be able to flash CM12 and be on my merry way. Sorry form the confusion. Back to square one.
[Nook HD, HD+ Android Development] evaporic:
I had the exact same issue on Ovation installing CM12. It is definitely a recovery issue and like he said at the beginning you need to flash the correct recovery. Maybe he can point you at the correct hummingbird recovery
[Nook HD, HD+ Android Development] Dread This Day:
I think it is recovery related, too. Or the installer script. But, as far as I know I'm using the same recovery as other people on Hummingbird who have successfully booted CM12. I guess I'll just have to wait and see if anyone figures it out. I'm on the edge of my seat with it.
[Nook HD, HD+ Android Development] robak1965:
I'm in the same boat as you, same result. I've access to 4 hummingbirds and all exhibit the exact same issue. I've not seen any actual hummingbird successfully boot cm12 from emmc with the available cwm recoveries for it. The root cause is elusive.
[Nook HD, HD+ Android Development] Dread This Day:
Thanks for sharing, I don't feel as bad now. Lol. It's infuriating the time and effort I've put in to trying to get this to successfully flash/boot. I guess all we can do is wait. Kresh had some luck getting a Hummingbird to boot. But it seems most people can't boot it.
[Nook HD, HD+ Android Development] king200:
I'd try installing the rom but don't boot. Then Backup->wipe(format system)->restore backup->boot system.
[Nook HD, HD+ Android Development] Dread This Day:
Trying now, thank you for the idea!

---------- Post added at 03:26 AM ---------- Previous post was at 03:11 AM ----------

Looks like a no-go. Full wipe, flash ROM and GAPPS, make back up, format /system, restore back up, same results as any other time I've tried. While making the backup though, I could see all the right things being backed up, so the ROM flashes at least most of the way.
[Nook HD, HD+ Android Development] :
Your doing too much to try to get it to work. It should work without doing that ergo its broken somewhere.
[Nook HD, HD+ Android Development] Dread This Day:
I know I am, and I know it is. But, it bugs me. How is it broken when it boots on some Hummingbirds? What is different about my device? My procedure?