Database Users

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?

[GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix

This is a step by step guide to install ClockworkMod v08, a ROM of your choosing, Flash, and the Android Market fix. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
I do NOT accept responsibility for anything good, bad, or indifferent that may come from following this guide. This includes and is not limited to completely destroying your tablet. I highly recommend leaving your tablet plugged in while doing anything like this with your device. I have no idea what will happen if the battery dies in the middle of flashing a ROM (if anything…but better safe than sorry).
ALL THE FILES NEEDED FOR THIS GUIDE EXCEPT FOR THE ROM ITSELF CAN BE FOUND AT THE BOTTOM OF THIS GUIDE.
ROM XDA Pages (Look at these to pick what ROM you want to use.)
TnT Lite
VEGAn-Tab
CyanogenMod 7 (Gingerbread)
Notion Ink Adam ROM Port
You do NOT need to root your tablet to install a ROM on this device using this guide. All the after-market ROMs come pre-rooted so you don't need to root after installing either.
Part One – Install ClockworkMod v08
ClockworkMod is what will ultimately be used for all your flashing of ROMs, backing up, clearing cache, etc.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.) There are two versions available; one for installing ClockworkMod from the internal memory, one for installing it from external memory (microSD/microSDHC card).
Step 2.
Unzip the file you chose (cwmod_internal.zip OR cwmod_microsd.zip) to the root folder on the storage option of your choice.
So, for example, if the storage option you chose has the drive letter “F:” assigned to it when hooked up to your computer, you would want it to look something like this…
A folder located at “F:\recovery”
A file located at “F:\update.zip”
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch ClockworkMod install. This will not take long. Your tablet will reboot when installation is complete.
Step 6.
Enter ClockworkMod:
To get into ClockworkMod you need to shut down your device, then press the Power and Volume+ button (the same way you did to install ClockworkMod).
Navigating ClockworkMod: Vol+ and Vol- are to scroll up and down, the home button selects an option, and the back button backs up.
Step 7.
Re-Partition your Tablet:
In order to make sure the Android Market works correctly after installing any ROM, we must re-partition the device.
Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared.
Part Two – Install a ROM.
A ROM (explained in very basic terms) is like Windows on your computer (assuming you’re not running Linux or Mac OS). Each ROM contains a customized version of Android that comes packaged with software, themes, and everything else you actually see when the device powers up. You install any additional apps you would like to use after installing the ROM. Beware, ROMs are device specific. You cannot reliably install ROMs designed for another device.
Step 1.
Now that your device is essentially empty, we need to be able to put files on it. ClockworkMod can do this for us. Connect your tablet’s USB cable from your tablet to your computer. Go to the ClockworkMod main menu, then navigate down to “mounts and storage”, and then select “mount USB storage”. The tablet’s internal storage will then be accessible from your computer. You will want to open it, and create a folder called “ROMs”.
Step 2.
Download whatever ROM you want to use. The links to the ROMs are located above. Click on the link to see what that ROM looks like. The most popular ROMs for this device are TnT Lite and VEGAn Tab.
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is).
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
Step 4.
Turn off your device.
Step 5.
Boot into ClockworkMod. (Press the power button and the volume+ button at the same time until the Viewsonic splash screen pops up, release, then you should see “Detect a recovery key pressed”. After that it will think for a few seconds and then it should boot into ClockworkMod)
Step 6.
Stand up and do a dance. Sitting too long isn't good for you.
Step 7.
Back up to the main menu, then navigate down to “mounts and storage”. When that is highlighted press the home button to select it.
Step 8.
We want to mount “/system” and “/data”.
The goal is to see the following:
“unmount/system”
and,
“unmount/data”
If either one says “mount” instead of “unmount” you need to navigate to that line and press the home button to mount it.
Step 9.
This is the step that we actually flash the ROM in.
From the ClockworkMod main menu, navigate down to “install zip from sdcard” and press the home button to select that option at the menu.
Then, navigate to “choose zip from sdcard” and press the home button to select that option.
Navigate to the line that reads “ROMs” and press the home button to select that option.
Navigate to the line that reads whatever .zip file you wish to install and press the home button to select that option.
Navigate to the line that reads “Yes – Install yourzipfile.zip” and press the home button to select that option.
You will now see it do its thing. When complete you will see something along the lines of “install zip from sdcard complete” at the bottom of the screen.
Press the back arrow over and over again until you get to the Clockwork’s main menu.
Step 10.
Here is where we prepare the system to run the new ROM.
Navigate down to “mounts and storage”, select it, and mount “/system” and “/data” again as in steps 7 and 8.
Back up to Clockwork’s main menu.
Navigate to “wipe data/factory reset”, select it. Navigate down to “Yes – delete all user data”, and select it to wipe out user data and all the cache. (You need to do this for the new ROM to function correctly)
Now, navigate to the top option “reboot system now” and select it. Your tablet will now reboot. It may take up to 15 minutes to start up the first time as it rebuilds the user data and cache for this ROM.
If your tablet boots to UID errors, or has force closes (known to fix a few of them)…
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, and then go to “Fix Permissions”. Afterwards, back out to the main menu, then select “reboot system now”. If that is unsuccessful then boot back into Clockwork and redo steps 7-10.
Part Three – Install Flash and fix Android Market
This is needed to view websites with Flash based content, and to download apps from the market. (Fairly obvious, I know, but just in case somebody doesn't know.) Log in/set up your Google Account before trying the market fix (steps vary on the ROM you are using…in most cases you can access the web accounts by opening the Contacts app, pressing the menu button (the one above the back button), and selecting accounts).
Step 1.
Download “Adobe Flash Player 10.1.120.1.apk” which you will find attached at the bottom of this post and save it on your tablet (I recommend creating a separate folder to save .apk files in).
Step 2.
On your tablet open up whatever file explorer comes pre-installed with the ROM you’ve selected. In there, open up where you saved your .apk, then select Adobe Flash Player, and follow the on screen instructions to finish installing that.
Step 3.
Open the Market app. Once it loads close it (press the home button).
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy. You should now have Flash and the Android Market.
This is the Titanium Backup method. Thanks to roebeet, xguntherc, and KorbenD.
http://forum.xda-developers.com/showthread.php?t=845175
Part Four – Show your appreciation! (First, be sure to play some Angry Birds)
I encourage everybody to take the time to send a kind message, or a small donation, to everybody that helped make this device what it is. This is not me saying "HEY HEY DONATE TO ME!!!!"...like some developers for other devices do. I just feel like the great ROM developers for this device don't get the credit they deserve, so please at least send them a quick thank you note. Keep in mind that ROMs, utilities, and yes (even guides), take a considerable amount of time to plan, compile, test, fix, and distribute.
With the following link you can donate as much or as little as you would like to me (even a dollar helps). Thanks and enjoy your tablet!
Donate Here

Thank You. This is exactly what we need. One thread with all the info consolidated into one will help many new users understand what to do. People otherwise may have come here and just been blown away by the different threads, I sure was when I first decided to Root my Eris.

scsione889 said:
This is a step by step guide to install ClockworkMod v08, TnT Lite 2.2, Flash, and get the Android Market working. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
...
Part Three – Install Flash and fix Android Market
Step 1.
Create a folder on your SD card called APKs. Download “Adobe Flash Player 10.1.120.1.apk” and "TitaniumBackup_latest.apk" which you will find attached at the bottom of this post and save them in that “APKs” folder on your SD card.
Step 2.
On your tablet open up “ES File Explorer”. In there, open up the “APKs” folder, then select Adobe Flash Player, and follow the on screen instructions to finish installing that. After that, select Titanium Backup in that same folder, and install the same way.
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps.
Step 4.
Open up Titanium Backup, go to Backup/Restore and look for Google Services Framework, select it, then select “Wipe Data”
Step 5.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 3 and 4 until you do.
Step 6.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 7.
Open the market again and enjoy. You now have Flash and the Android Market. (Keep in mind, this is not the FULL market, it just makes around 99% of it available. It is unknown which apps are not available. There is a full market fix, but it is MUCH more complicated).
Click to expand...
Click to collapse
Extremely Well Done!
Would be Nice to get this Stickied to keep easy for newbies to find...
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Also I only needed the first reboot in Step 6, wait a few minutes then tried Market and all was fine! No multiple reboots needed for me at least...

Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.

LTL11 said:
Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.
Click to expand...
Click to collapse
This technically isn't needed for TnT Lite...but if people were to use this guide as guidelines for installing other ROMs (as I hope people would do...you know...following directions is good, but learning what your doing is GREAT), step 8 is something that is always good to get in the habit of doing before a flash.
With many other ROMs, on this device and others, not mounting /data and /system before flashing causes headaches.

jtbnet said:
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Click to expand...
Click to collapse
I did it using 'Clear Data' as well...but this was my way of getting newbies to use TB (and to get more familiarized with side-loading apps). It's a great utility that I feel Android users should be familiar with.

Great guide, added clarifications
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.

Tommunicator said:
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.
Click to expand...
Click to collapse
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.

omnifox said:
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.
Click to expand...
Click to collapse
Sorry about this guys. Editing it now.
FIXED.

After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin

kevin stone said:
After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin
Click to expand...
Click to collapse
Does it display an error? Please be a little bit more specific. Did you try restarting the tablet (not just putting it into standby and bringing it back up)? Also, were you sure to force close the apps before clearing the data?

I did all these steps last night and everything seemed to work as expected. When I woke up this am and actually started to play with the Market, I realized that even though the Market looked good last night, all the important apps are gone this morning. I followed the instructions on the forms and on youtube videos and got the exact same results that were to be expected. I got all the errors and rebooted when asked and thought I was ok. When I opened Market after the Fix Process, all the same apps I would see on my HTC Evo are there. HOWEVER !! once I try to search or change the category to Apps or Games, or go to the sub catagorys 90% of the apps disappear. My app / game selection is now only 1 page long
When Market first opens up, I see Angry Birds and other apps I want, in the category description, but when I try to navigate to them, the screen simply says "loading" and never come up. It will stay that way for over an hour. The only thing I can do is change another catagory. When I do that, the loading text goes away and apps will show up, but alot are missing. Even the category description like for "Action Games" no longer lists Angry Birds in it. And if I try to search for an app I know is in the market like Advanced Task Killer... it says it can't be found.
I repeat the Market Fix process over and over and over again with the exact same results. Any Idea? Everything else seems to be working fine. Flash and Titanium Back up work perfect. Just can't get Market to show all the content.

I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\

You guys rock!
Picked up my GTab today @ Staples. 45 minutes later it's ready to go with TnT 2.2, full Market access and Flash using this guide! So far...so good!

Thanks for taking the time to write up this guide. Saved me from the slower-than-molasses-out-of-the-box-os-setup they shipped the tablet with.

Can't access Gtablet VIA USB cable from PC
I installed CWM 8, TNT lite 2.2 and performed market fix. Now my Gtab is working great. Prior to this thread I was stuck in a loop. My gtab is running great thanks a lot for posting this tutorial.
My only issue now is I can't access the internal SD from PC. Nothing shows up on my PC when I connect the USB cable to my Gtab. I have tried unmounting and mounting SD several times in CWM.
Prior to this update I was able to access and sideload APK's on my gtab running stock software with Viewsonic update.
any help would be greatly appreciated.
Wyngnut

Well after booting up a couple of times it just started to work (my Gtab showed showed the SD card option). I have downloaded several programs and they all install automatically and every one of then worked. No sideloading no additional steps for install this is amazing. I was coveting the windows 7 tabs on the horizon but the free programs available through the market are amazing and when they are Combined with the Gtab hardware its amazing.
Thanks again for posting this there is no way I would have tried to put this software on my system if I had not seen this guide.
Wyngnut

sano614 said:
I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\
Click to expand...
Click to collapse
The tablet doesn't seem to like giving the PC access to the microSD card. As far as I know this is a feature that is not available in any ROM. Also, it is my understanding that for this sort of thing to be possible we need to have the device's source code so we can make the hardware/software mesh better.
That is...unless I'm missing something very obvious...which is totally possible.

Thank you so much for taking the time to write this, worked perfectly for me

It's AMAZING!
Thanks to everyone on the site - from Roebeet and pals who pulled it together to scsione889 and others who did the walkthrough. For an absolute newbie (didn't know what "root" meant) to be able in one day to turn an absolute clunker into what I have now is unbelievable.
If you're new like me, and wondering whether you can pull it off, you can. Just make this the one time in your life when you read and follow the instructions exactly, without your usual improvisation!

[GUIDE] New unbrick guide compilation

I’ve been helping a buddy get his A500 back to working order, so I thought I’d add the steps taken here which lead to successful replacement of boot loader and ability to flash roms again.
First off Blackthun3r is a genius and you cats should totally donate and thank him if this stuff helps.
The info is a bit spread out so I hope this helps consolidate things. We all owe big ups to jnktechstuff for starting this post here:
http://forum.xda-developers.com/showthread.php?t=1699277 go thank him too.
One thing everyone is right about: You must secure your ID just in case, which is needed to properly reprogram the stock/crappy recovery boot. Two options I saw:
1) From a nandroid backup (inside the clockwork recovery folder or wherever your previous bootloader stored them) there is a uid.txt file.
2) When you run Afterota if it can’t find a uid it will generate a file “AcerIDs.txt”.
Afterota is great too but wouldn’t fix/attached to our A500 in APEX mode, but this feature alone is huge.
For AfterOTA, Thanks and Salute to Gersma:
http://forum.xda-developers.com/showthread.php?t=1675939
Next is just getting the thing to boot.
http://forum.xda-developers.com/showthread.php?t=1699277
Mentioned in “How to unbrick” , as stated they suggest you get 3 files. Here’s what we got :
1) Decrypter (mandatory)
2) 2 ICS roms (you only need one, but he suggests to get both just in case, or even an older Honeycomb if those fail you).
The one that worked for us was ICS 4.0.3: 7.014.01_41.203.01.
Extract the decrypter and use on the rom/zip you downloaded. It will make a separate rom/zip with the words ‘decrypted’ at the end. EXTRACT THIS FILE!
Inside the newly extracted zip file should be 3 files. If you don’t have it or your zip program says it’s corrupted then you don’t need to decrypt it, use the non-encrypted version of the rom pack you just downloaded (i.e. it wasn’t encrypted)!
3 files will look like:
1) Update.zip
2) AMSS.zip
3) Acer_A500_7.014.01_041.203.01_COM_GEN1.txt (or whatever rom you had downloaded)
These 3 files need to be on the root of your external SD micro card (either put it into a reader for pc access or if your system is functional copy it over via USB cable while mounted in the A500). The basic bootloader does nothing but check for an update.zip and apply it. However, it cannot replace itself (saw with a CWM or TWRP) and thus what I think is the ‘rub’ with this device.
After the update.zip applies, boot the system normally. You should have a locked OTA version of ICS with USB Debugging enabled, if not, hit Options, Developer and turn on USB Debugging. If it doesn’t boot, try another rom/decrypt combo. If it boots moved these three files into a sub folder on your SD Card and save for next time you brick it
Next, get the right driver for Windows from Acer site (this is important because it has the ICS USB and the APEX/boot USB driver needed):
http://www.acer.be/ac/nl/BE/content/drivers
You now need to unlock, add SU and Super User. Hit the following link and get Blackthund3r’s Root app (ICS7.1.x for Windows) top of page:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
When you hit some of this download links be sure to check for things like the skip ad button top right corner, else you’ll download the wrong thing:
Extract and run “ICS Root 2.exe”
1) DO NOT mess with the bundles tabs right now, but ensure all checks minus bottom two are selected and ‘Do it!’
2) You should see that it does confirm for you that it is connected and USB Debugging turned on.
You should now have the device setup to run a proper APEX adjustment, which lets you replace the bootloader and then apply all the little zips and roms your heart desires. Blackthund3r has the last tools we need:
Get APXFlash: http://a500bootloaderflash.tk/#download-links (again watch out for the adfly and click skip add to get to your zips).
APXFlash has all the bundles from proper Blackthund3r repository, the FAQ below may have suggested certain types but that info is kinda old SO just grab a bundle 15, 16 or whatever you are looking for (16 is a great team wiz recovery version combo Skrilax has done, we used that one).
1) Go to Bundle Market and follow the wizard:
2) After downloading the bundle of choice you’ll now be prompted to put in your SBK number from that Acer ID or uid txt file.
3) You should then back up your dump file as it is recommended in the process.
4) Hit blue arrow ‘next’ to see your flash options below, we used the Automatic method, smooth as butter.
5) Follow the prompts for APX mode and click blue once the device is blacked out and the mode has changed on status. This is where that official Acer driver comes in handy.
6) Complete the process as instructed and you’ll be good to go!
Last tool used is:
A500 Manager: http://a500bootloaderflash.tk/#download-links (again watch out for the adfly and click skip add to get to your zips).
This app rocks to help you get into recovery mode (or test your new bootloader) until you get a rom on there that allows you to do it from the power off button or notification tray.
Most of these links and info are at the bottom of Blackthund3r’s FAQ page, which were also super helpful:
http://a500bootloaderflash.tk/
Again this helped my friend and he was thinking several of you could benefit. Even when typing this up I figured some better/quicker ways to maybe get some of the data but this is the thorough steps we took and I hope it helps you! I also had screen caps so once I figure out how to add those, if it'll help or someone needs it will look into that ;p

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".
Kernals
To be continued....
Click to expand...
Click to collapse
I see you have already written a lot on the linked UK thread too, and that unfortunately shows me it's hard to find the right resources scattered over XDA. Nevermind.
I do indeed have a UK device running 1.2.1 so I shall follow your 1.2.2 upgrade guide. I actually factory reset and deregistered my device but retained a backup which I took with NookManager of the registered version so I guess I'll keep ahold of that and watch for more information on this thread!

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!

