yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
Well, heck, I've got a hardware console on my Nook Touch.

I'll take a look loading u-boot13.bin later

The default is using ttyS0 as console.

I have previously modified u-boots to use ttyS1

Note, these addresses are not guaranteed, check your image.

Look for ttyS0.

>modfile u-boot12.bin 27a45 31
[00027a45] 30 => 31
>modfile u-boot12.bin 27acd 31
[00027acd] 30 => 31
>modfile u-boot13.bin 2877f 31
[0002877f] 30 => 31
>modfile u-boot13.bin 2880c 31
[0002880c] 30 => 31

Edit:

Well, I checked, unfortunately I get nothing out of either u-boot.bin when booting.

The "ttyS1" is actually just an argument it feeds to uImage if it ends up loading that.

I only get output from a normal boot, then I get the whole dmesg stuff.

Mmm, I guess that u-boot.bin is using UART0.

I don't know where that comes out and it doesn't appear to have any level shifters.

I guess that I can go looking for it.

What's the config with this?

- Console Interface:
Depending on board, define exactly one serial port
(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
console by defining CONFIG_8xx_CONS_NONE
[Nook Touch General] Kramar111:
@ Makkand

http://xdaforums.com/showpost.php?p=60743883&postcount=574

:)
[Nook Touch General] 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?
[Nook Touch General] digixmax:
See this XDA thread http://xdaforums.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).
[Nook Touch General] 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.
[Nook Touch General] Renate:
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?
[Nook Touch General] StanIam:
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.
[Nook Touch General] 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?
[Nook Touch General] 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
[Nook Touch General] Greenstuff4:
Hi Renate, you seem to be the expert on the NGL. I need help.

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!
[Nook Touch General] Renate:
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 [MENTION=9138275]Becky2719[/MENTION] I didn't notice your post.
[Nook Touch General] 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
[Nook Touch General] Renate:
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
[Nook Touch General] ylmir:
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?
[Nook Touch General] Renate:
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.
[Nook Touch General] ylmir:
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.
[Nook Touch General] Renate:
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)
[Nook Touch General] straygecko:
Yeah, it does open a console. Its low level so we don't get ttys0, ttys1, etc. as its initializing the chip itself. It looks like its using COM1 / UART1 - everything is 1 based, not 0 based. Here's a version compiled to use COM2 / UART2. See if that gives you any output.

Edit:

Well some devices seem to have UART0 but there is none defined for the NST - only UART1, UART2 & UART3.

/*
* NS16550 Configuration:
*/
#define V_NS16550_CLK (48000000) /* 48 Mhz */

#define CFG_NS16550
#define CFG_NS16550_SERIAL
#define CFG_NS16550_REG_SIZE (-4)
#define CFG_NS16550_CLK V_NS16550_CLK
#define CONFIG_BAUDRATE 115200
#define CFG_BAUDRATE_TABLE {115200}
#define CFG_NS16550_COM1 OMAP34XX_UART1
#define CFG_NS16550_COM2 OMAP34XX_UART2
#define CFG_NS16550_COM3 OMAP34XX_UART3

/*
* select serial console configuration
*/
#define CONFIG_SERIAL1 1 /* UART1 on board */
#define CONFIG_CONS_INDEX 1

I changed CONFIG_CONS_INDEX to 2 which, looking at the code, should shift it up to UART2. But elsewhere in the code it looks like UART2 is the hardware keys. Elsewhere it looks like the code scans devices to choose a console port. I haven't been able to trace the initialization very well. So who knows if it will do anything.
[Nook Touch General] straygecko:
That README is very misleading and isn't very up to date on board dependencies for configurations. Those configuration settings look like they affect common/serial.c but our boards use drivers/serial.c
[Nook Touch General] Renate:
Yes, UART2 is ttyS1.

Can you mod x-loader too?

I'll try tonight.
[Nook Touch General] straygecko:
Sure. Here's one built from the 1.2.0 source and one from the 1.3.0 source. There is a note in the config:

/*
* Select serial console configuration. UART 1 is used as UART3 is muxed
* with USB and a GPIO already used for EPD screen
*/

1.3.0 has some USB boot stuff added - not sure what its all about but looks like a different protocol than aboot.
[Nook Touch General] usenothing:
Hi,Renate NST:

Firstly ,i have to say, the screen-shut picture in my last post , the "ADB ***" interface is not my NOOK , it's showing my android cellphone.

Then , I checked my regedit.

I didn't find the "AndroidUsbDeviceClass" item when i expand the "Vid_0451&Pid_d00e".

They are shown as the following :

when I try to delete the "Vid_0451&Pid_d00e" group, error happened like this:

Maybe my former operation is not correct , maybe ,something is wrong with my Win7_X64 ?

I am thinking about giving up trying all these , to leave you more time to do the more effective and valuable things rather than reply my post :)

However , thanks a lot :),
[Nook Touch General] Renate:
[MENTION=1584045]straygecko[/MENTION]:

Oops, I misspoke, I meant that I wanted an aboot with UART2:

