Hacking Tried to update atmosphere emunand on ipatched 4.1.0 and failed?

[Greedy_Boy]

Hello. Today i followed this caffeine guide https://switch.homebrew.guide on my ipatched 4.1.0 switch and it was succesfull (yes i have backups as guide says). And i tried to update atmospehere cfw emunand from 4.1.0 to latest 8.1.0 by following yet again this guide https://switch.homebrew.guide/usingcfw/manualupgrade As it says after preparations i started hekate -> launch cfw emunand -> ChoiDujourNX - > started update ( auto rcm was disabled by default), then pressed reboot and shutdown now, then deleted firmware folder. Started my switch but... it stucked on nintendo logo, oookay then i pressed power button and again started switch, it was successfull then joycon update poped up, after that i checked firmware and sadly it says 8.1.0 ... How if i started update from cfw ? now pegascape says that my firmware incompatible :/

Sorry if my English is bad But what can i do with backups from hekate now? can i downgrade somehow and why on the earth sysnand firmware was installed if i launched update from cfw emunand !? Heeelp!

 

[Lacius]

If you updated your sysNAND from 4.1.0 to 8.1.0, then there's a good chance you're forever without hacks on a patched system. The only solution is to restore your 4.1.0 NAND backup using a hardmod.

 

[Greedy_Boy]

If you updated your sysNAND from 4.1.0 to 8.1.0, then there's a good chance you're forever without hacks on a patched system. The only solution is to restore your 4.1.0 NAND backup using a hardmod.

is there hardmode guide? but first of all why this happened

 

[Lacius]

but first of all why this happened

You did something wrong and ran ChoiDujourNX from your sysNAND.

 

[tech3475]

If you updated your sysNAND from 4.1.0 to 8.1.0, then there's a good chance you're forever without hacks on a patched system. The only solution is to restore your 4.1.0 NAND backup using a hardmod.

Wont efuses prevent a downgrade?

 

[Lacius]

Wont efuses prevent a downgrade?

Yes, you are correct. You're screwed.

 

[Greedy_Boy]

And what purpose in this backups if they are useless...

 

[MachRc]

looks like hacking ipatched units is more troublesome than it is useful. Are there even any users out there playing games on this or setting up their ipatched units for their kids?

I imagine, it would only be super intelligent anime watching bookworm types that have the patience and time to achieve the caffiene hack in the first place, then keep constant

contact with the scene just to keep it running and working correctly?

lots of work and lots of risk

 

[Lacius]

And what purpose in this backups if they are useless...

In case you bricked your Switch in one of the many ways it can happen without burning efuses.

looks like hacking ipatched units is more troublesome than it is useful. Are there even any users out there playing games on this or setting up their ipatched units for their kids?

I imagine, it would only be super intelligent anime watching bookworm types that have the patience and time to achieve the caffiene hack in the first place, then keep constant

contact with the scene just to keep it running and working correctly?

lots of work and lots of risk

Having an unpatched Switch is highly recommended if one can help it. That being said, all issues I've seen like this have been caused by user error. It's not much different from the early 3DS days when people, for example, mistakenly updated the sysNAND instead of the emuNAND on Gateway 3DS.

 

[Basketto]

I have nfi how to downgrade via hardmod , but if he upgraded using Choi then in theory, should his efuses still be intact?

 

[Lacius]

I have nfi how to downgrade via hardmod , but if he upgraded using Choi then in theory, should his efuses still be intact?

The fuses have very likely been burnt. Restoring a NAND backup won't help him.

 

[smf]

And what purpose in this backups if they are useless...

They aren't useless, they just don't help in this circumstance. On ipatched systems they are only really useful if something bricks your switch, you have the ability to open the switch and flash the emmc & you haven't upgraded since the backup (you might get away with a minor downgrade, if it shares the same number of fuses).

You have to be really careful with ipatched units.

Although from the OP's description, I'm not sure what happened.

 

[bodefuceta]

Although from the OP's description, I'm not sure what happened.

He updated the system without burning fuses.
Then he booted it without RCM/hekate, and the bootloader should have burnt the fuses. So he can never downgrade.
Since it's ipatched, that means there's no way to hack the system anymore. But it still works. Though he might get banned if going online. Is what I think has happened.

 

[Lacius]

He updated the system without burning fuses.
Then he booted it without RCM/hekate, and the bootloader should have burnt the fuses. So he can never downgrade.
Since it's ipatched, that means there's no way to hack the system anymore. But it still works. Though he might get banned if going online. Is what I think has happened.

This all appears to be what happened. He's trapped on 8.1.0 with no way to downgrade and use hacks, and there's a good chance there will never be an exploit for 8.1.0 on patched systems.

Based on what he has done, there is also a chance it will get banned if it connects to the internet.

 

[bodefuceta]

I haven't heard of any exploit working on newer firmwares and it really looks like won't happen any time soon, but not all hope is lost yet. Every Switch Lite is in the same situation and that should boost interest in finding new exploits. Still I'm sorry for your loss, OP, go listen to some roki vulovic and drink rakia. You have waited long for this, failed, and now deserve a drink at least.

 

[smf]

He updated the system without burning fuses.

How do you do that without enabling autorcm? If you enable autorcm on sysnand on an ipatched unit then it will brick. He also said he didn't enable it.

 

[bodefuceta]

How do you do that without enabling autorcm? If you enable autorcm on sysnand on an ipatched unit then it will brick. He also said he didn't enable it.

I'm fairly sure it's an option in choidujourNX. Just not the default.

 

[smf]

I'm fairly sure it's an option in choidujourNX. Just not the default.

The option is called "prevent fuse burning (enable autorcm)"

That is bad news on an ipatched switch

https://switch.homebrew.guide/usingcfw/manualupgrade

WARNING
Never enable AutoRCM on an IPATCHED Switch
This is only intended to be used on consoles with a vulnerable RCM. Enabling AutoRCM on an IPATCHED Switch will literally BRICK your Switch.

So I don't think that was what happened to his sysnand as it still boots. My initial thought was he was still booted into emunand when it said it was running 8.1

 

[bodefuceta]

The option is called "prevent fuse burning (enable autorcm)"

That is bad news on an ipatched switch

https://switch.homebrew.guide/usingcfw/manualupgrade

WARNING
Never enable AutoRCM on an IPATCHED Switch
This is only intended to be used on consoles with a vulnerable RCM. Enabling AutoRCM on an IPATCHED Switch will literally BRICK your Switch.

So I don't think that was what happened to his sysnand as it still boots. My initial thought was he was still booted into emunand when it said it was running 8.1

He did not enable autoRCM! He says so in the OP.

 

[smf]

He did not enable autoRCM! He says so in the OP.

I know, you claimed "He updated the system without burning fuses." and the only way to do that is enable autorcm & not only did he say he didn't but if he had then his switch would be dead.

So that isn't what happened.