Hacking One Thread - All reported Gateway bricks

[bkifft]

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.

The sad thing is: that analogy wasn't meant to be funny. Just an extrapolation I took from my experiences in human behavior: once there aren't any harsh consequences for ones actions, lower instincts (sexdrive, greed, laziness, etc.) overthrow logical reasoning. I sometimes even catch myself doing it (sadly sometimes only in rertrospective).

And btw: I of all people am running 2.0b1 at the moment. Only downside for me (besides the common "fail to boot/save" bugs) is that for some strange reason the home button doesn't work in PW: DD. But as saving and power off do I don't really care enough to risk having to open my XL and mess about with the board.

 

[retrofan_k]

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...

Possible bug in the diagnostic check that triggers the brick code. That happened to me, if you not already read my post of what happened to my 3DS

 

[crazyace2011]

what could be causing the brick running the diagnostic check?? having emunand installed?

 

[retrofan_k]

what could be causing the brick running the diagnostic check?? having emunand installed?

Don't think so, as I never got as far to install emunand before mine bricked. My idea is just a guess, as nobody knows the true extent on why this occurs, except the GW team, which they'll never disclose.

 

[crazyace2011]

I just put the 2.02b firmware on my 3ds formatted for emunand and updated the firmware to 7.1.0 15u even downloaded Zelda four swords and nothing happened then put 2.0b1 on the sd card

 

[CraddaPoosta]

I am still running 2.0b2, and have booted into Gateway Mode probably two dozen times from having my 3DS completely powered off since my last post on this topic. With the exception of maybe one out of every ten times where the system would freeze and force me to power it off and back on again, still haven't run into a single issue.

Doesn't mean that I don't have a heart attack every single time it DOES freeze up, though.

 

[retrofan_k]

I am still running 2.0b2, and have booted into Gateway Mode probably two dozen times from having my 3DS completely powered off since my last post on this topic. With the exception of maybe one out of every ten times where the system would freeze and force me to power it off and back on again, still haven't run into a single issue.

Doesn't mean that I don't have a heart attack every single time it DOES freeze up, though.

Why still use it, if you're bricking it yourself (no pun intended every time you use it, yet guess its like the saying "I'm alright Jack"

Its how it happened to me, froze, forced power off. Reboot = nice blue debug screen (Brick)

I still think everyone is playing Russian roulette on 2.0b2 regardless of these countless posts by people saying their fine. I was fully aware of the bricking fiasco before it happened to me, yet like yourself and others who thought and still believe I'll be fine, because genuine hardware and unmodified are used it wont brick.

I was wrong and unfortunate to suffer from it, but, if I was a user now (non bricked) and read these type of comments and posts surrounding this problem, I would stay clear of 2.0b2 until this is 100% resolved.

For the sake of potentially being bricked for the sake of playing newer SDK games and using emunand is more than stupid to risk fucking up a $200 console.

 

[gamesquest1]

thing is dropping back to b1 doesnt even loose any game compatibility...only 7.1 emunand compatibility and eshop.

btw have you heard anything back about your 3ds yet?

 

[retrofan_k]

thing is dropping back to b1 doesnt even loose any game compatibility...only 7.1 emunand compatibility and eshop.

btw have you heard anything back about your 3ds yet?

Yeah, forgot to probably mention that about b1. I checked the tracking before and it was last updated the 29th at Customs in the UK. I emailed the GW with the details and they replied saying they will keep me posted.

 

[Searinox]

Allow me to get this straight: GW team's ability to fix broken 3DS consoles implies they have the ability to read the 3DS' unique key and encrypt a normal 4.5 firmware in a way that will work on the console?

 

[gamesquest1]

Or they just have the key to unlock the nand without wiping the nand

 

[Gabbo04]

Allow me to get this straight: GW team's ability to fix broken 3DS consoles implies they have the ability to read the 3DS' unique key and encrypt a normal 4.5 firmware in a way that will work on the console?

No, they need the nand backup to restore the consoles, so make your conclusions.

 

[bkifft]

No, they need the nand backup to restore the consoles, so make your conclusions.

They don't need it. Wiping the NAND and reflashing it is just quicker, as they have to generate the lock password on an working 3DS and then need to get it somehow to their unbrick system.

It's possible of course that they have a dedicated unbricking rig in which they have hooked up a working 3DS to the unbrick tool they are using (via IR for example).

Or (the scenario i deem more likely) they have subcontracted the unbricking (you don't need to know anything about the inner workings of the 3DS besides the solder points to unbrick it), but didn't want to hand out their lock key generation algorithm. In other words: the general NAND backup available unbrick could be done by hirelings, and only the ones without backup get forwarded to the GW core team.

 

[naughty_cat]

Hello everyone! I was reading through some stuff on the gbatemp wiki, and I got an idea.. I noticed that there are 2 different nand chipsets, the Toshiba nand and the Samsung nand. I was thinking.. what if the brick code that got triggered by official launcher.dat files only affected either one of these 2 chipsets, but not the other?? I mean what if, for example, Gateway devs tested the 2.0b2 launchers properly on the Samsung, or the Toshiba, but not on the other?? Or maybe it's something they overlooked.. I don't know what kind of scenario I can use to try to promote this theory, I'm not experienced at all in this kind of thing, though I strongly suggest that we try to find out the types of nand chipsets on the consoles that got bricked from their owners.. maybe we could find a pattern??

 

[naughty_cat]

Sorry, double post.

 

[Squall]

Hello everyone! I was reading through some stuff on the gbatemp wiki, and I got an idea.. I noticed that there are 2 different nand chipsets, the Toshiba nand and the Samsung nand. I was thinking.. what if the brick code that got triggered by official launcher.dat files only affected either one of these 2 chipsets, but not the other?? I mean what if, for example, Gateway devs tested the 2.0b2 launchers properly on the Samsung, or the Toshiba, but not on the other?? Or maybe it's something they overlooked.. I don't know what kind of scenario I can use to try to promote this theory, I'm not experienced at all in this kind of thing, though I strongly suggest that we try to find out the types of nand chipsets on the consoles that got bricked from their owners.. maybe we could find a pattern??

If its different by chip, that in the middle contacts for nand dumb - it different that I have seen here and with my brick console!

 

[naughty_cat]

I'm sorry.. I don't understand what you're saying.. are you saying that you had a console that got bricked, and it had a chip different from the chips in other bricked consoles??

 

[Squall]

I'm sorry.. I don't understand what you're saying.. are you saying that you had a console that got bricked, and it had a chip different from the chips in other bricked consoles??

yes

 

[naughty_cat]

I see.. well do you have any idea as well about the real sysnand in some of the bricked consoles?? Were they mixed (like some 4.5, some 4.3, etc..)?? I know I'm late in the game, but still it wouldn't harm to try to find a pattern somewhere..

 

[J. Sinclair]

Hmm... The first time I loaded the emuNAND after I updated it did freeze... for a while. Did a reboot and then it worked.