Hacking SWITCH NOOB PARADISE - Ask questions here

[anthony001]

whats the best switch official firmware to install 1.4.2 or 1.5.x? why?

 

[Draxzelex]

whats the best switch official firmware to install 1.4.2 or 1.5.x? why?

Firmware versions 1.4.2 and 1.5.X don't exist.

 

[anthony001]

Firmware versions 1.4.2 and 1.5.X don't exist.

sorry i meant 14.1.2 and 15.x.x

 

[Lamcza]

sup, another nub question is it normal that my joysticks and dpad are so sensitive in album and hb apps i mean they sometimes skipping by 2 or 3, this happens only in the album and hb apps and there is no drift on my joysticks at all (2pairs of og with new sticks and joy 1 pair of some third party all the same.)

nvm seems that reverting stock settings and new calibration helps a little.

 

[paoloandnikko]

Problem with All-in-One Nintendo Switch Updater by HamletduFromage

I’m trying to download cheats - cheat slips and it crashes in applet mode when the game is running (See screenshot). When I try to download cheats when the game isn’t running, it says this:

“This feature isn't available in applet mode. Please launch aio-switch-updater through title override to access it."

How do I title override the aio-switch-updater and will this fix the crashing error when downloading cheats from cheat slips? Thank you in advance for helping me.

 

[Lamcza]

Problem with All-in-One Nintendo Switch Updater by HamletduFromage

I’m trying to download cheats - cheat slips and it crashes in applet mode when the game is running (See screenshot). When I try to download cheats when the game isn’t running, it says this:

“This feature isn't available in applet mode. Please launch aio-switch-updater through title override to access it."

How do I title override the aio-switch-updater and will this fix the crashing error when downloading cheats from cheat slips? Thank you in advance for helping me.

o wow your oled is quacked as quack first class oled uniformity

Iam not sure what it is all about but did you try to launch it by holding R + A

 

[binkinator]

Problem with All-in-One Nintendo Switch Updater by HamletduFromage

I’m trying to download cheats - cheat slips and it crashes in applet mode when the game is running (See screenshot). When I try to download cheats when the game isn’t running, it says this:

“This feature isn't available in applet mode. Please launch aio-switch-updater through title override to access it."

How do I title override the aio-switch-updater and will this fix the crashing error when downloading cheats from cheat slips? Thank you in advance for helping me.

Title Override — What is title override and how to override its key combo

 

[soldiaz]

Happy Holidays!

Please post your hekate_ipl.ini.

Did you do a recent upgrade or anything?

Walk through this guide to see if you missed anything:
(Make sure you grabbed the new fusee.bin.)

I guess I experienced the very same seveal times....dont know why. Held power for couple of secs for hardware power off then booted normally to SD

 

[binkinator]

I've installed all the sigpatches and the latest version of Hekate (6.0.1 & Nyx v1.5.1) and my emunand boots just fine. I'm having issues booting my sysnand though, after the switch logo I get
error code 2005-005 0xa05
program 0100000000000000001f
firmware 15.0.1 something... I tried just installing fresh atmopshere Hekate (without the sigpatches) and I still get that error whenever I try to boot sysnand. Is the problem with my hekate_ipl.ini I wonder? These are its contents:

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1
customlogo=2
logopath=/bootlog0.bmp
logopath=/bootlogo.bmp

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
logopath=bootloader/bootlog0.bmp
icon=bootloader/res/icon_red.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_blue.bmp

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

Not sure how to fix this, any help would be appreciated immensely.

This error typically signifies corruption.
What brand of card do you have?
how did you format it?

Please check your SDCard w/ h2testw and let us know the results.

 

[brut_]

can I play online on switch and use nintendo online and then install modchip later? or i will get banned?

 

[Hayato213]

can I play online on switch and use nintendo online and then install modchip later? or i will get banned?

You can play online and install modchip as long you keep your pirated stuffs on an emunand.

 

[Taikutsumaranai]

Hello! Is there any way to translate the switch UI language? Specifically to Arabic so it doesn't contain any Latin letters.
I am willing to put my time into it so any kind of info is appreciated. Thanks!

 

[Hayato213]

Hello! Is there any way to translate the switch UI language? Specifically to Arabic so it doesn't contain any Latin letters.
I am willing to put my time into it so any kind of info is appreciated. Thanks!

No

 

[Kurnel5]

This error typically signifies corruption.
What brand of card do you have?
how did you format it?

Please check your SDCard w/h2testw and let us know the results.

Nah my SD's alright, I did try a brand new SD and had the same error show up.
The only thing that fixed it for me was turning the Switch off completely and turning it back on.

 

[Blakejansen]

Fusee.bin is the primary payload and package3 is the secondary payload. They used to be called fusee_primary.bin and fusee_secondary.bin respectively which made it more intuitive what each one did. Basically, you send fusee.bin as your payload which chainloads into package3. The reason for this is because there is a size limit on payloads that you can send so in order to work around this, developers make payloads chain into bigger payloads to perform the hack.

