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

[BMinkie]

playing luigi's mansion, went to a short nap, then BOOM, blue screen of death when i turned it on.


also: more proof:

http://i.imgur.com/3WLAy91.png

did you have it in sleep mode?

 

[profi200]

Gateways beta 1 is not affected. The checksums and the brick code exist since beta 2.

 

[Deleted member 333767]

So what is actually going on here? My 3DS setup consists of a Gateway card and has a clean install of the latest beta files with emuNAND setup and working great..... Am i in danger of a brick??? I dont want my beautiful white 3DS on 4.4 turned into a paperweight!!!

 

[Relenting]

did you have it in sleep mode?

Already answered:

no, i turned it off.

 

[liquidsolidyetboth]

Gateways beta 1 is not affected. The checksums and the brick code exist since beta 2.

thx for the info

 

[Relenting]

it a 6.25% chance it happens if the sd card fails to meet the checksum and the brick code would activate

and seems to be the case with at least 2 users reported with images.

I think those are the clone odds, not unmodified odds. The unmodified requires the mystery factor to pass the safety check.

 

[liquidsolidyetboth]

I have sadly gone back to 1.2 until this mess is sorted out either way.

 

[mr. fancypants]

I have sadly gone back to 1.2 until this mess is sorted out either way.

me too to dangerous for me

 

[viper133]

I will turn on my 3ds xl when gateway 2.0 final comes out. Until then, i have alot of games to catch up on my cfw ps3.

 

[crazyace2011]

I will turn on my 3ds xl when gateway 2.0 final comes out. Until then, i have alot of games to catch up on my cfw ps3.

ill deal with 1.2 until they give the all clear that there isn't a brick code in the 2.0 final release

 

[IronClouds]

I'm scared to check. Haven't turned my 3DS on since before this bricking business started. If Gateway take too much longer releasing 2.0 I might just try turning it on without the SD inserted just to see. Can't run brick code if the launcher.dat isn't accessible now, can it?

 

[MrOldboy]

I guess the consensus is to go back to 1.2 to be absolutely safe. My GW comes tomorrow so I guess I'll go this route and not 2.0b1.

 

[Aurora Wright]

I'm scared to check. Haven't turned my 3DS on since before this bricking business started. If Gateway take too much longer releasing 2.0 I might just try turning it on without the SD inserted just to see. Can't run brick code if the launcher.dat isn't accessible now, can it?

No code is executed if you don't go to "DS Profile".

 

[IronClouds]

No code is executed if you don't go to "DS Profile".

Well that's good to know. Thanks :-)

 

[Relenting]

I guess the consensus is to go back to 1.2 to be absolutely safe. My GW comes tomorrow so I guess I'll go this route and not 2.0b1.

2.01b should be safe, but it reportedly has save issues (which 1.2 doesn't seem to have from what I've heard), which were fixed in 2.02b, which again has the kill code.

 

[Tomy Sakazaki]

So what is actually going on here? My 3DS setup consists of a Gateway card and has a clean install of the latest beta files with emuNAND setup and working great..... Am i in danger of a brick??? I dont want my beautiful white 3DS on 4.4 turned into a paperweight!!!

3DS using latest gateway unmodified launcher.dat (2.0b2) got bricked after some game season.
This launcher.dat actually has some bricking routines that will erase the 3DS NAND contents and corrupt it's controller making the standard hardware rewriting procedures (connecting the 3DS NAND chip to a modified SD Card Reader) useless in these cases.


apollooo: I don't remember seeing this info at this thread, but you have made a emunand ambient (6.X or 7.X system menu loaded through launcher.dat) or were you running your gateway without it? It may be helpful to narrow what triggered your brick.

 

[Runehasa]

2.01b for me it is not chancing this. Finding another 4.5 3DS XL is going to be near impossible or insanely expensive on ebay.

 

[Keylogger]

I have to stay on 2.0b1 if I want to play my retail Pokemon X with emunand.. :/

 

[mathieulh]

I'm just asking a question. It's important we get accurate information. Unverified reports help no one, but create only further confusion.

Furthermore, the blue screen with the bootrom error can be caused by something other than the emmc controller reporting size 0, too.

The error codes in the screenshot match though.

 

[escherbach]

If you run the ROP on a system with code execution you can simply grab the decrypted code from memory.

Oh, and not to forget. They use a CPU emulator since beta 1 to obfuscate their code.

If you had said this from the start it would have given your claims much more credibility. In fact it would be basically essential for them to use obfuscation or encrypted code to pull off something like this.

Gateway are saying these brick code claims are being spread by gangsters (well script kid keyboard gangsters) and associates. Also, if the code is obfuscated it'd more likely people have misinterpreted an eMMC write routine to prevent a real system update during emuland update with DELIBERATE bricking code.

Since the beta code is causing problems even in its unaltered state it'd no surprise that clone firmware is even more susceptible.

In any case, Gateway say they will replace/fix consoles using original gateway cards - so quit with the whining everyone