Question [Atmosphere] Unknown pkg1 version '20190531152432' Failed to launch firmware

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by vernacular, Jun 21, 2019.

  1. vernacular
    OP

    vernacular Member

    Newcomer
    2
    Aug 30, 2010
    United States
    USA
    After updating my firmware to 8.1.0 using ChoiDujourNX (everything seemed to go fine without errors) I cannot launch Atmosphere. I have the latest SDfiles and latest Hekate, but Atmosphere doesn't auto-boot and when I try to launch it in Hekate I get an error:

    Initializing...
    Found pkg1 <'20190531152432'>.
    Unknown pkg1 version.
    Failed to launch firmware.

    Is my firmware broken or not recognized by Atmosphere? I have a NAND backup, but it's all the way back on version 1.0.0 and I don't know how to restore it. I have auto-RCM enabled. AFAIK I have never booted into the original firmware and have never burned fuses, but my joycons did receive a firmware update when I accidentally tapped on a persistent update nag for the joycons.
     
  2. FedDiSte

    FedDiSte Advanced Member

    Newcomer
    1
    Jun 19, 2019
    Italy
    You have to select "payloads" and then "fusee-primary.bin"
    Hekate can't boot 8.1.0 so you have to launch that
     
    Milad and vernacular like this.
  3. Hayato213

    Hayato213 GBAtemp Guru

    Member
    12
    Dec 26, 2015
    United States
    Use Fusee Primary instead of Hekate for now as it doesn't support it yet.
     
    vernacular likes this.
  4. vernacular
    OP

    vernacular Member

    Newcomer
    2
    Aug 30, 2010
    United States
    USA
    Yes! It does successfully boot if I just load "fusee-primary.bin" in Hekate.
    So it's just Hekate? Thanks a lot, fellas. I was super worried that I screwed something up there.

    If I push the "fusee-primary.bin" payload from Rekado (on my phone) I can get directly into Atmosphere, but is it okay to do that? Do I need to push the Hekate payload first for any reason?
     
    Swiminaha likes this.
  5. Hayato213

    Hayato213 GBAtemp Guru

    Member
    12
    Dec 26, 2015
    United States
    Fusee primary is for Atmosphere only, Hekate does have extra feature such as NAND backup , NAND restore, and ability to print fuse info and battery info. Both are bootloader, Personally I used Hekate to boot Fusee Primary to boot Atmosphere.
     
  6. vernacular
    OP

    vernacular Member

    Newcomer
    2
    Aug 30, 2010
    United States
    USA
    I thought Hekate's auto-boot feature was simply loading that payload automatically, but now auto-boot doesn't work and I have to specifically go in and launch "fusee-primary.bin". I don't really need to use Hekate until I screw something up badly, but if Hekate gets updated auto-boot will work again and I can push the Hekate payload as I did before. If I ever need Hekate I know I can hold volume down when pushing the payload to bypass auto-boot settings and get back into Hekate.

    This got me thinking though. Hypothetically, if I ever had to restore my NAND backup which is firmware 1.0.0 would that Joycon update cause my joycons to not function on that old firmware or would they be fine? AFAIK Joycon firmware cannot be downgraded.
     
  7. Hayato213

    Hayato213 GBAtemp Guru

    Member
    12
    Dec 26, 2015
    United States
    You have to configure hekate.ipl for it to point at fusee-primary, for it to autoboot, just wait for Kosmos to update their pack, they gonna have to wait until ctcaer update his.
     
  8. vernacular
    OP

    vernacular Member

    Newcomer
    2
    Aug 30, 2010
    United States
    USA
    So in hekate.ipl you'd change this part:

    {-- Custom Firmwares --}
    [CFW]
    fss0=atmosphere/fusee-secondary.bin
    kip1patch=nosigchk
    atmosphere=1
    logopath=bootloader/bootlogo.bmp
    { }

    to this:

    {-- Custom Firmwares --}
    [CFW]
    fss0=bootloader/payloads/fusee-primary.bin
    kip1patch=nosigchk
    atmosphere=1
    logopath=bootloader/bootlogo.bmp
    { }

    and that would fix auto-boot, but it would probably be better just to wait for the Hekate update.
     
  9. Hayato213

    Hayato213 GBAtemp Guru

    Member
    12
    Dec 26, 2015
    United States
    No, just leave it you need Kosmos and Ctcaer to update their files, top one is correct.
     
    Milad likes this.
  10. vernacular
    OP

    vernacular Member

    Newcomer
    2
    Aug 30, 2010
    United States
    USA
    Okay, I'll just leave it be.
     
  11. Akion94

    Akion94 Newbie

    Newcomer
    1
    Jun 23, 2019
    United States
    Also have the same problem after updating my switch to 8.1.0. But the problem is when I tried to use Fusee Primary instead of Hekate, my screen just turned black and nothing happened. If I hold the power button again, it just boots to stock firmware again. Does anyone know what is the problem here?
     
  12. FedDiSte

    FedDiSte Advanced Member

    Newcomer
    1
    Jun 19, 2019
    Italy
    You have to launch "fusee-primary.bin"
     
  13. MisterPantsEyes

    MisterPantsEyes GBAtemp Fan

    Member
    5
    Jan 10, 2015
    Germany
    I have the same problem. fusee-primary.bin only gives me a black screen.
     
    Last edited by MisterPantsEyes, Jun 23, 2019
  14. Zidapi

    Zidapi GBAtemp Psycho!

    Member
    11
    Dec 1, 2002
    Resend Atmos payload at black screen as a short term solution until hekate is updated.
     
    Milad likes this.
  15. Peanut42

    Peanut42 Member

    Newcomer
    2
    Jun 27, 2015
    Mexico
    Sorry for begin so repetitive, but I don't understand the "short term solution".

    I have the same problem as everybody, auto-rcm enabled. Which payload should I send first when the RCM mode enters?

    When you say "Atmos payload" what file from atmos (0.9.1) do you mean?

    Thanks for the pattience.
     
  16. FedDiSte

    FedDiSte Advanced Member

    Newcomer
    1
    Jun 19, 2019
    Italy
    The atmos payload is "fusee-primary.bin" located in "payloads" menu in hekate
     
  17. Peanut42

    Peanut42 Member

    Newcomer
    2
    Jun 27, 2015
    Mexico
    I tried to launch that payload from the Launch menu in Hekate and didn't work, got a black screen. actually, before going black, the letters "Welcome to Atmosphere" appear.
    I'm starting to think that the Atmosphere is not up to date, but I downloaded yesterday (6/23) from sdsetup.com
     
  18. FedDiSte

    FedDiSte Advanced Member

    Newcomer
    1
    Jun 19, 2019
    Italy
    Maybe is that.
    Try to download from github
     
  19. Peanut42

    Peanut42 Member

    Newcomer
    2
    Jun 27, 2015
    Mexico
    Yes, it was the old Atmosphere. But, now I got a different error.
    Can somebody suggest me an updated guide to download and re-arm the SD card?
     
  20. Iwanko

    Iwanko Newbie

    Newcomer
    1
    Jun 25, 2019
    United States
    Monroe, WA
    i updated to 8.1.0 by accident, got a blank screen, i updated the version of atmosphere from 0.8.9 to 0.9.1 now it boots but i think its still in stock, it says all the games are broken/corrupt and i cant access the HBmenu.. am i missing something?

    is the fw located on the nand? can i roll back to the 4.2 nand backup i made and then update back to 8.0.1?
    (only 5 fuses are burnt)
    sorry for so many questions at once
     
Quick Reply
Draft saved Draft deleted
Loading...