Homebrew Broken New 2DS

[Craftyawesome]

I currently get a blackscreen when trying to boot normally. What concerns me more is that in luma config or other custom firm files, the top screen is corrupted. It was last used to play non-homebrew games.


Notable(?) things:
Letting go of select while luma config is up will cause the bottom screen to go black.
Letting go of start will dim the brightness in gm9, regardless of the volume slider position
The home button doesn't work in gm9, leaving me unable to use scripts
EDIT: One time gm9 flickered between bright and dark for a couple seconds and I was able to use the home button
EDIT2: Attempting to shut off in gm9 freezes, but it still may shut off seconds after boot, before you get a chance.
it often just shuts off in custom firms (I don't recall avoiding force power off while booting normally, but I may be mistaken)

I have tried:
Booting without sd card: no difference other than not being able to boot gm9
Reinstalling/updating b9s: no difference
Charging/leaving it plugged in

I have not tried removing home menu extdata using the script or removing it off the sd card, due to the issue with the gm9 menu and there being no difference without the sd card.
I hope this isn't hardware failure, though would appreciate any tips if it is one.
also the message while typing this still says use al9h lol

 

[TyDye]

I currently get a blackscreen when trying to boot normally. What concerns me more is that in luma config or other custom firm files, the top screen is corrupted. It was last used to play non-homebrew games.


Notable(?) things:
Letting go of select while luma config is up will cause the bottom screen to go black.
Letting go of start will dim the brightness in gm9, regardless of the volume slider position
The home button doesn't work in gm9, leaving me unable to use scripts
it often just shuts off in custom firms (I don't recall avoiding force power off while booting normally, but I may be mistaken)

I have tried:
Booting without sd card: no difference other than not being able to boot gm9
Reinstalling/updating b9s: no difference
Charging/leaving it plugged in

I have not tried removing home menu extdata using the script or removing it off the sd card, due to the issue with the gm9 menu and there being no difference without the sd card.
I hope this isn't hardware failure, though would appreciate any tips if it is one.
also the message while typing this still says use al9h lol

hmmmm, do you have a NAND backup?

 

[TurdPooCharger]

Can you verify if this is a piece of hair or crack in the glass screen?

Spoiler: Top Screen Visual Inspection

I'm not familiar with this (Select) loader. This doesn't look like Luma3DS Configuration.

Spoiler: Is this 'Fastboot3DS' ????

 

[lAkdaOpeKA]

Can you verify if this is a piece of hair or crack in the glass screen?

Spoiler: Top Screen Visual Inspection

I'm not familiar with this (Select) loader. This doesn't look like Luma3DS Configuration.

Spoiler: Is this 'Fastboot3DS' ????

Yes that is the Luma3DS configuration screen

 

[TurdPooCharger]

Yes that is the Luma3DS configuration screen

OHHhh... I'm so used to seeing the top screen. lol.

 

[Craftyawesome]

hmmmm, do you have a NAND backup?

I have one, but it seems rtc wasn't set so it says it was from 2005 and I don't remember when it really was. I'm also not sure a bad nand would affect gm9 or Luma config in this way.

Can you verify if this is a piece of hair or crack in the glass screen?

Spoiler: Top Screen Visual Inspection

It is a hair. The only visual imperfection I see when off is scratches on the bottom of the system.

 

[TurdPooCharger]

I have one, but it seems rtc wasn't set so it says it was from 2005 and I don't remember when it really was. I'm also not sure a bad nand would affect gm9 or Luma config in this way.


It is a hair. The only visual imperfection I see when off is scratches on the bottom of the system.

See if this helps.

1. Remove and reinsert your battery to reset RAM memory.
2. Copy everything off your SD card onto computer, and reformat it as FAT32 + 32 KB cluster size. You'll need guiformat if the card is bigger than 32 GB.
3. In case you've never done so before, do a Full Write + Verify Test using H2testw. You'll want to ensure your card is free of hardware defects.
4. Go to my post here and extract the files within that archive to build a test CFW setup. Other than a backed up SysNAND image *.bin if you have one, do not use any of your files for the time being.
5. Check if you can boot into HOME Menu, GodMode9, Luma3DS configuration, and/or Recovery Mode.
6. If you're able to access GodMode9, do both SysNAND Restore (Safe) and Setup Luma3DS to CTRNAND.
7. If you don't have a backed up NAND image, you'll need to resort to CTRTransfer.

***

In case the above steps failed on you. I would like you to answer some questions.

Where do you mainly acquire your non-homebrew *.cia from? Please don't directly name those websites due to forum rules.
If it wasn't acquired through torrent, describe how those websites look or vaguely reference their web addresses.

Example Descriptions: that iso site, that title site, Voldemort eShop clone, evil doge desktop app, that cia site

Your issue is so strange, I'm almost inclined to believe someone purposely hid a specialized 3DS virus into your *.cia that infected your n2DSXL.

• Cracked screens usually have vertical lines. Your's isn't crack as far as you can tell, and the top display is rendering horizontal dead bar almost too inconveniently.
  
• You have disabled and severally handicapped buttons such as HOME, Select, and Start.
• Can't boot into or properly navigate in Luma3DS configuration, GodMode9, Recovery Mode, HOME Menu, etc.

If the problem isn't hardware related, all of those combined behaviors suggest malicious software.


I hope I'm dead wrong on my assessment because the idea of 3DS malware and virus can F-off... But should something similar like this crops up again, the community should stay aware.

 

[lAkdaOpeKA]

See if this helps.

1. Remove and reinsert your battery to reset RAM memory.
2. Copy everything off your SD card onto computer, and reformat it as FAT32 + 32 KB cluster size. You'll need guiformat if the card is bigger than 32 GB.
3. In case you've never done so before, do a Full Write + Verify Test using H2testw. You'll want to ensure your card is free of hardware defects.
4. Go to my post here and extract the files within that archive to build a test CFW setup. Other than a backed up SysNAND image *.bin if you have one, do not use any of your files for the time being.
5. Check if you can boot into HOME Menu, GodMode9, Luma3DS configuration, and/or Recovery Mode.
6. If you're able to access GodMode9, do both SysNAND Restore (Safe) and Setup Luma3DS to CTRNAND.
7. If you don't have a backed up name, you'll need to resort to CTRTransfer.

***

In case the above steps failed on you. I would you to answer some questions.

Where do you mainly acquire your non-homebrew *.cia from? Please don't directly name those websites due to forum rules.
If it wasn't acquired through torrent, describe how those websites look or vaguely reference their web addresses.

Example Descriptions: that iso site, that title site, Voldemort eShop clone, evil doge desktop app, that cia site

Your issue is so strange, I'm almost inclined to believe someone purposely hid a specialized 3DS virus into your *.cia that infected your n2DSXL.

• Cracked screens usually have vertical lines. Your's isn't crack as far as you can tell, and the top display is rendering horizontal dead bar almost too inconveniently.
  
• You have disabled and severally handicapped buttons such as HOME, Select, and Start.
• Can't boot into or properly navigate in Luma3DS configuration, GodMode9, Recovery Mode, HOME Menu, etc.

If the problem isn't hardware related, all of those combined behaviors suggest malicious software.


I hope I'm dead wrong on my assessment because the idea of 3DS malware and virus can F-off... But should something similar like this crops up again, the community should stay aware.

freeShop and Villain3DS are allowed to be named on this forum, I mean there are even the official threads here

 

[TurdPooCharger]

freeShop and Villain3DS are allowed to be named on this forum, I mean there are even the official threads here

There was an influx of reddit users who were following their sub-reddit rules here. While I'm flexible with using their names, I played it off naming them as a joke.

• PSA: You can mention the name of freeShop on GBAtemp.

I just want @Craftyawesome to know how to correctly go about telling us where he came across those *.cia files.

 

[Craftyawesome]

See if this helps.

1. Remove and reinsert your battery to reset RAM memory.
2. Copy everything off your SD card onto computer, and reformat it as FAT32 + 32 KB cluster size. You'll need guiformat if the card is bigger than 32 GB.
3. In case you've never done so before, do a Full Write + Verify Test using H2testw. You'll want to ensure your card is free of hardware defects.
4. Go to my post here and extract the files within that archive to build a test CFW setup. Other than a backed up SysNAND image *.bin if you have one, do not use any of your files for the time being.
5. Check if you can boot into HOME Menu, GodMode9, Luma3DS configuration, and/or Recovery Mode.
6. If you're able to access GodMode9, do both SysNAND Restore (Safe) and Setup Luma3DS to CTRNAND.
7. If you don't have a backed up NAND image, you'll need to resort to CTRTransfer.

Did not follow 1, because the new 2ds needs a tri-wing to do that. h2testw had no errors. There was no difference, so I wasn't able to do 5-7.

Where do you mainly acquire your non-homebrew *.cia from? Please don't directly name those websites due to forum rules.
If it wasn't acquired through torrent, describe how those websites look or vaguely reference their web addresses.

This 2ds mostly just has the recommended homebrew from 3ds.guide, other than bootntr and the "Voldemort eShop Clone".

• Cracked screens usually have vertical lines. Your's isn't crack as far as you can tell, and the top display is rendering horizontal dead bar almost too inconveniently.

I don't see any cracks, but there does seem to be vertical lines. It seems to be much more profound than when I recorded the video. I also once got vertical lines below the area I normally get glitched graphics, but it shut off before I could get a picture.
https://imgur.com/a/WbKOZnx

• You have disabled and severally handicapped buttons such as HOME, Select, and Start.
• Can't boot into or properly navigate in Luma3DS configuration, GodMode9, Recovery Mode, HOME Menu, etc.

I'm not sure if you saw the edit, but once gm9 was flickering between the bright and dark and I was able to use the home button. I didn't think to do anything with it and was unable to reproduce.

 

[TurdPooCharger]

Did not follow 1, because the new 2ds needs a tri-wing to do that. h2testw had no errors. There was no difference, so I wasn't able to do 5-7.

This 2ds mostly just has the recommended homebrew from 3ds.guide, other than bootntr and the "Voldemort eShop Clone".

I don't see any cracks, but there does seem to be vertical lines. It seems to be much more profound than when I recorded the video. I also once got vertical lines below the area I normally get glitched graphics, but it shut off before I could get a picture.
https://imgur.com/a/WbKOZnx

I'm not sure if you saw the edit, but once gm9 was flickering between the bright and dark and I was able to use the home button. I didn't think to do anything with it and was unable to reproduce.

There's a way to unscrew tri-wing screws with a flathead screw driver. The width needs to be long enough to span two grooves. This is if you wish to pursue the battery removal trick. To avoid damaging the top screen when opening the bottom cover, flip the clam shell fully open and lay the inner bottom screen on a towel for cushioning. The n2DSXL upper LCD has terrible durability, so avoid applying pressure on it when unscrewing the cover.

If disassembling is much too risky, you can substitute battery removal and reinsertion by keeping the n2DSXL turned on until the battery drains empty. After it shuts off, press and hold the power button several times to check if the LEDs flash or turn on. When there's no further signs of life comes on, let the n2DSXL sit for another several hours while checking throughout the day (I recommend 6 hours to one day). After you're fairly sure there's no more juice left, go ahead and recharge it and check again.

***

You mentioned that you reinstalled boot9strap. Was this done through a ntrboot flashcart? Can you verify that the top screen still displays correctly when doing ntrboot? If that's the case, we can rule out your top LCD as being bad.

I can't think of another cause to your problem other than some sort of hardware failure. Most likely suspect is that the PICA200 GPU prematurely failed, despite having a relatively new system (manufacture defect?). This could explain for the glitchy image output, but not the disabled buttons unless these were affected by knock on effects by the failed GPU.

Your issue is so strange and atypical, it might be the first of its kind, at least for a n2DSXL at this point in time. I'm not sure if it can be fixed and how. If it's still under the 1 year warranty, you may need to refer to Nintendo customer support.

If they do decide to take yours in and fix it, I recommend backing up your games and saves, selling off the n2DSXL, and buying a replacement n3DSXL (you might be able to snag a $150 SNES Edition if Amazon discount sale comes back again). The cost cutting measures that went into manufacturing this model is IMO, one of the worst products made by Nintendo.

 

[Craftyawesome]

You mentioned that you reinstalled boot9strap. Was this done through a ntrboot flashcart? Can you verify that the top screen still displays correctly when doing ntrboot? If that's the case, we can rule out your top LCD as being bad.

It was reinstalled via the upgrading b9s method in 3ds.guide. (the button combo is predetermined, so I was able to do it with the top screen as it is.

However, I do have a ntrboot cart. I booted Luma with it

Spoiler

Does this mean it is definitely a hardware failure?

 

[Itzumi]

There's a way to unscrew tri-wing screws with a flathead screw driver. The width needs to be long enough to span two grooves. This is if you wish to pursue the battery removal trick. To avoid damaging the top screen when opening the bottom cover, flip the clam shell fully open and lay the inner bottom screen on a towel for cushioning. The n2DSXL upper LCD has terrible durability, so avoid applying pressure on it when unscrewing the cover.

If disassembling is much too risky, you can substitute battery removal and reinsertion by keeping the n2DSXL turned on until the battery drains empty. After it shuts off, press and hold the power button several times to check if the LEDs flash or turn on. When there's no further signs of life comes on, let the n2DSXL sit for another several hours while checking throughout the day (I recommend 6 hours to one day). After you're fairly sure there's no more juice left, go ahead and recharge it and check again.

***

You mentioned that you reinstalled boot9strap. Was this done through a ntrboot flashcart? Can you verify that the top screen still displays correctly when doing ntrboot? If that's the case, we can rule out your top LCD as being bad.

I can't think of another cause to your problem other than some sort of hardware failure. Most likely suspect is that the PICA200 GPU prematurely failed, despite having a relatively new system (manufacture defect?). This could explain for the glitchy image output, but not the disabled buttons unless these were affected by knock on effects by the failed GPU.

Your issue is so strange and atypical, it might be the first of its kind, at least for a n2DSXL at this point in time. I'm not sure if it can be fixed and how. If it's still under the 1 year warranty, you may need to refer to Nintendo customer support.

If they do decide to take yours in and fix it, I recommend backing up your games and saves, selling off the n2DSXL, and buying a replacement n3DSXL (you might be able to snag a $150 SNES Edition if Amazon discount sale comes back again). The cost cutting measures that went into manufacturing this model is IMO, one of the worst products made by Nintendo.

what cost cutting measures

 

[TurdPooCharger]

It was reinstalled via the upgrading b9s method in 3ds.guide. (the button combo is predetermined, so I was able to do it with the top screen as it is.

However, I do have a ntrboot cart. I booted Luma with it

Does this mean it is definitely a hardware failure?

I'm afraid so.

If it's the PICA200 gpu is not at fault, your top LCD may been damaged either by the flex cable (from bending stress at the hinge) or developed a tiny, non-visible crack.

The n2DSXL has little stiffness support for that top lid. Any twisting or pressure could have damaged the LCD glass. This would usually be obvious with signs of black liquid spillage, but this isn't always obvious...

You can try attempting DIY repairs in replacing that top LCD if it's found to be broken. A replacement LCD costs about +$25 on aliexpress and eBay. You have a high chance of breaking the front outer glass panel when removing that LCD because Nintendo pulled an Apple in heavily gluing/adhesiving it.

Not much of a repair guide, but ifixit has a n2DSXL teardown video.

Check first with Nintendo if warranty work is still available to you. If they refuse to honor warranty, don't mess with repairs if you can afford to sell your's off your parts.

If you attempt DIY repair, try the battery removal and reinsertion first and check again before going any further. Sorry for the mishap and good luck!

what cost cutting measures

I'm a mechanical engineer, but I rather not go on a publicly long rant about my misgivings for the n2DSXL. Let's just say I have some nice things to say about it, like it's better located HOME button and ergonomic ZL & ZR shoulder buttons.

As for the not so nice things... Well.