yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] geeyoff:
I'm having the same two questions as dumalkin, but my confusion starts earlier. I'm able to install busybox.apk as per N00b-un-2's instructions but I don't know how to "run the busybox app," as he puts it. Help, please, for someone who's totally unfamiliar with ADB (but comfortable working within a shell)?

Also, I'm not sure how to install nano or bash because the files don't exist on my Windows machine. Are those binaries supposed to appear after running busybox, or am I supposed to download them from somewhere? TIA.
[Nook Touch General] :
Try this command in ADB...

adb shell
am start -n stericson.busybox/.Activity.MainActivity

...to launch the Busybox app on your NGL. :good:
[Nook Touch General] geeyoff:
Thanks, but no luck. Here's the output:

# am start -n stericson.busybox/.Activity.MainActivity
Starting: Intent { cmp=stericson.busybox/.Activity.MainActivity }
Error type 3
Error: Activity class {stericson.busybox/stericson.busybox.Activity.MainActivity} does not exist.

I've tried the command from within three different filesystem locations, those being /, /system, and /system/xbin (which is where busybox got installed.)

At least, I *think* that's where busybox got installed. I did things exactly as N00b-un-2 specified, which should place busybox in /system/xbin/. However, when I run "ls /system/xbin/" it lists "busybox" as the output, but when I do "ls -l /system/xbin/" it doesn't return any output at all. Confusing...
[Nook Touch General] :
Aha! That right there's the problem!

Try the command from within /system/bin. /system/xbin is where Busybox got installed, but its applets are symlinked to /system/bin and are consequently only executable from /system/bin.

Give that a try. :good:
[Nook Touch General] geeyoff:
Hmm. Trying it from within /system/bin returned the same error message as before. :(

Is it possible that something went wrong when I first followed N00b-un-2's instructions for installing busybox? I no longer have the output from those steps, but when I try to redo those steps, things get odd. Here are some examples:

$ adb shell chmod 6755 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: Stale NFS file handle
$ adb install busybox.apk
635 KB/s (2604627 bytes in 4.001s)
pkg: /data/local/tmp/busybox.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]

I understand the second failure ("INSTALL_FAILED_ALREADY_EXISTS") but I don't know what's up with "Stale NFS file handle."

Also, for what it's worth, here's something else that might or might not be informative. The following happens within the shell:

# ls -l /system/bin
-rwxr-xr-x root shell 26388 2008-08-01 07:00 AacDecTest
-rwxr-xr-x root shell 30404 2014-05-01 10:28 AacEncoder_Test
[I](many more files listed, and then...)[/I]
lrwxrwxrwx root root 2013-11-20 10:40 dumpcrash -> dumpstate
lrwxrwxrwx root root 2013-11-20 10:40 cat -> toolbox
lrwxrwxrwx root root 2013-11-20 10:40 chmod -> toolbox
[I](and lots more files linked to toolbox, then...)[/I]
lrwxrwxrwx root root 2013-11-20 10:40 wipe -> toolbox
-rwsr-sr-x root root 22364 2014-12-23 12:03 su
#

Does that output provide any clues? Thanks.

Edit: one more experiment that didn't work:

After poking through spedinfargo's notes at http://xdaforums.com/showpost.php?p=50419404&postcount=350, I tried a different busybox installation command and got a different error:

$ adb shell /system/xbin/busybox --install -s /system/xbin
/system/xbin/busybox: remote access failed
$

Does that suggest any possible fixes?
[Nook Touch General] geeyoff:
Post-rooting steps for total newbies like me.

After reading lots of threads and experimenting, I managed to get my NGL set up how I wanted. For others who, like me, know nothing about rooting, here's what I did.

First, many thanks to N00b-un-2, ИΘΘK¡€, Renate NST, paulobrien, and spedinfargo for all of their help throughout the forums. Everything here is more or less pieced together for separate pieces of advice that they'd posted earlier. Also, sorry if anything here seems trivial or annoyingly obvious. Thing is, it wasn't all obvious to me until after I'd made sense of it all... :o

Anyway, I'd followed N00b-un-2's rooting instructions at the top of this thread, but when I tried installing Busybox, it seemed as if things weren't working out (I'd see "rm failed for -f, Read-only file system"). Eventually, though, I just decided to ignore that issue and stop worrying that I was going to brick my Nook. :fingers-crossed:

