Error while loading fss0 nintendo switch

Error while loading fss0: atmosphere/package3 Wrong ini cfg or missing/corrupt files! Failed to launch HOS! After creating an emummc, I get this error when trying to launch it, I'm fucking clueless what to do, please help
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Joined
Oct 27, 2021
Messages
18
Trophies
0
Age
19
XP

65

Country

Ecuador

  • #1

Error while loading fss0:
atmosphere/package3
Wrong ini cfg or missing/corrupt files!
Failed to launch HOS!

After creating an emummc, I get this error when trying to launch it, I’m fucking clueless what to do, please help

  • #2

Check your hekate_ipl if you have a fusee-secondary.bin your line that why it won’t boot. Read the change log for Atmosphere 1.0.0

Joined
Oct 27, 2021
Messages
18
Trophies
0
Age
19
XP

65

Country

Ecuador

  • #3

Check your hekate_ipl if you have a fusee-secondary.bin your line that why it won’t boot. Read the change log for Atmosphere 1.0.0

[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

No fusee-secondary.bin in sight. That’s not the issue here

  • #4

[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

No fusee-secondary.bin in sight. That’s not the issue here

Replace your CFW files from where you previously get your fss0 build. Also update your hekate if it outdated.

Joined
Oct 27, 2021
Messages
18
Trophies
0
Age
19
XP

65

Country

Ecuador

  • #5

Replace your CFW files from where you previously get your fss0 build. Also update your hekate if it outdated.

How do I do that?

  • #6

Look at the folder that you get your CFW files from and replace them.

Joined
Oct 27, 2021
Messages
18
Trophies
0
Age
19
XP

65

Country

Ecuador

  • #7

omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

  • #8

omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

re add to root. aswell as sigpatches if u need and your exosphere if you used to block nintendo.

  • #9

Look at the folder that you get your CFW files from and replace them.

Reading the release and main page of the Atmosphère and Hekate repos on GitHub. Or reading the so many posts and guides existing here on GBATEMP.

  • #10

Reading the release and main page of the Atmosphère and Hekate repos on GitHub. Or reading the so many posts and guides existing here on GBATEMP.

My post earlier said Atmosphere 1.0.0 changelog

  • #11

It doesn’t show on my web browser after I put the post.

Draxzelex

  • #12

omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

Download the /atmosphere folder, put it on the root of your SD card, and make sure the SD card is formatted to FAT32.

  • #13

Check your hekate_ipl if you have a fusee-secondary.bin your line that why it won’t boot. Read the change log for Atmosphere 1.0.0

i do have it what would i do then?

  • #14

i do have it what would i do then?

You replace the specified fusee-primary.bin with fusee.bin and fusee-secondary.bin with package3, and also update your CFW files.

  • #15

You replace the specified fusee-primary.bin with fusee.bin and fusee-secondary.bin with package3, and also update your CFW files.

not entirely sure what those are but i can give you a layout of what i’m using right now and send a link to my current thread so we don’t accidentally revive this one https://gbatemp.net/threads/corrupted-files.603421/

  • #16

[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1

{— Custom Firmware —}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{— Stock —}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

If you use fusee.bin as bootloader , then it would be

[Atmosphere]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_atmosphere.bmp

  • #17

You replace the specified fusee-primary.bin with fusee.bin and fusee-secondary.bin with package3, and also update your CFW files

we can continue here if you’d prefer

  • #19

it’s now showing

failed to apply ‘nosigchk’
press POWER to continue
press VOL to go to the menu

  • #20

pressed VOL and got

failed to launch HOS
press any key

Similar threads

Draxzelex

You may also like…

  • No one is chatting at the moment.

    Содержание

    1. Error while loading fss0 — pls help
    2. ShowtimevonParty
    3. Hayato213
    4. ShowtimevonParty
    5. Hayato213
    6. ShowtimevonParty
    7. Hayato213
    8. ShowtimevonParty
    9. Chaosta
    10. impeeza
    11. Hayato213
    12. impeeza
    13. Draxzelex
    14. Felix12332
    15. Hayato213
    16. Felix12332
    17. Hayato213
    18. fss0 loaded is not the updated one [Solved. Wrong config path was used] #638
    19. Comments
    20. Error While loading fss0 — Any advice would be great!!
    21. Zay475
    22. hartleyshc
    23. Zay475
    24. Zay475
    25. Zay475
    26. Badablek
    27. Zay475
    28. kidkat210
    29. Badablek
    30. Zay475
    31. Fix: Error while loading FSS0 atmoshpehere/fusee-secondary.bin wrong ini cfg
    32. Check your SD card
    33. Update Atmosphere and Hekate
    34. Replace your configuration files
    35. Check the EMUMMC partition
    36. Replace fusee files
    37. error while loading fss0 , help?
    38. st4ticbuzz
    39. Shadow#1
    40. binkinator

    Error while loading fss0 — pls help

    ShowtimevonParty

    Member

    Error while loading fss0:
    atmosphere/package3
    Wrong ini cfg or missing/corrupt files!
    Failed to launch HOS!

    After creating an emummc, I get this error when trying to launch it, I’m fucking clueless what to do, please help

    Hayato213

    ShowtimevonParty

    Member

    [config]
    autoboot=0
    autoboot_list=0
    autohosoff=1
    autonogc=1
    backlight=100
    bootwait=3
    updater2p=0

    [CFW (sysMMC)]
    emummc_force_disable=1
    fss0=atmosphere/package3
    icon=bootloader/res/icon_payload.bmp

    [CFW (emuMMC)]
    emummcforce=1
    fss0=atmosphere/package3
    icon=bootloader/res/icon_payload.bmp

    [Stock]
    emummc_force_disable=1
    fss0=atmosphere/package3
    icon=bootloader/res/icon_switch.bmp
    stock=1

    [Fusee]
    icon=bootloader/res/icon_payload.bmp
    payload=bootloader/payloads/fusee.bin

    No fusee-secondary.bin in sight. That’s not the issue here

    Hayato213

    [config]
    autoboot=0
    autoboot_list=0
    autohosoff=1
    autonogc=1
    backlight=100
    bootwait=3
    updater2p=0

    [CFW (sysMMC)]
    emummc_force_disable=1
    fss0=atmosphere/package3
    icon=bootloader/res/icon_payload.bmp

    [CFW (emuMMC)]
    emummcforce=1
    fss0=atmosphere/package3
    icon=bootloader/res/icon_payload.bmp

    [Stock]
    emummc_force_disable=1
    fss0=atmosphere/package3
    icon=bootloader/res/icon_switch.bmp
    stock=1

    [Fusee]
    icon=bootloader/res/icon_payload.bmp
    payload=bootloader/payloads/fusee.bin

    No fusee-secondary.bin in sight. That’s not the issue here

    ShowtimevonParty

    Member

    Hayato213

    ShowtimevonParty

    Member

    omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

    I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

    Chaosta

    Well-Known Member

    omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

    I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

    impeeza

    ¡Kabito!

    Hayato213

    impeeza

    ¡Kabito!

    Draxzelex

    Well-Known Member

    omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

    I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

    Felix12332

    Well-Known Member

    Hayato213

    Felix12332

    Well-Known Member

    Hayato213

    [config]
    autoboot=0
    autoboot_list=0
    bootwait=3
    verification=1
    backlight=100
    autohosoff=0
    autonogc=1
    updater2p=1

    Источник

    fss0 loaded is not the updated one [Solved. Wrong config path was used] #638

    Note: I’m not 100% sure on the technical terms of things, but I’ll do my best. Sorry!

    I dug my switch out to play Pokemon Unite. I set it up a while ago with an EmuNAND and SysNAND, as I think they’re called? Basically, I can boot to stock and go online to play games I own, or boot into CFW (Atmosphere) to play ROMS and use homebrew. Switching back and forth between them via Hekate worked fine.

    I upgraded the firmware on my EmuNAND using Daybreak, and updated Atmosphere. No issues booting into EmuNAND.

    Today I booted into stock, upgraded the firmware via the HOS updater (to 12.1.0) and played a bunch of Pokemon Unite. Awesome! But then I tried to boot into hekate and I noticed autorcm had been turned off. I’m not worried about downgrading or burning fuses or whatever, so I just got back into RCM via the jig, turned on AutoRCM via Hekate, then booted into EmuNAND. Everything seemed to be working fine. However, when I turned off my system and tried to boot into Stock via Hekate, it gives me the following error (with logging on):

    Also, my understanding of how this works is that it shouldn’t be booting into Atmosphere CFW at all, but into the Stock HOS. Am I doing something wrong? I downloaded the latest atmosphere and extracted it to the root of my SD card, and booted with the latest Hekate as well.

    EDIT: Here is my hekate_ipl.ini as well, if that helps:

    The text was updated successfully, but these errors were encountered:

    Источник

    Error While loading fss0 — Any advice would be great!!

    Zay475

    Well-Known Member

    I have been in the process of hacking my Switch and had it almost there, I struggled to get awoo or tinfoil working and eventually settled on Goldleaf, however only some games would install and others would say I was missing sigpatches.

    I looked all over but the advice was conflicting and I decided to try Awoo again, I was installing the games from the sd card via Goldleaf and so tried to do the same with Awoo.

    Awoo ran into the same problems and i was offered the option to update to the latest Awoo firmware? At least I think that’s what it said!! Anyway once I’d done it, I now can not load into the Switch at all. everytime I press launch I am greeted with the following;

    Error while loading fss0:
    atmosphere/fusee-secondary.bin
    Wrong ini cfg or missing/corrupt files

    Failed to launch HOS!

    can anyone help me sort this? It’s so frustrating as even when I get back to where i was I’m still stuck only being able to install certain games lol

    I am on the latest build of atmosphere as far as I know.

    Should I hard reset and start all over again and if so does anyone know a more reliable way to install games?

    Any help would be massively appreciated.

    hartleyshc

    Well-Known Member

    Whatever you had set up before is old. Fusee primary and secondary have been deprecated.

    I don’t use awoo but it sounds like you upgraded Atmosphere with it.

    Just start fresh with the guide above.

    Sent from my Pixel 4 XL using Tapatalk

    Zay475

    Well-Known Member

    Whatever you had set up before is old. Fusee primary and secondary have been deprecated.

    I don’t use awoo but it sounds like you upgraded Atmosphere with it.

    Just start fresh with the guide above.

    Sent from my Pixel 4 XL using Tapatalk

    Zay475

    Well-Known Member

    thanks for the reply! Should I hard reset and is this an easier way to install games with this technique? I‘ m worried that I’ll end up back in the same situation lol.

    Zay475

    Well-Known Member

    Badablek

    Well-Known Member

    @Zay475 you’re using (probably) an old Hekate, with an old fusee-primary, to launch the latest Atmosphere. it can’t work.

    you don’t need to reset anything.

    Update Hekate to 5.6.5
    Update Atmosphere AND sigpatches to 1.2.5
    Edit bootloaderhekate_ipl.ini :

    ps : if you’re not using hekate, use latest 1.2.5 fusee.bin to launch Atmosphere

    Zay475

    Well-Known Member

    @Zay475 you’re using (probably) an old Hekate, with an old fusee-primary, to launch the latest Atmosphere. it can’t work.

    you don’t need to reset anything.

    Update Hekate to 5.6.5
    Update Atmosphere AND sigpatches to 1.2.5
    Edit bootloaderhekate_ipl.ini :

    ps : if you’re not using hekate, use latest 1.2.5 fusee.bin to launch Atmosphere

    Hi there, thanks! I know I’m using the latest Hecate and pretty sure I have the sigpatches, but I haven’t altered .ini.

    i‘ll give it a shot! If I can get back to where I was, what would you suggest is the best way to install games? Tinfoil wouldn’t recognise my usbf and gold leaf only let me install some of the games.

    kidkat210

    Well-Known Member

    Hi there, thanks! I know I’m using the latest Hecate and pretty sure I have the sigpatches, but I haven’t altered .ini.

    i‘ll give it a shot! If I can get back to where I was, what would you suggest is the best way to install games? Tinfoil wouldn’t recognise my usbf and gold leaf only let me install some of the games.

    Badablek

    Well-Known Member

    take DBI, use its MTP mode (X button)
    no driver needed

    But if you prefer using your switch to choose which games to install, then you can try DBIbackend (you will have to install libusbk from ZADIG)

    ps : when everything’s working again, you can change autoboot=0 to autoboot=1
    with autoboot_list=0 it will auto-launch AMS sysMMC (autoboot_list=1 for AMS emuMMC if you have made one, autoboot_list=2 for original Firmware)

    EDIT : if you have upgraded AMS from 0.x to 1.x, do not forget to delete atmospherefusee.secondary.bin or even better, remove atmosphere folder and unzip again v1.2.5 (but you will lose your personnal AMS parameters if you have set some of them). AMS can’t boot if there is package3 AND fusee-secondary.bin

    Zay475

    Well-Known Member

    take DBI, use its MTP mode (X button)
    no driver needed

    But if you prefer using your switch to choose which games to install, then you can try DBIbackend (you will have to install libusbk from ZADIG)

    ps : when everything’s working again, you can change autoboot=0 to autoboot=1
    with autoboot_list=0 it will auto-launch AMS sysMMC (autoboot_list=1 for AMS emuMMC if you have made one, autoboot_list=2 for original Firmware)

    EDIT : if you have upgraded AMS from 0.x to 1.x, do not forget to delete atmospherefusee.secondary.bin or even better, remove atmosphere folder and unzip again v1.2.5 (but you will lose your personnal AMS parameters if you have set some of them). AMS can’t boot if there is package3 AND fusee-secondary.bin

    Thanks for your help, it’s much appreciated. I haven’t had a chance to try the fix yet but hopefully I can get back to where I was. Do you know why some games were installing fine and others were asking for sigpatches? I had another switch modded last year and all the games I installed on that using tinfoil worked fine. but tinfoil wouldn’t find my folders on this switch.

    games like super Mario odyssey, luigis mansion just wouldn’t install with gold leaf but on my old one they worked perfectly , it’s very confusing lol

    Источник

    Fix: Error while loading FSS0 atmoshpehere/fusee-secondary.bin wrong ini cfg

    Modding gaming consoles rarely go without hiccups, especially if you’re running emulators for older consoles on newer hardware that may or may not support the software you’re trying to run.

    In this article, we’re talking about the “Error while loading FSS0 atmoshpehere/fusee-secondary.bin wrong ini cfg” problem, which can come up when running GameBoy emulators on modern handheld consoles like the Nintendo Switch and giving you x fixes to solve the problem.

    Check your SD card

    First up, check your SD card to ensure it’s formatted in the correct file format. While different emulators support different formats, you’re generally safe to go with FAT32 or NFTS.

    Update Atmosphere and Hekate

    Next, make sure that Atmosphere and Hekate are updated with the latest stable builds. Also, ensure that all required files for the programs to function after the update are on your Switch’s storage drive (or memory card), as the update often tends to remove the configuration files required for the emulator to function.

    Replace your configuration files

    Since the error indicates a problem with configuration files, try replacing the ones you currently have with the ones you got with your fss0 build to see if that gets things going.

    Check the EMUMMC partition

    Sometimes, during partition creation, the EMUMMC partition is the only one that remains with data, meaning all other files and folders, including Atmosphere, are deleted. Check your SD card’s root folder and if you only have the bootloader and EMUMMC, try installing Atmosphere again to see if that helps.

    Replace fusee files

    In addition to replacing your configuration files, you can alsy try replacing the currently in use fusee-primary.bin file with fusee.bin and fusee-secondary.bin file with package. This should get the emulator configuration in order and resolve the error.

    Someone who writes/edits/shoots/hosts all things tech and when he’s not, streams himself racing virtual cars.

    You can contact him here: [email protected]

    Источник

    error while loading fss0 , help?

    st4ticbuzz

    Member

    hi all . i’ve spent the past week or so attempting to jailbreak my switch . it feels like every single thing that can go wrong has gone wrong up to this point , but this is a problem i don’t know how to fix . i’m not sure what happened to cause it , but at some point every time i tried to run sysmmc , it would give me the same error message

    error while loading fss0 :
    atmosphere/fusee-secondary.bin
    wrong ini cfg or missing/corrput files/
    failed to launch HOS

    i have no idea what caused this . it only started doing this after i did something completely unrelated to atmosphere , fusee , or hekate . i’ve completely deleted and reinstalled both atmosphere and hekate at this point , and i cannot for the life of me figure out what the problem is . it’s getting so incredibly frustrating to try and fix over and over again . i have had so many problems and all of them i’ve found a way around , but this is apparently the road block that i finally have to ask for help for . any advice ? if the solution is just totally starting over , i would appreciate an up-to-date guide to follow if possible , since clearly the one i used was not great , as i had SEVERAL issues while trying to get it to work properly . thanks in advance .

    Shadow#1

    Wii, 3DS Softmod & Dumpster Diving Expert

    hi all . i’ve spent the past week or so attempting to jailbreak my switch . it feels like every single thing that can go wrong has gone wrong up to this point , but this is a problem i don’t know how to fix . i’m not sure what happened to cause it , but at some point every time i tried to run sysmmc , it would give me the same error message

    error while loading fss0 :
    atmosphere/fusee-secondary.bin
    wrong ini cfg or missing/corrput files/
    failed to launch HOS

    i have no idea what caused this . it only started doing this after i did something completely unrelated to atmosphere , fusee , or hekate . i’ve completely deleted and reinstalled both atmosphere and hekate at this point , and i cannot for the life of me figure out what the problem is . it’s getting so incredibly frustrating to try and fix over and over again . i have had so many problems and all of them i’ve found a way around , but this is apparently the road block that i finally have to ask for help for . any advice ? if the solution is just totally starting over , i would appreciate an up-to-date guide to follow if possible , since clearly the one i used was not great , as i had SEVERAL issues while trying to get it to work properly . thanks in advance .

    binkinator

    Garfield’s Fitness Coach

    hi all . i’ve spent the past week or so attempting to jailbreak my switch . it feels like every single thing that can go wrong has gone wrong up to this point , but this is a problem i don’t know how to fix . i’m not sure what happened to cause it , but at some point every time i tried to run sysmmc , it would give me the same error message

    error while loading fss0 :
    atmosphere/fusee-secondary.bin
    wrong ini cfg or missing/corrput files/
    failed to launch HOS

    i have no idea what caused this . it only started doing this after i did something completely unrelated to atmosphere , fusee , or hekate . i’ve completely deleted and reinstalled both atmosphere and hekate at this point , and i cannot for the life of me figure out what the problem is . it’s getting so incredibly frustrating to try and fix over and over again . i have had so many problems and all of them i’ve found a way around , but this is apparently the road block that i finally have to ask for help for . any advice ? if the solution is just totally starting over , i would appreciate an up-to-date guide to follow if possible , since clearly the one i used was not great , as i had SEVERAL issues while trying to get it to work properly . thanks in advance .

    Источник

    Modding gaming consoles rarely go without hiccups, especially if you’re running emulators for older consoles on newer hardware that may or may not support the software you’re trying to run. 

    In this article, we’re talking about the “Error while loading FSS0 atmoshpehere/fusee-secondary.bin wrong ini cfg” problem, which can come up when running GameBoy emulators on modern handheld consoles like the Nintendo Switch and giving you x fixes to solve the problem.

    Also read: How to fix Nintendo Switch error code 2137 8056?


    Check your SD card

    First up, check your SD card to ensure it’s formatted in the correct file format. While different emulators support different formats, you’re generally safe to go with FAT32 or NFTS. 


    Update Atmosphere and Hekate

    Next, make sure that Atmosphere and Hekate are updated with the latest stable builds. Also, ensure that all required files for the programs to function after the update are on your Switch’s storage drive (or memory card), as the update often tends to remove the configuration files required for the emulator to function. 

    Also read: Windows error 0xc1900106: 7 Fixes


    Replace your configuration files

    Since the error indicates a problem with configuration files, try replacing the ones you currently have with the ones you got with your fss0 build to see if that gets things going. 


    Check the EMUMMC partition

    Sometimes, during partition creation, the EMUMMC partition is the only one that remains with data, meaning all other files and folders, including Atmosphere, are deleted. Check your SD card’s root folder and if you only have the bootloader and EMUMMC, try installing Atmosphere again to see if that helps. 


    Replace fusee files

    In addition to replacing your configuration files, you can alsy try replacing the currently in use fusee-primary.bin file with fusee.bin and fusee-secondary.bin file with package. This should get the emulator configuration in order and resolve the error. 

    Also read: Nintendo Switch dock not working: 6 Fixes

    Yadullah Abidi

    Someone who writes/edits/shoots/hosts all things tech and when he’s not, streams himself racing virtual cars.

    You can contact him here: [email protected]

    Posté 12 mars 2022 — 20:46

    #1

    Bonsoir
    Voici mon soucis
    J’ai une switch V1 patchée équipée d’une puce SX Core et d’atmosphere en emunand
    Au démarrage j’ai hekate qui se lance (a priori rien d’anormal), MAIS quand je veux aller sur Stock sysMMC (j’imagine que c’est le OFW); CFW emummc ou CFW sysMMC, j’ai un écran noir avec écrit
    Error while loading fss0
    atmosphere/fusee-secondary.bin
    Wrong ini cfg or Missing/corrupt files!
    Failed to launch HOS
    Lancer Atmospehe CFW ne pose pas de soucis.
    J’ai aussi les jeux qui me disque qu’une mise a jour de la console est dispo, j’ai voulu acceder au menu lorsque l’on fait un Hard Reset, mais j’y ai pas accès.
    Pouvez vous m’aider svp ? 
    Merci beaucoup et dsl si ca a deja été demandé sur le forum, du coup si vous avez le lien je suis preneur. Merci encore

    • Retour en haut


    Posté 12 mars 2022 — 22:19

    #2

    BestPig

    BestPig

      Sunriseur

    • Shining VIP
    • 270 messages
    • Sexe:Male

    Probablement que ta config est un peu vielle.

    fusee-primary.bin et fusee-secondary.bin n’existe plus dans les versions récentes d’atmosphere.

    Je conseille donc je mettre à jour vers la dernière version d’atmosphere histoire d’être sur.

    Ensuite tu edit le fichier hekate_ipl.ini dans le dossier bootloader et tu remplaces les occurrences de fusee-primary.bin par fusee.bin et fusee-secondary.bin par package3

    Image IPB

    • Retour en haut


    Posté 13 mars 2022 — 00:40

    #3

    john the ripper

    Merci pour la réponse, j’ai oublié que j’étais un noob total concernant les switch sous atmosphere et du coup plusieurs question
    Depuis atmosphere, j’ai la console qui me demande de la mettre à jour, dois je le faire ? 
    Si oui depuis les paramètres de la console ? Depuis Tinfoil (qui me propose de faire lui meme de faire la mise a jour)?
    Ensuite, comment on met atmosphere à jour sachant que je suis sur emunand sans perte de données ? Il faut passer par un script ?
    Surtout que j’ai fait posé la puce il n’y a pas longtemps du coup je suis pas sur qu’il y ai eu de nouvelles version a moins qu’a chaque nouvelle version du OFW, il y a une nouvelle version d’atmosphere ?
    Concernant le fichier a modifier du coup au final il devra ressembler à ceci ?

    [config]

    autoboot=0

    autoboot_list=0

    bootwait=0

    autohosoff=0

    autonogc=1

    updater2p=1

    backlight=100

    [Atmosphere CFW]

    payload=bootloader/payloads/fusee.bin (rien modifié ici)

    [CFW — sysMMC]

    fss0=atmosphere/package3

    kip1patch=nosigchk

    emummc_force_disable=1

    [CFW — emuMMC]

    fss0=atmosphere/package3

    kip1patch=nosigchk

    emummcforce=1

    [Stock — sysMMC] (c’est bien d’ici qu’on est censé pouvoir booter sur l’OFW ? si oui comment faire ?)

    fss0=atmosphere/package3

    emummc_force_disable=1

    stock=1

    Merci encore pour votre aide

    PS : j’ai bien trouvé se tuto qui a l’air super http://www.logic-sun…a-daybreak.html mais au vu des commentaires je sais pas ce que ca va faire exactement, installer l’OFW ou atmosphere, si c’est l’OFW vaut mieux que je passe par lui ou par le menu parametre de la console ?

    Modifié par john the ripper, 13 mars 2022 — 00:46.

    • Retour en haut


    Posté 13 mars 2022 — 02:21

    #4

    BestPig

    BestPig

      Sunriseur

    • Shining VIP
    • 270 messages
    • Sexe:Male

    Aucune idée de ce que ça fait de passer par le moyen officiel de mettre a jour sur une emunand.
    Suit plutôt le tuto c’est comme ça qu’il faut faire, mais le tuto ne parle que de mettre a jour le firmware officiel, par le CFW, ce sont 2 choses bien distinct.

    Pour mettre à jour atmosphere tu vas sur le github d’atmosphere et tu dl la dernière version, et tu l’unzip à la racine de ta SD.

    Et tu fais pareil avec les sigpatches.

    Et oui, chaque nouvelle mise à jour de Nintendo nécessite une nouvelle version d’atmosphere.

    Ton fichier ini me semble correct oui.

    Et oui c’est bien «Stock — sysMMC» que tu dois choisir dans hekate pour boot ton OFW.

    Image IPB

    • Retour en haut


    Posté 13 mars 2022 — 15:24

    #5

    john the ripper

    Bon j’ai suivi le tuto et j’ai essayé de mettre a jour atmosphere mais maintenant quand je démarre la console j’ai ceci
    Missing LP0 (sleep mode) lib!
    Missing or old Minerva lib!
    Update bootloader folder!
    Press any key …

    l’avantage c’est que maintenant j’ai a nouveau acces a la OFW que j’ai pu mettre à jour (visiblement daybreak n’a pas marché …)

    • Retour en haut


    Posté 13 mars 2022 — 15:33

    #6

    john the ripper

    Bon j’ai mi a jour hekate, et j’arrive à booter dessus quand je clique sur emuMMC, j’ai bien enable du coup j’imagine qu’il détecte bien mon emunand.
    Dans Payloads j’ai rien du tout et quand je clique sur Launch j’ai ceci :

    No main boot entries found …
    check that bootloader/hekate_ipl.ini has boot entries 
    or use more configs button for more boot entries

    • Retour en haut


    Posté 13 mars 2022 — 15:39

    #7

    john the ripper

    bon bah probleme résolu, juste le fichier .ini qui était quasi vide, j’ai en plus, grace a vous, le mode OFW qui refonctionne ^^ Merci beaucoup

    • Retour en haut


    Posté 13 mars 2022 — 15:42

    #8

    john the ripper

    Par contre je peux plus lancer les jeux installé sur mon emunand, il me dit de relancer le jeu depuis le menu home ou que des données sont corrompu .. 

    • Retour en haut


    Posté 13 mars 2022 — 15:45

    #9

    BestPig

    BestPig

      Sunriseur

    • Shining VIP
    • 270 messages
    • Sexe:Male

    Tu n’as pas mis à jour les sigpatches ;).

    Extrait ça à la racine de la carte SD -> https://github.com/I…/SigPatches.zip

    Image IPB

    • Retour en haut


    Posté 13 mars 2022 — 16:02

    #10

    john the ripper

    bon c’était les sigpatchs effectivement

    Modifié par john the ripper, 13 mars 2022 — 16:03.

    • Retour en haut


    Posté 13 mars 2022 — 16:03

    #11

    john the ripper

    merci mais je suis passé par aio-switch-updater et ca fonctionne ^^
    Il a l’air vraiment énorme et cool pour faciliter la vie cet utilitaire ^^

    Modifié par john the ripper, 13 mars 2022 — 16:04.

    • Retour en haut


    Понравилась статья? Поделить с друзьями:

    Читайте также:

  • Error while loading configuration file 00000000009b0001 c99355ccd3e90636
  • Error while image upload
  • Error while compiling compiler version disconnected
  • Error were encountered while installing the software for your device
  • Error webgl disallowing antialiased backbuffers due to blacklisting

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии