PS3 DEX PS3 4.81 Updated to 4.82 OFW with Black screen

Zerious

Member
hello, i received my friends ps3 which is bricked i can say. The ps3 is SLIM with 4.81 rebug DEX Converted, it was then updated to 4.82 OFW and the ps3 now is in update loop,it boots only with its own HDD, with an another HDD or without stays in black screen unresponsive, nor enters recover mode. i have E3 Flasher, and i can make a dump and give it to anyone who can help me recover from this brick,i dont have a FSM Dongle nor the original dump(CEX), thanks for reading
EDIT:
ps3 shut downs after 10 seconds, soldered tristate to ground and now stays put.
Dumped nor with E3 Flasher the dump came good, is recognised as CEX and lv2kernel malfored
ROS0 is 4.82 ROS 1 4.81
 
Last edited:
Oh.pissed...did it do the full install of ofw?
Did it turn on after update?
Can you get it to xmb with original HDD ?
 
What happened after the update loop, to make it RLOD?

You should of been able to just use a spare HDD and reinstall rebug. Then put original HDD back and install rebug again. Then it would be back to normal and no data loss.
 
@playerkp420 (sup man i am mitsosg13 from ps3h.x) the machine was converted to DEX then during the installation about havingreached 70% threw an error. i rebooted and restarted installation. i can neither install from recovery or normal with a spare hdd. and if i try to enter recovery with the booting hdd throws me again on installing firmware, my guess is that machine was forced converted to CEX with the 4.82 installation and simply got bricked
 
@playerkp420 (sup man i am mitsosg13 from ps3h.x) the machine was converted to DEX then during the installation about havingreached 70% threw an error. i rebooted and restarted installation. i can neither install from recovery or normal with a spare hdd. and if i try to enter recovery with the booting hdd throws me again on installing firmware, my guess is that machine was forced converted to CEX with the 4.82 installation and simply got bricked
So your sure it has target id DEX? Because CEX OFW shouldn't even of tried to install. I guess maybe it would if kernel was still CEX? It is normal when updating to OFW from rebug to go into an update loop. Because it is patched to do so.

You checked target id in the dump you made? If DEX, then patch with DEX patches and install D-REX. But if it was CEX, recovery with a different HDD should of worked. Or just patch with CEX patches and install REX.
 
i am going to try the second, patch with ferrox 4.82 ros and flash it back, but if you remember on the other forum i had a CECH-L With same behaviour
 
I've had it happened for other customers before

You dump nor
Patch it
Flash back
Swap Hdd
Reinstall firmware
Swap Hdd back to original
Reinstall firmware

Removes the OFW install loop

That's how it's worked here many many times when people have updated and results in no loss of data
 
before OFW installation 82 (DEX) now 85 CEX
I just flashed the patched nor and now removing the tristate from ground
 
flashing the nor believe did it, because i dont get any shut down nows the problem is, i now have GLOD which i suspect the RSX as while removing the board is was halfway bent on the RSX because of thermal paste
 
before OFW installation 82 (DEX) now 85 CEX
I just flashed the patched nor and now removing the tristate from ground
I am pretty sure that installing system software can not change your target id. So it sounds like it was already CEX and the issues you have been having are from some hardware failing.
 
flashing the nor believe did it, because i dont get any shut down nows the problem is, i now have GLOD which i suspect the RSX as while removing the board is was halfway bent on the RSX because of thermal paste
So its toast unless you reball?
 
this is so bad, i fixed the flash and nor RSX Broke, i put one more ihs over it and booted up normaly.. so i guess i have soldved my issue
 

Similar threads

Back
Top