Database Users

Problems with adb push

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

[Q] Some system maps

Hi Every body,
In quit new in Android.
I just finaly rooted en S-Off my Desire.
Now I want to copy a file in to a system map, but I cant safe in that map.
Is there a way that I can Chmod the right, so I can Copy too their.

Check the file system you're trying to copy to, it might well be mounted as read-only. If you have permanent root you should be able to remount it as read/write.

steviewevie said:
Check the file system you're trying to copy to, it might well be mounted as read-only. If you have permanent root you should be able to remount it as read/write.
Click to expand...
Click to collapse
I am permanent root, waht should i do to get the map Write.
Is their een special chmod tool.
I use ES file Explorer.

Redbaser said:
I am permanent root, waht should i do to get the map Write.
Is their een special chmod tool.
I use ES file Explorer.
Click to expand...
Click to collapse
You need to mount /system as read/write :
Code:
mount -o remount,rw /system
Make your changes, then when you're done :
Code:
mount -o remount,ro /system

steviewevie said:
You need to mount /system as read/write :
Code:
mount -o remount,rw /system
Make your changes, then when you're done :
Code:
mount -o remount,ro /system
Click to expand...
Click to collapse
From my Pc then it is:
Code:
adb shell
Code:
su
Code:
mount -o remount,rw /system/media/audio/notifications
Code:
exit
Code:
exit

Redbaser said:
Code:
mount -o remount,rw /system/media/audio/notifications
Click to expand...
Click to collapse
No, you need to remount the /system file system (/system/media/audio/notifications) is just a directory within that file system.
Then go into that directory and make any changes that you need to. Then remount it as read-only when you're done.

steviewevie said:
No, you need to remount the /system file system (/system/media/audio/notifications) is just a directory within that file system.
Then go into that directory and make any changes that you need to. Then remount it as read-only when you're done.
Click to expand...
Click to collapse
I did it whit my terminal emulator,
just you told.
I want to copy a file in that directory, it want work, premision denied
I typed
su
#mount -o remount, rw /system
Then I tried to copy

Redbaser said:
I did it whit my terminal emulator,
just you told.
I want to copy a file in that directory, it want work, premision denied
I typed
su
#mount -o remount, rw /system
Then I tried to copy
Click to expand...
Click to collapse
Check your steps again. I just created a new file in that directory fine.
Did the su work ?
You're not typing that "#" symbol, are you ? That's the command prompt when you're root.

steviewevie said:
Check your steps again. I just created a new file in that directory fine.
Did the su work ?
You're not typing that "#" symbol, are you ? That's the command prompt when you're root.
Click to expand...
Click to collapse
I treid again, I type su, then $ change in #
I type mount -o remount, rw /system (puch enter)
I open ES file Explorer, the directory is still no Rightable only Read.
I

Redbaser said:
I treid again, I type su, then $ change in #
I type mount -o remount, rw /system (puch enter)
I open ES file Explorer, the directory is still no Rightable only Read.
Click to expand...
Click to collapse
The problem is ES File Explorer isn't running as the root user. So you can do a "chmod 777 /system/media/audio/notifications" then it will work.

steviewevie said:
The problem is ES File Explorer isn't running as the root user. So you can do a "chmod 777 /system/media/audio/notifications" then it will work.
Click to expand...
Click to collapse
Wich App do i need or how can i made the explorer as root user.

Redbaser said:
Wich App do i need or how can i made the explorer as root user.
Click to expand...
Click to collapse
Are you not comfortable doing it via the command line ? There is an "experimental" option within ES File Explorer to let it run as root, but I just tried it, and it doesn't work on the stock ROM.
I checked and it looks like one of the other main explorers, Astro, doesn't work as root either.
Maybe try the Root Explorer app (hmm, though I see you have to pay for it) ? Anyone else have recommendations ?

steviewevie said:
Are you not comfortable doing it via the command line ? There is an "experimental" option within ES File Explorer to let it run as root, but I just tried it, and it doesn't work on the stock ROM.
Click to expand...
Click to collapse
I so new whit android, I Realy dont now what are you mean, Sorry

Redbaser said:
I so new whit android, I Realy dont now what are you mean, Sorry
Click to expand...
Click to collapse
If you are willing to pay for the "Root Explorer" app, which you will find on the Android market, then that should do what you want (i.e. give you a file explorer app that will work as root).

How to remove the demo games?

I went to /system/app and found most applications, but the only thing that I really want to find are the demo games, and for some reason I can't find them! I even went to /data/app and found the apk packages there, I deleted them but the games are still installed.
Any ideas?

Are they in /cust?

if i have not remembered wrongly, the demo games r in /system/app/..
what specific game(s) do u want to remove? i can give u the location tonight after work (as i stored the paths in my home pc..)

