Please help me figuring out what's wrong with my console. (Trophy/debug/RSoD?)

P

PSX_Koto

Member
Specs: CECH 2504B 320 GB, 1 TB internal HDD + external
Previous FW: 4.76.1 REBUG REX
Current FW: 4.80.1 REBUG REX

Hello everyone,

(long post but I don't know what informations are helpful, so I'm just going to list everything I remember)

after wasting more than a whole week of trying to fix what's wrong with my console, I finally decided to ask here for help... I don't know what else to do at this point.

The problems started when my PS3 stopped detecting one of my external HDDs, and after rebooting from Recovery Mode it said the internal HDD was damaged or whatever and forced me to reformat it. Luckily I was able to extract all of our savegames with the eid_root_key and Aldo's HDD GUI (which was the only tool I found that allowed for extracting and restoring of folder structures, thanks for that friend).

I checked the internal disc with HDD Regenerator but no errors were found.

After that I reinserted the hard drive and installed Rebug's 4.80.1. I set it up to Rebug mode and XMB Operation Mode: Debug as usual but this time I enabled COBRA too, installed multiMAN and started restoring the savegames, made a PSN user with reActPSN and restored my RAPs etc.

Also, for the first time I was trying out webMAN MOD (nice stuff). Although I noticed a problem with the game covers; webMAN would always download the covers from web (and thus load them very slowly) instead of reading them from the HDD when Rebug's XMB Debug mode was activated. So I had to disable it, I didn't really use any of the settings there anyway so it wasn't needed.

This is where the problems started again. Suddenly, all (most) of the game would quit after displaying a similiar error regarding throphy data (which I by now have tried to delete/reset a dozen times).

The error message is:
Registration of the trophy information could not be completed.
The game will quit.
(80022D90)

Googling that, it appears to be a problem after an RSoD accured (which I never noticed happening on my console). One of the solutions was to boot into Service Factory Mode and executing the RSoD fix (all through Rebug's XMB menu). Doing that will cause the following error:
VTRM Init failed: 80010505

At this point I reinstalled Rebug 4.80.1 and I thought it had fixed some of the game errors, because I was able to load some games like Jet Set Radio now, without an trophy error.

But there is still the big issue with the Rebug XMB mode.
With the Rebug XMB Operation Mode set to Retail, the following problems occur:
- I cannot use reActPSN to 'repurchase' my games (it will copy/install the RAPs but the PS3 will not show a Buyer/Owner).
- games still have problems accessing trophy data when the Rebug Debug XMB is not selected, for example FIFA 16 will check the trophies (already installed or not) at game launch and with XMB set to 'Retail' instead of 'Debug' it will be stuck at 0% forever
- I cannot open the Trophy Collection on the XMB, pressing X and nothing happens (it only opens with debug mod enabled)

So something appearently is still very wrong and I'like to have it fixed because it causes serious problems again. But what now? I reinstalled the firmware, did a factory reset, deleted and recreated my profiles a bunch of times. I'm not sure what else I can do. If anyone has a few suggestions, please tell me. :(
 
Last edited:
PSX_Koto said:
I checked the internal disc with HDD Regenerator but no errors were found.
Click to expand...

HDD regenerator is a placebo. Check hdd with MHDD. If hdd will be fine (IMO is broken). Next in rebug toolbox check that target ID and kernel are both CEX or DEX (if one is cex other dex then is bad). I never messed with copying saves or trophies so i'm not sure you don't need to resign them (one more time IMO yes).

Now you can toggle cfw settings in toolbox and do RSOD fix from network column in XMB.

Hint from rebug site:
  • Advanced Service Tools – Entering FSM (!!!DO NOT Install FW while on FSM that may lead RSOD!!!), Remarry BD drive and RSOD fix
Click to expand...

If you have backup AND you are not using psn, you can try delete trophies by going to dev_hdd0/home/000000000x/Trophy and deleting everything inside.

For sure you should dehash your PS3 Also you can go thru 3.55 FSM to 3.55 OFW to recreate VTRM region. Now is really messed up after all this things.
Also is possible that your nor is just dying..
 
Thanks a lot for your help kozarovv!!

kozarovv said:
Check hdd with MHDD
Click to expand...

Thanks, I'm going to try that. I'm going through the rest of your post first though ;)

Next in rebug toolbox check that target ID and kernel are both CEX or DEX (if one is cex other dex then is bad).
Click to expand...

LV2 Kernel and Target Type are both shown to be CEX.

I never messed with copying saves or trophies so i'm not sure you don't need to resign them (one more time IMO yes).
Click to expand...

Saves so far worked as long as I restored them to the user with the same ID (ex. saves from user 00000001 to 0000001 but not 00000002). What program would you recommend to resign saves?

Now you can toggle cfw settings in toolbox and do RSOD fix from network column in XMB.
Click to expand...

I didn't recheck my HDD yet but as I said the RSoD fix gives me this error: "VTRM Init failed: 80010505"

This is my usual Rebug config:
System Mode: REBUG
XMB Operation Mode: Debug (because Retail breaks everything)
Debug Menu Type: CEX QA (I never touched this)
Toggle XMB CFW settings: Disabled
Toggle COBRA Mode: Enabled
Toggle PS2 Emulator: COBRA
Toggle webMAN: Enabled

If you have backup AND you are not using psn, you can try delete trophies by going to dev_hdd0/home/000000000x/Trophy and deleting everything inside.
Click to expand...

I already deleted them multiple times. Also my PSN account has been long lost because my console was banned back in 2011 or 2012, I don't remember.
Also the trophy issues happen even without any savegame or trophy data for that game.

For sure you should dehash your PS3 Also you can go thru 3.55 FSM to 3.55 OFW to recreate VTRM region.
Click to expand...

A quick google search leads me to this article.

Dehashing = Enable QA flag, downgrade to official 3.55? Is that correct?

I removed and re-enabled QA Flag in Rebug Toolbox, this should be enough? Or do I need to use the toggle_qa.pkg?
Then I can flash from my current 4.80 to the official 3.55 from FSM - or do you mean Recovery mode? Rebug warns about flashing in FSM? >It only says 'don't install cfw' in the xmb

And then I can go straight back to CFW from official 3.55, or do I need to install a 3.55 CFW first? And which one? I honestly don't remember sorry, it's been years... >reading, it helps



Thanks again and sorry for asking all these questions, but I don't want to F%$# it up completly (probably already did :p)
 
Last edited:
Alright, so I enabled QA flag, put my USB stick with 3.55 OFW in (tried both slots), booted up Factory Service Mode, and after selecting System Update via Storage Media, it would only display No applicable update data was found.

In Recovery Menu it will throw out the error "The data is currupted. (8002F2C5)".

Path is PS3\UPDATE\PS3UPDAT.PUP, CRC32=FC0B1B98/MD5=CA595AD9F3AF8F1491D9C9B6921A8C61+

I tried two different sticks, including the one I used to upgrade to 4.80 a few days ago...


Edit: I also did a NOR dump and compared it to a 4.46 one from two years ago.
They both failed three checks: ROS0 Hash, ROS1 Hash and Data Match Check.
 
Last edited:
PSX_Koto said:
Alright, so I enabled QA flag, put my USB stick with 3.55 OFW in (tried both slots), booted up Factory Service Mode, and after selecting System Update via Storage Media, it would only display No applicable update data was found.

In Recovery Menu it will throw out the error "The data is currupted. (8002F2C5)".

Path is PS3\UPDATE\PS3UPDAT.PUP, CRC32=FC0B1B98/MD5=CA595AD9F3AF8F1491D9C9B6921A8C61+

I tried two different sticks, including the one I used to upgrade to 4.80 a few days ago....
Click to expand...

I see you say "booted up factory service mode" , be careful not to mix up recovery menu and factory service mode, it could be bad. Recovery menu is what you get if you hold the power button, can be used to reinstall fw if console is semi bricked, Factory service mode requires a dongle or device plugged into the ps3 and needs the power AND eject button used and can recover a full brick on 3.55 FW or lower).

