Hi to all.
I just got my NST with firmware 1.1, and I wanted to root it, so I followed this guide:
[N2E][1.1] TouchNooter 2.1.31
http://forum.xda-developers.com/showthread.php?t=1343143
Now I have got exactly same problem posted there by "tappet" as the following:
I bought a brand-new Nook Simple Touch from my local B&N store, and I wanted to root it, but for some reason I can't get it to work.
Here's what I've done:
1. Downloaded TouchNooter 2.1.31
2. Written the disk image to a 16G micro SD card, per instructions.
3. Registered my NST.
4. Powered off the NST.
5. Inserted the SD card.
6. Powered on the NST. At this point, I get the TouchNooter instructions screen, but it never flashes black, even after several hours. so...
7. I pulled the SD card and rebooted, at which point I got the regular Nook "Read Forever" screen, and the device hangs again, even after several hours of waiting.
8. I forced a factory reset through the "8 failed reboots method," and the device resets, and eventually boots back to the stock configuration.
9. I have been through the process twice, once with firmware version 1.1.0, and once with version 1.1.2.
Is there some obvious step that I'm missing? Or alternatively, any advice on how to get this thing rooted?
Click to expand...
Click to collapse
However, I am on point# 7 above and my nook is now frozen on "Read Forever" and I don't know what is the "8 failed reboot method" and how to do it.
As I'm new here and I cannot post on the above thread. I hope I can find the solution here pls.
Waiting for your help.
thanks
UPDATE
I got it fixed now after using first image by "ros87" on his thread
n2T-Recovery - Nook Simple Touch - Factory Restore / Recovery [v:0.2 17.11.11]
Thank you ros87, for the great guide.
I then used again TouchNooter 2.1.31, and got same result with freezing on "Read Forever", but this time when I takeout the SD card and reboot the device, I was surprised that IT WORKS and showed the little Android guy, it was rooted ok I guess. Youtube is working, gmail is sync. and market is now working but I think it needs 24h to work as I read on the rooting guide.
I need now to add Arabic support, if anyone can please help.
thanks
Hey
I'm getting my Nook next month, but already trying to get ahead...
I was looking for Hebrew support (same as Arabic) and bookmarked this Thread:
http://forum.xda-developers.com/showthread.php?t=1611549
hope it helps
thanks for the reply.
I followed that post, and get the Arabic working, but not in the stock reader. I have Arabic working fine in Moon+ reader, the version with RTL feature.
In the Original Nook reader, the book titles are shown fine in Arabic, but the pages are shown Left to right instead of RTL. Same problem exists in all other readers I tried like Nomand reader, cool and Aldiko, they all showed books in LTR instead of RTL.
Any idea to help, mainly I need stock (Nook) reader to read from RTL.
thanks
Have you read up on using Calibre and/or Sigil to fiddle with the contents of epub files? There may be a setting you need to get into and explicitly set?
I'm very interested that one reader does work - is that reader one where, once you have a title open, you go to a menu and explicitly tell it "display RTL" or did it automatically show your file in RTL?
If it's the former, then you may well want to see if there's a CSS command that says "go RTL for this file," as the stock reader might understand the CSS even without having a menu command that does it.
roustabout said:
Have you read up on using Calibre and/or Sigil to fiddle with the contents of epub files? There may be a setting you need to get into and explicitly set?
I'm very interested that one reader does work - is that reader one where, once you have a title open, you go to a menu and explicitly tell it "display RTL" or did it automatically show your file in RTL?
If it's the former, then you may well want to see if there's a CSS command that says "go RTL for this file," as the stock reader might understand the CSS even without having a menu command that does it.
Click to expand...
Click to collapse
I didn't try Calibre or Sigil, my epub files are downloaded from some free Arabic library sites. I will download those softwares and try later.
Yes the Moon+ reader (RTL version) automatically opens the Arabic books in the correct RTL alignment.
So, there is a moon+ which defaults to right to left, is that what you mean by "RTL version?"
If so, I would search for other resoluions to this using sigil or calibre; I think some of the best epub formatting tips I found were on the mobiread or mobipocket forums. (That was how I learned to fix epubs which were locked into using black fonts no matter what - even in night mode, some badly formatted epubs keep using black as their font color!)
According to a CSS guide, you can specify RTL, overriding the default LTR, using this code or a variant:
div
{
direction:rtl;
}
http://www.w3schools.com/cssref/pr_text_direction.asp
Many but not all epubs, when examined with Sigil, do have a folder called styles which contain a css style sheet.
Where, exactly, you would put that snippet of code I don't know. I know my first try with it didn't work out well
Related
I just started a wiki here
USB Host mode
I am hoping that you who actually know how to do it would help develop a set of instructions that are simple enough for a literate, adventurous non-tech (like me) to follow.
UPDATE: The wiki now has a complete list of installation instructions. You'll have to hunt through verygreen's thread below for operating instructions till they organized on the wiki.
The wiki and this thread (where noobs like me can post) are based on verygreen's
[WIP] USB Host support (working)
I asked verygreen and ros87 to do the USB Host mode for the Nook Simple Touch. Verygreen announced success within 48 hours. The hack has gotten whipped into shape there with the amazing help of ros87, Renate NST, mali100, and other superb xda people.
The project started at mobileread.com:
Project: E-Paper Tablet (touch-typable!)
Thanks to fellow mobilereaders for support, especially Kumabjorn, poliorcetes, and nealsharmon for donating money for devices.
The wiki is super rough. It assumes a new device in the box and a non-tech user. I started the instructions to show how simple they need to be. I will continue helping with that because it does seem difficult for techs to believe just how lost we can be with this stuff. My goal is to bridge the gap between techs and literate users so that non-programmers who want to type on the NST can. If you are an expert writer of users manuals, maybe you would help, too.
Honestly, I don't know the first thing to do now that my NST is on and registered. For example, I don't even know if I need to:
root the NST first
install adb (which I also don't know about)
or what. I have studied the thread, so I will be familiar with the terms. But I'm completely clueless about actually doing the hack. I managed to unbox my refurbished NST, update its software to 1.1.2 and install a microSD card. The issue is, what exactly should be done now? Please leave your answers in the wiki! Thank you!
I would say the best way to start is from eded333's Minimal Touch http://forum.xda-developers.com/showthread.php?t=1346748 . That gives you a nice system with market and a launcher to install and start your texteditor or writing apps.
If I find some time i will create a small update-package that installs all the necessary things for the usb-host mode.
Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.
andrewed said:
Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.
Click to expand...
Click to collapse
1.1.2 is fine. You can still use eded333's MinimalTouch to root it and get a launcher.
Awesome. Will dive in, then!
As promised I created a small update package, to install all the necessary files and tools.
It is installable via Clockwork Recovery in the same way as eded333's MinimalTouch, which should be installed first, to get root, a launcher and a working Market.
Requirements:
Software version 1.1 or 1.1.2 (1.1.2 is recommended, as it fixes WLAN issues)
root, a launcher and working market (I recommend using eded333's MinimalTouch)
What it does:
changes the kernel to NST-kernel v0.1 with USB-Host and multitouch support
changes the uRamdisk to a uRamdisk with fixed init (needed for USB Input devices) and adb-usb
installs the busybox and sqlite binaries
adds the permission node for multitouch to /etc/permissions/required_hardware.xml
installs the app UsbMode-1.2 and the NullKbd-1.1 by Renate NST
adds the permission to enable the NullKbd
changes the qwerty.kl and qwerty.kcm.bin to the remapped one by Renate NST
installs the NookColorTools, so you can switch to the NullKbd
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher.
this is the first release and only tested by myself, so don't expect it to be bulletproof.
Credits go to:
verygreen, ros87 and everybody who helped with the USB-Host mode,
Renate NST, for all the effort making USB-Host support userfriendly (USB-Mode app, NullKbd, key remapping, testing),
wheilitjohnny and arkusuma for the Multitouch support,
eded333, for his great MinimalTouch,
Download:
usb-host-mt-pack_0.1.zip
Thanks, mali100.
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.
Renate NST said:
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.
Click to expand...
Click to collapse
Nice easter-egg didn't noticed this before. Thanks
Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.
andrewed said:
Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.
Click to expand...
Click to collapse
I'm using a 4G class 2 micro SD card for NOOGIE and it's fine.
where to?
Hi where to put content of META-INF? (dont wanna root again...)
mrWax said:
Hi where to put content of META-INF?
Click to expand...
Click to collapse
The META-INF folder contains the insallation script and the interpreter for the script, they are used by CWM to install the package and not copied to the nook.
(dont wanna root again...)
Click to expand...
Click to collapse
If you mean that your device isn't rooted, and you don't want to, then I have to tell you that root is needed to switch between usb-host mode and peripheral-mode, so root is mandatory.
If you mean your device is already rooted and you don't want to redo it, then don't worry, this package doesn't contain files that root the nook.
I had already rooted my nook another way...now what?
Friends,
I rooted my Nook using the instructions here (SalsichaNooter):
http://www.youtube.com/watch?v=O05Y7C9a4eU
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions. I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
I really would like to get a keyboard working on my Nook and feel like I'm so close.
nealsharmon said:
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions.
Click to expand...
Click to collapse
You don't have to revert anything, a device rooted with salsichanooter works fine.
I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Click to expand...
Click to collapse
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
Click to expand...
Click to collapse
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.
thank you
Thanks for your input. I will try the process you suggested.
It worked!
mali100 said:
You don't have to revert anything, a device rooted with salsichanooter works fine.
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.
Click to expand...
Click to collapse
I followed your instructions and it worked. Thank you very much.
Still Not working
I'm very new at this.
I have followed the above directions and patched with usb-host-mt-pack_0.1 successfully but my two USB keyboards are still not working.
I originally rooted my nook using TouchNooter 2.1.31.
I am using an OTG cable and am getting the solid green light after turning off current and selecting Host.
When i plug either keyboard (or bluetooth dongle for that matter) State changes from a_idle to a_host.
Other results:
Keyboard: none
all fields below that are blank.
Any suggestions on how i should proceed? Could this just be a matter of the keyboards not being compatible? What are the recommended keyboards?
Many thanks!
When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.
Renate NST said:
When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.
Click to expand...
Click to collapse
Thank you, Renate. That worked great. My Bluetooth is working and I'm using my apple wireless keyboard to word process. My arrow keys don't work so I have to do some touching or backspacing to edit in google documents.
I have a chronic case of CVS (eye condition). This is really gonna help me. Do you recommend a stand with space at the bottom for the cord?
Thank you so much!
Stand? I love mine. http://forum.xda-developers.com/showthread.php?t=1661902
You can use either a desk stand or the little bendy tripod.
The arrow keys should work, but they get rotated when in landscape mode.
There is a mod to make them not rotate.
http://forum.xda-developers.com/showthread.php?p=30260821&highlight=keyinputqueue#post30260821
Hey guys,
Just got my new Nook Yesterday, and I need a working guide on rooting it.
I was following the TouchNooter thread, but it doesn't work. I think it has some thing to do with the fact that I have the new 1.1.2 fw installed.
I got to the part when I need to boot the nook, but when it does boot it says that the SD card is not formatted and offers to format it.
Please help.
TN works fine with B&N 1.1.2 firmware. I've done it twice in recent weeks.
Try rebooting without the uSD card inserted. It should take you into ADW launcher. Be aware that it can take 24 hours for the Market to function.
bobstro said:
TN works fine with B&N 1.1.2 firmware. I've done it twice in recent weeks.
Try rebooting without the uSD card inserted. It should take you into ADW launcher. Be aware that it can take 24 hours for the Market to function.
Click to expand...
Click to collapse
Can you please explain the part about rebooting without the SD card?
What's the ADW launcher?
At step 9, take the card out and follow the rest of the procedure. As you do the procedure, on-screen instructions tell you to remove the card when the screen goes dark.
bobstro said:
At step 9, take the card out and follow the rest of the procedure. As you do the procedure, on-screen instructions tell you to remove the card when the screen goes dark.
Click to expand...
Click to collapse
Thanks !
I think I got it! It was my mistake in the dd syntax.
Do you know how I can add fonts to the reader?
Ah, you got the format uSD message on the FIRST boot, before the rooting process then? Glad you got it fixed.
I am not aware of any way to add fonts to the B&N reader, if that's what you mean.
ObiWan_C said:
Do you know how I can add fonts to the reader?
Click to expand...
Click to collapse
Fonts go in the /system/fonts directory. Just copy them.
The reader selects out of six fonts.
Unless you hack the app to use a ListView, you will be limited to six fonts.
You can easily replace one of the selections by modifying Reader.apk
If you pick a font with a short name you can just binary hack replacement of the string name in resources.arsc.
If you want full freedom of choice, you have to extract and recompile the string resources.
The strings are named (note misspelling):
font_1_lable Caecilia
font_2_lable Malabar
font_3_lable Amasis
font_4_lable Gill Sans
font_5_lable Helvetica Neue
font_6_lable Trebuchet
Hello, I am sorry that I write here but no 10 posts to write in development section.
I see threats in the forum bought nook from asda. Yesterday tried to install touchnooter-2-1-31.zip. I prepared the sd card. Put in the nook and restart. It started and I waited the screen to become black, remove the card and restart.... Then it freeze on "Your NOOK is starting up..." I waited about 20 min, but nothing happend. Then I installed firm 1.2.1 UK from http://forum.xda-developers.com/showpost.php?p=41296148&postcount=2 and then again try to install touchnooter-2-1-31.zip and the result was the same froze. Then made a factory reset via NookManager and again try touchnooter 2 1 31. After that I tried older version of touchnooter-2-1-26 but absolutely the same.
All i need is to run some app that support PDF.I have scanned textbooks scanned as puctures. I want to read them in landscape and I need to zoom in may be with 2 fingers (multitouch)
PS I restore default settings and root it with Nook Manager. Then install Alkido and it support lanscape reading, but no zoom. I tried to install different kernels with no success.
Sorry for may English. I hope you understand me
Thank you
garvanat said:
Hello, I am sorry that I write here but no 10 posts to write in development section.
I see threats in the forum bought nook from asda. Yesterday tried to install touchnooter-2-1-31.zip. I prepared the sd card. Put in the nook and restart. It started and I waited the screen to become black, remove the card and restart.... Then it freeze on "Your NOOK is starting up..." I waited about 20 min, but nothing happend. Then I installed firm 1.2.1 UK from http://forum.xda-developers.com/showpost.php?p=41296148&postcount=2 and then again try to install touchnooter-2-1-31.zip and the result was the same froze. Then made a factory reset via NookManager and again try touchnooter 2 1 31. After that I tried older version of touchnooter-2-1-26 but absolutely the same.
All i need is to run some app that support PDF.I have scanned textbooks scanned as puctures. I want to read them in landscape and I need to zoom in may be with 2 fingers (multitouch)
PS I restore default settings and root it with Nook Manager. Then install Alkido and it support lanscape reading, but no zoom. I tried to install different kernels with no success.
Sorry for may English. I hope you understand me
Thank you
Click to expand...
Click to collapse
I'm sorry I don't have any help for you, but my Nook is freezing up in the same way because of the same thing. I tried to install TouchNooter while my Nook was on 1.2.1 and it is still frozen on the "Your NOOK is starting up..." (it's been hours). How did you factory reset using NookManager?
Your help would be greatly appreciated
Thank you
I found the problem.
1) If you have 1.2.1 use => Nook Manager
2) If you have 1.1.0 use => touchnooter-2-1-31.zip
I downgrade firm to 1.1.0 and use touchnooter, then flash new kernel for multitouch and fastmode. Now everything is OK
garvanat said:
I found the problem.
1) If you have 1.2.1 use => Nook Manager
2) If you have 1.1.0 use => touchnooter-2-1-31.zip
I downgrade firm to 1.1.0 and use touchnooter, then flash new kernel for multitouch and fastmode. Now everything is OK
Click to expand...
Click to collapse
Ok, how did you use NookManager? Did you just "burn" the .img file onto the SD card and reboot the NOOK? I've done that and it doesn't recognize the NookManager SD card and just freezes on Your NOOK is starting up...
Use this program http://forum.xda-developers.com/attachment.php?attachmentid=2084266&stc=1&d=1372709166 choose the *.img file and click write. Use CARD READER not NOOK!
garvanat said:
Use this program http://forum.xda-developers.com/attachment.php?attachmentid=2084266&stc=1&d=1372709166 choose the *.img file and click write. Use CARD READER not NOOK!
Click to expand...
Click to collapse
Ok, yes that is how I put the .img file onto the SD card (through the card reader). Now I put the card in, and shut down the nook and restart it, and it will boot into the Nook Manager?
Thanks again
EDIT: I've fixed my problem. Again, thanks for your helpful replies.
Hello all ...
Please .. I need some advice..
This is my first post. My sister has given me her Nook Simple Touch Glowlight. I would like to root it, as I've been looking for a device to keep notes and stuff on. I went as far as booting up with noogie.img and backing up the firmware. I don't know what to do, because I read that having a certain firmware changes everything? I don't think my sister updated the nook. Here is the information from the Settings / Device Info / About Your Nook.
Software Version: 1. 1. 5
Model Number: BNRV350
I read someplace that the sizes of the firmwares are different. The simple touch is 1. 82 and the simple touch glow is 1. 86.
Mine is 1 .82, but yet it has the glowlight? It says to hold the button down for two seconds to turn it on.
I see that B&N have new firmware for the nst & nstg. 1. 3 I believe. It said on the site that this firmware would be installed when the nook is idle. (via wifi) Anyway, I'm wondering if it would be ok to go ahead and root the thing, or upgrade the firmware first to maybe - 1. 2 (if I can find it?) before I do anything else? Oh and should I stay away from B&N's new 1. 3 firmware?
Thank You Very Much !!
WillyS.......
If you indeed have the Nook Simple Touch with Glowlight (black bezel), then the most recent stock firmware is 1.2.1 which can be downloaded here. I would recommend that you update to this as the first thing you do. Next you need to decide which of the multitude of rooting methods is best for you. You need to take into account what you wish to achieve by rooting the Nook and your skill/comfort level with the processes. I have followed many of the different processes, doing a factory reset between root versions. By far the easiest is Nook Manager. I, personally, prefer the Minimal rooting - back to basics method because it allows you to install just what YOU want. However, this method requires a fair amount of command line work.
EDIT: I made the assumption that you are in the US and have a US model. I believe there is a different firmware number for the international model. In any case, you should update the Nook to the most recent firmware before rooting.
Rooting nook .. Glowlight ..
Hello David and Thank You kindly for the reply!
Yes, mine is a Canadian version and it has the black bezel.
Thank you .. for correcting me on the firmware. I was looking at the wrong Nook version. (nook.barnesandnoble.com/u/software-updates-nook-glowlight/379004086)
I downloaded the correct 1. 2. firmware for the nook and I (like you) would rather install what I want to and have more control over what gets put on it. After I update the firmware, I'll come back and follow the links you provided. If you know what threads have the latest / newest info on rooting the nstg, can you please point me to it? (If you haven't already) Thank You Very Much for your help .. David.
Cheers
WS
You're welcome. If you are comfortable with a lot of manual, command line manipulation, start with the Minimal rooting - back to basics thread. There are many more and newer rooting methods, but each of them installs a bunch of apps that the creators use, which may or may not be of importance to you. If you start with the Minimal rooting - back to basics, you can then pick and choose the apps and modifications you want to apply to give you the best experience for YOUR needs. I am attaching the document I use to keep track of what I have done for your reference. Feel free to post any questions here.
Rooting Nook STG .. Firmware 1. 2 ...
Hi David and Thank You for the reference document.
Last night I downloaded 1.2.1 firmware and dumped it on the Nook. When I got up this morning I checked and 1.2 is installed. I looked around and found a 16gb Kingston (from GPS) SD-Card. It is only class 4, but it should be usable for the time being. I'll take a look online for a class 10. I don't know if there is any size, or class limitations, or not?
I'm at the rooting - back to basics thread. I'm going to read all this stuff over and see if I can figure it all out. Thanks again for your help and the document.
WS...
WillySizard said:
...
Last night I downloaded 1.2.1 firmware and dumped it on the Nook. When I got up this morning I checked and 1.2 is installed. I looked around and found a 16gb Kingston (from GPS) SD-Card. It is only class 4, but it should be usable for the time being. I'll take a look online for a class 10. I don't know if there is any size, or class limitations, or not?
...
Click to expand...
Click to collapse
Class 4 should work just fine. Since noogie only takes ~2GB (if I remember correctly) you don't really need a card any larger than 4GB to use this method of rooting. Having 8GB or 16GB card would be useful if down the road you will make use of the card to backup your Nook ROM & user-content for ease in recovery.
Don't really know where to go from here, or what to do ..
@ digixmax .. Thank You for the info on the SD-card. Good to know info!
@ david0226 .. I went to the page about rooting via the link and I have basic
understanding how / what needs to be done, but I'm not having much
luck finding and using the tools. I went and looked for the file used to
extract the 2 files from uRamdisk, but I couldn't find it. I did some reading
and looking around and found a program called Preboot (I think) by
Intel and it contained bootutil 32/64 and so on. I had to install preboot & then
uninstall it, to get bootutil and then install it. I tried using it to extract
the files, but I kept getting failed messages. Like invalid switch /x.
Invalid switch /v. Invalid file uRamdisk. I know I need to extract out 2
files: init.rc and default.prop. I tried to do so in the "Administrative Command
Window" on Win7_64bit, but it just wouldn't work with bootutil. Not the
one I had anyway. Any ideas? Thanks!
WillyS......
David0226 said:
...
I am attaching the document I use to keep track of what I have done for your reference. Feel free to post any questions here.
Click to expand...
Click to collapse
What extensions does "Extended Power Menu" provide?
Also, which uImage and uRamdisk do you use as uRecImg and uRecRAM?
TIA.
Here are the links to the relevant threads.
Extended Power Menu
Clockworkmod based Recovery post #75, see the entire thread here.
If you are going to do the Extended Power Menu, be sure to do the Clockworkmod based Recovery also or you risk wiping out everything you have done by accidentally hitting recovery in the Extended Power Menu. I you have installed Clockworkmod Recovery and accidentally hit "Recovery", it will just boot to Clockworkmod and give you a chance to back out.
@willys. I will have to look up the software I use and post tomorrow. Sorry I missed your question earlier.
@willys, I believe the program you want is "bootutil" which was written and shared by Renate NST. If you find a post by her and click on the yellow box in her signature, you will find links to the many custom programs she has written for rooting and managing rooted Nook Simple Touch devices.
David0226 said:
@willys, I believe the program you want is "bootutil" which was written and shared by Renate NST. If you find a post by her and click on the yellow box in her signature, you will find links to the many custom programs she has written for rooting and managing rooted Nook Simple Touch devices.
Click to expand...
Click to collapse
Yes, I had to go to her profile and I found it there. I'll do this part first and see how it goes. After that (I think?) I need to get an android program (some kind of Installer maybe?) to do some other work with. Anyway, one step at a time. All for now. Thanks! ... WS.
digixmax said:
Class 4 should work just fine. Since noogie only takes ~2GB (if I remember correctly) you don't really need a card any larger than 4GB to use this method of rooting. Having 8GB or 16GB card would be useful if down the road you will make use of the card to backup your Nook ROM & user-content for ease in recovery.
Click to expand...
Click to collapse
Class 2 and 4 will do just fine, in my case I used 520 Mb microSD card for installing various ROMs, tried quite a lot of them, always worked fine.
Almost done, but need a little more help . . .
Mnurlan said:
Class 2 and 4 will do just fine, in my case I used 520 Mb microSD card for installing various ROMs, tried quite a lot of them, always worked fine.
Click to expand...
Click to collapse
OK .. Thank You Mnurlan!
@David0226 ...
Just getting to the point where I'm ready to add programs. have edited uRamdisk and re-installed the two files. I've download android-sdk package and have installed it. I have been in the nook via wifi using ndb shell as root. I am now following your notes file. I've created the archive folder on the nook - /system/archive and I've been moving files over from /system/apps folder. I got Nook Manager written to the sd-card and I have PackageInstaller.adk from it, but I I'm not sure how I get that onto the nook. When I boot with NookManager, it ask if I want to root. I have already done that and it is working. Should I let it do it anyway?
Thank You!
WillySizard . . . .
@WillySizard ...
Connect to the Nook with adb then exit the adb shell back to your Windows command prompt. Once back at the command prompt, you should be able to install any package using this command ...
adb install {package_name.apk}
Nook Simple Touch Glowlight .. Need advice before rooting ..
David0226 said:
@WillySizard ...
Connect to the Nook with adb then exit the adb shell back to your Windows command prompt. Once back at the command prompt, you should be able to install any package using this command ...
adb install {package_name.apk}
Click to expand...
Click to collapse
Ahhh .. ok. Good enough then. That should get me off and running.
Thank You .. David. Sorry I'm being such a pest.
Me, also
Just paid $5 for a BNRV350 at a rummage sale.
I understand BN disabled the web browser with the current operating system.
I can get a Google search window (by repeated tapping on the "Google" or maybe the "404" or the "that's all" links that appear when I try the "connect to social" settings menu choice for Google. And "find my account" worked when given the Gmail userid (because the keypad on the Nook lacks a period for typing a proper email address, in this view).
And I can get a Twitter login page. Neither works well -- typing even a single letter into the password field resets the page, so it's letter, then tap in the field window, then another letter, then tap in the field window. Sometimes it shows a row of dots for characters already entered, other times those are invisible but the entries are still there.
Just curious to add to the above fellow's thread for anyone searching for this Nook model number, if anyone has advice or suggestions about making it useful.
Reverting to the original OS to have use of the web browser would be a welcome option, if that's possible. Pointers welcome. Right now this Nook has version 1.1.5 installed -- I gather that's one of the improved versions that killed the stock web browser.
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.