Hacking SX Modchip firmware has been dumped

  • Thread starter Thread starter masagrator
  • Start date Start date
  • Views Views 131,465
  • Replies Replies 371
  • Likes Likes 49
I hope that there is way that I can DIY with an Arudino-compatible or like board.
More info about the STM32 chipset (but not GD32): https://en.wikipedia.org/wiki/STM32
Which STM32/GD32 chip is used, specifcally? Where can I find more info about GD32?
GD32F350CBT6

--------------------- MERGED ---------------------------

Datasheet
 

Attachments

This is like when they dumped the PS3 chip, you were then able to use much cheaper drives to load the exploit
? What drives
You could use a USB stick that would send a payload like a jig
After that it was found that the 3.55 / 3.56 firmware had a signing key fail.
After that you could downgrade via a tsop programmer
And were back to software solutions

I dont get the drives bit
 
Last edited by baileyscream,
You don't need rewrite modchip FW to run Atmosphere when it will have full compability with Mariko and Lite. You will be able to run Atmosphere via Hekate that you will be able to load via SX boot menu.

--------------------- MERGED ---------------------------


Sharing blueprints and any documentation explaining modchip execution process will be also illegal?
I think sharing the files to produce the PCB will be illegal but documentation probably isn't? Depends. Just relaying what someone from RS said. StuckPixel I believe but may be wrong on that.
 
  • Like
Reactions: Julie_Pilgrim
You don't need rewrite modchip FW to run Atmosphere when it will have full compability with Mariko and Lite. You will be able to run Atmosphere via Hekate that you will be able to load via SX boot menu.

oooooh even easier !!!! right ? ... so then it would only be needed to update hekate with the "drivers" (saw someone name them like that) for the patched and mariko so it can run ?
 
Last edited by Cachuchin1,
  • Like
Reactions: Julie_Pilgrim
I think sharing the files to produce the PCB will be illegal but documentation probably isn't? Depends. Just relaying what someone from RS said. StuckPixel I believe but may be wrong on that.
Blueprints and documents will be fine as its still a devboard at the end of the day.
It will be sharing any executable code that bypasses copy protection or any proprietary code that you carnt share
Discuss and share printed code yes but nothing compiled ready to run
 
oooooh even easier !!!! right ? ... so then it would only be needed to update hekate with the "drivers" (saw someone name them like that) for the patched and mariko so it can run ?
Yeah. I was updated now that Hekate code is already working on Mariko, but it will not be public until Atmosphere with Mariko support will be released. So drivers for Mariko are there already.
 
Yeah. I was updated now that Hekate code is already working on Mariko, but it will not be public until Atmosphere with Mariko support will be released. So drivers for Mariko are there already.
So this will only be working with the modchip so no way this can be fixed to work with non modchip switchs like I have.
 
Great news. I’m already running Atmosphere on my V1 with SX core but I’ll be happy the day someone releases a way of running Hekate from an SX Core chip without the need to use any of the dead SX software on it at all.
 
  • Like
Reactions: ChronoTrig
Seems as though it was not cracked but rather the info released.
Why was it not cracked prior to all the latest news?
 
So here is a good question lets just say they make a clone chip will it have the same functionality as SXOS and considering that SXOS status is unkown for the near future who is going to be updating the firmware?

I would stay away from a cheap clone and just get original
 

Site & Scene News

Popular threads in this forum