Hacking [RCM Payload] Hekate - CTCaer mod

[Nswitch]

Weird. I could swear I remember it since 2.0.0.
It was added in 4.0.0?

Hmm, anyway, I don't know if 3.0.0 uploads them without asking though.

I can see the errors under the "Support/Health and Safety" tab but I don't know if it is possible to disable it from being reported.

 

[Lacius]

Weird. I could swear I remember it since 2.0.0.
It was added in 4.0.0?

Hmm, anyway, I don't know if 3.0.0 uploads them without asking though.

I can see the errors under the "Support/Health and Safety" tab but I don't know if it is possible to disable it from being reported.

In the error history, hold the joystick in and hold the plus or minus button to display that setting.

 

[Nswitch]

In the error history, hold the joystick in and hold the plus or minus button to display that setting.

I try to hold both plus and minus with no luck. I there specific way to do it?

 

[Lacius]

I try to hold both plus and minus with no luck. I there specific way to do it?

Press in the joystick and hold it. Also, press and hold either the plus or the minus button. You need to be in your error log when you do this.

 

[CTCaer]

In the error history, hold the joystick in and hold the plus or minus button to display that setting.

So that's why I remember disabling it. It also exists in 2.0.0+?

 

[Lacius]

So that's why I remember disabling it. It also exists in 2.0.0+?

This is how you disable it on 3.0.0. I can't say anything for sure about anything above or below 3.0.0.

 

[Nswitch]

Press in the joystick and hold it. Also, press and hold either the plus or the minus button. You need to be in your error log when you do this.

Got it thanks for help guys! @CTCaer @Lacius

 

[CTCaer]

Got it thanks for help guys! @CTCaer @Lacius

That's nice, it's an opt-in option.

 

[Nswitch]

That's nice, it's an opt-in option.

Would never figure it out without you guys help!

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

That's nice, it's an opt-in option.

Just ran the nx-dreport and clean all the errors log.

 

[DiJornios]

Idk wouldn’t more stuff be optimized for lower firmwares first?

 

[CTCaer]

I'll need some users, that run linux and have severe battery desync problem, in the next days.
send a PM and I'll add you to a group PM.

I'm developing the battery gauge driver for hekate now and I think I know why the desync problem exists.
I have a probable simple solution.
And this solution is like removing the battery.
(btw, there's a reason why removing the battery works! And also why normal RCM does not desync the battery).

 

[2Siralv]

Yeah sth like that. But you still don't need to swap the legit fw. We are still going to patch future checks.

Yeah, it's overkill to run it every time. nx-dreport is only if and only if you had a crash from a homebrew and you want to wipe the error reports. But you should have the upload disabled (settings), in the first place.

Im on 5.0.1 or whatever before 5.1.0 how do i clewr my crashes and im getting the white nag

 

[SylasMc]

I'll need some users, that run linux and have severe battery desync problem, in the next days.
send a PM and I'll add you to a group PM.

I'm developing the battery gauge driver for hekate now and I think I know why the desync problem exists.
I have a probable simple solution.
And this solution is like removing the battery.
(btw, there's a reason why removing the battery works! And also why normal RCM does not desync the battery).

Mine dies at 75%. I need this!

 

[Krude]

I dumped my NAND on a FAT32 formatted SD card, and verification failed. This took like an hour or two, so i'm wary of trying to dump again.
I also tried dumping eMMC SYS, where it dumps a whole number of separate packages, and the verification for most of these failed, too, usually at 2%-25%.

This is a new Switch on 3.0.0 and the only thing i've done on it is setting up HB menu with PegaSwitch, nothing else. Should i just shrug and ignore the v erification errors? Any wy i can verify them after the fact?

edit: BOOT0 and 1 dump and verify correctly, and PRODINFO and PRODINFOF do the same on the SYS dump, but all the following (the BCPKG2 things) all fail verification at 25-28%, and SAFE even fails veriffication at 1%.

(also it took me a while to figure out how to navigate the menu, since the joycons didn't work. You should jsut throw a quick note somewhere in the OP to use the VOL and power buttons, for newcomers like me)

 

[CTCaer]

I dumped my NAND on a FAT32 formatted SD card, and verification failed. This took like an hour or two, so i'm wary of trying to dump again.
I also tried dumping eMMC SYS, where it dumps a whole number of separate packages, and the verification for most of these failed, too, usually at 2%-25%.

This is a new Switch on 3.0.0 and the only thing i've done on it is setting up HB menu with PegaSwitch, nothing else. Should i just shrug and ignore the v erification errors? Any wy i can verify them after the fact?

edit: BOOT0 and 1 dump and verify correctly, and PRODINFO and PRODINFOF do the same on the SYS dump, but all the following (the BCPKG2 things) all fail verification at 25-28%, and SAFE even fails veriffication at 1%.

(also it took me a while to figure out how to navigate the menu, since the joycons didn't work. You should jsut throw a quick note somewhere in the OP to use the VOL and power buttons, for newcomers like me)

Any other error message before the verification failed message ?

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

Im on 5.0.1 or whatever before 5.1.0 how do i clewr my crashes and im getting the white nag

nx-dreport and gag-order.

 

[Krude]

No, no error messages as far as i cn see. When dumping eMMC SYS, it dumps and verifies the first 2 files (the PRODINFO things) no problem, then the BCPKG2's all dump and fail at 25-28% pretty quickly.
So, it's kinda hard to tell, because due to the failure messages the screen fills up really quickly, and the last file dump for SYSTEM has it's dumping bar appear at the top of the screen, overwriting previous messages... But i think the SYSTEM file dumps and verifies correctly.

 

[CTCaer]

No, no error messages as far as i cn see. When dumping eMMC SYS, it dumps and verifies the first 2 files (the PRODINFO things) no problem, then the BCPKG2's all dump and fail at 25-28% pretty quickly.
So, it's kinda hard to tell, because due to the failure messages the screen fills up really quickly, and the last file dump for SYSTEM has it's dumping bar appear at the top of the screen, overwriting previous messages... But i think the SYSTEM file dumps and verifies correctly.

Oh I see. I'll need to fix it. The error messages are important to know what happened.

The EPRINTFs below are the possible verification messages:
https://github.com/nwert/hekate/com...c94#diff-799c7cc4c061751437d68637b5d9ae27R684

 

[Krude]

So i just dumped the eMMC SYS for a third time now, thinking that i could maybe make a photo on how the log screen looks, and.... suddenly, they dump and verify OK. The only thing i did differently, is that i put the SD card into the switch AFTER booting into RCM (i deleted the old dumps via PC).

IIRC, the errors were just "Verification failed.." twice in a row and "Press any key and try again." which you obviously can't do on a multi-file dump, but it said it anyway and that took up a lot of space.

 

[Krude]

Okay, i cleaned off all the dumps from my SD card again and re-ran the SYS dump for the 4th time. They all go through verification just fine now. ¯\_(ツ)_/¯

Really weird. I'll take my chances and run a full raw dump again... and hope it doen't fail verification this time.

 

[CTCaer]

Okay, i cleaned off all the dumps from my SD card again and re-ran the SYS dump for the 4th time. They all go through verification just fine now. ¯\_(ツ)_/¯

Really weird. I'll take my chances and run a full raw dump again... and hope it doen't fail verification this time.

Maybe it was a dirty unmount which was fixed subsequently with mounting it to your pc and then proper unmounting.
(The desktop fat32/exfat drivers have more proper sanitization and error checking than the tiny FatFs driver).

Or some bad sectors that fixed themselves though rewriting.