If anyone else is reading this who knows both French and English very well, can you help @samlach22 in private message relaying the more technical parts?
If anyone else is reading this who knows both French and English very well, can you help @samlach22 in private message relaying the more technical parts?
thanks for your help, I tried to follow your guide as best I could, I took the version of luma 9, etc. now when I start my 3ds I no longer have the alert I sent you, but this new alert:
thanks for your help, I tried to follow your guide as best I could, I took the version of luma 9, etc. now when I start my 3ds I no longer have the alert I sent you, but this new alert:
none of these methods work.
I have a backup of an old 3ds, the same kind as the one I have now, a sysnand backup, that would surprise me, but would it be flashable on this 3ds?
none of these methods work.
I have a backup of an old 3ds, the same kind as the one I have now, a sysnand backup, that would surprise me, but would it be flashable on this 3ds?
none of these methods work.
I have a backup of an old 3ds, the same kind as the one I have now, a sysnand backup, that would surprise me, but would it be flashable on this 3ds?
You can't restore the SysNAND *.bin image made from a different o3DS system. Reflashing a foreign NAND image will super softbrick that o3DS.
If standard CTRTransfer does not fix the 3DS firmware, the next best option is CTRTransfer (Type D9). This other one works a little differently and is meant to handle certain nontypical causes of softbricks.
Try the CTRTransfer (Type D9) next. I'll have to warn you that (Type D9) is not as user friendly to do versus standard as it is an advanced method of repairing the 3DS firmware. The instructions will be harder to follow.
You can't restore the SysNAND *.bin image made from a different o3DS system. Reflashing a foreign NAND image will super softbrick that o3DS.
If standard CTRTransfer does not fix the 3DS firmware, the next best option is CTRTransfer (Type D9). This other one works a little differently and is meant to handle certain nontypical causes of softbricks.
Try the CTRTransfer (Type D9) next. I'll have to warn you that (Type D9) is not as user friendly to do versus standard as it is an advanced method of repairing the 3DS firmware. The instructions will be harder to follow.
I tried what you told me to do, it still doesn't work, what would it be good to do?
- flash another CTRANSFERT backup (American or Japanese version)
- Flashing another version of the CTRANSFERT backup (older or more recent)
- other things
It's a 3ds that belonged to a friend, she told me she'd never been cracked. I tried the recovery mode, the system is up to date, and it doesn't change anything.
I don't really understand how to install B9S without ever being able to turn on the 3ds
I tried what you told me to do, it still doesn't work, what would it be good to do?
- flash another CTRANSFERT backup (American or Japanese version)
- Flashing another version of the CTRANSFERT backup (older or more recent)
- other things
In GodMode9, go into [1:] SYSNAND CTRNAND directory.
Hold (R)-shoulder button and press (X) button on the data folder.
Be very careful. Pressing only the (X) button brings up the delete option. Do not delete!
Rename the data folder to data2.
Press (START) button to exit GodMode9.
If successful, your 3DS system will try to make a new user profile.
***
If you want to keep and fix your original user profile,
5. Press (X) to delete the (dummy) data folder. Rename data2 back to data.
6. Hold (R)-shoulder and press (A) on data → Copy to 0:/gm9/out.
This will make a backup of this folder.
7. Go into 1:/data/<ID0>/ directory. You will see two subfolders,
extdata
sysdata
8. Press (X) to delete the extdata.
9. Press (START) to exit GodMode9.
***
(A) If the 3DS system boots to HOME Menu, the bug is coming from extdata.
(B) If the 3DS system does not boot HOME Menu, the bug is coming from sysdata.
***
10. Go to [0:] SD CARD ()/gm9/out. Press (Y) on data subfolder to [CLIPBOARD] select it.
If mistake was made, press (SELECT) to reset the selection.
In GodMode9, go into [1:] SYSNAND CTRNAND directory.
Hold (R)-shoulder button and press (X) button on the data folder.
Rename the data folder to data2.
Press (START) button to exit GodMode9.
If successful, your 3DS system will try to make a new user profile.
***
If you want to keep and fix your original user profile,
5. Press (X) to delete the dummy data folder. Rename data2 back to data.
6. Hold (R)-shoulder and press (A) on data → Copy to 0:/gm9/out.
This will make a backup of this folder.
7. Go into 1:/data/<ID0>/ directory. You will see two subfolders,
extdata
sysdata
8. Press (X) to delete the extdata.
9. Press (START) to exit GodMode9.
***
(A) If the 3DS system boots to HOME Menu, the bug is coming from extdata.
(B) If the 3DS system does not boot HOME Menu, the bug is coming from sysdata.
***
10. Go to [0:] SD CARD ()/gm9/out. Press (Y) on data subfolder to [CLIPBOARD] select it.
If mistake was made, press (SELECT) to reset the selection.
A big thank you, really thank you from the bottom of my heart, I renamed data to data2 and it worked, thank you for your patience and your research for me.
I have one last problem, I still have the sd card of my old 3ds, there must remain the game backups and games in it I suppose, is it possible to put them from the sd card to the 3ds we just fixed, if so, how?
A big thank you, really thank you from the bottom of my heart, I renamed data to data2 and it worked, thank you for your patience and your research for me.
I have one last problem, I still have the sd card of my old 3ds, there must remain the game backups and games in it I suppose, is it possible to put them from the sd card to the 3ds we just fixed, if so, how?
A big thank you, really thank you from the bottom of my heart, I renamed data to data2 and it worked, thank you for your patience and your research for me.
Keep the original folder.
Do you intend to keep and fix your real data folder?
If you mange to find and delete the subfolder that has the bug, I would like to know know which one it was.
Delete the folder.
If you plan to start over and don't want to keep your user profile (NNID, Friend List, Activity Log, etc), just delete the data2 folder.
I have one last problem, I still have the sd card of my old 3ds, there must remain the game backups and games in it I suppose, is it possible to put them from the sd card to the 3ds we just fixed, if so, how?
Keep the original folder.
Do you intend to keep and fix your real data folder?
If you mange to find and delete the subfolder that has the bug, I would like to know know which one it was.
Delete the folder.
If you plan to start over and don't want to keep your user profile (NNID, Friend List, Activity Log, etc), just delete the data2 folder.
Copy back the Nintendo 3DS folder to whichever SD card your o3DS will use.
For games not recognized on HOME Menu,
For missing tickets where titles are marked with grey X's in Data Management, use faketik to restore with fake tickets.
I didn't have to be very clear, the 3ds we just repaired is the pink 3ds, before I had a red 3ds with all my games and backups on the sd card, I'd like to put these games and backups on my pink 3ds, is that possible, keeping the same sd card?
I didn't have to be very clear, the 3ds we just repaired is the pink 3ds, before I had a red 3ds with all my games and backups on the sd card, I'd like to put these games and backups on my pink 3ds, is that possible, keeping the same sd card?
It is possible to recover the games and saves from the red o3DS and its SD card and move it over to using it on the pink o3DS.
Do you have any GBA Virtual Console games?
Do you have any DSiWare games?
User Profile: NNID, Activity Log, Friend List, SpotPass, StreetPass, Mii characters, etc?
Depending what you're trying to backup or import, this type of 3DS data recovery is difficult, time consuming, and requires careful management with NAND cloning.
I'm reluctant to help because of bad past experience with those who recovered their setups but ignored my warnings by taking shortcuts and keeping their unauthorized System Transferred user profile.
It is possible to recover the games and saves from the red o3DS and its SD card and move it over to using it on the pink o3DS.
Do you have any GBA Virtual Console games?
Do you have any DSiWare games?
User Profile: NNID, Activity Log, Friend List, SpotPass, StreetPass, Mii characters, etc?
Depending what you're trying to backup or import, this type of 3DS data recovery is difficult, time consuming, and requires careful management with NAND cloning.
I'm reluctant to help because of bad past experience with those who recovered their setups but ignored my warnings by taking shortcuts and keeping their unauthorized System Transferred user profile.
I would like to recover my games from the sd card with their backups, only the 3ds games, to be able to reinstall the same games as on the red 3ds on the pink 3ds and keep the backups I had on the red 3ds
I would like to recover my games from the sd card with their backups, only the 3ds games, to be able to reinstall the same games as on the red 3ds on the pink 3ds and keep the backups I had on the red 3ds
2A. Mount the SysNAND *.bin image and allow for the program to finish loading the various files. Go on a coffee or snack break and come back later.
Older made NAND images will not mount if the embedded essential.exefs is missing. You would be required to supply the red o3DS previously dumped otp.bin.
3A. In the essential subfolder, copy the movable.bin file over to the ninfs parent folder. Rename that file as movable (red).bin.
-or-
1B. Download the HxD hex editor, and open the SysNAND *.bin image.
2B. Go to offset 0x800. Look for the SEED header under the right column, Decoded text.
Older made NAND images will not have the embedded essential.exefs. That means the movable.sed cannot be directly extracted by hex editor.
3B. Copy the 0x140 sized block. Save that as a new file named movable (red).bin.
-or-
1C. Download and install the program, OSFMount.
2C. Found within the SysNAND *. bin image (see steps 1A–2A), extract and mount the ctrnand_fat.img .
(1) OSFMount → File → Mount new virtual disk...
(2) Select the ctrnand_fat.img. Mount as ☑ Read-only drive.
3C. Go in the private directory. Copy the movable.sed to the ninfs parent folder. Rename that file as movable (red).bin.
-or-
Part ID - Extract the movable.sed from the red o3DS CTRNAND.
1D. Add the GodMode9 .FIRM payload onto the red o3DS SD card. Insert the SD card into the red o3DS. Press (POWER) to turn on the system → hold (START) button → Luma3DS chainloader.
sdmc:/luma/payloads/GodMode9 v1.9.1.firm
2D. GodMode9 → [1:] SYSNAND CTRNAND/private/movable.sed → press (A) → Copy to 0:/gm9/out. Press (POWER) to turn off the system.
3D. On a computer looking in the sdmc:/gm9/out directory, copy the movable.sed to the parent ninfs folder. Rename that file as movable (red).bin.
Part II - Calculate and compare the movable.sedKeyY to the 32-char <ID0> subfolder.
4. In HxD hex editor, highlight the 0x110-11F block and generate its SHA-256 hash.
{ See the spoiler in step 2B. } ... → Analysis → Checksums... → SHA-256 → OK
Do not publicly upload or share yourmovable.sed. That file contains yourLocalFriendCodeSeed_B. Once this is shown, others will hijack and abuse it: you will be banned from online play.
5. Copy and paste the SHA-256 hash in the convert_0x30_KeyY_to_ID0.xlsx using Microsoft Office Excel or LibreOffice Calc. The spreadsheet will calculate the <ID0> for a given KeyY.
6. Compare the calculated <ID0> to the one found in the red o3DSNintendo 3DS folder.
If the calculated and actual <ID0> matches, jump to step 11 in Part III.
If the <ID0> do not match, continue instead on step 7.
Do not rename the actual<ID0>subfolder to match that of the calculated<ID0>. This doesn't fix the encryption.
***
7. Take the first half of the KeyY and paste this into the provided (blank) movable_part1.sed.
8. Upload the movable_part1.sed and input the actual subfolder's <ID0> at:
9. If a match is found, download the (dummy) movable.sed. Rename and replace it as the movable (red).bin. Jump to step 11 in Part III.
***
Step 10. Last chance.
If a match was not found in steps 8-9, this is most likely due to your user profile coming from a System Transfer.
You must find and contact someone who previously added you to their Friend List.
That person has to have a 3DS system that is hacked with custom firmware.
He or she would need to dump your first half of the KeyY using seedstarter.
smdc:/seedstarter/LFCS/#_####-####-####_part1.sed
####-####-####= (your) Friend Code
If the #_####-####-####_part1.sed is obtained, go to step 8.
If you do not have 3DS friends to rely on,you are shit out of luck.
*************************************************************************
************************************************************************* WARNING: About unauthorized System Transfer.
Do not replace/inject thered o3DSmovable.sedto thepink o3DS[1:] SYSNAND CTRNAND.
This can brick its 3DS firmware, permanently erase its own console unique copy of that file, and risk online service bans.
To learn more about why this is not recommended, please read:
Older made NAND images will not mount if the embedded essential.exefs is missing. You would be required to supply the red o3DS previously dumped otp.bin.
3A. In the essential subfolder, copy the movable.bin file over to the ninfs parent folder. Rename that file as movable (red).bin.
-or-
1B. Download the HxD hex editor and open the SysNAND *.bin image.
2B. Go to offset 0x800. Look for the SEED header under the right column, Decoded text.
Do not publicly upload or share yourmovable.sed. That file contains yourLocalFriendCodeSeed_B. Once this is shown, others will hijack and abuse it: you will be banned from online play.
5. Copy and paste the SHA-256 hash in the convert_0x30_KeyY_to_ID0.xlsx using Microsoft Office Excel or LibreOffice Calc. The spreadsheat will calculate the <ID0> for a given KeyY.
6. Compare the calculated <ID0> to the one found in the red o3DSNintendo 3DS folder.
If the calculated and actual <ID0> matches, jump to step 11 in Part III.
If the <ID0> do not a match, continue with step 7.
Do not rename the actual<ID0>subfolder to match that of the calculated<ID0>. This doesn't fix the encryption.
***
7. Take the first half of the KeyY and paste this into the provided (blank) movable_part1.sed.
8. Upload the movable_part1.sed and input the actual subfolder's <ID0> at:
If a match was not found in steps 8-9, this is most likely due to your user profile coming from a System Transfer.
You must find and contact someone who previously added you to their Friend List.
That person has to have a 3DS system that is hacked with custom firmware.
He or she would need to dump your first half of the KeyY using seedstarter.
smdc:/seedstarter/LFCS/#_####-####-####_part1.sed
####-####-####= (your) Friend Code
If the #_####-####-####_part1.sed is obtained, go to step 8.
If you do not have 3DS friends to rely on,you are shit out of luck.
*************************************************************************
************************************************************************* WARNING: About unauthorized System Transfer.
Do not replace/inject thered o3DSmovable.sedto thepink o3DS[1:] SYSNAND CTRNAND.
This can brick its 3DS firmware, permanently erase its own console unique copy of that file, and risk online service bans.
To learn more about why this is not recommended, please read:
I would like to help people recover their user profiles & NAND setups from their dead 2DS/3DS systems, but this is a soft modding subject I'm most afraid to talk about because..
(1) If done incorrectly where directions are not followed exactly or precautionary steps were skipped, one can permanently erase console unique files or even super softbrick the NAND with bootrom 8046 blue screens of death.
Some people are stubborn where they will deviant from the instructions by deciding to flash foreign NAND files that can't be used.
Even with a ntrboot flashcart to launch GodMode9, there are specific scenarios where your backed up SysNAND *.bin image might not save you. (ie, the nand_minsize.bin, trimmed version that's dumped and renamed as <yymmdd>_<serial>_sysnand_###.bin).
(2) Those who don't heed the warning about temporarily using their broken system image on their replacement system can end up getting banned.
Some people are complacent about importing their previous setup without doing the latter roundabout backup & restore parts where their stuff has to go on the replacement system's real setup.
(3) Other factors to account like wanting to clone the NAND between two systems from different regions or even different series/models: [ o3DS / o3DSXL / o2DS] ⇄ [ n3DS / n3DSXL / n2DSXL ].
What these all add up to is a tutorial that has to be sufficiently detailed enough step-by-step while covering all the pitfalls to watch out for. On top of that, it needs to be easy to follow and understand for even the most basic technically inclined 3DS homebrewer. With lots of color coded words and pictures.
Writing something like this would suck. Also, I rather not give anyone crappy / watered down instructions. This is so they don't come back and blame me for bricking their system or getting banned by Nintendo.
I would like to help people recover their user profiles & NAND setups from their dead 2DS/3DS systems, but this is a soft modding subject I'm most afraid to talk about because..
(1) If done incorrectly where directions are not followed exactly or precautionary steps were skipped, one can permanently erase console unique files or even super softbrick the NAND with bootrom 8046 blue screens of death.
Some people are stubborn where they will deviant from the instructions by deciding to flash foreign NAND files that can't be used.
Even with a ntrboot flashcart to launch GodMode9, there are specific scenarios where your backed up SysNAND *.bin image might not save you. (ie, the nand_minsize.bin, trimmed version that's dumped and renamed as <yymmdd>_<serial>_sysnand_###.bin).
(2) Those who don't heed the warning about temporarily using their broken system image on their replacement system can end up getting banned.
Some people are complacent about importing their previous setup without doing the latter roundabout backup & restore parts where their stuff has to go on the replacement system's real setup.
(3) Other factors to account like wanting to clone the NAND between two systems from different regions or even different series/models: [ o3DS / o3DSXL / o2DS] ⇄ [ n3DS / n3DSXL / n2DSXL ].
What these all add up to is a tutorial that has to be sufficiently detailed enough step-by-step while covering all the pitfalls to watch out for. On top of that, it needs to be easy to follow and understand for even the most basic technically inclined 3DS homebrewer. With lots of color coded words and pictures.
Writing something like this would suck. Also, I rather not give anyone crappy / watered down instructions. This is so they don't come back and blame me for bricking their system or getting banned by Nintendo.
I totally understand, my mii being quite basic, it doesn't matter if I don't get it back, but the list of friends (friend codes) I'd like to get them back, there are people I know that I can't contact anymore to have their friend codes, is it possible to just get the friend codes from the o3ds red
I totally understand, my mii being quite basic, it doesn't matter if I don't get it back, but the list of friends (friend codes) I'd like to get them back, there are people I know that I can't contact anymore to have their friend codes, is it possible to just get the friend codes from the o3ds red
The red o3DS Friend List is possible to get back or at least read off of. You might need to manually sent out requests to add your friends on the replacement pink o3DS.
I would like you study those two (very bad tutorials) so you're comfortable with what will need to be done later.
Don't actually follow those as they're a bit outdated. While they work, they're not geared towards backing up user profile settings saves.
The 3rd revision of this series will be much easier to follow than what you see in those two. When I'm finished with it, I will let you know by PM.
You may not hear back until later this week. It takes time to get over writer's block and triple check going over making sure information is correct.
Thank you so much. I had the "gamecoin"-type brick on my o2ds. Using your instructions, I found the extdata was the issue. It was folder f000000b. You asked about this from OP and didn't get a response, so here you go.
Sonic Unleashed was one of the few Sonic titles to never make its way to PC in any form. A 2013 fan project called Unleashed Project attempted to bring the levels of...
Nintendo's legal action against emulators continues yet again, as new DMCA takedown notices have been handed to several Ryujinx forks on Github.
Back in October...
Nintendo's own Public Relations (PR) department has issued today an email to several outlets and partners regarding a ruling from the French Supreme Court against the...
Almost exactly a year ago, Balatro stormed onto the scene as a surprise standout of 2024. The game features an utterly addictive gameplay loop that takes the familiar...
After being lost through several decades since their release at the hands of EA, and after a Remastered Collection with incomplete code from the final builds, today...
The constant changes, be it for bad or good, in the videogame industry continues, as this time, several studios under Warner Bros. will shut down, as well as Warner...
Back in October of last year, scene enthusiast "Grimdoomer" discovered a potential hypervisor exploit for the Xbox 360. Existing mostly as a proof-of-concept softmod...
It's the 29th anniversary of the release of the first Pokemon titles, and to celebrate, The Pokemon Company has a handful of announcements and reveals to make. A...
SEGA's official Sonic portal website, Sonic Channel, is celebrating its 20th anniversary on March 20th, 2025, and to celebrate the occasion, the website has added...
2025 is off and running, and with the first two months out of the way, the AAA release cycle is beginning to ramp up, with a handful of notable titles releasing this...
Nintendo's legal action against emulators continues yet again, as new DMCA takedown notices have been handed to several Ryujinx forks on Github.
Back in October...
Sonic Unleashed was one of the few Sonic titles to never make its way to PC in any form. A 2013 fan project called Unleashed Project attempted to bring the levels of...
Assassin's Creed Shadows faced a few bumps on its way to launch, ranging from a multitude of delays, to controversy over one of the game's characters, Yasuke, as well...
Nintendo's own Public Relations (PR) department has issued today an email to several outlets and partners regarding a ruling from the French Supreme Court against the...
The constant changes, be it for bad or good, in the videogame industry continues, as this time, several studios under Warner Bros. will shut down, as well as Warner...
It's the 29th anniversary of the release of the first Pokemon titles, and to celebrate, The Pokemon Company has a handful of announcements and reveals to make. A...
SEGA's official Sonic portal website, Sonic Channel, is celebrating its 20th anniversary on March 20th, 2025, and to celebrate the occasion, the website has added...
Yesterday's Silent Hill Transmission stream focused entirely on the newly revealed entry to the franchise, "Silent Hill f". The new reveal trailer is entirely in...
After being lost through several decades since their release at the hands of EA, and after a Remastered Collection with incomplete code from the final builds, today...
Niantic, the company behind the mobile app that took the mobile gaming by storm back in 2016, Pokemon GO, has reached an agreement with another giant in the mobile...
Spread peanut butter on one side of each bread slice
Top with banana slices
Add bacon
Drizzle with honey or jelly
Close the sandwich, peanut butter side down
Cook in a skillet or on a griddle until golden brown and crusty
Cut in half diagonally and serve
Be very careful. Pressing only the (X) button brings up the delete option. Do not delete!
