yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] rshack52:
AFAIK, if you have the light set to "auto" (or dim), and don't turn the light off, then when you turn the Nook off that setting will be remembered... so when you turn the Nook back on later, the light will come on by itself..
[Nook Touch General] thinhbk11:
Thank Rshack,

But if I switched the light off before (because of daylight).and then, When midnight come, before sleep, I want to use nook on my bed, it's so dark and I don't know how to turn light on quickly. On previous version, I've just only found Home button, press and hold it.
[Nook Touch General] rshack52:
I understand that's what you want to do. But you can't. If you want to get the light to come on in the pitch dark, the device needs to have it's light *not* turned off when you last used it.

Personally, I wouldn't want to have to remember to turn the light on when I turn it off during daylight. So, for me, I'd set the light to "auto" and leave it there. In daylight, it should automatically be either very dim or completely off, but in the dark it would light right up.

I don't know what e-reading app you use, but all the ones I have used have some way to control brightness from within the app; for example, by sliding your finger up and down the edge of the display. If your e-reading app has that, then you could just leave the light switched on, and then use your finger to dim it during the day and brighten it at night. The only thing you'd need to do in the dark is find the left edge of the display to control that.
[Nook Touch General] David0226:
"Auto" light setting not possible

The Nook Glowlight Plus does not have a light sensor, and so does not have an "auto" setting for the front light. If you use Cool Reader, you can set it up so that you can adjust the light, including turning it on or off, by sliding a finger up and down one edge of the display as rshack52 suggested. If you are using the stock Nook reader, your only option is to turn on a light to be able to see to turn on the Nook's light. I have seen apps that would allow you to bring up the light control by pressing the "home" button, but so far none that turn the light on. Likely one of the devs here could develop an app that would turn the light on to some fixed value if they felt it to be of value. Unfortunately, I don't have the java programming skills to do that, because I think it would help me also.
[Nook Touch General] tbs575:
I did know how to "go back" in FBreader, like I see at page 34, I click remark go to page 47, but when I want back to page 34. I don't not know how to do in FBreader, in nook. did you know it? thanks
[Nook Touch General] David0226:
ADB over USB?

I have an embarrassing question. I have a year old glowlight plus that I rooted. My son just received a new one for Christmas which is not rooted. I am embarrassed to say I cannot connect to the new device using ADB over USB. I have enabled ADB debugging in the developers menu and Windows 7 does see the MTP connection to the device, but ADB won't see it. It sees the old rooted Nook just fine. The versions listed on the software screen are the same (Version 45.2.22 / 4.5.2.58). I do notice that there DO seem to be some differences between the new Nook and my old one prior to rooting. The sleep screen on the new Nook is primarily black with a quote from Thomas Jefferson. I don't remember this being available on my older Nook before I rooted it.

So here is my question, is there something additional that needs to be done to a newer Nook Glowlight Plus to get it to connect to ADB over USB? At some point, my son will want to at least install additional apps and he may perhaps want to 'root' it. Perhaps I should try connecting it to a different laptop?
[Nook Touch General] digixmax:
ADB-over-USB is tricky to set up as it depends on installing an appropriate USB driver for your PC Windows and configuring the right vendor/device IDs for the particular Nook in USB ini file. A much easier alternative is to do ADB over WiFi using apps such as ADB Konnect or ADB Wireless.
[Nook Touch General] David0226:
How do you get these apps on a GlowLight + (no microsd card) without first setting up ADB over USB?
[Nook Touch General] digixmax:
Sorry, I forgot that your NGL is unrooted and does not have a uSD access.

I am wondering if the new NGL has a different USB vendor device ID than that of your older NGL -- see https://xdaforums.com/showpost.php?p=64497487&postcount=179.
[Nook Touch General] Renate:
All B&N devices use 2080 (hex) as the VID.

This is how you have to modify extras\google\usb_driver\android_winusb.inf to add B&N stuff.

; Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01

; Nook Glowlight
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0007
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0007&MI_01

; Nook Glowlight Plus
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_000A
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_000A&MI_01

Yes, getting the Windows WinUsb drivers going is a bit annoying.

Certainly getting udev rules in Linux is easier and less critical if you are root.

