yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
The link is dead.
[Nook Touch General] usenothing:
sorry.

Now, u can got it in attatchment of my previous post :)
[Nook Touch General] Renate:
Ok, I think that we're ready.

Do your stuff so that you see the boot partition.

Run bootutil.exe (in the signature) as follows:

bootutil /x /v uRamdisk init.rc default.prop

Then edit the two files using a Unix EOL capable editor (like Notepad++).

init.rc

Line #375, comment out "disabled" with a # at the start of the line.

Lines #392-399 comment out 6 lines that involve persist.service.adb.enable

default.prop

Just adjust the whole contents so that it reads:

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1

Now, put the files back in the ramdisk.

bootutil /r /v uRamdisk init.rc default.prop

Copy uRamdisk back to the boot partition.

Now do a normal reboot and cross your fingers.

See if ADB is running.

(You can use omaplink without any args just to get the LED display.)
[Nook Touch General] jwxuan:
After Ccopying uRamdisk back to the boot partition, do I need to disconnect the USB, and then do a normal reboot, or just do a normal reboot ?
[Nook Touch General] Renate:
Mmm, no big deal, but you might as well "Safely remove USB device" in Windows, unplug, reboot, then connect if/when you see a normal boot.
[Nook Touch General] shanks7777:
I followed your order, and still got NO ADB.
[Nook Touch General] Renate:
Ok, but at least it boots up 100% normal on your stock Glow system?

Does your "Media" partition appear as a disk over USB?

What does DeviceManager show? Any yellow bits?

adb kill-server

run omaplink (just by itself)

Does the green ADB LED light?
[Nook Touch General] shanks7777:
1. It boots up 100% normal on my stock Glow system.

2. I can't fully understand what you're meaning "Media" partition. Only thing I see is the normal NOOK drive.

3. I see some yellow question marked stuffs, however it looks irrelevant to GN2.

4. I also tried by first do kill-server and run omaplink, but nothing changed.
[Nook Touch General] usenothing:
I made a try as your instuctions .

When I just run omaplink.exe without any args , the "bootloader" light flashed and then the program exit. seen no other led lights.

Now,I boot my Nook GL normally with usb connected, I got this in device-manager:
[Nook Touch General] Renate:
Are you sure? Are the "Hardware Ids" not related to USB at all?

What are they?

[MENTION=4597750]usenothing[/MENTION] Ok!!! You have it.

Does adb shell work?

If not, adb kill-server, then check for green led on omaplink.exe (no args)

Hmm, if you are using the standard Google driver it should be saying "Android Composite ADB Interface".

You don't have another Android device plugged in at the same time, do you?
[Nook Touch General] shanks7777:
Okay, so I tried connecting GN2(normal boot) after deleting USB mass storage with 0x2080 0x0007.

And FINALLY got this!!!!!

ADB shell also works fine.
[Nook Touch General] usenothing:
1.

I tried again: run omaplink ,without any args, just "omaplink.exe" , and the "adb" led still dark...

When I run "adb kill-server", it told me "server not running" . with the "adb" keep dark.

2. I just connect my Nook GL to PC, no other android devices.

3. If i run omaplink with two args "omap3_aboot.bin" and "u-boot-ng2-exp-v05.bin" , got this:

Waiting for bootloader... 0451:D00E, OMAP3630, pbi, 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-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER瘀, Android Fastboot, ok
product 3621GOSSAMER
version 0.5

at the moment, the "fastboot" led turns yellow, "adb" led is dark again.

[MENTION=4597750]usenothing[/MENTION] Ok!!! You have it.

Does adb shell work?

If not, adb kill-server, then check for green led on omaplink.exe (no args)

Hmm, if you are using the standard Google driver it should be saying "Android Composite ADB Interface".

You don't have another Android device plugged in at the same time, do you?[/QUOTE]

---------- Post added at 07:33 AM ---------- Previous post was at 07:26 AM ----------

Aha！

Inspired by you.

I disconnected Nook GL from PC, and then reboot it normally . Then run omaplink, the "adb" led turned green. but ,then get dark.

(Didnot change anything with USB mass storage in device manager )

