Database Info

Trouble mounting /system through ADB

I'm having trouble mounting the /system directory on my Captivate. When I try an "adb remount" I get
Code:
remount failed: no such file or directory
When I try to push my framework, I get
Code:
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': Read-only file system
I've tried
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
and this and get "Permission Denied."
It is confusing, because before when I had this problem, the fix I linked to worked for me. Now I can't get it. Also, I can pull from the /system just fine, but can't push.
I'm definitely rooted, and have Busybox installed.
Thanks in advance!

Bump?
I have read throug tons of guides, but nothing seems to be working. I went back to stock and flashed my rom again, but no luck. Any ideas would be appreciated.

Did you type su first? It acts as if you're not root. /system is readable by everyone so you can pull, but it's only writeable by root so you can't push to it unless you're logged in as root.
I've only used adb once to root my phone so I'm not entirely sure how it should be typed in, but in a terminal you'd just type su and hit enter, then type in your remount command.
Also, for what it's worth, you can shorten it to just: mount -o rw,remount /system
Your method is fine, it's just not necessary to type it all out.

fubaya said:
Did you type su first? It acts as if you're not root. /system is readable by everyone so you can pull, but it's only writeable by root so you can't push to it unless you're logged in as root.
I've only used adb once to root my phone so I'm not entirely sure how it should be typed in, but in a terminal you'd just type su and hit enter, then type in your remount command.
Also, for what it's worth, you can shorten it to just: mount -o rw,remount /system
Your method is fine, it's just not necessary to type it all out.
Click to expand...
Click to collapse
Thanks for the reply.
If I type su in the terminal, this is what I get.
Code:
C:\Android\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file. C:\Android\tools>
However, when in shell, I can get it to recognize su, but it still doesn't like to mount.
Code:
C:\Android\tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#

Fix_permissions mistery

Ok, so here is what puzzles me:
I have a MT3G, SuperOneClick rooted, with RA 1.7.0, busybox 1.18.4, all apps requiring superuser permissions are working flawlessly (Titanium, SetCPU, Root Explorer, Droid Wall, etc). Fix_permissions works with RA (other/fix uid mismatches) and ROM Manager, but when I open the emulator and type $su #fix_permissions, it gives me
bash: fix_permissions: command not found
In adb shell fix_permissions, permission is denied. All useful ideas how to solve this are much appreciated, thanks...

Anyone?
Sent through XDA App