You will need to use the 3.55 downgrader pup and install from recovery, (can be got from Rebug site HERE 4th from the bottom)

Then once on 3.55 downgrader FW you could install 3.55 OFW twice to be sure. Then you could do FSM procedure with a FSM dongle or device or whatever if you have one.

At least that's what I did last time I was having weird problems and it sorted them out. :)
 
Thanks DeViL303, I was just trying to follow his instructions and he said flash OFW via FSM, but I just noticed I'm an idiot for not noticing him writing through 3.55 FSW to 3.55 OFW.. derp

I don't have any dongle, I can only access FSM through the Rebug custom xmb menu they added in their newer firmwares. What should I do?
 
Last edited:
PSX_Koto said:
Thanks DeViL303, I was just trying to follow his instructions and he said flash OFW via FSM, not flash rebug downgrader via Recovery...

I don't have any dongle, does it mean I have to go 3.55 downgrader -> 3.55 OFW -> 4.80 Rebug with custom xmb settings to access FSM?
Click to expand...

Well yes if I was you I would do both but don't do the last bit to access FSM, so install the 3.55 '999' downgrader pup > 3.55 OFW (install 3.55 OFW twice as this changes both ROS's to 3.55 from 9.99 afaik) > This is where I think you should do a FSM install of 3.55 . Do you have a CFW PSP? or there are lots of other devices like phones that can be used as a jig/dongle to get into FSM to flash 3.55 and properly restore the console to an as new condition software wise?

Its possible there are other ways to do a 3.55 FSM install that don't require any hardware, I have an E3 CARD READER so that's the way I do it.

If you don't have any way to do a FSM wipe then you could just try going back to 3.55 OFW (twice) after the 999 downgrader and then back up to Rebug 4.80 and forget about the FSM install. Its important you don't do the FSM procedure if you are on FW above 3.55 as you will end up stuck in FSM with no possible way out.
 
Last edited:
DeViL303 said:
Do you have a CFW PSP?
Click to expand...

Sorry I have edited my post.
Actually I do have a PSP-3000 with 6.61 PRO-C :)
I also have a E3 Card Reader thingie, but I have never used it - might be fake but the design looks exactly like this: https://imgur.com/jNdUDXo

Edit: I plugged the E3 into my PC and it shows two drives. I dropped the e3downgrade.bin into the 128 kb partition but after removing and pluggin it back in the file has disappeared? Its this normal?

Currently checking the PS3 hard disc for errors so I can't try out if it works right now.
 
Last edited:
PSX_Koto said:
Sorry I have edited my post.
Actually I do have a PSP-3000 with 6.61 PRO-C :)
I also have a E3 Card Reader thingie, but I have never used it - might be fake but the design looks exactly like this: https://imgur.com/jNdUDXo
Click to expand...

Ok, well then you are sorted, id say its the real thing. I have also read there is a pkg that gets you into FSM but I don't know much about that method so cant help much with it, You would need to be on 3.55 CFW to use that tool afaik so best off to use the E3 card reader as you have it.

So you need to go back to 999 downgrader FW, then 3.55 OFW twice, then do the FSM install of 3.55 OFW.

You need a few files for that, 2 of lv2diag.self . There are tutorials for that around the net like THIS one so I wont explain that too much here as there are quite a few steps. remember when installing using the dongle you put the PUP on the root of your USB stick, NOT inside the PS3/UPDATE folder like a normal install.
 
Last edited:
Thanks a lot guys, I really appreciate your help :)
I will report back once this hard drive check finishes (prolly tomorrow) and I managed to downgrade sucessfully - hopefully!
 
Last edited:
I really think the HDD is crapped out. Dehashing and HDD should fix all of your issues. Had very similar problems and this sorted to for me.
 
Alright, so I've successfully downgraded to 3.55 with the Rebug Downgrader.

From there I installed the official 3.55 via XMB two three times.

