Are you talking it to me?
Hmm, it was not that hard, i figured out it could be some of my sysmodules being not compatible with the latest Switch firmware update, so i opened my SD Card and deleted Sept and Atmosphere folders, copied whole AMS 0.11.1 again and Ta-Da! It booted correctly!
Last edited by TamarindoJuice,
Just for notification, since Atmosphere v0.11.1, DevMenu doesn't work anymore. I reported an issue which was closed due to it's illegal aspect:
https://github.com/Atmosphere-NX/Atmosphere/issues/898
I found from which part of code the issue comes and I did a second request for an evolution:
https://github.com/Atmosphere-NX/Atmosphere/issues/908
However, as I have very low hope that this request will be accepted, here is a modified file which allow Atmosphere v0.11.1 to run DevMenu again. It must be put in "/atmosphere/kips" folder if you run "fusee-primary.bin". If you do not trust it, you can recompile "loader.kip" from Atmosphere code with the following code removed in "ldr_meta.cpp", function "ValidateAcid":
/* Validate that the acid is for production if not development. */
if (!IsDevelopmentForAcidProductionCheck()) {
R_UNLESS((acid->flags & Acid::AcidFlag_Production) != 0, ResultInvalidMeta());
}
I perfom my test under FW 9.2.0, I didn't update yet due to the current chaotic situation for signature patches. I hope my modification will also work under FW 10.0.0.
https://github.com/Atmosphere-NX/Atmosphere/issues/898
I found from which part of code the issue comes and I did a second request for an evolution:
https://github.com/Atmosphere-NX/Atmosphere/issues/908
However, as I have very low hope that this request will be accepted, here is a modified file which allow Atmosphere v0.11.1 to run DevMenu again. It must be put in "/atmosphere/kips" folder if you run "fusee-primary.bin". If you do not trust it, you can recompile "loader.kip" from Atmosphere code with the following code removed in "ldr_meta.cpp", function "ValidateAcid":
/* Validate that the acid is for production if not development. */
if (!IsDevelopmentForAcidProductionCheck()) {
R_UNLESS((acid->flags & Acid::AcidFlag_Production) != 0, ResultInvalidMeta());
}
I perfom my test under FW 9.2.0, I didn't update yet due to the current chaotic situation for signature patches. I hope my modification will also work under FW 10.0.0.
Wait so just that kip by itsel works similarly to what sigpatches would?
By just having vanilla AMS with that loader.kip you'd be able to run DevMenu (and other unsigned) applications?
Yes but for the moment, I just tested it on FW 9.2.0 (with signature patches of course).
I don't know the status for FW 10.0.0 yet (and very specific path has been added for this new level).
EDIT: I also included a fix from Joonie which has been preserved by @HarukoNX. Here is the "loader.kip" which includes both fixes:
https://github.com/OperationNT414C/Atmosphere/releases/tag/0.11.1
Unfortunatly, after an update under FW 10.0.0, DevMenu from SDK 6.0.1 doesn't start anymore, even with those fixes. However, as it doesn't seem to be rejected by signature check ("return to HOME" panel), I suspect that, maybe, this DevMenu version, which is deprecated for a long time now, has some incompatibilities on FW 10.0.0. To test this theory, it would require the DevMenu from SDK 10.0.0 (if it exists).
I don't know the status for FW 10.0.0 yet (and very specific path has been added for this new level).
EDIT: I also included a fix from Joonie which has been preserved by @HarukoNX. Here is the "loader.kip" which includes both fixes:
https://github.com/OperationNT414C/Atmosphere/releases/tag/0.11.1
Unfortunatly, after an update under FW 10.0.0, DevMenu from SDK 6.0.1 doesn't start anymore, even with those fixes. However, as it doesn't seem to be rejected by signature check ("return to HOME" panel), I suspect that, maybe, this DevMenu version, which is deprecated for a long time now, has some incompatibilities on FW 10.0.0. To test this theory, it would require the DevMenu from SDK 10.0.0 (if it exists).
Last edited by OperationNT,
I guess it was bound to happen eventually, I'm surprised such an old version has worked for this long. Still, if there's one thing you can be sure of it's that people love to leak things so just a matter of time till another pops up.
I'm puzzled as to why that fork even exists -- why is tinfoil still requiring access to those things? Why is this being framed as "Atmosphere not supporting Tinfoil" instead of the exact inverse of that, which is that Tinfoil is intentionally not supporting Atmosphere by requiring more access than it needs to do its job. Am I missing something?
You're not missing anything. The move from a standardized homebrew environment to a homebrew NSP was an arbitrary decision on the part of @blawar, and there's no publicly known reason for Tinfoil to require the NAND access it does. That's his prerogative, but don't be fooled when someone tries to tell you it's Atmosphere that doesn't support Tinfoil; it's the other way around.
his fork does a lot of things. A fork is def required to boot tinfoil because atmosphere’s acid checks have to be patched out.
--------------------- MERGED ---------------------------
a kip in this instance is a fork.
It was your decision to develop Tinfoil in an unstandardized environment. An Atmosphere fork definitely isn't required. Ask virtually any other homebrew developer.
To steal our Nintendo login / cert ?
The reason is known: firmware installs and incognito install. You are spreading fud
--------------------- MERGED ---------------------------
It's nintendo's standard, the most standard of standards
You'd need NEUTOS or SX OS. Or a SX OS license to use Tinfoil, Tinfoil will remove the three files if they exist on your console and you hit Y on the red screen.
patches.ini
loader.kip
ams_mitm.kip
loader.kip
ams_mitm.kip
While atmosphere sigpatches "exist", tinfoil would remove patches.ini making it useless for Tinfoil.
The reason is known: firmware installs and incognito install. You are spreading fud
Who knows, I don't have your github / source code
For some reason they want us to leave our
curent setup
Last edited by chocoboss,
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
-
Xdqwerty
what are you looking at? -
realtimesave
-
Psionic Roshambo
-
-
-
-
-
-
-
@
Psionic Roshambo:
@SylverReZ, in my experience, I wouldn't say I am an audiophile because to me MP3s seem fine, frequency cut off but good enough lol although in my laundry list of freak gifts... Is the ability to hear frequencies beyond what anyone else I have ever met... I max out hearing tests with shocked looks from the Drs, sad part is I can hear frequencies much higher.+1
-
-
-
@
Psionic Roshambo:
I am thankful florescent lights are mostly LED now... And TVs are far less annoying lol
-
-
-
-
-
@
SylverReZ:
@Psionic Roshambo, As somebody who has listened to music over everything, I prefer some good quality headphones that can output the sharpest audio. I listen to my music mostly with WAVE or FLAC files, with MP3s I can tell the difference straight away by the compression artifacts.+1 -
-
-
@
Psionic Roshambo:
I mean I can tell the difference even with a high bitrate MP3 but I guess "it sounds good enough"
-
@
Psionic Roshambo:
Plus studio quality MP3's do exist, they are just like 512Kbps and are huge ass files lol
-
-
-
@
SylverReZ:
@Psionic Roshambo, MP3s were designed to be as small as possible, so that they can be shared on the internet. WAVE files were more bigger in size and would take hours to upload back in the day.
-
-
-
