Closed InsanePrimate closed 1 year ago
With v12.0 you need to enable both game patching and loading external firms and module. Please do it manually for now. I'll update the build process and instructions soon.
Both game patching and loading external firms and module options are enabled and the menu still doesn't open (tested in Metroid Samus Returns). I'll wait for a fix, thank you for having a look at it. :-)
https://mega.nz/file/wANSiSrA#3zffZjJHaCFseYSCzgdcdLkoOsnOKpAbaydcaKqOx-c
Try installing wumiibo through this. Should work.
"Verification failed. Please manually install the app. Press B to exit." Is all I get. What am I doing wrong? Could it be, that the cluster size of 64 kb (I am using a 256 gb SD card) is messing something up? It did work fine before though.
Open up luma config menu and enable both game patching and loading external firms and modules.
Both are enabled.
I am not sure what's wrong with your installation, the same steps seem to work fine for me without any problem.
Also, open amiibo settings and then open rosalina menu, go to process lista nd check whether you have a process named wumiibo/nfc
I am not sure what's wrong with your installation, the same steps seem to work fine for me without any problem.
Also, open amiibo settings and then open rosalina menu, go to process lista nd check whether you have a process named wumiibo/nfc
I do not have a process running named wumiibo/nfc... hmmm... could it be Fastboot? (that is the only difference in the setup compared to the standard)
I am not sure what's wrong with your installation, the same steps seem to work fine for me without any problem. Also, open amiibo settings and then open rosalina menu, go to process lista nd check whether you have a process named wumiibo/nfc
I do not have a process running named wumiibo/nfc... hmmm... could it be Fastboot? (that is the only difference in the setup compared to the standard)
Would you happen to be on discord? It looks like it would take time to debug this issue..
I am not sure what's wrong with your installation, the same steps seem to work fine for me without any problem. Also, open amiibo settings and then open rosalina menu, go to process lista nd check whether you have a process named wumiibo/nfc
I do not have a process running named wumiibo/nfc... hmmm... could it be Fastboot? (that is the only difference in the setup compared to the standard)
Would you happen to be on discord? It looks like it would take time to debug this issue..
Well I do have discord but i am not on your server.
I am not sure what's wrong with your installation, the same steps seem to work fine for me without any problem. Also, open amiibo settings and then open rosalina menu, go to process lista nd check whether you have a process named wumiibo/nfc
I do not have a process running named wumiibo/nfc... hmmm... could it be Fastboot? (that is the only difference in the setup compared to the standard)
Would you happen to be on discord? It looks like it would take time to debug this issue..
Well I do have discord but i am not on your server.
Please do join, and ping me after doing so. My discord id is: Kartik#9392
I tried joining (https://discord.com/invite/hyuvmb9) but it wouldn't let me XD nothing seems to be working on my end XD
My setup as of now.
System model: [New 2DS XL]
SysNAND version: [11.16.0-49E]
Entrypoint: [Fastboot v1.2]
Luma3DS version: [v12.0]
SD Card: [256 GB Sandisk Ultra] ( Fat 32 with 64 Kb cluster size)
Luma3DS configuration/options:
Screen brightness: (4 )
Splash: ( Off)
PIN lock: ( Off)
New 3DS CPU: ( Off)
Homebrew autoboot (Off)
--
Enable loading external FIRMs and modules: (X)
Enable game patching: (X)
Redirect app. syscore threads to core2 ( )
Show NAND or user string in System Settings: (X)
Show GBA boot screen in patched AGB_FIRM: ( )
Set developer UNITINFO: ( )
Disable Arm11 exception handlers: ( )
Enable Rosalina on SAFE_FIRM: ( )
I tried joining (https://discord.com/invite/hyuvmb9) but it wouldn't let me XD nothing seems to be working on my end XD
Please tell me your discord id
I did send you a friend invite on discord.
Closing as the issue was fixed. User had fastboot which was configured to load luma from CTRNAND instead of SD.
I delete luma boot.frim from sdcard and copy it to ctrnand but it not work
it work now
As the title says. It would appear, that the newest Luma release is no longer compatible. Maybe something to do with the way it handles LayeredFs patching?