Alright, so I've been trying to mount the /system partition as rw today now that we have perm-root and I've been failing. I'm tried multiple mount options such as
mount -o rw,remount -t ext3 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk0p15 /system
and a few others. The command works but when I try to uninstall an application via the package manager:
pm uninstall /system/app/amazonmp3.apk
pm uninstall /system/app/amazonmp3
I get failure.
I was also searching in the init.rc scripts in /, and noticed that it mounts the /system twice. Once in rw and then again in ro. I can't change that file though since for whatever reason, I still can't access the /system even with perm-root (s-off).
Titanium Backup also doesn't detect any /system applications.
Any thoughts, or enlightening clarifications? I'm not a Linux beginner and have experience in system administration all the way from Debian Sid to Arch Linux.
EDIT:
Solution: I have ro.secure=0 now and the remount is now successful.
You are using the pm command incorrectly. The argument is package name, not file name.
pm uninstall com.amazon.mp3
pm list packages for a full list.
That would be the reason. Unfortunately I can't look at the man pages of these commands on the phone ;D.
You edited your post to show that you now have r/w access to the /system folder, but you didn't say how you achieved ro.secure=0.
Care to share? I'm having the same issue.
perm root will give you ro.secure=0
jgro1976 said:
You edited your post to show that you now have r/w access to the /system folder, but you didn't say how you achieved ro.secure=0.
Care to share? I'm having the same issue.
Click to expand...
Click to collapse
rosecure=0 is set in the ramdisk of the kernel. It allows easy mounting rw , as in adb remount, however shouldn't be needed. Use this to mount as rw:
# mount -o rw,remount /dev/block/mmcblk0p25 /system
Replace rw with ro and run again when your done to return system to ro. I just tested it and it does mount as rw
Just to make sure it worked, I type that and get:
Usage: mount [-r] [-w] [-options] [-t type] device directory
after trying this.
jgro1976 said:
Just to make sure it worked, I type that and get:
Usage: mount [-r] [-w] [-options] [-t type] device directory
after trying this.
Click to expand...
Click to collapse
U sure you typed it exactly as I did?
There is a space after /dev/block/mmcblk0p25 before /system
Edit: and no space between comma and remount as in rw,remount
Yeah, that's how I typed it, exactly as you had it =\
jgro1976 said:
Yeah, that's how I typed it, exactly as you had it =\
Click to expand...
Click to collapse
Hmm, and you did this from root prompt # not $.
Can anyone else confirm or deny that command for me. I'm gonna flash a unmodified kernel when I get home tonight and see if that makes a difference.
fastludeh22 said:
Hmm, and you did this from root prompt # not $.
Can anyone else confirm or deny that command for me. I'm gonna flash a unmodified kernel when I get home tonight and see if that makes a difference.
Click to expand...
Click to collapse
I can confirm it doesn't work on my G2 either. I'm using Cyanogen RC1 btw.
try
mount -o remount,rw /dev/block/mmcblk0p25 /system
maybe the rw has to come after remount.
Anyways, I know mine works on permrooted stock
That did the trick, thanks!
ratchetrizzo said:
try
mount -o remount,rw /dev/block/mmcblk0p25 /system
maybe the rw has to come after remount.
Anyways, I know mine works on permrooted stock
Click to expand...
Click to collapse
jgro1976 said:
That did the trick, thanks!
Click to expand...
Click to collapse
So weird. If I type it that way, I get the mount options menu u were getting. If I type it my way it works.
I was messing around with remounting the /system partition with rw permissions, and the thing is that it does work as in, it doesn't give you an error when mounting, but it still doesn't let you access it. It's weird.
As for the ro.secure, I just used installed bacon bits, and it did it for me.
There's an app for that! I'm using a market app called mount /system (rw / ro). You can just search mount rw in the market, its free too
Sent from my T-Mobile G2 using XDA App
Can't you just use adb remount?
It worked for me (GT-P1000, CM 10.1-20130218-experimental- cdesai)
First, my Euro Desire Z is S-Off (using the gfree method) and perm-rooted.
I was messing with installing some new keyboard layouts to the /system folder, when I found and installed busybox from the market to use its cp command...
Then I discovered I could no longer write to /system -- I could before busybox
I booted to recovery, installed my nandroid backup (taken before installing busybox), and I still can't get write access to /system
I did a factory wipe (still have S-Off) ran visionary to root and permroot ( I get the # prompt just fine) and still no write access to /system.
I restored my nandroid to get my apps back and still can't seem to get write access.
Any ideas
Hmm -- I just found and installed "mount /system" from the market and that did it -- I can now write to /system.
Not sure why it stopped working before... Busybox may have been a red herring.
I think it was just that you still had /system mounted as read-only, and that app just mounted it as read-write (i.e. "mount /system -o rw, remount" )
steviewevie said:
I think it was just that you still had /system mounted as read-only, and that app just mounted it as read-write (i.e. "mount /system -o rw, remount" )
Click to expand...
Click to collapse
Yeah -- I had it RW and something must have remounted it to RO --perhaps when I was doing an adb session...
Speaking of BusyBox -- whats the best version people are using for the DZ?
Guys, can someone tell me what i'm missing? I followed this guide to root and S-OFF my phone, but just now i realized that i have no write access to /system partition. It isn't very important for me, since i'm flashing only rooted ROMs and when i need to gain write access to /system partition - i'm rebooting into CW Recovery, but... It would be handy to have it anyway
Some info form what i see in fastboot:
VISION PVT ENG S-OFF
HBOOT-0.8.4.2000
RADIO-26.03.02.26_M
Thank you in advance.
Did you verify that you have root? Use the Android Terminal Emulator, type su and if you get a #, you're good to go. If you do have root, just use Root Explorer and hit the R/W button while in the system folder.
Sent from my HTC Vision using XDA App
ScooterG said:
Did you verify that you have root? Use the Android Terminal Emulator, type su and if you get a #, you're good to go.
Click to expand...
Click to collapse
Yes, i'm getting root permissions here.
ScooterG said:
If you do have root, just use Root Explorer and hit the R/W button while in the system folder.
Click to expand...
Click to collapse
When i press mount as R/W, nothing happens and i can't make any changes in /system partition.
Also, i tried Font Changer Lite (from Market), but i'm getting message:
"Write access for the system partition was not established on your device and therefore this application will have to be closed.
Please make sure your device has full root before you try again"
Am i missing something? Thanks for quick reply btw.
Using ADB
1. adb shell
2. mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
3. exit
aznsnake666 said:
2. mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
Click to expand...
Click to collapse
"mount -o rw,remount /system" should work too.
(you need to mount /system specifically as rw, by default it's still mounted read-only even if you have root/S-OFF)
Or simply:
adb remount
Love that No need to remember the blocks and hassle with the mount command
AnyDone said:
Or simply:
adb remount
Love that No need to remember the blocks and hassle with the mount command
Click to expand...
Click to collapse
This is the best way I've found to do it, but it is only temporary.
Thank you guys very much, that worked
Edit: Font Changer Lite still complaining about permissions.
There's a /system remount app in the market lol
Sent from my HTC Vision using XDA App
stevencpoynter said:
There's a /system remount app in the market lol
Click to expand...
Click to collapse
Sure, let's download an app for each ADB command, so then we can complain about having not enough of internal memory again
I know that sounded a little sarcastic lol, was in the bank waiting in line.
Seriously though, there's a one click remount app, its wonderful as I no longer have to use adb or a terminal to make /system rw
Sent from my HTC Vision using XDA App
Hi All,
Can some one please suggest me a replacement for root explorer? I tried to run it on Moto ginger 2.3.4 but getting a force close.
How do you guys copy files to system or other protected directories? I tried adb remount but its failing for permissions issue.
You have to use root explorer v2.16
I use Yaffs Explorer. It's very nice in that it uses a small font for both file lists and the internal editor, so you see a lot of content on the screen.
As for ADB, do an "adb shell", then you can gain root by typing "su". On the phone the usual superuser popup will appear, confirm it and voila you have root in the adb shell. Then you can remount with "mount -o remount,rw -t ext3 /dev/block/mmcblk1p21 /system". And to go back to read-only: "mount -o remount,ro -t ext3 /dev/block/mmcblk1p21 /system"
Gusar321 said:
I use Yaffs Explorer. It's very nice in that it uses a small font for both file lists and the internal editor, so you see a lot of content on the screen.
As for ADB, do an "adb shell", then you can gain root by typing "su". On the phone the usual superuser popup will appear, confirm it and voila you have root in the adb shell. Then you can remount with "mount -o remount,rw -t ext3 /dev/block/mmcblk1p21 /system". And to go back to read-only: "mount -o remount,ro -t ext3 /dev/block/mmcblk1p21 /system"
Click to expand...
Click to collapse
Great!! Ill try that.. Thanks..
Also you can try Super Manager 2.2.9, it's free and it's pretty good.
It's my first relevant post in here so please be benevolent and friendly to me .
Hello everyone,
After long hours of roaming around on the internet, Moto forums, PowerAMP forums (you wouldn't believe how many people posted this problem in there), huge exchange of emails and debugs to the Nexus Media Importer dev, and checking out many many topics here on XDA, I finally came across the only way to use an USB-OTG pendrive as a music library, and having Android detect it (through the Media Service) and build the music library for other media apps to use.
tl dr; Problem: You wanted loads of music without wasting precious internal memory. You tried using an USB pen but no mp3 apps were able to find the files, nor stickmount, nor whatever.
This is so far the only way to do this on android Marshmallow.
Believe me, I've tried almost everything one can do, including using the Nexus Media Importer, Stickmount, OTG Helper, etc (spoiler alert, none of these worked).
Why is this happening, you ask? Well, Google changed things on Android 6.x.x so much regarding filesystems and USB support that full read/write on USB OTG with other apps no longer works, although I've never tested on previous versions of Android. But I finally managed to find a way to do it, and here I intend to share it with you guys.
Requirements - Rooted phone and permissive SELinux (what is that and how do I do it? don't worry, it's easy and I'll explain a bit later)
1st step - Verify that your phone is capable of using USB-OTG. If it is not, check on play store for other apps that supposedly can enable USB Host support on your phone, although I've never tried them because I never needed, so I can't say anything. My phone is a Moto X 2014 and it comes with OTG support embedded.
2nd step - Format your pendrive as NTFS. This is very important because...
If you use your pendrive as Fat32, Android will mount it to a folder in /data/media_rw/blablabla with GID and UID 1023 (media_rw), which most apps don't have permissions to access, thus they won't be able to find your pendrive and build a music library. Why? Well, glad you asked...
...Since Fat32 doesn't support the linux permissions system, Android mounts the pendrive with the FUSE fs wrapper, which cloaks a permission system hard-coded into some file in the Android system that I wasn't able to tell how could I modify it in order to set the pen permissions as 777 root root.
You can do so by plugging your pen on a Windows PC and right clicking -> Format. Remember to backup your data, otherwise you will lose everything. Your pen will still be able to be used on Windows pcs and Macs. You could also use other fileformats...
... like EXT4 or f2fs or exFAT or whatever, but do it at your own risk. I have no idea if those would work, despite them being able to use the linux permission system.
3rd step - Install the wonderful app Paragon HFS and NTFS mounter from appstore or whatever. They say it isn't compatible with marshmallow but it is, the only issue is that it can't mount a pendrive automatically but it's very easy to do it manually. In the settings menu, you can set SELinux as permissive. Since I'm not an android dev, only an ambicious amateur, I can't really explain what it does or what happens when you do that. So far, neither me or my phone died because of that, so.
Oh by the way, whenever you insert the pen , Android will say it's corrupted and ask you to format it. DO NOT DO IT! That happens because Android doesn't natively support NTFS (hence using an external app to solve that). Oh, and since we're talking about that, there is a way for Android to natively support NTFS...
..., just search it up on XDA. Beware that it's outdated and it won't work on Marshmallow either, unless you edit the copymodulecrc script, but that goes beyond my knowledge. For now, stick to the plan.
4th step - You need to choose the folder which you want to mount the pen to, which will be a folder in the root Android folder (I chose /pen so that I wouldn't forget)
You are now probably thinking, "That's insane! You need to edit init.rc in order to do that!" Well, you're kinda right, but there is a workaround for that. Why do I do this? Well...
... if you mount the pen in another random folder such as /storage/emulated/0/pen it won't work because all the folders underlying that one have certain permission issues that don't let other media apps be able to search for music files.
So here I'll show you two ways of accomplishing this.
4.1 Editing init.rc - This is very complex and NOT RECOMMENDED unless you're very comfortable with messing with boot files. PLEASE DO NOT DO THIS if you aren't sure of what you're doing, don't tell me I didn't warn you.
So in order to do this, well, I won't explain it to you. Search it up on the internet, it's very complex and too big for me to post here. But in the end what you want to do is edit the init.rc file, adding two lines:
"mkdir /pen" and "chmod 777 /pen".
4.2 Creating a script that runs on boot - This is the one method I recommend since it's harmless, but you have to install yet another app, that allows you to run scripts at boot. I used script manager. Then create a script that mounts the / folder as rw, creates the folder /pen, chmods it to 777. I used the following:
#!/system/bin/sh
su -c mount -o rw,remount /proc /
su -c mkdir /pen
su -c chmod 777 /pen
I tried other mount -o commands with rootfs instead of /proc but they didn't work. I don't know the difference but I hope it's harmless. Anyways, let's move on.
Run the script to see if it works, and to create the folder. Use a rooted file explorer to verify if the folder was created.
5th step - Reboot your phone if you had to set SELinux as permissive, and type on the Terminal "su -c getenforce" to confirm that your SELinux is permissive.
VERY IMPORTANT - On the Paragon app, open settings and disable FS access rights, otherwise it's the same as mounting a Fat32 pendrive - not what we want.
On the Paragon app, choose the folder we created before as the folder to mount the pen to, and mount the pendrive. If you followed all the previous steps correctly, the app won't have any issues mounting the pen.
6th step - Find a way to enforce Android building a media library with the new files in the USB OTG pendrive. There are many ways to do this and I recomment the one I used, but I will tell you other ways.
I used the app jetAudio which is a media player that can also forceably build a media library. On jetAudio settings menu, press "Rebuild media library" and point to the /pen folder. It will start reading all the files and Android now detects your pendrive as a media library.
Another way would be to use an app called FolderMount, and creat a symlink from the /pen to another folder in your emulated SD storage (you know, the only folder you have access to if you're not rooted), and wait for some time until hopefully Android detects your new music. If you don't want to use FolderMount, do a symlink with another method (like the ln command)
EDIT - Another cool way I found elsewhere on StackExchange is to run this command (through a script or whatever):
am broadcast -a android.intent.action.MEDIA_MOUNTED -n com.android.providers.media/.MediaScannerReceiver (-d file:///pen)
which forces Android to run a media scan. The part on parenthesis is optional, you can use it to choose the folder in which Android runs the media scan.
Hurray! Congrats for reaching this part of the post. If you did everything correctly, all media apps will finally be able to find the files. I posted some screenies to orientate you.
Feel free to ask anything and I will try to answer or explain. Remember that I'm no Android dev so my knowledge is limited. Feel free to thank me, if you want too.
reserved post
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
AndDiSa said:
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
Click to expand...
Click to collapse
It's not as straight-forward as you're saying.
Most media player apps that weren't updated to support Android 6's native USB OTG support will not be able to read a pen's contents. This topic that I made is aimed to circumvent the issue by mounting the pen in a different way. That bug you mentioned is not something I want to solve, and even if a new kernel solved the issue that I'm talking about, most manufacturers wouldn't update their devices...
Ok, you may be right with apps which are not yet updated to support Marshmallow, I didn't check that.
gaferreira13 said:
It's not as straight-forward as you're saying.
Most media player apps that weren't updated to support Android 6's native USB OTG support will not be able to read a pen's contents. This topic that I made is aimed to circumvent the issue by mounting the pen in a different way. That bug you mentioned is not something I want to solve, and even if a new kernel solved the issue that I'm talking about, most manufacturers wouldn't update their devices...
Click to expand...
Click to collapse
Oh, and maybe now that I think of it, this could solve the problem, since mounting/unmounting is done with the Paragon app instead of Android. Give it a shot
AndDiSa said:
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
Click to expand...
Click to collapse
Using native otg function, you can only copy files between phone and otg dive. To open a file e.g. To install apk from otg, you have to first copy it to phone's storage. On many media player, video can only be played sequentially (seek bar doesn't work).
Stuck at step 4.2, folder is not created
kashinath said:
View attachment 3746340Stuck at step 4.2, folder is not created
Click to expand...
Click to collapse
Hey, is there any way for you to determine the path of your root folder? Maybe using ES File Explorer. For some phones, the root folder isn't pointed to /.
EDIT - If you can't do that, try replacing the first of those commands with the following:
su -c mount -o rw,remount,rw /system
I'm also getting the same issue as kashinath, won't let me create pen. I've also tried pointing the mounter to a directory in /storage/emulated/0/pen but it seems to just crash and restart the app.
EDIT:
Okay so I've solved the problem completely differently. The otg storage is found in /mnt/media_rw, so I used the app "FolderMount [ROOT]" to point the folder "pen" (in the internal storage) to the /mnt/media_rw/*random string* folder. I then used the app "media.Re.Scan:" to force the media scanner to scan that folder as it didn't seem to want to do it. Now all apps seem to be working.
What tipped me off about this was this post: http://forum.xda-developers.com/nexus-6/help/marshmallow-usb-otg-mounting-media-t3230588
It seems you have to turn the folder mount on/off every time you plug/unplug the USB drive otherwise it won't play the files.
Thanks for the detailed instructions nonetheless.
Viridis said:
I'm also getting the same issue as kashinath, won't let me create pen. I've also tried pointing the mounter to a directory in /storage/emulated/0/pen but it seems to just crash and restart the app.
EDIT:
Okay so I've solved the problem completely differently. The otg storage is found in /mnt/media_rw, so I used the app "FolderMount [ROOT]" to point the folder "pen" (in the internal storage) to the /mnt/media_rw/*random string* folder. I then used the app "media.Re.Scan:" to force the media scanner to scan that folder as it didn't seem to want to do it. Now all apps seem to be working.
What tipped me off about this was this post: http://forum.xda-developers.com/nexus-6/help/marshmallow-usb-otg-mounting-media-t3230588
It seems you have to turn the folder mount on/off every time you plug/unplug the USB drive otherwise it won't play the files.
Thanks for the detailed instructions nonetheless.
Click to expand...
Click to collapse
Yeah forget mounting anything in the /storage/emulated/0...
According to the post you linked in your comment, "6.0 mounts to /mnt/media_rw/ but I can't seem to get any media players to see it. I tried creating a symbolic link in /storage/emulated, but I get an error with root explorer about symbolic links not being supported" which is exactly what happened to me
If you don't like the folder mount alternative you can always do a bind command (but i'm not sure how it works), search it up and see if you get any results.
Is your pen in Fat32 though?
There is a workaround for the pen thing... If you use Total Commander and want to edit any files in /, it asks you to run a command that mounts the / folder. Try to see what command it is and replicate it into the script, then the rest might work.
Thank you so much !! It worked on my XT1033 falcon dual sim - MM6.0 identity crisis 1.3a . I can finally restore all my nandroid backups.
Just to correct shouldn't the last command in the script be
su -c chmod 777 /pen
instead of
su -c chmod /pen 777
4k5blr said:
Just to correct shouldn't the last command in the script be
su -c chmod 777 /pen
instead of
su -c chmod /pen 777
Click to expand...
Click to collapse
No, thank you
And, damn you're right, lol I'll correct it ASAP, thanks a lot for pointing it out
I'm a complete newbie at this, in fact I rooted my device just to do this
Anyways I'm getting the same issue kashinath is getting and tried the other command you recommended (su -c mount -o rw,remount,rw /system ) wich also didn't work
In that reply you also said that the root folder is different between devices so, if I determine the path to my root folder, where exactly in the script do I have to put it? (Again I'm a newbie)
Arcane35 said:
I'm a complete newbie at this, in fact I rooted my device just to do this
Anyways I'm getting the same issue kashinath is getting and tried the other command you recommended (su -c mount -o rw,remount,rw /system ) wich also didn't work
In that reply you also said that the root folder is different between devices so, if I determine the path to my root folder, where exactly in the script do I have to put it? (Again I'm a newbie)
Click to expand...
Click to collapse
For my phone the Root folder's path is "/" so I'll put 2 arrows where the path to root is in the command:
" su -c mount -o rw,remount /proc --> / <-- "
So imagine your root path is /root
The command would look like this: " su -c mount -o rw,remount /proc /root " (without "" of course)
If you still can't find the path to your root folder, try searching on the internet "root folder for xxxxx phone"
Hope it helps
gaferreira13 said:
For my phone the Root folder's path is "/" so I'll put 2 arrows where the path to root is in the command:
" su -c mount -o rw,remount /proc --> / <-- "
So imagine your root path is /root
The command would look like this: " su -c mount -o rw,remount /proc /root " (without "" of course)
If you still can't find the path to your root folder, try searching on the internet "root folder for xxxxx phone"
Hope it helps
Click to expand...
Click to collapse
Turns out my phone's root folder is also / , and I'm still getting the same error (mount: '/' not in /proc/mounts)
Maybe its because I have Nougat :/
EDIT: So I think I managed to kinda work around that, I change the command to " su -c mount -o rw,remount / " and it ended up making the pen folder and no errors came out. So I then proceeded to open Paragon, disabled FS access rights, ensured that SELinux was permissive (it is) and change the mount point to the /pen folder, I finally proceeded to manually mount the thing BUT even tough that in my notifications says that I mounted it, on the app it still says that my Flash Drive is still not mounted (even tough it detects it and know that it is an NTFS file system). Basically whenever I try to mount my Flash Drive it wont work even tough the app detects it.
Arcane35 said:
Turns out my phone's root folder is also / , and I'm still getting the same error (mount: '/' not in /proc/mounts)
Maybe its because I have Nougat :/
Click to expand...
Click to collapse
Ooooh. Remember the topic is called "Full USB OTG on Media Players in Marshmallow"
I can't help you then, sorry. The only thing I can tell you is to open the /proc/mounts file as text on the top there should be a command that tells android to mount the root folder as rootfs I believe.
Maybe that could help.
Arcane35 said:
EDIT: So I think I managed to kinda work around that, I change the command to " su -c mount -o rw,remount / " and it ended up making the pen folder and no errors came out. So I then proceeded to open Paragon, disabled FS access rights, ensured that SELinux was permissive (it is) and change the mount point to the /pen folder, I finally proceeded to manually mount the thing BUT even tough that in my notifications says that I mounted it, on the app it still says that my Flash Drive is still not mounted (even tough it detects it and know that it is an NTFS file system). Basically whenever I try to mount my Flash Drive it wont work even tough the app detects it.
Click to expand...
Click to collapse
Try to open the /pen folder, try to see in the properties of /pen if the permissions are set to 777.
gaferreira13 said:
Try to open the /pen folder, try to see in the properties of /pen if the permissions are set to 777.
Click to expand...
Click to collapse
It is set as 0777, so yes (if the 0 is not supposed to be there)
Arcane35 said:
It is set as 0777, so yes (if the 0 is not supposed to be there)
Click to expand...
Click to collapse
Hmm... If you can open the folder fine and maybe create a file in there or something then I can't help you any further. The paragon app doesn't let you do much regarding troubleshooting.
Try using the methods that other people did like using Foldermount or something like that.