Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
- Pick a username
- Email Address
- Password
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
You should upgrade or use an alternative browser.
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 32
- XP
-
50
- Country
-
#1
I updated by mistake my switch v2 (SX Chips) to 11.0.1, so as you know, SX OS is not compatible with this version.
Like everyone, i tried to use Atmosphere with ChoiDujourNX to downgrade from 11.0.1 to 11.0 and maybe try Atmosphere.
In SDSetup, i downloaded Atmosphere and Hekate bin, boot up to Hekate and then launched CFW, I got this error :
**Even with RR Pro, i got the same problem when trying to launch Atmosphere
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————
PS: I don’t have any NAND backup unfortunately, and I don’t use emuMMC.
I look it up in Google, but no success, if someone could help please.
Have a good day.
-
#2
Hello everyone,I updated by mistake my switch v2 (SX Chips) to 11.0.1, so as you know, SX OS is not compatible with this version.
Like everyone, i tried to use Atmosphere with ChoiDujourNX to downgrade from 11.0.1 to 11.0 and maybe try Atmosphere.
In SDSetup, i downloaded Atmosphere and Hekate bin, boot up to Hekate and then launched CFW, I got this error :
**Even with RR Pro, i got the same problem when trying to launch Atmosphere
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————PS: I don’t have any NAND backup unfortunately, and I don’t use emuMMC.
I look it up in Google, but no success, if someone could help please.
Have a good day.
try booting stock with hekate 5.5.2 see if that works
to make sure your downgrade was success and you didnt mess up your sysnand but from what i know you should Not use
ChoiDujourNX on Sysnand on Mariko cause it bricks the cosnole you should’ve used Daybreak that comes with atmosphere
maybe little bit more reading before doing anything like that next time will be good
if you cant boot stock with hekate 5.5.2 then your sysnand is bad and it needs rebuilding look into that
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 32
- XP
-
50
- Country
-
#3
I think I misspoke the problem, actually, im still on 11.0.1, i am not able to boot with SX OS (last version) because is not compatible.
I have read on other forums that some people have successfully downgraded the firmware using Atmosphere/Hekate, so i tried to boot up Atmosphere (on 11.0.1 — Atmosphere-0.17.0 — hekate_ctcaer_5.5.2_Nyx_0.9.8).
As described in the first post, I always come across the same error message, even using RR Pro (with the right hekate_keys.ini).
PS: I always updated firmware using ChoiDujourNX, never had a problem.
-
#4
I had this problem where my card got converted to a GPT file system which wouldn’t work on my switch even with the correct files placed
I had to format it again and change it from GPT to MBR and it worked straight away
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 32
- XP
-
50
- Country
-
#5
You did have the same error ? You have a Mariko Switch ?
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————
-
#6
Hello LyuboA,I think I misspoke the problem, actually, im still on 11.0.1, i am not able to boot with SX OS (last version) because is not compatible.
I have read on other forums that some people have successfully downgraded the firmware using Atmosphere/Hekate, so i tried to boot up Atmosphere (on 11.0.1 — Atmosphere-0.17.0 — hekate_ctcaer_5.5.2_Nyx_0.9.8).
As described in the first post, I always come across the same error message, even using RR Pro (with the right hekate_keys.ini).
PS: I always updated firmware using ChoiDujourNX, never had a problem.
you need DRM free firmware for SX Mod Chip called «Spacecraft-NX» to run Atmosphere on Mariko consoles type in google «Spacecraft-NX github» download it and read the instructions on how to install it on your mod chip then you can use hekate and Atmosphere you need to read on that how to use them you will need the Mariko keys for hekate all that info is easily accessible with a simple google search
then if you want to downgrade dont use ChoidujourNX use Daybreak it comes woth Atmosphere ChoidujourNX is old and ppl have issues downgrading with it
but the safety option for Mariko consoles on 11.0.1 is to just use Atmosphere and dont downgrade
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 32
- XP
-
50
- Country
-
#7
Thanks for your answer, I will try this, and I will keep you informed.
-
#8
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 32
- XP
-
50
- Country
-
#9
Thanks for your answer, could you tell me where i can get a similar boot0/boot1 ?
I did look it up but no one is providing :'(
—
Update #1 :
I tried dump Package1/2 in Hekate, i got this problem : https://ibb.co/wLBTN7B
- Joined
- Nov 12, 2020
- Messages
- 19
- Trophies
- 0
- Age
- 31
- XP
-
102
- Country
-
#10
Hello urherenow,Thanks for your answer, could you tell me where i can get a similar boot0/boot1 ?
I did look it up but no one is providing :'(
—
Update #1 :
I tried dump Package1/2 in Hekate, i got this problem : https://ibb.co/wLBTN7B
Do a new emmummc dump using hekate and copy the boot0 and boot1 from it over (assuming you didn’t update your sysnand using choidujournx)
——————— MERGED —————————
you need DRM free firmware for SX Mod Chip called «Spacecraft-NX» to run Atmosphere on Mariko consoles type in google «Spacecraft-NX github» download it and read the instructions on how to install it on your mod chip then you can use hekate and Atmosphere you need to read on that how to use them you will need the Mariko keys for hekate all that info is easily accessible with a simple google search
then if you want to downgrade dont use ChoidujourNX use Daybreak it comes woth Atmosphere ChoidujourNX is old and ppl have issues downgrading with it
but the safety option for Mariko consoles on 11.0.1 is to just use Atmosphere and dont downgrade
You don’t need spacecraft nx to run hekate/atmosphere. you just need to patch the boot.dat with the sxgear 1.1 one and your mariko console will boot into the hekate
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 32
- XP
-
50
- Country
-
#11
Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
-
#12
Hey guys,Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
Hello friend, I have the same problem, the same thing happened to me when doing the update, could you teach me to repair it or mr purdr pass the boot0 please
- Joined
- Jul 17, 2020
- Messages
- 37
- Trophies
- 0
- Age
- 35
- XP
-
204
- Country
-
#13
Hey guys,Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
Can you please walk us through step by step how you did that?
I have a boot0.bin donor too.
What folders do you put them in and how to do you launch them?
Can you post screenshots of your SD card folders showing us how/where to place the files needed?
And then tell us if you launched hetake (and what version) to get into Atmosphere (and what version).
Then what buttons you pushed on the hetake interface to launch Atmosphere?
Just like a lot more detail so others can try it please.
For example, in SXOS when you create a backup it puts the boot0, boot1, and raw stuff on a backup folder in the sxos folder thats on the root of the SD.
So, when we restore a NAND do we put boot0 and boot1 in that same folder?
Do we need the rawnand?
Does it matter if the rawnand was created with a bad boot0 boot1?
- Joined
- Feb 5, 2017
- Messages
- 2
- Trophies
- 0
- Age
- 30
- XP
-
44
- Country
-
#14
Hey guys,Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
hi i have the same problem like you please can you share boot0.bin donor? please
Jan 24, 2021
-
#15
Hello friend, I have the same problem, the same thing happened to me when doing the update, could you teach me to repair it or mr purdr pass the boot0 please
You can just make your own with either eMMChacgen or ChoiDujour
Similar threads
- No one is chatting at the moment.
Mature Content
This post contains mature content and may not be appropriate for certain viewers. To continue, confirm that you’re over 18.
Go to Home
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
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 31
- XP
-
40
- Country
-
-
#1
Hello everyone,
I updated by mistake my switch v2 (SX Chips) to 11.0.1, so as you know, SX OS is not compatible with this version.
Like everyone, i tried to use Atmosphere with ChoiDujourNX to downgrade from 11.0.1 to 11.0 and maybe try Atmosphere.
In SDSetup, i downloaded Atmosphere and Hekate bin, boot up to Hekate and then launched CFW, I got this error :
**Even with RR Pro, i got the same problem when trying to launch Atmosphere
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————
PS: I don’t have any NAND backup unfortunately, and I don’t use emuMMC.
I look it up in Google, but no success, if someone could help please.
Have a good day.
-
#2
Hello everyone,
I updated by mistake my switch v2 (SX Chips) to 11.0.1, so as you know, SX OS is not compatible with this version.
Like everyone, i tried to use Atmosphere with ChoiDujourNX to downgrade from 11.0.1 to 11.0 and maybe try Atmosphere.
In SDSetup, i downloaded Atmosphere and Hekate bin, boot up to Hekate and then launched CFW, I got this error :
**Even with RR Pro, i got the same problem when trying to launch Atmosphere
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————PS: I don’t have any NAND backup unfortunately, and I don’t use emuMMC.
I look it up in Google, but no success, if someone could help please.
Have a good day.
try booting stock with hekate 5.5.2 see if that works
to make sure your downgrade was success and you didnt mess up your sysnand but from what i know you should Not use
ChoiDujourNX on Sysnand on Mariko cause it bricks the cosnole you should’ve used Daybreak that comes with atmosphere
maybe little bit more reading before doing anything like that next time will be good
if you cant boot stock with hekate 5.5.2 then your sysnand is bad and it needs rebuilding look into that
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 31
- XP
-
40
- Country
-
-
#3
Hello LyuboA,
I think I misspoke the problem, actually, im still on 11.0.1, i am not able to boot with SX OS (last version) because is not compatible.
I have read on other forums that some people have successfully downgraded the firmware using Atmosphere/Hekate, so i tried to boot up Atmosphere (on 11.0.1 — Atmosphere-0.17.0 — hekate_ctcaer_5.5.2_Nyx_0.9.8).
As described in the first post, I always come across the same error message, even using RR Pro (with the right hekate_keys.ini).
PS: I always updated firmware using ChoiDujourNX, never had a problem.
-
#4
Is it a freshly formatted card?
I had this problem where my card got converted to a GPT file system which wouldn’t work on my switch even with the correct files placed
I had to format it again and change it from GPT to MBR and it worked straight away
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 31
- XP
-
40
- Country
-
-
#5
Hello CloudStrife,
You did have the same error ? You have a Mariko Switch ?
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————
-
#6
Hello LyuboA,
I think I misspoke the problem, actually, im still on 11.0.1, i am not able to boot with SX OS (last version) because is not compatible.
I have read on other forums that some people have successfully downgraded the firmware using Atmosphere/Hekate, so i tried to boot up Atmosphere (on 11.0.1 — Atmosphere-0.17.0 — hekate_ctcaer_5.5.2_Nyx_0.9.8).
As described in the first post, I always come across the same error message, even using RR Pro (with the right hekate_keys.ini).
PS: I always updated firmware using ChoiDujourNX, never had a problem.
you need DRM free firmware for SX Mod Chip called «Spacecraft-NX» to run Atmosphere on Mariko consoles type in google «Spacecraft-NX github» download it and read the instructions on how to install it on your mod chip then you can use hekate and Atmosphere you need to read on that how to use them you will need the Mariko keys for hekate all that info is easily accessible with a simple google search
then if you want to downgrade dont use ChoidujourNX use Daybreak it comes woth Atmosphere ChoidujourNX is old and ppl have issues downgrading with it
but the safety option for Mariko consoles on 11.0.1 is to just use Atmosphere and dont downgrade
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 31
- XP
-
40
- Country
-
-
#7
Hello LyuboA,
Thanks for your answer, I will try this, and I will keep you informed.
-
#8
Always used Choi without problems, is the wrong answer. Using Choi on a Mariko system to update to 11.0.1 gets you a boot0 with erista data in it. Basically a softbrick. You need a donor boot0/boot1 from a working mariko unit on the same firmware as you. I’ve read several other posts just today with the same issue and this is the answer that’s given. This is on top of needing spacecraft-nx.
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 31
- XP
-
40
- Country
-
-
#9
Hello urherenow,
Thanks for your answer, could you tell me where i can get a similar boot0/boot1 ?
I did look it up but no one is providing :'(
—
Update #1 :
I tried dump Package1/2 in Hekate, i got this problem : https://ibb.co/wLBTN7B
- Joined
- Nov 12, 2020
- Messages
- 19
- Trophies
- 0
- Age
- 30
- XP
-
92
- Country
-
-
#10
Hello urherenow,
Thanks for your answer, could you tell me where i can get a similar boot0/boot1 ?
I did look it up but no one is providing :'(
—
Update #1 :
I tried dump Package1/2 in Hekate, i got this problem : https://ibb.co/wLBTN7B
Do a new emmummc dump using hekate and copy the boot0 and boot1 from it over (assuming you didn’t update your sysnand using choidujournx)
——————— MERGED —————————
you need DRM free firmware for SX Mod Chip called «Spacecraft-NX» to run Atmosphere on Mariko consoles type in google «Spacecraft-NX github» download it and read the instructions on how to install it on your mod chip then you can use hekate and Atmosphere you need to read on that how to use them you will need the Mariko keys for hekate all that info is easily accessible with a simple google search
then if you want to downgrade dont use ChoidujourNX use Daybreak it comes woth Atmosphere ChoidujourNX is old and ppl have issues downgrading with it
but the safety option for Mariko consoles on 11.0.1 is to just use Atmosphere and dont downgrade
You don’t need spacecraft nx to run hekate/atmosphere. you just need to patch the boot.dat with the sxgear 1.1 one and your mariko console will boot into the hekate
- Joined
- Jan 10, 2021
- Messages
- 6
- Trophies
- 0
- Age
- 31
- XP
-
40
- Country
-
-
#11
Hey guys,
Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
-
#12
Hey guys,
Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
Hello friend, I have the same problem, the same thing happened to me when doing the update, could you teach me to repair it or mr purdr pass the boot0 please
- Joined
- Jul 17, 2020
- Messages
- 37
- Trophies
- 0
- Age
- 34
- XP
-
204
- Country
-
-
#13
Hey guys,
Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
Can you please walk us through step by step how you did that?
I have a boot0.bin donor too.
What folders do you put them in and how to do you launch them?
Can you post screenshots of your SD card folders showing us how/where to place the files needed?
And then tell us if you launched hetake (and what version) to get into Atmosphere (and what version).
Then what buttons you pushed on the hetake interface to launch Atmosphere?
Just like a lot more detail so others can try it please.
For example, in SXOS when you create a backup it puts the boot0, boot1, and raw stuff on a backup folder in the sxos folder thats on the root of the SD.
So, when we restore a NAND do we put boot0 and boot1 in that same folder?
Do we need the rawnand?
Does it matter if the rawnand was created with a bad boot0 boot1?
- Joined
- Feb 5, 2017
- Messages
- 2
- Trophies
- 0
- Age
- 29
- XP
-
34
- Country
-
-
#14
Hey guys,
Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^
Thanks to everyone for help !
hi i have the same problem like you please can you share boot0.bin donor? please
Last edited by ROAVITA,
Jan 24, 2021
-
#15
Hello friend, I have the same problem, the same thing happened to me when doing the update, could you teach me to repair it or mr purdr pass the boot0 please
You can just make your own with either eMMChacgen or ChoiDujour
Similar threads
You may also like…
- No one is chatting at the moment.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
Posté 11 janvier 2021 — 02:25
#1
Bonjour,
J’ai fait l’erreur de mettre à jour ma switch en 11.0.1 sans vérifier la compatibilité avec SX OS, résultat : écran noir après le splash screen SX OS.
J’ai vu qu’il est possible de passer par Atmosphere pour un possible downgrade, après avoir préparé la SD — boot sur Hekate — je me retrouve coincé avec le message d’erreur suivant :
————————————————
Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader…
Found pkg1 (‘PG PG
~’).
Unknown pkg1 version.
HOS version not supported!
Failed to launch HOS!
Press any key…
————————————————
J’ai essayé d’autres packs AIO (DeepSea ; RR Pro) avec l’ajout hekate_keys.ini dans le répertoire bootloader mais sans succès, je tombe toujours sur le même message d’erreur.
Pouvez-vous m’aider s’il vous plaît ?
PI : je n’ai pas de backup NAND ni de emuMMC créé.
- Retour en haut
Posté 11 janvier 2021 — 07:50
#2
lemmej
Bonjour votre demande est déjà sur ce site:
https://gbatemp.net/…version.580598/
avez vous essayé sa méthode ?
- Retour en haut
Posté 11 janvier 2021 — 11:57
#3
saadibader
Bonjour,
Oui effectivement, j’ai posté la demande dans plusieurs forums ^^
Je vais voir ce que ça va donner.
Merci et très bonne journée !
- Retour en haut
Posté 11 janvier 2021 — 15:42
#4
shadow256
D’après se que je lis tu faisais les mises à jour avec ChoiDuJour-NX sur la sysnand avec une console Mariko alors que c’est expressément dit partout depuis le début de la mise en place des SX Core/Lite de ne pas faire çà sur ce genre de consoles car ça brick BOOT0, va falloir apprendre à se renseigner un peu mieux avant de faire des manipulations. Se que tu peux tenter, essayer l’option pour nettoyer les traces de SXOS sur la sysnand, je ne me souviens plus de l’intitulé exact de l’option dans le menu de démarrage de la puce et une fois cela fait tenter de relancer Atmosphere. Et avant tout, fais un dump de ta nand au cas où car çà non plus tu ne l’avais pas fait.
- Retour en haut
Posté 12 janvier 2021 — 15:56
#5
saadibader
Bonjour Shadow256,
Merci pour ta réponse, j’ai réalisé le dump du NAND comme conseillé, ensuite j’ai effectué un cleanup à partir du boot de SX OS, certe je me retrouve toujours avec le même message d’erreur.
Sur un autre forum, on m’a indiqué que ChoiDuJour-NX à mis à jour le BOOT0 avec les données de Erista, donc un softbrik, et qu’il me faut un boot0/boot1 à partir d’une console Mariko sous le même firmware, à savoir le 11.0.1
Je me retrouve coincé pour le moment 
- Retour en haut
Posté 12 janvier 2021 — 18:03
#6
shadow256
Oui je viens de voir çà sur le sujet Gbatemp et c’est se que je t’expliquais au sujet du brick de BOOT0, désolé mais sur ce point je ne peux pas t’aider car je n’ai pas de console Mariko en 11.0.1, faudrait voir s’il n’y a pas moyen de modifier tes BOOT0 et BOOT1 (pour BOOT1 je pense qu’il n’y a rien à faire, c’est BOOT0 qui doit être problématique selon moi) actuels pour les rendre compatibles Mariko, faudrait que je regarde les infos sur Switchbrew à ce sujet car même pas certain qu’avec le BOOT0 d’une autre console Mariko sur le même firmware la manipulation fonctionne car peut-être que le BOOT0 est lié à la console d’une manière ou d’une autre, sujet à creuser. Et le pire dans l’histoire c’est que je ne sais pas si on va même pouvoir récupérer les clés de la console, essaies le payload Lockpick-rcm pour voir s’il fonctionne et se qu’il te renvoi (attention ne transmet pas les infos de ton fichier de clés car elles sont uniques à ta console et interdite au partage sur ce forum).
Edit: Bon en fait si, BOOT1 semble aussi différer entre les consoles Erista et Mariko, voir cette page pour plus d’infos. Par contre pour réparer çà manuellement je ne sais pas si c’est même possible.
Modifié par shadow256, 12 janvier 2021 — 18:20.
- Retour en haut
Posté 12 janvier 2021 — 19:10
#7
saadibader
Shadow256,
Lockpick-rcm me fait le même message d’erreur :
MMC init… done in 44168 us
Unknown pkg1 version.
Make sur you have the latest LockPick_RCM.
If a new firmware versionb just came out,
Lockpick must be updated
Check Github for new releasse.
Modifié par saadibader, 12 janvier 2021 — 23:53.
- Retour en haut
Posté 13 janvier 2021 — 00:01
#8
shadow256
Je m’en doutais mais ça confirme, du coup pas possible de récupérer les clés apparemment se qui est un problème de plus. Bon faudra trouver une solution à ce problème de BOOT0 Mariko brické, si @eliboa passe par là il pourra peut-être nous apprendre des choses intéressantes sur ce sujet car il est bien plus calé que moi en se qui concerne ce genre de choses très techniques.
- Retour en haut
Posté 13 janvier 2021 — 00:30
#9
saadibader
J’ajoute plus d’infos on sait jamais :
Sur Hekate — Tools — Dump Package1/2 : j’ai presque le même message d’erreur :
- Retour en haut
Posté 14 janvier 2021 — 18:05
#10
Gluom
salut utilise retro reloaded version 1.54 utilise le bootdat2 pour switch mariko et les keys j ai le fichier si tu veux ou dispo sur leur discord en epinglé
- Retour en haut
Posté 14 janvier 2021 — 18:31
Meilleure réponse
#11
saadibader
Hey tout le monde,
J’ai réussi à résoudre mon problème, je me suis procuré un boot0.bin d’une console Mariko, ensuite j’ai placé ce fichier sous SD:sxosbackup (juste le fichier boot0.bin)
À partir du menu SX OS (Power + Vol+) -> Options -> NAND — Backup NAND, j’ai restauré le boot0.bin et bingo, la console démarre ^^
En cas de besoin, MP pour le boot0.bin
Et merci à tous pour les réponses fournies.
Excellente journée.
- Retour en haut
Posté 14 janvier 2021 — 21:50
#12
Z0rP
Intéressant de voir que cette méthode qui existe sous Erista est opérationnelle pour Mariko si l’on prend les BOOT0 des modèles correspondants.
Modifié par Z0rP, 15 janvier 2021 — 13:33.
- Retour en haut
Posté 15 janvier 2021 — 00:29
#13
saadibader
@shadow256 : Est ce possible que je partage le lien vers le boot0.bin sur le forum ? c’est OK ?
- Retour en haut
Posté 15 janvier 2021 — 10:19
#14
Speedloader_
@saadibader En tout cas moi ça m’intéresse, pour le moment j’en ai pas besoin mais on ne sait jamais !
- Retour en haut
Posté 15 janvier 2021 — 16:10
#15
saadibader
Voici le lien en cas de besoin https://drive.google…KZ3qiu_ZjN/view
Renommer ce fichier en boot0.bin
- Retour en haut
Posté 15 janvier 2021 — 22:04
#16
shadow256
@shadow256 : Est ce possible que je partage le lien vers le boot0.bin sur le forum ? c’est OK ?
Je pense que non car c’est un fichier appartenant à Nintendo, après là se sera aux modérateurs de voir. Ceci dit pareil, je l’ai récupéré au cas où et ça va me permettre d’étudier çà de manière plus détaillée donc merci pour le partage et content de voir que ton problème est résolu.
- saadibader aime ceci
- Retour en haut
-
#1
Hola !!
Por error actualicé la consola y ahora al inyectar la consola me lanza el error ´unknown pkg1 version hos version not supported´
Igual cuando actualicé el atmosphere al 16.0 tampoco inicia
qué puedo hacer? soy novato en esto
Muchas gracias
-
#2
Tengo el mismo problema. Y mi hija dice que le salio una pantalla donde ponia «actualizar» y le dio a actualizar
-
#3
Yo lo solucioné instalando el último atmostphere, me costó pero pude.
Hay que actualizar la consola hasta la última versión e igual el atmostphere
-
#5
No se les olvide también actualizar Hekate y los sigpatches
-
#6
En el pack que hay en la sección Descargas esta todo, no?
-
#7
Bueno, he conseguido arrancar la consola, efectivamente esta actualizada a la version 11.0.1. Lo que no se es como se ha podido actualizar si no estaba conectada a internet
-
#8
Y ahora, como ya me paso la ultima vez que actualice el atmosphere, la mayoria de los juegos no funcionan, me pone que hay datos dañados. Y me temo que como la otra vez, haya perdido la partida guardada de Animal Crossing.
Además ahora el goldleaf no funciona para reinstalarlos
-
#9
Sí actualizaste los sigpatches?
Probablemente también tengas que actualizar el Godleaf.
-
#10
Hola.
Ya lo he conseguido.
El Goldleaf parece que no funciona con la versión 11.0.1.
Me he instalado el Awoo y he actualizado los sigpatches con la opción que incluye y ya he podido reinstalar los juegos.
Y por suerte no he perdido la partida del animal crossing
Ya que estoy a ver si me podéis resolver una duda más sobre el animal crossing.
Actualmente no tengo emuNAND, si hago copia de la NAND actual y la meto en la SD como emuNAND y dejo la NAND con la copia original que tengo guarda del primer día, en la emuNAND me seguirá funcionando la partida guardada de animal crossing? Porque copiar la partida actual a la nueva NAND «limpia» para poder jugar online con el original supongo que no es posible.
Muchas gracias por vuestra ayuda.
-
gracias voy a investigar a ver si soy capaz
Ayer a las 22:11
-
Solid123 ha reaccionado al post de oscarstoja en el hilo de Por donde empezar? con Like.
Hola @Solid123,
Tan solo tienes que descargar el pack CFW Atmosphère de aquí…
Ayer a las 22:07
-
danimicroman ha comentado en el mensaje de perfil de danimicroman.
Hay alguna manera de modificarla de todas maneras?
Ayer a las 21:40
-
oscarstoja ha comentado en el mensaje de perfil de danimicroman.
Hola @danimicroman, en esta Web: https://suchmememanyskill.github.io/guides/switchserials/ podrás ver si tu consola está parcheada. Mira…
Ayer a las 21:38
-
Hola @Solid123,
Tan solo tienes que descargar el pack CFW Atmosphère de aquí…
Ayer a las 21:37
Estado de compatibilidad de los CFWs:
Versión actual firmware: 15.0.1
|
CFW |
Estado |
| Pack Atmosphère: |
Compatible |
Versión anterior firmware: 15.0.0
|
CFW |
Estado |
| Pack Atmosphère: |
Compatible |
SX OS ha quedado OBSOLETO
Última actualización: 08/11/2022
-
Firmware 15.0.1
2022-11-08
- oscarstoja
- Actualizado: Nov 8, 2022
-
Pack CFW Atmosphère
2019-01-24
- LinkPK
- Actualizado: Oct 13, 2022
-
Firmware 15.0.0
2022-12-10
- LinkPK
- Actualizado: Oct 12, 2022
-
Firmware 14.1.2 (Rebootless)
14/07/2022
- LinkPK
- Actualizado: Jul 14, 2022
-
Firmware 14.1.1
2022-04-30
- oscarstoja
- Actualizado: Abr 30, 2022
- Miembros en línea
- 1
- Invitados en línea
- 20
- Total de visitantes
- 21
- Robots
- 96
bennyc023 opened this issue 10 months ago · comments
Hello! After accidentally updating system software while trying to start a game, when trying to launch CFW I get the error code that is in the title. (there are some more similar codes below it but my switch is currently vanilla so I dont have access. I can update with full log if needed)
After scouring the internet, I found many posts on this issue. They all state the fix is updating atmosphere/hetake, but I have the most current versions. I reformatted my SD card multiple times alongside reinstalling the mods, and I am positive I have the most current versions and installed everything correctly.
Did I corrupt my SD card or are hetake/atmosphere out of date for the system update I did? Could it be another issue?
Thanks in advance for the help.
A brand new system update was released less than 24 hours ago. Neither Atmosphere nor Hekate have been updated for it yet. You will just have to be patient for a new release.
It is because the 14.0.0 update is very recent and hekate and atmosphere just haven’t had time to update to a new version. The solution is just waiting for the devs to make a new version.
A brand new system update was released less than 24 hours ago. Neither Atmosphere nor Hekate have been updated for it yet. You will just have to be patient for a new release.
Thank you. Everytime I have accidentally updated the system software, it was over a week since it originally prompted me so it’s always been an easy reinstall. I just wanted to make sure there were no issues on my end because this hasn’t happened to me before.
Thank you for the help! I will close this post
after entering RCM and injecting hekate on a switch v1 firmware 14.1.1, hekate freezes randomly — sometimes imediately, sometimes after browsing some of the menus, sometimes while making a backup of the system. how can I check what’s wrong? thanks!
Hi, I am consistently getting an error trying to back up eMMC RAW GPP:
SD & eMMC data (@lba 03488000) do not match!
Verification failed
Is there any way to rectify this?
Hi, is it possible to add repair GPT option in emmc? For some reason screwed up emmc partition and need to restore gpt, thanks
Hi again, after supposedly fixing my boot 0 and pkg2 error, I am greeted with a completely new problem. And now all it says is Unknown pkg1 version. HOS version not supported Or emuMMC corrupt! Trying backup bootloader… Found pkg1 <»>. Unknown pkg1 version. HOS version not supported! Or emuMMC corrupt! Failed to launch HOS! Press any key…
Hi, recently I did a raw partition backup since I wanted to add android to my switch. I have failed, but that doesn’t matter. So I had to repartition my card which included wiping everything (I backed it all up), but the problem is that I have restored the emuMMC and the boot 0/1 (with raw partition on), but all I could get was Pkg 1 / Pkg 2 mismatch, could not launch HOS. I looked on google, but I couldn’t,t find anything like this. Any help will be appreciated!
Hekate would freeze up completely after pushing the payload. Most of the time it would freeze at the logo screen, rarely would it freeze up after 5 seconds into the home menu, every time it would freeze. I ended up ruling out that the problem is related to my micro sd card because the exact same micro sd card worked perfectly fine in a different hacked switch.
I was able to find that v5.0.0 works fine with my switch. I was also able to find that in the newest version of hekate if I removed nyx.bin I was able to boot hekate (though the features were very limited i.e no emummc creation).
I am able to run nintendo’s firmware fine with no problems/delays on this switch.
Adding date to backup’s name might help someone like me (replaced clean backup with dirty one)
I think it isn’t hard to implement
Ok so, you can autoboot a selection from your hekate.ini, but not a payload… now I know what your about to say…
- Payloads can be added to the hekate.ini as a launch option.
- You are launching the hekate payload, just launch the payload you want instead of hekate.
Yes, yes those are good points, but it’s more of an enhancement thing. If your using a modchip and want to have hekate on there as a multi boot menu, but mostly want something like SXOS autobooted, this makes life easier for those who don’t know how to edit the ini.
Edit: I accidentally pressed enter when I barely had finished writing the title, sorry
Edit 2: Screw autocorrect
Hey i noticed somethin odd i dont know how to fix it.
I try to make 3 partitions in Hekate with the newsest version. on my 512gb San disk Ultra its new
1 for hos
2 for emummc 29gb
and 3 for Android with 36gb
After i click on next step in the Partition manager and the manager is done i go in Windows in the Partition manager and it shows me Wrong sized Partitions. Normally it would show me 1 partiton with 400gb 1 with 29 and 1 with 36
but it shows me 2 x 400 gb and 1 time 29gb
This Problem comes on Three different Switches. With 3 Different SD cards.
Why is this so ?
Sometimes the Partitions are Really wrong and i cant install anything. So i have to delete the sd card the SD card Splitting in 30 little pieces i have to mannuly format them get them all together again. This cost my a lot of tiime in the past few days.
I installed on a few hundred Switches CFW this is new to me
I know sometimes hekate makes it wrong.
But on 3 different switches ? with 3 different sd cards ? What is wrong with Hekate and the Partition manager ?
this wasnt so on the version before i guess ? itry use older verisons but the bug comes Again.
This comes cover and over again whats to do ?
I had upgraded to OFW 11.
I found hekate 5.5 and l4t ubuntu. After installation, when I try to load ubuntu got this error.
Does anyone have similar issues?
Hello CTCaer
Would it be possible that for each EmuMMC partition for example RAW1 and RAW2 that they do not use the same emummc.ini but use their own .ini like emummc_raw1.ini and emummc_raw2.ini?
as far as I know you could then use in the eummmc_raw1.ini an own version of atmosphere with the so-called atmosphere_path=emuMMC/RAW1/atmosphere or ? and so we could have 2 different CFW like an atmosphere standard without much garbage and without overclocking (p.s good for my girlfriend since she misclicked and overclocked my switch to 2000+ MHz on CPU i use the OC Suite from KazushiMe) and on RAW2 an atmosphere with own sysmodules , tesla , OC Suite etc …. on a SD without that they overwrite each other.
After updating to the latest hekate and atmosphere last night ( 0.11.0 ) i am running into “no mandatory secmon or warmboot provided”. The issue still happens on 0.11.1. I’m able to boot. By chainloading fusee-primary from hekate but i cant boot atmo directly. My Google fu has failed me.
USB Gamepad pop-up tells that removing cable or pressing L3 + HOME will end HID emulation. While removing the cable indeed works, L3 + HOME does nothing.
cant load emunand due to ‘atmosphere/fusee-secondary.bin wrong ini cfg or missing/corrupt files’
When i try to launch something or when i want to use anything sdcard related, this error message comes out.
But when i press the sdcard reader (from the case) its working…
Do someone has a solution for this problem?
I am trying to update my Switch’s CFW and I keep getting this error. I have tried just about everything to fix it and nothing is working.
I have:
Updated the Atmosphere files on my SD card
Updated the Sigpatches on my SD card
Updated Hekate on my SD card
Updated hekate_ipl.ini to the following:
[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=0
[Atmosphere]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
[Atmosphere_emummc]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummcforce=1
[Original]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
And freshly installed everything.
After all of that, I still get the error «fss0:atmosphere/package3» and it has started to leave me frustrated. I could really use some help.
Edit: So after replacing the «fss0’s» in the ini file to «fusee» it boots to a different error message.
«No mandatory secmon or warmboot provided!»
«Failed to launch HOS!»
I would like to request you for emummc options when using payload chainloading. Emummc options such as emummcforce=1 works well on fss0, but won’t work on payload chainloading. If people use sxos or reinx which won’t work with fss0, emummc options won’t work with downgraded emummc.
While trying to perform Fix Archive Bit (all folders) the screen froze at this point. I’ve tried about 3 times to get past this point.
On the 3rd attempt, I pressed the close button at the top right and got this message
(It says specifically: Nyx exception occurred <LR 81000E84> DABRT)
I’m assuming that this might have something to do with the freezing of the Archive Bit but i’m not entirely sure.
i made the mistake and updated the switch to 15.0.1. And now i get this message «unknown PKg1 version».
Does someone know how to fix this?
i updated atmosphere but this did not help.
All the infos i could find about this topic are old as fish.
Thank you 