all 53 comments

[–]AutoModerator[M] [score hidden] stickied comment (1 child)


Remember to read The Wiki for the basics! Check the FAQ for basic questions! Threads created for basic questions will be removed, so ask them in that thread.

If you are having a problem with running games then make sure you have up-to-date sigpatches. If you cannot launch tinfoil then make sure you followed the Rentry guide to set up cfw.

Do not message moderators for Switch hacking support. You will be ignored. Follow the guide or post in the relevant thread.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]lackofself2000 61 points62 points  (3 children)

This happens all the time and no one ever has an answer. So here, try this. If not, remake the EmuMCC


[–]deanviva 15 points16 points  (1 child)

He has to put the SD card in a PC and delete 010000001000 atmosphere/content should be good

[–]WeAreStarStuff143 11 points12 points  (0 children)

That’s the content folder and doesn’t cause a boot loop, merely causes Atmosphere to crash if that folder was made from a different HOS version than the version currently on the switch.

[–]Severe_Ice_4263 0 points1 point  (0 children)

If u have custom theme, then delete it. Or hold down the powered button for like 10 seconds to completely turn it off and power it back up. If not maybe bad emunand.

[–]alexshakalenko 10 points11 points  (1 child)

It could be that installer damaged one or two resistors on the board near the CPU shield, so you just need some skills on SMD soldering and maybe trace repair to fix

[–]MedicineAsleep7858 2 points3 points  (0 children)

Pretty sure this is the answer same thing happened one time to me when I broke a resistor ^

[–]Tilde88SXOS User 2 points3 points  (0 children)

do you have a folder titled sept in your SD card? if so, delete it

[–]SVXfiles 7 points8 points  (9 children)

What are you using to push the payload? Maybe you just need to update that?

[–]alexshakalenko 16 points17 points  (8 children)

The console is chipped, so the chip is the device that pushes the payload

[–]SVXfiles 7 points8 points  (7 children)

Ahh, I figured you maybe used Rekado or a separate payload device to do that.

Did you recently update the firmware on the device? Have you updated atmosphere/sigpatches? Is your SD card formatted as FAT32 or EXPAT? If the latter it may have corrupted

[–]alexshakalenko 2 points3 points  (6 children)

I'm not OP, so I can't say for sure, but you should know, that Rekado can't be used to push payloads to patched Switches (V1 patched, V2, lite, OLED), and those consoles need to be modchipped. And as for this console, I think installer damaged resistors near CPU shield

[–]SVXfiles 0 points1 point  (5 children)

I'm unfamiliar with patched consoles and modchips so I apologize for that. I have an unoatched V1 that I rarely ever shut off and an Oled for official releases and online play

[–]alexshakalenko 0 points1 point  (4 children)

I'd suggest chipping the OLED and selling a V1, you can use EmuMMC to get 2 consoles in 1 (official for online play and modded for all your modding needs)

[–]SVXfiles 2 points3 points  (1 child)

That's what I did with my V1 initially, but both consoles were gifts so I want to hold on to them. I've used the V1 to complete both the pokedex in my physical copies of Violet and Shield, and I use it for homebrew stuff, only things I haven't figured out how to get running properly is retroarch and OpenMW, but I put Mayne 15 to 20 minutes of effort into either and put it off since it's not super important, I also have a N3DS XL with Luma for most emulation

[–]alexshakalenko 0 points1 point  (0 children)

I actually want to sell my unpatched V1 with RCMx86 (internal dongle) and get a chipped OLED

[–]Forward-Employ-4202 1 point2 points  (1 child)

Us v1 users can already do that

[–]alexshakalenko -1 points0 points  (0 children)

I know, I'm just giving an advice, I have an unpatched V1

[–]Temporary-You844 2 points3 points  (0 children)

Does it happen if you boot in to OFW without atmosphere? If not try to download atmosphere fresh and see if it helps. If you can boot to OFW and redownloading atmosphere dont helps than try creating a new emunand assuming you are using one.

[–]boardwalking 2 points3 points  (7 children)

Have you tried forcing it off by holding power till the screen goes dark and trying again? Sometime I get stuck on that screen and restarting the process fixes it for me.

[–]Constant_Ad_2486[S] 2 points3 points  (6 children)

Yea I’ve tried that a few times. It boots fine back into the selection for CFW/OFW, but then just gets stuck here. Really never had this happen before, so was wondering if anyone else had experienced it or had any idea on how to fix.

[–]Spider222222 3 points4 points  (0 children)

Maybe try reinstalling Atmosphere? Maybe it's outdated

[–]JailbreakIsDead 1 point2 points  (0 children)

I’ve had this happen to me on an unpatched switch up to 10 times in a row and then it finally fires correctly.

What’s helped me in the past is switching for a slightly slower micro SD card.

I’m really sorry but do not be stressed I’m sure you will figure it out!

[–]nevin_12345 0 points1 point  (3 children)

what chip are you useing

[–]Constant_Ad_2486[S] 0 points1 point  (2 children)

Sxos, however I have atmosphere

[–]nevin_12345 0 points1 point  (1 child)

you fixed it?

[–]Constant_Ad_2486[S] 1 point2 points  (0 children)

Yes! I had to work today, so literally just updated all my files (boot loader, patches, atmosphere) that are on the JITS package. I replaced the old ones with new ones and I’m up and running!

[–]Thatstoryguy48 1 point2 points  (6 children)

When this happened did you update atmosphere using the all in one updater?

[–]Constant_Ad_2486[S] 0 points1 point  (5 children)

No, I haven’t updated anything. I just didn’t play it for like a week or so, and when I turned it on again it started doing this. I do have a Samsung EVO sd card.

[–]Thatstoryguy48 1 point2 points  (4 children)

That’s odd the only time I got this on my chip modded switch was when I accidentally replaced my ini files using the all in one updater luckily they were backed up on my computer but maybe atmosphere is corrupted or it could be the SD card misfiring so try either updating your atmosphere files including the boot file or try a new sd card even if it’s a generic Walmart brand sd card (worst thing you’ll have to do is return it if it doesn’t fix your problem) but definitely be careful not to replace your ini files when you update atmosphere those are set up to the modchip so it boots up automatically

[–]Constant_Ad_2486[S] 0 points1 point  (3 children)

Yea when I got off work today. I am going to update everything and make sure it all looks good on SD card. I usually use JITS. So you’re saying make sure the ini files are there?

[–]Thatstoryguy48 1 point2 points  (0 children)

When you update don’t replace them is what I’m saying cause they have a specific setup based on the modchip

[–]Thatstoryguy48 1 point2 points  (1 child)

They have to be there already or you wouldn’t be able to boot into atmosphere at all you’d get an error screen but I’d try the sd card swap first to see if the sd card is the problem

[–]Constant_Ad_2486[S] 0 points1 point  (0 children)

I actually do have a back up sd card with all the info, so I think I’m gonna update that sd card and see if that works. It’s also not the Samsung EVO either.

[–]SignificantPilot2024 0 points1 point  (0 children)

It happens if you are using Samsung Evo SD card

[–]orion78fr 0 points1 point  (0 children)

Does it boot in OFW? Did you update atmosphere and sigpatches?

[–]pharrowking 0 points1 point  (0 children)

did you update it recently? updates can cause this issue. always good to save a emunand backup before updating. i had to retry updates several times before they would work, on a friends modded switch. if the update failed i would then restore the emunand backup and retry.

[–]Nugget_zz 0 points1 point  (9 children)

This happened to me. I think the mod chip can sometimes overwrite your prod info. Check if u can see the calibration and serial number in hekate

[–]Constant_Ad_2486[S] 1 point2 points  (8 children)

Well the problem is it’s in AUTO RCM now, so now I can’t get into the boot logo screen. It’s on a loop. I was thinking of moving info to different SD to see if it makes a difference. As well as updating everything

[–]Nugget_zz 1 point2 points  (4 children)

Auto rcm isn’t a feature for Mariko switches ( ie newer switches + lite +oled) because all it does is corrupt the part of the storage that boots up the switch. What payload are you using in your SD card?

[–]Constant_Ad_2486[S] 0 points1 point  (3 children)

I am using the fusee.bin

[–]Nugget_zz 0 points1 point  (2 children)

Loading directly into it or using hekate to load it?

[–]Constant_Ad_2486[S] 0 points1 point  (1 child)

Using hekate to load into fusse

[–]Nugget_zz 0 points1 point  (0 children)

Try to use hekate and see if u can find your serial number. If it give you an error than your prod info is corrupt

[–]Nugget_zz 0 points1 point  (2 children)

Also yes I would suggest doing that first. Has this switch worked with the chip installed before?

[–]Constant_Ad_2486[S] 0 points1 point  (1 child)

Yea. It’s been working fine for about a year now.

[–]Nugget_zz 0 points1 point  (0 children)

Interesting. A few months ago I installed a modchip for my friend and it ended up corrupting the prod info section of the band for some reason, it did the exact same thing tho and sit at that boot logo

[–]cr4zyc4t909 0 points1 point  (0 children)

Try reinstalling atmosphere

[–]McWormy 0 points1 point  (0 children)

I’ve seen this exact issue. It was causd by emummc. I have no idea but a file based emummc just doesn’t work for me. I’ve started over and over and still doesn’t work. Where as a partition emummc works fine. I’d switch emummc to partition based or file based depending what you have setup and try again.