Related
And any tips to what change in it?
FelipeRRM said:
And any tips to what change in it?
Click to expand...
Click to collapse
Use root explorer. Go to /system and press and hold the build.prop file and then select open in text editor. Make sure you mount r/w in root explorer.
Thanks, and there it goes more money on Android Market =[
Edit: If I wanna add anything just add it to the end, save and reboot? This thing does need a search function to see if the line's already in there somewhere. Does it harm to add a line in the end if it is already there somewhere, working like botton lines overriding the top ones?
Any suggestions to add? And what's dalvik heapsize, head some talk about it.
would strongly suggest that you read and learn before making any changes.
FelipeRRM said:
Thanks, and there it goes more money on Android Market =[
Edit: If I wanna add anything just add it to the end, save and reboot? This thing does need a search function to see if the line's already in there somewhere. Does it harm to add a line in the end if it is already there somewhere, working like botton lines overriding the top ones?
Any suggestions to add? And what's dalvik heapsize, head some talk about it.
Click to expand...
Click to collapse
2nd post http://forum.xda-developers.com/showthread.php?p=10536952#post10536952
rendeiro2005 said:
2nd post http://forum.xda-developers.com/showthread.php?p=10536952#post10536952
Click to expand...
Click to collapse
Thanks, but I tried setting the dalvik to 12, as I use only light apps, to see if it would perfom any better (as you said it could be from 12 to 40), and the phone entered an endless loop from boot screen to "Sony Ericsson" screen. Had to re-flash, thankfuly xRecovery still worked and I had a zip in the SD card.
FelipeRRM said:
Thanks, but I tried setting the dalvik to 12, as I use only light apps, to see if it would perfom any better (as you said it could be from 12 to 40), and the phone entered an endless loop from boot screen to "Sony Ericsson" screen. Had to re-flash, thankfuly xRecovery still worked and I had a zip in the SD card.
Click to expand...
Click to collapse
that happen because you didn`t use the right permissions.
from what you`ve described i presume you edit build.prop and then copy paste to system, right?
do this:
enter on system folder, press and hold build.prop file select permitions and then check all. Now copy your new file to system and repeat the proccess (check all permitions).
reboot.
No, I had already changed it from 24 to 28 before, without errors, the only thing I did different in the first time was to "mount r/w". Maybe that's what happened lol.
Edit: Tried again, now mounting the r/w thing, like I did in the first time, but still got the boot loop.
I didn't change the permsions, I'm doing it directly through Root Explorer. click and hold, open in text editor.
I see some people advising people to fix permissions, but mine has never worked. I know how to do it, it worked fine on my G1, but not on my Vibrant. I seem to remember hearing about a fix, but I searched and couldnt find it.
Basically whenever I try it, it only starts and ends, but never actually does the process, then says "Done! You should now reboot your phone."
Could someone point me in the right direction for the fix, and is it a temporary or permanent one?
mine does the same from recovery, but when I look in files I see the fix permissions file there.
It doesn't show a status bar or anything. After you do it see if you have the "fix permissions" file on the root of your SD.
Are you manually doing it in an emulator? If you use clockwork to fix it will give you a graphical display of what it's doing.
Don't blame me, blame my keyboard's autocorrection algorithm.
The "fix"
thegreatcity said:
I see some people advising people to fix permissions, but mine has never worked. I know how to do it, it worked fine on my G1, but not on my Vibrant. I seem to remember hearing about a fix, but I searched and couldnt find it.
Basically whenever I try it, it only starts and ends, but never actually does the process, then says "Done! You should now reboot your phone."
Could someone point me in the right direction for the fix, and is it a temporary or permanent one?
Click to expand...
Click to collapse
It seems ROM manager is not looking in the correct place for the packages.xml, or at least the packages.xml file in not where ROM Manager expects it. The fix is simple, copy the current packages.xml to the right place. Everything works after that. You will need to do this each time you want to run fix permissions...
Copy, not Move /dbdata/system/packages.xml to /data/system/packages.xml
You can do this with Root Explorer, or in ADB.
Run fix_permissions, then reboot.
Go back and delete the /data/system/packages.xml if it remains after the fix_permissions reboot. My experience has been that the file is removed on it's own after the reboot.
Hope this helps.
I am a noob.
what does fix permission do? was is the purpose of doing a fix permission?
thanks,
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
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!
HELP!!
When i was running the RGUI ROM (JB) there was a fix zip to use in CWM to fix the 'Media' drain in the battery.
This worked wonders! So i just tried to flash it to my device again, except now i'm running the 'Anonorom' ROM.
It worked. Or flashed without error anyway.
The problem now is that since the reboot, the 'Fonts' have failed to be picked by my apps.
This is most noticibly with UCCW. The widget i created for the homescreen uses about 5 different fonts and its defaulted to 1 default font.
When i open the widget to change the fonts back, it tells me theres only 1 font available; "Default" and that if i want to add more then to put them in 'sd:\fonts'.
I've gone back to my file manager and checked this location and there are LOADS of fonts in there still, so its not as if they've been deleted.
Clearly this is the work of the fix_mediaDrain.zip, which i now obviously regret flashing. And WHO KNOWS what other errors i will now encounter!
So my question is, other than reflashing the ROM (which would be a pain because i've also flashed the JKay framework and other things like that, and amanaged to get the phone to my liking) does ANYONE know of a kind of UNDO fix for this fix_mediaDrain.zip that i can flash.
Obviously i dont even know if it exists,im just praying, but if anyone has any ideas i would greatly appriociate it.
I'm guessing the media scanner has been stopped, or a .nomedia file has been placed in the fonts folder.
So first check if there is a file called .nomedia in this folder and if so, delete it and reboot.
If not, then get rescan media root from play and try to enable media scanner and reboot.
Report back please
slaphead20 said:
first check if there is a file called .nomedia in this folder and if so, delete it and reboot.
If not, then get rescan media root from play and try to enable media scanner and reboot.
Report back please
Click to expand...
Click to collapse
Firstly, thanks for your reply..
I've checked the location for a '.nomedia' file and no it does not exist.
I even checked 'Root Explorer' incase the file was hiddenin my regular file manager. Still nothing.
I downloaded the 'Rescan Media Root' app, which looked successful, but didnt fix my issue.
I tried a different app called 'media Rescan Lite', but that too did not fix the issue.
It's not looking good for me is it?
well the obvious path note really is to post in the Rom thread/contact dev and find out what the file does and how it can be reverted, let me know if you don't have enough posts and I will post link to your dilemma for you
slaphead20 said:
well the obvious path note really is to post in the Rom thread/contact dev and find out what the file does and how it can be reverted
Click to expand...
Click to collapse
I have contacted the developer of this fix to ask what it does exactly and if theres any way to undo the fix.
I have also added a post to the thread where this fix was first suggested to me in the past, incase anyone there might be able to shed some light on it..
I will post my findings once i ear back from anyone incase anyone else ever has this problem...
Thanks again.
SOLVED!!
I have managed to fix this problem!
This is going to sound RIDICULOUS but.....
I renamed the 'Fonts' folder on my sdcard slightly.
I say 'renamed', but all i did was make the filename all lowercase, creating "fonts" instead of "Fonts".
Then, IMMEDIATLY, the fonts on my widget wer back to normal..!
How very odd that this was changed by the 'fix_mediaDrain.zip' throgh CWM + reboot.
AndyGalaxy said:
I have managed to fix this problem!
This is going to sound RIDICULOUS but.....
I renamed the 'Fonts' folder on my sdcard slightly.
I say 'renamed', but all i did was make the filename all lowercase, creating "fonts" instead of "Fonts".
Then, IMMEDIATLY, the fonts on my widget wer back to normal..!
How very odd that this was changed by the 'fix_mediaDrain.zip' throgh CWM + reboot.
Click to expand...
Click to collapse
well solved :thumbup: