Database Users

[Q] USB Host for non-techs

I just started a wiki here
USB Host mode
I am hoping that you who actually know how to do it would help develop a set of instructions that are simple enough for a literate, adventurous non-tech (like me) to follow.
UPDATE: The wiki now has a complete list of installation instructions. You'll have to hunt through verygreen's thread below for operating instructions till they organized on the wiki.
The wiki and this thread (where noobs like me can post) are based on verygreen's
[WIP] USB Host support (working)
I asked verygreen and ros87 to do the USB Host mode for the Nook Simple Touch. Verygreen announced success within 48 hours. The hack has gotten whipped into shape there with the amazing help of ros87, Renate NST, mali100, and other superb xda people.
The project started at mobileread.com:
Project: E-Paper Tablet (touch-typable!)
Thanks to fellow mobilereaders for support, especially Kumabjorn, poliorcetes, and nealsharmon for donating money for devices.
The wiki is super rough. It assumes a new device in the box and a non-tech user. I started the instructions to show how simple they need to be. I will continue helping with that because it does seem difficult for techs to believe just how lost we can be with this stuff. My goal is to bridge the gap between techs and literate users so that non-programmers who want to type on the NST can. If you are an expert writer of users manuals, maybe you would help, too.
Honestly, I don't know the first thing to do now that my NST is on and registered. For example, I don't even know if I need to:
root the NST first
install adb (which I also don't know about)
or what. I have studied the thread, so I will be familiar with the terms. But I'm completely clueless about actually doing the hack. I managed to unbox my refurbished NST, update its software to 1.1.2 and install a microSD card. The issue is, what exactly should be done now? Please leave your answers in the wiki! Thank you!

I would say the best way to start is from eded333's Minimal Touch http://forum.xda-developers.com/showthread.php?t=1346748 . That gives you a nice system with market and a launcher to install and start your texteditor or writing apps.
If I find some time i will create a small update-package that installs all the necessary things for the usb-host mode.

Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.

andrewed said:
Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.
Click to expand...
Click to collapse
1.1.2 is fine. You can still use eded333's MinimalTouch to root it and get a launcher.

Awesome. Will dive in, then!

As promised I created a small update package, to install all the necessary files and tools.
It is installable via Clockwork Recovery in the same way as eded333's MinimalTouch, which should be installed first, to get root, a launcher and a working Market.
Requirements:
Software version 1.1 or 1.1.2 (1.1.2 is recommended, as it fixes WLAN issues)
root, a launcher and working market (I recommend using eded333's MinimalTouch)
What it does:
changes the kernel to NST-kernel v0.1 with USB-Host and multitouch support
changes the uRamdisk to a uRamdisk with fixed init (needed for USB Input devices) and adb-usb
installs the busybox and sqlite binaries
adds the permission node for multitouch to /etc/permissions/required_hardware.xml
installs the app UsbMode-1.2 and the NullKbd-1.1 by Renate NST
adds the permission to enable the NullKbd
changes the qwerty.kl and qwerty.kcm.bin to the remapped one by Renate NST
installs the NookColorTools, so you can switch to the NullKbd
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher.
this is the first release and only tested by myself, so don't expect it to be bulletproof.
Credits go to:
verygreen, ros87 and everybody who helped with the USB-Host mode,
Renate NST, for all the effort making USB-Host support userfriendly (USB-Mode app, NullKbd, key remapping, testing),
wheilitjohnny and arkusuma for the Multitouch support,
eded333, for his great MinimalTouch,
Download:
usb-host-mt-pack_0.1.zip

Thanks, mali100.
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.

Renate NST said:
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.
Click to expand...
Click to collapse
Nice easter-egg didn't noticed this before. Thanks

Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.

andrewed said:
Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.
Click to expand...
Click to collapse
I'm using a 4G class 2 micro SD card for NOOGIE and it's fine.

where to?
Hi where to put content of META-INF? (dont wanna root again...)

mrWax said:
Hi where to put content of META-INF?
Click to expand...
Click to collapse
The META-INF folder contains the insallation script and the interpreter for the script, they are used by CWM to install the package and not copied to the nook.
(dont wanna root again...)
Click to expand...
Click to collapse
If you mean that your device isn't rooted, and you don't want to, then I have to tell you that root is needed to switch between usb-host mode and peripheral-mode, so root is mandatory.
If you mean your device is already rooted and you don't want to redo it, then don't worry, this package doesn't contain files that root the nook.

I had already rooted my nook another way...now what?
Friends,
I rooted my Nook using the instructions here (SalsichaNooter):
http://www.youtube.com/watch?v=O05Y7C9a4eU
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions. I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
I really would like to get a keyboard working on my Nook and feel like I'm so close.

nealsharmon said:
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions.
Click to expand...
Click to collapse
You don't have to revert anything, a device rooted with salsichanooter works fine.
I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Click to expand...
Click to collapse
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
Click to expand...
Click to collapse
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.

thank you
Thanks for your input. I will try the process you suggested.

It worked!
mali100 said:
You don't have to revert anything, a device rooted with salsichanooter works fine.
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.
Click to expand...
Click to collapse
I followed your instructions and it worked. Thank you very much.

Still Not working
I'm very new at this.
I have followed the above directions and patched with usb-host-mt-pack_0.1 successfully but my two USB keyboards are still not working.
I originally rooted my nook using TouchNooter 2.1.31.
I am using an OTG cable and am getting the solid green light after turning off current and selecting Host.
When i plug either keyboard (or bluetooth dongle for that matter) State changes from a_idle to a_host.
Other results:
Keyboard: none
all fields below that are blank.
Any suggestions on how i should proceed? Could this just be a matter of the keyboards not being compatible? What are the recommended keyboards?
Many thanks!

When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.

Renate NST said:
When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.
Click to expand...
Click to collapse
Thank you, Renate. That worked great. My Bluetooth is working and I'm using my apple wireless keyboard to word process. My arrow keys don't work so I have to do some touching or backspacing to edit in google documents.
I have a chronic case of CVS (eye condition). This is really gonna help me. Do you recommend a stand with space at the bottom for the cord?
Thank you so much!

Stand? I love mine. http://forum.xda-developers.com/showthread.php?t=1661902
You can use either a desk stand or the little bendy tripod.
The arrow keys should work, but they get rotated when in landscape mode.
There is a mod to make them not rotate.
http://forum.xda-developers.com/showthread.php?p=30260821&highlight=keyinputqueue#post30260821

[Q] Rooting newer Nook version: how to know which software?

I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.

There are at least two methods that work with the Glowworm.
You should not use any method until after you have
- made a noogie disk
- booted from it
- backed up your device
- restored that backup to a test disk (a 2 gig or larger microSD card, for instance) and confirmed that the test results in a disk that has 8 partitions.
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore seems to be only getting one partition restored and blowing out the other partitions.
I don't know if the stuff that eded is working on has come to fruition yet - he was looking at building a tool that could detect whether it was run on an NST or NSTG and root appropriately to the device.
The two routes I know work are:
- glownooter, the nooter project tool, includes Google apps and market support
- tinynoot, pasted together from various tools, gives you minimal root without google apps and with amazon appstore. Will work with either NST or NSTG because it's approach is so minimalist.

Thanks, roustabout! I will be sure to test the backups before I install anything else, then. Good to know!
In any case, what I am most concerned about is getting the right version of the rooting software for my device. I see that Nook devices have different firmware and that certain tools only work with certain firmware versions. I see no mention of my firmware version in any tools' websites, hence my apprehension.

hence the value of a backup
I saw your request on that and I think one of the issues here is that so many folks use Windows exclusively, and the backup process is so easy on linux that trying to tell people how to do it in Windows is like jabbing yourself in the eye with a stick, given that linux is free, vmware player is free, and linux can be installed and used for this job entirely in vmware player. On the other side of the coin, if you know nothing of linux, even using dd correctly will be a challenge since there's a pretty steep learning curve behind setting up a new OS successfully just to be able to get backups off an 80-130 dollar device.
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'

I didn't mention it, but I also use Linux at home (Kubuntu, like Ubuntu but with a better UI). So many people are now using Ubuntu that I find it surprising that the instructions even bother mentioning the OSes for which the operation is as difficult as you say. I remember when doing things in Linux was hard and Windows was easy, and at that time Linux was hardly ever mentioned!
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
Click to expand...
Click to collapse
I did not realize that the 1.1.5 release is glowlight-only. Great, thanks, I'm on to hacking this thing!

ok, so for you the backup process is:
- make the noogie disk
- put it into your device
- power cycle your device
- when it boots to "rooted forever," connect the USB cable to your linux box
- once the linux box mounts the NSTG as storage, pay attention to which device it is mounting it at. Assuming it's sdX:
- backup with dd if=/dev/sdX of=backup.img bs=1M
When that's done, disconnect your NSTG, throw media of some sort, larger than 2G, onto your box and test your restore with
dd if=backup.img of=/dev/sdY bs=1M
Once that's done, do an
fdisk /dev/sdY
and a
p to print the partition table.
You should have 8 partitions (and your backup.img file should be just under 2 gig.)
Hack away; if you ever need to restore, you can just drop the virgin image back on.
I take a snapshot like this of my device every so often since remembering how I got to whatever config I liked is harder than just backing it up.

Thanks for the backup instructions, the idea of testing it on a DVD-ROM looks to save quite a bit of trouble with the actual device..
I rooted with this terrific guide:
http://forum.xda-developers.com/showthread.php?t=1675706
The process was simple. I do have an issue where I need to install a Hebrew font but ES File Manager doesn't seem to see the root folders. I'm having a hard time googling my way out of this one, bu all the other little issues were fairly simple.
One issue that I will mention that was hard to solve was the inability to perform searches in the Market. This page helped me resolve that issue:
blog.the-ebook-reader . com/2011/07/15/rooted-nook-touch-fixing-market-search-and-other-tips-and-tricks-video/

I just figured out that the file manager has to have Root permissions enabled. I've enabled it and added some fonts to /system/fonts but I still cannot get Hebrew text to display on this device. All I get are the typical rectangles instead of characters. Any ideas about how to proceed?
Thanks.

Restore Nook 1.1.2
roustabout said:
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore .
Click to expand...
Click to collapse
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)

bubblewrapper said:
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Click to expand...
Click to collapse
Few people who will be knowledgeable will find your post buried here under this thread. i suggest that you simply start a new thread with a good descriptive title so that the gurus will find it.

Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.

roustabout said:
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
Click to expand...
Click to collapse
Actually, I think that I just need the fonts (or at least that would be a great first step). I put fonts with Hebrew glyphs in /system/fonts (using ES File Explorer in Root mode) but even after a restart it does not find the fonts (i.e. Hebrew text still shows as rectangles). I will fight with it some more in the coming days, if I don't succeed I will start a new, concise thread on the topic. There are plenty of Google posts on the subject, but all of the ones that I have seen (not Nook-specific) suggest that dropping the fonts is /system/fonts should be enough. Perhaps it is a permissions issue, I'll see if I can SSH into the device to see permissions.

dotancohen said:
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
Click to expand...
Click to collapse
Sorry that I am so slow to respond, but I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/

ladykayaker said:
Sorry that I am so slow to respond,
Click to expand...
Click to collapse
Thank you! You don't need to apologize for taking time to respond, you are under no obligation! But I very much do appreciate your assistance and am happy to wait patiently! You will notice that I usually google issues first to try to save us both the time!
I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Click to expand...
Click to collapse
Thank you. It seems that those posts are Windows-centric summerizations of information found here at XDA-developers. The root is pretty much the process that I used, but from the guide right here which has Linux directions as well.
By the way, the-ebook-reader site is often not responding for me. Is it just for me, or does everyone have trouble with that site?
Thanks!

version 1.2.0
UK glowlight ships with 1.2.0. Use tinynooter to root this. You may have issues installing apps atm though but you will get the browser at least.
http://forum.xda-developers.com/showthread.php?t=1961835

Thanks, Loney. In fact, I got this Glowlight in the US, and it reports that it has software verion 1.1.5. But the information will be good for others who might google this thread!

Nook Simple Touch Glowlight .. Need advice before rooting.

Hello all ...
Please .. I need some advice..
This is my first post. My sister has given me her Nook Simple Touch Glowlight. I would like to root it, as I've been looking for a device to keep notes and stuff on. I went as far as booting up with noogie.img and backing up the firmware. I don't know what to do, because I read that having a certain firmware changes everything? I don't think my sister updated the nook. Here is the information from the Settings / Device Info / About Your Nook.
Software Version: 1. 1. 5
Model Number: BNRV350
I read someplace that the sizes of the firmwares are different. The simple touch is 1. 82 and the simple touch glow is 1. 86.
Mine is 1 .82, but yet it has the glowlight? It says to hold the button down for two seconds to turn it on.
I see that B&N have new firmware for the nst & nstg. 1. 3 I believe. It said on the site that this firmware would be installed when the nook is idle. (via wifi) Anyway, I'm wondering if it would be ok to go ahead and root the thing, or upgrade the firmware first to maybe - 1. 2 (if I can find it?) before I do anything else? Oh and should I stay away from B&N's new 1. 3 firmware?
Thank You Very Much !!
WillyS.......

If you indeed have the Nook Simple Touch with Glowlight (black bezel), then the most recent stock firmware is 1.2.1 which can be downloaded here. I would recommend that you update to this as the first thing you do. Next you need to decide which of the multitude of rooting methods is best for you. You need to take into account what you wish to achieve by rooting the Nook and your skill/comfort level with the processes. I have followed many of the different processes, doing a factory reset between root versions. By far the easiest is Nook Manager. I, personally, prefer the Minimal rooting - back to basics method because it allows you to install just what YOU want. However, this method requires a fair amount of command line work.
EDIT: I made the assumption that you are in the US and have a US model. I believe there is a different firmware number for the international model. In any case, you should update the Nook to the most recent firmware before rooting.

Rooting nook .. Glowlight ..
Hello David and Thank You kindly for the reply!
Yes, mine is a Canadian version and it has the black bezel.
Thank you .. for correcting me on the firmware. I was looking at the wrong Nook version. (nook.barnesandnoble.com/u/software-updates-nook-glowlight/379004086)
I downloaded the correct 1. 2. firmware for the nook and I (like you) would rather install what I want to and have more control over what gets put on it. After I update the firmware, I'll come back and follow the links you provided. If you know what threads have the latest / newest info on rooting the nstg, can you please point me to it? (If you haven't already) Thank You Very Much for your help .. David.
Cheers
WS

