PS3 The Console Killer Strikes Again, Equipment Banned Slim with Evilnat 4.88.2

Perpetual_Noobness

Perpetual_Noobness

Forum Noob
Anyone can just chime in on this one, I don't see what more harm I can possibly do to my $350.00 paperweight/doorstop of a machine, a PS3 Slim formerly charged with Rebug Rex, banned during the 4.88 raid, and then given a labotomy with Evilnat's 4.88.2. This thing has been a pain in my arse since the day I took it out of the box. It sits on its stand, watching me play GTA5 on a beatup old refurb PS3 Superslim loaded with HEN, and it mocks me. It lurks around the house at night hiding all the phillips screwdrivers. It didn't hide them well enough, because I've done it again. I got the wise idea to put another hdd in it, and try out HEN on that console, keeping the CFW with all my other data safely put away to be reinstalled when I have finished my experiment. So, I did it, and HEN works, but it doesn't do anything at all for the equipment ban. It's still banned, and still useless to me right now, if I can't get online with it. So, when I put my CFW HDD back in the console, it doesn't boot up. No cranking up, no prompt, nothing. What have I done? How can I fix it without losing everything I paid for with hard earned money I could've just flushed down the toilet? Surely, we are in the latter days. I'm up to my neck in idiot s#!t.
 
In order to unban your console, you need to get a clean IDPS (preferably from a dead console, same model as yours) and replace it.

Changing HDDs or using HEN instead of CFW, even installing OFW, won't unban it.
 
Going online with HEN or CFW enabled you run a ban risk. What really sucks is if it is in fact banned you lose games bought with the system for PS5, PS4, PS3, PSP & Vita.

Try logging in with a PC browser and see if you can do so. If not your account and system is banned. Always mount game offline then disable syscalls and finally log into PSN but even then it is not 100% safe.

The cat and mouse we have to do in order to play online. I lost literally thousands of dollars due to a ban. I no longer go online with my CFW system. I was able to get all the PS3 games back using PSN Patch but still isn't the same.
 
Yep. Been there done that. Hey Atreyu, I know you probably help hundreds, if not thousands of people here and possibly elsewhere as well, so saying "Hey, Remember me..." is rather redundant, but yes I have done all of the above. After the 3rd IDPS washed with no results, I stopped blowing money on them, The new 4.88 seems to have changed some of the dynamics of how that whole thing works in the guts of the console. I know very little about the inner components, but I do know there is a motherboard, sisterboard, and the EID in there that can also contain and store information (such as the IDPS) and I have given up trying to beat that. It's not really the ban that's troubling me. It's the HDD. I seem to have either wiped it, or bricked my console by trying to run hen on a different HDD then putting the original HDD back after I was done. I know in hindsight, it was a terribly stupid thing to do, but nevertheless, I did it. I had no idea that it was going to cause this dilemma, or I would've just went to bed. Stupid internet went out in the middle of a GTA game, and I was bored. So, for those who don't know what happens when I'm bored, hello! My name is Perpetual_Noobness. Been here on multiple occasions with all sorts of screw-ups that I caused for myself (and for you guys) to try and work out. All this in the space of about 8 months.
 
PS3s are relatively inexpensive these days. I don't understand why folks don't just have a dedicated unmodded PS3 and a permanently offline modded one. I've personally had this sort of setup for years.
 
tktagmedia said:
PS3s are relatively inexpensive these days. I don't understand why folks don't just have a dedicated unmodded PS3 and a permanently offline modded one. I've personally had this sort of setup for years.
Click to expand...
Not necessarily. My PS3 cost me a good chunk of my salary, and another will be an investment. And yes, nearly all PS3s in my locale go for the same price if not higher. Not really worth it.
 
banned during the 4.88 raid
Click to expand...

Not directed to just the OP but just in general about these ban waves / raids claims that are made.

There is no such thing as a ban wave or a 4.88 raid......
Its simply you raised a flag and were banned.. if there was waves or raids of bans.
Then you would see anyone and everyone who logged into PSN on a modified console banned.
We simply do not see that. MANY people including my self have connected to PSN from a CFW enabled PS3.
Since firmware 3.41. So not sure why i manage to escape all those waves and raids.

Anyone can say they were banned and claimed it was a ban wave
Then it just takes a few user who were banned because they did something wrong and believe that is why it was without no information but someone's self theory (alot of time can be novice users) with nothing to back it up. I bet there was an influx of bans on 4.88 but this because many are updating and/or installing the new stuff and many of those will do something they should not of that raise a flag and depending on what it was they can be banned on the spot or it may be flagged for review and you may be banned. There is going to be the most new people and the most exploited system connecting after a firmware update. So it makes sense you see more "reports" of people being banned, your going to have way more people connecting and using PSN wrong on modified system . So if they do not even know how to use PSN on an exploited system HOW accurate can those reports be... Just something to think about.

