Hacking Atmosphere not booting

  • Thread starter Thread starter phobos7445
  • Start date Start date
  • Views Views 2,965
  • Replies Replies 10

phobos7445

Member
Newcomer
Joined
Dec 5, 2020
Messages
8
Reaction score
0
Trophies
0
Age
45
XP
121
Country
Germany
Hi friends,

I'm not new to the community but just registered to post my problem.

Once I load ctcaer 5.5 via RCM loader I can boot into Hekate. Once I select fusee primary, I cant boot into atmosphere and the screen turns black. AMS 0.16 was working before. Ideas anyone?
 
Hi friends,

I'm not new to the community but just registered to post my problem.

Once I load ctcaer 5.5 via RCM loader I can boot into Hekate. Once I select fusee primary, I cant boot into atmosphere and the screen turns black. AMS 0.16 was working before. Ideas anyone?
Hi
Did you copy paste new AMS 0.16 files or overwrite old ones? Something old must be blocking the launching so try a clean set up.
 
Well, I did set up everything from scratch and now AMS is booting. However, I cant boot the emunand (I think its due to AMS being in pre-release status). Once it did boot via sysnand, I cant use any apps like Tinfoil or other homebrew.

But thats another topic, right. The release of AMS is still a pre-release and I see a few users here complaning about issues with the pre-release AMS.
 
Hi friends,

I'm not new to the community but just registered to post my problem.

Once I load ctcaer 5.5 via RCM loader I can boot into Hekate. Once I select fusee primary, I cant boot into atmosphere and the screen turns black. AMS 0.16 was working before. Ideas anyone?
Try booting into Atmosphere directly with Hekate and don't use fusee.
 
I've got the same problem with Atmos 0.16.1. I can't get it to boot without it being the EXPERIMENTAL version, and when that boots the sigpatches don't work. I dunno where I went wrong. Did op ever figure it out?
 
I've got the same problem with Atmos 0.16.1. I can't get it to boot without it being the EXPERIMENTAL version, and when that boots the sigpatches don't work. I dunno where I went wrong. Did op ever figure it out?
There are new patches for the latest version of Atmosphere.
 
I ended up downgrading to 11.0 and 16.0 atmos, there was no combo of cfw/sigpatches that I could get working on 11.0.1/16.1.
 

Site & Scene News

Popular threads in this forum