First last
Member
Hello I have flashed my ps3 slim 3xx with a 2xx exploit without backup. This procedure could fix my ps3?
With an e3 flasher you should be able to get it running again.When you say : I should have made a backup dump... I saw a tutorial to install cfw on ps3 by usb drive and I did not take any security backups from web exploit url.
My ps3 do not turn on by himself... Since it was restarted from there...
With this tutorial and E3 flasher can be solved?
is like finding out someone has HIV, then tearing off the condom and doing your business anyways. Then expecting not to test positive for HIV.
At least in this console scenario, you aren't being left with an incurable disease that will eventually cause your death.



[spammed ROFL button]Hello littlebalup, I bricked my CECH-20xx PS3 Slim by applying the ps3xploit twice, and now it gives me a YLOD every time I attempt to turn it on. I obtained a dump after my console was on CFW right before the brick. The dump I obtained before the brick appears to be identical to the dumps I am getting from my bricked ps3, which only has errors in both ROS0 and ROS1 Hash in an older version of PS3DumpChecker and no errors in the newest version (ROS0 and ROS1 Hash are ok). I have patched my dump with the "CosOFW482.bin" file and flashed it to my PS3 using an E3 flasher in "Flash Fun" mode and the help of a soldered tristate, but to no avail. The YLOD remains and I have no original OFW dump. Is it possible to recover it?
Yes, the xploit was applied to a 4.82 CFW. I flashed my PS3 twice because I switched hard drives and thought that I would need to flash it again as the new hard drive was on OFW as opposed to the 4.82.1 Rebug CFW. I have already flashed the 'pre-brick dump' that I byte reversed and renamed from 'dump.hex' to 'bkpps3.bin' and patched using PS3DumpChecker and the 'CosOFW482.bin' file, which I am sure I have flashed correctly (secure connection with clamp, 'Flash Fun' mode on flasher, no e3 flasher errors, and flashing it at the correct time.) However, I did not connect my ps3 to a tv display while flashing and simply waited 30 seconds to flash after the light was green, after it was done I soldered the wire off to test if it was unbricked, and it wasn't. Thank you so much for your time and quick response.It's not so clear what you did.
Did you applied ps3xploit on a 4.82 CFW?
If so, flashing the dump you made right before the brick should solve your issue (don't forget to byte reverse it if you use an E3 flasher).
Is possible that the dump is still bad even with recieving an "ok" from the PS3DumpChecker? The PS3 should be unbricked after flashing and turn on normally, correct?It's not so clear what you did.
Did you applied ps3xploit on a 4.82 CFW?
If so, flashing the dump you made right before the brick should solve your issue (don't forget to byte reverse it if you use an E3 flasher).
No need to patch your dump with the 'CosOFW482.bin'. Simply reverse it and falsh it back to your NOR.
Then make a new dump with your E3 right after and hex compare it with the dump you used to flash.
If it's exaclty the same, the flash has been done correctly and your console should boot. If it's not the same, you have an issue with your E3.
My patcher.py does not work ... what could be
My patcher.py does not work ... what could be