ROM Hack Need help, is it possible to transfer my old game file on my 128gb sd card to my new nintendo 3ds xl

[TurdPooCharger]

okay i'll try it later, umm i have another question regarding installing cfw. last week, when i'm trying to removing my cfw and install it again using the Seedminer + unSAFE_MODE method, when it supposedly after open DSiware from data management, the 3ds bottom screen supposedly should flash Red but instead i got an error has occured and the bottom screen doesnt flash red, even though i recall doing the steps carefully from the 3dshacksguide site , and when typing the DSiWare folder, ithink i done it correctly, but the problem still persist, so i change to pichaxx method instead. my question is my dsi ware corrupt
sorry for my bad english and take so much of your time

I'm not familiar with the seedminer's unSAFE MODE method. It's stated in the guide revisiting the System Settings → Data Management → DSiWare → (micro)SD Card restores the WiFi profile settings, and that the sdmc:/Nintendo 3DS/<ID0>/<ID1>/Nintendo DSiWare/F00D43D5.bin needs to be deleted afterwards.

• Section V - Restoring WiFi Configuration Profiles

To find out if the DS(i) mode is softbricked, install and launch a homebrew DSiWare title: 3DSBank, GodMode9i, GameYob (DSiWare version).

Make sure the 3DS firmware is running under SysNAND where:

• Turn on n3DSXL → hold (SELECT) button → Luma3DS v10.1.3 configuration has (x) Show NAND or user string in System Settings
• System Settings shows the 3DS firmware is Sys 11.13.0-45[J/U/E/C/K/T].

If the n3DSXL boots to white screen launching one of the above DSiware, fix the DS(i) mode by doing this.

• DSi / DS functionality is broken after completing the guide

 

[giovannirizqy]

HOME Menu titles with the <TID_HIGH> of 00040002 are very few select demos.

• [3dbrew.org] EShop QR

These demos are not that common. Rebuild 3DS Database was not written to handle backing up these into CIAs & saves.

***

The (2b) Restore Saves won't continue if the CIAs backed up from (1b) Backup CIAs & Saves aren't reinstalled with FBI. Can't add back the saves when there are no games to put them back to.

If you've tried all of these,

• Reformatted and hardware tested the SD card. [ Quadruple reformat + H2testw ]
• Imported the seed + setup Locale emulation [ FBI → import seed | (x) Enabled Game Patching + LumaLocaleSwitcher ]
  
• Rebuilt the Nintendo 3DS folder. [ CTRTransfer (Type D9) - Rebuild 3DS Database: Option (B) Full ]
  
• Repaired the 3DS + CFW firmwares. [ CTRTransfer (Type D9) - CTRTransfer ]

, and the ARM11 errors are still not resolved, see if the battery trick clearing the RAM memory helps any.

Lastly, if battery trick also fails, your n3DSXL is likely to have a hardware fault for the motherboard. In this other thread, another user was able to diagnosis an underlying faulty NAND chip (eMMC) on his n3DS that was causing his 3DS mode to work incorrectly. Maybe your n3DSXL is experiencing a similiar failure.

