Hacking SWITCH NOOB PARADISE - Ask questions here

[Blythe93]

but I hadn't configure any wifi network so it didn't connect to internet.

No need to worry then. Just make sure that you have DNS MITM or 90DNS set up before you connect to the Internet.

 

[FawfulMinion497]

No need to worry then. Just make sure that you have DNS MITM or 90DNS set up before you connect to the Internet.

Ok, I was asking because I also play online on stock.

 

[Blythe93]

Ok, I was asking because I also play online on stock.

As long as your emuNAND didn't connect to the Internet, it should be fine. Just use DNS MITM even if your emuNAND is allergic to Internet connection and you should be good to go.

 

[Draxzelex]

Hi everyone, I have a big problem. My Switch refuses to boot up. Whenever I turn it on, I get an error message with the code 2002-2634. I already tried restarting it and shutting it off/on, but it still returns to the error message at bootup. This started happening just now after Smash Bros crashed after I exited the Mod Manager (it does that often for some reason) but this is the first time that I was unable to boot back into the Switch home menu after a crash. Could this have anything to do with disabling nogc? I followed the instructions in the following link yesterday so that I could fix my Switch's game cart reading issue. https://rentry.org/DisableNOGC

Is there a program ID associated with the error code?

 

[MikeyTaylorGaming]

Quick one, I'm currently running FW 16.0.3 and want to update to the latest 18.1.0.

Wondering whether I should be updating Atmosphere on the SD Card first, or using Daybreak to install the Update. Does the latest Atmosphere still work with the older FW or is it actually FW specific?

I've updated the switch many times in the past but it's ages in between updates so always forget the process.

Do I literally just copy everything from the Atmosphere download onto the SD card and replace all files, that is;

• hbmenu.nro
• Atmosphere folder
• Switch folder
• Then boot through TegraRCM using the latest Fusee from the Github?

I have AutoRCM turned on and have done since the switch was hacked.

Thanks all

 

[Dust2dust]

Quick one, I'm currently running FW 16.0.3 and want to update to the latest 18.1.0.

Wondering whether I should be updating Atmosphere on the SD Card first, or using Daybreak to install the Update.

I've updated the switch many times in the past but it's ageeees inbetween updates so always forget the process. Also, Do i literally just copy everything from the Atmosphere download onto the SD card and replace all files? And boot using the latest Fusee from the Github?

Thanks all

Read this. Not saying this is the only way, but this is what I do, and it works. It assumes you're going to push the Hekate payload.

 

[MikeyTaylorGaming]

Read this. Not saying this is the only way, but this is what I do, and it works. It assumes you're going to push the Hekate payload.

I tend not to push the Hekate payload, haven't used it for so many years now ahaha Does the newest atmosphere version work on the older FW16.0.3? If so, I can easily update Atmosphere, then do the FW update. Cheers

 

[Dust2dust]

I tend not to push the Hekate payload, haven't used it for so many years now ahaha Does the newest atmosphere version work on the older FW16.0.3? If so, I can easily update Atmosphere, then do the FW update. Cheers

Hekate is great. If you mean you don't use Hekate, you should reconsider. Atmosphere is always backwards compatible with old firmwares, no worry there.

 

[MikeyTaylorGaming]

Hekate is great. If you mean you don't use Hekate, you should reconsider. Atmosphere is always backwards compatible with old firmwares, no worry there.

Nice, thanks for the quick reply that's handy info! I'll back up the SD card and install the new Atmosphere, then install Daybreak. That'll be the least hassle I think!

To be honest I don't know what Hekate really is but I'll take a look at the link you shared, I've used atmosphere for the duration of my switch hacking days and don't think I've ever booted another payload in that many years ahaha!

I do have Hekate in my favourites in TegraRCMGUI, but it's 'hekate_ctcaer_5.1.2.bin' which is probably super outdated now.

 

[Dust2dust]

Nice, thanks for the quick reply that's handy info! I'll back up the SD card and install the new Atmosphere, then install Daybreak. That'll be the least hassle I think!

To be honest I don't know what Hekate really is but I'll take a look at the link you shared, I've used atmosphere for the duration of my switch hacking days and don't think I've ever booted another payload in that many years ahaha!

I do have Hekate in my favourites in TegraRCMGUI, but it's 'hekate_ctcaer_5.1.2.bin' which is probably super outdated now.

If you've never used Hekate at all, that would mean you don't have a backup of your eMMC. You should make one ASAP. That's like the first step of any guide on Switch hacking. Be safe, pal.

 

[MikeyTaylorGaming]

If you've never used Hekate at all, that would mean you don't have a backup of your eMMC. You should make one ASAP. That's like the first step of any guide on Switch hacking. Be safe, pal.

Well, that must be why I have the old version of hekate because I 100% have a backup of it. Thanks again

 

[gofer]

I wanted to perform a clean installation of Atmosphere 1.7.1 on my Switch Lite with the SXOS modchip. I installed the HATS package version 17.1.5, which is adapted for 18.1.0. My switch was running on 16.1.0 at the time. It worked fine after the clean installation on 16.1.0.

I tried to update os to 18.1.0 using Daybreak. However, when I created a new folder on the SD card with firmware files, EmuNAND stopped booting and the console would freeze at the Nintendo Switch logo. After deleting that folder, EmuNAND would boot again.

I then updated the system on SysNAND (through sysmmc cfw), and everything worked fine—the system on SysNAND updated to version 18.1.0. Unfortunately, EmuNAND still froze at the Switch logo. I tried various methods, including reinstalling, clean installation, partition based EmuNAND, but nothing worked. I couldn't boot EmuNAND at all—it kept freezing at the Switch logo after trying to update to 18.1.0.

edit #1
I performed a downgrade of the OS to version 17.1.0 and next to 16.0.1 using the same method as before. I deleted all files from the SD card and then restored a backup of the card that I had made before attempting the clean installation (when everything was still working). I then restored a NAND backup.

After trying to boot, I encountered the error "failed to match warmboot with fuses." When I tried to fix the issue using the warmboot error fix, the same error appeared. I have updated fusee.bin to the latest available file from github but still nothing. Additionally, now the Power button only boots into Hekate after several attempts—I have to try multiple times before it boots.

edit #2

Clean installation again without any packs like HATS. SX Gear loaded from rentry, loaded the latest versions of Hekate, Atmosphere, and fusee.bin from GitHub, installed sigpatches 1.5.2 binary from the forum, placed fusee.bin in the /bootloader/payloads with the file name fusee.bin. System Version: 16.1.0. Atmosphere Version: 1.7.1

I used the following hekate_ipl.ini setup:

Spoiler

