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
Related
Hi there,
is there a solution to make it possible that a microSD-card formatted in ext4 is able to be mounted in CM9?
This one I found for the Galaxy tab here.
I don't use any window systems and I'm not happy to have to format the extSD-card in FAT32 or exFAT.
Regards
Koeti
No one, who has a solution?
Gesendet von meinem GT-I9300 mit Tapatalk 2
There is such a feature, but you have to proceed with EXTREME caution.
You must also have taken a backup of you sd cards' contents.
Firstly, go and flash the Franco Kernel
On his secong post, you can see the instructions required:
franciscofranco said:
Wi-Fi Power Management toggle:
How to activate the special sdwatcher binary:
This binary is special *buzzwords incoming* and will get rid of the fuse mounting and get rid of the /data/media symlink which causes excessive Media Scanning load - basically just mounts the internal sdcard as ext4. Battery life gets a nice boost using this binary. Instructions on how to use it at the second post. All credits go to Greg White, I did nothing but testing it for him.
To activate use ADB or Terminal Emulator:
mount -o rw,remount /system
cp /system/bin/sdcard /system/bin/sdcard.bak
rm /system/bin/sdcard
cp /sbin/sdcard /system/bin/sdcard
chmod 0777 /system/bin/sdcard
reboot
Don't mess with this if you don't know what you're doing.
Click to expand...
Click to collapse
I, however, did this manually using RootExplorer:
Code:
1) Navigate to "/system/bin/" using a root enabled explorer app. Enable read and write access.
2) Rename the "sdcard" file found in that directory to "sdcard.bak" (so you know have a backup).
3) Navigate to "/sbin/". There will be an "sdcard" file there.
4) Copy the "sdcard" file to "system/bin/".
5) Change the permissions to "rwxr-xr-x".
6) Reboot the system.
My guess is that you can flash any kernel you want after this procedure. I have tried Siyah and it's working fine so far. Your mileage will vary.
If you find the camera saying things like "Unable to write to external storage" or whatever, you have to creat a "DCIM" folder in the root of your external sd card manually. It will then be alright (you have to change the storage device back to external in camera options).
Make a note that this is an extremely advanced procedure that I myself am in the process of fully vetting!
Cheers!
Erahgon said:
Firstly, go and flash the Franco Kernel
Click to expand...
Click to collapse
Thanks for your answer, but franco writes: 'This kernel is for Samsung roms only. No plans to make it work with AOSP or CM9'. So unfortunalety it's only runs on stock roms.
Hi, any news on how to get this to work on other kernels?
Thanks
Phk said:
Hi, any news on how to get this to work on other kernels?
Thanks
Click to expand...
Click to collapse
Also, on the mid-step of this, the file "/sbin/sdcard" does not exist...
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
pavitar said:
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
Click to expand...
Click to collapse
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
ricky310711 said:
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
Click to expand...
Click to collapse
Can you please tell me, how to apply a file permission? I tried checking the box which is not checked in the snapshot shared, but that too gives an error.Says "Operation failed"
pavitar said:
Can you please tell me, how to apply a file permission?
Click to expand...
Click to collapse
download mobile terminal from playstore
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
pavitar said:
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
Click to expand...
Click to collapse
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
iamareebjamal said:
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Click to expand...
Click to collapse
pavitar said:
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
Click to expand...
Click to collapse
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
iamareebjamal said:
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
Click to expand...
Click to collapse
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
pavitar said:
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
Click to expand...
Click to collapse
Try this
https://play.google.com/store/apps/...&utm_medium=organic&utm_term=universal+init.d
as there is no init.d here for moto e
1. so how we can run a script at boot without any scriptmanager app ,
and
2. where the default sdcard mounting points are specified (of internal sdcard0 )
Answer to second question
mnt/shell/emulated/0
Gogeta said:
Answer to second question
mnt/shell/emulated/0
Click to expand...
Click to collapse
and how do we change that ?
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 ?
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