Hacking 3DS Bricked with Gateway Launcher 2.0b1...

[profi200]

Not really useful, but we will see, if there is such code or not.

Btw: Because of the coming final from Gateway, if i were you, i would be very careful with the coming firmware. I bet they included even more brick shit.

 

[ov3rkill]

The day will come when the "bricking" code will be exposed. As for now, people should play it safe.

 

[mvmiranda]

It's decided!
I'm going back to 1.2...
I'm using GW with 2.0b2, actually I used a couple of times since I'm in the middle of house moving, and I've checked SD Card launcher MD5 matches the corect MD5 but I'm too scared to remain in this beta.

Until GW releases the FINAL 2.0 with multirom AND it's confirmed "safe", I'm sticking with 1.2.

I guess that's the safer to do right now.

Can anyone confirm 1.2 the MD5?
What I have is: 5A0775D695FFF7C2F2F1574220E25E21

Cheers!

 

[aofelix]

im on 2.01b.. is that no safe?

 

[mvmiranda]

im on 2.01b.. is that no safe?

Well, according to this thread, no...
One user fro EOL got bricked while using 2.0b1.

It could be that he was using 2.0b2 and got "flagged" to be bricked then moved to 2.0b1 and got bricked but, better safe than sorry, right?

I'm moving back to 1.2.

 

[osirisjem]

Another person "outta nowhere" coming out to announce a Gateway brick at GBATemp.
And no r4i bricks.
And no 3DSLink bricks.
Just doesnt add up.

 

[gamesquest1]

how long before the bricking code infiltrates all the way back in time to Nintendo's own official 1.0 FW?

in fact maybe it will brick any snes consoles owned by people with a flash card too...cant be too careful

 

[kyogre123]

im on 2.01b.. is that no safe?

I would say it's safe. I don't fully believe that report from the Spanglish forum and the analysis of both launchers neither is backing up the possibility.

 

[aofelix]

thanks. can someone give me a d/l link for 1.2?

and what are the disadvantages to using 1.2? i'm basically wanting to play KH ddd,

 

[Ryukouki]

thanks. can someone give me a d/l link for 1.2?

and what are the disadvantages to using 1.2? i'm basically wanting to play KH ddd,

Sadly we cannot provide download links due to the DMCA notice submitted to this website a while back. 1.2 has lower compatibility and no emuNAND.

 

[darkziosj]

1 random report from a spanish site mmm.

 

[PanCyan]

I have to post this again because I'm curious.

10 bricked 3DS's isn't going to stop me from using 2.0b2 lol. Oh and I am excited for this next release. Like this post if you agree with me 100%

 

[Huntereb]

Another person "outta nowhere" coming out to announce a Gateway brick at GBATemp.
And no r4i bricks.
And no 3DSLink bricks.
Just doesnt add up.

Because R4/Link downgraded their firmware and announced the issue to its users, so no new bricks are occuring. We're still getting bricks from Gateway because their firmware is infected with a virus, yet they still are insisting people use it.

 

[samljer]

It's decided!
I'm going back to 1.2...
I'm using GW with 2.0b2, actually I used a couple of times since I'm in the middle of house moving, and I've checked SD Card launcher MD5 matches the corect MD5 but I'm too scared to remain in this beta.

Until GW releases the FINAL 2.0 with multirom AND it's confirmed "safe", I'm sticking with 1.2.

I guess that's the safer to do right now.

Can anyone confirm 1.2 the MD5?
What I have is: 5A0775D695FFF7C2F2F1574220E25E21

Cheers!

--==** taken from Gateway site **==--

These are the official release file MD5 hash numbers for all files we have ever released. Please ONLY ever use VERIFIED files.

Launcher.dat v1.0 = 062b40817fa7e1ec4b12fb8c1a9b4310
Launcher.dat v1.1a = 3a06e08a703c5ca2d43cf5ff7fcd3526
Launcher.dat v1.2 = 5a0775d695fff7c2f2f1574220e25e21
Launcher.dat v2.0b1 = bf354d2616601715ee10269bb6dcda8d
Launcher.dat v2.0b2 = 6361c5d4935af6d888ffc0646548f5dd

