Related
if i edit my build.prop with astro, on a reboot the changes are lost, the file is marked r-w, so something altering it on bootup, anybody know where the source comes from??
Download Root Explorer and use that. Trust.
tried that, it keeps getting overwritten with some king of backup.
mallard729 said:
tried that, it keeps getting overwritten with some king of backup.
Click to expand...
Click to collapse
If that's the case, then it's a problem specific to the ROM. I haven't tried it on my TP2 but it worked flawlessly on my G1.
Lemme take a look once I get a second.
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
norpan111 said:
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
Click to expand...
Click to collapse
Because it does not excist in winmo. It only excists in android.
I tried Root Explorer and it workers . I use latest froyo build with lower incall volume kernel .
Can somebody tell me when I delete apps in system/apps folder I delete from data.img or from system.ext2 ?
Same here, I change my build.prop file or replace it and it gets overwritten.
Using the build.prop for protected apps but can't get it to stay.
I am using the latest BLAZEN build from PPCGEEKS/Reefer.
Being an Ext2 file instead of sqsh I figure this would have worked flawless.
I'd really like to download logmein, gbahours, paypal and a few other protected apps. I can't without fixing this build.prop file....
OR
Find some way to get a working fingerprint Google has already approved.
Glad to see I'm not the only one looking into this I have the same problem in my android OS - different phone, but same custom OS. Hopefully this thread won't die - if I ever figure it out I'll be sure to post here as well
AOSP is still too buggy for me on our device but I despise the Samsung dialer and contacts and was wondering if anyone can help provide the steps to get the AOSP dialer onto a TouchWiz rom like in this rom: http://forum.xda-developers.com/showthread.php?t=2170142
Do you just need to push an app to system/apps or is it more complicated?
Thanks.
I was wondering the same thing but I also wanted to add the email program too.
Sent from my SPH-L900 using xda premium
jamice4u said:
I was wondering the same thing but I also wanted to add the email program too.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
For email, copy the exchage.apk and email.apk from aosp and paste to system/app. You will have to remove samsung email and exchange to make it work. I use aosp email and mms on touchwiz roms.
nikonx said:
AOSP is still too buggy for me on our device but I despise the Samsung dialer and contacts and was wondering if anyone can help provide the steps to get the AOSP dialer onto a TouchWiz rom like in this rom: http://forum.xda-developers.com/showthread.php?t=2170142
Do you just need to push an app to system/apps or is it more complicated?
Thanks.
Click to expand...
Click to collapse
I tried that rom, but it's a little buggy for me. I would like to get the aosp dialer and contacts into another rom but can't figure it out.
I used 7zip to open up the NoWizAOSP rom, and dug into "system\app\" but I see no phone.
I see:
phoneerrservice.apk
phoneinfo.apk
phonesky.apk
secphone.apk
I do see contacts.apk - so I'm guessing that's the one I want for the contacts.... help!!
Phone is Contacts.apk the actual dialer is in phone.apk
---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------
You will probably want contactsprovider.apk or whatever it is as well.
shiftr182 said:
Phone is Contacts.apk the actual dialer is in phone.apk
---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------
You will probably want contactsprovider.apk or whatever it is as well.
Click to expand...
Click to collapse
So which stock samsung phone related things would you remove to make this work?
nikonx said:
So which stock samsung phone related things would you remove to make this work?
Click to expand...
Click to collapse
All the sec.....apk crap (anything that has to do with contacts or phone and if there is already a contactprovider.apk of some sort.)
Ok, so after playing around for a bit here's what worked for me (I only did the contacts since I wanted the "Send to Voicemail" option that AOSP offers).
I take no responsibility for your fat fingers or my mental illnesses which may have made me miss a few steps
DO NOT FLASH the zip in recovery!!!! You must extract the files!!!
must be rooted
These instructions are specifically for Macksrom, but I imagine with a little research one could get this to work on other ROMs..
back up your stuff - nandroid
using a root explorer (I use ES file explorer) navigate to /system/app/
rename: (done by long pressing on the file and scrolling down to rename)
contacts.apk -> contacts.apk.old
contactsprovider.apk -> contactsprovider.apk.old
seccontactsprovider.apk -> seccontactsprovider.apk.old
(this is a fail safe - if you have to, just rename the .apk.old back to .apk)
extract the zip file I attached (for some reason there's t- take the three files and push them to /system/app/
after they are in that directory, then for each file you must change permissions (long press file, scroll down to properties - click change)
rw
r
r
reboot - profit
you may have to bring from your app drawer the contacts (which is called "People") to your dock or wherever you want it to be.
altimuh said:
Ok, so after playing around for a bit here's what worked for me (I only did the contacts since I wanted the "Send to Voicemail" option that AOSP offers).
I take no responsibility for your fat fingers or my mental illnesses which may have made me miss a few steps
DO NOT FLASH the zip in recovery!!!! You must extract the files!!!
must be rooted
back up your stuff - nandroid
using a root explorer (I use ES file explorer) navigate to /system/app/
rename: (done by long pressing on the file and scrolling down to rename)
contacts.apk -> contacts.apk.old
contactsprovider.apk -> contactsprovider.apk.old
seccontactsprovider.apk -> seccontactsprovider.apk.old
(this is a fail safe - if you have to, just rename the .apk.old back to .apk)
extract the zip file I attached (for some reason there's t- take the three files and push them to /system/app/
after they are in that directory, then for each file you must change permissions (long press file, scroll down to properties - click change)
rw
r
r
reboot - profit
you may have to bring from your app drawer the contacts (which is called "People") to your dock or wherever you want it to be.
Click to expand...
Click to collapse
These directions are incomplete or innacurate because the 3 files you say to remain don't all exist in stock touch wiz... I gave it a shot anyways and ended up with no cellular service. Restoring to backup.
nikonx said:
These directions are incomplete or innacurate because the 3 files you say to remain don't all exist in stock touch wiz... I gave it a shot anyways and ended up with no cellular service. Restoring to backup.
Click to expand...
Click to collapse
I apologize - I failed to state that I was running Macksrom. I edited my post for other people, but I'm glad u made a backup.
What files do u have in system/app/ that relate in any form to "contacts"?
Install the AOSP touch wiz Rom. Problem solved.
Sent from my SPH-L900 using xda premium
jamice4u said:
Install the AOSP touch wiz Rom. Problem solved.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I love useless answers like that!!!!!
nikonx said:
I love useless answers like that!!!!!
Click to expand...
Click to collapse
The people who worked on the The NoTouchWizAOSPMOD already did all the work and they put all of AOSP stock apps into the Rom. You could PM the guy in the OP and of that Rom thread and maybe he will tell you how he did it. I personally think it is a waste of time and it would be faster if you just flashed his Rom.
At least I gave an answer all you did was troll my response.
Sent from my SPH-L900 using xda premium
rather dated thread but I figured I'd chime in.
I do realize this is for the note 2, but I have an epic 4g touch, so I doubt this would work on mine, but I'm curious, I've been looking for a way to get the aosp dialer & contacts on my epic 4g touch, and I have looked for this NoTouchWizAOSPMOD your referring to and can't seem to find anything, would it be possible to provide a link?
Also for my phone I have no contacts.apk or contactsprovider.apk, mine are SecContactsProvider.apk, SecContacts.apk that's the only 2 I see.
Not sure if this would be beneficial for anyone or not I just thought I'd throw it out there.
altimuh said:
Ok, so after playing around for a bit here's what worked for me (I only did the contacts since I wanted the "Send to Voicemail" option that AOSP offers).
I take no responsibility for your fat fingers or my mental illnesses which may have made me miss a few steps
DO NOT FLASH the zip in recovery!!!! You must extract the files!!!
must be rooted
These instructions are specifically for Macksrom, but I imagine with a little research one could get this to work on other ROMs..
back up your stuff - nandroid
using a root explorer (I use ES file explorer) navigate to /system/app/
rename: (done by long pressing on the file and scrolling down to rename)
contacts.apk -> contacts.apk.old
contactsprovider.apk -> contactsprovider.apk.old
seccontactsprovider.apk -> seccontactsprovider.apk.old
(this is a fail safe - if you have to, just rename the .apk.old back to .apk)
extract the zip file I attached (for some reason there's t- take the three files and push them to /system/app/
after they are in that directory, then for each file you must change permissions (long press file, scroll down to properties - click change)
rw
r
r
reboot - profit
you may have to bring from your app drawer the contacts (which is called "People") to your dock or wherever you want it to be.
Click to expand...
Click to collapse
Thank you a lot...
I know that this post is too old but I tried it on my Samsung Galaxy Young DUOS running stock jellybean 4.1.2, I removed SecContacts.apk and installed contacts.apk from your file and its working flawlessly.
Hi.. I've currently got my DHD rooted and running an Oxylite ROM, no problems with that it works beautifully, and i also have ROM toolbox pro installed to give me a bit more management and tweaks.. Now i'm new to bootanimations and have had a bit of a read before trying anything and it seems very straightforward to install, however, when i try to, it never works even though i'm following all the steps.
Now when i load one of the pre-installed boot animations within the toolbox pro, it works perfectly everytime.. However, when i try and install one of my own i have no luck at all..
So far i've made sure i do the following, is there anything i'm missing??
I make sure the folder is changed to R/W, i then put the bootanimation.zip file into the Data/Local directory, i know some say System/Media, but not mine because this is where the toolbox pro ones go, i've checked.. I've also tried installing into System/Media too, no joy there either..
Now when i delete the previous bootanimation (the one from toolbox pro) i've noticed it leaves a tmp directory behind as i'm only deleting the zip file, do i need to delete that too? Is it storing previous information and causing a conflict perhaps??
What could i be doing wrong if this isn't the case??
RyanH77 said:
Hi.. I've currently got my DHD rooted and running an Oxylite ROM, no problems with that it works beautifully, and i also have ROM toolbox pro installed to give me a bit more management and tweaks.. Now i'm new to bootanimations and have had a bit of a read before trying anything and it seems very straightforward to install, however, when i try to, it never works even though i'm following all the steps.
Now when i load one of the pre-installed boot animations within the toolbox pro, it works perfectly everytime.. However, when i try and install one of my own i have no luck at all..
So far i've made sure i do the following, is there anything i'm missing??
I make sure the folder is changed to R/W, i then put the bootanimation.zip file into the Data/Local directory, i know some say System/Media, but not mine because this is where the toolbox pro ones go, i've checked.. I've also tried installing into System/Media too, no joy there either..
Now when i delete the previous bootanimation (the one from toolbox pro) i've noticed it leaves a tmp directory behind as i'm only deleting the zip file, do i need to delete that too? Is it storing previous information and causing a conflict perhaps??
What could i be doing wrong if this isn't the case??
Click to expand...
Click to collapse
Just put the bootanimation.zip on your SD Card & use the local option in ROM Toolbox Pro
GuyInTheCorner said:
Just put the bootanimation.zip on your SD Card & use the local option in ROM Toolbox Pro
Click to expand...
Click to collapse
That IS how i've been doing it!! It still wont let me, it gives me some waffle about ROM toolbox not being able to open it and needing to open Clockwordmod in recovery.. Which i then do and it still won't acknowledge the zip.. Keeps throwing up installation aborted..
RyanH77 said:
That IS how i've been doing it!! It still wont let me, it gives me some waffle about ROM toolbox not being able to open it and needing to open Clockwordmod in recovery.. Which i then do and it still won't acknowledge the zip.. Keeps throwing up installation aborted..
Click to expand...
Click to collapse
Trying using this app here it seems to have alot of the same Boot animations and it never gives me a problem
UPDATE:
Also after updated to latest rbox prerooted rom i could install settings.apk.
/system/priv-app/Settings/Settings.apk chmod 644
Other things installed were busybox / xposed / daydream/Deskclock for changing picture screensaver to normal clock.
Due to the fact it is not in recent apps u might start it via firestarter or es file explorer.
please reply to this post if someone else has managed to get this also working.
--------------------------------------------------
For all that want to use the native Settings.apk.
just install this one:
put settings.apk somewhere on your sdcard. use any desired filemanager (i prefer es file manager) just klick on it and then on the button install.
it should work and visible in my apps and firestarter.
https://drive.google.com/file/d/0B3ZgrYnbvHpSRzhiRmNNVHE0ck0/view?usp=sharing
Screenshots in post #5
I'm also working in getting the old Wallpaper back like on old ftv.
Stay tuned.
Greetings
schybiorz
So how do you get this working then? Or have you just put this up randomly without testing or explaining the process? Cause I've tried pushing to all sorts of places & even resigned the apk but still as per usual nothing happening or even showing in the appsame section?
just copied it with es filemanager from sd card to System/priv-app changed permission and open it via firestarter.
also i tried about 8 different ones till i got the working one from custom nvidia shield 5.1 rom working.
only audio/language and developer menue wont open.
but i installed basic dreams and got rid off the wallpaper screensaver and replaced by clock.
schybiorz said:
just copied it with es filemanager from sd card to System/priv-app changed permission and open it via firestarter.
also i tried about 8 different ones till i got the working one from custom nvidia shield 5.1 rom working.
only audio/language and developer menue wont open.
but i installed basic dreams and got rid off the wallpaper screensaver and replaced by clock.
Click to expand...
Click to collapse
Ok.... What permissions you using?
Sent from my SM-G900F using Tapatalk
---------- Post added at 08:11 PM ---------- Previous post was at 07:40 PM ----------
I can't even see the settings app In firestarter? I've tried signing the apk, not signing it? Putting it in various different locations, & even putting it in a folder? Can you not give us more info?
I'm rooted on rboxs prerooted 5.0.5 r4 & have xposed & have googleplay running too if any of that makes any difference?
Sent from my SM-G900F using Tapatalk
u can also just go onto your sdcard and install as normal app. should work.
it should be visible in firestarter as settings. even visible in app library.
See screenshots
Also i'm on latest rbox prerooted 5.0.5 r4 & have xposed & have googleplay running too.
If you don't mind could you tell me if its in a folder & the name of the folder & what's the name of the settings app & what are the permissions set at? Cause this is bugging me now?
Sent from my SM-G900F using Tapatalk
hi,
just download my settings.apk from google drive (unzip it) put it on your sd card.
use es file explorer navigate to your sdcard and just klick on it and then install.
it should work and install. sry that i can't u help more, couse u might know how to install any apk. nothing more did i.
version number of my settings.apk is visible on screenshot in post 5
schybiorz said:
hi,
just download my settings.apk from google drive (unzip it) put it on your sd card.
use es file explorer navigate to your sdcard and just klick on it and then install.
it should work and install. sry that i can't u help more, couse u might know how to install any apk. nothing more did i.
version number of my settings.apk is visible on screenshot in post 5
Click to expand...
Click to collapse
mine won't install at all just says - app not installed? No one else has said they got it working yet ether? Very strange
Sent from my SM-G900F using Tapatalk
that's really strange.
i also installed some other standard rom stuff, but i can't imagine that someof them might be needed before installing settings.apk
but these things from stock i also installed:
Basic dream
deskclock
livewallpaper
livewallpaperpicker
launcher2
i'm also trying to get normal systemui.apk working, cause amazon has build their own AFTVSystemUI.apk as i see.
deanr1977 said:
mine won't install at all just says - app not installed? No one else has said they got it working yet ether? Very strange
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
schybiorz said:
that's really strange.
i also installed some other standard rom stuff, but i can't imagine that someof them might be needed before installing settings.apk
but these things from stock i also installed:
Basic dream
deskclock
livewallpaper
livewallpaperpicker
launcher2
i'm also trying to get normal systemui.apk working, cause amazon has build their own AFTVSystemUI.apk as i see.
Click to expand...
Click to collapse
If you wouldn't mind if you have time could you pull the apk from your system & pm me a link just incase It got messed up via downloading? With the permissions & file location it was installed to? I think it was put in system/priv-app location.
Sent from my SM-G900F using Tapatalk
u have busybox installed?
updated today to latest rbox pre rooted.
reinstalled xposed and busybox.
put settings filder in system/priv-app
changed to rw-r-r permission.
rebooted and installed settings apk (once again) via click on it then install.
due to the fact i havent install firestarter till now. settings apk can also be opened via es file explorer -> local-> apps
it should work.
pleasy reply
schybiorz said:
u have busybox installed?
updated today to latest rbox pre rooted.
reinstalled xposed and busybox.
put settings filder in system/priv-app
changed to rw-r-r permission.
rebooted and installed settings apk (once again) via click on it then install.
due to the fact i havent install firestarter till now. settings apk can also be opened via es file explorer -> local-> apps
it should work.
pleasy reply
Click to expand...
Click to collapse
Still no go, I also made the jump to 5.0.5.1 this morning, reinstalled xposed too, & busybox, I made a folder called Settings in /system/priv-app/ then changed The permissions of the folder to rw-r-r & put the settings apk in there & made that rw-r-r too & rebooted, settings does not show up in firestarter? & even looked in hidden via firestarter but not in there? When I click on the apk it says install failed
Sent from my SM-G900F using Tapatalk
Then i have no Clue. Maybe i Reset my ftv to stock and try to reproduce your problem.
Sry that i cant help you directly
schybiorz said:
Then i have no Clue. Maybe i Reset my ftv to stock and try to reproduce your problem.
Sry that i cant help you directly
Click to expand...
Click to collapse
like I said if you could pull the folder with the settings apk in it via adb & zip & send me the link that would be great, I maybe doing something wrong somewhere? or the download may have been corrupted somehow? You can pm me the link if you want?
Sent from my SM-G900F using Tapatalk
path of file is still
/system/priv-app/Settings/Settings.apk
chmod 644. filesize is the same like in my link in first post.
anyone have any luck enabling the location settings in this settings.apk? I have the well-known problem of it backing out every time i try to enable any of the 3 options.
d3adpool said:
anyone have any luck enabling the location settings in this settings.apk? I have the well-known problem of it backing out every time i try to enable any of the 3 options.
Click to expand...
Click to collapse
nvm I got it figured out, can't use the settings.apk anymore to do it.
d3adpool said:
nvm I got it figured out, can't use the settings.apk anymore to do it.
Click to expand...
Click to collapse
Ha ha I couldn't even get it to install on my AFTV2 for some reason? Tried all the steps loads & loads of times on my rbox prerooted/with busy box & on the latest firmware with all different versions of the settings all from various download sources for Android 5+, but no go at all?
Sent from my SM-G900F using Tapatalk
deanr1977 said:
Ha ha I couldn't even get it to install on my AFTV2 for some reason? Tried all the steps loads & loads of times on my rbox prerooted/with busy box & on the latest firmware with all different versions of the settings all from various download sources for Android 5+, but no go at all?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
i went thru the same thing of trying all different versions of settings.apk with no luck. I needed to enable location settings so watchtnt could work on my firetv. I ended up installing AnyLocation on both my ftv1 and ftv2 and it works great. Ftv1 unrooted had to enable mock location settings thru adb, and the ftv2 rooted I could enable Advanced version in the app and it would enable mock settings for me.
Has anyone version for aftv 1? Thx!
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?