Nook Glowlight Plus 7.8 2019 (NGP7.8, BNRV700)

This one20092011201220132015201720192021Nook v1 Nook Simple TouchNook Simple Touch w/ GlowlightNook GlowlightNook Glowlight PlusNook Glowlight 3Nook Glowlight Plus (7.8 inch)Nook Glowlight 4
The other one
The 2019 Glowlight Plus shares the same name as the 2015 release. To avoid confusion, people began referring to it as the Glowlight 4, a name later used for the 2021 Nook release (surprisedpikachu.jpg). While the 2019 Nook is both confused with the 2015 and 2021 Nooks, it is less common than either. This makes it difficult to find compatible resources and tutorials.
This thread is for collecting the available resources for the 2019 Nook in one place, and eventually building a step-by-step guide for unlocking the potential of the device.
Why the BNRV700?
Three years after its release, it's currently the cheapest option for a reader with a screen size ideal for large format PDFs, such as textbooks. As of writing, the Nook Glowlight Plus (2019) can be found for half (or less) the price of other options with a similar display.
Unfortunately, the Nook ships with poor support for PDFs, sluggish hardware, severely outdated firmware (Android 4.4.2, released 2013) and lacks additional features like expandable storage. Some of these issues can be remedied, meaning the Nook could be a great option for many people, but only if it's safe and convenient to expand its functionality.
If you know of any useful resources or guides, please leave them in the comments below.
Note: This is an early work in progress. As of writing this, I don't have the device yet.