Sony has the same detection always, they do not turn off and on the "switch" to say okay they can come on this week but we are going to check hard after.. NO that is not how it works..

You have tried 3 IDPS, did you obtain them yourself or did you purchase them through someone you found online.
Alot of those people who sell them sell the same IDPS over and over and if you have various console or even one other with the same one. There is ALL sorts of flags that can raised. If you and another console online at the same time, if someone else was running homebrew apps while online. or anything that an official unit would not do on PSN.. Really that is the secret to not get banned, is using PSN as if was a unmodified console.. Can a ban still happen? Of course we do not know 100% anything (no one does) but we have more of an educated guess and more so then just random people coming to a conclusion there was some wave. Waves MAKES ZERO SENSE when you really step back and look how they would fight it. If they had something that worked they wouldnt turn it on and off lol.. Think about it....

Edit: Also using IDPS is not fullproof either, that in itself can raise flags, Because if your on a fat and have a slim IDPS for example.. My guess sony knows a bit about how they assign IDPS's . You might get it to work, but how long will it work? Then if you bought randomly online your never going to really know what happened because you really do not know if that IDPS was exclusively given to you

Edit 2: When are the most IDPS going to be sold? When a new firmware update comes. WHen is a scammer going to try and capitalize If they are selling same IDPS.? Could there be user's who are selling this and putting out false info to scam others? ... BTW there is a reason we do not allow the sale of IDPS here.
 
Last edited:
OK, I've read my post over and over and nowhere in this post have I asked for anything to do with fixing the ban, or how it happened, or anything of that nature. I'm not trying to be a smart-arse, just a little frustrated that this post has been on here for a very long time relative to how fast I've been helped before, and while I do appreciate your input, really I do, it hasn't addressed the issue which I will explain one more time. Keeping away from any other subjects in order to avoid confusion, what happened was I removed the HDD from my console (the model is slim cech something) anyway, the data on the HDD is fine. I have removed the HDD before, without a hitch. What I did next is where the problem comes. I took a totally different HDD and reformatted it so that it was clean. I put the current OFW on it, then I installed HEN version 3.0.3. I wanted to see if it would run HEN any more efficiently than my superslim. I ran into the same problems as before, even though it does run HEN quite well, I still was unable to get online with it. So, I removed the "test HDD" and replaced it with the one I removed that was loaded with all my homebrew and CFW. The console would not even boot up. Black screen. Nothingness. Several tries yielded the same result again and again. Can you tell me what happened and if it can be fixed? Please. Thanks.
 
From what i know, ps3 consoles have one registered hdd as current and you can't swap between two or more. Slim ps3s have nor flash memory which means the entirety of OS is kept on the hdd. Currently your console has the Hen disk registered and cannot recognize the cfw hdd. I think it makes total sense.
 
SpyroMancer said:
From what i know, ps3 consoles have one registered hdd as current and you can't swap between two or more. Slim ps3s have nor flash memory which means the entirety of OS is kept on the hdd. Currently your console has the Hen disk registered and cannot recognize the cfw hdd. I think it makes total sense.
Click to expand...

It's true. The HDD info (serial number, model and size) is stored in the xRegistry.sys file.
 
Perpetual_Noobness said:
OK, I've read my post over and over and nowhere in this post have I asked for anything to do with fixing the ban, or how it happened, or anything of that nature. I'm not trying to be a smart-arse, just a little frustrated that this post has been on here for a very long time relative to how fast I've been helped before, and while I do appreciate your input, really I do, it hasn't addressed the issue which I will explain one more time. Keeping away from any other subjects in order to avoid confusion, what happened was I removed the HDD from my console (the model is slim cech something) anyway, the data on the HDD is fine. I have removed the HDD before, without a hitch. What I did next is where the problem comes. I took a totally different HDD and reformatted it so that it was clean. I put the current OFW on it, then I installed HEN version 3.0.3. I wanted to see if it would run HEN any more efficiently than my superslim. I ran into the same problems as before, even though it does run HEN quite well, I still was unable to get online with it. So, I removed the "test HDD" and replaced it with the one I removed that was loaded with all my homebrew and CFW. The console would not even boot up. Black screen. Nothingness. Several tries yielded the same result again and again. Can you tell me what happened and if it can be fixed? Please. Thanks.
Click to expand...
Not every contributor has the knowledge necessary to answer all questions, people do what they can in their own time, they don't have to & sometimes it can be better to wait a couple of weeks for elaborate answers than immediately get a lot of advice that won't help you.
In any case, you can only get frustrated with yourself or potentially with people who may owe you something, I doubt that any of our contributors owe you anything therefore I see no reason for you to vent your frustration with us so let's move on on that front & put an end to any further argument.

