The above video goes away if you are a member and logged in, so log in now!
Rebug fake save data owner / Bruteforce save tool / Borderlands 2 save
Rebug fake save data owner / Bruteforce save tool / Borderlands 2 save –
Please bear with me for the long explanation.
I was on Rebug and I'd been playing BL2 then had an issue during a firmware upgrade that required rebuilding the database on the PS3. The database rebuilt fine and I got Rebug 4. 21 installed.
Upon restart my user and the react PSN 'aa' user both had '*' next to the names - BL2 saves wouldn't load. Being impatient, I worked around it by turning on Fake save data owner (FSDO) in Rebug 4. 21.
BL2 was the only game I played with FSDO on.
The other day I finally decided to do some research and deal with the '*' and other saves not working - I turned off FSDO, signed into PSN and activated my PS3, and tested that all of my other game saves worked - they did.
Before doing anything else I FTP'd my BL2 save and profile to a safe place.
I started BL2 and it did not see the BL2 save at all, If I remember right, it said something about the profile being corrupt, and started me out fresh with no saves. If I use the save data utility from the XMB, it shows my level 35 BL2 save.
I tried to use Aldo's PS3 Bruteforce save data tool, but not sure if I'm using it correctly, or if Rebug FSDO does something to the save and/or profile that can't be undone - Yes, I read the warnings about FSDO and I'm prepared to start BL2 from scratch if need be, but if I can salvage my Level 35 save, I'd rather do that.
I grabbed a working save from one of my other games (Deus Ex) that I'd never played with FSDO on, and had Bruteforce save data read the param. sfo from it. Then I tried re-signing the BL2 save and ftp'ing it back to the PS3. BL2 still doesn't show the save. I deleted the profile and let BL2 create a new one, then tried again - same result.
So my questions:
Does anyone know for a fact that FSDO permanently breaks your saves in some way that they can't be fixed with a save resigning tool?
There's a readme that says global. conf should have you're console ID in it. I thought that was read out from the param. sfo the first time you start bruteforce save tool - do I need to also put it in global. conf and if so, do I need to pad it with 0's?
I didn't select any special options when I resigned the save - When I load it, the profile is BLANK (the profile for my Deus Ex save has my nickname & console ID), I click Rebuild save data full and the profile changes to be the same as my Deus Ex save.
I've also tried resigning my BL2 profile - same result.
(sidenote: the post link checker that complains about no space after a period is ridiculous)
In case anyone is curious, I worked out a way to do this.
Started BL2 and let it create the new profile, started a new game. Saved as soon as I was able to.
Copied the "new" save and my "old, broken" save to my PC.
Decrypted both with Aldos tools.
Opened my broken save in Gibbed save editor, saved it over top of my "new" save.
Encrypted the "new" save which now contained my level 35 zero progress.
Copied the "new" save back to the PS3. BL2 launched and I could continue my game where I left off
And now that I've wrapped my head around the encryption/decryption tools and eboot/npdrm signers, I will NOT be turning on FSDO anymore.