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?
Related
Hi friends;
I have HTC M8 Marshmallow with Sense 7.
I rooted my device with SuperSU 2.65.
But;
I can't edit build.prob file in system folder.
I can't put apk and lib files to system->priv-app folder.
In fact ;
I edited build.prob file in system folder. (I used Root Explorer)
I put apk and lib files to system->priv-app folder.
But, after I rebooted device edited build.prob file returned original and
deleted apk and lib file that I put to system->priv-app folder.
Before these applications I mounted system folder R/W
Why did this happen?
How can i solve this?
musti35 said:
Hi friends;
I have HTC M8 Marshmallow with Sense 7.
I rooted my device with SuperSU 2.65.
But;
I can't edit build.prob file in system folder.
I can't put apk and lib files to system->priv-app folder.
In fact ;
I edited build.prob file in system folder. (I used Root Explorer)
I put apk and lib files to system->priv-app folder.
But, after I rebooted device edited build.prob file returned original and
deleted apk and lib file that I put to system->priv-app folder.
Before these applications I mounted system folder R/W
Why did this happen?
How can i solve this?
Click to expand...
Click to collapse
Flash disable WP mod. http://forum.xda-developers.com/attachment.php?attachmentid=3564071&d=1449168286
Thank you very much.
Now everything is OK
musti35 said:
Thank you very much.
Now everything is OK
Click to expand...
Click to collapse
Add [SOLVED] to the title, so that other people can find this solution.
Imotep95 said:
Flash disable WP mod. http://forum.xda-developers.com/attachment.php?attachmentid=3564071&d=1449168286
Click to expand...
Click to collapse
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
skshakeel said:
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
Click to expand...
Click to collapse
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Sent from my htc_m8 using XDA Labs
justinchao740 said:
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Click to expand...
Click to collapse
You can't edit system files while your device s-on,you need wp module or custom kernel with wp module to edit system
Some m8 roms have this module implemented ( if not all roms )
Sent from my HTC M8 using XDA Labs
skshakeel said:
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
Click to expand...
Click to collapse
Hi
Earlier i see a post by @ckpv5 about adb manager Qtadb i can't find the post right now ( on mobile and it's hard to find )
https://qtadb.wordpress.com/download/
You can use this tool to remove system files
Reboot to twrp and mount system then connect the device with pc ( usb ) and start the tool from your pc
Give it a try
Sent from my HTC M8 using XDA Labs
justinchao740 said:
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Click to expand...
Click to collapse
You've got it wrong. Systemless root isn't the reason system is not writable. The same will occur with traditional root.
The system is write protected on this device (regardless of root method). You need the kernel mode to disable the write protection.
redpoint73 said:
You've got it wrong. Systemless root isn't the reason system is not writable. The same will occur with traditional root.
The system is write protected on this device (regardless of root method). You need the kernel mode to disable the write protection.
Click to expand...
Click to collapse
well thats what happened to me. I rooted with super su, it won't let me edit any build.prop or system files. But after i rooted with system root, it worked
Hi need help
Same problem in my device my device is not in too development
So I try to find solution on Google and find this thread..
Can I flash this file in my device my device is HTC desire 630 and also running in mm version.
So can I try to flash this file...???
vaibhav1 said:
Same problem in my device my device is not in too development
So I try to find solution on Google and find this thread..
Can I flash this file in my device my device is HTC desire 630 and also running in mm version.
So can I try to flash this file...???
Click to expand...
Click to collapse
No, it won't work. Kernels (and therefore kernel mods) are device specific. It won't work, and may harm your phone.
If the phone is rooted, you can try to mount system in a file explorer app, and apply the desired changes, to see if they stick (survive a reboot). Some folks have had success with that approach.
Be careful, and backup files accordingly. Or otherwise know how to return to stock, if anything goes wrong. Changes to system under root can result in unpredicted problems.
Further than that, I probably can't help; as I have no specific knowledge of your device.
redpoint73 said:
No, it won't work. Kernels (and therefore kernel mods) are device specific. It won't work, and may harm your phone.
If the phone is rooted, you can try to mount system in a file explorer app, and apply the desired changes, to see if they stick (survive a reboot). Some folks have had success with that approach.
Be careful, and backup files accordingly. Or otherwise know how to return to stock, if anything goes wrong. Changes to system under root can result in unpredicted problems.
Further than that, I probably can't help; as I have no specific knowledge of your device.
Click to expand...
Click to collapse
I try script but not working..
Thanks for you help
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
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2239421
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3xl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3xlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
sliding_billy said:
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
Click to expand...
Click to collapse
It's official. It works.
Tulsadiver said:
It's official. It works.
Click to expand...
Click to collapse
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
sliding_billy said:
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
Click to expand...
Click to collapse
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Tulsadiver said:
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Click to expand...
Click to collapse
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
sliding_billy said:
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
Click to expand...
Click to collapse
I pasted it again. Hopefully it works now.
Tulsadiver said:
I pasted it again. Hopefully it works now.
Click to expand...
Click to collapse
It works!
Thank you!!!!
Latest magisk canary added an adb command to remove modules if bootlopps happens ?
DvLAx3l said:
Latest magisk canary added an adb command to remove modules if bootlopps happens
Click to expand...
Click to collapse
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Tulsadiver said:
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Click to expand...
Click to collapse
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know ?
DvLAx3l said:
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know
Click to expand...
Click to collapse
Well, if it's an ADB fix, a person is going to have to, at the very least, flash boot.img (though probably system images depending on what you flashed), reboot without root. Enable the ADB mode, flash ADB commands, and reboot. Remove bad modules. Then, go back and root again.
Seems simpler to just flash the modded image-new.img, reboot with root, remove modules (with ADB if you like) and reboot.
Edit: what would be cool is an option to patch a boot.img in core-only mode, right from Magisk manager, where the other option is to patch the boot.img. All that would be needed on John's part is an edited init file in that option. That's the only difference.
Thanks for this! I could've really used this image a few times in the past...
Face_Plant said:
Thanks for this! I could've really used this image a few times in the past...
Click to expand...
Click to collapse
You and me both, buddy!
Got in to a bootloop situation with Bromite systemless webview module. I restored stock boot image and patched it with the latest canary build (the one with 'recovery mode' checked under advanced settings) and bootlooped again. I flashed this file, got in with magisk working, disabled the offending module, patched the boot image without recovery mode, then flashed the patched boot image and everything is up and running! Thanks for the help!
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Jiggs82 said:
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Click to expand...
Click to collapse
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Tulsadiver said:
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Click to expand...
Click to collapse
Yes I was able to open magisk but even if I uninstalled it I still had this weird bootlloop so before I saw this message I ended up just flashing factory 10 image clean this time just to be sure everything would flash/install successfully and luckily they did lol but thanks anyways and I will hold onto to these files for future references:good:
would the modded boot img that disables modules work for the pixel 3 as well?
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
Hi, this is Korea. I want to use the Volte option with my razr. For that, I need to modify the EFS for adding the value of the Korean telecommunication company. But the problem is this. Rooting can't make the RW mount in the system. So I can't modify build.prop and enter diag mode. What could be the problem? I unlocked boot loader, patched boot.img with magisk and finished well with magisk manager. The root checker also says it worked. If anyone succeeds in rooting, please give me advice.
zoonongk said:
Hi, this is Korea. I want to use the Volte option with my razr. For that, I need to modify the EFS for adding the value of the Korean telecommunication company. But the problem is this. Rooting can't make the RW mount in the system. So I can't modify build.prop and enter diag mode. What could be the problem? I unlocked boot loader, patched boot.img with magisk and finished well with magisk manager. The root checker also says it worked. If anyone succeeds in rooting, please give me advice.
Click to expand...
Click to collapse
You cannot mount the system in Read/Write (R/W) mode because the new system partition structure does not allow you to do so. In newer devices on Android 10, 11 all system partitions are in one big Super partition. You need to do custom firmware, rebuild the Stock firmware. I did it successfully for Motorola Edge.
ilia3367 said:
You cannot mount the system in Read/Write (R/W) mode because the new system partition structure does not allow you to do so. In newer devices on Android 10, 11 all system partitions are in one big Super partition. You need to do custom firmware, rebuild the Stock firmware. I did it successfully for Motorola Edge.
Click to expand...
Click to collapse
Thank you for your answer. Is it because it's an A/B partition device? It's sad that the solution is Custom Rom. Even TWPR doesn't have an official version. Is there any custom room I couldn't find?
zoonongk said:
Is it because it's an A/B partition device?
Click to expand...
Click to collapse
I told you in detail why. New system structure.