[Q] How to change the default keyboard on rooted NST? - Nook Touch General

I have rooted my nook simple touch. Originally it was meant for reading only, but I write a lot too and writing on a computer screen is very straining as well as intimidating. I installed an app for takig notes on my NST but then I found that the keyboard isn't very nice on the nook. I want to change it. There are several keyboard apps on the market but none of them seem to work. I am not very much aware about the android system, so will someone please help me install a new keyboard? I don't need swype, swiftkey x will do. please help me install swiftkey x or something similar.

you have to move the apk file from /data/app to /system/app. Then use Nook Color Tools to select new keyboard.
I can recommend Hacker's keyboard (on market it is for android 2.2 and later but you can find somewhere on the forum link to a 2.1 version). Only cons is that it is dark but I have asked a developer and he is working on a different look (and hopefully also integrate 2.1 compatibility pach).

if you dont wanna open adb or anything, just do this
you can just install the app using Market
(or)
Download the apk from tto your computer. copy it to your SD card. Insert the SD card into nook and just open the folder in your SD card where you have the .apk and tap on it. then nook will ask for an install prompt and then proceed to install.
Once done enable the keybord from the app itself, or if you open NookColor tools you will have an ption to change the default keyboard

Keyboards
Take a look at TorimuNooter, it has ICSKeyboard included.

Torimu.Joji said:
Take a look at TorimuNooter, it has ICSKeyboard included.
Click to expand...
Click to collapse
Just to add on to this, ICSKeyboard has a working autocorrect/suggestion system.

thanks everyone. I figured it all out myself. I am currently on touchpal and am loving it. thanks for the Co ordination

How did you get Touchpal to work. I installed TouchPal Tablet and the keyboard was all messed up?
What version of Touchpal are you using?

Hello, I'm also looking for a better keyboard (for Spanish, for example).
I've tried many (I like ICSKeyboard), but all they lack the key "Done" (required when adding notes in the stock Reader).
Somebody knows if there is a keyboard that includes it?
TIA,
jugaor

sorry I meant smart keyboard pro. its great and very customizeable. it also has Spanish language for it, and many more.
I think the done key is not dependent on what keyboard you use (its not available on the stock of course), it gets activated only in situations the app needs it to. so if the apparently commands the use of the done key, it will be there. I am not sure if this is correct, but I do get the one key whenever I want on the smart keyboard pro.

I have the same problem with the "Done" key: for example when I want to add a note to my books, I found I can only do that with the stock keyboard which has a permanent "done" button for me to press. Any other keyboard I tried has the normal "enter" key, but no "done"... pressing enter has the effect of a carriage return on the notes (that allow for multiline comments up to 512 char), but I can't save the note.
Anyone found a solution to this?
Thanks anyone!

ICS keyboard for NST
Googie2149 said:
Just to add on to this, ICSKeyboard has a working autocorrect/suggestion system.
Click to expand...
Click to collapse
Your post is my only hope left in the sea of misery of keyboards without auto-suggestion. I tried to install a couple of ICSKeyboard builds on my 1.2.1 Nook rooted with NootManager, but to no avail. Could you tell me where to find a cab of this ICSKeyboard working on Nook?
The TorimuNooter is not available anywhere anymore. The only image I could find is 06K version; it doesn't have this keyboard.

Clarification on installing a new keyboard: First you will need a browser with root privileges (ES File Explorer worked for me). In the settings menu, choose Root Explorer, then Mount R/W. Both "data" and "system" need to be set to R/W - otherwise I couldn't see the files and folders in data and I couldn't copy things to system/app). Find the keyboard install program (mine (graffiti) was not easy - I had to search for the APK). Copy it to the System/App folder. Run the install from that folder. That made it show up in the Nook Color Tools for me.

There must be a way to force the "Done" key to show in a 3rd party keyboard.. I use Smart keyboard to be able to write to my language (stock has only english) but the only problem is this "done" key not showing, although it show elsewhere..

