yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Kramar111:
[MENTION=1381628]bigtexan99[/MENTION]

did you use GParted Live bootable image?
[Nook Touch General] bigtexan99:
gparted

Yes, I pulled the stable ISO version from http://gparted.org/download.php and burned the ISO image to a CDR and boot the pc from that.
[Nook Touch General] Kramar111:
Run 'e2fsck -fy /dev/sdb9' one more time (as you restore Nook from backup, which probably contain filesystem error in sdb9)
[Nook Touch General] bigtexan99:
Kramar, thanks for not giving up on me! I reran the e2fsck command and it repaired some blocks. I then tried to resize the partition by grabbing the left side and moving it over 100mb. It failed. I've attached all the screen shots for you to see.
[Nook Touch General] Kramar111:
Did you refresh Gparted after e2fsck (re-read disk information)?

Try other cable/PC/flash drive (not CD) for boot
[Nook Touch General] Kramar111:
just checked, it works

Gparted Live 0.22 on USB flash drive
[Nook Touch General] bigtexan99:
Yes, I did refresh devices after running e2fsck. Okay, tonight when I get home I will try it on a different computer, burn the gparted image to a usb stick, and a different USB cable.
[Nook Touch General] bigtexan99:
I'm cursed!

I tried it with a new image of gparted on a USB stick. A different computer. A different USB cable. All new omaplink, aboot.bin, uimage, uramdisk files.

Same result!! It throws the same error when trying to resize the partition by dragging it from the left to the right: "could not stat device".
[Nook Touch General] Kramar111:
looks like bad block on Nook

Maybe somebody have any other idea? I'm don't
[Nook Touch General] kazikas:
Have you tried delete extended partition and recreate everything?
[Nook Touch General] bigtexan99:
Thanks Kramar.

Kazikas, I have not done that....I did run the e2fsck command on all the other partitions (except the FAT) and they all checked out good.

I'm not sure of the commands to delete the extended partition and recreate them but am willing to try if someone can provide some guidance.
[Nook Touch General] bigtexan99:
Success! It was easier than I thought. I deleted the partition, then created a new one with the same name but smaller size and created all the way to the 'right". Did one partition at a time. Gave them the same ext3 and the same volume label name., ie userdata, cache, reserve

The nook reset itself to factory oobe for some reason and root disappeared but it worked! Partitions are re-sized the way I want them and now I will re-root.
[Nook Touch General] Richard'as:
Noob friendly tutorial

Hey guys. I see here is a great effort for rooting NG2. I see Renate NST and others has put a lot of work here. That's why I love the Android community so much, they are just great and put a lot of work to make Android the best.

So far I was trying to follow this thread, but English is my foreign language I'm not so good at it and this thread is loooong... Even though I was using Linux (Manjaro) and its terminal a bit I'm still new to this stuff. Nor have used ADB (except copy/paste code to it).

So what I'm asking is could you kind smart ladies and gents put here a step by step tutorial for rooting NG2 with all the requisites necessary?

I just got a NG2 and it suck. I can't zoom pdfs, can't delete books from my e-reader, have WiFi, but can't surf the net... It's just plain stupid. The thing I got NG2 is that I was told it has custom Android that can be hacked to work as normal Android.

I just need a couple of reader apps, a web browser, a calculator and re partition flash for more user space for non Nook content.

If its possible, please, make a tidy clear step by step tutorial how to achieve this. I could also donate few EUR to xda community or certain persons for that.

Waiting your reply.

BTW: I would prefer using Win7, but if tutorial is easy Linux would be just fine.

Edit (2015-05-04):

Well somehow I managed to get all the needed posts with all the files and info so now have a working ADB connection. I used a Renate NST method, great thanks for you!

Probably going to make a tutorial for noobs like me, but first need to try playing with drivers on other PC, cause the most troubles I got when installing drivers.

And also need to play with some apps and such, cause using ADB is also troublesome for me, because of my low knowledge base on it, so when I'm finished myself with installing basic setup of apps, gonna include it in the tutorial too.

Again, many thanks for Renate NST!
[Nook Touch General] bigtexan99:
Glad you had success! This thread is too long and there are to many critical pieces of information widely scattered around. I hope you to take the effort to write a concise summary and give credit to the original authors.

Update on my NookGlowlight: Although I was able to root the device and then use omaplink to view the myriad of partitions, I still have not been successful in resizing the B&N and Nook partitions. I finally did get them to align correctly using Gparted, but then whenever I connected to my Windows machine to transfer files I got the "drive is not formatted" issues as described on post 511 of this thread. Followed those steps but had no success.

