Homebrew Question Had 6.2.0 CFW, but then UPDATED! Can I reverse it?

[FlareTech]

So I had homebrewed my Switch that was on 6.1.0 to 6.2.0 with Atmosphere and everything went fine. I was downloading some things off hb app store and everything was fine and dandy. However, I tried to play a game and it said software update available, and I thought like the previous homebrews that the CFW was thought to be the latest FW on the console and wouldnt ask to update. So, I pressed continue and in a matter of seconds the switch rebooted and I didn't have the CFW. Is there any way to reverse this?

I do not have any backups either

 

[Xenon Hacks]

I do not have any backups either

Taps.MP4

 

[iriez]

Since you updated it burned the fuse so if you choose to downgrade with choidejourNX you will have the issue with sleep mode.

Atmosphere 0.8.1 is out with 6.2.0 support. Why not just update a few files on your SD card? Much easier than all of this downgrade madness.

 

[FlareTech]

Since you updated it burned the fuse so if you choose to downgrade with choidejourNX you will have the issue with sleep mode.

Atmosphere 0.8.1 is out with 6.2.0 support. Why not just update a few files on your SD card?

Yeah I read about the fuse thing and heard about this Sleep Mode thing but what is it exactly? Also, what do you mean by "Updating a few files" ? I tried to inject the payload and got a fatal error. I am going to use this Switch as an offline switch for now because I bet it is too risky now for me to stay under the radar.

 

[notimp]

“I thought what I'd do was, I'd pretend I was one of those deaf-mutes."

What is the most depressing Sallinger quote for 200 points.

6.2.0 is cracked already - i can only speak from the perspective of an Atmosphere user - put simply use Atmosphere, put the sigpatches on the sdcard - and you are back to your CFW.

 

[FlareTech]

What is the most depressing Sallinger quote for 200 points.

6.2.0 is cracked already - i can only speak from the perspective of an Atmosphere user - put simply use Atmosphere, put the sigpatches on the sdcard - and you are back to your CFW.

Alright I will try to look up how to do that and try it. Ill let you know how it works out

 

[smf]

So I had homebrewed my Switch that was on 6.1.0 to 6.2.0 with Atmosphere and everything went fine.

I'm not sure what you mean? It sounds like you had atmosphere on 6.2

So, I pressed continue and in a matter of seconds the switch rebooted and I didn't have the CFW. Is there any way to reverse this?

Reverse what? If you were on 6.2 before and your switch said there was an update then you're still on 6.2. Unless there is a new version of 6.2 that nobody else has reported yet, then nothing has changed as there is no permanent CFW on Switch.

Just boot into RCM & inject atmosphere payload, like you have to do on every reboot.

If you were on 6.1 and now you're on 6.2 then update your payload and sd files first.

 

[The Dementor]

Sounds like it's just rebooted after restart into OFW, just need to inject payload agin

 

[FlareTech]

I pressed Continue on a Software Update while on CFW and I believe it updated to OFW. I had CFW 6.2 then updated by accident. I will update my files when I get home. Hopefully its as easy as we are saying it is...

 

[shchmue]

I pressed Continue on a Software Update while on CFW and I believe it updated to OFW. I had CFW 6.2 then updated by accident. I will update my files when I get home. Hopefully its as easy as we are saying it is...

it sounds like you're confused about where firmware lives, or else you're talking about SX OS emunand?

CFW lives on your SD card, period. there is no way presently to 'install' CFW. you boot CFW off your SD card. so it sounds like what happened is you did a game update or the exFAT update and it updated the firmware you have installed on your NAND. that means you probably burned fuses up to current (check in Hekate. 8 fuses == 6.2.0) unless you had BOOT0 protection from recent Atmosphere running and all you have to do is get into RCM and push your payload again.

 

[FlareTech]

it sounds like you're confused about where firmware lives, or else you're talking about SX OS emunand?

CFW lives on your SD card, period. there is no way presently to 'install' CFW. you boot CFW off your SD card. so it sounds like what happened is you did a game update or the exFAT update and it updated the firmware you have installed on your NAND. that means you probably burned fuses up to current (check in Hekate. 8 fuses == 6.2.0) unless you had BOOT0 protection from recent Atmosphere running and all you have to do is get into RCM and push your payload again.

Yeah that it was happened. I did have the latest Atmosphere but when I tried to push the payload again it failed. The firmware on my NAND was updated. I tried resetting my SD card files but it failed again. Can I downgrade then re-update to CFW 6.2?

 

[urherenow]

Yeah that it was happened. I did have the latest Atmosphere but when I tried to push the payload again it failed. The firmware on my NAND was updated. I tried resetting my SD card files but it failed again. Can I downgrade then re-update to CFW 6.2?

is your sd card still fat32? Do you use tegrarcmgui and did it indicate GREEN (rcm mode detected)? None of what you say makes any sense at all. If you were on 6.2 already and CFW was working, there's no way it magically stopped unless your sd card died. Any update while on 6.2 would either be burning fuses (if you booted without cfw) or updating joycon/cardslot/exfat.

 

[shchmue]

Atmosphere doesn't care which firmware version you're on. like the last commenter said there's something wrong with your SD or payload process

 

[FlareTech]

Thank you all for your help! I ended up having to format my SD card through my Switch and got a new batch of files for my Homebrew. It works now.

 

[urherenow]

Thank you all for your help! I ended up having to format my SD card through my Switch and got a new batch of files for my Homebrew. It works now.

So... perhaps you ejected the card with power on or something. Sounds exactly like it was corrupted. It'll happen again because it is most likely exFat now, so be sure to backup often.

 

[FlareTech]

So... perhaps you ejected the card with power on or something. Sounds exactly like it was corrupted. It'll happen again because it is most likely exFat now, so be sure to backup often.

Alrighty will do, thanks for the heads up!

 

[Csmrcc]

So I had homebrewed my Switch that was on 6.1.0 to 6.2.0 with Atmosphere and everything went fine. I was downloading some things off hb app store and everything was fine and dandy. However, I tried to play a game and it said software update available, and I thought like the previous homebrews that the CFW was thought to be the latest FW on the console and wouldnt ask to update. So, I pressed continue and in a matter of seconds the switch rebooted and I didn't have the CFW. Is there any way to reverse this?

I do not have any backups either

you can restore your backup