yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] sany:
Installing APKs

I am new to Nook rooting and customization and wanted to understand the process before I begin.

1. What are the different ways to install APKs into a rooted Nook? Since I saw a few APKs attached in the first post, do you copy to your device and run via nook manager?

2. After installing android market - I guess this is straight forward but I am assuming the market access could be challenging as the android market does not exist anymore and only play store exists. I am not sure about this.

3. If you install directly APK - any new updates to the app will be pushed via the app itself or a manual installation of the latest APK is the only way?

thanks

S
[Nook Touch Android Development] nmyshkin:
Either copy the apk file via USB from your PC to the NST and install using a file manager or install from your PC via ADB. NookManager can install some few apps if you take the time to update the files as described in the first post, but not as a continuing process, more like a baseline of stuff to get you started.

No Android Market and no PlayStore access as of 2017. Read in the first post. There was an alternative app (Yalp Store) for accessing the PlayStore,but the developer abandoned it and it no longer works.

Side-loading means you are on your own for updates. But seriously, updates to apps for Android 2.1?! Generally we want to

avoid

updates because they tend to break the functionality!
[Nook Touch Android Development] sany:
Thanks again for your information. I really appreciate.

Just a last question - I note that you are mentioning that I can install apps via file manager. Therefore, after nook manager is installed - I am assuming that there is a default file manager for me to use to install the other apps like Yalp store, ES file manager etc.,

Also I am assuming, I can save these apks anywhere in the device before installing it - not required to be saved in the root folder or anything like that?

S
[Nook Touch Android Development] nmyshkin:
If you only update NookManager for the 1.2.2 firmware, then Relaunch will be installed by default as a sort of launcher/file manager. Supposedly it is possible to install apps from Relaunch although people have expressed some difficulty with this. I personally do not find Relaunch very helpful. That is one reason I provided an update that installs ES File Explorer and ADW Launcher instead. But it's your choice.

Apps that you wish to side-load can be copied onto the NST anywhere. Most people use an SD card (not the NookManager card, a clean one) for additional storage. On my SD card I have a folder called "Download". That's where I generally move apps to be side-loaded. The Yalp Store app also makes use of this folder to stage apps before installing them.
[Nook Touch Android Development] sany:
That's great! I will do a few further research to clarify a few more things and if I can't find the answer I will come back. I don't want to keep bugging you.

I will look for the thread again on how to update to 1.2.2 (you have already provided me the link to download the firmware)

I also need to go and read the thread on how to do a factory reset using hardware buttons.

You can already see I am nervous :)

thanks for your support.

cheers

S
[Nook Touch Android Development] sany:
Sorry I did not imagine I will come back to you nagging so very soon!

I prepared the SD card now from original post. I see that you have modified script to install all those apps you wanted like ES_file explorer, ADW launcher etc., Does this mean that I have to copy all those apk files into the NookManager>files>data>app folder. I am guessing if I don't do that during rooting, it might search for those apps and throw error?

Secondly, what am I supposed to do with that last attachment in your first post 'patched_1.2.2_jars_for_NM.zip '?

thanks

S
[Nook Touch Android Development] nmyshkin:
At a minimum, assuming you have updated your firmware to 1.2.2, you need to make the updates to the NookManager card for that firmware. Otherwise the rooting procedure will not work. That includes substituting the patched 1.2.2 jars for the ones on the NookManager card which are for 1.2.1.

Anything else is optional. If you want, for example, ES File Explorer, installed with the rooting process then you need to add the modified files and place the apk file itself in NookManager>files>data>app. But only if you have made the modifications on the card for installing any other apps (or not installing ones, like the dead Amazon App Store).

OR, if all the fiddling with NookManager makes you nervous, just update the two files for the 1.2.2 FW and substitute the two jars. After rooting you can then add or subtract whatever apps you want.
[Nook Touch Android Development] PixieD:
I've got very little/no idea what I'm doing so I apologize in advance if my questions are facepalm worthy.

Everything seems fine with Nook Manager. It rooted, I've got backups from before I did the update and after in a couple of places. I deleted the correct apps and added the ones you suggested until I figure out my own preferences.

1. Where did Opera go? The apk is there &scripts are correct & iirc it had mentioned a successful install when I rooted it.

2. Similar situation as above with Yalp store.

3. What are some of the other apps on for? (ADB Konnect, Device Registrator, Nook Touch Mod, Superuser & TestCenterService)

I appreciate all of your help so far and hopefully I can get this ideally configured for me quickly so I stop being a bother.
[Nook Touch Android Development] nmyshkin:
What are you looking at which tells you Opera or Yalp Store are MIA? Did you install either ADW Launcher or ES File Explorer? Did you remember to put those apk files on the NookManager card?

