yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] ErikMunoz:
Sure

there you go :D

Sorry for my late response.

C:\Users\JGR-AutoTriage-002\AppData\Local\Android\sdk\platform-tools>adb shell m
ount
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

C:\Users\JGR-AutoTriage-002\AppData\Local\Android\sdk\platform-tools>

Edit:

i have 2 questions:

Question1:

if i could have a second NG2 could i use my modified uRamdisk on it? or i need to edit the files again?

Quiestion2:

to goes back ( unroot ) i need to replace the uramdisk with the original right?
[Nook Touch General] Renate:
Yes, to root another NG2 you just need to copy over the same modified uRamdisk.

There is nothing personalized in uImage or uRamdisk.

All the devices-specific data is in /rom

You've backed that up already in a safe place, right?

To unroot, just copy the original uRamdisk back.
[Nook Touch General] hrulik:
Cool! can you please make howto root NG2, or program to root for ppl?
[Nook Touch General] ErikMunoz:
:D :D

yes, everithing is backed up

many thanks renate :)
[Nook Touch General] Renate:
A short recap of how to root the new NG2:

All of these methods use the Texas Instruments OMAP processor USB bootloader.

The desktop system that you connect the Nook to can be either Linux or Windows.

This only details the Windows method.

The bootloaded system can be either noogie or Clockwork Mod or a modified stock Nook.

For now, we are only using the noogie method.

The bootloading sequence can be either aboot, u-boot or x-loader, u-boot.

For now, we are only using the aboot, u-boot method.

Preparation

In Window, we need drivers to communicate with all USB devices.

The bnusbdriver.zip attached below is the modified stock driver.

Unzip it and when installing or re-installing select this driver manually.

Manually means saying, "No, I will select" until you get down to "Have disk" and select the specific directory.

The driver info is unsigned, although the drivers themselves are stock Windows.

Collect the necessary files.

omaplink.exe can be found in the signature below.

The four files can be downloaded here: http://xdaforums.com/showpost.php?p=49779966&postcount=285

Booting

Fully power your Nook down with the USB disconnected.

Run this command on the PC.

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

Plug the USB into the Nook.

Whenever a "New Device" popup appears manually select android_winusb.inf to be loaded then start this step over.

omaplink should get as far as "Waiting for ADB..."

It won't find it just yet, use ^C to exit.

At this point there should be a new removable disk mounted with a dozen files on it, including uRamdisk

Rooting

Follow the directions here for modifying uRamdisk http://xdaforums.com/showthread.php?p=49070213#post49070213

Reboot to a rooted Nook with ADB over USB access
[Nook Touch General] kazem_aryan:
Driver

Hi

in first step, i can't install driver! i tried in win xp sp3 & win 7

i can't find any location to find the driver

i try this locations :

G:\

<sdk>\extras\google\usb_driver\

google\extras\usb_driver

how can i download the INF driver file?! or have any other way to install the driver?!

tnx
[Nook Touch General] digixmax:
It would be great if you can update this post to include the links to these necessary files.

TIA.
[Nook Touch General] Renate:
[MENTION=2862980]kazem_aryan[/MENTION] The ADB driver can be found at http://developer.android.com/sdk/win-usb.html#download

Since there is no Nook mentioned in android_winusb.inf it must be modified as above.

omaplink.exe can now be found in the signature below.

I'm trying to get a definitive source for the four files, but the NG2 archive has the last three:

http://xdaforums.com/attachment.php?attachmentid=2498006&d=1389013895

omap3_aboot.bin (3480 bytes) is the first one.
[Nook Touch General] kazem_aryan:
Files

we need this files, right?!

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

1."omaplink.exe" is ok

*2."omap3_aboot.bin" i can't find this file! :( (not included in this compressed file http://xdaforums.com/attachment.php?attachmentid=2498006&d=1389013895) and no file with 3480 bytes size on it.

3."u-boot-ng2-130-stk.bin" its ok

*4."uImage-noogie" is this file equal to "uImage-ng2-130-stk"?! because no file named "uImage-noogie" in the compressed file.

5."uRamdisk-noogie" is ok

tnx
[Nook Touch General] Renate:
See the re-edited post above: http://xdaforums.com/showpost.php?p=49665945&postcount=279

