yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] nmyshkin:
1. You cannot push an app to /system without write access. That means you would have to mount /system as RW before you attempt to push the app. Those ADB commands are here and there on this forum, but not at my fingertips. It's not something I would do unless there is no other alternative.

2. NookColorTools is

dangerous

. If you think you need it to enable side-loading of apps, NookManager took care of that already. Some of the more "interesting" (i.e., tempting) options shown in NookColorTools will cause (without warning) a complete factory re-image, taking you back to square 0.

I assume you are using ADB Konnect on the NST, so the IP address is correct as the device identifier. But...you need root access. So we're back to that if you want to push a system app. Back when I first started out and didn't know very much at all someone directed me to the Root Browser app. This is essentially a root file manager. So if you are more or less content with ReLaunch but would like to have some kind of root file access, that might be the way to go. The version in the PlayStore is no longer compatible down to Android 2.1, but this version: https://root-browser.en.uptodown.com/android/download/237717, should be fine. That will allow you to move things around and mount/unmount the /system as RW. It's not quite as elegant as something like ES File Explorer, but it will get the job done.

I should add that I'm pretty hard on ReLaunch, but admittedly version 1.3.8 is really old, in fact the last of its kind. Then a new coder took it up and created the fork ReLaunchX (more info here). It may be that there have been many improvements, including perhaps root access.
[Nook Touch Android Development] klewlessnoob:
Thanks again for the reply. I think I figured out my issue...for now :-)
[Nook Touch Android Development] jptiger:
Out of curiousity, after all the customization of NookManager, I kind of want to save another img file in case I need to use it again. Would using a utility to read the SD card to an image file after all the changes are made work in place of the current img file, or would it be stuck with the size of the drive I copy from/lose some secret sauce somehow?

If it works, I could save some folks some trouble and just upload a patched version to work with 1.2.2 to this thread.
[Nook Touch Android Development] nmyshkin:
Yeah, that's one of the reasons I did not produce an updated image. Someone tried that (another post hereabouts) and it seems the image is bad.

When I did the images for CM 11 I used a utility called dd for Windows: http://www.chrysocome.net/dd and this blog post: https://blog.thestateofme.com/2012/05/28/making-an-image-file-from-an-sd-card-on-windows/. I may have poked around for some other command to control the ultimate size of the image. I should have that somewhere....

---------------------------------------------------------------------

Edit: yep, here it is:

You MUST start CMD window as Administrator!!!!!!

dd if=\\?\Device\Harddisk1\Partition0 of=c:\temp\myimage.img bs=1M count=2050

The final value is the ultimate size of the image

-----------------------------------------------------------------------

I imagine the same can be done for NookManager but I was confused by the Backup partition which seems to fill the remains of whatever card you use. Since I was presenting a number of different options for updating NookManager I didn't want to produce a whole lot of potentially useless images.

So, yes, I am sure it can be done. But I didn't do it.
[Nook Touch Android Development] jptiger:
Fair enough. In that case, I don't want to sink too much time into this, but I'm attaching a version with the 1.2.2 updated scripts, jar files, and a few added apps: ES File Explorer, resigned Opera Mobile, Relaunch (I know, I know), and Button Savior. I used Win32DiskImager 1.0 with the Read Only Allocated Partitions box checked. Anyone trying this, YMMV.
[Nook Touch Android Development] nmyshkin:
Time for a reboot!

My original intention in this thread was to teach people to fish. However it is clear to me that some people were reeling in old tires and boots--or choking on fish bones!

I have rewritten the first two posts and provided 3 variations of updated NookManager images. Hopefully this will eliminate some of the bizarre results that were so difficult to diagnose and resulted in frustration. The whole idea of NookManager is to have something anyone can use to achieve a simple goal. I hope these changes help in the pursuit of that goal..
[Nook Touch Android Development] h2.618:
I was able to root a STR, with 1.2.2 firmware, in the US. The process is smooth as can be.