Ok, I don't want to open a new topic, but really need some advice here! I just used Root Check in advanced mode, before it ran it asked for and received superuser permissions, then the detailed results were:
Congratulations! You have root access!
Alternate su bin location:
/sbin/su: Permission denied
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Click to expand...
Click to collapse
Seriously, guys, please help, I dont have a clue whether I have a permanent root or not. I forgot to mention I'm using the T-Mobile OTA Froyo 2.2.1 FRG83D. I've rooted this same ROM once, 5-6 months ago, when it was pushed out, I had no problems, fix_permissions were working. Then I nandroid backed it up, so I can restore it if I don't like the other ROMs I used later (which were Ginger Yoshi RC7 -a great ROM, but the launcher was constantly restarting, and then back to Super D - most stable one, but lots of the good apps are not for 1.6 anymore). However, when I tried to restore Froyo, it didnt work, so I had to start over, using the following steps to get the OTA and root it. Please, let me know if I missed something or did it wrong:
1. I flashed sappimg.nbh with hboot to get to unrooted Cupcake
2. Flashed DRC92 and DMD64 Donut updates with stock recovery <3e>
3. Got the OTA Froyo from T-Mobile (*#*#checkin*#*#)
4. Used SuperOneClick to root, then restarted the phone
5. Using Droid Explorer, I installed a terminal emulator, then I uninstalled Superuser (have read in several threads people saying they had problems with it when it comes with SuperOneClick), using
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Superuser.apk
# pm uninstall com.noshufou.android.su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
$ exit
and reinstalled it from the market.
6. Installed the latest busybox with Busybox Installer.
7. Pasted flash_image and recovery.img (Amon RA 1.7.0) to the sdcard, then installed recovery:
$ su
# mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
# rm /system/etc/install-recovery.sh
# cd sdcard
# mount -o remount,exec /dev/block//vold/179:1 /sdcard
# ./flash_image recovery /sdcard/recovery.img
# exit
$ exit
8. And finally I started removing the unnecessary system apps (Amazon, MyFaves, etc) with the emulator, using the same method I did to remove Superuser in step 5
Click to expand...
Click to collapse
Now, as I mentioned before, I cannot run fix_permissions through the emulator, but it runs through ROM Manager and RA (fix package uid mismatches).
Why is that? Is it the ROM, which causes the problem?
I'm clueless, please help!

[Solution]SAMSUNG GIO S5660: adb remount failed

Hi guys,
If any one getting error while remounting system partition in rw mode using adb, please follow these steps :
C:\Android\android-sdk-windows\tools> adb remount
remount failed: No such file or directory
SOLUTION:
Connect to your device usb adb: [FOR ROOTED DEVICES ONLY]
C:\Android\android-sdk-windows\tools> adb shell
$su
#mount -o remount,rw /dev/stl12 /system
(do your desired work like copy some files on system/media folder , then remount the system partition in ro mode again)
# cd /
#mount -o remount,ro /dev/stl12 /system
#exit
$exit
Thats all
FYI if you want to know the dev partitions mounted on your device :
C:\Android\android-sdk-windows\tools> adb shell
$ su
# mount
cheers

Did you map the other partitions by any chance? I'd like to be able to make a full backup to eventually be flashed back with Heimdall or ODIN. I already have a system.rfs (stock + root) that could be made in a tar image.
I've see tutorials for other Samsung phones but these need to be adapted to our exact setup. I haven't found anything generic enough to know how to go about mapping things.
It might also help those who flashed GT-S5660 ROMs on the Bell Canada GT-S5660M, as the screen brightness issues sound very much like kernel issues to me...
I can't quite tell what the difference is between stl and bml either. (I'll probably try dd'ing the different blocks, except stl5, and peek around with a hex editor...)
Goodbye,
Darkshado

rm failed for /system/app/nfc.app, Read-only file system

I am locked out of my Nexus S due to a Force Close loop with Nfc.app caused by installing a non-working fix for the Google Wallet app on the T-Mobile (thanks Google!). I therefore can't run root explorer etc.
I am trying to remove Nfc.app using but get these errors:
Code:
$ rm /system/app/nfc.app
rm failed for /system/app/nfc.app, Read-only file system
$ remount
remount: permission denied
# mount -w -o remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Any way I can get past the read-only error, and the failure of remount?

Boot in recovery and run adb shell. That'll give you root permissions and access to the file system.
Greetz

That gives me:
error: device not found
I am using stock recovery (because it was a soft ClockworkMod recovery and I can't get back into ROM manager to reflash it).

Flash recovery with fastboot.

Thanks but I get:
$ fastboot flash recovery clockwork.img
fastboot: permission denied

Doing it wrong. Read the guides to learn how to set up and use fastboot.

I tried but that's all I came up with. If you could type the line of command I need, I'd really appreciate it, and give thanks

frutelaken said:
Boot in recovery and run adb shell. That'll give you root permissions and access to the file system.
Greetz
Click to expand...
Click to collapse
adb shell only inherently grants root permissions on an insecure boot image. If he's stock, rooted he'll get the standard user prompt and have to request elevated privileges.
CJSnet said:
I am locked out of my Nexus S due to a Force Close loop with Nfc.app caused by installing a non-working fix for the Google Wallet app on the T-Mobile (thanks Google!). I therefore can't run root explorer etc.
I am trying to remove Nfc.app using but get these errors:
Code:
$ rm /system/app/nfc.app
rm failed for /system/app/nfc.app, Read-only file system
$ remount
remount: permission denied
# mount -w -o remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Any way I can get past the read-only error, and the failure of remount?
Click to expand...
Click to collapse
No offense, but the Thanks Google is a bit snarky - they didn't provide for T-Mobile users and never distributed the APK to flash.
For something helpful though - go ahead and boot up normally. Grab a shell, su and remount /system manually
Code:
mount -o remount,rw /dev/mtdblock3 /system
You have to tell mount which partition to mount, it won't accept just a mount point.

Thanks, but how do I request elevated privileges? E.g. I get this:
$ mount -o remount,rw /dev/mtdblock3 /system
mount: Operation not permitted
And this:
$ fastboot OEM unlock
fastboot: permission denied
Seems I can't do anything from the $ prompt.
PS: My snark at Google was for releasing a fragmented product that was not available to T-Mobile in the first place, hence these problems with the cracked version.

CJSnet said:
Thanks, but how do I request elevated privileges? E.g. I get this:
$ mount -o remount,rw /dev/mtdblock3 /system
mount: Operation not permitted
And this:
$ fastboot OEM unlock
fastboot: permission denied
Seems I can't do anything from the $ prompt.
PS: My snark at Google was for releasing a fragmented product that was not available to T-Mobile in the first place, hence these problems with the cracked version.
Click to expand...
Click to collapse
Are you rooted - if so then su prior to issuing the mount command?
If not, Is the bootloader current unlocked? You don't use fastboot from the device shell. Fastboot is a command line utility used from your local computer to operate on the device when it is in the boot loader.

Bootloader was already unlocked.
I solved it:
Rebooted into fastboot mode by holding volume up and power
On computer navigated to folder containing fastboot and put the clockwork.img in there
Typed fastboot flash recovery clockwork.img
I now have CWM recovery back, thanks.

[Q] Mounting /system read-write fails under adb shell, CM11

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