yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
4.4.2

[ro.build.fingerprint]: [NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/47.2.70_user:user/release-keys]
[Nook Touch General] RyogoNA:
FYI, it is almost certain that Glowlight 3 firmware is same as in Glowlight Plus so rooting script for NGP should work for NG3 also.
[Nook Touch General] Windsor1959:
I tried to run the script on my Glowlight 3, using a Windows PC that has Minimal ADB and Fastboot installed. I can see my Glowlight in adb devices. I can install apps to my Glowlight. However, when I try to run rootnook.cmd, I get a message - ADB not connected?

What am I missing?
[Nook Touch General] RyogoNA:
maybe you should update adb in rootnook.cmd folder.
[Nook Touch General] Renate:
Glow 3 is a BNRV520, not a BNRV510.

Change line #9 in the script.

Unrelated to your problem, but as info VID 2080, PID 000B.
[Nook Touch General] Windsor1959:
That did it! I have root. Thanks.
[Nook Touch General] spedinfargo:
Stupid question here: do I literally change the line in the file from this:

key 192 F10

to this:

key 192 BACK

??

Thanks!
[Nook Touch General] Renate:
Yes.

Of course you have to remount /system to modify that.

mount -o rw,remount /system

My personal choice (because I use a reader that uses page up/page down):

