Hacking [RCM Payload] Hekate - CTCaer mod

[mariogamer]

Does this also dump the boot partitions in the dump?

 

[CTCaer]

Does this also dump the boot partitions in the dump?

Yes it can dump everything.

 

[mariogamer]

Yes it can dump everything.

Thank .

Btw, what would be the exact size of a valid nand backup? (for reference)

 

[CTCaer]

Thank .

Btw, what would be the exact size of a valid nand backup? (for reference)

31,268,536,320 bytes

 

[mariogamer]

While dumping, hekate report a total dump size of 29820MB, is it normal?

Nvm, the actual size of the file is ok.)

 

[Lacius]

Is your card a U3 sd card?
If yes, this is a known issue. I have working code, but it needs testing.


I checked the write filestystem code and it seems that in some cases, the cursor position moves, even when it fails to write. That's why your file size is correct.

Researching a bit for FatFS writing errors, all sources said that the error is actually fatal and you must try to write the file again and not retry (which seems normal, because it will make a bigger file than it should.).
So what is happening with rajkosto's version, is that it can't write to those sectors and they are left as they are. For example, if you have a file at the position where the error happened, it will be corrupt. Even though the image mounts correctly.

Because this is an important issue, we need to add mechanisms to overcome this (imagine this error happening in the MFT area, your whole partition will show up as corrupt).

Please, when you have time, test the attached version.
Like rajkosto's, it continues with the operation, but shows you the error code and a total of unwritten bytes.
So mark down the error code (if there are different ones, mark them all) and also how many bytes missed.

EDIT:
Use the v2 from below.
(V1 was the wrong payload...)

EDIT2:
Payload removed to not confuse users
Latest version adds the option to choose and continue (and potentially have a corrupt backup even if it mounts) or abort and try again from the last part right away

Like with rajkosto's, the dump succeeded with no errors using 1.2.

 

[Stoned]

What is wrong? I Use the Rawnand Dump Function but Hacdiskmount give the follow Error

Hacdiskmount Error.

[00:19:16:532970] [info] Trying to read partition table from \\?\PhysicalDrive1

[00:19:20:155751]

Primary GPT has invalid constants, trying secondary from default location

[00:19:20:156809]

Primary GPT current LBA mismatch, trying secondary from default location (63864569344 bytes in)

 

[Deleted User]

Posibble restore in the future?

 

[CTCaer]

While dumping, hekate report a total dump size of 29820MB, is it normal?

Nvm, the actual size of the file is ok.)

Yeah that number is in binary megabytes (mebibytes - MiB) and the conversion is division by 1024 and not 1000.

Like with rajkosto's, the dump succeeded with no errors using 1.2.