With the E3 Card Reader I activated the Factory Service Mode.
I put the first Lv2diag.self (CRC32=9338ABF2) and the OFW 3.55 PS3UPDAT.PUP into the root of an empty USB stick, turned the PS3 off, inserted the stick into the right USB port and turned it back on. The LEDs were blinking and the console started doing something but everytime I tried it the PS3 would not turn itself off (as described in the various online guides I read), instead the hard drive LED would eventually stop lighting up and the power button would blink indefinitly (I let her sit there for about 20 minutes). I pressed the power button and the console would shut down without beeping. After this I was still able to use the second Lv2diag.self and get back into normal mode.

I tried this a few times, with both my old HDD and a new one, and with two different USB sticks.

Here is my UPDATER_LOG.TXT: http://pastebin.com/xz88G1Qe
Bul-ray Disc Player Revoke done(0x8002f057)
update package elapsed time = 91889 msec
Updating or Verifying failure 0x8002f057
UpMng.UpdatePackage() failure
manufacturing updating FAILURE(0x8002f057)
Total Elapsed time = 144604 msec
Click to expand...

All the logs end with the same error.

Any suggestions?
 
Any ideas? :/

I redid all steps by upgrading to 4.80 again and downgrading back, but still getting the same error. bd drive works, usb works (installing firmwares any other way works without problems)

Online I found some people saying you need to install rogero cfw first, or at least any 3.55 cfw with peek&poke enabled, or is this irrelevant for the FSM 3.55 downgrade/reinstall method? It's all rather vague and I don't really want to try out random stuff and end up with a brick... besides the fact that most of the threads are from 2011 or so and most of the firmware and patch file links are dead...
 
Regarding hdd analysis, it's not always very clear why an internal hdd may fail in the PS3.
In the last year, I have had 2 different internal hdd failing on me with various side effects. Eventually after a while the PS3 could not even format them. (even after being checked, deleted, formatted on PC...)
In both cases, I couldn't detect anything wrong with either of my 2 hdd using various decent hdd tools to check them, including the one kozarovv mentioned in previous post.
I have been using them as external hdd ever since & they work great..
Has anyone experienced that?

Sent from my GT-I9305 using Tapatalk
 
Last edited:
OK so, I've managed to reinstall 3.55 in Factory Service Mode with a CFW called 3.55 Ferrox No-BD (link). After that, I reinstalled OFW 3.55 via Recovery Menu twice. Then I updated to Rebug 4.80.1 again.

This is what PS3DumpChecker has to say about my flash dump:

Before downgrade:
ROS0 Hash = MD5 Hash: 4853885368E6A601BF11945EE5E3F944
ROS1 Hash = MD5 Hash: 4853885368E6A601BF11945EE5E3F944
Data Match Check = vtrm0, vtrm1 failed

After:
ROS0 Hash = MD5 Hash: 4853885368E6A601BF11945EE5E3F944
ROS1 Hash = MD5 Hash: A974F88457424AC6D8E262DBF3ED7AA0 (3.55 CEX)
Data Match Check = vtrm0, vtrm1 failed

Still looking bad, huh...
 
PSX_Koto said:
OK so, I've managed to reinstall 3.55 in Factory Service Mode with a CFW called 3.55 Ferrox No-BD (link). After that, I reinstalled OFW 3.55 via Recovery Menu twice. Then I updated to Rebug 4.80.1 again.

This is what PS3DumpChecker has to say about my flash dump:

Before downgrade:
ROS0 Hash = MD5 Hash: 4853885368E6A601BF11945EE5E3F944
ROS1 Hash = MD5 Hash: 4853885368E6A601BF11945EE5E3F944
Data Match Check = vtrm0, vtrm1 failed

After:
ROS0 Hash = MD5 Hash: 4853885368E6A601BF11945EE5E3F944
ROS1 Hash = MD5 Hash: A974F88457424AC6D8E262DBF3ED7AA0 (3.55 CEX)
Data Match Check = vtrm0, vtrm1 failed

Still looking bad, huh...
Click to expand...
The 'After downgrade' dump was taken after the 4.80.1 update?
You installed 4.80.1 once only before dumping?
Shouldn't you install 4.80.1 a second time then check your dump?

Sent from my GT-I9305 using Tapatalk
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top