I'd just avoid ADB over WiFi because it's too easy to forget and a security risk.
[Nook Touch General] David0226:
The values for the Nook Simple Touch and Glowlight Plus are already in my android_winusb.inf. Also, I can connect my rooted Glowlight Plus using ADB over USB, but I cannot connect my son's Glowlight Plus. My son's Glowlight Plus does connect through the MTP interface. Is there perhaps some connection cache I need to clear to allow a different Glowlight Plus to connect? Perhaps I should set up the android development environment on a second computer and attempt to connect it to the one.
[Nook Touch General] digixmax:
ADB-over-USB Access to Multiple Identical Devices

Interestingly, I just tried out ADB-over-USB on my two Nook Simple Touch eReaders and had same problem: both of them can connect as MTP devices to my Win10 PC, ADB-over-WiFi can also connect to both of them, but ADB-over-USB only sees one of the two!!!

Update

OK, with a bit of google'ing and reading up on ADB I think I've figured out a solution: we need to do a 'adb kill-server' whenever we are done connecting to a device, or just before we connect to the other device with the command "adb devices'. With this procedure I can now alternate acess over USB to both of my Nook STs.
[Nook Touch General] rupor:
Renate, it would be really nice if you would be able to publish dumps somewhere - before buying device I would like to check a couple of things. Now that Sony is not an option and I am not really happy with my kindle - new Nook seems like valid alternative...
[Nook Touch General] Renate:
Making some progress, but currently you are not going to get here without opening your Nook up at least one time.
[Nook Touch General] dnastase:
Bravo!

But besides bringing the serial interface physically to the outside of the case, how do you see it that the case has to be opened only once ?
[Nook Touch General] Windsor1959:
Looks very promising! Alas, I've never done a root console connection before, and the searches I've done so far haven't turned up much that looks relevant to this - or I might try it, for the experience of learning a new trick! But I can wait. I want to be able to install a launcher and sideload two or three apps. That's all.
[Nook Touch General] Renate:
Ok! Here's the results.

C:\>adb shell
root@ntx_6sl:/ #

How is this different? It's not over the hardware connection, it's over ADB on USB.

(As said, at the current state of knowledge you will have to crack open your Nook one time to get here.)

Now I've got to get out and get some exercise.
[Nook Touch General] dnastase:
Oh, ok, now I understand. Yes, that's exactly what I was not getting... thanks.
[Nook Touch General] Renate:
Some information points:

The first two partitions are not file systems, they are raw images with kernel and ramdisk.

The images are "ANDROID!" format and not generic Linux.

/dev/block/mmcblk1 is the primary boot

/dev/block/mmcblk2 is recovery

Partition 1 is only defined for about 6 Megs even though it is has a full 19 Megs of space available to it.

The adbd in both of these partitions is compiled to not allow root operation even if the properties are set correctly.

The Plus is 4.4.2, but most of the user software seems a rehash of the old Nook stuff.

To make things rooted:

Change default.prop

Change init.rc

Replace sbin/adbd with a version snarfed off the Android emulator Nexus 5, API 19, ARM.

setprop persist.sys.usb.config mtp,adb

setprop sys.usb.config mtp,adb

Optional: Modify init.E60QD0.usb.rc if you want ADB without MTP

Try writing your new images to partition 2.

You can run them with reboot recovery

If it all works out, write it to partition 1.

