Conserte seus objetos Comunidade Loja

The Nintendo 3DS XL 2015, marketed as the New Nintendo 3DS XL, was released October 11, 2014 in Japan and February 13, 2015 in North America.

20 Perguntas Visualizar todos

Opções

How to transfer EVERYTHING with one 3DS? (NEEDS THERAPY)

So this is a kinda dumb question, but I've been FREAKING out because i think i may have lost everything.. sort off.. So this all started when i got a brand new 3DS. Did a system transfer, Everything was fine! ..that's until it broke 2 MONTHS LATER. and nobody could fix it (this is not the problem I'm talking about yet) so the dumb person i am, I threw it away rookie mistake i know.. :( and i decided to get another 3ds for a GREAT price! Now, could you transfer everything with just these files? "010101_QW12906450_sysnand_00.bin" "010101_QW12906450_sysnand_00.bin.sha" and lastly, "essential.exefs"? i also do have the Nintendo 3DS folder, and the DCIM, i pretty much have everything, and yes, i know it MAY not be possible to do, because i am missing the "movable.sed" but im begging, Is there a way to get all of the data back from using CFW?!?! if i cant, then i know there's a way around, like using checkpoint, or contacting Nintendo to get rid of the NNID on my broken one (that i threw away ugh..) and some more, but i just HOPE there's a answer. Thanks!

UPDATE NOVEMEBER 11, 2024

Thanks to darthmango, i can do this and maybe recover everything!

So.. SD:\Nintendo 3DS folder has a 32-character ID0 folder whose name is derived using your movable.sed file, which controls encryption on your console.

HELP!!!!!! please-

Respondido! Ver a resposta Também tenho esse problema

Esta é uma boa pergunta?

Sim Não
Pontuação 3
4 comentários

Hi!

I’ll leave this to @darthmango. He probably do know if this is possible with a CFW 3DS.

por

Ok, thanks so much! :)

por

Sure, it's possible. movable.sed is actually contained within essential.exefs, so in theory it should be possible to pull all the relevant files, decrypt them, then reencrypt with the new key and load them onto your new console. The process is a bit complex to explain though, so it'll take me a bit to put together a proper walkthrough

por

@darthmango THANK YOU SO MUCH :DDD YESSS

por

Adicionar um comentário

4 respostas

Filtrar por:
Mais úteis Mais recentes Mais antigas
Solução escolhida

Opções

@darthmango i have FIXED IT SOMEHOW. so 1st of all, the movablemoveover? i was stupid, i just had to rename it movable.sed and NOT .bin lol, then it said my old 3ds number, and it fixed my movable! and NOT ONLY THAT, i factory resetted before this, and doing research (since i didnt want to brick it if it even just said it worked.) and for some reason... i decided to go download ninfs because... on thier newest update it said. FIX CORRUPT CTRTRANSFER. and after doing some research, that is the WHOLE NAND. (i think) but not the other 2 drives,) and when i did that, oh? the ctrtransfer file came from that corrupt nand and somehow. to the lord.. IT GAVE ME ALL OF MY SYSTEM DATA, AND ALL OF MY APPS. not even joking,

Block Image
Block Image
Block Image
Block Image
Block Image

I restored, EVERYTHING. i took a risk, and it WORKED. so thank you for helping @darthmango , you helped me with my hacking skills and more. Anything else before we end this chat? i mean, i already did everything at this point soo uh.. Yea! :DD

(and yes, all i did was ninfis, saw the ctrnand.img inside of the nand.bin, transfered it into my 3ds, deleted the data folder inside of ctr and replaced it with the OLD, (after the transfer was done) and bam, everything worked @darthmango !)

Esta resposta foi útil?

Sim Não
Pontuação 0

2 comentários:

@darthmango also just asking, how would my 3ds be bricked if i unmodded it?

por

@darthmango and a little bit of an update, i have alot of dsiware, and.. since i fixed the movable.. i cannot seem to transfer my data in system settings, it just saids that it failed. Not really nessasary but..

por

Adicionar um comentário
Pergunta mais útil

Opções

@darthmango UPDATE!! Something happened to my 3ds.. Same thing.. But one different number code. If you go back to my 1st post when. II bricked it, and looked really closely to the numbers on top, the 2nd digit changed right after I did the X+Y+SELCET+START I can't tell if its good or bad news, since if I did that and it shows a other code, it may be 100% doomed..

Block Image

Esta resposta foi útil?

Sim Não
Pontuação 5

6 comentários:

