Related
Any TWRP for Umidigi One Pro that is able to read the /data partition ?
Edit:Solved
Ghost505 said:
Any TWRP for Umidigi One Pro that is able to read the /data partition ?
Edit:Solved
Click to expand...
Click to collapse
What was the solution? I didn't even know we had a twrp!
http://community.umidigi.com/forum.php?mod=viewthread&tid=2962&extra=page=1
https://forum.xda-developers.com/android/development/twrp-umidigi-z2-z2-special-edition-t3842866
Best twrp found here : http://community.umidigi.com/forum.php?mod=viewthread&tid=17560&extra=page=1
Hey, What is your device Android version?
Android 8.1
For those with Umidigi One / One Pro or Z2
0. Install twrp from first link
---
(second link)
1. now we need to edit the fstab file
because its a MTK device your fstab file looks like fstab.mt6763 or simliar
2. Download Mixplorer from XDA Thread. ( this root explorer is the best because it set permission automaticly.)
3. open mixplorer and browse to root/system/vendor/etc/fstab.mt6763..
4 open that file and search for ( should be line 15)
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
Click to expand...
Click to collapse
5. edit the file to this
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,
Click to expand...
Click to collapse
6.save and turn off the phone
---
7. Wipe Data from device and enter in the phone again and no more encryption so twrp will be able to access the data partition.
Ghost505 said:
http://community.umidigi.com/forum.php?mod=viewthread&tid=2962&extra=page=1
https://forum.xda-developers.com/android/development/twrp-umidigi-z2-z2-special-edition-t3842866
Click to expand...
Click to collapse
Thanks for the info, I'll give it a shot soon.
There's no item when I go to root in Mixplorer
Ghost505 said:
Android 8.1
For those with Umidigi One / One Pro or Z2
0. Install twrp from first link
---
(second link)
1. now we need to edit the fstab file
because its a MTK device your fstab file looks like fstab.mt6763 or simliar
2. Download Mixplorer from XDA Thread. ( this root explorer is the best because it set permission automaticly.)
3. open mixplorer and browse to root/system/vendor/etc/fstab.mt6763..
4 open that file and search for ( should be line 15)
5. edit the file to this
6.save and turn off the phone
---
7. Wipe Data from device and enter in the phone again and no more encryption so twrp will be able to access the data partition.
Click to expand...
Click to collapse
Blackchancellor said:
There's no item when I go to root in Mixplorer
Click to expand...
Click to collapse
This means that Mixplorer does not have root permissions to access root folder. Install magisk and try again, if it still does not work and you have root installed, clear data&cache for mixplorer app.
But I can't root the phone. I've tried all, but when I enter twrp it mounting data partition always fails. And TWRP also always only starts the first time after it's been flashed. Next time I start in recovery mode, I just see "No command".
Ghost505 said:
This means that Mixplorer does not have root permissions to access root folder. Install magisk and try again, if it still does not work and you have root installed, clear data&cache for mixplorer app.
Click to expand...
Click to collapse
Blackchancellor said:
But I can't root the phone. I've tried all, but when I enter twrp it mounting data partition always fails. And TWRP also always only starts the first time after it's been flashed. Next time I start in recovery mode, I just see "No command".
Click to expand...
Click to collapse
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
It didn't work. When I press "install" and select the rom in the file manager, it says "flashing" and then it disapears. Nothing changes
Ghost505 said:
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
Click to expand...
Click to collapse
Blackchancellor said:
It didn't work. When I press "install" and select the rom in the file manager, it says "flashing" and then it disapears. Nothing changes
Click to expand...
Click to collapse
Try SP_Flash_Tool to root with magisk first
But my main question has always been: hiw to root? I can't mount data partition after flasing twrp so I can't access my files in recovery mode and I can't install magisk
Ghost505 said:
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
Click to expand...
Click to collapse
Ghost505 said:
Try SP_Flash_Tool to root with magisk first
Click to expand...
Click to collapse
Blackchancellor said:
But my main question has always been: hiw to root? I can't mount data partition after flasing twrp so I can't access my files in recovery mode and I can't install magisk
Click to expand...
Click to collapse
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
OK. Could you please help me by explaining step to step how to root using SPFT? Thanks in andvance
Ghost505 said:
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
Click to expand...
Click to collapse
Blackchancellor said:
OK. Could you please help me by explaining step to step how to root using SPFT? Thanks in andvance
Click to expand...
Click to collapse
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
in here is the boot.img look in it with winrar
Thanks, but where to get this boot.img? Is it from the extracted rom (.rar) files.
Ghost505 said:
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
Click to expand...
Click to collapse
Ghost505 said:
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
Click to expand...
Click to collapse
It worked. Thanks!
Ghost505 said:
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
in here is the boot.img look in it with winrar
Click to expand...
Click to collapse
Phone is now rooted and TWRP installed, but I still can't mount data partition.
Go in ROOT /vendor/etc/fstab.mt6763 with MIXPLORER
Should be on line 15 I think
edit:
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
to:
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,
save and restart phone and wipe data in twrp, everything will be erased, enter in phone after that and follow instructions like the first time you started the phone
Disclaimer: Untested on the following devices:
-A2017U on Oreo B20
-A2017 (chinese version) Oreo B18
-A2017G B03
If you want to test, do so at your own risk!
If it does or does not work, please report back on this thread so i can edit the OP
Yes you read right, finally we can get rid of that nonsense system write protection and get system write permissions on Oreo back!
For those that are eager to know how to do it before i go on mumbling a story about the technical details yada yada yada:
Download this TWRP flashable zip by @raystef66 and flash it: https://androidfilehost.com/?fid=11410963190603874735
Now you have disabled ZTE's protection and got system write permissions (if you are rooted of course, if not then there is still androids native protection; more info on that matter below)
Huge thanks to @raystef66 for creating the zip.
Now to the technical stuff:
As you probably know, since Oreo we can't use "reboot disemmcwp" anymore. Thats because ZTE removed this option.
Why did they do this?
I don't have any idea
Does it make sense?
No, not at all. It doesn't even make sense for ZTE having this write protection implemented in the first place. Why not you ask? Because android itself already has its own native system write protection. If you are not rooted, system is write protected, it's as simple as that. After all, the whole point of rooting your device is to get system access so you can make all kinds of modifciations to your device that wouldn't otherwise be possible without root. Be it simple file edits (build.prop), xposed/magisk modules or any app that requires root and so on.
So what does the zip above do to disable system write protection and give write permissions to system?
To put it simply. The file inside it (emmc_appsboot.mbn) contains various lines regarding system write protection, fastboot etc. Some of those lines are for disabling system write protection. If you flash the zip, it gets disabled.
The original emmc_appsboot.mbn file that comes with the Oreo OTA, doesn't contain these lines. Instead it makes sure that system write protection is intact. Therefore, even if you are rooted, you won't be able to do any modifciations to system (they revert back after reboot).
Can you re-enable ZTE's system write protection?
Nope. Why would you even wanna do that?! Again, android has it's own system write protection (see "Does it make sense?" above). If you want that back, simply unroot.
Wait, you mentioned there are also lines for fastboot in that emmc_appsboot.mbn file, what about that?
Well yes, as mentioned earlier there are some lines regarding fastboot. But i'm unsure of one thing as of now. Was fastboot unavailable in Oreo B02 to any of you guys? If yes, then you should get also fastboot back after having flashed the zip. I could enter fastboot mode when selecting it in the unlocked bootloader warning screen. I forgot test it before disabling system write protection so i am not sure if it already was accessible or got enabled after flashing the zip.
@GodOfPsychos Thanks for your perseverance :good:
Thanks, I will test it on B02. I had install an old Bootstack for write permissions on B02.
On B03 can't flash a working TWRP
I can not install the b03 by edl adding it to the TWRP file for oreo. When trying to restart in twrp the phone turns off. I can not find the solution Therefore I can not flash anything else either.
I'm going to try the Chinese rom Oreo B19.
Thanks for everything! I hope that in the B19 we have good results
In the B19 for the a2017 after starting in EDL the system and rebooting in TWRP installing magisk 16.7 and after the zip I have found that the system only starts in fastboot.
I will continue testing
@GodOfPsychos @raystef66 On the assumption it does not work on B03/B18/B19/B20, can it be implemented on their original emmc_appsboot.mbn?
have tested on Oreo B03 and works. on B03 can only use TWRP 3.2.1-7NFound, but have no access to internal memory.
on B02 and B03 in system/priv-app i can´t delete top folder, inside folder have fully access. in system/app no problems.
blackpac said:
@GodOfPsychos @raystef66 On the assumption it does not work on B03/B18/B19/B20, can it be implemented on their original emmc_appsboot.mbn?
Click to expand...
Click to collapse
That depends. The file itself is not 100% readable via simple notepads (i looked into it with notepadd++ for example). It has a bunch of strange characters besides the bit of clear text. I don't know how or which lines need to put where and how etc. I know i said there are lines regarding disabling write protection in there etc. But the main issue is that not all of the file is fully readable. So there could be even more "unreadable" stuff (weird characters) that need to be taken into consideration besides the readable ones.
See attachment to see what it looks like when you open one of them with notepad++
But yes in theory it is possible if ZTE doesn't change the implementation of their protection.
I hope that anyone who is more of an expert for this sort of stuff can help with this.
Rennert said:
have tested on Oreo B03 and works. on B03 can only use TWRP 3.2.1-7NFound, but have no access to internal memory.
on B02 and B03 in system/priv-app i can´t delete top folder, inside folder have fully access. in system/app no problems.
Click to expand...
Click to collapse
which top folder do you mean? inside system/priv-app i can delete folders without a problem (using root explorer for example).
GodOfPsychos said:
which top folder do you mean? inside system/priv-app i can delete folders without a problem (using root explorer for example).
Click to expand...
Click to collapse
Yes top folder inside System/priv-app, example calendar_stock, can't delete it, but apk and subfolder inside this folder can delete without problems. It's only on priv-app folder, all other folders no problem.
Hmm. Are you trying to delete them via twrp file manager or an app like i mentioned previously?
Noob question whay you guys are booting to reboot disemmcwp,could anyone explain this method usage
GodOfPsychos said:
Hmm. Are you trying to delete them via twrp file manager or an app like i mentioned previously?
Click to expand...
Click to collapse
I use Root Explorer, can create new folder and delete this in priv-app. in TWRP file manager I can't delete folders, only files.
blackpac said:
@GodOfPsychos @raystef66 On the assumption it does not work on B03/B18/B19/B20, can it be implemented on their original emmc_appsboot.mbn?
Click to expand...
Click to collapse
First off, anyone on Oreo U and Oreo CN have to flash the zip and see if he/her can change f.e. build.prop (add a character), save and reboot and see if change has applied. Also test if system folder can be deleted, reboot and see if things boot. If not working i'll take a look into the changes ZTE made and see if I can change some lines into the aboot file. So let me know
Rennert said:
have tested on Oreo B03 and works. on B03 can only use TWRP 3.2.1-7NFound, but have no access to internal memory.
on B02 and B03 in system/priv-app i can´t delete top folder, inside folder have fully access. in system/app no problems.
Click to expand...
Click to collapse
3217 will do. Have you tested the 3218 too?
Rennert said:
Yes top folder inside System/priv-app, example calendar_stock, can't delete it, but apk and subfolder inside this folder can delete without problems. It's only on priv-app folder, all other folders no problem.
Click to expand...
Click to collapse
Normaly you should be able to delete a system folder. It's been tested. Use a Root explorer like Solid and it should work. On B02 it was.
raystef66 said:
Normaly you should be able to delete a system folder. It's been tested. Use a Root explorer like Solid and it should work. On B02 it was.
Click to expand...
Click to collapse
I can delete all folders in system, but can't delete the top folders in priv-app. Tested on B02 and B03. Have removed in TWRP terminal with rmdir and works
Rennert said:
I can delete all folders in system, but can't delete the top folders in priv-app. Tested on B02 and B03. Have removed in TWRP terminal with rmdir and works
Click to expand...
Click to collapse
I haven't any problems with deleting folder under /system/priv-app using MiXplorer on B03.
I tested A2017G.B03 and A2017.B19. Both of them were flashed using EDL full packages by djkuz.
Tested with b20 modified kernel (by Asderdd), Disable_Dm-Verity_ForceEncrypt_12.08.2018 (by zackptg5) and Magisk 18.0.
Haven't any issues. /system is writable and Magisk is working.
Thank you raystef66.
Does that mean we may expect SL!M 7?
Magisk 18 doesn't work on A2017GB02 and B03.
Yes system is writable except system/priv-app/ top folder, it's funny that I can create new folder and delete this and
existing top folders are fails.
Rennert said:
Magisk 18 doesn't work on A2017GB02 and B03.
Yes system is writable except system/priv-app/ top folder, it's funny that I can create new folder and delete this and
existing top folders are fails.
Click to expand...
Click to collapse
Just tried and deleted every folder in /system/priv-app/. Couldn't take a screenshot after that. :cyclops:
What kind of root do you have?
klałn said:
I haven't any problems with deleting folder under /system/priv-app using MiXplorer on B03.
I tested A2017G.B03 and A2017.B19. Both of them were flashed using EDL full packages by djkuz.
Tested with b20 modified kernel (by Asderdd), Disable_Dm-Verity_ForceEncrypt_12.08.2018 (by zackptg5) and Magisk 18.0.
Haven't any issues. /system is writable and Magisk is working.
Thank you raystef66.
Does that mean we may expect SL!M 7?
Click to expand...
Click to collapse
The one that had close contact with ZTE was @GodOfPsychos . All credits go to him
Thnx for reporting also thnx @Rennert
That would be the idea of making a Sl!M one even for U and CN, yes. Hope to find some time free :highfive:
klałn said:
Just tried and deleted every folder in /system/priv-app/. Couldn't take a screenshot after that. :cyclops:
What kind of root do you have?
Click to expand...
Click to collapse
have Magisk 16.7. if i flash Magisk18 it only boot in Bootloader. Flash 16.7 now system boots.
issue on priv-app folder solved. i had install Viper4AndroidFX in Magisk, deinstall and can delete top folder. new install and delete are fail.
Rennert said:
have Magisk 16.7. if i flash Magisk18 it only boot in Bootloader. Flash 16.7 now system boots.
issue on priv-app folder solved. i had install Viper4AndroidFX in Magisk, deinstall and can delete top folder. new install and delete are fail.
Click to expand...
Click to collapse
I've tried several things in Chinese b19: flashing rom by edl and booting with recovery twrp 3.2.1.7. then flashing dm_verity and your zio. In no case I succeed. maximum achievement that I boot in fastboot I do not achieve that. I started flashing magisk. Always in bootloop
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
Hello to all...
After the last system update from pie to android 10(stock rom) I can't change system media folder to be writable, so I can change the lock/unlock sounds. I have tried to do that first with Es explorer, than with Root explorer and Fx explorer, but nothing helps. Also I have tried to find "Documents"(to enable) in App list in main settings but there is no "Documents" in list.
The phone is rooted and every file explorer that have I tried getting granted root permissions. In earier versions of miui I didn't had this kind of problem.
Is there anyone who knows how to solve this ?
try x-plore
Roydamenz said:
try x-plore
Click to expand...
Click to collapse
Thanks for the reply but i don't think that problem is with any file explorer. Btw, I have tried X-plore, also.
Had the same problem and I've solved it by changing twrp to this unofficial twrp 3.3.1 beta08! After flashing this recovery boot to twrp and under mount, check system and vendor then reboot. Let me know if it worked.
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-3-1-beta01-touch-t3987567/amp/
is possible, but I can't remember exactly that I've also flashed this:
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
wizard8400 said:
is possible, but I can't remember exactly that I've also flashed this:
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Click to expand...
Click to collapse
Ok, before i do that... could it be solve from Magisk manager>Advanced settings>uncheck Preserve AVB 2.0/dm-verity ? I am on Magisk 20.2.
I remember that after flashing dfe zip those checks were cleared in magisk, I don't know if the zip does more. First try flashing that twrp, I think that will be enough.
wizard8400 said:
I remember that after flashing dfe zip those checks were cleared in magisk, I don't know if the zip does more. First try flashing that twrp, I think that will be enough.
Click to expand...
Click to collapse
Nothing was successful. First I flashed that TWRP from link. Than, after I tried, I also flash that zip through TWRP, but still can't paste files in system media folder.
For the information after flashed that zip, in Magisk advanced settings first two options was unchecked.
For now, I found that this is related to Android 10 changes.
did you go to twrp>mounts and check system and vendor, after flashing that version of twrp? was twrp beta08 the one you flashed? It worked for me, had the exact same problem after flashing 11.0.4
wizard8400 said:
did you go to twrp>mounts and check system and vendor, after flashing that version of twrp? was twrp beta08 the one you flashed? It worked for me, had the exact same problem after flashing 11.0.4
Click to expand...
Click to collapse
Sorry, Wizard8400 for my too quick response. It actually helped. But, for now only with Root Exporer, which is enough for me. And Root exporer does that change to r/w only once. With next operation it will be ask once again to change from r/o to r/w.
I didn't change anything in TWRP Mount section. Personally, I had thinking but didn't dare.
Thanks for everything !
As a recommendation, you cand try this file explorer, it has root features, and it never let me down:
https://forum.xda-developers.com/showthread.php?t=1523691
wizard8400 said:
As a recommendation, you cand try this file explorer, it has root features, and it never let me down:
https://forum.xda-developers.com/showthread.php?t=1523691
Click to expand...
Click to collapse
Yes, I had that file explorer. Very good. And with some really useful option like some sort of shift/click similar options for multiple files checking.
I really like Es file explorer and until now I was satisfied.