Hacking One Thread - All reported Gateway bricks

[Huntereb]

Have any of the gateway users tried flashing their nand?

Are they all the same bootrom error numbers?

Are they the same bootrom error numbers as the clone bricks?

Yes. Wait, has anyone? It's worthless to try, anyway.

Yes.

Yes.

 

[Tomobobo]

Thanks, non-gateway, non-bricked user.

It's possible that these bricks can be due to some other issue and/or are not having the emmc tricked.

I'm blind, I see one picture that clearly shows the bootrom error and another user posted the same error for his gateway brick.

 

[Huntereb]

You need to read back a bit in the forum, and zoom in on any pictures you find. I've seen maybe 4 pictures, from Gateway users, of their console.

 

[retrofan_k]

Still no updates via Email to GW about this. To the other GW users who got bricked, have you heard any replies on how to get this sorted out.

Personally, I think its a lie and the level of customer support is a piss take from what I have experienced so far and why they put malicious code in 2.02b is beyond me and they cannot have the balls to own up and admit that it backfired on real GW users.

I believe in KARMA and those heavily involved in this will get their come up-pence at some point in their real lives, if this is not resolved.

I have a lot more to say but all I want is for my system to be fixed as it was not user error to why it bricked in the first place. If GW can do this then my faith and trust will be restored but as of right now I have none.

 

[cabal_man]

Personally, I think its a lie and the level of customer support is a piss take from what I have experienced so far and why they put malicious code in 2.02b is beyond me and they cannot have the balls to own up and admit that it backfired on real GW users.

I am in no way wanting to encourage debate about this, but it IS possible that if gateway are a very small team who're working hard on getting a much anticipated release out, are also probably being bombarded by people with emails, as well as having website issues yesterday that they are not being particularly speedy in replying to emails.

Your email could potentially be sitting in a pile of 100s, some of which may not be constructive emails. I doubt gateway have a dedicated customer service rep... so I wouldn't expect quick replies.

Of course you may be right, I just don't think it is the most likely explanation. Does anyone know what the rough size of the gateway team is anyway?

Sorry for posting again... I don't want to clutter up this thread with my opinion.

I had another thought about issues as well... It might be relevant to say how you wrote to your SD/microSD card. I have one card reader which is a bit dodgy (DS roms I write to my card using it don't always work... it's getting binned today) and they are the sort of thing that people often use cheap versions of which come free with memory.... Or would corruption of this fashion show up in the MD5 check?

 

[pudink]

I am still running 2.02b. But, I am being as careful as I can reasonably be. I am not powering my system completely down. I am removing the Gateway card before even closing the lid, unless I have a game actively running in sleep mode. The only time I accessed the eShop was to redownload my purchased titles, to update Mario Kart 7, and to purchase the new Phoenix Wright game (off-topic, GET THIS GAME; it's fantastic).

dont know how the previous bricks happened ?
can you shed some light here please?

was it from removing the card or powering down the system?please someone elaborate

 

[retrofan_k]

I am in no way wanting to encourage debate about this, but it IS possible that if gateway are a very small team who're working hard on getting a much anticipated release out, are also probably being bombarded by people with emails, as well as having website issues yesterday that they are not being particularly speedy in replying to emails.

Your email could potentially be sitting in a pile of 100s, some of which may not be constructive emails. I doubt gateway have a dedicated customer service rep... so I wouldn't expect quick replies.

Of course you may be right, I just don't think it is the most likely explanation. Does anyone know what the rough size of the gateway team is anyway?

Sorry for posting again... I don't want to clutter up this thread with my opinion.

I had another thought about issues as well... It might be relevant to say how you wrote to your SD/microSD card. I have one card reader which is a bit dodgy (DS roms I write to my card using it don't always work... it's getting binned today) and they are the sort of thing that people often use cheap versions of which come free with memory.... Or would corruption of this fashion show up in the MD5 check?

I totally agree on that with them being busy, but if you put yourself in my shoes, you can imagine the frustration and anger involved over something so simple as to drag n drop some files, which then caused over $200 in damage that I cant do Jack shit about right now.

I did think about the SD/MicroSD being the problem, as I could not get it to pass the diagnostic check properly before the brick occurred, yet there is supposed to be sanity fail safe checks in place to avoid any bad checksums from what I heard. I have also heard Zelda could have been an issue too.

Its this statement which anger me

"We are still investigating individual brick incidents reported by legitimate Gateway 3DS users. So far, many isolated brick incidents that were blamed on us have been debunked in one way or another and turned out to be associated with use of the clones modified versions of our official release files".

So basically, to me, that means my brick was associated with clones or modified official release files, which I'm sorry but its BS. I cannot stress enough that it was legit GW hardware/software used. And why would I lie if I wanted to lets just say? I have no reason to and would not gain anything from it if I did.

Plus how can they say that if they have not actually inspected my console? This is why I'm so pissed off, as its not right to be treated like this to a customer of their's and will only drive more people away, as word will spread fast.

 

[misterb98]

That statement by Gateway, the way I interpret it, is an admittance that some users ARE having legit bricks. Notice how they say "many" and not "all" or "none". Basic logic says that if most were, some were not.

 

[Pong20302000]

In an effort to try to portray the Gateway bricking situation as realistically and accurately as possible, and to help cut down on the numerous topics to the same effect, I thought it might be a good idea to compile all reports of all verified bricks on one single topic that can be easily updated.

Since there are literally hundreds, if not thousands of posts on this same topic, I was going to ask for your help here, gentle Temp'ers. I know there are something like five or six reported bricks from Gateway users here on GBATemp, like kirrillov, apollooo, retrofan_k and (scariest of all) even one of the official product reviews for GBATemp, Devin.

If possible, I'd like to show the screenshots of the BSOD on this thread, as well, so the scene can see that the people reporting the bricks are genuinely bricked, and to dissuade any idea of a conspiracy theory.

As of this posting, though, I am able to find five-ish total reported bricks after a quick scan of the topics and comments on this forum. Please give me a hand and help me to get the most accurate number of confirmed bricks together in one place.

Thanks!

Reported Bricks on the GBAtemp Forum

kirillov
Discussion

apollooo
Discussion

retrofan_k
Discussion

Devin (Temp Reviewer)
Discussion

Users from other forums; (thanks to PolyChrome)

PhoenixBankai
MaxConsole Discussion
Photo with checksum value



Asus
MaxConsole Discussion

Arthurcara
MaxConsole Discussion

This brings the total number of confirmed bricks to seven.

could you contact all the People or maybe they will see this

Can they check there SD card for any files that have been created with a date on or later than the 4th Feb 2014??

or if they modified the console time to get play coins at any point to the 4th of Feb 2014 or a later date?

 

[kyogre123]

or if they modified the console time to get play coins at any point?

I did this a day before the second brick report here; nothing went wrong and my 3DS is safe. I changed the date to one day after and then one day back... twice.

 

[Pong20302000]

I did this a day before the second brick report here; nothing went wrong and my 3DS is safe. I changed the date to one day after and then one day back... twice.

the date also needed to have been 4th Feb 2014 or later, we just trying to confirm something

 

[misterb98]

the date also needed to have been 4th Feb 2014 or later, we just trying to confirm something

I don't know what you are trying to confirm, but the fact you are looking at something so specific is interesting. Are you hypothesizing that having a system clock after 4th of February 2014 causes the brick?

 

[Pong20302000]

I don't know what you are trying to confirm, but the fact you are looking at something so specific is interesting. Are you hypothesizing that having a system clock after 4th of February 2014 causes the brick?

Possible that the trigger for the Bricking code has been in the Gateway launcher as to why Official bricks are occurring

and relates to any file on the SD card being dated 4th Feb 2014 or later
so if someone either has a file with that date on there SD card or Puts Forward there Internal clock (for play coin cheating) thus when the 3DS next saves to the SD it creates a file with the date 4th Feb or Later then a Brick could occur

possible Kill Code found

0x10410,0x10) MMC_SET_BLOCKLEN
 
0x50c1b,0) //PROGRAM_CSD
 
0x50c2a,0x0) setpass
 
0x10410,0x200) MMC_SET_BLOCKLEN

 

[the_randomizer]

Yes, inserting and consistently disavowing the existence of bricking code and legit customers' suffering from GW3DS hardware is really gonna help get them more business, right? I don't know what their real reason for using it is, but either way, people are being baited back to them from their recent showcase about multi-ROM support.

 

[sonic2756]

Possible that the trigger for the Bricking code has been in the Gateway launcher as to why Official bricks are occurring

and relates to any file on the SD card being dated 4th Feb 2014 or later
so if someone either has a file with that date on there SD card or Puts Forward there Internal clock (for play coin cheating) thus when the 3DS next saves to the SD it creates a file with the date 4th Feb or Later then a Brick could occur

possible Kill Code found

0x10410,0x10) MMC_SET_BLOCKLEN
 
0x50c1b,0) //PROGRAM_CSD
 
0x50c2a,0x0) setpass
 
0x200) MMC_SET_BLOCKLEN

Is the "Feb 4" check intentional?

 

[Streeve]

http://gbatemp.net/threads/bricked-3ds-xl-help.360464/

This should very well be in the first post as well.
No, I don't have any pictures and I can't take any.
My description should be enough.

 

[Pong20302000]

Is the "Feb 4" check intentional?

whoops
the kill code i posted earlyier was incomplete, i edited it now so its now complete

 

[TheChield]

Maybe people who get bricked could tell what launcher they use ?

Regarding the very few brick, something might have been done wrong or a patch might have been applied...

 

[sonic2756]

whoops
the kill code i posted earlyier was incomplete, i edited it now so its now complete

I'm still a bit confused as to how having a file modified after Feb. 4th causes bricks.

 

[Pong20302000]

I'm still a bit confused as to how having a file modified after Feb. 4th causes bricks.

it just is one of the Triggers in the code,assume possibly a future check code possibly if another had already been bypassed