ADB Konnect is for ADB over WiFi. Probably not your biggest concern right now. Nook Touch Mod allows you to reassign all hard and soft buttons to whatever you like (within reason). SuperUser is installed with root to give you control over what apps are allowed to access/change system files. Most of the rest will be B&N stuff.
[Nook Touch Android Development] PixieD:
I installed both ADW Launcher & ES File Explorer. Just checked the SD, both Opera & Yalp Manager apk files are there. I'm looking in the app drawer on ADW.

Thank you for the explanations!
[Nook Touch Android Development] nmyshkin:
Huh. In the app drawer of ADW there are three vertical dots at the upper right. The menu these open includes the App Manager. Check there and see if Opera or Yalp Store are listed. It's probably just as simple to copy the apk files from your PC to the SD card you are using for storage and use ES File Explorer to install (or reinstall) the files. I guess it's possible they could be corrupt.
[Nook Touch Android Development] sany:
Thanks to [MENTION=5562185]nmyshkin[/MENTION] for continuously supporting in helping me root and install apps.

Now time for conclusion: In my usage, I never gained any advantage for having this good tiny e-reader rooted against what is being projected. Mostly because of the power it has from years past. This device cannot handle anything other than just light pdf (not even all pdfs - thanks to low resolution) and epubs.

At least for me, it is not usable for browsing or any other normal tasks that you would do with an android phone or tablet. It is way too slow and tests my patience. Just wastes so much time. Another challenge was getting the right app. For example, Youversion bible works fine but the catch is it will only work with the old version which does not have many features like loading custom bibles. In effect I noticed, installing other pdf readers are also not making life easy - they just work on some, some while loading crashed....

All this caused me to go and do a factory reset to be back like the original e-reader as I was only able to only read epubs decently and there was no real world practical benefit for rooting.

Other major challenge with this e-reader was installing non-english fonts.

I am making this loud and clear for all those new ones that might plan on buying this e-reader expecting it to do more.
[Nook Touch Android Development] mwahlgreen:
Trying to understand and make it happen (Top Hat Soaring)

Hey OP

I am grateful that you made this thread for us how still want to use the NOOK for good work.

I read the whole 52 pages and 515 posts of the first thread made by jeff_kz to try to understand why the NookManager would not work on my NOOK Simple Touch. And then I found this thread.

The non-updated version did not work and I have not yet rooted my NOOK ST with the updated version made by the OP. I plan to do it later today after I have made a backup with NookManager.

Update

The rooting did go well. And I am now able to run both Top Hat Soaring and XCSoar. Thank you very much.
[Nook Touch Android Development] nmyshkin:
Whew! And I still don't really know what Top Hat is or does. You've done a good job ferreting things out so far but I foresee an issue. Repartioning the sd card is what you needed to do but the info I read about Top Hat was written in 2016. Google cut off Android 2.1 access to the market back in 2017. So...unless there is a depository of updates, apps, whatever to download outside the PlayStore, your work will all be for nothing.

Is there?
[Nook Touch Android Development] mwahlgreen:
Yes Top Hat Soaring is build on XCSoar (Both being opensource glider computers (software) with moving map). And XCSoar is still being developed and the APK's is accessible online on XCSoar.org.

I am writting a how to in another post on how I have managed to root the device etc..

Since XCSoar does not have a forum I will post it here in XDA and link to it on the Top Hat Soaring forum.
[Nook Touch Android Development] nmyshkin:
Good for you! Too often people here just leave things hanging and we have no idea of any potential resolution in which there may be the germ of something that will help someone else.

I'm glad you persisted to get it working for you. These are just amazing little devices.
[Nook Touch Android Development] maddogbarber:
Hi, possibly too late to the party but found a new Nook STG and would like to get it running simply as an ereader for mobi epub etc.

boots ok and connects to wifi but next step throws a " Network related error occured" and gets caught in loop testing and reconnecting, have disabled security on wifi to test, not that, (is on 1.21 FW)

Only way to bypass is use nook manager to root and disable BN apps but after that i get lost easy tried region changing, samne network error.

Have spent some time looking now but can't seem to find out how to manually install the 1.22 FW, Tried the zip on the region change but after reboot when it throws the network error that page reports fw is 1.21 so not sure what is going on there, not tinkered under the hood with android much so simples is best :)

I suppose if I could manage to install a half decent ereader manually after disabling bn apps i would be happy but most links i follow are now dead and the info is widely scattered.
[Nook Touch Android Development] nmyshkin:
TMI. Slow down.

1. Are you in the US?

