Related
Ok so I have rooted my Hero and all is well. I've been trying to replace the sound files in system/media/audio/ui where the keyboard sounds are. I find that I cannot move a file into that folder, or apparently any of those folders. When I try to paste a copied or cut file using root explorer into the ui folder, the file just doesn't appear.
Why is this?
Switchbitch said:
Ok so I have rooted my Hero and all is well. I've been trying to replace the sound files in system/media/audio/ui where the keyboard sounds are. I find that I cannot move a file into that folder, or apparently any of those folders. When I try to paste a copied or cut file using root explorer into the ui folder, the file just doesn't appear.
Why is this?
Click to expand...
Click to collapse
have you tried with and without file extention?
Yes. Root explorer just won't let me move any files around in the phone memory. Do I have to do it using adb?
I have a feeling its Root Explorer not working properly in Hero.
I could do this easily on my magic, but I get the same thing - looks like its copied the file, but when I paste, nothing happens at all.
I did manage to delete the Stocks app. from the device (don't use it or need it) using root explorer but other attempts to copy and pasdte have failed.
I have however managed to successfully use Astro File Manager to copy a wallpaper file from the device memory and paste to the SDcard. Will explore Astro a little further and see if it can do more on the device.
Dayz
Phew, not just me being thick then....
I spent most of today trying to backup an .apk from /data/app-private to /sdcard. No luck with Root Explorer, adb pull or a 'cp' from the shell. "Remote file does not exist" was the result of the last two, but it's displayed by ls.
I think anything in app-private is a no go anyway as it contains copy protected apps. With regard to astro - it can copy from device in certain locations, and paste to sd to back up, but it can't delete from the device, and it can't copy or move files to the device.
Daisy xx
Dayzee said:
I think anything in app-private is a no go anyway as it contains copy protected apps.
Click to expand...
Click to collapse
Hmm, thanks Daisy. Will get on to the app's developer, as it was his advice to gain the ability to change location settings that I tried to follow.
Al
Shluggity said:
Phew, not just me being thick then....
I spent most of today trying to backup an .apk from /data/app-private to /sdcard. No luck with Root Explorer, adb pull or a 'cp' from the shell. "Remote file does not exist" was the result of the last two, but it's displayed by ls.
Click to expand...
Click to collapse
Try
Code:
adb shell
su
cat /data/app-private/some.app.apk > /sdcard/some.app.apk
exit
exit
adb pull /sdcard/some.app.apk some.app.apk
...it worked for me on a stock, rooted HTC Hero.
Switchbitch said:
Ok so I have rooted my Hero and all is well. I've been trying to replace the sound files in system/media/audio/ui where the keyboard sounds are. I find that I cannot move a file into that folder, or apparently any of those folders. When I try to paste a copied or cut file using root explorer into the ui folder, the file just doesn't appear.
Why is this?
Click to expand...
Click to collapse
Unless you made other changes than rooting, the /system partition is mounted read-only by default. As far as I know, you'll have to follow one of the root guides to mount it read-write (like you probably did to get /system/bin/su in place) and then do whatever changes you'd like.
Personally, I got tired of the boot audio real fast, so I changed useAudio in /system/media/boot_animation.xml from "1" to "0". Ahh, blessed boot silence...
nrkabul said:
Try
Code:
adb shell
su
cat /data/app-private/some.app.apk > /sdcard/some.app.apk
exit
exit
adb pull /sdcard/some.app.apk some.app.apk
...it worked for me on a stock, rooted HTC Hero.
Click to expand...
Click to collapse
And work it did for me also! Many thanks for your help - I really appreciate it.
Hi,
I tried changing file permission on one of the folders where I saved my photos to read-only using "Root Browser Lite".
The following error message came up: "Changing permission was not successful. Please note that some file systems do not allow permission changes".
I tried using ES file explorer but it also failed.
Could someone please tell me how I could change the file or folder permission. I wanted to prevent the photos from being accidentally deleted by my children when I let them browse their photos..
My phone I9300 was rooted using CF Auto Root.
Thanks
Get root explorer, it's much better.
Simply long press on a folder and the permissions option is there.
Sent from my GT-I9300 using xda premium
Don't forget to set to rw at the top of root explorer before attempting to change permissions
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
100% work
Try this.....
http://forum.xda-developers.com/showthread.php?t=2038243
this will help you 100%..
qwerty12 said:
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
Click to expand...
Click to collapse
=============
Thank you all for your advice. The file system explanation betw FAT and ext4 fs makes sense. I have BusyBox installed.
Via Terminal Emulator, when I did "chattr -i /data/media/DCIM/Camera", I got a "permission denied".
Is there something that prevented me from this?
I'm running ICS.
Thanks
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
zoot1 said:
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
Click to expand...
Click to collapse
Thanks Zoot1.
I did that.
Image Gallary is still showing /mnt/sdcard/DCIM/Camera as "writeable".
What is the difference between two folders /data/media/DCIM/Camera and /mnt/sdcard/DCIM/Camera?
Thanks,
Note that I used +i in my example invocation of chattr. - removes the attribute; + sets it, which is what you want
Sent from my GT-I9300 using Tapatalk 2
Thanks qwerty12, after 'chattr +i folder name' , I return to root browser lite to change permission on mnt/sdcard/DCIM/Camera, I still get permission denied. What did I do wrong?
Sent from my GT-I9300 using xda app-developers app
Mount System RW
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Vanyna said:
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Click to expand...
Click to collapse
finally its worked for me thx very much dude:laugh::good:
Two questions about the following thread (can't post in dev threads until 10 posts are made)
http://forum.xda-developers.com/showpost.php?p=47140596&postcount=1
Does anyone still have the files? The dropbox link doesn't contain any files
Is an external microsd card necessary?
The instructions are
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh tether.sh
Wouldn't it be fine to copy the MJ7_tether_unlock folder to root and use the following . . . ?
Code:
su
sh /sdcard/MJ7_tether_unlock/tether.sh
I fixed the link. Should download now. And no you cant use that command the reasoning has to do with how I wrote the script. If you dont have a micro sdcard you could also just make a new folder named "extSdCard" in the /mnt directory and then move the unzipped tether folder there.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
I fixed the link. Should download now. And no you cant use that command the reasoning has to do with how I wrote the script. If you dont have a micro sdcard you could also just make a new folder named "extSdCard" in the /mnt directory and then move the unzipped tether folder there.
Click to expand...
Click to collapse
I couldn't get r/w in /mnt
I know there's probably a smarter way to do it, and I never tried the chmod you recommended on /system . . . but I re-wrote your tether and untether sh files to use /sdcard/tether instead of /extSdCard/MJ7_Tether_Unlock
I'm not sure how to remove the "crapware" bundled into the VZW S4, but every time I connect it via usb (to my Mint 15 laptop or W7 machine) it asks me to install some Verizon helper junk. It also mounts as a CD-ROM (due to some .ini file)
Does anyone know where this "storage" area is and if it's safe to blow all that crapware away? My S4 gets mounted as CD-ROM everytime whether or not I have USB debugging enabled. In W7 if I cancel it's "Would you like to install this Verizon helper software?" then the S4 is mounted as a portable media player. In Mint 15, I can easily unmount the ROM and the S4 is mounted as a portable media player.
Since I couldn't get past this, I just moved the renamed "tether" folder over to /sdcard which is the only way I can get the phone to mount.
Surge, thanks for the framework patch, and scripts. I like the extSdCard approach since it is always preserved, but it's just a lot easier for me to use the /sdcard since I've not got an external SD and am too cheap to buy one just for this
After running the scripts, I just copied the entire folder over to my computer in case the /sdcard is ever reformatted
I can't attach the whole thing since I'm filesize limited, but I attached the folder with everything except the original MJ7framework-res.apk
Obviously the instructions are close your original, except you just move the tether folder into /sdcard (which is consquently what shows up as "Phone" when mounted as a portable media player storage area in Mint 15???). Then just
su
cd /sdcard/tether/
sh tether.sh
Thank again surge
darker_slayer said:
I couldn't get r/w in /mnt
I know there's probably a smarter way to do it, and I never tried the chmod you recommended on /system . . . but I re-wrote your tether and untether sh files to use /sdcard/tether instead of /extSdCard/MJ7_Tether_Unlock
I'm not sure how to remove the "crapware" bundled into the VZW S4, but every time I connect it via usb (to my Mint 15 laptop or W7 machine) it asks me to install some Verizon helper junk. It also mounts as a CD-ROM (due to some .ini file)
Does anyone know where this "storage" area is and if it's safe to blow all that crapware away? My S4 gets mounted as CD-ROM everytime whether or not I have USB debugging enabled. In W7 if I cancel it's "Would you like to install this Verizon helper software?" then the S4 is mounted as a portable media player. In Mint 15, I can easily unmount the ROM and the S4 is mounted as a portable media player.
Since I couldn't get past this, I just moved the renamed "tether" folder over to /sdcard which is the only way I can get the phone to mount.
Surge, thanks for the framework patch, and scripts. I like the extSdCard approach since it is always preserved, but it's just a lot easier for me to use the /sdcard since I've not got an external SD and am too cheap to buy one just for this
After running the scripts, I just copied the entire folder over to my computer in case the /sdcard is ever reformatted
I can't attach the whole thing since I'm filesize limited, but I attached the folder with everything except the original MJ7framework-res.apk
Obviously the instructions are close your original, except you just move the tether folder into /sdcard (which is consquently what shows up as "Phone" when mounted as a portable media player storage area in Mint 15???). Then just
su
cd /sdcard/tether/
sh tether.sh
Thank again surge
Click to expand...
Click to collapse
I don't recall recommending to chmod /system as that would lead to a brick if done improperly. Also I guess you could change the script and replace all instances of "/extSdCard" to "/sdcard" which is what you did, I just wanted the zip and folder to be named in such a way that youd easily be able to tell what it was. But why even bother with using a pc? I was saying to run the commands through terminal emulator on the phone.
P.S. /system/etc/autorun.iso
Sent from my SCH-I545 using XDA Premium 4 mobile app
I ran them from terminal emulator. I was just referring to mixing the files over to the phone. ES file Explorer wouldn't write in mnt. When plugged in to the laptop I just prefer to move stuff straight in. The only thing I could get to mount was a scarf
Anyway thanks again
Also, does removing the auto run iso from etc have any adverse effects?
darker_slayer said:
Also, does removing the auto run iso from etc have any adverse effects?
Click to expand...
Click to collapse
Removing or renaming the autorun.iso file does not stop the USB connection from connecting as "installer" when you first plug it in. There is still a delay of 20-30 seconds before it switches to "connected as media device" after you plug it in. If anyone has a permanent solution to this, please post it! I've tried changing the settings in the hidden menu *#7284#, but the settings don't stick and revert back to the "connect as installer" after a reboot.
Zelmo88 said:
Removing or renaming the autorun.iso file does not stop the USB connection from connecting as "installer" when you first plug it in. There is still a delay of 20-30 seconds before it switches to "connected as media device" after you plug it in. If anyone has a permanent solution to this, please post it! I've tried changing the settings in the hidden menu *#7284#, but the settings don't stick and revert back to the "connect as installer" after a reboot.
Click to expand...
Click to collapse
Thanks for the info, I was going to ask about this in a separate thread. After your reply looks like I need to look for some other method.
Also, the phone never mounts anything other than /sdcard/ right? Moving things to other places requires an explorer app?
To add to the growing number of noob questions, is it still possible to run ES File Explorer with SU in version 3? I know I used this way in the past, but I can't find the option and it's not showing me a bunch of stuff like /efs/carrier/HiddenMenus or letting me past into extSdCard
Is there a free root explorer if ES can no longer do it?
darker_slayer said:
Thanks for the info, I was going to ask about this in a separate thread. After your reply looks like I need to look for some other method.
Also, the phone never mounts anything other than /sdcard/ right? Moving things to other places requires an explorer app?
To add to the growing number of noob questions, is it still possible to run ES File Explorer with SU in version 3? I know I used this way in the past, but I can't find the option and it's not showing me a bunch of stuff like /efs/carrier/HiddenMenus or letting me past into extSdCard
Is there a free root explorer if ES can no longer do it?
Click to expand...
Click to collapse
I use ES File Explorer without any problems. Do you have "root explorer" switched ON in "Tools" in the ES File Explorer?
Zelmo88 said:
I use ES File Explorer without any problems. Do you have "root explorer" switched ON in "Tools" in the ES File Explorer?
Click to expand...
Click to collapse
Nope
Looked for it in settings, didn't think to check tools
This is a mystery. I have a Verizon Samsung Galaxy Note 2, running 4.1.1, rooted. A few days ago I ran out of space on the internal storage so I wanted to move /data/media/Download to /mnt/extSdCard/ and then symlink to it. But I screwed up and accidentally moved all of /data/media to the external SD card. I realized I did that and immediately moved it back to /data/. I did this using the Move command in RootExplorer.
Now I find I can no longer write to /storage/sdcard0/. For example, my S-Note files go there but when I try to save a note it says "Unable to save file". I have another app that also keeps data there and it too complains that it can't write to its own directory on /storage/sdcard0/. I also find there are files on sdcard0 I can't delete myself either with RootExplorer or from a terminal window, even with a "#" prompt.
/sstorage/sdcard0 has perms of 775, owned by root in group sdcard_rw. /storage has perms 775, owned by system in group sdcard_r.
I'm really stumped here. What the heck did I do to my phone? Any help would be *greatly* appreciated. Thanks!
Michele31415 said:
This is a mystery. I have a Verizon Samsung Galaxy Note 2, running 4.1.1, rooted. A few days ago I ran out of space on the internal storage so I wanted to move /data/media/Download to /mnt/extSdCard/ and then symlink to it. But I screwed up and accidentally moved all of /data/media to the external SD card. I realized I did that and immediately moved it back to /data/. I did this using the Move command in RootExplorer.
Now I find I can no longer write to /storage/sdcard0/. For example, my S-Note files go there but when I try to save a note it says "Unable to save file". I have another app that also keeps data there and it too complains that it can't write to its own directory on /storage/sdcard0/. I also find there are files on sdcard0 I can't delete myself either with RootExplorer or from a terminal window, even with a "#" prompt.
/sstorage/sdcard0 has perms of 775, owned by root in group sdcard_rw. /storage has perms 775, owned by system in group sdcard_r.
I'm really stumped here. What the heck did I do to my phone? Any help would be *greatly* appreciated. Thanks!
Click to expand...
Click to collapse
Do you have a nandroid backup? extsdcard and sdcard0 will stay untouched but maybe all you need its the system and data back to working order. I figure that's the first idea. I couldn't say what's happened though.
MunkinDrunky said:
Do you have a nandroid backup? extsdcard and sdcard0 will stay untouched but maybe all you need its the system and data back to working order. I figure that's the first idea. I couldn't say what's happened though.
Click to expand...
Click to collapse
That would be nice but unfortunately I don't have nandroid. I just back up my files to the external SD card with Titanium Backup and then store a copy on my PC. To be honest, I was afraid of screwing up something by running nandroid so I never got it.
In the meantime, none of my apps that are parked on /storage/sdcard0 run anymore, all claiming they can't create files there. The only thing I've been able to do there is chmod and chown but it doesn't seem to help. If I delete a file with Root Explorer, it says it's deleted but when I refresh the directory, it's still there.
I don't see how the two could be related, but I keep coming back to /data/media. I also have a Galaxy S3 that's working. /data/media on the S3 is 775, whereas it was 770 on the Note 2. I changed it to 775 and rebooted - didn't help. I changed the group of /storage from sdcard_r to sdcard_rw - didn't help either.
Could you tell me what the properties are on your Note 2 of /data, /data/media, /storage, and /storage/sdcard0? I'm thinking that Root Explorer munged up something when I moved /data/media/ to the extSdCard and then back again. The subdirectories and files are all there but sdcard0 isn't happy now.
Thanks very much for the reply.
Michele31415 said:
That would be nice but unfortunately I don't have nandroid. I just back up my files to the external SD card with Titanium Backup and then store a copy on my PC. To be honest, I was afraid of screwing up something by running nandroid so I never got it.
In the meantime, none of my apps that are parked on /storage/sdcard0 run anymore, all claiming they can't create files there. The only thing I've been able to do there is chmod and chown but it doesn't seem to help. If I delete a file with Root Explorer, it says it's deleted but when I refresh the directory, it's still there.
I don't see how the two could be related, but I keep coming back to /data/media. I also have a Galaxy S3 that's working. /data/media on the S3 is 775, whereas it was 770 on the Note 2. I changed it to 775 and rebooted - didn't help. I changed the group of /storage from sdcard_r to sdcard_rw - didn't help either.
Could you tell me what the properties are on your Note 2 of /data, /data/media, /storage, and /storage/sdcard0? I'm thinking that Root Explorer munged up something when I moved /data/media/ to the extSdCard and then back again. The subdirectories and files are all there but sdcard0 isn't happy now.
Thanks very much for the reply.
Click to expand...
Click to collapse
Did you want to know what permissions those directories have?
/data rwx rwx --x
/data/media rwx rwx ---
MunkinDrunky said:
Did you want to know what permissions those directories have?
/data rwx rwx --x
/data/media rwx rwx ---
Click to expand...
Click to collapse
Yes, thanks. That's the same I have on the Note 2, so that's not the problem (though oddly enough, on the S3, /data/media is rwxrwxr-x).
Still, it has to be *some* permission somewhere that's wrong and is preventing apps from writing or deleting files they have in sdcard0. What about /storage? I've got:
/storage r-xr-x--- owner=system, group = sdcard_r
/storage/sdcard0 rwxrwxr-x, owner = root, group = sdcard_rw
/storage in particular doesn't seem correct. ???
FWIW, here's someone else with the exact same problem - unfortuntely he didn't get a resolution: http://androidforums.com/android-lounge/716573-unable-delete-move-files-directories-sdcard0.html
And this one too: http://android.stackexchange.com/questions/30113/cant-delete-any-files-in-my-download-folder I tried the same things suggested there and they didn't work for me either.
I dont know enough about the permission system. You said you tried terminal. Maybe try another root enabled file explorer. I've only used es and root browser. Maybe your binaries need to be updated.
You might consider starting fresh if you can't find a solution. From here on out I'd take care to be meticulous and read up on the how to threads for rooting and unlocking bootloader just so you have an idea of where what your going to do fits in with everything else. It sounds like you've just beet rooted and left your phone stock.
Perhaps the internal memory need to be reformatted and everything taken back to a stock working order? If your bootloader is unlocked and you have a custom recovery (like twrp or cw) you could back up all contents of your ext and internal sd to a computer, do a nandroid backup(just in case), and back up your apps with titanium, then wipe everything, system data cache dalvick through recovery then reformat internal sd and re flash the stock rooted image of 4.1.1 or 4.1.2.
If your bootloader is locked up still you could use Odin to get back to stock factory image. You would no longer be rooted but you can then reroot. This is always the end of the line and one can run into some bigger problems here.
MunkinDrunky said:
I dont know enough about the permission system. You said you tried terminal. Maybe try another root enabled file explorer. I've only used es and root browser. Maybe your binaries need to be updated.
Click to expand...
Click to collapse
Yup - I've tried Root Explorer, File Expert, Terminal Emulator, and adb USB from the PC. Same result from all of them. Oddly enough, Root Explorer and FE both claim that files I select on /storage/sdcard0 have been deleted, but when I refresh the file list, they're baaaack...
MunkinDrunky said:
You might consider starting fresh if you can't find a solution. From here on out I'd take care to be meticulous and read up on the how to threads for rooting and unlocking bootloader just so you have an idea of where what your going to do fits in with everything else. It sounds like you've just beet rooted and left your phone stock.
Click to expand...
Click to collapse
Yes, I only flashed the Verizon rooted stock ROM because that's all I needed. I just want to be able to use apps like Titanium Backup, get rid of that stupid clicking sound the camera makes, and other things you need root for. I'm happy with the other features of the standard ROM. I never bothered unlocking the boot loader.
MunkinDrunky said:
Perhaps the internal memory need to be reformatted and everything taken back to a stock working order? If your bootloader is unlocked and you have a custom recovery (like twrp or cw) you could back up all contents of your ext and internal sd to a computer, do a nandroid backup(just in case), and back up your apps with titanium, then wipe everything, system data cache dalvick through recovery then reformat internal sd and re flash the stock rooted image of 4.1.1 or 4.1.2.
Click to expand...
Click to collapse
Yes, I've considered that, and it may come to that. But it's not a very intellectually appealing solution. It's sort of like burning down your house because you've got termites. I'm still hoping there's a less drastic solution. In the meantime, this may be locking the barn door after the horse is gone, but I downloaded a nandroid app and took a nandroid backup. Don't know if wiping and then restoring that will also restore the problem.
MunkinDrunky said:
If your bootloader is locked up still you could use Odin to get back to stock factory image. You would no longer be rooted but you can then reroot. This is always the end of the line and one can run into some bigger problems here.
Click to expand...
Click to collapse
Yup, if that doesn't do it, it's time for a new phone
UPDATE:
I started looking at /data/media and comparing permissions there to what my S3 was showing. It seems /data/media was owned by media_rw in group media_rw on the Note2, but owned by root in group root on the S3. So in adb on the Note 2 I did #chown root:root /data/media. To my surprise, that worked. I then changed the permission from 770 to 775 to match what the S3 has. I then tried saving an S-Note - didn't work. So I went into /data/media/S Note and changed *its* owner/group to root, and permissions to 777 also. I tried saving a note and ... success! It saved it OK.
I'm starting to think that when I copied /data/media back to /data from /mnt/extSdCard/data/media, Root Explorer bollixed up the owner/group/permissions. I'm going to try some other directories there and see if that helps too. And see if this survives a reboot. So that's some progress at least...
That is indeed good news. At least the permission will work through terminal on a subdirectory basis in the media dir. You could recursively change permission for all subdirectory in media. I belive -R probably best to Google that.
MunkinDrunky said:
That is indeed good news. At least the permission will work through terminal on a subdirectory basis in the media dir. You could recursively change permission for all subdirectory in media. I belive -R probably best to Google that.
Click to expand...
Click to collapse
Well that seems to have done it. Everything is working once again. In the final analysis, it appears that you just can't change permissions or delete files from /storage/sdcard0/. However, this is apparently just a mount point (I may be wrong here) for /data/media/ and you *can* change permissions/owners/etc. there. Once I did that, the apps I had that had installed themselves on sdcard0/ started working again. Go figure.
And as a bonus, I got the motivation I needed to start doing nandroid backups and learned a little about the storage hierarchy of Android. So big thumbs up for taking the time to read all this and help me out.
Michele31415 said:
Well that seems to have done it. Everything is working once again. In the final analysis, it appears that you just can't change permissions or delete files from /storage/sdcard0/. However, this is apparently just a mount point (I may be wrong here) for /data/media/ and you *can* change permissions/owners/etc. there. Once I did that, the apps I had that had installed themselves on sdcard0/ started working again. Go figure.
And as a bonus, I got the motivation I needed to start doing nandroid backups and learned a little about the storage hierarchy of Android. So big thumbs up for taking the time to read all this and help me out.
Click to expand...
Click to collapse
Yeah I leaned more bout this too. As an after thought, I have only ever moved items from sdcard0 to extsdcard by going to /storage then copying items from one to another. I too believe this is just a mount point. Nevertheless, probably most items in /data/media you were trying to move to extsdcard are found in sdcard0 and accessible through the mounting folder: /storage, well at least /downloads are there in /storage/sdcard0/ and i have always navigated to /storage first then to /sdcard0/ to grab /downloads or /android/data/ to copy to external whatever.
I know the thread is more than a year old, but I have the same issue here on the Xperia T.
Can't write on /storage/sdcard0
However, I have no idea what to do to fix it. I found a step by step actionplan here:
http://forum.cyanogenmod.org/topic/104879-cm12-issue-with-sd-card-and-wifi-network-detection/
is this what you did?
Hello,
I have Lenovo S720 running on Android 4.0.4 that I recently factory reset because It has only few little internal storage (~1,4 GB), and cannot support many updating apps.
After I do that, whats left in the internal storage is about 500 MB of storage, the rest being taken up by the system (I suppose).
I installed Framaroot to root the device, then System App Uninstaller (ROOT) and ES File Explorer.
First, I try to uninstall any bloatware with the System App Uninstaller -> I didn't get much free internal storage.
Then, I use ES File Explorer to seek, which folder took up the most space.
-> One of the is /system/vendor folder.
-> So, I copied that folder to /mnt/sdcard/backupsys/ (or /sdcard/backupsys/ [little bit forget]), Thinking it would come in handy later.
-> Then, I (foolishly) proceed to delete the folder using the root privileges .
-> It took a moment until all of my app start crashing (including the ES File Explorer!).
-> I turned-off the device, and now it still stuck in the (what I think as) "bootloop" mode.
Fortunately I still can communicate to the phone using adb tools, which I have a little knowledge of. But, the pm and am command cannot function well.
Now, I'm only thinking about moving back the vendor folder from /mnt/sdcard to the /system folder.
But I encounter some problem:
1) I can't (& don't know how to) write to the /system
2) I can't (& don't know how to) read from the /sdcard
- command 'ls' inside this dir returned nothing.
Glad I have the "su" tools from the Framaroot. I searched on the Internet and it seems the problem can be solved with mount tools, but I don't know how.
ls -la tools on root (/) return:
(other dir)
root /system ,,,,,,,,,,other info,,,,,,,
system /sdcard ,,,,,,,,,,other info,,,,,,,
(other dir)
So maybe because I can't gain system account, I can't access the folder and read it...
I try to hard-reset in the recovery mode, but I can't select the options! (I can move the selector with volume up/down) but I cant click it with the power button!
The phone seems to be worse every second.
My main question is: can I recover my phone (copying the vendor folder back) using command tools on my development computer? Or is there any other ways?
I'm willing to install any custom ROM best suited to my phone.
Thanks in advance.
Hello,
Welcome to XDA.
If you have a copy of what you deleted or can get it from somewhere and you want to adb push your missing files and folders back to your device then you need to have the files you want to push stored on your PC and push them from there to the device. For instructions on how to use adb read through the thread linked below and go from there.
http://forum.xda-developers.com/showthread.php?t=2141817
If you have further questions or need further help with using adb then you can post in the Q&A forum linked below:
http://forum.xda-developers.com/android/help