So when I want to update my sysfw, do I run OFW on sysnand or CFW? I thought the Nintendo boot loader is what burns the switches in which case I wouldn't need cfw on sysnand correct? I remember you stating that you used cfw in regards to sysnand and updating, is there a reason why I would need to run CFW on sysnand?

 

[Draxzelex]

sorry i meant 14.1.2 and 15.x.x

Well if that's the case, firmware 15.X has been out for long enough that most homebrew apps and other tools should have been updated to support it and if they haven't been updated yet, they have most likely already been abandoned by their authors.

So when I want to update my sysfw, do I run OFW on sysnand or CFW? I thought the Nintendo boot loader is what burns the switches in which case I wouldn't need cfw on sysnand correct? I remember you stating that you used cfw in regards to sysnand and updating, is there a reason why I would need to run CFW on sysnand?

Sorry if I wasn't clear before. What I do specifically is I boot Stock mode via Hekate to go online and download the system update then I go offline and boot into CFW to install the update system while AutoRCM is enabled. Both times I avoid using the stock bootloader. And the reason you need to run CFW on sysMMC is because if you update the console without CFW, AutoRCM will be removed and when the console reboots after the system update, since AutoRCM will have been removed, the stock bootloader will be used so you must install the system update in CFW to prevent AutoRCM from being uninstalled.

 

[Blakejansen]

Well if that's the case, firmware 15.X has been out for long enough that most homebrew apps and other tools should have been updated to support it and if they haven't been updated yet, they have most likely already been abandoned by their authors.

Sorry if I wasn't clear before. What I do specifically is I boot Stock mode via Hekate to go online and download the system update then I go offline and boot into CFW to install the update system while AutoRCM is enabled. Both times I avoid using the stock bootloader. And the reason you need to run CFW on sysMMC is because if you update the console without CFW, AutoRCM will be removed and when the console reboots after the system update, since AutoRCM will have been removed, the stock bootloader will be used so you must install the system update in CFW to prevent AutoRCM from being uninstalled.

Couldn't you just use a jig for the first RCM after installing the update and then install AutoRCM again? If so I wouldn't need to ever run CFW on sysnand correct? Does autorcm have a risk of permanently bricking my switch?

 

[urherenow]

Couldn't you just use a jig for the first RCM after installing the update and then install AutoRCM again? If so I wouldn't need to ever run CFW on sysnand correct? Does autorcm have a risk of permanently bricking my switch?

Some people are still holding onto hope that a coldboot exploit will come out for fw ~4.0 or some such, and they don't want to burn fuses. The stock option in Hekate prevents fuses from being burned, on top of preventing AutoRCM from being overwritten. Maybe even prevents the game slot from being updated.

I think it's all a big hassle and just boot OFW to update, then dump the update to install in emummc.

AutoRCM is technically a brick. Done on purpose. As long as you keep a backup of boot0/boot1 on your computer, you can always fix it within nyx.

 

[Draxzelex]

Couldn't you just use a jig for the first RCM after installing the update and then install AutoRCM again? If so I wouldn't need to ever run CFW on sysnand correct? Does autorcm have a risk of permanently bricking my switch?

Yes you can and that is the third option for being able to update your firmware without burning fuses. The problem is that method relies solely on your jig. That is to say if your jig fails to boot RCM, your fuses will be burnt so unless you have a jig with 100% efficacy, its an incredibly big risk which is pointless when there are safer and far more effective methods available. You see threads like that all the time where the user is not able to boot back into RCM despite using the same jig again. And that's because jigs cause wear and tear on your right Joy-Con rail so there is no jig with 100% effectiveness meaning its a big risk if you want to update this way.

Also, the device is technically already bricked from AutoRCM. I don't see how it can get any worse than that.

 

[binkinator]

Hi all,

I'm a bit worried about the steps on the other articles. All of them detail that the issue happens in CFW or emuMMC. I have Hekate (5.6.2) and Atmosphere ( 1.1.1), but I never was able to have it working with emuMMC, so it's disabled.

Switch Lite (Mariko) with chip SX Lite.
I'm use the switch loading hekate, Launch and stock. I've continued to update the OFW until 13.0.0.1. At that moment i had the switch shutdown for some time.

Yesterday I've started it and agreed to update the OFW, as usual. After that, I have that error.

Unknown pkg1 version.​

HOS version not supported!​

​

Trying to backup bootloader...​

found pkg1 ('2022....​

​

Unknown pkg1 version.​

HOS version not supported!​

​

Failed to launch HOS!​

Checking console info I can see now:
Burnt Fuses (ODM 7/6): 17 - 0 (HOS: Unknown)

CAL0 Version: 17 // Update Count: 8


I have a previous backup with that FW verison, but I guess I won't be able to boot to it if I restore due the Fuse on 17.

Do you think is there something I can do to recover it?

I read in other threads to update Hekate and Fusee.bin, but these threads are about CFW and emuMMC. May I use them in my configuration?

Maybe I have it broken already. All the help will be welcome

This error is typically a result of an outdated Hekate.

You can update Hekate here:
https://github.com/CTCaer/hekate

More information about keeping your Switch up to date can be found here:

https://rentry.org/SwitchHackingIsEasy