Assuming I understood what you did, correct me if I am wrong, I think the problem is quite simple & not related to the hdd being uniquely registered or whatever.

HDD1 was removed with a 4.88 Cobra CFW installed on it.
Then
HDD2 was used to install HFW or in other words OFW (HEN makes no difference here).

So basically now the CoreOS files (lv1/lv2 etc..) stored in the NOR chip are OFW files.
So when you are trying to reinsert HDD1, it should not even try to load Cobra stage2, it loads an OFW kernel which cannot run the modified system files installed on the disk like VSH & the rest of it making the system crash before the XMB gets a chance to load.

If you had installed another 4.88 CFW on HDD2, you would probably not have experienced any problems swapping hdds which may explain why you didn't experience issues in a past hdd swap attempt, but in order to swap 2 HDDs with different firmware versions or like in this instance CFW/OFW, the situation is more complicated, the only possible way out is to use a tool like the PS3 Toolset to patch CoreOS before swapping HDD.
In your case, you would have needed to keep a OFW 4.88 ROS dump & a Evilnat 4.88.2 Cobra CFW ROS dump then use them as patch to apply the appropriate CoreOS with the Toolset whenever you change the HDD.
You could ask someone you can trust to do a good job to dump a Evilnat 4.88.2 CoreOS with the PS3 Toolset & send it to you so you can try to get back to your orignal CFW setup with hdd1 & see if that works OK.

Alternatively, it's quite possible that patching your CoreOS with the PS3 Toolset using the standard 4.88 patch would make it possible to start your console with HDD1 but I cannot guarantee it, neither can I guarantee the degree of risk involved for the HDD1 contents (no brick risk in theory though but system asking for hdd reformatting might be in play) in this operation.
It is all at your own risk as always..

I haven't really confirmed how well these Toolset based swaps would work out & whether or not other changes might be necessary to avoid hdd reformatting or whatever, because after numerous posts mentioning the possibility, there has been no interest at all for such a feature so far so I focused on other things.
That's why making/using custom ROS dumps as patch file are features only available in strict mode off in FMM, to make it clear to the user that there are risks involved in those operations that the Toolset will be unable to prevent.

Hopefully this post answers your questions & gives you possible options.
 
Last edited:
[Assuming I understood what you did, correct me if I am wrong, I think the problem is quite simple & not related to the hdd being uniquely registered or whatever.

HDD1 was removed with a 4.88 Cobra CFW installed on it.
Then
HDD2 was used to install HFW or in other words OFW (HEN makes no difference here).]

BINGO! That's it my friend. That is the problem. When I inserted the blank HDD (HDD2), I had to format it using the console, because I have no SATA cable. This 100% explains the behavior of the console when I attempt to crank the CFW HDD with that console. I reverted the core back to OFW when I set up HEN. Son of a me. Why didn't I see that? That's what you guys are for. That has to be it. So, basically I am at square one with that core, but I should be able to jailbreak it with another HDD in it, because I want the one I formatted to stay the same for now, in case the jailbreak is futile. Correct me if I am wrong, but I can still run the HEN HDD on any console, but the CFW hdd will only run on the Slim that it came from, since my other console is a super slim. So in theory, if I re-jailbreak using the toolset online, (including the dump/patch for EvilnatOS) install CFW to the core just as if it had never been tampered with, it should work. Right? I am going to finish re-reading your post to be sure I am not missing anything before I move forward with it. But THANK YOU.Whether this works or not, you have helped me greatly. This gives me a place to start from. Whereas before, I was lost. I do apologize for seeming a bit flustered, there was no harm or offense intended. Thank again, to everyone for your time and input.

EDIT:ONE LAST QUICK QUESTION TO ANYONE WHO CARES TO ANSWER. CAN I PATCH THE CORE WITH THE 4.88 TOOLSET WITH THE CURRENT HDD STILL RUNNING HEN IF IT IS ONLY THE CORE THAT IS BEING PATCHED, OR SHOULD I CHANGE TO A DIFFERENT HDD TO AVOID THE RISK?
 
Last edited:
Perpetual_Noobness said:
[Assuming I understood what you did, correct me if I am wrong, I think the problem is quite simple & not related to the hdd being uniquely registered or whatever.

HDD1 was removed with a 4.88 Cobra CFW installed on it.
Then
HDD2 was used to install HFW or in other words OFW (HEN makes no difference here).]