-if yes, just do a factory reset (press and hold both lower hardware buttons as soon as the "Read Forever" screen appears during boot. Wait for the prompt. Once the device is reset it will go to the setup screen. Don't do anything but plug the device into your computer's USB port.

Download the 1.2.2 update zip from B&N and transfer the file via USB to your NST. You can eject the NST from the USB port or just wait but eventually it will sleep and during that time the update will occur. Once that has happened, you can register (if you like), etc.

If you want to eliminate the B&N stuff you will first need to root with NookManager. Be sue to update the files as described at the beginning of this thread. The original NookManager cannot root 1.2.2. If you decide to eliminate all the B&N stuff and create your own site of readers, dictionaries, etc., follow the directions here: https://xdaforums.com/nook-touch/general/nst-g-removing-bn-apps-t3972941.

Potential readers are FBReader, AIReader, and CoolReader, while Color Dict works well with all as a dictionary. None of the readers support DRM books, so if you want to read library books you'll need something like the Kindle app as well. I believe none of the readers supports PDFs so if you need that there is a good version of EBookDroid running around on the forum somewhere.

2. Are you outside the US?

-if yes, follow the directions for a region change found here: https://sites.google.com/site/xcdguides/nook/nookregion

Once the device is at the setup screen, proceed as above.

The key is to avoid trying to contact B&N with 1.2.1. That will not work and each failure means you have to go through the reset process again.
[Nook Touch Android Development] inkoma:
Hello guys. I am also not sure if I am too late for the party. I have a nook simpletouch and it is routed. I manage to run it not bad at all, but I am not able to login into my google account. Therefore I cannot use play books and more apps. What is it still working, and what not?
[Nook Touch Android Development] nmyshkin:
There is no way to achieve what I think you want. The last working version of Google Books died some time in November of 2018.

There are only two ways I know of at present to "sign in" to your Google account. Neither is an actual device sign-in in the sense that you may be used to on more modern devices. You can sign in through the Opera Mobile browser (I just tried that this morning and it worked fine). But you must first change the settings for TLS 1.2 in Opera Mobile as described here: https://xdaforums.com/nook-touch/general/opera-mobile-tls-1-2-t3843524

However, even if you could access your Google books via the browser, the reader will not work properly because of the limited screen resolution.

The second "sign-in" method involves installing what's left of Google Apps that will still function (see https://xdaforums.com/nook-touch/development/nst-g-updating-ntgappsattack-t3875957) but even there you cannot use the device sign-in method and can only sign in via Gmail.
[Nook Touch Android Development] coniliakis:
Hello, I have a Nook Simple Touch. I haven't done anything to it. Could you please advise me how I can root and get it useable again? I tried to find the appopriate rooting method for my version (1.2.2) but I am a little bit lost. Thank you very much
[Nook Touch Android Development] nmyshkin:
The method described in the first post will work, but you will see that you need to make a few changes in the original package. At minimum you need to make the changes described under the heading Updating for FW 1.2.2. Any other changes described there are optional and your choices there will depend on how you intend to use your device, what you want out of it, etc.
[Nook Touch Android Development] corradom:
Hi all,

I have an already rooted working nook simple touch with coolreader , ACV, Perfect Viewer and Fora Dictionary at a super early version (from 2010 or so, back when I bought and rooted this nook I think) on it.

Which advantage I will have upgrading to latest and greatest firmware 1.2.2 ?

Kindle app maybe ? (that never worked fine on my device).
[Nook Touch Android Development] nmyshkin:
If you've been working this long with an old firmware version without problems (and obviously not using B&N stuff), there may not be much to gain. You'd have to go back to stock in order to update and then rebuild your whole system. The TLS 1.2 upgrade seems to affect mainly B&N connections. Opera Mobile, for example, has its own TLS 1.2 setting and this works on older firmwares without the 1.2.2 upgrade.

I'm not saying there may not be something subtle, but if there isn't an issue with your device...

As for Kindle, if the issue is login (as opposed to the app simply not running) it's probably because you need to update your cacerts.bks file. The Amazon certificate expired some time ago but replacing it enables login and the app continues to function (at least on FW 1.2.1 and 1.2.2). Search the forum for "cacerts" and you'll find a couple of versions with updated certificates as well as instructions for updating the file.
[Nook Touch Android Development] corradom:
Thanks a lot for clearing any doubts.

I'm based in Italy so I'm not using B&N connection at all. I bought this device from US because of touch capabilities, and is stil running great (Except plastics that are melting down , getting sticky and breaking in the angles. And it never fell down)

;)
[Nook Touch Android Development] JollyRoger98:
Hello sorry if Im a bit late. I have already rooted my NST with fw 1.2.2, but I can't make the no refresh or fast mode function work. I only rooted my NST for viewing pdfs. Hope someone can help. Tried to scour the discussions here, but only vague posts. Thanks!
[Nook Touch Android Development] nmyshkin:
Both display modes require the "version 2" apps with FW 1.2.2. Fastmode2, at least, also requires a new kernal. NoRefresh may, but there is no mention of this in the original thread.

