Went to update my adaway hosts file and it failed to copy. I've googled it and count find anything to help.
I've uninstalled and reinstalled and even done it through f-droid and still not working.
OOS 3.2.1
Rooted
Busy box installed and up to date
In the adaway settings it allows you to change your target host file.
What's it set to?
Sent from my ONEPLUS A3000 using Tapatalk
It's set to system/ext/hosts
Ok, I don't slot more looking into this.
I cleared the dalvik/cache in TWRP then opened Es File Explorer went to system/ect/hosts and changed the permissions to full read and write permissions and it worked
Ok, I don't slot more looking into this.
I cleared the dalvik/cache in TWRP then opened Es File Explorer went to system/ect/hosts and changed the permissions to full read and write permissions and it worked
Related
I am unable to use my camera, whenever I try to use it I get the gallery has stopped error. I am rooted and running XeHD rom. It was working fine, not sure what changed. I have tried reflashing gapps and that did not help either.
Any ideas?
Thanks!
Short of a clean install you could try clearing cache and/or user data for the camera and gallery apps.
That did not work either.
Found this,wonder if it would fix it?
I have a Verizon (Toro) Gnex. I got the gallery has stopped issue when I first flashed the zip, but got it to work by doing the following. Thanks to SpecR for the detailed post and all here.
1) uninstalled CameraFX (not sure if this contributed, but it seemed prudent)
2) Set up ES File Explorer for /system access and modification (go to settings, Root settings and check everything)
3) Used ES File Explorer to change extensions to GalleryGoogle apk and odex to bak and obak (in /system/app)
4) Used ES File Explorer to change extension to GmsCore odex to bak (/system/app)
5) Used ES File Explorer to put all the files in the OP in their proper places and change file permissions to rw-r-r
6) Reboot in TWRP recovery
7) Wipe cache and dalvik cache
8) Reboot
I just did a factory reset and I still get the error.
What else can I try?
zmanzbo said:
I just did a factory reset and I still get the error.
What else can I try?
Click to expand...
Click to collapse
Same here, I can not use the camera, it keeps saying Gallery crashed. Other apps with cameras say the can connect to the camera (error -1). I did a factory reset and problem is still there.
zmanzbo said:
I just did a factory reset and I still get the error.
What else can I try?
Click to expand...
Click to collapse
Maybe you are flashing an incompatible gapps for your ROM?
Here is the scenario. I updated SuperSU v2.46 that came with the LG G4 root injection method with SuperSU v2.52 by running the Superuser.apk which basically installed /data/apps/<appname>/base.apk which worked as v2.52 except SuperSU will not install itself to /system even though I selected that option in SuperSU in which it said it will need to do a cleanup and reboot. So I manually renamed the base.apk to SuperSU.apk, changed the owner/group to root/root and kept the permissions as rw-r--r--, moved the file to /system/apps/SuperSU/SuperSU.apk, deleted the /data/apps/<appname> folder for SuperSU and restarted the phone. The only thing is SuperSU does not show up in the app launcher and the SuperSU.apk has the Android icon instead of the SuperSU app icon so I flashed the SuperSU v2.52 zip file with flashfire and it did restore /system/apps/SuperSU/SuperSU.apk with the correct icon except the problem is I noticed with Android 5.1 lollipop, you just can't replace a .apk in /system/app by moving it from /data/app as it will not even show up in the launcher. Not sure if this is a Lollipop thing or a LG thing as on previous Motorola phones running 4.4 Kitkat and below, replacing the .apk will usually work. I've cleared the app cache, deleted the files in /data/dalvik-cache/arm, /data/dalvik-cache/arm64 and /data/dalvik-cache/profiles without deleting the folders as I don't know if it's safe deleting the folders and also clearing the system /cache to see if it makes a difference. Didn't work. Does anyone know how I can fix this because it seems like once you updated to a newer version that installs in /data/apps, even if you delete the /data/apps version, it will not use the /system/apps version and simply ignore it. The only reason I still have root is probably because of the su binary still on the system.
Here is the scenario. I updated SuperSU v2.46 that came with the LG G4 root injection method with SuperSU v2.52 by running the Superuser.apk which basically installed /data/apps/<appname>/base.apk which worked as v2.52 except SuperSU will not install itself to /system even though I selected that option in SuperSU in which it said it will need to do a cleanup and reboot. So I manually renamed the base.apk to SuperSU.apk, changed the owner/group to root/root and kept the permissions as rw-r--r--, moved the file to /system/apps/SuperSU/SuperSU.apk, deleted the /data/apps/<appname> folder for SuperSU and restarted the phone. The only thing is SuperSU does not show up in the app launcher and the SuperSU.apk has the Android icon instead of the SuperSU app icon so I flashed the SuperSU v2.52 zip file with flashfire and it did restore /system/apps/SuperSU/SuperSU.apk with the correct icon except the problem is I noticed with Android 5.1 lollipop, you just can't replace a .apk in /system/app by moving it from /data/app as it will not even show up in the launcher. Not sure if this is a Lollipop thing or a LG thing as on previous Motorola phones running 4.4 Kitkat and below, replacing the .apk will usually work. I've cleared the app cache, deleted the files in /data/dalvik-cache/arm, /data/dalvik-cache/arm64 and /data/dalvik-cache/profiles without deleting the folders as I don't know if it's safe deleting the folders and also clearing the system /cache to see if it makes a difference. Didn't work. Does anyone know how I can fix this because it seems like once you updated to a newer version that installs in /data/apps, even if you delete the /data/apps version, it will not use the /system/apps version and simply ignore it. The only reason I still have root is probably because of the su binary still on the system.
Hi everyone.
I have
Android 9 + TWRP 323 + Magisk 16.7 + Magisk.apk
Root checker said that I have root.
SolidExplorer and Root Explorer can read root directory but cannot delete/write files in system directory.
Titanium Backup works good and restore applications.
What is wrong?
Thanks in advance.
v8088 said:
Hi everyone.
I have
Android 9 + TWRP 323 + Magisk 16.7 + Magisk.apk
Root checker said that I have root.
SolidExplorer and Root Explorer can read root directory but cannot delete/write files in system directory.
Titanium Backup works good and restore applications.
What is wrong?
Thanks in advance.
Click to expand...
Click to collapse
It's working fine for me. I just added a folder to /system, then added a text file to that directory, then edited the file without issue. Android 9, rooted using Magisk 16.7 Beta. Do the file explorers have root permission in Magisk?
One thing that happened to me the other day: I felt like an app (Fi Switch) wasn't properly prompting for root. I went into Magisk's root settings and changed the Automatic Response for root access to "Grant" from "Prompt". Went back to Fi Switch, did the thing that required root, and it worked. Checked Magisk again and it had now registered FiSwitch as a permitted root app. Then I changed the setting back to "Prompt" (not sure it really matters., but it feels safer lol).
It's almost like it just wasn't asking for root, then it was getting denied. Temporarily allowing it fixed it.
I have no idea why that worked for me, but maybe it'll work for you
borxnx said:
maybe it'll work for you
Click to expand...
Click to collapse
Unfortunately no. This is didn't help me.
borxnx said:
Do the file explorers have root permission in Magisk?
Click to expand...
Click to collapse
Yes, it has
So, I had some problems and flashed stock Nougat and OTA'd to Oreo. I then installed TWRP, rooted with Magisk, installed Viper4Android and Lucky patcher, but when I tried to install modded play store it didn't work. If I install play store as an user app it keeps crashing, if I try to install it as a system app or convert it to such it just doesn't show up nor is it on system/app or system/priv-app. I don't even mind it being modded or not, I just wanna get my play store back.
To start with modded/patched apps & the app you mentioned are not allowed on xda
You can just download the playstore and install it as a user app
You can also place it in system/priv-app/Phonesky
Set permissions to 644 and restart your phone
Some threads noted that out to me while I was searching for a fix. I'd even swear not to use it, I just wanted to bring Google Play back. For some reasong my Phonesky folder always had a device or resource busy message when I tried to delete it, so I'll have to keep manually installing Google Play and setting permissions to 644 to keep it working. Thanks a lot!
Hyoretsu said:
Some threads noted that out to me while I was searching for a fix. I'd even swear not to use it, I just wanted to bring Google Play back. For some reasong my Phonesky folder always had a device or resource busy message when I tried to delete it, so I'll have to keep manually installing Google Play and setting permissions to 644 to keep it working. Thanks a lot!
Click to expand...
Click to collapse
You probably didn't mount system to r/w
Quickest way is just to create a flashable zip & flash it
You can also use total commander app to manually copy the file & set permissions
You need to set root permissions everywhere in the app settings and mount system r/w
Ugh, this is the 3rd time I set system to be mounted on TWRP, 2nd one if you don't count that intial prompt. Should I mount persist and firmware too?
Hyoretsu said:
Ugh, this is the 3rd time I set system to be mounted on TWRP, 2nd one if you don't count that intial prompt. Should I mount persist and firmware too?
Click to expand...
Click to collapse
If you're flashing a zip twrp will automount system if you write that in your updater script
Why would you need to mount other partitions?
Was just curious if it's advised not to mount those partitions, already installed Play Store and set it as a system app with ES File Explorer. Never really did something to system partition but I've always left it mounted anyways.