I tried this:

omap3630.exe omap3_aboot.bin u-boot-nst-130-uart2-00.bin
Waiting for bootloader... connected
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13
CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... done
Ack: AABBCCDD
Sending image file u-boot-nst-130-uart2-00.bin, 164356 bytes... done
Waiting for disconnect... done
Waiting for fastboot startup... [i](never finished)[/i]

It never finished and it didn't spit a single char out on the UART that I was listening to.

I tried to see if I could get your MLO-nst-120-uart2.bin but they don't do that AABBCCDD thing.

I tried putting it into my /boot directory to try a normal boot with that.

That did not work either.

I replaced it with the stock mlo.

That still didn't work.

(The rom bootloaded wants mlo (x-loader) to be the first file on the partition.)

I copied everything off, formatted /boot, copied mlo over, copied u-boot over, copied the rest over.

Now it works.

I'll try to see tomorrow if I can do a normal boot with MLO-nst-120-uart2.bin and get it to output to the console.

[MENTION=4597750]usenothing[/MENTION]: You need to change/delete permissions on the keys to delete them.

I have a utility for deleting these keys automatically, but it's not public-ready.

Since I do a lot of USB work it's handy to make Windows forget it ever saw a USB device.

(That's especially true if the number of interfaces has changed.)

Fortunately, I can still read my bedtime book on my Nook. :p
[Nook Touch General] jwxuan:
The windows xp test
[Nook Touch General] Renate:
Oh, aren't you running this on the command line?

That is, "MS-DOS" or "Shell" or <Windows>-R and type cmd.

omap3630.exe needs the name of two files anyway.

OMG, I hope that you didn't reinstall Windows because of this?

Forget the asicidcheck.exe, just use the omap3630.exe as described above.
[Nook Touch General] straygecko:
Hmmm... Looking at aboot it uses UART3 and has no code at all in it for other UARTs. While investigating what code is needed for UART2 and looking at u-boot I ended up with a massive headache trying to understand the MUX initialization for the UARTs. In the end I think that u-boot doesn't properly intialize the MUX for UART2 to use it as a console. But I just don't understand the hardware well enough to sort it out.
[Nook Touch General] yeahman45:
can you attach the windows application plz? i am willing trying it on my NST with glowlight with a broken sd card slot

---------- Post added at 07:28 PM ---------- Previous post was at 07:08 PM ----------

where is the zip for this also?

---------- Post added at 08:05 PM ---------- Previous post was at 07:28 PM ----------

i get same error as usenothing for the registry keys and i cannot delete it although i am running regedit as administrator... also tried to change the permission but access denied also.
[Nook Touch General] Renate:
Back to our regular program...

When I was using omap3_aboot.bin and u-boot12.bin I could reliably fastboot into CWR.

I had problems fastbooting my usual (rooted) uImage, uRamdisk.

I meant to follow up on this tonight but it looks like I'll get around to it tomorrow.

If you have any questions about the OMAP36XX, just read the manual.

It's only 3771 pages long. (That's the actual length of swpu177aa.pdf.)
[Nook Touch General] jwxuan:
Finally，I made it

The attachment is the picture of the new glowlight with the experiment3，the result is

Microsoft Windows XP [版本 5.1.2600]