There is now a completely packaged driver for the Nook that you don't need to modify.

Use whichever uImage there and the uRamdisk_noogie
[Nook Touch General] straygecko:
Here's the files to boot Noogie on the NG2

I've been busy with business year-end stuff and haven't had time to look at this lately. Thanks to Renate for prodding me via PM to get the proper set of files together in one place as the bits and pieces are scattered throughout this thread. The attachment is the set of four files to use with Renate's omaplink to get your NG2 booted up into Noogie. This is for the aboot/fastboot method which seems to be the only reliable method right now. With this method you can get your boot partition mounted in Windows so you can make the necessary changes for root. But you will be unable to backup your entire nook storage. When I get a chance I'll see if I can get a reliable version of the x-load method working so you can do backups.

Use with omaplink like this:

omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
[Nook Touch General] kazem_aryan:
i've followed instructions, create "init.rc" and "default.prop". open by notepad++, but i have some problems about modifying "init.rc":

1. What does "Comment Out" mean?! just place a "#" in the start of line or replace entire the line with "#"?

2. I do not understand what I need to apply changes in line 392-399, and exactly which lines must be modify? :confused:

i modify this file like this: (Attachments). is this true?! :cyclops:

tnx
[Nook Touch General] Renate:
Yes, you've got the idea but it's only half done.

Put a # at the start of lines 392, 393, 396, 399

Unrelated comment: Wow, I didn't notice how ugly the code that B&N wrote underneath that all was.

Remounting /system to play with resolution stuff? :eek:
[Nook Touch General] kazem_aryan:
ADB

