Lol I knew they'd use hardware flags/checks to check if the console has been exploited, simply put it this way, look at the nes the 10nes all you had to do is short a pin to ground (or send a pulse to crash the chip... sounds like rgh was first on the nes lmao) to run unlicensed code, snes improved the flaws of that with its chip, Sega did the same on the genesis, and Atari on the 7800(which was cracked because someone found the internal software used to encrypt 7800 mode games thrown out In a Dumpster iirc) then Sony and Microsoft came, these systems now have basic forms of software drm, back when ps1, Saturn, Dreamcast (mid 90s to mid 2000s) onsole manufacturing was different as they simply assume people will only try to attack software so they locked software, when that proved inefficient (freemcboot, GameCube Homebrew, and custom bios/kernel on the og Xbox), at the time they (console makers) assumed people wouldn't bother reverse engineering the hardware or wouldn't have equipment, equity (aka money), or time or level of sophistication to do so, which led to a false sense of security (other words they got lazy with how secure it should be because of false assumptions about what the specific portions of the userbase is capable of doing)
so when ps3 and Xbox 360 came around the console makers are like hey these people aren't as stupid and dumb or as as we thought, they do have the ability to Snoop around places you may think are secure, so they designed the hardware in a way where the game is (Linux terms beware) running with superuser privileges, and the hypervisor which is the only thing that will allow code to execute is running with super-superuser essentially, and the hypervisor and all security is done inside the CPU die itself none of this info ever leaves, if the security has not been broken, any information that leaves and returns to the CPU buses is encrypted and will be checked, which did prove really difficult to crack
(ps3 may have better hardware, but 360 had better security, you cant JTAG/rgh with a ti84 se ) though mostly were patched (ps3 cfw need low system software or hardware downgrade, then ps3 lvl0 signing keys were leaked which is what was used to encrypt/ decrypt system software and updates iirc).
Jtag was actually a bug in the su su mode of the hypervisor that was discovered by the king Kong exploit which this specific mode of execution was permanently patched in hardware hardware updated past xx.4552.xx, the 360 knows what updates have been installed and which kernel updates are allowed to run, this is stored physically with fuses that are manufactured into the CPU die itself that can be blown permanently, forever, which tells the cpu to react and operate differently from that point onwards.
(specifically due to how $10EC was checked by the hypervisor had a overlooked flaw and this subtle and tiny flaw simply with microsoft devs using a 64 bit cpu operation to work on 32 bits of data allowed complete takeover of the console which was done originally with a modified copy of king Kong but was replaced with jtag which simply needed some wires and hardware and software to modify the nand)
RGH is delving to electrical engineering and low level attacks now, since you're using flaws of how the hardware is built at the electronic and physical level, rgh attacks the CPU during runtime and if you put the cpu in a certain state for a very specific amount of time during it's internal encryption/signature check you can induce a bug in the silicon implementation that allows any signature/encryption check to result with a pass (code that is signed will pass while unsigned code will either crash or cause the console to detect it as the cpu will try to decrypt code thats not encrypted and turn your code into garbage and crash trying to run it or see that the code has not been signed and halt)
the nand is modified with a bios which will continue to reboot and attack the CPU until it returns a pass (rgh boots into a modified kernel based on 4532 -4548 king Kong kernel which allow the $10EC vector to be used iirc to disable the hypervisor checks and run unsigned code)
with every generation they learn like was posted earlier Microsoft, Sony, and ninty more than likely are paying people money *cough* bug bounties*cough* *cough* to read these forurms, or even exploit the console and show them the exploit so they can fix it.
usually the exploits are public and documented, Microsoft just gets them a copy of it and sends it over to their system development team where they break down the exploit and build an update that should block the mode of execution and if they're smart they'd continue to keep looking, that's how exploits are found you keep looking around and you'll eventually find something interesting. It really isn't easy at all, should say its really difficult instead and its supposed to be thats why its called security, and that's what all the 10 years olds and leeches don't understand.
Honestly all of the things that most people would use the console for is to host modded lobbies, and if you pay attention and now look at cod and these same games on xb1 you have constant game mode updates, adding new games modes, features, not to the extent of of 10th lobby kill yourself and get 4 billion xp, but if you've ever used mod menus, other than modding stats, people would just use them to fuck around with the game engine, and people did write their own game modes, (icheeeeeeeetd and cod4 were married in that sense)
What killed the modding interest are the squeakers and wannabes who got infected with a mod menu or joined someone else's modded lobby, or a dev mad someone stole you're mod menu and put their name on it and quit development, you shouldn't own a hacked or modded console, and don't charge money for it if is only about greed. I've never made a penny from any lobby I hosted and I had people offer many times to pay, because people want to play something different and its fun to fuck around with the game in such ways, because you more than likely stole the game you're modding (not everyone) they think they're an uber hacker, uh no go hack the console and come back with a working 360 softmod and I'll be impressed... plus take that derank fakie (people who just reset peoples stats as a joke is another reason I only do it to people who tried to do it to me or were the biggest ass in the lobby, those who hold a sign begging will be hit with such hammer, otherwise enjoy the FREE unlock all 10th and just fuck around about the map) and the fact that people would charge insane amounts of money and ppl that were stupid enough to waste like 100 - 200 bucks at the peak for them to host you a private modded lobby for like 1-2 hours.
its not the mods that kill the game its how people use and abuse them are who kill it, and that's why you never saw really any homebrew 360 wise, everyone wanted to mod games, not run nes games. Which is why xb1 doesn't have that support, because looking back at the modding scene for the 360 was kind of trashy and only geared toward piracy, and modding games, and i guess people dont want to associate with the greedy and crap that was there, not all of it was crap, but there was a lot of drama going in the 360 scene which died really when the RGH was released
PS I really think that alot of the ps3 and 360 hacking scene was tied to employees or now former employees of said companies or their software devs leaking sdk info and dev kits to said people who chose to reverse engineer it.
