Hacking When was the most recent email response from Team Gateway?

[alexenochs]

yeah i got the same response pretty much...they said IF/WHEN we do a beta test we will let you know and that was after my second email to them the day after their update clearly stating they would be sending an email to beta testers

 

[hurfty]

Actually, it was proved it was intentional and malicious on Gateway's behalf since it required a very specific command to be run, and that command locked-up your 3DS rom chip with a very specific password, making it unusable until you either forced the rom to reset itself (losing all your data) or brute-forcing the password (which is what someone eventually found out how to do). And, surprise, all the bricked 3DS roms had the same password, something you would NEVER see if it was an accidental bug.

Alright thanks (and to gamesquest1 as well) for clearing that up for me. I guess the key search term was 'password' since I was having trouble digging it up amidst all the non-expert back and forth in all the threads.

 

[gamesquest1]

Alright thanks (and to gamesquest1 as well) for clearing that up for me. I guess the key search term was 'password' since I was having trouble digging it up amidst all the non-expert back and forth in all the threads.

don't worry i was probably one of the people in the back and forth threads saying there was no proof, but then i was helping bkifft out testing his unbricking code (i was just testing the code,bkifft and a fellow dev where the ones responsible for the unbricking code) he explained quite a bit to me about how the password's where generated and stuff, combined with the fact that the technique finally worked to unlock the nand without wiping it proves to me he and his "associate" knew what they where talking about

as for the motives, untill gateway comes out with a logical reason to explain "why" the code was included, the only explanation is that it was to brick the clone users, and it backfired and still triggers occasionally for legitimate gateway users

 

[Commoner]

A user from MaxConsole just posted that they managed to trigger a brick on Gateway 2.0b2 by leaving it on sleep mode running emuNand for a few days until the battery ran dry.

Can someone with access to easy unbricking like gamerequest1 check if this is a replicable method of triggering the brick code? Simplest way I can think of is to simply remove the battery while the 3DS is in sleep mode running emuNand although allowing the battery to drain and then barely charging it might be a more accurate way to test.

Also if someone could test this with MT-Card with the 1.1 update which also has emuNand, that would probably be a great help to the community as well.

 

[gamesquest1]

A user from MaxConsole just posted that they managed to trigger a brick on Gateway 2.0b2 by leaving it on sleep mode running emuNand for a few days until the battery ran dry.

Can someone with access to easy unbricking like gamerequest1 check if this is a replicable method of triggering the brick code? Simplest way I can think of is to simply remove the battery while the 3DS is in sleep mode running emuNand although allowing the battery to drain and then barely charging it might be a more accurate way to test.

Also if someone could test this with MT-Card with the 1.1 update which also has emuNand, that would probably be a great help to the community as well.

i kinda covered in my tests that you don't know if you have bricked until you reset the console if you are running emunand, the bricking that i triggered with diagnostics, still allowed me to boot into emunand, i can stay in emunand as much as i like from that point.......if my battery went flat for example, at that point im out of emunand and finally see that my console is bricked, i could of stayed in emunand for 10 years, never knowing that i was already bricked until i finally reset, This explains pretty much every official gateway report i have seen, i.e running out of power will kick you from emunand, exiting sytem setting's after the brick has occurred will boot you back to your bricked nand so you get a BSOD at that point instead(well it would actually just crash on a black screen untill you force reset...then you get the BSOD),basically any way you are kicked out of emunand would "appear" to be a different trigger, when in actual fact they could all be the exact same brick just discovered via a different route

this is not to say that diagnostics is the only way to brick, but that the point of when you find out is completely unrelated to the cause

 

[Commoner]

i kinda covered in my tests that you don't know if you have bricked until you reset the console if you are running emunand, the bricking that i triggered with diagnostics, still allowed me to boot into emunand, i can stay in emunand as much as i like from that point.......if my battery went flat for example, at that point im out of emunand and finally see that my console is bricked, i could of stayed in emunand for 10 years, never knowing that i was already bricked until i finally reset, This explains pretty much every official gateway report i have seen, i.e running out of power will kick you from emunand, exiting sytem setting's after the brick has occurred will boot you back to your bricked nand so you get a BSOD at that point instead(well it would actually just crash on a black screen untill you force reset...then you get the BSOD),basically any way you are kicked out of emunand would "appear" to be a different trigger, when in actual fact they could all be the exact same brick just discovered via a different route

this is not to say that diagnostics is the only way to brick, but that the point of when you find out is completely unrelated to the cause

Yeah the possibility of that happening occurred to me as well. Since the user did leave his 3DS in sleep mode for several days, it is very likely that he barely uses his 3DS and thus would probably not have been reading up on the Bricking Issues topic enough to know that Diagnostics is the most likely culprit when it comes to Gateway Bricks. I'll try to ask him if he did use Diagnostics at any point in time.

Still it is good to know that you have tried running previous tests with power cutting and were not able to trigger the Bricking Issue through that.

 

[gamesquest1]

Yeah the possibility of that happening occurred to me as well. Since the user did leave his 3DS in sleep mode for several days, it is very likely that he barely uses his 3DS and thus would probably not have been reading up on the Bricking Issues topic enough to know that Diagnostics is the most likely culprit when it comes to Gateway Bricks. I'll try to ask him if he did use Diagnostics at any point in time.