You're welcome. If you are comfortable with a lot of manual, command line manipulation, start with the Minimal rooting - back to basics thread. There are many more and newer rooting methods, but each of them installs a bunch of apps that the creators use, which may or may not be of importance to you. If you start with the Minimal rooting - back to basics, you can then pick and choose the apps and modifications you want to apply to give you the best experience for YOUR needs. I am attaching the document I use to keep track of what I have done for your reference. Feel free to post any questions here.

Rooting Nook STG .. Firmware 1. 2 ...
Hi David and Thank You for the reference document.
Last night I downloaded 1.2.1 firmware and dumped it on the Nook. When I got up this morning I checked and 1.2 is installed. I looked around and found a 16gb Kingston (from GPS) SD-Card. It is only class 4, but it should be usable for the time being. I'll take a look online for a class 10. I don't know if there is any size, or class limitations, or not?
I'm at the rooting - back to basics thread. I'm going to read all this stuff over and see if I can figure it all out. Thanks again for your help and the document.
WS...

WillySizard said:
...
Last night I downloaded 1.2.1 firmware and dumped it on the Nook. When I got up this morning I checked and 1.2 is installed. I looked around and found a 16gb Kingston (from GPS) SD-Card. It is only class 4, but it should be usable for the time being. I'll take a look online for a class 10. I don't know if there is any size, or class limitations, or not?
...
Click to expand...
Click to collapse
Class 4 should work just fine. Since noogie only takes ~2GB (if I remember correctly) you don't really need a card any larger than 4GB to use this method of rooting. Having 8GB or 16GB card would be useful if down the road you will make use of the card to backup your Nook ROM & user-content for ease in recovery.

