Hacking 3DS ****ing bricked, never even use clones.

[justinkb]

Aren't you ignoring the position requirement? They can't be just random 4 bits out of 32, they must be in a sequence.

no, the other 28 bits are inconsequential and don't even have to be considered.

also, consider this: the chance that the upper 4 bits are all 0 is the same as for example bits 3, 9, 13, and 30 all being 0.

(again, assuming the RNG gives uniformly distributed numbers)

 

[Runehasa]

Interesting email from Gateway.

 

[djgarf]

Its understandable why he is "ex staff"

because real life took over
i can guarantee you that if i was still one of the supervising team here some of you wouldnt be getting away with the stuff you do now

 

[liquidsolidyetboth]

Interesting email from Gateway.

at least they offered to collect his console and replace it if it was their fault.

 

[spinner09]

that would be 1/(2^4) or roughly 6%, assuming the RNG has no bias.

So that's about a 1 in 12.5 chance of the console bricking itself after a certain date? Since that date has come and passed in the last few days, as soon as someone has launched the launcher around 12 times, their console will become bricked.

If that's the case, we should be seeing a loooooot more blue screen brick reports in the coming days, and even Gateway users are effected. Gateway themselves doesn't seem to believe their code is screwing their own users, despite the various reports.

 

[ground]

Nopee.

i never tamper with any of the files and all i got from the gateway site.


EDIT: checked with MD5
is the checksum value is the one i'm supposed to post?

http://i.imgur.com/cQEziXW.png

Not really. This is the file on your desktop, bit not the file on the 3DS sdcard. We would rather see the file on your sdcard to look if something wentt wrong over there

 

[Relenting]

.

Why did you delete your post?

I found this line odd:

We just checked if it could happen to our users. And it can't. And in fact it took us more time than we should have because cloners posted email pretending to be Gateway users, but it was, as usual, lies. It wasted our time from instead work on our product for our users.

Again, we can guarantee that our product are 100% stable and safe.

What are they talking about? What is "it" that could happen to their users? Did they just admit to having a killswitch?

 

[GregoryRasputin]

Not really. This is the file on your desktop, bit not the file on the 3DS sdcard. We would rather see the file on your sdcard to look if something wentt wrong over there

Try reading, he already posted that.....

 

[Green Cat]

So that's about a 1 in 12.5 chance of the console bricking itself after a certain date? Since that date has come and passed in the last few days, as soon as someone has launched the launcher around 12 times, their console will become bricked.

If that's the case, we should be seeing a loooooot more blue screen brick reports in the coming days, and even Gateway users are effected. Gateway themselves doesn't seem to believe their code is screwing their own users, despite the various reports.

There is no check "for a certain date", it's just that the random number generator (like most of them) is seeded by the current datetime, so there was a higher probability at a certain time yesterday.

 

[justinkb]

It's possible his SDCARD has intermittent random read failures.

If he copied from his SDCARD to his Desktop and no read failures occurred that specific instance, he'll have a false sense of security about his SDCARD.

Ideally, he should disable all read caches in his operating system and hash the launcher.dat while on the SDCARD multiple times, to ensure there aren't intermittent read failures.

 

[ground]

So that's about a 1 in 12.5 chance of the console bricking itself after a certain date? Since that date has come and passed in the last few days, as soon as someone has launched the launcher around 12 times, their console will become bricked.

If that's the case, we should be seeing a loooooot more blue screen brick reports in the coming days, and even Gateway users are effected. Gateway themselves doesn't seem to believe their code is screwing their own users, despite the various reports.

that is not how it works (apperantly).

The code is calculating a chage to brick the console (i guess every boot, if the roploaders reloads again). There is no date in that

 

[Arras]

Not really. This is the file on your desktop, bit not the file on the 3DS sdcard. We would rather see the file on your sdcard to look if something wentt wrong over there

He already checked that too, it was fine as well.

Aren't you ignoring the position requirement? They can't be just random 4 bits out of 32, they must be in a sequence.

That doesn't matter. If it was 4 random bits out of 32 that had to be 0, the chances would be much higher. But here, these 4 specific bits need to be 0. Chance for 0 is 1/2, so the chance of 4 zeros is 1/2 * 1/2 * 1/2 * 1/2.

 

[apollooo]

Not really. This is the file on your desktop, bit not the file on the 3DS sdcard. We would rather see the file on your sdcard to look if something wentt wrong over there

check the my post in page 4 or 5. i tested it directly on the SD card plugged into my PC

 

[Runehasa]

Why did you delete your post?

I found this line odd:

What are they talking about? What is "it" that could happen to their users? Did they just admit to having a killswitch?

I actually responded back to them something similar trying to get them to admit to "IT"

 

[liquidsolidyetboth]

so there is 6.25% chance of this happening, i dont see in the code where it says it occurs on a 'certain time' hmm is it just by booting up you can trigger it ?

 

[justinkb]

so there is 6.25% chance of this happening, i dont see in the code where it says it occurs on a 'certain time' hmm is it just by booting up you can trigger it ?

it cannot occur without execution of the launcher, so right after using the mset exploit.

 

[WiiUBricker]

I don't think the OP is payed by a chinese gangster to make a false brick report. It's just ridiculous. Also they still haven't denied that they have included brick code in their launcher firmware, in fact, it seems they are sticking to it and tell people to deal with it. The fact that they claim they can see if a 3DS brick occured by gateway software (assuming they really can, perhaps some hackers can confirm it), further proves the existence of brick code in their software. Also the fact that they supposedly offer a replacement unit is interesting, although they wouldn't be able to make up for any lost eShop software. I wonder what shipping address they would provide.

 

[Arras]

that is not how it works (apperantly).

The code is calculating a chage to brick the console (i guess every boot, if the roploaders reloads again). There is no date in that

The random number calculator uses the date as a part of the data to calculate the number, so on some dates the chance may be higher.

 

[justinkb]

I think it's highly unlikely that the RNG is seeded by some factors, one of which is just the date... as opposed to, say, UNIX timestamp.

If the fact that the day is, say, January 13, makes it significantly more likely that the upper 4 bits of the generated numbers, that random number generator is _REALLY_ _REALLY_ broken.

If the date was used, instead of the timestamp, for an entire day, the RNG would have a bias? Nintendo has better programmers than that, surely.

 

[ground]

The random number calculator uses the date as a part of the data to calculate the number, so on some dates the chance may be higher.

hmm didn't know about that fact (but i believe it is true then). is the code already published and confirmed btw?