yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
Sorry, jwxuan.

Nothing should have been writing to your Nook.

I don't see how it could have been modified.

As long as a long press will get you to the bootloader we are still in business.

Here is another test version to try to see if the 2nd image is really not being accepted.

With XP and my Nook Touch, it goes like this:

C:\>omap3630 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
Waiting for ADB...^C
[Nook Touch General] jwxuan:
The good news

Never mind！

I think this is the good news

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...********************************

********************************************************************************

********************************************************************************

********************************************************************************

********************************************************************** ok

Waiting for disconnect... ok

Waiting for fastboot...
[Nook Touch General] Renate:
It's nice that that works.

Can you boot your Nook normally?

Can you see if the old version (experiment4.zip) works?

There isn't that much difference between 4 & 5.
[Nook Touch General] jwxuan:
No, I can't! After I take experiment5, I neither take the test again, nor power on！I have to charg the nook again！And then I need to power off for 20 Seconds，and then take the test again！

The old experiment4 still can't woks，it just gave me the same picture as my previous picture experiment4！
[Nook Touch General] straygecko:
Experiment4 wouldn't get to fastboot for me with Error 0000001F. Experiment5 works great. I'm looking forward to no more live CD boots to linux.:)

C:\temp\usbrec_nst2>omap3630 omap3_aboot.bin u-boot.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-boot.bin, 170572 bytes...**********************************
********************************************************************************
********************************************************************************
********************************************************************************
************************************************************ ok
Waiting for disconnect... ok
Waiting for fastboot... connected
product 3621GOSSAMER
version 0.5
Waiting for ADB...
[Nook Touch General] Renate:
I'm glad that X5 worked.

There seems to be something screwy with the driver breaking up things into wMaxPacketSize.

It always works on mine, but others have problems.

Here's X6.

We should be able to concentrate now on getting a NG2 compatible u-boot.
[Nook Touch General] yeahman45:
same problem with experiment 6 ... my NST with glowlight had a blank screen.. and when i connect it to charger it says battery 0 ... although i am pretty sure it was 85% - 90% a minute before
[Nook Touch General] straygecko:
Going from the powered off screen to a blank screen is generally a good thing. That usually means you made it to fastboot. Did you still not get the product, version and waiting for ADB messages?
[Nook Touch General] straygecko:
More fun with u-boot & UART2

X6 worked great. Booted into CWM. I've been researching UART2 a little more between tearing things out of the 1.3.0 u-boot code. Would you try the attached u-boot and see if you get anything on your console?
[Nook Touch General] yeahman45:
i posted my result on my thread http://xdaforums.com/showthread.php?p=48761982#post48761982

it's stuck at "Waiting for fastboot..."

Merry x-mas to you all
[Nook Touch General] straygecko:
Go into Device manager. Click on View | Show Hidden Devices. Look under Other Devices. See if you have a device 3621GOSSAMER. If you do right click and select Update Driver Software. Click on Browse my computer for driver software in the box that pops up and select the folder that has the .inf file you modified per Renate's instructions. Then try again.
[Nook Touch General] yeahman45:
yup thx with experiment5, windows asked me to install drivers for fastboot loader .. working now... here's my result:

U:\nook\usb_loading\experiment5>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
Waiting for ADB...

what does that mean? i still don't have adb

edit: same result with x6.. waiting for adb
[Nook Touch General] straygecko:
That means we're one step away from getting you ADB. I've attached the CWM uImage & uRamdisk from the NST CWM thread. Rerun experiment 6. When it shows Waiting for ADB you need to run a fastboot command to boot the CWM uImage & uRamdisk. The fastboot command is in the Android SDK platform-tools folder - same place as the ADB command. The command you want is:

fastboot boot <path to uImage> <path to uRamdisk>

Give it 30 seconds to a minute and you should get the CWM screen on your NST. CWM has ADB enabled so you will be able to connect with ADB and try correcting the problems you are having. If you haven't done it in the past, the very first thing you should do is pull over the /rom folder to your PC and keep it safe. It has your device specific stuff that can't be replaced. Then move back to your other thread or a new thread if you need help sorting out your device problems.
[Nook Touch General] yeahman45:
holy crap! this works!!! it booted to cwm!!! thx! thx thx... working with experiment 6

---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------

but i don't have adb in cwm....

the command adb devices did not display the nook (even when i restarted the daemon)
[Nook Touch General] straygecko:
Probably a driver problem again. Look in Device Manager for a yellow exclamation point device while you have your NST booted into CWM connected. Do the update driver like you did to get X6 working.
[Nook Touch General] yeahman45:
in device manager it says "Android composite Adb interface" with no exclamation mark.
[Nook Touch General] straygecko:
Is that without "Show hidden devices" checked? Look at the device properties, Details, Hardware Ids properties. Does it show VID_2080&PID_0003? Is your adb_usb.ini file set to 0x2080?
[Nook Touch General] yeahman45:
I am trying to restore an img backup i made with winimage but i get an error at about 10%.. any idea what may be wrong? I booted with noogie instead of cwm

i am not exactly sure if it booted with noogie actually... screen remains blank instead of "rooting forever"
[Nook Touch General] straygecko:
Nope, I've always backed up and restored to SD with NookManager. Move this over to another thread and leave this one to working on getting the NG2 to boot over USB.
[Nook Touch General] yeahman45:
yup it shows "VID_2080&PID_0003"

i can't find adb_usb.ini in my winxp user's folder.. did a search.. it is present in my win7 though...

moved my issue with restoring img backup in my thread .. plz help http://xdaforums.com/showthread.php?p=48795114#post48795114

---------- Post added at 09:33 PM ---------- Previous post was at 09:28 PM ----------

i also tried install glownooter with cwm but when flashing it ... the nook restarts
[Nook Touch General] Renate:
The "Waiting for ADB" is only to show you when the interface opens up.

I was going to add a step before for fastboot boot of CWR.
[Nook Touch General] jwxuan:
Experiment6 is just the same as experiment5

Experiment6 is just the same as experiment5，I can't see there is any difference！

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... ok
Waiting for disconnect... ok
Waiting for fastboot...
[Nook Touch General] Renate:
X6 is just a cleaned-up version of X5.

We're now at the point where an NG2-compatible u-boot is the next hurdle.

Right now I'm trying to get a console working on u-boot so we can see what it happening.
[Nook Touch General] Renate:
Some more experimental data:

On my NST on XP I can X6 with omap3_aboot.bin and u-boot12.bin into fastboot and boot image and ramdisk from CWM.

This does not work with the image and ramdisk from stock Nook.

The error is "init: cannot execve('/system/bin/app_process'): Exec format error".

This error sometimes appears with other processes, whichever tries to start first.

The problem is that the kernel can not find files.

CWM uses ramdisk and can always find things.

The stock Nook when booted this way does not know about the internal storage.

The other point is that I have never gotten a peep out of the console until it starts booting a regular image/ramdisk.

Both CWM and stock Nook print out lots.

omap3_aboot.bin has nothing in it for console.

With my setup, u-boot12.bin works fine.

There is a table of UART base addresses (0x4806a000, 0x4806c000, 0x49020000) in the file.

I tried swapping UART1 and UART2 with no success.

This was kind of to be expected since the interrupt vectors would be all mismatched.

I might see if I can write a "Hello world" program that goes where u-boot would be.
[Nook Touch General] yeahman45:
I think you need to go in device manager ... under "Android".. if there is an exclamation mark, update drivers for android fastboot device ... browse the ini modified with Renate's instructions .. then retry the process with the experiment
[Nook Touch General] straygecko:
jwxuan has an NG2 and is trying to load u-boot13.bin so he's not getting that far yet. We need to come up with a working u-boot for the NG2 for him to get there. But it is a good point to remember when we are testing u-boot.bin for the NG2 with Windows. We need to be sure the device is not presenting a fastboot VID & PID vs. a driver install issue before we can declare a u-boot as not working when it doesn't get past Waiting for fastboot.
[Nook Touch General] Renate:
Could someone do me a favor?

This is just a test to resolve exactly why X4 didn't work on some computers.

Could you run this if you got an 0000001F error before with X4?

This will not advance the cause of rooting the NG2, but it will help me to make sure my code is robust.

This executable is the same as X6, but has some debugging print out.

You don't need to do the whole test or specify arguments.

C:\>omap3630
Waiting for bootloader...
[b]Out endpoint MAXIMUM_TRANSFER_SIZE = 2097152
In endpoint MAXIMUM_TRANSFER_SIZE = 2097152[/b]
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

Thank you.
[Nook Touch General] straygecko:
Here ya go.

C:\temp\usbrec_nst2>omap3630 omap3_aboot.bin u-boot.bin
Waiting for bootloader...
Out endpoint MAXIMUM_TRANSFER_SIZE = 2097152
In endpoint MAXIMUM_TRANSFER_SIZE = 2097152
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-boot.bin, 170572 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot...
Out endpoint MAXIMUM_TRANSFER_SIZE = 2097152
In endpoint MAXIMUM_TRANSFER_SIZE = 2097152
connected
product 3621GOSSAMER
version 0.5
Waiting for ADB...

BTW, aboot uses the TI ROM API USB code. Doc on it is only available via NDA. There is some very limited info available in the lovely 3771 page TRM chapter 26.4.5 which seems to indicate it can only handle up to 512 byte chunks in a bulk transfer. OTOH, usbboot breaks its writes up into 4K chunks.

X6 has really helped me get nowhere fast. I did resolve one big issue where I inadvertently reverted to the linux toolchain which although it compiles u-boot fine it won't work. Getting back to the android toolchain has improved things but I still can't get a working nst u-boot from the 1.3.0 source.
[Nook Touch General] Renate:
Of course the Nook itself takes 512 byte packets as a high speed USB device.

The driver on Windows is supposed to take big (up to 2097152 for me) files and chop them into 512 byte packets.

This seems to have some problems, that's why I do the chopping myself.

As a sneak preview here's an unreleased version going all the way.

This is only bells & whistles because you can do it all manually with fastboot after it connects.

C:\>omap3630 omap3_aboot.bin u-boot12.bin backup\uRecImg backup\uRecRam
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
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... connected
Disconnected
[Nook Touch General] jwxuan:
Is there any thing we can do for you?

Is there any thing we can do for you?
[Nook Touch General] Renate:
:)

Mmm, no.

Right now we need to get a working u-boot & CWM for NG2.

It doesn't matter if the CWM screen and buttons don't work as long as the ADB does.

If B&N released a >1.3.0 update then we could easily see what is different from 1.2.1

We'll have to wait until we have enough connectivity.
[Nook Touch General] straygecko:
Thanks to Renate's Windows usb booting tool I have been able to do a ton of testing trying to get a usable u-boot out of the B&N 1.3.0 source. After 40 or 50 compiles I've tracked down the problem. B&N gave us non-working source. Fortunately it was something simple and easy to fix but was a pain to track down. They sprinkled a couple of printf statements in the low level board init where it was too early in the init to support printf causing the init to fail. Commenting out the printf's got everything working.

Attached is a u-boot for the adventurous ones to try who have tried previous versions. The interesting thing about this version is that even though it is built specifically for the NG2 it works fine on the NST thanks to B&N adding in some runtime device type testing instead of just relying on compile time configuration.
[Nook Touch General] jwxuan:
This is still a linux version？

This is still a linux version？
[Nook Touch General] straygecko:
It can be used either with the linux usbboot or Renate's windows X5 or X6. For windows extract to the same folder as your X5 or X6 then:

omap3630 omap3_aboot.bin u-boot-ng2-exp-v03.bin
[Nook Touch General] Renate:
Here's the latest version of the Windows loader.

As I mentioned above, it does the same as the last version if you specify the loader and uboot.

You have the option of also specifying the kernel and ramdisk and it will do that too.

Of course, you could just have the stock fastboot do that also.

C:\>omap3630 omap3_aboot.bin u-boot-ng2-exp-v03.bin uRecImg uRecRam
Waiting for bootloader... ok
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-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... ok
Disconnected
[Nook Touch General] usenothing:
I tried this morning on my XP pc.

After running "omap3630.exe omap3_aboot.bin u-boot-ng2-exp-v03.bin" ,it't gone a little until "Waiting for fastboot..."

