Hacking Don't wanna waste time [A9LH]

[RyeHyena]

Just wondering, as I'm in the process of switching to a9lh and sysnand cfw instead of booting into emunand. I was wondering if I could copy the things from the emunand-specific folder into the future sysnand-specific folder, and flash the ticket.db, would it work? I'd always be in cfw, of course. I REALLY don't wanna reinstall 64 gb of games haha, and please don't just pull answers out of your a**, I would like a real one with some explanation.


EDIT: Or, if anyone has a way of me doing something similar, please say.

 

[Rioluwott]

You can switch emunand and sysnand
you can have cfw updated sysnand

 

[RyeHyena]

You can switch emunand and sysnand
you can have cfw updated sysnand

Not gonna inject the emunand.bin into sysnand for reasons, but wondering if I can copy files over and the ticket.db?

 

[driverdis]

I would recommend keeping EmuNAND then you can autoboot EmuNAND via AL9H (AuReiNAND). this is what I did except that I formatted my sysNAND via tinyformat so I could keep SysNAND seperate for any homebrew that needs 9.2 alongside having EmuNAND, which with autoboot will stay in EmuNAND even after going to System Settings or playing DS/DSi games. the only thing I have noticed is that GBA games will exit to SysNAND if you exit via going home rather than powering off first.

 

[Rioluwott]

Not gonna inject the emunand.bin into sysnand for reasons, but wondering if I can copy files over and the ticket.db?

it doesn´t work like that

 

[RyeHyena]

I would recommend keeping EmuNAND then you can autoboot EmuNAND via AL9H (AuReiNAND). this is what I did except that I formatted my sysNAND via tinyformat so I could keep SysNAND seperate for any homebrew that needs 9.2 alongside having EmuNAND, which with autoboot will stay in EmuNAND even after going to System Settings or playing DS/DSi games. the only thing I have noticed is that GBA games will exit to SysNAND if you exit via going home rather than powering off first.

I would really rather switch to permanent sysnand cfw, as emunand has its pains. Do you have any ways I could get content from emunand to sysnand aside from backing up saves and spending hours on installing cias?

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

it doesn´t work like that

Why not?

 

[driverdis]

I would really rather switch to permanent sysnand cfw, as emunand has its pains. Do you have any ways I could get content from emunand to sysnand aside from backing up saves and spending hours on installing cias?

https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax-&-AuReiNAND)
follow the steps for copying EmuNAND data to SysNAND
I would make sure EmuNAND and SysNAND are on the same firmware version first to avoid any issues doing this
use Decrypt9 to do this, the guide mentions using it but does does so in a way that you can miss it easily.

If you are switching over still, it would be better to follow the guide exactly in case there is an issue doing this using a different guide.

 

[OrGoN3]

I would recommend keeping EmuNAND then you can autoboot EmuNAND via AL9H (AuReiNAND). this is what I did except that I formatted my sysNAND via tinyformat so I could keep SysNAND seperate for any homebrew that needs 9.2 alongside having EmuNAND, which with autoboot will stay in EmuNAND even after going to System Settings or playing DS/DSi games. the only thing I have noticed is that GBA games will exit to SysNAND if you exit via going home rather than powering off first.

Except there is very little reason to do this. What homebrew do you require to use that doesn't have native A9 booting by now?

 

[Grumpsta]

If you are following Plailect's guide the flash over for emuNAND to sysNAND is not for your files, but rather to grab the OTP... The last step in the OTP Retrieval section states to restore your original sysNAND before proceeding. I think you are confused with how the process works. Your games get transferred over when you copy your emuNAND partitions (CTRNAND, AGBSAVE Partition, TWLN Partition).

 

[RyeHyena]

If you are following Plailect's guide the flash over for emuNAND to sysNAND is not for your files, but rather to grab the OTP... The last step in the OTP Retrieval section states to restore your original sysNAND before proceeding. I think you are confused with how the process works. Your games get transferred over when you copy your emuNAND partitions (CTRNAND, AGBSAVE Partition, TWLN Partition).

thanks, wasn't following any guide, but will follow the guide other guy mentioned. thanks all!

 

[driverdis]

If you are following Plailect's guide the flash over for emuNAND to sysNAND is not for your files, but rather to grab the OTP... The last step in the OTP Retrieval section states to restore your original sysNAND before proceeding. I think you are confused with how the process works. Your games get transferred over when you copy your emuNAND partitions (CTRNAND, AGBSAVE Partition, TWLN Partition).

if you look at the last section, Part 5; It has a secondary copy from emuNAND to sysNAND so you can migrate from emuNAND to sysNAND only CFW.

 

[Deleted User]

Out of curiosity, and for learning purposes. If you already have a A9LH booting to emuNAND, do you really need to go back to pre-A9LH for updatedSysNAND conversion?

 

[Grumpsta]

if you look at the last section, Part 5; It has a secondary copy from emuNAND to sysNAND so you can migrate from emuNAND to sysNAND only CFW.

You are not restoring your full emuNAND image though, your just merging certain partitions. The OP was concerned:

Not gonna inject the emunand.bin into sysnand for reasons

I was letting him know that the flash of emuNAND.bin was for the OTP retrieval and not a permanent configuration, as he will flash his original sysNAND.bin to sysNAND. Not sure if your reply was intended for me or the OP to clarify CTRNAND, AGBSAVE, and TWLN Partitions from part 5.

Out of curiosity, and for learning purposes. If you already have a A9LH booting to emuNAND, do you really need to go back to pre-A9LH for updatedSysNAND conversion?

No, you should be able to just copy those partitions I listed above from your emuNAND to your sysNAND via Decrpt9. If you want to remove emuNAND all together, just remember you will need to reformat your SD Card so it would probably be a good idea to back it up before you do so!

 

[Deleted User]

No, you should be able to just copy those partitions I listed above from your emuNAND to your sysNAND via Decrpt9. If you want to remove emuNAND all together, just remember you will need to reformat your SD Card so it would probably be a good idea to back it up before you do so!

So if I'm following the guide, I can just skip up to "Configuring AuReiNAND"? Setting the flags first?

Edit: meant I already have all the files and such

 

[Grumpsta]

So if I'm following the guide, I can just skip up to "Configuring AuReiNAND"? Setting the flags first?

Edit: meant I already have all the files and such

Exactly

 

[driverdis]

You are not restoring your full emuNAND image though, your just merging certain partitions. The OP was concerned:



I was letting him know that the flash of emuNAND.bin was for the OTP retrieval and not a permanent configuration, as he will flash his original sysNAND.bin to sysNAND. Not sure if your reply was intended for me or the OP to clarify CTRNAND, AGBSAVE, and TWLN Partitions from part 5.


No, you should be able to just copy those partitions I listed above from your emuNAND to your sysNAND via Decrpt9. If you want to remove emuNAND all together, just remember you will need to reformat your SD Card so it would probably be a good idea to back it up before you do so!

You an also remove EmuNAND by using a partition manager that can resize partitions. This allows for removal without reformatting by resizing the FAT32 Partition over the "empty" partition on the SD Card.

 

[Deleted User]

You an also remove EmuNAND by using a partition manager that can resize partitions. This allows for removal without reformatting by resizing the FAT32 Partition over the "empty" partition on the SD Card.

Yep, that saves a lot of time. Makes it so you can just extend the partition over emuNAND without having to backup data first.