Hacking Bad customer NAND Hardware MOD (console just display blue screen now)

[mvmiranda]

Hello fellow modders,

I received a customer's 3DS xl 4.4 with a regular blue screen error resulted from a gateway tempered launcher brick.

The customer tried to do the NAND HW mod himself and ripped off the DAT0 pad.

Spoiler

It turns out that this pad is connected to a resistor array through a connecting track and it was ripped off too.

Spoiler

Red: ripped pad and track
Green: what's left of the track

I did a wire jumper between what's left of the trace leading to bellow the NAND and the array pin corresponding to the trace without much luck!

Spoiler

I scraped the trace carefully with a fiberglass pen paying attention to not scrap other traces to cause short.
Looked with a magnifying glass and everything looks cool.

The console still gives me a blue screen error.

Spoiler

Error message:

I wonder what else I might be missing or if the resistor array is screwed up.

Reading and writing to the NAND works perfectly. I wrote the NAND.bin, extracted it again, compared to the one I wrote and the MD5s matched.

Any clues?

EDIT:
The blue error message appears after 5 seconds.
A "regular" flashcart brick give us "instant" blue screen. You turn it on and the error message pops up immediately.

 

[andre104623]

That's what happend when my r4i deluxe version 3.3 bricked my 3ds xl and I tried to fix it myself I have good soldering skills but that doesn't matter when I dropped the mobo when I had it plugged in to the pi. I also ripped the pads off so I give up I still have everything. I was going to buy a mobo off ebay but never got a chance

 

[st4rk]

There is a documentation about ErrCode in BootLoader with NAND Loading here: http://3dbrew.org/wiki/Bootloader

Looking for you error it look like the first but with 00400000.
(Deixe me ver se entendi bem, o cliente raspou as trilhas da PCB ? ._. )

 

[mvmiranda]

There is a documentation about ErrCode in BootLoader with NAND Loading here: http://3dbrew.org/wiki/Bootloader

Looking for you error it look like the first but with 00400000.
(Deixe me ver se entendi bem, o cliente raspou as trilhas da PCB ? ._. )

Hey st4rk,
"Deixe me ver se entendi bem, o cliente raspou as trilhas da PCB ?"
You asked if the customer scrapped the trace... nope I did the that... veeeeery carefully and then looked with a magnifying glass. no shorts
The NAND inside the console isn't "locked" by the brick. I've just confirmed by wiring the the SD cable and using my RaspberryPi.

Yet, only I get is a blue screen error code.

 

[st4rk]

Hey st4rk,
"Deixe me ver se entendi bem, o cliente raspou as trilhas da PCB ?"
You asked if the customer scrapped the trace... nope I did the that... veeeeery carefully and then looked with a magnifying glass. no shorts
The NAND inside the console isn't "locked" by the brick. I've just confirmed by wiring the the SD cable and using my RaspberryPi.

Yet, only I get is a blue screen error code.

Very weird, never seen this ErrCode before, i will send PM to you.

 

[loco365]

I'm thinking that the removal of that pad is perhaps preventing something else from reading properly. That's my educated guess for the day.

 

[mvmiranda]

I was looking at the resistor array with a magnifier glass and ***maybe*** the res array pin cracked and went off...
can I just solder another resistor to "do the work of that one?

Plus, any clues on that resistor value?

 

[Deleted-355425]

I was looking at the resistor array with a magnifier glass and ***maybe*** the res array pin cracked and went off...
can I just solder another resistor to "do the work of that one?

Plus, any clues on that resistor value?

100r