N3DS - Unable to boot into the Gateway Menu using the OoT exploit after changing Launcher.dat

Discussion in '3DS - Flashcards & Custom Firmwares' started by Takanaka, Jul 17, 2015.

  1. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    Hello! I am going to make a thread here about my problem! I already posted this in the Noob thread but was told to make a thread for this problem.

    "Hello! I have been Googling around and looking around this place and MaxConsole but I was unable to find any help. I have been playing on my N3DS for a few days and used the MSET_EUR thing and everything was fine and happy and colours and things! Then I replaced the Launcher.dat file that I have (which was 3.2.2) with the newest 3.3 and as soon as I tried to boot into it, it made the screen go black. I kept trying and trying and sometimes it would light up in all colours (the red card). Wel, I used the Zelda cartridge that I first used to see if I could boot into it but it just sent went black on the upper screen and white on the lower screen. I kept trying and trying. But it was the same!

    Then I tried to update to an earlier version 3.2.2 and replace the Launcher.dat file again, with my old Nintendo 3DS, etc. Back and forth on both of them. But it didn't work.

    I then noticed that the "Super Stable" was gone from my N3DS and panicked. I still think that this is the reason why it won't work anymore but I don't know. I thought about using the "Format System" since I couldn't get access to the Gateway Menu or anything related to that. And that didn't help....in fact I am afraid that made it worse. Because now I am stuck in the downgraded Settings (I learned that this was the case after I had used the format thing, sadly) and the Nintendo Profile exploit is completely gone.

    I don't really know what to do. I read the manual and it told me to go here to ask for help. I am sorry if this is the wrong thread to ask."
     
  2. VerseHell

    VerseHell GBAtemp Psycho!

    Member
    3,067
    1,067
    Jun 29, 2014
    France
    You didn't install the bluecardfix ? Did you try to restore the oot save again ? (also, you had no reason to update if you have a n3ds, mine is still on 3.2.1)
     
  3. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    Thanks for your reply. No, I didn't install the "bluecardfix". I tried to restore the OoT save many times. The result was the same, sadly. You know, I was aware that I did not need to update it, since there was nothing in for the N3DS. I just don't know why I did it. I wasn't really thinking straight... I have been quite unlucky lately.
     
  4. usernametaken

    usernametaken GBAtemp Maniac

    Member
    1,247
    345
    May 13, 2015
    United States
    Installing the Mset removes the Super Stability from Sysnand.

    Go to Settings - Other Settings - Profile - Nintendo DS Profile.
    Does it take you to your profile name or does it try to boot gateway?

    If it tries to boot, you should perfectly fine. Gateway doesn't launch 100% of the time and you may just be getting unlucky. 3.2.2 or 3.3 shouldn't matter which you use since you don't actually update anything other than replacing the launcher file.

    Also if your mset exploit is still in place, booting the profile exploit without the cart inserted should take you to the gateway menu.
     
  5. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    Sadly, it didn't work before. My Red Card would just turn on all the lights at once, I think. Or a very bright white light with other colours. I tried many times that way and it didn't work. Trust me, I used it the day before yesterday and there was no problems at all what-so-ever.

    And no, I panicked and "Format System" which removed that. So I am stuck on the downgraded Settings. .____.'

    Please keep posting suggestions, thank you. I am going to bed now. It's way past midnight and almost morning. I have to get up for work in 2 hours.

    Bye bye!
     
  6. usernametaken

    usernametaken GBAtemp Maniac

    Member
    1,247
    345
    May 13, 2015
    United States
    Just want to clarify, is the led going off on the actual Gateway red cart or is it the 3ds that's flashing its lights?
     
  7. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    It was the LEDs that lit up. Not the 3DS itself. ^^
     
  8. usernametaken

    usernametaken GBAtemp Maniac

    Member
    1,247
    345
    May 13, 2015
    United States
    Alright, if it was the Leds on the 3ds then it could be an indicator of a bad internal mSD - mSD not seated properly - or damaged / blocked pins on the 3ds itself.

    If it's the led located on the gateway cart (the tiny hole next to the msd slot) then that shouldn't prevent you from booting into gateway menu (This was before you wiped the Mset exploit :P)

    Edit: The first set of potential problems would make the most sense to me. If the 3ds wasn't reading the internal mSD then it wouldn't have a way to launch gateway menu, thus causing a black screen.
     
  9. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    But it worked fine on my old Nintendo 3DS. It wouldn't even boot up Gateway Menu using the OoT and that was before I wiped it. Besides, I ran some diagnosi...diag....that word <----- Tests on it, on my old 3DS and it said that everything was just fine. And I was able to play games on it. Yet, I was unable to do that on the N3DS.

    If my writing is starting to get a bit weird is because I am kind of not looking while typing that much. So sleepy. Sorry mate, thank you for helping me. Will have to look at your reply tomorrow. Cheers.
     
  10. VerseHell

    VerseHell GBAtemp Psycho!

    Member
    3,067
    1,067
    Jun 29, 2014
    France
    Did you update your emunand ?
     
  11. usernametaken

    usernametaken GBAtemp Maniac

    Member
    1,247
    345
    May 13, 2015
    United States
    It sounds like your N3ds' mSD or the mSD reader is the problem to me.

    When you replaced the launcher.dat file originally, did you remove the mSD to transfer the file, or did you do it wirelessly?
    If not, i'd violently rip off not really the back plate again and first make sure the mSD is properly seated. You can eject it, then reinsert making sure you hear the click locking it down.
    After that i'd try booting to gateway menu using your OOT.

    If that doesn't work, remove the mSD from the N3ds & use some canned air (You could blow in it, but that introduces moisture you don't want or need) in case any particles are in the mSD bay.
    Reinsert mSD & try OOT again.

    Still not working? Try another mSD in your N3ds, copy over all of your files from the mSD onto another (You can use the gateways mSD if you need to)
    Then try OOT yet again :|

    If all of that doesn't work, gotta brainstorm lol.
     
  12. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    No, I did not update my EmuNAND or SysNAND.

    — Posts automatically merged - Please don't double post! —


    I have a Nintendo 3DS which can go into Gateway without problems and I have a New Nintendo DS which won't boot into Gateway what-so-ever. I am able to "Restore Savedata from SD Card" to 'inject' the Gateway exploit into the game, using the "Old Nintendo 3DS", so that I can use it in the "New Nintendo 3DS" to boot into Gateway Menu. Well, I used to be able to boot into the menu. ^^'
    I have tried to blow into the N3DS and the cartidge itself. It still works on my "Old Nintendo 3DS".
     
  13. usernametaken

    usernametaken GBAtemp Maniac

    Member
    1,247
    345
    May 13, 2015
    United States
    Try using a different mSD inside your N3ds with the Launcher.dat. *May as well use Launcher from 3.2.1 since that was the last update related to N3ds)
    Only place the Launcher.dat on the mSD in the root.

    If you're able to boot into gateway on your o3ds. It's either your N3ds internal mSD - mSD Reader or Game card reader.
    You're able to launch OOT and get to the main menu right?
     
  14. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    Hahahahahaha! I found the issue. I am so stupid..well, it's not my fault exactly....the latter part is, however. First of all, I am sorry. Yes, the fault is the internal MicroSD. It had formatted itself apparently to something called "FAT", instead of "FAT32". I formatted it to FAT32, and the 4 GB micro became a 1.68 GB? >_< That's my fault, I had no idea why it formatted itself into that. Sorry everybody. I am a noob. ^^'
     
  15. Typhin

    Typhin GBAtemp Fan

    Member
    305
    101
    Jan 30, 2008
    United States
    I'm glad you found the answer, I wouldn't have guessed that. Everyone's a noob in the beginning, and now that you've discovered what happened, maybe the next person this happens to will find the post and find the solution.

    The internal mSD must be FAT32, so that would be why it didn't work. The reason it's saying 1.68 GB is because the emuNand partition takes up around 2 GB on a New 3DS, and the remaining space is lost due to filesystem overhead.
     
  16. Takanaka
    OP

    Takanaka Member

    Newcomer
    30
    3
    Jul 16, 2015
    Thank you for being so kind to me, everybody! I was afraid that you were all going to be mean and laugh at me. But you were all so kind and welcoming. I feel good here. ^_^