-i make the uRamdisk and copy it back to the boot partition, restart the Nook, but did Not make a change! :(

What is the problem?! :confused:

-I do not know much about resolution!! :rolleyes:
[Nook Touch General] Renate:
No, after you finish modifying and copying uRamdisk you are all done with omaplink.exe

Just do a normal reboot without running omaplink.exe

After it comes up to regular Nook (looking exactly like it did before) connect the USB.

Does the PC say "Found new USB device"?

It might, if it does, select the correct driver that you unzipped.

Now run ADB.

Did you download ADB already?

If not, you can either download the SDK from Android or try the minimal here: http://xdaforums.com/showthread.php?p=42407269

C:\> [b][i]wherever-you-parked-ADB[/i]\adb shell[/b]
# [b]ls -l[/b]
[i]big-list-of-files[/i]
[Nook Touch General] hrulik:
windows 8.1 driver problem

Hello,

I have trouble to install fastboot/adb driver to windows 8.1. Driver is installed in advanced boot mode, but device not recognized anyway.

In case nexus4 disable corresponding usb host helped. Not work with nook. Any idea?

thank you
[Nook Touch General] Renate:
Step one, use Device Manager and see if it says Android Phone / Composite ADB Interface.

See if any device is flagged in yellow with an exclamation mark.

Run omaplink.exe with no arguments. Does the ADB green "LED" show on the popup?

If adb says "no devices found" but omaplink show green then you need to edit

C:\[i]<user directory>\<user>[/i]\.android\adb_usb.ini

You need to have a single line in it that says:

0x2080
[Nook Touch General] kazem_aryan:
my problem is that computer did not say found any device!

i retry all of instructions again but...! :(
[Nook Touch General] hrulik:
Only unknown device. http://prntscr.com/2nalbq

If I set driver manualy (android device -> google inc -> android adb interface)

http://prntscr.com/2name8
[Nook Touch General] Renate:
[MENTION=4225856]hrulik[/MENTION] It looks like your PC is seeing/using a Sony Ericsson driver.

Make sure that there is no Android device (besides the Nook) plugged in.

Check to see if the "Hardware Id" in the properties is actually 2080/0007.

When selecting a device driver do not use any selections.

Say, "No, I will choose" until you come to "Have disk" and select the directory with the unzipped driver.

I made a minor change to the driver, get the new one here: http://xdaforums.com/showpost.php?p=49665945&postcount=279

You didn't have a problem loading the driver to get the bootloader going, why now to get the ADB going?

It's the same driver.

[MENTION=2862980]kazem_aryan[/MENTION] Well, something is wrong.

Start Device Manager then plug your Nook in.

It should refresh and something should be different.

Do you have new storage volumes? Can you see new disks?

Use this utility and locate your Nook on the left pane.

Copy the right pane (and blank out your serial number).

To all: If you have problems loading drivers state Windows version and 32 or 64.
[Nook Touch General] kazem_aryan:
After plug in nook,the only things that changed, is 3 items in device manager

and in "usbview", this item:

View attachment 2544660

and this is the right pane for that item:

Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 (64)
idVendor: 0x2080
idProduct: 0x0007
bcdDevice: 0x0216
iManufacturer: 0x01
0x0409: "B&N"
iProduct: 0x02
0x0409: "NOOK GlowLight"
iSerialNumber: 0x03
0x0409: "3034750005993110"
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x05
Open Pipes: 2

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x01

Configuration Descriptor:
wTotalLength: 0x0037
bNumInterfaces: 0x02
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xE0 (Bus Powered Self Powered Remote Wakeup)
MaxPower: 0xFA (500 Ma)

Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x08
bInterfaceSubClass: 0x06
bInterfaceProtocol: 0x50
iInterface: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x01

Interface Descriptor:
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x42
bInterfaceProtocol: 0x01
iInterface: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
[Nook Touch General] Renate:
Well, you've got an ADB interface right there.

Look at "Other Devices" in Device Manager.

You should see the ADB interface there.

Load the driver for it.
[Nook Touch General] hrulik:
No any other android devices pligged in. Also field "Hardware Id" is absent in properties list

I use Windows 8.1 x64, looks like it is problem USB host driver at win 8.1
[Nook Touch General] kazem_aryan:
no, in other device no change happen when plug in device. only this 5 items.

when i plug in device, the nook must be in normal mode(usb mode) , right?!
[Nook Touch General] Renate:
Well, that ADB interface is somewhere in Device Manager.

Is it at the top under "Android Device" or "Android Phone" (you are scrolled down in the screenshot).

Or is it in "Other Devices / Unknown Device".

It's got to be somewhere.
[Nook Touch General] Renate:
Well, the joke's on me.

I just tried to get ADB working on a new Nook and it was a bear getting the correct drivers loaded.

Hints: Use usbview (linked above) to make sure that you have that important FF 42 01.

You see disk drives from the Nook in device manager.

Try reinstalling the driver (by taking the wizard's suggestions) for those.

You want "Composite USB Device".

Eventually it will try to load drivers for the disks and also the ADB.

Good luck.
[Nook Touch General] hrulik:
Can you send to me this zip to?
[Nook Touch General] Renate:
No, that stuff is very old. It was an experiment. We've moved beyond that.

Didn't you say that you had successfully extracted init.rc, modified it and put it back?

Use the usbview.exe quoted above to see if you have that FF 42 01 as quoted above.

Then all you need to do is get the drivers working.

You don't need to do any more USB booting with omaplink.exe

You can use omaplink.exe on a line all by itself to see if your Nook had ADB and the driver is loaded.

After that it's only a question of running adb.exe
[Nook Touch General] hrulik:
before that I had not even arrived. I uninstall rough USB Host driver. Now trying switch nook to fastboot mode. I turn nook completely then stick usb, then for 1-2 seconds appears "usb device not recognized" and then nook just booting. I certainly do not have time to install the driver for these 1-2 seconds.
[Nook Touch General] Renate:
No, of course not.

But your system should have identified that there is a new device.

It should have displayed a "New Device Found" popup.

At that point you should be able to install a driver even though the device interface has disappeared already.

Are you saying that when you do the full omaplink command it just sits on "Waiting for bootloader" and doesn't go further?

You speak of "fastboot", do you mean the bootloader?

The bootloader interface appears for only a few seconds.

The fastboot interface has no timeout and will sit there forever.
[Nook Touch General] hrulik:
No "new device found" popup, only this http://prntscr.com/2nn5ae

>Are you saying that when you do the full omaplink command it just sits on "Waiting for bootloader" and doesn't go further?

Yes it is, I think the reason is that the driver is not installed propetly
[Nook Touch General] Renate:
For people trying to get the ADB interface going and have problems with the drivers:

The PC loads in the drivers for "USB Mass Storage Device" but doesn't load the driver for "USB Composite Device".

Therefore the ADB driver never finds a place to install.

Go to Device Manager.

Look under "Universal Serial Bus Controllers".

Find a "USB Mass Storage Device".

Check "Properties" to see that the location says Nook.

Hit "Update driver".

Let it find the best driver by itself.

It should have found "USB Composite Device" and installed that.

Suddenly more unknown devices will pop up.

The PC should be able to find the drivers for the 2 volumes all by itself.

The ADB interface will cause a New Device Found wizard to start up.

That's where you keep saying "NO!" until you get to "Have Disk".

Select the unzipped driver directory.

[MENTION=4225856]hrulik[/MENTION] I don't know what is going on, but make your PC forget that it ever saw a Nook.

There are three registry keys that you should delete.

You will probably have to take ownership of the keys before you can delete them.

Permissions... / Security /Advanced / Owner / Change owner

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_2080&Pid_0007
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_2080&Pid_0007&MI_00
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_2080&Pid_0007&MI_01
[Nook Touch General] hrulik:
At this moment USB Composite Device installed and working:

http://prntscr.com/2nu4a4

But adb/bootloader cant setup anyway, Device failed enumeration

when there is 1-2 seconds I have to click on it, Hardware Ids - USB/unkown

http://prntscr.com/2nu82v

I found this http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx

think this is reason
[Nook Touch General] Renate:
[MENTION=4225856]hrulik[/MENTION] Did you delete the registry keys like I said?

You are getting error 45 not the 43 mentioned in that referenced article.

Also, all the USB device descriptors are version 2.0 so that doesn't apply.
[Nook Touch General] hrulik:
45 becouse device is disconecetd. it connected only 1-2 sec.
[Nook Touch General] kazem_aryan:
ADB

I've got to install driver! :D

What is next step?! :cyclops:

I Want anstall apk apps and some fonts.
[Nook Touch General] Renate:
Does ADB work?

C:\>adb shell
# ls
[i]<lots of files listed>[/i]

Then:

C:\>adb install [i]myfavoriteapp.apk[/i]

Probably ButtonSaviour to get some soft buttons on the screen would be a good idea.
[Nook Touch General] kazem_aryan:
ADB driver installed,

but... How can i check adb working?! in "Minimal ADB and Fastboot"? :confused:

in omaplink, the light of adb is green.
[Nook Touch General] Renate:
Good, that means that you rooted correctly and you have a working driver.

First, it's completely unimportant but you obviously loaded a bad driver at some point.

Registry edit:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{3F966BD9-FA04-4EC5-991C-D326973B5128}

and set the (Default) value to Android Device instead of %ClassName%.

That will make things look prettier in Device Manager.

For anybody else if theirs says "Android Phone" you can modify it likewise.

Yes, you need to install adb.exe and modify adb_usb.ini as described above.

The "Minimal install" is one solution.
[Nook Touch General] kazem_aryan:
ADB

I've download SDK, and run adb.exe

and this is result of adb shell

now i have 2 questions!

1.I can install apk files by this command "C:\>adb install myfavoriteapp.apk" right!?

I do that and messaged that success. but how can i open this apps in NOOK?

2. Can i install all apps that optimized for NST in NGL? and how?!

TNX
[Nook Touch General] Darrian:
I apologize if this has already been covered, but I was wondering if there is a way to repartition the internal storage so that less is available to the system and more is available to sideload my drm-free epubs. I really want to get one of these just for reading, but no sdcard and the storage available for personal files is just pitiful.
[Nook Touch General] idefix0815:
Tarball for easy rooting with Linux

First of all, many thanks for your great work!

I created a collection of files that should make rooting the Nook with Linux a breeze. It contains the files needed to boot cwm using the x-loader-usb method provided by straygecko and a couple of scripts I mostly took from NookManager and modified according to my needs, plus (also from NookManager) the binary files to be installed on the Nook.

There are scripts to boot cwm, patch the uRamdisk for ADB, install busybox, su, ReLaunch, enable non-market apps, disable and re-enable all B&N apps, and some more.

There is also a script that patches the uRamdisk to make /sdcard a symlink to /data/media, since some apps (notably recent versions of CoolReader) need an SD card present to work properly and there is enough space at /data. I haven't encountered any problems with this approach yet. Comments are very much appreciated.

Last but not least there is a detailed README file. Make sure to read it carefully. It contains (among others) a section on how to setup ADB on Linux and, most importantly, tells you what the scripts do, how to use them, and whether they have any additional dependencies you need to install on your computer.

I used these scripts several times successfully to root my Nook and I hope they will be helpful for other people as well.

Edit 2014-02-04:

Add a script to check for necessary tools and libraries and document in the README

Add note about yiselieren's problems with USB 3.0 to the README

Add note about the libusb-0.1 dependency

Edit 2014-02-02: Update README: At one point it said "hyphens" where it should have said "quotes"
[Nook Touch General] Renate:
[MENTION=2862980]kazem_aryan[/MENTION] To gain access to things you need a Launcher.

Many folks use Re-Launch, I use ADW Launcher.

I have no particular reason for using that, I just happened to use it.

Oh! I just looked at Re-Launch and I don't think that I'd like it.

I don't use all that many apps, especially on my Nook.

OTOH, Re-Launch will allow you to select an app without using the Home button.

If you need/want to use the "n" key for a real Home key you will need to modify or install something.

ButtonSaviour is one approach that will give you soft keys to get Home.

Yes, a link should be able to deal with the /sdcard question.

I've thought about how I would partition a NG2.

Personally, the first thing that I'd do would be to get rid of the FAT and UMS.

Having /media for your sideloaded stuff and syncing via UMS is a bit bogus.

If you wanted to be radical, you could delete /factory, /media and the mysterious mmcblk0p8.

That gives you about 1 Gig.

I'd chop down the /data in size by 1 Gig.

I'd make a new ext3 partition /sdcard at the end with that 2 Gigs.

Throw in one symlink for /media to /sdcard/media for things that want it (like Adobe DRM on Reader).
[Nook Touch General] kazem_aryan:
Re-launch is very ugly!

Is ADW Launcher prettier than is?! :D

Last Question! : how can i copy fonts in nook?! i need some font to open some non-english books.

Thank you very much for all your help and useful information :)
[Nook Touch General] Renate:
Fonts and RTL text is addressed here http://xdaforums.com/showthread.php?t=1367829
[Nook Touch General] hrulik:
Success

Hello Renate,

I found another laptop with window 8 x64. I followed your instructions and everything went absolutely no problems. Now I have NGL New with adb and root.

Thank you very much!

On windows 8.1 x64 as I wrote above, do not get to do so because error code 43. I googled this error. Internet full of messages like "windows 8.1 breaks fastboot" and something like this. It not resolved at this moment :(

Thank you agein!
[Nook Touch General] yiselieren:
Success

idefix0815, thank you very much, everything works just great.

Only one note - when I connected my NookGL to USB 3.0 port omap3_usbload didn't work (most libusb calls return EAGAIN). When I reconnected it to USB 2.0 port everything works fine.
[Nook Touch General] idefix0815:
Thanks for your report! I just uploaded an updated version of the tarball that contains a note about your findings.

I also ran into some problems myself when trying the scripts on a 64-bit machine. The problem was that the (32-bit) omap3_usbload requires a 32-bit libusb-0.1 which I had not installed by default. I added notes to the README and a script to the tarball (05-check_prerequisites.sh) to check not only for missing libraries but also for mkimage and sqlite3. If it encounters an error it tells you what to do/install.

Side note: In the process some of the scripts (those that previously had numbers 01 - 10) got 10 added to their numbers (so they have 11 - 20 now).

Edit: What I forgot to say: I don't own any USB 3.0 hardware, so I cannot try using USB 3.0 ports myself.
[Nook Touch General] headala:
So are we sure that we can't use Win 8.1? That's all I have right now and I don't have anything but a USB 3.0 port. So there's not anything I can do right now, right?:crying:
[Nook Touch General] Renate:
In the Windows domain the only issue is getting unsigned drivers installed on overprotective versions of Windows.

If you can do that, then omaplink.exe will work fine.