Do another test:

run omap first , disconnect the Nook GL(just disconnect ,without reboot) ,then connect , the "adb" led turn green and then get dark again.
[Nook Touch General] Renate:
[MENTION=4388886]shanks7777[/MENTION] So it's all good now? Great!

Try a few commands in ADB to see what the partitions are.

mount
fdisk -l /dev/block/mmcblk0
toolbox fdisk -l /dev/block/mmcblk0
busybox fdisk -l /dev/block/mmcblk0

The partitions are a little different from the Touch since mmcblk0p9 is /data

[MENTION=4597750]usenothing[/MENTION] No, you're getting confused and I'm getting confused.

Just boot your Nook normally without a USB cable or anything.

Does the regular system boot up normally?

Connect the USB cable.

What appears in Device Manager?

Try:

omaplink

Don't put anything else on the line.

It looks like you are using an old version.

Use the one zipped up in experiment12.zip from above.

You may have to reload the drivers like shanks7777 did.
[Nook Touch General] shanks7777:
C:\Documents and Settings\engine4>adb shell
# 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
# fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
fdisk: not found
# toolbox fdisk -l /dev/block/mmcblk0
toolbox fdisk -l /dev/block/mmcblk0
fdisk: no such tool
# busybox fdisk -l /dev/block/mmcblk0
busybox fdisk -l /dev/block/mmcblk0
busybox: not found
[Nook Touch General] usenothing:
OK. I have done with this.

adb worked!

However, I got the same result as shanks7777

i'm a little excited! Hmm, thanks you all~~~

[MENTION=4597750]usenothing[/MENTION] No, you're getting confused and I'm getting confused.

Just boot your Nook normally without a USB cable or anything.

Does the regular system boot up normally?

Connect the USB cable.

What appears in Device Manager?

Try:

omaplink

Don't put anything else on the line.

It looks like you are using an old version.

Use the one zipped up in experiment12.zip from above.

