Luma3ds: System Crashes on ARN 4.0+ at Boot

Created on 16 Apr 2016  路  24Comments  路  Source: LumaTeam/Luma3DS

  • Console = Blue JPN N3DS LL
  • sysNAND = 9.2 JPN
  • emuNAND = 10.7 JPN (Made with emuNAND9)
  • loader = a9lh

Ever since ARN 4.0 and above (nightlies included) my N3DS crashes after a second or two after booting my homescreen. It seems to load up fine showing my theme like normal, then proceeds to crash to this screen shown here. I get this no matter what NAND I boot into regardless if it is sysNAND or emuNAND. I have all of the right files in the right places (I know this because ARN 3.14 works just fine), and my a9lh work fine because I can boot other payloads with no issue (BootCTR9, D9, etc.).

What makes this issue even more odd for me is that is displays the error message in English. If I were to trigger the same kind of error screen by different means (like trying to run a poorly made .CIA) I would get the same error in Japanese. I can not even begin to wonder why is hows the message in English since i have not changed or installed any CIAs to either of my NANDs.

I am by no means an expert but have come to the conclusion it has to do something with the _3ds_injector_ code that was added and used on ARN 4.0+ not liking something on my system for some reason. I say this because when loading a 3ds_injector .cakes based on ARN implementation of it in CakesI experience the same issue. I am not sure where the issue lie in the 3ds_injector code in ARN because if I use the 3ds_injector.cakes mid-kid released a few days prior I don't have the crash at system start up, but the region free works just fine.

I have even tried coming through my installed titles on my NAND and they all match based on what 3DSbrew said I should have. I have also gone through looking for any bad installed CIAs on my SD and even uninstalled some that I thought may trigger it. Yet, I am left with the same problem.

Thank you for your time.

invalid

Most helpful comment

Delete the SecureInfo_C file. It was created because you used the original yifan injector, and now AuRei keeps loading it. I've disabled this feature in all builds since 4.1. SecureInfo_C is a copy, only useful for region changes.

All 24 comments

Have you tried renaming/moving the "Nintendo 3DS" folder in your SD?

Have you tried renaming/moving the "Nintendo 3DS" folder in your SD?

No, wouldn't that mess up my titles?
And if not, how is the right way to go about moving it?

It will mess with your titles, but it's for debugging.
Just rename "Nintendo 3DS" folder to "Nintendo 3DS_", and try booting.

Okay so I renamed it to "Nintendo 3DS_" as you said. I booted up the system like normal. It booted to the default white theme (as expected), but still after 2 seconds it crashes to the screen posted earlier (still English as well).

If you're using ARN5, can you enable "Use developer UNITINFO", and then try again?

If you're using ARN5, can you enable "Use developer UNITINFO", and then try again?

Alright so I made sure that i was using ARN 5, went into my settings and enabled "Use developer UNITINFO" (if it matters the only other setting I have enabled is force A9Hl detection & show the system version in system settings). I then booted the console to get the same crash. Here is a picture with the extra info at the top

Is there any way you can check the version of 0004013000003802? FBI 2.0.x is capable of doing that.

Is there any way you can check the version of 0004013000003802? FBI 2.0.x is capable of doing that.

Using FBI 2.0.4, this is the information on 0004013000003802.

Steveice10: that error is from failing to get the serial number from the config service, i think
Shadowhand: Steveice10, so NAND is fucked?
Steveice10: or maybe not necessarily
Steveice10: there are multiple places it can come from it seems
Steveice10: getting serial no, getting region, etc
Steveice10: basically its a general "could not get info from config service" error

basically its a general "could not get info from config service" error

So what is the (or is there) solution?

Try this build, see if that changes anything.

Try this build, see if that changes anything.

Yup the build works as it should. Everything loads up, region free is fine, & no errors.

Well, keep using that version until this is fixed. I'll inform AuroraWright.

Well, keep using that version until this is fixed. I'll inform AuroraWright.

Alright thank you very much for your time, and providing me a build that works on my system

If you could send me your SecureInfo_A (privately, don't post it in public as it contains unique infos) I could test that. You can use GodMode9 to dump it. It's in CTRNAND/sys/rw.

If you could send me your SecureInfo_A (privately, don't post it in public as it contains unique infos) I could test that. You can use GodMode9 to dump it. It's in CTRNAND/sys/rw.

I PMed you on gbatemp with what you requested.
Pulled it from my emuNAND using the latest GodMode9 as you suggested.

OK, this is all very weird and I can't replicate it. I have a Japanese 10.7 EmuNAND on my N3DS, I just replaced my own secureinfo_a with yours, and it works perfectly fine (so the secureinfo_a signature patch isn't at fault here).
Stupid question: by any chance, do you also have a SecureInfo_C where the SecureInfo_A is? Also, did you happen to install a pre-patched region-free Home Menu/NS or something like that, before ARN had region free built-in?
I have a feeling something is wrong with the original NAND you also cloned EmuNAND from, but I can't verify that from here lol.

Stupid question: by any chance, do you also have a SecureInfo_C where the SecureInfo_A is?

So I just checked via latest GodMode9 at EMUNAND CTRNAND/rw/sys/and it seems there is a file named "Secureinfo_C" below "Secureinfo_A". (this file is also in that same place as SYSNAND CTRNAND)

Also, did you happen to install a pre-patched region-free Home Menu/NS or something like that, before ARN had region free built-in?

I mean not that I know of, I never on purpose installed anything like that. For the longest time I just used gateway so RF stuff was never needed to run anything to play non JPN/RF titles.

I have a feeling something is wrong with the original NAND you also cloned EmuNAND from, but I can't verify that from here lol.

Well i appreciate the help. Is there any way to make fresh NANDs and then from there re inject my (I may be using the wrong word here) titles so they show up and such?

@AuroraWright Steveice10 said the problem lies within SecureInfo_C.

Uh, I've seen people talking about this SecureInfo_C file but never any explanation of its purpose (no info on 3dbrew about it and I don't have it on my 3DS)
What's it? Simply a copy of SecureInfo_A?
Why does it exist?

Delete the SecureInfo_C file. It was created because you used the original yifan injector, and now AuRei keeps loading it. I've disabled this feature in all builds since 4.1. SecureInfo_C is a copy, only useful for region changes.

@Melon-Bread Did this work?

Yes I removed SecureInfo_C from my sysNAND & emuNAND and everything worked as it should. No need for a custom build.

Perfect. Happy gaming.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

renatosk picture renatosk  路  4Comments

dbenfouzari picture dbenfouzari  路  3Comments

Azure-Agst picture Azure-Agst  路  3Comments

ksanislo picture ksanislo  路  4Comments

DartRuffian picture DartRuffian  路  3Comments