Homebrew Updated to 11.3 - Black Screen On Startup After Splash

[Wolfy]

I've seen that external firmware.bin are blocked, but it's been awhile since I screwed around with my 3DS, would this be the cause as that I can see the splash screen fine and get into Hourglass, but it just stays black.

Removing the SD Card works, and then putting it back in just brings the games back, can run them just fine. But starting the 3DS with SD Card in keeps it at a black screen....

 

[x65943]

I've seen that external firmware.bin are blocked, but it's been awhile since I screwed around with my 3DS, would this be the cause as that I can see the splash screen fine and get into Hourglass, but it just stays black.

Removing the SD Card works, and then putting it back in just brings the games back, can run them just fine. But starting the 3DS with SD Card in keeps it at a black screen....

are you running luma? get the latest luma, extract the arm9loaderhax.bin to the root of your sd card, and boot your 3ds.

https://github.com/AuroraWright/Luma3DS/releases

 

[Wolfy]

are you running luma? get the latest luma, extract the arm9loaderhax.bin to the root of your sd card, and boot your 3ds.

https://github.com/AuroraWright/Luma3DS/releases

I was running an older version before, but used the Luma Updater and it worked fine, but didn't help, attempted to try anyway and used the Github version directly, nothing.

Could ShadowNAND be the issue?

 

[x65943]

I was running an older version before, but used the Luma Updater and it worked fine, but didn't help, attempted to try anyway and used the Github version directly, nothing.

Could ShadowNAND be the issue?

if the arm9loaderhax.bin on your ctr nand is the issue, then restoring an older nand.bin from before you copied it to the ctrnand should fix the issue. Can you boot hourglass9?

 

[Wolfy]

if the arm9loaderhax.bin on your ctr nand is the issue, then restoring an older nand.bin from before you copied it to the ctrnand should fix the issue. Can you boot hourglass9?

I can, though I it's been awhile so forgive me for the "noob" question, would restoring an older NAND remove games that were installed after the fact? And can't seem to find any ways to remove ShadowNAND ~_~

 

[x65943]

I can, though I it's been awhile so forgive me for the "noob" question, would restoring an older NAND remove games that were installed after the fact? And can't seem to find any ways to remove ShadowNAND ~_~

You should be able to dump your tickets from this current nand, and reinject them into your older one. Which I think should allow you to keep your installed games.

To be safe, make a backup of your 11.3 nand before you do anything.

 

[Wolfy]

Yup, though I vaguely remember FBI having some sort of Dump tickets feature? If not then tik2sd...

 

[x65943]

Yup, though I vaguely remember FBI having some sort of Dump tickets feature? If not then tik2sd...

decrypt9 should be have a function to dump tickets.

 

[Giodude]

None of any of this has anything to do with the black screen. What happened is you're using a custom nfirm, and 11.3 prevents the use of external nfirm loading. Just delete firmware.bin in the luma folder or disable external nfirm loading in the luma config.

 

[Wolfy]

None of any of this has anything to do with the black screen. What happened is you're using a custom nfirm, and 11.3 prevents the use of external nfirm loading. Just delete firmware.bin in the luma folder or disable external nfirm loading in the luma config.

I feel like that would be the problem, except, deleting firmware.bin merely freezes the screen at the splash image, and by the luma config you mean the one placed at /luma/yukara.ini? It is already directing the default to /luma/arm9loaderhax.bin

Spoiler

#yakareo, yakareo, tra tra tra tra!
#No modifiques nada -NADA-.

[GLOBAL]
fileLog = 0
screenLog = 0

[DEFAULT]
path = /luma/arm9loaderhax.bin
delay = 100
offset = 0
payload = -1

[KEY_START]
path = /luma/arm9-payloads/cbm9.bin
delay = 2000
offset = 0
payload = -1
splash = 1
splash_image = /luma/arm9-payloads/splash/recovery.bin

 

[Giodude]

I feel like that would be the problem, except, deleting firmware.bin merely freezes the screen at the splash image, and by the luma config you mean the one placed at /luma/yukara.ini? It is already directing the default to /luma/arm9loaderhax.bin

Spoiler

#yakareo, yakareo, tra tra tra tra!
#No modifiques nada -NADA-.

[GLOBAL]
fileLog = 0
screenLog = 0

[DEFAULT]
path = /luma/arm9loaderhax.bin
delay = 100
offset = 0
payload = -1

[KEY_START]
path = /luma/arm9-payloads/cbm9.bin
delay = 2000
offset = 0
payload = -1
splash = 1
splash_image = /luma/arm9-payloads/splash/recovery.bin

Im talking about holding select while booting. Not the actual actual config.

 

[Wolfy]

Im talking about holding select while booting. Not the actual actual config.

What would that be under? For using external firm?

 

[Sonic Angel Knight]

Umm why restore nand? Just boot godmode 9 and replace the a9lh luma on NAND with the most recent one.

 

[Wolfy]

Umm why restore nand? Just boot godmode 9 and replace the a9lh luma on NAND with the most recent one.

Just cause it's been awhile since I've done so, could you link to a guide?

 

[Sonic Angel Knight]

Just cause it's been awhile since I've done so, could you link to a guide?

You have a9lh already right?

• Download god mode 9 from d0k3 github page. (Same place you get hourglass9 and decrypt9 from)
• Rename the arm9loaderhax.bin file to have a button in the title. (For example "Left_Godmode9.bin)
• Put the fiile in the luma/payloads folder on the sd card.
• Insert Sd card into 3ds, hold left and turn power on.
• You should have loaded godmode9.
• Select the SD browser option, and loacte the Latest build of luma (Should be on root named "arm9loaderhax.bin)
• Press the copy option (Should be y button.)
• Back out to main menu and select ctrnand
• there should be a arm9loaderhax.bin in this directory already if you had SD Less booting before hand set up. Simply past the copied file on clipboard.
• After paste is done, you updated the CTRNAND LUMA file. (NOTE YOU MUST DO THIS EVERY TIME A NEW UPDATE FOR LUMA IS AVAILABLE)

That is how you do it. Usually you would use FBI installer from system menu but only if you can access it.

 

[Dracari]

wait 11.3 blocks us using an external Nfirm? whelp for now RIP NTR :/

 

[KunoichiZ]

wait 11.3 blocks us using an external Nfirm? whelp for now RIP NTR :/

BootNTR has been updated to support 11.3.

 

[Dracari]

BootNTR has been updated to support 11.3.

Fuck that was fast this time around! any word what in 11.3 is blocking Nfirm loading?

 

[ngtunganh]

I got same problem too,how to fix this again?
Edit: Nvm I updated my luma and It just work

 

[The Catboy]

If you were running SaltFW, you will need to update. He has a test build on his thread that I just confirmed to be working
http://gbatemp.net/threads/saltfw-slim-alternative-firmware.423554/page-22#post-7075863
Also future builds of SaltFW can be copied to the CTRNAND, so you don't need ShadowNAND anymore.
You can just follow this part of the guide to updating the latest A9LH. It will safely update from ShadowNAND, I know because I did it before.
https://3ds.guide/updating-a9lh