First I plugged my Nook into the computer's USB port and connected to it via adb. In a terminal, I typed

adb connect 10.0.0.12

(with those digits being the IP address of my Nook, which I figured out by going into the Nook's settings, selecting Wireless, and clicking on the SSID that it was connected to.)

Next, I downloaded and unzipped N00b-un-2's collection of apps from here: http://xdaforums.com/showpost.php?p=54855773&postcount=1 Within the unzipped folder, I ran this command:

adb install ADWLauncher.apk

After that, it was all easy. When I hit the N button on my Nook, it gave me the option of completing the action using "Home" or "ADW Launcher." After choosing the latter, I was looking at something similar to the home screen on my Android phone. Playing around with the softkeys on the screen took me to the App Drawer that displayed various other apps (e.g. browser, library, etc.)

To load up my Nook with additional apps, I'd find one on the Google Play store, then copy-and-paste the URL into http://apps.evozi.com/apk-downloader/ in order to download the package. Then I'd install it on my Nook via USB using the aforementioned "install" command. To uninstall an app that I didn't like, the command was

adb uninstall org.adw.launcher

(or whatever the undesired app is. To see the apps by their name, run "adb shell ls -l /data/data". I found this helpful, because the files I installed had a different date than the ones that came stock on the Nook.)

Also, I could only install apps that were developed for Android 2.1 and earlier. Some apps on the Google Market are too recent, like the Kindle app, but by searching for the app here on xda-developers, I was able to find some earlier, compatible versions.

Thanks again, everyone, for your help. I hope my meager contribution here can help spare one or two people a couple hours of fiddling and worrying.
[Nook Touch General] JPo_23:
Hi,

Thanks very much for the guide. I had some trouble getting the driver installed and eventually found an alternative way to do it, which doesn't involve right clicking on the device before it disappears.

If you open an elveated command prompt and type the following:

set devmgr_show_nonpresent_devices=1

and then launch device manager from the same command prompt by typing:

devmgmt.msc

and then go to 'View' and select 'Show hidden devices', you'll be able to see the omap3660 device and set the correct driver for it.
[Nook Touch General] MrBollo:
Aldiko

Hey all, and thanks for all the instructions here. So, I installed Aldiko to be able to read public library EPUB books on my newly rooted Glowlight.. but when enter my Adobe login details I get an error message saying there's no SD card present. Granted, that is true.. but I wonder is there a way to tell the Nook to use the internal storage instead? I've been using Aldiko with a Nexus7 previously and that worked fine without an SD card so I just though it's about how the device is set up in terms of memory definitions.
[Nook Touch General] Kramar111:
[MENTION=6340636]MrBollo[/MENTION]

http://xdaforums.com/showpost.php?p=53896500&postcount=408
[Nook Touch General] MrBollo:
Thanks Kramar111! Sorry for my noob-ness, but could you help me accessing uRamdisk? I tried through Root Browser but I couldn't locate it... Also tried with omaplink that I used when rooting according to the first post in this thread, but the boot partition no longer shows up when I connect with USB...
[Nook Touch General] :
You can mount it in the shell using this:

mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot

Then you can use Root Explorer.
[Nook Touch General] Eddie Hicks:
Can't install the USB drivers

I have the new nook Glowlight. I want to root using the process on this thread but I'm stuck at the very beginning. I have downloaded all of the files and my OS is Windows 7 64bit. The problem is installing the drivers. I'm using a laptop that I never connected my nook to before today. I tried a half dozen times to install the drivers by right clicking as fast as I can on "omap3660" . The only thing that happens is Windows installs it's own drivers or drivers from the nook I'm not sure which ones. Each time I fail to install the drivers I use the process of editing the registry to remove the drivers using the program linked on this thread and the command "psexec -s -i -d regedit.exe". I delete the Nook bootloader's device ID "0451:d00e" and some of the time I search nook in the registry and delete 32 other nook keys. After all of that "omap3660" does pop up in the device manager when I connect the nook but as I said right clicking on it does nothing and Windows installs it's own drivers. I can't figure out what I'm doing wrong. Doesn't appear anyone else is having this issue. I would appreciate any advice. Thank you very much.
[Nook Touch General] Renate:
I know that getting the drivers installed on Win7 has been a problem.

Unfortunately, I don't even use Win7 so I can't give any specific advice.

It seems to me that on XP the "Found new hardware" dialog pops up and stays up even on briefly appearing devices.

Maybe you checked "automatically install" or something at one point?

Does this help? http://support.microsoft.com/kb/2500967
[Nook Touch General] Eddie Hicks:
Thank you very much for your reply. I gave up trying on my Windows 7 laptop and tried again on my Windows 8.1 desktop. I was able to get the drivers installed after going through a big hassle getting Win8 to let me install an unsigned driver. Anyway I still didn't get very far. I ran the omaplink command as instructed and plugged in my nook. I didn't see a popup to manually select android_winusb.inf but I did get something in the command prompt. The furthest it got was waiting for fastboot and not waiting for ADB as per your instructions. The attachment is a screen shot of where I am. Do you think you know what I need to do at this point?

[IMG="Screenshot of command prompt"]https://dl.dropboxusercontent.com/u/22954589/screenshot.JPG[/IMG]
[Nook Touch General] Renate:
Offhand, I believe you want the u-boot13.bin at 175,024 bytes.

Also you need the same drivers for fastboot too.

While you are doing this, run devmgmt.msc

If you stall with an unknown device, then you need to install a driver.

If you stall with nothing unknown, then your u-boot is wrong/bad.
[Nook Touch General] bryxer:
Back and Menu on fullscreen apps

Hi everyone. Sorry if I go slightly off-topic.

I did the root, everything worked fine. I have ADWLauncher now, can install apps etc.

The main concern I have now is that many apps hide the status bar at the top where the software buttons for "back" and "menu" are. I find that a lot of times I need these and my only alternative is to go back all the way with the "n" button and sometimes this isn't even enough since the app will just remember where it was if reopened.

I searched online and found changes to build.prop but none seem to apply to the old android 2.1 in the Nook GlowLight.

Is there any way to force these buttons to remain visible even if the app wants to go full screen? Alternatively, is there any way to do "back" and "menu" even without seeing the buttons? I wouldn't mind tapping blindly on predefined locations or some other blind gesture. As long as the functionality can be accessed I'd be happy.

Thanks for the help!
[Nook Touch General] :
With the Nook GlowLight, since it's sans hard buttons, the free (or paid) app Button Savior is a real life saver. Google it on your PC (or your Nook, lol) and read up on it, and then I can provide you with an .apk for it if you don't have GApps on your Nook.
[Nook Touch General] bryxer:
This app is just what I needed, thank you!

I got the apk from the play store and sideloaded without issue. Works just as expected (and it's footprint on screen while reading is tiny)

The reader is fully functional now!

Thanks again!
[Nook Touch General] studiostustar:
Hey guys! First timer here on the forums. I really appreciate all the knowledge here! I have the latest Nook Glowlight model and was thinking about rooting it. BeforeI attempt it I just wanted everyone's opinion. Is it worth it? What are the capabilities and what all can it run? I appreciate everyone's feedback in advance, like I said I just want to make sure it would be worth it before I commit to the root process since it looks pretty involved. Thanks! :)
[Nook Touch General] mickeyratt:
Do it

Truth is you can do it in 15 minutes if you follow the GREAT step-by-step in the first post. However, I could never do it on Windows 7 but 8 worked for me. I can now surf the web on Opera Mini, read PDF magazines, access my Kindle library and even use WhatsApp.

By the way, I found the Advanced IP Scanner program very useful to find my Nook's IP as my router and Windows 8 have no network map capabilities. Good luck!
[Nook Touch General] mingeloh:
hi guys, i will be a proud owner of nook glowlight soon! and am wondering if i will be able to "unlock" the additional 2gb storage reserved for nook content if i were to root it.
[Nook Touch General] :
Of course, you can! :)
[Nook Touch General] mingeloh:
thanks bud for the quick response, im pretty confident in rooting but not too sure about what will happen after. will i be able to retain the original nook os after i have rooted, my sole purpose is to utilize the 2gb storage reserved for nook content so im not planning to mess up the actual operation of the tablet, like the backlight function and etc.

