Multiman for 3.55/v.01.13.00 freeze/corrupt

**ACKRIGHT2001** · 01-20-2011,08:54 PM

I installed the new version of multiman 01.13.00 the one that allows backups in 3.55. It freezes upon install and leaves a corrupted data icon iunder game in the xmb. Does anyone have anthing similar? i had to reformat my HDD, 640 Gb lost.... any way to prevent or fix? Is this the firmware or the backupmanagers fault?.

**Bretmaster5** · 01-20-2011,09:05 PM

Yeah this happened to me and this fixed it

Make sure your on Kmeaw its the best available.

**flex360** · 01-20-2011,09:05 PM

its the backup manager
mine crashed, so i wont be using that anymore

ill stick to my lv2 pkg and rogero manager

**Keelah Se'lai** · 01-20-2011,09:15 PM

Why did you reformat? All you had to do is repair file.

**atreyu187** · 01-20-2011,09:17 PM

It happens to everyone who used Hermes and now is forced to use PL3. Had the same problem BEFORE CFW as it is a permissions error not the app. So please don't listen to this non sense. Run the fix like everyone in the world told you to before you do any CFW stuff and you will be just fine. I did that and installed it on all three machines no problem. Read, read, read, and when you thought you read enough read some more. And in case you missed it all run the syscall35.pkg or lvl2-2.pkg before running multiman once and it will boot fine and never need to be run again.

**SenorPickle** · 01-20-2011,09:18 PM

Originally Posted by flex360

its the backup manager
mine crashed, so i wont be using that anymore

ill stick to my lv2 pkg and rogero manager

That's incorrect. The problem the dude was describing was a failed install; that is the result of being on the wrong CFW and trying to install the wrong formatted pkg. Example: I originally did the 3.55OFW -> 3.55 Wutangrza -> 3.55 geohot and I had trouble doing EVERYTHING. PKGs were inconsistent installing, couldn't get backups to mount (and when I did they would blackscreen, and fixing permissions did not help.

Solution: Recovery mode back to 3.55OFW, then to 3.55 kmeaw. Since I did that I've had no problems. Everything installs fine, everything loads fine, no permission issues.

**BriansNSane** · 01-20-2011,11:45 PM

I'm actually contemplating leaving my beloved 3.41/jb avr Hermes payload for the Kmea cfw. I have read as much as I possibly can and some things seem to conflict. In my case I understood the process is 3.41 ofw, update to 3.55 ofw , enter recovery mode and install Kmeaw, reboot then.... so on and so forth. You say theres a fix to run before the custom firmware for the transition from hermes payload to the built in PL3 in MM 1.13 I would like to hear more about this as I want to be absolutely sure of every step before I begin.

**SenorPickle** · 01-20-2011,11:57 PM

Originally Posted by BriansNSane

I'm actually contemplating leaving my beloved 3.41/jb avr Hermes payload for the Kmea cfw. I have read as much as I possibly can and some things seem to conflict. In my case I understood the process is 3.41 ofw, update to 3.55 ofw , enter recovery mode and install Kmeaw, reboot then.... so on and so forth. You say theres a fix to run before the custom firmware for the transition from hermes payload to the built in PL3 in MM 1.13 I would like to hear more about this as I want to be absolutely sure of every step before I begin.

It doesn't make sense to me that running the hermes on 3.41 off of a dongle makes things not work after you've upgraded. I was under the impression that the hack/patches with the jailbreak were done at boot and left nothing behind once you turn off the console.

What I have heard is that if you switch between using lv2patcher and the syscall patcher it will mess things up, but even that seems irrelevant now with the all the backup manager updates that have been released that integrate the patches.

Also, the permissions thing is a legitimate issue but shouldn't have any impact on installing. I figured the best way to upgrade was delete all my homebrew and backups before I upgraded to ensure that I had a clean slate (as leftover stuff from previous BM's, homebrew, etc. can mess things up as well).

**BriansNSane** · 01-21-2011,12:27 AM

Same here. I'm going to go ahead with the updates as planned tommorow.I'll change the folder name that my backups are in uninstall all homebrew,update in the neccessary process and install the 1.13 MM change my backup folder name back and hopefully all is well. Im going to try it without using any patchers.Like you said MM is supposed to fix permissions that PL3 had issues with and the lvl 2 patcher is sposed to be built in. Ill report back when its done.

**AmazingLarry** · 01-21-2011,03:06 AM

wow...

just use the fixpermissions package, then use gaia manager, it will automatically ask if you want to fix file permissions. do so if it asks on every game in your collection. done.

and to upgrade to kmeaw you can actually go from 3.41 straight to kmeaw 3.55 in the system update in xmb. but i have only tested that on a slim.

User Tag List

Thread: Multiman for 3.55/v.01.13.00 freeze/corrupt

Tweet

LinkBack

Thread Tools

Display


	Would you like to get all the new info from PSX-Scene in your email each day? Subscribe to our Daily Digest! Want to learn more about the team keeping you up to date with the latest scene news? Read about them now! Check out our Developer bios, too!