cfw 2ds xl has black screen on bootup and cant get to home menu

Discussion in '3DS - Flashcards & Custom Firmwares' started by ThatOneCookie, May 29, 2019.

  1. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    I have been having this issue for over six months now and tried fixing it but it didn't work I dont get a error menu but i can get to the power-off menu but still cant get to the home menu When attempting to load the home menu it freezes I dont know what to do at this point can someone please help
     
  2. Quantumcat

    Quantumcat Dead and alive

    Moderator
    20
    GBAtemp Patron
    Quantumcat is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Nov 23, 2014
    Australia
    Canberra, Australia
    What happens if you boot without the SD card? If the blue light goes on then off can you try on a different SD card with a freshly downloaded boot.firm from Luma 9.1?
     
    NoNAND likes this.
  3. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    tried it with a fresh sd card with nothing but boot.firm still gets the issue and the 3ds stays on its just a black screen also tried with no sd card and same issue is there anything else i can do
     
  4. Quantumcat

    Quantumcat Dead and alive

    Moderator
    20
    GBAtemp Patron
    Quantumcat is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Nov 23, 2014
    Australia
    Canberra, Australia
    Can you access GodMode9? Get the GodMode9 payload, rename it to boot.firm and put it on the root of the SD card.
     
  5. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    with my current or fresh sd card
     
  6. Quantumcat

    Quantumcat Dead and alive

    Moderator
    20
    GBAtemp Patron
    Quantumcat is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Nov 23, 2014
    Australia
    Canberra, Australia
    Yep
     
  7. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    upload_2019-5-29_21-44-56.
    which one do i rename
     
  8. Quantumcat

    Quantumcat Dead and alive

    Moderator
    20
    GBAtemp Patron
    Quantumcat is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Nov 23, 2014
    Australia
    Canberra, Australia
    GodMode9.firm
     
  9. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    I overwrite the current boot.firm correct?
     
  10. Quantumcat

    Quantumcat Dead and alive

    Moderator
    20
    GBAtemp Patron
    Quantumcat is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Nov 23, 2014
    Australia
    Canberra, Australia
    Yes, you can back it up or download Luma 9.1 again when you're ready
     
  11. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    I overwrote it and the same thing happens this is what my files look like now
    upload_2019-5-29_22-7-19.
     
  12. Quantumcat

    Quantumcat Dead and alive

    Moderator
    20
    GBAtemp Patron
    Quantumcat is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Nov 23, 2014
    Australia
    Canberra, Australia
    Hmm I have no idea. Weird that you can't get to GodMode9. Do you have an ntrboot flashcart?

    I shall summon some more experienced troubleshooters @TurdPooCharger @KleinesSinchen
     
  13. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    I used a ntrboot flashcard to install CFW and i can get to godmode but i dont know what i should do there
     
  14. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    I tried helping @ThatOneCookie before with no success. :(
    Your n2DSXL has access to GodMode9, right?

    There's an unconventional way to troubleshoot your CTRNAND... Due to the nature of how the method works, further discussion would have to continue by private message.
    La la la, nothing fishy going on here, la la.
     
    Quantumcat likes this.
  15. ThatOneCookie
    OP

    ThatOneCookie Advanced Member

    Newcomer
    2
    Jan 10, 2018
    United States
    Yes it does Can you message me the method whenever you can
     
    Last edited by ThatOneCookie, May 30, 2019
  16. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    You guys probably won't believe certain parts of this story that's told here. Just ignore the unimportant details. The only thing that matters is how the n2DSXL was fixed.

    For the unconventional idea I proposed, @ThatOneCookie agreed to overnight ship his n2DSXL to me with included prepaid return label. While we came to an agreement on what was to be done on his system, his package nevertheless arrived at my door step as a very quick surprise. It's a darn shame because what I requested from him could have saved him money if only there was another way they could have been sent. Hmm...
    This part "totally happened" because of, you know, the forum implications if it didn't. Sorry, can't provide proof or details. I forgot to take pictures of his n2DSXL while it was in my possession, and the mail recipe were hastily thrown away from aggressive recycling. :creep:

    Found in the [S:] SYSNAND VIRTUAL, the ctrnand_full.bin, twln.bin, and twlp.bin from his n2DSXL were dumped. These three (3) BIN files are the raw decrypted images of the [1:] SYSNAND CTRNAND, [2:] SYSNAND TWLN(AND), and [3:] SYSNAND TWLP(HOTO).

    While I don't condon NAND swapping, sharing, or cloning under normal circumstances, I took his images and flashed them onto my n3DSXL. The idea behind this is to debug the NAND on a substitute 3DS system of the same (new/old)-series that's known to fully work and doesn't have major hardware issues. Even though I could have troubleshooted his n2DSXL as it was, having that Pokeball edition model in my hands proved too distracting with that push button. :mellow:

    At first glance in the CTRNAND, none of the n2DSXL's important files were missing or appeared out of place. The [title / import / certs / ticket / tmp_i / tmp_t] *.db, movable.sed, LocalFriendCodeSeed_B, SecureInfo_B, HWCAL0.DAt, HWCAL1.DAt, etc. were all present and looked fine in hex viewer. There was ticket.bak found in 1:/dbs, which meant @ThatOneCookie did attempt built-in GodMode9 CTRTransfer.

    I renamed his original ticket.bak back to ticket.db and ran the CTRTransfer (Type D9) script. At the time, I felt a mixture of bored, disappointed, and smug thinking this softbrick was going to be like the others we've witnessed. Surely, no softbricks based in the CTRNAND could withstand the might of Decrypt9 style of CTRTransfer. Muwahaha!

    Upon attempting to boot HOME Menu, I was hit with this gut punch.

    Dafuq?

    Here's a little background information about the 3DS firmware that makes the above event a little startling. Of all the files that are absolutely needed, a 3DS system with custom firmware will successfully boot to HOME Menu if these conditions are met:
    1. The SecureInfo_A/B that's in place is compatible and is set to the correct region hex value.
    2. The title folder containing system titles is mostly intact. You can uninstall almost everything except:
      • 00040130 - System Modules
      • 00040030 - System Applets
      • 00040138#0000002 - (old/new)-series NATIVE_FIRM
      • several some titles related to HOME Menu (can't recall which ones)
    3. The title.db and import.db found in 1:/dbs tied to the title folder is likewise intact.
    4. The CMACs for all the files within CTRNAND are matching or corrected.

    Things that can be missing in the CTRNAND.

    • One doesn't need the movable.sed because there's a backup 0x30 slot KeyY found in another file called the otp.bin that the 3DS will default next.
    • You don't need tickets.db in order to boot to HOME Menu, but icons for system titles will be missing.
    • The certs.db handles online services and installing games, etc. Again, not needed to boot to HOME Menu.
    • tmp_i.db and tmp_t.db are the (DS mode) temporary versions of the DSiWare title & import. They're used when switching to TWL_FIRM. Booting to HOME Menu means booting in NATIVE_FIRM.
    • The HWCAL0.DAt and HWCAL1.DAt are hardware calibration files for the two LCD screens. Not having them will make the image quality look bad but doesn't stop anything from functioning.
    • The data folder contains the user's profile. Without it, the 3DS will start a new one like when you set up a fresh profile after doing Format System Memory.

    My first assumption for why HOME Menu failed to boot was because the n2DSXL's SecureInfo_B isn't cross compatible with my n3DSXL. However, when I put back in my n3DSXL's own SecureInfo_B, it still refused to boot! NANI?!
    I can only surmise my initial shock as something akin to medical biologists who have discovered strains of superbugs that are fully resistant to last line of defense antibiotics.
    Luckily, the bad feelings would come to pass as the root cause of the softbrick was eventually found after some dragging/dropping process of elimination.

    The bug that long plagued @ThatOneCookie was found at:
    Within that folder,
    f000000b
    00000000
    00000001
    00000002
    00000003
    00000004
    00000005
    00000006
    00000007
    00000008
    Quota.dat

    All the files had valid CMACs as calculated by GodMode9. A single suspect file couldn't be isolated because they're interrelated. If one was changed out, this affects the others.

    So what are the lessons that can be gleamed from this?
    • :!: Both built-in GodMode9 CTRTransfer and CTRTransfer (Type D9) cannot fix this "gamecoin" softbrick because they're conservative. These two leave alone the data folder.
    • Ironically, the (older program) Decrypt9WIP CTRTransfer could have fixed this, but at the expense of wiping out the user's entire profile. :lol:
      • Decrypt9WIP might not have worked for a different reason. The program has a weird bug where it can abort the CTRTransfer run if it detects a borrowed ticket.db.
    • Anyone who still thinks it's not important to back up a clean *.bin image of the SysNAND should give me his or her 3DS/2DS.
    • The majority of CTRNAND-based softbricks occur in title and dbs folder often due to someone's misuse of FBI, sysUpdater, or system update failure.
    • This is an extremely rare type of CTRNAND-based softbrick. Maybe even the first example of it's kind that's ever heard of. @ThatOneCookie hit the unlucky jackpot of becoming a 3DS case study. Lmao.
    • This type of brick can occur in any of the other extdata and sysdata subfolders found in data, and there are a lot of them. It does not necessarily have to be "gamecoin".
    • The closest SD card equivalent to this NAND brick is this one: Clear Home Menu extdata
      • If the problematic XXXXXXXX subfolder is found, either slowly re-add the files one-by-one after each reboot or delete the folder outright to fix this.
    Conclusion
    The n2DSXL was reflashed back with its fixed up NAND images, updated to firmware 11.10.0-43U, had its TWL system titles reinstalled, and DS mode tested with flashcart before being sent back. Oh, if @ThatOneCookie tells you a vastly different story than the one listed here, that's just him being modest.
    La la, fishiness no where in sight.
     
    Last edited by TurdPooCharger, Jun 2, 2019
    NFates, SCOTT0852, Sono and 2 others like this.
Quick Reply
Draft saved Draft deleted
Loading...