yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] leapinlar:
Some devices have slightly different hardware (like different brand of ram chip, etc). Maybe the ones that work are different from yours.
[Nook HD, HD+ Android Development] Dread This Day:
I understand, I guess my biggest question then is, how would I go about figuring out what is different so that those of having issues with these builds can get in on the Lollipop love?
[Nook HD, HD+ Android Development] leapinlar:
The only way to find out what is not working is to look at the boot log created during the failed boot. Then when you see what is failing, get a developer to fix the code so that it works. Not an easy process.
[Nook HD, HD+ Android Development] Dread This Day:
Am I correct in assuming ADB is the only way to pull the boot log?
[Nook HD, HD+ Android Development] leapinlar:
That or the terminal in TWRP. The terminal is easiest.
[Nook HD, HD+ Android Development] Dread This Day:
Okay, would you happen to know the commands?
[Nook HD, HD+ Android Development] leapinlar:
No, but if you search for klog or something like that, you might find directions.
[Nook HD, HD+ Android Development] :
Tested twrp for you and for me on nook hd+ did not work very well for this and is more frustrating then setting up adb...

Can be used with twrp command terminal:

cat /proc/kmsg

This allows you to view the log that happens during the kernel part of the boot which I believe is during the green loader (cyanoboot logo).

cat /proc/kmsg > /emmc/kmsg.txt (or /sdcard/kmsg.txt) (paths could be different)

This saves the kernel log or so it would if it worked on the twrp I tested it on.

Alas, it might also not work for you.

If you make it past the green loader to the cyanogenmod boot animation then logcat should have started which can be seen in real-time via adb. Example from linux terminal: just type in and hit enter right after nook reboots then wait for it.

$ adb catlog

There are multiple ways of doing this. Setting up the nook for adb is the pain part, but if you need notes on it for linux that I have and for Windows I do not.

BTW, the logs will probably show errors and warnings that actually do not keep the device from booting so posting them (please check for personally identifying information) would be the best way of getting a fix.
[Nook HD, HD+ Android Development] Dread This Day:
Thank you! I will try kmsg logs. ADB does seem like a pain to set up, but of I need to to figure this out, I'll probably do it. I could do either a Linux or Windows ADB. The boot process never makes it to the CyanogenMod boot animation, only the Cyanoboot logo. Which then cuts out. So, on hoping the kmsg will show something obviously wrong. I know I'll only be able to dig so far with my limited knowledge. But, I'm hoping to get is Hummingbirds caught up to Ovation. So, I'll try.
[Nook HD, HD+ Android Development] :
Well here's a cheat sheet for linux then. Its not complete step-by-step as you'll need to download the android sdk for example.

====================ADB
if not already installed: $ sudo apt-get install android-tools-adb

Add tools->Add-on site->user defined->new in android SDK for nook hd then download and install driver:
NOOK HD and NOOK HD+: http://su.barnesandnoble.com/nook/sdk/nook_hd_addon.xml
NOOK Color: http://su.barnesandnoble.com/nook/sdk/addon.xml
NOOK Tablet: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml

copy nook adb zip rule files to /etc/udev/rules.d/ (nook requires 18d1)
(Appears to be working without this on Ubuntu 14.10)

Files are 50-android.rules, 51-android.rules, 90-android.rules and all are the following and the same:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"

$ sudo reload udev

$ gedit ~/.android/adb_usb.ini and add new line with: 0x2080 (<- just copy past 0x2080 into it)

adb kill-server
adb start-server

"$ adb devices" should show the nook and if so adb is now working for the device.

NOTE: DO NOT USE(!) "$ android update adb" as this removes the 0x2080 line which is necessary!

Additional help: https://nookdeveloper.zendesk.com/entries/21943338-nook-developer-start-up-guide#_EnableADB

From there $ adb /proc/kmsg (etc), adb logcat, adb shell are all very useful. There's more, just do a search.
[Nook HD, HD+ Android Development] leapinlar:
Something just came to mind about the hummingbird. There are two different brands for the screen. Early in bokbokan's development of the cyanoboot menu for the hummingbird, it would work on one brand (the one he owned) but others who had the other brand it would fail. He finally fixed it but that might be the issue for you. When you get your kmsg working, look at screen initialization for issues.
[Nook HD, HD+ Android Development] Dread This Day:
Well, maybe. Here we have it ladies and gentlemen, the ksmg boot log of CM12 Hummingbird. Feast your eyes. A lot of errors towards the bottom. I hope like hell this helps, it was a nightmare to grab.

