Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,187,981
  • Replies Replies 3,330
  • Likes Likes 128
I checked your BMP. The ARGB order inside is correct (it's BGRA inside btw. Little endian). It does not have the same header like windows paint and photoshop, but the raw data is correct.
I'll check why this is happening. If it is a bug, it will be fixed. GIMP is, imo, the best free image editor and it's important to support it.
For now use the online methods described by other users.


This is viable everywhere. If you really want to make 3 backups, make sure that you don't boot into Horizon between each backup.
Otherwise the 3 backups will be different.

Are you interested for providing daily build ?
Depending on commits
Thanks for your work
 
  • Like
Reactions: tiliarou
Suppose could do that altho wonder if I end up the SX OS triggering and bricking when doing a backup of things saying it's suppose to be sensitive and easy to trigger I could be 100 percent wrong but thanks for the reply

Just boot with the latest CTCaer payload instead of the SX OS one.

Then select tools and use the top two backup options. It's all in the first post.

I've swapped between the two without any problems. Do your backup and then switch back to using the TX payload. You'll be fine =)
 
  • Like
Reactions: KEITH-IRL
@CTCaer I just tried to back up my nand with 3.0 and got the same problem as the others, my SD I used was a 64GB Sandisk ultra exfat default cluster size

At 34% of verification

[FatFS] Error: Read - Low level disk I/O!

Failed to read 8192 blocks <@LBA 01454000>,
from sd card!

It took 70m 6s
 
@CTCaer if you want i can provide daily compiled binary of atmosphere based on last commits.
if you are ok please dm me
thanks for this 3.0
Are you interested for providing daily build ?
Depending on commits
Thanks for your work
Why should I want this? I don't care.
Just open a new thread somewhere and call it "The Daily Mai... ehm Atmosphere". /s
I'll say it again; I don't care what you patch and load and run.
It's not my responsibility.

@CTCaer I just tried to back up my nand with 3.0 and got the same problem as the others, my SD I used was a 64GB Sandisk ultra exfat default cluster size

At 34% of verification

[FatFS] Error: Read - Low level disk I/O!

Failed to read 8192 blocks <@LBA 01454000>,
from sd card!

It took 70m 6s
This is probably a sd card busy error.
Hmm... Maybe I should lower the buffer size from 4MB (8192 blocks) to sth lower.
Without doing anything at all at your sd card, wait to give you a test payload.

(I think that I should provide a "verify only" option.. but I want to avoid comments like "I booted in HOS, I then verified and failed".)
 
Last edited by CTCaer,
  • Like
Reactions: Azel and tiliarou
This is probably a sd card busy error.
Hmm... Maybe I should lower the buffer size from 4MB (8192 blocks) to sth lower.
Without doing anything at all at your sd card, wait to give you a test payload.

(I think that I should provide a "verify only" option.. but I want to avoid comments like "I booted in HOS, I then verified and failed".)
No problem man, just let me know when you are ready.
 
Last edited by wicksand420,
GjrbREv.png

I need some further detailed explanation on these options :rofl2:
 
Just checked version 3 and loving the battery info!
Also thanks for integrating the battery fix (will come in handy for sure)
This is the ultimate payload to have (deleting the other version).
 
  • Like
Reactions: Deleted User
So seem to be running into an issue. Using an SD ultra card, tired formatted to exFAT and FAT32. Only 16 gb.

I am trying to run a RAW NAND backup. The first 15 or so GB runs fine. I follow the instructions & power off my switch, move the .00, .01 etc files to my mac leaving all others there and intact. Re run the payload and RAW backup. It resumes from where it left off, but keeps failing after about 4 mins saying "SD Card and eMMC data (@LBA 00002000) do not match" "Verification Failed" "press any key and try again"

any ideas as to the issue/problem?
 
I'm having issues creating a color correct bootlogo.bmp. I'm using GIMP -> export as bootlogo.BMP -> Advanced options 32 bit A8 R8 G8 B8. On booting hekate the screen has a terrible blue tint to it. I also tried the X8 R8 G8 B8 option which had a orange tint to it. I know the issue is the bmp I'm exporting because the bootlogo.bmp in tumGER's SDFilesSwitch works fine.View attachment 134124
Same here, the color on my custom splash is all messed up, no matter what settings I use in gimp
So I just rechecked the attached bmp.
The format used is RGBA (inside is ABGR) instead of ARGB (BGRA).

If this was produced by GIMP, it's probably a bug.
I just used GIMP 2.10 with X8 R8 G8 B8 and it correctly produces XRGB (BGRX). We don't care if it's a color channel (X) or an alpha channel (A).
So try to update your GIMP installation with the latest.
Btw, the latest update is beautiful. It's starting to get really professional.

