yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] straygecko:
Make sure you have a good cable before starting. When you plug you Nook into your PC you should have a couple of drives show up like when you plug in a flash drive. If you are not getting the drives then get a cable that works before doing anything else.

Put everything from x14 and linux-usbload-ng2-noogie into one folder.

Power off your Nook

Open a command widow in the folder with x14 & stuff

Run this command:

omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage-ng2-130-stk uRamdisk-noogie

Plug your working USB cable into your Nook & your PC

Give it a while to load up everything and eventually you should have a drive named boot pop up on your PC.

Now take a backup of your Nook. You can use any disk imaging software like Acronis True Image if you have it. If not, some recommend Roadkil Diskimage as a basic freeware disk imager. If you do use Roadkil make sure you "store image" and choose the physical disk that's a little shy of 4 GB - that's your Nook. When your backup is done make sure the file it creates is around 4GB.

Now go back and read some of the previous posts on modifying your ramdisk init.rc and such.
[Nook Touch General] ErikMunoz:
Didn't work

i followed you instructions without success :( , i can see the omap devices connected for a second and then dissapear

the command windows still waiting for bootloader.

i guess im missing the omap driver ( did i?) i've never seen it
[Nook Touch General] Renate:
To everyone: If you have problems getting drivers working, please state Windows version & 32 or 64 bit.

Getting Win7 to load unsigned drivers can be tricky.

I don't have a Win7 box here to try.

You have hit upon one fact though, Windows (any version) sees a device plugged into a different USB hub port as a new and different device, even if it has a serial number.

I have a tool I use to make Windows forget that it ever saw a device.

It works fine on my computer, but I've never tested it on another.

It basically just deletes specific things under HKLM\System\CurrentControlSet\Enum\USB

There is the permission issue which makes it more work to do manually.

Still, the main problem here is getting Win7 to ask you what driver and to install that (unsigned) driver.

I've given advice to other Win7 users without being able to try it myself.

Try this:

Reboot your PC and hit F8 when rebooting to get to startup options.

Select "Disable Driver Signature Enforcement".

Get all the drivers to load correctly.

Restart your PC normally.

The logic is, the problem with this driver is that the INF file is modified and that the existing androidwinusb86.cat or androidwinusba64.cat is no longer valid.

You can try renaming them so that Windows finds no signatures.

The drivers themselves are Microsoft written USB files and will be fine once installed.

Edit:

Ok, here is that tool for clearing the registry from having seen a device.

This is unproven on other platforms, do not try any other options!

We will only use this to clear the previous detections of the OMAP3630 bootloader.

Only use these two commands exactly as typed

C:\>[b]enumusb /l /v0451 /pd00e[/b]
Vid_0451&Pid_d00e
2013-12-15 21:54 7&272036df&0&4 OMAP3630

C:\>[b]enumusb /d /v0451 /pd00e[/b]
Deleted 1 key

C:\>[b]enumusb /l /v0451 /pd00e[/b]

C:\>

It may list more than one occurrence if you have used multiple USB ports.

The timestamp will be different for you.
[Nook Touch General] ErikMunoz:
trying

if after the first command said:

VID_0451&PID_D00E

Failed to open key for read

mean that my registry is clear??

im sure i missing a driver ( omap or something? )
[Nook Touch General] Renate:
You have to be logged in as an Administrator. Are you?

Try looking for the key using regedit.
[Nook Touch General] ErikMunoz:
Still no luck

sure, i ran it as admin, and i was searching in regedit, i couldn't found it.

in the properties i press uninstall,that's the only thing that i could do

Edit:

i also have a nook simple touch ( gossamer ) and tried to do the same steps as straygecko give me , without success

the screen still on waiting for bootloader

Another noob question:

do i need to install omap driver before ? or everithing is made by omaplink.exe? if yes, do you have that driver?

sorry for my noob questions i just want to learn :)

Edit 2 :

i selected "update driver" on the omap device and choose the android_winusb.inf wich include the nook and seems like is working fine

after a while the android bootloader has been instaled but still seeing the same problem :c

Now whem i plug the the nook the pop-up of "new hardware" does't appear anymore ( is that correct?)
[Nook Touch General] Ten04031977:
I'm run cmd as Administrator.

enumusb /l - list all vids pids. In list there is

...

VID_0451&PID_D00E

2014-01-08 11:12 6&26a53c29&0&2 Port_#0002.Hub_#0003

Failed to open key for read

...

C:\!!>enumusb /d /v0451 /pd00e

Failed to clear DACL for key

Make Disable driver signing, will examine throught some time.
[Nook Touch General] Renate:
The driver for OMAP bootloader, FastBoot and ADB is all the same one.

It's the WinUSB driver from Microsoft.

The Google INF file is just to tell the system to use the WinUSB driver.

That's a generic driver that finds some USB endpoints and makes them available.

The problem is that this INF file is modified (remember, you edited it).

Therefore the signing in the CAT files is no longer valid.

In XP you can very easily say "I know that the driver is not signed, just load it."

Of course the actual driver is Microsoft and signed.

This bit about deleting registry keys is just to give you another chance to specify the driver to use.

I've played with my registry so much there, I'm not really sure what the original permissions were.

Could somebody look at HKLM\System\CurrentControlSet\Enum\USB and look under Permissions / Advamced / Effective Permissions ?

Could you do a screenshot of the permission block of that?

If you have another Android device, see about getting ADB to work with that first.

ADB sits around forever so there should be no problem updating the drivers.
[Nook Touch General] usenothing:
hi.i know a little about deleting the item in registry. The administrator privilege is not enough,it needs "system" privilege.And it could be done through google……
[Nook Touch General] straygecko:
Try right clicking on that OMAP3630, selecting Update driver and then choosing the ADB inf file with the added device information.
[Nook Touch General] ErikMunoz:
Another android
[Nook Touch General] yeahman45:
Renate i used experiment 14 and loaded cwm... i flashed glownooter but the flash does not complete and my NST rebooted
[Nook Touch General] straygecko:
How did you attempt to flash glownooter??? I thought glownooter is installed via a zip file on the SD card and yours is broken. Give us the exact steps you used including the command line showing what x-load- u-boot, uimage and uramdisk you used and what appeared on your screen step by step. Post the cwm log from /cache.
[Nook Touch General] yeahman45:
used that command to boot to cwm:

omaplink omap3_aboot.bin u-boot12.bin uImage uRam

booted fine... my zip is on my internal storage.. so in cwm i can access internal storage to flash the zip. Where is the cwm log found? there's nothing in cache/recovery
[Nook Touch General] straygecko:
Don't use aboot anymore. It doesn't properly initialize the device - that's why noogie backups / restores wouldn't work with aboot. Always use the NG2 x-load and u-boot (even on an NST) like this:

omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage uRam
[Nook Touch General] yeahman45:
see my other thread : http://xdaforums.com/showthread.php?p=49313536, x-load does not seem to work for me :(
[Nook Touch General] Renate:
For those of you who have too many versions of omaplink.exe here is X15.

It has extraordinarily trivial changes to it from X14.

If you don't know which omaplink.exe you have, go to (File) Explorer and look at Properties/Version/Build date.

For those with NST or NG1 (but not NG2), you might like a splash screen when booting over USB.

One reason is if you are doing a lot of stuff and you're never sure if it's booting off the internal memory or not.

(A failed boot will cause the Nook to continue looking for boot devices.)

If this seems all too complicated or silly, it's completely optional.

You need to duplicate some files on the boot partition.

cfg.bin => cfg_eink.bin

spl_flash.bin => spl_flash_eink.bin

wvf.bin => wvf_eink.bin

Then you need to copy bootusb.pgm to the boot partition.

The attached u-boot has been modified to the extent that it looks for bootusb.pgm instead of booting.pgm

Copying the 3 files allows for a splash screen.

The modified u-boot and the pgm file allow the splash screen to be different.
[Nook Touch General] ErikMunoz:
am i doing something wrong?

Hi, i downloaded the exp15 and tried again.

still no luck.

at this moment what i did is, plug my nook, and choose the driver for omap ( the modified android_winusb )

turn off completely and plug. Android bootloader is detected for 1 second o less.

do i need to do something else before?

thanks for your help :)
[Nook Touch General] Renate:
This thread has been going on for a while and I'm a bit unclear what success who has had with it.

