Rebug 4.86.1 - Failed Trying to Save

K

Keydran

Member
Hello! I'm new to all this console stuff, but recently got my hands into a Jailbroken PS3 with RSOD in it. I used the modified Rebug 4.86.1 RSOD fix CFW from here: https://www.psx-place.com/threads/modified-rebug-4-86-1-lite-for-broken-ps3-nobt-nobd-rsod.28922/

Then did the FSM Lv2diag.self stuff with the file Joonie posted on the thread he links in the above link. My PS3 is working wonderfully and I got 3 games into it: Guitar Hero III, ICO and Shadow of the Colossus.

In all of them I get the same error whenever I try to save. It says its trying to save to the HDD and that I shouldn't turn my console off, then it says "Failed Trying to Save". A broken save file is created at my Saved Data Utility (PS3) folder and I can't do anything with it, just delete it.

I tried using the RSOD Fix from Rebug inside FSM and it gave me the "VTRM Init failed: 80010505" error whenever I tried it and the log printed the following:
2011-12-31 19:00:47 [xai_plugin] : ACT0 : xai_plugin_action(rsod_fix)
VTRM Init failed: 80010505

I thought my hardware was broken, therefore I went to the PS3xploit website and used the tools to do a memory dump and I'll try to upload the dump test log (which was succesful) in a response below.

Do anyone have a clue on how to solve this? Until now, the only issue I'm having is that I can't save my games and therefore can't play them.

My dump check log file content is uploaded here: https://justpaste.it/7r0fq
Also, its a CECHL01 fat PS3, if it is of any help.
 
Last edited by a moderator:
I found that the SAVEDATA folder my PS3 creates at "/home/<user id>/savedata" for my game is named as something like "_UAS_2021050501451800440603" or "_BRK_2021050501451700511261" when it should be, for GH3 as an example, something like "BLES00134GPROGRESS006Q". Any ideas? I'm thinking of loading a dummy valid save there to see if it start working, but I won't be able to do it in the next few days probably.
 
I'm not familiar with VTRM issues and limitations (there are some) but second post sounds like HDD issues. Check it's health.
 
Berion said:
I'm not familiar with VTRM issues and limitations (there are some) but second post sounds like HDD issues. Check it's health.
Click to expand...

I did not think of HDD issues cause I was able to install CFW, packages and send games to the console via FTP, even tho the 80GB HDD is certainly ancient. Is there any way to check the HDD health from the PS3? I'm afraid I don't have the cables to plug the HDD to my PC to check it's S.M.A.R.T. from there. Anyway, I'll search some old hardware and cables I have around here just in case the answer is negative.
 
Probably not (especially that those save dirs following some pattern instead of random symbols), but that's quite strange, I never heard anything about such behavior. Maybe worth a try anyway.

From PS3 there is not.

Windows 8.1 and older will ask before initialize (and of course choose to NO). Windows 10 is a living monster so I cannot guarantee that he doesn't kill it. ;p All Linux distributions are safe as HDD low level operations needs root permission and they are not aggressive toward user. Use Rufus to put on USB Linux Mint 20.1, and after boot it (You do not need to install it, it runs from RAM fine if You have more than 2GiB), install gsmartcontrol (Administration > Software Manager > search for gsmartcontrol, enter into found entry and click to green Install button which will turn into Launch button after installation). Choose HDD and on Attributes card You can see short test report (i.e Rellocated Sector Count should be zero or at least not be larger than threshold).
 
Last edited:
I'll try this when I get my hands on some cables. On this thread there's another evidence of what happens when the savedata is corrupt: https://www.gtplanet.net/forum/threads/corrupt-save-data-i-might-have-a-fix-cfw-only.196974/

You can see that he mentions the same format as I do "_UAS_2009010711505700724842". Looking at it now, it seems that is the datetime of when the corrupt save was made. My PS3 tries to make a save, fails for some reason and creates a corrupt save folder. I checked the SFO file it creates in there and the metadata seems fine. It's trully a mistery to me why this is happening and I haven't found any evidence of it happening to anyone else.
 
I just generated a broken save file:
5YD7jND

5YD7jND

Apparently it has to do with not being able to create PARAM.SFD, since a "healthy" save has a 30MB .SFD file...

Direct link to image: https://imgur.com/a/5YD7jND
 
Maybe patched/broken VTRM in consequence breaks saves handling (and if saves than probably also trophies).
 
I honestly don't know what it might be. I have zero clue. Today I formatted my HDD and reinstalled everything, still the same error.
Ran the game as BD Mirror and as external (from USB) and nothing. I think it might be a permissions issue, but I can't know for sure without some kind of logging.

Is there any way I could see logs of what's happening when it tries to save??

edit: am using both multiMan and webMan to launch games from USB or that I transferred via FTP.
 
You must log in or register to reply here.

Similar threads

Back
Top