just 1 more question if it's okay, how do i go about unlocking the locked storage, must i download additional application or it will be shown once i plug it into the desktop?
[Nook Touch General] :
I personally don't know off the top of my head how to do it, but if you'll read very carefully through this entire thread, I believe there are instructions somewhere in here.
[Nook Touch General] kuvera:
I have a Nook Glowlight with sw version 1.3.1. I'm trying to root it to install a proper reader software that shows all Unicode ranges for fonts embedded into EPUB files, because the Nook Reader shows squares for some characters in my books, so the device in itself is completely unusable for me.

I followed this process on win7 and 8.1. On both I'm stuck at "Waiting for bootloader" in omaplink. The small OMAP window shows the increase in attached drives, but that's it.

The driver was installed with Have Disk selection. On win7 the device driver dialog then stated "Motorola Flash Interface" (I have a Moto G phone, which had been connected...), on 8.1 it was OMAP3630 (phone never connected).

Do you have some tips or pointers what to look for? Do I need a different set of files for version 1.3.1?
[Nook Touch General] photographernyc:
got half-bricked

hi guys,

before to find this thread I was searching how to root the Nook Glowlight (new version) and trough Win32DiskImager I thought I did the backup (pressed "read" and linked the paths). unfortunately it didn't save and I didn't check (stupid me), I dropped noogie image Win32DiskImager and all my folders on the small NOOK (this is how it shows internal storage in Expolorer) disappeared.

