Hacking SX Modchip firmware has been dumped

[shinwg]

I believe the aim now is to have a payload (ex, atmosphere) “fully” replace sxos on sx hardware. Or perhaps, sxos will be “maintained” by another group. I don’t think sxos is dead yet. Sure the team is being dismantled, but I think there will be “unofficial” updates in the near future. I’m staying on sxos now, but playing with atmosphere.

Can I boot atmosphere or that’s only for unpatch switch?

 

[slaphappygamer]

Can I boot atmosphere or that’s only for unpatch switch?

That’s only on an unpatched switch, for now. The next few months should be interesting.

 

[shinwg]

That’s only on an unpatched switch, for now. The next few months should be interesting.

I hope so

 

[DragarX]

That’s only on an unpatched switch, for now. The next few months should be interesting.

You are wrong sir, I'm running a patched switch right now with atmosphere. It's mariko based switches (v2 and lite) that cannot run other payloads.

 

[JaRocker]

You are wrong sir, I'm running a patched switch right now with atmosphere. It's mariko based switches (v2 and lite) that cannot run other payloads.

Do you plan on posting pics with your flying pigs also

 

[ChronoTrig]

Do you plan on posting pics with your flying pigs also

You realize they're talking about running Atmosphere on V1 patched with the modchip (which is doable), right?

 

[DragarX]

You realize they're talking about running Atmosphere on V1 patched with the modchip (which is doable), right?

I swear there needs to be a stickied thread somewhere. "patched v1 (only) switches are compatible with all unpatched software when using sx core"

 

[JaRocker]

You realize they're talking about running Atmosphere on V1 patched with the modchip (which is doable), right?

no, I didn't why would anyone be talking about the v1 switch here, what's the benefit its runs everything already kinda redundant

 

[Worldblender]

no, I didn't why would anyone be talking about the v1 switch here, what's the benefit its runs everything already kinda redundant

Being able to use alternative firmwares even on patched V1 units opens up more options, instead of being locked to only SXOS. The Mariko and Lite units will likely come later, but when that will happen, I don't know.

 

[pcwizard7]

no, I didn't why would anyone be talking about the v1 switch here, what's the benefit its runs everything already kinda redundant

you do realize there is v1 switch with the bootrom exploit patched and which you need a new exploit which this chip provides. but all v1 homebrew still works on these switches

 

[JaRocker]

Are you not already able to boot other cfw on the patches v1 switch using the modchip via the bootloader or rebooting to a payload ?
I saw Retro reloaded install one in his system when the chips just came out and he used other he was able to use other payload on the switch as will, but then again it could have been an unpatched system

 

[Kioku]

Are you not already able to boot other cfw on the patches v1 switch using the modchip via the bootloader or rebooting to a payload ?
I saw Retro reloaded install one in his system when the chips just came out and he used other he was able to use other payload on the switch as will, but then again it could have been an unpatched system

It's a mess compared to just being able to load up the payload on boot.

 

[JaRocker]

It's a mess compared to just being able to load up the payload on boot.

OK I get that it’s a mess But it’s way better than not being able to do it at all like the v2 system that’s the issue about convenience not Usability So I wouldn’t consider that a priority, Mariko systems should be the priority in my opinion, and also wouldn’t a modified Firmware for the Modchip solve the problem for all the systems

 

[hartleyshc]

a modified Firmware for the Modchip solve the problem for all the systems

That's actually the issue. The current firmware blocks out certain keys making it to where you can't load other cfw through the payloads button on mariko. It's the whole reason we didn't see mariko support in Hekate and Atmosphere like a week after people got their chips.

It's not like mariko is such a different system that they need entire rewrites. Or that it's such a difficult task for these devs to take months to write the updates, or even that there's not enough chipped devices out there to warrant doing the work.

From my understanding from what SciresM has posted in the past it's all from the wiping of these certain keys is the reason why we don't have any mariko payloads yet.

But now both the firmware has been dumped (at least the glitching part) and the windows fw flasher for sx core has been cracked, it's only a matter of time before someone makes a tool for us to convert our own payloads to boot.dat files, or someone makes their own firmware for the core/lites.


Sent from my KFONWI using Tapatalk

 

[JaRocker]

That's actually the issue. The current firmware blocks out certain keys making it to where you can't load other cfw through the payloads button on mariko. It's the whole reason we didn't see mariko support in Hekate and Atmosphere like a week after people got their chips.

