Hacking SWITCH NOOB PARADISE - Ask questions here

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
I can't auto boot into CFW after updating
Well what firmware did you update and what version is your CFW?

Ok so, Just bought a "hackable"Switch and I have been reading around the forum for a couple of days...

Got SX OS Pro..... finished backing up my Virgin NAND with SX OS bootloader and now I'm ready to hack..

My OFW is currently 4.1.0, so I know I won't be able to play many games with it...


Question: Is there a way (and is it the best way?) to keep my OFW on 4.1.0 and let's say, install EmuNAND on 8.1.0 to be able to play newer gamer?

or,

EmuNAND won't accept a newer firmware than the OFW from the device??

if not, should I use ChoiDujourNX to install 8.1.0 since 9.0.0 is non hackable yet and then install EmuNAND also in 8.1.0?

and lastly, should I go up to 8.1.0 or is there a better FW a long the way that I should update and stay at??

Details: Trying not to get banned so quickly, will be playing mostly offline on EmuNAND, want to play some switch games, and some emulators.

Sorry for the long post.... If anyone can help I appreciate, thanks..
The main purpose of EmuNAND is to load higher firmware versions than your system. Of course, you can only load as high a firmware version as the CFW you are booting supports. In the case of SX OS, that is firmware 8.1 but Atmosphere (which is a free alternative) currently supports up to firmware 9.0. Regardless of which CFW you choose, I recommend updating to firmware 8.1. And ChoiDujourNX is the perfect way to update your EmuNAND to that firmware.
 
  • Like
Reactions: 3dswitch and Chupa

Chupa

Member
Newcomer
Joined
Aug 17, 2010
Messages
15
Trophies
0
XP
36
Country
Brazil
Ok, fist of all, thank you so much for such a quick response, you guys rock :bow:

Since I never played Switch before I'll stick with SX OS 8.1 for now, I know there will be plenty of games for me to enjoy.

So as a next step clarification:

-It's fine to leave my OFW on 4.1.0 since I won't be using it that much now anyways.
-Install EmuNAND and then use ChoiDujourNX to update it to 8.1.0 so I can enjoy all the cool games that will support it.

Now the last question that should answer all my doubts:

Should I try to use ChoiDujourNX to also update sysnand to 8.1.0 when I have some spare time or maybe that could flag Nintendo since I'll be doing it offline and then when I go online crap can happen??

or,

Maybe I should just play my cool 8.1.0 emunand games offline untill SX OS releases a full integration with 9.0.0 so I can go ahead and update my OFW normally in Switch's system and then update emunand, etc, later?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
Ok, fist of all, thank you so much for such a quick response, you guys rock :bow:

Since I never played Switch before I'll stick with SX OS 8.1 for now, I know there will be plenty of games for me to enjoy.

So as a next step clarification:

-It's fine to leave my OFW on 4.1.0 since I won't be using it that much now anyways.
-Install EmuNAND and then use ChoiDujourNX to update it to 8.1.0 so I can enjoy all the cool games that will support it.

Now the last question that should answer all my doubts:

Should I try to use ChoiDujourNX to also update sysnand to 8.1.0 when I have some spare time or maybe that could flag Nintendo since I'll be doing it offline and then when I go online crap can happen??

or,

Maybe I should just play my cool 8.1.0 emunand games offline untill SX OS releases a full integration with 9.0.0 so I can go ahead and update my OFW normally in Switch's system and then update emunand, etc, later?
Well that depends if you don't mind using SX Pro to boot your CFW forever or if you want to have the chance to boot CFW in other ways in the future. See the Nintendo Switch has these things called fuses and some of these are used to prevent downgrading. When your console normally installs a system update and reboots. When the console's stock bootloader detects you are running a firmware higher than your current fuse count, it burns fuses until they match. And in order to prevent your console from downgrading, the stock bootloader will not allow you to boot a firmware lower than the current fuse count. So in order to prevent fuses from being burnt, we install firmware files and AutoRCM where AutoRCM prevents us from using the stock bootloader. This is how ChoiDujourNX works in order to update your firmware without burning fuses. However as you said, it may flag your console for a ban since it requires the usage of CFW & homebrew. But there are other ways of updating your firmware without burning fuses.

