My CFW Homebrew 3DS had been working fine with absolutely no issue at all, until today. My 3DS was powered off, and when I went to power it on, the blue light at the bottom turns on, but the light next to the right shoulder button lights up red (as shown in image). The lights then go out after a few seconds, the screen remaining completely black the whole time. I read online there could be issues with the SD card, so I tried removing the SD card, and it does the same exact thing, with the top right light turning purpleish instead of red, still not turning on whatsoever. I've tried replacing the boot.firm file with the newest version, but it hasn't changed anything whatsoever. Is my console bricked? Not really sure how to fix this problem
I'm not really sure what NTR mode is, so I looked it up, and it said I'd have to install it as a CIA? Sorry, I've never heard of NTR, how would I install/use that if I can't turn on the 3ds?
Post automatically merged:
I ran the HW Test on my 3ds, and it came up with an absurd number of errors, 1 million something errors detected. Does that mean it's guaranteed broken with no fix besides buying a new one or replacing the motherboard? any chance the test could be wrong? The number seems pretty unreal
Last edited by bleached,
https://github.com/SciresM/boot9strap/releases
So yes, there's something wrong with your SD card, and there's something wrong with the rest of your system too.
How did you run HW Test?
That is not unusual. If a memory chip fails or can't be properly reached the check might show a very high number of errors. We've had such cases on the forum before. Luma3DS boot.firm can't be loaded (detected as corrupt with red LED), but hardware test still loads.
As far as I know the check is based on Memtest86 -- and high numbers can occur on the PC platform as well when RAM goes bad (or doesn't work correctly when getting warm).
This shows there is probably nothing wrong with the SD, but the system as such. It would need somebody with knowledge in electronics troubleshooting to pinpoint the issue. I wish somebody would do this: Most people are just going to take the "replace device" route, which is obviously finite. And since this is not the first time something like this happens we'll most likely see that happen more often.
This is sadly not going to help. There is nothing called NTR mode anyway. There is a "TWL mode" (TWL_FIRM) and there is ntrboot, which means starting a FIRM from a special NTR cartridge. The latter is helpful on software damage/softbrick but it won't magically repair failing hardware.
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
@
Psionic Roshambo:
The end credits of that episode.... Just the names scrolling Hank says "It's so juicy!' and then Bobby kind of whimpers it's really weird lol -
-
-
-
-
-
-
-
-
-
-
-
-
@
ShantaeFan123:
i killed my og HDD all because of "curiosity" and stupidity so i had to get a new one -
-
-
-
-
-
