Hacking the new Nook GlowLight

[Kramar111]

@ Makkand
http://forum.xda-developers.com/showpost.php?p=60743883&postcount=574

 

[prestige777]

I have a couple of questions

1. Has anyone figured out how to force the B&N Partitioned Drive (f online on Windows? Windows sees the two Partitioned drives (E Sideload and (F B&N Downloads, but only one is online per the drivers used, obviously someone with greater knowledge of windows drivers should be able to easily force both drives online so that both can be used for sideloaded epubs.

2. With a rooted NGL can't the B&N Downloads Folder be accessed via File Explorer so sideloaded books can be stored there?

 

[digixmax]

...
1. Has anyone figured out how to force the B&N Partitioned Drive (f online on Windows? Windows sees the two Partitioned drives (E Sideload and (F B&N Downloads, but only one is online per the drivers used, obviously someone with greater knowledge of windows drivers should be able to easily force both drives online so that both can be used for sideloaded epubs.
...

See this XDA thread http://forum.xda-developers.com/showthread.php?t=1585572 for pointers on how to get Windows OS to see multiple partitions on a removable drive. It's not clear if this by itself is sufficient to get you access to the two partitions on the Nook EMMC (e.g., the Nook still needs to mount and made both partitions accessible over USB).

 

[StanIam]

I'm trying to setup ADB with NGL 1.3.1
I've followed all the steps and modified uRamdisk. At that point there was no Android in Device manager so I autoupdated driver for USB mass storage with 0x2080 0x0007 and Android ADB Interface appeared but B&N NOOK disappeared and NOOK drive no longer shows up when NGL is connected to PC. Omap still doesn't recognize the device.
I then updated Android ADB Interface driver with the one from bnusbdriver with no luck
Received the Nook yesterday and I'm really eager to get it to work.

 

[Renate]

I'm trying to setup ADB with NGL 1.3.1
I've followed all the steps and modified uRamdisk. At that point there was no Android in Device manager so I autoupdated driver for USB mass storage with 0x2080 0x0007 and Android ADB Interface appeared but B&N NOOK disappeared and NOOK drive no longer shows up when NGL is connected to PC. Omap still doesn't recognize the device.
I then updated Android ADB Interface driver with the one from bnusbdriver with no luck
Received the Nook yesterday and I'm really eager to get it to work.

You say "Omap" doesn't recognize the device? I'm confused.
When the Glow is booting it presents the bootloader interface, but after that it will present the ADB interface.
Does your Windows box go "bong" when you plug in your Nook?
Sometimes Windows gets confused and sees a composite device as only a single interface.
When you plug in your Nook, what changes appear to the Device Manager?

 

[StanIam]

You say "Omap" doesn't recognize the device? I'm confused.
When the Glow is booting it presents the bootloader interface, but after that it will present the ADB interface.
Does your Windows box go "bong" when you plug in your Nook?
Sometimes Windows gets confused and sees a composite device as only a single interface.
When you plug in your Nook, what changes appear to the Device Manager?

Thank you for the answer and sorry for delay.
As I said, Android ADB Interface appeared in Device manager and I no longer had access to NOOK drive. So I restored Windows to the point before the changes made to drivers, booted Ubuntu and followed Linux tutorial presented on this forum and everything worked.
Thank you again for your work and manuals.

 

[cmetz]

root adb enable = bootloop

I tried to root a BNRV500 running 1.3.1 with the kit ng2-root-prurigrofork-2014-05-20. Booting the device with cwm worked fine and I was able to image it.

Unfortunately, if I do all the steps, or if I only do 12-enable_adb.sh, I get the same result. I shows the bootanimation, then reboots. I am able to adb in, and logcat shows that the dalvik VM is unable to start up:

E/dalvikvm-gc( 798): Could not create 700416-byte ashmem mark stack: Permission denied
E/dalvikvm-heap( 798): dvmHeapBeginMarkStep failed; aborting
E/dalvikvm( 798): VM aborting

It looks from logcat like that tries and fails a bunch of times, then the system reboots. After that fails a bunch of times to fix the problem, the system goes into auto-recovery and restores itself.

Could anyone offer any suggestions on how to fix or debug this problem?

 

[Becky2719]

I have a nook glow , please can someone give me the easiets way to root this please . I am not very clever on a compluter so please be kind haha

 

[Greenstuff4]

Hi Renate, you seem to be the expert on the NGL. I need help.

A short recap of how to root the new NG2:

All of these methods use the Texas Instruments OMAP processor USB bootloader.

The desktop system that you connect the Nook to can be either Linux or Windows.
This only details the Windows method.

The bootloaded system can be either noogie or Clockwork Mod or a modified stock Nook.
For now, we are only using the noogie method.

The bootloading sequence can be either aboot, u-boot or x-loader, u-boot.
For now, we are only using the aboot, u-boot method.

Preparation
In Window, we need drivers to communicate with all USB devices.
The bnusbdriver.zip attached below is the modified stock driver.
Unzip it and when installing or re-installing select this driver manually.
Manually means saying, "No, I will select" until you get down to "Have disk" and select the specific directory.
The driver info is unsigned, although the drivers themselves are stock Windows.

Collect the necessary files.
omaplink.exe can be found in the signature below.
The four files can be downloaded here: http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285

Booting
Fully power your Nook down with the USB disconnected.
Run this command on the PC.

omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie

Plug the USB into the Nook.
Whenever a "New Device" popup appears manually select android_winusb.inf to be loaded then start this step over.
omaplink should get as far as "Waiting for ADB..."
It won't find it just yet, use ^C to exit.
At this point there should be a new removable disk mounted with a dozen files on it, including uRamdisk

Rooting
Follow the directions here for modifying uRamdisk http://forum.xda-developers.com/showthread.php?p=49070213#post49070213
Reboot to a rooted Nook with ADB over USB access

Hi Renate,
I would like to root my Nook Glowlight 2013. The problem I'm having is that I'm not sure how to change to drivers to to the bnusbdriver.zip. I plugged in my device several times, so it already has the stock drivers setup. The thing is, when I go into regedit to delete the keys for the bootloader, there not there. I'm completely stuck. I was hoping you had some words of wisdom.
Thanks in advanced!

 

[Renate]

I was hoping you had some words of wisdom.

Try downloading the latest omaplink.exe from the signature.
The old aboot.bin and u-boot12.bin should be fine.
I think there are some old system images hanging around for CWM or Noogie.

The biggest problem in the Windows 10 world is getting all the drivers installed and working.
You shouldn't need to delete anything from the registry?
omaplink.exe is pretty good at identifying which interface your Nook is presenting.
You can use it without any arguments (just "omaplink") to see.

The OMAP bootloader, fastboot and adb all use WinUsb bulk transfers, so it's all the same driver actually.

Oops, sorry @Becky2719 I didn't notice your post.

 

[ylmir]

I know this is an old thread, so I'm sorry to resurrect it, but I keep running into the driver issue trying to use the android_winusb.inf driver in Win10. I keep getting an error message that the directory does not contain a compatible driver, and to make sure the file is compatible with 64-bit systems. Is there something I am missing, or is that just a hang-up right now. I guess I could try and figure out Linux, but at this point all I really want to do is change the partition size to let me sideload more content. I would really appreciate your help @Renate NST

 

[Renate]

I keep getting an error message that the directory does not contain a compatible driver, and to make sure the file is compatible with 64-bit systems.

Are you using the stock Android stuff in extras\google\usb_driver\android_winusb.inf?
Do the two directories exist amd64, i386?

You need to have an .inf file with the Nook stuff in it.
I've just modified my own, but then it's unsigned and you have to go through the process of restart installing unsigned drivers once.

; Nook Glowlight 2
%SingleAdbInterface%         = USB_Install, USB\VID_2080&PID_000A
%CompositeAdbInterface%      = USB_Install, USB\VID_2080&PID_000A&MI_01

 

[ylmir]

Are you using the stock Android stuff in extras\google\usb_driver\android_winusb.inf?
Do the two directories exist amd64, i386?

You need to have an .inf file with the Nook stuff in it.
I've just modified my own, but then it's unsigned and you have to go through the process of restart installing unsigned drivers once.

; Nook Glowlight 2
%SingleAdbInterface%         = USB_Install, USB\VID_2080&PID_000A
%CompositeAdbInterface%      = USB_Install, USB\VID_2080&PID_000A&MI_01

Yes, I have tried the bnusbdriver file that was posted here, which has both the amd64 and i386 directories and the modified .inf file that includes my device, and I have also tried a newer version (ver. 11 instead of 8), with those lines added that you posted above. I am in a boot mode that lets me install unsigned drivers. Neither of them worked in device manager.

One thought: My nook is listed in the Device Manager under both "Portable Devices" and "disk drives," but not under Android devices. I tested the inf by updating the driver for "Android Bootloader Interface" under "Android Devices," and it seemed to be compatible, though I did not finish the installation just in case. Should I update that drier instead (Android Bootloader) or try something else?

 

[Renate]

My nook is listed in the Device Manager under both "Portable Devices" and "disk drives,"

Oh, that means that you have the USB on your Glow set to UMS (USB Mass Storage) and either PTP or MTP, but no ADB.

Did you enable "USB debugging" in "Developer Settings"?

There are tons of ways to check what you have, including usbview.exe

You could also download my imxlink.exe (in the sign) and just run it to see the little indicators.

C:\>imxlink.exe

If you have a terminal application you can:

# getprop|grep usb
[persist.sys.usb.config]: [adb]
[sys.usb.config]: [adb]
[sys.usb.state]: [adb]

You can have other things in there but it has to say adb.

 

[ylmir]

Oh, that means that you have the USB on your Glow set to UMS (USB Mass Storage) and either PTP or MTP, but no ADB.

Did you enable "USB debugging" in "Developer Settings"?

There are tons of ways to check what you have, including usbview.exe

You could also download my imxlink.exe (in the sign) and just run it to see the little indicators.

C:\>imxlink.exe

If you have a terminal application you can:

# getprop|grep usb
[persist.sys.usb.config]: [adb]
[sys.usb.config]: [adb]
[sys.usb.state]: [adb]

You can have other things in there but it has to say adb.

Hmmm...

I have the original Nook Glowlight (BNRV500, white, not NST or Glow Plus, just Nook Glowlight). I have not been able to find where to go to enable Dev settings in the first place, since it doesn't have the setup that earlier and later devices have had.
I wonder if that is why other posters (for example: here) mention that you need to catch the device in Device Manager very quickly, before it is fully recognized, in order to force installing the modified USB drivers. I'm not sure.

 

[Renate]

I have the original Nook Glowlight (BNRV500, white, not NST or Glow Plus, just Nook Glowlight).

Oops, my error.
So is your Glow1 is completely unmodified? Unrooted?

Yes, that thread you linked is one way to root it without an exploit.

That stuff with the registry in the first post is not necessary.
You need to "show hidden devices" in Device Manager, find the bootloader and install the drivers.
OmapLink is still in the sig, as well as ImgUtil (which replaces the old BootUtil).
You can also go up from the sig link and down to "Windows Related" for enumusb.exe and usblog.exe

C:\>enumusb /l /v0451
0451:CAFE     2b6e00029edc000     2021-02-03 16:06  OMAP Fastboot
0451:D00E     7&279c4dc7&1&7      2021-01-11 11:44  OMAP Bootloader

(Yours won't have the pretty names like mine, but should have D00E, CAFE)