yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] dorb87:
So I did the first one, the install looked like it might have worked. But now it won't boot into recovery or fastboot (while holding the n button).

Fastboot is now on left side volume down and power on. Different device ID showing now in Fastboot. Should I reflash recovery and give it a go?

PS C:\Users\hcors\Downloads> fastboot devices

12345 fastboot

More edit: I reflashed Recovery, but it won't load when sent through Fastboot Reboot Recovery.

It loads the screen to have the splash page of NN recovery, but ADB isn't up, nor does Windows see those 7 drives pop up asking to format them like it did previously.
[Nook Touch General] Renate:
If the buttons that affect booting have changed then the update must have changed uboot.

Where did you get that update? (Link please.)

You can unzip the update on your desktop and see if there is a u-boot in there.

NeoNoogie doesn't use the internal flash for anything, so it really should run fine as long as you can boot into it.

Reboot commands don't necessarily work correctly with arguments like they should.

Reboot recovery (or bootloader or fastboot) just makes a notation what to do the next boot and hope that the u-boot speaks the same language.

If you are at fastboot, fastboot boot <image> is the most direct way to do something.

If you can get to fastboot, you should be able to run Neo Noogie.

It seems like your main image has a problem or has a problem with the state of the internal flash.

It's hard to guess from here.

If you know what you're looking for, you can boot into Neo Noogie, mount the various partitions and see if they are sane.

