[Maajid]

Right, I'm now on Rogero and everything is fine but I get 80010017 errors when I try to launch multiman (or anything else for that matter). Help?

[furtsiv]

@Cheesethief @LoboGuara
im not saying don't install rogero at all
why not playin newer games like RE6 or dishonored on 3.55 when we can do it & wait for stable CFW ??

[fisiologhik]

Sorry for not read the all 47 pages to know my question but anyone know/ test it upgrade this CFW on Rogero V3.7A 320GB SLIM PS3?
I read some users got their PS3 brick updating do this CFW, so i´m not sure if it safe.
Does anyone know?

[carldenning]

Originally Posted by LoverboySimer isnt this still a 3.55 cfw which can play 4.21 games ? 4.21cfw will be made from 4.21 pup n could be installed over 4.21ofw. But still a lot lot thanks for keeping this drm free.

think its ofw 4.21 made into a 4.21 cfw but signed with 3.55 thats why only 3.55 can install and not 3.56+ ofw

[ecliipse]

Originally Posted by furtsiv @Cheesethief @LoboGuara im not saying don't install rogero at all why not playin newer games like RE6 or dishonored on 3.55 when we can do it & wait for stable CFW ??

i totally agree with you holmns. why not experience the best of both worlds?....i think @DEFAULTDNB would agree

[bearmon2010]

Originally Posted by Maajid Right, I'm now on Rogero and everything is fine but I get 80010017 errors when I try to launch multiman (or anything else for that matter). Help?

You need the latest version which is out today: multiman 4.07.2

[syxx8]

First off, thank you to all of the "legit" devs for all of your brain busting work. I wish I had half of the programming skills you guys posses. My question is this: I own a slim ps3, model cech-2101a. I had kmeaw355 on it for a while, then I converted my system to DEX. Missing my bluray playback I converted back to CEX but I missed one step of that process and ended up with a brick/semi-brick. I then used my E3 card reader to repair the damage. Im now back on kmeaw355. Im considering updating to Rogero 4.21 cfw. Ive read in a few posts that I should dehash/reset syscon Properly. 1) Would it be safe for me to upgrade to this newer cfw being that I had to repair a dex to cex brick/semi-brick prior? 2) How would I go about it to dehash/reset syscon on kmeaw 355? 3) Would I even have to dehash/reset syscon on my ps3 being that during the process of recovering from the brick I was able to install OFW 355 with no issues at all? I know this is alot of words for a simple question but I wanted to be thorough as the consoles history may affect the process of updating to Rogero 4.21. I thank you all in advance for your assistance with this. Power to the Gamers!!

[Mirac00lix]

We can play nearly all the games until now so what is the matter of a cfw 4.21 if we can´t install it on FW 3.56+?

[dadi4168]

Originally Posted by dadi4168 Well, I think I bricked. Here's what I did: First off I have an original 60 gig fatty. One of the first 500,000 at launch. I believe I've never downgraded, and I'm on 3.55 kmeaw. First I made a nand backup with multiman. I FTP'd it to my computer. I then setup the files on the usb stick. The toggle_qa.pkg on the root and rogero's CFW under PS3/UPDATE and renamed to PS3UPDAT.PUP I ran toggle and checked it under network settings. Even though I'm quite sure I never downgraded, I did this just to be safe. All is well so far. Booted into recovery mode and chose update. Update finished and my samsung showed a blue screen. I can no longer get into recovery or anything. I thought at first it might be the video was reset, but it's totally unresponsive. Just putting this out there for others. I'm going to play with it a little longer, but it's not looking good. Looks like I need a flasher.

So, I played around and noticed a few things. One, no yellow or red light of death. My ps3 booted up, just seemed to have no video. (Blue screen) Another thing I noticed is I could plug in the dualshock and have it work, but hitting the x button turned the screen black. I also noticed I could see a quick flash of the recovery screen before it turned black. So on a hunch, I dug out my old 60 gig HDD and slapped it in, booted, and lo and behold, the system restore started. Yes!! I corrupted my 500 gig drive. So sorry for my earlier post about bricking. Think I learned my lesson here. I'm waiting for a more stable release. Not saying this firmware is not stable, I'm just not taking anymore chances. My apologies to Rogero and anyone else involved. Not that I'm blaming anyone but myself. Also, sorry for derailing the thread. Just sharing info.

[miksu123]

Originally Posted by carldenning think its ofw 4.21 made into a 4.21 cfw but signed with 3.55 thats why only 3.55 can install and not 3.56+ ofw

can we sign it to 4.21 ofw ??????