Hacking One Thread - All reported Gateway bricks

[retrofan_k]

Has anyone checked this page? I think it has been posted here before.

http://www.elotrolado.net/wiki/Bricks_Nintendo_3DS#Recopilatorio_de_todos_los_casos_de_Brick

First time I have seen that but the cheeky bastards are saying this below on my brick, which is more than FALSE.
SIN modify Launcher

 

[xfcrowman]

Strange how Zelda is mentioned again, as its the 3rd time I have seen it mentioned including myself. Can you post up a step by step when it actually occurred like I have done a few pages back on this thread? Pics are good too if you can. Mine is now on its way to the GW team, which should get there soon.

Personally, I'd stay on 1.2 on your other console. 2.01b is known to cause save and instability issues frequently but depends on how bad you wanna play zelda.

As promised, here's a pic of my dead 3DS, along with my Gateway cards. Since I purchased my Gateway in late December, I only used 2.0B2 and never upgraded from any older versions of Gateway firmware.

Spoiler

Here's a summary of the sad life of my bricked 3DS:

---- Never played any games before GW exploit

---- Emunand was on latest FW 7.1U

---- Wifi was mostly on

---- Used 2.0b2 from GW official download page, MD5 matched the ones posted by Gateway

---- SD brand was 2GB Toshiba (came with 3DS), MicroSD was a PNY 16GB Class 10.

---- N/A the 3DS was never used online with OFW, only with emuNand

---- N/A because no previous flash carts used


Exploited the console with the blue card and copied the 2.02b launcher.dat to the SD. Gateway mode screen boots via holding L on profile. I then backed up the nand, set up emunand, and upgraded emunand to the latest firmware. Diagnostic checks always passed (did this several times, as the Gateway would occasionally freeze when I went to DS profile).

After setup, I played Zelda Link Between Worlds to completion (about 20 hours of play time over 2 week period). I would intermittently look at some of the other apps on emunand (i.e. miiverse, eShop, etc). After finishing Zelda, I switched to playing Super Mario 3D Land. Played Mario several times, and on Jan 28 I powered on the 3DS in the morning and was bricked (No freezing or anything beforehand, I turned on the 3DS a few minutes after waking up). I didn't do anything unconventional with my 3DS (e.g. modified Launcher.dat etc), so it's unclear to me why the bricking code in 2.0b2 was activated.

I already upgraded to 2.0b1, and my old Zelda and Mario saves from the bricked 3DS are working properly. However, I might go back to 1.2 since I already completed Zelda and I don't have any other games with the latest SDK in my collection of roms. Please let me know if anyone wants additional info about the brick, and thanks for the help!

 

[retrofan_k]

As promised, here's a pic of my dead 3DS, along with my Gateway cards. Since I purchased my Gateway in late December, I only used 2.0B2 and never upgraded from any older versions of Gateway firmware.

Spoiler

View attachment 6195

The order of events on my bricked 3DS is: Setup Gateway with 2.0b2 and emunand, updated emunand to latest firmware, played Zelda to completion. After finishing Zelda, I switched to playing Super Mario 3D Land. Played Mario several times, and on Jan 28 I powered on the 3DS in the morning and was bricked. I didn't do anything unconventional with my 3DS (e.g. modified Launcher.dat etc), so it's unclear to me why the bricking code in 2.0b2 was activated.

I already upgraded to 2.0b1, and my old Zelda and Mario saves from the bricked 3DS are working properly. However, I might go back to 1.2 since I already completed Zelda and I don't have any other games with the latest SDK in my collection of roms. Please let me know if anyone wants additional info about the brick, and thanks for the help!

Damm, that sucks, I know how you feel man.

Myself literally only had my new GW card for just over 30 mins last week until I got bricked. I didn't even have time to use emunand or play a game but your'e events seem less to me. Its really strange how its activated, but I guess its certain scenarios and combination of options to which I gather that trigger it, as others are still on that 2.02b and say their fine.

