Related
After the flash of V20a EUR-xx I would like to change my bootanimation and make some changes in my build.prop.
But it's not possible because the system partition is read only and it's not possible for me to change.
Root explorer did not work.
For this reason for example the use of faster GPS is not possible
Any help to make the system partition writable would be great.
Regards
mkpcxxl
Edit: Found solution by myself. Flashed no-verity-opt-encrypt-4.1.zip and now it works.
+
looking for help with that too. Nothing works: terminal on android; app mount system rw; adb shell; root explorers.
Same here ...
Tried TWRP 3.0.2.1 - Beta 1
... TWRP 3.0.2.1
no-verity-opt-encrypt-4.1
SuperSU v2.78
SuperSU v2.78 SR4
Normal wipe, Format data, etc. etc. ....
Can´t get the system to R/W
FX File Explorer lets me turn system to R/W with root but nothing is permanent ( build.prop entries ) and deletes are overwritten and not permanent
SD maid wont let me delete bloat apps ....
Anyone an idea?
Hey guys. I know how to mount system as R/W (It's not forever but you can operate on system files).
App "Root Explorer" can mount system. Thanks to @marco_wack
This guide is to help anyone who wants to use Android Pay but his XC phone is unlocked and rooted. It begins with an unlocked phone with a valid backup of the TA partition as well as an unrooted /system partition.
Prerequisites:
1. A backup of TA partition (https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236)
2. Unlocked bootloader
3. Working fastboot driver and command
4. Clean /system partition without any trace of su. Systemless root is fine because it will be overwritten by the new kernel. If needed, flash the stock system partition again.
5. TWRP image for XC (https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM)
6. Stock kernel image (Extract kernel.sin from official FTF)
7. Trim Area Proof Of Concept (https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893)
8. Tobias kernel repack tool (https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605)
9. Magisk v12.0 flashable zip, not Manager app (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Procedures:
1. Run TA PoC (DOUBLECLICKME.bat). You'll be asked to select your kernel image (kernel.sin) and TA backup (your TA backup file). Choose also to disable DM-Verity, Sony RIC but keep Force-encrypt (my data partition is encrypted, your choice). At the end a new file new_boot.img will be created.
2. Copy the new_boot.img in step 1 to Tobias tool folder. In the same folder, execute the following command. Again, disable Sony RIC, don't install TWRP, don't install DRM fix and don't install Busybox. At the end, another file boot.img will be created.
Code:
rootkernel.cmd new_boot.img boot.img
3. Power off your phone. Power on again while holding volume up rocker to enter fast boot mode. Execute the following command to flash the new boot image. Replace boot.img with your new image in step 2 with full path.
Code:
fastboot.exe flash boot [I]boot.img[/I]
4. Reboot your phone. No root or SuperSU app should be found.
5. Copy Magisk zip file into phone internal storage.
6. Dial *#*#7378423#*#*, followed by Service Test > Security to check if DRM is detected properly. At this point of time, your phone should be su free and DRM working properly.
7. Power off your phone. Power on again while holding volume up rocker to enter fast boot mode. Execute the following command to boot TWRP. Replace twrp.img with your TWRP image with full path.
Code:
fastboot.exe boot [I]TWRP.img[/I]
8. In TWRP, flash Magisk zip
9. Reboot your phone. Install Magisk Manager app (no long available in Play Store) (http://tiny.cc/latestmanager)
10. Run Magisk Manager and turn on Magisk Hide. You should see Magisk installed successfully and properly rooted with MagiskSU. Tap SafetyNet button to check if it can be passed.
11. (optional) Install Xposed using Magisk app, not official method. Xposed will break Safety Net again. But you can always disable it in Magisk Manager easily.
Remarks:
1. Trim Area Proof Of Concept is required to restore full DRM functionality so that Safety Net thinks the phone is still locked.
2. /system partition must be clean and free of any trace of previous su installation.
3. Magisk Manager app cannot be used to install Magisk because it requires root in the first place. Even with systemless root, after Magisk is installed this way, trace of su can be found in /vendor partition.
4. Tobias tool has to be used to repack the boot image because I found that if PoC image is used directly, phone will reboot unexpectedly after Magisk is installed.
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
itandy said:
1. Run TA PoC (DOUBLECLICKME.bat). You'll be asked to select your kernel image (kernel.sin) and TA backup (your TA backup file). Choose also to disable DM-Verity, Sony RIC but keep Force-encrypt (my data partition is encrypted, your choice). At the end a new file new_boot.img will be created.
Click to expand...
Click to collapse
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
itandy said:
2. Copy the new_boot.img in step 1 to Tobias tool folder. In the same folder, execute the following command. Again, disable Sony RIC, don't install TWRP, don't install DRM fix and don't install Busybox. At the end, another file boot.img will be created.
Click to expand...
Click to collapse
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
itandy said:
6. Dial *#*#7378423#*#*, followed by Service Test > Security to check if DRM is detected properly. At this point of time, your phone should be su free and DRM working properly.
Click to expand...
Click to collapse
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
trewelu said:
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
Click to expand...
Click to collapse
Your understanding is correct. As for busybox, I didn't install it because I don't use it. You can try and see if it affects Safety Net detection.
Yes, system partition can be updated without losing root.
trewelu said:
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
Click to expand...
Click to collapse
Just found that you can actually enable busybox in Magisk Manager so you don't have to pack it into the boot image.
Sent from my F5321 using Tapatalk
Done the step above and gained root and pass safety check in magisk.
Is there a way to disable the bootloader unlocked message during boot? I don't mind the message but it delay booting process I
trewelu said:
Done the step above and gained root and pass safety check in magisk.
Is there a way to disable the bootloader unlocked message during boot? I don't mind the message but it delay booting process I
Click to expand...
Click to collapse
I'm not aware anyone is able to do that so far.
itandy said:
I'm not aware anyone is able to do that so far.
Click to expand...
Click to collapse
You would need to alter bootloader....
Remark for Android 7.0 Users
If you will use this guide on Nougat, you will need to DISABLE force-encrypt, because data partition is encrypted by default on Nougat. On top of that, you will need to first boot to TWRP, wipe DATA partition without decrypting / mounting it and then reboot system to re-create unencrypted data partition. Only then you can flash Magisk..
ondrejvaroscak said:
If you will use this guide on Nougat, you will need to DISABLE force-encrypt, because data partition is encrypted by default on Nougat. On top of that, you will need to first boot to TWRP, wipe DATA partition without decrypting / mounting it and then reboot system to re-create unencrypted data partition. Only then you can flash Magisk..
Click to expand...
Click to collapse
Just curious, I'm on MM and my data partition is encrypted. But I didn't have to decrypt it first before installing Magisk. Is there anything on Nougat that makes it different?
itandy said:
Just curious, I'm on MM and my data partition is encrypted. But I didn't have to decrypt it first before installing Magisk. Is there anything on Nougat that makes it different?
Click to expand...
Click to collapse
Yes, quite substantially .... the TWRP does NOT support /data decryption on Nougat. On MM it works, on Nougat there is no way, until someone compiles TWRP with support for Nougat encrypted /data. The workaround is to DISABLE force-encrypt, wipe /data to force re-create unencrypted /data, install anything you need and then encrypt in Settings/Security. Once you do it, there is no way to get into /data in recovery...
ondrejvaroscak said:
Yes, quite substantially .... the TWRP does NOT support /data decryption on Nougat. On MM it works, on Nougat there is no way, until someone compiles TWRP with support for Nougat encrypted /data. The workaround is to DISABLE force-encrypt, wipe /data to force re-create unencrypted /data, install anything you need and then encrypt in Settings/Security. Once you do it, there is no way to get into /data in recovery...
Click to expand...
Click to collapse
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
itandy said:
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
Click to expand...
Click to collapse
I don't think so. I just re-did the step (accidentally locked back my bootloader when trying to remove the unlocked message). On twrp, it ask for password which I don't even know as after BL unlock wipe, I haven't set my screen lock yet. I skip that part, mount the sd card and flash magisk. Magisk modify the boot image and I can have root and safety net working.
Ps: You might need to update the step, the magisk manager stub will force you to download the app from play store, but it is already pulled. I need to download the app directly from magisk thread and side load it.
Edit: I was wrong. Magisk do use /data for magisk.img, but it have workaround instalation in case it is inaccessible during flashing install script. See #15
trewelu said:
Ps: You might need to update the step, the magisk manager stub will force you to download the app from play store, but it is already pulled. I need to download the app directly from magisk thread and side load it.
Click to expand...
Click to collapse
Updated. Thanks!
itandy said:
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
Click to expand...
Click to collapse
Magisk installs file magisk.img into /data. This file is than mounted as /magisk. I am not sure, how Magisk handles installation if /data is not accesible/mountable during flashing, did not try it.
ondrejvaroscak said:
Magisk installs file magisk.img into /data. This file is than mounted as /magisk. I am not sure, how Magisk handles installation if /data is not accesible/mountable during flashing, did not try it.
Click to expand...
Click to collapse
I'm not good with script, but here is my understanding,
In case of inaccessible data during flash, magisk will flash magisk.img temporarily in cache partition. During booting (after data is unencrypted), magisk check if the workaround image in cache exist and move it to data
scripts/flash_script.sh
Code:
if (is_mounted /data); then
IMG=/data/magisk.img
else
IMG=/cache/magisk.img
ui_print "- Data unavailable, use cache workaround"
fi
jni/daemon/bootstages.c
Code:
// Merge images
if (merge_img("/cache/magisk.img", MAINIMG))
goto unblock;
if (merge_img("/data/magisk_merge.img", MAINIMG))
goto unblock;
jni/magisk.h
Code:
#define MAINIMG "/data/magisk.img"
trewelu said:
I'm not good with script, but here is my understanding,
In case of inaccessible data during flash, magisk will flash magisk.img temporarily in cache partition. During booting (after data is unencrypted), magisk check if the workaround image in cache exist and move it to data
Click to expand...
Click to collapse
Cool, very clever. I did not make the effort to study in in depth, but expected some sort of solution to exist when users succesfully installed Magisk even when they can not mount /data in TWRP. This temporary /cache mount is just nice example of clever programming
Hey, I think I pseudo-bricked my device while following these steps. I used fastboot to boot into TWRP, without disabling encryption, on Nougat 7.1. I didn't notice the requirement to disable encryption in Post #8 until afterwards.
Now the device appears to be on (my computer detects an unknown device when I plug it in), but it doesn't show any LEDs or react to any buttons. Is my only recourse to wait till the battery dies in a few days and try again, or is there another way?
HAHA, I found if I hold EVERY button (power, vol up, vol dn, and camera), the phone restarts and I have access again. w00t!
Just wondering if somebody tried this with Nougat 7.1? I can't get TA_POC to work, security test displays error and sim card is not detected.
baz1 said:
Just wondering if somebody tried this with Nougat 7.1? I can't get TA_POC to work, security test displays error and sim card is not detected.
Click to expand...
Click to collapse
Yes this works with 7.1 the same as with 7.0. How did you perform the update to 7.1?
I followed the guide to perfection, and everything works perfectly...but...If I want to turn a user app into system apps, link2sd gives me this error: mount: '/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy" and system app mover gives me this error : "could not remount /system".
is system read only? why? I've already tried to enable "rw" "ro" through the command line without success...
Can anyone help me?
p.s. I have granted root permissions to the applications mentioned above at their opening
Hello.
I'm using Xiaomi Pocophone F1 (Global Edition). Upgraded from Android Oreo (8.1) MIUI Global 10.0.6.0 to Android Pie (9.0) MIUI Global 10.1.3.1 using system update (choose update package), then it will update through custom recovery, TWRP. The phone is root using Magisk v18.0.
Before I upgrade to Android Pie, I was able to move files from internal storage and SD Card to /system folder, such as bootanimation.zip. I'm using ES File Explorer Pro as a File Manager, and I already enable the Root Explorer in the tools tab. Next, I able to flash ARISE Sound Systems such as Viper4Arise, Dolby Digital Plus and Dolby Atmos. It works pretty good.
Right after I upgrade my phone to Android Pie, I can no longer create, move, modify files in /system folder. Moving files using the TWPR File Manager also failed. I also can't flash ARISE Sound Systems sound mod. There's no error flashing the sound mod, but after rebooting, the phone is still the same, no Viper4Arise, Dolby Digital Plus or Dolby Atmos was found.
Outside the system folder, (the root folder, "/"), I'm able to move the bootanimation from my internal storage and SD card to there.
I tried changing the ro.debuggable = 1, ro.secure = 0, ro.build.type = userdebug, using the MagiskHide Props Config modules. I don't know if that have something to do with my problem, but still no luck. I also have Busybox enabled in Magisk modules.
It seems like there's a problem with the system folder. Maybe it's because of Android Pie? Or the File Manager itself? Or Magisk? Who knows.
Below I provide you the screenshots of the result when I tried to move my bootanimation.zip file to /system folder.
I hope someone could help me with my problem. Thank you for taking your time to read my thread.
- Chaorrupted X - said:
Hello.
I'm using Xiaomi Pocophone F1 (Global Edition). Upgraded from Android Oreo (8.1) MIUI Global 10.0.6.0 to Android Pie (9.0) MIUI Global 10.1.3.1 using system update (choose update package), then it will update through custom recovery, TWRP. The phone is root using Magisk v18.0.
Before I upgrade to Android Pie, I was able to move files from internal storage and SD Card to /system folder, such as bootanimation.zip. I'm using ES File Explorer Pro as a File Manager, and I already enable the Root Explorer in the tools tab. Next, I able to flash ARISE Sound Systems such as Viper4Arise, Dolby Digital Plus and Dolby Atmos. It works pretty good.
Right after I upgrade my phone to Android Pie, I can no longer create, move, modify files in /system folder. Moving files using the TWPR File Manager also failed. I also can't flash ARISE Sound Systems sound mod. There's no error flashing the sound mod, but after rebooting, the phone is still the same, no Viper4Arise, Dolby Digital Plus or Dolby Atmos was found.
Outside the system folder, (the root folder, "/"), I'm able to move the bootanimation from my internal storage and SD card to there.
I tried changing the ro.debuggable = 1, ro.secure = 0, ro.build.type = userdebug, using the MagiskHide Props Config modules. I don't know if that have something to do with my problem, but still no luck. I also have Busybox enabled in Magisk modules.
It seems like there's a problem with the system folder. Maybe it's because of Android Pie? Or the File Manager itself? Or Magisk? Who knows.
Below I provide you the screenshots of the result when I tried to move my bootanimation.zip file to /system folder.
I hope someone could help me with my problem. Thank you for taking your time to read my thread.
Click to expand...
Click to collapse
I personally have almost the same setup as you (magisk 18 but updated using stock recovery) and have no issue using jrummy root browser (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree). Try with it
Blendman974 said:
I personally have almost the same setup as you (magisk 18 but updated using stock recovery) and have no issue using jrummy root browser (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree). Try with it
Click to expand...
Click to collapse
It's okay. My problem has been solved. I flash the rom (same version as I'm using) through the TWRP, without wiping anything (except dalvik cache). Root with Magisk. Now I can create, move and modify files in the /system folder.
Thanks for the suggestion anyway. I did try the jrummy Root Browser before I flash the rom through TWRP, but it's still the same.
I guess there's problem during my first upgrade to Android Pie.
- Chaorrupted X - said:
It's okay. My problem has been solved. I flash the rom (same version as I'm using) through the TWRP, without wiping anything (except dalvik cache). Root with Magisk. Now I can create, move and modify files in the /system folder.
Thanks for the suggestion anyway. I did try the jrummy Root Browser before I flash the rom through TWRP, but it's still the same.
I guess there's problem during my first upgrade to Android Pie.
Click to expand...
Click to collapse
Google enhanced the security on Android 9 including the Safetynet. I think that's the reason why we can't just deliberately create nor modify /system partition
Hello. I installed emui 9.1 on my mate20pro with the dload method. I unlocked the bootloader again and rooted the system with patched recovery. The phone is rooted, but the system partition remains in ro. I have tried various apps to mount the system in rw, but without success. I have also tried some commands found on the net both through adb and emulator, but nothing to do. I have also tried using rootexplorer which has been granted root permissions, but fails to modify anything, nor to insert or delete files within the system folders. What can be done?
ernia66 said:
Hello. I installed emui 9.1 on my mate20pro with the dload method. I unlocked the bootloader again and rooted the system with patched recovery. The phone is rooted, but the system partition remains in ro. I have tried various apps to mount the system in rw, but without success. I have also tried some commands found on the net both through adb and emulator, but nothing to do. I have also tried using rootexplorer which has been granted root permissions, but fails to modify anything, nor to insert or delete files within the system folders. What can be done?
Click to expand...
Click to collapse
it's the new filesystem called erofs (Extendable Read-Only File System)
So there's nothing to do?
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
ernia66 said:
So there's nothing to do?
Click to expand...
Click to collapse
Magisk can already 'replace on the fly' file from /system systemless-y.
It dies already support erofs.
Check Magisk documentations.
There is also a way to mount custom erofs partition....
which is?
ernia66 said:
which is?
Click to expand...
Click to collapse
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
Unfortunately I am not able to do it
:crying:
pvillasuso said:
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
Click to expand...
Click to collapse
use search button pls, you will find the solution already posted
ilos said:
use search button pls, you will find the solution already posted
Click to expand...
Click to collapse
Shhh
Here Rootexplorer paying app does not help writing on erofs partitions...
- Or did you meant something else ?
Magisk Doc. :
https://topjohnwu.github.io/Magisk/
So far, out-of-the-box, Magisk is already ready to replace systemless-ly files and paths on /system easily when used with modules.
-Module just need a a small tweak to add Magisk systemless-ly compatibility to other erofs partitions like /cust
Another way would be to bind or mount...
ilos said:
use search button pls, you will find the solution already posted
Click to expand...
Click to collapse
Wow , what , where ???
I did search but maybe I didnt use the right keywords for such an specific issue
Any extra help , would be very appreciated !
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
I'd like to create my own partition but I don't know how to do it. Is there any online guide for beginners that I can try?
oslo83 said:
Shhh
Here Rootexplorer paying app does not help writing on erofs partitions...
- Or did you meant something else ?
Click to expand...
Click to collapse
my reply was not for you but for the off topic before my reply: contact, ph app and message force close after root.
as I said, there is already a solution about force close.
Anyway I can only write in /system/etc and some over folders
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
Hi, I saw that you managed to get a custom erofs partition mounted using magisk. I was wondering if the same could be done for the/product folder because that would allow me to fix the DPI scaling issues found on EMUI 9.0-9.1. Would it be possible to see the code for your magisk module?
Ok, So.
After having a look at what I did with this WorkInProgress...
So far there is 2 main way I thought about and played with:
Method A
A1/
Using the mkfs.erofs tool to make your custom erofs partition and mount it over the original one. (mayne umount it before)
Thanks @ph03n!x for his work on mkfs.erofs.
Thanks @ante0 for his android arm build.
A2/
I did not yet tryed to flash via fastboot or adb these modded erofs images.
Method B
What I'm actually doing is just mounting systemless-y with a magisk module whole folders over erofs one ;
In post-fs-data.sh, I'm doing:
mount -o bind $MODDIR/cust /cust
mount -o bind $MODDIR/version /version
With a ~150MB custom /cust it is working ; It should be tryed/perfected for bigger folders.
Another way, to not replace/spoof the whole folders could be to mount the whole list of custom files at their respective path (-to be tested)
PS: I'm not sure if update-binary module's file should be modded with some:
mount /cust 2>/dev/null
@ line 42
Sources:
https://forum.xda-developers.com/huawei-p30-pro/how-to/erofs-mounting-accessing-img-t3944193
oslo83 said:
Ok, So.
After having a look at what I did with this WorkInProgress...
So far there is 2 main way I thought about and played with:
Method A
A1/
Using the mkfs.erofs tool to make your custom erofs partition and mount it over the original one. (mayne umount it before)
Thanks @ph03n!x for his work on mkfs.erofs.
Thanks @ante0 for his android arm build.
A2/
I did not yet tryed to flash via fastboot or adb these modded erofs images.
Method B
What I'm actually doing is just mounting systemless-y with a magisk module whole folders over erofs one ;
In post-fs-data.sh, I'm doing:
mount -o bind $MODDIR/cust /cust
mount -o bind $MODDIR/version /version
With a ~150MB custom /cust it is working ; It should be tryed/perfected for bigger folders.
Another way, to not replace/spoof the whole folders could be to mount the whole list of custom files at their respective path (-to be tested)
PS: I'm not sure if update-binary module's file should be modded with some:
mount /cust 2>/dev/null
@ line 42
Sources:
https://forum.xda-developers.com/huawei-p30-pro/how-to/erofs-mounting-accessing-img-t3944193
Click to expand...
Click to collapse
I'm rather new to this trying to do something similar on my EMUI9.1 using Magisk, I'm having a problem that i can replace anything in most other folders without much problem like /etc/ for example, but when i try to substitute /vendor/, whatever i put it the folder does not only fail to get substituted, it even disappears from the $MODDIR/system/vendor folder upon restart!
I.e. let's say I create a new file in $MODDIR/system/etc. Upon restart i'm successfully seeing that same file appear /etc.
However when I create a new file under $MODDIR/system/vendor, Upon restart i'm not seeing that under /vendor. ALSO the file is gone from $MODDIR/system/vendor like it was never there.
Any idea what is happening? I've also tried manually mounting in the post-fs-data.sh, where i put the following:
mount -o bind $MODDIR/system/vendor /vendor
That actually caused my system to freeze on the loading screen. I had to reset magisk to non-modded settings in order to get it to run again.
Any help's appreciated.
pvillasuso said:
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
Click to expand...
Click to collapse
i got the solution of above problem from this https://forum.xda-developers.com/huawei-p30-pro/how-to/guide-magisk-root-p30-pro-bl-code-t3938285
Hi I have almost the same issue after updating to EMUI 9.1 the phone hardbricked. It only shows as fastboot on my PC I tried flashing but not sending the img files please help
How to flash phh's system arm64-A/B GSI on the Redmi 9's (lancelot) dynamic system partition
All the development credits for this GSI go to @phhusson. For more information head over to his thread.
Bugs:
• Auto brightness (works with an overlay)
• Brightness slider
• Headphone jack
• Offline charging?
• VoLTE?
For bug fixes refer to Post #2 or search for reported bugs on Phh's treble experimentations issues tracker on GitHub.
What is working:
Everything else
WARNING:
Only proceed if you know what you are doing! Be aware of the risks associated to unlocking your bootloader. Ensure to have the MIUI Fastboot ROM downloaded to restore your device in case it soft bricks. All your data will be deleted during the process so a backup is essential. Charge your device to at least 50% before proceeding.
Requirements:
1) Unlocked bootloader here
2) Latest Android platform tools here
3) MIUI stock recovery (maintain it to be able to boot into userspace fastboot)
4) Xiaomi fastbootd drivers here
5) Phh-Treble GSI (Use a system-arm64-ab-gapps) here
6) vbmeta.img here
Steps:
Run the commands below within the platform-tools folder after enabling debugging in Developer settings on your phone.
1) adb devices (to authorize debugging)
2) adb reboot bootloader (to boot into fastboot mode)
3) fastboot reboot fastboot (to boot into userspace fastboot)
4) fastboot flash system system.img
5) fastboot -w
6) fastboot flash vbmeta vbmeta.img (use attached null vbmeta to disable avb)
7) fastboot reboot
Notes:
• First time boot takes 1 minute. phh's GSI has root by default however the logical system partition is read only. Any system mods should be done as Magisk modules systemlessly. A patched boot.img may cause bootlooping on Android 11 GSIs however Magisk now works fine even on R GSIs on MTK devices, thanks to @topjohnwu!
• System can be RW such as to push overlays. Thanks to the great phhusson!
• A better way to disable Android Verified Boot is by running below command using a stock vbmeta image file:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Fixes:
I'll post fixes to bugs as suggested by users in this thread here.
• Brightness slider and headphone jack [Credit to @M47Z and @Shas45558] — Run code below in root ADB shell or any Terminal app on your phone:
Code:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
setprop persist.sys.overlay.devinputjack true
reboot
• Note that CAOS by @eremitein has the above fixes integrated and is based on phhusson's AOSP.
How is the performance .any lag ?
Once you boot there are no lags. FYI my device is only 3 GB RAM. I just observed that booting is a little faster with the lighter Phh-Treble system installed as compared to Havoc. Maybe that's something for you to consider.
nielsync said:
Once you boot there are no lags. FYI my device is only 3 GB RAM. I just observed that booting is a little faster with the lighter Phh-Treble system installed as compared to Havoc. Maybe that's something for you to consider.
Click to expand...
Click to collapse
Is your headphones work??is brightness work?
Headphones not working but good enough BT audio works with speakers. Haven't tested in call audio on BT earphones though. Also not sure about USB-C audio output. Someone who has tested can share with us. Brightness is also broken.
I need testers
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
Edit: Not working. Refer to post #18 for info.
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
how did you pushed it into /vendor/overlay/ ?
I get the permission denied error everytime with adb and with any root file explorer on the phone too.
kW_ said:
how did you pushed it into /vendor/overlay/ ?
I get the permission denied error everytime with adb and with any root file explorer on the phone too.
Click to expand...
Click to collapse
I didn't test it I just build it . You should have root just copy it into your phone's /system/overlay/, and set permission to rw-r--r-- / 0644. If you can't then maybe we can't edit system partition . You can use root explorer.
Well. I can't change permissions and copy it. I have seen that other roms doesn't have read only on the system partition so i will try it later. Lineageos is one of these roms maybe.
Gsi will not boot with magisk_patch boot.img.....
So no root access......
How you push file into system or vendor??
Shas45558 said:
Gsi will not boot with magisk_patch boot.img.....
So no root access......
How you push file into system or vendor??
Click to expand...
Click to collapse
Phh-Treble has root so you are good to go. On the other hand without flashing a custom recovery I got root on Havoc-OS through flashing the patched boot image and even installed a module in Magisk manager without any issues. Its just that the way the system partition is mounted on these new phones released with Q makes it almost impossible to modify it. Let a genius surprise us.
nielsync said:
Phh-Treble has root so you are good to go. On the other hand without flashing a custom recovery I got root on Havoc-OS through flashing the patched boot image and even installed a module in Magisk manager without any issues. Its just that the way the system partition is mounted on these new phones released with Q makes it almost impossible to modify it. Let a genius surprise us.
Click to expand...
Click to collapse
In my case when I flash patch boot my gsi wili not boot....
What gsi are you use?? Give the link plz
@nielsync
So im a genius nd going to surprise you if anyone wants to modify system partition then custom recovery is must required e.g in Twrp mount /system , /vendor then go to file manager in twrp i forgot the name of tab in which you ll find the filemanager you can find it yourself lmao ,then select the file by finding in ur storage nd then copy and paste it in desired location and then after pasting go to path where you pasted it,Select it and give it 0644 permissions and restart ..Boom.( I think root is necessary because without root the changes revert )
Abdul [email protected] said:
@nielsync
So im a genius nd going to surprise you if anyone wants to modify system partition then custom recovery is must required e.g in Twrp mount /system , /vendor then go to file manager in twrp i forgot the name of tab in which you ll find the filemanager you can find it yourself lmao ,then select the file by finding in ur storage nd then copy and paste it in desired location and then after pasting go to path where you pasted it,Select it and give it 0644 permissions and restart ..Boom.( I think root is necessary because without root the changes revert )
Click to expand...
Click to collapse
File manager is in Advanced tab of TWRP. In theory and in devices released with the now old partition structure it was that simple. You have a right to claim anything Mr. Genius You seem to be ahead of even @Dees_Troy and his team over at TWRP despite this wonderful explanation!
Shas45558 said:
In my case when I flash patch boot my gsi wili not boot....
What gsi are you use?? Give the link plz
Click to expand...
Click to collapse
I've used both Phh-Treble and Havoc-OS and can confirm that Magisk works on both without any issues. My boot image was already patched on MIUI so I only installed the manager application each time after flashing the GSI. See screenshots of Magisk Manager on Phh-Treble below.
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
no it does not work
i mount the gsi system file on linux via loop disk...
then i place your apk /system/overly/
but the brightness is not work...
you can mount raw img file on linux ......
first creat folder on root via this cmd..
sudo mkdir /mnt/system
mount system.img via this cmd
sudo mount system.img /mnt/system
now you can edit system.img via root permission via this cmd...
sudo nautilus
now a file manager pop up with root
go to /mnt/system
copy your file where you want...and unmount via this cmd...
sudo umount /mnt/system
Thanks @Shas45558 for confirming that, it's still difficult to mod the installed system on the phone itself. I tried and got a 'permission denied' error via terminal in a custom recovery.
nielsync said:
Thanks @Shas45558 for confirming that, it's still difficult to mod the installed system on the phone itself. I tried and got a 'permission denied' error via terminal in a custom recovery.
Click to expand...
Click to collapse
That's why I use pc with Linux and do the above things to puss the file inside system.img....