Right, I've got a CIFS network share mounted using the following command:
su --mount-master -c busybox mount -o username=USER,password=PASSWORD,rw,file_mode=0777,dir_mode=0777,sec=ntlm,context=ubject_r:rootfs:s0 -t cifs //10.0.1.1/SHARE /data/media/0/SHARE
It mounts fine and as root I can write to it. However, when attempting to write to this location using an app (nzbget in this case) it gets a permission denied. The only thing I can figure is that the contexts may not be correct.
I've been scouring the internet for hours for an answer with no luck. Anyone have any ideas, or at least able to point me in the right direction?
gumbi2400 said:
It mounts fine and as root I can write to it. However, when attempting to write to this location using an app (nzbget in this case) it gets a permission denied. The only thing I can figure is that the contexts may not be correct.
Click to expand...
Click to collapse
Did you manage to solve this problem?
Related
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
fKngFtd said:
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
Click to expand...
Click to collapse
...it's a lowercase d in dev.
mount -o rw,remount /dev/block/mtdblock3 /system
n2imagination said:
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
Click to expand...
Click to collapse
I had the same problem. From what I could tell, I had the wrong ADB driver somehow. So I downloaded the drivers from the HTC website and went to device manager (Win7) and updated the driver software which fixed the problem. But I think i just lucked out when i stumbled onto that, I feel a blind retard with epilepsy trying to draw a circle on an etch-a-sketch when I'm doing things like rooting. But, it couldn't hurt to try it.
fKngFtd said:
su
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
Click to expand...
Click to collapse
adb install -l whatever.apk (from tools dir in sdk)
`mods said:
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
Click to expand...
Click to collapse
Did you ever get this fixed? I have the same problem!
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
LexusBrian400 said:
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
Click to expand...
Click to collapse
I think the proper permissions were not set for this ROM. Hopefully jcase can modify the file and re-upload the ROM =)
at least that's what I've gathered... someone PLEASE correct me if I'm wrong
edit: I looked at the script file and it seems like rw permissions are set properly???
jcase - any insight?
I personally get a bunch of "Out of memory" errors when trying to follow the recovery walk-through.
post baleeted
Ok.... I have googled them all and done a search on this website and have found nothing that is similar to my situation. I hate when people ask questions that are found in other forums and would not want to do the same... but I don't feel my situation is in the realm of that.
I followed all the basic ways of rooting and none worked for me. I did the Visionary (ver 14) root and root.zip (/root to sdcard), etc.... didn't work.
Finally Id/l Visionary for temp root.... and I followed http://forum.xda-developers.com/showthread.php?t=858996.
I got S=OFF, but had to 'sync' in terminal 5 or 6 times to be able to get su to work.
I finally get su to work (# instead of $ in terminal) and all the programs that require root to work do as they are supposed to. The main issue I have, is that without running visionary (with R/W access), I cannot delete files without it warning that I have read only access.
I thought if I had root access, I wouldn't need to set up Write access.
Once I run visionary, and delete *.apk files that came with my phone, they do stay away perm.
I just want to know if there is a way to keep the R/W access without visionary since I know I am in root.....
Root access is a separate entity from S-off, and that a separate entity from /system partition read/write mounting. That partition is read/only at boot. You can make it writable with adb, with Root Explorer, or with a linux mount command.
HTC Glacier running CM7 #33
root explorer has a button to push to mount r/w, or if you have adb setup you can plug in your phohne and type
adb remount
and you'll be r/w
or you can use terminal emulator and type
su
mount-o,remount -rw /dev/block/mmcblk0p25 /system
exit
and you'll be r/w
option94 said:
...
su
mount-o,remount -rw /dev/block/mmcblk0p25 /system
exit
and you'll be r/w
Click to expand...
Click to collapse
I see two typos in the command. There should be a space between mount and -o, and no comma between the -o and remount. Thus:
Code:
# mount -o remount -rw /dev/block/mmcblk0p25 /system
Of course, "adb remount" from a nearby PC is so much easier.
Thanks. I just woke up when i started typing that.
and the , will work with no space. Both methods are fine.
Thanks guys!
On another note, do either one of you know if you can mount the phones system folder as a drive on Vista like you would be able to do with the SD Card?
Im not talking with adb shell... More like using Windows Explorer
Nope. Only the "external" SD card can be mounted via USB, sorry.
This might be what your looking for.
adb commander
option94 said:
This might be what your looking for.
adb commander
Click to expand...
Click to collapse
That is close enough. Thanks option!
I'm having an issue with wi-fi. I'm running Andromadus Audacity 2. Yesterday I ran into an issue where my phone was randomly rebooting. I decided to reflash the rom and when I did so I could no longer connect to Wi-Fi. I can turn Wi-Fi on but it will immediately turn back off. In settings it will only say turning wi-fi on and hang up there.
I don't think that the issue is the router since my wife's G2 and other devices we have in the house still work fine on wi-fi.
Also it's not the rom because I have superwiped and reinstalled, then tried installing cm7, and ilwt. The issue persists on each rom. I have superwiped each time before installing.
I am really at a loss for what to do, I didn't change any settings on the phone and regardless, I don't know what I could have changed that would have carried over through flashing a new rom. I would appreciate any ideas on what to do.
ETA - I have changed the radio and the kernel and still no luck.
Check
Sent from my HTC Vision using XDA
Sorry accidental send, check the /etc/wifi/wpa*.conf permissions and ownership. This happened to me when that file was off.
Sent from my HTC Vision using XDA
A_Elizondo said:
Sorry accidental send, check the /etc/wifi/wpa*.conf permissions and ownership. This happened to me when that file was off.
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
When you say off do you mean it was absent?
When I got to /etc/wifi/ there is a file named wpa_supplicant.conf, it is the only file in the folder
the text file says:
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
mbrentrowe said:
When you say off do you mean it was absent?
When I got to /etc/wifi/ there is a file named wpa_supplicant.conf, it is the only file in the folder
the text file says:
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
Click to expand...
Click to collapse
Sorry my English is not as great as I wished it would be, this is what happens when I try to use "slang". When I say off I mean not correct. That is the correct file "wpa_supplicant.conf"
/etc/wifi/wpa_supplicant.conf --> needs rw-r--r--
/system/bin/wpa_supplicant --> needs rwxr-xr-x
I just checked my files and they are both owned by root and all works well so I guess its not an issue that wifi does not own them.
A_Elizondo said:
Sorry my English is not as great as I wished it would be, this is what happens when I try to use "slang". When I say off I mean not correct. That is the correct file "wpa_supplicant.conf"
/etc/wifi/wpa_supplicant.conf --> needs rw-r--r--
/system/bin/wpa_supplicant --> needs rwxr-xr-x
I just checked my files and they are both owned by root and all works well so I guess its not an issue that wifi does not own them.
Click to expand...
Click to collapse
Sorry I just misunderstood.
I checked both files and they had the same permissions that you wrote out.
mbrentrowe said:
Sorry I just misunderstood.
I checked both files and they had the same permissions that you wrote out.
Click to expand...
Click to collapse
Not sure if this helps but this is what's under my /etc/wifi/wpa_supplicant.conf file
update_config=1
ctrl_interface=eth0
eapol_version=1
ap_scan=1
fast_reauth=1
Notice my ctrl_interface=eth0 (thats a zero) I'd test that out see if it fixes it, if not then I'd download another rom and extract both /etc/wifi/wpa_supplicant.conf and /system/bin/wpa_supplicant files from it and replace yours. Again verify permissions are correct.
A_Elizondo said:
Not sure if this helps but this is what's under my /etc/wifi/wpa_supplicant.conf file
update_config=1
ctrl_interface=eth0
eapol_version=1
ap_scan=1
fast_reauth=1
Notice my ctrl_interface=eth0 (thats a zero) I'd test that out see if it fixes it, if not then I'd download another rom and extract both /etc/wifi/wpa_supplicant.conf and /system/bin/wpa_supplicant files from it and replace yours. Again verify permissions are correct.
Click to expand...
Click to collapse
Hey I'm on lunch now, in that file it says for ctrl_interface=wlan0. I am using es file explorer, it won't let me change it there but I think I read somewhere I can create a text file saying what I want it to and place it in the folder. Not sure if that will work.
As for the other roms, wifi doesn't work on any rom that I use.
mbrentrowe said:
Hey I'm on lunch now, in that file it says for ctrl_interface=wlan0. I am using es file explorer, it won't let me change it there but I think I read somewhere I can create a text file saying what I want it to and place it in the folder. Not sure if that will work.
As for the other roms, wifi doesn't work on any rom that I use.
Click to expand...
Click to collapse
You can replace the file using a terminal emulator here are the steps
Open terminal emulator and log in as super user by typing the following
su
Make the System Partition have read/write access by typing the following
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Now you can modify the file using es file explorer
When complete make the system partition read only by doing the following
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
You can also copy and replace the file using adb, not sure how familiar you are with that but the above should work.
A_Elizondo said:
You can replace the file using a terminal emulator here are the steps
Open terminal emulator and log in as super user by typing the following
su
Make the System Partition have read/write access by typing the following
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Now you can modify the file using es file explorer
When complete make the system partition read only by doing the following
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
You can also copy and replace the file using adb, not sure how familiar you are with that but the above should work.
Click to expand...
Click to collapse
Hmmm, I went into terminal emulator and did just as you said. This is what it says after I pasted in what you wrote to give me read/write access:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
After I did that it still won't let me change that file.
Sorry you are correct that command only works in adb do this instead of the above command
mount -o remount,rw /system
then when you are done do this instead of the other read only command
mount -o remount,r /system
A_Elizondo said:
Sorry you are correct that command only works in adb do this instead of the above command
mount -o remount,rw /system
then when you are done do this instead of the other read only command
mount -o remount,r /system
Click to expand...
Click to collapse
Thanks I will try it, but I'm becoming more convinced this is a hardware issue.
I was on the phone today and the phone froze and I had to pull the battery. When I restarted the phone Wi-Fi was working for the first time in a week. While it was working I checked that file and it said the same exact thing. The phone then froze again (I think it was my fault because in the excitement of having Wi-Fi again I tried to update all of my apps and other things I can't do on the crappy 2g data I have at home) when I turned it back on Wi-Fi was no longer working.
So now I'm thinking that this has to be hardware. I will give your method a try.
Yea I think you are correct especially since you tried different roms. If you have warranty just unroot it and return it else keep posting here about the status and a will find a work around eventually
Sent from my HTC Vision using XDA
Well I finally switched back to ilwt and my wifi isn't working all of the time but it has worked for a few hours each day since I flashed it. Whereas on andromadus it didn't work at all for two months. Still haven't figured out what happened but at least I get to keep my G2. Although I'll probably move on the first time they put the note on sale later this year. Thanks aeliizondo for trying to help me!
Sent from my HTC Vision using XDA
Hello fellow xda'ers,
A few weeks I am experiencing a problem with my moto x style. The problem is that i don't have access anymore to my system folder. I have full root access, I can use rooted apps, but i can't switch my file system to r/w. Also when I boot into recovery I can flash roms etc, they are fully working, but once again, no system access. Also when I try to mount the system folder in recovery it seems it won't stick. Also when I use root explorer it says it switched to r/w but in fact it is r/o..
Can someone please hint me out what I could do to fix this problem?
Thanks in advance,
Bump
Have you tried something like this in terminal as root, or via ADB root?
Code:
mount -o rw,remount,rw /system
Then for r/o...
Code:
mount -o ro,remount,ro /system
quakeaz said:
Have you tried something like this in terminal as root, or via ADB root?
Then for r/o...
Click to expand...
Click to collapse
Thanks for your reply. But i still can't get system access.
bartjeh1991 said:
Thanks for your reply. But i still can't get system access.
Click to expand...
Click to collapse
Did you receive an error running the command? You are root, correct? Possibly just use:
Code:
mount -o remount,rw /system
Then run...
Code:
mount | grep system
Mine is read-only, but this should tell you if yours is rw or not.
Code:
u0 a114 clark:/ mount | grep system
/dev/block/bootdevice/by-name/system /system ext4 [B]ro[/B],seclabel,relatime,data=ordered 0 0
quakeaz said:
Did you receive an error running the command? You are root, correct? Possibly just use:
Then run...
Mine is read-only, but this should tell you if yours is rw or not.
Click to expand...
Click to collapse
I get this message everytime i run the commands you give me.
I've rooted my M9P with SuperSU, and I think that I've correctly decrypted the data partition. (i followed this guide https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986/page2 )
I'm trying to move a GPS Spoofing app to system, but the system folder is R/O, and I've tried several different apps and commands to make it R/W, but nothing seems to work. I'm also unable to change permissions in data folder when I tested that. I've google'd myself to death and exhausted all solutions now, but to no avail. I cannot move apps to the system folder. The error I get from the "/system/app mover" app is
Could not remount /system
Click to expand...
Click to collapse
Using the app "Mount /system RO/RW" I get
Your device might not be rooted or is not compatible
Click to expand...
Click to collapse
Trying to change permissions with Root Browser gives me:
Changing permissions was not successful. Please note that some file systems do not allow permission changes.
Click to expand...
Click to collapse
I've also tried "mount -o rw,remount /system" with no luck. Any help would be greatly appreciated!