Hi,
i accidently changed the permission of the folder "system" to READ only. atleast i think so... i used Yaffs Explorer to change permission of "system" and i ticked the first line on all 3.
again.. this was an accident cuz i didnt know what i was doing.
now the problem is my phone just keeps restarting ... and then it boots into recovery (3e) on its own...
i tried using ADB to change the permission with adb shell ... and all that.. problem is
adb works. phone connects and shows off as device.
but if i try using the adb shell command or any other command with adb ( except sideload ) it tells me
"PERMISSION DENIED" and similar messages...
i have no clue how to safe my phone now any help would be much much appreciated.
i thought something of my own...
is it possible to write a shell script which changes the permission of "system" folder to its correct one.. make it as a .ZIP file and update use it with "update from adb"
please any help^^
best regards
Krype
I assume you are rooted have you gone into CWM and reset permissions?
Hi guys, having an odd problem.
I've made some nandroid backups (about three) via CWM Recovery, and I can't seem to browse to them, or delete them.
It's definitely taking up space, and I'm not sure what to do now.
A backup that I made straight to my external SD card however, seems to be browse-able, so I'm a bit confused now.
Attached are some screenshots from ES File Browser (with root access turned on).
The last screenshot is going to /storage/sdcard0/clockworkmod/ (same directory, but now I can't seem to see anything about "backups").
I've also tried to delete these backups straight from CWM Recovery, but CWM says that it can't access the folder.
Oddly enough, if I do another backup (straight to internal), it seems to put all the files in /sdcard/Clockworkmod/backups but never to be accessed again.
Anyone have any ideas?
Delete via Windows Explorer .
jje
JJEgan said:
Delete via Windows Explorer .
jje
Click to expand...
Click to collapse
Thanks for the suggestion, but nope, that didn't work. (Obviously tried that first).
The folder was shown as empty via Windows.
After a lot of digging and trying different things (including Root Explorer and Terminal Emulator), I've managed to delete it.
I'll post the instructions so other people who may have similar problems in the future can follow it.
First, you'll need ADB and you'll need to reboot into CWM Recovery.
Once you've gotten that sorted, boot into CWM Recovery and go to "mount and storage" and then select "mount /data".
This will mount the /data structure which we need to use.
Afterwards in CMD, use the following:
Code:
adb root
adb shell
After this, you should be logged in as ~ (root)
Proceed to go into the directory using the cd function. (PROTIP: Use the ls function to check where you're going.)
You need to get to ../clockworkmod/backup/
You'll find that you can finally access the /backup/ folder, and you'll then be able to delete the files. Please note that the below command will delete ALL the files within this folder.
Code:
rm -rf *
Afterwards, do
Code:
cd ..
to get back to the ../clockworkmod/ folder and then run the below code to delete the now empty /backup/ folder:
Code:
rmdir backup
no, to be logged in as root you need to type in "su"
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
EDIT:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
lalalalas said:
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
Click to expand...
Click to collapse
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
leadtk said:
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
Click to expand...
Click to collapse
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Quallenauge said:
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Click to expand...
Click to collapse
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
leadtk said:
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
Click to expand...
Click to collapse
From the guide, install using adb. http://forum.xda-developers.com/showthread.php?t=1871912
Originally Posted by surdu_petru
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /local/ ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
If you are a Linux user. http://forum.xda-developers.com/showpost.php?p=48731942&postcount=1
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
leadtk said:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
Click to expand...
Click to collapse
I do not know what i am doing wrong but when i type adb shell ..all i get is BUSYBOX v1.7.2 (2012-10-19 CEST) built in shell (ash) Enter help for a list of built in commands ...
I did have ics blue v04 rom on my tablet that i was trying to go from to 4.4.2 ..
I did this before and had the write problem . any help you can give would be appreciated
Unhappy [Q] Problems with deleting files and replacing sounds
HI all! New use here.
I superuser'd my phone, routed my phone, installed CM11 and all is well. It was my understanding that with apps like RootBrowser and or SuperManager i could browse to files change permissions and delete and remove them or replace them.
I am unable to change my lock sound or boot animation.
Ive granted the permissions to the apps and am operating the root browsers in Root mode. (sorry if my terminology is wrong but im new to this) When i try to replace the files in system/media or system/media/audio/ui they simply dont work, "operation failed". I am able to change the permissions on the replacement files going into these directories to match those im overwriting but its still fails.
Ive even successfully deleted the default lock sound but when i paste the new one into the folder it fails and says stuff like "out of space" or "no room" and then when i shut app and go back in the original file is back!
Can anyone help with this as my lovely rooted phone is being very difficult.
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
Thank you. I now know what to do but not how to do it? Are you able to help or link me to a post on how to do that?
Many thanks
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
When i use the app SuperManager to browse the file system to "system" folder it asks me "If you want to modify the file in teh system, you have to mount the system image first. Please choose access mode: System IMage: R/O"
then
"Do nothing Read only R/W" so i chose R/W but that does not fix the problem?
My errors i get are "not enough free space" well there is plenty of that!
So confused....
Any thoughts
Just ignore the "not enough free space".
Cant help you with RootBrowser or SuperManager because I never used them. I use ES File Explorer, and mounting partitions with it always solved my problems with not being able to delete / modify system files / apps.
Ive been able to decrypt adoptable storage and copy files over from my pc, however i had to chown the media folder to be able to write.
Now on android in a normal file manager the files are 0 bytes and not readable.
I can read them and open them normally with ghost browser as root but not in the stock file manager.
Ive tried to chown -R them back to media_rw:media_rw or system:media_rw but no avail
Somehow I was able to change one folder(including files) back in a test (cant remember how)
Does anyone know if I need to change the files in /mnt/expand/<uuid> or /sdcard ?
KenzooW said:
so does it works?
Click to expand...
Click to collapse
It didnt work for me, at least not yet because i gave up as it was taking to much time there are a few folders with sym links,
Code:
/mnt/expand/<uuid>
/sdcard/
/storage/emulated
/data/media
need to compare all the permissions sometime and replicate it.. It was taking to much time and i found another solution which was to move the folders to a writeable directory after mounting (no change in permissions)
Then on the phone moving it to the right place in ghost file manager. Android has separated the permissions for apps and what not.
Overall its easier just to copy via OTG.
One thing I forgot to mention, that if you're on Linux with the decrypted sd card mounted, you can copy files over directly to the media folder (as #root) without "chown"ing.
I didnt try this but i think that it may work that way since you're not altering existing permission settings