I think that some of the early adopters of it got their NG2 rooted and they are off somewhere else.

The last "experiment" should be working fine with either the aboot or the x-loader methods.

The aboot method is deprecated, so you should only be using the x-loader method.

The main problem that people seem to be having is getting the drivers installed.

There is also the issue of Error 0000001F for at least one person.

It's difficult for me to get a handle on these problems.

I must USB load my Nook a dozen times a day and never see any of them.

[MENTION=5656944]ErikMunoz[/MENTION]

It's unclear what you are saying.

Do you have the whole omaplink command line (with 4 files) entered before you plug in the Nook?

It has to be sitting there saying "Waiting for bootloader..."

"Detected for one second", what do you mean?

Do you see the red LED go on?

Doesn't omaplink print stuff?
[Nook Touch General] ErikMunoz:
close to get ir

i gues im doing it wrong... ( using win 7 x64)

i tried again using a new pc and only downloaded the last files ( exp. 15 and u-boot ,xload ... posted )

so i have this files:

bootusb.pgm

omaplink

u-boot-ng2-130-stk

x-load-ng2-130-stk

i plugged my nook and install de driver.

here is where i guess i made something wrong because my driver says Samsung Android phone ( the id is the ones from the nook)

i turned off my nook, opened the omaplink and then plugged my nook

for first time i can see that the omaplink shows something to me :D

but after some time the program close it by itself

Note: i've never seen a red Led ( only the normal orange )

sorry for my noob experience and bad explanation youre a really good guys ( and patients)
[Nook Touch General] Renate:
I meant the "LEDs" on the omaplink popup.

You have a red there.

You just have not written a complete command line.

Depending on what files you are trying to load the command line should be something like:

omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage-noogie uRamdisk-noogie

Since you apparently have the bootloader WinUSB driver installed you should be all set.

To anyone reporting either success or failure, please specify OS (XP, W7, W8) and bits (32, 64).

Also please quote the command line that you are calling.
[Nook Touch General] ErikMunoz:
ok im scared

i used this line

omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage-ng2-130-stk uRamdisk-noogie

now my nook is dead D: seems like a poweroff and when i plug my nook the pc show an usb error :/ my nook doesn't turn on

Edit:

i removed the battery and my nook is alive again :D ( but shows 0% battery , it was 97%)

still showing the same error, even if i choose only x-load or u-boot etc.

ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 0
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 0
CRC1: EF3EBF13, CRC2: 00000000
Sending image file x-load-ng2-130-stk.bin, 16692 bytes... ok
Error 0000001F reading response, read 0 bytes

Feeling frustrated jeje :P
[Nook Touch General] usenothing:
Hi,Renate:

I am a little busy recently,and not convenient to go on with this thread.

I don't think the "root" is done completely, because the virtual "sd-card" cannot be recognized by the third android-device manager.

I didn't test the last omaplink,maybe will try it this Saturday with enough time. And I will post the test result at that time.

Thanks for your continuous attention on this "rooting NG2" thread, and for your works.
[Nook Touch General] Renate:
[MENTION=5656944]ErikMunoz[/MENTION] Yes, it is frustrating.

I can't replicate the errors so it's difficult to fix them.

You say that your battery is reading zero now?

Make sure that the battery is charged before trying to USB load it.

If you have a voltmeter, check the battery.

Just as a test try using just the a-boot.bin to see if it gets past the starting point.

omaplink omap3_aboot.bin

[MENTION=4597750]usenothing[/MENTION] Three device managers?

I would have thought that one would be enough.

If you can ADB and you get a # for prompt, you are rooted.

/sdcard is not a mounted device, therefore it's a link.

Maybe your third app can't deal with that.

Tell me what this says:

ls -l /sdcard

To everyone, although I continually release new versions of omaplink.exe there is nothing to be gained by trying the latest one if you've already got one to work once.

For most people, omaplink.exe is a way to root, not a way of life.

(If you are constantly trying out new images and ramdisks, omaplink.exe can be a convenient tool.)
[Nook Touch General] ErikMunoz:
it show me 0% but when i restarted goes back to the normal state ( solved )

do you have omap3_aboot.bin file? i couldn't found it in the previous post.

