Related
Hey there,
I accidentally updated V4a today and now it is not working anymore. Is there any chance to get the version before the latest.
Solved: dared to flash Magisk 11. Everything is working again
Magisk says 2.5.0.5 and viper driver status says 2.5.0.4
The Magisk Log
Code:
** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
/data/magisk_merge.img found
/data/magisk.img found, attempt to merge
/dev/block/loop0 /data/magisk.img
/dev/block/loop1 /data/magisk_merge.img
Merging: v4a
Merge complete
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
Mount: /dev/magisk/dummy/system/lib/soundfx
* Stage 3: Mount module items
Mount: /magisk/v4a/system/lib/soundfx/libv4a_fx_ics.so
Mount: /magisk/v4a/system/etc/audio_effects.conf
Mount: /magisk/v4a/vendor/etc/audio_effects.conf
* Stage 4: Execute module scripts
post-fs-data: /magisk/v4a/post-fs-data.sh
post-fs-data: /magisk/xposed/post-fs-data.sh
Xposed: Mount: /magisk/xposed/system/lib64/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib64/libart.so
Xposed: Mount: /magisk/xposed/system/lib64/libart-disassembler.so
Xposed: Mount: /magisk/xposed/system/lib/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib/libart.so
Xposed: Mount: /magisk/xposed/system/lib/libart-compiler.so
Xposed: Mount: /magisk/xposed/system/bin/patchoat
Xposed: Mount: /magisk/xposed/system/bin/oatdump
Xposed: Mount: /magisk/xposed/system/bin/dex2oat
Xposed: Mount: /magisk/xposed/system/bin/app_process64
Xposed: Mount: /magisk/xposed/system/bin/app_process32
* Stage 5: Mount mirrored items back to dummy
Mount: /dev/magisk/mirror/system/lib/soundfx/libvisualizer.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libreverbwrapper.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libqcomvoiceprocessing.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libqcomvisualizer.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libqcompostprocbundle.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libldnhncr.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libeffectproxy.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libdownmix.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libdirac.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libbundlewrapper.so
Mount: /dev/magisk/mirror/system/lib/soundfx/libaudiopreprocessing.so
** Magisk late_start service mode running...
just remove libvolumelistener.so
me 2 viper doesnt work for me :/
ViPER causes bootloop for me too.
ryaniskira said:
ViPER causes bootloop for me too.
Click to expand...
Click to collapse
It did not cause bootloops on my phone. It just did not work. Driver status unsupported...
ViPER won't let my phone boot at all. Does it still need ElementalX even on Magisk?
Me too. Take me a lot time to rescure.
Same here, Dolby Atmos also. I think none of them are compatible with 7.1.*
Anyone, prove me wrong?
Download and install Viper2505 Magisk module by topjohnwhu then reboot , download viper2505 on the official thread and install viper via apk. It will work after reboot.
And when driver status is okay but audio isn't being processed?
Iaa85 from Brazil with Oneplus 3t
Powered by AEX ROM
iaa85 said:
And when driver status is okay but audio isn't being processed?
Iaa85 from Brazil with Oneplus 3t
Powered by AEX ROM
Click to expand...
Click to collapse
turn off-on the master power in V4a.
i installed magisk module (flashed it) and now my S8 keeps booting to recovery, and doenst boot to system. help? Thanks!
raracin said:
i installed magisk module (flashed it) and now my S8 keeps booting to recovery, and doenst boot to system. help? Thanks!
Click to expand...
Click to collapse
Find the Mount-Magisk flashable zip in this forum and flash it via twrp. Then use file-manager in twrp, go to magisk folder and delete the viper module. Then try booting up.
i use oneplus 3 with OxygenOs 3.5.5 when i use the rom (stock) and install magisk and enable magisk hide it hides root and safetynet succeed and it unmounts
But when i start from the beginning on the stock rom and install RR on the rom (customrom) and full unroot and reinstall magisk and enable magisk hide and reboot i get this in the log and it doesn't unmount :
HTML:
MagiskHide: starting MagiskHide Daemon
MagiskHide: Unable to watch /magisk/.core/magiskhide/hidelist
any help please to get it to unmount and hide root ?
to know after i installed RR and full unrooted safetynet passed
ahmedsasker said:
i use oneplus 3 with OxygenOs 3.5.5 when i use the rom (stock) and install magisk and enable magisk hide it hides root and safetynet succeed and it unmounts
But when i start from the beginning on the stock rom and install RR on the rom (customrom) and full unroot and reinstall magisk and enable magisk hide and reboot i get this in the log and it doesn't unmount :
HTML:
MagiskHide: starting MagiskHide Daemon
MagiskHide: Unable to watch /magisk/.core/magiskhide/hidelist
any help please to get it to unmount and hide root ?
to know after i installed RR and full unrooted safetynet passed
Click to expand...
Click to collapse
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Didgeridoohan said:
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Click to expand...
Click to collapse
that is what i get and safetynet doesn't pass still ..
Code:
[email protected]:/magisk/.core/magiskhide # sh disable
MagiskHide: Stopping MagiskHide daemon
disable[27]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
1|[email protected]:/magisk/.core/magiskhide # sh enable
MagiskHide: Removing dangerous read-only system props
touch: '/magisk/.core/magiskhide/hidelist': Read-only file system
chmod: chmod '/magisk/.core/magiskhide' to 40755: Read-only file system
chmod: chmod 'rm' to 100755: Read-only file system
chmod: chmod 'list' to 100755: Read-only file system
chmod: chmod 'enable' to 100755: Read-only file system
chmod: chmod 'disable' to 100755: Read-only file system
chmod: chmod 'add' to 100755: Read-only file system
grep: /magisk/.core/magiskhide/hidelist: Bad file descriptor/magisk/.core/magiskhide/add[14]: [: 0: unexpected operator/operand
enable[65]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
MagiskHide: Starting MagiskHide daemon
to know without the magisk and have root removed with the custom rom the safetynet passes so what is wrong ?
if magisk doesn't get mounted properly how could i fix that ?
i tried to install another karnel whick support systemless root and i got bootloop maybe cuz of the custom rom RR so i can't install another karnel while the one i tried the only one i saw that support systemless root
please anyway to make magisk work ? (i tried the two versions under 12.0 too)
ahmedsasker said:
that is what i get and safetynet doesn't pass still ..
Code:
[email protected]:/magisk/.core/magiskhide # sh disable
MagiskHide: Stopping MagiskHide daemon
disable[27]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
1|[email protected]:/magisk/.core/magiskhide # sh enable
MagiskHide: Removing dangerous read-only system props
touch: '/magisk/.core/magiskhide/hidelist': Read-only file system
chmod: chmod '/magisk/.core/magiskhide' to 40755: Read-only file system
chmod: chmod 'rm' to 100755: Read-only file system
chmod: chmod 'list' to 100755: Read-only file system
chmod: chmod 'enable' to 100755: Read-only file system
chmod: chmod 'disable' to 100755: Read-only file system
chmod: chmod 'add' to 100755: Read-only file system
grep: /magisk/.core/magiskhide/hidelist: Bad file descriptor/magisk/.core/magiskhide/add[14]: [: 0: unexpected operator/operand
enable[65]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
MagiskHide: Starting MagiskHide daemon
to know without the magisk and have root removed with the custom rom the safetynet passes so what is wrong ?
if magisk doesn't get mounted properly how could i fix that ?
i tried to install another karnel whick support systemless root and i got bootloop maybe cuz of the custom rom RR so i can't install another karnel while the one i tried the only one i saw that support systemless root
please anyway to make magisk work ? (i tried the two versions under 12.0 too)
Click to expand...
Click to collapse
Looks like what for a strange reason /magisk is mounted as read-only. Try mount as rw:
Code:
mount -w -o remount /magisk
Deic said:
Looks like what for a strange reason /magisk is mounted as read-only. Try mount as rw:
Code:
mount -w -o remount /magisk
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /magisk
[email protected]:/ # cd /magisk/.core/magiskhide
[email protected]:/magisk/.core/magiskhide # she disable
sh: she: not found
127|[email protected]:/magisk/.core/magiskhide # sh disable
MagiskHide: Stopping MagiskHide daemon
disable[27]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
1|[email protected]:/magisk/.core/magiskhide # sh enable
MagiskHide: Removing dangerous read-only system props
touch: '/magisk/.core/magiskhide/hidelist': Read-only file system
chmod: chmod '/magisk/.core/magiskhide' to 40755: Read-only file system
chmod: chmod 'rm' to 100755: Read-only file system
chmod: chmod 'list' to 100755: Read-only file system
chmod: chmod 'enable' to 100755: Read-only file system
chmod: chmod 'disable' to 100755: Read-only file system
chmod: chmod 'add' to 100755: Read-only file system
grep: /magisk/.core/magiskhide/hidelist: Bad file descriptor/magisk/.core/magiskhide/add[14]: [: 0: unexpected operator/operand
enable[65]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
MagiskHide: Starting MagiskHide daemon
[email protected]:/magisk/.core/magiskhide #
I still get the same result ...
ahmedsasker said:
I still get the same result ...
Click to expand...
Click to collapse
If you type just:
Code:
su
mount
and look for a line that starts something like:
Code:
/dev/block/loop0 on /magisk
In the parenthesis at the end of the line, the text should start with "rw". Does it?
Didgeridoohan said:
If you type just:
Code:
su
mount
and look for a line that starts something like:
Code:
/dev/block/loop0 on /magisk
In the parenthesis at the end of the line, the text should start with "rw". Does it?
Click to expand...
Click to collapse
No it it does start with ro
Code:
/dev/block/loop0 on /magisk type ext4 (ro,seclabel,noatime,data=ordered)
ahmedsasker said:
No it it does start with ro
Code:
/dev/block/loop0 on /magisk type ext4 (ro,seclabel,noatime,data=ordered)
Click to expand...
Click to collapse
Ok. Next, try:
Code:
mount -o remount,rw /magisk
If that doesn't work, try:
Code:
mount -o remount,rw -t ext4 /dev/block/loop0 /magisk
Didgeridoohan said:
Ok. Next, try:
Code:
mount -o remount,rw /magisk
If that doesn't work, try:
Code:
mount -o remount,rw -t ext4 /dev/block/loop0 /magisk
Click to expand...
Click to collapse
I tried both and it keeps telling me that it is read-only
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /magisk
'/dev/block/loop0' is read-only
ount -o remount,rw -t ext4 /dev/block/loop0 /magisk <
'/dev/block/loop0' is read-only
ahmedsasker said:
I tried both and it keeps telling me that it is read-only
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /magisk
'/dev/block/loop0' is read-only
ount -o remount,rw -t ext4 /dev/block/loop0 /magisk <
'/dev/block/loop0' is read-only
Click to expand...
Click to collapse
Hm... I have no idea...
From your earlier posts I assume you've already uninstalled and reinstalled Magisk a few times, right? Have you tried an unofficial beta snapshot (both Magisk and the Manager)?
I still say you should try a different kernel. I don't know what you mean with "supports systemless root", but I'd try flashing a kernel like Elemental over the one that comes with RR and then install Magisk. Maybe even try installing and running Kernel Auditor, like it says in the link I posted earlier.
Didgeridoohan said:
Hm... I have no idea...
From your earlier posts I assume you've already uninstalled and reinstalled Magisk a few times, right? Have you tried an unofficial beta snapshot (both Magisk and the Manager)?
I still say you should try a different kernel. I don't know what you mean with "supports systemless root", but I'd try flashing a kernel like Elemental over the one that comes with RR and then install Magisk. Maybe even try installing and running Kernel Auditor, like it says in the link I posted earlier.
Click to expand...
Click to collapse
I meant that it was written that it supports systemless root in the XDA forums plus I tried to flash elementalx karnel and went into boot loop ...
I'll try the snapshot one now and thanks alot <3
ahmedsasker said:
I meant that it was written that it supports systemless root in the XDA forums plus I tried to flash elementalx karnel and went into boot loop ... How can I uninstall the elementalx karnel to try another one without reflashing the whole rom ?
I'll try the snapshot one now and thanks alot <3
Click to expand...
Click to collapse
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Didgeridoohan said:
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Click to expand...
Click to collapse
OMG thanks alot it works well now and passes with the snapshot version <3
thanks again x3
Didgeridoohan said:
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Click to expand...
Click to collapse
please do you know compatible version of systemless xposed with snapshot magisk ! cuz latest v87 after I flash it, closed installer says that there's not framework installed but normal official one works
systemless xposed v87 was working fine on magisk v12
i installed the official one now and it is working very well
what is the difference between systemless xposed and the normal one ? (cuz both got caught by safety net)
ahmedsasker said:
please do you know compatible version of systemless xposed with snapshot magisk ! cuz latest v87 after I flash it, closed installer says that there's not framework installed but normal official one works
systemless xposed v87 was working fine on magisk v12
i installed the official one now and it is working very well
what is the difference between systemless xposed and the normal one ? (cuz both got caught by safety net)
Click to expand...
Click to collapse
It's very likely the Xposed Magisk module needs to be updated to work with v13... I don't use Xposed though, so I wouldn't know.
The difference between system and systemless xposed is that one is installed into system and the other one is systemless. :laugh: Seriously... That's the difference. They'll both trigger SafetyNet. Systemlessness is not about passing SafetyNet.
Didgeridoohan said:
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Click to expand...
Click to collapse
In my device, no file in /magisk/...why?:crying::crying:
Hooxp17 said:
In my device, no file in /magisk/...why?:crying::crying:
Click to expand...
Click to collapse
No idea. I can't see your device and I can't read your mind... Meaning: you've given very few details.
I'm gonna make a guess though: are you taking about the ".core" folder? It's a hidden folder, so if your file explorer isn't set to see hidden files and folders you won't see it.
If this is not your issue, give more details.
Didgeridoohan said:
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Click to expand...
Click to collapse
Which ROM? How to Dirty Flash? I have G5 Plus
brandonsisco said:
Which ROM? How to Dirty Flash? I have G5 Plus
Click to expand...
Click to collapse
Uhm... That was a specific advice for a specific issue...
What's your issue?
Didgeridoohan said:
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Click to expand...
Click to collapse
hello, i have a problem with magisk, so i found your post. but in the terminal emulator can't see this file.. can you help me?
Hi everyone,
in pixel 2, I can get super su for adb shell, and can remount the system, /vendor partition
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
but in pixel 3 with magisk 18 or 19, I always fail to remount /vendor
blueline:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-1'->'/vendor': I/O error
I need to modify some file under/vendor/etc
I've disable Preserve AVB 2.0/dm-verity and Preserve forceencryption in advanced Settings from Magisk, unfortunately do no avail,
any idea is appreciated
misslebulletttttt said:
Hi everyone,
in pixel 2, I can get super su for adb shell, and can remount the system, /vendor partition
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
but in pixel 3 with magisk 18 or 19, I always fail to remount /vendor
blueline:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-1'->'/vendor': I/O error
I need to modify some file under/vendor/etc
I've disable Preserve AVB 2.0/dm-verity and Preserve forceencryption in advanced Settings from Magisk, unfortunately do no avail,
any idea is appreciated
Click to expand...
Click to collapse
This isn't working for me either. Tried with TWRP and regular module install. My changes to files on /vendor/etc just get overwritten. On magisk 18 and Pie.
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
loserinru said:
This isn't working for me either. Tried with TWRP and regular module install. My changes to files on /vendor/etc just get overwritten. On magisk 18 and Pie.
Click to expand...
Click to collapse
so do I, want to move some file to /vendor/etc, adb push definitely not working, so copy to /sdcard,
mount -o rw,remount -t auto /vendor
cp /sdcard/XXX /vendor,
however
mount -o rw,remount -t auto /vendor
always show mount: '/dev/block/dm-1'->'/vendor': I/O error,
tried with the movement in TWRP, but after booting into system, it's gone,
any other method to overcome ?
Didgeridoohan said:
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
Click to expand...
Click to collapse
Hi, I've copied the new file to sdcard, boot into TWRP, in TWRP do the file movement from sdcard to /vendor/etc with success, however, every time after booting into system, the modification is gone, same as the guy replied in the second thread,
any method for the movement is pretty appreciated
Magisk is not active in TWRP, so there's something else going on... Check /sbin/.magisk/mirror/vendor/etc if the modification is there, and take a look at the Magisk log (you'll need the Canary debug build for more verbose logging) if anything shows there.
Didgeridoohan said:
Magisk is not active in TWRP, so there's something else going on... Check /sbin/.magisk/mirror/vendor/etc if the modification is there, and take a look at the Magisk log (you'll need the Canary debug build for more verbose logging) if anything shows there.
Click to expand...
Click to collapse
I solved this by modifying the install script of Magisk,
if [ -z $KEEPVERITY ]; then
if $SYSTEM_ROOT; then
- KEEPVERITY=true
+ KEEPVERITY=false
ui_print "- System-as-root, keep dm/avb-verity"
else
KEEPVERITY=false
fi
fi
and install Magisk again in TWRP
this can help to disable dm-verity completely, now I can remount /vendor without I/O error
Didgeridoohan said:
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
Click to expand...
Click to collapse
Riiii I always do system edits threw twrp instead of Un mounting modules like viper and air audio plug-in and do systemless system edits threw the OS
Sent from my SM-J327P using Tapatalk
I have Moto E4 plus Nicklaus. It's rooted by magisk and installed xposed magisk module. That worked but,,,, when trying edit build.prop, I got trouble.
I can't mount system directory to RW. That's always back to RO. I use es file explorer n root explorer to do that.
I try install kernel r3 by samarv via twrp, it work.
After boot I try edit build.prop and i did it. But around less from 1 hour, I try edit build.prop again but failed. The problem is I can't mount RW system directory again.
I not try install kernel again, it's look not the right way to solve this. But I try to non active all magisk module, but failed.
Can't someone help me???
I try mount via termux, but failed. There come massage "device or resource is busy"
I use this:
/system/bin/mount -o remount,rw /system
, And this:
mount -o remount,rw /system
Screenshot:
https://www.mediafire.com/view/smcztlosyrqciyr/Screenshot_20190817-231517.png/file
I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
groston said:
I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
Click to expand...
Click to collapse
I haven't used this, but maybe it can help you.
Lughnasadh said:
I haven't used this, but maybe it can help you.
Click to expand...
Click to collapse
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
groston said:
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
Click to expand...
Click to collapse
I've never used this before but I believe once you flash the module it makes the /system RW so you can start making modifications. There's a README that provides some information. I don't know of any other guides besides the information on that Github page.
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
simplepinoi177 said:
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
Click to expand...
Click to collapse
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
groston said:
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
Click to expand...
Click to collapse
When you say "gave it the appropriate permissions", just to confirm -- that doesn't mean that you changed the security permissions on the folder & files, correct? I hope it means you did not do what the OP in that thread had done and actually did enable root access particularly (hoping that's what you meant on "gave it appropriate permissions").
Because, in certain cases, I've changed permissions on files/folders vs. simply enabling root access mode....
Apologies in advanced if my inquiry seems fairly obvious (to the point of insulting maybe; it is not meant to be), but you never know and many foolish things has been done/assumed on this site that missed many (obvious) things because it wasn't confirmed....