So I restored to factory image, re-rooted, installed Relaunch.apk and am just living with my small amount of disk space available to me.
[Nook Touch General] thrackanomir:
Try to refer to specific post number, not the page of the thread, as other users may have different thread display settings ("Number of Posts to Show Per Page"). For example for me this thread has only 12 pages at the moment, so it makes your reference a mystery for me.

And about your problem - I have only the NSTwG, but have you checked that using GParted you leave the correct format type on user partition? Remember that Windows probably won't recognize the ex3 and ex4 formats. It will only see NTFS and FAT formats.
[Nook Touch General] bigtexan99:
Good catch! Post #511.

The original format of the partition is Fat16, and after it is resized, Gparted advises it wants to format is at Fat32 due to the size of the partition.

It seems some have been successful and some have failed using the same instructions.
[Nook Touch General] Kramar111:
[MENTION=1381628]bigtexan99[/MENTION]

if you carefully read http://xdaforums.com/showpost.php?p=57902601&postcount=526 (and i asked for it) you will see

and here http://xdaforums.com/showpost.php?p=57903798&postcount=528
[Nook Touch General] bigtexan99:
Thanks for all your troubleshooting help Kramar! I gave it one more shot and finally got it done!

I deleted cache,reserve,userdata,nook partitions. Then re-created them in the same order, but sized the way I wanted. Don't know what I did different this time, but I worked.

I grew the Nook partition to 2.0 gb.
[Nook Touch General] plantucha:
overdrive

can you install and use overdrive app to read and borrow library books on rooted NGL?

or is it tricky?
[Nook Touch General] Kramar111:
overdrive app need android 2.2 or higher

NGL have 2.1
[Nook Touch General] :
Only the newer versions of OverDrive need 2.2. The older ones need 1.6, and they work on the NST/NTG.
[Nook Touch General] dumalkin:
How to change MAC address ?

Hello,

I have working, rooted Nook Glowlight (root, custom readers, partitions resized, etc)

Now I just bought the second, exactly same Nook. I created backup image of the configured one, and restored it to the new device.

Everything works, but now both devices have same serial numbers and MAC addresses.

I don't mind identical serial numbers, but duplicate MACs prevent them to be simultaneously on my home network.

Is there way to change MAC address of the Nook ? Obviously it is stored somewhere in Ramdisk / boot partition, and not read from the hardware, else the problem won't appear.

Any help will be appreciated
[Nook Touch General] :
It's in some file in /system/etc/wifi/, but I don't know which.

Let me look into this.
[Nook Touch General] dumalkin:
Solved !

WiFiBackupCalibration stores MAC in the first 12 bytes (highest/leftmost byte of MAC is stored at offset 0B).

I connected ADB via WiFi, pulled the file, modified it using HexEditor, then pushed the file back.

Reboot, and it works.

adb pull /rom/devconf/WiFiBackupCalibration
//edit file
adb push WiFiBackupCalibration /rom/devconf/WiFiBackupCalibration

How I found it ?

in init.rc I see the following lines:

service wlan_loader /system/bin/tiwlan_loader \

-f /system/etc/wifi/firmware.bin \

-i /system/etc/wifi/tiwlan.ini \

-e /rom/devconf/WiFiBackupCalibration

Somewhere I saw reference to WiFiBackupCalibration file as to location where mac is stored.

I don't know how can I access this file to check it.

Thanks, and I hope it will be useful for someone else as well.
[Nook Touch General] :
Great find, thanks! You've made it onto the Useful Links list! :)
[Nook Touch General] remmons:
Is there a post in this thread that summarizes the procedure for rooting the Nook Glowlight?
[Nook Touch General] :
As of now, all the essential information has not yet been compiled into a single thread. It's somewhat spread around. Not the best, I agree. :eek:
[Nook Touch General] panickros:
Any hope for Android version 4.x?

Hey guys,

I am completely noob for any kind of hacking,

but I recently heard that there is a working CM11 test build for NST and NSTG.

Is there any hope for CM11 for New Nook Glowlight, too?

This is really important for me because I use some private reader apps only support android version 4.x or above.

Thank you. :)
[Nook Touch General] FerociousAndroid:
WHY?!
[Nook Touch General] Makkand:
Pleeeease help me - I'm going goggle-eyed from all the posts I've been reading!

