Hacking Bricked n2dsxl

[MineSweeper]

Hey guys, I very recently got a n2dsxl and installed cfw on it successfully. I think I had it all of 2 days before I bricked it. Woo.

Anyways, the symptoms:

• blank screen on boot
• no audio
• safe mode does not work
• blue persistent power on light

Things I have tried:

• Restoring the NAND from a backup
• CTRTransfer
• Leaving the system on for 30 minutes
• Using a different SD card and then restoring NAND/CTR

Restoring from a backup and the CTRTransfer method both allowed me to boot up the system into the home screen, but when I turn the system off and back on again it goes back to a blank screen. Does anyone know what may be causing this and how I might solve the problem?

 

[Quantumcat]

@TurdPooCharger

 

[TurdPooCharger]

The great @Quantumcat has summoned me?! I'm honored.

I've been following this thread to see what you guys offer first in ideas up front. His brick(ish) is indeed a strange one.

As always, (probably some are tired of seeing this), try removing & reinserting battery and booting without an SD card.

 

[tedmg091309131]

You said that booting after a nand backup or a ctr transfer made the n2dsxl work normally. Have you tried to factory reset the n2dsxl immediately?

 

[The Catboy]

I've seen something like before when my old3DS's wireless card was loose. I was able to boot into the A9LH payloads and even restore a NAND backup and everything, but I couldn't boot into the home menu. I fixed my issue by simply opening the system, cleaning the contacts, and firmly pressing the chip back into place.

 

[TurdPooCharger]

@Lilith Valentine , New 2DS XL got WiFi baked on motherboard. However, this doesn't rule out wifi or hardware failure of a different cause.

Oo, @MineSweeper , try using a strong magnet and go at it with that sleep switch like your namesake.

 

[The Catboy]

@Lilith Valentine , New 2DS XL got WiFi baked on motherboard. However, this doesn't rule out wifi or hardware failure of a different cause.

Looks like I am not buying a 2DSXL.
Still hardware failure sounds like the possible issue. B9S boots long before most hardware even has time to start. So as long as the bootrom isn't effected, B9S payloads will still work. This was what I found to be the case with A9LH when dealing with hardware issues.
Although with my case I wasn't even able to boot into the homemenu whatsoever, even after different methods of restoring the system. I was only able to boot into the system by fixing the hardware. It could be possible that something is loose in the system and that it's just making enough contact allowing the system to occasionally boot. Still this would be an issue that I would personally have to open the system and test every chip/solder point to see if they are damaged or loose.