But since then when I start/restart/hard reset nook it loads, after that shows locked screen, I swipe but after that I'm getting warning -

"Restart Required. Your nook encountered a problem that requires a system restart."

If this problem persist, please contact Customer Service."

Under that warning button OK.

I press OK and it restarts and brings me to the same screen.

It shows time, wifi is connected, battery status, settings, everything looks okay. I see even the featured books in the bottom of the screen but unfortunately I can't get rig of the warning window and you can press OK only that leads to restart and to the same thing again.

I tried to root it even in this situation, installed driver, opened rom, updated uramdisk but it doesn't go further (maybe I just didin't figure out yet).

please advice what to do or maybe somebody will make an image of the internal storage drive so I'll be able to drop it in Win32DiskImager and return to point 0 and start from there again.

please please please!!!
[Nook Touch General] Kramar111:
[MENTION=4628928]photographernyc[/MENTION]

Please follow the steps below to Hard Reset your NOOK Glow light. Please note that a Hard Reset deregisters your device as well as erases all local content such as contacts, sideloaded documents, personal information, 4 digit passcodes, etc. It is recommended that you backup any sideloaded material before continuing. All Barnes & Noble content will be downloadable upon re-registering

To Hard Reset NOOK Glow light:

1. Hold the power button down until NOOK Glow light is powered off, ignoring the "Power off" prompt.

2. After Your NOOK Glow light is powered off hold the "NOOK Home Key" down then simultaneously hold down the "Power" button, release the buttons immediately after the “Read Forever” logo disappears.

3. If successful, a grey NOOK Logo will appear and the screen will refresh momentarily and flash yellow. A prompt will appear asking if you would like to perform a “Factory Reset,” Tap the "NOOK Home key" to confirm. Tap the "Home key" again to begin the process.

4. After a few minutes your device will reset and re-install all necessary software. Once completed, you will have to register the device again.
[Nook Touch General] DmPanther:
thank you thank you thank you thank you!!!! Спасибо, будешь в Нью-Йорке просто напиши променад за мной :))
[Nook Touch General] nedslark:
help

Hello guys,

I installed the drivers as in this tutorial, but i just cant run omap link, it says:

"0451:d00e, OMAP , pbi ok

Timeout reading ASIC id"

there is red indiciator by the "bootloader" , then the window closes after few seconds. What could be the problem ?
[Nook Touch General] Renate:
Oh, yeah, I just remembered how this all goes together...

The bootloader will only issue its ASIC ID once, upon connect.

The bootloader interface might be visible to your PC, but without the inital ASIC ID, it won't initiate anything.

To keep the handshaking all in sync always do things the following way:

Disconnect Nook from the USB

Full power down of Nook

Make sure that no ADB server is running (adb kill-server)

Start your omaplink command

Then plug the USB cable into the Nook