That being said, I was not able to achieve my real goal, which is to load a different ebook reader app. I tried an fbreader apk, which was not recognized by the firmware. I tried a couple of coolreader apks (coolreader-3.2.6-armeabi-v7a-release.apk, and coolreader-3.2.6-arm64-v8a-release.apk), through SD card copy and ES, and both went through the installation motion but failed to install in the end. There is no error message to help diagnose the problem. Could someone please help? Thank you very much!
[Nook Touch Android Development] Renate:
Mmm, maybe incompatible versions?

The arm64 is 64 bit ARM which the NST certainly is not!

Do you have ADB working?

C:\>adb logcat
[Nook Touch Android Development] nmyshkin:
You have to be a bit of sleuth to find app versions that will work well on the NST. Keep in mind that the OS is Android 2.1. In ES File Explorer you will see that apps which are not going to install because of the wrong Android version will display a funny stacked box image rather than the apk package icon. Such apps will give parsing errors when the package installer gets a hold of them. But there are other issues which may let installation begin and seem to proceed only to finally end with "App not installed". So you need to "shop around"--or ask.

Here are correct versions of some popular readers:

FBReaderJ_nst (download here)

CoolReader 3.1.2-51 (download here)

AlReader 1.77 (download here)
[Nook Touch Android Development] h2.618:
Thank you very much, @nmyshkin! The FBreader you provided here installed immediately and successfully!

Now I have a couple of questions on how to use it:

1. The reader has a tendency to go back to the old stock home app and reader app. Can I change the default reader app over to the FBreader? And how do I get easier access to the new home app? (Currently I can only get to it by restarting.)

2. I read from many places that I can change the mapping of the hardware buttons, but I can't find how exactly to do that.

3. In the FBreader (or some other reader), how do I look up the books I have on the device? I put them in the internal memory, and in the Nook native reader they just show up. But in FBreader I can't seem to find a path to them.
[Nook Touch Android Development] h2.618:
Thank you, @Renate. I don't have adb right now (had it before, for different devices, mostly phones), and was in the process of getting one adapted for the NST when I saw @nmyshkin's message below, and it worked out fine on first try. I'm still learning and it seems the info about this device is scattered all over the place.
[Nook Touch Android Development] nmyshkin:
It depends on which version of NookManager you used. FBReader further complicates the picture because it will try to behave as a "home" app if you let it. Do you ever want to see the B&N default home screen? If the answer is "no", then the easiest thing is to reboot your device. There should be an initial prompt which will ask you which "home" app you want to use. First tick the little box at the bottom of the dialog to make your choice the default. Then pick whichever one you want. To make sure of what you want, you probably should make some new button assignments...

In your new app drawer you should see Nook Touch Mod Manager. This is the app which allows you to change not only hardware button assignments, but QuickNav "button" and other "soft" button assignments as well. So to make the "reading now" soft-button (left-most on status bar) open FBReader instead of the stock Reader, you would assign it to FBReader. Similarly, if you want the "n" button to take you to your new launcher rather than the B&N Home screen, assign it to that app (ADW Launcher, ReLaunchX, etc.). That last choice will prevent you from accessing the QuickNav buttons, of course, so if you still want to use those, you can assign a long-press of the "n" button to open them. Or whatever. You'll probably change your mind several times until you get what you like.

AFAIK none of the third-party reader apps does an autoscan the way the stock reader does. Perhaps that's something I could look at sometime in the future. Instead, each of the readers has a "scan" or "rescan" feature for their libraries so that books you have moved to the device will be indexed. With FBReader, you first need to go to Settings and set the directories where you want the app to look for books. You can choose more than one (e.g., /media and /sdcard--this will include all sub-folders, so you may want to narrow the fields). When in the main library screen, tap on the "menu" button in the status bar and you will see a "rescan" option at the bottom of the screen.

