I need help ps3 Affected by RSOD

Joonie said:
I bricked more than 300 times on my NOR on E3 flasher, don't worry about it's being damaged, anyways

you just need to use whatever NOR dump that's available to use with RSOD bypassed CFW, then initiate the fixing process via lv2diag OR RSOD homebrew, I wouldn't recommend linux method since you will need a lot more time researching how to get that setup unless you're just curious about it.
Click to expand...


1 - So I remove "Spansion Nor" the card with RSX faulty.
2 - I remove the Nor from the card with RSOD DYN-001
3 - Solder the "Nor Spansion" of DYN-001.
4 - E3Flasher install and create a dump to check if everything is working properly. tristate soldered.
5 - Old dump nor with Rsod. Ps3 patch checker dump.
6 - I write the NOR dump with RSOD previously.
7 - Install CFW 4.80 FERROX noRSOD
8 - Install CFW 4.80.1 Rebug noRSOD noBD my created with MFWBuilder
9 - FSM start
10 - Rsod fix
11 - FSM OUT.
12 - install Rebug 4.80.1 REX


Could I confirm if I have to follow these steps.
What are the steps taken already when I changed nor samsung.
 
baileyscream said:
I think that he thinks he needs to physically adapt the e3 flasher
I don't think he realises you can dual boot to the flasher
Click to expand...

yes, I understand that you can do dual booting with E3Flasher.
Only thing is that no wilt leave on this playstation.

Then Never did a dual boot.
I could do with another HDD.
 
I noticed something that I realized just now going to run from the rebug min version check
It gives me 2.70, whereas in the old nor ever samsung was 3.40.

I wonder changing nor changes the min version.
 
Joonie said:
@smikk
@haxxxen Hi there, haven't seen you while, I've been using E3's NOR ever since I heard about NOR flash being the cause of RSOD.
Click to expand...
hi Joonie :)
had to find to myself and starting new things, so i've took some off-time.

ever since you have told me about e3nor, i am using it on my test ps3 as well. it is much more comfortable and you cannot harm ps3nor.

btw (sorry offtopic), i have changed a bit with cobra payload and moved the string to different location, since it overwrites this spu error message. my luck i was messing with this rogero payload back then, so these kind of modifications are no problem for me any longer.

oh, and if somebody wants to take the linux route with rsod-fix, i can provide all necessary files and a small tutorial. only thing needed is red ribbon 5. older ones i have not tried and the newer ones have different dmutils. i also have precompiled ps3dm-vtrm linux elf.
 
Last edited:
Solution RSOD FIX and REMARRY​

After many vicissitudes, I found the time to dedicate myself, I managed to make the Rsod fix.
I found on Ps3Hax a post in which he referred to the Condor Update 3.1.
I performed the procedure by @playerkp420 with small variations dictated by my case,

Here the post by playerkp420 procedure:
http://www.ps3hax.net/showthread.php?t=68553&page=4
Do this:

Install Rogero 3.55 downgrader from the recovery menu. This will bypass the RSOD (but not fix it), so you can do the rest to fix it.
Install RSOD fix .pkg from install package files.
Install toggle.qa.pkg from install package files.
Install Condor Updater 3.1 from install package files.

Run toggle qa from game column. It will beep 3 times and back to xmb. Hover over network settings in settings tab, press R1,R2,L1,L2,L3, and down on d-pad all at once. If you get extra icons below network settings, qa flag is enabled.
Run RSOD fix app from game column. It will beep and return to xmb.
Run Condor Updater 3.1 from game column. Follow on screen instructions to install OFW 3.55.

It will now boot without red screen error to OFW 3.55. You can install any CFW from there.
Click to expand...

I summarize a bit 'the story;

PS3 SLIM 120GB affected by RSOD with broken logic board, I have not married, and lens that does not read BD failure.
Dump the original NOR done with E3 Flasher analyzed Ps3DumpChecker build.488 reports that the playstation and Dowgradable Min 4.30 and cheched OK.

ROS0 Hash = MD5 Hash: 18C8473E69BB332C43C5EAF8EA1D3527 4.80 CEX
ROS1 Hash = MD5 Hash: 18C8473E69BB332C43C5EAF8EA1D3527 4.80 CEX