(Too bad you don't have a full physical backup, this would be a piece of cake.)
[Nook Touch General] dorb87:
The update is from that link you had posted earlier https://su.barnesandnoble.com/nook/piper/5.0/piper/0.118/update.zip

There is a uboot in there, XDA forums would not let me attach it. I can post it to a file site if you'd like, let me know.

So to be more specific, it will try and load the Neo Noogie from that command, the screen clears, and the Neo Noogie page comes onto the screen. But ADB doesn't load, and the multiples drives Windows was finding and asking to format (which I never did), aren't doing that. So it's like it's partially loading Neo Noogie, but not far enough to load ADB.

If I load it via fastboot boot nn.img, it does the same. Loads the words Neo Noogie, Built on December 16, and that. But no background ADB.

Re-downloaded NN img a couple times now to make sure it wasn't the file at issue.
[Nook Touch General] Renate:
ARRRRRRRRRGGGGGGHHHHHH!!!!!!!!

That was posted in a thread that started three years ago for the "new Nook Glow Plus", that is BNRV510, a/k/a "Glow2".

B&N reused the stupid name.

The 7.8" is NOT piper, it is BNRV700, Glow4!

I didn't mean for you to take the *update* from there. You said that you had one for the 7.8"

Did you have a real update for *your* device?

What's it called? What's the link?

Is this how the whole problem started?

You've mashed the u-boot, which has the critical DCD for the Glow4, they are not at all compatible.

If you can find the *correct* u-boot you can try to flash it with fastboot (presuming that the wrong u-boot can still do stuff).

C:\> fastboot flashing unlock
C:\> fastboot flashing unlock_critical
C:\> fastboot flashing get_unlock_ability
C:\> fastboot flash bootloader <mycorrectuboot>
[Nook Touch General] dorb87:
Oh no, the Glowlight Plus name coming back to be reused got me. I saw Glowlight plus and it didn't dawn on me there was another Glowlight Plus in years past. If I had another Nook 7.8" in hand, would this be fixable still? And no, I hadn't done anything with that ZIP prior to tonight. The initial problem was I did a factory reset from within Nook OS, and I had that TWRP installed that didn't seem to work for either of us. I think that is what caused it initially.

All three of those commands failed, FYI.

PS C:\Users\hcors\Downloads> fastboot flashing unlock

FAILED (remote: '')

fastboot: error: Command failed

PS C:\Users\hcors\Downloads> fastboot flashing unlock_critical

FAILED (remote: '')

fastboot: error: Command failed

PS C:\Users\hcors\Downloads> fastboot flashing get_unlock_ability

FAILED (remote: '')
[Nook Touch General] Renate:
Ok, did you get the special Neo Noogie?

For now, just see if you can fastboot boot it like before and that ADB works, ok?
[Nook Touch General] dorb87:
It is booted, and I have ADB access!
[Nook Touch General] Renate:
Ok, do this carefully (using the special nnglow4).

# dd if=/uboot of=/dev/block/mmcblk0 seek=2
# dd if=/p1 of=/dev/block/mmcblk0p1
# reboot

Be careful, you're writing raw to the internal flash.

Notice that it's mmcblk0 and mmcblk0p1 and don't forget seek!

Cross your fingers.
[Nook Touch General] dorb87:
Hey, I crossed my fingers, but no luck.

PS C:\Users\hcors\Downloads> adb shell

# dd if=/uboot of=/dev/block/mmcblk0 seek=2

/uboot: cannot open for read: No such file or directory
[Nook Touch General] Renate:
My bad. I called it "uboot4".
[Nook Touch General] dorb87:
Commands completed, and now rebooted to the NN recovery again. ADB still up.

#

# dd if=/uboot4 of=/dev/block/mmcblk0 seek=2

1022+0 records in

1022+0 records out

523264 bytes transferred in 0.035 secs (14950400 bytes/sec)

# dd if=/p1 of=/dev/block/mmcblk0p1

12224+0 records in

12224+0 records out

6258688 bytes transferred in 0.609 secs (10276991 bytes/sec)

# reboot
[Nook Touch General] Renate:
Huh? We want it to boot to the main image now.

Are you letting it boot normally? Try a full power down/up.

Still not working?

fastboot boot special-noogie

adb pull p1

fastboot boot p1
[Nook Touch General] dorb87:
From a plain boot, it boots to NN still. Performed: adb pull p1

fastboot boot p1

AND IT BOOTED! Interestingly enough, it booted the load screen at a 6" size and then once booted filled it. :) How would I go about getting that P1 to boot by default?

Edit: Also my fastboot device ID is back to normal and the normal buttons to get into fastboot are back now.
[Nook Touch General] Renate:
Try doing a normal (on screen dialog) power down or reboot.

It should reset things so that it comes up all by itself.
[Nook Touch General] dorb87:
Tried both ways, and while it shuts down normally, once it tries to boot it loads NN. Honestly if I have to boot from fastboot every time I power on, thats fine by me. I can't believe it's working again :D

Bluetooth settings seem to be no more. Displays a blank page under there. Think they may be gone until I can find an update.zip for this actual device? USB file storage on the OS is also not functioning. No biggie, though I can work around.

Edit: Wifi doesn't seem to work either. I better get looking for a update.zip, methinks.
[Nook Touch General] Renate:
Woah there, pardner, slow down.

We just dug you out of a hole.

Lemme see if you bashed your NTX hwcfg.

Do you have ADB working on your normal image?

# dd if=/dev/block/mmcblk0 of=/sdcard/hwcfg skip=1024 count=1
C:\>adb pull /sdcard/hwcfg

Then put it somewhere that I can see it (there's no personal data on it).

I'm looking at this reboot issue and checking what the piper update trashed.
[Nook Touch General] dorb87:
Great point :)

When I ran the command I got an error:

# dd if=/dev/block/mmcblk0 of=/sdcard/hwcfg skip=1024 count=1

/sdcard/hwcfg: cannot open for write: No such file or directory
[Nook Touch General] Renate:
Well, does sdcard exist? DId you do this in regular Nook or Noogie?

sdcard is not mounted in Noogie.

You should do it in regular Nook.
[Nook Touch General] dorb87:
Yep this was done from regular Nook adb. Looking at the structure of the Nook root from the OS, and there is a file of some kind with no extension named sdcard, but no folder for some reason.
[Nook Touch General] Renate:
Well, that's a problem too.

# dd if=/dev/block/mmcblk0 of=/data/local/tmp/hwcfg skip=1024 count=1
C:\>adb pull /data/local/tmp/hwcfg

Also, do this:

# getprop wifi.driver.path
# ls -l /system/wifi/8189fs.ko

What was the original update that you loaded that caused all this trouble?

Did you later actually find an update for the Glow4?
[Nook Touch General] dorb87:
PS C:\Users\hcors\Downloads> adb pull /data/local/tmp/hwcfg
/data/local/tmp/hwcfg: 1 file pulled. 0.1 MB/s (512 bytes in 0.005s)
PS C:\Users\hcors\Downloads> adb shell
root@ntx_6sl:/ # getprop wifi.driver.path
/system/wifi/8189fs.ko
root@ntx_6sl:/ # ls -l /system/wifi/8189fs.ko
/system/wifi/8189fs.ko: No such file or directory

PM'ed the link to the file it pulled.

So the original thing started when I was in regular Nook OS, issued a factory reset from inside the OS, and I had previously installed TWRP without checking it to ensure it booted first. And from then on it wouldn't come up after rebooting for the factory resetting. I have no valid Update.zip unfortunately.
[Nook Touch General] Renate:
Ok, your NTX hwcfg is fine.

The piper update wiped out /system and the kernel module for WiFi. I'll send that to you.

There is something going on with sdcard, it might be to blame on my kernel.

I need to investigate it.

In any case you can:

# ps -e|grep sdcard

Don't see anything? Try:

# start sdcard
# ps -e|grep sdcard
[Nook Touch General] dorb87:
Okay, the command returned this.

root@ntx_6sl:/ # ps -e|grep sdcard

1|root@ntx_6sl:/ #

Do you want me to run this again, now:

dd if=/dev/block/mmcblk0 of=/sdcard/hwcfg skip=1024 count=1

Tried the other command also (same return):

root@ntx_6sl:/ # start sdcard

root@ntx_6sl:/ # ps -e|grep sdcard

1|root@ntx_6sl:/ #
[Nook Touch General] Renate:
We're done with hwcfg, it's fine.

Too many different version of ps. Do it without the "-e"

# ps|grep sdcard

Don't see anything? Try:

# start sdcard
# ps|grep sdcard
[Nook Touch General] dorb87:
That did the trick!

1|root@ntx_6sl:/ # ps|grep sdcard
media_rw 3342 1 6064 460 ffffffff 402ac378 S /system/bin/sdcard
[Nook Touch General] Renate:
And more to the point, you can see stuff on /sdcard/?
[Nook Touch General] dorb87:
Ah, I didn't realize I was looking for files on it yet. From within the OS I don't see the SD card mounted. Instead of a folder, it's that extension-less file. Doing the Wifi now.

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

Did the Wifi, as instructed. Was able to get the file into where it needs to be, and delete the other one. Powered down, brought back up with Fastboot Boot P1. Wifi still doesn't work, I turn it on with the slider, but on the page where it would list SSIDs, it just says to turn on the Wifi.

Would this all be a super quick fix at this point if I had another 7.8" device on hand to use?

Edit: Oh forgot to mention, I was able to send the driver over to /sdcard/ via ADB and move it from there. After it was mounted in shell. Files were in there!

To be honest, I rarely use Wifi. The main thing I would miss most from the Frankenstein build we have going is the Bluetooth. I don't mind not having wifi.
[Nook Touch General] Renate:
Two quick things to check (in normal Nook):

For the WiFi issues:

# getprop|grep wifi.driver

Does it show the correct driver?

For the reboot issues:

# dd if=/dev/block/mmcblk0p8 of=/dev/tty count=1

Does this just display a blank line or some other text (besides the data counts from the transfer).
[Nook Touch General] dorb87:
Hi there, ran the commands. I didn't leave that prompt, just in case

PS C:\Users\hcors\Downloads> adb shell

root@ntx_6sl:/ # getprop|grep wifi.driver

[wifi.driver.name]: [8189fs]

[wifi.driver.path]: [/system/wifi/8189fs.ko]

root@ntx_6sl:/ # dd if=/dev/block/mmcblk0p8 of=/dev/tty count=1

boot-recovery recovery

--wipe_data

--locale=en_US

1+0 records in

1+0 records out

512 bytes transferred in 0.002 secs (256000 bytes/sec)

Edit: Wifi driver is a different number than the file we added into the folder. Is that command showing that the recovery has the command to Wipe data still in there, and that would be why it keeps going to Recovery on boot? Just trying to piece this together somewhat. Been quite a learning opportunity :)

