[Patched 4.1.0] Switch getting Yellow and Black screen & acting scary

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by Francesca, Jul 5, 2019.

  1. Francesca
    OP

    Francesca GBAtemp Fan

    Member
    3
    Mar 17, 2015
    Armenia
    So I bought a new Switch this morning. It was patched, 4.1.0, and I discovered it was good for homebrew and CFW. I followed the Homebrew Guide in order to set up Hekate, Atmosphere, backing up my system and keys as explained in the guide's instructions. Because the guide hasn't been updated to include steps for installing an emuMMC on a patched console and warns very explicitly about the dangers of bricking when you don't know what you're doing (which is the case for me as I just don't understand how hacking works), I've left it there until a tutorial that is easy for me to understand and follow becomes available. Right now it doesn't seem like I'm able to set up emuMMC and get on with installing NSPs and using the console on my own.

    However, when I finished the setup of Atmosphere, I got the yellow screen. Here's how it happened: while in Hekate, you can launch into one of, I believe, four different "systems" - CFW SysNand, CFW EmuNAND, Stock SysNAND and Stock EmuNAND. Now, at this stage, why of these four work? I've done a little 3DS hacking and I can recognise just two systems - sysnand and emunand, in this case there are four. I haven't set up emuNAND (apparently called emuMMC this time), so out of these four, I understand I only have one option available - the SysNAND that the console had when I bought it. But is it CFW SysNand or Stock Sysnand?

    Anyway, the yellow screen occurred when I chose Stock Sysnand and then selected Sleep Mode. I panicked, but it wasn't lethal apparently.

    Moving on today, I turned on my console to locate where I saw autoRCM during the setup process I went through yesterday. I was aware how enabling autoRCM causes bricking and I was suspicious that it might have been turned on - the Homebrew Guide I linked mentioned neither enabling nor disabling it to avoid bricking the console. So I wanted to see where it was and then ask about it on this forum - launched PegaSwitch from the News menu while in sysnand (Atmosphere wasn't displayed in system settings), chose HBMenu as opposed to Hekate, waited until the Success! message appeared and... BLACK SCREEN! This is where I panicked, frankly. The buttons still made sound when I clicked them, but I couldn't restart or shut down the console at all (iirc after installing CFW choosing Restart is supposed to enter a different menu; I forget which of them). Eventually, the Nintendo logo appeared and the console turned on.

    Is there anything I did that I shouldn't be doing, looking at my story? I'd appreciate if somebody could help me understand how the four different sysnands work. And I'm still curious if there are any chances I can install emuMMC for playing backups before somebody releases a guide that babysits me through it, since I'm apparently far from being tech-savvy to understand what the existing tutorials want me to do.

    I could really use some assistance right now.
     
  2. gRoberts84

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    It would make sense to only show the options available to you but it appears Hetake isn't checking if you have an emunand/EmuMMC partition/file setup yet.

    If you try and load CFW/Stock (Emunand), it doesn't (or at least didn't when I tried) prevent you and then simply boots into Sysnand on CFW/Stock.

    You can verify this by going to Settings > System and the version should be 4.1.0 (AMS 0.92)

    I bought a patched 4.1.0 unit my self a couple of days ago and initially getting no where fast.

    Ultimately you need to make sure your SD Card is formatted in FAT32 with 32kb clustering and then make sure you download the latest files from SDSetup, as there was a bug a few days ago that caused problems with Atmosphere etc.

    The latest versions of ChoiDujourNX etc all detect iPatched units and prevent you from selecting AutoRCM.
     
  3. Francesca
    OP

    Francesca GBAtemp Fan

    Member
    3
    Mar 17, 2015
    Armenia
    Btw, I've finally found where I saw AutoRCM during the setup. It was when I was backing up eMMC in Hekate -> Tools menu. In the lower-right corner, it says 'Archive bit * AutoRCM'. Now, does this mean autoRCM is turned on? Turned off? Do I let it be? The Homebrew Guide confused me a little, as it first said not to touch autoRCM at all (quote Any homebrew or payloads involving the enabling or disabling of “AutoRCM”), but later on in the guide or perhaps somewhere else online that I was reading said "disable autoRCM". I can't rest it easy when it's there, is all.
     
  4. Kafluke

    Kafluke GBAtemp Guru

    Member
    14
    May 6, 2006
    United States
    If you ever accidentally turned on autoRCM youd have a paperweight that does nothing but boot to a black screen
     
  5. Francesca
    OP

    Francesca GBAtemp Fan

    Member
    3
    Mar 17, 2015
    Armenia
    Have you gone somewhere since then? As far as I understand, the next step is to install emuMMC, but it seems nobody's explained how it's done for ipatched systems yet. Tutorials that do explain it cover the autoRCM and jig methods which we're not supposed to use. If I understand things correctly that is.

    I formatted my SD Card to Fat32; what exactly is 32kb clustering and how is that done? The files I got from SDSetup were free, but before I saw the yellow screen there was nothing I'd describe as a 'bug', my Atmosphere installation went just the way it should have gone, without any failures that were covered in the Homebrew Guide in case they happened.

    'ChoiDujourNX' is a name I recognise for being a danger to an ipatched Switch. Not that it says anything to me right now.
     
  6. Basketto

    Basketto GBAtemp Regular

    Member
    2
    Jun 25, 2019
    Australia
    Since when has their been stock emunand? I always though emunand was run on CFW?
     
  7. Francesca
    OP

    Francesca GBAtemp Fan

    Member
    3
    Mar 17, 2015
    Armenia
    Okay, but I'd like to ensure it never happens rather than find out later I turned it on.

    This is what it looks like btw; just took a photo:

    https://i.imgur.com/921JBkE.jpg
     
  8. gRoberts84

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    Imagine it's just running emunand without any payload injection

    Pretty sure if you're getting that far, you're still ok. When do you get the yellow screen and what are you trying to do now?
     
  9. fantasticlain

    fantasticlain Member

    Newcomer
    1
    Apr 2, 2018
    United States
    I think you should qbRAuy advice from the team atlas nx discord (team atlas nx is the team behind pegascape )
    Link here: https://discord.gg/qbRAuy7
    Go to the support channel there.
     
  10. Francesca
    OP

    Francesca GBAtemp Fan

    Member
    3
    Mar 17, 2015
    Armenia
    As I said in the first post, 'Anyway, the yellow screen occurred when I chose Stock Sysnand and then selected Sleep Mode.' Still don't get the difference between Stock and CFW. If we assume I manage to install EmuNAND, will I be spending time in Stock EmuNAND or CFW EmuNAND? There was no dichotomy back in 3DS hacking. I haven't got the yellow screen since then, but getting black screen scared me a lot because it took me minutes to load my console afterwards.

    Right now I'm trying to... install emuMMC? "Trying" isn't really the right word, because the only tutorial I've found about it I find really hard to understand, and it doesn't seem to take IPatched consoles into consideration? There's this guide, which I find extremely confusing. What did you consult in order to succeed? Provided you did succeed, that is.

    Basically stuck waiting for the guide to come or somebody to help me out.

    This is useful indeed, it seems like the emuMMC portion of the ever-useful Homebrew guide will be available in about 2 weeks. From the searches I conducted there, it doesn't look like anybody's explained the process of setting up emuMMC for an ipatched unit.

    I'll make sure I hang around the discord and maybe somebody will explain the process of emuNAND setup before two weeks pass? I've been lurking a lot online in hopes of finishing the process of hacking my Switch, but it looks like it's still in its infancy for IPatched units...
     
  11. noahc3

    noahc3 GBAtemp Regular

    Member
    5
    Oct 17, 2015
    Canada
    Manitoba
    • The "Archive Bit * AutoRCM" is just a tab with more menu options. Hekate will never let you enable AutoRCM on an IPATCHED Switch, so there is no worry of enabling it (from Hekate, YMMV in other homebrew). I'll update the guide to mention this.
    • Sleep causing problems sounds like Hekate might be having some problems. I've uploaded a newer Hekate build to SDSetup, could you try redownloading (just click Atmosphere (Kosmos) and hit download, extract to SD and overwrite) and see if that fixes it?
    • You should not really use stock in emuMMC at all. Hekate's "stock" is sort of a lie, as it still runs three pieces of CFW that are necessary to make the Switch boot and to make emuMMC work (custom warmboot, custom secmon, emummc kipm). CFW alone won't get you banned, so it's safe to just boot with CFW into a "stock" emuMMC even if you want to go online and don't plan on doing anything detectable. It's probably safer to use full CFW than just some of it since Atmosphere has some anti-telemetry built in.
    • Every "good" emuMMC guide I've seen involves wiping the SD card. This is totally unnecessary. Our guide for emuMMC will hopefully be out by tomorrow (not two weeks heh). I've written most of it for Windows at this point, just need to rewrite it for Linux.
     
    Francesca likes this.
  12. Francesca
    OP

    Francesca GBAtemp Fan

    Member
    3
    Mar 17, 2015
    Armenia
    @noahc3 Whoa, awesome! That's great news indeed! So when I install emuMMC, I should be spending my time in CFW EmuMMC not Stock EmuMMC then? Got it. The sleep mode thing was a one-time only thing, but we'll see if it repeats - I imagine heavy use of the console will start when I'm finally in control of an EmuNAND.

    Looking forward to the EmuMMC guide! I'll post if any of it is unclear (the one guide I linked is almost impossible to understand with all partitions and other references I don't get; it probably assumes programming experience? I have none at all), but the Caffeine guide on the Homebrew guide was very clearly written and a pleasure to go through. Good to meet the person (one of the people?) behind it.

    P.S. I read "YMMV in other homebrew" in your post as "YHWH in other hebrew" so I think this is my cue to go to bed for tonight.
     
  13. gRoberts84

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    As per my reply. You need to make sure the SD Card is formatted in FAT32 with 32kb clustering and get the "latest" files from SDSetup. As I previously mentioned, I was downloading files that contained a bug that directly affected 4.1.0 units.

    So, this is how I have successfully done it...

    1. Go to SDSetup, download Kosmos + PegaScape, with Signature Patches enabled.
    2. Follow the Setting up the SD Card - Partitioning portion of https://www.scenefolks.com/pages.php?page=4210
    3. Extract the zip from #1.
    4. Copy contents from the payloads folder into sd/bootloader/payloads
    5. Copy contents of sd into your primary partition (the larger of the two)
    6. Insert the SD into the switch and boot into hetake as usual.
    7. If you haven't already, DO THIS! https://switch.homebrew.guide/hacking/caffeine/safetyprecautions
    8. Once complete, get back to hetake and click on EmuMMC.
    9. Click on Create EmuMMC and select SD Partition.
    10. Once complete, get press B a few times to get back to the main hetake screen and click reload.
    11. Click on EmuMMC to ensure you have enabled in the top left. If not, press Change EmuMMC and select an option from the left.
    12. Now, press B a few times to get back to the main hetake screen and click Launch > CFW (Emunand)
    If you happen to restart the Switch, you'll boot back into OFW, so you will need to:
    • Click on News > ReSwitched.
    • Follow instructions (Caffeine, tap textbox, wait 5 seconds and press power)
    • In hetake, click on Launch > CFW (Emunand)
    There are ways to get around this I think but for my own sanity sake, I do this manually.

    Once in CFW (Emunand) you need to make sure you are still on 90DNS, or airplane mode.

    Then you can use cartridges to play games, or load them over USB with goldleaf.

    Because my Switch came with Crash Team Racing, inserting that and installing it, upgraded my firmware to 7.1.0.

    If you were to reboot your switch and Settings > System (before going through ReSwitched etc) you will see the firmware of your Sysnand is still 4.1.0 and after booting into CFW (Emunand) it will be different.

    From there, I use choidujournx to install 8.1.0:
    • Download choidujournx (https://switchtools.sshnuke.net/)
    • Extract and copy ChoiDujourNX.nro to switch folder on SD Card.
    • Download the NX-8.1.0.zip
    • Create Firmware folder on SD Card.
    • Extract NX-8.1.0.zip and copy all files in the folder into the Firmware folder from above.
    • Insert the SD Card back into the Switch.
    • Boot into CFW (Emunand) and check System > Settings to make sure you see (AMS 0.92) in the firmware version.
    • Click home button.
    • Hold R and press Album twice.
    • Click on choidujournx.
    • Click on Choose (bottom right)
    • Click on 8.1.0 (or 8.1.0 exfat if you decided to format your SD with exfat)
    • Click on Select Firmware (bottom right)
    • Note on the left that "Prevent fuse burning (enable AutoRCM)" has a X and on the right, it mentions AutoRCM is disabled due to the device being patched. You do not need to change anything, this is forcibly disabled.
    • Once complete, click Reboot.
    After clicking Reboot it took me back to hetake, where I selected Launch > CFW (emunand)

    Now you will be on 8.1.0 on Emunand but 4.1.0 on Sysnand.

    Installing games can be done using Goldleaf. Plenty of tutorials etc on that around these parts.

    HTH

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

    Oh... And, if you have problems with homebrew showing nothing, delete the Switch folder, boot into CFW (emunand) and load hbmenu.

    Once you have done this, you can copy the contents of the switch folder from the SDSetup files back into the switch folder on the SD Card and it should work.
     
    Tininjo and Francesca like this.
  14. Tininjo

    Tininjo Newbie

    Newcomer
    1
    Aug 6, 2019
    Portugal
    Basicly you’re saying that upgrading emuNAND this way wont burn any fuse, since the Nintendo Switch will reboot into Hekate after installing. Am I right?

    So using ChoiDujourNX on emuNAND will ONLY affect the emuNAND and never sysNAND.

    Just wanted to be 100% sure before I go ahead with this.

    Really thanks for the guide!
     
  15. JotaBarba

    JotaBarba Member

    Newcomer
    1
    Aug 16, 2019
    Spain
    Hi Francesca!!

    Im completely noob on Switch's Scene, and i've an ipatched 4.1.0 switch, like yours.
    I've readed a few guides on how to install Atmosphere and emummc, but not followed anyone yet (i hope to get time to do it in a few weeks).

    The only thing that i didnt understand is if this is a tethered method, so, if console gets battery depleted, is mandatory to reach PegaScape over internet to had Hetake again??

    Thanks in advance for your response, and for share your experiences!!!


    Sent from my iPhone using Tapatalk
     
Quick Reply
Draft saved Draft deleted
Loading...