@darthmango.. it.. it does it without.. the r4 card.. i dont wanna get another 3ds :( i mean, ig i could ask somebody to put a new nand inside of the system and shouder the pins.. but thats really my only opinon tbh

por

@wyattd it's no more doomed than it was a few hours ago. In fact, it's one step closer to revival. Can you get your NAND backup from THIS console and copy it to the /gm9/out/ folder on the 3ds's SD card?

por

@darthmango :0 yes, I think so! Since I do have it

por

@darthmango well, I mean- I do have my old one (that we need to transfer) cuz as you said:

"It's probably not actually corrupted, the 3ds just doesn't know what to do with it since the backup you used was from the wrong console. If you want to be sure, verify the file against its SHA hash. The NAND restore script does that anyway though, so just use the right backup this time and everything should be normal"

So uh.. Yea BUT EVEN WORSE, I DOINT EVEN THINK I HAVE THE NAND FOR THE NEW CONSOLE BEFORE IT WAS EVEN BRICKED.😐 so ima do some research for awhile and update you if I have it

por

@wyattd OK. The filename contains the console's serial number, so you can check it against that. (you probably knew that though)

por

Exibir mais 1 comentário

Adicionar um comentário

Opções

Welp, I just found out the wiki already has a guide on this: https://wiki.hacks.guide/wiki/3DS:Movabl...

Two questions for you:

1: Is there anything on the new console that you care about?

2: Are you set on having a stock console after this is done?

If the answer to both of those is no, you can simply follow that guide and keep the CFW. Otherwise, we'll need to use ninfs to merge your data to the new console, then rebuild title.db. I should be able to get the specific steps for that option in a few hours, but assuming you still want to uninstall later, step 1 would be as follows:

  • Back up any files you may care about, particularly the Nintendo 3DS folder
  • Delete all titles you did not install from the eShop, including FBI, Anemone, FTPD, etc. (Keep gm9, we still need that)
  • Format the console through System Settings
  • Do not install any CIAs/illegitimate titles from this point forward. Everything we need will be done through gm9 and possibly HBL

The purpose of doing this now is to clear any illegitimate tickets, theoretically allowing you to skip formatting during uninstall (which would reshuffle the movable.sed) without breaking the eShop.

You can also go ahead and dump the new movable, we're gonna need it. It should be in the SYSNAND VIRTUAL drive iirc

Update (11/27/24)

Back with the rest of the steps! As I understand it, the process should go like this:

  1. Mount the source (old) Nintendo 3DS folder in ninfs and copy the contents of its ID1 to your computer
  2. Mount the target Nintendo 3DS folder with the new movable.sed you dumped. (Remember the format earlier will have shuffled it)
  3. Take everything you copied in step 1, and copy it inside the ID1 of the target Nintendo 3DS folder
  4. Unmount and close ninfs, then follow https://wiki.hacks.guide/wiki/3DS:Rebuil... to rebuild the title database and hopefully make your games appear

We might have to mess with tickets to get this working, I'm not entirely sure. Hopefully not. (In any case, DON'T run faketik, even if that page tells you to)

Esta resposta foi útil?

Sim Não
Pontuação 4

42 comentários:

sounds good!

por

i both have the answer NO to the 2 answers.. and i done step 1, and i did unstall any modded apps before i lost everything! *its a long story why, but i still kept the cfw* so step 2 done, but wdym by forrmating the console in system settings? cuz all im gonna do is as i said to just transfer the nand, and movable then git rid of cfw all of this by using only godmode9 cuz, if you go into the scripts you can git rid of cfw compelely then once im done i turn off the console then lastly on my pc, i take out the micro sd card on the 3ds and delete the modded files and im done.. so maybe i misunderstood what i was saying or something else idk- sorry for not saying stuff right, i am austic and cant even think as well anymore :( and remember, i only have ONE 3ds

por

@wyattd Yeah, that's the thing. Changing the movable.sed and then uninstalling CFW will brick your 3ds. That includes using a movable from a different console. If you're okay with keeping CFW at the end of this, you can just follow the movable moveover page I linked above and be done.

But, if you want CFW gone, keeping your data requires a different procedure, which the rest of the answer goes through

por

so really, the answer is that i can get all of my data back, but if i git rid of the cfw, it will be bricked. so all of the files the nand, and moveable, i can transfer, but unmodding it will brick it, am i correct? @darthmango

por

@wyattd If you're copying the movable over, then that's correct, yes.

However, I did update my answer with a method that _should_ allow you to both recover your data and still uninstall cfw

por

Exibir mais 37 comentários

Adicionar um comentário

Opções

Alright, final stretch! Here's what to do now:

  1. Remove the 010101 backup file from /gm9/out/ . Store it somewhere safe.
  2. Download GodMode9 from here.
  3. Copy GodMode9.firm to the root of your SD card and rename it to boot.firm
  4. Copy the /gm9/ folder to the root of your SD card. Overwrite files if it asks.
  5. Eject the SD card and reinsert it into your 3DS
  6. Insert the flashcart and boot from it (START + SELECT + X + magnet)
  7. If done correctly, you will have booted into GodMode9
  8. Press HOME, then select Scripts... > GM9Megascript > Restore Options > SysNAND Restore (full)
  9. Select your NAND backup
  10. Press A to unlock SysNAND (lvl3) writing, then input the keycombo given
  11. When the script finishes, press A to continue
  12. Press B to return to the main menu, then select Exit. Relock write permissions if it asks
  13. Hold R and press START to poweroff
  14. Insert your SD card back into your computer
  15. Download Luma3DS from here.
  16. Copy boot.firm and boot.3dsx to the root of your SD, overwriting the existing boot.firm
  17. Eject the SD card and reinsert it into your 3DS

Then just power on and hope for the best.

Esta resposta foi útil?

Sim Não
Pontuação 2

34 comentários:

Thanks!! ill try. If this works. You are a legend, like respect to you :D

por

@darthmango and also which nand? The one that has the corrupted one or the one with came with this one I got?

por

@darthmango uhhhh update i did the 1st 6 steps and im not into gm9, it still says the error code but same thing, with an 2 switched instead of a 0 i did everything right??

por

@wyattd including the magnet?

por

@darthmango or maybe its the card its self for the flashcart, cuz maybe the files i did r in the wrong place like for ex the backup.bin and the enject but im sure i did it right.. ALSO BOTH CARDS WERE HEATING UP so maybe it was trying to do something idk

por

Exibir mais 29 comentários

Adicionar um comentário

Adicionar a sua resposta

WyattDYT será eternamente grato(a).
Exibir estatísticas:

Últimas 24 horas: 3

Últimos 7 dias: 33

Últimos 30 dias: 94

Duração total: 1,235