Hacking Atmosphere error Unknown pkg1 version

  • Thread starter Thread starter saadibadr
  • Start date Start date
  • Views Views 29,292
  • Replies Replies 14

saadibadr

Member
Newcomer
Joined
Jan 10, 2021
Messages
6
Reaction score
0
Trophies
0
Age
35
XP
80
Country
Morocco
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.
 
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
 
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.
 
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
 
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...

------------------------------------------------
 
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
 
  • Like
Reactions: laramie
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.
 
Last edited by urherenow,
  • Like
Reactions: ucef
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
 
Last edited by saadibadr,
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
 
Hey guys,

Finally, i got a boot0.bin donor and i did a backup with that file, problem solved ^^

Thanks to everyone for help !
 
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
 
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?
 
Last edited by MarkBaker,

Site & Scene News

Popular threads in this forum