(link to BSU instead of the dead link to the less comprehensive troubleshooting on the guide) |
m ("Play Coin") |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
Lumabug is a simplified term for an issue that often occurs after following our CFW installation guide. Despite its name, it is not caused by Luma3DS, and could occur even on a stock system. | |||
== | Instead, the reason for its name is because having Luma3DS installed makes it far easier to cause it. | ||
==What is lumabug== | |||
This issue is due to the 3DS having two clocks, as follows: | This issue is due to the 3DS having two clocks, as follows: | ||
*Real-time clock (RTC): The RTC is embedded into the system's hardware. It starts at 2000-01-01, and begins ticking upward when the console is powered on for the first time, after which it works even while the 3DS is powered off. This clock cannot be changed without CFW (unless the battery is removed, but that only resets it). | *Real-time clock (RTC): The RTC is embedded into the system's hardware. It starts at 2000-01-01, and begins ticking upward when the console is powered on for the first time, after which it works even while the 3DS is powered off. This clock cannot be changed without CFW (unless the battery is removed, but that only resets it). | ||
Line 8: | Line 9: | ||
During our guide's Finalizing Setup, we set the real time clock to the actual time, and set the offset to 0 - this helps homebrew apps that use the time, as they cannot access the HOME Menu clock but would be using extremely old dates if the RTC were not changed.<br> | During our guide's Finalizing Setup, we set the real time clock to the actual time, and set the offset to 0 - this helps homebrew apps that use the time, as they cannot access the HOME Menu clock but would be using extremely old dates if the RTC were not changed.<br> | ||
This RTC fix has the side effect of causing | This RTC fix has the side effect of causing lumabug. | ||
The database for Play Coins, <code>gamecoin.dat</code>, stores the date of your last earned Play Coin as an RTC date. When you earn a Play Coin for the first time after fixing the RTC, a gap of (usually) ~22 years is created when the 3DS stores the new Play Coin's date. When the system is next powered on after this, it detects the gap and starts listing every single date up to the new Play Coin's date. | The database for Play Coins, <code>gamecoin.dat</code>, stores the date of your last earned Play Coin as an RTC date. When you earn a Play Coin for the first time after fixing the RTC, a gap of (usually) ~22 years is created when the 3DS stores the new Play Coin's date. When the system is next powered on after this, it detects the gap and starts listing every single date up to the new Play Coin's date. | ||
Line 16: | Line 17: | ||
If you leave your 3DS idle for multiple years, then get a Play Coin, this same issue can happen on stock firmware. However, it will take less time to boot, as there are fewer dates to list than the full 22 years caused by an RTC fix. | If you leave your 3DS idle for multiple years, then get a Play Coin, this same issue can happen on stock firmware. However, it will take less time to boot, as there are fewer dates to list than the full 22 years caused by an RTC fix. | ||
==Is | ==Is my issue lumabug?== | ||
While experiencing this bug, you cannot boot into the HOME menu normally, but you should still be able to access the Rosalina Menu (L + D-PAD DOWN + SELECT) on the black screen, and be able to hold buttons while powering on to boot to GodMode9 (START) and the Luma3DS configuration menu (SELECT). | While experiencing this bug, you cannot boot into the HOME menu normally, but you should still be able to access the Rosalina Menu (L + D-PAD DOWN + SELECT) on the black screen, and be able to hold buttons while powering on to boot to GodMode9 (START) and the Luma3DS configuration menu (SELECT). | ||
If your issue has any of the following, it is not | If your issue has any of the following, it is not lumabug: | ||
*If the power LED does not stay on when powering on the console, you are most likely missing <code>boot.firm</code> from the SD root. | *If the power LED does not stay on when powering on the console, you are most likely missing <code>boot.firm</code> from the SD root. | ||
*If you cannot access the Rosalina menu from the black screen, this is not | *If you cannot access the Rosalina menu from the black screen, this is not lumabug but may be [[3dsguide:troubleshooting#my-device-gets-stuck-on-a-black-screen-with-a-static-blue-light|one of these related issues]]. | ||
*If you cannot boot into GodMode9 or the Luma configuration menu, you may have missing CFW files or [[Checking SD card integrity|issues with SD integrity]]. If not, then you likely have a serious issue that will require guided assistance and should ask [https://discord.com/invite/nintendohomebrew the Nintendo Homebrew Discord] for help. | *If you cannot boot into GodMode9 or the Luma configuration menu, you may have missing CFW files or [[Checking SD card integrity|issues with SD integrity]]. If not, then you likely have a serious issue that will require guided assistance and should ask [https://discord.com/invite/nintendohomebrew the Nintendo Homebrew Discord] for help. | ||
==Fixing | ==Fixing lumabug== | ||
If you have verified that your issue is specifically | If you have verified that your issue is specifically lumabug, the steps for fixing lumabug are as follows: | ||
# Power off the console | # Power off the console | ||
# Take out any game cartridge, but leave the SD card in | # Take out any game cartridge, but leave the SD card in | ||
#* The cartridge is unrelated to | #* The cartridge is unrelated to lumabug, but could also cause issues with booting if it's not being read correctly | ||
# Power on the console | # Power on the console | ||
# Leave the console open and powered on for 10-15 minutes. Do not touch the console during this time | # Leave the console open and powered on for 10-15 minutes. Do not touch the console during this time | ||
If the console boots successfully in that time, the bug is now fixed and is unlikely to happen again. If the console still fails to boot to home menu, ask [https://discord.com/invite/nintendohomebrew the Nintendo Homebrew Discord] for more help. Mention that you have already tried the | If the console boots successfully in that time, the bug is now fixed and is unlikely to happen again. If the console still fails to boot to home menu, ask [https://discord.com/invite/nintendohomebrew the Nintendo Homebrew Discord] for more help. Mention that you have already tried the luma black screen process. | ||
[[Category:Nintendo 3DS information]] | [[Category:Nintendo 3DS information]] |
Revision as of 00:10, 18 November 2023
Lumabug is a simplified term for an issue that often occurs after following our CFW installation guide. Despite its name, it is not caused by Luma3DS, and could occur even on a stock system.
Instead, the reason for its name is because having Luma3DS installed makes it far easier to cause it.
What is lumabug
This issue is due to the 3DS having two clocks, as follows:
- Real-time clock (RTC): The RTC is embedded into the system's hardware. It starts at 2000-01-01, and begins ticking upward when the console is powered on for the first time, after which it works even while the 3DS is powered off. This clock cannot be changed without CFW (unless the battery is removed, but that only resets it).
- HOME Menu clock: A software value, set as a constant offset from the RTC. Most applications use this to determine the time, and use the offset to determine when the time is changed.
During our guide's Finalizing Setup, we set the real time clock to the actual time, and set the offset to 0 - this helps homebrew apps that use the time, as they cannot access the HOME Menu clock but would be using extremely old dates if the RTC were not changed.
This RTC fix has the side effect of causing lumabug.
The database for Play Coins, gamecoin.dat
, stores the date of your last earned Play Coin as an RTC date. When you earn a Play Coin for the first time after fixing the RTC, a gap of (usually) ~22 years is created when the 3DS stores the new Play Coin's date. When the system is next powered on after this, it detects the gap and starts listing every single date up to the new Play Coin's date.
This causes the system to need several minutes to boot.
If you leave your 3DS idle for multiple years, then get a Play Coin, this same issue can happen on stock firmware. However, it will take less time to boot, as there are fewer dates to list than the full 22 years caused by an RTC fix.
Is my issue lumabug?
While experiencing this bug, you cannot boot into the HOME menu normally, but you should still be able to access the Rosalina Menu (L + D-PAD DOWN + SELECT) on the black screen, and be able to hold buttons while powering on to boot to GodMode9 (START) and the Luma3DS configuration menu (SELECT).
If your issue has any of the following, it is not lumabug:
- If the power LED does not stay on when powering on the console, you are most likely missing
boot.firm
from the SD root. - If you cannot access the Rosalina menu from the black screen, this is not lumabug but may be one of these related issues.
- If you cannot boot into GodMode9 or the Luma configuration menu, you may have missing CFW files or issues with SD integrity. If not, then you likely have a serious issue that will require guided assistance and should ask the Nintendo Homebrew Discord for help.
Fixing lumabug
If you have verified that your issue is specifically lumabug, the steps for fixing lumabug are as follows:
- Power off the console
- Take out any game cartridge, but leave the SD card in
- The cartridge is unrelated to lumabug, but could also cause issues with booting if it's not being read correctly
- Power on the console
- Leave the console open and powered on for 10-15 minutes. Do not touch the console during this time
If the console boots successfully in that time, the bug is now fixed and is unlikely to happen again. If the console still fails to boot to home menu, ask the Nintendo Homebrew Discord for more help. Mention that you have already tried the luma black screen process.