[NG2] Rooted & installed ReLaunch. Now what? - Nook Touch General

Hello,
Recently I've bought a new B&N Nook Glowlight (4GB, BNRV500).
All was good and well, until I've figured out that I've a few kindle books (.mobi) and PDF's that I'd love to be able to read them on my brand new NG.
I've done some reading here on XDA, and it seemed like a root has to be achieved (to gain ADB access) to in order to sideload some APKs.
Root operation is a GO.
After reading 40 and something pages out of the 'Hacking the new glowlight' thread, I've decided to use the method described by idefix0815.
TBH, it took me a while. I'm a regular user of Ubuntu, and the older versions of libusb drivers (described in idefix0815 post) gave me a headache.
So, I've tried OpenSUSE distribution as someone has recommended, and after a few versions, I've found a good one (I've tried the 32bit version, 32bit GNOME live usb, 64bit KDE live usb).
I followed the instructions, and things were alright. Until I rebooted for the first time. Seems like I had only ReLaunch (with no stock launcher) and apparently I've disabled also the stock epub reader. So, again, I enabled them. Now, when pressing the home button , I get to choose between the stock launcher and the ReLaunch.
Quick question before I get to the point,
Isn't it weird that when I try to read a book (epub) using the stock launcher, it opens up immediately, yet when trying to open it up (same book or a different one) using the ReLaunch, a spinning wheel (loading icon) appears until I touch the screen (If I don't touch the screen, It just keeps 'spinning', also, I touch the screen right after opening the book, meaning the spinning wheel isn't 'loading the book' or something.) Any explanation?
Anyhow, I now have ADB access to the nook (Although when I try to 'adb shell' from my Ubuntu [AND NOT THE OS I USED FOR ROOTING IT, THAT ONE WORKS JUST FINE], I get an error message saying 'ADB: error: insufficient permissions for device'. So I've to run 'adb kill-server' and 'sudo adb usb' to gain access to adb shell (tried listing the files using 'ls', seems to be working.)
Now what?
Can someone please direct me to some APK worth installing (Kindle app? recommended PDF/EPUB reader?)
Sorry for the long post and thanks in advance.

Related

Rooted Nook Question

So I rooted my nook and everything was working fine, I powered it off and when I went to power it back on it's stuck on the book screen that says "nook c" or whatever in different colors.
Update: It actually stops at "nook c" when it's suppose to spell out "nook color" -____-
Could you detail what you were doing before you shut down? Installing anything, reinstalling from Titanium Backup, etc.
Are you using the stock ROM? Are you able to see the device with adb when you boot up (just use "adb devices" in a command prompt and see if the device name comes up)? If so, you might want to check the system logs. You can use "adb logcat" to see a few lines, or write to file with "adb logcat > logcat.txt" and view with a regular text viewer. You'll probably have to cut it off that command after a few seconds (with Ctrl+c) as the log file tends to be big. You could try posting any errors from the logcat file.
bluebear13 said:
Could you detail what you were doing before you shut down? Installing anything, reinstalling from Titanium Backup, etc.
Are you using the stock ROM? Are you able to see the device with adb when you boot up (just use "adb devices" in a command prompt and see if the device name comes up)? If so, you might want to check the system logs. You can use "adb logcat" to see a few lines, or write to file with "adb logcat > logcat.txt" and view with a regular text viewer. You'll probably have to cut it off that command after a few seconds (with Ctrl+c) as the log file tends to be big. You could try posting any errors from the logcat file.
Click to expand...
Click to collapse
I don't know what you mean by "am I able to see the device with adb? Well I ended up just doing a three finger reset and so now it's not rooted but I will try to root once again when I'm home and see how that goes I originally wanted honeycomb. Do I have to root and then flash honeycomb?
tamaramarrero said:
I don't know what you mean by "am I able to see the device with adb?
Click to expand...
Click to collapse
If you connect the Nook to your computer and run "adb devices" in a command prompt (from the sdk platform-tools folder), your Nook should be identified if it's still alive and running processes. It's a nice way to check if you're running into startup issues or if the thing just froze. Since you're starting over, I guess I won't detail this further. Have you gotten adb running? If not, you might want to consider it if you're playing with root. Have you been following the nookdevs website (http://nookdevs.com/Portal:NookColor)? There's a lot of detail there and good instructions on all this as well.
tamaramarrero said:
Do I have to root and then flash honeycomb?
Click to expand...
Click to collapse
You don't need root to flash a new ROM; you just need an unsecured bootloader, which the Nook has. I've only ever tried honeycomb from an unstable developer build a few months back booting from an SD card. Has anyone gotten honeycomb 3.2 compiled for Nook? CyanogenMod7 is a stable build of gingerbread. I'm running that now, and it's quite nice. I even like the Nook app better than the stock Nook experience, especially since it started supporting magazines.
I originally wanted honeycomb.
Click to expand...
Click to collapse
Then I suggest that you get a different tablet with it pre-installed from the factory. Google has not and will not release the source code so there is no bug free version for you to install. Gingerbread (CM7) is your best option. If you really like the look of Honeycomb you can later install a Honeycomb looking theme.

[Q] Thinkpad Tablet from China without PlayStore: Root, CWM, ROM?

Hi all,
After countless checks on forums and other threads on XDA, I've decided to post this thread as I couldn't find a similar case anywhere.
Situation is I have a TPT from China. Long story short, it was from my company, and when I moved back to Europe I got to keep it.
Anyway, the problem is that it comes with a blocked Lenovo Store, meaning I can't access any of European/US/international apps. Going to Google Play store online doesn't work ("you haven't used any device with this account") - tried from tablet or from computer.
So I thought I would root and install a custom ROM that could enable me to get to the store and personalization/optimization of the device.
I managed to root my TPT thru this thread: http://forum.xda-developers.com/showthread.php?t=1925025
Everything went OK but then I am stuck at the next stage.
If I understand well from this thread http://forum.xda-developers.com/showthread.php?t=1846044, I need to install CWM and then install the custom ROM.
The thread about installing CWM, http://forum.xda-developers.com/showthread.php?t=1831161, just doesn't work, maybe I'm doing something wrong.
If anyone can help it would be very helpful, right now my TPT is just useless...
Thanks all, any help will be very much appreciated.
M0t3l
Here are the specs:
Thinkpad Tablet 32GB
Android version 4.0.3
Kernel: 2.6.39.4-g9b8008b-dirty
Build number: A400_03_0070_0132_SC
Machine Type/model: 183825C
I am on Windows 7 and Mac OSX
Needing a few more details than "just doesn't work"... Are you getting an error message?
Thinkpad Tablet from China
da_reeseboy said:
Needing a few more details than "just doesn't work"... Are you getting an error message?
Click to expand...
Click to collapse
Hi Da Reeseboy, thanks for answering first.
ADB drivers have already been installed on my windows machine in order to root the TPT.
Then at step 3 of the tutorial ("backup your old recovery"), I tried to input the commands into the TPT but nothing happens.
I have installed an application from the chinese lenovo store called SuShell in order to do that (I do speak some chinese). SuShell just tells me "command executed", that's it.
Actually I am not clear if I have an "old recovery" or if it's only for people already with CWM.
So I went on to step 4.
I did copy the file "recovery.img" to an SD card, stick it into the TPT and tried to proceed on the TPT via SuShell again, but when I type in the commands, SuShell tells me "command executed", but nothing happens again.
So I am a little confused if I am doing something the wrong way or typing the commands not thru the right channel or something else.
That's where any help will be very useful.
Thanks again!
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
TPT from China
da_reeseboy said:
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
Click to expand...
Click to collapse
Thanks da_reeseboy, that made it!
I had a few gliches on the way but nothing major that I couldn't overcome.
I did follow the steps on the tutorials and now CM seems to be working fine on the tablet. It seems that a couple of functions on the TPT are either crashing or not working correctly, will try to look into it, but mainly I am now able to access the Play Store and said goodbye to the Chinese Lenovo Store.
Cheers again!
M0t3l

Nook Simple Touch Glowlight .. Need advice before rooting.

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.

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

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

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

This one20092011201220132015201720192021Nook v1 Nook Simple TouchNook Simple Touch w/ GlowlightNook GlowlightNook Glowlight PlusNook Glowlight 3Nook Glowlight Plus (7.8 inch)Nook Glowlight 4
The other one
The 2019 Glowlight Plus shares the same name as the 2015 release. To avoid confusion, people began referring to it as the Glowlight 4, a name later used for the 2021 Nook release (surprisedpikachu.jpg). While the 2019 Nook is both confused with the 2015 and 2021 Nooks, it is less common than either. This makes it difficult to find compatible resources and tutorials.
This thread is for collecting the available resources for the 2019 Nook in one place, and eventually building a step-by-step guide for unlocking the potential of the device.
Why the BNRV700?
Three years after its release, it's currently the cheapest option for a reader with a screen size ideal for large format PDFs, such as textbooks. As of writing, the Nook Glowlight Plus (2019) can be found for half (or less) the price of other options with a similar display.
Unfortunately, the Nook ships with poor support for PDFs, sluggish hardware, severely outdated firmware (Android 4.4.2, released 2013) and lacks additional features like expandable storage. Some of these issues can be remedied, meaning the Nook could be a great option for many people, but only if it's safe and convenient to expand its functionality.
If you know of any useful resources or guides, please leave them in the comments below.
Note: This is an early work in progress. As of writing this, I don't have the device yet.
I'm reserving this space to put any resources, or document my experience with rooting or recovering the Nook Glowlight Plus 7.8 2019 (NGP7.8, BNRV700).
Resources
Technical
Hardware overview: Temblast​Backup and Recovery
TWRP: Github​Neo Noogie: Temblast, XDA-thread​Rooting
Magisk Root guide (Glowlight 4): Mobileread-thread​Caution: This guide is specifically for the Glowlight 4 (2021) rather than the Glowlight Plus 7.8 (2019) but it might be applicable.​RootGLP-3 script (Glowlight 3): XDA-thread​Caution: This resource is for the Glowlight 3 (2017) rather than the Glowlight Plus 7.8 (2019), however it has been reported to work.​RootGLP-3 script (2019 Glowlight Plus): XDA-thread​Note: This is a small modification of the Glowlight 3 (2017) root script for the 2019 Glowlight Plus, from wgznz (Chinese).​Firmware
Alternate ROM: XDA-thread​Software
Installing a launcher:​Installing apps:​Compatible readers and utilities:​Adding wallpapers:​Adding a software back button:​Physical button remapping:​Hardware
Expandable storage mod::​
High risk or incompatible resources
Mods
NGP Exposed module with fast refresh: Mobileread-thread​Supported: Nook Glowlight Plus (2015), Nook Glowlight 3​Notes: Due to the similarities between the NG3 and NGP7.8 (2019), someone might be able to get this to work, but it's untested.​
jun127 said:
I think more people would be willing to try it. But, between confusing and inconsistent naming making searches difficult (now even worse with the "Glowlight 4") and a lack of step-by-step guides, it's a minefield for the casual user to modify, and most aren't interested in the sub-standard Nook software.
Click to expand...
Click to collapse
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.
nmyshkin said:
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.
Click to expand...
Click to collapse
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
Rough draft / work in progress (proceed at own risk)
Getting started
Download and install ADB
Using Android Studio
1: Download Android Studio
2: Scroll down and click on “SDK Tools Only”
3: Click on “ADB, Fastboot, and Platform Tools” and then click on the “Download” button.
4: After “adb_setup-x86.exe” is downloaded by the installer, run it and install adb inside the android SDK folder.
Using Minimal ADB and Fastboot
1: Download the installer or portable version (See: original XDA thread, latest version 1.4.3, 2018).
2: Install and run
Note: If you use the portable version, commands should be ran from the same directory. To open a console in the current folder on Windows, select the address bar, type cmd and hit enter.​
Enable USB debugging through developer options
1: Unplug the nook from the computer and turn the Nook on, register an account with Barnes and Noble and finish setting the device up.
2: Pull down the top menu
3: click "see all settings"
4: Press the down error on the bottom of the menu to go to the second page of settings
5: Press "about"
6: Tap the Nook logo until developer mode is enabled
7: Press "developer option settings"
8: Enable the "usb debugging" option
9: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.​Note: When running commands over USB, sometimes it's necessary to temporarily disable mass transfer mode. To do this, go back to the developer options menu and select "disable mass storage".​Important: Remember to re-enable mass storage mode if you would like to drag-and-drop files onto your device using Windows file explorer later.​
Backup and restoration
The two most popular methods of creating and restoring backups are TWRP and Neo Noogie. If possible, it's best to have a backup from both. However, if you're not comfortable using the command line in Windows, you may choose to use TWRP only. Neo Noogie is a more powerful (complete) backup method, but it's easy to accidentally format your device or write a backup to the wrong Windows drive, either of which could be a nightmare.
TWRP is recovery software that is installed to the device, and provides a menu to backup and restore parts of the device to internal memory. You'll have to copy the recovery files from your device afterwards.
Neo Noogie can either be installed like TWRP or booted with fastboot. When booted into Neo Noogie, the entire flash memory is served to Windows and appears as a raw unformated drive. The internal storage can then be copied with special software. This has the advantage over TWRP in that it can be used to backup every aspect of your device, but you have to be very careful not to accidentally format the drive in Windows, as it could brick your device.
TWRP
Download TWRP
1: Download twrp_quill.img (may, 2020) from https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases
2: Move twrp_generic to a folder (such as Documents\Nook)
Install TWRP
3: Power the NOOK BNRV700 off.
4: Hold the U button and then the power button until it starts into fastboot mode.
5: Connect the Nook to a Windows computer with USB, the drivers should be installed automatically.
6: Open the command prompt or Minimal ADB and Fastboot
7: Navigate to the folder you saved the TWRP image in (ex. starting from your user directory, enter "cd Documents\Nook").
8: Enter fastboot flash recovery twrp_generic.img to install TWRP
9: Enter adb reboot recovery (or interrupt startup 5 times) to enter TWRP recovery mode
Create backup with TWRP
Notice: (TWRP will not backup /storage/spsd as well as /data/media, which in practical terms means ...xyz...)
1: (I don't have a Nook anymore as my NST screen isn't working and haven't used TWRP in 10 years. I imagine it's something like boot into recovery/TWRP > Backup > check all the options > run)
2: Plug the Nook into the computer
3: Select USB mass transfer protocol
4: Open the Nook in file explorer and find wherever the recovery was saved to
5: Copy it to a safe place, like documents\nook.
Uninstall TWRP / reinstall stock recovery
The Nook's update file, 'update.zip' contains a copy of the stock recovery which can be reinstalled if you wish to return the Nook to factory defaults. However the stock recovery has fewer recovery features - so it is always safest to keep TWRP installed if you are tinkering with the device.
Rooting
Root Guide for the 2019 Glowlight Plus (using rootGLP)
1: Ensure you've enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.​3: Disconnect the Nook and go back to the developer settings menu (see steps 2.1) and select "disable mass storage".
Note: This will prevent USB mode from interfering as we run the ADB script.​3: Download rootGLP.rar
Note: this is the same root script for the Glowlight 3, updated with the correct device name BGRV700. The original can be found in this XDA-thread. For a root guide for the Glowlight 3 using rootGLP, see this XDA-thread. The source is the wgznz forum (Chinese).​4: Extract rootGLP
Note: It's best to run the script from a location like C:\rootGLP\ or D:\rootGLP\.​5: Run the rootnook.cmd
Note: After the process is complete, you will see superSUfree appear on the screen. You will still need to install an alternate launcher.​
Installing apps
Installing a launcher and apps (doesn't require root)
If you haven't installed ADB, you can use the copy of adb.exe in the rootGLP-3\bin\ folder by following the instructions below. After installing a launcher, you should consider installing a file browser (such as ES file explorer) and a better web browser, so that you can download and install apps without connecting to your computer.
1. Make sure you have enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2. Navigate to the rootGLP-3\bin\ folder.
3. Place the launcher .apk inside the bin folder with adb.exe.
4. Click the address bar in Windows Explorer and type "cmd" without quotes and hit enter. A windows CMD terminal will open at the current folder address.
5. type adb install launchername.apk (replace with the name of your .apk file)
Note: kk launcher and text launcher are known to work.​6. When you hit the U-shaped home button on your Nook, it will prompt you to select a launcher and ask if you would like to set it as the default. I recommend using "only once" at least until you can ensure you can always get back to the default launcher from whatever Android 4.4.2 compatible launcher you choose.
Installing KOreader and getting pageturn buttons working in KOreader (no root)
1. Download KOreader apk from https://koreader.rocks/
2. make sure your device is connected to adb and authorized with adb devices, if it t says "unauthorized", go to the developer menu (nook home > top right > all settings > page 2 > more > repeatedly tap logo) and tap "allow debugging".
3. install adb install koreader.apk. just hit tab to autocomplete the actual apk name.
4. Create a textfile "event_map.lua" in notepad and copy paste the following keymappings:
Code:
return {
[141] = "RPgBack",
[142] = "RPgFwd",
[140] = "RPgBack",
[139] = "RPgFwd",
}
5. use command adb push event_map.lua /sdcard/KOreader/settings/ to push the event map to the koreader settings.
6. If you had already installed and started KOreader before and just want to fix the keymapping, restart KOreader for the new settings to work (launcher > settings > apps > KOreader > force stop > home button > open KOreader > open book > test buttons > enjoy.
The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?
jun127 said:
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
etc.
Click to expand...
Click to collapse
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391
nmyshkin said:
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391
Click to expand...
Click to collapse
I'd like to put together a simple guide, similar to what I wrote for the original NST about 10 years ago. I think the device needs a roadmap to outline what is currently possible in terms that are easy to follow. The device seems like it has a lot of potential, but it's just not very accessible at the moment.
I watched your video on running the CM on the NST, very interesting stuff and I'm glad to see some people are still keeping the device alive. I had used the original NST as a smartphone for a (short) while, even using it with Google phone and Whatsapp. It was surprisingly functional and, with the right optimizations, the battery could seemingly last forever with light use. Although it otherwise held up well, the rubber front panel and soft-touch back eventually degraded into a gooey mess. Removing the soft-touch coating on the back shell and replacing the rubber on the front with leather made it a more enjoyable reading experience for a while. Unfortunately, very poor app availability on Android 2.1 and the small, relatively low resolution display made it almost unusable for large format PDFs. Ultimately, the screen started failing and although it's still worth fixing, after 10 years it's overdue for an upgrade.
Renate said:
The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?
Click to expand...
Click to collapse
There's some peace of mind in knowing how to return things to exactly where you started. Even if unnecessary, there's always the possibility of some unforeseen issue and having a clear roadmap that you can follow to get back to the very beginning makes a difference in my mind.

Categories

Resources