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...
Related
Make a backup of /system/build.prop file
Open /system/build.prop in text editor (one way to do this is via Root Explorer) and locate line that starts from "ro.build.fingerprint"
Edit this line to read:
ro.build.fingerprint=google/passion/passion:2.3.6/GRK39F/189904:user/release-key
Save the file. Reboot. You may be asked one more time to install update but after that you will no longer be asked.
Thanks to user efrant for providing me with this value.
This change makes OTA think you already have this update installed. "Settings/About phone" will still show correct information about OS version that you now have on your phone.
Note that if newer OTA updates are released you will need to edit this line again.
Easier to just "Freeze" DMClient.
If I remember correctly with this update is lost and the super-user recovery.
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.
EDIT: Fixed by flashing latest factory images via fastboot, then the latest TWRP, then MagiskSU.
Hi there,
I'm rooted on stock 7.1.1 but I can't seem to make write changes consistently on the system partition. I was trying to rename NotoColorEmoji.ttf in /system/fonts so I could copy across the version with the iOS emojis, and somehow the rename worked so it's now named NotoColorEmojiOld.ttf - I managed to do this with root permissions in Solid Explorer. However, when I try and copy across the new NotoColorEmoji.ttf to the fonts folder, Solid Explorer says it's unable to do so. I've tried rebooting into TWRP, mounting system and using the file manager but it fails with Error 1. What's worse is I can't seem to rename NotoColorEmojiOld.ttf back to NotoColorEmoji.ttf either - neither Solid Explorer nor TWRP work for this despite both obviously having root access, both throw errors. As a result I have no emoji font file so all my emojis are blank boxes.
Any help in fixing this would be appreciated!
Try flashing a zip version of notocolor in twrp
CarteNoir said:
Hi there,
I'm rooted on stock 7.1.1 but I can't seem to make write changes consistently on the system partition. I was trying to rename NotoColorEmoji.ttf in /system/fonts so I could copy across the version with the iOS emojis, and somehow the rename worked so it's now named NotoColorEmojiOld.ttf - I managed to do this with root permissions in Solid Explorer. However, when I try and copy across the new NotoColorEmoji.ttf to the fonts folder, Solid Explorer says it's unable to do so. I've tried rebooting into TWRP, mounting system and using the file manager but it fails with Error 1. What's worse is I can't seem to rename NotoColorEmojiOld.ttf back to NotoColorEmoji.ttf either - neither Solid Explorer nor TWRP work for this despite both obviously having root access, both throw errors. As a result I have no emoji font file so all my emojis are blank boxes.
Any help in fixing this would be appreciated!
Click to expand...
Click to collapse
Are you using either phh superuser or magisksu?
Try changing your SELinux to Permissive with this app https://forum.xda-developers.com/showthread.php?t=2524485
bozinsky73 said:
Try flashing a zip version of notocolor in twrp
Click to expand...
Click to collapse
I get "set_perm: some changes failed, Updater process ended with ERROR: 7" and it doesn't work.
blitzkriegger said:
Are you using either phh superuser or magisksu?
Click to expand...
Click to collapse
Nope, just plain old systemless SuperSU.
collinjames said:
Try changing your SELinux to Permissive with this app https://forum.xda-developers.com/showthread.php?t=2524485
Click to expand...
Click to collapse
For some reason the app claims I don't have root permission despite the SuperSU dialog popping up and me granting it root.
CarteNoir said:
I get "set_perm: some changes failed, Updater process ended with ERROR: 7" and it doesn't work.
Nope, just plain old systemless SuperSU.
For some reason the app claims I don't have root permission despite the SuperSU dialog popping up and me granting it root.
Click to expand...
Click to collapse
Selinux didn't work for me at first on 7.1.1, I got the same error as you. But I went into twrp made sure system mounted, go into twrp terminal and cd into /system/bin and /system/xbin and in both of these directories type in (touch su) with out parenthesis. Reboot and see if that makes selinux changer works now.
Fe Mike said:
Selinux didn't work for me at first on 7.1.1, I got the same error as you. But I went into twrp made sure system mounted, go into twrp terminal and cd into /system/bin and /system/xbin and in both of these directories type in (touch su) with out parenthesis. Reboot and see if that makes selinux changer works now.
Click to expand...
Click to collapse
That got the app working and I was able to change SELinux to permissive, but I still can't make lasting changes to /system unfortunately.
Bumping - anyone else have any ideas? I'm not so much concerned with not being able to change emoji fonts as I am concerned with the ramifications of not having system write access - if anything breaks or comes up in the future that I need rw system for, I won't be able to fix stuff unless I sort this out.
Hi !
My phone was rooted once, I flashed new system via Odin to uproot my phone but knox is not working nor S-Health.
S7Edge SM-G935F 7.0 Enyxos
Thanks for your replies.
Howzer95 said:
Hi !
My phone was rooted once, I flashed new system via Odin to uproot my phone but knox is not working nor S-Health.
S7Edge SM-G935F 7.0 Enyxos
Thanks for your replies.
Click to expand...
Click to collapse
If you ever rooted your phone, the knox e-fuse is blown permanently.
You can check this by going into download mode and you'll see knox status as 0x1 (tripped) instead of 0x0.
There is no way to reset this, you will have to go back to a rooted/custom rom with Masgisk and use Magisk Hide to simulate a knox 0x0 for apps. This may not work forever.
S-Health
You can still use s-health by doing the following which i have done and it works..
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
Error
chainsuk said:
You can still use s-health by doing the following which i have done and it works..
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
Click to expand...
Click to collapse
Is not working on my S7 G930. It os pop up one error: Root access is required to edit system properties. Is not let me to do any changes, from 1 to 0, what should I do? Thx in advance for help.
Try adb
Andromega, can you share how to fix this using adb?
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