Hacking [RCM Payload] Hekate - CTCaer mod

[Mr. Wizard]

These can happen from unaligned access to mem, or from kips or using an incorrect boot0 (so keygen generates the wrong keys).

It happened to me twice on
fw 3.0.0
tegrarcmgui 2.0
sxos 1.3 payload
pc -> 6' usbA extension -> 3' usbA to C -> switch.
Right after sending payload, had to hard reset.

Has not happened since I upgraded to 5.1.0. (knock on wood).

 

[yacepi15]

Just for curiosity... What does a orange screen at boot mean? It happened me one time on an unmodified Switch, forced power off and everything fine again.

 

[Mr. Wizard]

Just for curiosity... What does a orange screen at boot mean? It happened me one time on an unmodified Switch, forced power off and everything fine again.

Your switch may be low on vitamin C dude! Probably has SCURVY. /s

That's a new one haven't seen that.

 

[CTCaer]

Just for curiosity... What does a orange screen at boot mean? It happened me one time on an unmodified Switch, forced power off and everything fine again.

Secure Monitor (exception vectors)

http://switchbrew.org/index.php?title=Panic_codes

 

[Mr. Wizard]

Secure Monitor (exception vectors)

http://switchbrew.org/index.php?title=Panic_codes

Ooooh sexy link!

Any specific reason colors are used instead of actual codes or message?

 

[CTCaer]

Ooooh sexy link!

Any specific reason colors are used instead of actual codes or message?

The text engine is not yet initialized. And they just paint the framebuffer with one color.
I believe it's to obfuscate mostly. Hide the error meaning.

 

[BaamAlex]

Is it possible that the modifications will corrupt game data? Here an example: I bought fire emblem warriors...download finished, and it doesn't start. Tried an other game like okami... it starts. Or with other words said...can nintendo see that i have my console modded? I re-downloaded fire emblem on the internal storage and on the sd card. I believe i must send the console back to nintendo!!!

 

[CTCaer]

Just disable the version of fs.mitm you are using already.

For some reason it's not known or it's forgotten that games can tap in the system memory and not be limited to 3.5GB...

The version of fs.mitm you are using is hogging the system mem and there's not enough to run the game.

 

[comput3rus3r]

The text engine is not yet initialized. And they just paint the framebuffer with one color.
I believe it's to obfuscate mostly. Hide the error meaning.

hi, i never formally apologized for assuming your mod messed up my switch a while ago. I had an extraordinarily rare micro sd card reader problem on my switch where it would work perfectly except it wouldn't give hekate sd card access. I sent it to Nintendo and they replaced it and now it works perfectly with hekate.

 

[BaamAlex]

Just disable the version of fs.mitm you are using already.

For some reason it's not known or it's forgotten that games can tap in the system memory and not be limited to 3.5GB...

The version of fs.mitm you are using is hogging the system mem and there's not enough to run the game.

i dont use an cfw actually. Legally bought

 

[CTCaer]

hi, i never formally apologized for assuming your mod messed up my switch a while ago. I had an extraordinarily rare micro sd card reader problem on my switch where it would work perfectly except it wouldn't give hekate sd card access. I sent it to Nintendo and they replaced it and now it works perfectly with hekate.

Well, it's OK.
This is a mature gesture.

Hekate is carefully tailored and researched on all versions of nxbootloader, for these specific reasons.

Btw, I found long ago what these "mysterious" sd card readers are.
Basically the connector is not fully seated.
It's common when you change the shell for example. There's a reason the connector has that black padding on top of it.

So, this makes both the controller and the card to fallback to 1bit data bus width. let's call that mode SDSC, aka sd card v1.0.

