[playerkp420]

Originally Posted by nzie so how i can downgrade with red screen while booting ps3 to xmb?(e3 flasher). or just downgrade like normal way and reFSM to use RSOD fix Lv2diag.self ?

Yeah, just downgrade normally and when you are suppose to boot to xmb, you boot to the red screen.

Then do the RSOD fix after downgrade.

I have fixed a few RSOD ps3s. But the self file fix didn't work for me. Even after the log file said it was successful, it still booted to red screen. The only way I have done it successfully, is the old way with the notheros.pup and RSOD.pkg.

[nzie]

Originally Posted by playerkp420 Yeah, just downgrade normally and when you are suppose to boot to xmb, you boot to the red screen. Then do the RSOD fix after downgrade. I have fixed a few RSOD ps3s. But the self file fix didn't work for me. Even after the log file said it was successful, it still booted to red screen. The only way I have done it successfully, is the old way with the notheros.pup and RSOD.pkg.

i see. RSODfix Lv2diag.self not working on your rsod consoles at all?

[Tokobo]

Ok, I'm very confused here.

Give you guys and overview of what I have done, probably you guys can tell me what can I do next.

I initially installed 4.10 TechnoDon's MFW, but I accidentally upgraded to 4.11 Demo firmware, after which i used the e3 flasher to backup the bios, and downgraded successfully to 3.55 Rogero v2, I made another backup of it too.

I tried to go back to 3.55 OFW via recovery mode from Rogero v2, but ended up a YLOD brick.

Since the ps3 wouldn't stay on, I soldered a GND point on the PS3 to the NOR Tristate Point and managed to flash my bios following the e3 unbricking manual, completed and got the dancing lights.

Here's my current problem, the screen remains black. I tried formatting the HDD. I tried doing the one with the patched backup and e3_downgrade.bin. Both to no avail. It is good to know that I tried to enter recovery mode, but when I pressed and hold the ps3 power button (mine's a cechk06 fat), it switches off instead of producing the beeps.

Any ideas on how to go on? =(

EDIT: All my backups are verified with flowrebuilders, so I doubt it's the backup issue =(

[euss]

Originally Posted by playerkp420 The only way I have done it successfully, is the old way with the notheros.pup and RSOD.pkg.

That is because you have defective hardware.

The lv2diag.self does exactly the same as the package. It restores cvtrm in flash.
Only the package requires you to run XMB (something you cannot use, only by hardpatching out RSOD integrity catch and risk permabrick with further damage - hence why it "worked" under Notheros only which is an improper way of fixing it, because the defective hardware is not replaced).

Originally Posted by nzie i see. RSODfix Lv2diag.self not working on your rsod consoles at all?

See above. package and lv2diag.self do the same. You can check it by dumping and checking cvtrm section.

Originally Posted by Tokobo (crossgrading + road to bricking story) I tried to go back to 3.55 OFW via recovery mode from Rogero v2, but ended up a YLOD brick.

You just need to prepatched dump and use that in fun mode for debricking. Then remove Tristate/SBE to ground. From there use normal PSgrade service mode guide with Rogero 3.1 (and try to stay away from brickpups from strange men that have bricked a handfull of their own consoles on the internets this time, and prevent using OFW without having dehashed).

[playerkp420]

Originally Posted by euss That is because you have defective hardware. The lv2diag.self does exactly the same as the package. It restores cvtrm in flash. Only the package requires you to run XMB (something you cannot use, only by hardpatching out RSOD integrity catch and risk permabrick with further damage - hence why it "worked" under Notheros only which is an improper way of fixing it, because the defective hardware is not replaced). ).

So after risking the permabrick, and its not bricked now. But working fine. Am I in the clear or is there a chance it will still permabrick?

What I mean is since it seems to be fixed now and working fine. Will it continue to be ok? Or is there still a chance it will just brick, since I didnt replace any hardware?
I did qa flag downgrade it to the minimum firmware (2.30) then updated to OFW3.55 and installed Rebug. Seems to be working like it should.
Also any idea what hardware would need to be replaced?

Thanks.

[Tokobo]

Originally Posted by euss You just need to prepatched dump and use that in fun mode for debricking. Then remove Tristate/SBE to ground. From there use normal PSgrade service mode guide with Rogero 3.1 (and try to stay away from brickpups from strange men that have bricked a handfull of their own consoles on the internets this time, and prevent using OFW without having dehashed).

Now that's the MOST clearest set of instructions I got today!

That explains why everything isn't working

Will try it later, need to sleep, work at 8.30am tomorrow (it's 2.34am here).

THANK YOU VERY MUCH!

[BoneFreak]

Hey,

Finally got my E3 Flasher up and running and made a few NOR dumps (not sure if they are good bad or otherwise but I have them) and I'm stuck at step 2.5. I Don't have a dongle so I'm using a PSP (CFW 5.50 GEN-D3) and PS3jig (V1.00). I start up the PS3Jig App plug it into my FAT PS3 (which is turned off with the switch AND the power cord pulled out) in the right hand USB slot. I then plug in and turn on the PS3 pressing the power then the eject button. The PSP screen says it received and sends a Jig challenge but it doesn't turn off, it loads up the "Connect Controller" screen.

I then turn off the console and start again and have done it about 10 times all with the same result. I've tried changing the cable between the PSP and the PS3 and also changed the memory card in the PSP still nothing. Any ideas or should I look at getting a dongle from somewhere?

[Tokobo]

euss, I used the fun mode with the backup and now I get the Plug a controller into the ps3 and press the PS button.

I tried using both ports with both my psp and TI-84 silver to no avail, out of desperation, I plugged in my controller and press the button, but nothing happened. Could it be that there's something wrong with my USB? I plugged my phone in and it was charging though.

[euss]

Imo PSPJig is the worst implementation to use as a PSgrade device, seen too many people struggle with it, that solved within 1 second they used a dedicated AVR/PIC device.

[Tokobo]

Originally Posted by euss Imo PSPJig is the worst implementation to use as a PSgrade device, seen too many people struggle with it, that solved within 1 second they used a dedicated AVR/PIC device.

Oh right, just clarifying, prepatched firmware, I'll be using my rogero backup (the last firmware I used before trying to upgrade to OFW) and patching it according to ps3devwiki right?

Really? I was just afraid I shorted something during soldering :x

EDIT: Does this mean my Ti-84 would be a better choice than my psp?