Hacking Importent Questions about a9lh and Cfw

[CrazyMaxx]

Hi, I have a New 3ds with a9lh luma, and I wanna uninstall it to use it on ofw (I use a another system with cfw). I have googled about and get to uninstall a9lh with savea9lhuninstaller tool, but the step I need help is, how I get my emunand with my Nintendo ID back to my Sysnand? Can I make simply after delete emundand and custom tiles a nand backup to restore it on sysnand? Or must I use another steps like sys tranfer over another official new 3ds?

Thanks in advance

 

[Lacius]

First, there's no reason to remove CFW, and it's not recommended. You can opt to use CFW without using any features of CFW, and it's going to be the same as if you removed CFW. There's no reason to lock yourself out of CFW when you might choose to use it in the future.

What is recommended is that you follow these steps:

1. Update A9LH to B9S
2. Move your emuNAND to your sysNAND

 

[tech3475]

First, there's no reason to remove CFW, and it's not recommended. You can opt to use CFW without using any features of CFW, and it's going to be the same as if you removed CFW. There's no reason to lock yourself out of CFW when you might choose to use it in the future.

What is recommended is that you follow these steps:

1. Update A9LH to B9S
2. Move your emuNAND to your sysNAND

Presumably, the OP wants to be able to use the system without the risk of a ban of some kind, even just from a comfort perspective.

AFAIK, one way to remove CFW is to restore an old NAND dump but get someone to verify this first as it's inevitably risky.

 

[Lacius]

Presumably, the OP wants to be able to use the system without the risk of a ban of some kind, even just from a comfort perspective.

AFAIK, one way to remove CFW is to restore an old NAND dump but get someone to verify this first as it's inevitably risky.

Removing CFW isn't going to reduce the risk of a ban. Having used CFW up until this point might have already flagged the 3DS for a ban, and removing CFW now will only make it significantly more difficult for OP to unban the device.

Restoring an old NAND backup from before A9LH will remove A9LH if it's not a safe restore. A safe restore of a NAND dump preserves A9LH/B9S, regardless of when the NAND backup was made.

Edit: However, to reiterate what I said above, there is no reason to remove CFW.

 

[CrazyMaxx]

Thx for fast reply
The reason is i wanna have 1 ofw N3dsxl and 1 Cfw N3dsxl and I dont wanna ban on my 3ds with my Nintendo Id...
I have read right and after I restore my backup before a9lh its gone. And after this how can I get my emunand to sysnand?
I must have the Nintendo ID from the Emunand to my sysnand transfer

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

(Reply 2)

After I delete all cfw software I think have 2 ways to get my Id to ofw...
But what is saver?
Sys transfer to another system or Nand restore in Sysnand

 

[Hunter]

if you dont want a ban on the console with a nnid, the only option would be to buy a new console and transfer it to that, and dont hack it
since your consoles have already been hacked, there will be traces of that somewhere, you never know when or how nintendo gets the information, or when they will use it,

 

[CrazyMaxx]

if you dont want a ban on the console with a nnid, the only option would be to buy a new console and transfer it to that, and dont hack it
since your consoles have already been hacked, there will be traces of that somewhere, you never know when or how nintendo gets the information, or when they will use it,

This hears very good way
After remove all cfw titles and save backup all saves do you know about a sys transfer without delete on the send console a9lh? Or must before I use sys transfer delete a9lh? I have a new console with no cfw

 

[Tomy Sakazaki]

This hears very good way
After remove all cfw titles and save backup all saves do you know about a sys transfer without delete on the send console a9lh? Or must before I use sys transfer delete a9lh? I have a new console with no cfw