Also edited my IMX-Keypad file, to get the side buttons going for page turns
[Nook Touch General] Renate:
So, to fix the reboot problem:

# dd if=/dev/zero of=/dev/block/mmcblk0p8 count=1
[Nook Touch General] dorb87:
That did it!

Edit: Do you think the bluetooth is even salvageable at this point? If not, no big deal. Really appreciate all your help to get this back up. Can't thank you enough. :)

Did a getprop to look for BT related things. This stood out to me:

[ro.bt.bdaddr_path]: [/data/misc/bluetooth/bdaddr]

I went to the folder and there was nothing in /data/. Might be the cause?

[persist.service.bdroid.bdaddr]: [22:22:7c:ea:a9:80] That looks normal. Is there a way we could create the files needed for the data/misc/bluetooth folder?
[Nook Touch General] Renate:
Yes, it's just a question of figuring out how/why the kernel module for WiFi/BT is where

You need kernel module /system/wifi/8723ds.ko
[Nook Touch General] dorb87:
So I put those files in place, made sure to erase the old ones first, rebooted, and still no luck on wifi. Same issue as before.

It looks to me that getprop shows a different wifi driver it's looking for? But again, not sure.

[wifi.ap.interface]: [wlan0]

[wifi.driver.name]: [8189fs]

