Hi,
I have transformed CoolReader into system app with Titanium backup. It was crashing so I tried to move it back to user app again with Titanium backup. However during this procedure TB hanged and after some 20 minutes I killed it. I later tried to uninstall it (again with TB), but it seems that there are still left parts of it somewhere so now I am unable to reinstall the app from google play (error 491) or if I clear cache and data of google play and force the application to install it keeps crashing.
So I would like to ask what should I delete to completely eliminate the traces of CoolReader (or any application in general) and be able to install it again?
I'm not sure if this will work but give it a shot.
Try finding an apk of your app and, using Root Explorer, paste it in /system/app (remember to mount /system as RW using Root Explorer). Set permissions (All read, owner-write, owner-execute) and reboot. That should register the app as a system app.
Go back into /system/app and delete it. Reboot and it should unregister it as a system app, allowing you to reinstall from Google Play
Hi Everyone,
I'm having trouble manually installing apk files from a file explorer. Whenever I try to, it says I have insufficient memory. But I have over 10gb of available memory. This happened after tinkering with Lucky Patcher and then eventually uninstalling it. Im afraid i might have changed something whithin Lucky Patcher and now I cant reinstall it because of the installation problem. My s6 edge is Pingpong rooted and also has OTG helper if this helps. dont know if it messes up with drive mounting.
Installing from google play is no problem at all.
Thanks for anyones suggestions
jgatlabayan said:
Hi Everyone,
I'm having trouble manually installing apk files from a file explorer. Whenever I try to, it says I have insufficient memory. But I have over 10gb of available memory. This happened after tinkering with Lucky Patcher and then eventually uninstalling it. Im afraid i might have changed something whithin Lucky Patcher and now I cant reinstall it because of the installation problem. My s6 edge is Pingpong rooted and also has OTG helper if this helps. dont know if it messes up with drive mounting.
Installing from google play is no problem at all.
Thanks for anyones suggestions
Click to expand...
Click to collapse
Have you try this?
http://forum.xda-developers.com/showpost.php?p=40411252&postcount=5
Thank you for reply! Yes I did everything there. Thing is im not allowed to install any app for it shows insufficient memory for every app i try to install. But i think lucky patcher messed it up. But also lucky patcher might be able to fix it. Is there a way for me to manually install lucky patcher so I can bypass the installer menu?
Like extract its files to a specied folder?
I tried installing through adb with this command, adb install -r app.apk
but it still says I have insufficient memory even in adb.
Also, I noticed that Titanium Backup is not recognizing all of my apps. Just a few system apps.
Return to stock...
Yey! I was able to fix it with Rom toolbox! Switched installation path to internal.
Hello,
First, I would like to apologize for my English.
I have Acer Iconie One 7, B1-750 with Android 4.4.4 (Kitkat). I wanted to install GPS navigation (Sygic Voucher edition) through Google play. Everything was fine, I installed the application, but for the maps there was no enought free space on the system storage. Android Kitkat 4.4 removes ability to write files to the MicroSD card. So I rooted this android, I applied SDfix to restores this ability by modifying a configuration file. Than I installed FolderMount and Link2SD Plus applications. I successfully followed these instructions ( http://forum.xda-developers.com/showthread.php?t=2236566 ) ... everything was still ok, applications works correctly, linking applications works fine. But once during the linking mentioned application (Sygic Voucher edition) suddanly It freezes and restarted Android. The application will not run after that so I uninstalled it, and also I must delete ext2 partition and create it again through MiniTool Partition Wizard because Link2SD after a sudden restart could not load ext2 partition.
Now let's go to the heart of the matter
When I want to install Sygic Voucher edition application again through Google play (Google store) It gives me an error "Application could not be installed, insufficient storage available". This error gives me when It wants to install downloaded files. I tried all ways to fix the problem of this type- clear cache and data, uninstall updates of google play and update etc... but nothing helped. I also tried to install application by .xapk, but reported the same problem as google play. Of course I have enought space on system storage and SDcard. Other applications I can install without problems ! Only in this application reports mentioned bug! I think it may be due to the sudden restarting the system during the linking application. Is there anybody, who can help me with this problem please ? I will be very grateful because I am really dasperate ... Thanks
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.
Hey there
So i rooted my phone with TWRP (+ Data Wipe/Factory Reset)), installed Magisk, Magisk manager and phh's Superuser (all with the newest version of each).
Root Checker says im root, hide Magisk works like a dream but even with superuser access i cant transfer apps to the system apps... did i missed something? how can i fix this?
If i try to change the system from RO to RW with ES File Explorer for example it is back to RO when i recheck it... but i can copy apk files with the es Explorer to system >app and after a reboot the app is installed and can only be deactivated, not uninstalled... but i cant use the features of the app that i should have with the app as system app
All the other apps that can install apps directly as system apps tell me that they cant mount system partition as r/w
Thanks for your time and answer
Greetings
Chris
cmg15326 said:
Hey there
So i rooted my phone with TWRP (+ Data Wipe/Factory Reset)), installed Magisk, Magisk manager and phh's Superuser (all with the newest version of each).
Root Checker says im root, hide Magisk works like a dream but even with superuser access i cant transfer apps to the system apps... did i missed something? how can i fix this?
If i try to change the system from RO to RW with ES File Explorer for example it is back to RO when i recheck it... but i can copy apk files with the es Explorer to system >app and after a reboot the app is installed and can only be deactivated, not uninstalled... but i cant use the features of the app that i should have with the app as system app
All the other apps that can install apps directly as system apps tell me that they cant mount system partition as r/w
Thanks for your time and answer
Greetings
Chris
Click to expand...
Click to collapse
Just use another file manager like our forum 's MixExplorer
Sent from my SM-G318 using Tapatalk
SOLVED!
App needs to be in system>priv-app since Andorild 4.4 ... now it works perfect