yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
No, that's what I expected.

The partitioning worked fine

You had already bashed the boot partition.

Now try:

mkdir /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
ls -l /rom
[Nook Touch General] srgarfi:
Looks like there was already a /rom

D:\nook_root\adbshell>adb shell
~ # mkdir /rom
mkdir /rom
mkdir: can't create directory '/rom': File exists
~ # mount -t vfat /dev/block/mmcblk0p2 /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
mount: mounting /dev/block/mmcblk0p2 on /rom failed: Device or resource busy
~ # ls -l /rom
ls -l /rom
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #
[Nook Touch General] Renate:
Hmm, I thought of that at the last moment.

mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff
[Nook Touch General] srgarfi:
yes, works, but I don't get it?

~ # mkdir /stuff
mkdir /stuff
~ # mount -t vfat /dev/block/mmcblk0p2 /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
~ # ls -l /stuff
ls -l /stuff
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #

in the meantime I booted noogie and did a backup of the semibricked nook just in case.... =)

Now I'll write CWM to the SD and boot again
[Nook Touch General] Renate:
That means that the partitioning is correct and that your /rom is intact.

Make a good backup of your personalized stuff:

adb pull /stuff

Now you have to fix up the boot partition.

I'd probably try to install the factory.zip

mkdir /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
ls -l /fact

adb pull /fact/factory.zip
adb pull /fact/rombackup.zip

Then copy factory.zip to the external SD card and do a CWR update with that.
[Nook Touch General] srgarfi:
I now have an image copied with DiskImage and a devconf folder with my stuff =)

But

~ # mkdir /fact
mkdir /fact
~ # mount -t ext2 /dev/block/mmcblk0p3 /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
mount: mounting /dev/block/mmcblk0p3 on /fact failed: Invalid argument
[Nook Touch General] Renate:
There's two possibilities there, either the Glow has a bit different partition sizes than the touch

or else the formatting of your factory partition got bashed.

In any case, you are lucky to have backed up all your /rom

You could take someone elses full Glow backup, restore that, then restore your /rom

Check to see if the other partitions are good.

Just mount them with vfat, ext2, ext3, as the case may be.
[Nook Touch General] srgarfi:
Lucky me!

~ # mount -t vfat /dev/block/mmcblk0p1 /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
mount: mounting /dev/block/mmcblk0p1 on /boot failed: Invalid argument
~ # mount -t ext2 /dev/block/mmcblk0p5 /system
mount -t ext2 /dev/block/mmcblk0p5 /system
mount: mounting /dev/block/mmcblk0p5 on /system failed: Invalid argument
~ # mount -t vfat /dev/block/mmcblk0p6 /media
mount -t vfat /dev/block/mmcblk0p6 /media
mount: mounting /dev/block/mmcblk0p6 on /media failed: No such file or directory

~ # mount -t ext3 /dev/block/mmcblk0p7 /cache
mount -t ext3 /dev/block/mmcblk0p7 /cache
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
~ # mount -t ext3 /dev/block/mmcblk0p8 /data
mount -t ext3 /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
~ #

Someone willing to share a full backup of his Glow? I promise I'll overwrite /rom with my own data :fingers-crossed:
[Nook Touch General] Renate:
If somebody with a Nook Glow would simply do an fdisk -l we could see if the partitioning is right.
[Nook Touch General] speedman2202:
i guess he need partitioning info for NSTG , then he can just replace from any full back up or his incomplete backup the boot partition files , factory partition and rom partition ..... then the nook will work "like my case" , and thx to Renate , she helped me in that

just try found an full backup or do what i told u , but if u want to exchange files between ur nook and other backup image , u boot with noogie image for ur nook and burn ur backup on SD card , and try open them by any linux OS and copy files between them

good luck :)
[Nook Touch General] srgarfi:
posted a request in the community forums

http://bookclubs.barnesandnoble.com...ormation-for-Nook-Glowlight/m-p/1367570#M2787

let's see what comes out....

(going offline now, must have some sleep it's 1:30 am here and tomorrow I start at 7)

Thank you all!
[Nook Touch General] speedman2202:
hey , dont refer to ur nook device that may ur device get deactive by BN , try just here or dont say any info about ur device serial

anyway here many pple can help u , just be patient
[Nook Touch General] Renate:
If you get bored waiting you can always just format the partitions that aren't mountable.

The vfat and ext2 ones are easy, but the ext3 formatter seems to be missing out of busybox and friends.

If you get all 7 (excluding the extended #4 partition) mountable then you can try restoring from the 1.1.5 factory.zip:

http://xdaforums.com/showpost.php?p=25557213&postcount=10
[Nook Touch General] srgarfi:
I'm leaving on sunday for a 1 week shift, and I intended to take the nook with me. Now that I've realized it wont' happen, I can wait another week and see if someone shares the partition info.
[Nook Touch General] srgarfi:
Back from work, nobody has yet posted the info :crying:
[Nook Touch General] speedman2202:
i suggest u that go to glownooter thread and read all posts and then pick some members and send them pm's and ask them send u their NST glowwihite partioning info .... and send them the method also becoz may all is a beginner

that's my idea for now ..... good luck
[Nook Touch General] srgarfi:
thanks speedman2202, I did as you suggested.

Let's hope someone answers my call...

I also posted on Reddit, B&N forums, Mobileread and a few other places where I saw NSTG actvity, no luck yet :(
[Nook Touch General] stilger:
Here ya go... From my NSTG.

# busybox fdisk -l /dev/block/mmcblk0

busybox fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 2000 MB, 2000683008 bytes

128 heads, 32 sectors/track, 954 cylinders

Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)

/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)

/dev/block/mmcblk0p3 47 141 194560 83 Linux

/dev/block/mmcblk0p4 142 926 1607680 5 Extended

/dev/block/mmcblk0p5 142 285 294896 83 Linux

/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)

/dev/block/mmcblk0p7 406 525 245744 83 Linux

/dev/block/mmcblk0p8 526 926 821232 83 Linux
[Nook Touch General] srgarfi:
Thanks stilger !!

To mee it looks the same as the partition of the NST Renate NST sent....but with a different number of cylinders.

So I modified Renate's sh and tried this on my NSTG, and no it did not boot: Install Failed screen again.

Most probably something went wrong because fdisk -l returns nothing.
[Nook Touch General] srgarfi:
Did it again "old school", I mean typing commands in the adb shell prompt and this is the result:

D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
~ #

But the nook won't boot: install failed.

I'm running out of ideas here....

Perhaps the best option would be to write the full image of a working NSTG and overwrite /rom with my salvaged information?

thanks everyone.
[Nook Touch General] Renate:
So, what we now know:

The Glow uses the exact same partition sizes as the Touch.

The Glow uses a slightly bigger capacity internal SD card (which make absolutely no difference).

Since you've already tried mounting all the partitions, the answer is that the formatting of those partitions has been bashed.

As before, you have two options:

1) Get a full Glow backup from somebody, install with Noogie, then overwrite the /ram partition with your saved personal config.

2) Correctly format all the partitions that are not mountable and update using the CWR and the factory.zip
[Nook Touch General] srgarfi:
How would I do that?

Ina previous message you said:

mkdir /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
adb pull /fact/factory.zip
adb pull /fact/rombackup.zip

then it would be as easy as applying factory.zip from CWR.

Bu tI don't know how to correctly format /dev/block/mmcblk0p3
[Nook Touch General] Renate:
Either mmcblk0p3 is ok, in which case you can pull the stuff off it

or else it is bashed and you can format it to clean things up.

Somebody posted factory.zip here:

http://xdaforums.com/showpost.php?p=25557213&postcount=10

Only format partitions that are broken and can't be mounted.

mkfs.vfat -n boot /dev/block/mmcblk1p1
mkfs.vfat -n rom /dev/block/mmcblk1p2
mkfs.ext2 -L factory /dev/block/mmcblk1p3
mkfs.ext2 -L system /dev/block/mmcblk1p5
mkfs.vfat -n media /dev/block/mmcblk1p6

Partitions mmcblk1p6 & mmcblk1p7 are ext3 types.

I haven't found a good way to format them.

Partition Wizard can format ext3 but it will bash your partition tables.

You can try that then redo the partitioning afterwards.
[Nook Touch General] srgarfi:
I don't understand it: does that mean that DeanGibson extracted factory.zip from a NSTG but Glowlight won't work?

Or is it that he used a uRamdisk that disabled Glowlight but allowed to extract factory.zip?