You may have to reload the drivers like shanks7777 did.[/QUOTE]
[Nook Touch General] jwxuan:
[QUOTE……[/QUOTE]

I got almost the same result，but a little different is the omap link don't turn green, althroug it turn 8 from 6，but the adb shell work well.

Now, can we instead the system fonts with fonts which we love?
[Nook Touch General] jwxuan:
I got almost the same result，but a little different is the omap link don't turn green, althroug it turn 8 from 6，but the adb shell work well.

Now, can we instead the system fonts with fonts which we love?View attachment 2491241[/QUOTE]

F:\>adb devices
List of devices attached
3034360013843110 device

F:\>adb shell
# $su
$su
# ls
ls
rom
sqlite_stmt_journals
sdcard
media
cache
tmp
etc
system
sys
sbin
proc
init.rc
init.goldfish.rc
init
env.txt
default.prop
data
root
dev

I get the NG2 default reader software with a Chinese software “wandoujia”.
[Nook Touch General] Renate:
Ok, so usenothing, jwxuan & shanks7777 all have working ADB on stock 1.3 Nook?

shanks7777 has shown that the ADB shell is as root #.

Great!

Now, where to go?

You might take a step back to getting the noogie going again and do a full 4GB backup using Win32DiskImager.

I think that somebody ought to pull factory.zip

mount -o rw,remount rootfs /
mkdir /factory
mount -t ext2 /dev/block/mmcblk0p3 /factory

Then

adb pull /factory/factory.zip

I'd really like to get the disk partition layout, that's one thing that factory.zip does not recreate.

I guess that we should check space first:

df

We'd probably like to install busybox at least.

mount -o rw,remount /dev/block/mmcblk0p5 /system

Then

adb push busybox /system/bin

Then

chmod 755 /system/bin/busybox
busybox fdisk -l /dev/block/mmcblk0

This might be helpful too:

cat /system/etc/vold.conf

Eventually we will want to add a launcher and ButtonSaviour to get around.
[Nook Touch General] jwxuan:
I get the factory.zip，but it is too big，127M

and run df result which is below

F:\>adb shell
# df
df
/dev: 116568K total, 0K used, 116568K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16128K total, 234K used, 15894K available (block size 512)
/system: 285583K total, 215397K used, 70186K available (block size 1024)
/data: 2162964K total, 148436K used, 2014528K available (block size 4096)
/cache: 237987K total, 6231K used, 231756K available (block size 1024)
/factory: 188403K total, 129975K used, 58428K available (block size 1024)
#
[Nook Touch General] usenothing:
Hi，Renate：

1. I don't know how to make the bakcup with Win32DiskImager.

2. I pulled the factory.zip to my PC.

3. I moved on to the step: adb push busybox /system/bin ; but ,I don't know what's the busybox mean? so ,I find the busybox.apk on my PC, and changed to :

adb push busybox.apk /system/bin

Then, "chmod 755 /system/bin/busybox" , it told me

Unable to chmod /system/bin/busybox: No such file or directory

So, i stopped here.
[Nook Touch General] Renate:
Anything that starts with "adb" is a command you give to the Windows shell ("MS-DOS", whatever).

The commands were split into two boxes, one for the Nook shell, one for Windows.

You can have two separate windows in Windows or else ^C out of the Nook shell to return to Windows.

The busybox that I refer to is the raw "busybox", no extension.

If you unzip busybox.apk you should find it in there somewhere.

Could somebody quote the results of "df"?

Oh: And delete that apk that you copied over:

rm /system/bin/busybox[b].apk[/b]
[Nook Touch General] jwxuan:
F:\>adb shell
# df
df
/dev: 116568K total, 0K used, 116568K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16128K total, 234K used, 15894K available (block size 512)
/system: 285583K total, 215397K used, 70186K available (block size 1024)
/data: 2162964K total, 148436K used, 2014528K available (block size 4096)
/cache: 237987K total, 6231K used, 231756K available (block size 1024)
/factory: 188403K total, 129975K used, 58428K available (block size 1024)
#
[Nook Touch General] usenothing:
OK.

I checked the busybox.net, and found so many versions of busybox :

busybox-armv4l
busybox-armv4tl
busybox-armv5l
busybox-armv6l
busybox-armv7l
busybox-binaries.tar.bz2
busybox-i486
busybox-i586
busybox-i686
busybox-m68k
busybox-mips
busybox-mips64
busybox-mipsel
busybox-powerpc
busybox-powerpc-440fp
busybox-sh4
busybox-sparc

I don't know which one to choose :)

Then, the result of df is here:

df
/dev: 116568K total, 0K used, 116568K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16128K total, 231K used, 15896K available (block size 512)
/system: 285583K total, 215397K used, 70186K available (block size 1024)
/data: 2162964K total, 123812K used, 2039152K available (block size 4096)
/cache: 237987K total, 6256K used, 231731K available (block size 1024)
/factory: 188403K total, 129977K used, 58426K available (block size 1024)
[Nook Touch General] jwxuan:
With a friend guide ，I install a new launcher，and it is goodView attachment 2491411
[Nook Touch General] Renate:
This busybox works fine: busybox-armv7l

Either rename it or:

adb push busybox-armv7l /system/bin/busybox
chmod 755 /system/bin/busybox
[Nook Touch General] jwxuan:
The big news

with a software called coolreader，I can read Chinese book！View attachment 2491423
[Nook Touch General] usenothing:
OK.

I have installed the busybox ,and got this after input "busybox fdisk -l /dev/block/mmcblk0":

# busybox fdisk -l /dev/block/mmcblk0
busybox fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
128 heads, 32 sectors/track, 1864 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 1864 3528704 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 539 520176 c Win95 FAT32

(LB
A)
/dev/block/mmcblk0p7 540 659 245744 83 Linux
/dev/block/mmcblk0p8 660 791 270320 83 Linux
/dev/block/mmcblk0p9 792 1864 2197488 83 Linux

And, I got this after input "cat /system/etc/vold.conf":

cat /system/etc/vold.conf
## vold configuration file for zoom2
# modified for encore

volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 6
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}

volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1

So, so, what's next ?
[Nook Touch General] jwxuan:
Thank you very much ，I don't know what to say to express my grateful！
[Nook Touch General] jwxuan:
This is my result

