My new MicroSD appears to have a Nintendo 3DS folder, but given I did the above, is it not identical?
Hacking Arm11 (core 0) crash error near intro of games. Have formated fresh card, updated Luma.
- Thread starter ConfusedNDazzed
- Start date
- Views 17,838
- Replies 41
My new MicroSD appears to have a Nintendo 3DS folder, but given I did the above, is it not identical?
Yah, my bad. Step 5 would have copied your old Nintendo 3DS folder.
- Rename the Nintendo 3DS folder that's currently on the SD card to Nintendo 3DS (original); make sure there isn't a Nintendo 3DS folder (exactly named like that).
- Boot to HOME Menu, access Homebrew Launcher from whichever system title it was assigned to, and install those game CIAs via the 3DSX version of FBI.
- The n3DS should by now create the replacement Nintendo 3DS folder in the background. Launch those problematic games. Do they work now?
EDIT - I'm going to call it in for the tonight (1:51 AM EST). Leave a reply and I'll get back to you when I can.- Boot to HOME Menu, access Homebrew Launcher from whichever system title it was assigned to, and install those game CIAs via the 3DSX version of FBI.
- The n3DS should by now create the replacement Nintendo 3DS folder in the background. Launch those problematic games. Do they work now?
Last edited by TurdPooCharger,
Renaming the current Nintendo 3DS folder on the root of my card to Nintendo 3DS (original), inserting it into my n3DS and booting the system up has none of my previous icons come up on the homescreen. FBI, Homebrew Launcher, etc don't show up.
To open the 3DSX version of FBI using Homebrew Launcher, refer to the placement of the FBI.3dsx and boot.3dsx mentioned in post #14.
Here's how to Rosalina menu inject Homebrew Launcher and access it from a system title of choice,
If injecting HBL to a system title isn't working, you can use the CTRTransfer (Type D9) script as an assistance.
- Download and extract the gm9 script to the SD card at this location.
- sdmc:/gm9/scripts/CTRTransfer (Type D9).gm9
- GodMode9 → (HOME) button → Scripts... → CTRTransfer (Type D9) → Inject HBL to Camera → Exit
- HOME Menu → Nintendo 3DS Camera → Homebrew Launcher → FBI (3DSX version)
- Successfully injected Homebrew Launcher onto Nintendo Sound (for the heck of it), ran FBI, and installed the CIA of one of the problematic games (Pokemon X).
No worries. Pokemon X is a region free game. It should run on any region 3DS firmware. It's also a game that doesn't need a seed; it's not on the [GitHub, ihaveamac] SeedDB list.
That means the SD card and the games are not suspected to be the reasons why the n3DS crashes. Go to step 10 in post #10, and pray that this is a software issue with the 3DS firmware.
Last edited by TurdPooCharger,
Hello, again. Just gave that post a brief read, and it looks like quite the doozy.
Let's the say that doesn't fix my issue - what's the worst case scenario?
If reflashing the 3DS firmware with GodMode9 + CTRTransfer (Type D9), some post work with the accompanying homebrew apps (FBI, faketik, Cthulhu), and system updating back to the latest 11.13.0-45U firmware {all of this covered in the Instructions} does not fix the instability experienced with the games, the second worst outcome is that the n3DS motherboard has a hardware problem with the NAND storage chip that houses the 3DS firmware.
An example of the 2nd worst outcome
This can be seen by another n3DS user, fatsocat, who was able to get around the problem by switching over to an EmuNAND setup (secondary copy of the 3DS firmware placed and running off of the SD card since his primary/real 3DS firmware can't 100% function on the broken NAND chip).
- Am exeption occurred for N3DS CFW [posts #9–25 between fatsocat and I]
Examples of worst outcome
Here are others that have problems similiar to yours that couldn't be resolved with software repair solutions. Most moved on to buying a replacement 3DS system or replacing the bad motherboard.
Last edited by TurdPooCharger,
Heyo. Sorry for the late reply here. First and foremost, a massive thank you for your assistance, persistence, patience, and overall tolerance of me not being entirely the most adept at this kind of stuff. I've been lurking in the CFW scene for a few years now, around the early days of PSP, but besides helping with some translation stuff, surface level testing, going a bit deeper as I am now I've never really had to - nor have I come across an error that didn't just fix itself after the third or fourth attempt. I am eternally grateful, TurdPoo, I genuinely appreciate it. Part of me doesn't want to go through with the CTRTransfer, but I feel like I would have wasted your time if I don't. There must be a way for me to remunerate for your time in some capacity - does GBATemp have a donations, page, you yourself, something - this is my first time on the forum, and I've never had an individual be as helpful as you are right off the bat. Perpetually grateful, man.
If this doesn't work - the CTRTransfer - would I still be able to revert CFW on this n3DS? I know it plays carts, it's fully functional besides whatever problems it may have software wise, but I never intended on hacking it for myself. I was just passing it on to a younger relative of mine, and wanted them play freely without too much reliance on carts.
The whole hypothetical of a motherboard swap might be more effort than this system really warrants, so a revert would be case for me.
I'm on Step 13 of the guide at the moment, but I'm not seeing any tickets under FBI. I took a look at my /gm/out and only see my essentials.exefs inside there.
@ConfusedNDazed, you don't owe me or anyone anything. Here's my stance about accepting donations.
It has lots of steps involving upfront prep work ensuring the SD card is up to standard and post work after reflashing the ctrtransfer image. I've seen others skip the later steps where stuff like the DS(i) mode was left broken, and one person who reflash theirs under a suspected faulty SD card ended up with very negative consequence... That user's 3DS firmware was softbricked more than when he started.
About trust allowing CTRTransfer (Type D9) with Lvl3 write privileges,
If you later decide to try CTRTransfer (Type D9) but don't like the results or the script happens to crash in mid reflash,step 5 step 8 in the Instructions asks to backup the SysNAND *.bin image. All changes done by CTRTransfer (Type D9) and post work related homebrew apps can be reverse by restoring that sysnand.
If the n3DS can't be salvageable or you no longer wish to continue with what may end up being a goose chase, Nintendo still sells 2DS/3DS systems. Their refurbished units are just as good / indistinguishable from brand new ones.
If you decide to DIY fix yours by replacing the motherboard after determining it's hardware faulty,
Or, hire someone else to repair the n3DS. May need to be done as special request.
LATE EDIT - MY only request is that you don't throw away the n3DS. That model is the rarest in the 3DS family. Nintendo only made a limited production run of those.
- Am exeption occurred for N3DS CFW [post #21]
- Bottom half after the *** break.
It has lots of steps involving upfront prep work ensuring the SD card is up to standard and post work after reflashing the ctrtransfer image. I've seen others skip the later steps where stuff like the DS(i) mode was left broken, and one person who reflash theirs under a suspected faulty SD card ended up with very negative consequence... That user's 3DS firmware was softbricked more than when he started.
About trust allowing CTRTransfer (Type D9) with Lvl3 write privileges,
- Is my N3DS broken? Random crashes no matter what [post #8]
- Relevant explanation up til the Stabby McStab part.
If you later decide to try CTRTransfer (Type D9) but don't like the results or the script happens to crash in mid reflash,
If the n3DS can't be salvageable or you no longer wish to continue with what may end up being a goose chase, Nintendo still sells 2DS/3DS systems. Their refurbished units are just as good / indistinguishable from brand new ones.
- [store.nintendo.com] Nintendo 3DS | 2DS
- Sorry, choices are limited. Other models and editions would have to be found from private sellers as secondhand.
If you decide to DIY fix yours by replacing the motherboard after determining it's hardware faulty,
- [eBay] 2015 New 3DS Main board, Motherboard Replacement Part Nintendo WORKING
- [iFixit] Nintendo 3DS 2015
Or, hire someone else to repair the n3DS. May need to be done as special request.
- wiigotem - He's the same seller of the n3DS mobo from above.
- testerfan - Might need to supply him with a replacement n3DS motherboard. Maybe board reflow service?
LATE EDIT - MY only request is that you don't throw away the n3DS. That model is the rarest in the 3DS family. Nintendo only made a limited production run of those.
The tickets (TIK files) are dumped to a folder named in this format like this.
- sdmc:/gm9/out/
- <date>_<serial>_system tickets_(<region>)_000
- sdmc:/gm9/out/
- <date>_<serial>_dsiware_000
Last edited by TurdPooCharger,
I hear you loud and clear about the donations aspect - it's unfortunate that simple gestures can be misinterpreted and misconstrued. I'll try my best to pay it forward; in the off chance you want some good coffee or anything, do let me know - that's my forte outside of this haha. It's the least I can do.
It was my intention to go all in on trying to fix this issue, and if it came up a hardware issue then, that would be my point of defeat, but, I'm calling it here. I would much rather salvage the system before picking and prodding to its eventual death. I backed up the *.bin*, and *.exefs* gm9 gave out - what's my next approach to getting the 3DS back to normal? Do I wipe the current microSD (despite being on step 13 of the guide), and then perform the NAND backup? If so, what's next to removing CFW off the 3DS - I'd like to have it stock before passing it over. The last thing I want is the young one accidentally button combo-ing into something they're not supposed to.
Uninstalling custom firmware can leave the n3DS stuck in a software brick with no means to fix it. It would be like spelunking and then cutting the cord when you reach the bottom.
Removing custom firmware also stops almost all pirated games from working.
***
When referring to the Instruction's step 13 (FBI installing system tickets & TWL/DSiware CIAs), are their folders missing from the sdmc:/gm9/out directory?
Just to be sure we're on the same page, did you perform standard [3ds.hacks.guide] CTRTransfer or the alternative CTRTransfer (Type D9) - CTRTransfer?
Last edited by TurdPooCharger,
I'm using yours: https://gbatemp.net/threads/release-godmode9-scripts-megathread.482150/page-9#post-8550543.
I'm at this section in the guide:
The contents of my /gm9/out :
I injected Homebrew Launcher into 3DS Camera and don't have anything that looks similar to the image in your guide.
Last edited by ConfusedNDazzed,
This is a first I've seen my script fail this way. Those folders with the TIKs and CIAs are supposed to be in the sdmc:/gm9/out.
I have no explanation as to why they're missing other than it might be related to the latest v1.9.2pre1 of GodMode9 released back in August. There has been a past instance where the script engine broke where it rendered CTRTransfer (Type D9) unsafe to use at one point.
- [bug] Mounting `ticket.db` without `certs.db` can crash in a specific script run scenario in v1.9.0.
Apologies for the failed repair attempt. Looks like you'll have to undo the changes.
I'm going put a big warning on the CTRTransfer (Type D9) page and try to figure out what went wrong. Thank you * for bring this to my attention and your patience & understanding.
Last edited by TurdPooCharger,
This is a first I've seen my script fail this way. Those folders with the TIKs and CIAs are supposed to be in the sdmc:/gm9/out.
I have no explanation as to why they're missing other than it might be related to the latest v1.9.2pre1 of GodMode9 released back in August. There has been a past instance where the script engine broke where it rendered CTRTransfer (Type D9) unsafe to use at one point.
I wouldn't it past the idea the ticket mounting broke again as there are some interesting features being developing behind the scene that utilizes it.
- [bug] Mounting `ticket.db` without `certs.db` can crash in a specific script run scenario in v1.9.0.
Apologies for the failed repair attempt. Looks like you'll have to undo the changes.
I'm going put a big warning on the CTRTransfer (Type D9) page and try to figure out what went wrong. Thank you * for bring this to my attention and your patience & understanding.
The pleasure is all mine, Turbo - no worries at all. You have been more help than I could have ever imagined someone offer up. Much appreciated.
As for going forward with the NAND Backup, can I just go into it no problem with my current setup?
Back to my previous suggestion of reverting back to full OFW, and removing CFW, there's no possibility of that, correct?
Your SD card passed H2testw hardware checks, and the sysnand *.bin image is a recent backup. I don't foresee a problem restoring the SysNAND. The n3DS will revert back to the state it was in before the CTRTransfer (Type D9).
It's possible to go back to stock or open firmware but not recommended. Even if the custom firmware is uninstalled, that doesn't address the issue as to why the n3DS crashes in the first place. Removing CFW all it does is limit your repair options.
Was this n3DS recently purchased? If so, is the seller's return period still open? If we were to assume at this moment GodMode9 v1.9.2pre1 doesn't have a bug with mounting tickets or building CIAs by script, everything that has transpired in our troubleshooting sessions indicates yours likely has a bad motherboard. Having CFW or no CFW would not make a difference if that's the case.
@ConfusedNDazzed, is this you on Nintendo Homebrew discord?
***
I couldn't reproduce this supposed bug where CTRTransfer (Type D9) fails to dump the tickets and TWL system CIAs on my n3DSXL, o3DSXL, and n3DS under GodMode9 v1.9.2pre1.
Can you walk me through what happened as you followed the CTRTransfer (Type D9)'s Instructions?
***
From steps 5–7, were all of these files added onto your SD card?
(Root of the SD Card), sdmc:/
The image you shared in post #34 shows that the only file in the sdmc:/gm9/out directory is the essential.exefs.
At step 8, which method did you used to backup the SysNAND *.bin image?
If you created that image, was it moved off the SD card?
***
At step 9, when you launched the CTRTransfer (Type D9) script and selected the CTRTransfer option, do you recall seeing any one of these three messages?
***
I couldn't reproduce this supposed bug where CTRTransfer (Type D9) fails to dump the tickets and TWL system CIAs on my n3DSXL, o3DSXL, and n3DS under GodMode9 v1.9.2pre1.
Can you walk me through what happened as you followed the CTRTransfer (Type D9)'s Instructions?
***
From steps 5–7, were all of these files added onto your SD card?
(Root of the SD Card), sdmc:/
- 3ds/
- Cthulhu.3dsx
- FBI.3dsx
- faketik.3dsx
- luma/
- payloads/
- GodMode9.firm
- payloads/
- gm9/
- in/
- 11.5.0-38U_ctrtransfer_n3ds.bin
- 11.5.0-38U_ctrtransfer_n3ds.bin.sha
- scripts/
- CTRTransfer (Type D9).gm9
- GM9Megascript.gm9
- NANDManager.gm9
- in/
- boot.3dsx
- boot.firm
The image you shared in post #34 shows that the only file in the sdmc:/gm9/out directory is the essential.exefs.
At step 8, which method did you used to backup the SysNAND *.bin image?
If you created that image, was it moved off the SD card?
***
At step 9, when you launched the CTRTransfer (Type D9) script and selected the CTRTransfer option, do you recall seeing any one of these three messages?
Last edited by TurdPooCharger,
Hey, Turbo, sorry I missed your last two posts here - got caught up with some weekend errands. I went back and reverted my memory card some time yesterday, but steps 5 to 7, I had that identical set up in my memory card.
As for Step #8, I used Method A, and followed it directly so the .bin and bin.sha were deleted off the MicroSD card before being remounted.
When doing the CTRTransfer, I don't recall seeing the image farthest left - I ran the script and followed the prompts. I would have noted anything in red on the top screen, but everything seemed to function smoothly.
If I can offer any more help, do let me know. While the MicroSD I was using is reverted back, I still have backups of just about every state we had my memory card in.
I have one last software repair idea we can try but discussions would have to continue in PM (private message). If you're interested, I'll PM you the details.
EDIT 1 - There are several safety conditions that the script checks for before making the decision to reflash the ctrtransfer image.
- (1) Are the image *.bin and *.sha in the sdmc:/gm9/in directory?
- (2) Ask the user to grant Lvl1-3 editing permissions.
- (3) Determine if the 3DS firmware has unusual or atypical softbrick (2.1.0 downgrade, missing or nonstandard sized partitions).
- (4) Check if the SD card has enough free space to do work.
- (5) Make sure the selected image is for the appropriate system (Old 3DS vs New 3DS. 3DS firmware region vs image region).
- (6) Test if the BIN image is the correct size and image mountable.
- (7) Compare the actual hash of the BIN vs the SHA record. Is the image data intact?
Do you remember waiting several minutes while the script did its thing, seeing a bunch of text code scroll up, and several short pauses with colored messages explaining what the script was doing next?
Last edited by TurdPooCharger,
Similar threads
- Question
-
Xdqwerty
what are you looking at?
-
-
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
@realtimesave, hey there buddy chum pal friend buddy pal chum bud friend fella bruther amigo pal buddy friend chummy chum chum pal
-
@
Xdqwerty:
@realtimesave, hey there buddy chum pal friend buddy pal chum bud friend fella bruther amigo pal buddy friend chummy chum chum pal
-
-
-
-
-
-
-
-
-
-
-
@
Sicklyboy:
@Xdqwerty, Osu! Tatakae! Ouendan! is the Japanese version of the game, different settings/characters/songs but otherwise identical mechanics. I played that before I knew about Elite Beat Agents lol. Both fantastic games https://en.wikipedia.org/wiki/Osu!_Tatakae!_Ouendan+1 -
-
