The above video goes away if you are a member and logged in, so log in now!
Very Strange perm freezing situation after upgrading to latest MM - Tried everything and no fix.
Very Strange perm freezing situation after upgrading to latest MM - Tried everything and no fix. –
I have a CECHE01 phat model ps3 that I had successfully installed kmeaw 3.55 upon. After playing around with the different methods I successfully booted LBP2 that was installed via ftp from my internal HD. I was using mm 1.13.04.
When 1.14.00 came out I went to upgrade (by deleting previous install, rebooting, then installing new base pkg) and LBP2 no longer worked. I tried lv2 v4, v5 and v6 payload, and the built in syscall. Black screen, I can hear the error message beep sound, but not see it. The system then locks.
Ever since doing this, I can now no longer get my LBP2 to boot under any circumstance. All the apps appear to work, and the game gets loaded into the xmb as normal, but freeze upon launch.
Here is what I have attempted so far:
-Deleted install and restored back to original working condition, which was mm 1.13.04. Did not work.
-Delete game data
-Format/wipe everything and resent
-Fixed permissions manually and within mm(and by loading lv2 PL first)
-Tried every payload with all current BM's. thats gaia 2.04-2.06, rogero (last few releases) and mm from 1.13.01-1.14.01
-Installed OFW and went back to kmeaw CFW 3.55, then installed clean mm 1.14.01. same issue
-Using a different eboot for LBP2 thats confirmed working (despite it already working fine before on 1.13.04). Gives a error screen that I can dismiss, no lock.
Im really at my witts end. I've spent several days on this now and I have no idea what to do. It was all working fine until this update. I dont know how its even possible for anything to make such a permanent error/problem...but it seems only logical that something has been changed. I can put the system to exactly the way it was working before and it no longer works.
Any idea's or suggestions would be appreciated. I might respond that I've already tried it (and forgot to type it in the post)...because Ive done a million things to try to fix this in the past 48+ hours.
I actually had a very similar problem if not the same.
Before MM 1.14.00 I could run LBP 2 fine.
Then I tried using one of the test builds prior to the 1.14.00 release and LBP2 would not start up and kept giving me an error message code on boot (looking in google it seems the error code was related to dirty disk?).
So I reverted back to the previous 1.13 Multiman tried other backup managers yet still got the error code.
Anyways I was able to fix the problem by pressing R1 in multiman (I think it's a permission fix) then the game worked again.
However it seems you have tried that already so your problem could be different.
I have resolved the issue by using a external harddrive. I still do not know what precisely caused it, but its likely to do with FTP/directory structure or possibly transfer modes. I have to assume that there was a confliction somewhere going from 13.x to 14.x since nothing changed structurally, yet the games no longer loaded. Why the issues started becoming invasive after going back to OFW, and then CFW (with format) and re-xfering the games....I dont know. Nothing is adding up for me.
I've been using FTPRUSH with blackbox with no errors/issues. However the fact that the same game boots off external and not internal can only be a FTP client/server issue.
Any thoughts on this would be good. I would like to know what causes it so i can prevent it from future internal-hd users.
Last edited by Iriez; 01-29-2011 at 07:59 AM.