PS3 I bricked my PS3 :( what to do

what to do if i cant check check my dump an in pyps3 it shows the system cannot find the specified path

and i wanted to mention that the exploit initialization was a success but the dump took lots of time but sucess wasnt shown but on checking the usb found the dump there so is it safe to continue

could someone check my dump
 
Last edited by a moderator:
what to do if i cant check check my dump an in pyps3 it shows the system cannot find the specified path

and i wanted to mention that the exploit initialization was a success but the dump took lots of time but sucess wasnt shown but on checking the usb found the dump there so is it safe to continue

could someone check my dump
If you have an older system with nand flash it takes some time to dump the flash chips. if you never got the success message it's very possible it wasn't finished yet.
For PyPS3checker it sounds like it may be a problem with python using the standalone version of PyPS3checker may fix your problem.
 
it is nor and i tried repeatedly switchng it on and off and i waited for a long time btw if i dont want a backup can i skip this step
 
it is nor and i tried repeatedly switchng it on and off and i waited for a long time btw if i dont want a backup can i skip this step
Are you at the part where you make a dump of the flash after patching? If so the reason for making a dump and checking it before rebooting is to prevent any bricks. If you have already patched the nor then turned the system off and it still boots then it's not a problem to skip it.
 
what do u mean by patch i just pressed initialize exploitation which was a success then while i tried dumping nor it didnt show sucess but rather when i checked my usb found the dump file btw i just following steps mentioned in
 
Last edited:
what do u mean by patch i just pressed initialize exploitation which was a success then while i tried dumping nor it didnt show sucess but rather when i checked my usb found the dump file btw i just following steps mentioned in
Skip our official instructions & use YT vids at your own risk!
 
Skip our official instructions & use YT vids at your own risk!
Let me add another suggestion :)

If someobody have some doubt or problem about the procedures shown in a video... then go ask to the person that uploaded the video !
Youtube allows to write comments in the videos... thats where you should write your doubts about the video, not here because we dont know the video or care about watching it
 
Hello anyone please help me out so at first i was on rebug 4.82 cex then i converted it into dex and after that i tried installing 4.82 ita dex cfw and when the installation was complete when i booted up my ps3 it gave me the yellow light of death. im pretty sure it was because i forgot to turn on QA flag while downgrading to 4.75 ita or maybe the firmware is corrupted and ways i can fix this or do i have to fix it by using a e3 flash.
 
Hello anyone please help me out so at first i was on rebug 4.82 cex then i converted it into dex and after that i tried installing 4.82 ita dex cfw and when the installation was complete when i booted up my ps3 it gave me the yellow light of death. im pretty sure it was because i forgot to turn on QA flag while downgrading to 4.75 ita or maybe the firmware is corrupted and ways i can fix this or do i have to fix it by using a e3 flash.

Why install ITA DEX and you were on DEX when REBUG in DEX does the same thing but better? `\:confused:/`
 
Hello anyone please help me out so at first i was on rebug 4.82 cex then i converted it into dex and after that i tried installing 4.82 ita dex cfw and when the installation was complete when i booted up my ps3 it gave me the yellow light of death. im pretty sure it was because i forgot to turn on QA flag while downgrading to 4.75 ita or maybe the firmware is corrupted and ways i can fix this or do i have to fix it by using a e3 flash.
Most likely a thing for an E3 Flaher yes or it's maybe cause of a "natural death" of the system that has nothing to do with the FW
Maybe it was just a coincidence that it happened just that exact second :rolleyes:
 
Hello anyone please help me out so at first i was on rebug 4.82 cex then i converted it into dex and after that i tried installing 4.82 ita dex cfw and when the installation was complete when i booted up my ps3 it gave me the yellow light of death. im pretty sure it was because i forgot to turn on QA flag while downgrading to 4.75 ita or maybe the firmware is corrupted and ways i can fix this or do i have to fix it by using a e3 flash.

Yes, you'll need E3.
Then there are many way to fix your dump, depending if you already have a CEX backup, your ERK, or even by using a DEX coreOS.
 
even tho my firmware is corrupted would i still be able to make a valid dump with an e3 flasher ?
That is hard to answer, It depends on exactly which bit is corrupt, Think about it like this, maybe like 99.9% of your dump is not very important, what I mean by that is you can replace it with dump from another console and it will be fine, but you need to get that 0.1% (Console specific info) from your own console perfectly or it will never boot again, so if your complete dump is randomly corrupted in some places, maybe you could be lucky and still get your console specific info from it, hard to know until you dump it.

I would guess that as you only installed a PUP rather than messed up with a flasher, and that PUP completed installation, then there is a good chance your console specific information is still ok, but of course its not 100%..
 
If your firmware is corrupted, the e3 flasher will make an absolute perfect copy of your corrupted data in its entirety.
Yes, you are right, to answer his question exactly , if his firmware is corrupted then there is 100% no chance to get 100% valid dump from that chip.

but I guess that really what he wanted to know is can he fix his PS3 by dumping it with flasher, and the answer to that is hard to say and could be yes or no.
 
The problem is he was messing around with eEID (for the CEX to DEX conversion), and at that point the eEID could became corrupted

Incase is corrupted and you dont have a copy of the original (neither the EID root key to try to decrypt it in PC for repair purposes) i guess is a game over
 
The problem is he was messing around with eEID (for the CEX to DEX conversion), and at that point the eEID could became corrupted

Incase is corrupted and you dont have a copy of the original (neither the EID root key to try to decrypt it in PC for repair purposes) i guess is a game over
Yeah, amount of people who mess up their consoles over the years with DEX, most of them don't even need it in first place, getting info from youtube, or they do it for some COD mod, what a waste of consoles just to cheat in games.. I suppose it serves em right if thats why they did it, haha. One less cheater.

In this case though if he successfully was on DEX in rebug, then bricked through firmware update, does that not mean he has good chance of recovering? I mean the PUP should not have over written any console specific info should it, or at least it wouldn't normally?
 

Similar threads

Back
Top