Hacking Mistake while updating to 8.1.0, now PKG1 error, what should i do?

[Mycx]

Hello everyone, i'll just explain what stupid mistake i've done and hope that there's some way to fix this mess.

My Switch had version 7.0.1 using Kosmos 12 release, yesterday i updated Kosmos to the latest release which is 12.2 and that supports up to switch ver 8.0.1, but while on the github i misread the information and thought it supported up to 8.1.0 so i went ahead and connected my switch to the wi-fi, downloaded the update and installed ver 8.1.0, that's when i realized i was still in the CFW and didn't switch out to OFW before trying to update the legit way (Yeah, i know i could've used ChoiDujourNX but i realized that kinda too late).
So what happened is that after the update was done i think the switch rebooted, but froze up suddendly (It wouldn't enter RCM or accept any payloads i tryed to send to it), after force-shutting it down i rebooted in RCM and found myself in Hekate, then i proceeded to try and launch CFW but it showed up "Found PKG1 ('20190531152432'). Unknown PKG1 version. Failed to launch firmware.", so i tryed to update the fusee-primary.bin as some people suggested on other threads but it obviously wouldn't work since the Atmosphere loaded on the latest version of Kosmos doesn't support 8.1.0 yet.
I tryed launching OFW from Hekate and the same PKG1 error appears on screen, so i can't boot in both CFW and OFW.

So what have i done now? Leaving the current CFW version aside, is there a way to restore the OFW? Is it just AutoRCM that is somehow messing up with the OFW right now? Was it because i updated while inside CFW?

Any kind of help would be immensely appreciated

 

[Hayato213]

boot via fusee primary.

 

[Mycx]

boot via fusee primary.

As stated in the midst of the above post, i already updated the Fusee primary and tryed booting through it, but it still wouldn't work.
The text "Welcome to amosphere fusee" appears on the screen for a brief second and the screen just goes black.

 

[Hayato213]

You have to launch fusee primary, not through Hekate, hekate doesn't support 8.1.0 yet.

 

[Mycx]

Just tryed a bunch of times sending directly fusee primary, but the same thing happened, "Welcome to amosphere fusee"! and then it goes black (It is not in RCM mode as it doesn't accept any payloads)

 

[Hayato213]

Did you try a clean build of atmosphere not with Kosmos file?

 

[redmagejosh]

Hi @Mycx,

Ok, you need to update the atmosphere and sept forlders with the latests ones, which you can find in github (delete the old ones from the SD first then copy the new atmosphere and sept folders)
Also, you'll need to adquire the sigpatches for version 8.1.0 which are around here in the forum, a quick search shall lead you to them.
The sigpatches zip file you'll get needs to be decompressed into the SD card as well (it will be an atmosphere folder, but don't worry it will merge with the existing one)
After doing that you should be able to push fusee_primary and boot. If you still want to use Hekate, you can make Hekate auto boot to the fusee_primary payload, it is just extra steps but I know it is possible as I had to help a friend do this since he is using a chip RCM86 and had no way of flashing it and all he had was hekate.

 

[Mycx]

Did you try a clean build of atmosphere not with Kosmos file?

Yes and it wouldn't work

I just removed everything from the SD card except for the Nintendo folder and copied in the fresh Atmosphere and it worked, i am now booted into the CFW (Because i can access homebrew through the Album) but no NSP that i have installed will start, i probably need the sigpatches that Nekojosh mentioned and i should be okay.

Thank you both for lending me a hand, i'm grateful.
Have a good day!

 

[Hayato213]

Yes and it wouldn't work

I just removed everything from the SD card except for the Nintendo folder and copied in the fresh Atmosphere and it worked, i am now booted into the CFW (Because i can access homebrew through the Album) but no NSP that i have installed will start, i probably need the sigpatches that Nekojosh mentioned and i should be okay.

Thank you both for lending me a hand, i'm grateful.
Have a good day!

Yea you need the sig patches for the games.

 

[aaron0791]

I sadly also updated my Switch to 8.1 from 6.0 using ChoiDujourNX, now i cannot boot into my switch. I read the thread and I saw they said I had to updated my atmosphere, i thought I had the latest version since I used the sdsetup. I went to github to download the latest atmosphere version, but they dont offer a built up version of their software, but a lot of folders with make files. I don't know how to compile them.

Is there anyway to fix this issue? a friendly way to fix it, without programming?

Thanks in advanced.

edit: there is a github page that does not give you the master code, but instead a built version in case anyone is having difficulties finding these folders.

--------------------- MERGED ---------------------------

I updated to the latest atmosphere, now everytime my switch boots, it loads everything fine and after a few seconds atmosphere crashes down and i have to restart it.

Good times.

 

[jimong]

Hello everyone, i'll just explain what stupid mistake i've done and hope that there's some way to fix this mess.

My Switch had version 7.0.1 using Kosmos 12 release, yesterday i updated Kosmos to the latest release which is 12.2 and that supports up to switch ver 8.0.1, but while on the github i misread the information and thought it supported up to 8.1.0 so i went ahead and connected my switch to the wi-fi, downloaded the update and installed ver 8.1.0, that's when i realized i was still in the CFW and didn't switch out to OFW before trying to update the legit way (Yeah, i know i could've used ChoiDujourNX but i realized that kinda too late).
So what happened is that after the update was done i think the switch rebooted, but froze up suddendly (It wouldn't enter RCM or accept any payloads i tryed to send to it), after force-shutting it down i rebooted in RCM and found myself in Hekate, then i proceeded to try and launch CFW but it showed up "Found PKG1 ('20190531152432'). Unknown PKG1 version. Failed to launch firmware.", so i tryed to update the fusee-primary.bin as some people suggested on other threads but it obviously wouldn't work since the Atmosphere loaded on the latest version of Kosmos doesn't support 8.1.0 yet.
I tryed launching OFW from Hekate and the same PKG1 error appears on screen, so i can't boot in both CFW and OFW.

So what have i done now? Leaving the current CFW version aside, is there a way to restore the OFW? Is it just AutoRCM that is somehow messing up with the OFW right now? Was it because i updated while inside CFW?

Any kind of help would be immensely appreciated

I updated mine earlier to the latest firmware. I went to sd setup website and updated kosmos from there. Make sure to select (check) "Enable signature patches" before you download your zip. I played my games without problems.

 

[PHiLiPZ]

There’s a new 12.99 Kosmos available https://github.com/AtlasNX/Kosmos/releases which supports 8.1.0.

 

[Hayato213]

There’s a new 12.99 Kosmos available https://github.com/AtlasNX/Kosmos/releases which supports 8.1.0.

It says wait for full release.

 

[PHiLiPZ]

It says consider waiting, not wait. The reason is cause the next one hopefully won’t have to chainload fusee-primary from hekate. If they released it it’s better than the previous release with copied new Atmosphere on top. They even say it contains the new Atmosphere and 8.1 support.

It could get rid of the many posts about not working pkg1 from hekate after the update.

PS: I didn’t quote your post but since it’s right above mine I’d find it just a waste of space