New Nook Glowlight 4?

[Renate]

Oh, just to add a bit to my previous post about the silly lights.
In the non-partitioned part of mmcblk0 at block offset 1030, 19 blocks is 30 lookup tables for LEDs.
Since they are all for different models only one table is actually used.
There is a non-linear conversion in the kernel before the lookup table which apparently has a bug as we can see the non-monotonic glitch in the final result.
So we have a non-linear conversion to a non-linear lookup table just to generate a linear sequence to drive a chip that properly understands exponential conversion.
Sheesh.

This is the raw lookup table. With the non-linear conversion it becomes the blue line in the previous post.

[MrBryan]

I followed the rooting instructions verbatim and I got the same issue a previous poster had.

When I get to "adb reboot bootloader" the backlight just turns off on the Nook and it ceases to respond. Holding power for 10 seconds gets a reboot.


I'm on OS X, i installed android-platform-tools.

When i hit 'adb devices' I get:

List of devices attached
5014610072485003 device

Should that have an exclamation mark to indicate I have drivers, is that what I'm to understand?

Looking elsewhere I see that there might be issues with getting a fastboot driver to work on OSX?

https://forum.xda-developers.com/t/n...4363453/page-3

[MrBryan]

Just to clarify where I'm at in my last post: i was able to transfer apps onto this, and install magisk and patch the bootloader, and get said patched boot.img onto my mac. But can't issue the "adb reboot bootloader" command (or the subsequent command just fails anyhow : )

fastboot flash boot magisk_patched-24200_wziur.img
< waiting for any device >


Thanks so much for posting your own progress so i could try, anyhow.

[Renate]

I'm better at Linux than OS X.
If "adb devices" shows you something then you're all set.
If "fastboot devices" shows you something then you're all set.
ADB or fastboot saying "Waiting for device" means it can't detect it.
Use "lsusb" or "lsusb -v" to see what you've got.
2080/000d is ADB
18d1/d00d is fastboot

[MrBryan]

Seems it does make that to become present, but fastboot does not recognize the device somehow

After "adb reboot bootloader"

lsusb (it's not a native app on Mac, had to install from brew):


Bus 020 Device 049: ID 1f3a:1010 1f3a USB Developer Serial: Android Fastboot


lsusb -v:

USB Developer:

Product ID: 0x1010
Vendor ID: 0x1f3a
Version: 2.00
Serial Number: Android Fastboot
Speed: Up to 480 Mb/s
Manufacturer: Android Bootloader Interface
Location ID: 0x14230000 / 49
Current Available (mA): 500
Extra Operating Current (mA): 0



Before:

Lsusb before fastboot command:


Bus 020 Device 048: ID 2080:000d 2080 BNRV1100 Serial: 5014610072485003


lsusb -v

BNRV1100:

Product ID: 0x000d
Vendor ID: 0x2080
Version: 4.09
Serial Number: 5014610072485003
Speed: Up to 480 Mb/s
Manufacturer: BarnesAndNoble
Location ID: 0x14230000 / 48
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

[Renate]

Oops, my bad.
Most things use Google's 18d1/d00d, this uses Allwinner's non-standard 1f3a/1010
Have you got the latest fastboot? They might have fixed it.
If you have some Windows thing, that would be a solution too.

[MrBryan]

does having the latest fastboot just entail getting the latest executable?

I just fetched a fresh copy of the platform tools tarball which has fastboot... no difference

https://developer.android.com/studio...platform-tools

./fastboot devices

returns nothing when that device id is showing in lsusb

[MrBryan]

Tried another approach specifying the serial device since fastboot gives that option


Figured out what that device path was from this method

https://stackoverflow.com/questions/...ding-on-mac-os


and ... still no dice:



% fastboot -s /dev/ttys010 flash boot Downloads/magisk_patched-24200_wziur.img

< waiting for /dev/ttys010 >

[MrBryan]

Also tried a windows7 VM and I can assign the USB device to it just fine, it tries and fails to find a driver for the fastboot USB device even after installing the "Minimal ADB and Fastboot" package and if you try to search for a new driver there is no 'android device' or similar class to choose from.

I suppose if I had a known working driver file handy I could do 'have disk" and point to it.

[MrBryan]

[Renate]

Here you go. Rename this driver.inf and put this in the same directory as android_winusb.inf
Select it, but you'll have to install it as an unsigned driver.
(It's just the same gobble-dee-gook with 1f3a/1010 added.)

[MrBryan]

thanks so much!

that got the device recognized in windows... but alas, the command fails for some reason:

C:\Users\IEUser\Desktop\platform-tools_r33.0.3-windows\platform-tools>fast
s "Android Fastboot" flash boot magisk_patched-24200_wziur.img

Warning: skip copying boot image avb footer (boot partition size: 0, boot size: 17901568).
Sending 'boot' (17482 KB) FAILED (Write to device (Unknown error))
fastboot: error: Command failed


Now I'm afraid to reboot the device in case it's bricked...

NOTE: the minimal adb version didn't even get that far, I read elsewhere getting a newer version of the platform tools is necessary for newer devices:

https://dl.google.com/android/reposi...st-windows.zip

[Renate]

Hmm, that's strange. Did you try the command again? It might have been USB communication error. Still, "Unknown error" is pretty cheesy.
Magisk does put AVB sig on the end. I'm not sure who/what pays attention.

Just for fun, download imgutil.exe and

C:\>imgutil /v magisk-whatever.img

[MrBryan]

Haven't tried that yet... but, I added a USB hub in between the USB C -> USB connection on my mac and.... it worked!

I read elsewhere some devices can be picky like that.

PS to reboot you need 'fastboot reboot' since it's still in that mode (to clarify the instructions post on page 27)

[MrBryan]

My plan now is to try the twrp recovery:

https://github.com/Ryogo-Z/nook_gentoo_twrp/releases

then install xposed.. and see if this module still works which enabled a2 mode on GL3 and others:

https://www.mobileread.com/forums/sh...d.php?t=285684

Poll: will i regret this