yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] Cookoospite:
Successfully backed up. :) Is there a way to get relaunch to open in app view rather than the file explorer? Being searching but I can't figure out how.
[Nook Touch Android Development] J_Palito:
Well, I've been restraining myself from posting this call for help but I've have run out of options or information so, here it goes..

I had my nook updated with 1.2.1 and rooted with glownooter until about 1 month ago.

The performance was terrible, Market stoped showing and updating installed apps, gmail crashing during sync... well, quite a problematic experience.

For accident, I've gone to the wrong setting under Nook Touch Tools and had a quite hard reset.

I thought - heck, why not do things right for now?

So I rooted with NookManager, and all was fine.

But then, after adding the GApps...

I get to the startup screen, choose Sign in, put my email and password and I get this message:

I am on WiFi, it is working correctly, using NookManager 0.5.0 and the GApps 0.5.0 also.

Does anybody knows the solution to this?

Thank you!
[Nook Touch Android Development] foobster:
I made the mistake of ordering a class 10 card before reading deeply enough to know that there were issues with them. I've been unable to get an image to boot off of either the class 10 card or a class 2 card that I had laying around. The nook just boots up as if there were no microsd card at all. I'm using dd to write the images on a laptop that has an integrated sd slot and I'm fairly confident that I'm doing this correctly. Does this seem like an issue with the class of the cards or might there be something else going on?
[Nook Touch Android Development] J_Palito:
What is the OS you are using and what method?

If using Linux, make sure you are flashing to the root of the SD, not to the partition (/dev/sdn instead of /dev/sdn1 for instance).
[Nook Touch Android Development] foobster:
Oops, this was my mistake :o. I was using /dev/mmcblk0p1 instead of /dev/mmcblk0. Thanks!
[Nook Touch Android Development] J_Palito:
You're welcome!!

Now... could somebody please help me with my problem?

I've searched everywhere but the solution only applies on other phones/tablets, not on nook since this isn't a ful featured Android distribution!!
[Nook Touch Android Development] jkjacek:
[Q] are the NookManager backup also kernel?

I want to change kernel.

Am I able return to previous state using NookManager backup?
[Nook Touch Android Development] straygecko:
Yes, a NookManager backup is your entire internal memory.

---------- Post added at 02:47 PM ---------- Previous post was at 02:37 PM ----------

Did you remove the B&N apps with NookManager or freeze or remove any apps with another tool? If so, put them back or unfreeze them. Second, try uninstalling Market as described in the NTGAppsAttack thread OP. It may or may not be the problem. If that doesn't work or there is no update to uninstall then restore your backup from prior to installing NTGAppsAttack and try again. GApps can be finicky and there are not always any clear answers when you get these communication issues. Read through the NTGAppsAttack thread for things others have tried when they have had these bogus communication issues.
[Nook Touch Android Development] laffer98:
I've tried this a couple of times with a 2gb and a 4gb sd card on both my NST and my NST Glow and every time the backup fails... The root itself works just fine. The backup fails no matter what I try even tryed after the root was done and it failed there too.

Is there away to bring relaunch up from the standard nook mode other than shutting down and restarting the NST?
[Nook Touch Android Development] straygecko:
You would need to boot NookManager and run the backup with adb shell to see what the backup problem is.

umount /tmp/backups
mkdir -p /tmp/backups
mount -t vfat /dev/block/mmcblk1p2 /tmp/backups
dd if=/dev/block/mmcblk0 bs=1000k | gzip -1 > /tmp/backups/backup.full.gz

Use Nook Touch Mod Manager to map a button to ReLaunch. I use a long press of then button to bring up ReLaunch but pick whatever button you like - a hardware button short or long press or one of the QuickNav buttons.
[Nook Touch Android Development] laffer98:
Thanks for the quick reply. I have a button remapped now and I will explore adb shell as soon as I have time.

