[antgly]

Good thing I had a backup...

I'm running the latest aospCMod CM7 on my Optimus V right now. What happened was that I removed the default launcher, installed Launcher Pro, and moved it to the /system/apps area with proper permissions set, as told to me by different guides that I found.

After reboots, everything is fine... had everything set up the way I like it. For a while everything is great. Then I went to ClockworkMod Recovery mode and did "Fix Permissions" from there. After it was done and I rebooted, I was met with a ton of Force Close prompts from different apps and Launcher Pro looked like it does when you first installed it. I managed to open the Browser and it worked, but then I couldn't go back to Launcher Pro as it got killed supposedly as pressing the Home button did nothing.

Why did "Fix Permissions" screw things up?

[Liquidplacidity]

I did the same thing last night. I had constant force closes with everything. I told myself that I'd never hit fix permissions again. lol. I'm not sure why it does that though. Probably something with the default permissions being overwritten by the recovery, and it's not set right.

[antgly]

Using the fix_permissions.sh script seems to work fine though.

Terminal Emulator:
su
fix_permissions