Until a decrypted launcher.dat is done (if ever done), I dont think we all know for sure what is triggering it, as from what I hear, there is speculation surrounding it and no solid evidence and only GW know themselves, which they are still adamant that it only affects clones and modified launchers.

Its difficult and a hard one to narrow down and because the figures are very low on legit GW users getting bricked, people are still cautious to believe it.

I believe it happened because it happened to me and I wish some solid information is found and spread to the scene, as its not fair. I would even go as far and say its not fair on clone users either, as malicious code like this should not be implemented AT ALL and its very shady.

Even when 2.0 final is out, it be wise to wait a while, as the brick code could still be there

Good luck on getting it fixed hopefully.

 

[xfcrowman]

Damm, that sucks, I know how you feel man.

Myself literally only had my new GW card for just over 30 mins last week until I got bricked. I didn't even have time to use emunand or play a game but your'e events seem less to me. Its really strange how its activated, but I guess its certain scenarios and combination of options to which I gather that trigger it, as others are still on that 2.02b and say their fine.

Until a decrypted launcher.dat is done (if ever done), I dont think we all know for sure what is triggering it, as from what I hear, there is speculation surrounding it and no solid evidence and only GW know themselves, which they are still adamant that it only affects clones and modified launchers.

Its difficult and a hard one to narrow down and because the figures are very low on legit GW users getting bricked, people are still cautious to believe it.

I believe it happened because it happened to me and I wish some solid information is found and spread to the scene, as its not fair. I would even go as far and say its not fair on clone users either, as malicious code like this should not be implemented AT ALL and its very shady.

Good luck on getting it fixed hopefully.

Yeah, it's pretty terrible and I'm sorry to hear that yours died within 30 minutes of getting your Gateway. I updated my post to match what you did a few posts back, hopefully the extra info is useful.

I agree with you that the bricking code was a really awful thing to do, legit Gateway users and clone users should not have to worry about the risk of their console bricking like this. I know that many doubt that legit Gateway users are being bricked, but at some point there will be enough of us to dispel any doubts. At least it is now possible to unbrick without Gateway, and once people have Gateway unbricking services available I plan to fix my 3DS and then sell it off on ebay. I wish you the best of luck on your 3DS, and hopefully you will have it returned soon!

 

[cabal_man]

It seems that most people who have bricked have been running the diagnostic tests. Personally my card has NEVER frozen or hung and I've never run the diagnostic tests.

Running 2.02b fine...

 

[Warft]

First time I have seen that but the cheeky bastards are saying this below on my brick, which is more than FALSE.
SIN modify Launcher

Launcher SIN modificar = unmodified launcher = genuine launcher
Please use a translator before writing nonsense.

 

[JohnnyBlaze1986]

It seems that most people who have bricked have been running the diagnostic tests. Personally my card has NEVER frozen or hung and I've never run the diagnostic tests.

Running 2.02b fine...

That's me as well. I've been on the latest beta getting Streetpasses from Disney World and no issues yet. I've never run diagnostic because I personally have no reason to.

 

[Squall]

I run diagnostic at the begining and trying many feautures (console see wi-fi on 4.5 and ask me for update), but all was fine. After I used emunand about month.
My game (Bravely Default) has stopped on first screen and after that I try diagnostic and catch brick.
So maybe need write BIG READ LETTERS - didn't do anything, if your game (from GW flash) is stopped on first screen.
I think in this thing better do format and reset all. Then trying license cartidge game, than GW with older launcher (1.2).
Diagnostics - is evil!!! And often go to settings (especially not for turn on GW) - is evil too!!!

 

[Kei00]

Was that the incident where it was the friend of a friend who claimed to have a broken unit with no real proof? I wasn't sure about that one.

EOL is a trusted spanish scene community, so please, don't judge the whole community because of one person.

First time I have seen that but the cheeky bastards are saying this below on my brick, which is more than FALSE.
SIN modify Launcher

"Launcher SIN modificar" means "UNmodified launcher". 100% original launcher, if you prefer.

 

