Hacking SX Modchip firmware has been dumped

[gcrash]

In case you've missed it. The first release of spacecraft-nx has arrived.
github[dot]com\Spacecraft-NX\firmware (I cannot post any links yet)
Just tested it on my sx-core in an patched errista switch and it works perfectly. And even faster than the official sx firmware.
I just had a mistake with the debug connector which i installed the wrong way around, so if your chip doesn't power on check if the up writing is visible when your switch is face down.

 

[MaxiBus]

In case you've missed it. The first release of spacecraft-nx has arrived.
github[dot]com\Spacecraft-NX\firmware (I cannot post any links yet)
Just tested it on my sx-core in an patched errista switch and it works perfectly. And even faster than the official sx firmware.
I just had a mistake with the debug connector which i installed the wrong way around, so if your chip doesn't power on check if the up writing is visible when your switch is face down.

FINALLY!!! THX!

 

[hartleyshc]

FINALLY!!! THX!

Don't get too excited if you're on Mariko.

It doesn't boot sx, it will boot atmosphere/Hekate only on Erista.

As of right now, if you have a Mariko device you're not going to be able to boot anything besides Hekate and just look and use the menu. It will not load atmosphere and you still cannot load fusee-primary on Mariko.

Sent from my Pixel 4 XL using Tapatalk

 

[britain4]

Don't get too excited if you're on Mariko.

It doesn't boot sx, it will boot atmosphere/Hekate only on Erista.

As of right now, if you have a Mariko device you're not going to be able to boot anything besides Hekate and just look and use the menu. It will not load atmosphere and you still cannot load fusee-primary on Mariko.

Sent from my Pixel 4 XL using Tapatalk

That's only until Atmosphere is updated though correct? Which hopefully should be imminent.

Great news we have a path forward with the chips now in case TX stop with the updates.

 

[hartleyshc]

That's only until Atmosphere is updated though correct? Which hopefully should be imminent.

Great news we have a path forward with the chips now in case TX stop with the updates.

Yes. Which is probably the main reason it hasn't been posted about yet. It's been out for a bit now, but there's absolutely no reason to install it until a new version of Atmosphere comes out. Erista can already load Hekate/Fusee from the payloads menu. If someone is on Mariko, they're device will pretty much be useless until whenever atmosphere 17 comes out. Next Juneteenth.

And for people who compile their own version of Atmosphere, there's still bugs currently in the power delivery that can cause permanent damage to a lite.

Sent from my Pixel 4 XL using Tapatalk

 

[MaxiBus]

Don't get too excited if you're on Mariko

Its great news anyway

 

[Adran_Marit]

Yes. Which is probably the main reason it hasn't been posted about yet. It's been out for a bit now, but there's absolutely no reason to install it until a new version of Atmosphere comes out. Erista can already load Hekate/Fusee from the payloads menu. If someone is on Mariko, they're device will pretty much be useless until whenever atmosphere 17 comes out. Next Juneteenth.

And for people who compile their own version of Atmosphere, there's still bugs currently in the power delivery that can cause permanent damage to a lite.

Sent from my Pixel 4 XL using Tapatalk

Technically you can launch atmosphere on it already if you know what you're doing, but for most people this is out of reach but the official launch shouldn't be too far away

 

[hartleyshc]

Technically you can launch atmosphere on it already if you know what you're doing, but for most people this is out of reach but the official launch shouldn't be too far away

Yeah, it's more than just changing the version string on the build. Have tried that and just get a yellow screen. Haven't looked too much into it, but just building with a new version number to bypass the Hekate block isn't enough. Nor is simply building the current project from source. There's still more to be done and pushed to the git. I mean I've seen people boot it on lites, so it's doable, but there's definitely actual code that needs to be changed for it to work.

Sent from my Pixel 4 XL using Tapatalk

 

[Adran_Marit]

Yeah, it's more than just changing the version string on the build. Have tried that and just get a yellow screen. Haven't looked too much into it, but just building with a new version number to bypass the Hekate block isn't enough. Nor is simply building the current project from source. There's still more to be done and pushed to the git. I mean I've seen people boot it on lites, so it's doable, but there's definitely actual code that needs to be changed for it to work.

Sent from my Pixel 4 XL using Tapatalk

Yeah stuff needs to be commented/uncommented for it to work, again the average user tho

 

[hartleyshc]

Yeah stuff needs to be commented/uncommented for it to work, again the average user tho

Well if just commenting/uncommenting, I'll just look through the commits and see what I find. It doesn't take that long to build. Thanks.

Sent from my Pixel 4 XL using Tapatalk

 

[nero99]

Don't get too excited if you're on Mariko.

It doesn't boot sx, it will boot atmosphere/Hekate only on Erista.

As of right now, if you have a Mariko device you're not going to be able to boot anything besides Hekate and just look and use the menu. It will not load atmosphere and you still cannot load fusee-primary on Mariko.