I'm reserving this space to put any resources, or document my experience with rooting or recovering the Nook Glowlight Plus 7.8 2019 (NGP7.8, BNRV700).
Resources
Technical
Hardware overview: Temblast​Backup and Recovery
TWRP: Github​Neo Noogie: Temblast, XDA-thread​Rooting
Magisk Root guide (Glowlight 4): Mobileread-thread​Caution: This guide is specifically for the Glowlight 4 (2021) rather than the Glowlight Plus 7.8 (2019) but it might be applicable.​RootGLP-3 script (Glowlight 3): XDA-thread​Caution: This resource is for the Glowlight 3 (2017) rather than the Glowlight Plus 7.8 (2019), however it has been reported to work.​RootGLP-3 script (2019 Glowlight Plus): XDA-thread​Note: This is a small modification of the Glowlight 3 (2017) root script for the 2019 Glowlight Plus, from wgznz (Chinese).​Firmware
Alternate ROM: XDA-thread​Software
Installing a launcher:​Installing apps:​Compatible readers and utilities:​Adding wallpapers:​Adding a software back button:​Physical button remapping:​Hardware
Expandable storage mod::​
High risk or incompatible resources
Mods
NGP Exposed module with fast refresh: Mobileread-thread​Supported: Nook Glowlight Plus (2015), Nook Glowlight 3​Notes: Due to the similarities between the NG3 and NGP7.8 (2019), someone might be able to get this to work, but it's untested.​

