Hacking [RCM Payload] Hekate - CTCaer mod

[wicksand420]

no, i only have the 1

Damn, It may be the sd as well, I know PNY doesn't have a good track record when it comes to compatibility.

 

[SexiestManAlive]

Damn, It may be the sd as well, I know PNY doesn't have a good track record when it comes to compatibility.

well i may get a 256 gb sd card soon, but idk, if i do, what kind should i get?

 

[wicksand420]

well i may get a 256 gb sd card soon, but idk, if i do, what kind should i get?

CTCaer said Samsung works best, but I prefer sandisc

 

[veggietales4ever]

awesome updates going on today, thank you.
is clearing the log on hekate 3.0 with the new 5.0 sdfiles any different than how dreport was before? or do people still not know much about it

 

[DocKlokMan]

I made a whole backup of all and if i compare the size after I copied it from the sd card on the hard disk are different sizes.

On the left is the SD and on the right the HDD.

Size looks the same to me. Don't go by size on disk.

 

[grytek]

Does RAW nand dump includes everything like boot partitions too ? How to join the split files into single one ?

Thanks

 

[Leonidas87]

Is there a reason when I boot with Atmosphere the photo album opens but not Homebrew menue?

Am I missing a step?

Got the 5.0 sd files and ctcaer 3.0

Must be missing something.

4.1.0 by the way

 

[wicksand420]

Does RAW nand dump includes everything like boot partitions too ? How to join the split files into single one ?

Thanks

You need to dump the boots also, along with the nand, with the file joining, there is a program on the download page that joins the files for you

 

[tyler004]

just wondering the option to boot atmosphere full its that the option that will run layeredfs?

 

[DollyWhipDoll]

Does RAW nand dump includes everything like boot partitions too ? How to join the split files into single one ?

Thanks

As for 'Raw NAND', unless something changed with this update, you have to dump NAND, Boot 0, and Boot 1 if you want it complete.

I don't know how it goes for those bits and pieces {2gb or whatever} dumps.

All I know is I saw 1 of these devs on here or Twitter mention dumping all 3 of those for a complete dump.

 

[Deleted User]

My dumps worked out fine tonight on a Samsung Evo Plus 64gb exFAT.

But yes @grytek from what I've read you need Boot0 Boot1 and rawnand.bin to consider it as a full dump. My rawnand.bin size is 31,268,536,320 bytes. Boot0/1 are both 4,194,304 bytes.

 

[JJTapia19]

@CTCaer Thanks for the amazing update! Could you share your red atmosphere custom logo? It looks great!

 

[salamandrusker]

@CTCaer with this layerfs still does not work in 3.0.0, any solution? It says that the program could not be played when executing a donor

first of all thank you for your great work and share it

I think the problem is that layerfs is not compatible with fat32 and only works on exfat

 

[dingdongsong]

Is the atlas44 Web Fusee Launcher still compatible with the v3.0 update?

Edit: Runs with no problems

 

[Aldoria]

@CTCaer with this layerfs still does not work in 3.0.0, any solution? It says that the program could not be played when executing a donor

first of all thank you for your great work and share it

I think the problem is that layerfs is not compatible with fat32 and only works on exfat

that is not the problem

 

[CTCaer]

Just took a huge NAND dump.

Still took ~75 minutes (i appreciate that it automatically converts into min+sec now), but it's worth it if that means it's definitely verifying OK. No verification errors this time (i used a different SD card this time).

Nice. That means your sd card is fast. Because 45 minutes are needed only for the verification compare (excluding the emmac/sd re-reads).
So, 75minutes = (read emmc + write sd) + (read emmc + read sd + compare the 2 hashes).

Thanks for the new version, you outdid yourself !

Backup&verification took 89 mins on my samsung 256Gb Evo Plus ! :o

So I want to try a nand restore, as I said earlier in this thread, nx-dreport doesn't work for me on 3.0.1 and do have nand backups from before running homebrew (and encountering an error) and running SXOS with bad certs roms. (my switch never ever went online btw)

