Hacking N3DS BLACK SCREEN BLUE LIGHT AND WIFI LIGHT

[Voodood]

Would you know if the console was previously hacked or was it not?

sorry i dont know this.
i have insalled CFW on other 3ds and i have other 3ds in my house running CFW

 

[Voodood]

sorry i dont know this.
i have insalled CFW on other 3ds and i have other 3ds in my house running CFW

im been told its not been hacked before.

 

[TurdPooCharger]

im been told its not been hacked before.

Late reply. Not hacked, eh?

I'm a little wary giving the go ahead in disassembling this n3DS in case there's an off chance this is actually a software brick. The most likely way an unhacked 3DS system on open firmware can softbrick is from a failed system update resulting in an frankenfirm (ie, mismatch of old & new versions of system titles or incomplete download+install).

The only way to fix a frankenfirm would to be hacked that n3DS by ntrboot method with an ntrboot compatible DS flashcart like the R4i Gold 3DS Plus. Once you're able to gain access to GodMode9, fixing that 3DS firmware might require CTRTransfer (Type D9). This is with the assumption the ctrnand partition's FAT16 file system is severely corrupted like those of more worse frankenfirm bricks.

If that alternative CTRTransfer does not fix this brick, you can reverse the process with the backed up SysNAND *.bin image made from step 8 in the Instructions.

• Restoring a NAND Backup

Another reason to be wary about going straight into disassembling the n3DS without first exhausting all software repair options before reaching the conclusion it's a hardware fault is that there's a risk inadvertently damaging the delicate internals like the flexible cables and connectors. Basically, have a really good reason or diagnosis in the first place as to why you have to open up that 3DS. Again as was alluded from this thread that was pointed out several times, this particular brick is fixed by either replacing or disconnecting the camera flex cable assembly.