I had some problems with an in call echo. So I tried to fix this by some changes in mixer_paths.xml. I copied the original file to my sd-card so I thought I have a backup. But after I made some changes the phone get stuck and won't reboot. I didn't expect this to happen!
I restarted my phone in TWRP and tried to copy the original file from the sd-card. But I don't know how I can do this. Does anyone have an idea?? Is it possible in terminal? Or should I connect the phone to my computer and try with ADB?
Hopefully there will be a solution and I don't have to reinstall everything!
Edit: In terminal and file manager (in TWRP), I can't find the folder "etc" in "system". There is only the folder "usr". Or should I look at another folder?
NL_henk said:
I had some problems with an in call echo. So I tried to fix this by some changes in mixer_paths.xml. I copied the original file to my sd-card so I thought I have a backup. But after I made some changes the phone get stuck and won't reboot. I didn't expect this to happen!
I restarted my phone in TWRP and tried to copy the original file from the sd-card. But I don't know how I can do this. Does anyone have an idea?? Is it possible in terminal? Or should I connect the phone to my computer and try with ADB?
Hopefully there will be a solution and I don't have to reinstall everything!
Edit: In terminal and file manager (in TWRP), I can't find the folder "etc" in "system". There is only the folder "usr". Or should I look at another folder?
Click to expand...
Click to collapse
Could be just that you forgot to change permissions on mixer_path.xml....you could chmod it from twrp terminal.
chmod 644 /system/etc/mixer_path.xml
You could always restore your nandroid or dirty flash you rom.
Sent from my SM-G955F using Tapatalk
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.
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 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've messed with some of my files on my phone through ES File manager, and I kept getting errors with a specific folder, I then realized that, it's only happening with the folder I created while pushing a file through adb. ESFM has root permissions enabled, but I could not find where to view the permissions for a folder, only files. I also managed to change the stuff in the folder while in recovery. Do I need to set the permissions for the folder through adb right after i create it, or is it a bug somewhere with the ROM/device, or just a random error? If someone could provide an explanation it would be nice.
Viper 1.2.0
s-off
ML417 said:
I've messed with some of my files on my phone through ES File manager, and I kept getting errors with a specific folder, I then realized that, it's only happening with the folder I created while pushing a file through adb. ESFM has root permissions enabled, but I could not find where to view the permissions for a folder, only files. I also managed to change the stuff in the folder while in recovery. Do I need to set the permissions for the folder through adb right after i create it, or is it a bug somewhere with the ROM/device, or just a random error? If someone could provide an explanation it would be nice.
Viper 1.2.0
s-off
Click to expand...
Click to collapse
See if you can duplicate the error while pulling a logcat. That will help out in solving your problem.
if you dont wanna do that just adb remount and chmod the folder either through adb or adb shell access then restart phone
It's specific to only the folder i created through adb. I'm wondering if anyone else experienced it, or if it is only on my phone
what type of folder and either way you should be able to just adb shell then su then chmod /path to folder
t1gartist said:
what type of folder and either way you should be able to just adb shell then su then chmod /path to folder
Click to expand...
Click to collapse
I created the folder on the /sdcard while pushing a file from my computer. The folder was still accessable, I just wasn't able to copy anything into it/edit it. What permissions would be given to a folder like that if i didn't specify them?
you should have been able to read and write by default all of mine are... erm.... delete the folder and create it via root browser or what ever explorer you have and you should be able to long press and access permissions
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
the problem was in the file permissions. i had to remove write permissions to the group. (rw-r--r--)
You can fix permissions using adb
Sent from my GT-S5830 using xda premium
the.fuzzy.guy said:
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
Click to expand...
Click to collapse
First of all DO NOT WIPE DATA / FACTORY RESET
This will remove adb access. Depending how far you can boot, do you get adb in recovery or normal. Can you use adb shell? If you can you can us adb shell chmod 644 /system/build.prop
EDIT:
Failing that try to install a zip. Sell my links for both current and older zips