Hacking Gateway update regarding rumors

  • Thread starter Thread starter gamesquest1
  • Start date Start date
  • Views Views 79,129
  • Replies Replies 472
  • Likes Likes 7
ok maybe it is not a right move from gateway (although I think it was only ment for the clone card producer, to give them a hell lot of work for cloning, and somehow the cloners got lucky), but people are only pointing their fingers to gateway. This is also the fault of the cloners, they sell their product and they failed in releasing a good update. In fact Gateway didn't release anything that would brick your 3ds (if you are going to mess with the launcher, the launcher won't even start). The R4 team released something that bricks the 3ds's
 
ok maybe it is not a right move from gateway (although I think it was only ment for the clone card producer, to give them a hell lot of work for cloning, and somehow the cloners got lucky), but people are only pointing their fingers to gateway. This is also the fault of the cloners, they sell their product and they failed in releasing a good update. In fact Gateway didn't release anything that would brick your 3ds (if you are going to mess with the launcher, the launcher won't even start). The R4 team released something that bricks the 3ds's


100% true. R4/3DSLink released fcked update. They are responsible for the bricks. All cone users should blame them.
 
lol at people saying they want definitive proof that gateway bricks consoles on purpose when proof was clearly delivered. Feel free to enjoy the timebomb product from gateway.
 
lol at people saying they want definitive proof that gateway bricks consoles on purpose when proof was clearly delivered. Feel free to enjoy the timebomb product from gateway.
i dont know about you but i trust gateway 150% the problem only happens if you modified with your launcher i haven't done any of that and my gateway works fine idk but didn't come up to anyone if that yellow dude is really working for Nintendo or something? he didn't release very much and really hasn't shared nothing just had pics up
 
100% true. R4/3DSLink released fcked update. They are responsible for the bricks. All cone users should blame them.
Really?

According to you then, a manufacturer of a bullet designed to be safe in certain gun would not be responsible if they deliberately engineered that bullet to explode in the equivalent gun from a competing company?

If, as seems likely, Gateway designed this code to deliberately brick people's consoles (and their past warnings would seem to suggest this was a plan) then they have crossed the line from concerned owner of code to vandalising their competitor's customers. How can they EVER be trusted completely again to not repeat this for whatever reason, even triggering it against their genuine customers? If Nintendo discretely and anonymously offered them say $1 million how can anyone be sure they wouldn't do this to everyone?
 
  • Like
Reactions: NEP
i dont know about you but i trust gateway 150% the problem only happens if you modified with your launcher i haven't done any of that and my gateway works fine idk but didn't come up to anyone if that yellow dude is really working for Nintendo or something? he didn't release very much and really hasn't shared nothing just had pics up
It was already stated multiple times that you can brick your 3DS if your SD card gets corrupt or the launcher.dat wasn't downloaded correctly.
 
ok maybe it is not a right move from gateway (although I think it was only ment for the clone card producer, to give them a hell lot of work for cloning, and somehow the cloners got lucky), but people are only pointing their fingers to gateway. This is also the fault of the cloners, they sell their product and they failed in releasing a good update. In fact Gateway didn't release anything that would brick your 3ds (if you are going to mess with the launcher, the launcher won't even start). The R4 team released something that bricks the 3ds's
Gateway did release something that bricks consoles though.
Even though it doesn't target their own userbase, they were the ones who actually wrote the culprit code, and as such they are responsible.
Clone cart users weren't even the only people affected!
People such as Keylogger, who only used Normatt's (not for profit) region-free mod for playing out-of-region retail titles were also hit.
Perma-bricking any users for any reason whatsoever is just a terrible shit-thing to do. I don't think it justifiable.
 
  • Like
Reactions: NEP
It was already stated multiple times that you can brick your 3DS if your SD card gets corrupt or the launcher.dat wasn't downloaded correctly.


No. It was stated multiple times that GW has a sanity check to prevent corrupted Launcher.dat from even loading at all. So even if you download was corrupt, it won't run at all.

The patches by Normmatt and R4i/3dsLink neutralize the sanity check, and they got burned by this
 
No. It was stated multiple times that GW has a sanity check to prevent corrupted Launcher.dat from even loading at all. So even if you download was corrupt, it won't run at all.

The patches by Normmatt and R4i/3dsLink neutralize the sanity check, and they got burned by this


So its safe to use original gateway with original launcher.dat or should I replace it with 1.2-Launcher.dat?
 
So its safe to use original gateway with original launcher.dat or should I replace it with 1.2-Launcher.dat?


It's safe. I am using 2.0b2 just to show people how safe it is. If it gets bricked then I will come back and post it right here :)
 
No. It was stated multiple times that GW has a sanity check to prevent corrupted Launcher.dat from even loading at all. So even if you download was corrupt, it won't run at all.

The patches by Normmatt and R4i/3dsLink neutralize the sanity check, and they got burned by this
In case I missed it, surely you can point me to the post where this was proven?
 
  • Like
Reactions: cateater1
Gateway did release something that bricks consoles though.
Even though it doesn't target their own userbase, they were the ones who actually wrote the culprit code, and as such they are responsible.
Clone cart users weren't even the only people affected!
People such as Keylogger, who only used Normatt's (not for profit) region-free mod for playing out-of-region retail titles were also hit.
Perma-bricking any users for any reason whatsoever is just a terrible shit-thing to do. I don't think it justifiable.

i disagree, and i dont think justifiable Because all those carts were made for piracy, so in the end somebody end's up screwed anyway.
And again, gateway didn't release normatt's patch, normatt did. Again gateway made their code safe for their users, if you are going to screw with that code something bad can happen, but the persons who released that code should check it.

it is a duck move, sure. But so is downloading games and ripping money of the game developers. And that also people who only wanted to use it for region free were affected that is a shame, but not their fault either, I am not going to buy a gun, rebuild it to a hair dryer and when i accidentally hurt myself i am gonna blame the gun factory... (ok this is a little bit drastic, but get my point). I also understand that people are getting pissed of about the fact that they put a code to brick a console on purpose in their launcher, but then don't use it and wait for a full release instead of a beta (so other people will test it first and find out, like now)
 
i disagree, and i dont think justifiable Because all those carts were made for piracy, so in the end somebody end's up screwed anyway.
And again, gateway didn't release normatt's patch, normatt did. Again gateway made their code safe for their users, if you are going to screw with that code something bad can happen, but the persons who released that code should check it.

it is a duck move, sure. But so is downloading games and ripping money of the game developers. And that also people who only wanted to use it for region free were affected that is a shame, but not their fault either, I am not going to buy a gun, rebuild it to a hair dryer and when i accidentally hurt myself i am gonna blame the gun factory... (ok this is a little bit drastic, but get my point). I also understand that people are getting pissed of about the fact that they put a code to brick a console on purpose in their launcher, but then don't use it and wait for a full release instead of a beta (so other people will test it first and find out, like now)

At the very least they could have issued warnings such as "Modifying our code will cause irreparable damages to your 3DS", I know we did put such a warning back when we had our "anti-ps3news" message in M33 (a psp custom firmware), and even then it wasn't an active bricking code, we just used the message as a key for our modules. Not to mention we provided the users with a way to unbrick their units later on (the Pandora battery). You can't recover from a corrupt eMMC controller, at least not without very good soldering skills and the right hardware.
 
  • Like
Reactions: frown and NEP

Site & Scene News

Popular threads in this forum