New Nook Glowlight 4?

[halfsat]

Even better! Just tried again using the newest link and I was able to successfully get this rooted with no trouble at all.

Anyone else considering rooting: Learn from my mistakes, be careful about making sure you have the right update.zip downloaded and you'll save yourself from some major headaches. It's so obvious in hindsight, but easy to forget when you're in the moment.

[nick84]

Wouldn't mind a step by step guide on how to root GL4.

[halfsat]

I followed downeaster59's instructions (post #391 on page 27) a couple of weeks ago and that still worked perfectly. I only ran into trouble because I didn't download an update.zip file (step 1) that matched what was already on my 4e. So just check your firmware version first and then make sure to download the update.zip that will have the boot.img that matches your current firmware.

[nick84]

I would welcome any suggestion to help resolve battery issue. While using android launcher (I tried number of them - Nova, Niagara, ReLauchX, E-ink Launcher) the battery goes down from 100% to nearly 0% within 1 hour of just reading on Koreader. It may be 1,5 if I turn the light off.

It works fine when using nook stock reader and I can read 3, 4 books at one charge so it's not the battery itself. It's something to do with a android launcher.

Has anyone had the same issue?

[halfsat]

I use mLauncher - https://github.com/DroidWorksStudio/mLauncher
And then I have this energy saving patch in KOReader - https://github.com/Codereamp/nopowen
In addition, I also followed that person's advice to install Kernel Adiutor and set the CPU to interactive.

I thought my GL4e's battery life was surprisingly low when using the stock software (compared to battery life on my old NST and NGL), but it's been better for me now after making these changes. Just for context, I almost never use my light and wifi is basically always off.

[nick84]

Thanks. Done the first bit - adding patch. The second one requires root so not an option to me. Will charge the device to full and see if there is any improvement.

Thanks again.

[halfsat]

My GL4e is getting close to where I need to charge it, so I figured I'd share my battery stats (from KOReader). Meant to do this before the last charge, but I totally forgot.

Current: 32%

Awake since last charge

• Total time: 17:00
• Consumed: 56%
• Change per hour: 3.29%

Sleeping since last charge

• Total time: 13d15:35
• Consumed: 9%
• Change per hour: 0.03%

Since last charge

• Total time: 14d08:35
• Consumed: 64%
• Change per hour: 0.19%

I've read/made progress on three separate books during this charge. At a very rough estimate, I'd guess that it's been around 1000 pages or so. Now that I'm typing this up, I kind of wish that KOReader included the number of page turns in the battery stats.

This is on my Nook GL4e. My frontlight, wifi, and bluetooth are all always turned off. I only use KOReader (and pretty much never even exit out of the app). I have that energy saving patch enabled and my Nook is rooted (with Kernel Adiutor installed in order to set CPU as interactive). Other than that, I have very few other apps installed (mLauncher, Magisk, KOReader, Kernel Adiutor).

Overall, I'm decently happy with this battery life. I still feel like it was better on my old Nooks, but I tend to get about two weeks out of a charge and that's not too bad for me.

[rushium]

Originally Posted by halfsat

I was going to give this a try on my Nook GL 4e last night, but I ran into some trouble at step 11. Fastboot didn't seem to be doing anything in the terminal on my Mac. It got stuck on <waiting for devices>. When I ran fast boot devices, nothing happened. I'm thinking this might just be an issue with drivers or something, so I might try it on another machine tonight, but I'm curious if anyone has any ideas as I've seen this same issue mentioned before.

I'm having the same issue!
While trying to root my Nook GL 4 [using these instructions], everything goes great until I have to flash the magisk-patched boot.img file back to my device. My GL 4 freezes after sending "adb reboot bootloader" and when I type "fastboot flash boot file name", it says <waiting for devices>.

My GL 4 is on the latest update, and I've made sure twice I'm using that firmware boot.img file with information from here. I tried several times and nothing seems to be working!

If anybody has a solution, or has gone through this before, I would love any and all information.

[Renate]

Originally Posted by rushium

My GL 4 freezes after sending "adb reboot bootloader"...

The bootloader (fastboot) doesn't manifest itself on the screen so you won't know if it's frozen or just waiting for you.

"adb reboot bootloader". Then pull and insert the USB cable. Does your computer take any notice? Does it appear that something live is there? Go to Device Manager (devmgmt.msc) and look for something. Do you have the "Google USB driver"?

If you're on Linux, "lsusb".

[rushium]

Originally Posted by Renate

"adb reboot bootloader". Then pull and insert the USB cable. Does your computer take any notice? Does it appear that something live is there? Go to Device Manager (devmgmt.msc) and look for something. Do you have the "Google USB driver"?

If you're on Linux, "lsusb".

I'm using OS X.. which might not be ideal but I don't have access to another machine.
My computer recognizes the device up until I do "adb reboot bootloader", but it doesn't take any notice after that, even when pulling and reconnecting the cable.

[Renate]

That's very strange. Did an update completely kill the bootloader? Or is your abl mangled?

Eh, we don't need no stinkin' bootloader. Have you tried EDL? You're stuck with the Python one, but you can use the Firehose loaders as directed in my sig.

[halfsat]

This is not going to be much help and I'm not an expert so I don't have any explanation (although I'm sure there must be one), but I was never able to get the Fastboot commands to work from the Terminal on my Mac either. It worked without any trouble on a Win10 machine though.

ADB commands all work perfectly on my Mac, so it really was just the actual process of rooting that required me to use Win10, but since then I've been able to do everything else straight from my Mac.

I've never used EDL, so I'll be curious to hear how that goes.

[rushium]

Originally Posted by Renate

That's very strange. Did an update completely kill the bootloader? Or is your abl mangled?

Eh, we don't need no stinkin' bootloader. Have you tried EDL? You're stuck with the Python one, but you can use the Firehose loaders as directed in my sig.

sweet! thanks for your help!
forgive my lack of knowledge, but i'm not quite sure where to begin with that; how do i get my gl4 in edl? what then? also i can't seem to find your sig lol

[rushium]

Originally Posted by halfsat

This is not going to be much help and I'm not an expert so I don't have any explanation (although I'm sure there must be one), but I was never able to get the Fastboot commands to work from the Terminal on my Mac either. It worked without any trouble on a Win10 machine though.

ADB commands all work perfectly on my Mac, so it really was just the actual process of rooting that required me to use Win10, but since then I've been able to do everything else straight from my Mac.

I've never used EDL, so I'll be curious to hear how that goes.

your posts were helpful! i might just be better off trying to get access to a windows device...

[Solitaire1]

I just purchased a Nook Glowlight 4 (NG4) and I've been pleased with it. It is a replacement for my aging NookColor (which I've found out is no longer going to be supported) and my Lenovo Nook 9 Inch Tablet (which is a good tablet but not that good as an e-book reader). I like that the NG4 is just an ebook reader, rather than just being one application among many like in my Nook 9 Inch Tablet.