[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=1
updater2p=1

[SEMI-STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
usb3force=1
{}

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
usb3force=1
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
usb3force=1
{}

Semi-Stock (SysMMC): Boots, but I get the error "failed to match warmboot with fuses."
CFW (SysMMC): Boots with two errors: "failed to match warmboot with fuses" and "failed to apply nosigchk."
When I try to boot CFW, I only see the Atmosphere logo; the Nintendo Switch logo doesn’t appear, and the console freezes on a black screen.
The same happens when trying to boot into SysNAND through Reset -> OFW—it freezes on a black screen.

I also experimented with a different hekate_ipl.ini setup:

Spoiler

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

[Atmosphere CFW]
fss0=atmosphere/package3
emummcforce=1
kip1patch=nosigchk
icon=bootloader/res/icon_payload.bmp

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

Warmboot Error Fix: Shows the error "failed to match warmboot with fuses" but it does boot.
Atmosphere CFW: Restarting to hekate after warmboot fix and launching CFW, I see the errors "failed to match warmboot with fuses" and "failed to apply nosigchk," but it boots successfully. However, if I reboot into Hekate from CFW and try to relaunch CFW or try to launch CFW without warmboot fix, I just see the Atmosphere logo, and then the console freezes on a black screen again.

How to cope with this? I'm running out of ideas, any help would be much appreciated

edit #3
I have probably managed to deal with the problem. Burnt fuses: 19/0 HOS: 17.0.0+. I once again put first hekate_ipl.ini on the card bcs somehow the second one didn't work, cfw launched after warmboot fix shut down few times. Information about fuses was only available on the latest hekate. Again, CFW (SysMMC), daybreak, install fw 17.0.0. Then I tried to boot cfw and it froze on nintendo switch logo. Reboot -> ofw works now without errors. CFW (SysMMC) -> failed to apply nosigchk, no fuses error. Restart to hekate, launch cfw (emummc), nosigchk error but no fuses error, emummc was still on 16.1.0 but I've managed to update it to 17.0.0 through daybreak. AAAAND it's working. Power button is fine now too. Still, no idea what causes the problem (that switch stuck on the logo after putting firmware files on the card) and what the hell happened.

Next, I tried to get rid of nosigchk error;
Sys-Patch 1.5.0 Binary (FW 17 & Atmosphère 1.7.1+) -> cfw stuck on the logo
tried latest sigpatches -> cfw stuck on the logo
I put files from the backup after success at edit #3 -> cfw stuck on the logo
sd card format -> all files from the backup once again -> cfw works fine
??????did nand backup, tried to boot cfw and it stuck on the logo kekw

 

[Alegria]

is it possible at all to install android to an oled switch?

 

[mchabot1987]

If I wanted to upgrade my microSD to a larger capacity one, would I have to redo the softmod from scratch, or is there a way to clone the current microSD to the bigger one?

I'm aware that the Switch creates a hidden drive on the microSD, which may or may not be cloneable.

There are free software on the interwebs. I used AOMEI and cloned my 512gb to a 1.5tb took a while but have had no problems. Plugged it into my switch and bam everything exactly how I left it on the 512.........just more space lol

 

[That_Guy_Who]

Looking for help when switching Mod Chips. Previously running Instinct V6S (with minimal issues) and now Picofly rp2040 on Switch OLED. Since changing the chip, the switch will only boot up with the power cable plugged in. Holding VOL+ with power does nothing either.
Once it is plugged in it boots fine in to CFW.

- Just to clarify I've only changed the chip as i believed it was a straight swap as such. installation wise, I have the two ribbon cables installed and the wires from/to, C point, B point on the ribbon cables and the D+,D- and VBUS on the chip.

- When plugged in and turned on, the LED pulses blue for a good few seconds then flashes yellow/green than boots.

Any ideas whats gone wrong?
Cheers

 

[rsx]

I updated my console about a month ago to 18.1.0 but atmosphere bsod'd, tinfoil wouldn't load and there was a whole mess of other problems, was forced to rollback to 18.0.1. Have the issues been worked out?

 

[taffyponty]

I tried downloading and installing a few roms. Like I've done before. But there was a message about needing to update my switch??

Ok so how do I update all that stuff like all of it. Hekate/atmosphere/dbi / syspatch. Anything else? Oh and firmware

I obviously had a guide to initially set up my SD card. But the link to that is GONE from my watched threads? I also looked on the switch forum here. I can't see a thread stickied how to set up a switch (so basically I can follow the same steps but replace with newer versions)

Although do I need to delete the previous things I've extracted to switch SD card BEFORE replacing with new stuff.

So I want to only get a guide from here and not in a random place on Google. But I don't seem to be able to find the one I used here before. Why is it gone from my posts I've made here?

Another problem also popped up. When I plug in my switch to a usbc. I see no battery charge icon. On screen or no battery charge led.
Is this the battery or the entire device dead
Is it ok to take it to be repaired or not a good idea because it's hacked

Thanks

 

[Blythe93]

is it possible at all to install android to an oled switch?

If it's modded, it's possible. Check Switchroot Wiki for more info.

I updated my console about a month ago to 18.1.0 but atmosphere bsod'd, tinfoil wouldn't load and there was a whole mess of other problems, was forced to rollback to 18.0.1. Have the issues been worked out?

I'm running the latest firmware (18.1.0) and Atmosphere (1.7.1) and I'm yet to run into an issue. Which error were you getting?
For installing games, I prefer DBI since it never failed on me so, unless you're using Tinfoil for its free shops feature, I'd suggest that you switch to it as well. Unfortunately, it seems that the English version came to a halt, while Russian version is still receiving updates.

Ok so how do I update all that stuff like all of it.

I've made a short guide here.

Although do I need to delete the previous things I've extracted to switch SD card BEFORE replacing with new stuff.

Usually, you don't have to do that unless you run into issues. Overwriting the existing files worked for me so far.

Another problem also popped up. When I plug in my switch to a usbc. I see no battery charge icon. On screen or no battery charge led.
Is this the battery or the entire device dead

Make sure that you use the official power adapter and that both your adapter and USB port are working properly. I wouldn't trust third party chargers as I've seen in the past that they may cause more issues down the road. If your USB port is faulty, you'll need to repair or replace it. However, if everything seems fine, then it could be the battery issue.

Is it ok to take it to be repaired or not a good idea because it's hacked

I don't think that people at the repair shop will mind if your console is modded or not. Nintendo would, though, but you aren't sending it back to Nintendo for repairs, right?

 

[Alegria]

If it's modded, it's possible. Check Switchroot Wiki for more info.

According to the guy who installed the chip, Android crashes every time he tries to open it, so he didn't charge me for that, then he tried with his own marikos and realized it's general... but after some research I come to the conclusion he tried to install android 10 which is indeed limited to pre-mariko... I went to the link you're giving me and it doesn't look easy to do for me. For comparison, I could mod my 3ds without any help apart from the tutorial, but I gave up with my wii-u in the middle even with help and I'm not trying anymore.

Right now I'm in a pickle because I want to transfer some save files from my intact mariko to my chipped oled, then modify things (like take the pokémon files to my pc and inject some mystery gifts and pokémon from pksm's bank), then send a copy of the save files to the mariko so I'd have the save files on both consoles if necessary, I would keep playing on mariko and sometimes back up on the modded one (the aim is to leave the oled available for other people at home when needed) but I can't even log in to my account (probably because it's linked to a nintendo account) on the oled. I can't find either the pksm bank's files in the 3ds's sd card to open with pkhex but without the first part it's quite useless.
I feel very nooby and hopeless right now, sorry, I wish I was better at this.

 

[Manio]

Hello did i miss something here ? ( trying go online) and my exosphere look like this
# Key: debugmode, default: 1.
# Desc: Controls whether kernel is debug mode.
# Disabling this may break Atmosphere's debugger in a future release.

# Key: debugmode_user, default: 0.
# Desc: Controls whether userland is debug mode.

# Key: disable_user_exception_handlers, default: 0.
# Desc: Controls whether user exception handlers are executed on error.
# NOTE: This will cause atmosphere to not fail gracefully.
# Support may not be provided to users tho disable these.
# If you do not know what you are doing, leave them on.

# Key: enable_user_pmu_access, default: 0.
# Desc: Controls whether userland has access to the PMU registers.
# NOTE: It is unknown what effects this has on official code.

# Key: blank_prodinfo_sysmmc, default: 0.
# Desc: Controls whether PRODINFO should be blanked in sysmmc.
# This will cause the system to see dummied out keys and
# serial number information.
# NOTE: This is not known to be safe, as data may be
# cached elsewhere in the system. Usage is not encouraged.

# Key: blank_prodinfo_emummc, default: 0.
# Desc: Controls whether PRODINFO should be blanked in emummc.
# NOTE: This is not known to be safe, as data may be
# cached elsewhere in the system. Usage is not encouraged.

# Key: allow_writing_to_cal_sysmmc, default: 0.
# Desc: Controls whether PRODINFO can be written by homebrew in sysmmc.
# NOTE: Usage of this setting is strongly discouraged without
# a safe backup elsewhere. Turning this on will also cause Atmosphere
# to ensure a safe backup of calibration data is stored in unused
# mmc space, encrypted to prevent detection. This backup can be used
# to prevent unrecoverable edits in emergencies.

# Key: log_port, default: 0.
# Desc: Controls what uart port exosphere will set up for logging.
# NOTE: 0 = UART-A, 1 = UART-B, 2 = UART-C, 3 = UART-D

# Key: log_baud_rate, default: 115200
# Desc: Controls the baud rate exosphere will set up for logging.
# NOTE: 0 is treated as equivalent to 115200.

# Key: log_inverted, default: 0.
# Desc: Controls whether the logging uart port is inverted.

[exosphere]
blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1

ExosphereDNSMITM i try use this but when i go there its look much shorter than mine

thanks a lot , i am a big noob