One more question when using Amazon to get es task manager I find it and tell it to DL but it never actually starts the DL any ideas?
[Nook Touch Android Development] straygecko:
Get a logcat (more ADB) and post it. An easy way get up and going with ADB is to download QtADB. For the backup problem when you boot NookManager tell it to start ADB wireless then connect with QtADB and use the shell to try the backup commands. For the Amazon problem go into ReLaunch and start ADBKonnect then connect with QtADB and look at the logcat.
[Nook Touch Android Development] David0226:
I have two Nooks, a Nook ST and a Nook ST with Glowlight. Both are rooted using the NookManager tool. (Thanks for this GREAT tool.) I have a question about why I would be able to get ADB over USB working the NST but not the Glow. For various reasons I don't use WiFi much and it is usually turned off at my home. So I really want to get the ADB over USB working on the Glow. Any suggestions would be greatly appreciated.

In the interest of full disclosure, the NST has been rooted multiple times and not always with NookManager. Is it possible that ADB working over USB is a leftover from one of those other rooting packages?
[Nook Touch Android Development] straygecko:
Will the Glow do ADB over WiFi? If so, its probably a driver issue on your PC. Try some of the troubleshooting tips here.
[Nook Touch Android Development] David0226:
Yes, it will do ADB over WiFi as well as over USB when booted into NookManager.

This is very confusing.

I installed ADB Toggle which says ADB over USB is now enabled, but it still won't work.
[Nook Touch Android Development] straygecko:
If ADB works over WiFi it should work over USB. Does USB work at all - i.e. do the drives pop up on your PC when you plug it in when booted normally?
[Nook Touch Android Development] malc_b:
I've use this method on my NST and then on my new Glow. Both seemed to work fine. Relaunch runs on the Glow. I reset the NST and re-rooted it for the wife (different gmail). My new Glow I rooted and used my gmail address. In the past when I logged into to google play on my PC it saw my NST as "phone" and I could install apps direct on my PC. For the glow it doesn't see it. I still have the old NST "phone" listed with last date seen as when I reset it and re-rooted. Is this related to ADB not working or is there something I need to do to register my glow on google play?
[Nook Touch Android Development] David0226:
Yes, it connects and my PC sees two drives, the internal memory and the sdcard. Is it possible that this is caused by my attempting to us the same computer to access two different nooks using ADB over USB? (I never try to access them both at the same time.)
[Nook Touch Android Development] straygecko:
It shouldn't cause a problem for two different Nooks to connect. More likely the Windows drivers got installed wrong for the Glow. Go to Device Manager and click on View|Show hidden devices. Now delete everything that has a hardware ID with VID 2080 or says Nook. Look under any group that says ADB, ANdroid Disk Drive, Other devices, Unknown devices and Universal Serial Bus controllers. Now when you plug it in it should reinstall drivers.

---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------

Read through the NTGAppsAttack thread for hints on issues with connection to Google Play.
[Nook Touch Android Development] malc_b:
I've sorted it. I think the issue was that I hadn't used google play on the Nook Glow. When I ran that it asked me to accept the T&Cs. Some time later the Nook Glow appeared on google play opened on my PC.

I also got ABD to work on the glow (so maybe that was part of it). When I ran ADB it said needed superuser, so I tapped that then ran ADB again, after which ADB said connected.
[Nook Touch Android Development] straygecko:
Yep, you need to go into Market to get connected up to google play. ADB is related at all. Glad you sorted it out.
[Nook Touch Android Development] chrisnz1947:
rooted nook simple touch displays empty data directory

Hi I rooted my Simple touch using Nookmanager and all went well.

However then I select the data directory from the relaunch screen nothing is displayed (directory appears empty). Am I missing something?

Nook software version is 1.2.1
[Nook Touch Android Development] Kreatur3:
Edit: Nvm. I exited nook manager and removed sdcard. Reformatted card. Rewrote image to sdcard and tried again. Worked perfect this time.

Hey guys. Picked up a cheap nst w/ glowlight today. Made the SD card with the image. Got into nook manager just fine and am doing the backup. It's been on the "creating backup image" screen for over an hour now. It was completely empty of books. Did a clear of the reader previous to trying it. Any ideas?

Running fw 1.2.1

Thanks in advance.
[Nook Touch Android Development] straygecko:
That is normal. You need root to view the /data directory. Install a file manager (.e.g. ES File Explorer) that can run as root to view the /data directory.
[Nook Touch Android Development] the john:
Play Store?

I've searched the thread, but it's difficult to find which method applies to which version, so at the risk of sounding stupid: what's the best way to install Gapps? Mostly, I want it for Google Books. Thanks!
[Nook Touch Android Development] lekofraggle:
The John,