I've managed to install a 1337 ROM, but many apps fail to load e.g. YouTube.

I try to install APK but I get errors regarding unknown source.

I've tried to ADB, although the device is in developer mode and I can browse the storage (from Windows 10) I get the following: ADB Devices > (nothing listed under devices found).

Would it be cheeky to ask for the links to the instructions you followed? I've currently got 6 tabs open and finding conflicting information all over the shop :)
[Nook Touch General] straygecko:
Lets find out why 2nd stage didn't work

This is a good sign. As Renate pointed out the ASIC ID indicates that we have an unlocked bootloader so we should be able to sort this out. I don't understand why it wouldn't properly load the 2nd stage or why the 2nd stage failed. I've attached a new version with some added debugging to see if we can sort it out.

Again, this is Linux only

Extract the tar.gz file

Power off your NST or NG

run sudo ./boot1 <= change from last time (boot1 instead of booty)

Connect your NST / NG via USB cable - it should automatically power up and you'll see messages on your PC that it was recognized and things are being sent to it.

Copy/paste your results

I don't expect it to work any better than last time - just provide more information. But if it does work you'll see a couple of lines at the end something like this:

< waiting for device >
product:3621AVOCET
finished. total time 0.000s

If that happens you can reboot your NG2 with:

sudo ./fastboot reboot

Or if you are adventurous and want to try booting CWM

sudo ./boot2
[Nook Touch General] Edgur:
Happy to give it a whirl!

eddie@MyLinuxBox:~/usbrec_ng_130_debug$ sudo ./boot1
start usbboot
waiting for OMAP3/OMAP4 device...
[ usb read 69 fd = 5], fname=/dev/bus/usb/005/002
[ usb read 69 ] = 69, fname=/dev/bus/usb/005/002, Retry 0
0501050136300707130201001215010000000000000000000000000000000000000000141501000000000000000000000000000000000000000015090113FFFFFFBF3EFFFFFFEF00000000
Device OMAP3630 found
sending 2ndstage to target...
waiting for 2ndstage response...
[ usb read 4 fd = 5], fname=/dev/bus/usb/005/002
[ usb read 4 ] = 4, fname=/dev/bus/usb/005/002, Retry 0
ack response 0xAABBCCDD
sending image to target...
< waiting for device >
^C

AABBCCDD looks good :)

It behaved a little differently this time. Rather than continue its normal boot process, the Nook was "hung". I waited about a minute before giving up and ^C'ing out.

The display stayed stuck on the powered-off screen and was unresponsive to normal button presses.

But I pushed and held power and n in various ways (separately, together, sequentially, etc) until it rebooted and came up normally.

When I have some more time (hopefully tomorrow) I'll try to work through Renate's suggestions to get the winusb working under Windows 8, as well.
[Nook Touch General] usenothing:
thanks for all your work.

I just tried this:

I did this with Edubuntu, and used the latest debug program.

And the result seems to be like :

start usbboot
waiting for OMAP3/OMAP4 device...
[ usb read 69 fd = 5], fname=/dev/bus/usb/002/005
[ usb read 69 ] = 69, fname=/dev/bus/usb/002/005, Retry 0
0501050136300707130201001215010000000000000000000000000000000000000000141501000000000000000000000000000000000000000015090113FFFFFFBF3EFFFFFFEF00000000
Device OMAP3630 found
sending 2ndstage to target...
waiting for 2ndstage response...
[ usb read 4 fd = 5], fname=/dev/bus/usb/002/005
[ usb read 4 ] = 4, fname=/dev/bus/usb/002/005, Retry 0
ack response 0xAABBCCDD
sending image to target...
./fastboot: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

I don't know why this error occured. :) and i would like to try more ,with your guidance.
[Nook Touch General] Renate:
A new Windows version that allows you to specify the two files.

I include u-boot12.bin & u-boot13.bin.

Try them both.

omap3630.exe omap3_aboot.bin u-boot13.bin

u-boot12.bin works on my Touch fine.

u-boot13.bin loads on my Touch, but doesn't present a fastboot interface.
[Nook Touch General] straygecko:
You are running a 64-bit OS but fastboot is a 32 bit app. You need to install ia32-libs to run 32 bit apps. I wish Linux would just say that. The 32 / 64 error handling is abysmal. Just try running a 64-bit executable on 32-bit and get "unexpected end of file, expected ")"" or some such nonsense.