I proceed to the patch to install the CFW FERROX 4.80 STANDARD thinking they can fix it, but nothing done.
I install CFW 4.80.1 Rebug to use the Custom Tools (RSOD fix and remarry) but do not work.
So I proceed to the replacement of NOR Samsung with another Samsung doing the Flash nor the dump of the PS3 in question. But the problem is not resolved Rsod is always present.
Therefore it assumes that the VTRM is bad but not detected by PS3DumpChecker.

After performing various Rosd fix also via dongle and noFSM not solve, except with the following procedure:

Step 1:

Downgrade to 3:55 and run the DeHash installing Official Firmware 3:55 to 2 times from the Recovery Menu.
Install CFW 3.55 Rogero Downgrader RSOD_b67747f529d047d63151786544a58b50.PUP
You can also use any CFW 3.55 Downgrader with RSOD Fix.
Here Link:
https://mega.nz/#!f5kzDTjY!4l4RTzZLSJexNQmrqjWs7phJAn-4qQQtmQWFNpgry6k​

Step 2:

Remarry BD logic board:
For remarry procedure I used the FSM (FACTORY SERVICE MODE) with dongle, the only one that worked in my case, uses the following files:
Lv2diag.self (in/out), manufacturing_updater_for_reset.self , fdm_spu_module.self
PS3UPDAT.PUP OFW 3.30 CEX (optional, because we're not going to install any firmware.)
cfg / standalone.cfg (Already configured to only perform remarry).
Click to expand...

The important thing is the married logic board, as it allows us to launch homebrew, otherwise we will freeze, and black screen.

I attach the files to remarry 3.55 and RsodFix Condor Updater 3.1 ( thank you a @bguerville, Condorstrike , @playerkp420 )
Here Link:
https://mega.nz/#!XwEjSR7D!i9xcF823tYWYdIm2phG4arK54QVMP8Pxb6hEQlWpwPI
​
Remarry guide for 3.55 firmware:

Insert the root of your USB key files mentioned above is present in the folder remarry 3:55 BD of 'zip archive.

Put the service mode JIG/dongle/PSGrade / E3 Card Reader into port 0 (closest to the reader) and get into factory service mode.

Put the created USB Mass Storage device from previous step into port 0 (closest to the reader) and run.

Drive Init Executing means it is starting the remarry process
Drive Init Failed with big pink letters 'NG' (No Good!) means the process failed. Most likely solved by fixing the communication issue with the drive.
​
After you run the initial remarry process, do not take it out of factory service mode.

Put a BD movie disc in and run it on the PS3. (This restores your DRL files!)
If the BD works otherwise we skip the step.
Swich off Ps3.

Swap version Lv2diag.self (out) into Usb Key, and put into port 0, start ps3 for out from Factory Service Mode.

Launch as normal.​
Rsod Fix With Condor Updater 3.1:

Form XMB install the following Homebrew:

Install RSOD fix .pkg from install package files.
Install toggle.qa.pkg from install package files. (not necessary if activated).
Install Condor Updater 3.1 from install package files

Install Multiman or Rebug Toolbox (optional installation, you are only required to make a dump Nor with OFW 3:55 Firmware for verification of VTRM, with Ps3DumpChecker)

Run toggle qa from game column. It will beep 3 times and back to xmb. Hover over network settings in settings tab, press R1,R2,L1,L2,L3, and down on d-pad all at once. If you get extra icons below network settings, qa flag is enabled.
Run RSOD fix app from game column. It will beep and return to xmb.
Run Condor Updater 3.1 from game column. Follow on screen instructions to install OFW 3.55.

It will now boot without red screen error to OFW 3.55. You can install any CFW from there.

Install 2 times the firmware SONY OFW 3.55 Recovery Menu to make the DEHASH.
Now the ps3 boot without RSOD, we will finally have a start of XMB without any mistakes, both in Savegame and trophies.
If you have previously installed Multiman we can make a DUMP of the NOR.

RSOD FIX, but the VTRM is still partly incorrect.
Code: 
********************************************
PS3 Dump Checker v1.0 (Build: 488)
Check started: 15/11/2016 19:40:07
********************************************
19:40:07 : Reading image into memory and checking statistics...
19:40:09 : Statistics check skipped!  (nothing to check)
19:40:09 :  Binary check Started!
19:40:09 : Binary check for 001.02  First Region Header Magic Started...  Result: OK!
19:40:09 : Binary check for 002.01  Flash Format String Started...  Result: OK!
19:40:09 : Binary check for 002.02  Flash Format Version Started...  Result: OK!
19:40:09 : Binary check for 003.01  Flash Region Table Header Started...  Result: OK!
19:40:09 : Binary check for 003.02  asecure_loader Offset - Length Started...  Result: OK!
19:40:09 : Binary check for 003.03  asecure_loader Name Started...  Result: OK!
19:40:09 : Binary check for 003.04  eEID Offset - Length Started...  Result: OK!
19:40:09 : Binary check for 003.05  eEID Name Started...  Result: OK!
19:40:09 : Binary check for 003.06  cISD Offset - Length Started...  Result: OK!
19:40:09 : Binary check for 003.07  cISD Name Started...  Result: OK!
19:40:09 : Binary check for 003.08  cCSD Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.09  cCSD Name Started...  Result: OK!
19:40:10 : Binary check for 003.10  trvk_prg0 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.11  trvk_prg0 Name Started...  Result: OK!
19:40:10 : Binary check for 003.12  trvk_prg1 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.13  trvk_prg1 Name Started...  Result: OK!
19:40:10 : Binary check for 003.14  trvk_pkg0 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.15  trvk_pkg0 Name Started...  Result: OK!
19:40:10 : Binary check for 003.16  trvk_pkg1 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.17  trvk_pkg1 Name Started...  Result: OK!
19:40:10 : Binary check for 003.18  ros0 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.19  ros0 Name Started...  Result: OK!
19:40:10 : Binary check for 003.20  ros1 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.21  ros1 Name Started...  Result: OK!
19:40:10 : Binary check for 003.22  cvtrm Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 003.23  cvtrm Name Started...  Result: OK!
19:40:10 : Binary check for 004.01  asecure_loader Header Started...  Result: OK!
19:40:10 : Binary check for 004.02  metldr Offset Started...  Result: OK!
19:40:10 : Binary check for 004.03  metldr Length Started...  Result: OK!
19:40:10 : Binary check for 004.04  metldr Name Started...  Result: OK!
19:40:10 : Binary check for 004.05  metldr RevKey Started...  Result: OK!
19:40:10 : Binary check for 004.06  metldr Binary Size Started...  Result: OK!
19:40:10 : Binary check for 005.01  eEID Header Started...  Result: OK!
19:40:10 : Binary check for 005.02  EID0 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 005.03  EID1 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 005.04  EID2 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 005.05  EID3 Offset - Length Started...  Result: OK!
19:40:10 : Binary check for 005.06  EID4 Offset - Length Started...  Result: OK!
19:40:11 : Binary check for 005.07  EID5 Offset - Length Started...  Result: OK!
19:40:11 : Binary check for 005.08  EID0 IDPS0 Started...  Result: OK!
19:40:11 : Binary check for 005.09  EID0 IDPS1 Started...  Result: OK!
19:40:11 : Binary check for 005.10  EID0 Static Started...  Result: OK!
19:40:11 : Binary check for 005.11  EID2 BlockSize/Padding Started...  Result: OK!
19:40:11 : Binary check for 005.12  EID3 Static0 Started...  Result: OK!
19:40:11 : Binary check for 005.13  EID3 Static1 Started...  Result: OK!
19:40:11 : Binary check for 005.14  EID3 Static2 Started...  Result: OK!
19:40:11 : Binary check for 005.15  EID5 IDPS0 Started...  Result: OK!
19:40:11 : Binary check for 005.16  EID5 IDPS1 Started...  Result: OK!
19:40:11 : Binary check for 005.17  EID5 Static Started...  Result: OK!
19:40:11 : Binary check for 006.01  cISD Header Started...  Result: OK!
19:40:11 : Binary check for 006.02  cISD0 Offset - Length Started...  Result: OK!
19:40:11 : Binary check for 006.03  cISD1 Offset - Length Started...  Result: OK!
19:40:11 : Binary check for 006.04  cISD2 Offset - Length Started...  Result: OK!
19:40:11 : Binary check for 006.06  cISD1 IDLog Header Started...  Result: OK!
19:40:11 : Binary check for 006.07  cISD1 Semistatic 1 Started...  Result: OK!
19:40:11 : Binary check for 006.08  cISD1 Semistatic 2 Started...  Result: OK!
19:40:11 : Binary check for 006.10  cISD1 Static Started...  Result: OK!
19:40:11 : Binary check for 006.11  cISD1 Semistatic 3 Started...  Result: OK!
19:40:11 : Binary check for 006.14  cISD2 Started...  Result: OK!
19:40:11 : Binary check for 007.01  cCSD Header Started...  Result: OK!
19:40:11 : Binary check for 007.02  cCSD Entry Table Started...  Result: OK!
19:40:11 : Binary check for 008.01  trvk_prg0 SCE Started...  Result: OK!
19:40:11 : Binary check for 008.02  trvk_prg1 SCE Started...  Result: OK!
19:40:11 : Binary check for 008.03  trvk_pkg0 SCE Started...  Result: OK!
19:40:11 : Binary check for 008.04  trvk_pkg1 SCE Started...  Result: OK!
19:40:12 : Binary check for 009.01  ROS0 Header Started...  Result: OK!
19:40:12 : Binary check for 009.04  ROS1 Header Started...  Result: OK!
19:40:12 : Binary check for 010.02  cvtrm0 Header Started...  Result: OK!
19:40:12 : Binary check for 010.04  vtrm0 Magic Started...  Result: OK!
19:40:12 : Binary check for 010.05  vtrm0 Reserved Entries Started...  Result: OK!
19:40:12 : Binary check for 010.07  cvtrm1 Header Started...  Result: FAILED! Offset: 0xEE0000
53 43 45 49 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 00 FF FD FF FF FF FF FF FF FF FF FF FF
00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
Actual data: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
19:40:12 : Binary check for 010.09  vtrm1 Magic Started...  Result: FAILED! Offset: 0xEE4000
Expected data:
00 00 00 00 56 54 52 4D 00 00 00 00 00 00
Ascii Value:  VTRM
Actual data: FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Ascii Value: ??????????????
19:40:12 : Binary check for 010.10  vtrm1 Reserved Entries Started...  Result: FAILED! Offset: 0xEE4028
Expected data:
00 00 00 00 00 00 02 09
Actual data: FF FF FF FF FF FF FF FF
19:40:12 : Binary check for 011.02  Second Region Header Magic Started...  Result: OK!
19:40:12 : Binary check for 011.03  Second Region Header Count Started...  Result: OK!
19:40:12 : Binary check for 011.05  Second Region Unknown Block 0 Started...  Result: OK!
19:40:12 : Binary check for 011.07  Second Region Unknown Block 1 Started...  Result: OK!
19:40:12 : Binary check for 013.01  CELL_EXTNOR_AREA Header Started...  Result: OK!
19:40:12 : Binary check for 014.01  bootldr0 Started...  Result: OK!
19:40:12 : Binary check for 014.02  bootldr1 Started...  Result: OK!
19:40:12 : Binary check for 014.03  bootldr Rev key Started...  Result: OK!
19:40:12 :  Data check Started!
19:40:12 : Data Statistics check for 004.07  metldr Statistics Started...  Result: OK!
19:40:12 : Data Statistics check for 005.19  eEID Statistics0 Started...  Result: OK!
19:40:13 : Data Statistics check for 005.20  eEID Statistics1 Started...  Result: OK!
19:40:13 : Data Statistics check for 006.13  cISD1 Statistics Started...  Result: OK!
19:40:13 : Data Statistics check for 014.04  bootldr Statistics Started...  Result: OK!
19:40:13 :  Hash check Started!
19:40:13 : Hash check for 009.02  ROS0 Hash Started...  Result: FAILED!
Actual data: MD5 Hash: 4853885368E6A601BF11945EE5E3F944
19:40:13 : Hash check for 009.05  ROS1 Hash Started...  Result: OK!
19:40:13 :  ROS Version check Started!
19:40:13 : ROS Version check for ROS0 Started...  Result: OK! (480.000)
19:40:14 : ROS Version check for ROS1 Started...  Result: OK! (355.000)
19:40:14 :  Repetitions check Started!
19:40:14 : Repetitions check for Header Magic0 Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for Header Magic1 Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for asecure_loader Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for eEID Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for cISD Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for cCSD Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for trvk_prg0 Repetitions Started...  Result: OK!
19:40:14 : Repetitions check for trvk_prg1 Repetitions Started...  Result: OK!
19:40:15 : Repetitions check for trvk_pkg0 Repetitions Started...  Result: OK!
19:40:15 : Repetitions check for trvk_pkg1 Repetitions Started...  Result: OK!
19:40:15 : Repetitions check for ros0 Repetitions Started...  Result: OK!
19:40:15 : Repetitions check for ros1 Repetitions Started...  Result: OK!
19:40:15 : Repetitions check for cvtrm Repetitions Started...  Result: OK!
19:40:15 :  Data Match check Started!
19:40:15 : Datamatch for: bootldr size Started  Result: OK!
19:40:15 : Datamatch for: per console nonce Started  Result: OK!
19:40:15 : Datamatch for: CELL_EXTNOR_AREA Hash1 Started  Result: OK!
19:40:15 : Datamatch for: CELL_EXTNOR_AREA Hash2 Started  Result: OK!
19:40:15 : Datamatch for: metldr size Started  Result: OK!
19:40:15 : Datamatch for: vtrm0 Started  Result: OK!
19:40:15 : Datamatch for: vtrm1 Started  Result: OK!
19:40:15 : All is OK!
19:40:15 :  Data Fill check Started!
19:40:15 : Data Fill check for: 001.01  First Region Header 0x00 Filled Area 0 Started! Result: OK!
19:40:15 : Data Fill check for: 001.03  First Region Header 0x00 Filled Area 1 Started! Result: OK!
19:40:18 : Data Fill check for: 002.03  Flash Format 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 003.24  Flash Region Table 0x00 Filled Area Started! Result: OK!
19:40:18 : Data Fill check for: 004.08  asecure_loader 0x00 Filled Area Started! Result: OK!
19:40:18 : Data Fill check for: 005.18  eEID Region 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 006.05  cISD0 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 006.09  cISD1 0xFF Filled Area 0 Started!  Result: OK!
19:40:18 : Data Fill check for: 006.12  cISD1 0xFF Filled Area 1 Started!  Result: OK!
19:40:18 : Data Fill check for: 006.15  cISD 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 007.03  cCSD 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 010.01  Pre cvtrm 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 010.03  cvtrm0 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 010.08  cvtrm1 0xFF Filled Area Started!  Result: OK!
19:40:18 : Data Fill check for: 011.01  Second Region Header 0x00 Filled Area 0 Started! Result: OK!
19:40:18 : Data Fill check for: 011.04  Second Region Header 0x00 Filled Area 1 Started! Result: OK!
19:40:18 : Data Fill check for: 011.06  Second Region Header 0x00 Filled Area 2 Started! Result: OK!
19:40:18 : Data Fill check for: 011.08  Second Region Header 0x00 Filled Area 3 Started! Result: OK!
19:40:18 : Data Fill check for: 012.01  unreferenced area 0xFF Filled Started!  Result: OK!
19:40:18 : Data Fill check for: 013.02  CELL_EXTNOR_AREA 0x00 Filled Area 0 Started! Result: OK!
19:40:18 : Data Fill check for: 013.03  CELL_EXTNOR_AREA 0x00 Filled Area 1 Started! Result: OK!
19:40:18 : Data Fill check for: 013.04  CELL_EXTNOR_AREA 0x00 Filled Area 2 Started! Result: OK!
19:40:18 : Data Fill check for: 013.05  CELL_EXTNOR_AREA 0x00 Filled Area 3 Started! Result: OK!
19:40:18 : Data Fill check for: 013.06  CELL_EXTNOR_AREA 0xFF Filled Area 0 Started! Result: OK!
19:40:19 : Data Fill check for: 013.07  CELL_EXTNOR_AREA 0x00 Filled Area 5 Started! Result: OK!
19:40:19 : Data Fill check for: 013.08  CELL_EXTNOR_AREA 0x00 Filled Area 6 Started! Result: OK!
19:40:19 : Data Fill check for: 013.09  CELL_EXTNOR_AREA 0xFF Filled Area 1 Started! Result: OK!
19:40:19 : Data Fill check for: 014.05  bootldr 0xFF Filled Area Started!  Result: OK!
19:40:19 :  SKU List check Started!
19:40:19 : SKU Model: CECH-20xx (DYN-001)
19:40:19 : All checks (138 Checks) have been completed after 11 Second(s) and 448 Millisecond(s)
Bad count: 4 of 138 Tests  Result: Failed!

The partial VTRM correct the error, like this:

I installed the Rebug 4.80.1 REX on OFW 3:55, and I performed the Utility of the XMB Network "CUSTOM FIRMWARE TOOLS" specifically RSOD FIX and REMARRY.

I tested a Game with trophies it all works.


thank you @littlebalup , @Joonie , @kozarovv, @aldostools , @baileyscream , and thank very much @playerkp420 and CondorStrike, and Thank all user not cited.


@STLcardsWS Is possible to Sticky.​
 
Last edited:
So, to sum up, in order to fix both issues correctly, you had to remarry the logic board first then fixed RSOD. Am I right? You fixed it at the end?


Sent from my iPhone using Tapatalk
 
Joonie said:
So, to sum up, in order to fix both issues correctly, you had to remarry the logic board first then fixed RSOD. Am I right? You fixed it at the end?


Sent from my iPhone using Tapatalk
Click to expand...
Yes, Remarry old metod, after rsod fix in two step
 
smikk said:
Yes, Remarry old metod, after rsod fix in two step
Click to expand...

If you still have the partial VTRM error on your NOR dump, I suggest following.

1. Update your PS3 to the latest OFW 4.81
2. Log in to PSN and Activate your PS3
3. Try syncing trophies
4. Reinstall OFW 4.81
5. Dump the NOR see if you have correct dump.

I had the same problem but this method fixed my error on VTRM
 
Joonie said:
If you still have the partial VTRM error on your NOR dump, I suggest following.

1. Update your PS3 to the latest OFW 4.81
2. Log in to PSN and Activate your PS3
3. Try syncing trophies
4. Reinstall OFW 4.81
5. Dump the NOR see if you have correct dump.

I had the same problem but this method fixed my error on VTRM
Click to expand...

The partial VTRM correct the error, like this:

I installed the Rebug 4.80.1 REX on OFW 3:55, and I performed the Utility of the XMB Network "CUSTOM FIRMWARE TOOLS" specifically RSOD FIX and REMARRY.

I tested a Game with trophies it all works.
 
smikk said:
The partial VTRM correct the error, like this:

I installed the Rebug 4.80.1 REX on OFW 3:55, and I performed the Utility of the XMB Network "CUSTOM FIRMWARE TOOLS" specifically RSOD FIX and REMARRY.

I tested a Game with trophies it all works.
Click to expand...

If you make a new dump with e3 or multiman and run it in the validator again then the vtrm areas now pass or are they still showing any errors
If you can check then we all know for sure if the vtrm has been fully restored or just patched to get passed rsod


Sent from my iPhone using Tapatalk
 
@smikk
If you can check what baileyscream told you to in your vtrm areas & report. I am actually interested in the findings as am not entirely sure about the rsod fix feature from mysis that you just used.
If you cannot for some reason it's ok. [emoji6]
 
baileyscream said:
If you make a new dump with e3 or multiman and run it in the validator again then the vtrm areas now pass or are they still showing any errors
If you can check then we all know for sure if the vtrm has been fully restored or just patched to get passed rsod
Click to expand...

@baileyscream, @bguerville
I made the Flash dump with multiman, and I ran the validity check, no errors in Vtrm Area.

I'm comparing the various dump effected during the fix procedure, in the next few days I will post the comparison results.
 
You must log in or register to reply here.

Similar threads

Back
Top