Related
I'm fairly new to android, and rooting and custom roms and all that i have an a500 with the minimalistic 3.2 rom, and but this has happened with any other custom roms or stock firmwares aswell (all rooted)..
Anyway, ill use this as an example, one time, and I was trying to install the samsung Ebook.apk and it required a separate sytem app, and everyone said move this other app (my files. Apk.) to system / apps and change permissions, I've tried with several file managers and it always says that it is read only,
This happens when trying to move files to other system folders... Isn't rooting supposed to give me access to these and let me edit files or put files there ect
I'm probably just stupid, but but any help would be appreciated
ddpruel said:
I'm fairly new to android, and rooting and custom roms and all that i have an a500 with the minimalistic 3.2 rom, and but this has happened with any other custom roms or stock firmwares aswell (all rooted)..
Anyway, ill use this as an example, one time, and I was trying to install the samsung Ebook.apk and it required a separate sytem app, and everyone said move this other app (my files. Apk.) to system / apps and change permissions, I've tried with several file managers and it always says that it is read only,
This happens when trying to move files to other system folders... Isn't rooting supposed to give me access to these and let me edit files or put files there ect
I'm probably just stupid, but but any help would be appreciated
Click to expand...
Click to collapse
Can you just push the files with ADB and edit the permissions?
I could not get ES File Explorer to gain root permissions with the Minimalist Rom, but the ADB method worked for me (installing Polaris Office).
I've heard a lot about adb but have never used it.. Ill look it up and see if I can set it up... thanks
use root explorer. Great file manager and gives youba button to mount the filesystem r/w
ddpruel said:
I'm fairly new to android, and rooting and custom roms and all that i have an a500 with the minimalistic 3.2 rom, and but this has happened with any other custom roms or stock firmwares aswell (all rooted)..
Anyway, ill use this as an example, one time, and I was trying to install the samsung Ebook.apk and it required a separate sytem app, and everyone said move this other app (my files. Apk.) to system / apps and change permissions, I've tried with several file managers and it always says that it is read only,
This happens when trying to move files to other system folders... Isn't rooting supposed to give me access to these and let me edit files or put files there ect
I'm probably just stupid, but but any help would be appreciated
Click to expand...
Click to collapse
You need to remount the relevant folders as read/write. Most file explorers can do it. Most people swear by Root Explorer, but that's pay software. I use ES File Manager, which is free.
Thanks a lot but but how do i change permissions with root explorer? I (i am supposed i change them to 644)
ddpruel said:
Thanks a lot but but how do i change permissions with root explorer? I (i am supposed i change them to 644)
Click to expand...
Click to collapse
I could not get ES File Explorer to gain permissions with this rom.
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.
Flashed CleanGB Rom v16 today and there is no AllShare app
After some searching I found the dlna.apk for allshare.
used ES File Explorer to place it in the system/app folder set the permission that where given in another thread
USER = READ + WRITE
GROUP = READ
OTHERS = READ
App starts but then force closes after 5 sec.
Also installed it with SDX Stock App Removal and did the same thing.
Im stuck at this point
is there any way to get it working?
I grabbed my allshare app off of this thread and it worked. It's for Deodexed Roms. I'm currently on ACS ICS 5.1.
http://forum.xda-developers.com/showthread.php?t=824953
From your post though, it looks as if that's the file you may have used?
yea thats the thread i was looking at
and i got the apk file from there.
anyone has any idea how to fix this?
All I did to get it to work was copy the file, and paste it into the system/apps folder with write permissions. then just reset your phone and it should have shown up in your launcher. should work since cleangb is deodexed.
where the permission the same ones i posted?
Captain obvious stand-in:
There is a Q&A subforum. This is obviously a question as your title denotes with the [Q], so try to utilize it in the future.
Make sure the file you're trying to push over fits your current rom's structure, such as odexed or deodexed. Move the file over with a file manager, like Root Explorer, and a restart may be required.
If that doesn't help you could always try using the "fix permissions" feature in CWM.
I am really pissed about this one.. tried to make a Titanium Backup of my stuff before I unrooted and wiped the phone to ODIN the ANE update (it refused to update after being towelrooted).. So that was my first introduction to the bug that prevents TiBu from writing to the extSD.. I found several threads pointing to adding a line to the profiles.xml file in system/etc/permissions. Well I added the line using ES3 note editor (copied the original file to .bak first), saved and rebooted, and as soon as I unlocked the phone, the toasts started popping up that nearly everything was crashing - repeatedly. I went and deleted the modified file and changed the .bak back to normal, but it did not fix it. No apps would open, and I had no data connection (neither Wifi or 3G). The only thing that fixed it was booting into recovery and wiping it.
And then it happened AGAIN when I tried it again (after the ANE update was flashed via ODIN, so I know it was clean). So WTF is happening, and why does restoring the original file not fix it??
At this point I can't even get TiBu to back up to the internal storage.
Taz420nj said:
I am really pissed about this one..
Click to expand...
Click to collapse
There is no obvious reason why it shouldn't work of you reverted the changes. But of course that is the ultimate value of a tested backup method.. that ability to roll the clock back and revert accidental or inexplicable changes.
If you are certain that you reverted the edits.. no typos or line feed errors e.g.you used a linux aware file editor.. not notepad on a PC or something similar - then it's likely a permissions error.
What permissions does the file currently have? And what app did you edit the .xml with?
.
fffft said:
There is no obvious reason why it shouldn't work of you reverted the changes. But of course that is the ultimate value of a tested backup method.. that ability to roll the clock back and revert accidental or inexplicable changes.
If you are certain that you reverted the edits.. no typos or line feed errors e.g.you used a linux aware file editor.. not notepad on a PC or something similar - then it's likely a permissions error.
What permissions does the file currently have? And what app did you edit the .xml with?
.
Click to expand...
Click to collapse
As I said, I made a copy of the file and edited it with ES3 Note Editor right on the phone. Then I renamed the original file to platform.xml.bak, and copy/pasted the new platform.xml file into system/etc/permissions. When everything went haywire, I didn't try editing the file back (I couldn't - the toasts were popping up almost faster than I could clear them and Note Editor kept crashing), I just deleted the modified file and renamed platform.xml.bak back to platform.xml. I never edited the original file at all, so that's how I am 100% positive there are no errors in it - and that's why I can't figure out why renaming it back doesn't fix the mayhem.
Now I am a total weenie when it comes to Linux - I know OF the -rw-r--r-- permissions and what they mean, but I don't know how to make the phone tell me.. But in ES3 Explorer under file properties it simply says Readable: Yes Writable: Yes Hidden: No.
What sucks is I've had to go through and set the phone back up twice now, and lost all my settings/data in the meantime over this.. And I STILL don't have a working backup method, so if it borks again I'll be doing it all over again.. I am unwilling to blow the Knox fuse, hence not having a custom ROM at this point.. But I'm fine using Towelroot just so I can unbloat and install some things.
No one wishes for things to go awry. But of course they do sometimes and it would be imprudent not to plan for that eventuality. You didn't, nor do you seem to realize just how risky the changes you have been making are to your basic system stability. You are modifying critical, system level files and properties. The expected result if there is a typo or permissions error is chaos and corruption. If I was unable to have a working backup method (from refusing to increment Knox), I wouldn't risk the changes you are making.
It's all well and nice to customize features when things turn out smoothly. But all along you have been working without a safety net, so it's not reasonable to complain about the onerous amount of work it is to reinstall the firmware when fate bites you. You can't have it two ways at once. Either you incremement Knox, allowing inclusive backups and a way to recover. Or you accept that that you are taking crazy risks and having to start over the price for doing so.
You'd be in a better position if you had some basic tools to delineate what is going on. But you haven't taken the time to learn how to read file permissions. You are working deep within a linux filesystem, so this is a very basic and useful skill.
You don't use the same file manager as me, with mine (fx), you would long press and view details. Or even easier, use the ls command e.g. ls -la. There are a dozen ways you could check permissions and a simple forum search would elaborate on many of them. It sounds like you have permissions errors, i.e the system can't access the restored .xml sheet thereby causing numerous apps to crash.
.
Uhhh, except in order to implement the safety net I have to make this simple change to this one critical system file. It's no different than not having a means to backup before rooting/flashing (since TiBu requires root and you can't do a nandroid from stock recovery) and something goes wrong.
Adding the <group gid="media_rw" /> line to the profile.xml is posted in MANY locations as a "this is all you have to do" solution to this rather stupid quirk in 4.4, with no mention whatsoever of checking/verifying permissions or any other cautions, and other people are not having this issue.
I installed FX, and it lists the permissions of all the files (including the copies of platform.xml and platform.xml.bak that I had saved on the SD card, and the virgin file currently in use) as 0644.
Taz420nj said:
Uhhh, except in order to implement the safety net I have to make this simple change to this one critical system file
Click to expand...
Click to collapse
It's your phone so you can do as you like. But risks don't go away because you ignore them. There is nothing wrong with accepting a risk that you may have to start over if things go sideways. But plunging ahead recklessly then complaining about the work to recover is patently unreasonable
I had no problem effecting the changes you are attempting. Nor have many others. Perhaps you made a typo or followed a thread with erroneous advice. You may well have a permissions error because you didn't explicitly set it or check to see if it was correct.
It's all about attention to detail e.g. checking permissions and being prepared to deal with fallout when things go astray.
.
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?