I never added SDSC support to hekate and that's the reason it does not work.
This will remain like this for 2 reasons.
First, SDSC cards do not exist anymore (or it's quite difficult to find this ancient tech).
Second, it's the only way to identify this problem. And it's important to identify it because the bus speed is 4 times lower in these cases.
Imagine having a UHS-I U3 card and the speed would be like a crappy card.

i dont use an cfw actually. Legally bought

I'm not talking about legality -> Because the proper use case of fs.mitm (aka why it was made for), is mods, not pirating.

So, what modifications then?

Is it possible that the modifications will corrupt game data?

 

[comput3rus3r]

Well, it's OK.
This is a mature gesture.

Hekate is carefully tailored and researched on all versions of nxbootloader, for these specific reasons.

Btw, I found long ago what these "mysterious" sd card readers are.
Basically the connector is not fully seated.
It's common when you change the shell for example. There's a reason the connector has that black padding on top of it.

So, this makes both the controller and the card to fallback to 1bit data bus width. let's call that mode SDSC, aka sd card v1.0.

I never added SDSC support to hekate and that's the reason it does not work.
This will remain like this for 2 reasons.
First, SDSC cards do not exist anymore (or it's quite difficult to find this ancient tech).
Second, it's the only way to identify this problem. And it's important to identify it because the bus speed is 4 times lower in these cases.
Imagine having a UHS-I U3 card and the speed would be like a crappy card.


I'm not talking about legality -> Because the proper use case of fs.mitm (aka why it was made for), is mods, not pirating.

So, what modifications then?

that's awesome. Had i never tried hekate I would have never known there was an issue with my sdcard reader other than it being slow. Thank you.

 

[Krovax]

Hi, sorry if this has been addressed already but I keep getting a verification failed message when dumping my rawnand;

"SD card and emmc data (@LBA 01D9A000) do not match!"

It's happened twice at exactly 50% (during verification), in between the two occasions a bad IO error cropped up so I carried out a full format. Both times that it did occur it created a 29.1GB file.

I'm assuming it's the SD card at fault?

 

[yacepi15]

Hi, sorry if this has been addressed already but I keep getting a verification failed message when dumping my rawnand;

"SD card and emmc data (@LBA 01D9A000) do not match!"

It's happened twice at exactly 50% (during verification), in between the two occasions a bad IO error cropped up so I carried out a full format. Both times that it did occur it created a 29.1GB file.

I'm assuming it's the SD card at fault?

It is the sdcard. Do a low level format or use another one.

 

[CTCaer]

Hi, sorry if this has been addressed already but I keep getting a verification failed message when dumping my rawnand;

"SD card and emmc data (@LBA 01D9A000) do not match!"

It's happened twice at exactly 50% (during verification), in between the two occasions a bad IO error cropped up so I carried out a full format. Both times that it did occur it created a 29.1GB file.

I'm assuming it's the SD card at fault?

Try using h2testw and see if the reported size is the same with what it should be

 

[Krovax]

Try using h2testw and see if the reported size is the same with what it should be

That's a good shout. I've got that running already. Might take a while to finish though ... and for some odd reason it was at 32kb allocation size, thought I'm not sure if that woulda effected much.

What would you suggest if that checks up fine though? Or is that always printed when dumping on fake cards?

Thank you

 

[CTCaer]

That's a good shout. I've got that running already. Might take a while to finish though ... and for some odd reason it was at 32kb allocation size, thought I'm not sure if that woulda effected much.

What would you suggest if that checks up fine though? Or is that always printed when dumping on fake cards?

Thank you

First reason for that error msg is fake card.
Second is corruption.

But in your case, it's strange that happens 2 times at the same place.
So it's probably because of 16GB real size.

 

[RAGER]

@CTCaer , can you please elaborate on reverting the GC firmware more? Or soon(TM)?

 

[Krovax]

First reason for that error msg is fake card.
Second is corruption.

But in your case, it's strange that happens 2 times at the same place.
So it's probably because of 16GB real size.

Oddly enough. It managed to write all of it... The corruptions reached 20gb+ though. But out of fustration I just went out and got another card and it's dumping so much quicker then before.

Thanks for the quick responses. I should of checked that in the first instance. But knowing me I would of just kept messing around with it

 

[Krovax]

Eh. Maybe I'm just a bit dense. But yea. The card is fake >>