Hacking 3DS unbricking progress

[cy2u5]

My card is a real DSTWO+ card.
I downloaded the update from the manufacturers website and put it onto the microSD card.
When I launched the GW_Simulator App, it asked for an update. So I confirmed and did that.
So I updated from 1.04 to 1.05.

I think emuNAND is a safer option for me....next time, if unbrick is possible

--------------------- MERGED ---------------------------

Here it is:

 

[gamesquest1]

well emunand didnt protect people last time this code was unleased, it just meant people were unaware they had been bricked until they reset their console, the freeze happens as once the nand is locked you are unable to boot into gW mode, but if you boot into emunand you are unaware you have bricked until you power down

 

[cy2u5]

well emunand didnt protect people last time this code was unleased, it just meant people were unaware they had been bricked until they reset their console, the freeze happens as once the nand is locked you are unable to boot into gW mode, but if you boot into emunand you are unaware you have bricked until you power down

Yep, I got it.

 

[Xenon Hacks]

My card is a real DSTWO+ card.
I downloaded the update from the manufacturers website and put it onto the microSD card.
When I launched the GW_Simulator App, it asked for an update. So I confirmed and did that.
So I updsted from 1.04 to 1.05.

I think emuNAND is s safer option for me....next time, if unbrick is possible

--------------------- MERGED ---------------------------

Here it is:

Rip 3DS BRICKTWO+ strikes again

 

[dsrules]

nvm....wrong quote

 

[cy2u5]

I prayed to Shigeru and he heared my voice

I hope my 3DS will revive in a few minutes

 

[dandymanz]

I prayed to Shigeru and he heared my voice

I hope my 3DS will revive in a few minutes

Oh, sorry to hear that 1.05 bricked your 3ds. Maybe i shouldn't have posted the update on the DSTWO+ . Hope you can recover your 3ds back. I'm thinking maybe the Supercard team hasn't tested all scenarios that could cause bricks? Like i seem to read that you tried to enter Gateway mode without an Emunand setup. That could be a reason i guess?

 

[cy2u5]

Hi,

my 3DS has revived and it's´working again.
the weird thing is, that it won't brick anymore, when I perform my procedure like described before....

 

[bkifft]

Hi,

my 3DS has revived and it's´working again.
the weird thing is, that it won't brick anymore, when I perform my procedure like described before....

Have you done the same sysnand settings? Especially date time and Region?

 

[cy2u5]

Yep, everything same

 

[sunkist]

My card is a real DSTWO+ card.
My 3DSXL bricked
I dont know how to revive 3DSXL
teach me revive 3DSXL
I have not emunand backup
plz I will hope that solve the problem someone

 

[milerwan]

I prayed to Shigeru and he heared my voice

I hope my 3DS will revive in a few minutes

Sorry but if your 3DS is bricked due to GW's code, normaly a NAND restoration should not be allowed to fix the blue screen (BSOD).
Do you have used Raspberry Pi to unlock the NAND first ?

 

[Deleted-236924]

Sorry but if your 3DS is bricked due to GW's code, normaly a NAND restoration should not be allowed to fix the blue screen (BSOD).
Do you have used Raspberry Pi to unlock the NAND first ?

A bit late there; just a few posts above they said it was successful.

 

[cy2u5]

Sorry but if your 3DS is bricked due to GW's code, normaly a NAND restoration should not be allowed to fix the blue screen (BSOD).
Do you have used Raspberry Pi to unlock the NAND first ?

It is allowed and it worked.
I saved a NAND dump. Later the 3DS bricked and I unlocked it with a Raspberry Pi. Then I flashed the dump with a SD card reader using win32diskimager. That's it

 

[Apache Thunder]

The unlock code is only needed if you wanted to restore the NAND without wiping it.

If you have a backup, you can force erase it. Still requires a Raspberry Pi though so a normal NAND mod isn't enough.

 

[cy2u5]

The unlock code is only needed if you wanted to restore the NAND without wiping it.

If you have a backup, you can force erase it. Still requires a Raspberry Pi though so a normal NAND mod isn't enough.

Yep, you're right. I remember that I force erased the eMMC with my RPi because Unlock (safe) didn't work.
Then I had to flash the backup with a card reader.

 

[milerwan]

This fact is new with bricking issue, normally just need to unlock the eMMC as said Apache Thunder...
Did the "unbricker" files you use have been updated with the latest version (network access at start of launching the software) ?

Is there any other report of BSOD due to DSTwo+ that need force erase + NAND writing to fix it ?
Is there any report of New 3S bricking issue too ?

 

[cy2u5]

Unlocking didn't work for me. It stayed always at "MMC is locked" and yes, it downloaded the newest version when I started 3dsunbrick. I also tried manually downloading RPI-master.zip (renamed to RPI.zip) and putting it into the USB Stick with offline booting. Also no chance for unlocking.

Only force erase and reflashing the NAND dump rescued my 3DS.

 

[hundshamer]

This fact is new with bricking issue, normally just need to unlock the eMMC as said Apache Thunder...
Did the "unbricker" files you use have been updated with the latest version (network access at start of launching the software) ?

Is there any other report of BSOD due to DSTwo+ that need force erase + NAND writing to fix it ?

Yes, this has been confirmed.

When I had my brick last year they were already using a different key. I'm pretty sure they were using AES CBC mode so you can't just use an XOR pad to unbrick anymore. If someone manages to get the key they'll have to run some 3DS homebrew with the CID to get the unlock key.

thing is, there shouldn't be a force erase option in the latest version. I've just checked again to be sure....
you seem to be running the interim version that allowed to unlock, dump, force erase. the one our resident brickophile made the howto video for.

but doesn't matter, it seems they did indeed change the unlock key.
so you (and all other who got bricked) can either do the force erase, aka completely wiping the NAND, thereby unlocking it and enabling you to restore a NAND backup or an emunand dump from the 3DS in question, or wait and pray to the gods that someone is willing to reverse engineer the latest gateway launcher to extract the NAND lock key generation (which is way beyond my skills as I hate assembler).

edit: i've re-enabled the force erase. just to reiterate: this will empty the NAND, turning the 3DS into a paper weight or door stop if there is no good NAND dump of this specific 3DS.

(i don't know if one could be generated with the console keys, but i suppose someone who doesn#t have a NAND dump will not have the keys dumped as well).

Is there any report of New 3S bricking issue too ?

AFAIK the reports all have been from original 3DS's.

 

[cdante100]

This works using a raspberry pi zero? @bkifft