A way to do the transfer, not risking a ban on your NNID
0 - Don't remove CFW on hacked console, don't install CFW on new console, ever. Do a backup of sysnand/emunand of your cfw console just in case something goes awry.
1 - Backup all your saves on hacked console (JKSM), so you can copy them back to the same console after a system transfer.
2 - Perform system transfer, the target console (new console) will accept only games that you eventually had bought on eShop (it'll download every ticket of legit bought games, this won't check for fake tickets on cfw console so don't worry), all others will be unavailable to use.
3 - After doing system transfer on new console go to data management and remove everything that has a X mark on them, those games won't work on OFW.
4 - On older console reinstall any game that you want, use JKSM or your save manager of choice to restore the backups of your saves to these games.
I personally don't recommend doing a restore of a sysnand backup with your nnid on older/cfw console because I dunno if it sends data to nintendo to verify that said NNID isn't being cloned.

 

[Quantumcat]

This hears very good way
After remove all cfw titles and save backup all saves do you know about a sys transfer without delete on the send console a9lh? Or must before I use sys transfer delete a9lh? I have a new console with no cfw

You can transfer and keep A9LH on the source

A way to do the transfer, not risking a ban on your NNID
0 - Don't remove CFW on hacked console, don't install CFW on new console, ever. Do a backup of sysnand/emunand of your cfw console just in case something goes awry.
1 - Backup all your saves on hacked console (JKSM), so you can copy them back to the same console after a system transfer.
2 - Perform system transfer, the target console (new console) will accept only games that you eventually had bought on eShop (it'll download every ticket of legit bought games, this won't check for fake tickets on cfw console so don't worry), all others will be unavailable to use.
3 - After doing system transfer on new console go to data management and remove everything that has a X mark on them, those games won't work on OFW.
4 - On older console reinstall any game that you want, use JKSM or your save manager of choice to restore the backups of your saves to these games.
I personally don't recommend doing a restore of a sysnand backup with your nnid on older/cfw console because I dunno if it sends data to nintendo to verify that said NNID isn't being cloned.

Great answer! For 4. it's ok to restore sysNAND - the NNID is server side and can't be cloned, it will definitely be in the target console only. OP might get some errors trying to use NNID based things on the source after the restore (the console believes it has an NNID but the servers disagree), but that can be fixed by injecting a blank nnidsave.bin (see https://3ds.guide/troubleshooting for steps).

 

[CrazyMaxx]

I think with all your answers I can make this, its not my consoles... They are from my best Friend, and now i have a plan to make this Thanks to all

 

[Tomy Sakazaki]

You can transfer and keep A9LH on the source

Great answer! For 4. it's ok to restore sysNAND - the NNID is server side and can't be cloned, it will definitely be in the target console only. OP might get some errors trying to use NNID based things on the source after the restore (the console believes it has an NNID but the servers disagree), but that can be fixed by injecting a blank nnidsave.bin (see https://3ds.guide/troubleshooting for steps).

@CrazyMaxx if you go throught this route (restoring backup) you don't even need to deal with save backups.
In this case you'll have:
Step -1: Copy EVERYTHING from CFW console SD to a new SD (that will be used on target console).
0 - Don't remove CFW on hacked console, don't install CFW on new console, ever. Do a backup of sysnand/emunand of your cfw console just in case something goes awry. we'll use it to restore all games and saves.
1 - Backup all your saves on hacked console (JKSM), so you can copy them back to the same console after a system transfer. JUST IN CASE, probably won't be necessary.
2 - Remove SD from source/cfw console. Perform system transfer, the target console (new console) will accept only games that you eventually had bought on eShop (it'll download every ticket of legit bought games, this won't check for fake tickets on cfw console so don't worry), all others will be unavailable to use.
3 - After doing system transfer on new console go to data management and remove everything that has a X mark on them, those games won't work on OFW.
4 - On older console reinstall any game that you want, use JKSM or your save manager of choice to restore the backups of your saves to these games.
4 - On CFW console, restore the sysnand/emunand backup (use safe option on godmode9 or hourglass9), it will reinstate the previous user of the console, making the data on original SD usable again, if something doesn't work right away you can reinstall the cias of games (or get them on freeshop) and restore backups from JKSM, but most times it'll work right away.

 

[Quantumcat]

@CrazyMaxx if you go throught this route (restoring backup) you don't even need to deal with save backups.
In this case you'll have:
Step -1: Copy EVERYTHING from CFW console SD to a new SD (that will be used on target console).
0 - Don't remove CFW on hacked console, don't install CFW on new console, ever. Do a backup of sysnand/emunand of your cfw console just in case something goes awry. we'll use it to restore all games and saves.
1 - Backup all your saves on hacked console (JKSM), so you can copy them back to the same console after a system transfer. JUST IN CASE, probably won't be necessary.
2 - Remove SD from source/cfw console. Perform system transfer, the target console (new console) will accept only games that you eventually had bought on eShop (it'll download every ticket of legit bought games, this won't check for fake tickets on cfw console so don't worry), all others will be unavailable to use.
3 - After doing system transfer on new console go to data management and remove everything that has a X mark on them, those games won't work on OFW.
4 - On older console reinstall any game that you want, use JKSM or your save manager of choice to restore the backups of your saves to these games.
4 - On CFW console, restore the sysnand/emunand backup (use safe option on godmode9 or hourglass9), it will reinstate the previous user of the console, making the data on original SD usable again, if something doesn't work right away you can reinstall the cias of games (or get them on freeshop) and restore backups from JKSM, but most times it'll work right away.

Don't remove the SD from the CFW console, or else your game saves from bought games will not transfer to the target (hardly a lot of point doing the transfer in that case - except for moving the NNID)

 

[Tomy Sakazaki]

Don't remove the SD from the CFW console, or else your game saves from bought games will not transfer to the target (hardly a lot of point doing the transfer in that case - except for moving the NNID)

Was I wrong to assume that copying the entirety of SD to target console was enough to make the transfer work? Because the major problem with saves and games is the directory names under Nintendo 3DS and those are generated with moveble.sed (unless I was remembering wrong). AFAIK (and I may be wrong about it) the only actual saves that are copied over wifi are those of 3ds internal memory applications (face raiders and mii plaza progress).

 

[Giodude]

I haven't read everything here, but to debunk most of this, if the op is really this afraid, deleting all Homebrew apps would make the console indistinguishable from a vanilla 3ds. A cfw in essence is just several patches applied to the 3ds OS upon booting. Everything about your nnid being tainted has no evidence whatever, and is complete paranoia. The only possible way it could be detected if you have a cfw with nothing else installed is if you sent the console into Nintendo to get it fixed. My advice is to update a9lh to b9s. This will allow you to use any Homebrew app you like injected into DS download play. This completely conceals what you're doing, while opening access to everything you've been doing prior untill now (emulators, hb games etc). The guide to upgrade is here, and I can guarantee without a hint of doubt you will be completely safe from any future banwaves to come. https://3ds.guide/a9lh-to-b9s.html

 

[Quantumcat]

Was I wrong to assume that copying the entirety of SD to target console was enough to make the transfer work? Because the major problem with saves and games is the directory names under Nintendo 3DS and those are generated with moveble.sed (unless I was remembering wrong). AFAIK (and I may be wrong about it) the only actual saves that are copied over wifi are those of 3ds internal memory applications (face raiders and mii plaza progress).

Something I can think of is if you have DSiWare, the SD has to be in the console so it gets moved to SD card and can be moved to the target memory afterward.

 

[CrazyMaxx]

It has works now I will only the Data from emunand and a9lh from my sd on a new sd for my still hacked 3ds