Hacking Discussion SX Core Mariko list of non-compatible tools

[Thejigmaster]

That just sounds dangerous. Isn't it better if Tinfoil got updated instead?

to quote TX verbatim

“you can use choijournx if you wish now, it will still brick, but you will not notice it. it corrects the error, the only issue choidijournx had is it wrote some info that only compatible with erista switches, we remove that info and replace it with the mariko info, so your system can bootup normally.”

He was asked well what if it were to brick brick?

“yeah worse case, but once you run v3.0.3 on your switch you have the update added, no need for ext. tools”

 

[linuxares]

Sounds very fishy but sure.

 

[Thejigmaster]

Sounds very fishy but sure.

I agree why not just re-build something like Choi with compatibility for Mariko it seems like they understand how it flashes/upgrades the firmware. Instead they use the glitch chip to rewrite something in the nand during boot so it will boot normally but I wonder if it does it one time or every time.. The announcement was from the official Rocket.Chat. In any case people will be happy that they are not stuck with bricks.

 

[linuxares]

I agree why not just re-build something like Choi with compatibility for Mariko it seems like they understand how it flashes/upgrades the firmware. Instead they use the glitch chip to rewrite something in the nand during boot so it will boot normally but I wonder if it does it one time or every time.. The announcement was from the official Rocket.Chat. In any case people will be happy that they are not stuck with bricks.

Yeah! Or even build their own tool(s) and just release it.

 

[froid_san]

Supposedly you can use choidujournx now if you have v3.03 with their firmware update. What TX said is it’ll still brick but SXOS will fix it so you can still boot emunand etc normally basically you won’t notice it’s bricked(?) also if you bricked it before v3.03 run sxupdater with your switch connected to computer via usb debug port and flash firmware v1.3 it unbricks it.

I think that is my scenario right now.

I'm on 3.0.2 used ChoidujourNX on my emunand.

10.0.4 Emunand works
5.0.10 SysNAND is Dead (error on both CFW and OFW)

So if I did what you've mention and updated to 3.0.3 OS and 1.3 firmware it should fix my dead sysnand?

BTW any link of that TX statement?

 

[Thejigmaster]

I think that is my scenario right now.

I'm on 3.0.2 used ChoidujourNX on my emunand.

10.0.4 Emunand works
5.0.10 SysNAND is Dead (error on both CFW and OFW)

So if I did what you've mention and updated to 3.0.3 OS and 1.3 firmware it should fix my dead sysnand?

BTW any link of that TX statement?

to fix the brick you have to turn off switch, plug usb into the debug port from sxcore into your computer, your computer will recognize switch as a COM device and the SX core will turn green, you then use sx installer to flash firmware v1.3 to the sx core and put 3.03 boot.dat on sd card it’ll boot now again as normal.

xecuter.rocks is the rocket chat website.

 

[froid_san]

I'm blind just found it in the main tx page.

I'm not really bricked, its kinda Semi.

my EMUNAND works fine, my SYSNAND is the one I can't boot to.

its similar in your quote

you can still boot emunand etc normally basically you won’t notice it’s bricked

so this is normal that EMUNAND Works and SYSnand is bricked?

Does anyone know If lockpick compatible with sx core for v1 patched switch?

I don't think so. I was also dumping my prod.keys and get a few errors on lockpick RCM, it can't even detect the 10.0.0 emunand

also on sx core firmware 1.2 my secure_boot_key is bunch of 'f' and when updated to 1.3 sx core firmware it shows some keys but get bunch of corrupted key blob error.

the nor version dumps some keys dunno if they are valid as they are only 41 keys compared to the prod.keys I dump on my brothers switch which was unpatched

 

[NazD]

Does anyone know if I can dump my games with the SX Core?

 

[SrsRobert]

I tried sys-con and it works on V2 (sx core).

 

[Deleted member 510354]

I know this is a Mariko related thread, but did somebody test biskeydump with a patched V1 and SX Core?

 

[Redasx]

I tried sys-con and it works on V2 (sx core).

Please what is the use of sys-con please

 

[froid_san]

I know this is a Mariko related thread, but did somebody test biskeydump with a patched V1 and SX Core?

haven't tried biskeydump yet, does it even support FW 9.0 and above? But I have tried Hekate to dump some kfuses and tsec_keys and other stuffs on a V1 switch using Sx core. Dunno if the keys I've dump are correct or valid

Please what is the use of sys-con please

It lets use user 3rd parties controller on your switch, I've used it so I could use my PS4 controller on it.

 

[Deleted member 510354]

haven't tried biskeydump yet, does it even support FW 9.0 and above? But I have tried Hekate to dump some kfuses and tsec_keys and other stuffs on a V1 switch using Sx core. Dunno if the keys I've dump are correct or valid

So does that mean, that besides the things you can dump with hekate there is no other way to dump keys?
As I understood Lockpick RCM mustn't be used with SX Core and the nro version is not compatible with 10.0.4. I'm a bit confused or worried about having the keys not backed up.

 

[HenryMin]

So does that mean, that besides the things you can dump with hekate there is no other way to dump keys?
As I understood Lockpick RCM mustn't be used with SX Core and the nro version is not compatible with 10.0.4. I'm a bit confused or worried about having the keys not backed up.

You can just use Lockpick.nro to dump your biskeys. Lockpick.nro cannot dump all keys in 10.0.4, but probably it can dump biskeys.

 

[froid_san]

problem is the keys dump by lock pick nro is insufficient if I want to do decryption of romfs to do some modding and also create mods which were my original goal for modding my switch

I got some keys using lockpick nro, lockpick_rcm kinda works on mine since my sysnand is still on 5.1.0 but dunno if I can trust the few keys dump by it since a few match with the keys dump using the nro but some keys are different or not found on the nro

 

[berkcan00]

Hi, first of all I am sorry for noob questions I will ask:
So as I understand boot sequence is different on mariko switches so booting hekate or atmosphere is not possible because of that right and can it be possible if their boot sequence is updated by developers?
And other than that is everything same on Nintendo side for OG and mariko switches, why some homebrews doesnt work or why they need updates in code to be able to work?

 

[pixel_mx]

NO EFFECT (No brick, but doesn't work):
1. Hekate

i have a v1 switch and was able to load hekate

 

[izy]

i have a v1 switch and was able to load hekate

yes beecause hekate works with v1 switches
it doesnt with v2

 

[pixel_mx]

yes beecause hekate works with v1 switches
it doesnt with v2

It would be good if you indicated that in the post

edit:

I know the title says "tools that are not compatible on the mariko v2 switch"

but it would be equally good if they specified which tools work with v1 and which with v2

 

[izy]

It would be good if you indicated that in the post

With more and more people receiving the SX Core, I think we need to have a thread to warn SX Core users, especially on patched switches, which are the tools that should be avoided

I mean you would assume everyone using a core for mariko switchs, eristas are a rare case and is mostly compatible