Hacking So I backedup my emunand titles

[funnystory]

The below guide was written by @cearp
my idea...
system transfer.
this will let you use the encrypted stuff on your old 3ds on your new3ds.
then, copy the games installed on the sd card over.
i guess you won't have the tickets needed after the transfer... you will have to install them...
dump the tickets first with FunkyCIA, then... yifanlu made a ticket installer homebrew.
this should all work, no cia installing needed


the best answer i think for you.
not so simple i guess. but very possible. good luck
best answer you will get in my opinion




So I ended up with a folder called titles(supposedly my tickets weighing around 163mb)

I cannot find the yifanlu ticket installer homebrew

My main goal was to transfer cias already installed on 03ds and pass them to new 3ds. Cearp told me to dump the tickets and I could transfer my title folder(50gb) to my new3ds and they should all load as long as I have the tickets. The problem is I don't know how to reinject the tickets into my new 3ds emunand. Can someone lend some help or show me the yifanlu ticket installer?

 

[Tony_93]

I don't think you can do that.

NANDS are unique per system regardless of NNID.

If you want the cias in your N3DS you have to download and install them from scratch.

 

[funnystory]

I don't think you can do that.

NANDS are unique per system regardless of NNID.

If you want the cias in your N3DS you have to download and install them from scratch.

@cearp told me that it was indeed posssible

 

[driverdis]

I don't think you can do that.

NANDS are unique per system regardless of NNID.

If you want the cias in your N3DS you have to download and install them from scratch.

If you dump tickets, it is no longer unique as the thing that makes NANDs unique is that they are encrypted per console, and in this case, files in the NAND are being swapped rather than the whole NAND dump. In this case,dumping and injecting movable.sed along with ticket.db should be enough to work.

 

[funnystory]

If you dump tickets, it is no longer unique as the thing that makes NANDs unique is that they are encrypted per console, and in this case, files in the NAND are being swapped rather than the whole NAND dump. In this case,dumping and injecting movable.sed along with ticket.db should be enough to work.

This is one of the titlekeys I dumped emu_0004013800000202.app . Could I just reinject these into my n3ds and wallah?

 

[driverdis]

This is one of the titlekeys I dumped emu_0004013800000202.app . Could I just reinject these into my n3ds and wallah?

without injecting ticket.db, the title key will probably not be recognized as it is not in the database.I could be wrong, hopefully, someone who has more in depth knowledge on this can chime in on the subject. I would try to inject ticket.db along with movable.sed then inject your title keys, that should be enough to act like a system transfer.afterward, you should be able to put the SD card in the n3ds and use it.

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

The only issue I can see is that you are going from o3ds to n3ds and the n3ds ticket.db may contain n3ds exclusive system titlekeys , I do not know what the results will be injecting it. However, I see no issues doing this to a same region same firmware o3ds as the system titles should match in ticket.db.

 

[funnystory]

without injecting ticket.db, the title key will probably not be recognized as it is not in the database.I could be wrong, hopefully, someone who has more in depth knowledge on this can chime in on the subject. I would try to inject ticket.db along with movable.sed then inject your title keys, that should be enough to act like a system transfer.afterward, you should be able to put the SD card in the n3ds and use it.

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

The only issue I can see is that you are going from o3ds to n3ds and the n3ds ticket.db may contain n3ds exclusive system titlekeys , I do not know what the results will be injecting it. However, I see no issues doing this to a same region same firmware o3ds as the system titles should match in ticket.db.

I bricked my emunand either with the titles drag n drop or with the injecting ticket.db. Something did not work out.

 

[funnystory]

my emunand is bricked even after replacing the nintendo 3ds folder back to the old one.Any tips?

 

[driverdis]

my emunand is bricked even after replacing the nintendo 3ds folder back to the old one.Any tips?

create a new EmuNAND. I am not sure how to get this to work going from a o3ds to a n3ds. Transferring ticket.db should work from o3ds to o3ds as both share system titles but the n3ds has different titles. I guess the best thing to do would be to get some help from others, whom seem to be ignoring this thread for some reason.

 

[funnystory]

create a new EmuNAND and
create a new EmuNAND. I am not sure how to get this to work going from a o3ds to a n3ds. Transferring ticket.db should work from o3ds to o3ds as both share system titles but the n3ds has different titles. I guess the best thing to do would be to get some help from others, whom seem to be ignoring this thread for some reason.

Im creating a new emunand but I am afraid im going to lose my zelda progress

 

[driverdis]

Im creating a new emunand but I am afraid im going to lose my zelda progress

progress should be stored on the SD card, not NAND so your progress should be safe.

 

[funnystory]

progress should be stored on the SD card, not NAND so your progress should be safe.

that would be a homerun

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

progress should be stored on the SD card, not NAND so your progress should be safe.

weird zelda ocarina of time said it was already installed but it wasnt showing up. That tickets thing is no joke,and your right I have no doubt the ticket injection would have worked on an o3ds to o3ds transfer.

 

[cearp]

If you dump tickets, it is no longer unique as the thing that makes NANDs unique is that they are encrypted per console, and in this case, files in the NAND are being swapped rather than the whole NAND dump. In this case,dumping and injecting movable.sed along with ticket.db should be enough to work.

i don't think... (maybe, but i don't think) we can inject the ticket.db after system transfer. but yes why not? it's worth a shot
nicer than installing the tickets -
ok - don't inject the old ticket.db it won't work because n3ds needs new system titles and they won't exist in the o3ds ticket.db so = blackscreen
install the tickets

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

@funnystory
https://github.com/yifanlu/3DSSystemTools/tree/master/3DSInstallTickets

maybe a compiled version is somewhere... sorry for not checking this before

 

[driverdis]

i don't think... (maybe, but i don't think) we can inject the ticket.db after system transfer. but yes why not? it's worth a shot
nicer than installing the tickets -
ok - don't inject the old ticket.db it won't work because n3ds needs new system titles and they won't exist in the o3ds ticket.db so = blackscreen
install the tickets

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

@funnystory
https://github.com/yifanlu/3DSSystemTools/tree/master/3DSInstallTickets

maybe a compiled version is somewhere... sorry for not checking this before

Yea, I tried helping the OP but then realized the same thing, ticket.db can only be swapped between o3ds and o3ds and n3ds and n3ds becuase of specific titles that do not exist on one another.

 

[cearp]

Yea, I tried helping the OP but then realized the same thing, ticket.db can only be swapped between o3ds and o3ds and n3ds and n3ds becuase of specific titles that do not exist on one another.

i guess you could do it then reinstall the fw but that is risky.

we either need to find a compiled 3DSInstallTickets, ideally with the latest hacks, or this project is a no go.
UNLESS the system transfer ports over all the illegal tickets but i doubt that, surely it will ignore/skip them.

 

[funnystory]

i guess you could do it then reinstall the fw but that is risky.

we either need to find a compiled 3DSInstallTickets, ideally with the latest hacks, or this project is a no go.
UNLESS the system transfer ports over all the illegal tickets but i doubt that, surely it will ignore/skip them.

I pretty much fucked myself over because now I have no browserhax on emunand or sysnand(i had to recreate emunand from scratch)