New Nook Glowlight Plus

Search This thread

FerociousAndroid

Senior Member
Sep 23, 2011
267
30
Hard reset

I just did the same... Here is how I resolved it. You need to do a HARD RESET per B&N NOOK support.

STEPS:
0. Make sure you have at least 20% battery charge or plug in a charger.
1. Power off your NOOK.
2. Press and hold the power button for 3 sec, screen will light up and will start booting.
3. While booting HOLD (1) the POWER button for 12 sec or until the three boot dots stop/freeze.
4. Press and hold the power button for 3 sec.
5. While booting HOLD (2) the POWER button for 12 sec or until the three boot dots stop/freeze.
6. Press and hold the power button for 3 sec.
7. While booting HOLD (3) the POWER button for 12 sec or until the three boot dots stop/freeze.
8. Press and hold the power button for 3 sec.
9. While booting HOLD (4) the POWER button for 12 sec or until the three boot dots stop/freeze.
10. Press and hold the power button for 3 sec, let the NOOK fully boot up. You will get Factory Reset screen. THIS WILL ERASE ALL YOUR SETTINGS & DATA.

NOTE:
If are on firmware version 4.5 you will not be able to register your device with B&N. "Error: Unable to connect to the NOOK service. Please try later.". Need a newer firmware. You can download the latest firmware here under the "Manual Download Instructions"

ht[delete]tps://help.barnesandnoble.com/app/answers/detail/a_id/4212/kw/4212

B&N firmware
ht[delete]tps://su.barnesandnoble.com/nook/piper/4.9/piper/2.37/update.zip
ht[delete]tp://su.barnesandnoble.com/nook/piper/4.7/2.102/update.zip
ht[delete]tp://su.barnesandnoble.com/nook/piper/4.6/2.13/update.zip
ht[delete]tp://su.barnesandnoble.com/nook/piper/4.5/1.14/update.zip




Unfortunately, I got into trouble. I downloaded the su.barnesandnoble.com/nook/piper/4.5/1.14/update.zip file, copied it to the root directory, restarted the device. For a while the old one left everything but in a minute started upgrading ... Then he restarted and came the surprise: "Unfortunately, NOOK has stopped." And another subtitle appears: "com.nook.partner is not responding. Do you want to close it? " Choosing: Wait or No.
Unfortunately, I'm not very familiar with these things, so I would like to ask for help after the NOOK brick.
What can I do???
 

FerociousAndroid

Senior Member
Sep 23, 2011
267
30
On 4.5 how did you get pass the Sign In screen? I can't get pass the "Error: Unable to connect to the NOOK service. Please try later." due to not a new firmware according to B&N support. I'm trying to enable USB debug mode.

Thanks in advance.

Update: Went back to 4.5 with old official update.zip, then rooted, installed TWRP, trying to flash the 4.9 update.zip with edited default.prop, got the classic error 7 on TWRP...
 

tarnagy

Member
Feb 4, 2009
30
1
FerociousAndroid
I was able to recover the device and I installed version 4.7. I turned off the wifi, so do not upgrade to 4.9. Now I'm trying to move on and use adb to install android apps!
Thank you very much for your help!
Now I know at least that it can be reset to 4.5 version. Can it be similar to higher versions?
 

Renate

Recognized Contributor / Inactive Recognized Dev
no adb and no recovery, and what's worse, no screen display so that I can't figure out what's happening.

I tried to see if there were any OEM USB on boot up, but it appears that the USB is not configured until the Nook software does it.

I don't know if B&N has any secret way to recover bricked NGPs without opening the case.
I know that if I opened your case, used the hardware console and the u-boot were ok I could recover it.

Sorry
 

klemperer

Member
Mar 1, 2011
19
0
I tried to see if there were any OEM USB on boot up, but it appears that the USB is not configured until the Nook software does it.

