Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

ChoidujourNX does support 6.2.0, ChoiDujour for PC does not.

Currently boot just gives me an ugly blue screen. Is there no method by which I can get 6.2.0 on my NAND without having a backup of that version?

What happen when you try to load Atmosphere, still blue screen?

 

[xPatsy]

What happen when you try to load Atmosphere, still blue screen?

I'd have to get up on Atmos to try it out.
I had been rolling ReiNX for awhile. That one, on boot, was throwing " package2 magic invalid " Their documentation, and much of the internet, says the most common reason for this is an old version of CFW running. That shouldn't be the case, I tried using the most recent version of it and my backup should only be older in time.

 

[Hayato213]

I'd have to get up on Atmos to try it out.
I had been rolling ReiNX for awhile. That one, on boot, was throwing " package2 magic invalid " Their documentation, and much of the internet, says the most common reason for this is an old version of CFW running. That shouldn't be the case, I tried using the most recent version of it and my backup should only be older in time.

Try the latest Kosmos and Atmosphere files, if you can't boot you might have to rebuild your nand.

 

[xPatsy]

Try the latest Kosmos and Atmosphere files, if you can't boot you might have to rebuild your nand.

Okay, thank you.

If I go through rebuilding the NAND, is it expected that CFW should boot even if the fuses aren't proper?
i.e. I could load CFW of 6.0.1 with fuses requiring 6.2 as long as it's loading Atmosphere and not OFW?

 

[Hayato213]

Okay, thank you.

If I go through rebuilding the NAND, is it expected that CFW should boot even if the fuses aren't proper?
i.e. I could load CFW of 6.0.1 with fuses requiring 6.2 as long as it's loading Atmosphere and not OFW?

Yes but only if it boot properly, worth a try to see if it still boot into CFW.

 

[xPatsy]

Yes but only if it boot properly, worth a try to see if it still boot into CFW.

Okay. I'm getting pkg2 decryption failed on atmos as well. I guess something went wrong with my backup / recov process. I'll rebuild NAND for 6.0.1 and come back here if I have any other troubles.

Thanks

 

[DrDoctor]

If a 3.0.0 Switch is updated directly to 7.0.1, will it burn a single e-fuse, or all e-fuses it would've otherwise burn if it had been updated version by version?

 

[Hayato213]

If a 3.0.0 Switch is updated directly to 7.0.1, will it burn a single e-fuse, or all e-fuses it would've otherwise burn if it had been updated version by version?

You burn fuse when you update via nintendo server update, only through autoRCM and ChoidujourNX you preserve your fuse.

 

[NFates]

If a 3.0.0 Switch is updated directly to 7.0.1, will it burn a single e-fuse, or all e-fuses it would've otherwise burn if it had been updated version by version?

Firmware versions have a set amount of required burned fuses to run, which goes up every new major update. In other words, it's the same.

 

[DrDoctor]

Firmware versions have a set amount of required burned fuses to run, which goes up every new major update. In other words, it's the same.

So it would burn a X fuses per update that was release between 3.0.0 and 7.0.1, okay.

Firmware versions have a set amount of required burned fuses to run

So how does normal firmware run if you use autoRCM to keep fuses from burning?
Can't Nintendo detect how many fuses were/weren't burned and ban a system?

 

[NFates]

So it would burn a X fuses per update that was release between 3.0.0 and 7.0.1, okay.

So how does normal firmware run if you use autoRCM to keep fuses from burning?
Can't Nintendo detect how many fuses were/weren't burned and ban a system?

Bootloaders other than Nintendo's, like Hekate, won't check fuses, so you can be either under the required amount (which would have burned fuses) or over the required amount (which would have led to the system not starting Horizon).

 

[DrDoctor]

Bootloaders other than Nintendo's, like Hekate, won't check fuses, so you can be either under the required amount (which would have burned fuses) or over the required amount (which would have led to the system not starting Horizon).

So what's the recommended steps to have a modded offline/up-to-date online system? With an unpatched system, in this case.
From what I understand, I need to burn fuses to get 7.0.1 to run.
I guess that if I do a 3.0.0 NAND backup and then update to 7.0.1, that backup is useless because it probably won't run due to the burned fuses.

 

[NFates]