key 191 BACK
key 192 MENU
key 193 PAGE_UP
key 194 PAGE_DOWN
[Nook Touch General] spedinfargo:
Wow - that all worked great! Had to dust off my VI skills from 20 years ago (and learn about PuttyTray so you can run busybox's VI on Windows). Also didn't notice that my nook was prompting me to confirm my SU request to be able to mount the system as read-write. Thanks again for helping with the super-basic questions...
[Nook Touch General] Windsor1959:
Pardon my own super-basic question - but, now that I have root, is this something I can do with Root Explorer, or some similar app? If so, would this remap the buttons for everything that uses them? Thanks!
[Nook Touch General] Renate:
I don't know Root Explorer, but if it can remount /system rw, then sure.

If you have a rooted ADB shell, then sure.

You don't have to use an editor on the Nook.

If you have any ADB connectivity at all, just pull the file directly, edit it on your desktop, push it to /sdcard, then copy it back to /system/usr/keylayout.

Yes, this is what translates the (arbitrary) "scan codes" from an input device to the keycodes that Android uses.

If you use the stock B&N reader you'll probably want to keep some of the F9-F12 keys as they are.
[Nook Touch General] Renate:
Does this void my warranty?

Does this void my warranty?

JST XH style 4 pin straight header into the PCB.

(Note: The conformal coating on the PCB is pretty mean, scrape it off the pads.)

Adafruit FTDI Friend.

The case is cutout right at the lower edge of the back case.
[Nook Touch General] Renate:
Here's another reason to install a connector.

Yes, it gives you easy root access (and if you're interested in it, early boot progress).

You can also attach a little box with a µP and buttons to be your buttons.

This is not paralleled off the switches.

It actually issues commands to the shell which runs some code which injects scancodes which get converted to keycodes which turns pages.

(This doesn't use the Android "input" command which is too slow because it has to load Java.)

I've wanted this for a while so that I can park my Nook at a convenient spot and use a clicker.

Ok, you could implement this with WiFi or simply paralleling the push switches,

but I intend to use this on my old Glow Plus which is still my primary reading device.
[Nook Touch General] Windsor1959:
Remapping the buttons through Root Explorer and its text editor worked just fine. I kept 191 and 192 for the Nook stock reader, and changed 193 and 194 to be used with AlReader and a couple of other apps I have installed. I have installed Button Savior for Back and Menu functions. All buttons work as intended. Thanks again!
[Nook Touch General] Windsor1959:
Interesting. When reading with the stock Nook reader and using the page turn buttons, there is a delay after the button is clicked before the page turns. Not so when using AlReader. Page turns are almost instantaneous.
[Nook Touch General] RyogoNA:
FYI: kernel and boot sources for G3 available on BN site.
[Nook Touch General] Renate:
First, the Nooks have always been underpowered (in comparison to most Androids).

Epubs that have larger HTML chunks are always slower.

Jumping to a photo section is the worst.

The stock Nook reader uses Adobe RMSDK, libpdfhost.so.

I don't believe that it prefetches the next page.

The AIReader might prefetch.

Does it use the Adobe RMSDK?
[Nook Touch General] Windsor1959:
I don't know if AlReader uses Adobe RMSDK. When I have a little more time, I'll see if I can find out.

Yes, I can see that the Nook is underpowered compared to my Onyx Kepler Pro, but I expected that.

I've been reading with the Nook today. I like the adjustable color display more and more. I've tweaked it until I found my sweet spot. Now, others seem a little harsher by comparison.
[Nook Touch General] Renate:
I think another aspect is the psychological.

You get used to poking fingers at the screen and expect a delay.

When you hit a button you expect action.

I think this effect is felt with the side buttons on the Glow 3 and also with my button box on the Glow Plus (2).
[Nook Touch General] Renate:
A minor note:

If you (like me) don't allow your Nooks to play on the internet and just keep the WiFi shut off,

then you always have the problem of keeping the time synced.

I've used a utility called "adbtime.exe" to sync the time from a Windows box to a Nook.

The new Glow 3 was a little different than the Glow 2 and I've just updated the executable to deal with this wrinkle.

It's downloadable through the banner below.

C:\>adbtime
Thu Nov 16 15:21:21 EST 2017
[Nook Touch General] Renate:
Hmm, they seemed to have changed the way they are governing the CPU frequency from the Glow2 to the Glow3.

Is everybody else seeing a lot of these in the logcat?

Try going to the reader and changing pages.

C:\>adb logcat
...
E/i.MXPowerHAL( 2086): Not in interactive mode. Warning.

The change was in init.rc:

on property:sys.boot_completed=1
# Set default CPU frequency governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
# Set timer 40ms, min sample 60ms,hispeed at cpufreq MAX freq in freq_table at load 40%
# write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive

I commented out the "ondemand" and uncommented the "interactive".

I can't say that it makes a lot of difference in performance (or battery?), but there are no more of those annoying messages.
[Nook Touch General] Windsor1959:
Using No-Frills CPU Control Classic, I see several governor options: ondemand, conservative, interactive, userspace, powersave, and performance. I see three possible clock frequencies: 996 MHz, 792 MHz, and 396 MHz. I see three possible I/O schedulers: noop, deadline and cfq. These are typical options for similar devices I have seen, like the Onyx Boox C67ML Carta.
[Nook Touch General] alitx:
Hello, experts.

Totally new to adb and rooting.

.

I followed the GP rooting procedure ( http://xdaforums.com/show...&postcount=153), replaced model with 520 in the script. The script run successfully without error. I rebooted the device but I don't see any changes when it was up.

1. What could I do to verify the device is rooted properly? I tried to use "adb shell " to check files that were pushed to the folder /data/local/tmp/.nookrooter/ but don't see any files there..

2. Assume the device is rooted properly. what to do next? To use "adb install" to install any apks, or I'd better to install a launcher first?

Thanks in advance.
[Nook Touch General] Windsor1959:
Welcome aboard!

First, install a launcher thru adb install. You won't be able to find any apps you install later without another launcher installed, as the stock launcher isn't designed to display apps. Then, after your launcher is installed, check out the app drawer. If your Nook is rooted properly, one of the app icons you will see is SuperSU. If SuperSU is not there, try rooting again. (Root is not needed for adb install.)

If you have your launcher installed, and SuperSU, you're good to go. Install the other apps you want on the Nook by adb install.

Every time you click the Home button, you'll notice that you can now pick from two launchers, the stock Nook launcher and the launcher you installed. You can just choose the launcher you want, each time, for that time only. Or, because the Nook launcher will be an app icon in your new launcher's app drawer, you can pick your new launcher as the default one and still access the stock Nook launcher/reader whenever you want.

As you learn about root, you can then decide how you want to use those abilities to further customize your device.

Hope this helps!
[Nook Touch General] alitx:
Thank you Windsor1959! It definitely helps.

After the root script, I checked around the forum for launchers and came across zerolab's nookrooter package (https://xdaforums.com/showpost.php?p=72985958&postcount=465 ). It seemed a good choice for me since it includes both launchers and readers. I went ahead and installed the apk. The lauchers did not show up as it should be. I made a stupid move and rebooted the device. Unfortunately the GL3 does not come up and is stuck in loading/booting stage (the running dash line).

Later I realized the apk was made for GL plus, not for GL 3, and I forgot that. The device probably got messed up during the installation.

The ADB is still able to connect the device and I could run adb commands.

Is it possible, or any idea to recover/reset the device? I used "adb logcat" and got logs. It has a lot of errors.

Can I do a factory reset?

Thanks a lot in advance.

.

---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------

Looks like I'd better not to do a hard reset. People reported that they lost ADB connection after the hard reset.

Experts, any ideas?
[Nook Touch General] Windsor1959:
First of all, that package is not an apk. It needs to be installed in a special way. You would do better to direct questions to the developer of that package.

If your G3 is still stuck in 'loading' stage, try this: press the home (n) button and the power button at the same time, briefly, and then let go of both. That has snapped my G3 out of that 'stuck' state when it happened to me.
[Nook Touch General] Renate:
The first thing to do is determine what shape it is in.

The continuous dot stuff is the bootanimation which just means that it doesn't have anything better to do.

Since you still have ADB do a "ps".

Do you have zygote and surfaceflinger listed?

Try entering "am start -n com.android.settings/.Settings".

Does settings appear?

Can you summarize what the logcat errors are?
[Nook Touch General] alitx:
The trick worked ! It got my G3 out of the "stuck" state, and brought back the menu of launchers. Did you do anything afterwards, such as uninstall the apps to clean up the system? Not sure if it happens again if the device reboots next time.

---------- Post added at 05:11 AM ---------- Previous post was at 04:31 AM ----------

Thanks, Renate NST. I read a lot of your posts while searching around. I tried this command "am start -n com.android.settings/.Settings" earlier without luck.

I found zygote and surfaceflinger processes. but I did this check after the device was out of the stuck stage.

From the logcat logs, it appears that both zygote and surfaceflinger were started ok.

------------ one error related to zygote.

Line 205: I/Zygote ( 2090): Preloading classes...

Line 353: W/Zygote ( 2090): Class not found for preloading: java.lang.UnsafeByteSequence

=========== a lot of "unknown permission" for different "package".

W/PackageManager( 2468): Unknown permission android.permission.ACCESS_DOWNLOAD_MANAGER in package com.android.defcontainer

W/PackageManager( 2468): Unknown permission android.permission.ACCESS_ALL_DOWNLOADS in package com.android.defcontainer

W/PackageManager( 2468): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings

W/PackageManager( 2468): Unknown permission android.permission.ACCESS_DOWNLOAD_MANAGER in package com.android.settings

W/PackageManager( 2468): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.settings

W/PackageManager( 2468): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.settings

W/PackageManager( 2468): Unknown permission android.permission.ACCESS_ALL_DOWNLOADS in package bn.ereader

W/PackageManager( 2468): Unknown permission android.permission.BROADCAST_PACKAGE_ADDED in package bn.ereader

W/PackageManager( 2468): Unknown permission android.permission.BROADCAST_PACKAGE_CHANGED in package bn.ereader

W/PackageManager( 2468): Unknown permission android.permission.BROADCAST_PACKAGE_REPLACED in package bn.ereader

W/PackageManager( 2468): Unknown permission android.permission.READ_SETTINGS in package bn.ereader

============
[Nook Touch General] Windsor1959:
No, I didn't uninstall any apps, as the problem did not happen again - or maybe it happened once after that. I think the Nook just needs to settle down after getting new launchers and/or other apps installed!

I have a couple of reader apps, a couple of other apps that are mainly about reading (like Instapaper), and Root Explorer (a file manager that allows you - with root - to access all the partitions on the device). Everything works well, so far.
[Nook Touch General] Renate:
It could have been that /data/system/packages.xml got screwed up.

That keeps track of packages and permissions.

If it's deleted it will be rebuilt automatically but preferred activities and some other things might get lost.
[Nook Touch General] Renate:
A note only for people who like doing things the difficult way:

If you have ADB or a console and you want to bypass all the B&N new user stuff:

pm disable com.nook.partner/.OobeLauncherActivity
pm disable com.nook.partner/.FacadeLauncherActivity
reboot

The first line is necessary to kill the "Let's get started".

The second line just kills competition with your installed launcher so that you don't have to go through the picker.

(The picker will stay hidden behind the bootanimation. If that happens you can ps, then kill it.)
[Nook Touch General] speed_phreak:
So my wife currently has the original Simple Touch. This looks like a compelling upgrade. One of the things she likes most about the ST is that she can get books from both the Nook store and from the side-loaded Amazon Kindle app... Has anyone successfully installed the Kindle app, and used it to buy/sync books, on the new Glowlight 3?

Based on the comments here, it seems the Glowlight 3 is similar to previous devices, so hopefully this is still possible.
[Nook Touch General] Windsor1959:
That should work, in theory. However, you may want to try older versions of the Kindle app. First of all, the color scheme is not designed with eInk in mind. Secondly, the newer versions of the Kindle app will likely be s..l..o..w... on the Glowlight 3, or any eInk device! The app is designed with faster Android tablets in view. But, if you stick with an older version of the app, it may work fine. You may have to try more than one version to find a good one.

If anyone has installed the Kindle app on the Glowlight 3, feel free to chime in!
[Nook Touch General] nmyshkin:
You could always try the version that was optimized for the NST at one point: http://xdaforums.com/showthread.php?t=2024062
[Nook Touch General] Windsor1959:
I tried that version, out of curiosity. It had worked great on the NST. On the Glowlight 3, it wasn't pretty. It didn't look very good or work very well. I deleted it. I tried it on an Onyx that I had. That didn't work well, either.

Setting up Calibre to de-DRM books is definitely worth the bother. Then, I can read any of my books on this or any other eInk device, and use a reader that's made for eInk.
[Nook Touch General] alitx:
Great! Good to know. I unstalled them and installed relaunchx apk. My G3 has been working fine since (I did not reboot it though).

The G3 gives less than 1G to the partition for sideloading but a lot to BN's own partition. Will Root Explorer help to sideload books to BN's partition?

---------- Post added at 02:57 AM ---------- Previous post was at 02:51 AM ----------

Thanks, Renate NST. I guess I'd better leave it as is, for now.
[Nook Touch General] Windsor1959:
Trying to do that with Root Explorer might be tricky. I recommend finding out about Calibre. Calibre is an ebook management software that installs on Windows or macOS (maybe Linux, too?). You can get your eBooks into Calibre. There are plug-ins available for Calibre which can remove the DRM from Kindle and Nook books. That allows you to read these books on almost any e-reader app that supports its format, and allows Calibre to edit or change the book's format. Calibre can change a book's format - from Kindle to Nook, or vice versa - so you can read almost any book on almost any e-reader app. Then, you can get the Calibre Companion app. With that app, you can connect the Nook by WiFi to your computer with Calibre on it, and then import any or all books into the Nook. Calibre Companion and all its books will live in BN's own partition.

There is a little learning curve involved, especially if you want to de-DRM books. But once it's set up, it's quite easy to maintain and use. To me, Calibre and Calibre Companion are the best solution for what you want to do.

This forum has more info on Calibre, and is a great place to ask questions and learn a lot of stuff.
[Nook Touch General] alitx:
It sounds a perfect solution. I will dig into it. Appreciate it.
[Nook Touch General] MatthewLibre:
I am thinking of getting an ereader for my wife. We both like having complete control over our devices (we run linux on our main computers). How much control is possible on this device?

Are there any stock android roms for this device?

If we're stuck with the installed rom can the B&N software be removed?

Can the full 8GB of space be used as we see fit, or is it partitioned in such a way that hoops need to be jumped through?

Thanks for any assistance.
[Nook Touch General] Nookgirl29:
I'd like to try to get Overdrive on my Nook Glowlight 3.... that's the only app I'm interested in getting on there. Does anybody think that is possible to do? I'd like to try to play around with it myself to try to find out but I don't know anything about that.
[Nook Touch General] nmyshkin:
It may not run--or at least not without whining constantly. The app is listed on dependent on Google Play Services. I did some research awhile ago into setting up PlayStore access without GApps--mainly for devices with limited storage/RAM. You can "easily" get copies of apk files from other sources (or even the Yalp Store, which accesses the PlayStore), but they won't necessarily run without some kind of authentication, basically the ability to "phone home". Not sure if the microG apps will run on KitKat, but that would be the approach to setting up authentication for the Google Framework Services.

If you want to get into the subject, you can read my post (long one, sorry): https://xdaforums.com/nook-tablet/general/how-to-cm-11-8-gb-nook-tablet-bntv250a-t3667555

I can tell you that Overdrive (and Hoopla) works under these conditions. Not saying that Overdrive would be satisfactory on the GP3. That I don't know, although the old version--when it was still working--was fine for the NST.
[Nook Touch General] Windsor1959:
On one of the MobileRead forums, one NG3 owner reports that B&N emailed them an invitation to try out a beta firmware with only one storage partition (instead of two) after that owner had complained to B&N about the partitioning of the device. Someone else in that thread posted the update.zip for that beta firmware. - in case anyone is interested. I tried it, and sure enough - I see one partition with 6.35 GB. My Mac and my Windows device see the same.
[Nook Touch General] pejams:
Im lost

Not working for me I can't get into developer options

---------- Post added at 03:17 AM ---------- Previous post was at 03:05 AM ----------

I can't seem to turn on developer mode and install apps
[Nook Touch General] TGC-TECH:
I managed to use ADB on my GLP however I can't seem to get it to work here. It simply fails to authorize on matter what I do. There is no prompt to autorize and unlike the GLP there is no 'authorize ADB' in the hidden menu used to enable USB debugging

Thanks for the help :)
[Nook Touch General] anubis2591:
What worked for me is, go into the About section in the Settings and press the nook logo until a menu pops up. Enable USB debugging inside of Android Development Settings. Now that you've done this, selecting Allow Debugging in the previous menu will authorize the device. From there I used adb install to install ReLaunchX and other apps.

Just got my Glowlight 3 today and I love it. I had an original Glowlight that I had rooted and I'm loving how similar this is.
[Nook Touch General] poczynek:
Does anyone know what it weighs? Can't find it anywhere the weight!
[Nook Touch General] anubis2591:
I don't have a scale handy but the MobileRead Wiki say that it weights 7.0oz (196g).
[Nook Touch General] tnfsmith:
Can we load any documents outside onto the e-reader through usb connect from the PC?
[Nook Touch General] dotancohen:
Which firmware are you using? Just as soon as I finished the login process on a new GL3 it self-updated to 47.2.113 and I didn't interrupt it. I've enabled USB debugging and then clicked "Allow Debugging" but I still don't see anything in `adb devices`. A reset didn't help, either.

The output of `lsusb` contains `Bus 001 Device 070: ID 2080:000b Barnes & Noble` and I've successfully connected all three of my prior Nooks (Nook with Glowlight, Nook Glowlight, Nook Glowlight Plus) and my Note 3, so I'm pretty sure that my desktop (CentOS) is set up properly. I've tried with my trusty "the good one" USB cable and also with the cable that came with the Nook, in different USB ports on the desktop.

If it is not due to differing firmware, what else might prevent this device from being recognized by ADB?
[Nook Touch General] anubis2591:
That's odd. I have the same firmware version, 47.2.113 / 4.8.2.8 and it updated to that on first boot as you mentioned. I did all of the adb stuff initially on my Windows 10 install with an exe of adb I grabbed so I decided to try it out in my Arch Linux install to see if it was a *nix issue but my Nook shows up just fine there as well. It was just unauthorized and all I had to do to authorize the Arch install was to press "Allow Debugging" again. My lsusb string is the same as yours save for the ID and such.

I did have issues getting the Nook to authorize USB debugging at first, I do believe I enabled and disabled things at least twice as Windsor1959 mentioned on the first page but even then it was showing up in adb devices for me, it just showed up as unauthorized. The only way I've been able to reproduce your issue is by disabling USB Debugging which doesn't really help anything lol.

You can sideload any of the following document types using the stock firmware, as the official site notes:
[Nook Touch General] dotancohen:
Thank you. I'll continue to pound it and see where it goes.