Hacking Question Error 2495-1623 on boot after upgrading to Atmosphere 0.7.3 to 0.7.4

Essasetic

General Spectator
OP
Member
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
Can anybody help me try and resolve this error? I'm not sure if it's happened to anybody else yet but this happens everytime I try to boot Atmosphere (after upgrading to 0.7.4) via Hekate.
 

ZachyCatGames

Well-Known Member
Member
Joined
Jun 19, 2018
Messages
3,398
Trophies
1
Location
Hell
XP
4,209
Country
United States
Are you loading all the kips and exosphere through Hekate or are you just loading fusee-primary through Hekate. Usually you'll get that error if any part of Atmosphere doesn't match the same version as the rest, which probably means you didn't update something
 

Essasetic

General Spectator
OP
Member
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
I've tried using SDFiles v11 but that hasn't worked. Tried replacing 0.7.4 with 0.7.5 but that didn't work either. I'll either revert back to 0.7.3 or move back to Reinx. I really hope this is resolved for the next release.

--------------------- MERGED ---------------------------

Ok now 0.7.3 doesn't work so idk what I've done wrong :/

--------------------- MERGED ---------------------------

UPDATE: Wiping the atmosphere folder and coming with a clean config fixed everything. (Used SD Setup btw) so currently running 0.7.4! I'll see if I can get 0.7.5 working without wiping the atmosphere folder again.

UPDATE #2: It looks like you'll have to wipe the atmosphere config everytime you update. Make sure to backup mods beforehand though.
 
Last edited by Essasetic,
A

a9lh-1user

Guest
It would be the best if you DONT upgrade by COPY everything into the OLD FOLDERS!
Make a CLEAN install by DELETING everything (before) copy from the NEW release!

DON'T COPY AND PASTE THE NEW RELEASE that will NEVER work! (Most of the time ;))
 
  • Like
Reactions: Deleted User

Essasetic

General Spectator
OP
Member
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
It would be the best if you DONT upgrade by COPY everything into the OLD FOLDERS!
Make a CLEAN install by DELETING everything that you copy from the NEW release!

DON'T COPY AND PASTE THE NEW RELEASE that will NEVER work! (Most of the time ;))
That's what I literally just said lol
 

Paffo

Well-Known Member
Member
Joined
Aug 10, 2018
Messages
105
Trophies
0
Age
43
XP
568
Country
Italy
It doesnt work on me either. Same error. Im not loading it via fusee-primary, but via hekate. Might be it?
 

edtemp

Member
Newcomer
Joined
Oct 8, 2018
Messages
15
Trophies
0
Age
44
XP
86
Country
United States
I'm getting this error too with sdsetup.com

I was trying to switch from reinx to atmosphere. I deleted everything off the SD except the Nintendo and switch folders. On sdsetup.com, all I chose were minimal, enable sig patches, and under payloads both hekate and fusee-primary.

Went back to reinx for now. Hopefully a stable release will be out soon with the 32 launch fix.

edit: I was pushing the fusee-primary payload
 
Last edited by edtemp,

Essasetic

General Spectator
OP
Member
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
I'm getting this error too with sdsetup.com

I was trying to switch from reinx to atmosphere. I deleted everything off the SD except the Nintendo and switch folders. On sdsetup.com, all I chose were minimal, enable sig patches, and under payloads both hekate and fusee-primary.

Went back to reinx for now. Hopefully a stable release will be out soon with the 32 launch fix.
You need to compile your own kips to get it to work. That's how I got it to work.

--------------------- MERGED ---------------------------

It doesnt work on me either. Same error. Im not loading it via fusee-primary, but via hekate. Might be it?
Same issue. Same solution.
 

edtemp

Member
Newcomer
Joined
Oct 8, 2018
Messages
15
Trophies
0
Age
44
XP
86
Country
United States
You need to compile your own kips to get it to work. That's how I got it to work.

--------------------- MERGED ---------------------------


Same issue. Same solution.
Read on reddit that sdsetup/kosmos is only designed to boot with hekate, so I went back and tried that and it works.
Same setup as I described in my previous post, but pushed hekate and booted the CFW option after launch. Pushing fusee-primary from tegrarcmgui or chainbooting from hekate both don't work, so I don't know why sdsetup even includes that option.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Gong