Full Root for Nook Glowlight

[lenavel]

Can't root my Nook Glowlight

I'm new in the forum and I need some help with my Nook Glowlight.
It drains the battery in five hours. It also freezes all the time when it goes to sleep. I've tried everything: new battery, turning off, hard reset, update software, erase & deregister...

When I turn it off or try hard reset, it freezes instantanely and stops working. When it happens, I have to wait at least two days to put it on charging.
I manually installed the software update 1.3.1, it didn't fix the problem. Next step was erase & deregister, it was succesfully, but my Nook continues working bad.

I read in this forum that rooting the Nook might be helpful. I read carefully all the thread, but the problem is running omaplink, cause then I have to connect my Nook completely turned off, and when I turned it off it stops working, so I can't continue.

Maybe somebody have any idea? Any help would be appreciated.

 

[Renate]

Can you boot it on Noogie on an SD card and make a full (2 gig) backup?

Does an adb reboot work while connected to power on USB?

You can try using UsbMode.apk and letting it die. The screen it freezes on will show battery voltage and percentage.
Does UsbMode.apk indicate realistic temperatures (68F and not 30F or 110F)?
Are you sure that the replacement battery is the correct one?

 

[lenavel]

Thanks for all your instructions, Renate NST!

I bought the replacement battery on Amazon. It's an X-Longer, model No. CS-BNR003SL, Lithium Polymer, 3.7 VDC, Part No.DRNK03, S11ND018A. Both batteries, the new one and the original, seem to have the same problem, that's why I thought the problem was not the battery.

I know nothing about rooting, just need to fix my NGL. That's why probably I'm asking something it is obvious.

Finally, I did the complete root, just needed to let it die every time it was neccesary to reboot, and then wait patiently for the moment it began to charge again and restart. Already install superuser.apk, but I think now I need to install ADWlauncher.apk for apps to run ??

Anyway, the problem with power off remains, so i will try your suggestion about using USbmode.apk. I don't know what do I have to do: Install USB.apk using ADB??

 

[ashgk98]

resizing nook partitions

Thanks for the help, I've got it now. I guess I was more successful with it then I thought I was. I just needed to run it in noogie mode before connecting to it with gParted. I was able to do partitions without issue. I think what worked best for me was to delete the last four partitions, and then re-create them with the exact names and in the correct order. I created the NOOK partition as fat32 with over 2GB of space.

I still have a question that maybe someone here can answer.
What is the purpose of "cache" "reserve" and "userdata" ?
I understand that "userdata" is where Barnes & Noble books are stored, and probably some of the account information as well. Does it store information such as shelves that I create, or some other useful info?
I've shrank these three partitions to around 200MB each, and I just want to know if I will have an issue later on from doing that, or if maybe I didn't need to leave those as much space as I did. Just to mention, I plan to store loads and loads of ebooks on the device, and just use it for that purpose, no extra apps, no special modding.

Thank you for your time.

@Mythra13, even I am interested in resizing the partitions, but how to run the NGL in noogie mode?
thanks

 

[ZenM]

adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/

and then in terminal emulator under 'Preferences' change the initial command to

export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;

and finally

adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit

nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.

Hi
1º Thanks a lot.
2º May I ask you to elaborate on profile and .bashrc files, no alias seam to be executed and when I try to use nano from adb shell I get "Error opening terminal: unknown".

I hunted all the way to the MoDaCo forum but I didn't find a clear explanation.

 

[unaunu]

mounting problem

I tried on Windows 7, 64 bit

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

My Nook was off, and I pluged it in my PC, all was ok until it stopped at the line
Waiting for ADB...
The Nook halted. But the PC was able to read the NOOK drive to get the uRamdisk. So I continued to edit the uRamdisk. Then, I restart the Nook.

Connecting the Nook by wifi was ok. But at the command:
adb shell mount -o remount, rw /system
It responded
mount: Operation not permitted

Could anyone help me?

Thanks in advance

 

[Becky2719]

Ngl

I tried on Windows 7, 64 bit

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