Don't really know where to go from here, or what to do ..
@ digixmax .. Thank You for the info on the SD-card. Good to know info!
@ david0226 .. I went to the page about rooting via the link and I have basic
understanding how / what needs to be done, but I'm not having much
luck finding and using the tools. I went and looked for the file used to
extract the 2 files from uRamdisk, but I couldn't find it. I did some reading
and looking around and found a program called Preboot (I think) by
Intel and it contained bootutil 32/64 and so on. I had to install preboot & then
uninstall it, to get bootutil and then install it. I tried using it to extract
the files, but I kept getting failed messages. Like invalid switch /x.
Invalid switch /v. Invalid file uRamdisk. I know I need to extract out 2
files: init.rc and default.prop. I tried to do so in the "Administrative Command
Window" on Win7_64bit, but it just wouldn't work with bootutil. Not the
one I had anyway. Any ideas? Thanks!
WillyS......

David0226 said:
...
I am attaching the document I use to keep track of what I have done for your reference. Feel free to post any questions here.
Click to expand...
Click to collapse
What extensions does "Extended Power Menu" provide?
Also, which uImage and uRamdisk do you use as uRecImg and uRecRAM?
TIA.

Here are the links to the relevant threads.
Extended Power Menu
Clockworkmod based Recovery post #75, see the entire thread here.
If you are going to do the Extended Power Menu, be sure to do the Clockworkmod based Recovery also or you risk wiping out everything you have done by accidentally hitting recovery in the Extended Power Menu. I you have installed Clockworkmod Recovery and accidentally hit "Recovery", it will just boot to Clockworkmod and give you a chance to back out.

