Hi..
I've had problems with Gmail and Maps applications previously with Neophyte ROMs. In that case one of the solutions was removing the apks for these apps from with the /system/app folder of the ROM zip.
My question is:
Is it possible to add our own apks to the custom ROM so that these apks come preinstalled on the ROM when someone flashes it..in a manner, a kind of 2nd generation mod?
Is it possible to add our own system variables and settings files so that the ROM autoinstalls it on First Install? In particular, I'd like to preset my own APN file for the network.
The simple answer is yes.
The entire system folder in the zip file is written to your /system partition, with the full architecture of folders and so on, so any changes made in there will also be on the system, when it is flashed.
There is also a script file, in the META-INF folder, which you can use to run commands to delete or edit something along with the flash, whenever the zip file is flashed. This is a bit more advanced though.
edit: it is the same for the data folder of course, which folders is flashed and where to is also specified in the script file mentioned above.
Thank you!
In that case, for installation of a program like Gmail.apk or Maps.apk, would be as simple as adding the .apk to the /system/app, or would I have to include other files? Would there be dependancies in other folders?
Well the apps have their own data folder on the data partition, but this is for storing changes in settings and so on, and it should be created by the app itself on first boot just like right after you wipe the data partition/factory reset
Thanks..Got some mod modding to do!
So in case I'd want to manually uninstall/manually install an apk, what would be the steps I'd have to go through?
Would there be filesystem config files (like the older Windows versions), or a central database of entries of the likes of the Registry tables of newer Windows? How does Android go about installing a file? Like which folders and files would be modified other than /system/app and /data/app? Any common files with entries? And in case of the latter, whether it would be machine readable or plain text?
guys how can i put a bunch of applications in a zip folder a flash it by recovery.Ive tried putting 3 apps in a zip folder and flshing it via recovery but it says failed..
I tried that a while ago on the g1 with mixed results.
You have to put them in the data/app/ folder the same way they appear on your phone. If you are feeling ambitious, you can also grab the corresponding folder in data/data. You'll have to look for the java package name, not the app name. Lastly, you have to adjust the updater-script in META-INF/com/google/android/ to mount and flash the data folder, not system and then clean out the extra cruft.
You might have to resign the zip or just toggle sig checks.
Other options include using recovery to restore the data partition, but this will be everything, not just your 3 favorite apps. Alternatively, you could write a script that runs from your PC while your phone is in recovery and use the "adb install" command. I think there are also apps that do that for you, such as Titanium backup.
Gee one thanks for the reply but can you plz reexplain "If you are feeling ambitious, you can also grab the corresponding folder in data/data. You'll have to look for the java package name, not the app name. Lastly, you have to adjust the updater-script in META-INF/com/google/android/ to mount and flash the data folder, not system and then clean out the extra cruft.
You might have to resign the zip or just toggle sig checks."
Your phone stores the app in data/app/some.java.name.here so if you use flash those files, your apps will be installed. The app itself stores settings, history, etc in data/data/some.java.name.here If you flash the corresponding folder in data/data, you'll also get all your settings and won't have to bother setting it all up from scratch.
If you use adb or a file explorer to poke around in your data/data and data/app folders, you'll see what I mean.
In order to get the zip to flash, you have to include "instructions" that tell the recovery what to do with the zip. Unzip one of the flashable roms and look in the META-INF/com/google/android folder. There should be two files there. You want to edit the updater-script so that it flashes your data. Most likely, it is set up to flash a custom rom to your system folder. You'll have to do some editing and some trial and error to figure it out, but if you are just flashing the data partition, most of the commands in updater-script will be superfluous.
Lastly, and this the part that everyone hates (second only to adding adb to your path), you either have to sign the zip with jarsigner, signapk, or something similar, or turn off signature checking in your recovery. Signing the zip is essentially adding a digital signature so that your phone knows that the zip is intact. Clockworkmod recovery will let you toggle the signature checks in one of the options- poke around and get familiar with your recovery. It's probably in there somewhere.
I think Titanium backup will let you freeze/unfreeze apps- you might want to consider it.
Thanks
Sent from my HTC Vision using xda premium
Did this work? Like to buy a beer for someone who wants to upload a zip with a file explorer all for a project I have that has no play store or file explorer on it. Thank you
*Pretty please make a NANDROID backup before you do this. I know you just recently installed the ROM, so if you don't have much on there and don't mind to flash in the event that something goes wrong, then no worries. Still, it wouldn't hurt!!*
Basically, what we are doing here, is giving you the app, installing it on the phone and then copying the APK file from /data/app to /system/app. I don't know much about the Fassy, but the file system structure should be close.
There are two ways to do this. You can use ADB to execute the commands, or use a file explorer (I use Root Explorer) to move the APK file. I also picked a free APN app .
APN Manager Pro
Throw this on your external SD card. Once you have it on there, open up your File Manager.
Navigate to your external SD card(should be /mnt/sdcard/external_sd or something similar, we have already established our phones are slightly different, ha ha).
Find the file ale.android.apnmanagerwithanimation-1.apk and long press it. You should get a list of options. You want to select move.
Navigate back to your root directory.
Go to /system/app. Once you get there, depending on your file manager, you should have the option to set the permissions as r/w (read/write). By default, Root Explorer is always set to r/o (read only) on my phone.
Paste the APK file.
Long press the APK file and select permissions.
- You have three sets of privileges: Read/Write/Execute
- You have three sets of groups: Owner/Group/Others
- - Make sure Owner, Group and Others have checks under Read.
- - Make sure Owner has checks under Write.
- - There should not be any checks under Execute.
- - There should not be any checks on any of the special permissions.
Hit OK.
Click on the APK file and select install.
Once the install has completed (should be almost instantly) reboot the phone.
Now you have an app that is capable of setting APN information.
When the phone has booted back up, open the app and select Backup & Restore. Make a backup. If the new APN doesn't work properly, you will have a backup you can fallback to.
Enter the information and hit save. Once you have done that you can select the APN and set it as the main. If you lose functions then restore the backup.
I hope this works out!!
What's the information u have to input?
jaysmi32 said:
What's the information u have to input?
Click to expand...
Click to collapse
what company do you need the info for
Boost mobile!
This is a simple guide to make your own custom rom……..(the other parts will be written…as soon as I become bothered to type for hours again)
PART 1:setup the kitchen and rom
1.Download java(java.com) and install the java JDK(www.oracle.com/technetwork/java/javase/downloads/index.html)
2.Download the kitchen(http://forum.xda-developers.com/showthread.php?t=633246) (thankyou DSIXDA for your amazing kitchen)
3.Download Cygwin(Cygwin.com)
3.extract the cygwin file(using winzip or winrar) in C drive only….dont put it into any folders
a.Enter a file called Cygwin(setup file)
b.click next>install from local directory
c.now it will ask you where to put the program….leave everything as default
d.now It will ask you where the location of the packages are so>click browse>click my computer >go to drive C>and you will fin the folder Cygwin-packages>so select that folder and click ok>next.
e.now it will extract the folders>a promt is going to pop up..>click ok
f.now you will see a list>go to the first line and you will see next to the word ALL ,two arrows>click on them so all files can be installed.
g.now it will install the program whick take from 5-10min.
h.when its done …select finish.
i.you can now delete the setup file and Cygwin-packages folder.
j.now enter the Cygwin program and it will create some files..>when its done exit the program….
Now Cygwin program is done installing .
3.To use the kitchen:
a.Enter Cygwin folder>home>your user name>so you will find 3 files
b.in the same folder>extract the kitchen zip file(Android-Kitchen-master.zip)
c.now enter the kitchen folder>you will find a folder called>put rom here.
d.so in that folder>either put a rom.zip file or put a system.img file if you want complete stock…..(which you get from the ruu of your phone)
e.now enter tools folder>edifly_......(something like that) and see if you mount points are in it…
f.to know go to your build.prop file>check ro.product.device>and if you see a txt file under the name of your device …..your device is supported…
g.if NOT,go to the original thread …where the dev has stated a way on how to add your device…..
Now we are done from the setup of the kitchen…..
To use the kitchen:
1.Enter Cygwin
2.type
a.cd kitchen>press enter
b. ./menu>press enter
Now a list of options will come infront of you ……
3.go to the option>setup working folder>enter its number and press enter…
4.now if you go to Cygwin folder >enter home>user name>kitchen.
5.you will find a folder called(working folder_8254897)
NOW YOU ARE DONE WITH SETTING UP THE KITCHEN……AND YOU CAN START PLAYING WITH THE ROM
PART 2:Clearing up the options
Explanation for each option:
1.creates you a working folder,which extracts the rom for you.
2. It gives you super user access aka SU, Some apps require root to work properly….so if your rom isn’t rooted … it’ll be useless.
3. Busy Box is something that you install on your phone to give you some additional handy LINUX / UNIX based commands. You need Busy Box installed because some commands are not available to you and you made need them for some root level tasks.
4.To disable sounds while phone is booting
5.To add you a tethering app…..and allow you do wireless tethering
6. Zipalign is an archive alignment tool. It optimizes the way an app is packaged. Doing so enables the operating system to interact with the application more efficiently, and has the potential to make the application and overall the whole system much faster. Execution time is minimized for zipaligned applications, resulting in a lower amount of RAM consumption when running the app.
7.If you want the rom to do a FULL WIPE while installing the rom
8.To change the name of the rom
9.Checks if the update script contains any errors….because if it did the rom wont be installed correctly,which may lead to a brick
10.To see all information about your rom..ex: if you have root access/if you aren’t using stock kernel/if you have app2sd support etc..
11. Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
12.To add a task killer….which closes applications to free RAM
13.To add a /data/app folder so applications could be installed their rather than getting installed in system/app
14.To add text editor…for ex.if you want to edit build.prop or any txt file which is in system.
15.To add a command shell which allows you to use in in the terminal
16.To give the option of moving applications to sd card
17. To add /etc/init.d scripts support ….which allow you to add tweaks and stuff for the phone
18.To allow user to put the boot-animation that he desires.
19.To be able to extract the boot.img(kernel)
20.To extract data.img (which I don’t know what it is )
21.check this (http://developer.android.com/tools/publishing/app-signing.html)
22.To covert update script to updater script which is a must before you build the rom.
99.To build the rom when you finish editing and modding.
PART 3:How to mod apks
OK SO NOW SINCE YOU KNOW WHAT EACH OPTION DOES…..LETS START MODDING,and to start customizing,you have to use an apk extractor and zipper because the apks contain all the treasure …..for example:SystemUI.apk(contains battery icons ,signal icons, the location of the clock and many many more things)
So what were gonna use is apk manager,which is an very easy program to use,and helps a lot in apk extracting and zipping and signing.
Here are the steps to use it:
1.Extract the zip file(apk manager)
2.youll find a file called setup>enter it and select option 3 and press enter.
3.folders will be created
4.so to extract an apk>select an apk file and drop it into the folder (put apk here)
5.go into script file>press enter file>and after you’ve put the apk file in the specified folder>select option 2 >so the apk will be extracted
6.after you extract it you will find the extracted files it in the same folder(put apk here) in a new folder under the name of the apk file.
7.edit whatever you want
8.When you finish >select option 3>press enter.
9.then select option 5 and 6 to sign and zipalign the apk…..
And your done ,but to find the modded apk…..go into place apk here for signing and you will find it there.
.........................
RESERVVED
Reserved45
RESE8VED
Hayde reserved yaben 3amme
W hayde kamen yaben 5alte....................reserved
Sorry need help....
donhashem.dh said:
.........................
Click to expand...
Click to collapse
Hey dude/*****.....
Me again and loving yr tutorial. But do have a couple of questions that I hope you can help with.
Firstly the update version of Cygwin menu is not exactly as yours in the tutorial. Why is the allow Tethering function not there and could this be a problem.
Secondly i am nooooooB and are unsure on how to add remove system apk's from rom. Do I just dig in and delete them from windows. And can I pull apk's from another rom to put into the data app folder which was created using Cygwin.
I was wanting to add aroma installer as well but another story....
Really appreciate if you can advise. If I sound to noooobish then understrand that I am to much work.
veroby said:
Hey dude/*****.....
Me again and loving yr tutorial. But do have a couple of questions that I hope you can help with.
Firstly the update version of Cygwin menu is not exactly as yours in the tutorial. Why is the allow Tethering function not there and could this be a problem.
Secondly i am nooooooB and are unsure on how to add remove system apk's from rom. Do I just dig in and delete them from windows. And can I pull apk's from another rom to put into the data app folder which was created using Cygwin.
I was wanting to add aroma installer as well but another story....
Really appreciate if you can advise. If I sound to noooobish then understrand that I am to much work.
Click to expand...
Click to collapse
Ayyy take it easy cun*
I'll update the tutorial because I made it from a long time and posted it now
For the apks you just enter the rom.zip system>app and you'll find all the apks there..
The data folder cygwin creates is that when you use the Rom ..the apps won't be installed in system>app anymore,they will be installed the folder the kitchen created data
And for the aroma installer,leave it for later ...your still not ready for it ...
no signature....problem ?!?!?!
donhashem.dh said:
Ayyy take it easy cun*
I'll update the tutorial because I made it from a long time and posted it now
For the apks you just enter the rom.zip system>app and you'll find all the apks there..
The data folder cygwin creates is that when you use the Rom ..the apps won't be installed in system>app anymore,they will be installed the folder the kitchen created data
And for the aroma installer,leave it for later ...your still not ready for it ...
no signature....problem ?!?!?!
Click to expand...
Click to collapse
I was going to ask you about signature but didnt want to over do it. I am guessing you need to sign it after the 99 - Build ROM from working folder?
I have proceed with the Build rom and are at the recomend to sign rom stage. Its some thing I dont understand. Is it ok to proceed without?
Cool I have noticed the roms produced by dev's here xda are not signed so doesnt seem to matter for this purpose. I have hit thx ***** 5 or 6 times.
I will hit 500 s****y if you give share some knowledge in installing arroma installer. or do you recomend just trying things....cheers anyway its been awsome.....:good:
XDA member @jeff_kz released NookManager back in 2012 and many grateful people have used it to root their devices and make backups. It's still a great piece of software but a little dust has settled on it and the NST/G has moved on to FW 1.2.2 which NookManager can't handle in its default condition.
I have updated NookManager so that it will work with FW 1.2.2 and have also made a few other updates and changes, hopefully resulting in a slightly better experience. This update also works for FW 1.2.1 if you have some reason to retain it.
Changes in NookManager
Changes in apps
"Classic" version
-updated the old ReLaunch 1.3.8 to ReLaunchX 2.1.5 from F-Droid
-removed the defunct Amazon App Store
-added Opera Mini 7.6.40125
"Traditional" version
-removed ReLaunch 1.3.8
-removed defunct Amazon App Store
-added Opera Mini 7.6.40125
-added ADW Launcher 1.3.3.9
-added ES File Explorer 1.6.2.3
"Stealth" version
-updated the old ReLaunch 1.3.8 to ReLaunchX 2.1.5 from F-Droid (this is a temporary app which you will uninstall eventually)
-removed the defunct Amazon App Store
-added Opera Mini 7.6.40125
-added ES File Explorer 1.6.2.3
-added MIUI App Drawer 1.5.1
Changes in rooting process
-updates the file /system/etc/security/cacerts.bks with a more current version
-removes the three junk apps: Browser, Gallery, Music (they don't work)
Changes in function
"Disable B&N apps" has been reworked. In the original version this option essentially gutted /system/app but it did not address the residual B&N jar files which continue to stir up activity in the system and lower battery charge life. Meanwhile some standard Android stuff in /system/app was thrown out as well. Some of those files are needed for other things people might want to do. So I have scaled back the purge to only the B&N apps and jars. This option is for people who want to build their own interface and completely abandon the stock home, reader, library, dictionary, etc. Surprisingly the Quicknav button system survives this exorcism, although their target functions have been removed. They can be assigned other functions with NTMM.
The change is non-destructive as the apps and jars are simply moved into "disabled" folders. So if you get buyers remorse the option to "Enable B&N apps" moves everything back where it belongs and deletes the "disabled" folders.
Other changes
-replaced the patched 1.2.1 jars with patched 1.2.2 jars (required for Nook Touch Mod Manager app)
Note: for those with non-US firmware, the "simplest" route to a fully functioning NST/G is to flash US firmware (https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion) [alternate download: https://www.mediafire.com/file/tipfqtwevr5i90q/nook_region_changer.zip/file], at the setup screen attach your device to your PC via USB. 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) and transfer it to your NST/G. Either eject the NST or just let it alone until it goes to sleep. During that time the update will take place. Although you may not want to purchase books from B&N, the shortest path to a stable, non-complaining device is to register fully updated firmware. For other options with non-US devices, including an unofficial 1.2.2 UK update, see here: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/
Getting it done!
Follow the directions in the original NookManager thread, substituting one of the three images I have provided below.
NookManager Classic (download) MD5: d3a90a8a473d635f93f3b7d2feb9b177
This is the closest to the original version, with an updated ReLaunchX (a combination launcher and file manager expressly made for e-ink readers) and the added Opera Mini. Note that ReLaunchX does not offer root access so any manipulation of files at the system level must be done via ADB or with yet another file manager app.
NookManager Traditional (download) MD5: 71722794f4186be7769b74f1d70ae194
This offers a more typical Android experience with a regular launcher and a separate file manager (with root access). Both ADW Launcher and ES File Explorer are less than ideal visually for the NST out-of-the-box. For that reason the zip includes basic configuration files for both apps as well as instructions for applying them.
NookManager Stealth (download) MD5: 23371cad76ec8b05a1e0c0b7c8754720
This combination is for the person who really is content with the B&N overlay but wants to run "just a few" apps occasionally. ReLaunchX is installed initially only to allow manipulation of apps while configuration is done. Then it is to be uninstalled. The MIUI App Drawer is only an app drawer, not a launcher. Nook Touch Mod Manager is used to assign the App Drawer to a hardware button press or long-press. ES File Explorer is also installed to allow easy file manipulation (and root access). To the casual observer, this configuration looks and behaves like a stock NST--until the secret button is pressed. The zip contains a configuration file for ES File Explorer as well as instructions for setting up the App Drawer.
I have tested these image files repeatedly on a device running registered FW 1.2.2.
If you would like to further customize NookManager to meet your personal requirements there are instructions for changing the app complement in post #2 below.
As always, Make A Backup before you try anything with your NookManager card.
"I don't need no stinkin' backup". Au contraire. No one has a device with hard-baked FW 1.2.2. If you have to go back....you'll end up back at 1.2.1 or 1.1.5 or.... If you have a non-US device it will be even worse. So a backup of non-rooted and registered FW 1.2.2 will save you time and trouble in the end. NookManager makes it so easy. Did you know that if you connect your NST/G to your PC via USB while NookManager is running, the invisible NookBackup partition becomes visible and you can copy any backups to your PC? I keep a few with notes so I can return to a working configuration if I mess things up (or just change my mind). Backup, Backup, Backup.
Tips:
1. Superuser is a small nuisance because it wants to tell you each time an app accesses root. You can stop this alert by going into its Settings and unchecking Notifications. You'll still get a first-time permission prompt, but not the "there s/he goes again" one. If SU is being a super pain and refuses to even open when you tap on the app icon, navigate to /data/data/com.noshufou.android.su/shared_prefs and delete the xml file inside. Then try accessing the app again. That generally frightens it into submission.
2. If you use the B&N system but don't use "Nook Community" you can stop this nagware from spitting out little notifications all the time. Using a file manager with root access, go to /system/app and locate NookCommunity.apk. Rename it NookCommunity.apk.bak. Voila! This doesn't seem to upset the rest of the B&N system at all.
Customizing NookManager
In the original NookManager, a few basic apps were installed. The idea was to keep things simple and let people decide afterwards if they wanted other things. I've tried to keep to that concept with the three packages in the first post but maybe you'd like a base root/install to always include app "x". How to achieve this?
Here's an example of how to make a customization:
Note: to make these changes you should use a good text editor like Notepad++. Windows users can probably get away with Notepad, but NOT Wordpad.
1. On your NookManager SD card copy the app you'd like to include to files/data/app.
2. Find the folder "scripts". Every app that is installed has a little file there, for example "install_opera_mini". Make a copy of the file and rename it so that it reads something like:
install_yourapp (substitute the name of the app you are going to install--no spaces)
Then edit the file, changing the name of the apk file in the first line to exactly match the filename of the apk file you have placed in files/data/app
Below that, edit the little completion phrase that displays on the screen that the app has been installed. You don't have to match text. It's just a message, so something like
echo "My App installed" (substitute the name of the app you are installing)
would be fine. Save the file.
3. Locate the file scripts/do_root and edit it to reflect whatever change you have made. You'll see the "install_x" files listed in there. Make a copy of any of these and rename it ("install_yourapp"--use the same name as in step 2). Order does not matter in the list so if you add something new, just keep the app install files together. Save the file.
Every app change can be handled in the same way.
An afterthought
Opera Mobile used to be my go-to Browser and it does still have some useful features which Opera Mini lacks. But for casual browsing with fewer errors, I now recommend Opera Mini. However, if you'd like to install Opera Mobile as well, the original app needs resigning to work with FW 1.2.2 for some reason. After installation you should make the changes needed for TLS 1.2 compliance. That doesn't mean it will access every site successfully. Some are simply too complex for it or the overall SSL compliance of the device and the app are just not up-to-date enough. I've attached a copy of the resigned app below. Easiest to just side-load it.
Hi,
There's a typo above. Please let me know if I am wrong about what the correct path should be:
nmyshkin said:
Cacerts.bks update...
...2. Copy whichever updated cacerts.bks file you choose from the two mentioned above into files/etc/security
Click to expand...
Click to collapse
should be
...2. Copy whichever updated cacerts.bks file you choose from the two mentioned above into files/system/etc/security
Click to expand...
Click to collapse
gggirlgeek said:
Hi,
There's a typo above. Please let me know if I am wrong about what the correct path should be.
Click to expand...
Click to collapse
Oops! Thanks for catching my mistake. I have made the correction in the instructions.
Mea culpa
When I put together the update package for NookManager I just assumed that the patched jars for FW 1.2.1 (android.policy.jar and services.jar) that were used to enable NookTouchModManager would be the same for FW 1.2.2. And, in fact, I've not had any issues yet.
But in tracking down an, as it now turns out, unrelated issue, I had cause to look more closely at the jars from the two firmwares. They are very close, but not identical. This made me a little nervous because I don't want to mess up peoples' devices
So, with guidance from @Renate NST I have patched the jars from FW 1.2.2. These can now be found at the attachment section of the first post in this thread.
The good news is that you can just "hot swap" these files:
Code:
adb push android.policy.jar /system/framework/
adb push services.jar /system/framework/
After I had done that I deleted the dalvik-cache files for the same two jars (found in /data/dalvik-cache near the end of the listings), and then completely shut down. Boot on powering up is alarmingly slow, but it does happen and then everything is back to normal.
As always, you might want to make a back-up first if doing this makes you a little nervous. Or, you could just ignore the whole thing. It may not matter.
Changes added to first post.
deleted
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
sany said:
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?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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.
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?
Click to expand...
Click to collapse
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!
nmyshkin said:
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.
Click to expand...
Click to collapse
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
sany said:
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
Click to expand...
Click to collapse
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.
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
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
sany said:
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
Click to expand...
Click to collapse
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.
nmyshkin said:
XDA member @jeff_kz released NookManager back in 2012 and many grateful people have used it to root their devices and make backups. It's still a great piece of software but a little dust has settled on it and the NST/G has moved on to FW 1.2.2 which NookManager can't handle in its default condition.
I've addressed a number of issues with NookManager in separate posts but I think it's time to pull it all together in one place and offer some suggestions not only for updating the software but also doing a little customization. The information on customization is partly available in the files of NookManager itself and also on the GitHub links given in the original posting, but it can be a little intimidating (it was to me at first) so I'll offer a few simple examples and files.
Click to expand...
Click to collapse
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.
PixieD said:
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.
Click to expand...
Click to collapse
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.
nmyshkin said:
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.
Click to expand...
Click to collapse
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!
PixieD said:
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!
Click to expand...
Click to collapse
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.
Thanks to @nmyshkin 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.
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.
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?