I don't know if B&N has any secret way to recover bricked NGPs without opening the case.
I know that if I opened your case, used the hardware console and the u-boot were ok I could recover it.

Sorry

I've opened the case. Could you let me know the steps to recover it using the hardware console and the u-boot? And will the data be erased during the recovery?
Thanks.
 

Renate

Recognized Contributor / Inactive Recognized Dev
The hardware console is described here: https://forum.xda-developers.com/no...light-plus-t3230323/post63456985#post63456985
You should be able to see activity on it when you power up your NGP.

You can follow the directions here: https://forum.xda-developers.com/no...low2-glow3-t3784575/post76391539#post76391539
This will allow you to boot a system without altering the internal memory at all.
I'd advise that you do a backup before you plow forward seeing what the actual problem is.

If you can't get Neo Noogie and the splash screen going you may have either a trashed u-boot or hardware problems.
 

klemperer

Member
Mar 1, 2011
19
0
The hardware console is described here: https://forum.xda-developers.com/no...light-plus-t3230323/post63456985#post63456985
You should be able to see activity on it when you power up your NGP.

You can follow the directions here: https://forum.xda-developers.com/no...low2-glow3-t3784575/post76391539#post76391539
This will allow you to boot a system without altering the internal memory at all.
I'd advise that you do a backup before you plow forward seeing what the actual problem is.

If you can't get Neo Noogie and the splash screen going you may have either a trashed u-boot or hardware problems.

Thank you for your quick reply. I have an USB2TTL line on hand, which has VCC/GND/RXD/TXD for connection. Then I should connect RXD to RX, TXD to TX and GND to J4?
 
Last edited:

Renate

Recognized Contributor / Inactive Recognized Dev
Then I should connect RXD to RX, TXD to TX and GND to J4?
No.
The "TX" or "RX" is from each side's perspective.
Connect TX to RXD and connect RX to TXD.
And connect ground, obviously.
Leave the VCC alone.
All the logic levels are 3.3V
It's best if the adapter works at this level, but 5V won't kill the Nook.
(As long as you leave the VCC alone.)
 
Last edited:

klemperer

Member
Mar 1, 2011
19
0
No.
The "TX" or "RX" is from each side's perspective.
Connect TX to RXD and connect RX to TXD.
And connect ground, obviously.
Leave the VCC alone.
All the logic levels are 3.3V
It's best if the adapter works at this level, but 5V won't kill the Nook.
(As long as you leave the VCC alone.)

I see, my connector works at 5V only. I will buy another one and try later.
 

Renate

Recognized Contributor / Inactive Recognized Dev
I see, my connector works at 5V only. I will buy another one and try later.

If you don't want to live dangerously, you can:

Just connect the TX out of the Nook to the RX of the adapter (and the ground too).
That way you can watch the boot up on the Nook without any fear of blowing anything up.

If you have any resistors, like 1K to 5K, you can connect the TX out of the adapter through the resistor to the RX of the Nook.
(Then you can additionally type at the Nook.)
 

klemperer

Member
Mar 1, 2011
19
0
If you don't want to live dangerously, you can:

Just connect the TX out of the Nook to the RX of the adapter (and the ground too).
That way you can watch the boot up on the Nook without any fear of blowing anything up.

If you have any resistors, like 1K to 5K, you can connect the TX out of the adapter through the resistor to the RX of the Nook.
(Then you can additionally type at the Nook.)

I tried and the output messed up, as attached. The serial port (COM3) and the bit rate were configured as the same.
 

Renate

Recognized Contributor / Inactive Recognized Dev
I tried and the output messed up...
Are you really sure that Putty is configured for 115200 baud, 8 bits, 1 stop, no parity, no flow control?
It looks like the incoming data rate is faster than Putty is reading it.

If something really strange happened it could be using 921600 (8 x 115200). You can try that.

Do you get a reasonably busy flurry of traffic continuously for a minute after power-up?
 

klemperer