---------- Post added at 09:17 AM ---------- Previous post was at 09:07 AM ----------

Yes, aabbccdd is good. That means aboot is loading and working properly. Now its on to u-boot. Staying on the power off display isn't good. When u-boot initializes it clears the screen (at least on the NST) so it flashes and goes to a white screen. So its not fully loading or initializing.

I'll take a look at it. In the meantime you might try Renate's u-boot13.bin from the Windows experiment. Copy it to your usbrec_ng_130_debug directory and modify boot1 to load it.

On the NST, when it goes unresponsive I hold down the power button for 20 seconds to get it truly powered off then power up as normal.
[Nook Touch General] shanks7777:
stephen@ubuntu:~/다운로드/usbrec_ng_130_debug$ sudo ./boot1
start usbboot
waiting for OMAP3/OMAP4 device...
[ usb read 69 fd = 5], fname=/dev/bus/usb/001/007
[ usb read 69 ] = 69, fname=/dev/bus/usb/001/007, Retry 0
0501050136300707130201001215010000000000000000000000000000000000000000141501000000000000000000000000000000000000000015090113FFFFFFBF3EFFFFFFEF00000000
Device OMAP3630 found
sending 2ndstage to target...
waiting for 2ndstage response...
[ usb read 4 fd = 5], fname=/dev/bus/usb/001/007
[ usb read 4 ] = 4, fname=/dev/bus/usb/001/007, Retry 0
ack response 0xAABBCCDD
sending image to target...
< waiting for device >

Tried with u-boot13.bin from Renate's zip file, however end up with same screen.

"Your NOOK has turned off completely."
[Nook Touch General] Edgur:
How are you generating these u-boot files? Is it possible to generate a hyper-minimal u-boot image that just has the device start up as a simple serial-over-USB that we can use a terminal to go to a minimal shell, or something?
[Nook Touch General] straygecko:
I'm modifying the B&N source to force it into fastboot mode. u-boot's purpose in life is to load your kernel or flash your device - it is sort of a stripped down kernel with minimal functions available. A minimal shell environment would require a more complete kernel which is what u-boot will load.
[Nook Touch General] usenothing:
my Nook GlowLight became bricked ?!

hi,I have a problem ,and i want your help :)

I have an old Thinkpad-T43, and it's armed with Ubuntu_i386. This evening, i tried your idea ,and got the same result as what other friends got.

But ,but, after i connected the nook to PC with usb, nook didn't boot. It stayed at the Power-off screen (it's said : your nook has turned off **)

Then, I disconnected the nook from PC,and press the power button ,it still didn't boot.

Even I have long-pressed the power button, nothing got happened.

Finaly , i connect the nook to pc with usb again, and, the screen changed to the "charging icon" interface. However, it didn't boot.

I tried many times , having the same result.

At this very moment, the power light is red, and charing icon is on the screen.

[In my memory, battery is almost full 4-5hours ago.I don't think all this is because of “lack of electricity” . ]

What should I do?

Hoping to hear from you ,thanks.

---------- Post added at 03:40 PM ---------- Previous post was at 02:45 PM ----------

Sorry for my question. i dis nothing，but i can boot the nook normally. maybe something is wrong with the battery .i will do more to make it more clear. tomorrow.
[Nook Touch General] straygecko:
If long pressing (20 - 30 seconds) the power button then releasing it and then powering up as normal (press power button for a few seconds) doesn't get your device to boot then you will probably need to disconnect the battery and reconnect it. I assume it comes apart the same as for the simple touch. iFixit has a good walk-through of opening the NST - its really easy. I would wait for your charging light to go green then unplug and try booting again before pulling the battery as opening it up will void your warranty.

BTW, at this stage I don't need a lot of people testing. If it doesn't work for the first two testers no need for another. Lets limit the number of possible bricks.

An update on where I'm at. I'm still puzzling over the failure of u-boot. I'm compiling from the B&N NG2 1.3.0 source with minor modifications to force it into fastboot mode and for fastboot to load a ramdisk image when told to boot. I don't see any obvious errors. On the NST compiling from the NST 1.2.0 source with the same changes works fine on the NST. The B&N NG2 1.3.0 source also includes a config to compile for the NST. So I've been playing around with that and can't get a 1.3.0 u-boot to work on the NST. I don't know if B&N gave us a bad 1.3.0 u-boot or its a problem with my compile. I'll try some more tests and see where I can get. In the mean time, someone could try my NST 1.2.0 u-boot and/or Renate's u-boot12.bin on their NG2. I don't have high hopes as I see some board specific (display & clock stuff) added in the 1.3.0 u-boot but you never know.
[Nook Touch General] Edgur:
Disconnecting the battery on the Nook GlowLight is extremely easy.

1) Remove the rubber ring around the edge.