BINGO! That's it my friend. That is the problem. When I inserted the blank HDD (HDD2), I had to format it using the console, because I have no SATA cable. This 100% explains the behavior of the console when I attempt to crank the CFW HDD with that console. I reverted the core back to OFW when I set up HEN. Son of a me. Why didn't I see that? That's what you guys are for. That has to be it. So, basically I am at square one with that core, but I should be able to jailbreak it with another HDD in it, because I want the one I formatted to stay the same for now, in case the jailbreak is futile. Correct me if I am wrong, but I can still run the HEN HDD on any console, but the CFW hdd will only run on the Slim that it came from, since my other console is a super slim. So in theory, if I re-jailbreak using the toolset online, (including the dump/patch for EvilnatOS) install CFW to the core just as if it had never been tampered with, it should work. Right? I am going to finish re-reading your post to be sure I am not missing anything before I move forward with it. But THANK YOU.Whether this works or not, you have helped me greatly. This gives me a place to start from. Whereas before, I was lost. I do apologize for seeming a bit flustered, there was no harm or offense intended. Thank again, to everyone for your time and input.

EDIT:ONE LAST QUICK QUESTION TO ANYONE WHO CARES TO ANSWER. CAN I PATCH THE CORE WITH THE 4.88 TOOLSET WITH THE CURRENT HDD STILL RUNNING HEN IF IT IS ONLY THE CORE THAT IS BEING PATCHED, OR SHOULD I CHANGE TO A DIFFERENT HDD TO AVOID THE RISK?
Click to expand...
In theory, if you patch the Flash memory with the PS3 Toolset with hdd2 mounted, you should be able to turn the console off & restart with hdd1, when you do, boot directly into recovery mode as you will still need to reinstall the CFW PUP that was originally installed on hdd1 in order to put everything back into place correctly.
 
This might sound silly but the best way to stay safe online is not to send messages especially disrespectful messages to other users ($ony is strict on that). So to avoid bans in the future just block everyone from messaging you except your friends.
 
bguerville said:
In theory, if you patch the Flash memory with the PS3 Toolset with hdd2 mounted, you should be able to turn the console off & restart with hdd1, when you do, boot directly into recovery mode as you will still need to reinstall the CFW PUP that was originally installed on hdd1 in order to put everything back into place correctly.
Click to expand...
OK my wise friends, I have patched with a different hdd altogether. I removed an hdd from an old console that had been wiped completely, so I was forced to reformat (which is what I was hoping) and I had OFW 4.88 on my flash drive to get the console to start the reformat process. All that was successful, and it has been restored to OFW 4.88 (like new) but now I am at the critical part. I have ran the toolset to prep for CFW and loaded the patch and received the checksum for ROS 0 & 1. That has checked out clean, no errors. My current status is Firmware 4.88 CEX/CEX with no Custom Syscalls. Am I ready to put my CFW hdd in yet? If not, please advise. Thanks.
 
Felt the need to revisit this post, as it has been weighing on my mind. It's amazing just how much one can learn from a simple mistake. Although this one cost me a few ROMS and a little free time, it was worth it just for the knowledge that was gained in the wake of it all. No amount of lessons learned is ever going to stop me from being inquisitive, curious, and just destructively adventurous. Like the first time I busted open my Stretch Armstrong action figure to see what was inside it, each new technology introduced will continue to gnaw at my curiosity until I see the viscous ooze inside that makes the magic on the outside. Although, some might say knowing the trick ruins the magic, I beg to differ. Knowing the trick improves the magic for the next guy. Even though Stretch Armstrong might disagree with that analogy. As long as there are those of us who press on in spite of what the discoveries may reveal, advances will go on, and the more they try to stop us, the more we will learn and try to beat them at their own game. That is what makes the industry improve. The people who break it down piece by piece. So until the eternal stalemate is reached, don't put away those screwdrivers. Happy New Year, and many more to us all.
 
Atari800 said:
@Perpetual_Noobness
Without the colorful commentary - were you playing GTAV modded and got banned?
or
you got banned prior to swapping drives?
*possibly 2 or more identical IDPS on PSN at same time triggering event
Click to expand...
Sorry to leave you hanging on so long. So I answer now, even though the issue has been resolved. The ban happened long ago, in the great battle of Black Ops 2, when a game I didn't even ask for decided it was going to snitch me out for using CFW online. Of course, then Captain Hindsight gave his not-so-helpful 2 cents worth, by telling me that I shouldn't have gone online with a modded game. But therein lies the catch 22, because the mod in question would not even work unless it was connected to an online lobby. So, in my opinion, I was setup for failure from day one, especially given my natural affinity for the curious and awe-inspiring creations that have been demonized by the very people who created them. It's like putting a huge display of chocolates out for a sales event, then getting angry because people bought them and ruined the display. I knew the risks, it was no surprise. What I did not know, however, was that there was such a ban that could not be beaten. That is the hitch in my craw. Commentary colorful enough? ;) Happy New Year.
 
You must log in or register to reply here.

Similar threads

Back
Top