My Nook was off, and I pluged it in my PC, all was ok until it stopped at the line
Waiting for ADB...
The Nook halted. But the PC was able to read the NOOK drive to get the uRamdisk. So I continued to edit the uRamdisk. Then, I restart the Nook.

Connecting the Nook by wifi was ok. But at the command:
adb shell mount -o remount, rw /system
It responded
mount: Operation not permitted

Could anyone help me?

Thanks in advance

Please can you help me. I am trying to root my nook glowlight. Please can you give me a simple step by step instruction as to how to root the nook.


Many thanks

 

[Renate]

Please can you give me a simple step by step instruction as to how to root the nook.

Mmm, that was what this whole thread was trying to do.
Like most threads it just grew out of control obscuring things.
This thread is about the Nook Simple Touch and the original black Nook Glowlight.
If you have a white Glowlight Plus or a black Glowlight 3, you are in the wrong place.

The Nook Simple Touch had an SD card, so the simplest route is through Noogie on an SD card.

The original Nook Glowlight did not have an SD card so the method here is the way to do it without an exploit.

The OmapLink method works on Windows.
With Windows you need to get drivers working for 3 different interfaces.
It's kind of a pain and it's gotten worse since Windows 10.

Do you have ADB working? That's the first step.
Then you need to get fastboot working.
Then you need to get the bootloader working.

I don't have a Nook Glowlight. I only have a few NST, a Glow2 and a Glow3.
I just tried to refresh my memory by doing OmapLink on it, but I have to plow my way through unsigned drivers.
Which means that I have to reboot. Which means this is the end of this particular post for now.

 

[Renate]

Hmm, the whole USB situation on Windows gets worse and worse.
The bootloader interface pops up for only a few seconds and you have to grab it.
My Windows 10 seems unable to do that.

My $5 Raspberry Pi Zero gets it fine:

[ 1027.250822] usb 1-1: New USB device found, idVendor=0451, idProduct=d00e
[ 1027.250848] usb 1-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0
[ 1027.250856] usb 1-1: Product: OMAP3630
[ 1027.250863] usb 1-1: Manufacturer: Texas Instruments
[color=red][i]Note that three seconds elapses.[/i][/color]
[ 1030.330162] usb 1-1: USB disconnect, device number 4

I'll work on this.

 

[stryker9]

Hmm, the whole USB situation on Windows gets worse and worse.
The bootloader interface pops up for only a few seconds and you have to grab it.
My Windows 10 seems unable to do that.

My $5 Raspberry Pi Zero gets it fine..
I'll work on this.

Dear @Renate NST..
I have been at this for over a month now - trying to follow every instruction (highly fragmented and spread out all over the forum) to the t. The fact that I've failed to even brick the device must say something about how incapable I am Win10 is - in connecting to the innards of my BNRV500 (v1.3.2). There is no way to update the driver, not this, and therefore not even this works.

There is no response from omaplink, it just says '3 removable disks' and nothing else.
The ADB server is off; etc. The NOOK starts up super-quick, on being connected.

My main purpose is to reorganize the partitions and sideload a couple of apps, so I am willing to try things on a Linux VirtualBox - if you'll kindly help.
Next, I'm gonna try the ZeroLab method (mod by @Kramar111) here. Wish me luck; will report any success/failure here.

Plus, my device info:

Device Descriptor:
bcdUSB:             0x0210
bDeviceClass:         0xFF
bDeviceSubClass:      0xFF
bDeviceProtocol:      0xFF
bMaxPacketSize0:      0x40 (64)
idVendor:           0x0451 (Texas Instruments)
idProduct:          0xD00E
bcdDevice:          0x0000
iManufacturer:        0x21
iProduct:             0x25
iSerialNumber:        0x00
bNumConfigurations:   0x01

ConnectionStatus: DeviceFailedEnumeration
Current Config Value: 0x00
Device Bus Speed:     High
Device Address:       0x13
Open Pipes:              0


==

Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x40 (64)
idVendor:           0x2080
idProduct:          0x0007
bcdDevice:          0x0216
iManufacturer:        0x01
0x0409: "B&N"
iProduct:             0x02
0x0409: "NOOK GlowLight"
iSerialNumber:        0x03
0x0409: "_______________"
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     High
Device Address:       0x14
Open Pipes:              2

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0200 (512)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x01  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0200 (512)
bInterval:            0x01