It's not like mariko is such a different system that they need entire rewrites. Or that it's such a difficult task for these devs to take months to write the updates, or even that there's not enough chipped devices out there to warrant doing the work.

From my understanding from what SciresM has posted in the past it's all from the wiping of these certain keys is the reason why we don't have any mariko payloads yet.

But now both the firmware has been dumped (at least the glitching part) and the windows fw flasher for sx core has been cracked, it's only a matter of time before someone makes a tool for us to convert our own payloads to boot.dat files, or someone makes their own firmware for the core/lites.


Sent from my KFONWI using Tapatalk

OK I’m not sure if you understood what I was trying to say before if the modchip gets re-flashed by a modified from where it would enable users to put any custom from where they like that’s what I’m talking about, and from what I heard they are missing the FPGA thats what’s really holding up the Progress Correct me if I’m missing something

 

[hartleyshc]

OK I’m not sure if you understood what I was trying to say before if the modchip gets re-flashed by a modified from where it would enable users to put any custom from where they like that’s what I’m talking about, and from what I heard they are missing the FPGA thats what’s really holding up the Progress Correct me if I’m missing something

I understood and that's what I mention in my last paragraph. What my post was mostly about was those (not you) that say that stuff just needs to be updated for Mariko. If that was the case we would have had updated firmware/payloads back in June. TX made it much more difficult to load custom fw from others on Mariko.

But on to your point, I also heard that only the part of the current firmware was dumped. But I also read more recently that it's now possible to load your own code on to the chip (inferring that the roadblock was bypassed with getting a full fw dump). But all of my info is just what's public out on Twitter. I am not a member of any dev groups or discussion groups so I have no further details than what anyone can read.


Sent from my ONEPLUS A6013 using Tapatalk

 

[rody2k6]

I understood and that's what I mention in my last paragraph. What my post was mostly about was those (not you) that say that stuff just needs to be updated for Mariko. If that was the case we would have had updated firmware/payloads back in June. TX made it much more difficult to load custom fw from others on Mariko.

But on to your point, I also heard that only the part of the current firmware was dumped. But I also read more recently that it's now possible to load your own code on to the chip (inferring that the roadblock was bypassed with getting a full fw dump). But all of my info is just what's public out on Twitter. I am not a member of any dev groups or discussion groups so I have no further details than what anyone can read.


Sent from my ONEPLUS A6013 using Tapatalk

Which Twitter users do you follow that talk about this stuff? I'm interested

 

[hartleyshc]

Which Twitter users do you follow that talk about this stuff? I'm interested

I mostly just follow SciresM, and then just read the threads of stuff that he posts and retweets. If he retweets someone, I'll go through their stuff and read that. Read all of the comments on posts, the responses, etc.

I'm not active enough on Twitter to use it with any sort of regularity.

Sent from my ONEPLUS A6013 using Tapatalk

 

[JaRocker]

I understood and that's what I mention in my last paragraph. What my post was mostly about was those (not you) that say that stuff just needs to be updated for Mariko. If that was the case we would have had updated firmware/payloads back in June. TX made it much more difficult to load custom fw from others on Mariko.

But on to your point, I also heard that only the part of the current firmware was dumped. But I also read more recently that it's now possible to load your own code on to the chip (inferring that the roadblock was bypassed with getting a full fw dump). But all of my info is just what's public out on Twitter. I am not a member of any dev groups or discussion groups so I have no further details than what anyone can read.


Sent from my ONEPLUS A6013 using Tapatalk

Ok that’s the case then that’s good news, I know that most users only use cfw pirate but I just home that the devs know that There are other users that are dying to run home for a while your systems no just apps, a lot of the Mariko uses have been waiting for android and Lakka os, on and I remembered something just now why don’t the v1 switch Owners just Convert There Payload to boot.bat files that why they don’t have to boot sxos all, I have a v1 switch that’s patched so I’m going to install a chip and then test this for my self to see if it works, sorry I know I went off on a tangent
: update I just got done modding my v1 switch with chip and I tested the converted payload to boot.bat and yeah it didn’t work, payloads only works if booted from the sx bootloader

 

[AngryCinnabon]

with this firmware dump honestly i expect hekate and atmosphere in a few months at best, possibly a year at worst. it will happen eventually though and i'm quite eager for that.