I tried using an app. the apps I used: es file explorer, mount system ro/rw, mount system rw
and I tried using a command, both on my PC and on my phone. the command I used:
Code:
su
mount -o remount,rw /system
my rom is AOSIP if this is relevant, because I didn't have this problem on any other roms I used.
Portrucci said:
I tried using an app. the apps I used: es file explorer, mount system ro/rw, mount system rw
and I tried using a command, both on my PC and on my phone. the command I used:
Code:
su
mount -o remount,rw /system
my rom is AOSIP if this is relevant, because I didn't have this problem on any other roms I used.
Click to expand...
Click to collapse
Did you check if AOSIP has root by default?
FSadino said:
Did you check if AOSIP has root by default?
Click to expand...
Click to collapse
Yes, it does
Related
i rooted my verizon galaxy tab and i can run Root apps, but i cant move a wpa_supplicant file to my /system/root using Astro.
Is this a root issue or do i need something better than Astro? I also tried OI file manager but it just says "cannot move file here".
By default, /system is (usually) mounted read-only. You probably need to remount it read-write.
Code:
adb remount /system
adb push [path-to-file] /system/bin
If remount doesn't work, try
Code:
adb shell mount -t yaffs2 -o rw,remount /dev/block/mtdblock3 /system
Hey guys,
Loaded BAMF 1.5 yesterday and have been enjoying the ROM thus far. However, I've been trying to push my custom widget.txt to the \system\customize\ folder so I can have my own power controls in the notifcation bar. I have tried the Mount rw/ro app from the Market, and have also tried mounting rw using adb (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Each time, when I use the command: adb push widget.txt /system/customize/ I get the error: failed to copy 'widget.txt' to '\system\customize\': Read-only file system
Where am I going wrong?
Seth
sethschmautz said:
Hey guys,
Loaded BAMF 1.5 yesterday and have been enjoying the ROM thus far. However, I've been trying to push my custom widget.txt to the \system\customize\ folder so I can have my own power controls in the notifcation bar. I have tried the Mount rw/ro app from the Market, and have also tried mounting rw using adb (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Each time, when I use the command: adb push widget.txt /system/customize/ I get the error: failed to copy 'widget.txt' to '\system\customize\': Read-only file system
Where am I going wrong?
Seth
Click to expand...
Click to collapse
I'm pretty sure the TB is using EXT3, not YAFFS2.
Try
Code:
mount -o remount,rw -t ext3 /dev/block/mtdblock3 /system
Even easier, assuming you have busybox. busybox mount isn't as lame as the standard mount which is provided, so you don't have to tell it as much, it can figure things out on its own:
busybox mount -o remount,rw /system
busybox mount -o remount,ro /system
Click to expand...
Click to collapse
even easier.
sysrw
sysro
Doesn't anyone ever read the first post of my rom?
I'm an idiot. Thanks for the ext3 vs yaffs2 reminder.
I'll try busybox at some point also to check
And to Adrynalyne, apparently I didn't read the first post...my bad. Thanks for reading mine, though. I'll pay closer attention in the future.
Seth
i want to use INT2EXT in cm9 i followed this tutorial
xpmode said:
INT2EXT+ INSTALLATION TUTORIAL
IF YOU ALREADY HAVE S2E, LINK2SD OR SIMILAR, YOU MUST REPARTITION SD CARD AND FACTORY WIPE
int2ext+ is a relatively new script that instead of making symbolic links(Link2SD) or moving certain partitions(S2E) to sd, extends your internal storage into your ext partition in sd, which means S2E's potential space saving and Link2SD's stability combined together and gives you something to brag about.
PREPARATIONS
Download the latest build of CyanogenMod 9.
Download the latest version of CronMod INT2EXT+ here.
Open CyanogenMod 9 zip.
Navigate to /system/etc/init.d
Open INT2EXT+ zip.
Navigate to /system/etc/init.d
Add the file called 40int2ext in the /system/etc/init.d directory in CM9 zip.
INSTALLATION
Go to recovery, do factory reset and advanced > partition sd card.
Select 1024M for ext(for some reason, I selected 4096 and it only read the first 1GB-ish) and 0M for swap.
Wait until it says Done and goes to menu.
Go to Mounts and Storage.
Select USB storage and connect your phone to your computer.
Copy your modified CM9 zip file to the root of your sd.
Select unmount.
Reflash ROM.
Reboot.
After reboot, go to settings > developer settings > root access and select Apps and ADB.
Go to your adb directory and do adb shell.
Type su.
Then do:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Reboot.
After reboot, reboot into recovery and flash gapps.zip normally.
Then go to Applications and enjoy your new, extended internal storage.
Click to expand...
Click to collapse
can someone help me how to do adb shell and go to adb directory
Use the directory that you used to root your device.
Hpsgill said:
can someone help me how to do adb shell and go to adb directory
Click to expand...
Click to collapse
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Chaosgod27 said:
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Click to expand...
Click to collapse
Thanks
No worries =)
Chaosgod27 said:
No worries =)
Click to expand...
Click to collapse
can u tell me how to use other scripts eg apps2sd,link2sd and their works
Hmm, if you want. Right now I'm a bit busy with work...
Chaosgod27 said:
Hmm, if you want. Right now I'm a bit busy with work...
Click to expand...
Click to collapse
Anytime ,when u r free or pm me
Sent from my HTC Explorer A310 using xda premium
What did you want to know about them? You want to know how to install them or?
Chaosgod27 said:
What did you want to know about them? You want to know how to install them or?
Click to expand...
Click to collapse
Every thing about there scripts I never partation my memory card
Sent from my HTC Explorer A310 using xda premium
Chaosgod27 said:
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Click to expand...
Click to collapse
Hmmm, you don't need adb for this. Just use terminal emulator on your phone. It comes installed by default on CM9 roms. Or you can search play store for android terminal emulator. The app is by Jack Palevich
Code:
su
mount -rwo remount /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -ro remount /system
Then again, I don't really see why it is necessary to deny execute permissions to these scripts in first place. They are just empty shells - unless they have been modified.
I'm using int2ext4 right now and never really had to...
EDIT: If you want to reverse these changes then
Code:
su
mount -rwo remount /system
chmod -R 755 /system/etc/init.d
mount -ro remount /system
Hpsgill said:
can u tell me how to use other scripts eg apps2sd,link2sd and their works
Click to expand...
Click to collapse
Script details:
a2sd,a2sd+,a2sd++,d2ext,d2ext+,int2ext,int2ext+,int2ext4,int2ext4+ --- forum.xda-developers.com/showthread.php?t=1716124
mount2sd --- forum.xda-developers.com/showthread.php?t=1342387
As of link2sd it uses installrecovery.sh file in /system/etc to mount sd-ext partition. It then moves apps/data/dalvik-cache to sd-ext and places symlinks at the original locations.
Take a look here where i've explained why symlink based apps/scripts should not be used on HTC explorer.
Hit thanks if i helped!:good::good:
sabaatworld said:
Script details:
a2sd,a2sd+,a2sd++,d2ext,d2ext+,int2ext,int2ext+,int2ext4,int2ext4+ --- forum.xda-developers.com/showthread.php?t=1716124
mount2sd --- forum.xda-developers.com/showthread.php?t=1342387
As of link2sd it uses installrecovery.sh file in /system/etc to mount sd-ext partition. It then moves apps/data/dalvik-cache to sd-ext and places symlinks at the original locations.
Take a look here where i've explained why symlink based apps/scripts should not be used on HTC explorer.
Hit thanks if i helped!:good::good:
Click to expand...
Click to collapse
thanks maaaaaan!!!
where is the adb directory?? do we have to install it in our pc or its there in our explorer?
Sent from my HTC Explorer A310e using xda premium
everything i did went well and i checked the internal memory its shows 850mb ... now the problem is when i type adb shell in terminal its say error:device not found ... so what should i do ???
Hi! My problem is that I want to mod /system/etc stuff. But problem is: I can't mount /system rw in adb shell!
I'm using CM11 20140622 Nightly
What i've tried:
- sysrw command(alias sysrw='mount -o remount,rw /system')
- by hand(mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system)
None of those commands produce output and they exit 0
- ES File Explorer and CM File Manager
I don't know how, but mounting rw in UI always works, but not over adb.
Can anyone tell me a solution how to mount /system rw successfully over shell?
mikroskeem said:
Hi! My problem is that I want to mod /system/etc stuff. But problem is: I can't mount /system rw in adb shell!
I'm using CM11 20140622 Nightly
What i've tried:
- sysrw command(alias sysrw='mount -o remount,rw /system')
- by hand(mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system)
None of those commands produce output and they exit 0
- ES File Explorer and CM File Manager
I don't know how, but mounting rw in UI always works, but not over adb.
Can anyone tell me a solution how to mount /system rw successfully over shell?
Click to expand...
Click to collapse
Code:
adb root
adb shell
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
Sent from my Nexus 5 using Tapatalk
rootSU said:
Code:
adb root
adb shell
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Still same thing, no rw, no output
mikroskeem said:
Still same thing, no rw, no output
Click to expand...
Click to collapse
Windows or Linux? Are you using an outdated adb?
That's definitely correct, I tested it.
rootSU said:
Windows or Linux? Are you using an outdated adb?
That's definitely correct, I tested it.
Click to expand...
Click to collapse
Linux, adb version 1.0.31
Yeah it's correct but problem is it doesn't work.
mikroskeem said:
Linux, adb version 1.0.31
Yeah it's correct but problem is it doesn't work.
Click to expand...
Click to collapse
remove and reinstall your adb
Works fine with that command on both windows and linux for me.
Does adb devices even work?
Can you screenshot the error?
rootSU said:
remove and reinstall your adb
Works fine with that command on both windows and linux for me.
Does adb devices even work?
Can you screenshot the error?
Click to expand...
Click to collapse
No error output, i'm in adb shell so "[email protected]:~ #" will appear
I run commands there.
adb itself works fine.
mikroskeem said:
No error output, i'm in adb shell so "[email protected]:~ #" will appear
I run commands there.
adb itself works fine.
Click to expand...
Click to collapse
Screenshot please
Of this:
Code:
H:\>adb root
adbd is already running as root
H:\>adb shell
[email protected]:/ # mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
platform/msm_sdcc.1/by-name/system /system <
[email protected]:/ #
rootSU said:
Screenshot please
Of this:
Code:
H:\>adb root
adbd is already running as root
H:\>adb shell
[email protected]:/ # mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
platform/msm_sdcc.1/by-name/system /system <
[email protected]:/ #
Click to expand...
Click to collapse
sorry can't make screenshot atm, but i copyed terminal contents to here: http://hastebin.com/dicuhiyema.hs
EDIT: 6th line is the mount command, it wrapped badly
mikroskeem said:
sorry can't make screenshot atm, but i copyed terminal contents to here: http://hastebin.com/dicuhiyema.hs
Click to expand...
Click to collapse
Ah yeah that's as good as a screenshot.
Theres no option in CM11 dev options for adb root is there? I have on in SlimKat where I must enable ADB root.
mikroskeem said:
EDIT: 6th line is the mount command, it wrapped badly
Click to expand...
Click to collapse
Yeah my ubuntu terminal does that too.
rootSU said:
Ah yeah that's as good as a screenshot.
Theres no option in CM11 dev options for adb root is there? I have on in SlimKat where I must enable ADB root.
Yeah my ubuntu terminal does that too.
Click to expand...
Click to collapse
There is actually and it's set to "Apps and ADB", but I might try out next nightly. It might doesn't have that problem anymore. Prolly some SELinux conflict or kernel blocks something
Now it works.
I think it was CM problem.
mikroskeem said:
Now it works.
I think it was CM problem.
Click to expand...
Click to collapse
At first I was thinking it was your computer but everything you were doing was right so I agree. It seems it was.
Sent from my Nexus 5 using Tapatalk
using bin/mount rather than xbin/mount
mikroskeem said:
I can't mount /system rw in adb shell!
What i've tried:
- sysrw command(alias sysrw='mount -o remount,rw /system')
...
Can anyone tell me a solution how to mount /system rw successfully over shell?
Click to expand...
Click to collapse
For posterity, I'm adding what worked for me on LolliKat (which is cm11) for doing this from the phone's console/shell: I had to use the command `/system/bin/mount` rather than just `mount`. Once that had been done once, the other methods would work fine until reboot. (I was doing this because somehow link2sd had lost its ability to "update mount scripts" and "integrate system app updates".
These all worked for me:
/system/bin/mount -o remount,rw /system
/system/bin/mount -o remount,rw -t yaffs2 /system
/system/bin/mount -o remount,rw -t yaffs2 /system /system
/system/bin/mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /system
More info (in my own context) here and here:
http://forum.xda-developers.com/showpost.php?p=61068974&postcount=3
http://android.stackexchange.com/a/110883/109855
Have flash my new pixel 2 with latest android P preview5, rooted with twrp and magisk 16.04, I can get su under adb shell
I can remount the system as rw but fail in /vendor, an mount: '/dev/block/dm-0'->'/vendor': I/O error is coming accross
130|walleye:/ $ su
walleye:/ # mount -o rw,remount -t auto /system
walleye:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-0'->'/vendor': I/O error
1|walleye:/ # cp /mnt/sdcard/xxxx.so /vendor/etc
cp: /vendor/etc/xxx.so: Read-only file system
I'm pretty sure this is working in a rooted pixel XL of android OREO,
copy the file in TWRP file manager can't work either, I can see the file is copied into the vendor in TWRP, but file gone away after reboot into system, any suggestion is pretty appreciated !
misslebulletttttt said:
Have flash my new pixel 2 with latest android P preview5, rooted with twrp and magisk 16.04, I can get su under adb shell
I can remount the system as rw but fail in /vendor, an mount: '/dev/block/dm-0'->'/vendor': I/O error is coming accross
130|walleye:/ $ su
walleye:/ # mount -o rw,remount -t auto /system
walleye:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-0'->'/vendor': I/O error
1|walleye:/ # cp /mnt/sdcard/xxxx.so /vendor/etc
cp: /vendor/etc/xxx.so: Read-only file system
I'm pretty sure this is working in a rooted pixel XL of android OREO,
copy the file in TWRP file manager can't work either, I can see the file is copied into the vendor in TWRP, but file gone away after reboot into system, any suggestion is pretty appreciated !
Click to expand...
Click to collapse
Why not use the latest magisk? Btw this is the wrong section.
Sent from my Pixel 2 using Tapatalk
joetheshmo said:
Why not use the latest magisk? Btw this is the wrong section.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Have tried magisk 16.7, but in vain, system partition can be remounted as "RW", however not the case in /vendor,
any tool can help to remount a partition during runtime ?
I found disable AVB2.0 / dm-verity can do the trick, now I can remount /vendor partition without I/O error !
If i can ever get my Gf to stop playing with my pixel 2 ( she has an iphone ). Ill update from DP4>DP5 and see how far i get.
Im having no issues after the update.
- flashed DP5 with Deuces Script.
- Flashed Twrp 3.2.2
-Booted system to setup initially.
-Booted to twrp installed Magisk 16.7
-reboot system .
havent had an I/O error. rooted fine.
misslebulletttttt said:
I found disable AVB2.0 / dm-verity can do the trick, now I can remount /vendor partition without I/O error !
Click to expand...
Click to collapse
after unchecking Preserve AVB v2.0/dm-verity in app, Magisk needs to be reinstalled. Quoted from here:
in Magisk Manager, “Uninstall > Restore Images” to restore the images, check “Preserve AVB 2.0/dm-verity” box in Advanced Settings, then reinstall Magisk via the app.