"free of the infamous bricking code" , is this confirmed or speculation ?
few pages back someone mentioned the bricking code is still intact and has not changed at all since 2.1
"free of the infamous bricking code" , is this confirmed or speculation ?
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.
You just need to swap the launcher.dat file is all. Nothing more than that.with this new release does the gateway cart need to be flashed ike it did with the 2.1 release ?
You just need to swap the launcher.dat file is all. Nothing more than that.
It's been more well hidden. Some hackers haven't been able to find it (yet).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.
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.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'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).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.
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.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.
It does not seem like it will pose much danger to genuine users judging by the things Slashmolder told me (specifically, this):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).
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.[07:45] <+Slashmolder> you'd have to be REALLY unlucky with bit coruption for it to trigger a brick
[07:46] <+Slashmolder> and it's not like a bitflip or two
[07:46] <+Slashmolder> it'd be like kilobytes changing (he might be exaggerating a bit about this part)
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.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.
You respond too fast I edited my post with a bit more information.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.
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.On 2.2 (at least with the games with inserted 4gb headers that I've tested) I've noticed an increase in load times and decrease in stability of games. Anyone else?
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.
Damn, so should people be waiting for gatway-dumped roms in order to ensure stability?
3DS games haven't been decrypted to any meaningful extent to allow this, so online play is safe from cheaters for now.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...
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...
well that shouldn't be a problem as long as you are only backing up your own legally purchased gamesLOL:
As always, use online play at your own risk. Since online play is linked to a genuine Game Card,
we do not recommend that multiple users go online with the same game dump simultaneously as it will most likely result in a future online ban.
We cannot help you if your 3ds console gets banned from online play.
Sorry guys, only one user at a time may go online. Where can I reserve a time window?