Maybe the new stabilization changes for the low voltage support gave your sd card more juice and this corrected the problem.
Or for some reason this area was occupied (by a file or with filesystem data).
But we will never know (because rajkosto's version does not check at all for write errors).

What is wrong? I Use the Rawnand Dump Function but Hacdiskmount give the follow Error

Hacdiskmount Error.

[00:19:16:532970] [info] Trying to read partition table from \\?\PhysicalDrive1

[00:19:20:155751]

Primary GPT has invalid constants, trying secondary from default location

[00:19:20:156809]

Primary GPT current LBA mismatch, trying secondary from default location (63864569344 bytes in)

Obviously your dump is corrupt for some reason.
63864569344 bytes?
What's your dump file size?
Was it a one big file dump or multiple parts?
If multiple parts, what command did you use to join the files into one big one?

Also, is it possible to open the file with a HEX editor and send me a screenshot of the first 2KB? (by personal message).

 

[Stoned]

bviously your dump is corrupt for some reason.
63864569344 bytes?
What's your dump file size?
Was it a one big file dump or multiple parts?
If multiple parts, what command did you use to join the files into one big one?

Also, is it possible to open the file with a HEX editor and send me a screenshot of the first 2KB? (by personal message).

Okay Nand Dump Was Corrupted i have redumped and its work.

 

[Lacius]

Maybe the new stabilization changes for the low voltage support gave your sd card more juice and this corrected the problem.
Or for some reason this area was occupied (by a file or with filesystem data).
But we will never know (because rajkosto's version does not check at all for write errors).

You're probably right. The raw dump from rajkosto's version and the raw dump from your 1.2 version don't match, despite being the same size and having no errors during the dumps.

 

[Naked_Snake]

any chance of updating this to dump saves into folders instead of single files, so we can see all the files of our saves?

 

[soaresden]

31,268,536,320 bytes

Mine is 30,535,680 ko , using the 1.1

EDIT : wait ... it appears 30,535,680 ko but it's OK if I right click properties
See

Edit 2 : Remind that kb different from ko, I read too fast ... my fault

WATCH OUT then !

My sd card : Mixza 64Go 26.68$ if anyone is interested...

 

[atkfromabove]

If writing to the eMMC becomes possible in the future could I downgrade back to my 4.0.1 backup? I am wanting to update to 5.x for some games/DLC.

 

[digipimp75]

What program do you use to join the split files together? I can't seem to find one that works properly.

 

[CTCaer]

any chance of updating this to dump saves into folders instead of single files, so we can see all the files of our saves?

Nope, it's out of the scope of this. hekate - ipl is intended as a bootloader.
Sth like pressing power + vol down on a nexus phone but with recovery tools. Imagine bootloader + twrp.

Mine is 30,535,680 ko , using the 1.1

EDIT : wait ... it appears 30,535,680 ko but it's OK if I right click properties
See

Edit 2 : Remind that kb different from ko, I read too fast ... my fault

WATCH OUT then !

My sd card : Mixza 64Go 26.68$ if anyone is interested...

ko is kb in your language actually.
What you misunderstood the first time was KiB vs Bytes.
If you multiply 30,535,680 with 1024 you will get the one in details. That's the reason you have 29.1 Go (GB). bytes /1024/1024/1024

If writing to the eMMC becomes possible in the future could I downgrade back to my 4.0.1 backup? I am wanting to update to 5.x for some games/DLC.

It is possible, but no one touches it for now, to not cause bricks.
The problem with your scenario is actually the fuses. The v4.0.1 backup will not boot after restoring it back from a v5.x.
And there comes Atmosphere.

What program do you use to join the split files together? I can't seem to find one that works properly.

Just use the script provided.

 

[Naked_Snake]

Nope, it's out of the scope of this. hekate - ipl is intended as a bootloader.
Sth like pressing power + vol down on a nexus phone but with recovery tools. Imagine bootloader + twrp.


ko is kb in your language actually.
What you misunderstood the first time was KiB vs Bytes.
If you multiply 30,535,680 with 1024 you will get the one in details. That's the reason you have 29.1 Go (GB). bytes /1024/1024/1024


It is possible, but no one touches it for now, to not cause bricks.
The problem with your scenario is actually the fuses. The v4.0.1 backup will not boot after restoring it back from a v5.x.
And there comes Atmosphere.


Just use the script provided.

No worries pal

 

[Scoreless Pine]

If writing to the eMMC becomes possible in the future could I downgrade back to my 4.0.1 backup? I am wanting to update to 5.x for some games/DLC.

I don't think that's likely, the Switch has digital fuses that detect if you're on a firmware lower than you were in the past and blow if you downgrade, so unless someone finds how to access and disable that safely, downgrading is probably not gonna happen.

 

[Lacius]

If writing to the eMMC becomes possible in the future could I downgrade back to my 4.0.1 backup? I am wanting to update to 5.x for some games/DLC.

As people already mentioned before me, downgrading by restoring an old NAND backup is problematic because the system version won't match the number of expended efuses.

If you can wait a little bit longer without updating, Atmosphere will be released with an emuNAND option that can be upgraded to the latest version so you don't have to actually update your sysNAND. In other words, you'll be able to play the latest games and use the eShop without expending efuses.

If you plan on using something like a bent paperclip or 3D-printed jig to launch Fusée Gelée and Atmosphere CFW, then it really doesn't matter if you update to the latest version, if you just can't help but update soon. This method of launching Fusée Gelée works on all system versions. A software method of launching Atmosphere on 4.0.1 is unlikely to be released anytime soon anyway.

 

[link42586]

Now if I have the Raw NAND dump..Do I absolutely need the USER and other ones or should I basically get all of them? And does the USER dump get the NAND & USER dump or just USER. Dumb questions maybe but I didn't see them in this thread.