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.
Yes.
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?
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.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 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).
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?
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.
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.
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?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?
0x10410,0x10) MMC_SET_BLOCKLEN
0x50c1b,0) //PROGRAM_CSD
0x50c2a,0x0) setpass
0x10410,0x200) MMC_SET_BLOCKLEN
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
Code:0x10410,0x10) MMC_SET_BLOCKLEN 0x50c1b,0) //PROGRAM_CSD 0x50c2a,0x0) setpass 0x200) MMC_SET_BLOCKLEN
Is the "Feb 4" check intentional?
I'm still a bit confused as to how having a file modified after Feb. 4th causes bricks.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.