Related

MT3G + Hero + Console App = no numbers?

I am currently running [PORT] TF3D V3 By Drizzy for 32B on my MT3G.
I have noticed that in any console app, be it ConnectBot, or SU File Manager & Terminal, I am literally unable to enter a number.
When I longpress the "e/3" I get "e3" as output
When I press the "12#" button The VK doesnt switch to number/symbol mode
This isn't a big enough problem for me to try flashing other ROMs and testing, but thought I could put the communal brainpower here on XDA to try and narrow down a solution (unless it's unique to me lol)
Thanks in advance for the help!
you need to use the default android keyboard in these applications. The HTC keyboard does not work correctly. Currently i have not been able to find a resolution to that problem but noticed the same thing. Switch keyboards and works just fine.
TheArtiszan said:
you need to use the default android keyboard in these applications. The HTC keyboard does not work correctly. Currently i have not been able to find a resolution to that problem but noticed the same thing. Switch keyboards and works just fine.
Click to expand...
Click to collapse
Ok, thanks, glad to hear it's not just me going crazy.
The ROM I am currently using does not have the android keyboard. Any idea what APK and ODEX are named that I would need to pull out of a stock cupcake ROM in order to install the default android keyboard?
Well, I found LatinIME.apk in another ROM, but when trying to Install I get this error:
Application not Installed
Android keyboard could not be installed on this phone.
wtf?

[Q] Gingerbread keyboard languagepack

Good morning all!
I've tried to search both on this forum and on google in general, but I'm having trouble finding a good answare to my question.
I recently changed from a SD ROM to Pongsters great NAND build. Had to use DFT, due to problems with the CWM. I'm now on Gingerbread - excellent!
Unfortunately I live in this weird country called Norway and we use an alphabet with three more letters (Æ, Ø and Å). Is there anyway I could get these three letters into my gingerbread keyboard, any language pack?
I found this link by searching, but I'm not sure how to install it. It seems like i need CWM.
My temporary solution was to download a 2.3 modification of the "Scandinavian keyboard". It works, but I'm loosing the famous gingerbread keyboard.
A dictionary would too, almost be overkill, awesome.
All help would be greatly appreciated.
Hi mate, maybe this package can help you:
http://forum.xda-developers.com/showthread.php?t=875202
the above is an add on keyboard, you will need to switch to it through keyboard selection.
Otherwise you can push the content of your CMW zip with adb (i suggest to pull the original files before).
adb remount
(optional, gets the original file from your phone) adb pull /system/app/LatinIME.apk "local Location" (ex. c: or /home/user/desktop)
adb push "replacement APK file location" /system/app/
(optional, gets the original file from your phone) adb pull /system/lib/libjni_latinime.so "HDD Location" (ex. c: or /home/user/desktop)
adb push "replacement lib file location" /system/lib/
then reboot and you will use the new KB.
Cheers.
The keyboard looks nice, but as far as I can see there are no Norwegian (NO) alternate.
Anyhow, the ADB-way seems interesting. Never tried, or even heard, about ADB before, but that's why we have tutorials and forums, right?
Downloading the SDK at this very moment.
bluescan said:
The keyboard looks nice, but as far as I can see there are no Norwegian (NO) alternate.
Anyhow, the ADB-way seems interesting. Never tried, or even heard, about ADB before, but that's why we have tutorials and forums, right?
Downloading the SDK at this very moment.
Click to expand...
Click to collapse
Once you go ADB you won't back.
It's not that difficult, if you have some nerd past it will be very easy, otherwise it's plenty of tutorials, just follow them and you won't do it wrong.
Just a small hint,
with CWM always backup before.
w/out CWM always titanum backup.
Cheers.
Maybe a long shot, but have u tried SwiftKey? It supports the Norwegian language, u can set it to two language packages so it shows suggestions in both languages and no need to switch anymore.
I use it German/English and it is IMO just awesome. In particular after a few days using it it is predicting almost whole sentences by it's own.
Just a suggestion without messing with pushing commands ect. ;-)
Sent from my Nexus One using Tapatalk

