Discussion Atmosphere and Hekate now supports Mariko

Via SX mod chip or fake mod chip

 

but why didn't anyone even post it as news here when atmosphere was updated to support 11.0 ?

 

I'm pretty sure the very first Mariko systems released with firmwares vulnerable to Deja Vu

 

Atmosphere cannot be used on Mariko yet.
The cfw for the modchip still needs to be released (also hekate will not let you boot AMS unless it’s AMS 0.17.0 or above).

— Posts automatically merged - Please don't double post! —

Deja Vu cannot work on Mariko.
It relied on a bootrom exploit

 

Nope. 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.
correction, see post below.

The only way currently to load payload on to a Mariko/Lite unit is via modchip.

Sent from my Pixel 4 XL using Tapatalk

 

*6.0.0
(That’s not the issue though, Deja Vu works upto 7.0.1 on Erista. Mariko doesn’t have the bootrom bug it needs, as said above)

 

Okay, so how to use it with the modchip? Any tutorials? My modchip is otw so i would like to prepare these stuff beforehand, if any

 

I mean, just take a look at the latest patch notes

Please Note: Atmosphere is still not properly usable on Mariko hardware.

• In particular, wake-from-sleep will not properly function (the magic numbers aren't set correctly), among a few other minor issues.

Do you need anything else to understand that Atmosphere doesn't support Mariko yet ?

 

What is Mariko for ?

 

better TDP basically
in other words you get like 20 % better battery life

 

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.

 

Call me dumb if you want, you said it yourself, it's not « fully » supported.
Well then it's just not, for the moment, but you'll want to calm your ass.
I « fool » around because I found your title misleading, what did changed from last time ? iirc it's not the first time they updated with some work on Mariko, so I don't understand the « now supports Mariko » because in the end it's still not running. Re-reading the patchnote, they said Atmosphere now supports 11.0 because it actually runs, nothing about « now supports Mariko » so again, I find that very misleading so I'm wondering why you say that.
I mean, they said they added support for some components to run on Mariko, but didn't they already did on some other before ? Because if yes, you could have said that it added support for Mariko by then.

But whatever, if it's enough for you to be happy and say that the whole OS now supports Mariko, I guess that's fine ? I mean, still wouldn't be right, but it's fine.

 

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?

 

Well Atmosphere and Hekate will eventually be alternatives that you can run on the TX modchip because the support is currently incomplete for both.