Configuration Descriptor:
wTotalLength:       0x0020
bNumInterfaces:       0x01
bConfigurationValue:  0x01
iConfiguration:       0x00
bmAttributes:         0xE0 (Bus Powered Self Powered Remote Wakeup)
MaxPower:             0xFA (500 Ma)

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0x08
bInterfaceSubClass:   0x06
bInterfaceProtocol:   0x50
iInterface:           0x00

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0200 (512)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x01  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0200 (512)
bInterval:            0x01

 

[Renate]

Do you have a driver for the bootloader?
That is, an inf file that directs to winusb?

; OMAP3630
%SingleBootLoaderInterface%  = USB_Install, USB\VID_0451&PID_D00E
...
[USB_Install]
Include = winusb.inf
Needs   = WINUSB.NT

(It doesn't have to be exactly like this, but something similar.)

Is the problem that Windows is too slow to deal with it popping up suddenly?

C:\>sysdm.cpl

Hardware/Device Installation Settings -> "No" (You can turn it back on later.)

C:\devmgmt.msc

View/Hidden Devices
See if you can find 0451/d00e anywhere.
(Hint: Enter Ctrl-Tab Ctrl-Tab DownArrow will get you the "Device instance path" which shows the VID/PID.)

 

[stryker9]

Dear @Renate NST.. thank you!

The USB driver, I have from the folder over at "Hacking the new Nook GlowLight" thread; it has these lines:

; OMAP3630
%SingleBootLoaderInterface%  = USB_Install, USB\VID_0451&PID_D00E
%SingleFastBootInterface%    = USB_Install, USB\VID_0451&PID_CAFE

[USB_Install]
Include = winusb.inf
Needs   = WINUSB.NT

..the problem with the pop-up notification may be about it being too fast. I'm on a 2.2GHz-i7/16GB system. I'm not sure though..
I do not see any "VID_0451&PID_D00E" here, but I will try uninstalling the driver and trying again after the "Hardware/Device Installation Settings -> No" setting you've suggested.

Plus, I now have win-7, win-xp, and ubuntu16.04 in virtual machines, all set up.
From your attempts elsewhere, I'm gonna try it all.

 

[Renate]

@stryker9 (Sorry for the lateness of reply).
The snapshot that you displayed is for the UMS mounted disks, that's not anything that we're interested in.
The bootloader would be visible under devmgmt.msc
Be sure to click View > Show Hidden Devices
If it already had a named driver it could be under "Android Devices" (or "Androids" or whatever).
If it never had a driver it could be under "Universal Serial Bus devices".

If you're really lost, click View > Devices by connection.
Use a hub and put something well known in an adjacent socket.
Then just look for the thing next to your "SuperMouse2000" (or whatever).

 

[mahdishake]

Stuck on the first step...

@stryker9 (Sorry for the lateness of reply).
The snapshot that you displayed is for the UMS mounted disks, that's not anything that we're interested in.
The bootloader would be visible under devmgmt.msc
Be sure to click View > Show Hidden Devices
If it already had a named driver it could be under "Android Devices" (or "Androids" or whatever).
If it never had a driver it could be under "Universal Serial Bus devices".

If you're really lost, click View > Devices by connection.
Use a hub and put something well known in an adjacent socket.
Then just look for the thing next to your "SuperMouse2000" (or whatever).

I'm having a lot of trouble with this step as well. Not sure if it is because my computer is too fast or what, but after uninstalling the 0451:d00e keys I still do not see my device show up as omap.
My device is the white nook glowlight 2 (BVNR500) model running 1.3.2 firmware. Is my device even supported by this method?
I have also turned on show hidden devices in Device Manager.
Yet when I plug my device in, it simply takes a while but loads as a disk drive. I don't have any category labeled "Android Device" or "Androids" either.

I think this guide could use a YouTube video tutorial but, unfortunately, none have been made with this process.

Any help would be greatly appreciated!

 

[Renate]

I'm getting all confused here.
The white Nook is the Glow 2 is the BNRV510 (and it's an iMX6).
The "Nook Simple Touch with Glowlight" is the BNRV500 (and it's an OMAP, I think, I've never owned one).

 

[mahdishake]

I have the BNRV500

I'm getting all confused here.
The white Nook is the Glow 2 is the BNRV510 (and it's an iMX6).
The "Nook Simple Touch with Glowlight" is the BNRV500 (and it's an OMAP, I think, I've never owned one).

According to Amazon, I have the BNRV500 (A simple search for the BNRV500 leads me to an Amazon page with the white device). The Nook Simple Touch with Glowlight is black with page turn buttons and a micro sd slot, I believe the one I have is the version after it (all white no page turn buttons and NO micro SD card slot). Unfortunately, it seems like the one I have was very limited and discontinued shortly after its release. The lack of a microSD card means it's very hard to root, and I wasn't sure if this process would apply to it.

Any idea of rooting this version is even possible? I can't seem to find anything on it besides your process outlined in this thread.

 

[Renate]

Sorry, my confusion.
There are two models of Nooks that I have never had in my hands.

Model    Nickname  Size  Color  SOC       VID/PID    Board
-------  --------  ----  -----  --------  ---------  ------
BNRV200  "Color"
BNRV300  "NST"     6.0   Black  OMAP3621  2080/0003  zoom2
BNRV350            6.0   Black  OMAP3621                     ???
BNRV500  "Glow1"   6.0   White  iMX6SL    2080/0007          ???
BNRV510  "Glow2"   6.0   White  iMX6SL    2080/000A  E60QD0
BNRV520  "Glow3"   6.0   Black  iMX6SL    2080/000B  E60QQ0
BNRV700  "Glow4"   7.8   Black  iMX6SL    2080/000C  E70Q50

Try this:

# getprop ro.board.platform
# getprop ro.product.board
# grep Product /*.rc
# busybox grep Product /*.rc

The last one is only if the third one doesn't work.

Edit: Err, if you're not rooted you probably can't see the rc files.
If you know Windows device manager (devmgmt.msc) find your Nook, look in the properties and see if you can find something like:
USB\VID_2080&PID_0007&MI_01\8&B724262&0&000

 

[mahdishake]

Sorry, my confusion.
There are two models of Nooks that I have never had in my hands.

Model    Nickname  Size  Color  SOC       VID/PID    Board
-------  --------  ----  -----  --------  ---------  ------
BNRV200  "Color"
BNRV300  "NST"     6.0   Black  OMAP3621  2080/0003  zoom2
BNRV350            6.0   Black  OMAP3621                     ???
BNRV500  "Glow1"   6.0   White  iMX6SL    2080/0007          ???
BNRV510  "Glow2"   6.0   White  iMX6SL    2080/000A  E60QD0
BNRV520  "Glow3"   6.0   Black  iMX6SL    2080/000B  E60QQ0
BNRV700  "Glow4"   7.8   Black  iMX6SL    2080/000C  E70Q50

Try this:

# getprop ro.board.platform
# getprop ro.product.board
# grep Product /*.rc
# busybox grep Product /*.rc

The last one is only if the third one doesn't work.

Edit: Err, if you're not rooted you probably can't see the rc files.
If you know Windows device manager (devmgmt.msc) find your Nook, look in the properties and see if you can find something like:
USB\VID_2080&PID_0007&MI_01\8&B724262&0&000

Ah no worries, I think I was mistakingly calling it the NG2. I don't have the Nook with me at the moment, I can get back to you in a couple of days.

 

[likesnooks]

thanks for the instructions

 

[grockk]

It's worth noting that if you only want to change the partition sizes, you can do the noogie boot, connect to GPartEd or similar and resize without needing to root. Since our NGL is my wife's, it's all stock except for 2.3gb of side loading book space.

Also all 4 of the partitions that need to be resized/moved can be deleted and recreated if you get errors trying to move them. Then i did a factory restore. The partitions persist through restore. But the restore image is 1.3.1 which doesn't have the TLS 1.2 update so you need to update to 1.3.2 by manually updating at help.barnesandnoble.com/app/answers/detail/a_id/4212