Homebrew Strange Luma v9.1 Problem.

  • Thread starter Thread starter msbmarth
  • Start date Start date
  • Views Views 1,193
  • Replies Replies 7

msbmarth

Member
Newcomer
Joined
Mar 18, 2018
Messages
23
Reaction score
0
Trophies
0
Age
36
XP
136
Country
United States
Hey Everyone,
So, I have a 3DS running Luma v9.1 and the latest B9S version. However, most of the time when I try booting up the 3DS, I am met with a blue light flashing on, and then off again almost immediately afterwards. Sometimes, I'm met with a message saying , "Unable to mount CTRNand" or something along those lines. And then sometimes, the 3DS will boot into the homescreen completely fine and function as normal, or crash. I doubt its the SD card, as I've done checks already before and it doesn't seem to be the problem. Boot.firm is also on the root of the SD card, and the correct version.
So, any suggestions?
 
Last edited by msbmarth,
The problem is the 3DS is sometimes having trouble reading the Luma3DS boot.firm from the root of the SD card. If you haven't already done so, you should copy and paste the Luma3DS 9.1 boot.firm from the SD card to the CTRNAND, replacing anything that is already there.
 
The problem is the 3DS is sometimes having trouble reading the Luma3DS boot.firm from the root of the SD card. If you haven't already done so, you should copy and paste the Luma3DS 9.1 boot.firm from the SD card to the CTRNAND, replacing anything that is already there.
How would I go about doing that?
 
Okay. I just have, and it seems to be working much better now. Thank you for the help!
No problem. If you want to decrease the likelihood that you will run into this error again, you might want to delete boot.firm from your SD card so it defaults to the one on your CTRNAND. If your SD card is the problem, then you still might run into errors before it can load the CTRNAND version.
 
No problem. If you want to decrease the likelihood that you will run into this error again, you might want to delete boot.firm from your SD card so it defaults to the one on your CTRNAND. If your SD card is the problem, then you still might run into errors before it can load the CTRNAND version.
Noted... because it’s happening again! Ill see if that improves it.
 
No problem. If you want to decrease the likelihood that you will run into this error again, you might want to delete boot.firm from your SD card so it defaults to the one on your CTRNAND. If your SD card is the problem, then you still might run into errors before it can load the CTRNAND version.
Okay, quick update...
It has gone back to the original problem, except there is no error message, as I’ve seen.
 

Site & Scene News

Popular threads in this forum