Accidentally Update OFW to 13.1.0 While Using HWFly/SX Chip + Atmos

[ijoin]

Hi
Hope someone can help me
I accidentally updated my Switch V2 OFW to 13.1.10, since then I always boot directly to OFW when restarting the switch
The switch itself is hacked by using modchip by either HWFly or SX (dunno which, but I'm pretty sure it is HWFly, since I googled it and the image is the same)

Any idea how to make it able to boot into CFW again?

Followed this tutorial with no success, the swtich still boot direcly to OFW
https://rentry.org/UpdateCFW

This is the screenshot for the files inside

 

[ijoin]

Bump
So far no hope

 

[s3m80]

Bump
So far no hope

search for kefir github its all in one solution just drop the file and update using hekate..uppss 13.1.10 sorry dude its not supported yet?

 

[ijoin]

search for kefir github its all in one solution just drop the file and update using hekate..uppss 13.1.10 sorry dude its not supported yet?

Seriously it's not supported yet?

 

[pr0dukt]

Man how does one "accidently update to newest OFW" and do it on their sysNAND at that? Did you not even have a emuNAND active when this happened? Nor did you have nin servers DNS blocked evidently...

The stars of bad decision making have to align just perfectly in the shape of a retard's football helmet for someone to somehow manage doing this after already running cfw on their switch for awhile. There are too many assets and methods on the wire to prevent accidents like this...

You might be fucked my guy, especially if you can't even get your switch back into RCM mode on boot.... Godspeed.

 

[ijoin]

Man how does one "accidently update to newest OFW" and do it on their sysNAND at that? Did you not even have a emuNAND active when this happened? Nor did you have nin servers DNS blocked evidently...

The stars of bad decision making have to align just perfectly in the shape of a retard's football helmet for someone to somehow manage doing this after already running cfw on their switch for awhile. There are too many assets and methods on the wire to prevent accidents like this...

You might be fucked my guy, especially if you can't even get your switch back into RCM mode on boot.... Godspeed.

Yeah, I maybe fucked
Already tried all the possible way to bring it back

cmon atleast there should be a way to cfw it again

 

[s3m80]

Seriously it's not supported yet?

seriously I dont get it is 13.1.0 or 13.1.10? if it 13.1 is supported

 

[ijoin]

seriously I dont get it is 13.1.0 or 13.1.10? if it 13.1 is supported

It's 13.1.0

 

[ijoin]

seriously I dont get it is 13.1.0 or 13.1.10? if it 13.1 is supported

Downloaded the kefir files and copy paste them into the sdcard, still boot directly into OFW with no option

 

[ijoin]

Edit, also tried to do this again
https://rentry.org/MarikoEmuNAND

Still nothing happened and it boots directly to OFW

 

[s3m80]

Edit, also tried to do this again
https://rentry.org/MarikoEmuNAND

Still nothing happened and it boots directly to OFW

can u boot into hekate?

 

[ijoin]

can u boot into hekate?

nope, but I fixed it now

Thanks

 

[ijoin]

Empty game title, any idea how to remove it?
Pressing the + button is useless

 

[Kallrkyle]

Man how does one "accidently update to newest OFW" and do it on their sysNAND at that? Did you not even have a emuNAND active when this happened? Nor did you have nin servers DNS blocked evidently...

The stars of bad decision making have to align just perfectly in the shape of a retard's football helmet for someone to somehow manage doing this after already running cfw on their switch for awhile. There are too many assets and methods on the wire to prevent accidents like this...

You might be fucked my guy, especially if you can't even get your switch back into RCM mode on boot.... Godspeed.

Must be nice to be so fu**ing perfect as you sound to be, congrats

 

[Kallrkyle]

nope, but I fixed it now

Thanks

So how did you fix it ?

 

[ijoin]

So how did you fix it ?

By using kefir files

Tahnks to @s3m80
Strange, since I followed other tutorial really precisely but it still not booting at all to hekate

 

[Halvorsen]

Man how does one "accidently update to newest OFW" and do it on their sysNAND at that? Did you not even have a emuNAND active when this happened? Nor did you have nin servers DNS blocked evidently...

The stars of bad decision making have to align just perfectly in the shape of a retard's football helmet for someone to somehow manage doing this after already running cfw on their switch for awhile. There are too many assets and methods on the wire to prevent accidents like this...

You might be fucked my guy, especially if you can't even get your switch back into RCM mode on boot.... Godspeed.

Why are we pretending that there is an issue with being on the latest firmware on sysNAND when that is the recommended and expected end result all users should be on at this moment?
Why is RCM relevant to this scenario at all? They are using a HWFly modchip.

...what are you even talking about?

 

[diarie2005]

Hi can it applicable as well for SXOS. Do the stupid thing accidently update it into new version as well.

 

[Jujube]

Hi can it applicable as well for SXOS. Do the stupid thing accidently update it into new version as well.

SxOS doesn‘t support OFW over 11.0.1 and never will. Sorry but you gotta switch to atmos

 

[diarie2005]

SxOS doesn‘t support OFW over 11.0.1 and never will. Sorry but you hotta switch to atmos

Yes @Jujube. That's its break. But after follow instruction in youtube i am totally move to atmosphere. The last problem faced is related to format of SD Card. Its should be using FAT32 instead of ExFAT. Thank you