Hey,
I've rooted my A1 using this guide:
https://www.youtube.com/watch?v=tRcYUMBgvaI
I have magisk 13.4 installed, and passing Root checker verification.
When I try to edit build.prop file using solid explorer or buidprop editor app I get an error, "can't save the file"
even tough both of them has been granted "superuser accesses" using magisk.
Any ideas?
On another matter, I just received November OTA, I have TWRP installed,
Will it be possible to install the update at all? in particularity will I be able to install it right after I manage to edit the build.prop file, and still "have" the edited file after the OTA in order to keep using GCAM? I don't care about root access, all I want is GCAM, and updated phone if possible.
Thanks!
You need to change ur system permission for writing!
Tip:- use es file explorer to change it
Or get the app BuildProp Editor from the playstore.
I can't get the Nov update with TWRP installed.
I think there's a magisk module to enable google camera
Build prop app and solid explorer failed changing permission. Any ideas?
WishMonster said:
Build prop app and solid explorer failed changing permission. Any ideas?
Click to expand...
Click to collapse
Maybe you should try magisk 14.4
Everything just work like a charm in my devices, root woth magisk 14.4
Update:
I reinstalled magisk, and updated to v 14.5.
tried GCAM ports from here:
https://www.xda-developers.com/google-camera-hdr-customization-raw-support/
& here:
https://www.xda-developers.com/google-camera-updated-zero-shutter-lag-xiaomi/
all keep crashing. should I do something other then installing the apk and editing the build prop?
Second update:
The "enabled" keyword vs "enable" made the difference. Everything works like a charm. Picture quality is dramatically improved.
Thanks!
BTW:
Anyone has good configuration for GCAM port from here:
https://www.xda-developers.com/google-camera-hdr-customization-raw-support/
I copied the configuration from post.
I believe there is a better one since the picture is size is significantly smaller (~1.7mb vs 2.5 - 3mb usually),
- Note that although the smaller size picture quality is definitely better.
WishMonster said:
Hey,
I've rooted my A1 using this guide:
https://www.youtube.com/watch?v=tRcYUMBgvaI
I have magisk 13.4 installed, and passing Root checker verification.
When I try to edit build.prop file using solid explorer or buidprop editor app I get an error, "can't save the file"
even tough both of them has been granted "superuser accesses" using magisk.
Any ideas?
On another matter, I just received November OTA, I have TWRP installed,
Will it be possible to install the update at all? in particularity will I be able to install it right after I manage to edit the build.prop file, and still "have" the edited file after the OTA in order to keep using GCAM? I don't care about root access, all I want is GCAM, and updated phone if possible.
Thanks!
Click to expand...
Click to collapse
Please refer my guide... maybe it will help u
https://forum.xda-developers.com/mi-max-3/themes/problem-fixed-failed-to-enabled-t3913133
Related
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
So to clarify, if we want android pay to work we can't use xposed?
Sent from my Nexus 6P using Tapatalk
Wehdota said:
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
Click to expand...
Click to collapse
sweet, i flashed 2.62 thinking it was systemless root too and android pay stopped working. came here looking for a solution, deleted /su/xbin_bind and android pay is working again!
Giving Root Access?
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
I'd like to know this as well
leamdav said:
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
Click to expand...
Click to collapse
Some apps don't ask for root by default, and only do so when you tell them you want to enable the features that require root. ES File Explorer is one such app, and to enable root features you have to open the side menu and toggle the option.
IMO this is the way all apps should be, as I don't always need the root features of every app, as it adds a security risk. I like how BoldBeast Call Recorder does this for example.
bkkzak said:
I'd like to know this as well
Click to expand...
Click to collapse
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
It's a compatability mode that was automatically enabled for a while in older SuperSu.zips to allow developer's apps to work until they update their app to work with systemless root. It is now disabled by defult in newer SuperSu.zips, with the user having to explicitly enable it for its use.
Some apps that requires this to work (becuse they haven't updated their app to work with systemless yet) include:
- Secure Settings
- Es File Explorer.
Etc.Etc.
Hope this helps clarify things for you
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes
flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked
you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version
I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...
kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again
Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.
@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.
Anyone else having a problem getting these things working on 7.0?
I was pretty much stock, other than being unencrypted. I modified the build.prop to enable tethering and changed the hosts file to block ads, as I've done several other times and it won't work. I had it working just fine on NRD90M too.
So I tried rooting with SuperSU. Solid Explorer will let me change and delete stuff. ES File Explorer won't allow me to gain root access. AdAway won't let change the hosts file. It's like SU is hit or miss for some reason. I checked that the build.prop and the hosts file was changed, and they were. But they aren't doing what I want them to do.
Anyone have any insight?
brkshr said:
Anyone else having a problem getting these things working on 7.0?
I was pretty much stock, other than being unencrypted. I modified the build.prop to enable tethering and changed the hosts file to block ads, as I've done several other times and it won't work. I had it working just fine on NRD90M too.
So I tried rooting with SuperSU. Solid Explorer will let me change and delete stuff. ES File Explorer won't allow me to gain root access. AdAway won't let change the hosts file. It's like SU is hit or miss for some reason. I checked that the build.prop and the hosts file was changed, and they were. But they aren't doing what I want them to do.
Anyone have any insight?
Click to expand...
Click to collapse
busybox maybe??
i42o said:
busybox maybe??
Click to expand...
Click to collapse
Just installed BusyBox Free and updated busybox. Didn't seem to help anything
Edit: I take that back. I now have tethering and it seems it is also blocking ads. I can't get root with ES File Explorer or use AdAway, but whatever. This fixed my original complaints. This is just weird that it took BusyBox to get these working. I've been modifying build.prop and the hosts file without root/busybox for some time now and never had this problem.
brkshr said:
Just installed BusyBox Free and updated busybox. Didn't seem to help anything
Edit: I take that back. I now have tethering and it seems it is also blocking ads. I can't get root with ES File Explorer or use AdAway, but whatever. This fixed my original complaints. This is just weird that it took BusyBox to get these working. I've been modifying build.prop and the hosts file without root/busybox for some time now and never had this problem.
Click to expand...
Click to collapse
You're welcome.
i42o said:
You're welcome.
Click to expand...
Click to collapse
Sorry. Forgot my manners. Trying to get this going and working at the same time. Thank you!
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...
Lineage 17 and last version Magisk installed.
Buildprop last version installed.
Buildprop shows SuperUser rights
I want the entry then
ro.product.system.brand
change from samsung to htc
Why? To get the Samsung Wear app working for Watch 3 ...
But I got an error.
Report from BuildProp:
Please ensure the app has root ...
But they are there and are displayed under properties ...
What am I doing wrong?
Problem solved with a workaround.
Finding: You don't need a BuildProp ...
After installing MagisK you have root rights.
As a file manager you take the TotalCommander and give it root rights.
You can then access the build.prop file in the system directory and change it with the integrated text editor.
Just stupid:
My SamsungWear app still does not start.
But this is another story...