Hello,
I had [JVT]Galaxydroid 2.0 but decided to go back to stock JVT. Now I'm having all kinds of trouble with copying a file to /system/etc.
I flashed stock JVT over Galaxydroid and rooted with speedmod kernel. Wiped caches and wiped user data. Then I installed su+busybox with speedmod's recovery option.
Titanium Backup didn't want to recognize su and busybox but after few tries it worked. Then I tried to copy spn-conf.xml to /system/etc (mounted /system as writeable with ES Root Explorer) and it seems like it copies succesfully, but the filesize is 0 bytes and the file is empty.
Then I tried adb, but it can't mount and doesn't even recognize cp or other commands. Where did I fail and how to fix this?
Thanks in advance
Related
Hello
I have had this same problem on doomlords (With z's working xrec) and wolfbreaks rooted 2.3.3 roms
1. Root explorer always FC
2. Other explorers show the folder /data/data is empty
3. adb cannot push files to /data/data
'copy failed permission denied'4. When in recovery if I mount system and data manully then adb push works
Has anyone else had the same problem, or can you give me some advice to help me
Copying a font in /system/fonts resulted in a 'read only file system' error.
Googling around looks that the /system folder is mounted read only.
How can I (temporarily) set this folder to read/write ?
By using a rooted file explorer or Super Manager .
jje
Thanks, this works.
When I set /shystem to r/w I can manipulate files / copy files to this folder even from an SSH terminal from my Mac.
Worked extremely well!
Thanks for the help guys. I had installed Beans Stock Rom and lost my VVM support. The market even said my device was not compatible. Tried all prior versions of VVM and none worked until I got this file and used Root Explorer to install it and set permissions as described. Thanks heavens.
Hello,i accidently deleted all the files inside /efs while messing with root explorer.Now the /efs folder is empty.
but i had done backup (both clean and raw).(have both tar.gz and .img of mmcblk0p1)
So when i try to restore it :
1)Using Hellcat's kTool .It gives the msg "efs restored.you may want to reboot now."
but when i check in /efs folder it is still empty.And after reboot there is only 1 file named cryptprop_essiv (1 byte) in it.
using terminal emulator
a)i type
Code:
su
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
it says
Code:
efs/
efs/cryptprop_rebootMode
tar:can't remove old file efs/cryptprop_rebootMode:
read-only file system
#tar:write: Broken pipe
then when i try the above after mounting /efs as r/w in root explorer,then this happens
Code:
efs/
efs/cryptprop_rebootMode
efs/cryptprop_onetimeboot
efs/cryptprop_securewipedata
efs/.files/
efs/.files/.dx1/
efs/.files/.dm33/
efs/.files/.mp301/
efs/nv_data.bin
efs/nv.log
efs/nv_data.bin.md5
efs/dmp/
efs/dmp/sett/
efs/dmp/sett/system/
efs/dmp/sett/system/volume_ring_last_audible
efs/dmp/sett/system/vibrate_on
efs/dmp/sett/system/time_12_24
efs/dmp/sett/system/screen_brightness_mode
efs/dmp/sett/system/volume_ring
efs/dmp/sett/system/volume_notification
efs/dmp/sett/system/volume_notification_last_audible
efs/dmp/sett/system/dtmf_tone
efs/dmp/sett/system/sound_effects_enabled
efs/dmp/sett/system/haptic_feedback_enabled
efs/dmp/sett/system/VIB_FEEDBACK_MAGNITUDE
efs/dmp/sett/system/screen_brightness
efs/dmp/sett/system/screen_off_timeout
efs/dmp/sett/system/mode_ringer
efs/dmp/sett/system/volume_system
efs/dmp/sett/system/volume_system_last_audible
efs/dmp/sett/system/vibrate_in_silent
efs/dmp/sett/system/airplane_mode_on
efs/dmp/sett/system/power_saving_mode
efs/dmp/sett/secure/
efs/dmp/sett/secure/mobile_data
efs/cryptprop_applied_result
efs/imei/
efs/imei/mps_code.dat
efs/imei/bt.txt
efs/imei/keystr
efs/calibration_data
efs/.nv_core.bak
efs/.nv_core.bak.md5
efs/.nv_data.bak
efs/.nv_data.bak.md5
efs/.nv_state
efs/redata.bin
efs/edk_p
efs/cryptprop_persist.sys.timezone
efs/cryptprop_lockscreen.patterneverchosen
efs/cryptprop_lockscreen.password_type
efs/cryptprop_lock_pattern_autolock
efs/cryptprop_lock_pattern_visible_pattern
efs/cryptprop_lock_pattern_tactile_feedback_enabled
efs/cryptprop_lockscreen.lockoutattemptdeadline
#
After this all files get back in /efs,but after i reboot.same problem occurs.no imei.Only 1 file present in folder
cryptprop_essiv
b)when i try to use this method
Code:
su
busybox umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
it says
Code:
umount:can't umount /efs:Invalid argument
and i just did a little experiment.i just copied a small random file in the efs folder.after i reboot it is gone and replaced by that cryptprop_essiv file.
even if i delete this file and reboot it comes back again.
Please any help would be appreciated.
i have the same problem too but i did't play with those folder it happened when my phone run out of battery and shut down it self when turn on no signal imei gone. inside efs folder only have cryptprop_essiv file
Seems like you have permission problems. I don't know if this will help any, but in CWM, goto Advanced, and Fix Permissions.
You could try using Heimdall to flash the efs.img using download mode.
You can get Heimdall at http://www.glassechidna.com.au/products/heimdall/
Using the command line should be as easy as when the phone is connected in download mode.
"heimdall flash --efs efs.img"
*If it is possible using Odin I don't know since I don't have Windows and have never used it.
** I have also never used the Heimdall GUI
i solved it... i extract the tar.gz file and rename the .nv_data.bak to nv_data.bin and copy to efs folder then reboot and wait for awhile all done in root explorer ...by the way i also got fix permission but i dont know whether got effect anot.
seemsoweird said:
i solved it... i extract the tar.gz file and rename the .nv_data.bak to nv_data.bin and copy to efs folder then reboot and wait for awhile all done in root explorer ...by the way i also got fix permission but i dont know whether got effect anot.
Click to expand...
Click to collapse
please can you explain more how can you copy file in efs folder? becuase its system file read only?
Hi,
I'm using the last Envi-ROM based in stock 23.0.1.A.0.167 and I would like to disable the charger plugged in notification so I tried to remove ChargerPluggedIn.ogg from /system/media/audio/ui but it says that it's an only read file and I can't do it. I'm root and I tried with RootExplorer, ES File Explorer, ADB (mv, chmod,...) but I'm not able to change the permissions neither the file nor /system folder.
Any idea?
Thanks in advance
So i just changed the permissions of that file with rom toolbox lite to 777 without issues. I also moved it up a directory without issue. Maybe try that app ( https://play.google.com/store/apps/...+lite&pcampaignid=APPU_EaWoVMe9Nce7mwWlnILYCw)
If you still have issues why don't you backup your phone and redownload envi-rom zip. Open the zip and navigate to the file and delete it. Then install that moded zip file and restore your data from the backup?
You can try to remove this file via file explorer in recovery, like for example aroma explorer.
Sent from Xperia Z2
Nope no good. Could only see /system/bin/ no other directories.
Thanks a lot for your comments. I tried toolbox with the same result as the previous tries. With aroma explorer I can only access to /system/bin/. So no luck for the moment. It seems that the only solution is install again the ROM without the file, but I still looking for other alternatives first.
Here is the solution: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
My Samsung Galaxy have been inject some virus in /system/app. Now I root my phone and run rm command by root user, but still can not remove the apk file. The system show:
rm failed for /system/app/providerdown.apk, Operation not permitted
I want to know why the root use don't have the permission to remove some file?
I post the cmd log of my operation:
[email protected]:/system/app # ll -la |grep providerdown.apk
-rwsr-sr-x root root 178557 2015-06-11 14:07 providerdown.apk
[email protected]:/system/app # mount -o remount,rw /system
[email protected]:/system/app # rm -rf /system/app/providerdown.apk
rm failed for /system/app/providerdown.apk, Operation not permitted
The system file system have already mounted, and I can touch a new file, and also can remove new file by rm command.
Can Selinux affect the root permission, or there have some other permission that upon root user?
Any one can help me and Thank you for your ANSWER!
Have you tried with an app with root permissions, like Root Explorer? Or Titanium Backup? Found something about it here http://stackoverflow.com/questions/30771742/aggressive-adware-irremovable-apk-on-android but not a complete solution. I suspect the best way, if all else fails, is to reinstall the stock OS. 1 of 2 possible ways... 1 via Odin. 2 via flashing a rom zip of the same build via custom recovery. If you are just stock rooted and are REALLY against resetting your phone, then flashing the rom via a recovery like TWRP while only wiping /system, /dalvik cache, and cache partitions should let you be in the clear and not lose any settings, though always recommend backing up any important info before trying such a thing. If you do not have a popular model, then the rom option might not work if there is nothing available for it. If that is the case, then reinstalling the OS via Odin is about the only way, but will wipe everything on the phone.
Thanks so much, I will try.
es0tericcha0s said:
Have you tried with an app with root permissions, like Root Explorer? Or Titanium Backup? Found something about it here but not a complete solution. I suspect the best way, if all else fails, is to reinstall the stock OS. 1 of 2 possible ways... 1 via Odin. 2 via flashing a rom zip of the same build via custom recovery. If you are just stock rooted and are REALLY against resetting your phone, then flashing the rom via a recovery like TWRP while only wiping /system, /dalvik cache, and cache partitions should let you be in the clear and not lose any settings, though always recommend backing up any important info before trying such a thing. If you do not have a popular model, then the rom option might not work if there is nothing available for it. If that is the case, then reinstalling the OS via Odin is about the only way, but will wipe everything on the phone.
Click to expand...
Click to collapse
Thanks so much, I will try.