Homebrew error 2002-4373 (0x222a02)

Tthat1guy

Member
OP
Newcomer
Joined
Apr 12, 2024
Messages
7
Trophies
0
Age
24
XP
38
Country
United States
got this error randomly as I loaded a game installed using tinfoil on my mariko w switch. turning off the switch and running the payload gives the same error right after the switch logo appears. when loading into OFW it gets stuck on the switch logo. this error happened when I was running atmosphere 1.70 on firmware 18.0 and I updated atmosphere to 1.71 to try to fix it. from what I've seen on other threads this issue is a corrupted nand and the solution is to wipe it by going into the switch repair mode (by pressing both volume and power) it just stalls on the switch logo the same as if I try to boot into OFW

picture.jpg
 

Tthat1guy

Member
OP
Newcomer
Joined
Apr 12, 2024
Messages
7
Trophies
0
Age
24
XP
38
Country
United States
Did you try looking for a 010000000000001F folder in atmosphere/contents and deleting it?
there is only one file labeled 420000000000000B in atmosphere/contents
Do you have an exosphere.ini file? If so, paste it here.
[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0
(taken from the rentry guide)
 

Tthat1guy

Member
OP
Newcomer
Joined
Apr 12, 2024
Messages
7
Trophies
0
Age
24
XP
38
Country
United States
blank_prodinfo_emummc=1 <-- there is your issue.

Since FW 18 they crash if you boot with prodinfo blanking and not using 90DNS or DNSMITM

EDIT: DNSMITM is recommended to use anyway - https://rentry.org/ExosphereDNSMITM
I changed blank_prodinfo_emummc=1 to =0 and got the same error
Post automatically merged:

I got the same probleme recently did you add exefs_patches (ips)
whats that? I'm somewhat new to switch modding.
Post automatically merged:

I'm pretty sure that I install
I got the same probleme recently did you add exefs_patches (ips)
I installed exefs _patches and still get the same error
 
Last edited by Tthat1guy,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    SylverReZ @ SylverReZ: @DinohScene, HEY DINOHSCENE