So what's the recommended steps to have a modded offline/up-to-date online system? With an unpatched system, in this case.
From what I understand, I need to burn fuses to get 7.0.1 to run.
I guess that if I do a 3.0.0 NAND backup and then update to 7.0.1, that backup is useless because it probably won't run due to the burned fuses.

As Hayato said,

You burn fuse when you update via nintendo server update, only through autoRCM and ChoidujourNX you preserve your fuse.

if you get your firmware files (don't ask me where, a quick Google search should suffice) and update through ChoiDujourNX, you won't burn fuses. Be wary of not entering RCM at startup though, as that will cause you to burn fuses. AutoRCM is recommended to eliminate said possiblity.

And because you won't have burned fuses, the backup is usable. Though even if you had burned fuses, restoring the backup and loading Horizon through Hekate (or another non-Nintendo bootloader) is possible.

 

[DrDoctor]

if you get your firmware files (don't ask me where, a quick Google search should suffice) and update through ChoiDujourNX, you won't burn fuses. Be wary of not entering RCM at startup though, as that will cause you to burn fuses. AutoRCM is recommended to eliminate said possiblity.

I understood that, but is it safe to go online by booting the normal current firmware from AutoRCM?
Does AutoRCM "fool" the firmware to think the fuses have been burned?
Does it also "fool" the servers?

 

[NFates]

I understood that, but is it safe to go online by booting the normal current firmware from AutoRCM?
Does AutoRCM "fool" the firmware to think the fuses have been burned?
Does it also "fool" the servers?

A yes or no answer to that is out of my knowledge, but you could simply block Nintendo from checking by using 90DNS.

 

[xPatsy]

Yes but only if it boot properly, worth a try to see if it still boot into CFW.

So I went through the steps for putting 6.1.0 on, tried booting Atmos.
I get no errors but the follow happens:
Starts booting, I see the splash screen associated with the hekate payload I've pushed.
I then see the Nintendo logo
A few moments later, Nintendo logo disappears and I'm sitting at a black screen. No backlight appears to be on.

I've tried booting without RCM and I get nothing, not even the blue kernel panic I saw prior.

I can still enter RCM, can still mount partitions in hactool... Unsure how to proceed from here.

 

[DrDoctor]

A yes or no answer to that is out of my knowledge, but you could simply block Nintendo from checking by using 90DNS.

I see. That also blocks the eshop, correct?
I was hoping to be able to use the system normally online, and if I couldn't use it modded offline, at least be able to future-proof it for when the console is no longer supported

 

[Hayato213]

So I went through the steps for putting 6.1.0 on, tried booting Atmos.
I get no errors but the follow happens:
Starts booting, I see the splash screen associated with the hekate payload I've pushed.
I then see the Nintendo logo
A few moments later, Nintendo logo disappears and I'm sitting at a black screen. No backlight appears to be on.

I've tried booting without RCM and I get nothing, not even the blue kernel panic I saw prior.

I can still enter RCM, can still mount partitions in hactool... Unsure how to proceed from here.

Rebuild it for 6.2.0

 

[xPatsy]

Rebuild it for 6.2.0

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/ relies on using ChoiDojour which doesn't support up to 6.2.0, I'm not able to boot in to any running firmware on the switch to run, say, ChoiDojourNX to push that update.
What tool should I use to build for 6.2.0?

Thank you,

-- Edit --

Okay, I believe I've fixed it. At the very least I've now got a booting Switch to work further from.
The problem was that the kip file in the last step didn't get ran properly.
It was kind of a catch-22... Couldn't launch atmosphere as-is WITH the kip file, and launching Stock would lock, I believe due to the fuses.

So I edited the hekate_ipl.ini file for atmosphere to include this for kip1. It was unable to launch with the kip1patch of nosigchk, so I removed that line and just loaded my one kip1, boot atmos.

I'm not at the initial set up screen, hopefully I can get through this and get an okay system rolling.
Thanks for the help.

 

[Hayato213]

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/ relies on using ChoiDojour which doesn't support up to 6.2.0, I'm not able to boot in to any running firmware on the switch to run, say, ChoiDojourNX to push that update.
What tool should I use to build for 6.2.0?

Thank you,

Look like you need to find something that force you to update to 6.2.0,

6.2.0 Game Updates

Xenoblade Chronicles 2 [UPD][v917504]
Aces of the Luftwaffe Squadron [UPD][v262144]

So these might work?