[wifi.driver.path]: [/system/wifi/8189fs.ko]

[wifi.interface]: [wlan0]

[wlan.interface]: [wlan0]

Should I rename the 8723ds.ko to 8189fs.ko?

Edit: I found a copy of 8189fs.ko on Github, didn't do anything with it in case I'd make it worse.

https://github.com/pine64-android/d...master/tulip-chiphd/modules/modules/8189fs.ko
[Nook Touch General] Renate:
No, 8723ds.ko is the right file.

What does this do?

# lsmod
[Nook Touch General] dorb87:
Doesn't seem to do anything:

root@ntx_6sl:/ # lsmod

root@ntx_6sl:/ #
[Nook Touch General] Renate:
# insmod /system/wifi/8723ds.ko
# lsmod
[Nook Touch General] dorb87:
root@ntx_6sl:/ # insmod /system/wifi/8723ds.ko
root@ntx_6sl:/ # lsmod
8723ds 1603812 0 - Live 0x00000000

Rebooted the device, nothing seems to have changed for the Wifi.
[Nook Touch General] Renate:
Ok, but did you check your properties, check your WiFi before you rebooted?

If you don't make any permanent changes a reboot will be the same as ever.
[Nook Touch General] dorb87:
Apologies, I wasn't aware this wasn't a perm change. I re-ran it, and tested, but no change. Didn't appear to be any change under getprop, either.
[Nook Touch General] Renate:
Try:

# insmod /system/wifi/8723ds.ko
# lsmod
# stop
[i]- wait 10 seconds -[/i]
#start
[i]- check wifi -[/i]
[Nook Touch General] dorb87:
When I ran the start command, that made the device reboot. When it loaded back up, tried Wifi and still the same.

Ran it again to confirm, the start command restarts it.
[Nook Touch General] Renate:
Well, it restarts Android, but it doesn't reboot it.

I mean, you didn't lose your ADB shell when this all happened, right?

The whole WiFi thing is a bit complicated and also implementation dependent.

It's the only loadable (that is not built into the kernel) module on the system.

It's using hardware that needs its own firmware loaded.

I can't seem to find where/how it's all loaded.

I got down as far as libhardware_legacy.so

I'm still looking.
[Nook Touch General] dorb87:
Okay, you are correct. It re-loaded but not rebooted. ADB wasn't lost. No WiFi though. I really appreciate all your time and please, if you decide this is a waste of your time, don't hesitate to tell me to deal with no BT :p
[Nook Touch General] dorb87:
Hi Renate,

If I had access to a brand new device, pre-firmware update, could I feasibly determine the OTA FW 5 update.zip url for the Glow4 using logcat, and then use that update.zip to fix my BT by flashing it?
[Nook Touch General] Renate:
Well, the easiest would be if a new OTA update were released.

Except for the bit about not having WiFi you are in a position to update.

