Hacking SWITCH NOOB PARADISE - Ask questions here

[zografos]

This is on your old card? Looks like emunand is completely disabled And you’re on (S)ysnand there as well. Updating my mental diagram here…

Since your Atmosphere is 1.3.1 let’s upgrade to FW 14.1.0 (with FAT32 and exfat) using Daybreak on your new card. This should fix everything and you’ll be on your way.

Thank you very much !!!

 

[binkinator]

Hi guys, I have a small problem. I installed a sx core in my nephews switch 2 years ago and wanted to switch to atmosphere today. When installing the latest atmosphere files and using original (sysnand) boot0 and boot1 I get a black screen after the atmosphere Logo. The sysnand is still on 9.1 and the emunand on 10.1 Updated with choid iirc. Any idea what I can do?

I followed this tutorial:

https://rentry.org/mys8q

Is the mismatch in the sysnand version and emunand version causing this because I use sysnand boot0/1?


Thank you!

Move /atmosphere/contents to /atmosphere/contents.bak and see if that helps.

If not, double check you download the latest fusee.bin payload and place it in /bootloader/payloads/

if those things don’t work, please post the contents of your /bootloader/hekate_ipl.ini file.

 

[binkinator]

TL;DR: Switch from 2017 doesn't go into RCM anymore and also the WiFi just... shat itself somehow. No connections show up at all when I search in the settings. Full story under the spoilers, because it's long and I figured it might help me try to figure something out if I wrote down everything I can best remember.

Spoiler: Full story

