Error code 2168 0002

Unable to launch atmosphere, error code 2168-0001 & 2168-0002 #1582

Bug Report

Unable to launch atmosphere

What’s the issue you encountered?

This is my first time trying to hack a switch, so I hope I’m just doing something wrong. Here is a screenshot of the error

I have reinstalled all the files a couple of times, and reformatted my SD card (format is MSDOS fat-32) in an effort to try every possible solution. I could really use some help as I’m totally stuck.

How can the issue be reproduced?

I put in the SD card, the dongle on the right, and the injector, successfully loaded Hekate, went to launch > CFS (sysMMC). The Nintendo logo and Atmopshere logo loaded, and then I received the above error, with code 2168-0001

Here is a link to the exact files I downloaded:
https://www.sdsetup.com/console?switch#atmosphere;atmos_musthave;hekate_musthave;tesla_menu;atmos_ovlloader;atmos_sys-clk;atmos_sysftpd;ovl_sysmodules;appstorenx;hbmenu;edizon;goldleaf;nxdumptool;hekate;lockpick_rcm;

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?

hekate/fusee was used, and I used the files shown in the above link at sdsetup.com

Additional context?

I bought a used switch online that has been banned from the internet. I am using RCMLoader One. The files used are the generic install recommended for fussee-gelee in switch.homebrew.guide. The SDcard is a micro-sd card

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

Источник

Error when trying to install an app from the homebrew store #695

##What’s the issue you encountered?

Received Error code: 2168-0002 (0x4a8)
after trying to install any app within the homebrew store.

How can the issue be reproduced?

Tried to install a different app and issue persisted.

System Firmware Version

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Hekate
• Official release or unofficial build: official 5.0.2
• Do you have additional kips or sysmodules you’re loading: NO
• Homebrew software installed: None since it wouldn’t let me

Additional context?

• Additional info about your environment:
  Running CFW through EMUMMC SanDisk 128GB exFAT SD Card

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

Open hbmenu from a title. Also format your sd as fat32, exfat is asking for a bad time.

«2168-0002» is a userland data abort, sounds not like an atmosphere problem.

Also, «homebrew store» is not supported or recommended.

Open hbmenu from a title. Also format your sd as fat32, exfat is asking for a bad time.

What do you mean open from a title?

«2168-0002» is a userland data abort, sounds not like an atmosphere problem.

Also, «homebrew store» is not supported or recommended.

Could you please elaborate? I understood the homebrew store not being supported or recommended but what does the userland abort mean? do I need to fix something in my files?

It means that the homebrew’s code is accessing invalid memory — it’s a homebrew store problem, not an atmosphere problem.

It means that the homebrew’s code is accessing invalid memory — it’s a homebrew store problem, not an atmosphere problem.

Thank you, now I understand the issue. I will find the app and open in a different way via .nro I guess.

Источник

Hacking Suggestion For those who also have trouble with homebrew (atmosphere 2168-0002 error)

Treskatae

Member

If you get error 2168-0002 or similar errors when trying to use homebrew apps, or trying to install any .nro’s or nsp’s, this is what I did to fix it. After days of throwing everything at the damn thing, I’m up and running and back to normal. I’ll list everything I did, but I’m pretty sure what fixed it is installing ReinX and removing atmosphere AND/OR upgrading my firmware.

• First thing I did was remove Atmosphere and tried setting it up from a fresh download.
• After that didn’t work, I tried launching the homebrew app store by running the nro through goldleaf (people online were saying you have to do this because there’s not enough memory in applet mode).
• After that also didn’t work and I tried to weasel my way around it 6 ways from Sunday, I nuked my sd card totally reformatted. First I formatted through the Switch’s options, then I formatted to FAT32 via PC. Then I tried building a whole new SD card from the set-up. Surely it would work this time.
• You get the idea by now it didn’t work of course it didn’t. So then I tried just installing ReinX and hbmenu to see if I could do that.
• It worked! Just kidding. It didn’t work either. At first. First it wouldn’t let me into the menu at all. Title override was not functioning. I read that you can get around this by using hekate, so I installed all that stuff. This caused ReinX to hang after the first splash image. Something told me I should try again, but copy over the ReinX files from the sd builder with the files I had downloaded directly from ReinX’s website.