Member
Mar 1, 2011
19
0
Are you really sure that Putty is configured for 115200 baud, 8 bits, 1 stop, no parity, no flow control?
It looks like the incoming data rate is faster than Putty is reading it.

If something really strange happened it could be using 921600 (8 x 115200). You can try that.

Do you get a reasonably busy flurry of traffic continuously for a minute after power-up?

The chips of my USB2UART converters are FT232RL and PL232TA (TTL). Maybe I should get an USB2RS232 converter? (Sorry, I have few knowledge on such areas)
 

Renate

Recognized Contributor / Inactive Recognized Dev
The chips of my USB2UART converters are FT232RL and PL232TA (TTL).
Well, we could get into a whole discussion about FTDI chips, fakes, performance and drivers, but that's probably not your problem.

Connect the USB adapter all by itself from TX to RX.
Twiddle some keys.
Do you see what you typed?
If you did that's good enough.

It's sometimes hard to tell which direction (too high, too low) a baud rate mismatch is just from a screen display.
It's harder to tell from a screen shot.
If I were really scratching my head I would just look at the signal with my oscilloscope and see what the baud rate is.

Are you positively sure that you're at 115200?
In Putty you can change the baud rate on the fly under Change Settings > Connection > Serial > Speed (baud).
Try 'em all.
 

peter_rong

New member
Jul 12, 2018
4
2
On 4.5 how did you get pass the Sign In screen? I can't get pass the "Error: Unable to connect to the NOOK service. Please try later." due to not a new firmware according to B&N support. I'm trying to enable USB debug mode.

Thanks in advance.

I did not encounter this problem... Maybe because I wasnt using NOOK as default launcher...? Can you somehow get to settings?
 

FerociousAndroid

Senior Member
Sep 23, 2011
267
30
Last edited:

copota

Senior Member
Jun 29, 2012
187
91
USA
Samsung Galaxy Note 20 Ultra
In FW 4.5 can't get to the NOOK settings until I sign in. Was wondering if there is a way to bypass[/url][/SIZE]

Anyone know how to root a Glow Plus that's already been updated to FW4.7?
Since Barnes and Noble disabled all the older firmware's, it appears there's no way to access the device since you can't turn on USB debugging in the current firmware's.
Is there a work around for this to get USB Debugging enabled in firmware's later than 4.7?
Any help is appreciated.


I was able to get Developer Settings in firmware 47 and 49 by going into...

All Settings > Page 2 > About > and from the About page, rapidly tap the Nook logo icon near the center top of the screen until a hidden setting page appears. From that hidden page, do the following to enable USB Debugging...

  • Tap "Android Development Settings" and then tap the USB debugging check box to select USB debugging.
  • Go back to the main Development Settings page and tap "Allow Debugging". This will enable Debugging and allow ADB access.
    ***NOTE:*** There's no confirmation that the button activated USB Debugging, so just tap it, and you can verify ADB is active by typing the "ADB devices" command from a command prompt, and it should return a message listing your device number with the word "Device" listed next to it. If it returns a message that reads "Unauthorized" then USB debugging was not activated.
I successfully rooted my Nook Glow Plus after updating to Firmware 49 by doing the following...

  • Download rootGLP-3.zip from here from here >link<. You'll need this to run ADB from a command prompt on Windows or Linux. It also has the script to root your Nook.
  • Enable USB Debugging by ticking the checkbox found in Android Development Settings (see above).
  • Once USB debugging is activated, you can run the "rootnook" script found in the rootGLP-3.zip. The script is run from a command prompt in either Windows (rootnook.cmd) or Linux (rootnook.sh).
 
Last edited:

bonchien

Member
Dec 3, 2007
34
6
The kindle app isnt great on this, the one for the Nook ST has issues with a black screen when turning pages, & the others I've tried crash occasionally.