(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>f:

F:\>omap3630.exe omap3_aboot.bin u-boot13.bin

Waiting for bootloader... connected

Received ASIC id, 69 bytes

OMAP36XX, rev 07

Unlocked

ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

CRC1: EF3EBF13

CRC2: 00000000

Sending image file omap3_aboot.bin, 3480 bytes... done

Ack: AABBCCDD

Sending image file u-boot13.bin, 175024 bytes...Error sending image data

F:\>

Hoping this‘s help！
[Nook Touch General] jwxuan:
the new nook glowlight as Android Bootloader Interface

The Device Manager recognize the new nook glowlight as Android Bootloader Interface

View attachment 2470090
[Nook Touch General] Renate:
Thanks, jwxuan.

On your device the x-loader is running but it doesn't accept the full u-boot download.

Normally it shouldn't care about the contents of the file while it's downloading.

This seems to indicate that the NG2 doesn't like the aboot all that much.

I have a new version of omap3630.exe zipped below.

It has better error reporting and will tell us where it stopped.

It also queries a few fastboot variables to see that all is working ok.

Tell me if you know of any interesting variables to query.

Here's how the new version runs on my NST:

C:\>omap3630.exe omap3_aboot.bin u-boot12.bin
Waiting for bootloader... connected
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot12.bin, 170572 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... connected
product 3621GOSSAMER
version 0.5
Disconnected
[Nook Touch General] straygecko:
We have one report of this with a NST with a broken SD slot and one with a NG2 - both connecting from Windows. So its not likely a NG2 related problem. The latest usbboot people have used to test with linux reports any USB read or write errors and we haven't seen any. OTOH, usbboot doesn't explicitly close the usb fd and even if it did the close function doesn't check the return code. Normally this is a bad thing due to buffering possibly delaying errors. But usbboot writes use ioctl usb bulk transfer which is a synchronous operation so it should be seeing any errors. So I lean towards this being a Windows issue of some sort but I will modify usbboot to explicitly close & check the close return code for my next build so we'll have full error reporting on both platforms.
[Nook Touch General] Renate:
You mean this works ok on Linux?

I thought that we had not seen fastboot start correctly on anything but NST?

Can you get NST to fastboot and load a full image (not CWR) correctly?

Can you get any (1 or 2) glow to fastboot getvar?

Here is my understanding, could you add your stuff?

---- NST ---- --- Glow1 --- --- Glow2 ---
Linux Windows Linux Windows Linux Windows
----- ------- ----- ------- ----- -------
1st image loads yes yes yes
aabbccdd ack yes yes yes
2nd image loads yes no no
getvar yes no no
boot CWR yes no no
boot Nook no no no

The last Linux result I see is shanks7777 where it hangs during/after loading the 2nd image.

http://xdaforums.com/showpost.php?p=48675691&postcount=53

How are you sure that it really ate all the 2nd image, let alone started it?
[Nook Touch General] Renate:
Since there seems to be a lot of problems with Win7 drivers,

I'd like to check that there is no problem with my software under Win7.

Could somebody check this please?

You just need a Win7 or greater and any kind of Android device that has ADB working already.

This test will not do anything to your device.

It will just see if the USB connection stuff works under Win7.

You kill the (possibly running) ADB server so it won't hog the connection.

It will check to see if it can see an ADB USB interface out there.

You can kill it with ^C as soon as it says "Waiting".

The "foo" (or whatever you like) is just a dummy arg that won't get used.

C:\>adb kill-server
C:\>omap3630 foo foo
[b]Device in ADB mode[/b]
Waiting for bootloader...^C
C:\>

I'm looking for the response in bold.
[Nook Touch General] usenothing:
Hi, I tried this.

I connect my Nexus S to Win7_x64 . then : run "adb kill-server" .

Finally ,run "omap3630 foo foo ", and the result is :

Device in ADB mode

Waiting for bootloaders...

So, i have to "Ctrl+C" ...

the screen-shut :
[Nook Touch General] straygecko:
Renate, I hope I didn't come off as attacking your Windows code as that wasn't my intention. The Nook Color stuff and the B&N u-boot stuff I'm using is a little ugly. You started out building in better error checking and output formatting, have done far more low level USB stuff than me and have a great reputation here on XDA so I'd trust your code over the stuff I'm working with any day.

I only meant that the write errors clearly weren't NG2 related as we had a non-NG2 device see the same write error. It was just quick speculation that Windows is in some way involved in the write errors since the linux usbboot has not reported any write errors sending u-boot.bin. I didn't spend much time thinking about it as I have a bunch of year-end stuff piling up for my business right now. You're right that it wasn't particularly well founded speculation.
[Nook Touch General] Renate:
Eh, speculation is what we do. We'll get there eventually.

There's a kind of parallel thread here on rooting a Nook with a broken SD card slot.

http://xdaforums.com/showthread.php?t=2579521

The problem is similar, but different than rooting the new Glow.

At the time it seemed like keeping them separate was a good idea.

It's certainly strange that some things work on the Touch but not Glow1.

There's not all that much difference between the two.

Unfortunately, both straygecko and I only have Nook Touches, where most stuff mostly works.

We'll have to work on some more experimenting.
[Nook Touch General] Renate:
Well, I'm more confused than ever.

I've basically got 3 different things that I can try to fastboot boot my NST up on:

Clockwork Mod Recovery

The stock Nook 1.2.1

My usual modified uImage and uRamdisk

CWR works fine all the time, the other things don't.

The funny part is, since CWR has a big file system in ramdisk it's twice as big as the others!

It looks now like this error occurs in Win7 with Touches too:

Sending image file u-boot.bin, 170572 bytes...
Error 0000001F sending image data, sent 0 bytes

The message may be a red herring.

The Nook may shut down its USB interface too quickly after the last byte is received.

If that is the case, manually doing fastboot commands after the above error might still work.

Could somebody with this error try (a good 15 seconds after that error).

fastboot getvar product
[Nook Touch General] jwxuan:
The new test with experiment4

The test result is “

Microsoft Windows XP [版本 5.1.2600]

(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>F:

F:\>omap3630.exe omap3_aboot.bin u-boot13.bin

Waiting for bootloader... connected

Received ASIC id, 69 bytes

OMAP36XX, rev 07

Unlocked

ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

CRC1: EF3EBF13, CRC2: 00000000

Sending image file omap3_aboot.bin, 3480 bytes... ok

Ack: AABBCCDD

Sending image file u-boot13.bin, 175024 bytes...

Error 0000001F sending image data, sent 0 bytes

F:\>

BUT I have a big problem，my new nook glowlight can't be power on，no matter what I do！

OK，I know what's going on, after you connecting the nook with Android boot loader Interface, it will decrease power very fast, I don't know why!