Still it is good to know that you have tried running previous tests with power cutting and were not able to trigger the Bricking Issue through that.

i actually checked with him on maxconsole and he said he didn't run diagnostics, but the dev's who have looked into the code did say that diagnostics was likely to be just speeding up the process by forcing it to do the checks that trigger the brick code, and that they "could" still be running independently during normal use, just much less frequent.

it could be that there is 1 check that will sometimes fail, the odd's of getting that specific check during normal usage is very slim, could be that with it being left on for several days it was slowly going through the different checks randomly until it finally got the bad "check" enough times for it to fail verification and trigger the code.....i don't think anyone will ever know 100% exactly why or what check is triggering the bricks for legitimate gateway bricks but something is obviously not working as gateway had planned

 

[Sorox]

Hey guys. Wanted to post this over on Maxconsole, but the forums NEVER sends me a confirmation email no matter how many accounts I make, so I'll put it here.

2 weeks ago, after seeing Gateway's new update, I tried guilt tripping them into letting me into the 2.0 beta because I got a faulty card. Considering they said "check your email soon" I figured they were going to start it within a couple days, you know?
Anyway, 2 days later, I get this response:

ok, i put you in the list for your inconvenience then, although normally it was
closed.

mailto:[email protected]

Now, considering I haven't gotten anything in my email about the beta within the alst 2 weeks, here's the possibilities:
1. This guy who answered my email had no authority to let me into the beta and lied to me.
2. There was never any beta, and this guy just said yes to string me along.
3. Gateway is still working 2.0 out and beta isn't out yet.

Thought I'd just share what i know.

 

[Habbert]

Hey guys. Wanted to post this over on Maxconsole, but the forums NEVER sends me a confirmation email no matter how many accounts I make, so I'll put it here.

2 weeks ago, after seeing Gateway's new update, I tried guilt tripping them into letting me into the 2.0 beta because I got a faulty card. Considering they said "check your email soon" I figured they were going to start it within a couple days, you know?
Anyway, 2 days later, I get this response:



Now, considering I haven't gotten anything in my email about the beta within the alst 2 weeks, here's the possibilities:
1. This guy who answered my email had no authority to let me into the beta and lied to me.
2. There was never any beta, and this guy just said yes to string me along.
3. Gateway is still working 2.0 out and beta isn't out yet.

Thought I'd just share what i know.

Or they have already sent out the beta to people on the list before you were added...

No one knows, I think it will be another couple weeks before a release anyway....

 

[CraddaPoosta]

I dunno... at this point, I wouldn't be at all surprised if Team Gateway just scarpered.

By this time, there should be SOMEONE who is a beta tester for them, who has received the latest firmware update to test. We've seen how every other beta in the history of the universe has leaked, but, somehow, Team Gateway is better capable of keeping their projects under wraps?

Yeah... methinks not.

 

[gamesquest1]

I dunno... at this point, I wouldn't be at all surprised if Team Gateway just scarpered.

By this time, there should be SOMEONE who is a beta tester for them, who has received the latest firmware update to test. We've seen how every other beta in the history of the universe has leaked, but, somehow, Team Gateway is better capable of keeping their projects under wraps?

Yeah... methinks not.

how could you know if their was an unleaked beta

 

[b17bomber]

I love how even the maxconsole moderator they hired (the former user one, not bullshitOPA) says if it isn't coming out before march, he's giving up.

 

[gamesquest1]

powertome was just a normal user given moderator status to keep the forum clean

 

[b17bomber]

powertome was just a normal user given moderator status to keep the forum clean

He probably regrets being hired. Though he has definitely had some Baghdad Bob moments of "everything is fine, everything will be fine."

 

[CraddaPoosta]

A certain peace has settled over me since I simply accepted the likelihood that Team Gateway has made like a tree and gone away.

That, and, I believe that the scene will, as usual, come through for the rest of the community. There has to be some form of 'Wood' on the horizon for Gateway cards and their clones.

 

[gamesquest1]

A certain peace has settled over me since I simply accepted the likelihood that Team Gateway has made like a tree and gone away.

That, and, I believe that the scene will, as usual, come through for the rest of the community. There has to be some form of 'Wood' on the horizon for Gateway cards and their clones.

more likely see a rom loader for the SD slot, although thinking about it, that would mean 3 diffrent things loading/saving to the SD card....not sure if that would have much effect on the load times etc as the nand loads a lil bit slower from the SD slot as it is, if you had the roms loading from there and saves and any DLC you have installed i would imagine it could get a bit.....sluggy, then again i suppose it works ok with eshop games, so who knows

what would be funny just for lols is if they enabled loading 3DS games from normal R4 DS card

 

[placebooooo]

Honestly, I think gateway is on its way to dying. Im sure they will release this update sometime soon, but the next update they come up with will take even longer than this one to come out, then the next even longer than nothing at all. They just got what they wanted.

 

[mattrunks]

So we're basically waiting for Team Gateway to release a beta of a beta, makes so much sense, thought we were the beta testers.

 

[groit]

gateway has to outdo mt card

 

[jrr6415sun]

if gateway was going to quit why leave in the brick code? Why not release 2.0b3 with the brick code removed and then call it a day and move on. who cares if someone steals their code if they are no longer in business