Hacking What happens after Feb. 4th?

  • Thread starter Thread starter sonic2756
  • Start date Start date
  • Views Views 23,931
  • Replies Replies 100
Oh, so if I'm on 2.0b2 with no emunand and I haven't bricked yet (play many games each day) I should be fine after the 4th? This is very confusing =/
 
Oh, so if I'm on 2.0b2 with no emunand and I haven't bricked yet (play many games each day) I should be fine after the 4th? This is very confusing =/

No. The 4th Feb trigger found here is separate from the random bricks happening. So, if you want to be fully safe, use 2.0b1. On 4th/5th we will know if brick-o-calypse happened or not.
 
I think GW-team have killed of a few random 3DS units before with BSOD, but on the 4th Feb the BIG BANG is going to strike... All GW-cards will be self destroyed... :lol:
 
  • Like
Reactions: the_randomizer
even if there is a 4th day brick check on ( which I doubt ) and even on older versions ( I doubt it even more) just wind back 1 week the clock of the 3ds and voila , you'll have 1 week of time to watch if there are any bricks , which would be easily seen since they would happen earlier on clones
 
Except that 90% of people have probably already downgraded! and the other 10% will follow this tip and be bricked on the 11th XD
 
maybe the 4th is when they intend to release 2.0 official along with a way to un-do the bricks for official devices, we can only hope.
 
maybe the 4th is when they intend to release 2.0 official along with a way to un-do the bricks for official devices, we can only hope.
I'd be happy enough if they released the lock password generation method. Which they most likely wont, as then they'd have to admit the brick code in the first place.
 
even if there is a 4th day brick check on ( which I doubt ) and even on older versions ( I doubt it even more) just wind back 1 week the clock of the 3ds and voila , you'll have 1 week of time to watch if there are any bricks , which would be easily seen since they would happen earlier on clones


you cant back the clock from a file using your 3ds ( the launcher.dat file is made on 3 jan 2014 ) so the file is a specific amount of time "old" and after that amount of time there "will" an brick-o-calypse (or the say so)
 
you cant back the clock from a file ( the launcher.dat file is made on 3 jan 2014 ) so the file is a specific amount of time "old" and after that amount of time there "will" an brick-o-calypse (or the say so)

sure you can.

either you manipulate the files metadata in it's filesystem entry entry or (easier) you set your system time to the desired date and modify the file (e.g increase first byte by one, save, decrease first byte by one, save)
 
This whole Feb 4th BS issue reminds me of the year 2K bug a lot of people were worried about back in the days before Jan 1st, 2000 hit. They all thought it would be the end of the world, computers would crash, blah, blah, blah. Of course, a lot of you that believe this and think Gateway intentionally put brick code in their software weren't old enough (or born yet) to remember the Y2K fiasco.

Well, nothing happened then and nothing will happen on Feb 4th so just relax.
 
This whole Feb 4th BS issue reminds me of the year 2K bug a lot of people were worried about back in the days before Jan 1st, 2000 hit. They all thought it would be the end of the world, computers would crash, blah, blah, blah. Of course, a lot of you that believe this and think Gateway intentionally put brick code in their software weren't old enough (or born yet) to remember the Y2K fiasco.

Well, nothing happened then and nothing will happen on Feb 4th so just relax.

Y2k bug was a different thing tho. It could happen to old hardware and software (the one that wrote the date using 2-digit numbers), but MOST of the organizations that went batpink insane about it, already had newer solution that it wouldn't affect.

Now here, we have a device that ALREADY bricked a few 3DSes, and a trigger-code that could POSSIBLY (keyword possibly) trigger it on that date. With Y2k people spent thousands to get their computers checked if they will survive the 'bug'. Here, all you have to do is change one file to make sure that if it IS true, it won't happen.
 
This whole Feb 4th BS issue reminds me of the year 2K bug a lot of people were worried about back in the days before Jan 1st, 2000 hit. They all thought it would be the end of the world, computers would crash, blah, blah, blah. Of course, a lot of you that believe this and think Gateway intentionally put brick code in their software weren't old enough (or born yet) to remember the Y2K fiasco.

Well, nothing happened then and nothing will happen on Feb 4th so just relax.
Y2K was just media without tech background hyping at it's best. 2038 is when shits gonna break on a big scale (unless all the systems get fixed first that is).

Just set your old/cheap devices to 20th January 2038 and watch what happens (modern stuff should already use 64bit unixtime, but android 4.1 used to have problems for example).
 

Site & Scene News

Popular threads in this forum