Root for Glowlight 4 Plus?

[elteber]

Originally Posted by elteber

In the next thread I found out the code to access the developer mode, here it is: “NOOK-BNRV1300” (without quotes). And recently James Scholz released a video with detailed instruction of getting root rights. I'm thinking of flashing the reader using this instruction.

sorry for the duplicate

[scientifically]

Wondering if anyone has been successful at rooting the GL4+ here. I've enabled developer options and installed several reader and other apps through adb. I've attempted a couple of times to root the device via a patched Magisk boot image but each time after sending the adb reboot bootloader command (via Windows 10, only option) the device just freezes and I have to reboot by long pressing/repeatedly pressing the power button. I noticed in many of the rooting guides that enabling oem unlocking in developer options was not mentioned, but I have done this. Perhaps I am missing or overlooking something? Any help or guidance is appreciated!

[Renate]

Originally Posted by scientifically

.. but each time after sending the adb reboot bootloader command (via Windows 10, only option) the device just freezes ...

The bootloader is not very demonstrative, it won't say, "I love you". You can only tell that it's there if you have fastboot running and the Windows driver installed correctly.

C:\>fastboot devices
fastbooot 12345678

[scientifically]

Thank you -- I have used the adb and fastboot tool on the same computer to root a couple of android phones in the past and recently so I believe the set-up is good. Adb devices will show the Nook device, but I've tried fastboot devices but nothing shows up and the same behavior happens -- the device freezes and needs to be rebooted. I can't seem to actually get it into fastboot mode for some reason.

[scientifically]

Still wondering if anyone here has been able to root this device -- specifically if downeaster59 or elteber have been successful. Despite many attempts I've not been able to get into fastboot mode. I can install apk files via adb and adb devices shows my device but after command adb reboot bootloader there is no activity and fastboot devices shows nothing with the device frozen and requiring a hard reboot. Once again, I appreciate the feedback!

[Renate]

You have to check if there is some USB presence after you "adb reboot bootloader".
Does pulling the USB cable and re-plugging it cause Windows to "bong"?
Can you find anything new in Device Manager (devmgmt.msc)?

[scientifically]

I have run into a new snag. Two nights ago I upgraded the firmware to version 8.1.7.38 (from 8.1.7.15 I believe) and now, after I downloaded and unzipped the firmware and transferred the boot.img file to the device, when I try to select and patch the file in Magisk nothing happens. The file manager will open to select the file but when it is tapped to select it the screen just takes me back to the select and patch a file page in Magisk and not patching is done. I had previously successfully selected and patched the boot.img file with version 8.1.7.15 so I am not sure why I am having trouble now. I uninstalled and reinstalled Magisk but still had the same result. I may now try to downgrade the firmware to attempt root again or perhaps some more research will reveal the cause of the current problem. The quest continues . . .

[Renate]

I've always found the file selection on Magisk non-intuitive and balky.
Moreover, the "Let's Go!" doesn't even say where it's going.

[aikiharp]

Originally Posted by downeaster59

Thanks for your comments! The problem is that I cannot get adb to work at all. Nothing comes up when I try "adb devices". The display has remained frozen and does not change when I try to turn the device on or off.

This is very odd. Once, I messed up on my GL 4 by flashing the boot.img from the wrong update. The display went completely blank after that, but I could still access adb. With the GL4+ now, I can't. It's like everything is frozen. Only the light near the USB-C port responds when I connect it to a power source.

Did you figure this out? I did essentially the same thing (flashed rooted boot image) and the GL4+ is unresponsive. I'm now trying hardware key combos to see if I can get to recovery.

[aikiharp]

Originally Posted by aikiharp

Did you figure this out? I did essentially the same thing (flashed rooted boot image) and the GL4+ is unresponsive. I'm now trying hardware key combos to see if I can get to recovery.

I found that pressing power and the lower left page turn key can get me to recovery, where the factory reset option appears. If I choose to reset it by pushing N (home), the Nook starts the "Your Nook is updating" process. Unfortunately, it gets stuck there--the progress bar gets to 100% and sits there. I have a feeling the Magisk-modified boot.img is making it unable to complete the wipe. Pushing power to abort/boot normally doesn't have any effect. While it's in recovery I can't detect it by USB, so ADB/Fastboot commands aren't available.

Sigh.