Hello,
My S4 is rooted, es3 cannot delete, move or change permission.
With a terminal under su, chmod or rm - Rf gives Access Denied.
The directory is a clockworkmod created by backup, named backup.
Suggestions ?
Hi there,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
[email protected] said:
Hello,
My S4 is rooted, es3 cannot delete, move or change permission.
With a terminal under su, chmod or rm - Rf gives Access Denied.
The directory is a clockworkmod created by backup, named backup.
Suggestions ?
Click to expand...
Click to collapse
I am on cm12 nightly.
On modern versions of CWM, you should always use the delete function within the backup and restore menu to remove nandroid backups. This is because CWM by default automatically does incremental backups whenever you make a nandroid. Manually deleting nandroid backups when CWM is set up for incremental backups is a really bad idea, as it screws up every single nandroid backup you have, including the master backup. Thus CWM protects the nandroid backup directory.
So, to recap, enter CWM, go to "backup and restore", then delete your nandroid backup from there. After that, go to "free unused backup data" and select it to have CWM restore access to the now freed space.
Thanks for the explanation.
Rom Manager is not installed at present. I am using TRWP manager instead.
I installed CWM Backup manager from Guimberg .
I could pull the backup to a new folder, but delete the original clockworkmod folder did not work.
Would I need to have a cwm recovery installed in order to delete cwm backups ?
You didn't mention you had replaced CWM with TWRP. So, before putting CWM back on to the S4 and using it to wipe away the directory, did you change permissions in ES File Explorer or execute a chmod 777 command in Terminal? Since permissions is the issue here you have to change them.
Being in su I used chmod 777 and rm -rf as well as trying with es3 to change permission but always got "access denied".
I also try with twrp recovery file manager.
I have busy box and sudo installed.
The directory is at /mnt/shell/emulated/
In a nutshell I cannot change permission.
Replace TWRP with CWM, delete the nandroid backups and free the space. Then restore TWRP and you should be good to go. If that doesn't work, your only other alternative is to reset.
I replaced and try, but the only change I could do is the rename of the bu and a zip. Delete was denied.
It is a minor isue since the file is only 255MB. I guess that their are some bits corrupted somewhere and therefore as you suggested a format will fix it.
I will wait for a better reason to do that and live with the bu files happily.
Thanks for your advises.
Didn't find the thanks button. I didn't not understood near the quote as the location for doing it?
Thanks button is on the left, at the bottom of each post under the user information.
Done
Related
When i download and install an App from the Android Market where the Apk installation file is temporary placed? Which path?
tnx in advance
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
sidvizioso said:
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
Click to expand...
Click to collapse
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
So which is the temp path of the downloaded apk from market?
i want to grab them...
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
of course you can.
you just have to copy them to your sdcard or pc an install them again, with «adb install something.apk» or «Astro File Manager» (or a similar file managerapp)
a hard reset will delete everything on «/data»
If you have root copy the contents of both folders to your SD card.
mkdir /sdcard/apps
cp /data/app/* /sdcard/apps
cp /data/app-private/* /sdcard/apps
Then after you wipe (I've never heard anyone call it a 'hard reset' before) you can use an app like Astore or ApkInstaller to reinstall them.
If you don't have root then not only will you not be able to read app-private, but your ROM wont have busybox so you wont be able to bash in those commands. In that case use an app like Astro or AppManager to copy non-private apks to the sdcard, but for private apps you'll have to redownload them (without being charged of course.)
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
Only if they're non-private (reside in /app, private being /app-private).
He's probably coming from WinMo. We called a factory reset/wipe a hard reset.
mopodo said:
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Click to expand...
Click to collapse
Slightly off topic lol But i see you said Private does that mean you could manually back up Private apps you buy off market by just copying them /w root access?
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
You could try an app manager and back 'em up from there.
Just try the following command.
busybox cp /data/app/* /sdcard/<your backup loc>
askwhy said:
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
Click to expand...
Click to collapse
Well in windows
'adb pull' is used if that helps
Ok got root, but cant delete bloatware.
tried to delete amazon with rootexplorer and said
it is a read-only file and cannot delete.
So if anyone can please tell me or show how to delete bloatware it would be much appreciated
saldebot said:
Ok got root, but cant delete bloatware.
tried to delete amazon with rootexplorer and said
it is a read-only file and cannot delete.
So if anyone can please tell me or show how to delete bloatware it would be much appreciated
Click to expand...
Click to collapse
WRONG FORUM, next time please post in general
Have you tried using titanium backup (market)? Open titanium backup, click on "problems?" download busybox, re-open titanium backup (it closes automatically after installing busybox), click on backup/restore, click on amazon (or whatever you want to uninstall) hit uninstall.
NOTE: in titanium backup you might have to go to preferences and enable "chuck norris mode" (uninstaller settings) for some uninstalls to work. (Might be pro feature only)
NOTE: I'd use titanium backup to make a complete backup fist before uninstalling any apps. Might be needed for OTA updates.
At the top of the app, there is an option to mount the folder as R/W
it is mounted as R/O
I made that mistake the first time I used root explorer.
UberMario said:
At the top of the app, there is an option to mount the folder as R/W
it is mounted as R/O
I made that mistake the first time I used root explorer.
Click to expand...
Click to collapse
That didn't work for me, no matter how many times I clicked on the R/W remount icon. It does work after I run the following commands in abd though, weird.
mount -o remount, rw /system
i hit the RW buttom on the root explorer it deleted fine.
Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.
cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer
cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again
I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.
cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.
So, before I do a firmware update (In this case 4.2.2 to 4.3 OTA) I do a Titanium backup and a TWRP backup and copy both sets of backup files to my PC; it obviously makes no sense to only have backups on the device you are backing up. I upgraded to TWRP 2.6.0.0, did a full backup, and as usual I went to copy my backup files over to my Windows 7 computer using Windows Explorer and I can only get a couple of the files to move over. No warning, no error, no nuttin. This has always worked before......Did something change, and if so, how do I fix it?
I see from another post that TWRP changed the permissions of the backup files in the latest version of the program, and in my case the location as well. The workaround is to a) change the permissions on all those backup files, which I could see the nightmare problems that could cause later on when doing a restore and/or the security issues or b) doing an adb pull.
SOLVED.
The adb pull did the trick. All files were transferred over to my PC.
I had several issues getting adb to work:
1) I had an old version of the SDK installed on my PC which was causing a devices not recognized problem or something similar.
2) I didn't notice the message about verifying the RSA on my phone, which once verified, fixed the phone "offline" problem.
3) The screen lock on my phone was coming on after its timeout and locking me out from seeing the phone.
reverted to twrp 2.5.0.0
Same problem here with Google Nexus i9250 / twrp 2.6.0.0 / win7 64bit. Tried to copy backup of (BOOT/SYSTEM/DATA) via MTP or ftp from Nexus to PC. Only the first two files (boot.emmc.win/-md5) were copied. After downgrading to twrp 2.5.0.0 everthing was fine.
I had the same problem. It is caused by strange suid permissions set by TWRP. Solved it using chmod 0664 /data/media/0/TWRP/... (as root)
I was not able to adb pull before changing the files' permissions.
More details here:
http://forum.xda-developers.com/showpost.php?p=44120545&postcount=14
(Google found that HTC One thread first, so I didn't search any further)
Type this in Terminal Emulator:
su
busybox chown - R 1023.1023 /data/media/*
That should solve all permissions problems.
I had no trouble at all by doing the following:
Access the sdcard from /data/media/0
Copy data.ext4.win and system.ext4.win to a temporary location.
(The "Set UID" and "Set GID" permissions were automatically removed. If not, you can change them from here.)
Copy the files to PC using MTP.
The remaining backup files from the TWRP directory can be copied normally.
Done
Note: You can instead just change the permissions on these two files inside the TWRP directory, but I did the temporary location copy just to be safe.
Mercado_Negro said:
Type this in Terminal Emulator:
su
busybox chown - R 1013.1023 /data/media/*
That should solve all permissions problems.
Click to expand...
Click to collapse
coming up with chown: unknown user -
is that a space between 1023 and /data?
daryllh said:
coming up with chown: unknown user -
is that a space between 1023 and /data?
Click to expand...
Click to collapse
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
After I did this command, my pc can't detect the back up
handols said:
After I did this command, my pc can't detect the back up
Click to expand...
Click to collapse
Did you plug/unplug your device after running this command? There shouldn't be any problems. Furthermore, now you should be able to copy your TWRP and TiBu backups successfully to your computer. It's a pretty straight forward process.
Im on twrp 2.5.0.0 with Android 4.3. I cant copy the BACKUP folder directly to my PC with the default windows explorer because the backup isnt stored in /sdcard/TWRP. How can I fix this? I used to be able to do this without adb push/pull...
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Thanks for this. I'm able to backup TWRP folder to PC now :highfive:
Since my original post 3 months ago I updated all my programs to 4.3 friendly versions as each was released (superuser 1.0.2.1, Windows drivers, TWRP 2.6.3.0, etc.) and now I don't need to do adb pulls any more and I can just copy and paste files from my phone to my pc and all files are copied over without missing any of them. Now I see the updated programs are already starting to show up for Android 4.4; here we go again.
Now see 0 / legacy emulated
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
NightCrawler504 said:
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
Click to expand...
Click to collapse
What's the problem? That's a valid path.
Legacy emulated 0
Mercado_Negro said:
What's the problem? That's a valid path.
Click to expand...
Click to collapse
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
NightCrawler504 said:
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
Click to expand...
Click to collapse
No, it doesn't have anything to do with this command since it's just a way to set different permissions.
After doing a restore with CWM of 4.4.4 backup, I'm unable to save files to user storage. Owner is 0 root, GID is 1028 sdcard_r, permissions drwxrwx--x, same as on my N7 '13.
Drive can export a file to ./Downloads though. ?:| Other files can save to that folder.
Have tried with Nova Launcher backup (can save backup file to ./Download, but no other), ES File manager ("EACCES (Permission Denied)"), Total Commander file manager. Helium backup can't backup locally either.
Noticed yesterday that I couldn't delete folders or move files from folders (Alarms, Notifications, Pictures), so did it in Recovery with ADB shell. Think that's just another symptom.
Never encountered this before. Anyone ever see this, fixed this?
Oh, one note. During my 5.1.1 order, I did a fresh wiped boot of 4.4.4, set up accounts and basic apps, and did a CWM backup. Moved it off with adb (adb pull /sdcard/ ./sdcard/).
After flashing 4.4.4 completely, I used CWM and adb push to move the entire backed up /sdcard/ back to the device so I could do a restore (adb push /sdcard/ ./sdcard/). Restored in CWM.
Could this have been an issue? /sdcard/ created by adb ?
Solved. Did a CWM backup and was readying to pull that off, and checked on a hunch. After mounting /data/, I shelled in (adb shell) and checked permissions (ls -ald /sdcard/0/ ) and lo and behold -- many (not all) of the folders were owned by root:root, not media_rw:media_rw. /sdcard/0/Download/ was not.
Changed ownership of all under /sdcard/0 (chown -R media_rw:media:rw * ) rebooted, and can save in those folders again. Hopefully that didn't bork something else up.