Related
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!
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
I have been working on changing the Operating system on my A500 for the past 3 days. I'm retired and it really has been three 12 hour days. The forum has been a font of information but it is scattered and confusing to someone new like me. I have been writing what I did and wanted to share it with the other noobs. Of course I had to register on the forum first. So today is my first day registered and here is my first post.
A procedure for changing the ROM in an A500
This procedure is for Windows. It can be done on Mac and Linux but we're not going there. It uses Afterota v1.09 by gersma. Although the program is great, there is really no explanation of how it works or how to use it. I hope this procedure helps the noobs like me.
You can install Honeycomb (HC), Ice Cream Sandwich (ICS) or Jelly Bean (JB). I'm not giving links because they change, are unavailable or otherwise wrong. Plus this is written to be printed and followed on paper because there is a PC restart involved; also I sometimes lose my place while online. If you can keep it straight, more power to you. I'm writing this for complete noobs. Admit it, we were not born knowing this stuff. As a complete noob I am also assuming you and I have not changed our A500 in any way other than the normal updates from Acer and Google.
Now for the disclaimer:
You do this at your own risk. If you point a finger at me and start yelling, I will hold up a mirror facing you so you can see who is to blame.
Prep your A500 for the procedure
For safety sake, remove the micro SD card if you have one installed.
Plug the A500 in to AC power, power it ON and ensure it is fully charged. Keep the tablet powered from AC. Ensuring it is fully charged is insurance against accidental power loss. You don't want to loose power while doing this procedure or your tablet could become a paperweight. Place the tablet close to the PC (notebook or desktop) you will be using for the procedure. You're going to connect the tablet and PC together with a USB cable later. The best cable is the one that came with the A500, the one with the micro USB end and regular USB at the other. If you use something different, make sure it is a good quality cable.
The next step is to set the tablet to accept changes. Tap Apps → Settings → Developer options → USB Debugging.
If your tablet is password protected, disable it now. You'll have to set it up again anyway after the change.
Prep your PC for the procedure
Download and install the USB drivers for the A500 from acer.com.
Go to the xda-developers.com forum and download Afterota. You can search for the program. It doesn't require installation, it just runs as is.
Another thing to look up is recovery apps. There are a number of them and they all do the same thing in slightly different ways. Afterota v1.09 offers four, Thor 1.7.3 (touch screen), TWRP 2.1.3-ICS (touch screen), Ra v3.1.7 (touch screen) and Pub v0.2 (Vol and power button). I discuss recovery later.
Next we need a ROM to load. Again, go to xda-developers.com and search for one that interests you. They are under the Iconia A500 Development section. When this was written, I installed JB 4.1.2. I highly suggest you read up on the ROM you want. Check for status, useability, included apps, excluded apps, bootloader requirement (for this procedure ICS), etc. When you finally download your preferred ROM, do not extract it. You will be using it in the zipped form.
I have seen a zip file called gapps (Google apps) on xda-developers.com. It appears to be needed for some ROMs. Again, download it if necessary but do not unzip it. The JB ROM I used specifically stated the gapps were included.
The next step is to disable User Account Control (UAC) in Windows. Go to Control Panel → User Accounts → Change User Account Control settings and drag the slider to the bottom. You will have to restart the PC for changes to take effect.
The procedure
Install bootloader and recovery
It looks like you're ready to proceed.
Connect the PC and tablet together with the USB cable. Place the small end into the tablet and the larger end in a PC USB port. You will see the device drivers load and Windows Explorer will ask what to do. Click on Open device to view files.
At this time, you can browse the tablet using Windows Explorer. Most everything you want to see is on the Internal storage partition. If you have a micro SD card inserted, it will show as SD card. I strongly suggest you check through the folders for any data, documents, music, videos, etc that you may want to safeguard. Copy the folders and/or files to the PC. If they get destroyed on the tablet, you can copy them back later.
Run Afterota. The first thing Afterota does is collect information from your A500. It takes a few moments so be patient. When done, it will save the text file, AcerIDs, to your desktop. This file is very important. It will have the tablet's serial number, CPUID, SBK and other stuff. It is a very good idea to save it and/or print it for future use; it could get overwritten later.
There are five tabs in the Afterota window. Info – where we just collected the information, Stock – to go back to HC, Standard – where we will be going next, Advanced – unbrick and other stuff and About.
In Standard we need to choose a bootloader.
What exactly is a bootloader and why do we need it? A bootloader is akin to the starter of a vehicle. You insert your key into the ignition and turn it to start the engine. A bootloader starts the operating system (engine) of your tablet. If you change the engine in your vehicle, you need to install a compatible starter. We are going to be changing the engine of your tablet, so we need a new starter as well.
Afterota v1.09 has 2 bootloaders. One is just for HC. The other one is for ICS and presumably for JB. Make sure your ROM will use an ICS bootloader. You'll notice the Bootloader ICS options have the same bootloader version but different recovery apps.
Recovery here is and isn't the same thing as in Windows. From the factory, you use the Acer Recovery app to get your A500 back to original factory setup like in Windows. You use one of these Afterota recoveries to install a new operating system (OS). The differences in the Afterota recovery apps is the way they present options. The only one I've used is Twrp v2.1.3. It has a nice GUI. You should have read up on them all and decided for yourself which to use.
Click on the A50x box for the recovery you want and the program will do the install.
Once the program is done it will reread the tablet and generate a new AcerIDs file. Keep the original file, for some reason the second one doesn't get the tablet serial number. Of course, you can keep both. You can close Afterota now.
Install ROM
The next step is to copy your zipped ROM to the Internal storage of the A500 tablet. Do not put it in the SD card. You can also put the gapps zip file here now if you need it.
Disconnect the USB cable and power OFF the tablet.
Press and hold Volume down side of the Volume button (the side closest to the power button) while pressing power on. Wait til you see the booting recovery image message then release the buttons. You are now in the recovery app you chose earlier.
The words and menus may differ between recovery apps but the functions are the same. You will probably have to move between menus. Just take your time and think about what you are doing and you should be fine.
Wipe, Erase or Delete caches and do a Factory Reset. Next, format the system and flexrom.
Now, traverse to where you see the menu option Install Zip from SD (or something to that effect). Choose your ROM and install it. If you put the zipped gapps on the tablet, you can install that as well. If not, you can do that later.
Once successful, boot up normally to your new OS. The first boot takes a very long time. Be patient.
Time for thanks. Thanks to gersma for Afterota. Thanks to all the developers of the booloaders, recoveries and ROMs. Especially thanks for sharing your work.
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for options 3 or 4 it does not matter as much because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Nook" logo screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there are only two working reader apps besides the stock Reader that can handle Adobe DRM protected epubs: Mantano 2.2.3 Premium (activated or not), and Aldiko 2.0
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions. Since the site seems to be down, here is a link for the image zip.
b. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
c. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Eject the device from the USB connection and tap the power button to put it to sleep. If you hang around you may see the device wake up and the update commence. Otherwise come back awhile later. If the update zip is no longer visible on the Nook drive when it is reconnected to your PC via USB then the update has been done.
d. Register your device. Remember you don't need to use a credit card, just an email address.
e. If you wish to root the device select one of the updated versions of NookManager for FW 1.2.2 that are given here.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
4. Try out my unofficial UK FW 1.2.2 update.
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
pkk11 said:
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
Yes, it is possible but there are some special issues surrounding the Glowlight model.
The definitive DIY summary for USB Audio by @Renate NST is buried deep in the original USB Host development thread: https://forum.xda-developers.com/t/wip-usb-host-support-working.1457971/page-19#post-43281985
I recollect that there is a minor path error somewhere in the description, but I will have to search around to find that.
For those who would rather not get their hands quite so dirty (or who don't trust their hands...), there is a CWM-flashable zip prepared by @pinguy1982: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/. This is what I have used since my first initial set up following the DIY directions, although I swapped in a different kernal. More on that later. The advantage (beyond the obvious) is that the zip contains a tweaked set of audio drivers.
Here, too, there were a few minor issues which I corrected in my own copy, although clearly the package works as it was originally posted.
The issue with the Glowlight revolves around the choice of USB Host-enabled kernals. The one referenced by @Renate NST is for FW 1.1.5. It also enables multi-touch and allows you to run NoRefresh display mode if you desire. However, FW 1.1.5 was written when the concept of the Glowlight was just a glimmer in some developer's eye. Consequently it behaves poorly with the Glowlight control, in essence separating the actual light function from the light icon in the status bar. I use this kernal with my Glowlight because I also run my QuickTiles app and it controls both the light and status bar icon, bypassing the system controls. The reason I chose this kernal is because it allows the use of NoRefresh which I feel is superior to FastMode for text reading.
As far as I know all of the other USB Host-enabled kernals are over-clocked kernals that were designed to allow the usage of the FastMode display mode. This is true of the kernal included in the CWM zip created by @pinguy1982. None of these kernals, to my knowledge, will also work with NoRefresh. There is only one kernal that allows you to use both NoRefresh and FastMode (not at the same time, of course) and that is kernal 166--but for some reason this was not the base for adding USB Host to a 1.2.x kernal. Maybe there is an essential incompatibility. It's way beyond my pay grade.
I've meant to look at this more closely and get some definitive information. This will take a few days and involves backing up my device and trying the various kernals. There is one that claims to support the Glowlight function, USB Host, and NoRefresh but I suspect the author of that post was being sloppy in describing the screen refresh mode.
Anyway, that and tracking down the other minor issues I mentioned above will likely take a few days.
Yeah, I didn't have anything to do with the kernel mods on the NST for USB host mode.
There is one patch for audio sample rates on the page for MergeSmali (in sig).
The current UsbMode-2.2.apk supports NST and Glows (although the Glows need the injectd daemon also).
pkk11 said:
A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
OK, so I'm glad you asked this question because it prompted me to look more closely at the kernal issue and I found that there is an appropriate kernal for the Glowlight!
CAUTION: before you do this, use NookManager to make a backup of your device.
For audio playback:
You will need a CWM card to flash the zip. You can make a card from one of the two files at: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. There is a "2 gb" file and one for "128 gb". The card you choose should have at least the capacity mentioned in the file name. Download the file, unzip and burn the image to an SDcard. DO NOT try to install CWM directly onto your device. This will destroy the one fail-safe that makes the NST so hard to kill: the factory image.
Next, download the CWM-flashable USB Audio zip from here: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/
The kernal in this zip is based on 1.2.x so it will work with a Glowlight. It includes multitouch, enables FastMode (with the appropriate app), and USBHost. It is overclocked, so you may want to install some kind of CPU regulator to calm it down. It will not work with the NoRefresh app.
If you would prefer a kernal that is not overclocked and works with NoRefresh (but not FastMode), you can download the zips here: https://forum.xda-developers.com/t/nstg-kernel-multitouch-usb-host-kernel.2846867/#post-54803848. Unzip the files. Open (not unzip) the CWM-flashable USB Audio zip and inspect the contents (WinRAR allows this kind of thing, not sure about other archiving software). In the "boot" folder you will find the two kernal files. Drag the replacement files you downloaded into this folder (within the archive) and set the overwrite to "storage" or "store". You don't want any more compression going on. Then close the archive.
Once you have the CWM-flashable zip set up the way you want it, copy it to the CWM card. Power down the NSTG, insert the CWM card, power up and wait for completion of boot. This is the button function layout for CWM:
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Once you've flashed the zip, you'll need to reboot. If there is a message about possibly losing root, etc., just say no. I've been down that road before.... By attempting to fix a non-existent problem it will create that very problem. So don't let it "fix" nothing.
You need some hardware to make all of these changes actually do something. Also a little software. As far as the hardware, you need an OTG cable (e.g. https://www.ebay.com/itm/Micro-USB-...48?hash=item365c5af32c:g:LmEAAOSwa6heLwTo)and a USB-C audio thingy (e.g. https://www.ebay.com/p/94253551?iid=383621510193 or https://www.ebay.com/itm/Sabrent-Us...259335?hash=item42166fae07:g:v~kAAOSwG5ZekgAB). Both are available on ebay or Amazon and are not expensive. Some audio gizmos include volume control buttons, some don't. I have one of each, but don't use the one with the buttons because it's full of LEDs and the whole USB Host thing drains power anyway, so who needs a bunch of lights?
Some people have had issues with USB Host. I suspect it's because of the OTG cables. The first one I got just did not work. The USB socket on the NSTG is not exactly an industry standard and the cheap OTG cables are not precision instruments. I finally got one that fits well but I have another (right-angle model) which sticks out half-way when fully inserted. It works, but it's worrisome. Also, do not let the cable and audio gizmo dangle. Everything should be on a flat surface. If you put stress on the USB jack and make it unhappy, you're going to have trouble doing something very important: charging. I speak from experience.
Now the software. To activate USB Host (and Audio) you need one or two apps. @Renate NST has a USB Host app as well as an Audio Control app. Both are needed for Audio and are useful if you need to troubleshoot. They can be downloaded from her signature link.
I have found that with a good OTG cable I never have initialization issues with USB Host (on all three devices I own). So I wrote a little one-touch toggle app to turn USB Audio on and off. There are screen prompts to tell you when to connect and disconnect things. Version 4 of the app displays on-screen volume controls as well. You can find that here: https://forum.xda-developers.com/t/app-nst-g-usb-one-touch-toggles.3172213/. The same functionality is also built in to my QuickTiles app, although with nicer screen prompts
If you get this working and are interested in audio recording with the NSTG, there are a few more things to do, but we'll leave that alone for now.
nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
alexhorner said:
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
Click to expand...
Click to collapse
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
nmyshkin said:
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
Click to expand...
Click to collapse
Self host FTW!
alexhorner said:
Self host FTW!
Click to expand...
Click to collapse
yah....my Mediafire account is almost full now with all the NST and Nook Tablet stuff I'm trying to save from oblivion. Hope there's room for this one more.
nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
alexhorner said:
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
Click to expand...
Click to collapse
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
nmyshkin said:
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
Click to expand...
Click to collapse
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
alexhorner said:
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
Click to expand...
Click to collapse
The only way to test the dictionary is to load up an ebook, long-press on a word, select "Look up" and see what happens.
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!