regards.

Edit:

i found the file, this is what i got ( see image ):

now i tried with this command

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

this is what i got:

in this moment my nook seems like turned off, i don't know if is doing something i guess i need to remove the battery again to turn it on again.
[Nook Touch General] headala:
Thanks to all of you who are working so hard on this. I look forward to the results! I'm happy to help beta test when the time is right (Nook w/ Glowlight, W8.1 Pro 64).
[Nook Touch General] Renate:
[MENTION=5656944]ErikMunoz[/MENTION] Well, the USB interface seems to be working.

Go back to trying to use x-loaders and u-boots.

Maybe you have a bad copy of x-loader or something that is killing the USB?

[MENTION=593965]headala[/MENTION] The time is now. Some have rooted their NG2s with this already.
[Nook Touch General] ErikMunoz:
same with NST

i've downloaded the latest files for both models ( Gossamer and avocet ) from http://xdaforums.com/showpost.php?p=49173298&postcount=220, with same results ( win 7 x64)

this is weird pff ... maybe my problem is relatet with the " Samsung android phone" , i don't know why is showing my devices as samsung.

in my other Pc both nooks are detected as Android device but still undetected by omaplink so i'll continue using the "samsung" one.

is there some extra things that i could do to know what's happening?

i also have a linux machine with Xubuntu 13.10 ( with anything installed )
[Nook Touch General] Renate:
Well, I'm confused with this Samsung driver stuff.

When does it show this?

See, the bootloader for the Nook is a TI OMAP bootloader and it's totally different, so it can't be showing it then, even if you did load some Samsung driver.

If you ever see something in Device Manager that says "Samsung", click on "Update Driver" and select the extras\google\usb_driver\android_winusb.inf that you modified.
[Nook Touch General] usenothing:
Hi,Renate：

I tried to run "ls -l /sdcard" , with nothing got.

Like this ——

# ls -l /sdcard
ls -l /sdcard

As I know, "ls -l" will show us all the details about the files and folders. I don't know what happened. Is it that the "sdcard" is empty essentially?
[Nook Touch General] Renate:
It looks like they create /sdcard in init.rc like the other nooks do but don't have that linked to anywhere.

export EXTERNAL_STORAGE /sdcard
export INTERNAL_STORAGE /media
export BN_PURCHASED_CONTENT /data/media

This will probably cause problems with many apps that want to store things on /sdcard

As I've said already, the best solution is to make /data on mmcblk1p8 like the older nooks and make /sdcard on mmcblk1p9

The relative sizes depends on what you want to do.
[Nook Touch General] ErikMunoz:
Smsung solved

i've deleted all samsung trail of my computer(drivers and registry) and now i can see my device as "Android Device" and " Android Bootloader interface" which is good, i've tried again the command getting the same results:

Error 0000001F reading response, read 0 bytes

i was hoping the driver issue could solve it.
[Nook Touch General] Renate:
I really think that there is something about x-loader that does not agree with your Nook.

Run omaplink with just one filename.

Try all the files that have aboot in their name and all the files that have x-loader in their name.

I don't believe that I've heard it confirmed from any NG2 loader that x-loader has worked.

The original success on NG2 was with aboot.

Unrelated, just for your reference, here is the complete partitioning scheme:

Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
128 heads, 32 sectors/track, 1864 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- ---- ------------- --------
Total 1 1864 3,909,091,328
MBR 1 16,384
mmcblk0p1 vfat 0c 1+ 38 79,675,392 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 1864 3,613,392,896
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 539 532,676,608 /media
mmcblk0p7 ext3 83 540 659 251,658,240 /cache
mmcblk0p8 ext3 83 660 791 276,824,064 ???
mmcblk0p9 ext3 83 792 1864 2,250,244,096 /data
[Nook Touch General] ErikMunoz:
got it

i've followed the instruccions of here http://bbs.cooldu.net/forum.php?mod=viewthread&tid=680 and now i got Fastboot access, but google translator is not good whit chinesse :P , i don't know hot to edit the uRamdisk.

Now i'm waiting for ADB but i don't know how to continue.

Why my devices is showed as Gossamer?

Note:

