How to Root and set up a new Nook Glowlight 3

Search This thread

ShinRa Actual

New member
May 26, 2019
2
0
what is the adb command to manually launch relaunchx? the launcher option stopped working, and i can't get it to run at all.

to clarify, i followed this guide last year and had everything working. A few weeks ago, the nook booted into the original B&N OS, and I no longer have the option of switching to relaunch x. I've tried uninstalling and reinstalling it, among other things, and I can't get the thing to boot into relaunch x, or give me the window with the option to switch. How can I run relaunchx manually through adb or otherwise get the option to switch over?
 

dotancohen

Senior Member
Aug 8, 2011
57
6
dotancohen.com
Could not use ADB, "unauthorized" without device prompt

On my 6" Nook 3, I had set up a launcher and Ankidroid, but a few months later I could not use ADB, rather I kept getting the "unauthorized" error without a device prompt.

For those in the same situation, try opening the stock Nook reader app, then opening the top-down curtain and clicking Settings. From there, go into the About menu and click the Nook icon about a dozen times to get into the debugging screen. Now, click Disable Mass Storage, then click Allow Debugging.

After this, I was able to use ADB to get a shell or install apps.
 
  • Like
Reactions: Pastinakel

retrobits

Senior Member
Nov 30, 2007
69
14
new Glowlight 3, new firmware, root still good!

I just picked up an amazon refurb GL3 app version 49.2.36/4.9.2.24. Followed the instructions in the OP and was successful installing relauncherx and custom bootanimation.
After a few days, I noticed there was an update, and reading about it elsewhere, found that apparently there were significant performance improvements.
I was having trouble with the update installing, kept freezing the GL3. So I performed "Erase and Deregister" and did the B&N setup again, this time accepting the update.
I checked the version after upgrade: 50.0.117/5.05.35. Again, the instructions in the OP for rooting worked 100%. THANK YOU! Running FBReaderJ_nst now.
I can report the performance of the device is noticeably much better. Its still a little pokey like a typical e-ink device, but does not lag as much as before.
 

purrow19

New member
Mar 11, 2020
1
0
Hey, sorry if posting in old threads isn't allowed.... I have the GL3, trying to fix the boot animation after I completed installing ReLaunchX and I encounter an error after inputting "mv /system/bin/bootanimation /system/bin/bootanimation.bak" and it returns "failed on '/system/bin/bootanimation' - Permission denied" This is after running rootnook.cmd

If anyone can help me out I'd be super grateful, I'm a complete newb to rooting and fiddling with cmd in general so if any additional info is needed let me know !
 

aiamuzz

Senior Member
Dec 24, 2011
505
46
@Renate NST ...

a small question on Glowlight 3(the 6 inch black 512MB Ram Device) ... can one modd a sd card reader into this device ?
If so ... can you point me to a thread which successfully accomplishes the same ?

thanks.
 

Renate

Recognized Contributor / Inactive Recognized Dev
SD card reader into this device?
https://forum.xda-developers.com/nook-touch/general/adding-sd-card-to-glowlights-2-3-4-t3944830

This works great on the Glow2 and the Glow4.
(I have 32GB on my Glow2 and 128GB on my Glow4.)

The Glow3 uses the same SDIO port on the breakout pads and the WiFi.
You'd have to sacrifice the WiFi (including desoldering the WiFi module) to make it work.

You could do this using USB host mode and a flash drive/card burner/card,
but USB host is so problematical unless you want to use an always on/always powered setup
this would really not work so well.
 
  • Like
Reactions: aiamuzz

aiamuzz

Senior Member
Dec 24, 2011
505
46
https://forum.xda-developers.com/nook-touch/general/adding-sd-card-to-glowlights-2-3-4-t3944830

This works great on the Glow2 and the Glow4.
(I have 32GB on my Glow2 and 128GB on my Glow4.)
Wow ... fantastic !!!