The first method involves updating the console with AutoRCM enabled while running CFW. You may have asked, "If AutoRCM can be used to prevent fuses from being burnt, why not just update with AutoRCM already enabled?" The reason that is not possible is because system updates normally remove AutoRCM. However free CFW can prevent this. This is not a feature of SX OS and may never come to the CFW much like the other features of free CFW such as overclocking and external sysmodule loading. Anyway, installing a system update with AutoRCM enabled while running a free CFW will not remove AutoRCM thus preventing your fuses from being burnt. But this still requires the usage of CFW which means it still has a chance to ban your console. There is one more method of updating without burning fuses.

The last way involves manually applying AutoRCM after the system installs the system update. There is technically a way to prevent the stock bootloader from burning fuses without CFW and that involves putting the console into RCM before it has the chance. This is the safest method in terms of a ban since RCM and AutoRCM are next to undetectable but it is also the most dangerous as failing to boot into RCM will burn your fuses. If you wish to try this method, I recommend following this guide.

Or if you do not care about other exploits and are content with using SX Pro until time immemorial, then you can just ignore the walls of text above and just update to 9.0 normally once SX OS supports that firmware.
 

Chupa

Member
Newcomer
Joined
Aug 17, 2010
Messages
15
Trophies
0
XP
36
Country
Brazil
Well that depends if you don't mind using SX Pro to boot your CFW forever or if you want to have the chance to boot CFW in other ways in the future. See the Nintendo Switch has these things called fuses and some of these are used to prevent downgrading. When your console normally installs a system update and reboots. When the console's stock bootloader detects you are running a firmware higher than your current fuse count, it burns fuses until they match. And in order to prevent your console from downgrading, the stock bootloader will not allow you to boot a firmware lower than the current fuse count. So in order to prevent fuses from being burnt, we install firmware files and AutoRCM where AutoRCM prevents us from using the stock bootloader. This is how ChoiDujourNX works in order to update your firmware without burning fuses. However as you said, it may flag your console for a ban since it requires the usage of CFW & homebrew. But there are other ways of updating your firmware without burning fuses.

The first method involves updating the console with AutoRCM enabled while running CFW. You may have asked, "If AutoRCM can be used to prevent fuses from being burnt, why not just update with AutoRCM already enabled?" The reason that is not possible is because system updates normally remove AutoRCM. However free CFW can prevent this. This is not a feature of SX OS and may never come to the CFW much like the other features of free CFW such as overclocking and external sysmodule loading. Anyway, installing a system update with AutoRCM enabled while running a free CFW will not remove AutoRCM thus preventing your fuses from being burnt. But this still requires the usage of CFW which means it still has a chance to ban your console. There is one more method of updating without burning fuses.

The last way involves manually applying AutoRCM after the system installs the system update. There is technically a way to prevent the stock bootloader from burning fuses without CFW and that involves putting the console into RCM before it has the chance. This is the safest method in terms of a ban since RCM and AutoRCM are next to undetectable but it is also the most dangerous as failing to boot into RCM will burn your fuses. If you wish to try this method, I recommend following this guide.

Or if you do not care about other exploits and are content with using SX Pro until time immemorial, then you can just ignore the walls of text above and just update to 9.0 normally once SX OS supports that firmware.

Thanks again for the quick (and thorough) response. I don't know how you type that fast:O..

So, yeah I don't really care for other exploits that much, if SX OS can get me the right amount of games and emulators that's all need from my hacking.

I had actually rad your discussions around the forum about burning fuse's and what not and you just refreshed my memory about the process of doing the RCM at the right exact time to prevent the fuse burning but I'm too much of a sloppy guy when it comes to dealing with this type of stuff (it actually took me 5min to fit the SX jig on my Switch cuz I was trying to slide it in on the wrong side :hateit:lol)

With that being said, I think I'm on the right track then... Emunand is being created here (40% right now), while that installs I'm getting everything ready for updating it with ChoiDujourNX and then from there I'll be enjoying my fare share of gaming and emus for a while:gba:

So, last NOOB question if you may be kind to answer:

- I actually installed SX OS 2.5.3 because I'm usually scared of beta realeases and I'm having a hard time finding what is the latest ChoiDujourNX update it can support. Some sites say 6.2, others say 7.0. Which one is it?

or,

-Should I trust the 2.8 beta version of SX OS and rebuild my EmuNAND on it so I can use ChoiDujourNX to update to 8.1 and not worry too much about what games I can or cannot play since it will be a much more newer FW???

and thanks again for being so helpful.
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
So, last NOOB question if you may be kind to answer:

- I actually installed SX OS 2.5.3 because I'm usually scared of beta realeases and I'm having a hard time finding what is the latest ChoiDujourNX update it can support. Some sites say 6.2, others say 7.0. Which one is it?

or,

-Should I trust the 2.8 beta version of SX OS and rebuild my EmuNAND on it so I can use ChoiDujourNX to update to 8.1 and not worry too much about what games I can or cannot play since it will be a much more newer FW???

and thanks again for being so helpful.
For all intents and purposes, assume ChoiDujourNX supports all firmware versions. There is a tool with a similar name by the name of ChoiDujour which only supports up to firmware 6.1. As for your other question, the beta tag is just an excuse for them to not take responsibility for any bugs users encounter. You can easily encounter bugs on the stable versions and several users still experience those without using the beta.
 
  • Like
Reactions: Chupa

Chupa

Member
Newcomer
Joined
Aug 17, 2010
Messages
15
Trophies
0
XP
36
Country
Brazil
For all intents and purposes, assume ChoiDujourNX supports all firmware versions. There is a tool with a similar name by the name of ChoiDujour which only supports up to firmware 6.1. As for your other question, the beta tag is just an excuse for them to not take responsibility for any bugs users encounter. You can easily encounter bugs on the stable versions and several users still experience those without using the beta.


Ok, cool...

I kind of knew that ChoiDujourNX supported all firmwares but I thought that SX OS on a certain (older) version wouldn't accept an update of a certain (newer) FW from ChoiDujourNX update... I guess I was wrong..

I think I get it know, let's see if this makes sense. I can keep using SX OS 2.5.3 because my OFW is 4.1.0 so it runs OK, then I can use ChoiDujourNX to update my EmuNAND to 8.1.0 since it supports all versions and then I'm good to go???


"if feels that I'm getting so close to have my perfect gaming machine here... this is awesome haha!!!"

EDIT: It's never that easy right? :cry::cry:

So,
- finished installing EmuNAND, loaded and it was fine..then
- got ChoiDujourNX and updated EmuNAND to 8.1.0
- Now CFW only boots to a black screen :sad:

What did I do wrong?? or maybe I was right and SX OS 2.5.3 does not support EmuNAND running 8.1.0???
 
Last edited by Chupa,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
Ok, cool...

I kind of knew that ChoiDujourNX supported all firmwares but I thought that SX OS on a certain (older) version wouldn't accept an update of a certain (newer) FW from ChoiDujourNX update... I guess I was wrong..

I think I get it know, let's see if this makes sense. I can keep using SX OS 2.5.3 because my OFW is 4.1.0 so it runs OK, then I can use ChoiDujourNX to update my EmuNAND to 8.1.0 since it supports all versions and then I'm good to go???


"if feels that I'm getting so close to have my perfect gaming machine here... this is awesome haha!!!"

EDIT: It's never that easy right? :cry::cry:

So,
- finished installing EmuNAND, loaded and it was fine..then
- got ChoiDujourNX and updated EmuNAND to 8.1.0
- Now CFW only boots to a black screen :sad:

What did I do wrong?? or maybe I was right and SX OS 2.5.3 does not support EmuNAND running 8.1.0???
This is why the beta line is stupid. Version 2.5.3 only supports up to firmware 6.2. The only way to boot higher firmware versions with SX OS is with the betas
 
  • Like
Reactions: Chupa

Chupa

Member
Newcomer
Joined
Aug 17, 2010
Messages
15
Trophies
0
XP
36
Country
Brazil
This is why the beta line is stupid. Version 2.5.3 only supports up to firmware 6.2. The only way to boot higher firmware versions with SX OS is with the betas

Ow, crap, I understand.. I tried to ask you that but I think I stated my question wrongly (sorry english is not my native language)

now, since I can't boot into CFW I guess I need to boot into SX OS menu, delete emunand, update SX OS to 2.8 beta, redo de emunand process and then use ChoiDujourNX update 8.1.0 right?

or is there a faster route to this?

EDIT: if I just leave everything as is and update the SX OS files from the 2.5.3 version to the 2.8 beta will it work?

