cacerts.bks updated 12-6-20
When the original search was on to repair the aging cacerts.bks file in order to get the Kindle app working again, one of the things I came across was a remark from a fellow who had located a Honeycomb ROM (Android 3.2...last stop before the format of the security certificate storage was changed) and copied the cacerts.bks file from it to his Android 2.2 device which was having problems with websites, etc.
I still can't get the method described by @tshoulihane in this thread to work for me. But his edited cacerts.bks file works really well in solving the problem.
Yesterday I managed to locate a CM 7 ROM (Honeycomb). It contains a largish cacerts.bks file (compared to ours) with 127 certificates, 17 of which have expired. These seem to be mostly for central/eastern European and Asian entities, so perhaps not that critical. Well, it's only 10 years old
It has worked for me with the Kindle app and perhaps will help with some of the websites that complain about a secure connection even though I have enabled TLS 1.2 in Opera Mobile. More testing is needed there.
For anyone who wants to try it out, it is attached below. To use, rename your current cacerts.bks file (that's in /system/etc/security) to cacerts.bks.bak or similar. Then move the new file (unzip) into the same place. Check permissions. They should be rw-r-r. Reboot.
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
xrayd2 said:
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
Click to expand...
Click to collapse
So was your SU app missing? Or did your file manager just not have root access?
Hard to know where to start. From my experience, the best-behaving SU for the NST/G is the one that comes with NookManager (attached below). It's old and the binaries are probably out of date, but you don't need anything better for the device.
You can try removing the one you have now, reboot, and install the one below. Then check that your file manager has root acccess. In ES File Explorer, for example, you have to go into settings and tick the selection for root access. It's not automatic. And even with that, you have to tick an additional box to mount /system as rw while you're working in it.
At one time the superuser app was included -- but is no longer linked, and I had overlooked it after initially flashing the rom.
Unfortunately, the su app you provided also doesn't work. When I try to delete the old cacerts.blk it looks like it's doing something, but then the file still remains. If I instead try to rename the file, I get "operation failed".
I tried to delete or rename using an app called "root browser", and also the file manager in "super manager" suite. When I try to enable the root explorer function in ES file manager , I get "sorry, test failed. This feature cannot run on your device."
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
I appreciate your help though!
xrayd2 said:
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
Click to expand...
Click to collapse
Mmm.... so the ROM came "rooted"? I've attached a root check app which I've tried on my NST. This should answer the question of root.
If root has been lost somehow, it might be possible to salvage what you have by running NookManager. If you don't want the various additions like Relaunch, you can remove those apps from the data/app folder once you've written the card and then make the other needed changes as described here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Or, you could just use NM as-is and uninstall unwanted material afterwards. The important thing is root and a functioning SU.
Okay... turns out my device was NOT rooted after all; I had assumed the binaries were already installed. Fortunately, I was able to find a superSU 0.93 binary and root through CWM. I replaced cacerts.blk with yours, and now the kindle app works! At first I had difficulty logging in, but turns out Amazon was emailing me a one time password after every attempt. After entering the OTP I am now up and running.
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Thanks for the link to your other post. I will sideload the apk's you recommended.
xrayd2 said:
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Click to expand...
Click to collapse
Might not be possible. Chatter here: https://forum.xda-developers.com/showthread.php?t=1604661&page=2 goes back to 2013.
I found reference to a functioning version in 9/2016. Had hoped it was a cacerts issue but maybe pocket changed their api.
https://forum.xda-developers.com/showpost.php?p=68600731&postcount=54
Would this be what's causing my Nook to not load certain https sites?
I can get to gmail fine, but I can't for the life of me load the todoist website
Tried loading your cacerts.bks, doesn't seem like it changed anything
I had no problem getting the Todoist home page. Logging in may be another matter.
Are you using Opera Mobile and did you make the settings change for TLS 1.2?
Related
so I had replaced the original WPA-suplicant file so I could connect to ad hoc networks. Had lost the original WPA file. someone posted up a copy of the original. uploaded to tab. replaced the old (Ad hoc friendly) with "original", now my Wi-Fi states ERROR, rebooted PC, same, put in the other WPA-supplicant file I had originally, still getting the same ERROR on Wi-Fi. any suggestions? something tells me I was suppose to disabled wifi before I did that, forgot.. chit..
FIX:
had to hold on the WPA_SUPPLICANT file and select view permissions
check/tick all the boxes in the first two columns and the first 2 in the last column.
Wifi is back ON! (THANK GOODNESS!!)
now to see if 3.1 installs.. wish me luck!
Nope. 3.1 failed to install... OMG!!! >,<
So I dont have my original WPA_Supplicant file.
Someone on another thread posted up theyre original WPA_Supplicant file.
I replaced the old one with his original one.
I did not make any other changes to my tab when I had root.
What could be the problem? anyway to bypass this & get 3.1 installed?
I did similar and it completely f*cked me up.
I factory reset and now my wifi just scans with out anything coming up. UGH.
HD87 said:
Nope. 3.1 failed to install... OMG!!! >,<
So I dont have my original WPA_Supplicant file.
Someone on another thread posted up theyre original WPA_Supplicant file.
I replaced the old one with his original one.
I did not make any other changes to my tab when I had root.
What could be the problem? anyway to bypass this & get 3.1 installed?
Click to expand...
Click to collapse
Here is the fix for your issue..
i had exactly the same problem that you described and this file (original wpa_supplicant.zip) helped and solved my issue..i'm now running Honeycomb 3.1
Solution posted by Bob here: (just correct the "www" on the link below before opening)
w w w.androidtablets.net/forum/acer-iconia-tab-a500-forum/18444-update-failed-help.html
Here's the WPA_Supplicant from my A500, after the 3.1 update. Hope this works for you guys.
I'm not sure what the extension is for the A500, but I had to add .zip to be able to upload it. Try removing the .zip before using it. Also, remove the 'original'. I added that to keep it straight on my tablet.
Good Luck.
Bob
p.s: sorry i'm a newbie here and can't post any link outside the forum at the moment..
just follow the steps described by Bob!
bigjuju4fr said:
Here is the fix for your issue..
i had exactly the same problem that you described and this file (original wpa_supplicant.zip) helped and solved my issue..i'm now running Honeycomb 3.1
Solution posted by Bob here: (just correct the "www" on the link below before opening)
w w w.androidtablets.net/forum/acer-iconia-tab-a500-forum/18444-update-failed-help.html
Here's the WPA_Supplicant from my A500, after the 3.1 update. Hope this works for you guys.
I'm not sure what the extension is for the A500, but I had to add .zip to be able to upload it. Try removing the .zip before using it. Also, remove the 'original'. I added that to keep it straight on my tablet.
Good Luck.
Bob
p.s: sorry i'm a newbie here and can't post any link outside the forum at the moment..
just follow the steps described by Bob!
Click to expand...
Click to collapse
No luck. Every wpa_supp file that I try just gives me an error.
rorytmeadows said:
No luck. Every wpa_supp file that I try just gives me an error.
Click to expand...
Click to collapse
did you change the permissions on the file after copying that on /system/bin?
with gingerbreak.apk, you have to root ur device.(download and install gingerbeak.apk!! is available here in forum)
Then i used "es file explorer" (file explorer with root permissions) from the market. In the settings of the program, go to the root options and check the available two boxes before you copy the file in the system directory.
After copying the file, change the permissions as follow:
you have to check all the boxes for the first 2 columns and the first 2 for the last column; so at the end you should have: rwxrwxrw-
After that, go again on the settings of the program,
1. uncheck the two boxes,
2. go to installed gingerbreak app and unroot your device.. --> device will restart
after the restart go to the system from settings of the device and check if an update is available to your device and download it.. then install
it will work.
Good Luck
Claude
bigjuju4fr said:
did you change the permissions on the file after copying that on /system/bin?
with gingerbreak.apk, you have to root ur device.(download and install gingerbeak.apk!! is available here in forum)
Then i used "es file explorer" (file explorer with root permissions) from the market. In the settings of the program, go to the root options and check the available two boxes before you copy the file in the system directory.
After copying the file, change the permissions as follow:
you have to check all the boxes for the first 2 columns and the first 2 for the last column; so at the end you should have: rwxrwxrw-
After that, go again on the settings of the program,
1. uncheck the two boxes,
2. go to installed gingerbreak app and unroot your device.. --> device will restart
after the restart go to the system from settings of the device and check if an update is available to your device and download it.. then install
it will work.
Good Luck
Claude
Click to expand...
Click to collapse
Ahh yes, that's it. I remember that originally, but I couldn't remember what the permissions settings were for and that was it!
Thanks,
could someone please post the original wpa_supplicant file? Every one that i have come across in the xda-developers forums i get the following error when trying to transfer it to my tablet "cannot copy item - the device has either stopped responding or has been disconnected". If i try to extract the file i get "cannot open file: it does not appear to be a valid archive." Im at a lost so any help with this would be greatly appreciated. Thanks
Recently flashed Malice v5. Now get message that I have to update swype which requires uninstalling except that under app management there is no option under swype to uninstall. I unistalled the installer and deleted the apk. What else can I do?
scooter421 said:
Recently flashed Malice v5. Now get message that I have to update swype which requires uninstalling except that under app management there is no option under swype to uninstall. I unistalled the installer and deleted the apk. What else can I do?
Click to expand...
Click to collapse
Got to system/lib/
Delete libSwypeCore.so
Rerun Swype installer.
you can use titanium backup to uninstall it.
then when you install it through the installer, it will show up in manage apps in settings.
Thanks jneal9 but I can not delete the file. I have Astro and File Expert. Neither worked.
Thanks funeralthirst. Was able to uninstall but I still need to delete the .so file
after much searching I found an alternative to root explorer- super manager. was able to delete the .so file
Thanks for the help. I learn something new everyday.
scooter421 said:
Thanks jneal9 but I can not delete the file. I have Astro and File Expert. Neither worked.
Thanks funeralthirst. Was able to uninstall but I still need to delete the .so file
after much searching I found an alternative to root explorer- super manager. was able to delete the .so file
Thanks for the help. I learn something new everyday.
Click to expand...
Click to collapse
Try root explorer, astro can't access the file.
I was trying to install the lastest swype beta apk following almost all the steps above (I didn't erased the files, only renamed them) but wasn't successful, is there any other way? I'm using ES Explorer (with Root Explorer option checked)
The above mentioned steps worked for me:
-uninstall with Titanium
-delete the libswypecore.so file
I used Super Manager for the root explorer. Search marketplace for this. It's free and Root Explorer is not. In either of them you need to change the permissions of the file from r/o to r/w (read only to read write).
The thing with Titanium is that once before i've tried to install a new email app, so I used this Titanium to uninstall it first and when i've run the installer it showed "Application Not Installed" no matter how many times I excuted it, and this totally messed my phone up, I had to odin back to stock!
So, in this case is safe to unistall Swype and the installer apk won't give that error?
I make no guarantees but what is mentioned in this thread works. And, as I've learned the hard way, you should make a backup of your phone before flashing anything.
Follow the above steps. Not only remove the AOL but also the file"kinetoscope.so". Use root explorer or super manager to do this.
It seems like it's alot of work but once you have everything you need it goes fast. Searching for the answer is the hardest part.
Sent from my SGS-t959 using XDA App
ok 2 things
1. ES File Manager (Root explorer for free on market
2. when you uninstall Swype using Titanium Reboot phone before reinstalling Swype. Same with most applications. Rebooting clears out the temp files that can corrupt a reinstallation.
Hi,
I've only had an android phone for a month or two (Samsung Galaxy S2, 2.3.3 Gingerbread, not rooted)
I have the same problem removing swype with no 'uninstall' option (trying to update to new version). All of these solutions seem to require a rooted droid, is that the case or have I misunderstood?
Can anyone offer a solution that does not involve rooting?
Thanks!
djbeezo said:
Hi,
I've only had an android phone for a month or two (Samsung Galaxy S2, 2.3.3 Gingerbread, not rooted)
I have the same problem removing swype with no 'uninstall' option (trying to update to new version). All of these solutions seem to require a rooted droid, is that the case or have I misunderstood?
Can anyone offer a solution that does not involve rooting?
Thanks!
Click to expand...
Click to collapse
If Swype came preinstalled you won't be able to remove it without root.
Thanks for your reply jneal9. Swype did not come pre-installed on my phone, I had to download the beta to be able to use it.
However, after I updated the Swype Installer (so that I could then update Swype itself) it gives the message "Sorry, the Swype Beta is currently unavailable for devices that have Swype preinstalled" (which it definitely did not).
Is this something that anyone has come across before? I'm a bit surprised that it seems like this application (although I do realize that it is a Beta) cannot be uninstalled without rooting the phone!
Thanks!
This also happened to me when i was on malice v5. i tried everything to get swype back but to no avail. i switched from that to miui because malice will soft boot while ur on the phone when u have 30% or less battery.
I had the same problems and hopefully this will help others: first I had tried to restore Swype from Titanium and got Force Closes. Then, I downloaded a new version of Swype and after deleting the old installed: "Application Did Not Install" then I went to /system/lib and saw that libswypecore.so was NOT there. So after many combinations of the above recommendations, I finally did this: deleted all traces of Swype, rebooted phone, used Root Explorer to change /system/apps to R/W, copied the latest Swype in, ran the install (success), then EXTRACTED the libswypecore.so from the Swype.apk and manually copied to /system/lib and changed the permissions to the recommended settings above. Worked! No Swype alerts me to a new version, I download within Swype, it asks to replace, I say yes, and the installation fails! At least the version I loaded still works.
I have followed the instructions from pcworld.com(unable to post link due to noob status) which happen to appear on several other sites.
I'm having issues copying the vending.apk file to /system/app with File Expert. I think it's a write-permissions issue but I don't know enough to get around that. File Expert says that it's mounting this directory successfully but it's just acting like the file is being copied when it's actually not. Please help...
Use the method posted here then if you are still having problems come back and ask questions.
http://forum.xda-developers.com/showthread.php?t=1351283
Thank you for your reply. The method I used is very similar to that one. I have been trying to paste the vending.apk into the /system/app folder as this tutorial instructed and it has also failed. I tried mounting with File Exper and with ES file explorer. Is there another app I should try to use to accomplish this? Doesn't seem like there's anything better in the amazon app store. Maybe I have to manually install an .apk of sorts?
payote40oz said:
I have been trying to paste the vending.apk into the /system/app folder as this tutorial instructed and it has also failed.
Click to expand...
Click to collapse
What was the failure?
had also troubles installing with explorers - would recomend you the adb method:
http://forum.xda-developers.com/showpost.php?p=19789892&postcount=35
payote40oz said:
Thank you for your reply. The method I used is very similar to that one. I have been trying to paste the vending.apk into the /system/app folder as this tutorial instructed and it has also failed. I tried mounting with File Exper and with ES file explorer. Is there another app I should try to use to accomplish this? Doesn't seem like there's anything better in the amazon app store. Maybe I have to manually install an .apk of sorts?
Click to expand...
Click to collapse
Other users have reported lack of root privelages with file explorers from the Amazon App Store. At one point Root Explorer and File Explorer were removed, and File Explorer was the only one that's returned (now with limited funciontality). I'm guessing Root Explorer no longer shows up for this reason.
Either sideload the Android Market version of a file explorer from your phone, or download the .apk I posted here. I pulled it from my phone and it should have full root privelages. It worked when I was setting up my KF. This version was pulled prior to the most recent update, so it's a little outdated.
So basically what I've followed thus far was a combination of both instructions. I'm going to assume that since SuperOneClick said everything was rooted - that it is. So in terms of installing the android market, here's a tl;dr of what i've done and where i'm at:
- adb push googleframeworkservices.apk
- adb push vending.apk to the appropriate directory and assign its permissions.
- Used File Expert to install MarketOpener.apk(places an icon in carousel so you don't have to use alternate launchers)
- rebooted KF
The market opens up fine now but whenever I go to download something it either says "authorizing purchase" or "downloading" and never progresses beyond that. Please, PLEASE let me know if i'm omitting any piece of information that may help you guys assist me. Thanks for all your good work fellas, I appreciate it.
maybe you have a bad vending.apk - there are some bad versions around.
post you mine and try again with the adb method i suggested.
posted framework just to be shure.
did you install the vending.apk ? look at point 7 of the guide i linked in carefully !
good luck !
Greetings all. The rooting with SalsichaNooter 0.4 went well. One thing I didn't understand, however, was how to replace the Vending.apk on with Nook with the new one supplied.
The relevant link is
http://forum.xda-developers.com/showthread.php?t=1351719
Could someone explain how I do this? So far, I have copied the new file to the /media folder. That is as far as I've gotten.
Thanks.
Well, you must replace the Vending.apk in data/app. Use Root Explorer
Root Explorer
Thanks, Platinum_Lotus. I am wondering, though, why, with my paid version of Astro, I can't seem to do what you suggest. I can definitely copy the new Vending; I just can't paste it, overwriting what is already in apps.
Is there some permissions issue that I need to address? Or will RE bypass permissions somehow?
srk05 said:
Thanks, Platinum_Lotus. I am wondering, though, why, with my paid version of Astro, I can't seem to do what you suggest. I can definitely copy the new Vending; I just can't paste it, overwriting what is already in apps.
Is there some permissions issue that I need to address? Or will RE bypass permissions somehow?
Click to expand...
Click to collapse
Perhaps install the apk using Astro (if you can) or ES File explorer / ADB. If it says install blocked, you need to open Nook Color Tools and uncheck then check the box.
Well, I have tried. I noticed that the permissions on the app folder looked Linux-like (I *am* a newbie), and eventually figured out how to change permissions (it seems, only temporarily) so that I could copy the new vending.apk to the app folder. Before that, I renamed the old vending app.
So now, I have no access to the Google Marketplace whatsoever. And, the permissions have reverted to read-only. I do not understand.
I wish one of the heavier hitters here could help me out. I'm about ready just to quit.
(Note: I got back into the Nook and just used Linux commands to delete the new Vending & rename the old one to Vending. Now I have the crippled Android Market.)
I am getting my Nook ST from ebay very soon. Please help me understand the process:
What is the difference between just rooting using Nook Manager and flashing a ROM like 1337?
I am assuming, I can still install APKs after rooting?
thanks
S
sany said:
I am getting my Nook ST from ebay very soon. Please help me understand the process:
What is the difference between just rooting using Nook Manager and flashing a ROM like 1337?
I am assuming, I can still install APKs after rooting?
thanks
S
Click to expand...
Click to collapse
Rooting with NookManager gives you access to "root" directories that are normally off limits to users. It also allows for various customizations. It sets the security flag for installing from "unknown sources", allowing you to install apps via a file manager (or ADB), as opposed to getting them from the PlayStore (which you can't anymore). And it installs a base set of apps to get you going, like a file manager, launcher, browser, etc. That is customizable.
Custom ROMs like the 1337 simply enable different features that some people like. Perhaps better to use the system "as-is" for a bit before you decide to wipe it out? Then you'll have a better idea of what you'd like to have.
nmyshkin said:
Rooting with NookManager gives you access to "root" directories that are normally off limits to users. It also allows for various customizations. It sets the security flag for installing from "unknown sources", allowing you to install apps via a file manager (or ADB), as opposed to getting them from the PlayStore (which you can't anymore). And it installs a base set of apps to get you going, like a file manager, launcher, browser, etc. That is customizable.
Custom ROMs like the 1337 simply enable different features that some people like. Perhaps better to use the system "as-is" for a bit before you decide to wipe it out? Then you'll have a better idea of what you'd like to have.
Click to expand...
Click to collapse
Thank you @nmyshkin, I think my liking will be towards Nook Manager. So I will try to get ready with the Nook Manager installation files and instruction. The only thing confusing here in the forum is there are too many threads and geeting lost which and where to start. Hope if I start with the original thread which is from way back 2012, it will still work. My understanding is if I am on a new firmware 2.1.2 I will rewrite the modification files to nook manager as per that thread.
thanks again
S
sany said:
Thank you @nmyshkin, I think my liking will be towards Nook Manager. So I will try to get ready with the Nook Manager installation files and instruction. The only thing confusing here in the forum is there are too many threads and geeting lost which and where to start. Hope if I start with the original thread which is from way back 2012, it will still work. My understanding is if I am on a new firmware 2.1.2 I will rewrite the modification files to nook manager as per that thread.
thanks again
S
Click to expand...
Click to collapse
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 .
Click to expand...
Click to collapse
Very helpful! thanks again.
nmyshkin said:
2. Register your device with B&N.
Click to expand...
Click to collapse
How important is this step - do I really need to register? any advantages and disadvantages?
sany said:
How important is this step - do I really need to register? any advantages and disadvantages?
Click to expand...
Click to collapse
The device software is designed to sell ebooks from B&N. Anything that frustrates this design (like not registering or disabling parts of the B&N system) tends to raise all kinds of internal alarms and the system dialogs constantly with itself, worrying about its purpose in life, its inability to "phone home", and generally fritters away a lot of its battery charge on rehearsing for a role it cannot assume.
In short, the path of least resistance results in the least system hand-wringing, improved battery life, etc. You don't need to enter any credit card information. All you need is an email address (which I suppose could be fake) and a password. Then you can forget about it if you have no interest in purchasing ebooks from B&N. I have completely ignored the B&N system except for the Reader and Library which I find adequate--and simple--enough for my needs. But everything else is hidden. It just lives its happy little digital life waiting for that one special day when I will buy an ebook with a patience only electrons can exhibit. Meanwhile I have all kinds of other stuff that I am interested in and there don't seem to be any issues or conflicts with the B&N system.
My 2 cents.
Installed but no apps
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
Click to expand...
Click to collapse
I successfully backed up and rooted the device. Firmware is 1.2.2.
But I don't have any apps. Not even the base software. See screenshot. Even the extras like es file explorer were not installed. Since I don't have any file explorer, I am unable to install any apps. I want to go for ADB method as last resort. Please advice.
Thanks
sany said:
I successfully backed up and rooted the device. Firmware is 1.2.2.
But I don't have any apps. Not even the base software. See screenshot. Even the extras like es file explorer were not installed. Since I don't have any file explorer, I am unable to install any apps. I want to go for ADB method as last resort. Please advice.
Thanks
Click to expand...
Click to collapse
You can try for ADB (more headaches there), but it would be better now to get some useful apps and have a way to conveniently side-load others. You are supposed to be able to install apps from Relaunch in the file manager screen. That would involve copying the apk file to the NST via a USB connection, then locating that apk file using the file folder browser and tapping on the icon. I could never get that to work, but it is supposed to work.
Failing that, you need to revisit NookManager. You must not have done the customization correctly if none of the apps you wanted were installed. If you can get that fixed, you can simply root again with NookManager (right on top of what you have now) and it will fix the problem IF you get it set up correctly.
There are four steps required to add an app to the NookManager rooting routine:
1. Copy the apk file to the folder files/data/app on the NookManager SD card
2. in the folder "scripts" on the NookManager SD card, copy and rename one of the "install_x" files so it represents the app you just moved into the folder in step 1. So, if you want ES File Explorer, you might rename the file "install_esfileexplorer"
3. Edit the file you just copied and renamed, changing the name of the apk file in the first line to exactly match the filename of the apk file you have replaced in files/data/app. So continuing the example, "es_file_explorer.apk" (which is the name of the apk file as I provided it). Then edit the "echo" statement so it reads something like "echo ES File Explorer installed"
4. Locate the file scripts/do_root. Copy and rename one of the "install_x" files so it matches what you did earlier, in this case "install_es_file_explorer". There are no contents to edit.
You need to do those four steps for each app you want to add to the install list. To remove an app you don't want (like the Amazon App Store), remove the apk file from files/data/app, remove the "install_x" file for that app from the folder "scripts", and remove the "install_x" file for that app from the file scripts/do_root.
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
Click to expand...
Click to collapse
Thanks, I followed all those steps...I will take a relook at it. But without es file explorer, I thought there is already a file manager. How to I get there as I can't see anything in the app drawer? (Screenshot in previous post).
sany said:
Thanks, I followed all those steps...I will take a relook at it. But without es file explorer, I thought there is already a file manager. How to I get there as I can't see anything in the app drawer? (Screenshot in previous post).
Click to expand...
Click to collapse
I know very little about Relaunch, but I believe you need to tap on the open door in the upper right corner to get out of the app drawer.
Oh okay! I was expecting to launch file manager from app drawer. So when relaunch opens we are already in file explorer.
One more question: how do we make dictionary work in the default nook reader, that is when you you open a book from library. I thought pressing on a particular word will present me the option. I only see option to bookmark. I have to read the manual again.
sany said:
Oh okay! I was expecting to launch file manager from app drawer. So when relaunch opens we are already in file explorer.
One more question: how do we make dictionary work in the default nook reader, that is when you you open a book from library. I thought pressing on a particular word will present me the option. I only see option to bookmark. I have to read the manual again.
Click to expand...
Click to collapse
That's how the dictionary works for me. Hold your finger on a word until it is highlighted. Then a series of options pops up from the bottom, one of which is "Look up".
nmyshkin said:
You can try for ADB (more headaches there), but it would be better now to get some useful apps and have a way to conveniently side-load others. You are supposed to be able to install apps from Relaunch in the file manager screen. That would involve copying the apk file to the NST via a USB connection, then locating that apk file using the file folder browser and tapping on the icon. I could never get that to work, but it is supposed to work.
Failing that, you need to revisit NookManager. You must not have done the customization correctly if none of the apps you wanted were installed. If you can get that fixed, you can simply root again with NookManager (right on top of what you have now) and it will fix the problem IF you get it set up correctly.
There are four steps required to add an app to the NookManager rooting routine:
1. Copy the apk file to the folder files/data/app on the NookManager SD card
2. in the folder "scripts" on the NookManager SD card, copy and rename one of the "install_x" files so it represents the app you just moved into the folder in step 1. So, if you want ES File Explorer, you might rename the file "install_esfileexplorer"
3. Edit the file you just copied and renamed, changing the name of the apk file in the first line to exactly match the filename of the apk file you have replaced in files/data/app. So continuing the example, "es_file_explorer.apk" (which is the name of the apk file as I provided it). Then edit the "echo" statement so it reads something like "echo ES File Explorer installed"
4. Locate the file scripts/do_root. Copy and rename one of the "install_x" files so it matches what you did earlier, in this case "install_es_file_explorer". There are no contents to edit.
You need to do those four steps for each app you want to add to the install list. To remove an app you don't want (like the Amazon App Store), remove the apk file from files/data/app, remove the "install_x" file for that app from the folder "scripts", and remove the "install_x" file for that app from the file scripts/do_root.
Click to expand...
Click to collapse
\
I followed all your instructions above and successfully installed all apps. To summarise my observation after the successful installation:
1. Only Opera browser app and ES File Explorer app works
2. Yalp app store does not work at all - it just takes me to the next screen with options to 'update' or 'run'. Pressing update keeps searching forever and 'run' takes me back to the previous screen. After several tests, I decided to uninstall the app.
I tried to install youversion bible app which also works (but its a old version) so several features not available. But at least it works.
I noticed wifi outage issues intermittently on the opera browser and also once while trying the yalp store app. It said I was not connected, but I know for a fact I was connected when I connect to the Nook store etc.,
Overall, I am wondering what did I gain out of the whole process. Not much I can do with the custom installation. So I might return back to a original nook after playing with this setup for a while. This leaves me with couple of questions that I will start on a new thread.
Thanks again @nmyshkin for your patience in explaining.
S
To go back to original nook state - do I need to simply go into settings>Device Info> Erase & Deregister Device to get it back to out of box condition? Will this cancel the rooting?
Or do I have to stick the nook manager card and restore from backup?
sany said:
To go back to original nook state - do I need to simply go into settings>Device Info> Erase & Deregister Device to get it back to out of box condition? Will this cancel the rooting?
Or do I have to stick the nook manager card and restore from backup?
Click to expand...
Click to collapse
Erase and deregister will remove root and restore to out-of-the-box state unless you have done something serious. In that case, a factory re-image should solve the problem. That is done by powering off, then powering on and holding down the two lower hardware buttons as soon as the "Read Forever" screen appears. Wait for the prompt and follow it.
Re: Yalp Store, I just checked mine a minute ago and it's running fine. Very rarely it goes down and can't log in to the PlayStore, but it generally comes back later in the day.
Okay - so maybe I should try yalpstore at different times.