Hacking Any proof GW3DS's code is deliberately malicious?

  • Thread starter Thread starter elMagnate
  • Start date Start date
  • Views Views 6,035
  • Replies Replies 30
Its confirmed now, gateway did it and not the clones, the eMMC controller was locked by a password and not by a ram writing error or what they told us before.


That actually makes a LOT of sense. Remember when they said they'd know if it was done by a clone? That's how they "unbrick", they remove the password....
 
Come to think of it, the brick does seem more and more the failed "update protection" as we get more info.

Think about it.
It bricks because they set write protection.
If you set write protection you can't modify it.
If you can't modify it, you can't update it.

It really seems like it was the failed update protection and GW decided to use it for another purpose.
 
But users of legit gateways without the region free patch are getting bricked too.
I know, which was another outcome that was surely unforeseen by the Gateway team. And it's something that will actually cost them money to fix for their customers. So if profit was their only motivation for this, let's hope they're taught a lesson by it.
 
Bricking the cart is technically just as bad as bricking the console. I could live with SD cart corruption though.

Yes, but 4.5 3DSes are discontinued while 3DS flashcards aren't.
Right now, only 4.5 3DSes can use the DS profile exploit to run Gateway. Every 4.5 3DS bricked is a 4.5 3DS lost that cannot re-appear (apart from using the recent un-bricking program for the Raspberry Pi and such, but that's very complicated for now.)

If they just bricked the clone flashcards (with them making 100% sure it wouldn't brick Gateways), then the user could just go and buy a legit Gateway instead, but since they brick the 3DS itself, the clone user can't even go and convert to a Gateway user, which is counter-productive for the GW team.

From a legal point of view, sure, they'd be destroying private property in both cases (and nobody would like having something they spent ~50-60 bucks on destroyed), but I would say that destroying clone cards instead of 4.5 3DSes would be the lesser of the two evils.
Of course, they *could* also decide not to brick anything at all, but yeah, I don't think the Gateway team would be willing to do that.
 
  • Like
Reactions: Ryukouki
pretty sure they cant brick the clone cards....if they could, im sure they would of done that
Right. There's nothing that can really be "bricked" inside a clone cart. Corrupting the SD card could have been a simple task for the GW team, though. There were alternatives. I think they simply used the failed "update blocking" code they've mentioned before to brick consoles, though, so as to save time on developing any code specific to copy protection.

It all ended up costing them more time though, which is why we're all still sitting here waiting for 2.0.
 
i think they just intended to scare people away from clones, the fact it wasn't just a 100% brick chance shows they didn't just want to brick everyone, just show the clones up and show that they are crappy coders......i think they achieved that goal but it also backfired once it was discovered it was an intentional move, then backfired even more when gateway users got hit......poor plan with poor execution......but still they can walk away with the same effect...i dont think anyone will fully trust any future clone updates, gateway just got their hands dirty in the process
 

So where's the proof Gateway caused this? Let me go buy a clone, brick my console and put my Gateway cart in a picture.

Still haven't seen 1 thread from people sending their console into Gateway. Why? They used the region free patch or a clone before hand.
 
The proof is in the fact how it's done. They issue a CMD42 on the eMMC card that locks the eMMC. It needs to be unlocked before it can be used again. This is different to the write protect command, so it's not an accidental misinterpreted write protect attempt that causes this. The procedure to lock an eMMC is not something that happens by accident as the manufacturers of those eMMC's realise very well that such is causing operation failure of the devices it's used in.
Obvious, the bricking was only supposed to happen on the clone cards. The region free patch that came out and the fact that the hashing routines weren't 100% reliable changed that. Official gateway users with the region patched launcher.dat and even some official users without that patch are having bricks as well.

I know gateway fanboys and the team itself will always deny this, as it's in their best interest.
Whenever you buy a gateway or a clone after this happened is obvious yours to decide.
If I have 2 choose between 2 products offering the same, and one of them only costs 75%, the choice is quickly made.
The fact they did came out with that bricking garbage instead of doing some serious work to improve their product makes the balance move even further away from their site.
But, I don't have a 3ds with a < 4.5 firmware and if I would buy one it would be to experiment with homebrew on it.
 

Site & Scene News

Popular threads in this forum