I wouldn't want to loose the Glowlight ;)
[Nook Touch General] Renate:
Huh? That factory.zip mentioned is out of a Glow.
[Nook Touch General] srgarfi:
I installed it out of the sdcard in CWM, and everything went fine. But the result is the same: the nook won't boot, it displays the "install failed" screen still. I tried also rebooting into recovery, and nothing.

If I can't find an image to install I think I'll purchase another unit to try and recover this brick.....
[Nook Touch General] Renate:
You haven't convinced me yet that all your partitions are formatted correctly and mountable.

If everything is not correct it will not boot.
[Nook Touch General] srgarfi:
Yes, you're right, partitions formatted except for 6, 7 and 8 (?)

/tmp # mount -t vfat /dev/block/mmcblk0p6 /media
mount -t vfat /dev/block/mmcblk0p6 /media
mount: mounting /dev/block/mmcblk0p6 on /media failed: No such file or directory

/tmp # mount -t ext3 /dev/block/mmcblk0p7 /cache
mount -t ext3 /dev/block/mmcblk0p7 /cache
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
/tmp # mount -t ext3 /dev/block/mmcblk0p8 /data
mount -t ext3 /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
/tmp #

Was trying to speed things up :silly:

You said:

Partition Wizard can format ext3 but it will bash your partition tables.

You can try that then redo the partitioning afterwards.

Should I format the whole thing as ext3 in Partition Wizard? And then proceed in ADB to partition and format all the other partitions?
[Nook Touch General] srgarfi:
Stupid move, after installing factory.zip in CWR the nook is stuck in "Rebooting...." more than 15 minutes, and the buttons don't seem to affect it.
[Nook Touch General] Renate:
Well, you've got beyond this point, but if somebody wants to check their partitions,

then they can put the attached zip on the SD card and run it as an update on CWR.

It will either fail on an assert or tell you that all partitions are mountable.

You format a single partition, you can't format "the whole thing".

You can access the whole internal SD card through noogie and use

Linux or Windows tools to format the individual partitions.
[Nook Touch General] srgarfi:
Rebooted into CWR and executed checkfs:

assert failed: mount ("ext3". "/dev/block/mmcblk0p7". "/tmp")
E: Error in /sdcard/checkfs.zip
(Status 7)
Installation aborted

I'll try to format p7 with partition wizard....
[Nook Touch General] Renate:
p8 needs it too.
[Nook Touch General] srgarfi:
I'm completely lost here: all I can see in Partition Wizard are two partitions

No name, 75.98 MB Capacity, 9.63 MB Used, 66.35 MB Unused, FAT32 FileSystem, Primary Type, Active Status

No name, 1.75 GB Capacity, 0 B Used, 1.75 GB Unused, Unallocated File System, Logical Type, None Status

To create new partitions I must delete these two, but they will appear again when applying changes.

I can't see or create p7 nor p8, and thus I can't format them in ext3 to get back to CWR and recreate the rest of the partitions....
[Nook Touch General] Renate:
Why did you format everything?

Now you have to restore the /rom partition.

I don't know what happened between the time you did fdisk and looked at it with PW.

In Windows you can also look at the internal SD card with the stock Windows Disk Management.

You won't be able to do a lot, but you should see the 7 partitions.
[Nook Touch General] srgarfi:
I did format everything because I was no longer sure about anything :)

In Windows Disk Management I can see 7 partitions, but not in PW (v7.5)

I can build a Linux Mint box in a couple of hours, but I wouldn't know how to mount the nook and have access to format p7 and p8....
[Nook Touch General] Renate:
What you reported from PartWiz was the layout of the noogie on the external SD card.

You're looking at the wrong thing somehow.
[Nook Touch General] srgarfi:
I think that was the layout of the CWR card, the layout of the noogie looks like

no name Partition, 1.82 GB Capacity, 1.82 GB Used, 0 B Unused, Bad Disk FileSystem, Logical Type, None Status.

Neither booting from CWR nor noogie I can see the internal nook partitions, that's true. But I don't knwo why....
[Nook Touch General] Renate:
Time to look again with fdisk -l

Something is screwed up.
[Nook Touch General] srgarfi:
Everything is still there.....could it be an error with usb drivers in windows?

I'll have a linux mint box with gparted in a while....

formatted p7 and p8 in gparted to ext3 successfully.

In gparted I can see all mounted partitions (boot, rom, factory, system, media) now I need to mount p7 and p8 and isolate the error with p6 before applying again factory.zip from CWR, isn't it?
[Nook Touch General] Renate:
I kind of doubt it.

The driver is just the stock Windows one for USB Mass Storage.

Actually, I think of the two disks that noogie serves, the first is the internal SD card and the second doesn't have anything attached.

How many new drive letters do you have and what does a dir show?

How about a screenshot of Disk Management and PartWiz?
[Nook Touch General] srgarfi:
No driver letters, but there's a 2 GB disk with 8 partitions in it as I see in Disk Management.

PartWiz shows a Disk 2 drive with 2 no name partitions (as in previous posts).

Sorry I don't know how to upload images here (or should I upload them to imgur and place a link?)

And then there's a USB device called boot with a yellow sign in device administration: it could not be started and the name is Ebook disk.

As for the gparted progress:

D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
~ # mount -t ext3 /dev/block/mmcblk0p7 /cache
mount -t ext3 /dev/block/mmcblk0p7 /cache
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Device or resource busy
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 15 00:14 boot
drwxr-xr-x 4 root root 1024 Jan 15 00:14 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
-rw-r--r-- 1 root root 2244 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2120 Jan 15 00:14 dev
drwxr-xr-x 2 root root 0 Jan 15 00:14 emmc
drwxr-xr-x 3 root root 0 Jan 15 00:14 etc
drwxr-xr-x 2 root root 0 Jan 15 00:14 factory
-rwxr-x--- 1 root root 94400 Jan 1 1970 init
-rwxr-x--- 1 root root 2018 Jan 1 1970 init.rc
dr-xr-xr-x 48 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 512 Jan 1 1970 rom
drwx------ 2 root root 0 Oct 29 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 15 00:14 sd-ext
drwxr-xr-x 2 root root 0 Jan 15 00:14 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 15 00:14 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4078 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.zoom2.rc
~ # mount -t ext3 /dev/block/mmcblk0p8 /data
mount -t ext3 /dev/block/mmcblk0p8 /data
~ # mount -t vfat /dev/block/mmcblk0p6 /media
mount -t vfat /dev/block/mmcblk0p6 /media
mount: mounting /dev/block/mmcblk0p6 on /media failed: No such file or directory

~ # mkdir media
mkdir media
~ # mount -t vfat /dev/block/mmcblk0p6 /media
mount -t vfat /dev/block/mmcblk0p6 /media
~ # ls
ls
boot init sd-ext
cache init.rc sdcard
data media sys
default.prop proc system
dev res tmp
emmc rom ueventd.goldfish.rc
etc root ueventd.rc
factory sbin ueventd.zoom2.rc
~ #
D:\nook_root\adbshell>

Everything seems to be in place now, right?

Should I try and apply factory.zip?
[Nook Touch General] Renate:
Well, the warning symbol on the eBook device is probably significant.

Is there any info on what the error is?

The partition that you are seeing on PartWiz is the noogie.

If you've got p7 & p8 fixed now and you've restored /ram, you can give it a try.
[Nook Touch General] speedman2202:
ok , i suggest u have a full backup from beginning to play in nook to keep ur original data save ..... sec ..... u must check all partitions if they mountable or not then mount the un mountable partitions .... then check clusters , size ...etc with the fdisk partition table then copy files from ur original back up (check if file is correct or damage first) and u must take care about factory partition and rom cuz they have the unique info about ur nook (Mac , serial , model....etc) and try do update ur nook files by download update from BN and then unrar ur file then compress it with zip extension then boot up with CWR and install this update ur nook and then try start up ur nook ... and if didnt start .... plug ur usb cable into ur computer to charge ur nook cuz may ur battery too low to start up (happened with me) then it will works as i expected :)

good luck
[Nook Touch General] srgarfi:
No detailed info, just a standard "this device can't be initiated (code 10)" message. The controller is the general 2006 Microsoft.

I've just pushed /devconf to /rom/devconf, installed factory.zip from CWR and reboot.......and the nook displays the CWR Rebooting messge but nothing happens.

If I reboot into CWR the name of the device has changed and everything seems to be ok:

D:\nook_root\adbshell>adb devices
List of devices attached
11223344556677 recovery

D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
~ #
~ # du -c -s -h
du -c -s -h
4.7M .
4.7M total
~ #

:eek:

(need to have some sleep, tomorrow I have a trip to the outback. All day offline...)