I have a "android-device-manager" program made by the third party,and when I stay at "waiting for fastboot...", the program downloaded a "fastboot driver" automaticly. However, I guess the driver maybe wrong.

I downloaded the "android-SDK" again, and stilll not found the fastboot driver within it. So depressed :(
[Nook Touch General] Renate:
Did you modify the INF file as in above?

When it's sitting in fastboot mode you have all the time in the world to update the driver.

What does Device Manager say?
[Nook Touch General] shanks7777:
I tried with Renate's experiment7.zip and straygecko's u-boot-ng2-exp-v03.bin, and got

D:\성산\nook>omap3630.exe omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage uRamdisk

Waiting for bootloader... ok
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-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4079616 bytes... ok
Waiting for disconnect... ok
Waiting for ADB...

This was done in NG2
[Nook Touch General] Renate:
That looks good so far....

The first point, if you have the ADB server running it will hog the connection and it won't say that it found ADB.

So before you do this, make sure that you do adb kill-server

Of course you tried to see if you did have ADB by typing adb shell

Ok, the problem is, booting like this a normal Nook uImage and uRamdisk it doesn't know where /system is.

CWM has it all wrapped up in the uRamdisk, that boots easier.

Use the image and ramdisk from CWM.
[Nook Touch General] usenothing:
I borrowed one copy of edited usb-driver from a net friend.

I attached the winusb.inf in this reply post with url:　http://xdaforums.com/attachment.php?attachmentid=2476690&stc=1&d=1388118188

Ｉpower of the NG2 completely , and then connect it to PC . Xp showed me a hint to install driver, then i specified the edited driver folder and install the driver successfully.

But, when I check the "device manager", I still have the same problem. The "android *(*(@*# " isn't there.

For me, the first thing to do is installing driver correctly.

A weired thing: during above process, I found the "android tablet *(" splashed in "device manager " interface about one second ,then disappeared.

I delete the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\U SB\Vid_0451&Pid_d00e" item group in regedit, and repeat previous steps , got same problem, again. A nightmare for me :confused:

Another thing, there is a hidded folder called ".adobe-digital-editions", and there is a .xml file:

<deviceInfo xmlns="http://ns.adobe.com/adept">
<deviceClass>Barnes & Noble Nook</deviceClass>
<deviceSerial>***************</deviceSerial>
<deviceName>NOOK</deviceName>
<deviceType>mobile</deviceType>
<version name="NOOK" value="9.3.50818" />
<fingerprint>Many Random characters</fingerprint>
</deviceInfo>

I thought it's in relation to Font_Call system, but, found nothing useful.

As I know, epub with fonts embeded can be recognized perfectly in Adobe Digital Editons on PC. Sigh, damned B&N!
[Nook Touch General] Renate:
The adobe-digital-editions file has nothing to do with anything.

The two things that you are seeing in the shot are the two UMS drives that the Nook is presenting.

That's not really material now.

Unlesss... What are the two drives showing?

You want to be looking at devmgmt.msc when X7 tries to put your Nook in fastboot mode.

Then update the drivers.
[Nook Touch General] usenothing:
Thanks for your patience.

1. I don't get what you say "What are the two drives showing?" .

When i connect NG2 to PC normally, I saw two drives : NOOK , Removable Disk.

And the "Removable Disk" cannot be opened.

2. I now have this result :

Waiting for bootloader... ok
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-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5

but, it's got so strangely :)

I repeat so many times. and every time, the same presentation：

When I connect NG2 to PC， the "android tablet" flash about 1 second in device-manager interface, so that I couldn't specify the driver path. But，the testing steps appears to move on normally(I think so because of the printed result) ?

So weired.
[Nook Touch General] jwxuan:
It's like a big progress

Thank you very mach, it's all your credit! Now it seems we have a big progress，so what's next? Do we use image and ramdisk of NOOK2's CWM to take a test? Can you give us the more details？If we have to wait for the new firmfire of NOOK G2，it certainly still need a long time！
[Nook Touch General] jwxuan:
What did you do？

When it stopped on Waiting for fastboot…，what did you do to make it go ahead，can you upload the driver？View attachment 2477273