Hacking Gateway update regarding rumors

  • Thread starter Thread starter gamesquest1
  • Start date Start date
  • Views Views 79,129
  • Replies Replies 472
  • Likes Likes 7
I like that the company which exists to sell devices that can only play pirated software is complaining about other people stealing their ''hard work'' and making money from it... :P
There is a distinction there. Whether or not you can see it is a different issue.

Copying someone else's work is one thing. Copying their work, and then selling and profiting off of it while claiming it to be your own work, is entirely another.

To reiterate, not saying that that Gateway's actions were justified, just that all morality shouldn't be immediately thrown out the door simply because piracy is involved.
 
Well, thanks to some kind soul now I have all public Gateway releases to date. If you want to check whether your Gateway file is an untouched official release, here's the info.
GW_Release_1.0.zip
19,0 MB (19 983 588 bytes)
CRC32: C67864D1
MD5: E0B7530B5D9949A47627EC86512DFF5E
SHA-1: 7E5F8058E2066464488F999CEE943EA27767149E

GW_Release_1.1a.zip
19,1 MB (20 033 340 bytes)
CRC32: DE3C2EFA
MD5: EF766280C1143E58E6D98463DDB1C98C
SHA-1: AECAAC68EED8A5C759A7CF54072DFF73ED8D4AE9

GW_Release_1.2.zip
14,0 MB (14 746 834 bytes)
CRC32: 1519F9F4
MD5: 4A688ACB3C6DA27A92C71E5818868BCB
SHA-1: 4731BA8B9D2DFAD47841CEF68FD4F304DA10E1A6

GW_BETA_RELEASE_2.0b1.zip
16,1 MB (16 937 431 bytes)
CRC32: 75233963
MD5: D2EE752831FDADCE7F3CC5B42898B0AB
SHA-1: F911782FA2CF1400A6AE905F4CAA62A5CF9D5323

GW_BETA_RELEASE_2.0b2.zip
16,1 MB (16 935 746 bytes)
CRC32: E3991259
MD5: 6EB789292D27305351060639600C68BB
SHA-1: 7E6A5817727EA7D8AA5EF189A01FC01C801B8F0A
Keep in mind that GW v2.0 beta 2 contains code specifically designed to brick 3DS beyond any repair and later releases will likely have more of the same, so use older versions if you want to play it really safe.
 
Well, thanks to some kind soul now I have all public Gateway releases to date. If you want to check whether your Gateway file is an untouched official release, here's the info.
GW_Release_1.0.zip
19,0 MB (19 983 588 bytes)
CRC32: C67864D1
MD5: E0B7530B5D9949A47627EC86512DFF5E
SHA-1: 7E5F8058E2066464488F999CEE943EA27767149E

GW_Release_1.1a.zip
19,1 MB (20 033 340 bytes)
CRC32: DE3C2EFA
MD5: EF766280C1143E58E6D98463DDB1C98C
SHA-1: AECAAC68EED8A5C759A7CF54072DFF73ED8D4AE9

GW_Release_1.2.zip
14,0 MB (14 746 834 bytes)
CRC32: 1519F9F4
MD5: 4A688ACB3C6DA27A92C71E5818868BCB
SHA-1: 4731BA8B9D2DFAD47841CEF68FD4F304DA10E1A6

GW_BETA_RELEASE_2.0b1.zip
16,1 MB (16 937 431 bytes)
CRC32: 75233963
MD5: D2EE752831FDADCE7F3CC5B42898B0AB
SHA-1: F911782FA2CF1400A6AE905F4CAA62A5CF9D5323

GW_BETA_RELEASE_2.0b2.zip
16,1 MB (16 935 746 bytes)
CRC32: E3991259
MD5: 6EB789292D27305351060639600C68BB
SHA-1: 7E6A5817727EA7D8AA5EF189A01FC01C801B8F0A
Keep in mind that GW v2.0 beta 2 contains code specifically designed to brick 3DS beyond any repair and later releases will likely have more of the same, so use older versions if you want to play it really safe.

Thank you, but there are two things to consider.

1. As the file is inside a zip file, it can't be corrupted after downloading, since any possible corruption would simple make the zip file unusable.
2. It's stated that the code won't cause a brick even if the launcher file gets corrupted on the SD card (yes, it's all about the coding, it's not any sort of magic involved).
 
to be honest, I am not trusting any of them

1. if Gateway left "Kill Code" in there as an "Anti-Fake" (reminds me of DSTT) why make it so that it kills the whole console why not just kill the card, its very cold and I think Gateway should be held accountable, Killing the Fake is one thing. Killing the console is another.
2. sounds even more worrying in the fact that if anything is slightly off on your SD Card, even without user error (memory card corrupting itself when it fails) it can take out your whole console too
3. there is a saying "You protest too much" and that is what Gateway have been doing, No one likes there work potentially stolen but the aggressiveness of there responses has always made me take what they say with a pinch of salt
4. Normatt should have reported about the kill code since Gateway didnt care for users enough to actually mention it
 
