Hacking Gateway 3DS working on the New Nintendo 3DS.

[MichiS97]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

 

[yoshinatsu]

Because I'm a huge noob, can someone please clarify again:

I need .3dz to play online, not .3ds?

[Damn, guess all my .3ds downloads were pointless ]

Then again, I suppose there aren't that many games to play online. Smash, Animal Crossing?

I haven't used Gateway yet, but if I understand correctly, if the game rip isn't yours and you downloaded a .3ds game online, you need to get a tool such as Gateway ROM Patcher and inject the header data and chip ID from another game into the one you want to play online, or use a header people have shared publicly. Then rename it from .3ds to 3dz.

 

[thorasgar]

Do you need .3dz or .cia for DS Download play, or just local multiplayer. I am not sure that is still a thing with 3DS games.

 

[yoshinatsu]

Do you need .3dz or .cia for DS Download play, or just local multiplayer. I am not sure that is still a thing with 3DS games.

You could try .3dz. It's very easy to make them, unlike .cia.

 

[PLEYOR]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

Wasn't here last year but did gateway show a video of the new features this early on?

 

[Kenneth196]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

580+ pages of posts summed up in 1 post. Spot on. We just have to be patient. Plenty of other things to do while GW work their magic.

 

[Phantom_User]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

It's only fitting History repeats itself. Has been the norm for quite some time too so.. 4.5 Vets might be having a blast looking at us, hehe.

Either way, yeah, we'll hang. The e-mails thing is just everyone's way of coping around with the hype I suppose. It always leads to more discussion, to more speculation, to.. Pretty much everything else. Ironicaly, just like you guys did before, so to speak .
I feel sorry for those that got bricked, of course, so I hope we, the newcomers, won't suffer the same fate/wait.

 

[baker]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

Thank you, didn't know about that. Still waiting patiently, it's been two months, now I'm used to.

 

[Phantom_User]

Oh yeah, something's been troubling my mind recently.

Take games that only use Wi-Fi to download puzzles or like Bravely Default, that connects online to download data to the game and the village. Do you need those to .3DZ too?

 

[Rizzorules]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

Yeah until now it has been the same situation but after seeing 2hacks posts i bet history will be different this time, it would be a great opportunity for Gateway team to start 2015 with 9.2 support and saying 2015 will be a year of more updates

 

[MichiS97]

Wasn't here last year but did gateway show a video of the new features this early on?

Okay, here comes the timeline


October 2, 2013: First sneak peak of the 2.0 update, showing that you can dump your NAND and your retail cartridges, also there's on-screen diagnostics (yay?)
October 15, 2013: Second sneak peak, showing the first video footage of emuNAND, confirming that Monster Hunter 4 is working, Pokemon XY are confirmed WIP
October 20, 2013: FAQ, confirming that they are working on MultiROM and other things
November 1, 2013: Pretty much only saying that the update is "close to completion", addressing the clones
December 1, 2013: First beta was released, that's when emuNAND was made public, all games except Pokemon and Animal Crossing worked
December 17, 2013: The 7.0 update for the 3DS screwed up emuNAND, on this post they just confirmed that there will be a second beta with support for 7.0 with emuNAND
December 23, 2013: Yeah, making it possible to update emuNAND to 7.0
December 26, 2013: Just a video guide
January 1, 2014: Happy New Year post, just promising stuff
January 4, 2014: Video is released that shows Animal Crossing and Pokemon working
January 13, 2014: The bricks are addressed, however the clones are being blamed, their copy of the original GW firmware is claimed to be flawed
January 20, 2014: The team is still getting shit from consumers, post another message of how the original GW firmare is perfectly safe and stable (which was a simply wrong statement)
January 21, 2014: Admitting that some legitimate GW users' systems have been bricked, teaser video of the MultiROM feature (first video footage of this very feature)
Februrary 25, 2014: Denying that the bricks are their fault, pretty much just saying that you have to buy the flashcard from their official resellers
March 28, 2014: Announcing a private beta of the 2.0 update, showcasing all features
March 30, 2014: Evaluation of the beta
March 30, 2014: RELEASE OF THE 2.1 OMEGA UPDATE (2.0 private beta, 2.1 public update with e-shop support)


