Hacking Trying to downgrade below 3.55 OFW from CFW. How do I do it?

JoelLouviere

Well-Known Member
OP
Newcomer
Joined
Apr 22, 2012
Messages
71
Trophies
0
XP
209
There seems to be just way too much information but no definitive information or how-to method for trying to downgrade a PS3 below 3.55, just to get it to 3.55.
I'm trying to bring my PS3 back to an OFW that's old enough that still has OtherOS functionality built-in so as to make the process of installing Linux much easier for me as well as for some sweet nostalgia. This is a 2nd PS3, so I'm not worried. The 4.82 patch that came out for OFW is making me want to experiment with the other one now that I have 2 CFW PS3s to play with.
QA flagging just doesn't want to let me downgrade to version 2.00, and FSM seems really, REALLY confusing. I can't really make out the information with what I keep seeing. FSM only lets you downgrade if you're in recovery mode or something? Will it not work UNLESS I'm on 3.55 CFW? What about OFW? does 3.55 CFW need to be used to enable QA flagging? Does the Rebug Toolbox method differ from the PKG method? There's just so much information and no one seems to have asked enough questions for my specific niche situation, so I'm finding help on forums without signing up for ones I don't already belong to.
If you say something like "why do you want to do that?" or "why bother? Just use OtherOS++?" and don't have any feedback on how to solve this problem, don't bother posting. Just tell me if it's possible or not so I can try do it or eventually give up and do the OtherOS++ route.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • SylverReZ @ SylverReZ:
    One would have to make several changes to the code to ensure that it fills the entire screen.
  • nitr8 @ nitr8:
    I went back to the old port I had previously running as it's the only one which was up to complete with sound, music, controls etc.
  • SylverReZ @ SylverReZ:
    @nitr8, How long have you worked on this port, just this year?
  • nitr8 @ nitr8:
    ...and I'm currently playing it - no crash so far. If I could, I'd live-stream
  • SylverReZ @ SylverReZ:
    Or play through it until you encounter a bug or so.
  • SylverReZ @ SylverReZ:
    You should maybe hire beta/alpha testers to playtest your game while you continue to update the port, but that's up to you.
  • nitr8 @ nitr8:
    I have been working on BLOOD for the Wii for a few weeks but that was 2 years ago until I noticed that it would randomly crash out of a sudden at some point and I never managed to find the origin of the bug.
    +1
  • SylverReZ @ SylverReZ:
    @nitr8, Something like an USB Gecko would be extremely helpful for debugging. Not sure if there might be an IDA plugin which can do this wirelessly.
  • nitr8 @ nitr8:
    That also was the reason why I never released it to the public. Which btw. is a shame because the game is basically "complete" and ready for release
  • SylverReZ @ SylverReZ:
    @nitr8, If you consider open-sourcing this, then I'm sure somebody could point out the bugs for you in the repository, such as walking through step-by-step on what it's doing.
  • nitr8 @ nitr8:
    I have 2 USB Gecko's. I'm using one for debug printout messages while I use the second one for realtime debugging within Eclipse where I make changes to the code
    +1
  • SylverReZ @ SylverReZ:
    @nitr8, Ah good, having two is always handy.
  • SylverReZ @ SylverReZ:
    Not sure why you'd want to, but it's a good thing at least.
  • nitr8 @ nitr8:
    You need two if you want realtime-debugging AND debug printout at the same time. The problem is that GDB (the GNU debugger) needs a connection over a serial port while the other one also needs a connection over a serial port. You cannot send debugging commands and printout messages over the same port. It just wouldn't work. I've tested this.
    +1
  • nitr8 @ nitr8:
    I should probably see if I can run this natively on a PC using the original commits where I pulled the code from. Basically the repository is the same but the commits were different when it comes to the main game code and the engine overlay...
    +1
  • nitr8 @ nitr8:
    BTW: I saw you mentioned me in the link to the ROTT wall bug where a moving wall exits the game map.
    +1
  • nitr8 @ nitr8:
    The original developers put an image into the code which would be shown once this bug happens. It's the one you see at the end of the video and it's also the same image I'm using as an avatar.
    +1
  • nitr8 @ nitr8:
    Anyway, I hope BLOOD will finally make it's way onto the Wii. I ported DOOM, HERETIC, HEXEN, STRIFE, ROTT and HEXEN II before years ago. I simply cannot imagine that it's too hard to get the game
    running stable.
    +1
  • K3Nv2 @ K3Nv2:
    Wut
  • SylverReZ @ SylverReZ:
    @nitr8, Okay, good luck with that. :)
  • realtimesave @ realtimesave:
    don't hide pls
  • realtimesave @ realtimesave:
    oh hi SylverReZ
  • nitr8 @ nitr8:
    If I just had the chance to live-stream the running game on the Wii... :unsure:
    +1
  • SylverReZ @ SylverReZ:
    @realtimesave, Oh, hey. I was pretty busy lol.
    SylverReZ @ SylverReZ: @realtimesave, Oh, hey. I was pretty busy lol.