Since I can see this problem from many sides (i.e. NeoNoogie doesn't have WiFi either) I am in a position to figure this out.

Eventually.
[Nook Touch General] dorb87:
Okay, I will wait it out then. Happy Holidays.
[Nook Touch General] dorb87:
Hi Renate,

A friend of mine ordered a Glow4, soon to arrive. Would I be able to pull the stock image from that device, and then flash it to my Glow4 in some way to repair it?

Edit: Using Neo Noogie and Sdcard.exe, I was able to repair my device. Thanks for your great Nook tools and help.
[Nook Touch General] Renate:
Mmm, I'm glad that you got it all working.

I'm sorry that I didn't figure out anything else in time.

I did get the WiFi running and scanning in NeoNoogie, but I couldn't figure out why it didn't start itself.
[Nook Touch General] dmc123:
Brother, I have successfully connected to putty, but what can I do? There is no u-boot menu. What button can stop initialization and access the u-boot menu? I want to flash twrp

The following is a portion of the startup log

U-Boot 2009.08-00178-gcb174de ( 1月 31 2019 - 14:26:05)

CPU: Freescale i.MX6 family TO0.0 at 792 MHz

Temperature: 77 C, calibration data 0x57e5075f

mx6q pll1: 792MHz

mx6q pll2: 528MHz

mx6q pll3: 480MHz

mx6q pll8: 50MHz

ipg clock : 66000000Hz

ipg per clock : 24000000Hz

uart clock : 80000000Hz

cspi clock : 60000000Hz

ahb clock : 132000000Hz

axi clock : 198000000Hz

emi_slow clock: 22000000Hz

ddr clock : 396000000Hz

usdhc1 clock : 198000000Hz

usdhc2 clock : 198000000Hz

usdhc3 clock : 198000000Hz

usdhc4 clock : 198000000Hz

Board: MX6SoloLite-NTX:[ POR ]

Boot Device: MMC

I2C: ready

DRAM: 1 GB

MMC: ram p=80000000,size=1073741824

csd is 0xd0270132, 0xf5903ff, 0xf6dbffef, 0x8e404000

mmc0(part 0) is current device

MMC read: dev # 0, block # 1023, count 1 ... 1 blocks read: OK

MMC read: dev # 0, block # 1024, count 1 ... 1 blocks read: OK

FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2

i2c: I2C1 SDA is low, start i2c recovery...

I2C1 Recovery failed, I2C1 SDA still low!!!

RC5T619_disable_NOE(): done

hw_anadig_reg_core=7c3e1f

MMC read: dev # 0, block # 34815, count 1 ... 1 blocks read: OK

binary magic @ sector no. 34816 not found !

"logo" not exist !!

MMC read: dev # 0, block # 18431, count 1 ... 1 blocks read: OK

binary magic @ sector no. 18432 not found !

"logo" not exist !!

In: serial

Out: serial

Err: serial

ntx_hw_late_init()

MMC read: dev # 0, block # 1, count 1 ... 1 blocks read: OK

NTXSN:""
[Nook Touch General] Renate:
The spacebar should stop it.

Then type "fastboot".

There is no menu, just a command line.
[Nook Touch General] Renate:
I have no idea what tool/script/batch you are using or if it's even for this device.

It looks like you're killing everything.
[Nook Touch General] dmc123:
i using the putty on windows 10 connect the Nook Glowlight Plus 78 . boot into fastboot successfully . but can not flash twrp to recovery partition or boot when i use command 'fastboot flash recovery/boot twrp.img' , adb show message 'fail:partition not exist'
[Nook Touch General] dmc123:
The following is PUTTY output message .Why is the partition table different from other Android devices? There is no BOOT, system, or recovery

downloading of 8067072 bytes finished

cmdbuf: flash:boot

can't find partition: boot, dump the partition table

ptn 0 name='mbr' start=0 len=1

ptn 1 name='sn' start=1 len=1

ptn 2 name='bootloader' start=2 len=1022

ptn 3 name='hwcfg' start=1024 len=2

ptn 4 name='ntxfw' start=1030 len=256

ptn 5 name='waveform' start=14336 len=20480

ptn 6 name='logo' start=34816 len=4096

ptn 7 name='bootenv' start=1536 len=510

ptn 8 name='kernel' start=2048 len=12284

ptn 9 name='rootfs' start=13631484 len=1605633

ptn 10 name='vfat' start=1567715 len=12063769
[Nook Touch General] Renate:
Who or what is telling it to getvars that don't exist on this?

Who or what is telling it to flash partitions that don't exist on this?
[Nook Touch General] dmc123:
A Glowlight Plus 7.8 got a touch error because flash an unknown system. I used PUTTY to connect the nook PCB to enter fastboot .it showed '???????????? fastboot 'after using the' fastboot devices' command in adb.exe.

Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 8067072).

Sending 'recovery' (7878 KB) OKAY [ 1.458s]