[Q] Installing swype?

I'm new to the android ecosystem but I've always been jealous of swype users, is it possible to port this feature to the nook touch?
Just replace apk file of swype with default keyboard using Root Explorer in system/app
I tried installing a keyboard apk file into system/app file by copy and paste with ES file explorer but it said failed. is there a special app or procedure I need to do this with? and where did you get the apk file? I would like a keyboard with directional arrows (for spreadsheets) and numbers for faster input. Thanks
Are you sure system is r/w?
Sent from my GT-I5700 using Tapatalk
roryn3kids using ES file explorer use the following instructions and you'll have access to r/w root files:
1. Scroll down to Root Settings and enable Root Explorer and Mount File System.
Not sure if this next step was needed but I did it anyway
2. Once again from the setting menu click on File Settings and enable "Show Hidden Files"
then copy the file from your data\app folder to your system\app folder
Swype "friendliness" to nook STR
The instructions above worked fine for me.
The problem is that I found the apk somewhere (a rather new version but still not the latest) and, even when it works, I do not get any "word list menu" like the one shown in those Swype Howto videos.
This means that, either I use an extremely short vocabulary, or I waste 50% of the time correcting the suggested word...
For instance, let's say I wanted to write f***, Swype forces me to accept the word duck.
This is good, because then I have the time to think twice before swearing but in the end... hum, let's say it's not that productive.
Of course, I checked that the options are properly configured (or I think so)
Does it happen to any of you, nook STR users?
BTW, I might also say that I cannot install the beta from swype.com/category/get-swype/
Have any of you succeeded on this?
Not that I want to re-activate a Post that was last updated in August, but it's nice to have as much information regarding swype as possible in a single post.
Thanks
I just discovered the Swype feature on my galaxy player 4.0 and it's great!
Never used Swype before this, But Since finding it a few days ago, it's all I've used! lol
Hope you get it installed, cuz its awesome.
Ok, I have further investigated the Issue and I can confirm now that it is properly configured (I compared it with some other devices) so let's ask it the other way around...
Is there any nook-STR-user who properly installed Swype?
How did you do it or, better said, where did you get your swype from?
Thanks very much, and a happy new year!
(sent using my not-that-effective-but-still-funny-to-play-with swype keyboard )
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
2. As mentioned over here, the word prediction/suggestion is not visible so really, there is the small nuisance when you have to correct few words. keep an eye on it, when writing.
3. You might find a little bit frustrating the highlighting of a pressed button. Well, OK ... the truth is, that it's TOTALLY ANNOYING !!! Have a look on my video on youtube so you know, what I'm talking about :
youtube.com/watch?v=OYKjvqhxJmU&context=C3503defADOEgsToPDskIus5a7mP57B922B9wWU5cP
But, this can be fixed !!!
youtube.com/watch?v=S3vwQSvjUYM&context=C34142eeADOEgsToPDskJDd6sKkvt8EqkgO74yVfe7
Big THANK YOU goes to "djdarkknight96". His solution is to make the "highlighting" transparent, so it doesn't bother you any more. There was an attempt to make the trace line transparent as well, but without success (FC). Please, have a look at his thread for more info.
P.S. : With the youtube links -> as a new member outside links are not allowed for me yet -> so please add "www"
zholy said:
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
Click to expand...
Click to collapse
My findings with this are that the swype keyboard is actually still there, so you need to use adb to delete the apk file and, if you replaced the original, find that one and use adb to add it.

[Q] azerty keybaord

