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,
Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
I rely on metamorph to make/test my themes, and all of a sudden, the other day, it stopped morphing. ill open up the app go to apply the theme, everything runs as normal, it will ask me to reboot. i will reboot and no changes take effect.....
i have searched for 20min now looking for answers. ive tried applying with /system mounted as r/w and r/o. ive verified my folder structure is still correct (including hdpi/mdpi etc). ive tried uninstalling/reinstalling. nothing is working.
would a kernel or lagfix affect it? thats really the only thing ive changed in the past two days.
EDIT: Ok so i think there is something wrong with /system altogether. normally, if you delete Phone.apk from /system/app, either through RootExplorer or ADB, your phone will go haywire as it is a vital app. well, just to test things out, i deleted it. nothing happened. rebooted fine. went into /system/app and verified that Phone.apk was not there. however, i could still call people!!!!! WTF?????
Thats is very odd all together, whats your current software setup?
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
Thats is very odd all together, whats your current software setup?
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
Deadhorse ovuv ulf running ext4 (nonvoodoo) lagfix....trigger v2.1.1...kb1 modem
update: so it seems like these symptoms are only happening with framework-res.apk and Phone.apk (both which ive been morphing a lot lately, im assuming its a metamorph thing). i just successfully morphed and ADB pushed Google Talk as a test. i was also able to delete thinkdroid.apk using root explorer.
so basically framework-res.apk and Phone.apk are inaccessible. even if i delete them or replace them through root explorer they are still functional or no changes occur. How in the world would this happen? How would i replace them?
PLEASE no one say "ODIN back to stock"....its the most obvious cop-out answer on this forum nowadays, we should try to figure more things out instead of leaning on ODIN all the time.
TopShelf10 said:
Deadhorse ovuv ulf running ext4 (nonvoodoo) lagfix....trigger v2.1.1...kb1 modem
update: so it seems like these symptoms are only happening with framework-res.apk and Phone.apk (both which ive been morphing a lot lately, im assuming its a metamorph thing). i just successfully morphed and ADB pushed Google Talk as a test. i was also able to delete thinkdroid.apk using root explorer.
so basically framework-res.apk and Phone.apk are inaccessible. even if i delete them or replace them through root explorer they are still functional or no changes occur. How in the world would this happen? How would i replace them?
PLEASE no one say "ODIN back to stock"....its the most obvious cop-out answer on this forum nowadays, we should try to figure more things out instead of leaning on ODIN all the time.
Click to expand...
Click to collapse
Lol no youve been around and know enough that the we both know the odin answer doesnt apply here. I think youre right thats its a metamorph issue. I was able to push custom framework-res to trigger 2.6.2 when I was doing the aosp theme. Have you tried to push the files yourself ather than letting metamorph push them for you?
Edited, ok reread your last post. Try making a flashable of the files and see if they will install that way? I also wonder if the ext4 fs your using may be causing the issue, did you try on rfs as well?
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
Lol no youve been around and know enough that the we both know the odin answer doesnt apply here. I think youre right thats its a metamorph issue. I was able to push custom framework-res to trigger 2.6.2 when I was doing the aosp theme. Have you tried to push the files yourself ather than letting metamorph push them for you?
Edited, ok reread your last post. Try making a flashable of the files and see if they will install that way? I also wonder if the ext4 fs your using may be causing the issue, did you try on rfs as well?
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
hey man thanks for responding. i tried flashabled, adb, metamorph, root explorer, nothing worked.
i dont think its ext4 causing it because im prettttty sure its happened to me before on no lagfix...my memory could be lying to me though.
I shouldve updated the OP with my solution. I ended up altering trigger2.1.1 rom so that it doesnt wipe data and doesnt flash a kernel....so when i flashed it, it effectively only replaced my system. that was the best thing i was able to do, and now the problem is gone
Master told me that metamorph once messed up his phone so he never uses it, i wonder if this is what happened to him? Aggressive morphers, beware.
so im editing the strings in SystemUI and it decompiles and builds correctly, im using textmate as the file editor.
when i try to flash it or anything it either just says 'install complete' or i get FC
im not changing anything else, but for some reason it ALWAYS messes up
anyone got an idea?
I'm pretty sure that you just make sure it's in the right SPOT, set the correct permissions, (change back from rewritable to read-only after inserting with those permissions) and reboot WITHOUT ACTUALLY INSTALLING...(using a dalvik wipe immediately after also , I'm sure.). I've had the same issues with changing 'proprietary' system apps before, and that trick has always helped me.
Edit: This is the lazy, 'Root Explorer' method, lol.
Sent from my Evo³d
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: