Hacking It is now February 4th. No brick.

[weatMod]

already 1 report of a brick on official support forum

http://www.maxconsole.com/maxcon_fo...es-Statement-about-RMA-ing-your-Bricks/page28

could be totally unrelated or fake report ,who knows

 

[Dinomite]

You forgot a number. It's either 2.01b or 2.02b.

Don't correct people if you're still wrong yourself. If you want to get technical the version number is 2.0b2
'2.02b' would be for if they had developed past 2.0, which they haven't.

Like has been said over and over, if you're using official Gateway hardware and using the official Gateway software, you shouldn't have any fears of a brick. I don't blame anyone for rolling back to 2.0b1 or lower and that's fine, but I hate people coming here and 'stating' outright that running 2.0b2 will brick your 3DS. It's completely unfounded and false.

 

[Ante0]

Going to turn my 2.0b2 on now! wish me luck!

Booted, emunand running at 7.1.
Everything works fine.

I read something the other day about someone trying to force it to brick. Took numerous of reboots and tries after setting internal clock to 2014/2/4

Y2K says Hello!

Made me chuckle xD

 

[DinohScene]

Y2K says Hello!

 

[Arras]

Don't correct people if you're still wrong yourself. If you want to get technical the version number is 2.0b2
'2.02b' would be for if they had developed past 2.0, which they haven't.

Like has been said over and over, if you're using official Gateway hardware and using the official Gateway software, you shouldn't have any fears of a brick. I don't blame anyone for rolling back to 2.0b1 or lower and that's fine, but I hate people coming here and 'stating' outright that running 2.0b2 will brick your 3DS. It's completely unfounded and false.

Except for the part where quite a few people using said official Gateway hardware with official Gateway software got bricked already, including one of our reviewers. 2.0b2 won't brick your 3DS outright but stating that it's 100% safe is false.

 

[Askedforthis]

Oh please, it's not supposed to brick the thing immediately. It didn't back then and it won't now. Of course it won't brick it the moment you push the power button. The point was that the CHANCE might increase due to more flags being tripped, thus we might see more bricks than usual. Not that you're screwed the moment you turn the thing on. It's not even confirmed it's "February 4th".

 

[masterzero]

Except for the part where quite a few people using said official Gateway hardware with official Gateway software got bricked already, including one of our reviewers. 2.0b2 won't brick your 3DS outright but stating that it's 100% safe is false.

It's funny one of the "Taligateways" on the spanish forum has stated that delvin had a testing/developer ds and that's enough different to not being fully compatible with gateway and caused the brick...

Yes really..

 

[Arras]

It's funny one of the "Taligateways" on the spanish forum has stated that delvin had a testing/developer ds and that's enough different to not being fully compatible with gateway and caused the brick...

Yes really..

No, the official explanation was that they sent him a prototype Gateway and that somehow caused the brick. IMO that's bullshit considering quite a few others have been bricked and they still refuse to acknowledge or deny the bricking code but that's what they said.

 

[Dinomite]

I never said it's 100% safe, but I do stand by the belief that if the official software was installed correctly as per the instructions, then peoples concerns should be no higher than modding any other console on any given platform.

It's hard for me to comment on any of the reported Gateway bricks on GBATemp (like it is for any member) and details have been sketchy at best for each of the very few cases reported here, excluding Devins' whose case seems to be odd with him having folders with dates not showing the correct time stamp and the fact that he was running a Gateway dev unit in the first place.

 

[Pedeadstrian]

It's all a conspiracy. First Y2K happened, then 2012, and now this. I don't see any sentient machines or armageddons, so ipso facto columbo oreo, my 3DS won't brick. Thanks, science!

 

[retrofan_k]

Don't correct people if you're still wrong yourself. If you want to get technical the version number is 2.0b2
'2.02b' would be for if they had developed past 2.0, which they haven't.

Like has been said over and over, if you're using official Gateway hardware and using the official Gateway software, you shouldn't have any fears of a brick. I don't blame anyone for rolling back to 2.0b1 or lower and that's fine, but I hate people coming here and 'stating' outright that running 2.0b2 will brick your 3DS. It's completely unfounded and false.

Ignorance is blind. Love it

 

[Deleted User]