(I'm working on updating my bootutil tool to work with "ANDROID!" image headers.)
[Nook Touch General] rupor:
Well, not sure yet, I only looked quickly but judging by OSS code B&N just released device should fully support fastboot.

delta\u-boot\drivers\fastboot\fastboot.c: printf("fastboot is in init......");

And we should be able to enter various modes by putting our fingers on screen during boot:

distro\u-boot\board\freescale\mx6sl_ntx\ntx_cmd.c:

if (3 == flag) {
_led_R (1);
printf ("Entering recovery mode !!\n");
iRet = 1;
break;
}
else if (0x30 == flag) {
_led_R (1);
printf ("Entering external sd boot mode !!\n");
iRet = 2;
break;
}
else if (0x11 == flag) {
_led_R (1);
printf ("Entering fastboot mode !!\n");
iRet = 3;
break;
}
else {
printf ("Wrong points combination ! 0x%x\n",flag);
}
[Nook Touch General] dnastase:
Wow.! that would be interesting !

I just tried with two and three fingers but nothing happened. Maybe it depends on other things (eg: a screen region) ?

Where is this code ? what is OSS ?
[Nook Touch General] Renate:
Good catch [MENTION=4231280]rupor[/MENTION] !

There is fastboot supported.

The console prompts you to hit any key to go to fastboot mode.

The regular screen sensor driver is two point (verified with UsbMode).

It's clear from the snippet of code that it's looking for two fingers.

There could be other conditions, power switch, home key, USB connected...

It's also nice that it seems to print the flag if you hit the wrong points.

OTOH, I've tried a bunch of combinations and never seen a peep on the console.

We need to look at the rest of the code.
[Nook Touch General] rupor:
[MENTION=1584006]dnastase[/MENTION] I cannot post links here, but is you google for "OSS Release for NOOK 4.2" you will find "NOOK Device Terms of Service" with links to OSS releases.

Check happens during boot process (obviously as it is part of u-boot sources), presumably LED should blink:

_led_R(iRLight);iRLight=!iRLight;

And here is the rest:

dataCnt=zforce_read (data);
if (0 <= iRet && 4 == data[0]) {
if (2 == data[1]) {
int x,y;
unsigned long flag=0;
printf ("Got dual finger touched!!\n");
x = (data[3]<<8) | data[2];
y = (data[5]<<8) | data[4];
if (60 > x && (DEFAULT_PANEL_W-60) < y)
flag |= 1;
if ((DEFAULT_PANEL_H-60) < x && (DEFAULT_PANEL_W-60) < y)
flag |= 2;
if (60 > x && 60 > y)
flag |= 0x10;
if ((DEFAULT_PANEL_H-60) < x && 60 > y)
flag |= 0x20;
x = (data[12]<<8) | data[11];
y = (data[14]<<8) | data[13];

if (60 > x && (DEFAULT_PANEL_W-60) < y)
flag |= 1;
if ((DEFAULT_PANEL_H-60) < x && (DEFAULT_PANEL_W-60) < y)
flag |= 2;
if (60 > x && 60 > y)
flag |= 0x10;
if ((DEFAULT_PANEL_H-60) < x && 60 > y)
flag |= 0x20;

So it checking coordinates it seems - 2 fingers should be in some areas of the screen, will analyze code some more tomorrow.

Renate is right though - some other conditions may apply albeit I have not seen it yet...
[Nook Touch General] Renate:
The OSS sources are here:

http://dispatch.barnesandnoble.com/content/dam/ccr/nook/nook12/oss/nook_glowlight_plus_4_2_0.tgz

http://dispatch.barnesandnoble.com/content/dam/ccr/nook/nook12/oss/nook_4.5-delta.tgz

If you manage to get fastboot to popup it will appear as VID 18D1, PID 0D02.

For Windows users you may need to add this to your INF for the driver:

; IMX6SL
%SingleFastBootInterface% = USB_Install, USB\VID_18D1&PID_0D02
[Nook Touch General] Renate:
Looking through the code, it appears that the two fingers must be in adjacent corners.

They must be within 60 pixels of the corner, that means, pretty tight inside.

I see all the messages from the source in the actual u_boot ("Got dual finger touched!!"),

but I have never seen that message. It should be easy to get a dual finger message.
[Nook Touch General] rupor:
If I am reading code right (and I do not have the device - will try to visit store tomorrow, but who knows) it goes like that:

Device should be turned on by pressing power key and holding finger on home key (let's say "pressing" home key) - this initiates selection procedure. LED should change status and then you suppose to have your fingers in proper corners of the screen to select fastboot or recovery procedure. If fingers are in adjacent corners it will be fastboot, if in diagonal - recovery.

Of course I could be totally wrong, but entering recovery on Sony (also FreeScale) was never easy and device had physical buttons :p

Renate, if you could get into u-boot shell - verifying that we are looking at proper code should be fairly easy. Just issue

ntxup init

ntxup waittouch [interval (ms)] [timeout (ms)]

And you should be able to check this two-finger procedure locating proper positions...
[Nook Touch General] Renate:
Hmm, it looks like something is screwed up somewhere:

eBR-1A # ntxup waittouch
i2c_addr:chip address cycle fail(a1)
i2c_addr failed
zforce read failed !

It goes into a loop and repeats.

It's the same with supplied arguments.
[Nook Touch General] rupor:
The only thing which comes to mind is issuing "ntxup release" and then trying to read again. If it would not help - I am looking in the wrong place, that would not be the first time :(
[Nook Touch General] dnastase:
There is also some confusion I think to the orientation of the screen:

#define DEFAULT_PANEL_W	1440

#define DEFAULT_PANEL_H	1080

so maybe it should be hold horizontally ??
[Nook Touch General] Renate:
Yes, the native viewpoint is landscape.

That is fairly typical, also true of the other Nooks.

OTOH, the coordinates in that routine are considered from the portrait viewpoint.

ntxup release goes without a complaint.

(OTOH, all unknown commands to ntxup also do.)

ntxup waittouch does as before, loops on failure to read.

Wait! I know what the problem is:

They have the u-boot touch configured for Zforce IR screen.

We have an Elan touch. :mad:
[Nook Touch General] rupor:
Nice - and I though it would be easy :laugh:

Seriously - device cannot be serviced without opening the case as it has no way to enter recovery mode during boot? Or I am missing something here? Back to sources...
[Nook Touch General] rupor:
OK, how about this one:

in ntx_comm.c:

iUSB_in=ntx_detect_usb_plugin(0);
. . . . .
if(iUSB_in&USB_CHARGER_OTG) {
printf("\n**********************************\n\n");
printf("\n** fastboot mode OTG USB **\n\n");
printf("\n**********************************\n\n");
iRet = NTX_BOOTMODE_FASTBOOT;
//fastboot_connection_timeout_us_set(5*1000*1000);
fastboot_connection_timeout_us_set(0);
fastboot_connection_abort_at_usb_remove_chk_setup(&ntx_is_fastboot_abort_inusbremove);
}

ntx_detect_usb_plugin seems to be ntx_hw.c. I am not sure what parts are relevant to us (since I do not know what hardware configuration we have) but in one particular case it seems to be looking for usb id pin and then returns USB_CHARGER_OTG. Execution of this particular branch of code depends on hardware configuration:

if(49==gptNtxHwCfg->m_val.bPCB && gptNtxHwCfg->m_val.bPCB_REV>=0x20) {
// E60QDXA2
// detect the usb id pin .
if(!ntx_gpio_get_value(&gt_ntx_gpio_USBID)) {
iRet |= USB_CHARGER_OTG;
}
}

Do you think it worth exploring? I am not sure why timeout is set to 0 here...
[Nook Touch General] digixmax:
Sorry for the wrong choice of words, I had meant the PIDs being different.
[Nook Touch General] David0226:
GlowLight Plus update to 46.2.13/4.6.2.42

I connected my GlowLight Plus to WiFi yesterday, something I rarely do, to download a book from B&N. The next time I brought the device out of sleep mode, it installed an update!

The update removed my 'root' access, but did not touch my third party launcher (lightning launcher) or any of my third party reading apps. I was easily able to re-root by using the rootnook.sh script mentioned earlier in this thread. There are some big improvements (at least in my opinion) in the stock Nook reader with this update. The size of the header and footer have been reduce so that generally there is an additional two to three lines displayed per page. There are also additional formatting options, including a new justification option and three font weights.

The attached photographs show the old software on the left and the new software on the right.
[Nook Touch General] thinhbk11:
New software of BNRV510 has released.

anyone updated and rooted yet?
[Nook Touch General] David0226:
BMRV510 = Nook Glowlight Plus

See the post directly above yours.
[Nook Touch General] nessh:
Hello Guys,

First of all thanks for your work!

2nd: i see that it is possible to install es explorer and some other apps without rooting. Could somebody please write down in few lines how to do this? (i have a win10 pc if required)

Thank you!
[Nook Touch General] David0226:
Install the latest android development kit on your PC.

On the Glowlight Plus, go to settings, then software. Tap the software version number multiple time quickly until the an additional settings screen comes up. Pick Android Development Settings, check USB debugging.

Connect the Glowlight to your PC, open a command prompt and type adb shell. If it connects, you will see a prompt from the Nook. If it does not connect, find the adb_usb.ini file and add the following lines.

Add the following lines to adb_usb.ini

; Nook Glowlight Plus

%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_000A

%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_000A&MI_01

in the command window, type adb kill-server, then adb shell again. Hopefully you will get a prompt from the Nook now.

Exit the ADB shell in the Nook

Install the apks you wish using:

adb install {whatever}.apk

This is a VERY bare bones description. You will have to worry about paths to executables and other such issues which I can't help you with without being the one to install the software.

All of this information is already available on this thread, just not all in one post.
[Nook Touch General] hawki:
Can anyone recommend what's safe to uninstall? Have root, in Canada - so anything nook or B&N related isn't of any use.
[Nook Touch General] digixmax:
Rather than uninstalling the unwanted apps, you can disable them by renaming those apps' apk file extension from ".apk" to ".apk.bak" (and then rebooting the device), that way you can easily revert the change if ever needed.

FWIW, here are the apps I disabled on my NST:

Browser.apk.bak

Calendar.apk.bak

CalendarProvider.apk.bak

DemoMode.apk.bak

Music.apk.bak

NookCommunity.apk.bak

QuickStartActivity.apk.bak

ServiceOne.apk.bak

Shop.apk.bak

Social.apk.bak

Talk.apk.bak

TalkProvider.apk.bak

TelephonyProvider.apk.bak

TtsService.apk.bak
[Nook Touch General] hawki:
Great tip! Btw, what browser (and version ) and which version of Kindle app works if you know by chance

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

Just a heads up, ran the root script for the first time after updating to the latest firmware - worked great and have root.
[Nook Touch General] digixmax:
For browser (which I rarely use) I chose Opera Mobile, as my Nook is the dated Simple Touch the OM version I use is circa late 2012.
[Nook Touch General] bigphil1999:
Nook Glowlight Plus screen frozen -- help!

I rooted my Nook Glowlight Plus and had been happily reading library ebooks on it with Zeam launcher, Aldiko reader, etc for a few months...

But I took it out of my protective cover a few days ago, and unfortunately noticed that the screen and n button seem to be completely non-responsive. There are black streaks over parts of the wallpaper image.

The backlight does light up when power button is pressed. But it does not power down or reboot when I hold the power button down for 20+ secs. The unit even seems to interact with my computer through adb commands (install, reboot are reported to be "successful")... even though the screen doesn't show activity besides the backlight going on and off.

Per various posts, I tried wiping the screen with a moist towel, cleaning the crevice between the white screen front and metal backing, etc.

Any other ideas? Unfortunately I don't have the purchase receipt (X'mas office gift). Do you think B&O would facilitate a return or exchange?
[Nook Touch General] David0226:
You will have to un-root it before attempting an exchange, at least an in-store exchange if that is what you had in mind. Fortunately, you still have adb access so you should be able to get this accomplished. It sounds like you have a problem with the screen hardware as everything else seems to work.
[Nook Touch General] swd1:
I wanted to share my experience in case it helps someone.

I have been using NGP without rooting but with several apps installed and using Nova Launcher.

NGP updated the software to 4.6.2 automatically and then if I clicked on "Nook" - the stock app - it would not show up - the icon will only flicker.

I tried rebooting but still Nook app won't show up.

To get it back I uninstalled "Nova Launcher" and reinstalled it and Nook app works again.
[Nook Touch General] noimjosh:
So, it seems like the NOOK launcher was reworked to call the "Home" action, which is why the icon would flicker. After clicking it, it would call "Home" which was set to Nova Launcher. The best way I've found to get around this is to use an Activity Launcher Widget (from Nova) and launch the com.bn.nook.library.MainActivity, which loads your library.
[Nook Touch General] bigphil1999:
Unrooting a Glowlight Plus

Thank you David. I called B&N and they're going to send me a replacement. But they took my CC and asked me to return my old unit, so I still want to make sure it's as compliant as can be. What's the best way to "unroot" a Glowlight Plus over ADB? I originally used rootGLP, but it doesn't seem to have unroot capabilities. Thank you for helping out a newbie!
[Nook Touch General] swd1:
Thanks. Your explanation makes sense. But in my case just uninstalling and then reinstalling Nova Launcher fixed the problem and I can run Nook app and Nova Launcher.
[Nook Touch General] David0226:
I am not aware of an un-root script for the Glowlight Plus. However, I would at least use adb to uninstall busybox and supersu.

adb uninstall [-k] <package> - remove this app package from the device

('-k' means keep the data and cache directories)
[Nook Touch General] FerociousAndroid:
Thanks to everyone for the information posted here. Translated this site to get AI, Cool and FB readers installed.

https://zerolab.net/2016/11/23/zerolab-nooter-uncompromising-prism-edition-nook-glowlight-plus/

:good:
[Nook Touch General] bnook:
Hello, thanks for all this great work here.

A few questions I have after going through this thread.

1.) Does the Kindle App work? Some mention of it not working. Does it work by simple sideload? if rooted?

2.) Does Zerolab Nooter actually root the glowlight plus, or simply install some packages on it if you previously rooted it (using Cazar's tool)

3.) Does the google play store work if you root? How about the Good e-reader app store?

4.) How is the battery life after rooting? I have the Arta Tech C67 and battery life is only a couple days of use.

Thanks!
[Nook Touch General] bigphil1999:
Answers in-line