So seem to be running into an issue. Using an SD ultra card, tired formatted to exFAT and FAT32. Only 16 gb.

I am trying to run a RAW NAND backup. The first 15 or so GB runs fine. I follow the instructions & power off my switch, move the .00, .01 etc files to my mac leaving all others there and intact. Re run the payload and RAW backup. It resumes from where it left off, but keeps failing after about 4 mins saying "SD Card and eMMC data (@LBA 00002000) do not match" "Verification Failed" "press any key and try again"

any ideas as to the issue/problem?
Because the error is the compare error, try h2testw on your sd card.

Amazing update ! Thanks !

Just, what is SVC perms ?
and "atmosphere=1" ?
SVC perms
gives full service permissions to everything when inside Horizon OS.
This should never be enabled by default. It can eventually crash the system after a while.

atmosphere=1
is when you run atmosphere as a cfw solution. It applies the fusse-secondary patches and enables the configuration of exosphere.

  • Raise sd card power limit for faster transfer speeds
Interesing when im at Xecuter OS can i apply this?
Nope. This is only for hekate. Horizon's drivers have this anyway.
 
So the verification fails when reading from sd card. Try to do a format with windows: exFAT, default cluster size.
tried this, still fails at 52%

it's a Samsung Evo 64 GB UHS-I card

Here's sd card info from hekate if it helps
 

Attachments

  • IMG_20180702_082412.jpg
    IMG_20180702_082412.jpg
    47.6 KB · Views: 257
Same here, the color on my custom splash is all messed up, no matter what settings I use in gimp
I'm having issues creating a color correct bootlogo.bmp. I'm using GIMP -> export as bootlogo.BMP -> Advanced options 32 bit A8 R8 G8 B8. On booting hekate the screen has a terrible blue tint to it. I also tried the X8 R8 G8 B8 option which had a orange tint to it. I know the issue is the bmp I'm exporting because the bootlogo.bmp in tumGER's SDFilesSwitch works fine.View attachment 134124
I had the same issue with Gimp - Export as PNG and use some online converter for it

(That worked for me at least)
 
Currently making a fresh RawaNAND backup on a 32GB Scandisk SD Card. Done a while ago but verification taking some time. And from the looks of it it's 90% okay now.
But I really think you should make the verification optional @CTCaer.
 
Currently making a fresh RawaNAND backup on a 32GB Scandisk SD Card. Done a while ago but verification taking some time. And from the looks of it it's 90% okay now.
But I really think you should make the verification optional @CTCaer.
It's optional, isn't it
 
It's optional, isn't it

Oh really? Maybe it's on by default then. Will check once my backup is done.
I never experienced any failure btw, that's why.

Edit: Time taken for the rawNAND backup + verfication: 94m 36s (I missed my Switch:D). Finished and verified.
 
Last edited by Zumoly,
  • Like
Reactions: Azel and tomGER
So I just rechecked the attached bmp.
The format used is RGBA (inside is ABGR) instead of ARGB (BGRA).

If this was produced by GIMP, it's probably a bug.
I just used GIMP 2.10 with X8 R8 G8 B8 and it correctly produces XRGB (BGRX). We don't care if it's a color channel (X) or an alpha channel (A).
So try to update your GIMP installation with the latest.
Btw, the latest update is beautiful. It's starting to get really professional.
Updated GIMP from 2.8.XX to the latest and it fixed the issue.
Seems GIMP doesn't have an update feature for dumb windows. Where's apt-get update when you need it.
 
tried this, still fails at 52%

it's a Samsung Evo 64 GB UHS-I card

Here's sd card info from hekate if it helps
Your card appears to be legit. But your verification didn't fail at comparing, so that's why I didn't said for h2testw or sd card info.
I think I should change the sdmmc driver, to print the sd card status on a failed read or write.
Try a full (slow) format if you want.

Currently making a fresh RawaNAND backup on a 32GB Scandisk SD Card. Done a while ago but verification taking some time. And from the looks of it it's 90% okay now.
But I really think you should make the verification optional @CTCaer.
It is optional. The default is set to Full.
You can try Sparse instead of disabling it completely, imo.
 
  • Like
Reactions: Zumoly
If I've done Rajkosto's method of going from 1.0.0 to 5.1.0, I can use this to restore my NAND dump yeah? And if I dump my current 5.1.0 one I can use it to go back up? Repeat infinite?
 

Site & Scene News

Popular threads in this forum