Sent from my Pixel 4 XL using Tapatalk

taken directly from atmosphere "
Support was added to a number of components for running on Mariko hardware.

• The boot system module can now safely be run on MARIKO hardware, performing correct hardware initialization.
• Daybreak (and generally, system update logic) were updated to be usable on Mariko.
• Boot0 protection/management logic was updated to perform correct actions on Mariko.
• Reboot to payload does not and cannot work on Mariko. Correspondingly, A "fatal error" handler was written, to display and save fatal errors from within TrustZone.
• 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."

sure there's a few issues, but nothing is going to break if you don't do stuff you're not supposed to do. You don't need to load fusee_primary if you want or already use hekate.

 

[hartleyshc]

taken directly from atmosphere "
Support was added to a number of components for running on Mariko hardware.

• The boot system module can now safely be run on MARIKO hardware, performing correct hardware initialization.
• Daybreak (and generally, system update logic) were updated to be usable on Mariko.
• Boot0 protection/management logic was updated to perform correct actions on Mariko.
• Reboot to payload does not and cannot work on Mariko. Correspondingly, A "fatal error" handler was written, to display and save fatal errors from within TrustZone.
• 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."

sure there's a few issues, but nothing is going to break if you don't do stuff you're not supposed to do. You don't need to load fusee_primary if you want or already use hekate.

It doesn't work out of the box.

You have to make changes and compile it yourself for it to boot. Hekate will block all versions under v17 from booting on Mariko, and if you load fusee-primary directly with spacecraft-nx, it will just boot to a black screen.

And if you look at SciresM's twitter, there's a post where he told a lite user they shouldn't be booting AMS on a lite, because there's still a power bug that can cause permanent damage to a lite unit. I have not seen any commits that seem to fix that yet, so I definitely wouldn't try on a Lite.

Sent from my Pixel 4 XL using Tapatalk

 

[fst312]

I’m just curious a bit if the mariko system is switch lite you will still need the mod chip but the regular mariko switch shouldn’t need it or is it still going to need the mod chip.

 

[hartleyshc]

I’m just curious a bit if the mariko system is switch lite you will still need the mod chip but the regular mariko switch shouldn’t need it or is it still going to need the mod chip.

They both will need a modchip.

Sent from my Pixel 4 XL using Tapatalk

 

[HollowGrams]

They both will need a modchip.

Sent from my Pixel 4 XL using Tapatalk

8.1.0 Lites has private CFW no chip needed, maybe similar to pegasys. Lets hop he releases it.

 

[britain4]

Yes. Which is the main reason it hasn't been posted about yet. It's been out for a bit now, but there's absolutely no reason to install it until a new version of Atmosphere comes out. Erista can already load Hekate/Fusee from the payloads menu. If someone is on Mariko, they're device will pretty much be useless until whenever atmosphere 17 comes out. Next Juneteenth.

And for people who compile their own version of Atmosphere, there's still bugs currently in the power delivery that can cause permanent damage to a lite.

Sent from my Pixel 4 XL using Tapatalk

That’s true, not much use until the new Atmosphere. I’ve been told by SciresM that AMS 16 isn’t fully compatible with a patched V1 with an SX Core either and won’t boot on mine, at least with FW 11.0.

 

[hartleyshc]

8.1.0 Lites has private CFW no chip needed, maybe similar to pegasys. Lets hop he releases it.

He actually talked about that the other day. Pretty much it's not happening.

Trustzone isn't compromised with that exploit, so he said Atmosphere won't boot without an extensive amount of work.

"like, maybe in 5 years my todo list will be cleared enough to do something"

It's better to just stay updated and get a modchip instead of waiting 5+ years on an old firmware for something that might not even happen.

Sent from my Pixel 4 XL using Tapatalk

 

[HollowGrams]

He actually talked about that the other day. Pretty much it's not happening.

Trustzone isn't compromised with that exploit, so he said Atmosphere won't boot without an extensive amount of work.

"like, maybe in 5 years my todo list will be cleared enough to do something"

It's better to just stay updated and get a modchip instead of waiting 5+ years on an old firmware for something that might not even happen.

Sent from my Pixel 4 XL using Tapatalk

Not what he told me. Things do change though. I personally wouldn't wait though. All mine are 11.x.

 

[hartleyshc]

Not what he told me.

Ok. I'm just quoting what he said about it when someone asked in the discord yesterday. Only SciresM knows for sure I guess.

Sent from my Pixel 4 XL using Tapatalk

 

[HollowGrams]

Ok. I'm just quoting what he said about it when someone asked in the discord yesterday. Only SciresM knows for sure I guess.

Sent from my Pixel 4 XL using Tapatalk

Your info is more recent so prolly what it is now. Also, many or most have updated from 8.x so I see why its not priority.