EDIT 2: It works, the short route.... just swapped boot.dat files from 2.5.3 to 2.8 and it booted by EmuNAND on 8.1.0 now!!!

YEEEAAHHH mission accomplished
 
Last edited by Chupa,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
Ow, crap, I understand.. I tried to ask you that but I think I stated my question wrongly (sorry english is not my native language)

now, since I can't boot into CFW I guess I need to boot into SX OS menu, delete emunand, update SX OS to 2.8 beta, redo de emunand process and then use ChoiDujourNX update 8.1.0 right?

or is there a faster route to this?

EDIT: if I just leave everything as is and update the SX OS files from the 2.5.3 version to the 2.8 beta will it work?
Yes, you can just update your version of SX OS to the latest version.
 
  • Like
Reactions: Chupa

Mogiie

New Member
Newbie
Joined
Sep 16, 2018
Messages
4
Trophies
0
Age
44
XP
147
Country
Greece
what happens if I update with ChoiDujourNX from 5.1 to 8.1 and one time I forget to go to RCM and inject the payload (my switch doesn't have internet access) ?

thanks
 

LuigiXL

Well-Known Member
Member
Joined
Jan 19, 2016
Messages
673
Trophies
0
XP
2,170
Country
I am wondering if to use my third party dock on my Switch. Ever since the great "3p docks brick the Switch" debacle a couple of years back I have held off using it regularly (once on 6.x and it seemed fine) I am wondering was there ever any truth to it if using the official AC adaptor?
 
Last edited by LuigiXL,

Gamese

Member
Newcomer
Joined
Sep 18, 2019
Messages
21
Trophies
0
Age
34
XP
76
Country
United States
Ok so... two new questions:

1) I tried booting a cartridge which used to work on my switch (BOTW)... but I get an error "Could not start software Please try again from the HOME menu". How do I solve this?
2) What's the easiest way to get from 6.2.0 to 8.1 as @Draxzelex mentioned? I found a guide from @rajkosto titled: "How to install/run ANY Switch firmware UNOFFICIALLY (WITHOUT burning any fuses)"

Thank you in advance.
 

Something whatever

Gazer of the East
Member
Joined
Sep 1, 2015
Messages
901
Trophies
0
Age
32
Website
www.pixiv.net
XP
2,030
Country
United States
Well what firmware did you update and what version is your CFW?

The main purpose of EmuNAND is to load higher firmware versions than your system. Of course, you can only load as high a firmware version as the CFW you are booting supports. In the case of SX OS, that is firmware 8.1 but Atmosphere (which is a free alternative) currently supports up to firmware 9.0. Regardless of which CFW you choose, I recommend updating to firmware 8.1. And ChoiDujourNX is the perfect way to update your EmuNAND to that firmware.
current FW
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
I am wondering if to use my third party dock on my Switch. Ever since the great "3p docks brick the Switch" debacle a couple of years back I have held off using it regularly (once on 6.x and it seemed fine) I am wondering was there ever any truth to it if using the official AC adaptor?
It is a hardware issue, not a software issue. The third-party docks are lacking a part that the official docks have. The charger will also not make a difference.

Ok so... two new questions:

1) I tried booting a cartridge which used to work on my switch (BOTW)... but I get an error "Could not start software Please try again from the HOME menu". How do I solve this?
2) What's the easiest way to get from 6.2.0 to 8.1 as @Draxzelex mentioned? I found a guide from @rajkosto titled: "How to install/run ANY Switch firmware UNOFFICIALLY (WITHOUT burning any fuses)"

Thank you in advance.
  1. What changed since you were last able to use your cartridge?
  2. Unfortunately the guide you linked has a tool that only supports up to firmware 6.1. A more streamlined app called ChoiDujourNX is better for this process

current FW
You only answered half of my questions
 
  • Like
Reactions: LuigiXL

Something whatever

Gazer of the East
Member
Joined
Sep 1, 2015
Messages
901
Trophies
0
Age
32
Website
www.pixiv.net
XP
2,030
Country
United States
It is a hardware issue, not a software issue. The third-party docks are lacking a part that the official docks have. The charger will also not make a difference.


  1. What changed since you were last able to use your cartridge?
  2. Unfortunately the guide you linked has a tool that only supports up to firmware 6.1. A more streamlined app called ChoiDujourNX is better for this process