What file should I restore to eliminate the error and bad certs roms reports (I don't know where those would be stored on the emmc) ? would "SYSTEM" suffice ? or should I do a rawnand restore ? which option should I choose I the restore menu?

I know those backups are from a version of Hekate that didn't have verification but at least I managed to do the whole EXFat drivers installation with it, nand opened fine in hacdiskmount etc. so if anything goes wrong, I'll still have acess to RCM/Hekate to do the nand restore I just did and verified ok, right ?

thanks for your work and your help

If I remember correctly it's SYSTEM. And you basically only copy the file SYSTEM in /backup/restore/partitions/, to only restore this specific partition.
But I'm 90% sure that this will mess your switch. Because you are going to restore any other change made in system.
It's better to not do a partial restore.

If you want to play with this, do a new backup (boot0/1,rawnand) with v3.0, so if your system is fucked from restoring only SYSTEM, you can make a full restore back to where it was.

i'm getting the same error with rawnand.bin.09, did low level format and that one part doesn't verify

firmware 3.0.0

Just tried again with a brand new Samsung 64 GB card and the full dump finishes but verification fails at 52%

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

Failed to read 8192 blocks (@LBA 01E98000), from sd card!

So the verification fails when reading from sd card. Try to do a format with windows: exFAT, default cluster size.

Forgive my ignorance, but what is "Auto-Boot"?

The realist in me makes me think that it means that when you select "Launch Firmware" from the Hekate menu, it will wait an allotted time (as you can now set) and if nothing happens it will automatically load the default selection.
Optimistically, it makes it sound like it will simply automatically boot the firmware on entering RCM.

I presume the realistic approach is what it actually is. One can dream of the day you dont have to select any options on powering up (so long as autorcm is on). But it never hurts to ask?

Also if we had made a full backup nand with the previous release, does the new release imply that that backup is bad? or just not able to verify? I've gone through the upgrade process from 4.1.0 to 5 and I'd hate to have to downgrade just to pull the nand again (but hey, better safe than sorry).

It does not imply that the backup is bad. It is just not verified that is OK with v2.3 and older.
Yes you can restore it and it will boot. Hekate bypasses the fuses.

Make sure that you do a new full (boot0/1, rawnand) backup on 5.x, so if the 4.1.0 backup has problems, you can restore it back.
But why you want to switch to 4.1?

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

I've only tried bmps created through photoshop. I'll check gimp and reply back.
(Normally it should have the same options with photoshop. I mean always use GIMP for creating raw images, because photshop meshes with the color contrast.)

I can't seem to find the BACKUP files for eMMC boot? I only see rawnand.bin on the sd card.

Anyone know where it backs it up to?

With v3.0, all eMMC backups go to /Backup.

can someone help, im getting this error
it says sd card and eMMC data do not match verification failed

im doing it in parts and it keeps saying sd card and emmc data (@LBA 00002000>, do not match verification failed

yes, and it would give the same error

no, it would check for sd space when it go to nand file 9 then when it goes green, it gives me an error, it does that on version 3.0 but for some reason, it doesnt give me any errors on 2.3, i think theres a glitch with 3.0.

The backup is successful in v2.3, because the verification was not working there. Now it works and throws error because it found differences.

I suggest you run h2testw to test your sd card. Another user had this problem, and his sd card was fake. So better check this first, before losing hours with trying to find what's wrong.


--------------------------------------

So here are 2 cents:

• Full backup is BOOT0, BOOT1 and rawnand.bin.

Why you don't read the captions? Under ----- Full ----- it has 2 options. That implies that when these 2 options are used, then you have a full backup.

• Verification in v2.3 and older was broken!

If your backup fails now, it's good. Because now you know that it's corrupted. If you want a corrupted backup, just go to verification options and disable the verification. Otherwise, it's best to find why it fails.

 

[KEITH-IRL]

I messed up installed SX OS without backing up my Nand first surprised at myself for actually doing that usually wouldn't be that dumb Am I basicly screwed if the SX OS triggers and bricks the device?

Expecting ones who dont have SX OS and hate TX to reply negatively

 

[Odb718]

CTCaer, when I was working with the xbox 360s, I'd always make 3 nand back ups and use UltraEdit to compare them. I was wondering if that would be a viable option here.

 

[Deleted User]

I messed up installed SX OS without backing up my Nand first surprised at myself for actually doing that usually wouldn't be that dumb Am I basicly screwed if the SX OS triggers and bricks the device?

Expecting ones who dont have SX OS and hate TX to reply negatively

I mean at this point do a full backup since its working. Worst case we find out they've done some nasty stuff and at least you have this backup to revert to if you need to fix something. A backup in a working state is better than nothing.

 

[KEITH-IRL]

I mean at this point do a full backup since its working. Worst case we find out they've done some nasty stuff and at least you have this backup to revert to if you need to fix something. A backup in a working state is better than nothing.

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

 

[CTCaer]

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

CTCaer, when I was working with the xbox 360s, I'd always make 3 nand back ups and use UltraEdit to compare them. I was wondering if that would be a viable option here.

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.