FYI. Mine are all in /cust/pccw/hk/app.

simplistian said:
FYI. Mine are all in /cust/pccw/hk/app.
Click to expand...
Click to collapse
is it possible\safe to delete them?

if u meant those "Ironman", "Prince of Persia", etc., then its okay to delete them..
i did..

My phone didnt have any demo games and i found it weird couse in all the reviews i saw them in the menu screen...

my memory didnt fail me.. the 4 games that i removed were all in /system/app/
BubbleBash2.apk (Launcher: Bubble Bash 2)
IronMan2.apk (Launcher: Iron Man 2)
PrinceofPersiaZero.apk (Prince of Persia)
UNO.apk (Launcher: UNO)
btw, im with the hong kong B135 version..

@flipmodegr
yeah, it seems that ROM for Wind is cleaner..

nice to hear that its normal for the greek phones

yes, Wind Gr gives a stock android rom (not even hauwei has added anything) so its clean like water

Thanks everyone I found them in /cust/roadhound/au/app but for some reason I can't mount the location as R/W using Root Explorer.. my phone IS rooted.. I don't know why it does not let me mount it as R/W.. therefore I can't delete them!!
Any ideas on this?
Thanks

Tcm9669 said:
Thanks everyone I found them in /cust/roadhound/au/app but for some reason I can't mount the location as R/W using Root Explorer.. my phone IS rooted.. I don't know why it does not let me mount it as R/W.. therefore I can't delete them!!
Any ideas on this?
Thanks
Click to expand...
Click to collapse
Try using adb or you could try in terminal emulator:
Mount R/W
Code:
mount -o remount,rw /dev/block/mmcblk0p12 /system
Mount R/O
Code:
mount -o remount,ro /dev/block/mmcblk0p12 /system

I can mount /system as R/W.. I just cant mount that directory in R/W .. it just opens as R/O even if I mount /system as R/W

Tcm9669 said:
I can mount /system as R/W.. I just cant mount that directory in R/W .. it just opens as R/O even if I mount /system as R/W
Click to expand...
Click to collapse
Oops sorry. See Below.
Try using adb or you could try in terminal emulator:
Mount R/W
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /cust_backup
Mount R/O
Code:
mount -o remount,ro /dev/block/mmcblk0p1 /cust_backup
And the apps are in cust_backup/image/cust_data/roadhound/au/app. The /cust directory is just a link to the cust_backup direcctory. Which is why you cant mount it RW

Tried in Terminal Emulator, said
mount: Operation not permitted
Click to expand...
Click to collapse
then tried with sudo and said
sudo: permission denied
Click to expand...
Click to collapse

Tcm9669 said:
Tried in Terminal Emulator, said then tried with sudo and said
Click to expand...
Click to collapse
Root is su

Ahh, I tried
sudo <<command here>>
su worked! Thanks finally removed them ... WOHO!
Thank you very much mate.. oz oz oz, oi oi oi!

I want to remove those demos too, is it possible with stock non-rooted system?

No.. you need to root it. It's quite easy to do.

Upgrading to 4.2.2 Issue

I tried today to upgrade from 4.1.2 to 4.2.2 but it failed about 30% of the way through the upgrade and ended with the Droid on his back with a red x.
Its rooted but got stock recovery.
I did the same upgrade for my Nexus 4 to 4.2.2 from 4.2.1 and that upgraded fine.
What's causing the upgrade to fail?
Any help would be much appreciated.
Thanks
Jon
Sent from my Nexus 7 using XDA Premium HD app

look for the error message in /cache/recovery/recovery.log

If you comb thru the bigger threads on the 4.2.2 update....every imaginable problem and solutions are in there.
Sent from my cell phone telephone....

This is part of the log that shows the failure.
Any help would be much appreciated.
Thanks
Verifying current system...
failed to stat "/system/xbin/bttest": No such file or directory
file "/system/xbin/bttest" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
E:Error in /cache/da55f917feee.signed-nakasi-JDQ39-from-JZO54K.da55f917.zip
Sent from my Nexus 7 using XDA Premium HD app

