Hacking [RCM Payload] Hekate - CTCaer mod

[HaHaYeah]

Excuse me, I am a bit lost. I really appreciate your contribution CTCaer. But I use the NXLoader method in android to launche fusee gelee, and I dont know how can I load your payload because is not a .bin file. How can i load it?. I want to make my nand dump. Thanks again

 

[jakkal]

Just add .bin at the end of the file name

 

[HaHaYeah]

Just add .bin at the end of the file name

So many thanks . I'll try

 

[SwitchGuy]

Just created an account here to thank you for your work. I successfully backed everything up on a 128GB card. Extremely simple to use and didn't take too long to back up either. Thanks, man!

 

[CTCaer]

@whyyes @Justin20020
Please try the attached beta version.

Changes:
Partial dumping:
Makes sure that the partial.idx is created even when a fatal error occurs. (helps to continue from the last part when an error occurred).
Can now force partial dumping by creating "partial.idx" file and writing 0x00 into it, even if the sd card has enough space (and fs is exFAT).
Other:
Optimizations
Fatal errors abort immediately. (They don't ask if you want to ignore errors now. What's the point if you get a corrupt backup.)

 

[Justin20020]

I will response to you when I‘m back from work

 

[kamo]

I'm still having problems. Backup takes about 2 hours to reach 5% on my 64gb class 10 Sandisk card. I made sure to zero the card before using it. Tried FAT32 and exFAT. I could endure the long time but it always ends in an endless stream of errors (read error, if I press volume it just comes up again until the whole screen is full of errors). I have another slower 32gb card but it ends all the same albeit even slower. Any tips?

edit
I managed to get a backup of boot, now I'm trying system. Would that count as the bare minimum if something goes wrong?

 

[CTCaer]

I'm still having problems. Backup takes about 2 hours to reach 5% on my 64gb class 10 Sandisk card. I made sure to zero the card before using it. Tried FAT32 and exFAT. I could endure the long time but it always ends in an endless stream of errors (read error, if I press volume it just comes up again until the whole screen is full of errors). I have another slower 32gb card but it ends all the same albeit even slower. Any tips?

edit
I managed to get a backup of boot, now I'm trying system. Would that count as the bare minimum if something goes wrong?

What error it shows? You say read error, but the VOL/POWER options to ignore are only in write errors..
Also don't ignore the errors. Otherwise your backup will be corrupted.
Lastly, 2 hours for 1.5GB (200KB/s) with a class 10? Are your sd cards worn out (writing overused)?
A class 6 16GB sandisk I have, writes with average 5.6-6.1MB/s, so the 5% takes around 5minutes.
And well my class10 U3 cards take 1-1.2minutes for 5%.

The system is not enough.
You need BOOT and RAW (includes SYS+USER).
Or BOOT, SYS and USER.

 

[kamo]

What error it shows? You say read error, but the VOL/POWER options to ignore are only in write errors..
Also don't ignore the errors. Otherwise your backup will be corrupted.
Lastly, 2 hours for 1.5GB (200KB/s) with a class 10? Are your sd cards worn out (writing overused)?
A class 6 16GB sandisk I have, writes with average 5.6-6.1MB/s, so the 5% takes around 5minutes.
And well my class10 U3 cards take 1-1.2minutes for 5%.

The system is not enough.
You need BOOT and RAW (includes SYS+USER).
Or BOOT, SYS and USER.

It shows error 1. I don't ignore it with power. After hitting volume the error -1 repeats until the whole screen is full of the same error messages.
About my cards. Both are fairly new and chkdsk doesn't report any errors.

Could it be the nand? Maybe it is corrupted?

 

[CTCaer]

It shows error 1. I don't ignore it with power. After hitting volume the error -1 repeats until the whole screen is full of the same error messages.
About my cards. Both are fairly new and chkdsk doesn't report any errors.

Could it be the nand? Maybe it is corrupted?

What payload version you used? 1.3 or the testing 1.5?

 

[kamo]

What payload version you used? 1.3 or the testing 1.5?

Both.

 

[CTCaer]

Both.

Which one filled your screen with write errors 1 and write errors -1?

 

[kamo]

Which one filled your screen with write errors 1 and write errors -1?

The new beta filled the screen after pressing volume once. The older version just showed the error once for every time I pressed volume.

I just started a new try with the 32gb card. I post a pic of the error later if it comes up again.

 

[CTCaer]

The new beta filled the screen after pressing volume once. The older version just showed the error once for every time I pressed volume.

I just started a new try with the 32gb card. I post a pic of the error later if it comes up again.

ipl-ctc1.5fatal_error_test.zip does not let you choose to ignore errors.. If you press a button you go to the menu..

 

[kamo]

ipl-ctc1.5fatal_error_test.zip does not let you choose to ignore errors.. If you press a button you go to the menu..

You're right I didn't press anything in that version. The screen was filled with red error lines after awhile. Anyway the backup on the 32gb card is still running. It's at 8% after about 25 minutes. It's just a class 4 card tho so that might be expected.

 

[CTCaer]

You're right I didn't press anything in that version. The screen was filled with red error lines after awhile. Anyway the backup on the 32gb card is still running. It's at 8% after about 25 minutes. It's just a class 4 card tho so that might be expected.

Look. The error lines are specific.
If you don't tell me exactly what they are saying, I can't help.
(And by the way, you can only see 1 WRITE error, not a screen filled with them)

 

[kamo]

Look. The error lines are specific.
If you don't tell me exactly what they are saying, I can't help.
(And by the way, you can only see 1 WRITE error, not a screen filled with them)

Look m8 I'm sorry to bother you but as I said I will post a pic I take with my cam to show you the exact error message if it comes up again. And I don't know what to tell you about the whole screen that was filled with these error messages. Why would I ask you about that if it didn't happen? Not that it matters anyway.

 

[kamo]

Look. The error lines are specific.
If you don't tell me exactly what they are saying, I can't help.
(And by the way, you can only see 1 WRITE error, not a screen filled with them)

Fatal error (1) while writing to SD card
37% time taken 4223 seconds

Found a rather old 32gb Adata. I'm gonna try that one.

 

[CTCaer]

Fatal error (1) while writing to SD card
37% time taken 4223 seconds

Found a rather old 32gb Adata. I'm gonna try that one.

After that error, you pressed again "Dump RAW eMMC"?
If it was a partial dump, it will continue from the last part it was trying.
When you have write errors, the trick is to finally collect all 15 parts from retries. Not to dump it all in one session.
If you used the 1.5 it will know where it stopped.

 

[kamo]

After that error, you pressed again "Dump RAW eMMC"?
If it was a partial dump, it will continue from the last part it was trying.
When you have write errors, the trick is to finally collect all 15 parts from retries. Not to dump it all in one session.
If you used the 1.5 it will know where it stopped.

I used 1.5. I did not try to "Dump RAW eMMC" again. What I did is trying the new card where the backup still runs as of now. I've checked the other card (the one with 37% Fatal error (1) while writing to SD card) It has rawnand.bin.00 to .05 where .05 is only 0 bytes. The others look good. There is however no partial.idx file on the card. Should I try to do something with these files?