It just shows that some of these "respected" devs (i'm looking at profi200 and mathieu) are talking out of their ass with this 4th feb date. Parrots that just spread a rumor. Their anti-GW agenda is showing....

This is just the one of the only things we can fact check with what they have said, all the other things they said are not fact checkable...

 

[ground]

It just shows that some of these "respected" devs (i'm looking at profi200 and mathieu) are talking out of their ass with this 4th feb date. Parrots that just spread a rumor. Their anti-GW agenda is showing....

This is just the one of the only things we can fact check with what they have said, all the other things they said are not fact checkable...

yeah completely, there is only one downpart in your story.

they literally said that they didn't know what it was going to do, that they only found that trigger (without linkage to briking)

 

[Huntereb]

It just shows that some of these "respected" devs (i'm looking at profi200 and mathieu) are talking out of their ass with this 4th feb date. Parrots that just spread a rumor. Their anti-GW agenda is showing....

This is just the one of the only things we can fact check with what they have said, all the other things they said are not fact checkable...

They don't know what it's supposed to do, it could be a brick-disabler for all we know.

 

[profi200]

I have said many times. It is related to the date, at which the Launcher.dat was created on. So it doesn't hit everyone. It hits only the users, which setup their GW or clone after the 4. It will not brick another 30 users, probably 1 or 2 more and that's it. It's a second check in case the cloners remove the first one and don't see the second one.

 

[mathieulh]

I have said many times. It is related to the date, at which the Launcher.dat was created on. So it doesn't hit everyone. It hits only the users, which setup their GW or clone after the 4. It will not brick another 30 users, probably 1 or 2 more and that's it. It's a second check in case the cloners remove the first one and don't see the second one.

No, even if you do set it up after the 4th, the creation timestamp in the file's attribute is still going to be lower as the file was copied to the SD card but created long before then.
Likewise if the file was generated through emunand the timestamp value is blank.

Basically for this to trigger, you would need to modify/create your own Launcher.dat (or any file that starts with "L") after Feb, 4th 2014 and copy it to the root of the SD card.
Seems rather unlikely at this point.
You would also need the payload hashes to fail as well because there is another check for that before the timestamp is even checked.

 

[retrofan_k]

I have said many times. It is related to the date, at which the Launcher.dat was created on. So it doesn't hit everyone. It hits only the users, which setup their GW or clone after the 4. It will not brick another 30 users, probably 1 or 2 more and that's it. It's a second check in case the cloners remove the first one and don't see the second one.

My brick occurred on my genuine GW on the 01/20/2014 with the launcher.dat (2.0b2) time stamped 12.39:54 on the 20th January. Again, no modified launchers as I had no reason to or any intentions as it was a genuine GW product. So, if what you say is true, the bricks occurred after the 4th January?

So, people would brick now after the 4th Feb in small numbers again and then stop again?

 

[profi200]

No, even if you do set it up after the 4th, the creation timestamp in the file's attribute is still going to be lower as the file was copied to the SD card but created long before then.

Then explain the picture here: http://gbatemp.net/threads/it-is-now-february-4th-no-brick.361634/page-2#post-4908917

Likewise if the file was generated through emunand the timestamp value is blank.

Before that the chances of a brick are doubled. Or if you have "emuNAND" already and just update to 2.0b2.

So, people would brick now after the 4th Feb in small numbers again and then stop again?

It stopped not really. It's more that the users are now more careful and the most use versions prior 2.0b2. That's why it almost stopped. It will not affect much. Probably 1 or 2. No idea. I don't have a cristal ball and can see that

 

[mathieulh]

Then explain the picture here: http://gbatemp.net/threads/it-is-now-february-4th-no-brick.361634/page-2#post-4908917

It seems unrelated to the second check (the file timestamp check) and most likely related to another check that did fail for one reason or another (maybe even the initial check that's been running for a while now)

And I am not saying that the exploit is anything stable, or that their checks (they have many) are all fail proof. I did say however that on paper, the chances for the actual timestamp check to trigger the brick code are very low.

Before that the chances of a brick are doubled. Or if you have "emuNAND" already and just update to 2.0b2.

Err... no, if you "just update to 2.0b2" you will simply overwrite the Launcher.dat file with the one from the 2.0b2 update which has older timestamp last modified and created attributes than Feb, 4th 2014, therefore that particular check will not trigger from this.

(remember, that particular check is performed against the file's timestamp, not the actual 3DS date)

Oh ! and I would avoid writing any file which name starts with "l" at the root of your SD card, just to be on the safe side, because their code actually looks for any file starting with "l"

 

[KazoWAR]

they used greater than, not greater than or equal to, gotta wait until tomorrow.