If all you want are Google books, I reccommend just downloading them on a computer, opening them in adobe digital editions, and then transferring them to your nook. I hear the playbooks app does not work well on the Nook.

But, if you just want root and gapps, this should work, but you need to add the gapps package in the op.

This is for version 1.2.1 of the bn software, but should work on others too.

Good luck.
[Nook Touch Android Development] speedman2202:
hiiii

i got root my with nook manager earlier and when i tried to make my device support arabic , i moved files to system directory my ES explorer and when i do that every-time i enter the sd card i\the screen flashes always ... then i do my backup and get back to 1.1.5 version and update it manually by download 1.2.1 then i burn nook manager image to sd card and when try boot with it ... it show me welcome screen for 15 sec's as u said ... then empty page!!!!!

i tried press on many buttons and all buttons with no success ... can u tell me whats wrong??!!!

thx
[Nook Touch Android Development] richardcoop:
I have just tried this to be able to get to the wifi at the B&N store and am now stuck in the traveling dots on rebooting. I used root manager and renmamed the old services jar.

Sometimes I guess you should stopfooling with stuff.

I need help restoring my system.

I am now going to load adb on my computer. Will I be able to restore my system?
[Nook Touch Android Development] Renate:
I don't know anything about the issue of B&N WiFi...

I must say though, before you get knee-deep in modding a Nook you should have ADB running already, otherwise you are flying blind.

When the dots are running continuously (and not stalling, flashing and restarting) you probably have a fully running Linux system that can be rescued.

You can run logcat and see what it doesn't like.

If the problem is that it can't start a Home application, you can even start one with the Activity Manager over ADB.
[Nook Touch Android Development] Celtic67:
Hi all,

Sorry if this is a stupid question, it's getting late & my searching isn't finding the answers.

I've just used NookManager to root my device again after I wiped it to get rid of my account to put my wife's on. Everything seems to be OK, but I've noticed that the media partition (where Nook stores books?) is only 245MB. I've got nearly 700MB free on data and am not likely to install many extra apps. Any way to use some of this for book storage?

I was thinking maybe repartition the Nook (unlikely), use a different book reader app, or create a link to a folder in data. Has anyone tried anything to get more storage? Other than just adding an SD card, that is.
[Nook Touch Android Development] straygecko:
Yes, ADB will get you in to fix the problem. You may have not set the permissions on the new services.jar properly. With ADB you can fix hat or rename back the old working services.jar.
[Nook Touch Android Development] tomleeuw:
??

Ithx for the manager, everything for fine, however....

I cant retour to my library, when I press the "n" and then press library it return to filemanager.

I guess it will be a simple setting, but i can't find out how to.
[Nook Touch Android Development] Tarnak:
Guys,

I've rooted by this good software but last time when I left my nook after reading, I finished with not working touch.

After restart by long holding power button its works again.

any clues?
[Nook Touch Android Development] mswells:
Is just rooted my NST (no gapps yet) and on reboot I accidentally selected home after checking the box. Is there a quick way of getting to ReLauncher other than re-rooting?

Also, I no longer have WiFi.

Edit: MAC address changed and router blocked Nook. WiFi works now.
[Nook Touch Android Development] Tarnak:
The simplest way is to install other launcher. You will get again ability to select home.
[Nook Touch Android Development] mswells:
How do I go about that if I cannot get to ReLauncher and I do not have gapps installed?
[Nook Touch Android Development] Tarnak:
Sorry, I supposed that you'll be able to copy apk and install it from adb.
[Nook Touch Android Development] mswells:
Thanks. I ended up adding a different launcher to the sdcard and re-rooting the Nook and it gave me the option to select relaunched or home.:)
[Nook Touch Android Development] Tarnak:
I've solved it by myself, seems to be a problem with simple task manager. Probably it removes some tasks without notify me :silly:
[Nook Touch Android Development] iddqd2:
Hello.

Can't get it working.

After boot and showing Nook Manager screen goes blank and nothig happens. Other tools isn't working too.

NST (BNRV300). Firmware 1.2.1 (tried on 1.1.0 with same effects then updated to 1.2.1).

What I should do next.

Sorry. Change SD-card and all work fine. Thank you TS
[Nook Touch Android Development] Torimu.Joji:
NST with Glowlight