@willys. I will have to look up the software I use and post tomorrow. Sorry I missed your question earlier.

@willys, I believe the program you want is "bootutil" which was written and shared by Renate NST. If you find a post by her and click on the yellow box in her signature, you will find links to the many custom programs she has written for rooting and managing rooted Nook Simple Touch devices.

David0226 said:
@willys, I believe the program you want is "bootutil" which was written and shared by Renate NST. If you find a post by her and click on the yellow box in her signature, you will find links to the many custom programs she has written for rooting and managing rooted Nook Simple Touch devices.
Click to expand...
Click to collapse
Yes, I had to go to her profile and I found it there. I'll do this part first and see how it goes. After that (I think?) I need to get an android program (some kind of Installer maybe?) to do some other work with. Anyway, one step at a time. All for now. Thanks! ... WS.

digixmax said:
Class 4 should work just fine. Since noogie only takes ~2GB (if I remember correctly) you don't really need a card any larger than 4GB to use this method of rooting. Having 8GB or 16GB card would be useful if down the road you will make use of the card to backup your Nook ROM & user-content for ease in recovery.
Click to expand...
Click to collapse
Class 2 and 4 will do just fine, in my case I used 520 Mb microSD card for installing various ROMs, tried quite a lot of them, always worked fine.

Almost done, but need a little more help . . .
Mnurlan said:
Class 2 and 4 will do just fine, in my case I used 520 Mb microSD card for installing various ROMs, tried quite a lot of them, always worked fine.
Click to expand...
Click to collapse
OK .. Thank You Mnurlan!
@David0226 ...
Just getting to the point where I'm ready to add programs. have edited uRamdisk and re-installed the two files. I've download android-sdk package and have installed it. I have been in the nook via wifi using ndb shell as root. I am now following your notes file. I've created the archive folder on the nook - /system/archive and I've been moving files over from /system/apps folder. I got Nook Manager written to the sd-card and I have PackageInstaller.adk from it, but I I'm not sure how I get that onto the nook. When I boot with NookManager, it ask if I want to root. I have already done that and it is working. Should I let it do it anyway?
Thank You!
WillySizard . . . .