Finally I was able to get into the menu, get into the app store, and tried installing something. After homebrew installs causing my Switch to crash 379 times I just knew it was going to crash again. But it didn’t. What a freaking escapade just to use a different SD card.

Only problem I have now is that Goldbricks either freezes when I connect to USB, or it can’t find any files. I’m using an alternative method that works fine, though.

The problem started after I tried using a new SD.

Источник

Hacking Question Error Code 2168-0002 booting SX OS

gamecaptor

R.I.P. Densetsu. Legends never die!

Let me begin by stating I am a dumb @$$. I haven’t touched my hacked Switch in a while and I should have done more homework prior to me doing anything with it.

My setup is SX OS v2.9.2 with an EmuNAND CFW.

I went to test out a game and it required an update. I can’t recall what version the CFW OS was previously, but I was updating to 9.0.1. Here is the first mistake I made. I did the update via the CFW Switch OS. Now when it boots (after both the Nintendo and Switch logos) it says:

Error Code: 2168-0002
Oops! Something went wrong.
Your switch ran into a problem and needs to be restart.
To restart SX OS press the power button.

(p.s. that bad grammar is not mine, that’s really what it says).

SO THEN I remembered the right way to update the CFW OS was via ChoiDujourNX.

I followed the instructions below to update the original (non-EmuNAND) CFW to 9.0.1 so I can try said new game and now I get the same error message on it. The original CFW is now having the same error as the EmuNAND CFW:
Error Code: 2168-0002
https://team-xecuter.com/community/. ine-nintendo-switch-with-choidujournx.128170/

So at the moment only the official Switch FW is booting fine (v9.0.1) and I’m not touching it!

Any recommendations on how to clear this up? I’m good with wiping everything out and starting over if this is what it takes. This is just my test before I buy Switch so there is nothing important on it.

I’ve also been reading there really isn’t a big need for the EmuNAND. Is that the general consensus or is it a good thing to have/use?

Источник

Hacking Updated to 9.1.0 — Error 2168-0002 on atmosphere boot (emunand)

onibaku

Lurker

I have an ipatched unit on 4.1.0. I have emunand set up and I did the following:

updated to atmosphere 0.10.1 (replaced the old 0.9.4 atmosphere contents with the new)
updated hekate (replaced the old hekate contents with the 5.1.0 contents)
updated sigpatches (via the sweet patches thread)

I then updated my emunand firmware using choidujourNX from 9.0.1 to 9.1.0 (fat32 and im sure i selected the correct option) but when i try to boot into atmosphere, i get the error message «Error 2168-0002». I tried multiple times but the same error pops up immediately on boot. I saw the lockscreen once for a split second before the error popped up.. any idea what could be causing this?

I have previously tested my SD card using h2testw and it is a legit SD card.

Thanks in advance..

EDIT: So I tried to redownload all the atmosphere files and replace them again however, the same error pops up. any help would be greatly appreciated as I’ll be travelling soon and would really like to take my Switch with me

should i just format everything and redo the entire partition process and emunand setup process? I was hoping there would be an easier fix..

FINAL EDIT: I managed to fix it by removing the atmosphere, bootloader and sept folders from my sd card and putting fresh ones in from the latest updates.

Источник

tl;dr: turn off your router before trying to turn on your switch then delete your network settings.

Hi, So I had been experiencing occasional 2168-0002 errors on and off on my switch. When I got home tonight after a flat battery, I put it in the dock and my switch was stuck in a continuous boot-loop with this damn error…

After researching online the only common thread was that this occurred after a network outage, which made me realise that I too had had a network outage recently… <tinfoil> I’m suspecting it might have been caused by the switch somehow now </tinfoil>…

Anyway, I decided that since the switch was in the vicinity of my network it might be having problems on connection. I turned off my router, powered up, and hey-presto the problem was gone!

I’ve decided to delete my network connectivity (5ghz) and reconnect at 2.4ghz as the 5ghz thing was also a common theme in my research…

Hopefully it won’t come back, but for now it looks good, and I hope that this post helps other people too!

Thanks, ultimatechipmunk

submitted by /u/ultimatechipmunk

[link] [….]

…

Игровая консоль 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 в некоторых играх