PS: checkfs result "All partitions are formatted and mountable"

Speedman2202 I can barely follow you, but since the nook does not yet boot a backup would be useless isn't it?

Download update from B&N? I installaed a 1.1.5 factory.zip, isn't it the last version?
[Nook Touch General] Renate:
Look what's on the p1 (/boot).

With just p1 correct and everything else wrong you should be able to get it to say "booting up" at least.
[Nook Touch General] srgarfi:
/boot is empty :confused:
[Nook Touch General] Renate:
When you tried to execute the patch factory-1_1_5.zip did you see any error messages?

Try executing the factory-1_1_5.zip again carefully noting any error messages.

Try copying a file to /boot and see if the copy works.
[Nook Touch General] srgarfi:
factory.zip was installed without any warnings nor errors.

I have a /boot copy and I tried to push it

D:\nook_root\adbshell>adb push D:\nook_root\boot /boot
push: D:\nook_root\boot/wvf.bin -> /boot/wvf.bin
push: D:\nook_root\boot/white.pgm -> /boot/white.pgm
push: D:\nook_root\boot/uRecRam -> /boot/uRecRam
push: D:\nook_root\boot/uRecImg -> /boot/uRecImg
push: D:\nook_root\boot/uRamdisk -> /boot/uRamdisk
push: D:\nook_root\boot/uImage -> /boot/uImage
push: D:\nook_root\boot/u-boot.bin -> /boot/u-boot.bin
push: D:\nook_root\boot/romrestore.zip -> /boot/romrestore.zip
push: D:\nook_root\boot/pic.pgm -> /boot/pic.pgm
push: D:\nook_root\boot/MLO -> /boot/MLO
push: D:\nook_root\boot/flash_spl.bin -> /boot/flash_spl.bin
push: D:\nook_root\boot/dead.pgm -> /boot/dead.pgm
push: D:\nook_root\boot/charging3.pgm -> /boot/charging3.pgm
push: D:\nook_root\boot/charging2.pgm -> /boot/charging2.pgm
push: D:\nook_root\boot/charging1.pgm -> /boot/charging1.pgm
push: D:\nook_root\boot/charging0.pgm -> /boot/charging0.pgm
push: D:\nook_root\boot/cfg.bin -> /boot/cfg.bin
push: D:\nook_root\boot/booting.pgm -> /boot/booting.pgm
push: D:\nook_root\boot/black.pgm -> /boot/black.pgm
19 files pushed. 0 files skipped.
4638 KB/s (10227445 bytes in 2.153s)

D:\nook_root\adbshell>adb shell
~ # ls
ls
boot init sdcard
cache init.rc sys
data proc system
default.prop res tmp
dev rom ueventd.goldfish.rc
emmc root ueventd.rc
etc sbin ueventd.zoom2.rc
factory sd-ext
~ # ls boot
ls boot
MLO charging0.pgm dead.pgm u-boot.bin uRecRam
black.pgm charging1.pgm flash_spl.bin uImage white.pgm
booting.pgm charging2.pgm pic.pgm uRamdisk wvf.bin
cfg.bin charging3.pgm romrestore.zip uRecImg
~ #

but when I booted nothing happened. The I booted again in CWR and ls -al /boot and to my surprise it was empty !

(must.go.to.sleep.now)
[Nook Touch General] Renate:
Double check what you have mounted on "boot" with mount.
[Nook Touch General] srgarfi:
off to work

~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/block/mmcblk0p2 on /rom type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0
000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,errors=remount-ro)
/dev/block/mmcblk0p7 on /cache type ext3 (rw,nodev,noatime,nodiratime,errors=con
tinue,data=ordered)
/dev/block/mmcblk0p1 on /boot type vfat (rw,fmask=0000,dmask=0000,allow_utime=00
22,codepage=cp437,iocharset=iso8859-1,errors=remount-ro)
/dev/block/mmcblk0p6 on /media type vfat (rw,fmask=0000,dmask=0000,allow_utime=0
022,codepage=cp437,iocharset=iso8859-1,errors=remount-ro)
/dev/block/mmcblk0p8 on /data type ext3 (rw,errors=continue,data=ordered)
/dev/block/mmcblk0p3 on /factory type ext2 (rw,errors=continue)
/dev/block/mmcblk0p5 on /system type ext2 (rw,errors=continue)
~ #