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... 
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
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.
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)
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.
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.
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).
Similar threads
-
- Article
- No one is chatting at the moment.
-
@
Psionic Roshambo:
I wonder if they could get CPUs to run that hot then use the heat to power a steam turbine to power the CPUs.... -
-
@
Psionic Roshambo:
It's not the movies or games downloads that I would worry about, like breaking into networks, downloading encrypted things, spying on network traffic. I have seen so many "Top Secret" seals on files when I was a kid
-
@
Psionic Roshambo:
I was obsessed with finding UFOs, a surprising amount of US files where stashed on computers in other countries, China back in the early 90s omg sooo much
-
@
BigOnYa:
Yea that crazy, I've never tried hack into anything, I just pirate, and my ISP have send me 3-4 letters, so had to VPN it -
@
Psionic Roshambo:
Ship to ship communication software for the Navy although without access to the encrypting chips it was mostly useless
-
@
Psionic Roshambo:
I bet now a 4090 could probably crack it? Hmmm maybe not even back then I'm pretty sure they where using like 1024 bit encryption
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
I remember one time I downloaded like a 500MB ISO file on 56K and that literally took like 2 days
-
-
-
-
-
-
-
-