If you miss being able to directly access the library like you can in the stock system, I have written a little app that takes you directly to the FBReader library. Probably that is where I should think about adding an "autoscan" feature so the system is not constantly being queried, although the added feature would then be limited to accessing the library through the new app only, and not when the library is accessed within FBReader. Still, it's a thought.
[Nook Touch Android Development] h2.618:
I cannot thank you enough, @nmyshkin! With your detailed instructions I was able to accomplish everything I needed to read Chinese books on this device, in addition to the default English. This feels great!

I'll take the reader with me for the trip I'm taking later today and give it a few days of good use!

A very happy camper I am!
[Nook Touch Android Development] regancipher:
This should be fun. Just found my nook that was rooted about 10 years ago.... here we go!
[Nook Touch Android Development] regancipher:
Works fine for me
[Nook Touch Android Development] fireh9lly:
Hi, I'm new here - thanks so much for helping me revive my Dad's obsolete old Nook. Flashed from UK to US, then used Nookmanager to remove all the B&N software.

However, I'm still getting significant battery drain from "Cell standby". Admittedly, it's only 20% over 4 days standby, but I still would rather avoid that (it's not necessary, and one of the main benefits of ereaders is the battery life). I tried renaming Phone.apk in the RelaunchX browser, but it didn't work (presumably it's already running).

Is there a way I can get rid of this? Ideally, I don't want to install gigabytes of Android software development tools that I don't even know will work with ancient Android versions to do it.
[Nook Touch Android Development] aaciii:
I've just revived my old NST and updated to 1.2.2 and rooted with "Stealth" - piece of cake, thanks.

question. my main goal in rooting was to be able to jump online and download a PDF and/or EPUB (from a a variety of web sources). I want to avoid having to download on my PC and side-load the files to the Nook.

however the Opera Mini browser wont allow me to download - it says " download failed - a memory card is needed for file downloads"

Is there a way to get the browser to allow downloading to the Nook's filesystem? After all I can mount and side-load files to it from my laptop.
[Nook Touch Android Development] nmyshkin:
My initial response would be that microSD cards are pretty cheap and can be useful, but that really does not address your issue.

It may be possible to alter the permissions for Opera Mini to convince it that it's OK to download to someplace like /media/Download, but I have my doubts. I can't think of any app I run that will place files in /media, other than B&N stuff. I've never really thought about this much because I've always used an sdcard in my NSTs.

Let me poke around a little and see what I can find.
[Nook Touch Android Development] aaciii:
by default if mounting the Nook on a laptop (USB mode), the "My Files" folder is where content is placed. the actual NST filesystem path to that folder is media/My Files
[Nook Touch Android Development] nmyshkin:
Yes, and...?

Not sure where you are headed with that. The /media (partition) is internal storage and can be used (will be used) if there is no external sdcard inserted. But apps (especially old ones) can be very persnickety about where downloaded material will go. Before the amped-up security of KitKat and later, this generally meant the external sdcard so that you would not fill up internal storage with lots of videos, audio files, etc. Then the whole thing flip-flopped with the advent of hypersecurity so that everything went to the emmc storage by default and you had to fight to get things to go to the external sdcard.

FWIW, there is a file that seems to exercise some control over this situation: /etc/vold.conf. It's a text file which seems to assign name and mounts for internal and external storage. If you study it carefully you will see opposite lines commented out for internal and external storage.

I am not suggesting that you alter this file. It might wreak havoc on your device and the behavior of other things. It might do nothing. I would consider that a "nuclear" option.

Instead I would check out the file /data/system/packages.xml

It's very long and is easier to look at if you offload to your PC. You want to find Opera Mini and see if it has permission for external storage. If not, you may be able to add it and it

may

have some effect after a reboot (be SURE to backup this file before you do anything. If you screw up you will be in a real fix). But my money is on this not working. It's the app. You probably can't convince it otherwise.

So I'm back to get a microSD card.
[Nook Touch Android Development] Zaq_Tactic:
So, i don't know if its just me, but whenever I insert the SDcard with the nookmanager traditional, it doesnt boot back up when I hold or press or basically do anything to the power button, BUT the moment I pull the card out and try again, it boots up as if like nothing had happened...

What could be the problem...
[Nook Touch Android Development] Zaq_Tactic:
Nevermind...

That's fixed but now its stuck on the loading screen "NookManager Loading..."
[Nook Touch Android Development] nmyshkin:
OK...well it sounds to me like there is a problem with the card. It may have been damaged during the..er..little dustup which inspired you to post in the first place or there may have been an error when you burned the image. Problems such as you describe almost always come down to the card.

So...wipe it and try again, or use a different card.
[Nook Touch Android Development] malc_b:
Hi,

I'm a little bit confused and not sure of the best way to proceed. I have 2 NST, both UK, one version 1.2.0 and one 1.2.1. The 1.2.0 is on its last legs. The rubber is falling off, the battery seems to get to 65% then fall off a cliff and the unit crash, plus it used to a glow but that died a long while back. I'm looking to get the 1.2.1 version working as a replacement. This has been wiped and is not registered. I assume OOBE has been done as it works to read books but the home page has the endless spinner. I've installed Nook Manager Classic (I have an older Nook Manger on the 1.2.0).

Is there any point updating to 1.2.2? What do I gain? I've read the post on the unofficial UK update which is a lot of work if there is no significant gain for 1.2.2. Also, it says I have to use my B&N registration. I have registered, a long while back on www.nook.com. That URL just displays a notice saying UK has been abandoned (in effect). The web site www.barnesandnoble.com doesn't recognize my old login. I guess I have to create a new login on www.barnesandnoble.com is that right?

My other option is to stick with 1.2.1, delete all the B&N stuff and install another reader. That sounds interesting as I've had some books where the font choice was only 2 sizes, too big or too small. I guess I need to follow these instructions on the 1.2.1 to give a no B&N unit, but first maybe do a factory reset? Or could I just repeat the install of Nook Manager with Nook Manager Traditional to get ES File Explorer and a different launcher than B&N. Maybe even follow the instructions to modify the install to add my new apps. I only use it to read so I'd just need a reader and UK dictionary (with in the reader maybe?). AIreader or FBreader maybe?
[Nook Touch Android Development] nmyshkin:
Lots to think about here.

First you should know that B&N will stop supporting the NST (sound familiar?) in June 2024. For that reason alone I would recommend that you update both devices to FW 1.2.2 and register them. If the info from B&N is correct this will not be quite as traumatic as the UK fiasco. They claim the devices will still be able to ping B&N servers and wifi will function without errors. Just no transactions or downloading. So even if you decide later to try without B&N stuff you could have these devices backed up as registered if you change your mind.

Why register? I cannot testify to this myself but I intend to experiment in the near future. It has long been reported by those who skip OOBE that battery life is significantly shorter. This is believable if you look at the logcat of such a device as there is all kinds of futile activity in search of B&N. Not to mention the spinner...

So skipping OOBE has to be a fanatic's last ditch effort to continue using the NST.

You can use the region changer on your UK devices to convert them to US firmware and then they will accept the 1.2.2 update. You will lose the Oxford dictionary if you do this and get the Merriam-Webster in it's place. I've tried to do a conversion, but the dictionaries have structural differences that have bested my efforts.

Or, you can make the change to my custom UK firmware 1.2.2 (first open an account at B&N) and register. You'll retain everything you're used to and increase battery life. I know it looks daunting but it's not bad once you actually get started.

The updated NookManager has a new "remove all B&N" routine which does the job properly so if you want to think about building up your own system, that will make it easier and, yes, the Traditional version of NM would be better for that. CoolReader, AlReader, FBReader, Mantano, Moon+ ... The list goes on. Each has a fanbase.

You're ahead of my production time line but I'm thinking of working on custom packages for some of those readers for all the people who show up after June 2024, using my new custom UI.

Register both, make backups with NM and store them on your PC somewhere. Then think about what will work best for you.
[Nook Touch Android Development] malc_b:
Hi,

You make a good point. Getting the 1.2.1 registered and up to 1.2.2 with Nook Manager and relaunch means I have a new copy of my current, falling to bits, nook. And taking a backup at that point would give me a fall back position. I could then play with options on the "was 1.2.1" nook to see if I liked them better. And when I've swapped to using the newer nook for my reader I could update the 1.2.0 version, just in case. But it is literally falling to bits. The rubber has come off the right hand side page buttons so they physically do not work any more.

I appreciate your reply and the work you do.

Thanks
[Nook Touch Android Development] nmyshkin:
I had another thought which may or may not matter for the functioning of either device. Before you do the updating I would use NookManager to initiate a Factory zip reimage. This will take you back to some earlier firmware, perhaps, but it doesn't matter since you will be updating anyway. It might affect the charging issue and (very slim chance) the glowlight issue. If there are glitches in the system (garbled battery stats) it could straighten that out. Something unknown in the code might also be preventing the glowlight from operating. You can only try and at least down the line you won't be wondering if...

Hardware issues, IMO, are not worth addressing because devices without hardware issues (one hopes) are readily available on ebay. It's too bad about the rubber on the bezel. I have only one device where that has started to happen and only in one area.I did a lot of cleaning with 409/rubbing alcohol to get rid of all the goo and then massaged in ArmorAll. It makes things a bit slick but seems to help a lot. Mine are in cases anyway, so it's not going to slip out of my hands!

BTW, here are links to the region change if you decide to go that route:
[Nook Touch Android Development] malc_b:
I'm now trying a "no B&N" reader. I added AlReader apk to the do_root as per instructions and then reran Nook Manger root. I guess there is a better way but that seemed the easiest. I've installed AlReader, FBreader and FBreader PDF plugin. Alreader runs ok but I've no dictionary. I downloaded colordict to install but I can't seem to find dictionaries for that, UK english that is, Oxford I guess. Maybe if I install the app knows where to get them.

FBreader does not run. I just get a blank white screen. I'm got the FBreader for the nook and e-ink but maybe it doesn't like V1.2.2?

Not sure how to uninstall, can I do this in ReLaunchX? Or is it easiest to create a script in custom scripts, copying the install .... and changing install to uninstall? Do I just uninstall FBreader or do I need to remove the PDF plugin first? That is would removing FBreader also remove the plugin? Of course I could always do a backup restore to get back to clean V1.2.2. and then root and install.

Any suggestions on best reader and dictionary? I just want it as a book reader primarily (with a launcher and file browser), uk english. More font sizes would be good so I like the ease of change font size in AlReader. A library app might be good too.
[Nook Touch Android Development] nmyshkin:
Yeah, that's really the hard way if you're still playing around trying to figure out what you want. Modifying the scripts really should be a one-off to get a base structure when you are developing over and over and over....

So, I'm not a RelaunchX expert (or fan) but the easiest way to install an app is to copy it to the device and then tap on the apk file in the file manager. You should be given the option to install. Similarly (but not) to uninstall you long-press on the app icon in the app drawer and you should get a context menu with the option to uninstall.

I doubt that. As I recall, the only plugin that works with this version of FBReader is the TTS plugin. The oldest PDF plugin is for Android 2.3 (maybe 2.2). I don't know how this may have affected the script (another reason not to use the scripts for routine app management) but it may account for your white screen with FBReader.

See your PM.

I doubt the plugin is there as I said above but this reveals another issue with RelaunchX. The plugin would not show in the app drawer. There is no interface. So there is no way to remove it with RelaunchX (even if it were installed which I doubt it is).

Take a look at my mod of Mantano. As I say there, it's not for everybody (especially if you're a font fanatic). I used AlReader for awhile before moving to Mantano. I've also tried FBReader in the past. Each has quirks which I was (more or less) able to work around with custom apps. Of the three, Mantano is definitely the least "featured". It's very similar to the stock reading app (but with better PDF support) in terms of adjustments and you can change font size just by swiping up or down on the screen while you're reading. You might like that.

Library? Other than what the reader offers? @Renate wrote a Library app which is available here. Some people have expressed a liking for it in the past. You might try it out. I don't know anything about it.