Related
I am trying to enable Miracast by editing build.prop but system is not mounting. Tried ES file explorer and build prop editor too. I'm on stock Oreo right now. Any means to edit build prop? Unable to mount system to r/w.
Edit : The problem is may be due to Magisk, the systemless root prevents changes in system files. All the method I've tried the problem seems to be the Magisk. SuperSU working fine.
It is a very good idea not to edit build.prop directly using Magisk. You put some resetprop command in a directory (which changed with newest Magisk, before it was some init.d), and it will be executed on startup. There are quite some threads about this, just search for it.
I asked several times how to prevent system from being mounted r/w. I don't want any app to achieve this. If you find it how you did it, please tell me what to do to enable this problem prevention.
tag68 said:
It is a very good idea not to edit build.prop directly using Magisk. You put some resetprop command in a directory (which changed with newest Magisk, before it was some init.d), and it will be executed on startup. There are quite some threads about this, just search for it.
I asked several times how to prevent system from being mounted r/w. I don't want any app to achieve this. If you find it how you did it, please tell me what to do to enable this problem prevention.
Click to expand...
Click to collapse
I don't know how to do it, I am looking for ways. There is a magisk module for build prop but the problem is it's not for Oreo so it doesn't work. I think I need to make a module but I don't know how to make one.
You do not need to do a Magisk module, although it is possible to so. You probably want to do a shell skript. This is a text file with one line
resetprop (parameters)
You may need to write more lines into it, one for every property you need to change.
Until Magisk 16.3 there was some dir post.fs where you could put startup shell scripts. This changed recently. Please search for the syntax of resetprop and which dir you need to put the skript into.
Please ask how to to do it in this thread, there were some more people which had the same task.
Edit: As usual, do not forget to read the thread before asking anything
tag68 said:
You do not need to do a Magisk module, although it is possible to so. You probably want to do a shell skript. This is a text file with one line
resetprop (parameters)
You may need to write more lines into it, one for every property you need to change.
Until Magisk 16.3 there was some dir post.fs where you could put startup shell scripts. This changed recently. Please search for the syntax of resetprop and which dir you need to put the skript into.
Please ask how to to do it in this thread, there were some more people which had the same task.
Edit: As usual, do not forget to read the thread before asking anything
Click to expand...
Click to collapse
I don't get it. How am I supposed to do this? Any tutorial?
tag68 said:
It is a very good idea not to edit build.prop directly using Magisk. You put some resetprop command in a directory (which changed with newest Magisk, before it was some init.d), and it will be executed on startup. There are quite some threads about this, just search for it.
I asked several times how to prevent system from being mounted r/w. I don't want any app to achieve this. If you find it how you did it, please tell me what to do to enable this problem prevention.
Click to expand...
Click to collapse
I've found a Magisk module that do the same stuff, it's called Magisk props config. You can add tweaks to build prop without editing it. It's so easy and helpful.
THIS IS NOT FOR FAINT OF HEART. DON'T BLAME ME IF YOU BREAK SOMETHING.
Mount system as RW in TWRP. (this took mounting, unmounting, then remounting for me)
Use the following commands CAREFULLY from a computer.
cat /system/build.prop > /sdcard/build.prop
Open the build.prop from the sdcard and edit the following line numbers: 25, 26
You are changing:
ro.product.name=perseus
ro.product.device=perseus
To this:
ro.product.name=perseus_global
ro.product.device=perseus_global
save the file on the sdcard
Go back to ADB session and do this:
cat /sdcard/build.prop > /system/build.prop
IF THIS FAILS YOUR SYSTEM IS NOT RW, UNMOUNT AND REMOUNT IN THE MOUNTS MENU.
Go back to the mounts menu and unmount /system
Flash Magisk 17.3 (18.0 seems to be having intermittent issues with passing checks)
Reboot, and enjoy your CN device running Global with ROOT.
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Great find, works!!
Thanks!!
You're welcome. I may try to make a flashable zip to do this automatically, but I haven't had a chance to look at it.
Work so well, Thanks @PWn3R!
xterminater07 said:
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Click to expand...
Click to collapse
Here is the clue. " 'C:\sdcard\build.prop'."
What is a Windows drive letter doing on an Android? Adb session?
@PWn3R YOU ARE THE MAN
Has anyone tried a custom kernel on the latest global? I tried androplus v 0.6 and it didnt really work. It allows me to replace files in system but not rename because when I overwrite it still says there is an existing file with same name.
Any kernel that works please let me know. I am working with defcomg to get gcam modded more than the current ones.
I would like to try, i already had install last global, and this rtemove my twrp instead the official recovery.... Can you give me all the steps to do from this position? Thank you
I have a problem with camera, force close no matter what I've done. may be build.prop change?
kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
i got this as well... oh well going back to xiaomi eu rom
Hi the change to the build.prop did not break the camera. Mine is working fine. Maybe clear app data for that app?
I do many times, didn't work,
---------- Post added at 11:45 PM ---------- Previous post was at 11:23 PM ----------
This is the error:
java.lang.RuntimeException: unSupported Saturation
at com.android.camera2.compat.MiCameraCompatBaseImpl.applySaturation(MiCameraCompatBaseImpl.java:248)
at com.android.camera2.compat.MiCameraCompat.applySaturation(MiCameraCompat.java:49)
at com.android.camera2.MiCamera2.applySaturation(MiCamera2.java:2486)
at com.android.camera2.MiCamera2.applyCommonSettings(MiCamera2.java:2858)
at com.android.camera2.MiCamera2.applySettingsForCapture(MiCamera2.java:2971)
at com.android.camera2.MiCamera2ShotNormal.generateRequestBuilder(MiCamera2ShotNormal.java:141)
at com.android.camera2.MiCamera2ShotNormal.startShot(MiCamera2ShotNormal.java:59)
at com.android.camera2.MiCamera2.captureStillPicture(MiCamera2.java:2042)
at com.android.camera2.MiCamera2.triggerCapture(MiCamera2.java:1892)
at com.android.camera2.MiCamera2.takePicture(MiCamera2.java:991)
at com.android.camera.module.Camera2Module.startNormalCapture(Camera2Module.java:1130)
at com.android.camera.module.Camera2Module.onWaitingFocusFinished(Camera2Module.java:406)
at com.android.camera.module.loader.camera2.FocusManager2.capture(FocusManager2.java:767)
at com.android.camera.module.loader.camera2.FocusManager2.doSnap(FocusManager2.java:326)
at com.android.camera.module.Camera2Module.onShutterButtonClick(Camera2Module.java:1057)
at com.android.camera.fragment.bottom.FragmentBottomAction.onSnapClick(FragmentBottomAction.java:1653)
at com.android.camera.ui.CameraSnapView$1.handleMessage(CameraSnapView.java:67)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6806)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
@PWn3R, the root is working but there are some functionalities that disappeared in the setting menu such as slider settings, screen color.
For those who wants to revert to CN rom, revert the changes you have done and DO NOT forget to remove Magisk by flashing the uninstaller zip otherwise the device will bootloop.
I restore the original build.prop and boot.img, the camera came back to work. Any workaround?
kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
I didn't notice if the slider settings were there before changing the build.prop. The problem here is that when you flash magisk it's enabling secure boot, which is triggering a check that normally runs when the device is locked. I think we can probably fix that by modifying the file that causes it and then this will work without build.prop changes. I have not had a chance to look into that, but will try to do so.
So, grabbed the latest OTA, and went through the usual re-root cycle, but was unable to edit the build.prop. While /root is mountable, /root/system is not, which means no tethering for me.
Anyone else running into the same issue?
I have the same issue, I've been fighting with it all day.
I patched the boot.img with Magisk Manager and flashed it, Magisk Manager show's I'm installed and Root Checker says I'm rooted, I was even able to install Adaway. But i cannot use any root app that needs to mount /System
I tried using Root Uninstaller and it says it has root access but cannot mount /system as R/W
It seems Magisk is only able to partially root on Android 10
I tried this with the Canary version and the standard version of Magisk and the same issue both times
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
bbarnes1 said:
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
Click to expand...
Click to collapse
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
This has been a problem since the Q beta came out, with each update I tried to figure something out. With no luck! I tried the Magisk Mod but it didn't seem to work.
suggestions would be most appreciated!!
Thinkin about a clean install....maybe.....
Edit: It was also a problem with the P beta until it was out of beta (That was my hope for this)
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....
Click to expand...
Click to collapse
I'm trying to add a prop, which seems like a different need, but will look into it.
tufyuma said:
Thinkin about a clean install....maybe.....
Click to expand...
Click to collapse
Was thinking about this, but realized a clean install for every update isn't worth a hotspot to me.
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I gave this a whirl, its doesn't appear to actually be change build.prop
bbarnes1 said:
I gave this a whirl, its doesn't appear to actually be change build.prop
Click to expand...
Click to collapse
It doesn't physically change anything in system. The intent is to offer the same functionality as physically editing the build.prop without modifying that file. It creates the prop and value setting and loads into into memory at boot time.....(similar to the way the build.prop file is read at boot time for those settings.) At least that is my understanding. It works for me on Android 9 for setting the prop for tethering...for example. You can confirm it works by using the getprop command to verify the prop you set is set as you intended.
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
somethingsomethingroot said:
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
Click to expand...
Click to collapse
Can you tell me what the process is that got you tethering capability?
Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it.
I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I couldn't mount anything under system so I still can't edit build.prop.
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
Thanks for posting this, it worked great on my Pixel XL on Sprint. I had about given up on being able to edit the build.prop.
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Your prop
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Are you sure that your screenshot of the props output is correct? Because it looks like you have the value set to "net.tethering.noprovisioning" and the prop name has =true in it. I'm just trying to figure this out because I've tried this and everything else trying to get my hotspot to work. My hotspot will turn on and devices can connect to it, but they don't have internet access. Any ideas at all?
Edit: Nevermind, I had the custom prop set to post fs data when it was supposed to be set at boot stage (default). My hotspot is working now. Thank you all.
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Confirming that this works on rooted pixel 4. Thank you for this btw
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
This seems to have worked for me, though I don't really understand why or what did it.
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
wolvmarine said:
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
Click to expand...
Click to collapse
Why need to turn on Hotspot for build.Prop editing? What's wamo?
truelies1 said:
Why need to turn on Hotspot for build.Prop editing? What's wamo?
Click to expand...
Click to collapse
Does anyone know a way to enable gestures on 3rd party launchers on stock rom
As this post https://forum.xda-developers.com/showpost.php?p=78125891&postcount=43 describes, I modified mixer_paths_tavil.xml changing the AVC Volume value in attribute headphones-hifi-dac, from 15 to 6, in order to achieve the AUX volume values in normal mode
The file mixer_paths_tavil.xml is saved correctly. Then I mount /vendor read-only again and remount, and I check that the file remains changed with the modification done. The modification date timestamp reflects the change
But no effect in the sound
So I guess I should reboot the phone for the change takes into effect. But then, after the reboot, the mixer_paths_tavil.xml is again the original one without the changes (and the mofication date is Dec 31 2008, the original ...)
So how should I edit this file to keep the changes with the reboot?
I'm on Pie
Thanks in advance
I know with my v30 i changed values in mixer_paths tavil.xml set permissions reboot and I was all good but my lg g7 im still trying to unlock my bootloader with the instructions but after updating magisk manager I have no root to finish the rest of the commands. I wish I could edit this same file and see whats going on and why it wont stick after reboot.
I am also facing the sam issue my bootloader is unlocked and i am rooted on android 10. Changes dont stick after reboot.
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Code:
killall audioserver
Explanation: Vendor partition in pie and android 10 is impossible to edit in case of LG G7. You need to have this file modified in magisk module with proper permissions and catalogs (vendor/etc). Even if you have audio related files modified in magisk module, there's second problem. Everything will be booted with default values. That's why you need service.sh with killall audioserver. This will reload all your audio related files at early stage of system boot, and new values will be applied.
ShuAK said:
I am also facing the sam issue my bootloader is unlocked and i am rooted on android 10. Changes dont stick after reboot.
Click to expand...
Click to collapse
Can you please tell me that how you rooted your device?
hasnawtahmed said:
Can you please tell me that how you rooted your device?
Click to expand...
Click to collapse
Are u bootloader unlocked? If not then follow this guide to unlock it.
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-updated-guide-to-unlock-t4168771
After that rooting is very simple process use QFIL to backup your boot_a img copy it to phone install magisk manager and and patch that file with magisk. Then write this img file to ur boot_a partition using QFIL and thats it.
ShuAK said:
Are u bootloader unlocked? If not then follow this guide to unlock it.
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-updated-guide-to-unlock-t4168771
After that rooting is very simple process use QFIL to backup your boot_a img copy it to phone install magisk manager and and patch that file with magisk. Then write this img file to ur boot_a partition using QFIL and thats it.
Click to expand...
Click to collapse
I have unlocked bootloader. Qfil gives an error something like firehose failed or download fail somethinh like that.
ShadoV90 said:
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Code:
killall audioserver
Explanation: Vendor partition in pie and android 10 is impossible to edit in case of LG G7. You need to have this file modified in magisk module with proper permissions and catalogs (vendor/etc). Even if you have audio related files modified in magisk module, there's second problem. Everything will be booted with default values. That's why you need service.sh with killall audioserver. This will reload all your audio related files at early stage of system boot, and new values will be applied.
Click to expand...
Click to collapse
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
ShuAK said:
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
Click to expand...
Click to collapse
I'm also using a windows 10 pc
Then reinstall drivers
ShuAK said:
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
Click to expand...
Click to collapse
You can create that file in main module catalog.
I created service.sh and copy it inside a dual speaker magisk module zip file.
Yep thnx man its working now sounds are too much lowder
ShuAK said:
I created service.sh and copy it inside a dual speaker magisk module zip file.
Yep thnx man its working now sounds are too much lowder
Click to expand...
Click to collapse
Would you mind to share the modified module? Thank you in advance
Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.
hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions
I think the root is not perfect, I can't change the permissions of the files
carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.
hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet
What are you trying to achieve?
the terminal command to try to mount as RO would you know?
_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files
carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.
I wanted to change the audio files regarding the volume, I wanted it a little higher
carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
i read android 10 problem, would you recommend me to mount with termux, installing vim?
_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls
carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module
Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?