1. acho

    OP acho Advanced Member
    Newcomer

    Joined:
    Apr 27, 2007
    Messages:
    55
    Country:
    Indonesia
    I have a bricked old 3ds that's just been lying for a long time. Its been too long I could not remember exactly what happened to it. It had something to do with Gateway, maybe I accidentally updated the firmware of sysnand/emunand through settings. NAND backup can no longer be found.

    Decided to give it a try and bring it back to life with this guide https://gbatemp.net/threads/tutoria...ping-2ds-3ds-3ds-xl-n3ds-n3ds-xl.414498/#o3ds. I used Transcend P8 TS-RDP8K : ALCOR AU6476 reader and frankensd. Plugging the reader and frankensd through a reader to my windows 10 pc did not prompt anything. On win32diskimager, I could not click on anything, no device can be selected.

    Got the blue screen but only at the bottom screen (not sure what happened to the top screen) with this error
    Bootrom 8046
    ERRCODE: 00FE00FE
    00000000 00000000
    00000400 00000000

    I have attached some photos of the soldering. Any advice on what to do next? Thanks. Much appreciated.
     

    Attached Files:

  2. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    7,292
    Country:
    United States
    This error code means that the NAND chip (eMMC) has hardbricked or fried.

    Code:
    BOOTROM 8046
    ERRCODE: 00FE00FE
             00000000 00000000
             00000400 00000000

    While it's possible to replace the NAND chip, it's not generally feasible or cost effective.

    Salvage the rest of the o3DS by replacing the motherboard.
     
    E1ite007 and alexander1970 like this.
  3. BaamAlex

    BaamAlex S̶̥͝l̷̹̀͗e̶̼̖̩̅͊e̷̛̦͉̦p̷̘͌͝i̵͇̠̞̿̌n̷̰͚͌̓͝g̷̦̲̍̆͝
    Member

    Joined:
    Jul 23, 2018
    Messages:
    3,864
    Country:
    Germany
    If not the hardware is broken/destroyed, ntrboot should fix this. Or am i completely wrong? Dumping or restoring a nand backup is not needed because we have ntrboot.
     
  4. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    7,292
    Country:
    United States
    @acho has the hardware bricked variety of bootrom 8046. ntrboot can't fix this.
    His hardmod workmanship is very shoddy: wire gage is too big, cross wiring at the SD adapter, yucky solders... It's not surprising his NAND chip is dead now.

    Question is, why didn't he fix his o3DS with ntrboot in the first place?
     
    E1ite007 likes this.
  5. BaamAlex

    BaamAlex S̶̥͝l̷̹̀͗e̶̼̖̩̅͊e̷̛̦͉̦p̷̘͌͝i̵͇̠̞̿̌n̷̰͚͌̓͝g̷̦̲̍̆͝
    Member

    Joined:
    Jul 23, 2018
    Messages:
    3,864
    Country:
    Germany
    It was just a guess. But if it's hardware related...makes sense.
     
  6. acho

    OP acho Advanced Member
    Newcomer

    Joined:
    Apr 27, 2007
    Messages:
    55
    Country:
    Indonesia
    Thank you for the reply guys , i guess this one is a goner. I will just get the motherboard instead as turd recommended. Was just trying to fix with I had but I guess it might have costed me a bricked nand. How would you have used ntrboot to fix it if the 3ds was just showing blackscreen and no cfw?
     
  7. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    7,292
    Country:
    United States
    The ntrboot method can install custom firmware to a 2DS/3DS system even if the 3DS firmware is severely software bricked. The hacking procedure would be the same as if the 3DS was functioning normal.

    Except for those who buy a R4i Gold 3DS Plus or Ace3DS X, the only drawback to ntrboot (other than cost $$$) is that you need a (o/n)(2/3)DS(i)(XL/LL)(phat/lite) system with working DS(i) mode to reflash or put the cart into ntrboot mode. So if your only 2DS/3DS system is already bricked, you will need to borrow one from a friend or family. Any Nintendo handheld that has 'DS' in its name will do.

    Depending on the severity, softbricks are typically fixed with SysNAND Restore, CTRTransfer, CTRTransfer (Type D9), or Lazarus3DS.
     
Draft saved Draft deleted
Loading...

Hide similar threads Similar threads with keywords - bootrom, Please, error