Any idea if the next Atmosphere release (14) will create compatibility for people with the SX Core on patched/mariko?
Thanks, SciresM. I view your Twitter from time to time too. You do amazing things so again thank you!
hey Scires by chance do you happen to know what causes the fatal error on atmosphere after updating the emuMMC from 9.x up to the latest 10.x?
I've been experimenting on two consoles and while in one I fixed it by doing a fresh instal of the tmos files the other one persist no matter what I do
I've been experimenting on two consoles and while in one I fixed it by doing a fresh instal of the tmos files the other one persist no matter what I do
【https://t.co/k1vfl5raSg】記事を投稿しました！「MarikoでのAtmosphère MODチップには依存しない方向」- https://t.co/NA0acNiZI4 pic.twitter.com/kwGGIeL5gO
— mamosuke (@mamo_suke) July 11, 2020
I have exactly this problem... I've been messing around for a while and I still cannot make it work.
Can somebody help with this issue? Or maybe give me an idea what can I check for?
I'm using hekate to launch fusee-primary.bin, I have exosphere.ini created on the root of my micro SD card with blank_prodinfo_emummc=1, I also have a hetake_ipl.ini to launch atmosphere from there (with cal0blank=1).
I've been looking for answers in the forums, but either people make the blank_prodinfo_emummc=1 change and it is working, or simply it has been unanswered or solved in a mysterious-non explicit way.
As a side note, I have atmosphere (10.0.4) + hekate (5.3.0) up to date.
Any help will be greatly appreciated!
Edited: Well... after hours of trying several things to fix this, I've seem to notice that I was erroneously using outdated files (from NX-Atmosphere it seems..) even when I downloaded the latest version of Atmosphere and Hetake. Now I made sure to erase everything on my SD card and reupload all up to date files and... It is now (finally!) working! I hope this helps someone who happens to be in the same spot that I was!
Last edited by Zeus2u,
Tweet translation:
...it's a discussion article, not a mod release or anything, in case the pic gets anyone's hopes up.
one question what exactly is the Homebrew app Daybreak for? (included in ams)...for updating the HOS Firmware or for updating AMS?
whats shitty on ChoidojourNX?
--------------------- MERGED ---------------------------
i am desperate i need help because of my modchip but in the Fusee Suite thread no one answers me nor in my new created thread.....can i get help elsewhere?
--------------------- MERGED ---------------------------
i am desperate i need help because of my modchip but in the Fusee Suite thread no one answers me nor in my new created thread.....can i get help elsewhere?
i doubt its less shitty because ChoidojourNX reconized the FW Package for 10.1.0 i had but Daybreak told me it couldnt find any update lol
It often silently fails and doesn't work at all on non-production environments.
Far from what I'd call perfect.
but ChoiJudourNX reconized my 10.1.0 FW Package and Daybreak didnt....it told me there is no Firmware...so.....
Files didn't have the correct file extensions.
(Edit: daybreak needs meta ncas to have a ".cnmt.nca")
Last edited by ZachyCatGames,
i am using the StarDustCFW Package and my settings say AMS 0.14/10.1.0..... but i dont see 0.14 is released or am i stupid
--------------------- MERGED ---------------------------
ok that was the reason i guess
--------------------- MERGED ---------------------------
ok that was the reason i guess
0.14.0 isn't released yet, whoever made that pack probably compiled an unfinished version themselves.
It's planned to release sometime this week iirc.
oh ok weird
--------------------- MERGED ---------------------------
the guy who made it is named Kronos2308 or something like that ill ask him
--------------------- MERGED ---------------------------
the guy who made it is named Kronos2308 or something like that ill ask him
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