if you ask me pretty bad move on gateway side. peoples work gets stolen all the time but people still buy original like gateway. but bricking the console. its like me piritng a music album with a special frequency inbedded that makea my stereo or car explode? common if they are upset by people stealing their work deal it with them and dont make the users suffer. someone who has no clue that the r4 is a clone buys it and finds out ups my console has been bricked.
 
  • Like
Reactions: NEP
If Gateway had written their software so that it fried counterfeit DS cards, that would be understandable (if a bit extreme). However, going to the lengths of frying the console itself is a bit like a third party creating a high-tech exhaust system for a Honda wherein if some creates a counterfeit system using that software, then steps will be taken to destroy the car in which it's installed.

They don't have any right whatsoever to overwrite the software that Nintendo has written. Their protection scheme does exactly that. It not only overwrites it, but corrupts it.

Gateway is going to get reamed sideways for this.
 
  • Like
Reactions: NEP
to be honest, I am not trusting any of them

1. if Gateway left "Kill Code" in there as an "Anti-Fake" (reminds me of DSTT) why make it so that it kills the whole console why not just kill the card, its very cold and I think Gateway should be held accountable, Killing the Fake is one thing. Killing the console is another.
2. sounds even more worrying in the fact that if anything is slightly off on your SD Card, even without user error (memory card corrupting itself when it fails) it can take out your whole console too
3. there is a saying "You protest too much" and that is what Gateway have been doing, No one likes there work potentially stolen but the aggressiveness of there responses has always made me take what they say with a pinch of salt
4. Normatt should have reported about the kill code since Gateway didnt care for users enough to actually mention it
Actually, the official Gateway launcher.dat has a specific checksum sanity check that will make the launcher file not run if it is corrupted, so even if your SD card, or the launcher.dat file corrupts, you'll still be safe. The sanity check is actually disabled on the clones, which causes a checksum error that triggers the bricking code semi-randomly, hence the time delay between the release of the clone firmware and the start of the bricks. Does this mean that Gateway is safe and that there isn't any other way to trigger the bricking code? No, because I seriously doubt Gateway though of all the possibilities/scenarios in which their bricking code can screw people (such as with the region-free hex patching).
 
If they indeed have written a clone kill code, it hurts them as well. I've seen regular non-cart people talking about flashcarts bricking 3DSs now. They don't make a distinction between Gateway and the rest. The image of Gateway is just as tarnished among the population.
 
  • Like
Reactions: NEP
They are just plain idiots.
Implementing kill code of any kind is always a bad idea and always backfires.
Reminds me of the whole true blue situation in the PS3 scene.

But it´s funny how strong the Gateway defence force is on GBAtemp.
Bunch of stupid warez kiddies is the right term once again.
 
  • Like
Reactions: NEP
If they indeed have written a clone kill code, it hurts them as well. I've seen regular non-cart people talking about flashcarts bricking 3DSs now. They don't make a distinction between Gateway and the rest. The image of Gateway is just as tarnished among the population.
I'm sure if Gateway goes down, the others that are left will find a way to survive, although I seriously doubt that anyone will get any new features.
 
So they basically bricked consoles to make more money. If they get payed by Nintendo they will also brick Gateway 3ds? I'm not saying they did wrong but instead of ordering Gateway I bought a game.
 
  • Like
Reactions: Rob Blou
New 3ds Flashcard GW3DS-Next to be announced!!!

Features:
-Keep your 3ds working! Fist flashcard EVER that does not brick your 3DS!
-More info soon
Coming next: GW3DS Unbricker v1.0! Unbrick your 3DS today! Order now and get a special price: only $149.99 (shipping not included)
 
  • Like
Reactions: Keylogger
Hope the 2.0 final comes with a hardware FW update that cloners can't copy. So the GW team will not have to put those bricker code into the launcher.
I don't want to sleep with a bomb even if I was told it won't blow up.
 
Hope the 2.0 final comes with a hardware FW update that cloners can't copy. So the GW team will not have to put those bricker code into the launcher.
I don't want to sleep with a bomb even if I was told it won't blow up.
The cloners will just release a new hardware revision. That's what they always do.
They aren't complaining at all though. All they are doing is adding protection. Just like nintendo never acknowledges flashcarts and roms but games have anti-piracy.
Actually constantly going "well we innovate stuff instead of COPYING EVERYTHING" counts as complaining to me. Also Nintendo does acknowledge flashcarts https://ap.nintendo.com/detect/photos/platform.jsp?platformId=10&categoryId=3 (horribly outdated, but still).

About the Normmatt thing, apparently he though he patched the brick code (making it technically safe), but he missed some parts of it. We all fuck up somtimes, I suppose.
 

Site & Scene News

Popular threads in this forum