Blue card GW_INSTALLER.NDS (1.0 - 1.1a) = d93dfe51df98422be4856e9800a9718e
Blue Card GW_INSTALLER.NDS (1.2 - 2.0b2) = b3e570efdcc097ebc44cf24a6d53e650

GW_Release_1.0.zip = e0b7530b5d9949a47627ec86512dff5e
GW_Release_1.1a.zip = ef766280c1143e58e6d98463ddb1c98c
GW_Release_1.2.zip = 4a688acb3c6da27a92c71e5818868bcb
GW_BETA_RELEASE_2.0b1 = d2ee752831fdadce7f3cc5b42898b0ab
GW_BETA_RELEASE_2.0b2 = 6eb789292d27305351060639600c68bb

 

[mvmiranda]

--==** taken from Gateway site **==--

These are the official release file MD5 hash numbers for all files we have ever released. Please ONLY ever use VERIFIED files.

Launcher.dat v1.0 = 062b40817fa7e1ec4b12fb8c1a9b4310
Launcher.dat v1.1a = 3a06e08a703c5ca2d43cf5ff7fcd3526
Launcher.dat v1.2 = 5a0775d695fff7c2f2f1574220e25e21
Launcher.dat v2.0b1 = bf354d2616601715ee10269bb6dcda8d
Launcher.dat v2.0b2 = 6361c5d4935af6d888ffc0646548f5dd

Blue card GW_INSTALLER.NDS (1.0 - 1.1a) = d93dfe51df98422be4856e9800a9718e
Blue Card GW_INSTALLER.NDS (1.2 - 2.0b2) = b3e570efdcc097ebc44cf24a6d53e650

GW_Release_1.0.zip = e0b7530b5d9949a47627ec86512dff5e
GW_Release_1.1a.zip = ef766280c1143e58e6d98463ddb1c98c
GW_Release_1.2.zip = 4a688acb3c6da27a92c71e5818868bcb
GW_BETA_RELEASE_2.0b1 = d2ee752831fdadce7f3cc5b42898b0ab
GW_BETA_RELEASE_2.0b2 = 6eb789292d27305351060639600c68bb

Nice!
Thx!

 

[condiczek]

Because R4/Link downgraded their firmware and announced the issue to its users, so no new bricks are occuring. We're still getting bricks from Gateway because their firmware is infected with a virus, yet they still are insisting people use it.

I can't resist to reply to your post.
So as far as you're concerned - R4i/Link takes care about their clone users, and they downgraded (NOPE - not downgrade - its update on their site!), and there is no bricks on clones. Hmm okkkkkk.
And second thing - we're still getting Gateway bricks? " One Thread - All reported Gateway bricks - in this thread I see 7 bricks, thread has been edited last time on wednesday. Maybe you count photoshopico-brick one? I don't see massive Gateway bricks lately??? Do you?

 

[Huntereb]

So as far as you're concerned - R4i/Link takes care about their clone users, and they downgraded (NOPE - not downgrade - its update on their site!)

I will admit that it is shown as an "Update", you can't hide that. It has been said that maybe this is just to make users want to upgrade, as, if they just said "It's a downgrade", people would keep using their old firmware (And get bricked).

...and there is no bricks on clones. Hmm okkkkkk.

I never said that, I said that the bricks have stopped.

...in this thread I see 7 bricks, thread has been edited last time on wednesday. ... I don't see massive Gateway bricks lately??? Do you?

Yes, I'd call two days ago fairly recent.

 

[Lyrra]

We really need 2.0 final now, 2.0b1/b2 are too dangerous.

 

[gamesquest1]

would a rushed 2.0 be any safer?

 

[samljer]

We really need 2.0 final now, 2.0b1/b2 are too dangerous.

No guarantee 2.0 final will be any safer. Keep that in mind when its released.
In fact if its true, and the brick code was intentional to trap clones (and hit a few legits)
what makes you think they will remove that code from 2.0final

They havent even admitted anythings wrong, they blame everything else under the sun.