Hardware transfer stuff from a bricked N3DS to a new N3DS?

[DJPlayer]

Hey Guys,

today, a friend of mine called me that he has bricked his N3DS by deleting the first Application of his NAND with FBI.
I checked which file it was on my own N3DS. it was "0328builder -> TitleID: 0004013000001b02".
His N3DS won't boot anymore (only blackscreen and blue light).
He bought a N3DS (same model, N3DS -> YEM1005) and he asked me if it is possible to transfer his stuff (NNID and other stuff) from his dead N3DS to his new 3DS which is unlinked right now.
I'm able to NAND-Mod his N3DS and it would be interesting to know if it is possible to transfer some of the stuff (especially his friendlist and his NNID) to the New N3DS.
He does not have a NAND-Backup of his COnsole so I think we can't unbrick it.
But I want to help him to transfer his stuff to the new N3DS (because he's not able to transfer his NNID).
The Recovery Mode (A+R+L+Up(DPad)) Seems not work.

Could you help us with this problem?

 

[Monty Kensicle]

As far as I understand, NAND backups are only useful for restoring to a 3DS in their entirety. And since they're encrypted on a per console basis there's no way currently to pull any data out of them.

 

[DJPlayer]

As far as I understand, NAND backups are only useful for restoring to a 3DS in their entirety. And since they're encrypted on a per console basis there's no way currently to pull any data out of them.

not sure, but can I dump the NAND of the bricked N3DS with Hardmod and create xorpads for it on another N3DS?
With the xorpads, I could dump the fat16-partition and possibly copy files out of it.
But for this, I need to know how to create the needed xorpads for the NAND

 

[The Real Jdbye]

not sure, but can I dump the NAND of the bricked N3DS with Hardmod and create xorpads for it on another N3DS?
With the xorpads, I could dump the fat16-partition and possibly copy files out of it.
But for this, I need to know how to create the needed xorpads for the NAND

NAND xorpads are console-unique.

 

[DJPlayer]

NAND xorpads are console-unique.

is it not possible to create a file like ncchinfo.bin for GAmes a bin-file for the Bricked3DS-Nand and create the xorpads with the bin-file via Decrypt9?

Is there ANY other way to fix the bricked N3DS or get the files from it to use it on another 3ds?

 

[The Real Jdbye]

is it not possible to create a file like ncchinfo.bin for GAmes a bin-file for the Bricked3DS-Nand and create the xorpads with the bin-file via Decrypt9?

Is there ANY other way to fix the bricked N3DS or get the files from it to use it on another 3ds?

Without a (working) NAND backup, there's NO way.

 

[DJPlayer]

Without a (working) NAND backup, there's NO way.

Argh, that suck ~___~

 

[Apache Thunder]

You had to have created xorpads of a nand backup of the console before it bricked before you can extract files from it. Had he done so you could have him extract movable.sed and data folder from ctr_nand partition to move to the other console. (he'd have to call nintendo and have the unlink the dead console and move it to the other console first). Then once the NNID is moved over, the moved data will work on the new console. (the movable.sed would need some alterations first to avoid a brick)

However this seems not the case. Does he even have a backup of NAND? Any one with common sense that has a console with exploitable firmware has to have at least used the gateway menu to make a full nand backup at least once. (said feature doesn't even require that you own a Gateway)

If not, he's really boned. He can still move his account over to the new 3DS by calling Nintendo and he can redownload all the games he had on the bricked 3DS. But his friendcode and save games are gone forever unless he can get a backup of NAND restored to that bricked 3DS via a NAND mod. If he doesn't have a backup, then even a NAND mod won't save it.

Once he gets the account moved over, he should consider selling the bricked unit. I'm sure there are some here who could buy one and replace part of the motherboard and have a working console. It would help him recoup some of the loss.

 

[DJPlayer]

You had to have created xorpads of a nand backup of the console before it bricked before you can extract files from it. Had he done so you could have him extract movable.sed and data folder from ctr_nand partition to move to the other console. (he'd have to call nintendo and have the unlink the dead console and move it to the other console first). Then once the NNID is moved over, the moved data will work on the new console. (the movable.sed would need some alterations first to avoid a brick)

However this seems not the case. Does he even have a backup of NAND? Any one with common sense that has a console with exploitable firmware has to have at least used the gateway menu to make a full nand backup at least once. (said feature doesn't even require that you own a Gateway)

If not, he's really boned. He can still move his account over to the new 3DS by calling Nintendo and he can redownload all the games he had on the bricked 3DS. But his friendcode and save games are gone forever unless he can get a backup of NAND restored to that bricked 3DS via a NAND mod. If he doesn't have a backup, then even a NAND mod won't save it.

Once he gets the account moved over, he should consider selling the bricked unit. I'm sure there are some here who could buy one and replace part of the motherboard and have a working console. It would help him recoup some of the loss.

Thank you for the info.
Badly, there's no existing NAND Backup of his 3DS, I could make one with a NAND Mod but If we're unable to decrypt the NAND (or only the fat16 Partition), it won't be useful...
The Savegames will be lost? Do you mean, he can't use his Savegames which are saved on his SD Card (title/gameid/data/**.sav)?
Oh, that will really suck^^'

 

[The Real Jdbye]

You had to have created xorpads of a nand backup of the console before it bricked before you can extract files from it. Had he done so you could have him extract movable.sed and data folder from ctr_nand partition to move to the other console. (he'd have to call nintendo and have the unlink the dead console and move it to the other console first). Then once the NNID is moved over, the moved data will work on the new console. (the movable.sed would need some alterations first to avoid a brick)

However this seems not the case. Does he even have a backup of NAND? Any one with common sense that has a console with exploitable firmware has to have at least used the gateway menu to make a full nand backup at least once. (said feature doesn't even require that you own a Gateway)

If not, he's really boned. He can still move his account over to the new 3DS by calling Nintendo and he can redownload all the games he had on the bricked 3DS. But his friendcode and save games are gone forever unless he can get a backup of NAND restored to that bricked 3DS via a NAND mod. If he doesn't have a backup, then even a NAND mod won't save it.

Once he gets the account moved over, he should consider selling the bricked unit. I'm sure there are some here who could buy one and replace part of the motherboard and have a working console. It would help him recoup some of the loss.

Nintendo don't generally transfer over NNIDs, but it's worth a shot. I've seen some people claiming they can do that but no confirmed reports of them actually ever having done it. It's more of a rumor.

 

[Apache Thunder]

It's not a rumor. I've done it myself. I bricked my original 3DS back in late January/February and called Nintendo and told them my old 3DS stopped working and no longer boots and wanted to transfer the account over to a new console. They will not unlink it without relinking it to a new console. So you need a console to move it to. They asked me some security questions like what my most recent purchase history was on the old 3DS. Then told me they passed it off to their back office and the account would transfer over in 1-2 days. Once it does they emailed me telling me it was done.

At that point all I had to do is relink my NNID to the new console via the NNID menu in system settings. That's all there is to it. Of coarse if they ask how it stopped working, you'll have to come up with a story. Tell them it's something like water damage from a pool or something. I didn't have to say much on how it happened to mine. I just told them it didn't work and wanted to move it over. Oh and they'll ask you how long ago it stopped working.

Also make sure the console you are moving it to does not have an NNID already linked to it.

Thank you for the info.
Badly, there's no existing NAND Backup of his 3DS, I could make one with a NAND Mod but If we're unable to decrypt the NAND (or only the fat16 Partition), it won't be useful...
The Savegames will be lost? Do you mean, he can't use his Savegames which are saved on his SD Card (title/gameid/data/**.sav)?
Oh, that will really suck^^'

Yeah. Save games will not be recoverable as you would have no way of booting the console to gen the needed xorpads to decrypt fat16 partition. The movable.sed is the encryption seed used on SD card content like apps and save games. Without it, you have no way of getting the saves moved over.

 

[DJPlayer]

Yeah. Save games will not be recoverable as you would have no way of booting the console to gen the needed xorpads to decrypt fat16 partition. The movable.sed is the encryption seed used on SD card content like apps and save games. Without it, you have no way of getting the saves moved over.

oh :/ thanks for the info

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

Okay, @Apache Thunder ,
My friend told me, he decrypted his NAND some time ago but he only has his "Fat16.iso" file (757MB) which contains: "0.fat" and "1".
He made it form his o3DS XL before he transfered all his stuff to the N3DS.
Can we use the files in it to recover needed stuff to his n3DS?

And if yes: How can I open this fat16-partition?

 

[DjoeN]

People need to understand that making a NAND backup, the first thing to do is!!
I don't get it, that they don't do it, they are messing with FBI and cia's but doing something as simple as making a NAND backup seems to be to hard for them!

 

[DJPlayer]

People need to understand that making a NAND backup, the first thing to do is!!
I don't get it, that they don't do it, they are messing with FBI and cia's but doing something as simple as making a NAND backup seems to be to hard for them!

yea, I can't understand this, too.
But now, it happened. Finally we found on his external harddrive a dump of his fat16-partition of the NAND (o3DS). Some months after this dump he transfered his stuff from o3DS to n3DS without making a new Nand-backup. Only the fat16-partition has left (xorpad is available too) but he seems to deleted the NAND.bin.

@Apache Thunder ,
can we use the decrypted fat16-dump of his o3DS to transfer stuff to the new n3ds he has?
If yes: how we can open his fat16-partition?

 

[Apache Thunder]

You can open the ISO using WinImage assuming he is using a Windows machine. If the o3DS he system transferred to the n3DS, then that also contains the correct movable.sed and should work with the new n3DS once you call nintendo to move the account over. (as doing it now will work only partially since NNID won't work on new console yet and you need that to get the tickets moved over as you can NOT move the ticket.db file to a different console.

Once you get that far, generate xorpads for your new 3DS so that you can decrypt fat16 partition. The process to do it correctly is tricky, so I recommend modifying it and using that as emunand. (don't use it on sysnand directly unless it's a 9.2 image and if it is, make sure it boots from emunand before using it as sysnand)

If you wish, you can PM me and I can help you through the process a bit provided you have a way of uploading the fat16 iso file and the nand dump of your new n3DS with the included xorpad.

There's a lot you have to do to correctly re-encrypt the injected files and what not. It may be safer for someone else to do it for you. That I can help you with if you want. Don't post the nand files publically though. Keep those to private messages.

 

[hundshamer]

Nintendo don't generally transfer over NNIDs, but it's worth a shot. I've seen some people claiming they can do that but no confirmed reports of them actually ever having done it. It's more of a rumor.

I was one those claiming to have done it. I called Nintendo and told them I lost my 3DS and they did it for me. I had to confirm identity with a few security questions like credit card number used, games owned, etc. With Apache Thunder's testimony there's some confirmation.

 

[Apache Thunder]

Yeah, hundshamer was the one who was able to unbrick my o3DS after I sold it to him. He was nice enough to give me a decrypted nand of it so I can recover the movable.sed/data folders from fat16. Now I'm back to using my old friend code such. Even my save games were back.

 

[DJPlayer]

Yeah, hundshamer was the one who was able to unbrick my o3DS after I sold it to him. He was nice enough to give me a decrypted nand of it so I can recover the movable.sed/data folders from fat16. Now I'm back to using my old friend code such. Even my save games were back.

OKay, I was able to decrypt and open the fat16-partition.

Spoiler

Right now, my Internet Connection is not the best :/ Uploading the files will take a very long time ~___~
I made a Dump of his new n3DS right now with Gateway-Launcher and will make XORPADs for it, too.

Would you explain me what I've exactly to do to transfer the files to the new N3DS? For the first I want to try it by myself (I want to learn this, too) it would epic if you could describe what I have to do.

 

[The Real Jdbye]

I was one those claiming to have done it. I called Nintendo and told them I lost my 3DS and they did it for me. I had to confirm identity with a few security questions like credit card number used, games owned, etc. With Apache Thunder's testimony there's some confirmation.

I guess it depends on who you talk to at Nintendo, so YMMV. They certainly have the ability to do it, but it's not part of their policy AFAIK.
But like I said, it's worth a shot. I have heard good things about Nintendo's customer service in the US, but I don't know about EU. Where you live could certainly make a difference in situations like these, since NoE and NoA are more or less two separate entities and they could have different policies and such.

yea, I can't understand this, too.
But now, it happened. Finally we found on his external harddrive a dump of his fat16-partition of the NAND (o3DS). Some months after this dump he transfered his stuff from o3DS to n3DS without making a new Nand-backup. Only the fat16-partition has left (xorpad is available too) but he seems to deleted the NAND.bin.

@Apache Thunder ,
can we use the decrypted fat16-dump of his o3DS to transfer stuff to the new n3ds he has?
If yes: how we can open his fat16-partition?

Thirded.
There's a reason the GW launcher forces you to make a NAND backup before downgrading.
It still felt risky downgrading my brother's 9.2 3DS to put PBT/Palantine on it (ended up with PBT because his SD card was so small), since if it broke I would have had to send it to gamesquest to get a NAND mod installed. And that is an automated process, which is certainly safer than manually uninstalling and installing files.

Did you ask him why he decided to delete that title?
I'm really curious as to what went through his head. I doubt any guide available on the Internet would tell him to do that.

 

[gamesquest1]

oh :/ thanks for the info

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

Okay, @Apache Thunder ,
My friend told me, he decrypted his NAND some time ago but he only has his "Fat16.iso" file (757MB) which contains: "0.fat" and "1".
He made it form his o3DS XL before he transfered all his stuff to the N3DS.
Can we use the files in it to recover needed stuff to his n3DS?

And if yes: How can I open this fat16-partition?

just the encrypted fat16 partition should be enough to actually unbrick....and if he had the xorpad & decrypted nand that should also work, nand mod required ofc, but it should be enough to get the 3DS back into action

EDIT....nevermind i see your talking about a completely different 3DS now.....in which case no, nand dumps from different 3DS's won't help anyone