Hacking SWITCH NOOB PARADISE - Ask questions here

[Zap2000]

Maybe its referring to the modifications EmuNAND makes to boot1 rendering booting OFW impossible on 4.1 and below? As I stated previously, I don't have a license to test this but it seems like a rather simple thing to test. Just boot 2.4, setup EmuNAND but don't enable AutoRCM, turn off the console, and try booting OFW without SX OS. Even if it black screens, you can get out of it with a manual shutdown (holding power for 12 seconds).
If you update to 6.2 now, you will burn fuses and it will be impossible for you to downgrade in case a future exploit (like untethered coldboot) comes out on a lower firmware. If you don't care about downgrading or other potential exploits, you can just burn fuses and update normally right now. If you do care, wait until you get the SX Pro then use the homebrew application ChoiDujourNX to update to whatever firmware you want.
Honestly never heard of this issue. Maybe try booting a newer version of Atmosphere? It is up to 0.8.2 now. If you haven't tried this package already, you can try loading Kosmos which is Atmosphere but with Hekate instead of Fusee.
4NXCI is based off of Hactool which hasn't been updated with most of the newer keys so it just freaks out and spits a lot of warnings but at the end of the day, that's all they are, warnings.
Sounds like they require a game update because a system update would say a system update is required.
Different programs use differently formatted key files for whatever reason. You can just rename the prod.keys file to whatever you want like keys.txt if the program you are using requires such.

I’m not sure mate if I test things out il brick is there any testers in gbatemp could check? they also said see below


Team Xecuter has put out a post on their forums which says that their 2.4 doesn't work with ofw 4.1.0 and below. Also they have said that on 2.4 you can't boot other payloads (so ox will freeze if you choose this option) so for your first step you'd need to find another way to push hekate to your switch.
As far as I know, SX OS 2.3 can push henkate and create emuNAND (sort of, but i don't pretend to go online right now anyway, so this kind of emuNAND works just fine).
So i'll have a emunand on 6.2 and my OFW on 4.1.0 without burned fuses.

 

[Draxzelex]

I’m not sure mate if I test things out il brick is there any testers in gbatemp could check? they also said see below


Team Xecuter has put out a post on their forums which says that their 2.4 doesn't work with ofw 4.1.0 and below. Also they have said that on 2.4 you can't boot other payloads (so ox will freeze if you choose this option) so for your first step you'd need to find another way to push hekate to your switch.
As far as I know, SX OS 2.3 can push henkate and create emuNAND (sort of, but i don't pretend to go online right now anyway, so this kind of emuNAND works just fine).
So i'll have a emunand on 6.2 and my OFW on 4.1.0 without burned fuses.

If using SX OS 2.4 on firmware 4.1 caused a brick, everyone would know about it and nobody would use their product.

 

[Agent Moose]

Question: I was looking around what seems like everywhere to find a XCI to NSP Convertor for Mac OS. Is there such a thing because I would love to see if I dumped my MK8 cartridge correctly.

 

[Zap2000]

If using SX OS 2.4 on firmware 4.1 caused a brick, everyone would know about it and nobody would use their product.

Haven’t heard anyone trying it here or they forum? the person on here is using sx 2.3? Maybe il have to think of a diff way? They using these steps below

1 - use sx loadder to boot henkate and backup my nand
2 - Create a emunand throught SX OS 2.3 (I've read somewhere on this forum that the emunand is not working on 4.1.0 OFW with SX OS 2.4).
3 - Update the emuNAND to 6.2 with Choi and enable exFAT leaving me with OFW 4.1.0 no exfat support and emuNAND 6.2 exfat support.
4 - Stay offline
5 - hope for a coldbot someday.


Does 2.3 work on 6.2?

 

[Draxzelex]

Haven’t heard anyone trying it here or they forum? the person on here is using sx 2.3? Maybe il have to think of a diff way? They using these steps below

1 - use sx loadder to boot henkate and backup my nand
2 - Create a emunand throught SX OS 2.3 (I've read somewhere on this forum that the emunand is not working on 4.1.0 OFW with SX OS 2.4).
3 - Update the emuNAND to 6.2 with Choi and enable exFAT leaving me with OFW 4.1.0 no exfat support and emuNAND 6.2 exfat support.
4 - Stay offline
5 - hope for a coldbot someday.

If you update the EmuNAND to 6.2, you won't be able to use it unless you boot with SX OS V2.4 just so you know.

 

[Zap2000]

If you update the EmuNAND to 6.2, you won't be able to use it unless you boot with SX OS V2.4 just so you know.

That’s what I thought I will msg them and tell them. I can’t think of any other way to do wat I want to can u? Without using Autorcm? Could I bypass the fuse check some other way ? Or update sysnand to another fw that’s supported ?

 

[Draxzelex]

That’s what I thought I will msg them and tell them. I can’t think of any other way to do wat I want to can u? Without using Autorcm? Could I bypass the fuse check some other way ? Or update sysnand to another fw that’s supported ?

That's actually what my next suggestion was going to be. You could just update SysNAND to a firmware that is supported by SX OS V2.4. You can do this with ChoiDujour/ChoiDujourNX or if you want to spend some money, can update offline with a cartridge.

 

[Zap2000]

That's actually what my next suggestion was going to be. You could just update SysNAND to a firmware that is supported by SX OS V2.4. You can do this with ChoiDujour/ChoiDujourNX or if you want to spend some money, can update offline with a cartridge.

Will I be able to get back to 4.1 later without using Autorcm or could I blow fuses without Autorcm?

 

[Draxzelex]

Will I be able to get back to 4.1 later without using Autorcm or could I blow fuses without Autorcm?

If you never turn off the console, you can do so without AutoRCM. But you would also have to ensure it never runs out of battery either. For a less anxiety-inducing method, you have to use AutoRCM to prevent fuses from being burnt.

 

[Zap2000]

If you never turn off the console, you can do so without AutoRCM. But you would also have to ensure it never runs out of battery either. For a less anxiety-inducing method, you have to use AutoRCM to prevent fuses from being burnt.

Why does fuses blow again even if I didn’t go to latest fw?

 

[Draxzelex]

Why does fuses blow again even if I didn’t go to latest fw?

You should read this.

 

[Zap2000]

There's plenty of tutorials around, the best imo is

https://guide.sdsetup.com

Is there a

You should read this.

Cheers

You should read this.

Wat about if I run a lower emuNAND version 6.1 on sx version 2.3?

 

[Draxzelex]

Is there a



Cheers


Wat about if I run a lower emuNAND version 6.1 on sx version 2.3?

You can run any firmware on EmuNAND but the higher, the better since there is no downside in running higher firmwares and games/updates will require higher firmwares at one point or another.

 

[Zap2000]

You can run any firmware on EmuNAND but the higher, the better since there is no downside in running higher firmwares and games/updates will require higher firmwares at one point or another.

Yeah Would it be a hard process to update sx os version and emuNAND fw later on?

Would I be missing out on much running 6.1 instead of 6.2?

 

[TPMJB]

Okay, so after a lot of troubleshooting, I finally got Hekate to boot again. I think what I did was dump kfuse values to my SD card? Anyway, now I cannot load atmosphere because it says "payload file is missing." The fusee-primary file is definitely where it should be so I don't understand what is going wrong.

Also, now when I try to dump TSEC keys it says "unknown package1 version for reading TSEC firmware (= '20181107105733').

I mean I can at least launch hekate and charge, but I can't actually use the console. I think this all started after I tried dumping the keys in lockpick in 6.2 after I had dumped the keys in 4.1 already.

Edit: Also, for some reason I cannot restore my backups.

Edit2: I got to 6.2 using Choidujour.

 

[Trollface1011]

Is there a way to boot the switch when it has autorcm to OFW Without any thing else to put the switch into something like hekate?

 

[Wanap]

today I hacked my friend's switch (fw 6.2) and eventually we managed to run atmosphere with fuse gele and it runs fine (album is hb etc.), but:
1) does reinx work on 6.2? we couldnt get it to work
2) I get error 2168-0002 when I try to dump keys from kezplez (I dumped the fuses and tsec_keys via hekate, but when I try to run kezplez I get that error)
3) I can't install any games if I dont have the keys extracted (by using kezplez) am I right?
4) can I use n1dus if im running atmosphere?

