CTRTransfer (Type D9) does not delete user data like Activity Log, NNID, Friend Code, Friend List, etc. User data found in,
[1:] SYSNAND CTRNAND/data
, are all left alone. The only exception is that the anti-cheat savegame restore (secure value) is automatically deleted to prevent games that have that tamper measure from erasing your saves.
If the setup is missing something after repairing the 3DS + CFW firmwares, that would be on the user or owner having deleted those prior to the softbrick.
CTRTransfer (Type D9) does not delete user data like Activity Log, NNID, Friend Code, Friend List, etc. User data found in,
[1:] SYSNAND CTRNAND/data
, are all left alone. The only exception is that the anti-cheat savegame restore (secure value) is automatically deleted to prevent games that have that tamper measure from erasing your saves.
If the setup is missing something after repairing the 3DS + CFW firmwares, that would be on the user or owner having deleted those prior to the softbrick.
Alright, so should I do the quick one or the long one? Also, will I need a big sd card for it? Because I'm using all my other sd cards in other consoles, and I just have a 4gb one. But the one I used before my N3DSXL bricked was 128gb, so will I need another 128gb one for it? I had filled up most of the 128gb sd card with games, emulators and stuff, so will I need to use a 128gb card to unbrick it?
Alright, so should I do the quick one or the long one? Also, will I need a big sd card for it? Because I'm using all my other sd cards in other consoles, and I just have a 4gb one. But the one I used before my N3DSXL bricked was 128gb, so will I need another 128gb one for it? I had filled up most of the 128gb sd card with games, emulators and stuff, so will I need to use a 128gb card to unbrick it?
Follow the Instructions for the CTRTransfer (Type D9) using the smaller 4 GB microSD card. After completing all steps 6–16 (skipping steps 1–5 if you're using that CFW starter kit and had already reformatted + H2testw checked that 4 GB card, step 17 depends on the severity of the softbrick), switch over to using your main 128 GB microSD card to finish the Finalizing Setup.
Edit 1 - Do not skip steps 1–5 if that 4 GB card has not been hardware tested before. It is super crucial the SD card is 100% fully functional or reliable, or else really bad things will happen to the n3DSXL using the CTRTransfer (Type D9).
Edit 2 - For quadruple reformat, do 'Quick Reformat' for all four (4) programs.
Follow the Instructions for the CTRTransfer (Type D9) using the smaller 4 GB microSD card. After completing all steps 6–16 (skipping steps 1–5 if you're using that CFW starter kit and had already reformatted + H2testw checked that 4 GB card, step 17 depends on the severity of the softbrick), switch over to using your main 128 GB microSD card to finish the Finalizing Setup.
Edit 1 - Do not skip steps 1–5 if that 4 GB card has not been hardware tested before. It is super crucial the SD card is 100% fully functional or reliable, or else really bad things will happen to the n3DSXL using the CTRTransfer (Type D9).
Edit 2 - For quadruple reformat, do 'Quick Reformat' for all four (4) programs.
Reinstalling games, updates, and dlcs in the Nintendo 3DS folder will not be necessary as long as the encryption still matches between the movable.sedKeyY ⇄ sdmc:/Nintendo 3DS/<ID0>.
Also, reinstalling a game CIA (00040000XXXXXXXX) should be avoided if possible. Directly reinstalling a game CIA will permanently overwrite and delete that game's savedata (00000001.sav).
If the KeyY ⇄ <ID0> encryption no longer matches, this can be fixed with that script's other feature, CTRTransfer (Type D9) - Fix movable.sed KeyY.
Edit - After following all the steps in the CTRTransfer (Type D9)'s Instructions, switch back to the main 128 GB microSD card. You may need to do additional troubleshooting if all or some of the games are not showing up on HOME Menu. Here are other,
Reinstalling games, updates, and dlcs in the Nintendo 3DS folder will not be necessary as long as the encryption still matches between the movable.sedKeyY ⇄ sdmc:/Nintendo 3DS/<ID0>.
Also, reinstalling a game CIA (00040000XXXXXXXX) should be avoided if possible. Directly reinstalling a game CIA will permanently overwrite and delete that game's savedata (00000001.sav).
If the KeyY ⇄ <ID0> encryption no longer matches, this can be fixed with that script's other feature, CTRTransfer (Type D9) - Fix movable.sed KeyY.
Edit - After following all the steps in the CTRTransfer (Type D9)'s Instructions, switch back to the main 128 GB microSD card. You may need to do additional troubleshooting if all or some of the games are not showing up on HOME Menu. Here are other,
It'll be like going on a 3 months long vacation traveling all over the world only to come back to home just like how you left everything sitting the way they are.
Whether you tidy up or left the house a mess before leaving is what awaits you.
Fix that n3DSXL's softbrick first before worrying about the collection of titles & savedata. If you're worried about unwanted changes caused by CTRTransfer (Type D9) - CTRTransfer, you can revert the reflash using the backed up SysNAND *.bin image that is instructed to be created at step 8. It'll just return that n3DSXL back to its current state of softbrick like as if nothing happened.
It'll be like going on a 3 months long vacation traveling all over the world only to come back to home just like how you left everything sitting the way they are.
Whether you tidy up or left the house a mess before leaving is what awaits you.
Fix that n3DSXL's softbrick first before worrying about the collection of titles & savedata. If you're worried about unwanted changes caused by CTRTransfer (Type D9) - CTRTransfer, you can revert the reflash using the backed up SysNAND *.bin image that is instructed to be created at step 8. It'll just return that n3DSXL back to its current state of softbrick like as if nothing happened.
Okay, something is not getting across in this conversation.
Does your main 128 GB microSD card contains your original setup of all files, HOME Menu games, updates, DLCs, saves, and extdata when the n3DSXL was last working?
What part are you worried about using the spare 4 GB microSD card to fix the n3DSXL's 3DS + CFW firmware(s) by performing CTRTransfer (Type D9) as described in the Instructions?
Are you afraid or unsure that after CTRTransfer is done, all of your titles will be missing when you switch/swap back to the 128 GB card?
Okay, something is not getting across in this conversation.
Does your main 128 GB microSD card contains your original setup of all files, HOME Menu games, updates, DLCs, saves, and extdata when the n3DSXL was last working?
What part are you worried about using the spare 4 GB microSD card to fix the n3DSXL's 3DS + CFW firmware(s) by performing CTRTransfer (Type D9) as described in the Instructions?
Are you afraid or unsure that after CTRTransfer is done, all of your titles will be missing when you switch/swap back to the 128 GB card?
Yes, it has everything, and I'm a little bit confused on whether or not it would work that way.
(Edit) Also where do I get the CTRtransfer files to put in sd/gm9/in
At the beginning of the Instructions, there's a header with some points on how to read or interpret the steps. One of these is underlined where they're the download links to the files of interest.
At the beginning of the Instructions, there's a header with some points on how to read or interpret the steps. One of these is underlined where they're the download links to the files of interest.
The first time setting up Luma3DS v10.1.3 configuration will automatically boot to that screen whether or not you press and hold (SELECT), (START), or nothing. Luma3DS wants you to specify or select what settings to use. Have the settings like this, press (START) to save the settings, and press + hold (START) again to boot Luma3DS chainloader → GodMode9.
I will not be available to answer any further questions until later tonight (EST time). Going on errand soon.
The first time setting up Luma3DS v10.1.3 configuration will automatically boot to that screen whether or not you press and hold (SELECT), (START), or nothing. Luma3DS wants you to specify or select what settings to use. Have the settings like this, press (START) to save the settings, and press + hold (START) again to boot Luma3DS chainloader → GodMode9.
I will not be available to answer any further questions until later tonight (EST time). Going on errand soon.
Alright, now I'm getting the "The payload is invalid or corrupted" error again, but sometimes it's letting me on gm9. It's also still having the issue of the power led only coming on very briefly unless I hold the 3ds a certain way, and it froze when I tried to use the CTRTransfer script
Alright, now I'm getting the "The payload is invalid or corrupted" error again, but sometimes it's letting me on gm9. It's also still having the issue of the power led only coming on very briefly unless I hold the 3ds a certain way, and it froze when I tried to use the CTRTransfer script
[Update] I got it to do the CTRTransfer thing, but it froze up and says "Reinitializing SD card...SDg"
(Update 2) It's back to saying "The payload is invalid or corrupted" and I'm not sure why it's so inconsistent, I'll copy all the files off and do the quadruple reformat again
[Update] I got it to do the CTRTransfer thing, but it froze up and says "Reinitializing SD card...SDg"
(Update 2) It's back to saying "The payload is invalid or corrupted" and I'm not sure why it's so inconsistent, I'll copy all the files off and do the quadruple reformat again
Alright, now I'm getting the "The payload is invalid or corrupted" error again, but sometimes it's letting me on gm9. It's also still having the issue of the power led only coming on very briefly unless I hold the 3ds a certain way, and it froze when I tried to use the CTRTransfer script
[Update] I got it to do the CTRTransfer thing, but it froze up and says "Reinitializing SD card...SDg"
(Update 2) It's back to saying "The payload is invalid or corrupted" and I'm not sure why it's so inconsistent, I'll copy all the files off and do the quadruple reformat again
One of these three (3) possible scenarios could be causing this hang-up.
(1) That 4 GB microSD card is a relabelled fake (ie, real capacity is 256 MB pandering as a 4 GB), or the card is dead/dying. The card has met its end of useful life.
When checking the card in H2testw, look out for [BAD].
(2) The SD card comes back as [GOOD] but has a secondary mode of hardware failure with a failing controller. This failure mode is harder to pin point. This is basically like the above (1) but not as obvious.
I don't like advising people to buy something if the item is not necessary or tremendously helpful.
However, this is one of these few times where I believe there's no other way. @DumpingDonuts, if this suggestion is within your means and not too much trouble, can you purchase a brand new microSD card from Walmart, Target, or Best Buy? This 16 GB onn. brand is the cheapest that should be widely available to buy in-store for about US $6.
Of course, money might be better spent on buying even bigger card or from a different (longer established reputable) brand. For comparison, $15-20 can usual net you a 128 GB micro SD card from Amazon or B&H Photo Video.
Because it's very difficult to determine if an SD card is bad due to possibility (2), I rather not have you risk fixing/replacing that n3DSXL's microSD card slot reader [possibility (3)] unless we know for certain that part is broken by using a known to be good card.
Also, it doesn't help public shopping these days carries a health risk... If you do decide to go out and buy a new card, please stay safe with social distancing and wearing face mask.
***
Edit - We can't advance with repairing the softbrick until the (A) microSD card or (B) microSD card slot reader issue is sorted out.
One of these three (3) possible scenarios could be causing this hang-up.
(1) That 4 GB microSD card is a relabelled fake (ie, real capacity is 256 MB pandering as a 4 GB), or the card is dead/dying. The card has met its end of useful life.
When checking the card in H2testw, look out for [BAD].
(2) The SD card comes back as [GOOD] but has a secondary mode of hardware failure with a failing controller. This failure mode is harder to pin point. This is basically like the above (1) but not as obvious.
I don't like advising people to buy something if the item is not necessary or tremendously helpful.
However, this is one of these few times where I believe there's no other way. @DumpingDonuts, if this suggestion is within your means and not too much trouble, can you purchase a brand new microSD card from Walmart, Target, or Best Buy? This 16 GB onn. brand is the cheapest that should be widely available to buy in-store for about US $6.
Of course, money might be better spent on buying even bigger card or from a different (longer established reputable) brand. For comparison, $15-20 can usual net you a 128 GB micro SD card from Amazon or B&H Photo Video.
Because it's very difficult to determine if an SD card is bad due to possibility (2), I rather not have you risk fixing/replacing that n3DSXL's microSD card slot reader [possibility (3)] unless we know for certain that part is broken by using a known to be good card.
Also, it doesn't help public shopping these days carries a health risk... If you do decide to go out and buy a new card, please stay safe with social distancing and wearing face mask.
***
Edit - We can't advance with repairing the softbrick until the (A) microSD card or (B) microSD card slot reader issue is sorted out.
I tried another ss card, same issues. I think it might just be an issue with the microsd reader itself, but i might try my 128gb card i bought yesterday.
Once again I fell down the martial arts rabbit hole and am plumbing the murky depths of the internet's various martial arts and fighting crafts echo chambers.
If you're not actively involved and only get up to speed every few years or so, you can see the tide of public opinion flapping worse than my dong while I'm skipping naked down a hallway.