The Nook will awaken and the omaplink will do its stuff
[Nook Touch General] nedslark:
When I hit "omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie" in the CMD , this command isn't recognized, so i suppose my bootloader drivers wasn't installed correctly right ?
[Nook Touch General] Renate:
Huh? Did you download omaplink.exe?

What do you mean "not recognized"?

What did it type out?

Can you just see if the executable is even there?

C:\>omaplink.exe /?

If your drivers are not installed, the sequence will stall somewhere.

C:\>omaplink.exe 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 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
uid=0(root) gid=0(root)

I wipe my USB registry often and I just had to reinstall the fastboot drivers to get the output from above.
[Nook Touch General] FerociousAndroid:
Hello all,

Need a bit of help. I'm connected to my Nook GL via Wifi and at the Win7 (32bit) cmd prompt typing the follow commands and having some trouble. Not sure what I'm missing? Thx in advance.

C:\usbboot>adb install superuser.apk

272 KB/s (843503 bytes in 3.026s)

pkg: /data/local/tmp/superuser.a

Success

rm failed for -f, Read-only file system

C:\usbboot>adb shell mkdir -p /system/xbin

mkdir failed for -p, Read-only file system

EDIT:

Thanks geeyoff!

http://xdaforums.com/showpost.php?p=57761108&postcount=28
[Nook Touch General] FerociousAndroid:
ROOT and SU permanent?

Is there anyway to make the ROOT and SU permanent? I mean implanting the modified uRamdisk and superuser.apk and maybe a launcher like Smart Launcher 2 Free?
[Nook Touch General] Mythra13:
modding novice needs help

So, how did you get past the problem? I checked out the other thread that you linked but I'm not sure how that helped.

I followed the instructions at the beginning of this thread. I'm at what seems to be the very last step.

I established the Wifi link with adb connect 192.168.X.X I was able to push su.

When I try to enter into the cmd window adb install superuser.apk I get this error:

Failure [INSTALL_FAILED_ALREADY_EXISTS]

rm failed for -f, Read-only file system

I tired to do it by changing it to adb install -r superuser.apk and I still get this:

Success

rm failed for -f, Read-only file system

So, from what I understand, I've been able to:

1.) install bootloader driver onto my Nook Glowlight

2.) access it's boot partitions instead of normal internal storage

3.) Edit uRamdisk

4.) make a connection and push the "su" as per instructions

Issues I seem to be having:

1.) I've never seen any lights light up when using omaplink

2.) a failure message when doing the install command for superuser.apk

3.) I've used gparted to look into the partitioning of my Nook, but it only shows me the side loaded content partition, nothing else

*I'm only trying to shrink or delete the partitions for Barnes & Noble content and unnecessary stuff to have more room for sideloaded content. I'm not interested in any other additional apps or modding for my Nook Glowlight. Can anyone help me please?
[Nook Touch General] Kramar111:
[MENTION=6933777]Mythra13[/MENTION]

http://xdaforums.com/showpost.php?p=57902601&postcount=526

as for "rm failed for -f, Read-only file system" after "adb install", just ignore it
[Nook Touch General] geeyoff:
It's been a while since I did any Nook hacking, so I might not remember correctly, but I think that error might mean that you're trying to install something that requires a version of Android greater than 2.1. See if you can find an earlier version of superuser.apk. I seem to recall there being one somewhere within this thread...

Again, please take this suggestion with a grain of salt!
[Nook Touch General] Mythra13:
Thanks for the help, I've got it now. I guess I was more successful with it then I thought I was. I just needed to run it in noogie mode before connecting to it with gParted. I was able to do partitions without issue. I think what worked best for me was to delete the last four partitions, and then re-create them with the exact names and in the correct order. I created the NOOK partition as fat32 with over 2GB of space.

I still have a question that maybe someone here can answer.

What is the purpose of "cache" "reserve" and "userdata" ?

I understand that "userdata" is where Barnes & Noble books are stored, and probably some of the account information as well. Does it store information such as shelves that I create, or some other useful info?

I've shrank these three partitions to around 200MB each, and I just want to know if I will have an issue later on from doing that, or if maybe I didn't need to leave those as much space as I did. Just to mention, I plan to store loads and loads of ebooks on the device, and just use it for that purpose, no extra apps, no special modding.

Thank you for your time. :)