Root for Glowlight 4 Plus?

[plainbriny]

Originally Posted by brevew

I do not want to login with an account again or setup wifi. I want to root it from this screen and install my own launcher.

Is that possible? I tried tapping top left and right corner and that didn't do anything. I read somewhere else to hold all buttons plus power button and then plug in usb and that didn't do anything. Hoping for some guidance. Thanks.

That's possible, you have to alternatively tap top left and right corners several times, not just once.

[brevew]

Originally Posted by plainbriny

That's possible, you have to alternatively tap top left and right corners several times, not just once.

Thank you this worked but now I have another issue.

Everything was going smoothly until I made it to step 8. When I typed adb reboot bootloader and hit Enter, my Nook screen instantly went dim and froze. It was frozen for a while and I was mashing all the buttons trying to make it do something until a factory reset screen came. I did a factory reset and it's back to where I started.

I used the correct version of magisk so I don't think the issue is there. My only guess is that my problem is from Step 4 adb push boot.img /sdcard/ (extracted from update.zip for matching version, 8.1.7.109).

I haven't updated my Nook in a while so here where you say 'matching version', does that mean the version currently installed on my Nook? In which case I don't think I have version 8.1.7.109 installed. How can I check?

Sorry if these are stupid questions. I have no idea what I'm doing but it's fun learning this stuff.

[plainbriny]

Originally Posted by brevew

Everything was going smoothly until I made it to step 8. When I typed adb reboot bootloader and hit Enter, my Nook screen instantly went dim and froze.

This is normal, "adb reboot bootloader" makes nook entering fastboot, so that you can flash the boot.img to the device. While in fastboot, the device will become non-responsive, but you can perform fastboot actions in the following steps.

Matching version of your nook and the boot image is important. You need to know the firmware version of your nook (on the welcome screen, holding lower left and right cornors will show the version), and use the boot.img from the same version.

Fortunately you stopped at step 8, otherwise the mismatched boot image might brick the device.

[brevew]

Originally Posted by plainbriny

This is normal, "adb reboot bootloader" makes nook entering fastboot, so that you can flash the boot.img to the device. While in fastboot, the device will become non-responsive, but you can perform fastboot actions in the following steps.

Matching version of your nook and the boot image is important. You need to know the firmware version of your nook (on the welcome screen, holding lower left and right cornors will show the version), and use the boot.img from the same version.

Fortunately you stopped at step 8, otherwise the mismatched boot image might brick the device.

I held the bottom corners and found out I have version 8.1.7.50. I downloaded the update.zip here - http://su.barnesandnoble.com/nook/pi....50/update.zip

Went back into the adb terminal to try again. Got to Step 8 again, typed adb reboot bootloader and again the screen went dim. Ok no problem.

Typed fastboot devices hit Enter. Nothing changed I figured it was fine.

Tried the last step to flash the new patched boot.img from/sdcard/Download/magisk_patched-24000_JMBNg.img and my terminal says <waiting for any device>

I couldn't type anything and it was waiting and waiting forever. After like 5 minutes I closed it and unplugged the device. It was frozen again for a while but I was able to factory reset it again. Was I supposed to just keep waiting?

[brevew]

Sorry just re-reading the instructions. I now realize I was supposed to make sure it was in fastboot mode when I typed in fastboot devices. Since nothing appeared after, it clearly was not in fastboot mode so that's where I'm stuck.

[Renate]

"fastboot devices" has to show that there are devices.

fastboot devices
12345678

You need to have a loader for fastboot.

[brevew]

Originally Posted by Renate

"fastboot devices" has to show that there are devices.

fastboot devices
12345678

You need to have a loader for fastboot.

Could you explain what you mean by that? How do I get a loader for fastboot?

[Renate]

Well, you remember with "Google extras" how you installed the driver for ADB?
It's the same, but different.

[spectralrainbows]

Originally Posted by tombert

It is not!

If you just want to install an Android launcher, you can install one with adb, but you need a way to "launch the launcher". You can do this with adb as well but that would require you to hook it up to a computer which would be kind of lame.

I wrote an app that overrides the top left button to launch Simple App Launcher, which can then launch anything you sideloaded, which is fine if that's all you want. No root required: https://github.com/Tombert/StupidLauncher

This Glowlight is actually for my wife, and she wanted custom sleep screens, and if you want that then you *do* need to root it.

BTW I am not an Android developer, this was an ad-hoc thing I wrote to get stuff working. If anyone here has Android dev experience I encourage you to make a pull request to clean up my crappy code.

I just wanted to ask how you went about doing the custom sleep screens? I understand the rooting process but what did you do after that?

[Renate]

Originally Posted by tombert

If you just want to install an Android launcher, you can install one with adb, but you need a way to "launch the launcher".

You shouldn't have to.

A "home" app or "launcher" app is simply one that responds to the HOME intent:

      <intent-filter>
        <action android:name="android.intent.action.MAIN"/>
        <category android:name="android.intent.category.HOME"/>
        <category android:name="android.intent.category.LAUNCHER"/>
        <category android:name="android.intent.category.DEFAULT"/>
      </intent-filter>

When you have multiple apps that do that the system should ask you which one to use.

[TheAndroidx]

Hello I'm here but I am successfully follow the guide and rooted my nook and I'm using koreader and mihon, however in koreader while reading I will get a message randomly saying external storage has stopped but nothing is wrong and I can just continue reading, however in mihon when downloading chapters it would constantly give me the pop-up saying external storage has stopped and if I dismiss it it pops back again and if I do it enough it crashes the app if I don't press away everything downloads fine. Has anyone else encountered this issue?