Hacking Where did Gateway go wrong?

  • Thread starter Thread starter CreAtor135
  • Start date Start date
  • Views Views 10,925
  • Replies Replies 107
To be clear, Gateway using A9LH itself doesn't constitute a source code licence violation. They're free to make their own A9LH implementation If they actually used code from other CFW however, then that obviously would.

It should hardly be a surprise if they did steal open source code, however. After all, their launcher even contains code from Nintendo.
don't forget that they took credit for patching the 9.6 firm issue on the new 3ds/xl.
 
  • Like
Reactions: LongTimeLurker
So, was free CFW leaked or not? And what might have theoretically happened had it not been leaked if my first question is true?
 
I know this has probably been beaten to death, but I'll add my two cents

Gateway are terrible about the way they handle their customer support. Let's take a look at some of their payload attributes: if 1 bit is changed in the entire launcher.dat, assuming it can still execute the relevant code, it WILL brick your device. This sort of thing could happen easily with a bad file copy. Sure, hasn't happened, at least afaik, but the potential is there... Next, let me ask, what right do GW have to attempt to brick a device, no matter the circumstance? Answer is, they really don't. They're just assholes. They can detect clone cards, obviously, so why screw the user over when they could simply present a simple message saying "the detected device is not a compatible gateway device" and simply refuse to boot? This kind of thing makes them terrible. Next, sure the first exploit was actually by them and we RE'd it out... OK, fine, add some protection to your code. Reasonable. There are, however, a few base rules you should follow: if you're using code that others made CREDIT THEM, the "GW fastboot" shit is literally identical to an old commit of a9lh code, aside from stage 2 where they made MINIMAL changes and shitted their code on top. Do you think we got any recognition for this? No. We didn't. Next, again, do NOT add a bricking feature, especially when you stole our code in the first place to do what you did.

This is a paid product. It's supposed to be professional, the fact that the above are issues are HUGE red flags, it has always screamed to me to stay as far as I possibly can away from GW.

In closing, there are many ways GW went wrong, all of which have simple solutions to them that could be implemented tomorrow. But they won't. Because that's the kind of people they are
 
I know this has probably been beaten to death, but I'll add my two cents

Gateway are terrible about the way they handle their customer support. Let's take a look at some of their payload attributes: if 1 bit is changed in the entire launcher.dat, assuming it can still execute the relevant code, it WILL brick your device. This sort of thing could happen easily with a bad file copy. Sure, hasn't happened, at least afaik, but the potential is there... Next, let me ask, what right do GW have to attempt to brick a device, no matter the circumstance? Answer is, they really don't. They're just assholes. They can detect clone cards, obviously, so why screw the user over when they could simply present a simple message saying "the detected device is not a compatible gateway device" and simply refuse to boot? This kind of thing makes them terrible. Next, sure the first exploit was actually by them and we RE'd it out... OK, fine, add some protection to your code. Reasonable. There are, however, a few base rules you should follow: if you're using code that others made CREDIT THEM, the "GW fastboot" shit is literally identical to an old commit of a9lh code, aside from stage 2 where they made MINIMAL changes and shitted their code on top. Do you think we got any recognition for this? No. We didn't. Next, again, do NOT add a bricking feature, especially when you stole our code in the first place to do what you did.

This is a paid product. It's supposed to be professional, the fact that the above are issues are HUGE red flags, it has always screamed to me to stay as far as I possibly can away from GW.

In closing, there are many ways GW went wrong, all of which have simple solutions to them that could be implemented tomorrow. But they won't. Because that's the kind of people they are
I would like to add that this is a paid product. Yet it's always out of date.
Gateway users had to wait months for A9LH support and the answer they got was horrible! It bricked new 3DS's because they didn't execute the 2.1 downgrade properly, resulting in systems bricking, Then by the time they did release their A9LH build, it was grossly out of date because A9LHv2 had already been released several weeks before hand. Which getting it to work on A9LHv2 still requires a little extra effort.
Coupled with the fact that fact that cart still uses out of date set ups, like emuNANDS, GBA/DS(i) patches are not built in, every 3DS update has the chance of breaking support because reasons. and of course months without updates.

People are basically paying 80$ to be always be out of date.
 
People are basically paying 80$ to be always be out of date.
I used to feel like this when i had to buy new flash carts for ds, i figured one was enough but then i get told that for my dsi firmware updates i need to install a update on the flashcart to make it work, and they never let me get anymore, i had to buy a new card with one flashed on it, and after 4 cards, i feel skepectical to buy anymore even though 2 don't work, lost one of them and only one works with CFW on my 3DS. Is horrible.:sad:

$80 for one of that and no support? It makes me upset if this is true. I paid for the product, make it work until is no longer needs fixes or support. :glare:
 
1: The fact that you have to pay for one
2: CFW's are a better solution
3: Online play can get you banned
4: Just... Outdated...
5: SD's are so overrated (unless your pirating)

EDIT: 1000th POST
 
Last edited by YugamiSekai,
1: The fact that you have to pay for one
2: CFW's are a better solution
3: Online play can get you banned
4: Just... Outdated...
5: SD's are so overrated (unless your pirating)
"5: SD's are so overrated (unless your pirating)"

is the only reason to cfw
 

Site & Scene News

Popular threads in this forum