The files that i used with a-boot seems like old files from here.
[Nook Touch General] Renate:
Try replacing the last two files with the noogie image and ramdisk.

When it says "Waiting for ADB..." don't worry, just see if your PC mounted a disk from your Nook.
[Nook Touch General] usenothing:
hi.

500 M is enough for me, and i donot have the need to adjust the "500 M" space.

I just want to know how to achieve "the best choice" you mentioned. Is it the code you quoted in this relpy？
[Nook Touch General] Renate:
The snippet of code that I posted above is from the NG2 init.rc in uRamdisk.

It just was meant to show the intended storage usage.

Your Nook should run similarly to a Nook Touch without any SD card inserted.

I'm not sure if any apps dislike having no SD card.

They have to store their stuff in the corresponding /data/data/com.example.app/ directory.

It looks right now that there are some problems using the x-loader method with the NG2.

If an NG2 owner has gotten x-loader to work with either Linux or Windows we'd like to know.

For now, use the omap3_aboot.bin with u-boot

The later versions of omaplink.exe support both aboot and x-loader methods

There are 3 possible things to boot, noogie, Clockwork Mod or stock Nook.

As far as I know, only noogie has been successfully booted on a NG2.

If you are an NG2 owner and just want to get it rooted, follow the instructions in this thread using omap3_aboot.bin, u-boot, noogie_image, noogie_ramdisk.

Then modify uRamdisk on the NG2 /boot partition using bootutil.exe and a Unix-style editor on init.rc

straygecko has said that he will eventually be working on trying to get x-loader running better on NG2.
[Nook Touch General] ErikMunoz:
sure

it mounts a boot device...
[Nook Touch General] Renate:
So, copy uRamdisk over to your PC.

Follow the instructions here: http://xdaforums.com/showthread.php?p=49070213#post49070213
[Nook Touch General] ErikMunoz:
Finally i got it :D

got it!! now i have ADB enabled

thank you so much!
[Nook Touch General] Renate:
Great!

Could you copy/paste the results of this command:

adb shell mount

I think I'm confused about what is normally mounted in the NG2.

I didn't see any mention of mmcblk0p6 or mmcblk0p8 in the previous posts from others.
[Nook Touch General] usenothing:
I achieved "running adb" two weeks ago.

1. The result of "mount" :

mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmas
k=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=rem
ount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p9 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=contin
ue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=conti
nue,data=ordered 0 0

2.You said we have three ways to boot.

If ,if we want to boot with CWM mode, what arguments should I use?

I tried

omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage-ng2-130-stk uRamdisk-noogie

one week about ago, and it didn't work (I cannot remember the error hint,sorry) .
[Nook Touch General] Renate:
So that dump of mount is what you get on your NG2 when it's happily running the stock reader software?

I'm confused.

When you have your NG2 connected over USB do you see two removable disks on your PC?

What is on these disks? What is the volume label?

I can boot up CWM using bootloader methods easily.

The problem is that the NG2 has a different screen resolution and needs a different CWM.

Without the screen working correctly, all you get out of using CWM is the use of ADB.

Neither straygecko or I have a NG2, so in some ways we've been lucky to get this far.
[Nook Touch General] usenothing:
1.

1.1

When I connect my Nook to PC with USB, I can only open one "removable disk" ('J' in my PC), although I can see another "removable disk" in "my computer"( 'K' in my PC, it's called 'boot' and can be opened in the process of rooting, not now).

In 'J', I can see all my books I have transfered.

1.2

When Iconnect my Nook to PC with usb cable, it's on "USB mode" defaultly . At this time, "adb" works finely, but, I cannot read any books with the Nook hint——You may now safely move files from your PC to your NOOK: please properly eject NOOK from your computer to avoid file transfer problems.

2.

Thanks you and straygecko for all your work. I know we are lucky to get all this ,but ,we should mostly give the credit to

your works ,not "luck".
[Nook Touch General] Renate:
Oh, alright, silly me.

mmcblk0p6 is mounted on /media by vold.

When you are using ADB over USB, the UMS kicks in and unmounts /media from the Nook.

vold.conf does have stuff in it for mounting a (non-existent) SD card on /sdcard.

So the only mystery is what mmcblk0p8 is being saved for?