@WillySizard ...
Connect to the Nook with adb then exit the adb shell back to your Windows command prompt. Once back at the command prompt, you should be able to install any package using this command ...
adb install {package_name.apk}

Nook Simple Touch Glowlight .. Need advice before rooting ..
David0226 said:
@WillySizard ...
Connect to the Nook with adb then exit the adb shell back to your Windows command prompt. Once back at the command prompt, you should be able to install any package using this command ...
adb install {package_name.apk}
Click to expand...
Click to collapse
Ahhh .. ok. Good enough then. That should get me off and running.
Thank You .. David. Sorry I'm being such a pest.

Me, also
Just paid $5 for a BNRV350 at a rummage sale.
I understand BN disabled the web browser with the current operating system.
I can get a Google search window (by repeated tapping on the "Google" or maybe the "404" or the "that's all" links that appear when I try the "connect to social" settings menu choice for Google. And "find my account" worked when given the Gmail userid (because the keypad on the Nook lacks a period for typing a proper email address, in this view).
And I can get a Twitter login page. Neither works well -- typing even a single letter into the password field resets the page, so it's letter, then tap in the field window, then another letter, then tap in the field window. Sometimes it shows a row of dots for characters already entered, other times those are invisible but the entries are still there.
Just curious to add to the above fellow's thread for anyone searching for this Nook model number, if anyone has advice or suggestions about making it useful.
Reverting to the original OS to have use of the web browser would be a welcome option, if that's possible. Pointers welcome. Right now this Nook has version 1.1.5 installed -- I gather that's one of the improved versions that killed the stock web browser.

nst glowlight starting up stops every time

I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?

sinlog said:
I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
Click to expand...
Click to collapse
That backup is too large, I think. Should be more in the neighborhood of 250 MB? Have you tried the factory re-image where you just see the booting up screen and then hold down the two bottom hardware buttons until you get a prompt?
It's difficult--but not impossible--to damage the factory image unless you've been messing with the partitions. If that method does not get you there, consider making a NookManager card and trying to access the re-image routine from its menu.

Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.

sinlog said:
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
Click to expand...
Click to collapse
5 seconds is not enough time for NookManager to correctly make a backup. And, backups can only be seen on the card if you connect your NSTG to your PC while NookManager is running. Otherwise the partition is invisible.
It's hard to know since I have no experience with the NSTG. If it were an NST I would suggest that you perform the region change flash, but it's not clear if that will remove your light function or, indeed, if the flash is deep enough to rewrite the areas of your device that appear to be preventing boot. AFAIK there are no ROM images for the NSTG available. But there might be. Somewhere.
I guess if you have exhausted all the possibilities, rather than trashing the device I would try the region change (just flash the US firmware again--I assume that's what's on there already). It may or may not preserve the glowlight capability, but it might at least produce a functioning e-reader. But only as a last resort.
Edit: Hmm.... seems like I've been down this winding road before: https://forum.xda-developers.com/showpost.php?p=72551413&postcount=57
But I emphasize that this process worked for a plain NST, not the NSTG, so it is an absolute last resort (and might not work anyway because you could have a completely different situation). Next thing is to look at the innards of the 1.1 updater and see if Glowlight updates could be substituted...

O.K. So here is a thread that contains a link to an NSTG image and the instructions to write to your device (read down in the thread).
https://forum.xda-developers.com/showthread.php?t=2608815
What "may" happen: your device could end up with a mismatched serial number and or MAC address depending on how this image was made. There is information on this forum for correcting the MAC address. Just a disclaimer. I don't know. IF this is successful, you can then do a manual update to 1.2.2 and then root with the updated NookManager. I've checked the link to the image and it is still good. I got a file that is about 245 MB--seems about right. Presumably you use the image in place of your backup in the restoring process described in the thread.

I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?

sinlog said:
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
Click to expand...
Click to collapse
Oy.
I didn't think you would act so rashly with all my disclaimers. Well, it's done. I actually don't think the MAC address is a big deal unless you begin to have issues.
Did you actually manage to register? If so then the serial number must not currently be in use and the change you effected was deep enough to pass muster. If not....well battery life is said to be shorter for devices that have skipped registration.
Correcting the MAC address is described (sort of) here: https://forum.xda-developers.com/showthread.php?t=1483600
As far as I can guess it involves editing a hex file. Doable, but maybe not needed. There is no way to correct the serial number. It is heavily encrypted with private keys. Again, if you managed to register then this is all moot.
How are you judging lack of internet connectivity?

I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2

sinlog said:
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
Click to expand...
Click to collapse
You didn't answer my question about connectivity. Are you not able to make a connection? With only the stock device there is nothing to connect to other than B&N. What does it say about "Owner" in the Settings?
Yes, you should root. Be sure to use the NookManager update or it won't work.
Before we even think about the MAC address issue you need root access and some way to tell if you actually have an internet connection. That means some kind of functioning browser, etc.
Do you still have that weird backup? If so, keep it safe somewhere. You may want that someday.

I tried to download a book and I got this : Unable to download, Internal error...
I can ping the nook from the computer.
I will look into rooting the device in 2 or 3 hours and then post again. I suppose this is what you're referring to :
https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Thank you for your patience with me.

sinlog said:
I tried to download a book and I got this : Unable to download, Internal error...
Click to expand...
Click to collapse
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?

nmyshkin said:
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
Click to expand...
Click to collapse
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.

sinlog said:
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
Click to expand...
Click to collapse
Hmm... I'm surprised there are any books populating that section at all since the device is not registered. In any case, that is no test of connectivity since without registration the NSTG will spit out all kinds of generic messages about connections and failures if you attempt anything that requires access of B&N servers--like buying/downloading a book (which you can't do unless you are registered).