F:\aaaa>adb shell
# chmod 755 /system/bin/busybox
chmod 755 /system/bin/busybox
# busybox fdisk -l /dev/block/mmcblk0
busybox fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
128 heads, 32 sectors/track, 1864 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 1864 3528704 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 539 520176 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 540 659 245744 83 Linux
/dev/block/mmcblk0p8 660 791 270320 83 Linux
/dev/block/mmcblk0p9 792 1864 2197488 83 Linux
# cat /system/etc/vold.conf
cat /system/etc/vold.conf
## vold configuration file for zoom2
# modified for encore

volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 6
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}

volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
#

And I installed some apk yesterday for a test，with the code

adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

and then install a new launcher.apk

adb shell chmod 644 /system/app/*
adb install io.xor.nook.touch.launcher.apk

then, you can install some software with

adb shell chmod 644 /system/app/*
adb install NookColorTools_0.2.apk
adb install cr3.1.2-34-release.apk

Of course，my friend modified the setting.adbView attachment settings.rar
[Nook Touch General] jwxuan:
There are still many problem，for example，the input sofeware can't work，there is only 500M space we can use！
[Nook Touch General] Renate:
The partitioning is almost like the older version.

mmcblk0p6 /media has been stretched a bit to 500M

mmcblk0p8 (the old /data) has been shrunk to 250M, but does not seem to be used.

mmcblk0p9 (the new /data) has been increased to 2G

Of course we can shuffle the partitioning around but I'd like to wait until we know what's going on.

Those who want to use the B&N book store may want to do things differently.

Least radical is shifting the sizes of a few things around.

Most radical would be to eliminate /media entirely, make mmcblk0p8 /data and mmcblk0p9 /sdcard and forget about UMS mounting.

As far as I can tell eliminating UMS would only pose a hiccup to using Adobe Digital Editions with library books, but that can probably be worked around.

For all other transfers ADB or adbsync would work fine.

I think we need to figure out first what mmcblk0p8 is doing.

mount -o rw,remount rootfs /
mkdir /test
mount -t ext3 /dev/block/mmcblk0p8 /test
ls -l /test

There should not be a problem adding input methods, although the settings.db has to be modified.

If someone has previous experience with USB OTG and UsbMode.apk, can you see if a keyboard with an OTG adapter works?
[Nook Touch General] usenothing:
I just read your reply and tried .

Because i don't know how to use the usbmode.apk, I only tested your first method, then got this:

# mount -o rw,remount rootfs /
mount -o rw,remount rootfs /
# mkdir /test
mkdir /test
# mount -t ext3 /dev/block/mmcblk0p8 /test
mount -t ext3 /dev/block/mmcblk0p8 /test
# ls -l /test
ls -l /test
[B]drwx------ root root 2000-01-01 08:00 lost+found[/B]
[Nook Touch General] Renate:
So mmcblk0p8 is an empty, correctly formatted ext3 partition.

I wonder what B&N was planning there? A place for OTA updates?
[Nook Touch General] usenothing:
Thanks for your immediate reply.

1.Your question "I wonder what B&N was planning there?" is beyond my ability ,mm, :o

2.I just googled "usb OTG", in my opinion, We transfer data between two android devices by a USB line with mini-usb port of both ends?

Unfortunately, I have no this sub-OTG line, and can do nothing about this.

3.Do you need me to do something else for testing ?
[Nook Touch General] dorfd1:
Is it confirmed that this device runs android 2.1?
[Nook Touch General] usenothing:
Thanks for your hard work to explore the New Nook GL.

I tried "sudo ./noogie" then connect the nook to PC, and got the same result as you got. At this time, the Nook stayed at the boot screen and the light turned red.

But ,when I tried to make a backup with dd as your instruction, I got error "There is no such file or directory".

It seems the nook wasnot be mounted?

I run "lsusb", and found no one could be the "nook".

BTW: If I understand correctly, I need to run the "dd ***" after trying the "sudo ./noogie" ,but without rebooting the Nook. Isn't it ?
[Nook Touch General] straygecko:
Sorry, I forgot the NG2 needs its own kernel and included just the NST kernel. I packaged it two ways now - one for NST & one for NG2. Try the NG2 version attached.
[Nook Touch General] usenothing:
Thanks.

It worked this time, and I made a backup.

However , to those not familiar with "dd" command like me :

1. "dd" needs su privilege to run;

2. You could modily the last arg of "dd" command to a existing folder(if you don't have a folder called backups under \tmp), for example, mine code is :

sudo dd if=/dev/sdb bs=1000k | gzip -1 > /tmp/nookbackup.full.gz
[Nook Touch General] Renate:
Ok, X13 is ready.

This will operate with either a-boot or x-loader depending on which you give.

With a-boot

C:\>omaplink omap3_aboot.bin u-boot12.bin uRecImg uRecRam
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, 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
Received a-boot response
Sending image file u-boot12.bin, 170572 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot, ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... 2080:0003, NOOK, ok
Version: 01000000, payload: 4096, type: recovery

With x-loader

C:\>omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage-noogie uRamdisk-noogie
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, 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 x-load-ng2-130-stk.bin, 16692 bytes... ok
Received x-loader response
Sending image file u-boot-ng2-130-stk.bin, 162996 bytes @ 80E80000... ok
Sending image file uImage-noogie, 1839448 bytes @ 82000000... ok
Sending image file uRamdisk-noogie, 180318 bytes @ 83000000... ok
Sending execute @ 80E80000 command
Waiting for disconnect... ok

And finally, it does check existence of the files first.
[Nook Touch General] straygecko:
Thanks for the quick work Renate - and the file checking up front.

On an NG2, for either aboot or x-load replace uRecImg or uImage-noogie with uImage-ng2-130-stk from the NG2 package in this post.
[Nook Touch General] Renate:
:o X14 is now the one to use.

The changes are minor.

It will add more graceful interruption by ^C.

It adds resiliency for when the x-loader style sequence gets screwed up.

The Nook will still be in bootloader mode but it will be in an odd phase.

Not only that, but the Nook will not even be USB negotiating correctly.

At least on XP, this causes the Windows internal numeration to run slow.

Everything on omaplink is now on separate threads so it will do its best.

What you'll see is the little popup will display "Scanning..."

After 3 or 4 seconds when the bootloader gets somewhat identified it will display:

Waiting for bootloader... 0451:D00E, ok

Instead of:

Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok

Outside of intentionally screwing things up, I've not seen this rev omaplink.exe fail.
[Nook Touch General] yeahman45:
thx Renate and straygecko for your great work. I will try experiment14 on my NST with glowlight once i get it.

C:\>omaplink omap3_aboot.bin u-boot12.bin uRecImg uRecRam

uRecImg and uRecRam are the ones from straygecko attachement right? : http://xdaforums.com/attachment.php?attachmentid=2498007&d=1389013895 (uImage-noogie and uRamdisk-noogie)
[Nook Touch General] Renate:
They are just the CWM recovery ones that I usually use.

You can load any image & ramdisk using either the a-boot/u-boot/fastboot or else the x-loader/u-boot method.

The 2nd is faster.

The only downside is that you can't enter any command line parameters.

The defaults work fine, but you can change load addresses with flags (since X13).

usage: omaplink [loader] [uboot] [kernel] [ramdisk]
/u uboot address
/k kernel address
/r ramdisk address
/x execute address

The flags are entered in the style /uabcd1234
[Nook Touch General] Renate:
The next big questions on the new Nook Glow 2:

Does it support USB host mode? (Probably, the NST does.)

Does it support Bluetooth? (Mmm, not likely, but it does have a different WiFi module, so it might.)
[Nook Touch General] ErikMunoz:
Noob Question

Hello guys

i just finish to read all the posts, but to be honest i finished same as the beggining ( lost )

i have a Nook GlowLight ( avocet ) and i want to get adb access.

i already downloaded the exp 14 from Renate and the	linux-usbload-ng2-noogie from straygecko

now i dont know how to start.

if you want to help me it would be great :D

P.D.

i have an usb OTG cable and seems not working in normal mode, i don't know if works with root access