[QUOTE

The Glow3 uses the same SDIO port on the breakout pads and the WiFi.
You'd have to sacrifice the WiFi (including desoldering the WiFi module) to make it work.
[/QUOTE]

Oh !!!
does this mean i can't have a functional SD card slot ... AS WELL AS .. a wifi on a Glow 3 device ?
 

Renate

Recognized Contributor / Inactive Recognized Dev
Oh !!! Does this mean i can't have a functional SD card slot ... AS WELL AS .. a wifi?
Erm, I went back to look at my Glow3.
I hadn't gotten that to work before.
It's dependent on NTX hwcfg, the kernel and the hardware.
I couldn't directly see again the connection between the pads and the WiFi module.
I'll have to double check this all again.
Still, I think that you probably can't have it all.
I'll look again.
 
  • Like
Reactions: aiamuzz

Renate

Recognized Contributor / Inactive Recognized Dev
I took another look at the Glow3, it's complicated.
SD2 is actually connected to the WiFi.
SD3 is connected to the test points.
When you enable/disable WiFi the software enables/disables SD3!
This is wrong. It's what had me jumping to conclusions.

I'll see if I can get an SD card working on the Glow3.
Then I'll see if I can config hwcfg or patch to have it enable/disable the right SD.

Edit: Yes, I got the hardware working. See the specific thread.
https://forum.xda-developers.com/nook-touch/general/adding-sd-card-to-glowlights-2-3-4-t3944830
 
Last edited:

Renate

Recognized Contributor / Inactive Recognized Dev
Thanks, @Kramar111

It's good to get that synced up to the 5.0.
I have the source tree from a while ago. Does anyone have the link for the source? (I'm a mess at keeping track of this stuff.)
Who around here builds kernels from source? I've never done that. I only patch them.

Trivia:
The "image" packs the kernel and the gzipped/cpio'ed ramdisk.
The kernel is not compressed, but is composed of an uncompressed stub and a compressed payload.
So to patch the kernel, you only have to extract the kernel, extract the payload from that, patch the binary, then everything in reverse (plus patching the internal offsets).

So, I got the SD card working on the Glow3. It requires kernel and ntxcfg mods.
Code:
[email protected]_6sl:/ # df
Filesystem               Size     Used     Free   Blksize
...
/mnt/media_rw/extsd     28.5G    20.0K    28.5G   4096
Follow this on: https://forum.xda-developers.com/nook-touch/general/adding-sd-card-to-glowlights-2-3-4-t3944830
 
  • Like
Reactions: Kramar111

aiamuzz

Senior Member
Dec 24, 2011
505
46
Hi,
Can somebody post screenshots of the Glowlight 3 rooted and running a non-stock launcher ?
the apps drawer / dock ...
anybody tried any other full fledged android launcher besides the RelaunchX ? Kindly post the screenshots of the same ...

thanks.
 

jchimene

New member
May 28, 2020
2
0
Hi,
Can somebody post screenshots of the Glowlight 3 rooted and running a non-stock launcher ?
the apps drawer / dock ...
anybody tried any other full fledged android launcher besides the RelaunchX ? Kindly post the screenshots of the same ...
thanks.
I only have relaunchx running. So IDK if screen shots will do you any good.
However, rootnook.sh is mostly barfage w/r/t/ the error checking. Execute the adb steps individually to fix the script. I do have Moonreader and an old version of Opera installed and running.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    I got tired of having to jump between a bunch of threads when setting up my Glowlight 3. So I'm consolidating directions into one post in the hopes that it'll save others time and trouble. Credit for instructions should go to the people who actually wrote them: arnchav of mobileread; RyogoNA, Silent eInk, cazar and Renate NST here on xda; and everyone who figured out the root exploit, sideloading, the devs behind Relaunch, RelaunchX and F-Droid. Material lifted from their original posts (linked at the bottom).

    Now, this is going to walk you through doing a few things:
    A) Setting up a progam called ADB on your computer so that it can talk to your NG3
    B) Adding a "Launcher" app to your nook so that you can access other apps you sideload later
    C) Root theNook so that you can do more stuff with the settings, including the ability to...
    D) Fix a bug that, after installing a launcher, causes the NG3 to get stuck on the loading screen after rebooting

    Before you start, you need to set up ADB on your computer. Follow the instructions linked here. The rest of this post will assume you're using Windows, but won't be hugely different from other OSs.

    Here we go:

    To set up ADB on your nook:

    1. On your Nook, go to Settings>About. You should see the serial number, app version, etc. At the top of that page, there is a nook icon. Tap that icon rapidly until the developer menu opens.
    2. Tap "Android Development Settings" and check the box for "USB debugging".
    3. At the Developer options screen you are on (where you checked the box), hit the back arrow at the top-left of the screen to go back. But do not exit the developer menu.
    4. On your computer, open a command prompt and navigate to the folder where you put adb (in my case I typed in "cd adb/platform-tools")
    5. Plug the USB in to the nook. When the nook prompts you to turn on USB mode, do so. At the adb command prompt, type adb devices. ADB should recognize the nook, but say that it is unauthorized.
    6. From windows, eject the nook to disconnect nook's file sharing. Once the nook's USB file sharing screen goes away, you should be able to see the developer menu again. Tap "Allow Debugging" one time! There will be no confirmation, just do it one time.
    6. Unplug the USB, plug it back in, turn on USB mode when prompted. Back in the command prompt, type adb devices again. This time it should see the device and simply say "device" where it used to say "unauthorized". Congratulations! You can now install a launcher.

    To install a launcher, like RelaunchX

    1. Download your launcher apk of choice. If you don't know what to pick, try RelaunchX, and download the latest version from plusz's thread here: https://www.mobileread.com/forums/showthread.php?t=284418 (n.b. To make things easy, ignore his suggestion to get it through F-Droid as you'll need a new launcher to use F-Droid in the first place. Just download the apk).
    2. In Command prompt, type adb install <filelocation>, where filelocation is the complete address of the apk. If you have file explorer open, you can just type adb install then a space, then drag the file in to the terminal and it will copy the location for you. (Make sure again that there is a space between "install" and the path or it won't work).
    3. ADB should do it's thing and you will get a "success" message in Terminal.
    4. Eject the nook from the PC. Shortly after the connection is cut, a window should open on the nook allowing you to select either the nook launcher or your new launcher. If you use RelaunchX, you may get a warning that it wasn't built with this device in mind. You can ignore it, it works great on this device.

    This is all great, except there's a bug in how B&N set up the device that only shows up if you install a new launcher. If you reboot the device, you'll be stuck on the boot animation until you do weird things like hold down the power button for a long time to pull up the reboot/power off options (only seems to sometimes work). To fix that, we actually have to disable, remove, or replace the boot animation file itself.

    To root:
    1. Download the modified Glowlight Plus script attached here ("rootGL3.zip" - almost identical to cazar's rooGLP-3 script package, but with one line changing the model number from 510 to 520)
    1. Enable USB debugging in Developer options
    2. Connect USB cable and make sure your nook is showing up in 'adb devices'
    3. Extract rootGLP.zip and run rootnook.cmd (or rootnook.sh on linux)

    To fix (read: disable) the buggy boot animation:
    1. Connect your nook to the computer again
    2. (windows) open a command prompt and and navigate to the folder that adb is in.
    3. Enter the following commands, in order:

    Code:
    adb shell
    su
    mount -o remount, rw /system
    mv /system/bin/bootanimation /system/bin/bootanimation.bak
    reboot

    OPTIONAL: To restore a working boot animation (steps above will replace broken boot animation with a black screen that goes away after a few seconds)
    1. Download the attached zip
    2. If it's not still connected, connect the Nook to the computer again and tap the button on the nook to turn on USB mode when prompted,
    3. On your computer, open up the Nook in Explorer(/Finder/your file manager of choice). Open up the NOOK Folder if you see one.
    4. Copy the file inside the zip (bootanimation) to that folder on the Nook.
    5. Eject the nook (as in, in windows, click the option to safely remove it as a device) but keep it physically connected
    6. Open a command prompt(/terminal/whatever you use for adb) and navigate to the folder that adb is in.
    7. Enter the following commands:

    Code:
    adb shell
    su
    mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
    cp /storage/spsd/NOOK/bootanimation /system/bin/bootanimation
    cd /system/bin
    chmod 755 bootanimation
    reboot

    You now have a rooted Nook Glowlight 3 that'll boot into a launcher of your choice! You can now sideload apks of your choice using adb the same way you installed RelaunchX.

    Have fun!

    Sources for these instructions:
    https://www.mobileread.com/forums/showpost.php?p=3632665&postcount=118 (how to sideload onto nook 3)
    https://forum.xda-developers.com/showpost.php?p=75717722&postcount=113 (same as above, diff user)
    https://www.mobileread.com/forums/showthread.php?p=3632665#post3632665 (to get RelaunchX)
    https://forum.xda-developers.com/showpost.php?p=64191791 (for nook GLP rooting script)
    https://forum.xda-developers.com/showpost.php?p=76042888&postcount=127 (to fix boot animation loop)


    HELP! I DID THIS A LONG TIME AGO AND NOW MY NOOK GLOWLIGHT 3 IS STUCK ON THE LOADING SCREEN!

    Don't worry, this is fixable. What's happened is that Barnes and Noble pushed out a system update that undid almost everything except that part that breaks the boot animation thing (specifically it overwrites the directory with everything that gives you root access and a working boot animation, but left your custom launcher in place).

    All you have to do is re-do most of the steps above. Start from the "to root" step - even if the device is stuck on a boot animation, you should still be able to use adb. After redoing the steps, your GL3 should work normally again.

    Unfortunately it looks like this is going to happen every time B&N pushes a system update, but that's not that often.
    2
    @Shagbark You seem to have a lot of trouble with your Glow. I hope that some of the standard things you've learned by now.
    Yes, ADB supports multiple devices at a time but you have to differentiate them by serial number.
    Code:
    C:\>adb -s 12345678 shell
    $ ls -l
    At least I try to make it clear what you're typing to. "C:\>" means from the desktop (even if you are using Linux), "$" means to an unrooted shell, "#" means to a rooted shell.

    You can remap the physical buttons on the Glows, it's all in /system/usr/keylayout

    There's no reason anything should be taking 10 seconds to do on your device.

    If you're in "NOOK" on your Windows File Explorer, you're running UMS.
    Most people would not recommend that. It's bad technology and you are using a tiny "sandbox".
    I use exclusively ADB (and my adbsync.exe utility) to sync things.

    There are other readers besides the stock B&N readers. People have different tastes.
    2
    I took another look at the Glow3, it's complicated.
    SD2 is actually connected to the WiFi.
    SD3 is connected to the test points.
    When you enable/disable WiFi the software enables/disables SD3!
    This is wrong. It's what had me jumping to conclusions.

    I'll see if I can get an SD card working on the Glow3.
    Then I'll see if I can config hwcfg or patch to have it enable/disable the right SD.

    Edit: Yes, I got the hardware working. See the specific thread.
    https://forum.xda-developers.com/nook-touch/general/adding-sd-card-to-glowlights-2-3-4-t3944830
    1
    Happy to report that the excellent instructions work great on the new 7.8" Glowlight Plus that got released yesterday. Change the model number to BNRV700 in the rootnook.cmd file and you're good to go!
    1
    Could not use ADB, "unauthorized" without device prompt

    On my 6" Nook 3, I had set up a launcher and Ankidroid, but a few months later I could not use ADB, rather I kept getting the "unauthorized" error without a device prompt.

    For those in the same situation, try opening the stock Nook reader app, then opening the top-down curtain and clicking Settings. From there, go into the About menu and click the Nook icon about a dozen times to get into the debugging screen. Now, click Disable Mass Storage, then click Allow Debugging.

    After this, I was able to use ADB to get a shell or install apps.