[Q] How do I prevent a B&N OTA update? - Nook Color Q&A, Help & Troubleshooting

[Q] How do I prevent a B&N OTA update? - Nook Color Q&A, Help & Troubleshooting

OK, I thought I saw this mentioned -somewhere- on this forum, but I've tried searching in vain.... Most likely I just can't put together the correct search phrase.
I'm currently running ManualNootered B&N 1.3. I've read very conflicting info as to whether B&N can or will update a rooted OS, but is there a way that I can prevent it? I vaguely remember someone mentioning that they had a rooted 1.2 and woke up one morning to a screwed up 1.3. My biggest concern, of course, is the upcoming 1.4. Don't want to try that until someone figures out what might be needed to apply ManualNooter.

That happened to me. I had nootered a 1.2 and it was working beautifully!
Then I turned on wifi, checked my email and got force fed the update to 1.3.
I've just found an old text file on my PC that had directions to block the update though so I tried it out, it requires that you buy the SQlite editor from the market.
It is priced a $2.99 but I feel it was worth it if it works!!
You can still side load the updates if and when you choose to also!
So I bought the editor and followed these directions:
*Open SQLite. It will scan your entire Nook and find every SQL database file there. Even the hidden ones. It only takes ~10 seconds. (You may see a message about granting super-user permissions, which is normal.)
*Scroll down to DeviceManagerService, and tap on it. Then tap on devicemanager.db.
*Tap on the "registry" entry. It's easier now if you rotate to landscape, so you can see more of the fields in each entry.
*All the entries in this table start with "com.bn.device....". Look for the one that's labeled '...fota.mode" at the end.
*In the far right Value column, you'll see "Auto". Tap on that to select it. Then go down to the Status Bar at the bottom, and tap the Menu button (3 horizontal lines), and pick Edit Field.
*You'll then see a black screen with one entry, the field editing form. You should see the field name of "value" there, and its contents will be "auto". If it turned out that your selection picked some other field (they are pretty small!), don't panic! :smileywink: Just go back and retry until you get the right one.
*Tap on "auto" and the keyboard will come up. Backspace to delete the current contents, and enter "manual" in its place. Then tap Done. Then tap Save. Until you tap Save, you've changed nothing, so poking about is fairly safe.
*You can now exit out of SQLite if you like (it's not necessary), but you're not quite done yet, so don't enable WiFi immediately. To make sure that the system is using the settings you just modified, you need to force it to reload and "see" them. So just power your Nook off and back on. After it reboots, it will use your new settings from then on. That's it.
This file was signed ~Mark, and unfortunately I didn't add the username or anything, so Thanks go to "Mark"

Another method?
I found this over on the B&N forum. I don't know if it is more or less effective than the method above. Perhaps a belt-and-suspenders approach would be best - do both.
Link:
http://bookclubs.barnesandnoble.com...be-possible/m-p/1220616/highlight/true#M68396
And the complete OP:
Title:
Declining the 1.4 update should be possible
Text:
I am looking at build.prop from the 1.4 OS released with the Nook Tablet, with an eye to testing an edit of a system file, build.prop, to update the file and make a Nook Color look as if it is already on 1.4. So far, I'm not seeing anything which looks like a showstopper in the new build.prop for drawing elements out of it for a modded build.prop.
Once the actual update is out, I think I should be able to create a modified file very quickly that will tell the BN servers a device does not need the update as it is already running 1.4.
This is the technique I've used successfully to keep my device at 1.2, which I prefer to 1.3.
If my experiments work, I'll post both the raw build.prop, for folks with root who know how to mount /system as rw to simply copy in (after backing up their original build.prop) and as a set of Clockwork installable files. These will need to be run from a Clockwork disk but will not require rooting the device. One script will move your current build.prop and put in an edited one; a second script would remove the modified build.prop and restore your original so you can receive the update if you choose.

If you have a custom recovery in place, ie clockworkmod, it will prevent installation of the update. Your device will still download the update, but when it boots into recovery for install, it will fail. Reboot and you are back to normal. This has worked for me twice.

Related

First time ROMing, Rogers HTC Magic, Lessons Learned

So, i'm sure there's many posts about this, but I thought I'd drop in my 2 cents. Basically, the purpose of this post is to try and help completely new users get acquainted with the world of Android "ROMing". I know there's beginners tutorials and wiki's and such, and I'm very grateful for all the time put into them by their writers, but the fact remains that they're written by experts, and as such, their expertise shines through and can sometimes confuse new users such as my self.
Up front: I'm an AT&T customer who's using a Rogers branded HTC Magic purchased from ImportGSM. I'm using Rogers cause Rogers has the same 3G bands as AT&T. I am coming from a Sony-Ericsson dumbphone. I use Gmail for my primary email and applied for a Google Voice account a while ago (got the account before getting the phone). I'm a practicing computer engineer so if I lapse into jargon, I apologize.
READ THE ENTIRE POST BEFORE PERFORMING THESE ACTIONS
OK, so you got an android phone (if you're on this forum, its most likely an HTC Magic/Dream/Hero) and you want to install new ROMs onto it (for whatever reason, just to do it, to get more functionality, to remove the carrier 'branding', whatever). You've done your research. You've read through the wikis (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) and you're still a little confused as to where to start, or you're worried you're gonna brick your phone.
First, relax, as long as you follow the instructions, there's little chance of bricking your phone.
Second, some vocab:
SPL: Secondary Program Loader. don't worry too much about this, you shouldn't have to mess with it. I like to think of it as your phones BIOS. There's an off chance that you'll have a "perfected" SPL (.0006 or .0010), which basically means that you have a phone that is hardened against hackers, but as long as you use the one touch root method described below, you won't even notice it. You won't be able to use the Adb/Fastboot/Android SDK method mentioned below, you'll just get a "no access" error when you try to terminal into your phone.
ROM: Catch all term for software to be loaded onto your android. Generally comes in two flavors, a Recovery ROM, and what I call an Operating System ROM. A Recovery ROM is what gives you root access. An Operating System ROM is the user experience (where Amon_Ra or Cyanogen or others mix and match features to make a better user experience). I know that Operating System ROM might be misleading, but its the closest computer analogy I could come up with.
Now, this process will completely refresh your phone, removing all of your contacts, apps, etc. So before you start, if you have stuff on your phone you want to save, best copy them somewhere off your phone now. There's free apps out there to do all of this.
Lets get started.
Now, the first thing you're gonna wanna do is get something called "root" access to your phone. This allows you to install those fancy homebrewed ROMs that people are talking about. To get root, you have to install a recovery ROM. Installing a recovery ROM is is roughly similar to flashing a new BIOS on your computer. Except in this case, its on your phone and it gives you unrestricted access to the phone (like the Root user in Linux). There's two ways of getting Root. The first way is to install the Android SDK onto your computer and image your android with one of the recovery ROMs via your computers command line. I won't get into details on this one because its not the method I chose, and instructions are all over the web on this one. NOTE that this method doesn't work with updated Rogers phones. They installed the 'Perfected' .0010 SPL effectively removing remote command line access thus making this method a non-starter. The other way is to use the "one click root" program, which is a program you install on your Android phone. To do this, go to the one click root website (http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/). Download the .apk file and drop it onto the SD card in the Android phone (you'll have to connect the phone to your computer via USB, and select "Mount SD card". then simply drag and drop the .apk onto the SD card in your computer's file browser). Then, on the android phone, open up your file browser (I suggest Astro or Linda, both free downloads from the market) and open the .apk using the default Android application launcher. It should be a dark screen with a text box and a few buttons. The textbox should have a URL in it pointing to a .img recovery image (This is the cyanogen one). You'll first want to make a backup of your current (factory) ROM by pressing the (i believe) botton button. It'll work for a few seconds. Then you're ready to flash the recovery ROM. You can either accept the default (the cyanogen, which works fine) or specify a different ROM (such as Amon_Ra's which has slightly more capabilities) by entering in a different path (URL or path to SD card if you have a recovery image stored on the SD card). Then hit the first button to begin the flash. Wait for it to finish. DO NOT DISTURB THE PHONE WHILE FLASHING.
Once its finished flashing, congrats, you've rooted your phone. Now power off the phone, and power it back on while while holding power and Home. Hold Power and Home the entire time till you see an 'old computer' style menu come up. Should have some options such as reboot, install update.zip, install other .zip, wipe data/factory reset, etc. you should be able to use the trackball to cycle through the selections. The botton should have something like <cyanogen/Amon_Ra> recovery vX.X.X. If you see this screen, then you've successfully rooted your phone. Congrats.
Now, before you do anything else, IMMEDIATELY perform a nandroid backup. This should be on of the options in the recovery ROM. What this is doing is creating a backup of your current phone configuration so if anything goes wrong with installing the hacked ROM, you can revert to the state the phone is in now.
Next, perform a data wipe. There should be a selection for "wipe data/factory reset" or something similar. Select that. Wait for it to finish wiping your data from the SD card.
Now to install other hacked ROMs, just download whatever ROM you want to install from the xda site. Check the bottom of this page for a listing of the main ones (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking). It should download as a .zip. Copy the .zip file (DON'T UNZIP IT) onto the root of the SD Card (you can do this while in recovery mode by mounting the SD card or by physically removing the SD card from the phone and putting it into a card reader on your computer and copying the files). Once you have the ROM .zip on the SD card, with the SD card in the phone, select "install other .zip" or something similar and select the .zip file of the ROM you want to run. Should be some combination of the creators name (Amon_Ra or CM (for CyanogenMod)), what board the .zip is for (32A, 32B), what version the ROM is (4.1.1 or something). Then select "home" to confirm that you want to do this and wait for the periods to stop appearing. Once it stops, you should be able to select "reboot".
After it reboots (you should see different splash screens than when it was factory configured, except for the very first screen which on mine is "Rogers". Mine goes from Rogers to "Android" spelled out in blue text) you should have a fully functioning phone running a hacked ROM.
If it doesn't boot fully (which mine did a few times), try a different ROM or try wiping your data again. If all else fails, go into your recovery ROM (power and Home) and restore the Nandroid recovery image you made earlier.
Once it boots, it should have a tutorial on how to use Android.
When you get to the google login, I would suggest setting up your APN settings prior to doing that. At the google login screen, hit the menu button and select "APN Settings". Select add new APN (either an on screen choice or brought up by the menu button) and add in the APN details for your provider. You can find these easily by googling "<your provider> APN settings". Log into Google and you should up and running.
I just kinda threw this semi-tutorail together, so it may be a little confusing, but I tried to explain everything as best as I could. I know that i found all of the different ways to get root and the different ROMs and such to be very confusing. Just throwing out how I went about doing it.
Disclaimer: one click root works by exploiting a vulnerability in Android, which was closed by Google on Aug 11 or so. Therefore, if you have a factory Android build from that was released after Aug 11, one click root may not work for you, and you'll have to go the SDK route. I updated my Rogers phone in mid oct 2009, and my build was still prior to Aug 11, so don't just assume cause its after Aug 11 that it won't work on your phone.

thanks alot for the tutorial! you're a saint, i've been looking all over for something exactly like this!
i will test this out and let you know!
Edit:
I was successful! Huzzah! Thanks for the guide again!
What rom did you load onto your phone?
Also,
Could you give a brief tutorial on what exactly changing the radio and spl are?

[HOW TO] Fix the "Low on space" problem (in plain English)

The Problem
The HTC Droid Incredible shows a "Low on space: Phone storage space is getting low" warning despite having gobs of space free because the "Application data storage" folder (also known as /data/data) that is shared by all apps on the phone is only 150mb in size. As soon as only 10% of this folder is available, the warning appears. If it gets too much lower, apps stop responding and the phone crashes.
The Story
After many months of clearing app data, uninstalling apps, resetting my phone, and generally walking on eggshells trying to keep my data storage under the limit, I was getting ready to upgrade my device. I would search every few weeks to see if anyone had solved the problem, but all I found were more people stuck in my boat, and I was ready to give up. But then I stumbled across a series of threads on xda-developers.com that gave me new hope. In the course of one night, I learned from scratch how to root my phone, and I applied a fix that increased the "Application data storage" folder to a whopping 750mb. I am now able to download as many apps as I'd like and not have to worry about clearing out app data ever again.
However, it took a bit of scouring the forums and reading various guides to figure out how to do all this. Some of the items are quite technical in nature, and some of the guides skip steps that more experienced users would know how to do already. So I joined the forum to write this guide for the "regular" users out there like myself. My goal is to explain in plain English how to fix this nagging issue once and for all and to consolidate all the relevant info and files into one place. If you find this useful, please share this with others so we can all fully enjoy our phones!
The Credits
I did not invent any of the steps, tools, or methods I am about to describe. Hats off to the following people for supplying all the info and files I needed to fix the problem and write this how-to thread. Please let me know if I've missed anyone that should be mentioned and I will add them.
vbhines for the "New to Modding/Rooting" guide
The unrevoked team for their excellent one-click rooting software and drivers
dreamersipaq for the guide to rooting an Incredible
scotty1223 for the guide to rooting a 2.3.4 Incredible
jermaine151 for the "no data limit" mod that actually fixes the problem
cmlusco and tiny4579 for all their help answering questions and troubleshooting in this thread
The Ingredients
Here's what you'll need to perform this fix:
An HTC Incredible (obviously) with an SD card
A micro USB cable (you can use the one you charge your phone with)
A computer with a USB port and internet access (PC, Mac, or Linux)
An hour of free time
The Fix
Step 1: Read the "New to Modding/Rooting" guide so you know what you're getting into and can understand the terminology: http://forum.xda-developers.com/showthread.php?t=744807
Step 2: Back up your contacts, pictures, etc. This guide is safe for your phone and will not erase any of your data if you follow it correctly, but it never hurts to back things up just in case.
Step 3a: Make sure your phone is decently charged. (at least 50%)
Step 3b: Make sure your phone isn't currently showing the "low on space" error. Delete some apps or data until the error goes away. You don't want to go through all this effort only to have your phone crash halfway through!
Step 4: Uninstall HTC sync software from your computer. Also make sure you are not running any software that communicates to your phone using USB, such as PDANet or DoubleTwist. If you haven't had to plug your phone into your computer to do anything prior to now, you're probably OK.
Step 5: On your phone, go to Menu -> Settings -> Applications -> Development and put a check in the "USB debugging" box.
Step 6: Plug your phone into your computer, select "Charge Only", select "remember my selection", click "Done", and then unplug your phone.
Step 7: If you are on a Windows PC, follow this user-friendly guide to install the USB drivers you'll need: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
When I did this step, I actually found my Android entry from the first screenshot in the guide under "Android Phone" and it did not say "Android 1.0". Don't worry, you can still use this entry to continue with the next step in the guide to "Update Driver Software".
Mac and Linux users can skip this step.
Step 8: Root your phone. This step is a bit more involved, so be sure to read the directions carefully. On your phone, go to Menu -> Settings -> About phone -> Software information and look at what it says under "Android version" at the top.
If it says 2.3.4, do this:
Download Clockwork 5.0.2.0: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip (link updated 6/22/12)
Extract the recovery-clockwork-5.0.2.0-inc.img from the zip file and put it somewhere you'll remember.
Download Unrevoked 3.22 (this is intentionally NOT the latest version): http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe (link updated 6/22/12)
Run Unrevoked_3.22.exe
Inside the program, go to File -> Custom Recovery and select the .img file from above. At the bottom of the program window, it should now say "Recovery: Custom" and "Waiting for device"
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
Once it's done, unplug your phone and ensure that a "Superuser Permissions" application is inside your app drawer. Don't run it. Instead, go to Menu -> Settings -> Applications -> Manage applications -> All, scroll down to "Superuser Permissions", click it, then click "Clear data". Return back Home.
If it says anything other than 2.3.4, do this:
Download Unrevoked 3.32: http://www.unrevoked.com/recovery/
Run reflash_package.exe. It may start up right away, or it may ask you to extract the files. Put them somewhere you can find, and once the extraction is done, find and run reflash.exe.
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
After the above steps, everyone should do this:
Launch the Android Market and search for "ROM Manager". The first result should be "ROM Manager" by ClockworkMod and it should have a picture of a top hat above a gear as its icon. Click it, then click "Download", then "Accept & download". If it is already installed, you can just return Home.
Once ROM Manager has finished installing, launch it and select "Flash ClockworkMod Recovery" (the first option). Confirm your phone model (HTC Incredible). A window will pop up asking for root permissions - click to allow it.
Optional: After the download completes, scroll down and click "Backup Current ROM". You may need a lot of space free on your SD card to perform this backup depending on what you have on your phone. Once you create this backup, you can use ROM Manager to fully restore your phone (including all apps, data, and settings) in case anything goes wrong. This can take a significant amount of time, so again, be patient!
If all went well, your phone should be exactly the same as it was before, except you now have a couple new apps, and more importantly, root access!
Step 9: On your phone, go to Menu -> Settings -> Applications -> Development and uncheck the "USB debugging" box.
Step 10: Apply the Fix. This is the step you've been waiting for!
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1623038, click the link for the EXT4All files in the first post, download "Convert2Ext4_no_data_limit_normal_dalvik.zip", and put it somewhere you'll remember. You can also go directly to this URL to download the file: http://dinc.does-it.net/EXT4_Mods/ (links updated 6/22/12)
Plug your phone into your computer, bring down the notification bar, select the "USB connection type" item, select "Disk drive", and click Done.
On your computer, find your phone's SD card. If you're unsure which drive is your SD card, look at how big each drive is. The drive that has a size of 6.59GB is the phone's internal memory, so the other drive is the SD card. The SD card that comes with the Incredible is 1.83GB in size, but yours may be different if you bought your own SD card.
Move "Convert2Ext4_no_data_limit_normal_dalvik.zip" from your computer to the SD card. Do not put it inside any folders.
After the file has finished moving, bring down the notifications bar, select the "USB connection type" item, select "Charge only", then click done.
Unplug your phone from your computer.
Launch ROM Manager from your app drawer and click "Reboot into Recovery" (the second option). Click "OK" to proceed.
After the phone reboots, you will now see a black screen with some blue options on it. Use the volume buttons on the left to scroll down to "install zip from sdcard" and click the optical trackpad button at the bottom of the phone to select it.
Click "choose zip from sdcard" (the first option)
Scroll down to the very bottom and select "Convert2Ext4_no_data_limit_normal_dalvik.zip"
Scroll down to "Yes - Install Convert2Ext4_no_data_limit_normal_dalvik.zip" and click it. This step will take some time to complete, and the progress bar may not move at all. Be patient!
Once it is done, click the power button at the top of your phone until you're back at the main menu, then select "Reboot system" (the first option). If you hit power too many times and end up with a blank screen, just hit power one more time and you'll see the menu.
When the phone is done rebooting after this last step, verify that the fix worked by going to Menu -> Settings -> SD & phone storage and look at the "Application data storage" section. It should now say that the "Total space" is 748mb!
At this point you can run happily through an open field, shout from the highest mountaintop, or just shed a tear of joy, because you can now install tons of apps and let them accumulate all the data they want. Enjoy!
P.S. Please let me know if any of these steps are incorrect or unclear so I can fix them. Thanks!
Troubleshooting
Here are a couple of issues people have come across while doing the steps in this guide, along with the solutions. Thanks to cmlusco for these helpful answers!
The guide says my phone should have rebooted back to the main screen, but I'm on a black screen with a bunch of blue options!
If you're on this step and the guide doesn't say you need to be here yet, just use the volume buttons to scroll to the "Reboot System Now" option and click the optical trackpad. Then you can continue on with the guide!
I'm stuck on a black screen with white bars on the side!
If your phone is "s-off", reflash the recovery-clockwork-5.0.2.0-inc.img file from Step #8 using hboot. To get to hboot, turn your phone off, hold the "volume down" button, and turn it back on. Keep holding the "volume down" button until you get to the menu where you can flash the .img file.
If your phone is not "s-off" or you have no idea what "s-off" means, run Unrevoked again with the same .img file from Step #8.
In either case, you should be able to continue using the guide from where you left off!
My phone keeps rebooting over and over and I can't do anything!
Pull out the battery, wait for 15 seconds, and put it back in and turn the phone back on. If it still keeps rebooting, pull out/re-insert the battery again, go into hboot (see above answer) and try the following steps. You can stop as soon as one of them works!
1. Restore a backup that you made in a previous step (if you have one).
2. Reflash the .img file from Step #8.
3. Flash the .img file here: http://dinc.does-it.net/wildstang83_inc_4.08.605.2_11232011.zip (note: this one will take you back to stock, so you'll have to start the guide over).
I'm still stuck!
If all else fails, please post your issue in this thread so someone can help you out. You can also try restoring your backup (you made a backup, right??) and starting over from the top. Good luck!

Potential Alternate Solution
Soniclude that was a great very detailed write up. Here is another option that I found that seems to also solve the dreaded low disk space...
Since you clearly outlined the steps for rooting your device, I wont go into that. But, why stop at fixing one of the most annoying stock problems. Rooting is half the battle to flashing a new rom - which is precisely what I did to stop the LDS issue.
I used to use CM7 and then flashed over to MIUI but recently I flashed the best rom I have used to date - ICS-Dinc AOKP (]http://forum.xda-developers.com/showthread.php?t=1475936) which is a full fledged ICS port for your OG Dinc.
Since then I have not received any LDS errors (although I have not been using this ROM that long) but I would assume that it would be similar to my lengthy experience with CM7, in which I never got the LDS warning.
Here is what my device displays as available space for applications
View attachment 895332
As you can see I have used 144MB with 604MB free for a total of 748MB, identified as internal storage.
Also, just so you can see that this ROM is not an ICS overlay and is truly a port, here is the device info
View attachment 895331
72ls1's (the dev for ICS-Dinc AOKP) has some really good directions and make the process very easy.
For those that are interested and need a few more additional details, here are a few things that helped me:
1. Make sure you have backup your device data, this includes your apps, contacts (you should be just setting all contacts to sync with your gmail account to begin with), messages and email settings. Use an app like Titanium Backup for apps; Backup and Restore app for messages; Call Log Restore for calling
2. Download the zip files outline in the ROM posting of your chocie to your sdcard; They should be placed at the top level of your sdcard, meaning not in another folder. The zip files for ICS-Dinc AOK include the ICS-Dinc zip, Gapps (use this one gapps-ics-20120207-signed.zip - http://goo-inside.me/gapps/gapps-ics-20120207-signed.zip), and Tiamat Kernel
3. In Recovery make a backup of your device (in case you need to flash back due to an error)
4. Within Recovery prior to flashing the rom make sure to unmount data, sdcard and cache
5. Then clear cache and dalivik-cache (this one is under the advanced options)
6. Do a factory reset
7. Install from zip in the following order: ICS-Dinc AOK V.02, Gapps, Tiamat
8. Reset your device
Now go enjoy the goodness of a fresh ice cream sandwich!
Hope this helps anyone else out there in either the low disk space issue or that is having questions about flashing a rom.

Where is Unrevoked 3.22?
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan

Captainjerky said:
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan
Click to expand...
Click to collapse
You can actually acomplish that without rooting.
Open dial pad and type ##778# and hit call.
Select edit mode and enter six zeros (000000) as the password.
Select security and look for S.IP DUN username, it should look something like this [email protected]. Change it to be [email protected], just remove the "dun.".
Back out to the main menu and select M.IP Default Profile. Look for DUN NAI and change it to be [email protected], remove the "dun."
Hit the menu button and select commit modifications. Your phone will reboot.
Now just use the stock 3g mobile hotspot app. When you first open it it will say you have to have a subscription and pay, just procede you will not be charged, and verizion is none the wiser. I have been doing this my self for over a year now.

Compass sensor broken
Somebody has the same issue? after flashing the zip i cannot use correctly the compass sensor, for example in SkyMaps app.

This is by far the best tutorial out there to gain root and achieve s-OFF I've come across. Thank you SIR for your time and tutorial. Just EXCELLENT!!

for me the issue was my data/data folder (hint dont sync 1500 facebook friends and never do it with high res pics and with two differant apps haha) =] jsut removed all the contacts i didnt need and turned off the sync from normal facebook app and working perfect now

stuck in loop
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here

scals37 said:
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here
Click to expand...
Click to collapse
If you made or have a previous roms backup. Just wipe everything in mounts and storage menu except sdcard and emmc, then restore your backup. If you dont have a backup flash a fresh rom.

You kind sir are a gentleman and a scholar. That "low space" bug has been annoying me since July 2009. I greatly appreciate you breaking down the l337 sp33k to plain English.
THANK YOU THANK YOU THANK YOU THANK YOU

Captainjerky said:
Does anybody have a working link to 3.22?
Click to expand...
Click to collapse
downloads.unrevoked.com/recovery/3.22/reflash_package.exe
---------- Post added at 01:19 PM ---------- Previous post was at 01:11 PM ----------
Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?

[/COLOR]Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?[/QUOTE]
I agree that this was an excellent how to. Thanks for the effort.
I used the no_data_limit_dalvik_moved mod and for some reason, my phone became really laggy. I'm on Pons CM7. 2. Now I'm a little hesitant to use any of the ext4 mods b/c I don't understand them too well. I'm not clear on why there is a partition in the first place. Why htc devs made it so small... Homework to do.
Sent from my ADR6300 using Tapatalk

Thanks cmlusco I used your method to unlock the 3G Hotspot on my phone and it worked like a charm.

Issue in Step 10
Thank you very much for the easy to follow directions soniclude. I went through all the steps and when I got to step 10, I ran into an issue. After clicking on "Reboot into Recovery" the phone restarts and goes to the white htc screen. After that the screen just goes black with thin white lines down the sides and stays like that. So I never see the blue options. Has anyone come across this? If so, what do I do from there?

I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.

joeyz400 said:
I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.
Click to expand...
Click to collapse
If your on 2.3.4 you need to follow this guide http://forum.xda-developers.com/showthread.php?t=1306400 to root and get s-off.

I understand I could downgrade to 2.2 to get s off but only after I gain root. It seems I can't get rooted because I am running 2.3?
---------- Post added at 06:58 PM ---------- Previous post was at 06:53 PM ----------
It looks like the only step diffrent from the link you posted and this one is to run unrevoked as admin

I think I know what is wrong. The link to Unrevoked 3.22 is not working so I googled it and 3.22 came up but it was actually 3.32 that was downloaded and I can't find 3.22 anywhere. Does anyone have a copy of 3.22?

I found the correct 3.22 and now my Incredible is Incredible!!!! Rooted and it feels so good
Thanks for such a great thread!!!!

SWEEEEEET This worked awesome.

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.

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.

[NST/G] Dealing with non-US (aka "UK") devices in 2021

Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for options 3 or 4 it does not matter as much because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Nook" logo screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there are only two working reader apps besides the stock Reader that can handle Adobe DRM protected epubs: Mantano 2.2.3 Premium (activated or not), and Aldiko 2.0
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions. Since the site seems to be down, here is a link for the image zip.
b. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
c. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Eject the device from the USB connection and tap the power button to put it to sleep. If you hang around you may see the device wake up and the update commence. Otherwise come back awhile later. If the update zip is no longer visible on the Nook drive when it is reconnected to your PC via USB then the update has been done.
d. Register your device. Remember you don't need to use a credit card, just an email address.
e. If you wish to root the device select one of the updated versions of NookManager for FW 1.2.2 that are given here.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
4. Try out my unofficial UK FW 1.2.2 update.

Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!

pkk11 said:
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
Yes, it is possible but there are some special issues surrounding the Glowlight model.
The definitive DIY summary for USB Audio by @Renate NST is buried deep in the original USB Host development thread: https://forum.xda-developers.com/t/wip-usb-host-support-working.1457971/page-19#post-43281985
I recollect that there is a minor path error somewhere in the description, but I will have to search around to find that.
For those who would rather not get their hands quite so dirty (or who don't trust their hands...), there is a CWM-flashable zip prepared by @pinguy1982: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/. This is what I have used since my first initial set up following the DIY directions, although I swapped in a different kernal. More on that later. The advantage (beyond the obvious) is that the zip contains a tweaked set of audio drivers.
Here, too, there were a few minor issues which I corrected in my own copy, although clearly the package works as it was originally posted.
The issue with the Glowlight revolves around the choice of USB Host-enabled kernals. The one referenced by @Renate NST is for FW 1.1.5. It also enables multi-touch and allows you to run NoRefresh display mode if you desire. However, FW 1.1.5 was written when the concept of the Glowlight was just a glimmer in some developer's eye. Consequently it behaves poorly with the Glowlight control, in essence separating the actual light function from the light icon in the status bar. I use this kernal with my Glowlight because I also run my QuickTiles app and it controls both the light and status bar icon, bypassing the system controls. The reason I chose this kernal is because it allows the use of NoRefresh which I feel is superior to FastMode for text reading.
As far as I know all of the other USB Host-enabled kernals are over-clocked kernals that were designed to allow the usage of the FastMode display mode. This is true of the kernal included in the CWM zip created by @pinguy1982. None of these kernals, to my knowledge, will also work with NoRefresh. There is only one kernal that allows you to use both NoRefresh and FastMode (not at the same time, of course) and that is kernal 166--but for some reason this was not the base for adding USB Host to a 1.2.x kernal. Maybe there is an essential incompatibility. It's way beyond my pay grade.
I've meant to look at this more closely and get some definitive information. This will take a few days and involves backing up my device and trying the various kernals. There is one that claims to support the Glowlight function, USB Host, and NoRefresh but I suspect the author of that post was being sloppy in describing the screen refresh mode.
Anyway, that and tracking down the other minor issues I mentioned above will likely take a few days.

Yeah, I didn't have anything to do with the kernel mods on the NST for USB host mode.
There is one patch for audio sample rates on the page for MergeSmali (in sig).
The current UsbMode-2.2.apk supports NST and Glows (although the Glows need the injectd daemon also).

pkk11 said:
A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
OK, so I'm glad you asked this question because it prompted me to look more closely at the kernal issue and I found that there is an appropriate kernal for the Glowlight!
CAUTION: before you do this, use NookManager to make a backup of your device.
For audio playback:
You will need a CWM card to flash the zip. You can make a card from one of the two files at: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. There is a "2 gb" file and one for "128 gb". The card you choose should have at least the capacity mentioned in the file name. Download the file, unzip and burn the image to an SDcard. DO NOT try to install CWM directly onto your device. This will destroy the one fail-safe that makes the NST so hard to kill: the factory image.
Next, download the CWM-flashable USB Audio zip from here: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/
The kernal in this zip is based on 1.2.x so it will work with a Glowlight. It includes multitouch, enables FastMode (with the appropriate app), and USBHost. It is overclocked, so you may want to install some kind of CPU regulator to calm it down. It will not work with the NoRefresh app.
If you would prefer a kernal that is not overclocked and works with NoRefresh (but not FastMode), you can download the zips here: https://forum.xda-developers.com/t/nstg-kernel-multitouch-usb-host-kernel.2846867/#post-54803848. Unzip the files. Open (not unzip) the CWM-flashable USB Audio zip and inspect the contents (WinRAR allows this kind of thing, not sure about other archiving software). In the "boot" folder you will find the two kernal files. Drag the replacement files you downloaded into this folder (within the archive) and set the overwrite to "storage" or "store". You don't want any more compression going on. Then close the archive.
Once you have the CWM-flashable zip set up the way you want it, copy it to the CWM card. Power down the NSTG, insert the CWM card, power up and wait for completion of boot. This is the button function layout for CWM:
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Once you've flashed the zip, you'll need to reboot. If there is a message about possibly losing root, etc., just say no. I've been down that road before.... By attempting to fix a non-existent problem it will create that very problem. So don't let it "fix" nothing.
You need some hardware to make all of these changes actually do something. Also a little software. As far as the hardware, you need an OTG cable (e.g. https://www.ebay.com/itm/Micro-USB-...48?hash=item365c5af32c:g:LmEAAOSwa6heLwTo)and a USB-C audio thingy (e.g. https://www.ebay.com/p/94253551?iid=383621510193 or https://www.ebay.com/itm/Sabrent-Us...259335?hash=item42166fae07:g:v~kAAOSwG5ZekgAB). Both are available on ebay or Amazon and are not expensive. Some audio gizmos include volume control buttons, some don't. I have one of each, but don't use the one with the buttons because it's full of LEDs and the whole USB Host thing drains power anyway, so who needs a bunch of lights?
Some people have had issues with USB Host. I suspect it's because of the OTG cables. The first one I got just did not work. The USB socket on the NSTG is not exactly an industry standard and the cheap OTG cables are not precision instruments. I finally got one that fits well but I have another (right-angle model) which sticks out half-way when fully inserted. It works, but it's worrisome. Also, do not let the cable and audio gizmo dangle. Everything should be on a flat surface. If you put stress on the USB jack and make it unhappy, you're going to have trouble doing something very important: charging. I speak from experience.
Now the software. To activate USB Host (and Audio) you need one or two apps. @Renate NST has a USB Host app as well as an Audio Control app. Both are needed for Audio and are useful if you need to troubleshoot. They can be downloaded from her signature link.
I have found that with a good OTG cable I never have initialization issues with USB Host (on all three devices I own). So I wrote a little one-touch toggle app to turn USB Audio on and off. There are screen prompts to tell you when to connect and disconnect things. Version 4 of the app displays on-screen volume controls as well. You can find that here: https://forum.xda-developers.com/t/app-nst-g-usb-one-touch-toggles.3172213/. The same functionality is also built in to my QuickTiles app, although with nicer screen prompts
If you get this working and are interested in audio recording with the NSTG, there are a few more things to do, but we'll leave that alone for now.

nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip

alexhorner said:
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
Click to expand...
Click to collapse
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!

nmyshkin said:
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
Click to expand...
Click to collapse
Self host FTW!

alexhorner said:
Self host FTW!
Click to expand...
Click to collapse
yah....my Mediafire account is almost full now with all the NST and Nook Tablet stuff I'm trying to save from oblivion. Hope there's room for this one more.

nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such

alexhorner said:
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
Click to expand...
Click to collapse
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.

nmyshkin said:
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
Click to expand...
Click to collapse
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!

alexhorner said:
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
Click to expand...
Click to collapse
The only way to test the dictionary is to load up an ebook, long-press on a word, select "Look up" and see what happens.

Nook Simple Touch - Resources?

Hi!
Theres lots of different packages and resources scattered around, and theres missing instructions and unclear details.
Would it be possible to compile a list, with instructions, on modding a rooted NST (/Glowlight)?
I have seen new kernels with USB Host/OTG, multitouch, upgrades, additional launchers etc, but no real details of how to use them, whats the most up to date etc
Thanks!

alexhorner said:
Hi!
Theres lots of different packages and resources scattered around, and theres missing instructions and unclear details.
Would it be possible to compile a list, with instructions, on modding a rooted NST (/Glowlight)?
I have seen new kernels with USB Host/OTG, multitouch, upgrades, additional launchers etc, but no real details of how to use them, whats the most up to date etc
Thanks!
Click to expand...
Click to collapse
Well, that will take a very long time. It's something I've thought about for this year, but it's a big effort.
Suppose you list what you'd like to do, and I'll try to point you in the right directions, in some kind of logical order.

Thanks for such a fast reply!
Referencing https://forum.xda-developers.com/t/share-your-setup-app-list.3143404/
I'd like to get the best kernel I can, with USB HOST and Sound drivers if possible
From that list I can also see of interest:
Extended Power Menu
AndroNook Settings
UsbMode
TuneIn Radio
QQPlayer
FastMode2
Opera Mini
AirDroid
adbWireless
Nook Clear Screen
Terminal Emulator
Stock Settings
Would you have any developers/stock experience and performance/featureset upgrade recommendations too?
Ideally I'd love to write up a page for everything I use with downloads and instructions where applicable
Thanks!
Edit: Tools like OpenSSH and BusyBox would be handy too, though I could probably build those from older sources if I need to

alexhorner said:
Thanks for such a fast reply!
Referencing https://forum.xda-developers.com/t/share-your-setup-app-list.3143404/
I'd like to get the best kernel I can, with USB HOST and Sound drivers if possible
From that list I can also see of interest:
Extended Power Menu
AndroNook Settings
UsbMode
TuneIn Radio
QQPlayer
FastMode2
Opera Mini
AirDroid
adbWireless
Nook Clear Screen
Terminal Emulator
Stock Settings
Would you have any developers/stock experience and performance/featureset upgrade recommendations too?
Ideally I'd love to write up a page for everything I use with downloads and instructions where applicable
Thanks!
Edit: Tools like OpenSSH and BusyBox would be handy too, though I could probably build those from older sources if I need to
Click to expand...
Click to collapse
Most of that list is apps. Give me a day to put something together.

nmyshkin said:
Most of that list is apps. Give me a day to put something together.
Click to expand...
Click to collapse
No rush! Thank you so much for your help

[I'm going to try to address your issues in this single post, but not all at once. I'll be adding things over the next few days. Since I don't know where in the process you are currently, just skip things you have already done]
Updating to FW 1.2.2
[Note: if you have a UK device, go to: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/ and return here to the "Kernals" section after completing option 3]
If your device is still on FW 1.2.1 you will need to do a manual update. In theory, you should be able to download the update zip from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip), connect your NST/G to your PC via USB, copy the update zip to the "Nook" drive and wait. When the device sleeps, the update should be installed. If you come back later and look at the "Nook" drive and you don't see the update zip, it's done. You can check this by looking in the Settings app for the software version.
IF the theoretical procedure does not work for you, a deregistration might be in order. Since a device on FW 1.2.1 cannot deregister by contacting B&N servers (this is generally done via the Settings app), you will have to force a user data wipe. To do this, turn off the device. Power back on and as soon as you see the "Read Forever" screen, press and hold the two lower hardware buttons (page-turn buttons) until a prompt appears. Follow the on-screen directions. This will eventually leave you at the "Welcome" screen. Now attach the device to your PC via USB, drag the update zip onto the "Nook" drive and wait for the update to occur. Again, if you come back later and you don't see the update zip listed on the "Nook" drive, you're done. At this point you can continue and register your device.
IF the second method was unsuccessful, there might be something messed up with the resident FW. In that case, the best course is to initiate a factory re-write of the entire system. The eight-failed-boot attempts is painful and often very frustrating, but NookManager can do the job in the push of a button. So if you are still having issues updating, proceed to the "Rooting" section below and prepare a NookManager card. Then power down your device, insert the NookManager card and power up. Skip WiFi turn on. The "Restore Factory zip" option is found under "Rescue". Follow the directions and after a reboot you will be at the "Welcome" screen on some unknown FW. Attach the device to your PC via USB, drag the update zip to the "Nook" drive, and wait for the update to occur as described above. Once that has happened, continue on to registration.
Rooting
Go here: https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/ and choose whichever version of NookManager seems like it will best meet your needs. I strongly suggest you make a FW 1.2.2 registered backup before rooting (NookManager can do this). When your device is rooted and you have done some configuration on the possible launchers and/or file managers, return here to the next section, "Kernals".
Note: regarding your question about ssh and busybox, the latter is installed during rooting with NookManager. I'm really not familiar with ssh but I note that you can supposedly use it with NookManager running. There is some info on the opening screen where the WiFi option is located.
Kernels
The first kernel modification was for multi-touch to enable pinch-zoom for those apps that would support it on the NST. Every subsequent kernel has included this change.
Now it gets a little confusing. For practical purposes, only kernels based on at least FW 1.2.1 are of use. Earlier kernels do not understand glowlight control (you can work around this, but why bother?). So there are more or less three "modern" kernels for the NST/G, one without support for USB Host and two with USB Host support.
Kernel 166 (see attachment below) does not support USB Host but it does support both augmented display modes, NoRefresh and FastMode (with the appropriate apps installed). NoRefresh is an augment for flicker-free reading when scrolling in an app (like a webpage, for example) or when moving around on a PDF image. Based on the original development thread, this appears not to require kernel modification, only the installation and configuration of an app (link below). FastMode is an augment for, well, I guess for playing with video. It presents a highly dithered image (lots of tiny dots) in an attempt to simulate greater grey-scale. Initially it seems like a good idea (impressive coding, anyway) but it's not good at all for reading and there is a lot of ghosting in video until the screen is finally filled with swirls of dots in various states of visibility. At least that was my experience. FastMode requires both kernel modification and an app (link below). Kernel 166 is the only kernel that can run both display modes. Like all kernels that support FastMode it is overclocked, supposedly up to 1100 Mz, although I never saw it indicated more than 1000 Mz. When running it you probably should have a CPU governor app installed (download below), perhaps trim the CPU down to 800 Mz to help with battery life.
NoRefresh and FastMode both require apps to activate the display augments (not simultaneously). But the point of all this (since you want USB Audio) is to try to make clear(?) that any other kernel that supports FastMode kills NoRefresh (somehow). So, if you want USB Host/Audio (and you do) then you have to choose which display augment you want because you can't have both. That is not to say it's impossible (clearly kernel 166 shows that it is) but only that there is no existing kernel that makes it possible.
The two kernels which support USB Host probably have numbers. Maybe one of them is 174. But probably nobody knows at this point. The kernel in the CWM zip for enabling USB Audio (with all the nifty drivers) is an overclocked kernel that supports FastMode. If you would prefer to have access to NoRefresh instead of FastMode, you can use the kernel attached below (can't find the original link, so...). Just open the CWM USB Audio zip in something like WinRAR and drag the new kernel into the "boot" folder, replacing the file already there. Be sure to not recompress the file. Use the "store" or similar option when dragging into the opened archive.
Kernel installation can be done via adb. The directions for that are here. But since you have the CWM zip available and want to install all the audio stuff as well, the easiest path is via CWM. That means you need a card.
Download one of the two sdcard options from here and burn a card (do NOT install CWM internally on the NSTG! It will replace the fail-safe factory image!!). Then copy the zip with the kernel and audio drivers to the card and boot your NSTG from the CWM card. Install from the zip and you're good to go after a reboot. If you change your mind later about the kernel just swap in the one you want in the zip file and flash the whole package again.
Two details on this CWM USB Audio package: microphone recording is not entirely/correctly implemented in the files as supplied. If that is not important to you, skip to the next stuff. If you want to get it done right and then forget about it, you need to replace one of the files in the zip with a corrected version and you also need to copy a patched version of framework.jar into /system/framework. The zip of patches below contains the framework.jar and a file called alsa.default.so. You can use a file manager to copy the framework.jar into /system/framework. Be sure the permissions are set the same as the original (you can rename original to framework.jar.bak first, if you want). Then reboot.
As for the little alsa file, open the CWM USBAudio zip and navigate inside to system/lib/hw. You'll see the original file there. Drag the replacement over and be sure not to recompress it (i.e., use "store" or similar). Now the zip is good to go for a complete USB Audio installation including both playback and recording. Whew!
USB Audio
Of course, it's not that simple. There's no headphone jack or speakers. How does the audio come out?! You need two pieces of hardware (three, if you count earbuds/headphones---or a cable to attach to the auxiliary jack of your sound system) and some software.
USB Host in general requires the use of an OTG cable stub. This seems to be a very critical part of the arrangement. My first cable fit poorly and I almost gave up on the whole enterprise. A second one fit in the slightly non-standard USB jack like a hand in a glove. Suddenly it all worked! I can't tell you which cable might work for you. They are cheap (that's part of the problem...) and you may need to try more than one. Amazon, ebay, etc. Some are straight-line, others 90 degrees. What's important is a good fit. I'm not saying the example in the link above is a good fit. I got mine so long ago I have no idea where it came from. Probably ebay. Long gone.
Since the NSTG has no sound hardware, you need a USB-C external sound card device (here's another link to the button/LED kind--expired, but you get the idea). These also are not very expensive and can be found on Amazon or ebay. There are two basic designs. One has a bunch of LEDs that just waste battery power. It may also have volume control and/or other buttons. The other one is more spartan, lacking LEDs and buttons. I have one of each and never use with one with the LEDs.
To initiate USB Host or Audio you need at least one app (each). @Renate has produced an app for USB Host and an additional one for USB Audio. They can be downloaded from her signature page. Both are used to activate USB Audio. They are great for diagnostics but I just never have any issues with USB Host (that perfect plug!) so I wanted something that would be simpler. Just one touch. I made two small apps, one for USB Host (does not activate audio stuff) and one for USB Audio (sets up host and activates audio). The latest version of the USB Audio app places volume control buttons on the screen when in use, so you really don't need a device with volume buttons. My apps are found here. These routines are also included as options in my QuickTiles app.
ADB
You didn't specifically mention ADB so perhaps you are already fixed for that or maybe don't think you'll want it. There are certainly some things that are really only possible with ADB when you start getting down and dirty with the device. But a good file manager and/or terminal app can also do a lot of stuff without ADB. Still, if you don't have it, the easiest way to get just ADB and not the entire Android SDK is to download and install Minimal ADB and Fastboot. This is for Windows. If you're using a Mac, you're on your own.
The apps in your list
I'm going to try not to editorialize too much here, but some things may not work as well as they sound and there might be better alternatives to others, so...based on my experiences (and prejudices...).
Extended Power Menu (caution, "reboot to recovery" option goes straight to factory re-image without any chance to say no! A possible alternative, my Alternate Power Menu app)
AndroNook Settings (I had trouble with this and the stock B&N system; some settings don't seem to work, some cause a reboot. A possible alternative my Nook Settings app--not as tidy but full-featured)
UsbMode (this is the kernal thing and/or maybe the activating app--already covered above)
TuneIn Radio (still works great, available in the package of apps linked in my signature)
QQPlayer (@pinguy1982 posted this copy--MX Player w/codec pkg also is great--again in my app pack)
FastMode2 (app already linked above; needed to activate FastMode with supporting kernel)
Opera Mini (installed with the updated NookManager packages. Direct link to Opera archive)
AirDroid (also, if you use ES File Explorer it has a "remote manager" capability. Creates an FTP address. You type in the address in the Windows Explorer address bar and voila, you can move files back and forth via WiFi. Hard to get to, though, buried in the app settings, so I made a little app to access directly. Also available as an option in my QuickTiles app.
adbWireless (ADB Konnect is installed by NookManager. One drawback: for long sessions you need to extend screen timeout since connection seems to drop when screen goes into sleep mode)
Nook Clear Screen (I found this not very useful; maybe I have a greater tolerance for little screen artifacts. Also available as an option in my QuickTiles app.
Terminal Emulator (couldn't track this one down in the forum so I uploaded a copy below)
Stock Settings (well, this is what's on the device out-of-the-box!)
I think (hope) that covers everything you mentioned. I did see a reference to an app called DroidSSH while I was tracking down some of this stuff, but no link. If that's something you might find useful, you'll need to do a lot of Googling. (or maybe it was SSHDroid?
If there is anything else, or something here is not clear, give a holler.

nmyshkin said:
[I'm going to try to address your issues in this single post, but not all at once. I'll be adding things over the next few days. Since I don't know where in the process you are currently, just skip things you have already done]
Updating to FW 1.2.2
[Note: if you have a UK device, go to: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/ and return here to the "Kernals" section after completing option 3]
If your device is still on FW 1.2.1 you will need to do a manual update. In theory, you should be able to download the update zip from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip), connect your NST/G to your PC via USB, copy the update zip to the "Nook" drive and wait. When the device sleeps, the update should be installed. If you come back later and look at the "Nook" drive and you don't see the update zip, it's done. You can check this by looking in the Settings app for the software version.
IF the theoretical procedure does not work for you, a deregistration might be in order. Since a device on FW 1.2.1 cannot deregister by contacting B&N servers (this is generally done via the Settings app), you will have to force a user data wipe. To do this, turn off the device. Power back on and as soon as you see the "Read Forever" screen, press and hold the two lower hardware buttons (page-turn buttons) until a prompt appears. Follow the on-screen directions. This will eventually leave you at the "Welcome" screen. Now attach the device to your PC via USB, drag the update zip onto the "Nook" drive and wait for the update to occur. Again, if you come back later and you don't see the update zip listed on the "Nook" drive, you're done. At this point you can continue and register your device.
IF the second method was unsuccessful, there might be something messed up with the resident FW. In that case, the best course is to initiate a factory re-write of the entire system. The eight-failed-boot attempts is painful and often very frustrating, but NookManager can do the job in the push of a button. So if you are still having issues updating, proceed to the "Rooting" section below and prepare a NookManager card. Then power down your device, insert the NookManager card and power up. Skip WiFi turn on. The "Restore Factory zip" option is found under "Rescue". Follow the directions and after a reboot you will be at the "Welcome" screen on some unknown FW. Attach the device to your PC via USB, drag the update zip to the "Nook" drive, and wait for the update to occur as described above. Once that has happened, continue on to registration.
Rooting
Go here: https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/ and choose whichever version of NookManager seems like it will best meet your needs. I strongly suggest you make a FW 1.2.2 registered backup before rooting (NookManager can do this). When your device is rooted and you have done some configuration on the possible launchers and/or file managers, return here to the next section, "Kernals".
Note: regarding your question about ssh and busybox, the latter is installed during rooting with NookManager. I'm really not familiar with ssh but I note that you can supposedly use it with NookManager running. There is some info on the opening screen where the WiFi option is located.
Kernals
The first kernal modification was for multi-touch to enable pinch-zoom for those apps that would support it on the NST. Every subsequent kernal has included this change.
Now it gets a little confusing. For practical purposes, only kernals based on at least FW 1.2.1 are of use. Earlier kernals do not understand glowlight control (you can work around this, but why bother?). So there are more or less three "modern" kernals for the NST/G, one without support for USB Host and two with USB Host support.
Kernal 166 (see attachment below) does not support USB Host but it does support both augmented display modes, NoRefresh and FastMode (with the appropriate apps installed). NoRefresh is an augment for flicker-free reading when scrolling in an app (like a webpage, for example) or when moving around on a PDF image. Based on the original development thread, this appears not to require kernal modification, only the installation and configuration of an app (link below). FastMode is an augment for, well, I guess for playing with video. It presents a highly dithered image (lots of tiny dots) in an attempt to simulate greater grey-scale. Initially it seems like a good idea (impressive coding, anyway) but it's not good at all for reading and there is a lot of ghosting in video until the screen is finally filled with swirls of dots in various states of visibility. At least that was my experience. FastMode requires both kernal modification and an app (link below). Kernal 166 is the only kernal that can run both display modes. Like all kernals that support FastMode it is overclocked, supposedly up to 1100 Mz, although I never saw it indicated more than 1000 Mz. When running it you probably should have a CPU governor app installed (download below), perhaps trim the CPU down to 800 Mz to help with battery life.
NoRefresh and FastMode both require apps to activate the display augments (not simultaneously). But the point of all this (since you want USB Audio) is to try to make clear(?) that any other kernal that supports FastMode kills NoRefresh (somehow). So, if you want USB Host/Audio (and you do) then you have to choose which display augment you want because you can't have both. That is not to say it's impossible (clearly kernal 166 shows that it is) but only that there is no existing kernal that makes it possible.
The two kernals which support USB Host probably have numbers. Maybe one of them is 174. But probably nobody knows at this point. The kernal in the CWM zip for enabling USB Audio (with all the nifty drivers) is an overclocked kernal that supports FastMode. If you would prefer to have access to NoRefresh instead of FastMode, you can use the kernal attached below (can't find the original link, so...). Just open the CWM USB Audio zip in something like WinRAR and drag the new kernal into the "boot" folder, replacing the file already there. Be sure to not recompress the file. Use the "store" or similar option when dragging into the opened archive.
Kernal installation can be done via adb. The directions for that are here. But since you have the CWM zip available and want to install all the audio stuff as well, the easiest path is via CWM. That means you need a card.
Download one of the two sdcard options from here and burn a card (do NOT install CWM internally on the NSTG! It will replace the fail-safe factory image!!). Then copy the zip with the kernal and audio drivers to the card and boot your NSTG from the CWM card. Install from the zip and you're good to go after a reboot. If you change your mind later about the kernal just swap in the one you want in the zip file and flash the whole package again.
Two details on this CWM USB Audio package: microphone recording is not entirely/correctly implemented in the files as supplied. If that is not important to you, skip to the next stuff. If you want to get it done right and then forget about it, you need to replace one of the files in the zip with a corrected version and you also need to copy a patched version of framework.jar into /system/framework. The zip of patches below contains the framework.jar and a file called alsa.default.so. You can use a file manager to copy the framework.jar into /system/framework. Be sure the permissions are set the same as the original (you can rename original to framework.jar.bak first, if you want). Then reboot.
As for the little alsa file, open the CWM USBAudio zip and navigate inside to system/lib/hw. You'll see the original file there. Drag the replacement over and be sure not to recompress it (i.e., use "store" or similar). Now the zip is good to go for a complete USB Audio installation including both playback and recording. Whew!
USB Audio
Of course, it's not that simple. There's no headphone jack or speakers. How does the audio come out?! You need two pieces of hardware (three, if you count earbuds/headphones---or a cable to attach to the auxiliary jack of your sound system) and some software.
USB Host in general requires the use of an OTG cable stub. This seems to be a very critical part of the arrangement. My first cable fit poorly and I almost gave up on the whole enterprise. A second one fit in the slightly non-standard USB jack like a hand in a glove. Suddenly it all worked! I can't tell you which cable might work for you. They are cheap (that's part of the problem...) and you may need to try more than one. Amazon, ebay, etc. Some are straight-line, others 90 degrees. What's important is a good fit. I'm not saying the example in the link above is a good fit. I got mine so long ago I have no idea where it came from. Probably ebay. Long gone.
Since the NSTG has no sound hardware, you need a USB-C external sound card device (here's another link to the button/LED kind--expired, but you get the idea). These also are not very expensive and can be found on Amazon or ebay. There are two basic designs. One has a bunch of LEDs that just waste battery power. It may also have volume control and/or other buttons. The other one is more spartan, lacking LEDs and buttons. I have one of each and never use with one with the LEDs.
To initiate USB Host or Audio you need at least one app (each). @Renate has produced an app for USB Host and an additional one for USB Audio. They can be downloaded from her signature page. Both are used to activate USB Audio. They are great for diagnostics but I just never have any issues with USB Host (that perfect plug!) so I wanted something that would be simpler. Just one touch. I made two small apps, one for USB Host (does not activate audio stuff) and one for USB Audio (sets up host and activates audio). The latest version of the USB Audio app places volume control buttons on the screen when in use, so you really don't need a device with volume buttons. My apps are found here. These routines are also included as options in my QuickTiles app.
ADB
You didn't specifically mention ADB so perhaps you are already fixed for that or maybe don't think you'll want it. There are certainly some things that are really only possible with ADB when you start getting down and dirty with the device. But a good file manager and/or terminal app can also do a lot of stuff without ADB. Still, if you don't have it, the easiest way to get just ADB and not the entire Android SDK is to download and install Minimal ADB and Fastboot. This is for Windows. If you're using a Mac, you're on your own.
The apps in your list
I'm going to try not to editorialize too much here, but some things may not work as well as they sound and there might be better alternatives to others, so...based on my experiences (and prejudices...).
Extended Power Menu (caution, "reboot to recovery" option goes straight to factory re-image without any chance to say no! A possible alternative, my Alternate Power Menu app)
AndroNook Settings (I had trouble with this and the stock B&N system; some settings don't seem to work, some cause a reboot. A possible alternative my Nook Settings app--not as tidy but full-featured)
UsbMode (this is the kernal thing and/or maybe the activating app--already covered above)
TuneIn Radio (still works great, available in the package of apps linked in my signature)
QQPlayer (@pinguy1982 posted this copy--MX Player w/codec pkg also is great--again in my app pack)
FastMode2 (app already linked above; needed to activate FastMode with supporting kernal)
Opera Mini (installed with the updated NookManager packages. Direct link to Opera archive)
AirDroid (also, if you use ES File Explorer it has a "remote manager" capability. Creates an FTP address. You type in the address in the Windows Explorer address bar and voila, you can move files back and forth via WiFi. Hard to get to, though, buried in the app settings, so I made a little app to access directly. Also available as an option in my QuickTiles app.
adbWireless (ADB Konnect is installed by NookManager. One drawback: for long sessions you need to extend screen timeout since connection seems to drop when screen goes into sleep mode)
Nook Clear Screen (I found this not very useful; maybe I have a greater tolerance for little screen artifacts. Also available as an option in my QuickTiles app.
Terminal Emulator (couldn't track this one down in the forum so I uploaded a copy below)
Stock Settings (well, this is what's on the device out-of-the-box!)
I think (hope) that covers everything you mentioned. I did see a reference to an app called DroidSSH while I was tracking down some of this stuff, but no link. If that's something you might find useful, you'll need to do a lot of Googling.
If there is anything else, or something here is not clear, give a holler.
Click to expand...
Click to collapse
Looking very complete, thank you for the awesome work! I'm quite busy but I shall dedicate a couple hours before next week to go through this entire process.
I do have a questions which I think I know the answer to, but wanted to confirm: With NookManager, does it run its own OS from the SD Card, or does the normal internal Flash Storage OS load and then NookManager takes over?
Same with CWM - Does the whole device (properly) boot off of the SD card and not internal flash?
If they do boot off of the card, due to the bootloader (I assume UBoot from what I read, nice!) then that leaves a lot of custom linuxy opportunities available for a really lightweight Linux OS, though drivers might be a painpoint.
Thanks!

alexhorner said:
Looking very complete, thank you for the awesome work! I'm quite busy but I shall dedicate a couple hours before next week to go through this entire process.
I do have a questions which I think I know the answer to, but wanted to confirm: With NookManager, does it run its own OS from the SD Card, or does the normal internal Flash Storage OS load and then NookManager takes over?
Same with CWM - Does the whole device (properly) boot off of the SD card and not internal flash?
If they do boot off of the card, due to the bootloader (I assume UBoot from what I read, nice!) then that leaves a lot of custom linuxy opportunities available for a really lightweight Linux OS, though drivers might be a painpoint.
Thanks!
Click to expand...
Click to collapse
According to my understanding, both NookManager and CWM boot directly from the sdcard. You can check the card contents, replete with its own uboot, mlo, etc. Similar set up as the CM 11 card.

nmyshkin said:
[I'm going to try to address your issues in this single post, but not all at once. I'll be adding things over the next few days. Since I don't know where in the process you are currently, just skip things you have already done]
Updating to FW 1.2.2
[Note: if you have a UK device, go to: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/ and return here to the "Kernals" section after completing option 3]
If your device is still on FW 1.2.1 you will need to do a manual update. In theory, you should be able to download the update zip from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip), connect your NST/G to your PC via USB, copy the update zip to the "Nook" drive and wait. When the device sleeps, the update should be installed. If you come back later and look at the "Nook" drive and you don't see the update zip, it's done. You can check this by looking in the Settings app for the software version.
IF the theoretical procedure does not work for you, a deregistration might be in order. Since a device on FW 1.2.1 cannot deregister by contacting B&N servers (this is generally done via the Settings app), you will have to force a user data wipe. To do this, turn off the device. Power back on and as soon as you see the "Read Forever" screen, press and hold the two lower hardware buttons (page-turn buttons) until a prompt appears. Follow the on-screen directions. This will eventually leave you at the "Welcome" screen. Now attach the device to your PC via USB, drag the update zip onto the "Nook" drive and wait for the update to occur. Again, if you come back later and you don't see the update zip listed on the "Nook" drive, you're done. At this point you can continue and register your device.
IF the second method was unsuccessful, there might be something messed up with the resident FW. In that case, the best course is to initiate a factory re-write of the entire system. The eight-failed-boot attempts is painful and often very frustrating, but NookManager can do the job in the push of a button. So if you are still having issues updating, proceed to the "Rooting" section below and prepare a NookManager card. Then power down your device, insert the NookManager card and power up. Skip WiFi turn on. The "Restore Factory zip" option is found under "Rescue". Follow the directions and after a reboot you will be at the "Welcome" screen on some unknown FW. Attach the device to your PC via USB, drag the update zip to the "Nook" drive, and wait for the update to occur as described above. Once that has happened, continue on to registration.
Rooting
Go here: https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/ and choose whichever version of NookManager seems like it will best meet your needs. I strongly suggest you make a FW 1.2.2 registered backup before rooting (NookManager can do this). When your device is rooted and you have done some configuration on the possible launchers and/or file managers, return here to the next section, "Kernals".
Note: regarding your question about ssh and busybox, the latter is installed during rooting with NookManager. I'm really not familiar with ssh but I note that you can supposedly use it with NookManager running. There is some info on the opening screen where the WiFi option is located.
Kernals
The first kernal modification was for multi-touch to enable pinch-zoom for those apps that would support it on the NST. Every subsequent kernal has included this change.
Now it gets a little confusing. For practical purposes, only kernals based on at least FW 1.2.1 are of use. Earlier kernals do not understand glowlight control (you can work around this, but why bother?). So there are more or less three "modern" kernals for the NST/G, one without support for USB Host and two with USB Host support.
Kernal 166 (see attachment below) does not support USB Host but it does support both augmented display modes, NoRefresh and FastMode (with the appropriate apps installed). NoRefresh is an augment for flicker-free reading when scrolling in an app (like a webpage, for example) or when moving around on a PDF image. Based on the original development thread, this appears not to require kernal modification, only the installation and configuration of an app (link below). FastMode is an augment for, well, I guess for playing with video. It presents a highly dithered image (lots of tiny dots) in an attempt to simulate greater grey-scale. Initially it seems like a good idea (impressive coding, anyway) but it's not good at all for reading and there is a lot of ghosting in video until the screen is finally filled with swirls of dots in various states of visibility. At least that was my experience. FastMode requires both kernal modification and an app (link below). Kernal 166 is the only kernal that can run both display modes. Like all kernals that support FastMode it is overclocked, supposedly up to 1100 Mz, although I never saw it indicated more than 1000 Mz. When running it you probably should have a CPU governor app installed (download below), perhaps trim the CPU down to 800 Mz to help with battery life.
NoRefresh and FastMode both require apps to activate the display augments (not simultaneously). But the point of all this (since you want USB Audio) is to try to make clear(?) that any other kernal that supports FastMode kills NoRefresh (somehow). So, if you want USB Host/Audio (and you do) then you have to choose which display augment you want because you can't have both. That is not to say it's impossible (clearly kernal 166 shows that it is) but only that there is no existing kernal that makes it possible.
The two kernals which support USB Host probably have numbers. Maybe one of them is 174. But probably nobody knows at this point. The kernal in the CWM zip for enabling USB Audio (with all the nifty drivers) is an overclocked kernal that supports FastMode. If you would prefer to have access to NoRefresh instead of FastMode, you can use the kernal attached below (can't find the original link, so...). Just open the CWM USB Audio zip in something like WinRAR and drag the new kernal into the "boot" folder, replacing the file already there. Be sure to not recompress the file. Use the "store" or similar option when dragging into the opened archive.
Kernal installation can be done via adb. The directions for that are here. But since you have the CWM zip available and want to install all the audio stuff as well, the easiest path is via CWM. That means you need a card.
Download one of the two sdcard options from here and burn a card (do NOT install CWM internally on the NSTG! It will replace the fail-safe factory image!!). Then copy the zip with the kernal and audio drivers to the card and boot your NSTG from the CWM card. Install from the zip and you're good to go after a reboot. If you change your mind later about the kernal just swap in the one you want in the zip file and flash the whole package again.
Two details on this CWM USB Audio package: microphone recording is not entirely/correctly implemented in the files as supplied. If that is not important to you, skip to the next stuff. If you want to get it done right and then forget about it, you need to replace one of the files in the zip with a corrected version and you also need to copy a patched version of framework.jar into /system/framework. The zip of patches below contains the framework.jar and a file called alsa.default.so. You can use a file manager to copy the framework.jar into /system/framework. Be sure the permissions are set the same as the original (you can rename original to framework.jar.bak first, if you want). Then reboot.
As for the little alsa file, open the CWM USBAudio zip and navigate inside to system/lib/hw. You'll see the original file there. Drag the replacement over and be sure not to recompress it (i.e., use "store" or similar). Now the zip is good to go for a complete USB Audio installation including both playback and recording. Whew!
USB Audio
Of course, it's not that simple. There's no headphone jack or speakers. How does the audio come out?! You need two pieces of hardware (three, if you count earbuds/headphones---or a cable to attach to the auxiliary jack of your sound system) and some software.
USB Host in general requires the use of an OTG cable stub. This seems to be a very critical part of the arrangement. My first cable fit poorly and I almost gave up on the whole enterprise. A second one fit in the slightly non-standard USB jack like a hand in a glove. Suddenly it all worked! I can't tell you which cable might work for you. They are cheap (that's part of the problem...) and you may need to try more than one. Amazon, ebay, etc. Some are straight-line, others 90 degrees. What's important is a good fit. I'm not saying the example in the link above is a good fit. I got mine so long ago I have no idea where it came from. Probably ebay. Long gone.
Since the NSTG has no sound hardware, you need a USB-C external sound card device (here's another link to the button/LED kind--expired, but you get the idea). These also are not very expensive and can be found on Amazon or ebay. There are two basic designs. One has a bunch of LEDs that just waste battery power. It may also have volume control and/or other buttons. The other one is more spartan, lacking LEDs and buttons. I have one of each and never use with one with the LEDs.
To initiate USB Host or Audio you need at least one app (each). @Renate has produced an app for USB Host and an additional one for USB Audio. They can be downloaded from her signature page. Both are used to activate USB Audio. They are great for diagnostics but I just never have any issues with USB Host (that perfect plug!) so I wanted something that would be simpler. Just one touch. I made two small apps, one for USB Host (does not activate audio stuff) and one for USB Audio (sets up host and activates audio). The latest version of the USB Audio app places volume control buttons on the screen when in use, so you really don't need a device with volume buttons. My apps are found here. These routines are also included as options in my QuickTiles app.
ADB
You didn't specifically mention ADB so perhaps you are already fixed for that or maybe don't think you'll want it. There are certainly some things that are really only possible with ADB when you start getting down and dirty with the device. But a good file manager and/or terminal app can also do a lot of stuff without ADB. Still, if you don't have it, the easiest way to get just ADB and not the entire Android SDK is to download and install Minimal ADB and Fastboot. This is for Windows. If you're using a Mac, you're on your own.
The apps in your list
I'm going to try not to editorialize too much here, but some things may not work as well as they sound and there might be better alternatives to others, so...based on my experiences (and prejudices...).
Extended Power Menu (caution, "reboot to recovery" option goes straight to factory re-image without any chance to say no! A possible alternative, my Alternate Power Menu app)
AndroNook Settings (I had trouble with this and the stock B&N system; some settings don't seem to work, some cause a reboot. A possible alternative my Nook Settings app--not as tidy but full-featured)
UsbMode (this is the kernal thing and/or maybe the activating app--already covered above)
TuneIn Radio (still works great, available in the package of apps linked in my signature)
QQPlayer (@pinguy1982 posted this copy--MX Player w/codec pkg also is great--again in my app pack)
FastMode2 (app already linked above; needed to activate FastMode with supporting kernal)
Opera Mini (installed with the updated NookManager packages. Direct link to Opera archive)
AirDroid (also, if you use ES File Explorer it has a "remote manager" capability. Creates an FTP address. You type in the address in the Windows Explorer address bar and voila, you can move files back and forth via WiFi. Hard to get to, though, buried in the app settings, so I made a little app to access directly. Also available as an option in my QuickTiles app.
adbWireless (ADB Konnect is installed by NookManager. One drawback: for long sessions you need to extend screen timeout since connection seems to drop when screen goes into sleep mode)
Nook Clear Screen (I found this not very useful; maybe I have a greater tolerance for little screen artifacts. Also available as an option in my QuickTiles app.
Terminal Emulator (couldn't track this one down in the forum so I uploaded a copy below)
Stock Settings (well, this is what's on the device out-of-the-box!)
I think (hope) that covers everything you mentioned. I did see a reference to an app called DroidSSH while I was tracking down some of this stuff, but no link. If that's something you might find useful, you'll need to do a lot of Googling. (or maybe it was SSHDroid?
If there is anything else, or something here is not clear, give a holler.
Click to expand...
Click to collapse
Kernel installed via CWM, USB audio working! Not a fan of FastMode and can't be bothered to mess with NoRefresh yet. Going to look at the OpenSSL stuff soon I think though.
Installing various apps from your list above and also your personal app list as linked in your signature, thank you once again!

Database Users

welcome