Is this compatable with the Nook Simple Touch with Glowlight?
[Nook Touch Android Development] straygecko:
Yes
[Nook Touch Android Development] smart1:
Do kernel include the modifications for multitouch? Thanks
[Nook Touch Android Development] straygecko:
No, NookManager doesn't touch the kernel.
[Nook Touch Android Development] smart1:
Is it possible to use NM's backup function to make backup of rooted device (in addition to the backup that I've made prior rooting the device via NM) so that I don't have to use noogie? Thanks
[Nook Touch Android Development] Renate:
What's the objection to using noogie?

Just throw it on an SD card and boot.

If you don't like that use a bootloader approach:

omaplink.exe aboot.bin u-boot12.bin uImage-noogie uRamdisk-noogie
[Nook Touch Android Development] David0226:
You can boot the device using NookManager and connect using USB. Once you do this, you can copy the current (pre-root) backup files to your computer. Put them somewhere you can keep track of and rename them so that you will be able to

1) Know it is the un-rooted backup

2) Rename it back to the original name on the SD card if you ever have to restore from it.

Once you have a copy of the un-root backup on your computer, you can perform another NookManager backup of the rooted device. This will overwrite the non-root backup on the SD card, but you now have that stored on your computer.
[Nook Touch Android Development] nmyshkin:
Cleaning up folders from NookManager SD

So it looks like my power switch is becoming uncooperative. I finally managed to get the Nook started with the NookManager card in place and did another backup. So far, so good.

I thought I'd try inserting the NM SD card after normal boot and then use ADB wireless to invoke a reboot to see if the Nook would boot from the card that way or if it had to start up cold to work. To my relief, it actually worked (I hope CWM will do the same). Maybe I will NEVER shut off my Nook again.

My question is about the folders that the Nook automatically placed on the NM SD card: My Files, and others from various apps I have installed. Should I remove those from the card after ejecting it or can I just ignore them (it's an 8 Gb card so there's plenty of space).
[Nook Touch Android Development] OverByter:
I personally ignore them, it's more of an Android thing than anything specific to the way the Nook manages the SD card, I find that most of the directorys are created when the particular app is installed and unless you have the app use the card for storage or dB most of the directorys will be empty and not using any storage.

OB
[Nook Touch Android Development] remmons:
No ADB debugging

I used NookManager to root a Nook Simple Touch with Glowlight. The ReLauncher works, and I can start various apps, but ADB debugging is not working. I have used ADB debugging with various other Android devices (phones, tablets, etc.) so I am familiar with it.

When I connect the rooted Nook to my computer via USB, it is recognized as J:, and K: (SDcard) drives. However, if I start a command line and type:

adb devices

No devices are listed.

I do no see any way to turn on ADB debugging on the Nook. Most android devices have "Developer" options which include a option to turn on ADB debugging. I don't see this on my rooted Nook.

How can I get ADB debugging working?
[Nook Touch Android Development] OverByter:
You can use Nook color tools to enable usb debugging.

OB
[Nook Touch Android Development] straygecko:
NookManager already enables USB debugging you don't need Nook Color tools. Did you install the ADB driver for the NST and setup adb_usb.ini? See the Nook Color directions for installing ADB drivers. Works for the NST.
[Nook Touch Android Development] Renate:
adb_usb.ini is an extension to allow unknown vendor VIDs.

The latest version of ADB has 0x2080 listed as a "known vendor".

You don't need to modify adb_usb.ini

See: https://android.googlesource.com/platform/system/core/+/master/adb/usb_vendors.c
[Nook Touch Android Development] remmons:
Thanks to all for the info.

NookManager did not install Nook Color Tools. I'm not sure where to get it or how to install it without ADB. Where can I get it, and how do I install it?

I'm not sure why I should need additional drivers. I routinely use ADB to Access a Google Nexus 7, a Samsung S3 mini, a Samsung S1, various Android Virtual Devices (AVDs) and various other Android devices.. I also hesitate to install any other ADB drivers which could break my working connections to those other devices and emulators.

I connect the Nook Simple Touch with Glowlight (NSTG), and "adb devices" lists no devices. I disconnect it and connect any other Android device, and "adb devices" lists that device.