[gamesquest1]

It seems that most people who have bricked have been running the diagnostic tests. Personally my card has NEVER frozen or hung and I've never run the diagnostic tests.

Running 2.02b fine...

i am now noticing quite a few of these bricks have been after using the diagnostics menu....wonder if there is a bug in there somewhere, i did read that the clones always fail fpga test on diagnostics.....maybe they used that as a trigger as well......but that then hits people who just have a faulty fpga on a genuine gateway card

 

[Huntereb]

Ryukouki

This brings the total number of confirmed bricks to eight.

*11

 

[retrofan_k]

Launcher SIN modificar = unmodified launcher = genuine launcherx
Please use a translator before writing nonsense.

Launcher SIN modificar = unmodified launcher = genuine launcher
Please use a translator before writing nonsense.

Don't read Spanish okay, so next time quit being a dick

 

[retrofan_k]

EOL is a trusted spanish scene community, so please, don't judge the whole community because of one person.




"Launcher SIN modificar" means "UNmodified launcher". 100% original launcher, if you prefer.

Thanks for that, not like the other tit who posted his reply on that. Translators don't always work properly

 

[atlboyz_247]

I've been watching from the background on this, but are there a bit of people out there that have been consistently using 2.0b2 w/o bricks? Only stories I hear of are related to the bricks and issues w/ 2.0b2. I only used b2 twice before I stopped using my XL due to everyone starting to post bricks on b2. So much cares for my XL

(After seeing many many threads getting opened for similar purposes, I assumed this would be the appropriate place to ask, if not, someone can move this post to a new thread/another thread/etc)

 

[MichiS97]

I've been watching from the background on this, but are there a bit of people out there that have been consistently using 2.0b2 w/o bricks? Only stories I hear of are related to the bricks and issues w/ 2.0b2. I only used b2 twice before I stopped using my XL due to everyone starting to post bricks on b2. So much cares for my XL

I am still using 2.0b2 without any problems whatsoever.

 

[Huntereb]

I am still using 2.0b2 without any problems whatsoever.

And no one's going to stop you from doing that, nor do we care. It's just odd that someone is willing to use something known for causing a system to kill itself, just because of a few small features.

 

[bkifft]

And no one's going to stop you from doing that, nor do we care. It's just odd that someone is willing to use something known for causing a system to kill itself, just because of a few small features.

Well, now that there's a way to fix the brick some people are switching back to 2.0b2 ("low risk of brick in the first place and if it happens I know a guy").
Kinda like there will most likely once again be a surge in unprotected intercourse once a real cure for HIV is found.

 

[Kouichi]

We used also the diagnostic test...
the test was ok, so I went back to the GW main menu and changed the game. ---> BRICK

very strange...

 

[kyogre123]

Kinda like there will most likely once again be a surge in unprotected intercourse once a real cure for HIV is found.

Oh, mate, you made me laugh with that analogy.

 

[Huntereb]

Kinda like there will most likely once again be a surge in unprotected intercourse once a real cure for HIV is found.

Funny, but in reality the cost of such a cure will inevitably be incredibly expensive. Similar to the cost of fixing your console once it is bricked. Most users here do not have the proper skills to solder their 3DS, especially in the way required to fix this specific type of brick (Hell, even I don't, I'd have to grab a buddy to help me). Not to mention the cost of the tools required to do this type of thing, I mean, is it really worth the extra features? 2.0B1 can already do everything 2.0B2 already does, minus proper Emunand (eShop, Miiverse, etc.). It can play all of the games requiring SDK 5.X+, cartridges in Classic Mode, and all the other old games. Besides a few small bugs, which can usually be countered by not running 7.X on Emunand, there isn't enough room for me to want to "upgrade" to a firmware that also includes the possibility of having to do all the work I mentioned previously.

As I always say when participating in a discussion of this proportion, I am not trying to offend anyone. I'm not sure how this could be interpreted as offensive, as it's simply my understanding of the matter, but it usually seems to come back to bite me in the butt.