Error fatal error nxboot unable to identify package nintendo switch

nintendo switch fatal error nxboot unable to identify package 1 #1415

Bug Report

[ If any section does not apply, replace its contents with «N/A». ]

[ Lines between [ ] (square brackets) should be removed before posting. ]

[ Note: If the bug or crash you encountered is related to; ]

[ — software used to make «backups», ]

[ — software explicitly distributed for piracy, etc ]

[ then contributors will not provide support for your issue and your issue will be closed. ]

What’s the issue you encountered?

[ Describe the issue in detail and what you were doing beforehand. ]

[ Did you make any changes related to Atmosphère itself? ]

[ If so, make sure to include details relating to what exactly you changed. ]

How can the issue be reproduced?

[ Include a detailed step by step process for recreating your issue. ]

Crash Report

[ Crash reports can be found under /atmosphere/crash_reports . ]

[ If your issue caused Atmosphère to crash, include the crash report(s) by creating a gist and pasting the link here. ]

[ If you don’t include a crash report in instances of crash related issues, we will ask you one to provide one. ]

System Firmware Version

[ Replace X’s with system firmware version at time of crash. ]

[ You can find your firmware version in the Settings -> System, under «System Update». ]

[ If it says «Update Pending», you can clear the pending update by rebooting to Maintenance Mode. ]

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
• Official release or unofficial build:
  • [ Official release version x.x.x (or) unofficial build ]
  • [ If using an unofficial build, include details on where/how you acquired the build. ]
    • [ Ex: Self-compilation ]
    • [ Ex: Kosmos’ distribution of Atmosphère ]
• Do you have additional kips or sysmodules you’re loading:
• Homebrew software installed: [ * ]

Additional context?

• Additional info about your environment:
• [ Any other information relevant to your issue. ]

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

Источник

«Fatal error: [NXBOOT]: Unable to identify package1!» #1640

Updated the nitendo switch to the latest version 13.0.0.
And I did the last download of the atmosfere and installed everything correctly with the «RCM Loader» and the screen goes all black and if I try again it looks like «Fatal error: [NXBOOT]: Unable to identify package1!».

What should you do to get the atmosphere back on track?

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

you have not used the details of the template please open a new one because without a template it will simply be closed please folks please do yourself a favor it saves you time and you don’t have to rewrite it over and over again your problem with atmospehre!

I’m starting with Fusee.
And how do I do this from the model details?

Hi guys if u use new atmosphe downgrade the consol to 12.1 and wait atmosphere for 13.0

The new atmosphere for Hos 13.0.0 has long been published!

There is a loot of beugs so still waiting the final version of atmosphere

At this moment it already appears to me «Fatal error: failed to stat stage2 (fusee-secondary.bin)!»

@abdelmoumen03 there have been zero actual bugs so far. Just user errors.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Hacking Switch possibly bricked?

Weyay

Member

blahblah

Well-Known Member

Weyay

Member

blahblah

Well-Known Member

ZachyCatGames

Well-Known Member

Or they’re somehow running a firmware that Atmosphere doesn’t support/recognize at all (I have a few firms that are like this, like 20161011093138)

though I doubt this is the case here

Canna

Bad Ass Poisonous Mushroom

first of all you updated to 8.0
second of all you downgraded to older firmware,
not thinking of the fuses burned.

1
try running hekate payload first then ofw,

2
Restore your original backup again, making sure to restore the boot0/1 files that come with your backup, using boot0/1 of other system version wont work..

3
use choidujour.exe to build system files and boot0/1 for 5.1.0
flash the boot0/1 files with etcher from choidujour.exe ouput folder,
then run hacdiskmount,enter all your biskeys in the correct places save them,then replace the system files from the output folder of choidujour.

4
Use biskeydump payload and get your system specific keys, or i think lockpick now gets them also.

Skip steps 1,2,3 and start at 4 (only if you have a nand backup)

Источник

Hacking Error when updating switch

SarahShouldNotPlayHacker

New Member

Hi! So today I tried to update the firmware of my switch, since I couldn’t play ACNH in the old version. I downloaded the 0.9.1 since a friend has same version as me and we did it together. Difference is hers worked, mine didn’t.

I used the bunny app thing to load it. Good. Then reboot it. Fail. Copied the new payload to pc, injected it with Tetra and Hekate opens. Then, I try to launch Atmosphere but the screen goes black and gives me an error message.

FATAL ERROR [NXBOOT] Unable to identify package1!