However, if you download the book from within the kindle app, you can use AlReader (I assume others, but I've only tried AlReader) to read the downloaded book by navigating to the kindle folder from within the AlReader app.

Not ideal, but a handy workaround for those books you buy from Amazon & want to read on this.
Thanks to all who contributed to this thread. I received a refurb Nook GLP and side loaded Nova Launcher and several other apps. FWIW, the Kindle app linked in this thread seems to work without any issues on the Nook GLP: https://forum.xda-developers.com/nook-touch/general/15-mins-to-install-kindle-to-nook-t3304847 It's the only version of Kindle I've tried that worked.
 

bonchien

Member
Dec 3, 2007
34
6
When I got the NGP, I installed moon+ right away and never used nook app. I also noticed that I had to recharge the NGP daily, with backlight and wifi off. When I did some experiments moon+ was chewing through 1% battery almost every minute. It seemed worse than a full on tablet. What it's doing I have no idea, but it is an insane battery hog.

After the last update I've been using nook app. With wifi on and brightness on and at minimum, I've read ~550pg of Game of Thrones and still have 33%.
Glad I saw this. After installing MoonReader on my Nook GLP, battery went from 100% to 13% in one day with very little use. I though the battery was shot. Since uninstalling MoonReader, turning off wifi and the backlight, battery has been fairly stable, decreasing a few percent per day with about 30 minutes of use per day.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    Nook GlowLight Plus rooting script

    It's pretty simple rooting script using local exploit found here:
    retme.net/index.php/2014/10/08/vold-asec.html

    Instructions:
    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)
    4. Choose 'Continue' then 'Normal' when prompted for SuperSU binary update.

    Update: removed unnecessary reboot.
    10
    Well, I bought my Glow Plus, turned it on and it said, "Let's Get Started".
    So I did.

    The entire display is simply glued to the frame.
    You can work a knife carefully around the rim and detach the display, folding it gently to the left side.
    7
    NGP Toolkit (xposed module)

    WARNING: THIS IS NOT A STANDALONE APPLICATION, THIS IS A MODULE FOR Xposed Framework

    version: v0.9
    features:
    • (Glowlight Plus) full access to external memory (/sdcard/) from PC;
    • (Glowlight 3) access to /data/media and /sdcard partitions from PC;
    • enable/disable frontlight by home (nook) key long-press;
    • disable wake-up on usb connected/disconnected;
    • fully hide status-bar;
    • custom sleep screen with possibility to use own images;
    • disable default launcher;
    • enable default status-bar;
    • enable fast refresh mode;

    notes:
    • if you wish to use own images for custom sleep screen put them into /system/usr/sleep/custom, supported image formats - jpg, png;
    • home (nook) key long-press uses current brightness value, so if brightness is set to 0 it will do nothing;
    • status-bar requires FW version 4.7 and bnereader.apk and partner.apk installed and enabled;

    download page: https://bitbucket.org/…n-toolkit/downloads/
    7
    Yow! I could kiss B&N! :D
    Code:
    [email protected]_6sl:/ # getprop
    ...
    [ro.build.version.release]: [4.4.2]
    [ro.build.version.sdk]: [19]

    4G storage, only 512M RAM, no Bluetooth.
    7
    So, to let the cat out of the bag, getting a root console connection to the new Nook Glow Plus is quite easy.
    There is a connector location, J4, which is quite clearly labelled with the pinout.
    The output is 115200-8-N-1 on a 3.3V signal level.
    TX refers to the output of the Nook, RX is the input, connect up ground, leave the V alone.

    (Don't connect anything to this unless you understand the description above,
    it's not anything related to a 9 pin RS-232 signal without a converter.
    There are plenty of cheap USB-UART converters that run 3.3V that you can buy for $3.)

    You can:
    Code:
    setprop persist.sys.usb.config mtp,adb
    setprop sys.usb.config mtp,adb
    Then you will have (unrooted) ADB over USB, which is still useful to load things.

    Those who don't want to scuff up their new Nook would do better to wait a bit.