• Am exeption occurred for N3DS CFW [post #9]
  • Follow the conversation between fatsocat and I.

Hi @TurdPooCharger i have a bad news, after i tried all of the method you gave me yesterday, unfortunately the error still persist, the battery trick doesnt solve it, and during the crt transter method my 3ds seems like pass the eMMC verification, so i dont exacly know the problem why the arms 11 data abort and the freeze when playing some games still persist and the white screen photo is when i play mario tenis, when i press start in the intro the freeze problem occurs

 

[TurdPooCharger]

Hi @TurdPooCharger i have a bad news, after i tried all of the method you gave me yesterday, unfortunately the error still persist, the battery trick doesnt solve it, and during the crt transter method my 3ds seems like pass the eMMC verification, so i dont exacly know the problem why the arms 11 data abort and the freeze when playing some games still persist and the white screen photo is when i play mario tenis, when i press start in the intro the freeze problem occurs

F*%&.

Do you still have the other n3DSXL that you purchased to replace this one? If you do, try this.

1. In GodMode9, backup into CIAs only those five (5) games that are giving you trouble.
   • Dumping a Title
   • Note: Step 1 can skipped if you still have copies of those CIAs dumped earlier from Rebuild 3DS Database.
2. Backup the saves + extdata for those games in Checkpoint or JKSM.
3. Turn off the n3DSXL, and remove the SD card. On computer, rename the Nintendo 3DS folder to something else like Nintendo 3DS (main).
4. Safely eject the SD card. Insert the card to the second n3DSXL.
5. (Conditional) Install custom firmware to this system as per 3ds.hacks.guide if it hasn't already been hacked yet.
6. Install those game CIAs with FBI. Restore the saves + extdata with save manager of choice. This will create a separate Nintendo 3DS folder.
   
7. Play those games to check if the ARM11 errors are repeatable on this second n3DSXL.

Outcome (A) If this n3DSXL also crashes with ARM11 errors, that means your first n3DSXL is probably okay hardware-wise BUT something is wrong with your games' savedata. These might have been corrupted somehow. Were they modified with save editors by any chance?

• Basically, your gameplay progress will need to be scrapped; start all over again for just those games.

Outcome (B) If the n3DSXL is able to play those games just fine, your first n3DSXL is a lemon. Chalk this up to faulty RAM that can't keep up and tends to crash on games that use extended memory. There's no real way to fixing this except to replace the motherboard or [ get another 3DS system / migrate to the second n3DSXL ].

• [iFixit] Nintendo 3DS XL 2015 Motherboard Replacement
• [aliexpress] Original USA Version Motherboard for New 3DS XL LL Replacement Mainboard PCB Board for New 3DSXL 3DSLL

If this is Outcome (B), revisit post #5 in how to System Transfer or SDTransfer the Nintendo 3DS folder to the new n3DSXL or replacement motherboard.

 

[giovannirizqy]

F*%&.

Do you still have the other n3DSXL that you purchased to replace this one? If you do, try this.

1. In GodMode9, backup into CIAs only those five (5) games that are giving you trouble.
   • Dumping a Title
   • Note: Step 1 can skipped if you still have copies of those CIAs dumped earlier from Rebuild 3DS Database.
2. Backup the saves + extdata for those games in Checkpoint or JKSM.
3. Turn off the n3DSXL, and remove the SD card. On computer, rename the Nintendo 3DS folder to something else like Nintendo 3DS (main).
4. Safely eject the SD card. Insert the card to the second n3DSXL.
5. (Conditional) Install custom firmware to this system as per 3ds.hacks.guide if it hasn't already been hacked yet.
6. Install those game CIAs with FBI. Restore the saves + extdata with save manager of choice. This will create a separate Nintendo 3DS folder.
   
7. Play those games to check if the ARM11 errors are repeatable on this second n3DSXL.

Outcome (A) If this n3DSXL also crashes with ARM11 errors, that means your first n3DSXL is probably okay hardware-wise BUT something is wrong with your games' savedata. These might have been corrupted somehow. Were they modified with save editors by any chance?

• Basically, your gameplay progress will need to be scrapped; start all over again for just those games.

Outcome (B) If the n3DSXL is able to play those games just fine, your first n3DSXL is a lemon. Chalk this up to faulty RAM that can't keep up and tends to crash on games that use extended memory. There's no real way to fixing this except to replace the motherboard or [ get another 3DS system / migrate to the second n3DSXL ].

• [iFixit] Nintendo 3DS XL 2015 Motherboard Replacement
• [aliexpress] Original USA Version Motherboard for New 3DS XL LL Replacement Mainboard PCB Board for New 3DSXL 3DSLL

If this is Outcome (B), revisit post #5 in how to System Transfer or SDTransfer the Nintendo 3DS folder to the new n3DSXL or replacement motherboard.

unfortunately i already sell it to the guy who previously bought my previous new 3ds xl (again) cuz i haven't homebrew (cfw) it. i think i should give up when i got the arms 11 problem, my solution is play the game that has this problem in citra, but another problem is my pc is a potato so it barely can run any 3ds game ^^ (lmao), thank you so much for all the help you gave me @TurdPooCharger really appreciate it, have a nice day and bless you bro

 

[TurdPooCharger]

unfortunately i already sell it to the guy who previously bought my previous new 3ds xl (again) cuz i haven't homebrew (cfw) it. i think i should give up when i got the arms 11 problem, my solution is play the game that has this problem in citra, but another problem is my pc is a potato so it barely can run any 3ds game ^^ (lmao), thank you so much for all the help you gave me @TurdPooCharger really appreciate it, have a nice day and bless you bro

If you wish, I can check the saves + extdata on my n3DSXL. Just back them up with Checkpoint/JKSM, put them in a zip archive, and upload them here.

* Edit - Check the saves + extdata by playing those same games on my n3DSXL.

 

[giovannirizqy]

If you wish, I can check the saves + extdata on my n3DSXL. Just back them up with Checkpoint/JKSM, put them in a zip archive, and upload them here.

* Edit - Check the saves + extdata by playing those same games on my n3DSXL.

here's my save and exdata the problem occurs in pokemon moon when you had to press R button to the damaged wall to use the poke finder to work

* EDIT and this is my save data and exdata when playing Monster hunter 3 Ultimate. the problem occur after completing 1 or 2 quest, i got the usual arms 11 data abort translation section error

 

[TurdPooCharger]

here's my save and exdata the problem occurs in pokemon moon when you had to press R button to the damaged wall to use the poke finder to work

* EDIT and this is my save data and exdata when playing Monster hunter 3 Ultimate. the problem occur after completing 1 or 2 quest, i got the usual arms 11 data abort translation section error

For Pokemon Moon, I installed both a converted .3DS → .CIA rom and the update v1.2. No locale emulation for this game on my USA n3DSXL. The Poke Finder was able to capture pictures of the Pikachu over the broken wall.

Monster Hunter 3 Ultimate, also installed a .3DS → .CIA rom. Not experienced with the mechanics of this series. Completed the first three level 1 quests on your main profile in one go and also tried to kill Lagiacrus. F' that monstie's stun attack and confusion knock.

No crashes encountered on my end. The saves are fine. That concludes assessing your n3DSXL as definitely having a bad motherboard.

 

[giovannirizqy]

For Pokemon Moon, I installed both a converted .3DS → .CIA rom and the update v1.2. No locale emulation for this game on my USA n3DSXL. The Poke Finder was able to capture pictures of the Pikachu over the broken wall.

Monster Hunter 3 Ultimate, also installed a .3DS → .CIA rom. Not experienced with the mechanics of this series. Completed the first three level 1 quests on your main profile in one go and also tried to kill Lagiacrus. F' that monstie's stun attack and confusion knock.

No crashes encountered on my end. The saves are fine. That concludes assessing your n3DSXL as definitely having a bad motherboard.

View attachment 214993

yep its really my motherboard problem , lmao F' that lagiacrus XD, u sopposedly leave him alone tho cuz my current rank isn't that high or switching my armor set based on his weakness , umm should i try to switching to emunand setup method? , can i use the 128 gb micro sd, if i switch to emunand ?, and can i keep my game and save if i switch to emunand?

 

[TurdPooCharger]

yep its really my motherboard problem , lmao F' that lagiacrus XD, u sopposedly leave him alone tho cuz my current rank isn't that high or switching my armor set based on his weakness , umm should i try to switching to emunand setup method? , can i use the 128 gb micro sd, if i switch to emunand ?, and can i keep my game and save if i switch to emunand?

In one of my responses to fatsocat in that other thread, there was another post explaining why having EmuNAND is not a good idea especially on SD cards with larger capacities.

• Will Rednand/Emunand expand the lifespan of the 2ds/3ds? [post #3]

The reason he needed to switch over to EmuNAND was because the eMMC Status Checker revealed the eMMC (NAND chip) on his New 3DS could no longer reliably be read from and written to. To see what the eMMC looks like on the New 3DS XL, look for the Samsung component boxed in yellow at step 13.

• [iFixit] Nintendo 3DS XL 2015

That chip is what holds the custom firmware and 3DS firmware. It's the analogy equivalent to a computer hard drive containing the [ Windows / Mac / Linux ] operating system. In the case of fatsocat, he could get away with substituting the microSD card to act as a secondary or backup NAND.

Unfortunately, because your n3DSXL passed its scan run in eMMC Status Checker, that means a different part on the motherboard has failed. The likely culprit is the RAM; Fujitsu component boxed in green. The RAM shares similarity to the eMMC and SD card as they're all computer/flash memory technologies. The best way to describe the difference between eMMC and RAM would be like having a large pot of soup and a bowl, where the eMMC is more like the pot and the RAM is to the bowl. Both are similiar in that they're containers but their main purposes are different.

You would much rather use the pot to store hot soup throughout the day while for the bowl to be able to scoop, hold in yours hand, and drink from. Let's say your RAM is like a broken or cracked bowl that'll hold the soup perfectly fine when sat down on a table, but the moment you pick up, tilt, and drink from that bowl, some of the soup leaks out of the cracks found along the bowl's brim.

While it's technically possible to use a USB flash drive or SD card as virtual RAM on computers for basic and light duty applications, that wouldn't hold up in practice for the 3DS systems. See the (ARM CPU + PICA200 GPU)/SoC boxed in red. It's not a coincidence these two components are placed right next to each other. Not only would there be the problem of no custom firmware programmed to utilize the SD card as the RAM, the distance between SoC & SD card, mismatch in read & write speed rates (compared to the RAM), and footprint (density of 256 MB vs surface area) means the SD card acting as RAM would be too bottle-necked in I/O and thermal stress limits.

***

Your n3DSXL reminded me of another person who had a n3DSXL with a nearly identical instability issue as yours (also ARM11 errors but slightly different readouts). All of the typical troubleshooting methods were tried to no lasting positive effects (ie, battery trick, quadruple reformat + H2testw, CTRTransfer, CTRTransfer (Type D9), SysNAND restore, eMMC Status Checker, etc).

• Is my N3DS broken? Random crashes no matter what