Question SDSetup + Atmosphere 0.92 (6f85b11) unable to access Hekate

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by gRoberts84, Jul 2, 2019.

  1. gRoberts84
    OP

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    Hi all,

    So, warmbooted with Caffeine (from SDSetup guide) on my 4.1.0 iPatched unit and hit the Atmosphere bug that was fixed last night.

    Problem is, when updating Atmosphere etc on my SD card, instead of loading Hekate, it boots directly into AMS 0.92.

    I need to create my EmuMMC partition and boot into that so I can start updating etc but I seem to have lost Hekate :(

    Can anyone shed some light beyond simply waiting for SDSetup to update their side?
     
  2. stick267

    stick267 GBAtemp Advanced Fan

    Member
    5
    Dec 17, 2018
    United States
    Turn off autoboot in the hekate_ipl.ini file in the bootloader folder on your SD card.
     
  3. gRoberts84
    OP

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    It's already off :(

    Code:
    [config]
    autoboot=0
    autoboot_list=0
    bootwait=1
    verification=1
    backlight=100
    autohosoff=0
    autonogc=1
    
    {AtlasNX/Kosmos v13}
    {}
    {Discord: discord.teamatlasnx.com}
    {Github: git.teamatlasnx.com}
    {Patreon: patreon.teamatlasnx.com}
    {Pegascape DNS: pegascape.sdsetup.com}
    {This bundle provided by SDSetup}
    {}
    
    {-- Custom Firmware --}
    [CFW]
    fss0=atmosphere/fusee-secondary.bin
    kip1patch=nosigchk
    atmosphere=1
    logopath=bootloader/bootlogo.bmp
    icon=bootloader/res/icon_payload.bmp
    {}
    
    {---- Miscellaneous ---}
    [Stock]
    fss0=atmosphere/fusee-secondary.bin
    stock=1
    icon=bootloader/res/icon_switch.bmp
    {}
    
    {--- FORCED SYSNAND ---}
    [CFW (EMUMMC Disabled)]
    emummc_force_disable=1
    fss0=atmosphere/fusee-secondary.bin
    kip1patch=nosigchk
    atmosphere=1
    logopath=bootloader/bootlogo.bmp
    icon=bootloader/res/icon_payload.bmp
    [Stock (EMUMMC Disabled)]
    emummc_force_disable=1
    fss0=atmosphere/fusee-secondary.bin
    stock=1
    icon=bootloader/res/icon_switch.bmp
    {}
    Basically took known working SDSetup SD card and copied across the Atmosphere 0.92 files.
     
  4. stick267

    stick267 GBAtemp Advanced Fan

    Member
    5
    Dec 17, 2018
    United States
    Hmmm I'm stumped then.
     
  5. gRoberts84
    OP

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    I'll try just SDSetup on it's own. Maybes they have already updated their end and I'm screwing with things (it said it was on 0.92 but would not boot CFW due to a bug in Atmosphere)
     
  6. Hayato213

    Hayato213 GBAtemp Guru

    Member
    11
    Dec 26, 2015
    United States
    If you want it to boot Hekate first then point it at payload=bootloader/payloads/hekate.bin , move the hekate 5.0.0 file there.
     
  7. gRoberts84
    OP

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    Stupid question, will no doubt deserve a stupid answer :D

    Where do I put that? I can't see anywhere so far that sets payload already.
     
  8. Hayato213

    Hayato213 GBAtemp Guru

    Member
    11
    Dec 26, 2015
    United States
    In the hekate.ipl if you want it to point toward that as autoboot, you can set it like this

    [Hekate]
    payload=bootloader/payloads/hekate.bin
     
  9. gRoberts84
    OP

    gRoberts84 Member

    Newcomer
    1
    Jul 1, 2019
    United Kingdom
    No dice :( Still boots directly into CFW.

    FYI, before updating Atmosphere, I would go to Fake News Injector and do the 5 second countdown and it'd boot into Hekate.

    Now when doing that, it goes straight to Atmosphere which loads CFW.
     
Loading...