So after a few months of not being charged at all, due to holding off on a digitizer repair (touch screen is mostly okay, just a small section doesn't respond to touch), I decided to charge my Switch back up. First thing I noticed was that the WiFi wasn't connected, so I tried to connect, wouldn't connect. Checked everything, kept getting error code 2110 1100, so cleared settings and set up the WiFi connection manually. Still didn't work. :s

Decided to set that to the side, so I rebooted back into stock to play some Skywalker Saga, and I found that I had to update the system to play the game. Thought that was weird, since I thought I had to be online for that, so I hit okay to see what would happen, and I guess it was a cart update? Because it didn't show up when I said no, but did when I hit update, so my Switch is on FW 13.2.0 now. A few hours later, I wanted to try again with the WiFi, figuring I could try to do something in Hekate. Not sure what my reasoning was behind that, but yeah.

Couldn't get into RCM. Okay, just gotta update the payloads and such on my RCM loader, right? I updated to the very latest payloads, and... well, I still couldn't get into RCM. I Googled it and it seems that the likely culprit is that something wore out on the rail, but I'm not sure if they mean the rail on the tablet that the JoyCons go into or the rails on the JoyCons themselves, because my JoyCons still charge and work just fine.

When you turn your Switch on with your jig in place does it go to the black screen or just boot normally?

What injector are you using, possibly RCM Loader? What version?

Have you done a reset (hold power for 15 seconds to turn off and then tap to turn back on)

Try maintenance mode with just a regular boot while holding both (Vol +) and (Vol -)

 

[Kingston]

Move /atmosphere/contents to /atmosphere/contents.bak and see if that helps.

If not, double check you download the latest fusee.bin payload and place it in /bootloader/payloads/

if those things don’t work, please post the contents of your /bootloader/hekate_ipl.ini file.

Hey, thanks for the answer but I tried and checked that already. The content of hekate_ipl.ini is like mentioned in the reentry guide.

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

 

[binkinator]

Hey, thanks for the answer but I tried and checked that already. The content of hekate_ipl.ini is like mentioned in the reentry guide.

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Great. That all looks good. Since you upgraded with Choi did you follow this? https://rentry.org/SwitchFAQ#error-fatal-error-nxboot-couldnt-parse-boot0

It wouldn’t hurt to update your *nand either.

What Is your ultimate end state?

If you have backups of your games and wouldn’t mind going 100% Atmosphere it will probably be better to upgrade you Sysnand to 14.1.0 and make a new empty Emunand based on that.

 

[Kingston]

Great. That all looks good. Since you upgraded with Choi did you follow this? https://rentry.org/SwitchFAQ#error-fatal-error-nxboot-couldnt-parse-boot0

It wouldn’t hurt to update your *nand either.

What Is your ultimate end state?

If you have backups of your games and wouldn’t mind going 100% Atmosphere it will probably be better to upgrade you Sysnand to 14.1.0 and make a new empty Emunand based on that.

I have a file based emunand and after converting it from sx to atmo I replaced Boot0/1 with the ones from the sysnand.

Could using the boot0/1 from fw 9.1 on the 10.1 emunand cause this?

 

[binkinator]

I have a file based emunand and after converting it from sx to atmo I replaced Boot0/1 with the ones from the sysnand.

Could using the boot0/1 from fw 9.1 on the 10.1 emunand cause this?

Oh I see. Yes, it it very well might. Not the kind of mixing and matching I would Think would work well. At this point since you’ve been swapping things out you’ve kinda got a Frankenand anyway and there’s little hope it would play any installed games. Unless you have backups of your file based boot0/1 you should go back to square one on the reentry guide and walk through a new install rather than a migration. To be very clear, it will grab a fresh copy of you Sysnand and put it into a partition based emunand. It will be as if starting over.

 

[Kingston]

Oh I see. Yes, it it very well might. Not the kind of mixing and matching I would Think would work well. At this point since you’ve been swapping things out you’ve kinda got a Frankenand anyway and there’s little hope it would play any installed games. Unless you have backups of your file based boot0/1 you should go back to square one on the reentry guide and walk through a new install rather than a migration. To be very clear, it will grab a fresh copy of you Sysnand and put it into a partition based emunand. It will be as if starting over.

Okay, thank you I guess I will have to do that. I Just wanted to try the quick and dirty way first

I did backups of the file based boot0 and 1 so I'm back to working sx on 10.1 right now

 

[Deleted member 390274]

Hi there!

I'm currently following this guide for migrating from SX OS to Atmosphere.

So far so good, I managed to solve the BOOT0/BOOT1 corruption issue I had by recreating it using a third-party tool.

But now I have another problem: when I boot Atmosphere (emuMMC) I get the following error:

Pkg1 decryption failed!
BEK is missing!
Failed to launch HOS!

No matter what, I can't seem to find any relevant information on this that doesn't contradict the others, so could anyone indicate me exactly what this error means and how I can solve it?

I have a proper hekate_keys.ini file in my bootloader directory, so this doesn't seem to be the problem.

Thanks in advance for your help!

 

[Draxzelex]

Hi there!

I'm currently following this guide for migrating from SX OS to Atmosphere.

So far so good, I managed to solve the BOOT0/BOOT1 corruption issue I had by recreating it using a third-party tool.

But now I have another problem: when I boot Atmosphere (emuMMC) I get the following error:

Pkg1 decryption failed!
BEK is missing!
Failed to launch HOS!

No matter what, I can't seem to find any relevant information on this that doesn't contradict the others, so could anyone indicate me exactly what this error means and how I can solve it?

I have a proper hekate_keys.ini file in my bootloader directory, so this doesn't seem to be the problem.

Thanks in advance for your help!

For starters, in all my years of Switch hacking, I have never seen this guide nor heard of this person so I would stay very far away from it because it doesn't seem reliable. In fact, I might even recommend starting from scratch with another & better guide such as this one. In short, your problem stems from trying to chainload either Hekate or fusee from SX OS which doesn't work on Mariko units. You will have to use either SX Gear or Spacecraft to launch Hekate/fusee. The guide I linked you will explain how to do everything properly.

 

[Deleted member 390274]

For starters, in all my years of Switch hacking, I have never seen this guide nor heard of this person so I would stay very far away from it because it doesn't seem reliable. In fact, I might even recommend starting from scratch with another & better guide such as this one. In short, your problem stems from trying to chainload either Hekate or fusee from SX OS which doesn't work on Mariko units. You will have to use either SX Gear or Spacecraft to launch Hekate/fusee. The guide I linked you will explain how to do everything properly.

Thanks!

The problem is that the guide you linked indicates to either open the console and flash the modchip itself, which I won't do because I'm too afraid to mess things up (which I've already done in the past), and the second indicates to use SX Gear which I don't have as I'm using a Switch Lite which as an SX Lite chip (without a dongle).

 

[binkinator]

Okay, thank you I guess I will have to do that. I Just wanted to try the quick and dirty way first

I did backups of the file based boot0 and 1 so I'm back to working sx on 10.1 right now

just keep it simple and get SXOS converted to atmosphere. Once in atmosphere you can use Daybreak to upgrade your Emunand firmware.

 

[Taikutsumaranai]

Hello everyone.
I recently switched to my second switch cause' I broke one of the pins on the motherboard's SD card connector of the first one (see the pic) . I first attempted to solder the golden end of the trace with a regular iron directly to the SD card reader (which proved to be very stupid) as I managed to remove it (orange circle.) I then replaced the SD card connector of the motherboard with a solder station along with the SD card reader just to be sure. However, Hekate still gives me 1Bit mode.
Since I replaced everything I can, Is it unrepairable now that I lost the golden end of the trace?

 

[Kingston]

just keep it simple and get SXOS converted to atmosphere. Once in atmosphere you can use Daybreak to upgrade your Emunand firmware.

I updated both sys and emunand to 14.1 and now everything works. Thank you.

 

[binkinator]

I updated both sys and emunand to 14.1 and now everything works. Thank you.

You did it! Congratulations man!

 

[binkinator]

Hello everyone.
I recently switched to my second switch cause' I broke one of the pins on the motherboard's SD card connector of the first one (see the pic) . I first attempted to solder the golden end of the trace with a regular iron directly to the SD card reader (which proved to be very stupid) as I managed to remove it (orange circle.) I then replaced the SD card connector of the motherboard with a solder station along with the SD card reader just to be sure. However, Hekate still gives me 1Bit mode.
Since I replaced everything I can, Is it unrepairable now that I lost the golden end of the trace?

You need to take it to an electronics repair shop and ask to get your fpc connector replaced. It’s easy to munge them up without proper tools. Quick and easy reflow work for a competent repair guy with a rework station. (Not taking a poke at your skills btw.)

 

[Adran_Marit]

Hello everyone.
I recently switched to my second switch cause' I broke one of the pins on the motherboard's SD card connector of the first one (see the pic) . I first attempted to solder the golden end of the trace with a regular iron directly to the SD card reader (which proved to be very stupid) as I managed to remove it (orange circle.) I then replaced the SD card connector of the motherboard with a solder station along with the SD card reader just to be sure. However, Hekate still gives me 1Bit mode.
Since I replaced everything I can, Is it unrepairable now that I lost the golden end of the trace?

There are some people experienced in switch sd card repair in this discord

They should be able to help out if possible.

 

[rantex92]

i dont think its a nooby question but does anybody tried to install kali nethunter on the switch? or is there even are precompiled switch version ?

EDIT: the android version not as a switch homebrew app

 

[HelloShitty]

Hi

Can we flex our mod chip installs in a dedicated thread? I started yesterday my very first one and I would like to show some pics even for people to tell me how bad or how reasonable it is!

 

[SeventyTurtle]

Question
I saw SwitchMe by rebug and other DIY Payload/Dongle/Modchip Injector online and their threads. But what's the difference between these and the hwfly, sx core etc... modchips? And can SwitchMe and the other relative DIY stuff mod a V2 Switch with serial XKJ7?

Sorry if this sounds dumb but I really didn't see any post fully explaining it.