Rooted with nookManager updated. Opera mobile needs to be reinstalled. I can connect to the computer using es file explorer, so wifi is ok. BUT I can't use nookManager because I can't read the icon labels. I'll restore the backup tomorrow and I will try another rooting method. There are 2 more, I think : tiny and glownooter. Are there others ?

sinlog said:
BUT I can't use nookManager because I can't read the icon labels.
Click to expand...
Click to collapse
? Do you mean ADW Launcher? You can fix the icon label issue in the Settings. As I recall the default font color is white. That needs to be changed to black. The size can also be changed. Depending on what icon style you pick the label will either be on one line or, if longer, on two. LOTS of Settings in ADW. Don't write it off without spending some time working with it.

Sorry, I used glownooter. It's a lot like touchnooter, with which I am familiar. I still have to sign in to my google account and to install opera mobile. I'll be back when finished.

Opera mobile is installed and working. I still can't sign in to google but I can use yalp store and that's good. Thanks again, nmyshkin, you saved my nook glowlight.

How to force reinstall nook simple touch update 1.2.2

My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.

smjohn1 said:
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
Click to expand...
Click to collapse
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.

Thank you, but by two lower hardware buttons, you mean the page turning buttons?

nmyshkin said:
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Click to expand...
Click to collapse
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.

