Hacking [RCM Payload] Hekate - CTCaer mod

[Krude]

I hope it's something like that. It's strange because the first two times i tried, the same files failed verification in the same way (like, PRODINFO always verified okay), and i deleted the files in-between those first two attemps via PC, too.

I'm 50% through the raw dump, i'll let you know if that throws up errors again.

 

[CTCaer]

I hope it's something like that. It's strange because the first two times i tried, the same files failed verification in the same way (like, PRODINFO always verified okay), and i deleted the files in-between those first two attemps via PC, too.

I'm 50% through the raw dump, i'll let you know if that throws up errors again.

If they failed on the exact same part, that means the same sectors. But you never know. That's why the error messages are important.

 

[mariogamer]

I don't know if it is out of the scope of hekate, but is it possible to add a payload chainloader?

 

[CTCaer]

I don't know if it is out of the scope of hekate, but is it possible to add a payload chainloader?

Yeah but why?

 

[Krude]

00: rawnand.bin (0000000-3A3DFFF)
SD card free space:119199 MiB, Total dump size 29820 MiB
[ 96%]
Verification failed.
Verification failed..

Press any key and try again.

Time taken: 3648 seconds.



NOOOOOOOOOOOOO

 

[eldgrim001]

Thanks for making this, very useful.

 

[mariogamer]

Yeah but why?

I guess it would be better to have one payload for everything. (Also this is better for people who need to flash a payload in a custom dongle)

 

[CTCaer]

00: rawnand.bin (0000000-3A3DFFF)
SD card free space:119199 MiB, Total dump size 29820 MiB
[ 96%]
Verification failed.
Verification failed..

Press any key and try again.

Time taken: 3648 seconds.



NOOOOOOOOOOOOO

I need to fix that message. It means that the data from eMMC in 96% did not match the data written to sd card.
I hope you kept the succeeded backups.

I guess it would be better to have one payload for everything. (Also this is better for people who need to flash a payload in a custom dongle)

I don't know any other payloads that you can use many times other than memloader. Can you point me to something?

 

[Krude]

I need to fix that message. It means that the data from eMMC in 96% did not match the data written to sd card.
I hope you kept the succeeded backups.

If i kept backup parts 0-13 or whatever, would there be a way to just dump part 14 again? As far as i can tell, it will start over from the beginning and just overwrite the parts i have already dumped correctly.

 

[mariogamer]

I need to fix that message. It means that the data from eMMC in 96% did not match the data written to sd card.
I hope you kept the succeeded backups.


I don't know any other payloads that you can use many times other than memloader. Can you point me to something?

I forgot that memloader support elf files. But still, might be better than having an ini for each one. Anyways, I'd understand why this would not be necessary.

 

[CTCaer]

If i kept backup parts 0-13 or whatever, would there be a way to just dump part 14 again? As far as i can tell, it will start over from the beginning and just overwrite the parts i have already dumped correctly.

There is a way of doing that. Only if you didn't booted in Horizon OS at all after these 13 parts.

You'll need to create a file named partial.idx and with a hey editor write the number of the part in hex. The value should be 4 bytes.

14 is 0E in hex. So it should be like this: 00 00 00 0E

 

[mariogamer]

Actually my point still stand. You need to generate an elf file which aren't necessarily provided (annd because of toolchain error/32bit not being supported, multiple people can't) and then generate an INI (I know it is fairly simple to do it manually, but see the compile thing...).

 

[iZenCoderJ9]

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).

I really need this,5.1.0 and shuts down at 60-40%,please add me to the group.

 

[mickeeee35]

add me to the group please 15-40 shuts down switch

 

[eldgrim001]

Got a fatal error when backing up eMMc. Cant format card in windows or delete files. Is my sd card done for?

 

[M7L7NK7]

Just tried dumping my nand and got the verification error too. Really dpon't want to wait another hour and it hapens again

 

[CTCaer]

I forgot that memloader support elf files. But still, might be better than having an ini for each one. Anyways, I'd understand why this would not be necessary.

I was talking about memloader from a payload PoV. I meant that this payload, currently it's the only one that could be used multiple times along side hekate and can make you change the payload all the time, if you have a dongle.
I'll add it to a wishlist though. I'll try porting memloader functions to hekate at some point, if the available space allows that.
(Because the next step is to support officially exosphere and this will cut 16KB from the max 160KB.)

Actually my point still stand. You need to generate an elf file which aren't necessarily provided (annd because of toolchain error/32bit not being supported, multiple people can't) and then generate an INI (I know it is fairly simple to do it manually, but see the compile thing...).

That's because you also need devkitPRO which is the aarch64 version of it. And that's memloader launches the extra payload with the normal cores, instead of the BPMP co-processor.
But you can still use devkitARM and compile the payload in armv7 arch, if you make the necessary changes.

Got a fatal error when backing up eMMc. Cant format card in windows or delete files. Is my sd card done for?

Try to format it through a smartphone.

Just tried dumping my nand and got the verification error too. Really dpon't want to wait another hour and it hapens again

Which error you got? eMMC, sd card or the double verification failed?



EDIT:
Thank you all that wanted to test possible fixes to battery desync. My list of testers is pretty full now. You'll learn along the way if a specific fix works.

 

[M7L7NK7]

Yep the same error as Krude
Just saw you can restart it from a certain part (thought it would've dumped it in one file) so I just need to start from part 14 as well.

 

[CTCaer]

Yep the same error as Krude
Just saw you can restart it from a certain part (thought it would've dumped it in one file) so I just need to start from part 14 as well.

How the partial dumping was triggered? Low space or FAT32?

 

[M7L7NK7]

Still have 17GB free and it's FAT 32