I guess it is a payload issue but it shouldn’t be right? I don’t know what to do anymore.

Can you help me out?

Draxzelex

Well-Known Member

Hi! So today I tried to update the firmware of my switch, since I couldn’t play ACNH in the old version. I downloaded the 0.9.1 since a friend has same version as me and we did it together. Difference is hers worked, mine didn’t.

I used the bunny app thing to load it. Good. Then reboot it. Fail. Copied the new payload to pc, injected it with Tetra and Hekate opens. Then, I try to launch Atmosphere but the screen goes black and gives me an error message.

FATAL ERROR [NXBOOT] Unable to identify package1!

I guess it is a payload issue but it shouldn’t be right? I don’t know what to do anymore.

Источник

Unable to identify package1 #734

I had posted earlier about the fusee-secondary file not being read, now it is saying that it is unable to to identify package1

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

@RoyallyOblivious it really sounds to me like you’re not actually using the latest release fusee-primary + fusee-secondary. Please make sure you’re using the latest release binaries.

I am using Tegra to go into CFW, is that an issue? What are the new releases? I’m still learning to do this

You need the latest payload, along with the latest Atmosphere release. I’d recommend

• backing up SD:/atmosphere and SD:/sept
• deleting those folders
• deleting your old Tegra atmo payload
• grabbing zip + fusee-primary from https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.10.0
• extracting the whole zip to your SD card to get the latest atmo/sept files
• using latest fusee-primary with Tegra
  As long as your thing can serve payloads, I don’t thiiiink it matters what you use?

What’s atmo and I’m using the recent release of Tegra to load the CFW, I already have entered the RCM on the switch, but I’m having no luck

latest version of Atmosphere. You need to update sd:/atmosphere, sd:/sept, and the xxx.bin file you use with Tegra every time an update comes out

I got the atmosphere screen up and then it goes to the nintendo logo after it loads, is that normal, what else should i do? This is the farthest I have gotten, so now what else do I need to do?

That’s normal, after that it should just boot same as a normal Switch. Did it pop up with a crash log or make a file or something?

@NWPlayer123 nope, so what do I do to access the home brew and to edit my game data?

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Игровая консоль Nintendo Switch в продаже уже больше 5 лет (с 2017-го) и, очевидно, пользуется стабильной популярностью.

Девайс как минимум очень удобный — играть на Switch-е можно и дома (на большом экране), и в мобильном режиме вообще где угодно.

Но всякие сбои, баги, ошибки и прочие неприятности у Switch-а, как известно, тоже случаются. О чем мы повествуем регулярно и, есть такое подозрение, повествовать будем еще не раз.

И в продолжение темы — вот наш большой справочник по кодам ошибок Nintendo Switch, в котором мы постарались собрать все самые распространенные из них. С кратким описанием по каждой из проблем и, разумеется, с предложениями относительно того, что и как в каждом отдельном случае надо делать.

Пост этот мы наверняка будем дополнять (по мере сил и возможностей), но пока получается примерно следующее. Итак, по порядку:

#1 — Проблемы с аппаратной частью консоли

Не пропустите: ОШИБКА 2002-3537 У SWITCH: ЧТО НАДО СДЕЛАТЬ

#2 — Общие проблемы Switch

Не пропустите: ОШИБКА 2123-1502 У SWITCH-А ПОСЛЕ ОБНОВЫ: ЧТО МОЖНО СДЕЛАТЬ САМОМУ

#3 — Проблемы с ПО Switch

Не пропустите: ЕСЛИ MORTAL KOMBAT 11 НА SWITCH ВЫЛЕТАЕТ: ЧТО ДЕЛАТЬ? [АРХИВЪ]

#4 — Проблемы с подключением Switch

Не пропустите: ОШИБКА 2137-8056 В SWITCH: ЧТО ОЗНАЧАЕТ И КАК УСТРАНИТЬ [АРХИВЪ]

#5 — Проблемы на стороне сервера

Не пропустите: КОГДА ДОК-СТАНЦИЯ SWITCH МИГАЕТ ЗЕЛЕНЫМ И НЕ РАБОТАЕТ: ЧТО ДЕЛАТЬ?

#6 — Проблемы с картой памяти MicroSD

Не пропустите: ЕСЛИ ЛАГАЕТ ЗВУК У SWITCH ПОСЛЕ ПОДКЛЮЧЕНИЯ К ТЕЛЕКУ: ЧТО МОЖНО СДЕЛАТЬ?

#7 — Проблемы Switch в некоторых играх