Hacking [RCM Payload] Hekate - CTCaer mod

[wicksand420]

@CTCaer I still get the same error when dumping rawnand.bin

Checking for available free space...
00: rawnand.bin
SD Card free space: 53928 MiB, Total dump size 29828 MiB
[ 83%]
Fatal error 1 when writing to SD Card

 

[CTCaer]

@CTCaer I still get the same error when dumping rawnand.bin

Checking for available free space...
00: rawnand.bin
SD Card free space: 53928 MiB, Total dump size 29828 MiB
[ 83%]
Fatal error 1 when writing to SD Card

Ah, so it's a writing error.

About the error:
Error 1 is /*A hard error occurred in the low level disk I/O layer */
These are fatal and cannot be mitigated/corrected from the current state of the tiny FatFS filesystem code, like what windows do.
Maybe in the future we can make it better.

You can ignore the error but better not do it... (you may end up with a corrupt backup and your first backup should be A+ OK).

So,
First do full error checking from windows:
In cmd enter: chkdsk /f /r /x Z:
where Z: is your sd card drive letter

You can also try a full format before that, with: format Z: /fs:exFAT
This command writes zeroes to all your sd card and makes sure that no bad sectors exist. If they exist they get marked for avoidance.
Both commands show a summary when they are done. You can check if everything is OK.

If these 2 do not work, try to get the dump in parts:
Fill your sd card to have less space than 29,828MB.
(Another way to kickstart the partial dumping when you have enough space, is to create the partial.idx file, and write with a hex editor, 00.)
Now it will try with partial dumping.
When it fails, reboot (into RCM), remove your sd card, move the dumped files that are 2GB, but leave the partial.idx file.
Run the ipl again.
Now it will dump from the last part it was trying to and because you removed the previous files, it will write on an the OK area.

 

[wicksand420]

I'm running chkdsk now, my file system is fat32 and i was dumping it to 2gb parts

chkdsk found nothing wrong with my sd

 

[CTCaer]

I'm running chkdsk now, my file system is fat32 and i was dumping it to 2gb parts

chkdsk found nothing wrong with my sd

If you have fat32 it's easy to do the above operation.
When it fails at 83%, press vol to abort and then try again right away.
If it still fails at 83%, move the files that were dumped correctly to your PC, leave the partial.idx file, delete the incorrect part that is 0 bytes and try again.

 

[wicksand420]

I have to start my dump over though, correct

 

[CTCaer]

I have to start my dump over though, correct

If you kept the correct files to your PC, and you didn't touched the partial.idx file in sd card,
it will continue from the last part it was trying to dump. No need to do it all over again. Just move the already dumped files to your pc first

 

[PatrickStarSb]

Anyone who has successfully created a nand backup have a recommendation for what Micro SD card to use, my switch is on 4.1, I'm guessing a 64gb card is best?

I've tried with my current 32gb card but got an error half way through.

 

[Addconsult]

Anyone who has successfully created a nand backup have a recommendation for what Micro SD card to use, my switch is on 4.1, I'm guessing a 64gb card is best?

I've tried with my current 32gb card but got an error half way through.

I bought Samsung 64gb Sdxc and i have successfully dumped NAND and all the others with this release on a 4.0.1 system

 

[CTCaer]

Anyone who has successfully created a nand backup have a recommendation for what Micro SD card to use, my switch is on 4.1, I'm guessing a 64gb card is best?

If you are going to use it for linux and digital downloaded games also, it should be at least 64GB and up.
Preferably with Class10 / U3 support. If you want to save money, then a U1.
But not a class10 only. It's too slow for games.

My main is a Samsung EVO+ U3 128GB and I'm pretty happy with this one.
Bought it 45euro and blows away my Sandisk Extreme Plus U3 64GB (50euro) on performance level (sequential/random)...

Btw U1/U3 is not to be confused with UHS-I/II. U1/3 is the minimum performance level of the UHS-I/II bus.
U1: 10MB/s and up
U3: 30MB/s and up

Lastly, my release works with every SDHC/SDXC cards on the physical layer (no failed to init/mount sd card messages).
So, buy an SD card based on value (performance per buck).

 

