Did I bricked the 3DS with the hard mod?

Discussion in '3DS - Console, Accessories and Hardware' started by CoolAlpha, Dec 5, 2016.

  1. CoolAlpha
    OP

    CoolAlpha GBAtemp Regular

    Member
    109
    23
    Jan 21, 2015
    Hello,
    yesterday I tried to hardmod one o3ds but the card reader was unable to read the NAND.
    I was getting the 00F800FE 00000000 00000000 00000400 00000000 error code but my PC was not able to recognize the NAND.

    I already made 3 hardmods (eur consoles) with that reader, but maybe the NAND type also influence the reader?
    All previous were Toshiba, maybe this one is Samsung (usa console).

    The bad thing is that I removed the wires and reassembled the 3ds but it still shows the blue screen with the 00F800FE 00000000 00000000 00000400 00000000 error.
    Is possible that I bricked the 3ds?
    I have not written any file to the memory, maybe some of the left pads (dat0/cmd) make a short with a board?
     
  2. mashers

    mashers Stubborn ape

    Member
    3,837
    5,157
    Jun 10, 2015
    Kongo Jungle
    Does the blue screen error show even if the SD card reader isn't attached to the 3DS when it boots?
     
  3. CoolAlpha
    OP

    CoolAlpha GBAtemp Regular

    Member
    109
    23
    Jan 21, 2015
    Yes, i removed the wires, but left the pads.
    But I was wondering if is possible because some short of some pad with the board?
     
  4. mashers

    mashers Stubborn ape

    Member
    3,837
    5,157
    Jun 10, 2015
    Kongo Jungle
    Yes. If the blue screen error shows even with the hardmod wires removed, then you have damaged the board in some way. Either a short, a damaged trace, a burned component, a lifted pad... there are numerous possibilities really. If possible, upload some high resolution photos of the board so your work can be examined for faults or damage.
     
  5. CoolAlpha
    OP

    CoolAlpha GBAtemp Regular

    Member
    109
    23
    Jan 21, 2015
    Thanks for the reply, I'll do it after work when I find some free time
     
  6. mashers

    mashers Stubborn ape

    Member
    3,837
    5,157
    Jun 10, 2015
    Kongo Jungle
    No problem :)
     
  7. Dennis G

    Dennis G GBAtemp Advanced Fan

    Member
    671
    205
    Jan 4, 2016
    Netherlands
    you're right about the samsung/thoshiba, i had a EU console and it had toshiba, and my US motherboard has samsung and yes indeed, some readers can read the one but not the other, that's why i recommend the anker 3.0 reader always because it's pretty cheap and read's them all, but sucks that you probably fried it :s
     
    CoolAlpha likes this.
  8. CoolAlpha
    OP

    CoolAlpha GBAtemp Regular

    Member
    109
    23
    Jan 21, 2015
    OK, I found time to clean the pads, cleaned GND, CMD and DAT0, still blue screen, cleaned the CLK and the 3DS booted :)
    I scratched a bit of the board while trying to clean the point with a scalpel and I bridged it.
    I'll try again on weekend with the natural light
    before
    after
     
  9. CoolAlpha
    OP

    CoolAlpha GBAtemp Regular

    Member
    109
    23
    Jan 21, 2015
    OK, I resoldered the wires,
    but instead of
    00000200 00000000
    I got the error
    00000002 00000000

    I read the memory and the dump is of the correct size and it contains the NCSD string at offset 0x100
    The reading was pretty slow, 0.68 MB/s
    Am I safe to write the patched nand?
     
  10. Dennis G

    Dennis G GBAtemp Advanced Fan

    Member
    671
    205
    Jan 4, 2016
    Netherlands
    sounds good, but keep a backup of the original nand, you'll always be able to re-write to the nand with hard mods so you can't really mess up with faulty writes as long you have a good valid original nand restore.
     
    CoolAlpha likes this.
  11. CoolAlpha
    OP

    CoolAlpha GBAtemp Regular

    Member
    109
    23
    Jan 21, 2015
    OK, I made it, just to notify that the error 00000002 00000000 is also fine as long as the dump is valid