jun127 said:
I think more people would be willing to try it. But, between confusing and inconsistent naming making searches difficult (now even worse with the "Glowlight 4") and a lack of step-by-step guides, it's a minefield for the casual user to modify, and most aren't interested in the sub-standard Nook software.
Click to expand...
Click to collapse
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.

nmyshkin said:
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.
Click to expand...
Click to collapse
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
Rough draft / work in progress (proceed at own risk)
Getting started
Download and install ADB
Using Android Studio
1: Download Android Studio
2: Scroll down and click on “SDK Tools Only”
3: Click on “ADB, Fastboot, and Platform Tools” and then click on the “Download” button.
4: After “adb_setup-x86.exe” is downloaded by the installer, run it and install adb inside the android SDK folder.
Using Minimal ADB and Fastboot
1: Download the installer or portable version (See: original XDA thread, latest version 1.4.3, 2018).
2: Install and run
Note: If you use the portable version, commands should be ran from the same directory. To open a console in the current folder on Windows, select the address bar, type cmd and hit enter.​
Enable USB debugging through developer options
1: Unplug the nook from the computer and turn the Nook on, register an account with Barnes and Noble and finish setting the device up.
2: Pull down the top menu
3: click "see all settings"
4: Press the down error on the bottom of the menu to go to the second page of settings
5: Press "about"
6: Tap the Nook logo until developer mode is enabled
7: Press "developer option settings"
8: Enable the "usb debugging" option
9: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.​Note: When running commands over USB, sometimes it's necessary to temporarily disable mass transfer mode. To do this, go back to the developer options menu and select "disable mass storage".​Important: Remember to re-enable mass storage mode if you would like to drag-and-drop files onto your device using Windows file explorer later.​
Backup and restoration
The two most popular methods of creating and restoring backups are TWRP and Neo Noogie. If possible, it's best to have a backup from both. However, if you're not comfortable using the command line in Windows, you may choose to use TWRP only. Neo Noogie is a more powerful (complete) backup method, but it's easy to accidentally format your device or write a backup to the wrong Windows drive, either of which could be a nightmare.
TWRP is recovery software that is installed to the device, and provides a menu to backup and restore parts of the device to internal memory. You'll have to copy the recovery files from your device afterwards.
Neo Noogie can either be installed like TWRP or booted with fastboot. When booted into Neo Noogie, the entire flash memory is served to Windows and appears as a raw unformated drive. The internal storage can then be copied with special software. This has the advantage over TWRP in that it can be used to backup every aspect of your device, but you have to be very careful not to accidentally format the drive in Windows, as it could brick your device.
TWRP
Download TWRP
1: Download twrp_quill.img (may, 2020) from https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases
2: Move twrp_generic to a folder (such as Documents\Nook)
Install TWRP
3: Power the NOOK BNRV700 off.
4: Hold the U button and then the power button until it starts into fastboot mode.
5: Connect the Nook to a Windows computer with USB, the drivers should be installed automatically.
6: Open the command prompt or Minimal ADB and Fastboot
7: Navigate to the folder you saved the TWRP image in (ex. starting from your user directory, enter "cd Documents\Nook").
8: Enter fastboot flash recovery twrp_generic.img to install TWRP
9: Enter adb reboot recovery (or interrupt startup 5 times) to enter TWRP recovery mode
Create backup with TWRP
Notice: (TWRP will not backup /storage/spsd as well as /data/media, which in practical terms means ...xyz...)
1: (I don't have a Nook anymore as my NST screen isn't working and haven't used TWRP in 10 years. I imagine it's something like boot into recovery/TWRP > Backup > check all the options > run)
2: Plug the Nook into the computer
3: Select USB mass transfer protocol
4: Open the Nook in file explorer and find wherever the recovery was saved to
5: Copy it to a safe place, like documents\nook.
Uninstall TWRP / reinstall stock recovery
The Nook's update file, 'update.zip' contains a copy of the stock recovery which can be reinstalled if you wish to return the Nook to factory defaults. However the stock recovery has fewer recovery features - so it is always safest to keep TWRP installed if you are tinkering with the device.
Rooting
Root Guide for the 2019 Glowlight Plus (using rootGLP)
1: Ensure you've enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.​3: Disconnect the Nook and go back to the developer settings menu (see steps 2.1) and select "disable mass storage".
Note: This will prevent USB mode from interfering as we run the ADB script.​3: Download rootGLP.rar
Note: this is the same root script for the Glowlight 3, updated with the correct device name BGRV700. The original can be found in this XDA-thread. For a root guide for the Glowlight 3 using rootGLP, see this XDA-thread. The source is the wgznz forum (Chinese).​4: Extract rootGLP
Note: It's best to run the script from a location like C:\rootGLP\ or D:\rootGLP\.​5: Run the rootnook.cmd
Note: After the process is complete, you will see superSUfree appear on the screen. You will still need to install an alternate launcher.​
Installing apps
Installing a launcher and apps (doesn't require root)
If you haven't installed ADB, you can use the copy of adb.exe in the rootGLP-3\bin\ folder by following the instructions below. After installing a launcher, you should consider installing a file browser (such as ES file explorer) and a better web browser, so that you can download and install apps without connecting to your computer.
1. Make sure you have enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2. Navigate to the rootGLP-3\bin\ folder.
3. Place the launcher .apk inside the bin folder with adb.exe.
4. Click the address bar in Windows Explorer and type "cmd" without quotes and hit enter. A windows CMD terminal will open at the current folder address.
5. type adb install launchername.apk (replace with the name of your .apk file)
Note: kk launcher and text launcher are known to work.​6. When you hit the U-shaped home button on your Nook, it will prompt you to select a launcher and ask if you would like to set it as the default. I recommend using "only once" at least until you can ensure you can always get back to the default launcher from whatever Android 4.4.2 compatible launcher you choose.
Installing KOreader and getting pageturn buttons working in KOreader (no root)
1. Download KOreader apk from https://koreader.rocks/
2. make sure your device is connected to adb and authorized with adb devices, if it t says "unauthorized", go to the developer menu (nook home > top right > all settings > page 2 > more > repeatedly tap logo) and tap "allow debugging".
3. install adb install koreader.apk. just hit tab to autocomplete the actual apk name.
4. Create a textfile "event_map.lua" in notepad and copy paste the following keymappings:
Code:
return {
[141] = "RPgBack",
[142] = "RPgFwd",
[140] = "RPgBack",
[139] = "RPgFwd",
}
5. use command adb push event_map.lua /sdcard/KOreader/settings/ to push the event map to the koreader settings.
6. If you had already installed and started KOreader before and just want to fix the keymapping, restart KOreader for the new settings to work (launcher > settings > apps > KOreader > force stop > home button > open KOreader > open book > test buttons > enjoy.

The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?

jun127 said:
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
etc.
Click to expand...
Click to collapse
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391

nmyshkin said:
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391
Click to expand...
Click to collapse
I'd like to put together a simple guide, similar to what I wrote for the original NST about 10 years ago. I think the device needs a roadmap to outline what is currently possible in terms that are easy to follow. The device seems like it has a lot of potential, but it's just not very accessible at the moment.
I watched your video on running the CM on the NST, very interesting stuff and I'm glad to see some people are still keeping the device alive. I had used the original NST as a smartphone for a (short) while, even using it with Google phone and Whatsapp. It was surprisingly functional and, with the right optimizations, the battery could seemingly last forever with light use. Although it otherwise held up well, the rubber front panel and soft-touch back eventually degraded into a gooey mess. Removing the soft-touch coating on the back shell and replacing the rubber on the front with leather made it a more enjoyable reading experience for a while. Unfortunately, very poor app availability on Android 2.1 and the small, relatively low resolution display made it almost unusable for large format PDFs. Ultimately, the screen started failing and although it's still worth fixing, after 10 years it's overdue for an upgrade.
Renate said:
The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?
Click to expand...
Click to collapse
There's some peace of mind in knowing how to return things to exactly where you started. Even if unnecessary, there's always the possibility of some unforeseen issue and having a clear roadmap that you can follow to get back to the very beginning makes a difference in my mind.