Hacking Homebrew Homebrewed 3DS won't turn on anymore

[bleached]

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

 

[SonyUSA]

See if you can boot it into NTR mode then maybe redo hacks

 

[bleached]

See if you can boot it into NTR mode then maybe redo hacks

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: Sep 1, 2024

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

 

[Kwyjor]

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.

https://github.com/SciresM/boot9strap/releases

SD FIRM missing, CTRNAND FIRM corrupt: magenta
SD FIRM corrupt, CTRNAND FIRM also corrupt: red

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?

 

[KleinesSinchen]

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

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.

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?

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.

 

[SonyUSA]

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.

This is what I meant, try and boot it with NTR cart and see what it does.

 

[bleached]

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.

Depressing, guess there's nothing left I can try. Out of desperation I tried a bunch of different fixes, but all I managed was to get it to launch up one time, but it immediately had an error and crashed. Any other time I was able to get it to start had an error as well. Guess I gotta just give up on it. So replacing the motherboard of the 3DS would be a cheaper solution than just buying a whole new one, right? Any places to buy a reliable motherboard to replace it with? Also, would I be able to use the SD card on my current broken 3DS to bring my data over, or no?

 

[KleinesSinchen]

There are a few things to try. Having the console warm or cold (danger of condensation), gently pressing down on the memory chip while booting.

If any of these show an effect it would give a hint in the direction of cracked solder joints.
========

Everything inside the Nintendo 3DS folder is encrypted with your movable.sed -- decrypted stuff like Checkpoint backups can be restored on another console.

I can't help you regarding where to buy motherboards.

 

[bleached]

I've been able to get the 3DS (sometimes) past the red light and not turning on whatsoever, but it still boots up to an error. I've been slightly taking off the back casing, holding it at strange angles, and sometimes it will power on and shows my splash that I have set (Which I guess I might as well add the 3ds broke later in the day that I installed my first splash, could be useless info but maybe some troubleshooting possibilities there) but after showing the splash, it results in this error screen:

 

[lone_wolf323]

I've been able to get the 3DS (sometimes) past the red light and not turning on whatsoever, but it still boots up to an error. I've been slightly taking off the back casing, holding it at strange angles, and sometimes it will power on and shows my splash that I have set (Which I guess I might as well add the 3ds broke later in the day that I installed my first splash, could be useless info but maybe some troubleshooting possibilities there) but after showing the splash, it results in this error screen:

Have you tried using a new different sd card? that error seems to show with bad sd cards that i have seen

 

[bleached]

Have you tried using a new different sd card? that error seems to show with bad sd cards that i have seen

I know I have another SD card laying around, but I'm struggling to find it. Just out of curiosity when I do, should I try a completely empty SD card, or install the newest version of Luma, or move everything over?

 

[Kwyjor]

Just out of curiosity when I do, should I try a completely empty SD card, or install the newest version of Luma, or move everything over?

Start with just the latest boot.firm; if that works, you can worry about copying other stuff over.

 

[bleached]

Well I didn't really get to try a new SD card, because as of last night, it has begun working normally again. I've played games, been able to turn it off and on again, with absolutely no issue, so I suppose my issue is fixed? I really didn't do anything other than not use it at all for ~2 days, so I'm not sure how it began working again. Hope it stays this way though.

 

[Tofu_mommy]

If it behaves like that, could it just be something to do with capacitors on the motherboard? Please post here if it suddenly stops working again.

 

[djbusx]

I’m in the same boat as OP. I just wrote a lengthy reply but I don’t think it posted since I wasn’t logged in right.

Should I start a new thread or add to here? TIA

 

[Kwyjor]

I’m in the same boat as OP.

I hope you already read the other posts in this thread.

Should I start a new thread or add to here?

That depends on how sure you are about being in the same boat.

 

[djbusx]

Absolutely. I’m coming across a system with a red notification light like OP stated. Read every comment in here and have been doing various tests for the past couple days.

Since I’m new here I’m limited on what I can write. Had to delete my in-depth response. Weird system. Not sure what in my reply is being marked as spam or inappropriate language.

 

[Kwyjor]

Not sure what in my reply is being marked as spam or inappropriate language.

The usual strategy in cases like this is to delete portions one by one until you figure out what you're allowed to post.

But to take a wild guess, you might be trying to post a link.

 

[djbusx]

Still being flagged and can't PM.. so maybe an screen shot will work?

 

[lone_wolf323]

Still being flagged and can't PM.. so maybe an screen shot will work?
View attachment 462265

that last sentence is bullshit. winrar, 7zip, are all better than the shit that your pcs built in extractor is capable of.