Only one kernal (166) works with both display modes. You can search the forum with this info in mind, but if you still come up empty, I'll check my links. (link to correct NoRefresh app in my setup link found in my signature below)

FWIW, I think you'll be better served by NoRefresh for PDF reading. Fastmode is so dithered it's not much good for reading text. Lots of ghosting, too.
[Nook Touch Android Development] klewlessnoob:
Another noob in need of some help please....

I rooted following instructions for 1.2.2. Made appropriate changes to 2 scripts and substituted 2 jar files per instructions. I also swapped the Amazon store app with a different app apk that I wanted installed.

Root seems to have been successful, however, I do not have NookMod Manager app listed, nor do I have the application that i manually placed into the install package, even though I did receive the installed OK message at root.

Is there another place I should be looking for the above two applications, or should I re-root?

Thanks!!
[Nook Touch Android Development] nmyshkin:
It's hard to know exactly what might have happened, but if NookTouch ModManager is missing then something went very wrong.

Remember that for each app you want to install automatically, there are at least two changes in scripts to be made (steps 3 and 4 in the original post for "customization"). Also, the apk package name in the script must match exactly the apk package name. Finally, of course, you have to place the actual apk package in files/data/app on the card.

How are you looking at the installed apps? If you're using ReLaunch you have to set it up in "Launcher" mode to see the app drawer (the default is "File Manager" mode from which you cannot access any apps except those from the B&N interface). If you're using a more traditional file manager and you don't see NTTM in the app drawer then check /data/app and see if you find it there (along with the other app you tried to install).

If there were no error messages during installation, it should all be there, but if not, there is no problem with running Root again, especially if you haven't done anything else yet.

Also, you can always copy the NTTM apk from the sdcard and side-load it (along with your other app) but that should not be necessary. My money is on a mode issue with ReLaunch. I really dislike that app.....
[Nook Touch Android Development] klewlessnoob:
Thanks for the suggestion. I decided to re-root, without changing the file package. This time all seems to have come over correctly, including the ModManager. I will now attempt to learn ADB to install the apk I tried to bake in during first install. Is there a refernce to change Relaunch view to "launcher" mode?
[Nook Touch Android Development] nmyshkin:
ReLaunch....

I installed a copy on one of my devices so I could sort this out for you. If it is set up properly you won't need ADB to install your app. You should just be able to copy it to your sdcard and tap on the apk file to install. I think. Not to say that ADB is not a good thing to get going. In fact you will need it to make any serious changes because ReLaunch cannot access the root level--just another reason I don't like it.

So...from the default install, select the "cog wheel" at the upper right to access settings. You should see General Settings and under that "Start Mode" and "Work Mode". These are, respectively, "launcher" and "file manager". Change "Start Mode" to "start as usual program". Then exit with the arrow at the top right and you will be asked if you want to save changes (yes). You then go back to the same useless screen you started with. Repeat the process but this time change the "Start Mode" setting back to "start as launcher" exit and save changes as before. Voila. You end up with a bottom row of additional screen buttons, with the middle one being the app drawer.

This is very lame, but it was the only way I could reveal that lower row of buttons. A long-press on an app in the drawer brings up the option to uninstall. Back on the main screen, if you've moved an apk package to the sdcard, tapping on the package activates the system package installer, so no need for ADB for that purpose.

Obviously there are other settings, but that will get you at least started. You may find that in the long run a more traditional Android file manager (like ES File Explorer provided in the original post) will be more useful as it has settings for accessing the root directory and mounting it as RW. The drawback is that you will then also need a more traditional launcher (like the ADW provided in the original post...) in order to access your apps. It's all a matter of how you plan to use your device and how your use evolves. FWIW, I like ADW a lot but it is not e-ink friendly out-of-the-box and requires a lot of settings to get it looking good, so I understand why some people take a look at it and just give up. I guess I should look at whether a basic start on decent settings can be exported and imported. That would make it a lot more attractive as a launcher for the device.
[Nook Touch Android Development] klewlessnoob:
Thanks again for the help. I am with you so far, but can't get adb working to put an apk on the device. NST is listed by adb as a connected device, although it is using the ip address as the device serial number (not sure if this is right). When I try and push an apk, I am getting a failure:

XXX.apk: 1 file pushed, 0 skipped. 7.7 MB/s (12130 bytes in 0.001s)

adb: error: failed to copy 'XXX.apk' to '/system/app/NookColorTools_0.2.apk': remote Read-only file system

Wondering if I was supposed to do something to allow debugging on the device?