Hi all, have just update my milestone to the cm71-111105.0200-NIGHTLY-Milestone2-ICS-v1.0 version
All so far seems Ok, wife, phone, mails etc I have changed the settings to french as I live in France, the onscreen keyboard works fine BUT the physical keyboard is still typing in qwerty rather than azerty
so any help would be nice
thanks
Use ES File explorer for instance and grant root privilegies - since you need to use it on root FS and follow this post http://forum.xda-developers.com/showpost.php?p=19108106&postcount=1889
tl;dr: in /system/scriptbox is keypad switching script
Thanks for the info, downloaded the es explorer and managed to grant it root access, but cant 'see' the local files I only can see whats on the SD card or Lan for instance what have I missed ?
You have to grant root access in the settings of ES file manager and then you have to change home directory in the settings of ES from "/sdcard/" to "/" and then you'll see root directory of your phone. Then simply go to /system/scriptbox and there should be it. (I have older version of CM, so I can change my layout in the settings menu and so I don't have scriptbox folder).
I changed to file manager and gave it root access, its clearer to use use than ES, I can get into the /system file but the there is no no /scriptbox in it
Since my firstpost I changed to cm7-111108-2350-NIGHTLY-Milestone2.zip
so maybe thats why
minty95 said:
I changed to file manager and gave it root access, its clearer to use use than ES, I can get into the /system file but the there is no no /scriptbox in it
Since my firstpost I changed to cm7-111108-2350-NIGHTLY-Milestone2.zip
so maybe thats why
Click to expand...
Click to collapse
Checkout the new version, there's azerty keyboard as well (cyanogenmod settings -> input -> keyboard char map)
Hi
thats is just great, installed cm7-111111-2028-NIGHTLY-Milestone2, switched to English to find the input section, changed it to AZERTY and then switched back to French. For info you need to reboot for the keyboard changes to be taken into account, many thnaks for this
Now I still have the problem of loosing the 'reseau', (I get the message no service available) then after awhile it commes back, in another post someone says that I may need to change the baseband, but am a little lost on this problem
minty95: If you're using CM7 from Endless7, then it is really easy. There should be application named Milestone 2 Toolbox.. In this app, there is option "Baseband Switching Tools", which installs english baseband switcher. Then just use second option (Europe 2.2.2) and it should work ok. (you could also try first option, if you have problem with second option)
And you can also see actual baseband in this app.
Thanks I'm not using this rom but this one http://forum.xda-developers.com/showthread.php?t=1338183
I'm downloading the one from Endless7 and will flash and try it, to see as in the one I'm running I doesn't have the milestone toolkit, but does have a Azerty keyboard, so I wuill test it and get back
I think, it should be possible to extract milestone toolkit apk from endless7's CM7... Also, you can download it separately from his topic http://forum.xda-developers.com/showthread.php?t=1239778 - in the first post, there is attachment named "ToolBox+Baseband+others.rar" - this is what you need - there is milestone 2 toolkit apk, which you can simply install to any rom
I downloaded the Endless7 rom and installed it
The program for the baseband is all in chinese (I had already found and installed it on the other ROM) but as it's all in chinese I have no idea what to choose
Have already switched back to the other ROM, shown in my last post as it gives me the possibilty to change the keyboard to azerty and which Endless7 does not
So I'm just stuck with this baseband program in chinese
I have Endless7's ROM and I don't have it in chinese, I have english version.
In the attachment of this message I included screenshot of my version, apk of my baseband switcher and apk of my Milestone2ToolBox (which gave me this baseband version)...
Hope it helps somehow.
I think that you just saved my life
Have installed your download and it is in English, phew, testing now,
many thanks
Update : After a afternoon of using the first option (2.2) on the basedband APK 1.5.4 and having had no loss what so ever, am now trying the second option europe 2.2.2
I know have a phone that is at least twice as fast as last week
again many thanks

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

Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for options 3 or 4 it does not matter as much because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Nook" logo screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there are only two working reader apps besides the stock Reader that can handle Adobe DRM protected epubs: Mantano 2.2.3 Premium (activated or not), and Aldiko 2.0
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions. Since the site seems to be down, here is a link for the image zip.
b. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
c. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Eject the device from the USB connection and tap the power button to put it to sleep. If you hang around you may see the device wake up and the update commence. Otherwise come back awhile later. If the update zip is no longer visible on the Nook drive when it is reconnected to your PC via USB then the update has been done.
d. Register your device. Remember you don't need to use a credit card, just an email address.
e. If you wish to root the device select one of the updated versions of NookManager for FW 1.2.2 that are given here.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
4. Try out my unofficial UK FW 1.2.2 update.
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
pkk11 said:
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
Yes, it is possible but there are some special issues surrounding the Glowlight model.
The definitive DIY summary for USB Audio by @Renate NST is buried deep in the original USB Host development thread: https://forum.xda-developers.com/t/wip-usb-host-support-working.1457971/page-19#post-43281985
I recollect that there is a minor path error somewhere in the description, but I will have to search around to find that.
For those who would rather not get their hands quite so dirty (or who don't trust their hands...), there is a CWM-flashable zip prepared by @pinguy1982: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/. This is what I have used since my first initial set up following the DIY directions, although I swapped in a different kernal. More on that later. The advantage (beyond the obvious) is that the zip contains a tweaked set of audio drivers.
Here, too, there were a few minor issues which I corrected in my own copy, although clearly the package works as it was originally posted.
The issue with the Glowlight revolves around the choice of USB Host-enabled kernals. The one referenced by @Renate NST is for FW 1.1.5. It also enables multi-touch and allows you to run NoRefresh display mode if you desire. However, FW 1.1.5 was written when the concept of the Glowlight was just a glimmer in some developer's eye. Consequently it behaves poorly with the Glowlight control, in essence separating the actual light function from the light icon in the status bar. I use this kernal with my Glowlight because I also run my QuickTiles app and it controls both the light and status bar icon, bypassing the system controls. The reason I chose this kernal is because it allows the use of NoRefresh which I feel is superior to FastMode for text reading.
As far as I know all of the other USB Host-enabled kernals are over-clocked kernals that were designed to allow the usage of the FastMode display mode. This is true of the kernal included in the CWM zip created by @pinguy1982. None of these kernals, to my knowledge, will also work with NoRefresh. There is only one kernal that allows you to use both NoRefresh and FastMode (not at the same time, of course) and that is kernal 166--but for some reason this was not the base for adding USB Host to a 1.2.x kernal. Maybe there is an essential incompatibility. It's way beyond my pay grade.
I've meant to look at this more closely and get some definitive information. This will take a few days and involves backing up my device and trying the various kernals. There is one that claims to support the Glowlight function, USB Host, and NoRefresh but I suspect the author of that post was being sloppy in describing the screen refresh mode.
Anyway, that and tracking down the other minor issues I mentioned above will likely take a few days.
Yeah, I didn't have anything to do with the kernel mods on the NST for USB host mode.
There is one patch for audio sample rates on the page for MergeSmali (in sig).
The current UsbMode-2.2.apk supports NST and Glows (although the Glows need the injectd daemon also).
pkk11 said:
A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
OK, so I'm glad you asked this question because it prompted me to look more closely at the kernal issue and I found that there is an appropriate kernal for the Glowlight!
CAUTION: before you do this, use NookManager to make a backup of your device.
For audio playback:
You will need a CWM card to flash the zip. You can make a card from one of the two files at: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. There is a "2 gb" file and one for "128 gb". The card you choose should have at least the capacity mentioned in the file name. Download the file, unzip and burn the image to an SDcard. DO NOT try to install CWM directly onto your device. This will destroy the one fail-safe that makes the NST so hard to kill: the factory image.
Next, download the CWM-flashable USB Audio zip from here: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/
The kernal in this zip is based on 1.2.x so it will work with a Glowlight. It includes multitouch, enables FastMode (with the appropriate app), and USBHost. It is overclocked, so you may want to install some kind of CPU regulator to calm it down. It will not work with the NoRefresh app.
If you would prefer a kernal that is not overclocked and works with NoRefresh (but not FastMode), you can download the zips here: https://forum.xda-developers.com/t/nstg-kernel-multitouch-usb-host-kernel.2846867/#post-54803848. Unzip the files. Open (not unzip) the CWM-flashable USB Audio zip and inspect the contents (WinRAR allows this kind of thing, not sure about other archiving software). In the "boot" folder you will find the two kernal files. Drag the replacement files you downloaded into this folder (within the archive) and set the overwrite to "storage" or "store". You don't want any more compression going on. Then close the archive.
Once you have the CWM-flashable zip set up the way you want it, copy it to the CWM card. Power down the NSTG, insert the CWM card, power up and wait for completion of boot. This is the button function layout for CWM:
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Once you've flashed the zip, you'll need to reboot. If there is a message about possibly losing root, etc., just say no. I've been down that road before.... By attempting to fix a non-existent problem it will create that very problem. So don't let it "fix" nothing.
You need some hardware to make all of these changes actually do something. Also a little software. As far as the hardware, you need an OTG cable (e.g. https://www.ebay.com/itm/Micro-USB-...48?hash=item365c5af32c:g:LmEAAOSwa6heLwTo)and a USB-C audio thingy (e.g. https://www.ebay.com/p/94253551?iid=383621510193 or https://www.ebay.com/itm/Sabrent-Us...259335?hash=item42166fae07:g:v~kAAOSwG5ZekgAB). Both are available on ebay or Amazon and are not expensive. Some audio gizmos include volume control buttons, some don't. I have one of each, but don't use the one with the buttons because it's full of LEDs and the whole USB Host thing drains power anyway, so who needs a bunch of lights?
Some people have had issues with USB Host. I suspect it's because of the OTG cables. The first one I got just did not work. The USB socket on the NSTG is not exactly an industry standard and the cheap OTG cables are not precision instruments. I finally got one that fits well but I have another (right-angle model) which sticks out half-way when fully inserted. It works, but it's worrisome. Also, do not let the cable and audio gizmo dangle. Everything should be on a flat surface. If you put stress on the USB jack and make it unhappy, you're going to have trouble doing something very important: charging. I speak from experience.
Now the software. To activate USB Host (and Audio) you need one or two apps. @Renate NST has a USB Host app as well as an Audio Control app. Both are needed for Audio and are useful if you need to troubleshoot. They can be downloaded from her signature link.
I have found that with a good OTG cable I never have initialization issues with USB Host (on all three devices I own). So I wrote a little one-touch toggle app to turn USB Audio on and off. There are screen prompts to tell you when to connect and disconnect things. Version 4 of the app displays on-screen volume controls as well. You can find that here: https://forum.xda-developers.com/t/app-nst-g-usb-one-touch-toggles.3172213/. The same functionality is also built in to my QuickTiles app, although with nicer screen prompts
If you get this working and are interested in audio recording with the NSTG, there are a few more things to do, but we'll leave that alone for now.
nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
alexhorner said:
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
Click to expand...
Click to collapse
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
nmyshkin said:
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
Click to expand...
Click to collapse
Self host FTW!
alexhorner said:
Self host FTW!
Click to expand...
Click to collapse
yah....my Mediafire account is almost full now with all the NST and Nook Tablet stuff I'm trying to save from oblivion. Hope there's room for this one more.
nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
alexhorner said:
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
Click to expand...
Click to collapse
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
nmyshkin said:
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
Click to expand...
Click to collapse
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
alexhorner said:
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
Click to expand...
Click to collapse
The only way to test the dictionary is to load up an ebook, long-press on a word, select "Look up" and see what happens.

Resources