2) With the front of the Nook facing you, you can see 3 clips on either side, 2 on top, and 1 on bottom.

3) Use a thin screwdriver or something to carefully press those clips inward, so they are not catching on the metal frame anymore.

4) do that for each clip, and the back cover will be off!

5) The battery is attached to the inside of the back cover. A ribbon cable goes to the main board. Simply detach that cable.

Voila, you are finished. Now re-attach the battery cable and clip the back cover back on.
[Nook Touch General] straygecko:
Another u-boot test

OK, I have another NG2 u-boot to test attached for you Linux testers. You can ignore the request to try the NST versions - there is just too much different between the boards for it to work - display, clock, USB device location, mux initialization. Extract it to your usbrec_ng_130_debug directory and modify boot1 to load it.
[Nook Touch General] shanks7777:
start usbboot
waiting for OMAP3/OMAP4 device...
[ usb read 69 fd = 5], fname=/dev/bus/usb/001/004
[ usb read 69 ] = 69, fname=/dev/bus/usb/001/004, Retry 0
0501050136300707130201001215010000000000000000000000000000000000000000141501000000000000000000000000000000000000000015090113FFFFFFBF3EFFFFFFEF00000000
Device OMAP3630 found
sending 2ndstage to target...
waiting for 2ndstage response...
[ usb read 4 fd = 5], fname=/dev/bus/usb/001/004
[ usb read 4 ] = 4, fname=/dev/bus/usb/001/004, Retry 0
ack response 0xAABBCCDD
sending image to target...
< waiting for device >

Still the same result here.
[Nook Touch General] Renate:
I guess that all the brave people are Linux users.

I haven't heard of any successes from anybody using my Windows version above.

I'd like to see if it indicates anything different than the Linux version.

Hmm, we may need to get a console output or something going to debug this.

It's difficult to do this by remote control.

Anybody want to send straygecko a new Glow? :fingers-crossed:
[Nook Touch General] usenothing:
hmm,thanks your work ,firstly.

I tried your way a week ago.My probelm is :

I edited the inf file, but ,cannnot install the modified driver.

If i deleted the NOOK in device manager , two results happened:

A. the win7_x64 installed driver automaticly , the modified driver folder cannot be specified.

B. I changed the driver-install mechanism by editing the "gpedit.msc". However, when i specify the edited driver folder ,the OS told me : cannot find correct driver files.

So, the next step never be finished :)
[Nook Touch General] Renate:
Did you try:

bcdedit.exe /set nointegritychecks ON

Does it show any driver loaded?
[Nook Touch General] usenothing:
Glad to see your reply.

I don't get you exactly ,sorry.

I just disconnected the Nook GL from PC. and run the commander with administrator privilege.

It's said "operation finished succefully. ",something like :)

I got a screen-shot from my PC:

Hoping it will help you understand what problem i'm meeting with .Cause my english is so poor.
[Nook Touch General] Renate:
Wait, am I missing something here?

Are you saying that the NG2 comes out of the box with ADB enabled?

Is there a setting in Settings for "Enable USB debugging"?

Have you connected to it on ADB and is it $ or #

You say that your Nook is off and you plug in the USB cable and no popups appear on the desktop?

Look in the registry for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_d00e

There should be at least one subkey

In that subkey should be Class: AndroidUsbDeviceClass

Is it there?

Try deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_d00e

Powered down Nook, USB cable in, what does it do?
[Nook Touch General] straygecko:
A serial console even on the NST would be most helpful to track down where the 1.3.0 u-boot is failing. I've been rolling back 1.3.0 to 1.2.0 piece by piece along with a couple of other long shots trying to sort out what's causing it to fail. So far 9 attempts to get a 1.3.0 u-boot to work on the NST with no luck. So far I've been avoiding the stuff that's harder to roll back where they have intertwined the NST & NG2 code for board & display detection / specific code across multiple source files. I've got a few other things to try before I dive into that. I'll get there eventually but it will take some time. Hopefully, whatever is keeping 1.3.0 from working on the NST will be the same thing that's keeping it from working on the NG2.