I understand that the NookManager is supposed to enable USB debugging, but in my case it is not enabled or not working. I connect the Nook Simple Touch with Glowlight (NSTG), and "adb devices" lists no devices. I disconnect it and connect any other Android device, and "adb devices" lists that device.

I also rooted the Nook with ClockWorkMod and glownooter. That did install NookColorTools, but I had various problems, including no ADB access. I factory reset the NSTG, and tried the NookManager approach.

In general, do you think it is better to root the NSTG via NookManager or ClockWorkMod/glownooter method?

I would really like to have an Eink Android tablet that I can see in the sunlight. I'm surprised no one makes one. So far, for me, the NSTG is not really fitting the bill. It seems to be painfully slow, and crashes on many apps. Do you have similar experiences with your Nooks?

Thanks for the help.
[Nook Touch Android Development] straygecko:
The INF file for the driver lists the Vendor ID's it will work for. Lots of vendor ID's are already there but the B&N vendor ID isn't there so ADB won't work. At least that's the way its been in the past. From Renate's post it sounds like that may have changed in the latest ADB version as the B&N vendor ID has been added as a known vendor and you no longer need to add it to the adb_usb.ini. So perhaps just downloading the latest ADB version and updating to the driver from that version will do the job rather than using the Nook Color INF file.
[Nook Touch Android Development] wozhere:
Sometimes adb over WiFi (if interested) initiates but doesn't stay up, not always. There is a major thread on xda somewhere about this problem. Basically this is what I posted there:

A lot of factors can be involved including firewall, etc and router f/w protocols. Solution for me when this strikes:

Install ADB Wireless.

Install and launch Airdroid.

Open up URL given by Airdroid, then it's file manager in browser, eg: SD Card folder.

Launch ADB Wireless, connect.

Works every time when ADB Wireless keeps dropping connection, basically Airdroid seems to keep it up as I initially hoped.

Tip: to get a command (DOS) Window in a folder location:

Open the location folder

Hold down shift key, right-mouse-click, choose option: Open command window here.
[Nook Touch Android Development] remmons:
Renate,

I saw your post at http://xdaforums.com/showthread.php?t=2122046, which specified these settings in default.prop:

ro.secure=0

ro.allow.mock.location=1

ro.debuggable=1

I have found that my ADB works via wireless, but not via USB. Using the wireless ADB, I found these settings on my Nook:

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=0

persist.service.adb.enable=1

Could this cause my ADB to not work via USB?
[Nook Touch Android Development] straygecko:
Nope. Run like that all the time on my NST and ADB works fine. Since you can adb via wireless I don't think you have an issue on your NST.

The change Renate mentioned concerning adb_usb.ini and presumably the drivers that come with adb so that adb will recognize a Nook looks like it was introduced with the 4.4 version of adb.
[Nook Touch Android Development] rushic24:
Can you please make a video tutorial

Would this work wid nook simple touch (not glowlight)
[Nook Touch Android Development] remmons:
I'm confused. I just updated my Android SDK to the latest version, but when I enter the command:

adb version

It responds:

Android Debug Bridge version 1.0.31.

You're saying it should be version 4.4? Am I 3 versions behind?
[Nook Touch Android Development] straygecko:
4.4 is the Android SDK version that should include the adb version with the adb_usb.ini change. That said, Google sure makes it hard to figure out what made it in what. It appears adb 1.0.31 is the latest adb (no commits to update the version numbe rbeyond 1.0.31 in the code) but the adb_usb.ini change wasn't committed until months after the 1.0.31 version change was committed. I ran SDK manager and updated my machine with the Android 4.4.2 SDK and adb still reports 1.0.31. So I'm unsure if the adb_usb.ini change has actually been released.

In any event, you will need to load the driver from the link in my earlier post. I forgot, google does not supply the drivers for any devices other than the Nexus. http://developer.android.com/tools/extras/oem-usb.html B&N doesn't supply us with a driver so you'll need to get it from the link I posted earlier. When you rooted your other devices you probably loaded some kind of toolset from the manufacturers which included their adb drivers.

Once that is loaded plug your NST into your PC and see if the adb driver installs. If it does try adb. If adb still doesn't work create the adb_usb.ini file per the directions in the link.
[Nook Touch Android Development] osowiecki:
Have you tried to add these 2 lines to

/system/bin/clrbootcount.sh

?

EDIT :

# umount /sdcard

failed.