Now, here is one of my e-mail exchanges with the team from late November to early December 2013

As you can see, they promised a christmas release when actually, the update came out at the end of March

 

[henn64]

Oh yeah, something's been troubling my mind recently.

Take games that only use Wi-Fi to download puzzles or like Bravely Default, that connects online to download data to the game and the village. Do you need those to .3DZ too?

Streetpass? No. Spotpass/Connecting to Nintendo's servers? Yes.
I don't know why you want an extra copy of Mii Plaza for puzzles though.

 

[Phantom_User]

Streetpass? No. Spotpass/Connecting to Nintendo's servers? Yes.
I don't know why you want an extra copy of Mii Plaza for puzzles though.

Oh lol, sorry. When I meant puzzles I was thinking of Professor Layton type of downloads.

I see then, thanks for clearing it up

 

[ryanjf97]

Okay, here comes the timeline


October 2, 2013: First sneak peak of the 2.0 update, showing that you can dump your NAND and your retail cartridges, also there's on-screen diagnostics (yay?)
October 15, 2013: Second sneak peak, showing the first video footage of emuNAND, confirming that Monster Hunter 4 is working, Pokemon XY are confirmed WIP
October 20, 2013: FAQ, confirming that they are working on MultiROM and other things
November 1, 2013: Pretty much only saying that the update is "close to completion", addressing the clones
December 1, 2013: First beta was released, that's when emuNAND was made public, all games except Pokemon and Animal Crossing worked
-snip-

I'd be more than happy if they released a public beta!
also, thanks for this, I missed out last year on all the Gateway stuff, so it's nice to be caught up!

 

[Phantom_User]

Okay, here comes the timeline


October 2, 2013: First sneak peak of the 2.0 update, showing that you can dump your NAND and your retail cartridges, also there's on-screen diagnostics (yay?)
October 15, 2013: Second sneak peak, showing the first video footage of emuNAND, confirming that Monster Hunter 4 is working, Pokemon XY are confirmed WIP
October 20, 2013: FAQ, confirming that they are working on MultiROM and other things
November 1, 2013: Pretty much only saying that the update is "close to completion", addressing the clones
December 1, 2013: First beta was released, that's when emuNAND was made public, all games except Pokemon and Animal Crossing worked
December 17, 2013: The 7.0 update for the 3DS screwed up emuNAND, on this post they just confirmed that there will be a second beta with support for 7.0 with emuNAND
December 23, 2013: Yeah, making it possible to update emuNAND to 7.0
December 26, 2013: Just a video guide
January 1, 2014: Happy New Year post, just promising stuff
January 4, 2014: Video is released that shows Animal Crossing and Pokemon working
January 13, 2014: The bricks are addressed, however the clones are being blamed, their copy of the original GW firmware is claimed to be flawed
January 20, 2014: The team is still getting shit from consumers, post another message of how the original GW firmare is perfectly safe and stable (which was a simply wrong statement)
January 21, 2014: Admitting that some legitimate GW users' systems have been bricked, teaser video of the MultiROM feature (first video footage of this very feature)
Februrary 25, 2014: Denying that the bricks are their fault, pretty much just saying that you have to buy the flashcard from their official resellers
March 28, 2014: Announcing a private beta of the 2.0 update, showcasing all features
March 30, 2014: Evaluation of the beta
March 30, 2014: RELEASE OF THE 2.1 OMEGA UPDATE (2.0 private beta, 2.1 public update with e-shop support)

Thanks for that hardwork! It wasn't as bad as everyone makes it seem then. We're all stressing out so to speak because we can't use our systems yet.

I mean your hype begins October 2. October 15th hype replenished. December 1 you got the first beta that allowed you to emuNAND, except Pokemon and AC weren't working. After that you had to wait towards March 30th for the actual Multi-ROM and eShop releases.

A long wait, yes, but I was imagining some sort of horrid, Sahara'ish type of waiting for Multi-ROM. Still, history does repeat itself as we know, nothing we can do about that.

