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 ?
Related
I want to know that can we mount system files from sdcard?
I used to do on my old phone ( moto rokr e6 ) so if i want to change any boot anim i just write a script.
It would be nice to see mounting on android.
mnomaanw said:
I want to know that can we mount system files from sdcard?
I used to do on my old phone ( moto rokr e6 ) so if i want to change any boot anim i just write a script.
It would be nice to see mounting on android.
Click to expand...
Click to collapse
Go to the file on your sd, long press and select either copy or move. Go to system and hit paste..
What are you trying to move?
Twolazyg said:
Go to the file on your sd, long press and select either copy or move. Go to system and hit paste..
What are you trying to move?
Click to expand...
Click to collapse
Yes i could have done that but i m rooted via htc method
So i cant write in /system
mnomaanw said:
Yes i could have done that but i m rooted via htc method
So i cant write in /system
Click to expand...
Click to collapse
How about making a Flashable zip with the files? Not Sure about the HTC method man...
Hi all,
I am using BlaY0 's rom on my rooted HTC legend
i used clockworkmod rom manager to partition my SD card
now i was wondering how to enbale A2SD on the rom, i would love a step by step through the adb commands
also when i try to patch (Blayo's) the rom it keeps saying that this patch is not signed and wont install
Thanks in advance
bido91 said:
Hi all,
I am using BlaY0 's rom on my rooted HTC legend
i used clockworkmod rom manager to partition my SD card
now i was wondering how to enbale A2SD on the rom, i would love a step by step through the adb commands
also when i try to patch (Blayo's) the rom it keeps saying that this patch is not signed and wont install
Thanks in advance
Click to expand...
Click to collapse
In the Rom thread it clearly says
a2sd
To use this feature you have to enable it first. You do that by executing "a2sd --enable" via adb shell or some terminal app. To relocate dalvik-cache also, execute "a2sd --dc2sd" too. Reboot for changes to take effect. To see how much space do you have on relevant partitions execute "a2sd --free". If you want to disable a2sd, execute "a2sd --disable". In this case you loose all apps and dalvik-cache needs to be recreated upon reboot so make sure to backup apps before disabling.
Click to expand...
Click to collapse
So that should be the answer to your question
Try searching a bit before posting Question
I'v installed a 2nd rom with siyah 3.4.1, I see a hidden folder @ internal memory called '.secondrom' with size of 2.2 GB and only two img files: data&cache.
There is any way to browse the 'root' dir of the 2nd rom ?
I want to get into its system/etc folder, but these folders are only at the 'original' root (of the primary rom).
Another question -
Should I install every app (same apps) to each rom?
There is a simple way to install app to both roms at once or only separate to each rom?
About deleting 2nd rom:
After I'm doing a wipe date&cache to 2nd rom, what should I delete manualy from internal memory? (which folders?)
If you want to explore 2nd ROM files, you need to enter to "hidden" partition.
About deleting: just remove .secondrom folder.
You can't install one app at the same moment on both ROMs, cause the ROMs are independent of each other.
przemcio510 said:
If you want to explore 2nd ROM files, you need to enter to "hidden" partition.
About deleting: just remove .secondrom folder.
You can't install one app at the same moment on both ROMs, cause the ROMs are independent of each other.
Click to expand...
Click to collapse
Thanks for the answers!
What is the path of the hidden partition? there is any way to see it?
I'm using 'es file explorer' with all the root permissions enable, include enabled showing all the hidden files/folders... but can't see this partition. (if its possible of course)
PsyOr said:
What is the path of the hidden partition? there is any way to see it?
I'm using 'es file explorer' with all the root permissions enable, include enabled showing all the hidden files/folders... but can't see this partition. (if its possible of course)
Click to expand...
Click to collapse
Below the previous question -
If I'll update Siyah kernel or install other dual-boot kernel (for example dorimnax) will I have any problem with loading the 2nd rom?
anyone have any idea?
PsyOr said:
Below the previous question -
If I'll update Siyah kernel or install other dual-boot kernel (for example dorimnax) will I have any problem with loading the 2nd rom?
Click to expand...
Click to collapse
I don't think so because I believe that those kernels are based off Siyah in the first place.
Sent from my GT-I9100 using Tapatalk 2
PsyOr said:
Below the previous question -
If I'll update Siyah kernel or install other dual-boot kernel (for example dorimnax) will I have any problem with loading the 2nd rom?
Click to expand...
Click to collapse
No everything will be fine, I have even changed kernels to a non dual boot just to try them out and when I install SiyahKernel again it's just like I never changed and no need to set up the 2nd rom again as it's already there
Sent from my GT-I9100 using xda app-developers app
Awesome! Thanks for the answers!
Any answer to the other question:
There is any way to browse the 'root' dir of the 2nd rom ?
I want to get into its system/etc folder, but these folders are only at the 'original' root (of the primary rom). - all I can see is a folder @ internal sd .secondrom with 2.2gb - data & cache .img only...not all the other directories (system, ...)
What is the path of the hidden partition? there is any way to see it?
I'm using 'es file explorer' with all the root permissions enable, include enabled showing all the hidden files/folders... but can't see this partition. (if its possible of course)
[the folders of the 2nd rom as its shows like 1st rom]
/dev/block/mmcblk0p9 if I remember.
przemcio510 said:
/dev/block/mmcblk0p9 if I remember.
Click to expand...
Click to collapse
yeah I see it as a file [size 0] ,,, any way to get into this path [or there is other path to get into 2nd rom root?]
anyone have any idea ?
PsyOr said:
anyone have any idea ?
Click to expand...
Click to collapse
Swap 1 and 2 rom. After edit switch back
Gesendet von meinem GT-I9100 mit Tapatalk 2
accessing system root in 2nd rom
Its really very simple and you'll kick yourselves.
Boot into the second ROM.
Navigate to system in your file manager.
For dual boot the image file from your sd is mounted as the system so when you navigate to system while booted to second ROM it will be the contents of that file you are seeing.
For more info about how it works follow the link from the siyah website.
While we're on the topic can anybody help me to bind/symlink the standard app installation folder in data to the data folder in the second ROM to save duplicating installed apps? I understand that the data and dalvik will need to be desperate but surely the apk files don't need to be duplicated?
All hail gokhanmoral!
beetnubbin said:
Its really very simple and you'll kick yourselves.
Boot into the second ROM.
Navigate to system in your file manager.
For dual boot the image file from your sd is mounted as the system so when you navigate to system while booted to second ROM it will be the contents of that file you are seeing.
For more info about how it works follow the link from the siyah website.
While we're on the topic can anybody help me to bind/symlink the standard app installation folder in data to the data folder in the second ROM to save duplicating installed apps? I understand that the data and dalvik will need to be desperate but surely the apk files don't need to be duplicated?
All hail gokhanmoral!
Click to expand...
Click to collapse
I was thinking the same! Does anyone have a solution for this? it would be great if the apps on both roms would be the same!
Alexsk8.93 said:
I was thinking the same! Does anyone have a solution for this? it would be great if the apps on both roms would be the same!
Click to expand...
Click to collapse
The only way (as far as I know) is doing it via Titanium Backup...that what I did...
Hello
Some of application such as Sygic, Aptoid, Waze and others cannot access to sdcard unless I reboot.
When verffying with Root Explorere I have noticed that the default access to Sdcard is R/O. As soon as I change that to Read/Write every thing goes right.
The problem is R/O keeps come back and apps cannot run until I do modification again.
Anyone can help please as to fix permenantly this issue.
Thanks
samaliset said:
Hello
Some of application such as Sygic, Aptoid, Waze and others cannot access to sdcard unless I reboot.
When verffying with Root Explorere I have noticed that the default access to Sdcard is R/O. As soon as I change that to Read/Write every thing goes right.
The problem is R/O keeps come back and apps cannot run until I do modification again.
Anyone can help please as to fix permenantly this issue.
Thanks
Click to expand...
Click to collapse
There are two ways
1 the easy way is an app from playstore to do that at every boot
Are many can do this
2 the hard way is a script
You can paste it to init.d folder or script manager execute at every boot
Do you have gtab?
And sd card should not have sysrw option
Something wrong with install of rom
samaliset said:
When verffying with Root Explorere I have noticed that the default access to Sdcard is R/O. As soon as I change that to Read/Write every thing goes right.
The problem is R/O keeps come back and apps cannot run until I do modification again.
Click to expand...
Click to collapse
Peculiar problem. Will have to do some tests and look at some logs to find out the cause.
1. Can you create or delete files/dirs. on the SDcard, and do these changes persist after a reboot? Or do they vanish--like the changes never happened?
2. What's the output of this command right after a reboot?
Code:
$ [B]mount[/B]
rajeevvp said:
Peculiar problem. Will have to do some tests and look at some logs to find out the cause.
1. Can you create or delete files/dirs. on the SDcard, and do these changes persist after a reboot? Or do they vanish--like the changes never happened?
2. What's the output of this command right after a reboot?
Code:
$ [B]mount[/B]
Click to expand...
Click to collapse
Thanks for your reply,
1- I realy need some more details about this point. Some more explaination will be highly appreciated.
2- After typing this line and enter, the output is : /system/bin/sh:
Code:
$: not found. Moreover,after reboot, wh
ile launching Waze, I get the message : "Wazecan't access your sd card. Make sure it isn't mounted".
geowolf1000 said:
There are two ways
1 the easy way is an app from playstore to do that at every boot
Are many can do this
2 the hard way is a script
You can paste it to init.d folder or script manager execute at every boot
Do you have gtab?
And sd card should not have sysrw option
Something wrong with install of rom
Click to expand...
Click to collapse
Thanks fro your reply.
1- May know which app I should use.
2- Sure it looks hard for me to do that.
Yes I do have a Gtab 7.7 with JB.
The rest of the message needs more explaination if possible.
samaliset said:
Thanks fro your reply.
1- May know which app I should use.
2- Sure it looks hard for me to do that.
Yes I do have a Gtab 7.7 with JB.
The rest of the message needs more explaination if possible.
Click to expand...
Click to collapse
Sd card always alow read/write permission is not part of root
Type mount to terminal and post the result so rajeevvp give you his knowledge
samaliset said:
Yes I do have a Gtab 7.7 with JB.
Click to expand...
Click to collapse
There is no such device as a gTablet 7.7. Is this the tablet you have?
1. Use the standard file manager app and create or delete some files and directories on the SDcard. Reboot the gTablet. Verify that the changes you made remain after the reboot.
2. The $ character is just a prompt, used to indicate that the commands that follow can be executed by any user. Don't type that into the Terminal emulator app. Type in only the stuff shown in bold.
3. Setup adb (see the sticky threads) to make entering commands and collecting logs easier.
4. From now on post the exact error or diagnostic messages that you see. Or, make screenshots and post them.
I am very sorry to post my message here by mistzke.
Anyway I would like to thank all for your help and would like to inform you that the probme had been solved in installing a new tom.
Thanks znd sorry again
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