I have the OTA Froyo, rooted...But I can't change any files in the system/media folder. If I do, it says deleted...but comes right back. I also can't write to it either (and yes, It is mounted R/W)...
Ideas?
also, I have tried to fix permissions as recommended by another user but that didn't affect anything.
basically, I am trying to delete the old shutdown_1.png and replace it with my own. Is this possible? Or am I digging a hole?
I have been able to do this easily on my X, but my wifes Fascinate is kicking my arse!!!
Related
hey, i got a virgin mobile s2 yesterday and i rooted and unlocked with
http://forum.xda-developers.com/showthread.php?p=13715727
and galaxy s unlock on the market.
im assuming it went well since i have the yellow triangle and my rogers sim now works.
i got root explorer and followed instructions on making "local.prop" in data with "ro.camera.sound.forced=0" but it hasnt been working.
is there any known problems with my type of combination
Virgin
XWKDD_insecure.tar
or any other help at all?
Im totally new to this and i dont want to mess anything up by using another rom or something because i need it before a flight tomorrow morning.
You could delete the following using root explorer:
/system/media/audio/ui/camera_click.ogg
/system/media/audio/ui/camera_click_short.ogg
/system/media/audio/ui/Shutter_01.ogg
That way you delete the audio file the camera uses. If you don't want to do it as a permanent solution, you could backup the files if you want to restore them.
hmm i already tried to rename those files in root explorer but i got a no permission error. but your post brought me back to it and i successfully renamed them after turning on "mount r/w".
Thanks! lol
Although it would have been cool to keep the sounds and only make it silent when it was in silent mode :/
Hi,
I cannot edit /default.prop after update.
To be more accurate, I can edit it, but after reboot it is the way it was before.
I have root, any idea what is happening?
CORRECTION it's 2.3.4
Could be a couple of things,
1. I've read a post on here before about a phone that couldn't be flashed with different firmware at all, possibly due to corrupted nand memory.. Hopefully yours isn't
2. How are you editing the file, are you using something like root explorer or copying the file onto pc then trying to push / paste it back to the phone, because either way you have to make sure you have write access to the system and file.
Hope you get it sussed
Sent via courier pigeon
Thanks for the reply, morg01.
I used for editing a pack of tools, first "super manager" to mount "/" as RW then either "script manager" to edit the file, or Terminal Emulator to add the needed line.
So far I've only found a workaround for the problem, by using ADW launcher, instead of original one. But even though it is very rich in options I prefer the TouchWiz. ADW is kind of lagging I have no idea why
What exactly is nand memory, and how could it get corrupted. I've experienced some problems lately, with a slight pressing of the back cover or if it is removed on the upper end of the battery the phone reboots.
Is it possible to be more than just a battery problem?
Hi there,
I upgraded my Galaxy 551 to Gingerbread 2.3.6. All went well. Unfortunately it seems to be a common side effect that the Z and Y keys (and some others) get swapped. The fix is apparently to modify the file /system/usr/keychars/sec_keypad.kcm.bin. The ideal thing is to put the old file from before the FW update back in, but of course I don't have that anymore! But the existing one can apparently be altered. If I can copy it to the SD card I can alter it in a hex editor and put it back.
So, I rooted my phone with that one click application, and that went OK too. I installed root explorer and found the file. There were also some others in the same folder I may be able to use. But, I cant make the folder R/W (pressing the button does nothing) so cant do anything with the file. I also tried Super Manager with no luck.
I am new to the phone fiddling stuff so noob level instructions would be appreciated!
Think I have it sorted. I installed superuser and then Root Explorer allowed me to select read/write. Now to try sort out this file!
OK, seems that you need to edit the file /system/usr/keylayout/sec_keypad.kl. Did that. DO'H now my keyboard doesn't work at all! Glad it saved a backup for me! Not sure what I did wrong, only edited two characters in a text file! Even the power button doesn't work. Got to pull that battery out LOL!
It seems when the file was saved it was saved with zero size. When I try to delete it to replace it with the backup it says cant delete, read only. So, not sure how I am meant to replace this and fix this problem.
Any ideas, remembering that I cant actually use any buttons on the phone!
Hey I was just wondering if someone could pull an unedited copie of tegra-kbc.kl from system/usr/keylayout for me? I just SBF to 2.34 a couple days to reinstall Eclipse was on CM9. After I SBF my back and home buttons always reverse. I changed my keylayout before trying to update to 418 and install fails bc I modified it. I don't currently have a way to SBF but I'm thinking if I take an unmodified copy push it to keylayout & set permissions it might take the update any thoughts?
Here you go just remove the .zip
Sound's like a plan...
Thanks updated worked like a charm.
Glad to help, and everything's working for you
I ended up needing this too. Does 418 have a messed up key layout built in? I've SBF'd this phone several times and it's like it contains a bad /system that needs to be modified in order to work properly.
I had something weird like that happen to me too never really figured it out but I ended up flashing it away and had to reverse the key settings again so no clue but if this'll help here it is http://forum.xda-developers.com/showthread.php?t=1961001
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
Even better. I was too lazy to copy in a file so I just used ES File Explorer to navigate to system/usr/keylayout/tegra-kbc.kl and then I just used ES's text editor to swap the key settings. I rebooted and all was well after that.
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
positivehxcgo said:
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
Click to expand...
Click to collapse
Sounds like you are on 4.5.3 but lost root. Might try to reroot using Kingroot although I believe that involves a reboot. Pretty sure your device will not restart (effectively brick) without build.prop. You really need to get adb working to expand beyond those options. Keep your device on charge to prevent a shutdown due to low battery.
I absolutely would not attempt a 3.2.8 rollback. There is an outside chance a factory reset from stock recovery would restore a generic build.prop if none is found. It generally will not repair or replace a damaged file and involves a reboot which could be fatal. This becomes an last resort option imo.
If you device was purchased from Amazon it may still be under warranty. Sometimes that is the best/only path. Good luck.
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
positivehxcgo said:
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
Click to expand...
Click to collapse
You will probably need to root via adb which is challenging and by no means certain. Take a look at this thread for ideas. You may want to reach out to @myotai as he faced a similar problem.