Writing 'recovery' FAILED (remote: 'partition does not exist')

fastboot: error: Command failed

appears when I use the command 'fastboot flash recovery twrp_quill.img' in adb.exe

The following information is displayed on PUTTY

wait usb cable into the connector!

USB Mini b cable Connected!

fastboot initialized

USB_SUSPEND

USB_RESET

cmdbuf: getvar:has-slot:recovery

unknown var

send: OKAYunknown var

cmdbuf: getvar:max-download-size

unknown var

send: OKAYunknown var

cmdbuf: getvar:is-logical:recovery

unknown var

send: OKAYunknown var

cmdbuf: getvar:is-logical:recovery

unknown var

send: OKAYunknown var

cmdbuf: getvar:partition-size:recovery

unknown var

send: OKAYunknown var

cmdbuf: getvar:is-logical:recovery

unknown var

send: OKAYunknown var

cmdbuf: download:007b1800

Starting download of 8067072 bytes

send: DATA007b1800

................................................................................

...........................................send: OKAY

downloading of 8067072 bytes finished

cmdbuf: flash:recovery

can't find partition: recovery, dump the partition table

ptn 0 name='mbr' start=0 len=1

ptn 1 name='sn' start=1 len=1

ptn 2 name='bootloader' start=2 len=1022

ptn 3 name='hwcfg' start=1024 len=2

ptn 4 name='ntxfw' start=1030 len=256

ptn 5 name='waveform' start=14336 len=20480

ptn 6 name='logo' start=34816 len=4096

ptn 7 name='bootenv' start=1536 len=510

ptn 8 name='kernel' start=2048 len=12284

ptn 9 name='rootfs' start=13631484 len=1605633

ptn 10 name='vfat' start=1567715 len=12063769

Partition:'<NULL>' does not exist

send: FAILpartition does not exist
[Nook Touch General] dmc123:
If I want to write another proper ROM, or official system, do I need to write TWRP first? Where can I download the official system?
[Nook Touch General] dmc123:
putty show

====[elan_touch_ts_interrupt_1002]====

====[elan_touch_ts_interrupt_1002]====

when i touch the screen .
[Nook Touch General] Renate:
I don't know what the state of your device is now.

When u-boot speaks of "partitions" they are only speaking of areas on the eMMC (many before mmcblk0p1) that are used for low level things.

The high level partitioning of this device should be:

/dev/block/mmcblk0p1 /boot emmc
/dev/block/mmcblk0p2 /recovery emmc
/dev/block/mmcblk0p4 /data ext4
/dev/block/mmcblk0p5 /system ext4
/dev/block/mmcblk0p6 /cache ext4
/dev/block/mmcblk0p7 /device ext4
/dev/block/mmcblk0p8 /misc emmc

If fastboot can't find recovery there is a problem somewhere.
[Nook Touch General] dmc123:
When not connected to the computer, nook book can enter the system normally. Touch is responsive (can unlock the screen) but you cannot click the any app icon. the book can be entered into fastboot mode too ,but i can not flash the twrp it say 'FAILED (remote: 'partition does not exist')'
[Nook Touch General] Renate:
Did you flash the wrong u-boot to this or something?

Or did you try to repartition it or something?

What does this say:

fastboot getvar all
[Nook Touch General] dmc123:
all: unknown var
[Nook Touch General] dmc123:
Or should I view the memory partition information under u-boot?
[Nook Touch General] dmc123:
C:\platform-tools>fastboot flash recovery twrp_quill.img

couldn't parse max-download-size 'unknown var'

Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 8067072).

Sending 'recovery' (7878 KB) OKAY [ 1.453s]

Writing 'recovery' FAILED (remote: 'partition does not exist')

fastboot: error: Command failed
[Nook Touch General] Renate:
I dunno, try 'em all.

fastboot getvar
fastboot getvar *
fastboot getvar all

Get nnglow4.img from NeoNoogie in my sig.

fastboot boot nnglow4.img

Do you get a splash screen?

Do you have ADB?
[Nook Touch General] dmc123:
Suddenly I can't enter the U-boot, no matter how I press the space bar, BOOK directly load the kernel into the system. i have download adb from internet .need a special ADB program？
[Nook Touch General] Renate:
You need ADB. Google "minimal ADB".