Hacking What happens after Feb. 4th?

  • Thread starter Thread starter sonic2756
  • Start date Start date
  • Views Views 23,931
  • Replies Replies 100
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).



Yep that didnt go well.

Had to relogin to everything in chrome after trying that on my pc :wacko:

Wonder what would happen if i changed the server time (64 bit system) That controls lots of pcs running 32 bit os in college.:ph34r:
 
Yep that didnt go well.

Had to relogin to everything in chrome after trying that on my pc :wacko:

Wonder what would happen if i changed the server time (64 bit system) That controls lots of pcs running 32 bit os in college.:ph34r:

doesn't have that much to do with what bit os a systems runs, only how many bits are used to save time (usually done by counting the seconds passed since 1.1.1970). and when one uses a signed 32bit counter (in other words 2^31 possible values) for that it rolls over to about 2^31 seconds before the 1.1.1970.

Of course on a 64bit system that's most likely a 64bit number.

but you should try sooner than later to get going working on a fix (in case someone happens to work for a bank or insurance company ask your sysad. he/she is most likely thrilled for that to happen to the basic accounting database systems.)
 
9:42am here in Aus.

Yes, I am on 2.0b2. I'm a rebel, and I live on the edge.
And while I'm all for calculated risk, I think I'll just leave my 3DS off for a few days.
 
erm... somehow while playing chinese whispers some of you might have forgotten the initial post: its about file dates, not 3DS system time.

so the real danger seekers out there might want to create a file named l.txt (that's an small L) on your sd card, making certain file creation as well as file modification are being set.

and yeah, even then the correct crc of the unmodified launcher should prevent a brick.
but i wouldn't want to lick a leper even though i know it most likely wouldn't get me infected.
 
I think this was a check not a bricking sequence. :)
You are just wasting your time overthinking things.
From what I have seen so far the majority of bricked 3DS consoles got bricked after playing Nintendo games but this might won't have to do with anything at all.
 
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...
 
lol.. Has been on 2.0b2 since long time ago, i do have an arduino that i could use if i want to backup the nand, anyway, could i be able to run 7.1 firmware on a 2.0b1 3ds?...
 
The code logic might've been simply misinterpreted, I have no doubt that whoever analyzed the brick code (which is undoubtedly there) had all the good intentions. We should just be happy that no global 3DS apocalypse happened and we can move on with our lives.
 

Site & Scene News

Popular threads in this forum