Well i just got that screenshot now, but maybe was cached. idk.@DeViL303 that help page was updated a few hours ago for 4.84 haha
Well what areas does the patch flash? and what areas were bad..and what file was corrupt....also, this does not mean BAD dump automatically either, as my 2501 always has warnings in ROS from spoofing and it works fine. that same tool will always report my dumps as BAD
Joonie said:So, a couple of things could have saved his PS3, such as
1. Verification of hex file (which was suggested in the flash writer post).
2. Verification of patched dump before rebooting PS3 (which was suggested in the flash writer post).
Joonie said:For the time being, you need to figure out why you have the wrong file that bricked your PS3, you could already have working PS3 right now if you didn't flash that broken file. Could you please download the file again from where you downloaded ?
Joonie said:You get BAD if you use that corrupted flash_484.hex and that is expected
@DeViL303 my 2501a used to be spoofed to a 3001 and long story short, my backup has a corrupted PSID for some reason my ROS always show warnings, but flashing hex is always fine. ill see if i can find an example, i did a lot of testing lol
thanksOK, I found your problem, your flash_484.hex's corrupted and if you keep using that you will brick every PS3 that you flash that.
View attachment 16349
The one of the left is what you have, I'm not sure where you downloaded this.
FYI @esc0rtd3w
patching again with correct file or using HDD method at that point, before reboot, would be your best option , yesI've been successfully jailbraking 2 consoles without any problem. I just checked the MD5 of the patch file on USB drive and didn't bother with flash dumps, as it's actually more expensive to get a e3 flasher / Teensy than a used PS3.
Anyway, just out of curiosity, what if I patch the flash, make a dump but the dump checker reports the dump is bad? Obviously, I can't install the firmware again, which will reboot the PS3 and result in instant brick. Do I run the flash writer again with the correct patch file? This doesn't sound like a valid option either, since bad data has already been patched to flash.
patching again with correct file or using HDD method at that point, before reboot, would be your best option , yes
and then of course, re-dump to verify patch
if you get stuck in some state of disrepair, then idk of another option other than hardware flasher at that point for current tools
Don't listen the hate, @MrMario2011 is a great guy.So what your saying is, don't trust MrMario2011 at all?![]()
It is not nice to insult your fellow forum member's, in fact it is not nice to insult anyone, especially when the cause of the brick seems to be you.that muppet mislead me with steps mr my arsehole he got my ps3 bricked TODAY
I see, i just had trouble remember it, my mistake.flash_484.hex is only for those downgrable units which can't be used on 3K and 4K slims including your model.
The reason why this part can be extremely dangerous is that the flasher itself doesn't stop flashing 3K/4K models which is why we warn people and have them validate their minimum version before proceeding any further, and even after flashing, in case of situation like @shab, verification step was recommended before rebooting so he would have saved his console from bricking that was caused by corrupted hex file that he downloaded.
So, a couple of things could have saved his PS3, such as
1. Verification of hex file (which was suggested in the flash writer post).
2. Verification of patched dump before rebooting PS3 (which was suggested in the flash writer post).
and you DID NOT CHECK PATCHES?? even though you read that yourself, and just ignored it?
im all for calling out people on bad tutorials, but if you actually read what it said in the first place, you also would not be in this situation.
i personally know MrMario and he is a good guy, not out to harm anyone or their PS3. obviously the video skips a few steps that can be considered critical, but i also have skipped these steps many times without issue.
i think its a combination of some bad advice and someone not reading instructions that are clear as day on the screen!
either way, i am not condoning bad advice, but clearly this is an issue for some people, and it has been resolved with future tools to be released
EDIT:
after reading more posts, i am fairly confident that you flashed that hex file to a CFW console, mostly cause you did not know it was jailbroken. did you read the title of auction? looks like CFW to me
no way to know now, without your old dump. i would be curious to see it.
and yeah, we get it, someone on YouTube broke your PS3...but that is not the case, it was YOU that actually broke it.
any tutorial you followed would have bricked that console by flashing the 3MB patch to a Rebug or other CFW console, even though its clearly stated on exploit page to NOT USE ON CFW!
Don't listen the hate, @MrMario2011 is a great guy.
I can understand wanting to protect end users and fully support such, but condemning MrMario and other YouTuber's is not the way to go about it.
It is not nice to insult your fellow forum member's, in fact it is not nice to insult anyone, especially when the cause of the brick seems to be you.
That coming from you is f*cking hilarious, you insult more than anyone in the entire scene. piss off with your hypocritical bullshit. You have dedicated threads to insulting me before lolIt is not nice to insult your fellow forum member's, in fact it is not nice to insult anyon
Where is proof of that? We have already established that the hex was corrupt, and also we know that the step to check it is missing from the tutorial...especially when the cause of the brick seems to be you.
That coming from you is f*cking hilarious, you insult more than anyone in the entire scene. piss off with your hypocritical bullshit. You have dedicated threads to insulting me before lol
Where is proof of that? We have already established that the hex was corrupt, and also we know that the step to check it is missing from the tutorial...
So its nice you are trying to stand up for MrMario.... but its complete BS. IF this was someone else, who was not buddies with Team xploit etc, you would hang him out to dry. ffs.
All because the guys recommended this video, now you are all trying to twist every little thing said, to blame the user 100% and move all blame from MrMario for his crappy tutorial, its a joke, never thought id see the day when top scene members are defending youtube tutorials..
Its 50/50 % fault IMO, you should have researched more, and MrMario should have made a better tutorial, and members here should not be recommending any tutorial without watching it first. Even if you are friends with the uploader, verify its a good video first.I went to watch your tutorial and you never mentioned ANYTHING About checking my USB after Successfully writing to flash instead you wrote it in the description huh you were 75% of my Brick the other 25% was my corrupted file