http://pastebin.com/R4KpLe3G
[Nook HD, HD+ Android Development] digixmax:
FWIW the BootCnt counter can be reset manually, or by flashing a flashable zip to replace the BootCnt file in /bootdata.
[Nook HD, HD+ Android Development] keshabbhattarai126:
I currently have two hummingbird device. Black (smoke gray) boots cm12 and White (Snow) fails to boot in my case.
[Nook HD, HD+ Android Development] Dread This Day:
I think we're on the right track. Just need [MENTION=4243514]Hashcode[/MENTION] or [MENTION=3654172]verygreen[/MENTION] to take a look.
[Nook HD, HD+ Android Development] ST Dog:
Boot logs from both would certainly help. Compare what failed with what succeeded to help narrow the cause.
[Nook HD, HD+ Android Development] Dread This Day:
Hopefully my failed boot log is sufficient so that he doesn't have to go through what I did to get it.

---------- Post added at 11:36 AM ---------- Previous post was at 11:17 AM ----------

Mine that won't boot CM12 is the white version as well.
[Nook HD, HD+ Android Development] ST Dog:
Could be, but [MENTION=4243514]Hashcode[/MENTION] has been swamped at his day job (according to recent posts) so it may be a while before he can dig into it.

With both logs maybe someone else can more easily find where to look in the code.

I looked through your log, but I don't know what errors are "normal"
[Nook HD, HD+ Android Development] Dread This Day:
I don't know who else would/could look at it, so I guess it'll have to wait. Yeah, some of those errors are strange, and like you, I'm not sure which are to be expected and which aren't. Even if I did, I wouldn't know how to fix it.
[Nook HD, HD+ Android Development] ST Dog:
I'd have a go at it, but I'm out of the country and the cost to download everything to even attempt a build is quite high.

I can browse the source, but can't check any changes.

I don't want to install anything other than stock to EMMC as well (just a personal preference), and was going to attempt a SD Card setup, but that would cause additional points of failure.

Really need a good, working base to start with.
[Nook HD, HD+ Android Development] :
No expert, but this stuff doesn't look good:

<3>[ 4.065338] fs_mgr: Cannot open file /fstab.omap4hummingbirdboad <- Why is it failing to open fstab?

<6>[ 4.956542] SELinux: Context u:object_r:adb_keys_file:s0 is not valid (left unmapped) <- These lines are labeling problems, but don't know if they will bork the boot.

<3>[ 4.096374] HDCP: failed to load keys <- Probably best if it did not fail.

<3>[ 4.062438] init: cannot find '/sbin/setup_adbd', disabling 'setup_adbd' <- Missing file or otherwise. unsure if this can be ignored or not
[Nook HD, HD+ Android Development] Dread This Day:
Those, and these, seem bad:

[Nominal=1190000Calib=1152100 margin=0
<6>[ 2.050994] cannotapply mgr(lcd) on inactive device
<4>[ 2.051269] omapfb omapfb: failed to apply dispc config
<6>[ 2.051391] cannot apply mgr(tv) on inactive device
<4>[ 2.051635] omapfb omapfb: failed to apply dispc config
<6>[ 2.051788] cannot apply mgr(lcd2) on inactive device
<4>[ 2.052032] omapfb omapfb: failed to apply dispc config

And

<3>[ 3.901092] init: could not import file '/init.recovery.omap4hummingbirdboard.rc' from '/nit.rc'
<3>[ 3.904541] healthd: wakealarm_init: timerfd_create failed
<3>[ 4.054840] init: /dev/hw_random not found
<3>[ 4.055114] init: cannot open '/initlogo.rle'
<7>[ 4.057037] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<7>[ 4.057434] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<7>[ 4.057861] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<3>[ 4.059265] android_usb: already disabled
<3>[ 4.059661] init: property 'o.serialno' doesn't exist while expanding '${ro.serialno}'
<3>[ 4.059783] init: cannot expand '${ro.serialno}' while writing to '/sys/class/android_usb/android0/iSerial'
<3>[ 4.060333] init: /dev/hw_random not found
<3>[ 4.060546] init: Unable to open persistent property directory /data/property errno: 2
<3>[ 4.062438] init: cannot find '/sbin/setup_adbd', disabling 'setup_adbd'

Don't look very good.
[Nook HD, HD+ Android Development] :
These are found on bootable ovation builds so they don't have anything to do with keeping it from booting OR can be ignored.
[Nook HD, HD+ Android Development] Dread This Day:
Ah, alright. I wish I knew enough to figure this out. I guess we'll see when [MENTION=4243514]Hashcode[/MENTION] has some time. Hopefully whatever the problem is is easily discernable in the log. Waiting game time.
[Nook HD, HD+ Android Development] :
Apparently, I missed an error (edit: well, there's actually two errors here) -> <3>[ 3.901092] init: could not import file '/init.recovery.omap4hummingbirdboard.rc' from '/nit.rc'

which sort of goes with this one that was in the other post -> <3>[ 4.065338] fs_mgr: Cannot open file /fstab.omap4hummingbirdboad

Was able to nearly duplicate your kmsg log and broken boot on the ovation. Will upload what will hopefully be a fix maybe within an hour or so of this post.

Don't know where these files names came from as they do not show up in either of hashcode's or cm's git code nor are they in the build nor are they even spelled correctly. Also do not know why this build would work for others with this problem. So it will be interesting to see what happens...
[Nook HD, HD+ Android Development] Dread This Day:
Thank you for your help, time, and effort. That's pretty strange. And, I'll guinea pig anything you've got. I'll be at the ready.
[Nook HD, HD+ Android Development] :
Here ya go:

MD5: 2dd373fbe7351bfd1a3b6b7805c7c660

https://www.dropbox.com/s/1hry18d10fwr23z/DREAD-cm-12-20150111-UNOFFICIAL-hummingbird.zip?dl=0

Worst case is nothing worthwhile happens which means there's some other problem that's causing the problem where a new build would possibly be necessary. Best case and what I expect is that it likes seeing the files it couldn't find before and finally boots into lollipop.

No problem. Its a nice change of pace now and then. Though I generally don't like doing this if I can't test it first, but at least did do some testing on the ovation which is very similar so that's good.
[Nook HD, HD+ Android Development] Dread This Day:
Okay, another minute or two and I'll be flashing, I will report back, of course.

---------- Post added at 02:02 AM ---------- Previous post was at 01:36 AM ----------

Sorry for the delay. After full wipe and flash, upon boot, LCD lights up but is blank, and stays blank. I'm redownloading just in case, to flash again, and get a kmsg log again.
[Nook HD, HD+ Android Development] :
Rats. Had triple checked to make sure it was put back together correctly and vice versa. poodoo.

Not sure what else to try at this time. Yeah, if there's something in the kmsg log it might be interesting.
[Nook HD, HD+ Android Development] Dread This Day:
Hey, i appreciate the effort. We'll get the kmsg log as soon as the restore is done, I'm doing this all mobile wise from bed. I'm excited to see this log.

---------- Post added at 03:12 AM ---------- Previous post was at 02:31 AM ----------

Okay, the log is here http://pastebin.com/grbSPrXF. I haven't looked through it yet, but will now.
[Nook HD, HD+ Android Development] :
Apparently, the spelling has become a bit better -> <3>[ 3.777954] init: could not import file '/init.recovery.omap4hummingbirdboard.rc' from '/init.rc'

<3>[ 3.943359] fs_mgr: Cannot open file /fstab.omap4hummingbirdboard

So what I did was null as the spelling changed. That's annoying. lol

It seems I need a break for now as my simple tests that should boot are failing to do so which does no good. Its gotta boot.
[Nook HD, HD+ Android Development] ST Dog:
Still errors init.

<3>[ 3.777954] init: could not import file '/init.recovery.omap4hummingbirdboard.rc' from '/init.rc'
<3>[ 3.781433] healthd: wakealarm_init: timerfd_create failed
<3>[ 3.931793] init: /dev/hw_random not found
<3>[ 3.932067] init: cannot open '/initlogo.rle'
...
<3>[ 3.936614] init: property 'ro.serialno' doesn't exist while expanding '${ro.serialno}'
<3>[ 3.936706] init: cannot expand '${ro.serialno}' while writing to '/sys/class/android_usb/android0/iSerial'
<3>[ 3.937469] init: /dev/hw_random not found
<3>[ 3.937652] init: Unable to open persistent property irectory /data/property errno: 2
<3>[ 3.939514] init: cannot find '/sbin/setup_adbd', disabling 'setup_adbd'
<3>[ 3.940246] android_usb: already disabled
<3>[ 3.943359] fs_mgr: Cannot open file /fstab.omap4hummingbirdboard
[Nook HD, HD+ Android Development] :
Sorry. EDIT: Just can't get it to boot after changes. Will continue to try in a more quite fashion. If something works, you'll know.

If someone else knows how to then they can do so.
[Nook HD, HD+ Android Development] ST Dog:
I sort of dropped out of the linux kernel game around the time selinux was getting started and have never dealt with it much.
[Nook HD, HD+ Android Development] Dread This Day:
Well, us mere mortals tried. At least we have some logs and a sense of direction. If anyone stumbles upon anything new, or had any new ideas, I'll be here waiting. We'll figure it out, sooner or later.
[Nook HD, HD+ Android Development] :
I've come to the conclusion that a full build from source is

definitely

required to get this thing fixed. After simplifying the flashing process as far as possible I can only assume selinux. Even a comment added inside boot.img will cause boot to fail which I don't remembering happening the last time I did this stuff pre-cm11 or the advanced hard drive is missing some information by now.

Not sure I've got the time to set that all up and build it so if I do you'll just find out and if not then someone else will eventually.

Striked for lameness, please continue to newer posts.
[Nook HD, HD+ Android Development] Dread This Day:
Either way, thank you for all of your help. I understand if you don't have the time or don't feel like dealing with it. I'd do it myself if I A). Knew more B.) Had a decent build machine. I'll just try to be patient and hope someone with the time and expertise to fix it pops up.
[Nook HD, HD+ Android Development] ST Dog:
I like that :good:
[Nook HD, HD+ Android Development] :
Get your horses. I might have just been doing something stupid expecting linux to just get it right with my corner cutting. Will know within an hour more or less from this post...
[Nook HD, HD+ Android Development] Dread This Day:
Oooooooooooooooo :D
[Nook HD, HD+ Android Development] :
View attachment 3157973

EDIT: Removed attachment as it didn't fix boot.
[Nook HD, HD+ Android Development] Dread This Day:
Okay, will test in about 5 minutes. Oh, I still have the build. :D
[Nook HD, HD+ Android Development] Zippy Dufus:
Could you tell me (or point me to a how-to) how you signed your flash-able zip file?

I bundled up a special kernel but could not make the updater-script's safety-check against flashing in the wrong device work probably because it was unsigned. So I commented that line out making for a very dangerous installation package!

In advance, thanks.
[Nook HD, HD+ Android Development] Dread This Day:
I regret to say that it would not boot, but, it did show more signs of life than the last flash. This time, the Nook logo appears, last time, it did not. Then, it disappears, the screen stays on, but blank, and that is it. I grabbed the kmsg log: http://pastebin.com/rP0Nc1jJ
[Nook HD, HD+ Android Development] :
Not sure what's happening there as it should just be compressed it into a normal zip as that's all that's needed. Nothing has to be signed.
[Nook HD, HD+ Android Development] leapinlar:
To stop it from checking for signature, just toggle the option off in CWM. But it is not the signature check that stops a flash to the wrong device, it is the assert statement in the updater script file. And you fix that by changing ovation to hummingbird in the assert line.
[Nook HD, HD+ Android Development] :
That means the edited boot file is now working...

But yeah, it looks like there's nothing new. As long as you flashed the patch after the build and then rebooted then the files that its complaining about not finding should be there in which case it shouldn't still be doing the same thing. Yet it is.

Sadly, its back to waiting. Sorry :(
[Nook HD, HD+ Android Development] Dread This Day:
I seriously appreciate all of your help and input. You're awesome. Hey, we tried. I'll just wait.
[Nook HD, HD+ Android Development] :
Not to get your hopes up again but just found out where the filenames are coming from -> /proc/cpuinfo

Hardware	: OMAP4 ovation board <- look familiar?

As in -> fstab.omap4hummingbirdboard

Now, ovation build doesn't seem to look for files named like that but the hummingbird build does. So I'm going to try something else today or tomorrow and see if it can be overridden without the source which according to research may be possible.

It hasn't beaten us yet.
[Nook HD, HD+ Android Development] Dread This Day:
As you can tell, I live for the notifications of this thread. I'll be around for whatever you come up with that may work. Thank you!
[Nook HD, HD+ Android Development] Blenky:
New build?

Any update on a new build? Its been a month since the last one?

Heres hoping.
[Nook HD, HD+ Android Development] FirePsych:
1st rule of Fight Club is you don't talk about Fight Club

1st rule if XDA is you don't ask about ETAs
[Nook HD, HD+ Android Development] Dread This Day:
Seriously. [MENTION=4794037]Blenky[/MENTION] [MENTION=4243514]Hashcode[/MENTION] does it on his own time, we'll get it when we get it, if we get it.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Well, then what about official cyanogenmod forum??
[Nook HD, HD+ Android Development] Dread This Day:
If we don't have a device maintainer, such as [MENTION=4243514]Hashcode[/MENTION], Cyanogen won't pick it up.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Ya, I totally do agree with you. But I wish there were few more of them. I am hopeful in these guys to support the development even if the cyanogenmod drops official support.
[Nook HD, HD+ Android Development] :
Actually, cyanogenmod has the lollipop source code for acclaim, hummingbird, and ovation and there have been several updates to the code recently for acclaim so they are being worked on a tiny bit. Likely will only be available in the nightlies once they meet all of cyanogenmod's requirements.

I know selinux is a requirement for cm12 which ovation and hummingbird have that turned on in the unofficial build here, but I don't know what the other requirements are. Apparently ovation isn't good enough yet and hummingbird is still not booting for some, so that gives you and idea that its not yet ready for prime time.

How long will it take? Not sure anyone knows. It will be when it is.
[Nook HD, HD+ Android Development] Dread This Day:
I wonder if any of their code changes in Hummingbird fix the boot issue.
[Nook HD, HD+ Android Development] :
I updated the post to clarify changes have been for acclaim specifically. And handful general non-device updates about 10 days ago that I'm not including, but nothing for hummingbird that I can see.
[Nook HD, HD+ Android Development] Dread This Day:
Hummingbird doesn't get any love any more.
[Nook HD, HD+ Android Development] :
EDIT: Removed as it probably doesn't work. Its in verygreen's hands now :) Yay!
[Nook HD, HD+ Android Development] Dread This Day:
Okay, I'm on it! :D
[Nook HD, HD+ Android Development] verygreen:
If somebody can briefly state the current problems with hummingbird or point at a post that describes all the problems in one place - that would be great, I do not really have time to read 34 pages of messages, sorry.

I've been doing hummingbird builds for some time to test for Hashcode and I have zero problems whatsoever since the very first build. I know there's a different display option for hummingbird, but I do not have a device like that - could this be the problem at hand?

Anyway, I imagine we can increase the testerbase somewhat with an sdcard build, then people can experiment without wiping out their working base. If there's enough interest, I can publish some binaries.
[Nook HD, HD+ Android Development] Dread This Day:
I just checked my screen vendor, it's "LGD".: I guess that is our problem. But, how to fix? Also, in a nutshell, on most hummingbird devices, it won't boot. It cuts out at the cyanoboot logo, and loops into recovery. Also, thank you for responding to me.
[Nook HD, HD+ Android Development] :
Awesome. Dread this day's original kmsg is posted here -> http://xdaforums.com/showpost.php?p=58689427&postcount=287

Some quick highlights:

<3>[ 4.065338] fs_mgr: Cannot open file /fstab.omap4hummingbirdboard

<3>[ 3.901092] init: could not import file '/init.recovery.omap4hummingbirdboard.rc' from '/init.rc'

<6>[ 4.956542] SELinux: Context ubject_r:adb_keys_file:s0 is not valid (left unmapped)

<3>[ 4.096374] HDCP: failed to load keys

If there's something else of importance, idk.
[Nook HD, HD+ Android Development] Dread This Day:
Oh and here is the kmsg boot log from the failed boot.http://pastebin.com/R4KpLe3G