Hacking System transfer between hacked new 3ds?

  • Thread starter Thread starter kralde
  • Start date Start date
  • Views Views 4,001
  • Replies Replies 12

kralde

Well-Known Member
Newcomer
Joined
Mar 20, 2009
Messages
74
Reaction score
16
Trophies
1
XP
269
Country
Hi!
So my scenario is:

-Hacked new 3ds xl with Luma
-Fresh new 3ds xl hackable, but I didn't do it yet

So, I want to move from the hacked console to the new one.
The question is, how?
I was thinking in doing the following:
1-Hack the new 3DS and update it to hacked 11.4 with Luma
2-System transfer from the first console, taking care when changing micro sd in order to keep the arm file correct for both consoles


If I do this, Will I have everything copied 1:1?
Thanks!
 
1- Yes exactly.
2- The arm file is the same for both console so I don't understand what you meant there.

No, only legit ticket will be transferred, you will have to reinstall all the ticket for your non legit homebrew.
 
Hi! Thanks!
I though that the otp is unique for each console?
OR Im confused about the arm file? Does the arm file in the root of micro sd have any relation with the unique otp?

So all my games and saves will be lost!!? Even with both consoles hacked?

Thanks!
 
The OPT is unique. Don't use it on one console to the other or you will brick.

At some point in the transfer it will ask if you want to transfer the data on the SD card. Just don't, tell it you'll do it manually.
When it's done copy your Nintendo 3DS folder to the new console, everything will be there.

The process is explain somewhere on the Nintendo website, I don't remember exactly how to do it. It's also a lot faster as the wifi and write/read speed are crap.

You'll just have to reinstall the ticket for your non legit stuff because the transfer don't transfer them.
 
The otp is unique, but isn't needed on the SD. Store it with your NAND backups.

Do this:
  1. Hack second 3ds
  2. Create a CTRNAND backup of the first 3ds.
  3. Create a NAND backup of the second.
  4. Perform the system transfer.
  5. Restore the CTRNAND backup from the first to the second.
 
  • Like
Reactions: kralde
The otp is unique, but isn't needed on the SD. Store it with your NAND backups.

Do this:
  1. Hack second 3ds
  2. Create a CTRNAND backup of the first 3ds.
  3. Create a NAND backup of the second.
  4. Perform the system transfer.
  5. Restore the CTRNAND backup from the first to the second.

Are you telling him to restore a nand backup from one 3ds to a different one? If so, I'm pretty sure that will brick his 3ds.
 
The otp is unique, but isn't needed on the SD. Store it with your NAND backups.

Do this:
  1. Hack second 3ds
  2. Create a CTRNAND backup of the first 3ds.
  3. Create a NAND backup of the second.
  4. Perform the system transfer.
  5. Restore the CTRNAND backup from the first to the second.

For not being crazy myself, do a system transfer between them, placing the micro sd from. The first 3ds with the second and using the right arm file for the new console, and finally reinstall the tickets, will be fine?

Thanks a lot!

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

The otp is unique, but isn't needed on the SD. Store it with your NAND backups.

Do this:
  1. Hack second 3ds
  2. Create a CTRNAND backup of the first 3ds.
  3. Create a NAND backup of the second.
  4. Perform the system transfer.
  5. Restore the CTRNAND backup from the first to the second.
I just understood this
The crtnand is different to a common nand right? And in the case of brick, if I follow your steps, I will have available a nand to recover right?
 
Are you telling him to restore a nand backup from one 3ds to a different one? If so, I'm pretty sure that will brick his 3ds.
No, ctrnand is just part of the nand, decrypted.

The crtnand is different to a common nand right? And in the case of brick, if I follow your steps, I will have available a nand to recover right?
Yes
 
No, ctrnand is just part of the nand, decrypted.


Yes
Thanks a lot, so, by doing this, I don't have to take care of the armxxxxx
No, ctrnand is just part of the nand, decrypted.


Yes
Thanks! Just one more question, by following your steps, do I need to keep any of the arm9loaderhax.bin files from the old and new one?
Thanks a lot really!
 
Thanks a lot, so, by doing this, I don't have to take care of the armxxxxx
A9LH still needs to be installed as normal

Thanks! Just one more question, by following your steps, do I need to keep any of the arm9loaderhax.bin files from the old and new one?
Thanks a lot really!
a9lh.bin files are the same depending on the program used, but do need to be on the card
 
Hello to all,
Yesterday I finally performed all the transfer between consoles.
The method given by @Mikemk worked like a charm
I'm very grateful for all your help guys :)
 

Site & Scene News

Popular threads in this forum