OK jonchill I will try to help out.
But only because you inadvertently disclosed a new OTA download (JZO54K->JDQ39) for nakasi.
Here's the deal:
The OTA process performs checksums on hundreds of individual files (and even partitions e.g. boot partition) before it begins any work. 100% of checksums must pass before anything gets changed by the OTA.
It's a safety feature meant to protect people from applying the wrong files to their tablets/phones. More importantly, the reason that it is done is because the OTA does not contain "replacement" files - it only has small binary "patch" files which can be used only in conjunction with the original file to create the intended replacement file. This is how OTAs can be so much smaller than a full ROM - the files already present are "patched" to create their replacements.
But the bottom line is that if *you* removed or altered any single file which is a target of the OTA patching process, these pre-installation checks will fail. (Even worse, it stops immediately - it is possible that you have more than one file involved in this. Because of this stop-on-first-fail behavior, you don't know yet whether or not there are more to come.)
When I say *you* I mean you personally plus any root-using apps which you installed and ran on your tablet. Could have been an app.
OK, now for the good news. I downloaded the OTA - thanks for providing the file name - and looked at the installer script; that installer script for JZO54K-> JDQ39 is shown here on pastebin. The file which your OTA is complaining about is "bttest" - and as it turns out, this check occurs on line 1040 - it is the third from last file checked. The only thing which comes after that is a check of
/system/xbin/dexdump
and
the boot partition ( EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX )
Now I don't have any idea what might have caused "bttest" to disappear from your ROM. On the off-chance that "dexdump" got deleted too, attached is a zip of those two files from the JZO54K distro.
This is not a flashable zip - it's just the two files. It's your responsibility to get them into /system/xbin/
Note their ownership info:
Code:
-rwxr-xr-x 1 root 2000 5448 Oct 2 14:49 /system/xbin/bttest
-rwxr-xr-x 1 root 2000 59828 Oct 2 14:49 /system/xbin/dexdump
If you restore them to /system/xbin/ make sure you
Code:
chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
chmod 755 /system/xbin/bttest /system/xbin/dexdump
I verified their SHA1 checksums (note these are the 2nd string of digits in the failing assert_check).
2bb363a3f434d165d1167d915c2ba44967e22071 bttest
e5e4d35038ed3e32a15194275806d90e64e003c6 dexdump
good luck.

I've downloaded the files and tried transferring them across to XBIN but it fails saying the folder isn't writable, I've tried changing the permissions on the folder but it errors saying can't set permissions.
What am I doing wrong?
Thanks

The /system partition is typically mounted "ro" - Read Only.
Root-aware file browsers typically have a toggle in their (root-related) menu to remount /system in rw mode, but you can easily do it yourself from the command line. (using a terminal emulator or adb). You just need to be root to do this. (Or you can just do everything in the custom recovery, in which case the /system mount point will be in "rw" mode by default)
C:\foo> adb shell
$ su
# mount -o remount,rw /system
(copy files into place, do chmods , etc)
# mount -o remount,ro /system

Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks

jonchill said:
Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks
Click to expand...
Click to collapse
Well, that's odd. I'm not really sure why that is happening. You could fool around with the mount command a little bit or just avoid all this nonsense and do what you need via adb in the custom recovery.
If your bootloader is unlocked, but you don't want to *flash* a custom recovery (I see you said you have stock recovery), you can nevertheless temporarily *boot* one, and just that temporarily booted custom recovery as in:
- put device in bootloader mode
C:\fubar> fastboot boot name-of-custom-recovery-image.img
(wait until it is booted)
C:\fubar> adb shell
# mount /system
# cp /sdcard/wherever/bttest /system/xbin/bttest
# cp /sdcard/wherever/dexdump /system/xbin/bttest
# chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
# chmod 755 /system/xbin/bttest /system/xbin/dexdump
# sync
# umount /system
reboot
I don't know how you originally rooted, but generally the adb connection from either custom recovery (TWRP/CWM) needs an additional USB driver (yes, even though you "already have ADB working with the normal OS"). I suppose most lazy folks use either a toolkit or the XDA Universal Naked driver for this. (No support will be given by me on driver installs - I need to draw the line someplace.)
good luck

Tried booting to a temp custom recovery (TWRP) and followed your instructions but still getting the Read-Only file system. At this stage would it be better to take a backup and re-flash a full image?
C:\NRT\data>adb shell
~ # ←[6n
~ # ←[6nmount /system
mount /system
~ # ←[6ncp /sdcard/bttest /system/xbin/bttest
cp /sdcard/bttest /system/xbin/bttest
cp: can't create '/system/xbin/bttest': I/O error
~ # ←[6ncp /sdcard/dexdump /system/xbin/dexdump
cp /sdcard/dexdump /system/xbin/dexdump
cp: can't create '/system/xbin/dexdump': Read-only file system
Thanks

Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?

bftb0 said:
Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?
Click to expand...
Click to collapse
Thanks for all your help, as this is going to be quite a bit more complex than first thought I'm going to leave the above until I come back from holiday.
Thanks again.

You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.

GedBlake said:
You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.
Click to expand...
Click to collapse
Ged
The OTA was what I received automatically.
I've already got XPlore and have tried what you suggested but get Can't write to file /system/xbin/bttest can't move temp file to /system/xbin/bttest.
Thanks

System r/o

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.