In the past two days, Atmosphere and Hekate released updates that stated "Mariko Support". I know that Mariko patched RCMSmash, so what are the current proposed methods to inject payloads on Mariko?
Via SX mod chip or fake mod chipIn the past two days, Atmosphere and Hekate released updates that stated "Mariko Support". I know that Mariko patched RCMSmash, so what are the current proposed methods to inject payloads on Mariko?
I'm pretty sure the very first Mariko systems released with firmwares vulnerable to Deja VuIn the past two days, Atmosphere and Hekate released updates that stated "Mariko Support". I know that Mariko patched RCMSmash, so what are the current proposed methods to inject payloads on Mariko?
Deja Vu cannot work on Mariko.I'm pretty sure the very first Mariko systems released with firmwares vulnerable to Deja Vu
Nope. That is for patched units only.I'm pretty sure the very first Mariko systems released with firmwares vulnerable to Deja Vu
*6.0.0Nope. That is for patched units only.
The lowest possible firmware on a Mariko unit is 5.0.0. HOS didn't even support Mariko before that version.
The only way currently to load payload on to a Mariko/Lite unit is via modchip.
Sent from my Pixel 4 XL using Tapatalk
I mean, just take a look at the latest patch notes
Please Note: Atmosphere is still not properly usable on Mariko hardware.
Do you need anything else to understand that Atmosphere doesn't support Mariko yet ?
- In particular, wake-from-sleep will not properly function (the magic numbers aren't set correctly), among a few other minor issues.
better TDP basicallyWhat is Mariko for ?
not properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usableIt is supported; just not fully supported yet
Are you dumb? They are supported on Mariko, their code can be executed and run on Mariko, a few bits that aren't supported doesn't mean that they are not supported.. Not properly usable is NOT the same as not supporting. Atmosphere and Hekate ARE supporting Mariko, this is stated as a fact in their changelog. You are the one who is trying to fool around.not properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usablenot properly usable
It can't be used on Mariko yet, so please stop, the topic's name is pure clickbait
Atmosphere won't boot on Mariko currently.Are you dumb? They are supported on Mariko, their code can be executed and run on Mariko, a few bits that aren't supported doesn't mean that they are not supported.. Not properly usable is NOT the same as not supporting. Atmosphere and Hekate ARE supporting Mariko, this is stated as a fact in their changelog. You are the one who is trying to fool around.
Yes I know, but Atmosphere's modules are runnable on MarikoAtmosphere won't boot on Mariko currently.
Well Atmosphere and Hekate will eventually be alternatives that you can run on the TX modchip because the support is currently incomplete for both.If I'm understanding correctly, Atmosphere and Hekate are advertising that they are now one of multiple available OS options you can use (instead of SX OS) on your Mariko Switch if you have a modchip. Whereas perhaps another OS might only have been designed to be compatible with V1 Switch.
Can someone confirm that that about sums things up? In other words, there is no reason to think that the solution to this modchip code/boot exploit situation is imminent?