I'm trying to use Link2SD, so I created the 2nd partition with ext3 format, while the first is FAT32 both are primary.
It did gives me the error "script cannot be created. Invalid argument". I did some research and for what i could understand, I need to enable Init.d, so link2sd scripts can be executed.
So i got Universal Init.d, it says my kernel doesn't support it. Tryed some scripts, but no deal.
The "init.d" folder is there with the script, but it's ignored.
Even if I try to execute the command manually (mount -o rw -t ext3 /dev/block/mmcblk1p2 /data/sdext2) i get the same error using "su" privileges (invalid argument)....
My phone is Xperia Z2 rooted on Lollipop 5.1.1 with SuperSU and XZRecovery (TWRP & CWM).
Thanks for any help
@dthknt ,
XZDR does support init.d but you need to enable it yourself. edit XZDR.prop on your sd card and enable / add:
dr.initd.active=true
dr.keep.byeselinux=true
this last one disables SElinux permanently on your device, if you don't want that install SElinux mode changer app and disable when you want.
SElinux probably needs to be disabled for everything to work correctly.
ptmaniac said:
@dthknt ,
XZDR does support init.d but you need to enable it yourself. edit XZDR.prop on your sd card and enable / add:
dr.initd.active=true
dr.keep.byeselinux=true
this last one disables SElinux permanently on your device, if you don't want that install SElinux mode changer app and disable when you want.
SElinux probably needs to be disabled for everything to work correctly.
Click to expand...
Click to collapse
Thanks @ptmaniac, init.d is working !!!!
But the error remains....invalid argument, even on link2sd log files !
Any ideas ?
Thanks
@dthknt , no problem glad init.d is working, i can't really help you with links2sd as i never used it... try setting selinux to permissive if you didn't do that already.
I personally use obb on sd xposed module to move my obb files to external sd card. Just moving obb's to the sd card is enough for me, i have about 20gb of apps installed right now
It looks like that didn't work, init.d is not enabled.
The XZDR.prop file got corrupted, editing through root explorer or notepad++ from PC.
Any help, @ptmaniac ?
Related
Hi there
I m using Moto E(Condor) with CM 13.0-20160325 NIGHTLY BUILD..
I have installed link2sd but it is not working.. I have partitioned my sd card using mini partition tool.
Whenever i open link2sd app it shows MOUNT SCRIPT ERROR
Mount script cannot be created
mount: '/dev/block/vold/179:66'->'/data/sdext2': no such file or directory
On the other hand if i use apps2sd it works fine for linking apps but after rebooting all the apps stored on sd card are disappeared
What should i do now? Any help or fix?
Thanx in advance
You need to set the kernel on permissive mode
Run this comand on terminal
setenforce 0
While creating Mount script on app2sd choose for init.d support and after that open the script created by app2sd and add
su0
setenforce 0
After this you don't have to make it permissive every time you reboot
Sent from my Moto E using Tapatalk
Abhimanyu Shekhawat 121 said:
While creating Mount script on app2sd choose for init.d support and after that open the script created by app2sd and add
su0
setenforce 0
After this you don't have to make it permissive every time you reboot
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
I dont knw anything about scripting or init.d :crying: what should i do??
In app2sd click on recreate mount script and when selecting type of partition choose I have init.d support after this got to system/etc/init.d folder and open app2sd script with any editor and add the lines I have mentioned and then reboot
Sent from my Moto E using Tapatalk
Abhimanyu Shekhawat 121 said:
While creating Mount script on app2sd choose for init.d support and after that open the script created by app2sd and add
su0
setenforce 0
After this you don't have to make it permissive every time you reboot
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Applied this method and it is working fine. Only problem is that external files like obb are not binding properly.
U using.folder Mount option of app2sd??
Sent from my Moto E using Tapatalk
rohanbhagat said:
Hi there
I m using Moto E(Condor) with CM 13.0-20160325 NIGHTLY BUILD..
I have installed link2sd but it is not working.. I have partitioned my sd card using mini partition tool.
Whenever i open link2sd app it shows MOUNT SCRIPT ERROR
Mount script cannot be created
mount: '/dev/block/vold/179:66'->'/data/sdext2': no such file or directory
On the other hand if i use apps2sd it works fine for linking apps but after rebooting all the apps stored on sd card are disappeared
What should i do now? Any help or fix?
Thanx in advance
Click to expand...
Click to collapse
THANK YOU BRO IT HELPED FOR ME
You are saying app2sd can't link apps after reboot.
then after creating mount script from apps2sd use lin2sd for linking apps
Well Apps2sd works fine as far as mount script is concerned.... It does successfully creates mount script for 2nd partition while link2sd(pro) doesnt.... All was working well on cm12... But still there are some issues which are not resolved even by apps2sd... All linked apps dissappears after rebooting.... Thus you have create mount scripts again or soft reboot to get back your linked apps!!! Thats a haptic job 4 me.... Anybody who can help to resolve this issue??
Sent from my GT-I9082 using XDA-Developers mobile app
ankii91 said:
Well Apps2sd works fine as far as mount script is concerned.... It does successfully creates mount script for 2nd partition while link2sd(pro) doesnt.... All was working well on cm12... But still there are some issues which are not resolved even by apps2sd... All linked apps dissappears after rebooting.... Thus you have create mount scripts again or soft reboot to get back your linked apps!!! Thats a haptic job 4 me.... Anybody who can help to resolve this issue??
Click to expand...
Click to collapse
In marshmallow, if SElinux is permissive ,no problem in rebooting but if your SElinux is enforcing , a soft reboot is needed after every reboot in order to relink all apps..
There is an opt available of autosoft-reboot in app2sd , which triggers soft reboot after every reboot ,if the apps are missing...
Hope it helps!????
need help!!
I followed ur steps and i have done till choosing init.d . Now here is my problem starts. You said to open scrscript and give those commands , but where do i find script?? Where is the system /etc... folder. Plz help ,i am stuck here
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
Hello everyone!
since some time ago I was customizing the ROM of Android 5.0. Everything was in order while I didn't try to change the system files. Obviously after flashing device refuse the normal boot and stacked on boot screen.. The reason was selinux context which I've never applied.
The process is:
1. Mount the ROM as EXT4
2. Add/Change files
3. Change the permissions
4. Unmount and flash...The question is:
How to label and chcon the newly added files with Android's default context in a mounted EXT4 image?
PS: Not sure is the right forum. Please suggest a solution.
Thanks!
dFrem said:
Hello everyone!
since some time ago I was customizing the ROM of Android 5.0. Everything was in order while I didn't try to change the system files. Obviously after flashing device refuse the normal boot and stacked on boot screen.. The reason was selinux context which I've never applied.
The process is:
1. Mount the ROM as EXT4
2. Add/Change files
3. Change the permissions
4. Unmount and flash...
The question is:
How to label and chcon the newly added files with Android's default context in a mounted EXT4 image?
PS: Not sure is the right forum. Please suggest a solution.
Thanks!
Click to expand...
Click to collapse
What do u mean u mounted the ROM ext4? The file system should have been defined upon install. If u changed the file system of your system partition I would assume you wiped you accidently wiped the installed os . Selinux status could affect boot but only if you did something that requires permissive status (a custom kernel is a good ready example of the type of flAsh that would need selinux on permissive). Ok so let's assume u didn't mean ROM . You meAnt system partition and you naturraly mounted that (system) as R/W . What permissions did you set on file . 644 is the correct answer if you were trying to install as system file. Wht was it you flashed? It's probably an easy fix bud . Just need more info
mojoswagger1980 said:
What do u mean u mounted the ROM ext4? The file system should have been defined upon install. If u changed the file system of your system partition I would assume you wiped you accidently wiped the installed os . Selinux status could affect boot but only if you did something that requires permissive status (a custom kernel is a good ready example of the type of flAsh that would need selinux on permissive). Ok so let's assume u didn't mean ROM . You meAnt system partition and you naturraly mounted that (system) as R/W . What permissions did you set on file . 644 is the correct answer if you were trying to install as system file. Wht was it you flashed? It's probably an easy fix bud . Just need more info
Click to expand...
Click to collapse
@mojoswagger1980 Thanks for answering. My bad, of course meaning is to mount "system.img" and not the ROM. Will explain.
The image is mounted, adding busybox into system/xbin, chmod 644, (automatically set owner root:root). As expected ls -Z is showing "?" for system/xbin/busybox...
Not changing anything more, flashing this image. File is not accessible or doesn't exists.
No doubts that if I am doing "chcon ubject_r:system_file:s0 system/xbin/busybox" it says first relabel the file... Relabel says there is no such type, user, etc...
What can I do in this case?
PS: Setting permissive 1 with inject-sepolicy doesn't help. May be I am doing something wrong here. Please suggestions.
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
I wanted to delete some files from the system like some useless system apps/themes etc. I was trying to root my phone with magisk. The magisk would install but I couldn't make any kind of changes because I found it was read-only! Now if I want it to mount read-write, it just won't. Any solutions, anyone?
Resmi Note 9S Curtana, OFox R11 installed with xiaomi.eu 12.0.1.0, android 11
Try this script from this thread.
You can't mount system because of dynamic partitions (super partition). The script linked above doesn't mount system rw, it just makes a new super partition.
The real way to make edits to dynamic partitions is with adb remount which replaces the old 'mount -o rw, remount /system' method.
The practical way to make edits is systemlessly with a magisk module.
Adb remount info
Dynamic partitions info
jwchips said:
You can't mount system because of dynamic partitions (super partition). The script linked above doesn't mount system rw, it just makes a new super partition.
The real way to make edits to dynamic partitions is with adb remount which replaces the old 'mount -o rw, remount /system' method.
The practical way to make edits is systemlessly with a magisk module.
Adb remount info
Dynamic partitions info
Click to expand...
Click to collapse
I feel superdumb but @jwchips , where am I supposed to put those commands- in custom recovery terminals, in Windows command prompt or in a terminal emulator app?
Plz someone teach me step by step. I can't rw system by root explorer in miui rom, but I can do it in aosp rom. I don't know what causing this result. Since android 2 to android 11. Every upgrade time I struggle a lot. Now I spend 2 mouth to search internet but for code noob like me, get nothing. I'm still study it hope a newvice tutorial post.
same problem here, ive tried different zips and also doing it manually, no success
Azamsm said:
I wanted to delete some files from the system like some useless system apps/themes etc. I was trying to root my phone with magisk. The magisk would install but I couldn't make any kind of changes because I found it was read-only! Now if I want it to mount read-write, it just won't. Any solutions, anyone?
Resmi Note 9S Curtana, OFox R11 installed with xiaomi.eu 12.0.1.0, android 11
Click to expand...
Click to collapse
Why not try debloater magisk?
GitHub - sunilpaulmathew/De-Bloater: An application using the power of Magisk to debloat unwanted system apps!
An application using the power of Magisk to debloat unwanted system apps! - GitHub - sunilpaulmathew/De-Bloater: An application using the power of Magisk to debloat unwanted system apps!
github.com