smjohn1 said:
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
Click to expand...
Click to collapse
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.

nmyshkin said:
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
Click to expand...
Click to collapse
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.

smjohn1 said:
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
Click to expand...
Click to collapse
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.

nmyshkin said:
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
Click to expand...
Click to collapse
Thank you very much. Waiting for your experiment results.
1) I can do root. But I couldn't find the package any more. Any pointers?
2) What do you by removing the card? Which card? I was planning to open the back cover and remove the battery, but then I found out you would need a T5 Torx screwdriver, which I don't have. So I gave up.

smjohn1 said:
Thank you very much. Waiting for your experiment results.
Click to expand...
Click to collapse
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.

nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
As for my NST, after reinstallation, the Home button still doesn't work. So I have to believe it seems to be hardware problem and the cover has to be opened.

nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
See the previous one.

smjohn1 said:
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
Click to expand...
Click to collapse
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.

nmyshkin said:
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
Click to expand...
Click to collapse
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now

smjohn1 said:
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
Click to expand...
Click to collapse
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Edit: in the long run, once you find NTM and reassign the "n" button, you might be better served by having the standard B&N home screen as your default launcher. This would provide you with your accustomed functions, easy access to the Library via the quick-nav buttons, etc. You could assign along press of the same button to bring up Relaunch for the few times you'll want it.

