Hacking Gateway Brick on b2 caught on camera finally :D

[groit]

everyone make sure you back up NAND

 

[kyogre123]

Definitely the first thing I'll do when I update my second 3DS to 4.5 will be creating a NAND backup using the b1 launcher, just to be safe.

 

[Rinnux]

I already have a nand backup. But I'm backing it up again just to make sure I'm safe. I wouldn't want something dumb to happen like finding out the old backup was flawed in some way.

 

[KazoWAR]

Gateway might (keyword = might) claim you have used a modified launcher previously or a clone previously to weasel out.

It makes no sense for them to own up to anything since it is impossible to prove you have not used a modified launcher or a clone. That's the beauty of the spaghetti monster defense. Just because you can't see it does not mean it does not exist.

make a video with an unboxing if a brand new 3ds with 4.5 and repeat the process

 

[the_randomizer]

unbox a brand new 3ds with 4.5 and repeat the process

I bet they'll still be claiming that it was fake or from a clone lol

 

[cloud1250000]

Probably not... but it's not like it's the fault of any brick code, there's probably something wrong in their diagnostic function...

 

[alexenochs]

If that's the case then if he's up to it I think he should totally try doing the brick on the b1 firmware through diagnosis then that would prove its not due to gateways brick code but because of something faulty in the diagnosis application in the launcher

 

[alexenochs]

That is..if it bricks in b1 I mean

 

[cloud1250000]

It's not like there's a guaranteed that the diagnostic app in b1 is exactly the same in b2 ahah

 

[gamesquest1]

That is..if it bricks in b1 I mean

ill give it a try before i pack the raspberry pi away i think the 3ds has been through enough for 1 night personally

 

[lambstone]

make a video with an unboxing if a brand new 3ds with 4.5 and repeat the process

That's one way to do it. BUT... GW can then claim that it wasn't a sealed set and that it was a "resealed set". Unless you can get a video of the 3ds being assembled and boxed and unboxed, GW has the opportunity to deny.

Well, that's 50 bucks wasted for me. Was intending to get a new 4.5 3ds but i'm just going to ride things out.

 

[gamesquest1]

If that's the case then if he's up to it I think he should totally try doing the brick on the b1 firmware through diagnosis then that would prove its not due to gateways brick code but because of something faulty in the diagnosis application in the launcher

ok after booting gateway mode 20 times and running diagnostics each time on b1, no bricks....i cba testing any more though, but it would seem b1 is perfectly fine in terms of running diagnostics

 

[Askedforthis]

Damn, seems like I've been extremely lucky. The few times I used Gateway 2.0b2 after the bricks reports had barely started coming in I used diagnostics. In total maybe 4-5 times on b2 before switching to b1.

 

[kyogre123]

ok after booting gateway mode 20 times and running diagnostics each time on b1, no bricks....i cba testing any more though, but it would seem b1 is perfectly fine in terms of running diagnostics

You may want to try the diagnostic test thing with b2 setting the date of your 3DS to 23 December 2013 and see if it bricks. That's what I'm doing right know to prevent it (except for the diagnostic test part). Also, all of the files stored on the SD have a timestamp set at 2013.

 

[nervx]

has anyone managed to look through the gateway code to figure out where the brick code is?

we need a way to make sure the final 2.0 is safe. hopefully we can get a handful of people like gamesquest1 who can restore their systems to try and brick them with the final release.

Probably not... but it's not like it's the fault of any brick code, there's probably something wrong in their diagnostic function...

its possible the brick code is injected during the test.

 

[gamesquest1]

You may want to try the diagnostic test thing with b2 setting the date of your 3DS to 23 December 2013 and see if it bricks. That's what I'm doing right know to prevent it (except for the diagnostic test part). Also, all of the files stored on the SD have a timestamp set at 2013.

well my date is indeed still incorrect, so ill set it to dec, 2013 and see what effect it has, but this is definitely definitely my last test, the 3ds has been a loyal test subject.

 

[kyogre123]

Probably would be a pointless test since even the clone users weren't affected until around 7 January.

 

[gamesquest1]

You may want to try the diagnostic test thing with b2 setting the date of your 3DS to 23 December 2013 and see if it bricks. That's what I'm doing right know to prevent it (except for the diagnostic test part). Also, all of the files stored on the SD have a timestamp set at 2013.

well, your test results are in, andddd, you will still be bricked even with a valid date, i set it to christmas day 2013 and bricked on the 4th try running diagnostics

BUTTTTT i think we can officially say it appears to be confined to diagnostics

 

[kyogre123]

well, your test results are in, andddd, you will still be bricked even with a valid date, i set it to christmas day 2013 and bricked on the 4th try running diagnostics

BUTTTTT i think we can officially say it appears to be confined to diagnostics

But how about the files on your SD? And just to make sure, that date has to be set on the real NAND.

And to avoid creating another post. Will you forward this to Gateway?

 

[gamesquest1]

set both clocks to make sure both set to christmas, launcher file has timestamp 23/12/2013

it just looks like the bug is in the diagnostics and you have pretty much a 1 in 5 chance of it getting you

im guessing the reason all the clones got hit was due to the fact that their firmware had save bug so clone users where more likely to go running diagnostics