1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Question First time installing CFW on PS3 running OFW 3.55

Discussion in 'PS3 - Modding & Hacking' started by Dameon, Mar 19, 2015.

  1. Dameon

    Dameon Newbie

    Joined:
    Mar 19, 2015
    Messages:
    4
    Likes Received:
    1
    Trophy Points:
    1
    I've been reading up on various forums (mostly psx-scene and ps3hax), but was unable to register on either. I assume they aren't accepting new registrations at this (or any other) time. I have extensive console modification experience including XBOX, Wii, PS2, and XBOX 360. This is my first foray into the PS3. It actually looks fairly easy, according to the guide provided here, but I wanted to ensure I'm safeguarding myself as much as possible. My primary goal is to be able to copy my OEM games onto an external, USB connected, hard drive so I don't have to keep swapping discs between games. I don't have any desire to play burned discs, nor do I utilize the PSN (although I'd prefer not to remove that as an option). Ultimately I would like to install a larger internal hard drive (1TB?) and use that in place of the external drive. Maybe I should do that from the beginning? I have nothing I care to save on the PS3 at this time.

    My plan is as follows:

    1) Obtain a method to either back up my current OFW or otherwise obtain the 3.55 OFW release. I want to be able to revert back to "square one" for whatever reason. The how-to linked above had a link to 3.55 OFW, but it appears to be broken at this point.

    2) I also want to dump my eEID root key before proceeding in case I ever need it for whatever reason. I intend to use "eEID_RKDumper_(3.55).pkg (69 kB)".

    3) I intend to use CFW "HABIB 4.70 CFW V1.00". Everyone seems to have their own favorite, but this one sounds as though it will serve my needs.

    4) I've heard discussions from both sides on which firmware update method to use: Through the menu (using the typical OEM method) or using "Recovery Mode". I'm still undecided. I would think the Recovery Mode would be the safest (no open files ala PC updates), but menu mode might have better checks and balances.

    Please enlighten me to the potential error of my ways. Thanks.
     
    Last edited: Mar 19, 2015
    waleed likes this.
  2. Eisherz

    Eisherz Active member

    Joined:
    Nov 28, 2006
    Messages:
    2,831
    Likes Received:
    33
    Trophy Points:
    78
    For your step 2 you need to be on a custom firmware, so you can't use it before proceeding. Also step 1 is not realy neccessary, because you can't realy go back to 3.55 official firmware, there is a way to downgrade to a 3.55 custom firmware if you did something wrong. You could theoretically downgrade to 3.42 (if you're not on a slim) and then install 3.55 again, but that downgrade is beyond risky even on phat consoles.
     
  3. Dameon

    Dameon Newbie

    Joined:
    Mar 19, 2015
    Messages:
    4
    Likes Received:
    1
    Trophy Points:
    1
    Thanks for the reply Eisherz.

    I was organizing my files to prepare for this and I did observe that the eEID dumper is a .pkg file that I obviously can't install on OFW. I guess I'll skip that step as I doubt I would ever install a developer (DEX) firmware.

    I am a bit curious why I wouldn't be able to "recover" (while on CFW) to 3.55 OFW. The installation of the 3.55 OFW (which I was able to locate and MD5 hash verify) shouldn't "verify" anything on the current flash before installing itself. Maybe I just don't completely understand the Sony flashing methodolgy.
     
  4. Eisherz

    Eisherz Active member

    Joined:
    Nov 28, 2006
    Messages:
    2,831
    Likes Received:
    33
    Trophy Points:
    78
    The firmware checks which firmware is already installed on a PS3 and you can only install a firmware higher than the one already installed to the PS3. If you're on a higher (custom) firmware you can't install 3.55, otherwise downgrading would be piece of cake. I have never tried installing the same firmware version like the one already on the PS3, but as far as I know that doesn't work aswell (it gives some message claiming that the firmware is already installed on the PS3), but I could be wrong on this. It's pretty much like the PSP, if you have any experience with that PS3 is the same.
     
  5. Cyprien

    Cyprien Active member

    Joined:
    Nov 2, 2003
    Messages:
    2,050
    Likes Received:
    1
    Trophy Points:
    68
    firmware is only part of the problem.... the main culprit is syscon.... that chip is the main driver behind the ps3 boot chain..... syscon knows the lowest firmware you can downgrade to and the only reason on dex you can downgrade at your own leisure its because dex firmware does not touch syscon while flashing but i digress...

    going from 3.55OFW to 3.55CFW to 4.70CFW should be logical.... also root key dumper works on higher firmwares

    http://store.brewology.com/ahomebrew.php?brewid=228
     
  6. Dameon

    Dameon Newbie

    Joined:
    Mar 19, 2015
    Messages:
    4
    Likes Received:
    1
    Trophy Points:
    1
    Excellent information. Thanks for the responses.

    "syscon" must be analogous to soft fuses. Once you get to a certain level, there's no going back. I am a bit surprised the CFW trips this fuses, but that may be due to the Sony flashing process, NOT the CFW itself. Sony sees the CFW as a "valid" 4.70 OFW due to some kind of spoofing by the CFW. As far as the Sony flashing application, it is flashing 4.70 OFW and trips the soft fuses (i.e. updates the WORM EPROM flash) appropriately.

    The root key is the same regardless of FW installed? It must be more strictly hardware than I thought. I've read reference of having to go from 4.70 CFW to 3.55 CFW, dump root key, then move to DEX. Based on your statement, that doesn't appear to be the case.

    The process I ended up following (which worked great) was:

    1) Started with 3.55 OFW. Used OEM Backup utility to FAT32 16GB USB drive in port 0 (front left port). Didn't have much I cared about really. Primarily I didn't want to have to re-type my username and define theme settings.

    2) Powered down PS3. Installed 1TB hard drive.

    3) Copied CFW (newest Habib Starbucks) to same FAT32 16GB USB drive from my PC. I observed my backup directory on USB drive.

    4) Powered up PS3. It displayed that it couldn't complete boot due to missing system software. Asked to insert media with update, to which I plugged the FAT32 16GB USB drive in port 0. It located the firmware (labeled as 4.70, which gave me a bit of concern) and seemed to install and update fine.

    5) After it completed, and rebooted, I had to restore my profile from USB, which also went fine. I then installed the multiMAN .pkg from the root of the same USB drive (it HAS to be in root, not a subdirectory) which went fine.

    This was all done while disconnected from my network and with no disc loaded. I didn't want the PS3 to accidently grab a newer OFW from elsewhere. Since then I've copied, and successfully tested, three retail games onto my 1TB internal hard drive.

    Questions:

    1) Is there a way to kill the stupid "Windows startup music" from the multiMAN boot? Seriously? Windows? I was able to locate the setting for the techno beat music that plays after the startup music and disabled that.

    2) I assume the way the multiMAN works is that it virtually mounts games from its interface and then kicks you back to the OEM desktop to run them? If not, I have something configured incorrectly. If so, is there a way to configure a single "click" interface to games on the internal hard drive... more typical of USB Loader on Wii or Freesstyle on 360?

    3) I am not able to connect my PS3 to the Internet (rural area, no DSL/Cable), so I am going to have to update game covers manually. I do most of my Internet functions at the local library. I can download the 3D .png covers from various sources and copy them to my PS3 via FTP, but I'll have to research where they need to go. Not sure if they go to dedicated cover directory (like Wii) or as a "cover.png" in each game directoy like 360. Worse case scenario would be a database, in which case I'd have considerable hoops to jump through to import them.
     
  7. Cyprien

    Cyprien Active member

    Joined:
    Nov 2, 2003
    Messages:
    2,050
    Likes Received:
    1
    Trophy Points:
    68
    most of the 4.xx cfw have qa flag built in... its a way to reset the syscon info to a lower state of 3.55 or lower.... at that point you can go back to 3.55 using recovery but whats the point.... 4.xx cfw is the better option... as for the ps3 seeing the cfw as valid... there's a reason why we use 3.55 as a base... we use private keys to sign the cfw sadly we don't have higher private keys that are based on 4.xx.. so we sign any cfw even if its 4.70 with 3.55 keys.. this way we can only use 3.55 as base...

    the root key will always be the same it does not change each ps3 has its own key... you can always move to DEX by using rebug the tool box the comes with it can convert CEX to DEX.. heres a tutorial http://www.ps3hax.net/showthread.php?t=76528 you can go from habib 4.70 to rebug 4.65 and do it that way i don't think both cfw will conflict....

    the kick back to XMB thing all managers on the ps3 do this... the habib cfw comes with cobra correct? if it does you can use webman as kinda 1 click tool... you can actually see if webman is loaded.. top right corner should say "webman loaded" at the boot of the system... if the cfw comes with it built in you should see "webman games" in the game column it can load psp/ps1/ps2/ps3 games make sure you use the proper dirs when loading psp/ps1/ps2 games PSPISO PSXISO PS2ISO they have to be at root of the hdd or usb.... for ps3 games either use FAT32 GAMES dir or if you use usb NTFS then PS3ISO dir.. or just on the internal drive on DEV_HDD0/GAMES...

    you can use this http://store.brewology.com/ahomebrew.php?brewid=258 to get cover packs
     
    Last edited: Mar 22, 2015
  8. Dameon

    Dameon Newbie

    Joined:
    Mar 19, 2015
    Messages:
    4
    Likes Received:
    1
    Trophy Points:
    1
    More excellent information! Concise answers that I spent a lot of time seeking out via searches, but was unable to obtain clean, trustworthy, responses.

    I'm just happy that I can play my games without the discs. I shudder at the thought of having to replace my aging BD-ROM drive. Plus the speed I gain on game load times is well worth the effort. Not sure if I'll even bother with installing emulators for PS1/PS2 games. There weren't any games from that era I was addicted to.

    Thanks again!
     
  9. Cyprien

    Cyprien Active member

    Joined:
    Nov 2, 2003
    Messages:
    2,050
    Likes Received:
    1
    Trophy Points:
    68
    on a final note cobra IS the emulator :3 multiman and webman are the same i mean the do have the MAN in them lol they both load PSP/PSX/PS2/PS3 games and as i remember correctly webman can also load from network
     

Share This Page