[PatrickStarSb]

If you are going to use it for linux and digital downloaded games also, it should be at least 64GB and up.
Preferably with Class10 / U3 support. If you want to save money, then a U1.
But not a class10 only. It's too slow for games.

My main is a Samsung EVO+ U3 128GB and I'm pretty happy with this one.
Bought it 45euro and blows away my Sandisk Extreme Plus U3 64GB (50euro) on performance level (sequential/random)...

Btw U1/U3 is not to be confused with UHS-I/II. U1/3 is the minimum performance level of the UHS-I/II bus.
U1: 10MB/s and up
U3: 30MB/s and up

Lastly, my release works with every SDHC/SDXC cards on the physical layer (no failed to init/mount sd card messages).
So, buy an SD card based on value (performance per buck).

Do i need an update to use MicroSDXC cards?
I haven't used one in my switch yet...

 

[CTCaer]

Do i need an update to use MicroSDXC cards?
I haven't used one in my switch yet...

No. The update has nothing to do with the sd card type.
It has to do with the exFAT filesystem.

If you don't have the update and you don't want to update your console (you can't choose, the exFAT update comes with any new system update), just format your SDHC or SDXC card with FAT32.

 

[Deleted User]

Deleted

 

[alexj9626]

Just got the rawnand dump. Thanks a lot dude!

Do i need to dump anything else to be safe?

 

[Deleted User]

Deleted

 

[alexj9626]

I think boot1/0

Thanks, i have seen couple messages about that. Do you know how big they are?

Edit: Never mind, i just did. It was like 2 seconds lol so they must be kinda small files.

 

[hudhair]

Hey guys, this is my second time dumping and I'm running into this error. Any ideas?

Sent from my iPhone using Tapatalk

 

[AlphaSapphire]

is there a tutorial for me how to do this

 

[wicksand420]

@CTCaer I went ahead and pushed the vol button when it said fatal error 1 and just let it continue to dump my nand and it worked, is it possible that the error is because of the slow speed of my sd?

@hudhair try to press the vol button when you get your error and just let it run again, worked for me, you probably have a 64GB sandisc sd?

 

[CTCaer]

Hey guys, this is my second time dumping and I'm running into this error. Any ideas?

Sent from my iPhone using Tapatalk

@CTCaer I went ahead and pushed the vol button when it said fatal error 1 and just let it continue to dump my nand and it worked, is it possible that the error is because of the slow speed of my sd?

@hudhair try to press the vol button when you get your error and just let it run again, worked for me, you probably have a 64GB sandisc sd?

No, the problem is low level disk i/o error. This can happen for many reasons. I can not find the reason on my own though. I don't have any problematic sd card..
I can find the reason for you if you want. I can write a special debugging version and we can check the last step it failed.

Anyway, what I really want to say is that, please don't give the "press power btn" to ignore errors as a suggestion..
This function ignores 256KB chunks for every error (you can only see the 1st one, there maybe are countless after that).
If there's data there, it means your end result dump file is actually corrupted.

What someone needs to do, is to force the partial dumping.
This way and by not letting the sd card write to those areas with some clever manipulation, you can get a 100% perfect backup.
I explain some of these ways in previous posts.

 

[wicksand420]

No, the problem is low level disk i/o error. This can happen for many reasons. I can not find the reason on my own though. I don't have any problematic sd card..
I can find the reason for you if you want. I can write a special debugging version and we can check the last step it failed.

Anyway, what I really want to say is that, please don't give the "press power btn" to ignore errors as a suggestion..
This function ignores 256KB chunks for every error (you can only see the 1st one, there maybe are countless after that).
If there's data there, it means your end result dump file is actually corrupted.

What someone needs to do, is to force the partial dumping.
This way and by not letting the sd card write to those areas with some clever manipulation, you can get a 100% perfect backup.
I explain some of these ways in previous posts.

I didn't say to press the power button, I said press the volume button and let it finish, I made my dump and it got to 83% like before, and said it had a fatal error 1, so i pressed volume, then restarted it from where the error was and it completed fine

Also, its dumping 30 1GB files instead of 15 2GB files, whats up with that?