Hacking Blue Screen (BOOTROM 8046) Brick From HardMod

[BanditBat]

Hello! Basically I soldered the wires to the proper contacts, booted up my N3DSXL, and all was AOK until I decided to open the device back up to re-arrange the wiring. While doing this, the TINY CLK contact came up, and I was greeted with the Blue Screen brick once I tried booting again.

I used a silver pen and neatly replaced the contact point, however I'm still getting a blue screen. Is there any way I can fix this?

Thank you.

EDIT:

I fixed the problem by exposing the traces and using THIS silver pen to draw in the connection. I then used the alternate CLK point for the hardmod (found in several places on this board). If need be I can upload photos of the silver contact I made.

 

[hobbledehoy899]

all was AOK until I decided to open the device back up to re-arrange the wiring.

I decided to open the device back up to re-arrange the wiring.

re-arrange the wiring.

Why? For what purpose?

 

[zoogie]

Why? For what purpose?

WHAT?! It actually matters which wires go where?

 

[BanditBat]

Why? For what purpose?

The state of the wires prevented full closure of the device. So I had to reroute them.

 

[Urbanshadow]

I'm afraid we would need more info and some photos to assist.
First, I would like to know the system model.
Then, I would like you to write down the bootrom error in its entirety, specially the hex numbers:

BOOTROM 8046:
    A           B
    C           D

We possibly can't figure anything from there, but try. Then I would like you to make some photos of the soldering points
in the motherboard and in the SD. Make sure they are clear, definite and with the soldering points in the center.

We possibly can check what went wrong there.

 

[hobbledehoy899]

The state of the wires prevented full closure of the device. So I had to reroute them.

Oh...

 

[leerz]

yea, this sht happened to one of my n3dsxl units that I have, no wires no nothing, no bridged joints.
the clk was mangled. disconnected the line from the clk to the nand itself.

 

[JCR1]

yea, this sht happened to one of my n3dsxl units that I have, no wires no nothing, no bridged joints.
the clk was mangled. disconnected the line from the clk to the nand itself.

Same to me, the line of dat0 disconnected on new3ds(non xl) and blue screen without wires, was very hard join the tiny line again but worked, boot normally.

 

[leerz]

Same to me, the line of dat0 disconnected on new3ds(non xl) and blue screen without wires, was very hard join the tiny line again but worked, boot normally.

it wasn't my shty work (maiming the line), but i fixed it lol. man those little traces are a bch to scrape of the copper. I slopped some epoxy to make it strong with a lead protruding for future use.

 

[BanditBat]

it wasn't my shty work (maiming the line), but i fixed it lol. man those little traces are a bch to scrape of the copper. I slopped some epoxy to make it strong with a lead protruding for future use.

Did you get a blue screen brick when this happened? Did it go away when you fixed the connection?

EDIT:
GOOD LORD I FIXED IT!!! I thought my 3ds was permanently dead

Edits will be made to OP in case anyone runs into this issue.

 

[leerz]

Did you get a blue screen brick when this happened? Did it go away when you fixed the connection?

EDIT:
GOOD LORD I FIXED IT!!! I thought my 3ds was permanently dead

Edits will be made to OP in case anyone runs into this issue.

absolutely yes

 

[xxturtlederpxx]

Did you get a blue screen brick when this happened? Did it go away when you fixed the connection?

EDIT:
GOOD LORD I FIXED IT!!! I thought my 3ds was permanently dead

Edits will be made to OP in case anyone runs into this issue.

i am having the problem on a 2ds. the clk pad came off and i got to the copper by scraping the plastic off with a x-acto knife

Edit: Nevermind this was supposed to happen because i am hardmodding.