Again, thanks for the research work.

 

[MichiS97]

ryanjf97 Those private betas I mentioned in the timeline stayed public for about five minutes before they were distributed everywhere

 

[AdowTatep]

I saw that timeline of 2.0, well, in here we have an expression that it's something like that: do something wrong is normal, but continue making things wrong is fucking dumb.

So I don't think they will do this again

 

[guitarheroknight]

Okay, here comes the timeline


October 2, 2013: First sneak peak of the 2.0 update, showing that you can dump your NAND and your retail cartridges, also there's on-screen diagnostics (yay?)
October 15, 2013: Second sneak peak, showing the first video footage of emuNAND, confirming that Monster Hunter 4 is working, Pokemon XY are confirmed WIP
October 20, 2013: FAQ, confirming that they are working on MultiROM and other things
November 1, 2013: Pretty much only saying that the update is "close to completion", addressing the clones
December 1, 2013: First beta was released, that's when emuNAND was made public, all games except Pokemon and Animal Crossing worked
December 17, 2013: The 7.0 update for the 3DS screwed up emuNAND, on this post they just confirmed that there will be a second beta with support for 7.0 with emuNAND
December 23, 2013: Yeah, making it possible to update emuNAND to 7.0
December 26, 2013: Just a video guide
January 1, 2014: Happy New Year post, just promising stuff
January 4, 2014: Video is released that shows Animal Crossing and Pokemon working
January 13, 2014: The bricks are addressed, however the clones are being blamed, their copy of the original GW firmware is claimed to be flawed
January 20, 2014: The team is still getting shit from consumers, post another message of how the original GW firmare is perfectly safe and stable (which was a simply wrong statement)
January 21, 2014: Admitting that some legitimate GW users' systems have been bricked, teaser video of the MultiROM feature (first video footage of this very feature)
Februrary 25, 2014: Denying that the bricks are their fault, pretty much just saying that you have to buy the flashcard from their official resellers
March 28, 2014: Announcing a private beta of the 2.0 update, showcasing all features
March 30, 2014: Evaluation of the beta
March 30, 2014: RELEASE OF THE 2.1 OMEGA UPDATE (2.0 private beta, 2.1 public update with e-shop support)


Now, here is one of my e-mail exchanges with the team from late November to early December 2013

As you can see, they promised a christmas release when actually, the update came out at the end of March

Thats a long wait but it was worth it! The difference this time is that everything is apparently finished and ready to be distributed if the email are to be trusted. But i still
hope for a New Year release.

 

[ChrisRX]

I think it's kind of funny that this is the exact same situation as it was last year before the release of 2.0 (or OMEGA, as they called it). The same impatience, the same e-mail spam, heck even the same "OMG TEH WEBSITE IS D0WN, RELEASE IS COMING!!!!!"-threads. I don't want to crush people's hopes here, but just to give you the facts: The 2.0 update, which we waited for last year at christmas and New Year's Eve time wasn't released until March and they used the same cryptic time frames in their e-mails, like "very soon", "a matter of days". Then came the second beta 2.0b2 which brought upon the bricking code and some people here are still flaming about this. It was one flawed firmware (well to be fair, flawed is the wrong word. The bricking code was intentional. The fact that Gateway owners were affected by it however, was not), and there haven't been any bricks since the 2.0 final and the few bricks that happened have long become fixable. So what do I want to say? Guys, hang in there, the update will be released soon, but sending thousands of e-mails to the GW team every single day isn't going to make it happen any faster. Let them take their time, it will be worth it.

I think in all the time I've spent reading this thread, I could've probably completed one of the games I have sitting on my shelf. Batman arkham origins blackgate has been begging to be finished for about a year.

 

[gamesquest1]

plus you have to bear in mind at that point they where building the framework of functionality, as seen in the video they can just reuse that framework, but apply it to their new exploit, rather than having to start from the ground up, so this time its probably mostly A) getting the exploit stable and reliable, and B) checking for any bugs caused by the base FW change