nmyshkin said:
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Click to expand...
Click to collapse
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.

smjohn1 said:
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
Click to expand...
Click to collapse
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "again" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.

nmyshkin said:
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "agai n" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
Click to expand...
Click to collapse
OK, I think I need to go back to basics:
1. here is the NM used: http://download.doozan.com/nook/NookManager-0.5.0.zip
2. Here are some screen shots from relaunch:
1) relauncher
2) all apps installed ( from the middle icon at the bottom ): no NTMM there
3) and 4) settings ( from right icon at the top )
3. I don't see a way to install other Android apps, except from Amazon stores ( which I didn't try ) but not from Google App store. Did I install a "wrong" version of NM?
4. One more thing: I "rooted" again, finished quickly, and no changes after boot ( My guess is NM sees the same root package to decide not to do anything ).
Any advice?
----------------------------------------------------------------------------------------------------
After posting above, I installed NTMM-0.4.0.apk successfully, but it says it needs modified jars. From https://forum.xda-developers.com/showthread.php?t=1991048 and https://github.com/doozan/NookTouchPatches.
So NTMM wasn't installed during root.
Now my questions:
how to install these patches? I am using Linux with no adb ( I don't want to use adb anyway ), any apk file that can be written to sdcard for quick and easy installation?
and does this patch work for 1.2.2?

smjohn1 said:
OK, I think I need to go back to basics.
Click to expand...
Click to collapse
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.

nmyshkin said:
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
Click to expand...
Click to collapse
Ha, the step missed was 5, as it was difficult to change the files. But I remade an NM card ( there must be something wrong with the old one ), afterwards it was to update NM to 1.2.2.
Now buttons are reassigned and this reader is usable again ( I don't plan to make it a full android pad, as there are already too many tablets in house ). So this e-reader owes its life to you. Big thanks!
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )

smjohn1 said:
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
Click to expand...
Click to collapse
If there is a way to access the App Manager through ReLaunch, you can run down the list until you get to ReLaunch and there remove any default actions associated with it.
If that is not obvious then the next easiest thing is to install yet another launcher! So you could transfer a copy of ADW Launcher from the NookManager update page to your NST and install it. If you then reboot it will trigger the App Picker dialog again because now there is a new choice. Before you select "Home", be sure to tick the little check box.
Then you can uninstall ADW Launcher. It's possible that may trigger another App Picker with the remaining two choices but I don't think so.
Once that's sorted you can finish your button reassignments. I think ReLaunch actually hijacks some of the QuickNav buttons so you might have to use NTTM to return them to default or pick completely new assignments, as you like.
I'm glad you were able to get the device back in a usable state. I love my NST for reading. After all these years I think it's still a great little piece of technology.