as always thanks in advance

 

[Draxzelex]

Yeah Would it be a hard process to update sx os version and emuNAND fw later on?

Would I be missing out on much running 6.1 instead of 6.2?

Again, as stated previously, for the time being no but eventually games/updates will require higher firmware so you will have to update at some point if you plan on playing the latest games/updates.

Is there a way to boot the switch when it has autorcm to OFW Without any thing else to put the switch into something like hekate?

Nope.

today I hacked my friend's switch (fw 6.2) and eventually we managed to run atmosphere with fuse gele and it runs fine (album is hb etc.), but:
1) does reinx work on 6.2? we couldnt get it to work
2) I get error 2168-0002 when I try to dump keys from kezplez (I dumped the fuses and tsec_keys via hekate, but when I try to run kezplez I get that error)
3) I can't install any games if I dont have the keys extracted (by using kezplez) am I right?
4) can I use n1dus if im running atmosphere?

as always thanks in advance

1. Yes, you have to use the zip file in the ReiSwitched Discord server. None of the nightlies, GitHub releases, nor builds in the guide have 6.2 support
2. There is now a better homebrew application known as lockpick you can try out
3. You only need the keys from kezplez/lockpick for converting .XCI files into .NSP format or for installing .XCI files. Raw, unconverted .NSP files don't need keys to be installed
4. I do not see why not

 

[TPMJB]

Alright I fixed my many screw ups by just using TeamRCMGui and booting fusee-primary that way. Not sure why Hekate couldn't boot it though.

 

[Zap2000]

Again, as stated previously, for the time being no but eventually games/updates will require higher firmware so you will have to update at some point if you plan on playing the latest games/updates.
Nope.

1. Yes, you have to use the zip file in the ReiSwitched Discord server. None of the nightlies, GitHub releases, nor builds in the guide have 6.2 support
2. There is now a better homebrew application known as lockpick you can try out
3. You only need the keys from kezplez/lockpick for converting .XCI files into .NSP format or for installing .XCI files. Raw, unconverted .NSP files don't need keys to be installed
4. I do not see why not

1/ Ok my choices on 4.1 are just update normal and burn fuses

2/ Update and use autorcm

3/ use sysnand 4.1 with sx os 2.3 and emuNAND 6.1
Or
4/ Use sysnand 4.1 with sx os 2.4 on emuNAND 6.2 not sure if it work/boot or how to fix it/ update it after that.

Can u help me with them 4 options which would be most patical for me?