few pages back someone mentioned the bricking code is still intact and has not changed at all since 2.1
few pages back someone mentioned the bricking code is still intact and has not changed at all since 2.1
mathieulh says otherwise and I'll go by his word as he was one of the first hackers to even report the original bricking code's existence. The post stays unchanged unless I see conclusive evidence that the code is still there in v.2.1 Omega and v.2.2 Omega.Foxi4 don't mislead users, 2.1 and 2.2 still have the bricking code
It just won't trigger by mistake as easily.
There is in-menu bricking code as well as an in-firm check that has not been confirmed to trigger bricking code (but likely does as it's already known that the brick code still exists). Ask ichichfly, or read some of his previous posts. Other people have confirmed it as well.
EDIT: Aaaaand I think I have now.
It's been more well hidden. Some hackers haven't been able to find it (yet).
The fact they haven't found it doesn't mean it's not there. However, the fact that several people DID, including ichichfly who is on the team with smealum, Normmatt and the like, is about as conclusive as it can get. Slashmolder has confirmed it as well. Slashmolder and ichichfly may not agree on whether there is brick code in FIRM or not, but they both agree on one thing; there is bricking code in their ROP payload and it CAN be triggered, even though it's no longer likely to happen by accident. That is about as conclusive as it gets, unless you want video of confirmed bricks on GW Omega (that isn't likely to happen unless someone starts modifying GW's code or perhaps the NAND)
I've asked Slashmolder what would be required to artificially trigger the code - if we can catch it on camera, that's conclusive evidence to me that it's there. For now the recommendation has been retracted, I'm interested in how mathieulh will respond to the screencap and the marked address area where the supposed code is.
Can't you both just agree GW's firmware is under control whether or not code meant to sabotage competitors is present. It's time to put it behind us. The bad clones (3DS Link, R4i Deluxe, etc) have been essentially killed off with the FPGA update so only 2 great cards ( GW and MT ) remain.
That's not the point - before recommending Omega officially it's worth to know if the code is actually there, if it poses any danger to genuine users and if they can trigger it by an unfortunate accident or not. There haven't been any bricking cases as of late, but that doesn't mean that none will pop up in the future and I don't want to have anyone's 3DS on my conscience, regardless of whether it can be unbricked or not (and if the Masterkey has changed then it cannot).
He certainly has the means to do that - it should require nothing more than simply modifying the GW launcher a bit, which he has already decrypted. At least that is what I gather from the things he told me a few days ago when I asked about modifying the launcher to disable signature checking.
It does not seem like it will pose much danger to genuine users judging by the things Slashmolder told me (specifically, this):
But I still don't feel 100% safe knowing that, as long as the brick code still exists there will always be doubt in my mind. I think that for the flashcart to be truly considered safe (despite lingering brick code), a few months would need to pass without any reported bricks.
It's all about assessing the danger. If random SD corruption could trigger it, we have a ticking bomb problem on our hands. If it has to be a very deliberate modification then everything is fine in my book.
You respond too fast
I edited my post with a bit more information.He might be exaggerating when he says kilobytes though.
I have heard that some ROMs were becoming unstable but it was pretty much related to the scene ROMs with headers grafted onto them. I've not heard much on load times being longer though.
So far, it seems that the most stable ROMs have been those dumped using Gateway and left unmodified. The problem is that some Gateway dumped scene ROMs were "cleaned up" and the headers were removed. There are still a few out there with the header still intact, but they are few and far between.
Edit: I am not implying that all ROMs with grafted headers are unstable. I'm just saying that those seem to be the only people complaining about instability. It could be that there is no difference between the grafted and original dumped ROMs, but due to sampling error (there are way many more people grafting headers onto scene ROMs than there are dumping ROMs from carts) we see an apparent difference even though no exists.
I don't intend on getting one Gateway, but it's pretty cool they achieved online play. What brings my piss to a boil though is that this is just the beginning for f**king cheaters to start ruining online play... Why they do this?! Oh the humanity...
3DS games haven't been decrypted to any meaningful extent to allow this, so online play is safe from cheaters for now.
Edit: And the possibility of cheaters is overshadowed by the benefit of fan translations and customized ROMs, in my opinion...
For as long as there has been online gaming, there have been cheaters. And for the record, there has already been instances of online cheating on the 3ds. The first instance of cheating was the series of map exploits in Mario Kart 7 that were patched over in with the 1.1 update. The second instance of online cheating was that program that read the unencrypted wireless data from Pokemon X/Y, allowing the user to see the exact makeup of the opponent's team before the start of the battle. Nintendo found out about that one and we got update 1.2 to close the exploit. What honestly makes you believe that Nintendo won't be quick to plug any further exploits found in the online multiplayer servers?
One of the key differences between DS/Wii online services and 3DS online services is that the 3DS has taken a page out of the Xbox Live/PSN playbook: online play only works with the most current version of a given game. If we do somehow see the flashcarts contribute to online cheating--which we've already seen isn't necessary hardware for cheating---then the developer of the exploited game can simply release an update that patches the exploit and the exploit can no longer be used online at all. I foresee 3DS online cheating being a series of windows of opportunity, as opposed to the constant nuisance that it was in the DS lifecycle. The perpetual game of cat and mouse will eventually cause the 3ds cheat developers to focus primarily on offline cheating, as that kind of cheating will be less able to be detected by Nintendo.
well that shouldn't be a problem as long as you are only backing up your own legally purchased games
Similar threads
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