You only answered half of my questions
9.0.0 on OFW and the CFW I use is Atmosphere I didnt set up a emuNND yet just hacked it last week XD
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,986
Trophies
2
Age
29
Location
New York City
XP
13,325
Country
United States
9.0.0 on OFW and the CFW I use is Atmosphere I didnt set up a emuNND yet just hacked it last week XD
emuMMC does not really make a difference here but if you are on firmware 9.0 and Atmosphere is not auto-booting, your CFW version is probably outdated. Update your build of Atmosphere.
 
  • Like
Reactions: Something whatever

kruptah

Well-Known Member
Newcomer
Joined
Dec 12, 2014
Messages
59
Trophies
0
Age
38
XP
176
Country
Canada
Can somebody please help me with modding my switch or direct me to the right thread or guide?

Current system version: 9.0.0


Have a r4s to inject payloads and microSD with the following contents:


Screen Shot 2019-09-19 at 9.33.04 AM.png


I'm using argon with multiple payloads and R4S Dongle Firmware to boot into the launcher where I'll select SX OS or any other one to only encounter issues with launching them.

For instance SX OS will turn off my Switch completely requiring a hard reset to power back on the console.

Do I require the SX Loader as I'm not a pro user yet?

Also, where do I extract xci files to on my Switch, the /Nintendo/Albums folder, correct?

Regards.
 
Last edited by kruptah,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • BigOnYa @ BigOnYa:
    I just been playing offline, and they give you a few bots here n there on your team to help battle. I don't think it's as funny as the other games tho, more battle oriented than humor, which kinda sucks, but I'm still early in it
  • Xdqwerty @ Xdqwerty:
    @BigOnYa, doesnt the game have a campaign mode?
  • BigOnYa @ BigOnYa:
    Yea, and co-op, but you can also start a pvp session and battle just with friends. You get special skill cards (powers) the more you play. And higher value cards, but you can only enable so many cards at a time.
  • K3Nv2 @ K3Nv2:
    If you can find enough for it
  • BigOnYa @ BigOnYa:
    Toilet paper is considered the money, you collect and buy stuff with TP, kinda funny. Graphics are def better than the other games tho, I think they used Unity 5 engine.
  • Psionic Roshambo @ Psionic Roshambo:
    Look if I zoom in enough I can see the herpes!!!
    +1
  • BigOnYa @ BigOnYa:
    In fact I'm gonna go make a drink, roll a fatty n play some, good night to all!
    +2
  • Xdqwerty @ Xdqwerty:
    I bet most people at the time still watched it in black and white
  • SylverReZ @ SylverReZ:
    @Xdqwerty, Many of them did before colour television was common.
  • SylverReZ @ SylverReZ:
    Likely because black and white TV was in-expensive.
    +1
  • K3Nv2 @ K3Nv2:
    It certainly wasn't inexpensive it cost the same as a new car back then
  • K3Nv2 @ K3Nv2:
    How much did a 1965 color TV cost?

    For example, a 21-inch (diagonal) GE color television in 1965 had an advertised price of $499, which is equal to $4,724 in today's dollars, according to the federal government's inflation calculator.
    +1
  • Xdqwerty @ Xdqwerty:
    @K3Nv2, take into consideration how economy was back then
  • K3Nv2 @ K3Nv2:
    Yeah that's why they listed inflation rates
  • Xdqwerty @ Xdqwerty:
    Sorry didnt read that part
  • BakerMan @ BakerMan:
    @LeoTCK don't worry i knew he was joking
    +1
  • Psionic Roshambo @ Psionic Roshambo:
    My first color TV was like 1984 or something lol
  • Psionic Roshambo @ Psionic Roshambo:
    19 inches it was glorious lol
  • SylverReZ @ SylverReZ:
    @Psionic Roshambo, If it doesn't fit, you should've gotten one smaller lol
    +2
  • SylverReZ @ SylverReZ:
    If a racoon can fit up to 8-inches then so be it
    +1
  • Psionic Roshambo @ Psionic Roshambo:
    Lol it it fits I sit? Lol
    +1
  • SylverReZ @ SylverReZ:
    @Psionic Roshambo, Will it blend lol
    +1
    SylverReZ @ SylverReZ: @Psionic Roshambo, Will it blend lol +1