I just rooted my Moto G 2014 XT1064 running 5.0.1.
I used this article to do the root process: http://maktechblog.com/how-to-unlock-the-bootloader-and-root-the-motorola-moto-g-2nd-gen/#Root Which evolved unlocking the bootloader (which caused data to be erased, of course), installing TWRP, then copying SuperSU.zip over adb, then going back to TWRP recovery and installing SuperSU through TWRP.
Since then, /sdcard seems to be acting like its mounted as read only. I cannot seem to get anything written to it. I've tried to adb push files to /sdcard, but I keep getting the same "Permission denied" error. Taking screenshots don't work either, I get a "Couldn't capture screenshot" error. And I've also noticed the Twitter app is unable to display profile pictures nor pictures inside of tweets.
I've tried numerous things, but I'm stumped.
I've tried to see if its mounted as read only. Via adb shell, and su to get root, and mount to view the mounted file systems. Everything dealing with /sdcard, /storage/emulated/legacy, and /data/media are all mounted as rw (Read & Write, of course).
Remounting them doesn't produce any errors, but has no effect.
The file system for /sdcard seems to be just fine, as I can adb shell in, and use ls /sdcard/, from either regular shell or root. And via TWRP, it was able to successfully save a recovery.log to the /sdcard/ file system, indicating nothing should be preventing things from being written to the file system.
I am also unable to copy files to it via Windows, it tells me "Cannot copy [file name] ... The device has either stopped responding or has been disconnected", and OS X still doesn't seem to recognize it at all despite installing drivers from Motorola, which has happened before I rooted it.
What I found particularly weird is that I can download and install apps still. I installed a root checker app just after rooting it, and it worked, and I wanted to screenshot it, and then I noticed the issues happening.
And I've even tried a free app from Google Play which uses SuperUser permissions and attempts to fix the sdcard file system and make it mount right. Still, I am unable to write anything to it.
I've also tried to see if restarting adbd as root via the 'adb root' command would work, only to be disappointed because it doesn't work on production phones, despite my phone already being rooted.
I'm pretty new to android in general, including rooting, but I've definitely gotten a good feel for how it works, when I installed 5.0.1 onto it a few days ago (It came with 4.4.4 and didn't have an OTA update yet). But now I'm really confused about why this happened after I rooted, and after a bunch of googling to find nothing helpful, I have to ask here.
Edit: Just to be clear, Settings also reports I have 2.4 GB available space, and the file I am trying to copy over is far less than that.