Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter CTCaer
  • Start date
  • Views 1,071,040
  • Replies 3,243
  • Likes 128

ErrADDict

Member
Newcomer
Joined
Oct 19, 2018
Messages
12
Trophies
0
Age
35
XP
126
Country
United States
I'm wondering about the "Restore" options. I noticed that the BOOT0 and BOOT1 are required to be in different locations:
/Backup/Restore/BOOT0
/Backup/<eMMC S/N>/Restore/BOOT1

Is this a typo?

From OP:
Restore eMMC BOOT0/1 (Dangerous!):
Do not use that if you don't know what you are doing! No one is responsible for messing with your device.
You have a 10 second mandatory wait time before letting you start restore by pressing POWER.
This let's you restore your eMMC BOOT0 and BOOT1 partitions.
It will only restore the files at /Backup/Restore/BOOT0 and /Backup/<eMMC S/N>/Restore/BOOT1.
 

whyyes

Well-Known Member
Member
Joined
Sep 20, 2009
Messages
160
Trophies
0
XP
466
Country
United States
I did a full restore earlier tonight and it seems to have worked fine except during the verification of the rawnand I got the old issue mentioned here https://github.com/CTCaer/hekate/issues/30 . It did complete properly, my NAND backup was the correct size and all. It definitely took 70 minutes though so maybe I just have a weird SD I used for my restore. I think I'll be picking up a second samsung to use for backup and restore instead of this kingston. Seeing an error spooked me

Edit: Maybe the kingston is fake? It was able to contain the full nand backup to restore but in SD Info it says it's speed class 4. Yep, definitely thinking fake after closer inspection of it.

Basically I created the backup on a known good sd card but attempted to restore on a spare I had laying around. I might try to restore again with my known good card but my switch appears to be working fine so I'm not sure if I should bother
 
Last edited by whyyes,

XaneTenshi

Well-Known Member
Member
Joined
Nov 24, 2013
Messages
506
Trophies
0
Age
34
XP
1,124
Country
Denmark
I'm wondering about the "Restore" options. I noticed that the BOOT0 and BOOT1 are required to be in different locations:
/Backup/Restore/BOOT0
/Backup/<eMMC S/N>/Restore/BOOT1

Is this a typo?

From OP:
Restore eMMC BOOT0/1 (Dangerous!):
Do not use that if you don't know what you are doing! No one is responsible for messing with your device.
You have a 10 second mandatory wait time before letting you start restore by pressing POWER.
This let's you restore your eMMC BOOT0 and BOOT1 partitions.
It will only restore the files at /Backup/Restore/BOOT0 and /Backup/<eMMC S/N>/Restore/BOOT1.

I don't know why he does not include the file extensions on the boot files in that path, but no, it's not really a typo, but it's not an extra folder either. The "BOOT1" and "BOOT0" refers to the files themselves, so you'd just place the boot files under "Restore/"

Look here for another example:

From OP
"This let's you restore your eMMC general purpose partition. If hekate find the /Backup/<eMMC S/N>/Restore/rawnand.bin it will restore it and verify it."

As in previous example, you place "rawnand.bin" under "/Restore/". It is not an extra folder. Basically all 3 files need to be in the same directory.
 

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
I'm wondering about the "Restore" options. I noticed that the BOOT0 and BOOT1 are required to be in different locations:
/Backup/Restore/BOOT0
/Backup/<eMMC S/N>/Restore/BOOT1

Is this a typo?

From OP:
Restore eMMC BOOT0/1 (Dangerous!):
Do not use that if you don't know what you are doing! No one is responsible for messing with your device.
You have a 10 second mandatory wait time before letting you start restore by pressing POWER.
This let's you restore your eMMC BOOT0 and BOOT1 partitions.
It will only restore the files at /Backup/Restore/BOOT0 and /Backup/<eMMC S/N>/Restore/BOOT1.
I don't know why he does not include the file extensions on the boot files in that path, but no, it's not really a typo, but it's not an extra folder either. The "BOOT1" and "BOOT0" refers to the files themselves, so you'd just place the boot files under "Restore/"

Look here for another example:

From OP
"This let's you restore your eMMC general purpose partition. If hekate find the /Backup/<eMMC S/N>/Restore/rawnand.bin it will restore it and verify it."

As in previous example, you place "rawnand.bin" under "/Restore/". It is not an extra folder. Basically all 3 files need to be in the same directory.
It's a typo. Both have to be in /backup/<emmc sn>/restore/ folder.

I did a full restore earlier tonight and it seems to have worked fine except during the verification of the rawnand I got the old issue mentioned here https://github.com/CTCaer/hekate/issues/30 . It did complete properly, my NAND backup was the correct size and all. It definitely took 70 minutes though so maybe I just have a weird SD I used for my restore. I think I'll be picking up a second samsung to use for backup and restore instead of this kingston. Seeing an error spooked me

Edit: Maybe the kingston is fake? It was able to contain the full nand backup to restore but in SD Info it says it's speed class 4. Yep, definitely thinking fake after closer inspection of it.

Basically I created the backup on a known good sd card but attempted to restore on a spare I had laying around. I might try to restore again with my known good card but my switch appears to be working fine so I'm not sure if I should bother
Class 4 are dead, since ever. So, if it's not an old sd card, it's def fake.


EDIT:
Fixed the typo in OP. If you find anything else please tell me.
I never properly updated it though.. Just some bits here and there.
 
Last edited by CTCaer,

GDT

Active Member
Newcomer
Joined
Nov 12, 2009
Messages
29
Trophies
1
Age
45
XP
583
Country
Italy
Yes, in the ini file just add this kind of line after the [config] block

{-- category name --}
[sub category name]
payload=bootloader/payloads/nameofpayload.bin
{ }

On the sd card, put your payload in the bootloader/payloads folder
Then in ctcaer mod, go to autoboot and select your payload under your chosen category name and select it for autoboot

I'm a noob about switch modding, I need to understand... I enabled autoRCM, after going the first time in RCM mode with a modded paperclip. I don't have a usb dongle for inject payload, so with this method I can autoboot a payload from sd?
 

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
So should I rerun the restore with a legit card? It did work with the fake it just failed to verify, possibly because of how slow the card is.
It's better to do that yeah!

I'm a noob about switch modding, I need to understand... I enabled autoRCM, after going the first time in RCM mode with a modded paperclip. I don't have a usb dongle for inject payload, so with this method I can autoboot a payload from sd?
You always need to inject a payload.
It's just that now you don't need the paperclip.
 

p1w1x

Well-Known Member
Newcomer
Joined
Aug 14, 2018
Messages
68
Trophies
0
XP
1,132
Country
Uruguay
Hi, I have some troubles to get a new nand dump. I did a backup before (I was on 5.1.0) and I am trying to do a new one with my Switch on 6.1.0 with the fuses burned & exFat update. MicroSD info: SanDisk Ultra 32gb 10 HC I, its the same SD used in my first backup. Using the lastest version of hekate I have the next errors and it is imposible to do a nand backup.

SD in exFat with more than 29.8 gb free space
[fatfs] Error: WLIO. Fatal error (1)

SD in exFat with less than 29.8 gb free space (partition enabled)
SD card and eMMC data (@LBA <code>), do not match! Verification failed..

Resuming the last one:
[fatfs] Error: WLIO. Fatal error (1) - Again!

SD in fat32 with more than 29.8 gb free space
SD card and eMMC data (@LBA <code>), do not match! Verification failed.. - Again!

I dont know what to do.
I am going to try with ReiNX Toolkit, but the format of that backup nand works with Hekate for restore in the future?

EDIT: now I remember that my last nand backup was using Rei Toolkit, the new files this tool just generated looks the same
 
Last edited by p1w1x,

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
Hi, I have some troubles to get a new nand dump. I did a backup before (I was on 5.1.0) and I am trying to do a new one with my Switch on 6.1.0 with the fuses burned & exFat update. MicroSD info: SanDisk Ultra 32gb 10 HC I, its the same SD used in my first backup. Using the lastest version of hekate I have the next errors and it is imposible to do a nand backup.

SD in exFat with more than 29.8 gb free space
[fatfs] Error: WLIO. Fatal error (1)

SD in exFat with less than 29.8 gb free space (partition enabled)
SD card and eMMC data (@LBA <code>), do not match! Verification failed..

Resuming the last one:
[fatfs] Error: WLIO. Fatal error (1) - Again!

SD in fat32 with more than 29.8 gb free space
SD card and eMMC data (@LBA <code>), do not match! Verification failed.. - Again!

I dont know what to do.
I am going to try with ReiNX Toolkit, but the format of that backup nand works with Hekate for restore in the future?
That's a low level I/O error.
Can you send me a photo of Console info -> Sd card info?

EDIT:
And prepare yourself
 

p1w1x

Well-Known Member
Newcomer
Joined
Aug 14, 2018
Messages
68
Trophies
0
XP
1,132
Country
Uruguay
That's a low level I/O error.
Can you send me a photo of Console info -> Sd card info?

EDIT:
And prepare yourself

You scared me a little haha. I attached a picture. I am doing the backup with Rei Toolkit and it seems there is no problem, it stopped at 7 of 10 because the space. If this continue to 100% and a get the backup, is compatible with Hekate for restore?

I appreciate your response and I take the opportunity say great job with your mod!
 

Attachments

  • WhatsApp Image 2018-11-26 at 20.32.50.jpeg
    WhatsApp Image 2018-11-26 at 20.32.50.jpeg
    179 KB · Views: 228

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
Your card seems to be a very good fake.

Unfortunately, it's easy to see for me.
1: All sandisk A1 cards and generally A1 cards are U1 also.
2: All sandisk A1 careds are also SDR104, aka 104MB/s bus speed.

But, even though this data is valid afaik, there's a chance that this is not a fake and Sandisk cheaped out and started creating even more crappier cards.
So to see if it's not really fake or it hasn't any problem, it's best to test it with a program like h2testw.
(Can you attach a photo of the card? I'm curious to see how it looks like)
 
  • Like
Reactions: tiliarou

p1w1x

Well-Known Member
Newcomer
Joined
Aug 14, 2018
Messages
68
Trophies
0
XP
1,132
Country
Uruguay
Your card seems to be a very good fake.

Unfortunately, it's easy to see for me.
1: All sandisk A1 cards and generally A1 cards are U1 also.
2: All sandisk A1 careds are also SDR104, aka 104MB/s bus speed.

But, even though this data is valid afaik, there's a chance that this is not a fake and Sandisk cheaped out and started creating even more crappier cards.
So to see if it's not really fake or it hasn't any problem, it's best to test it with a program like h2testw.
(Can you attach a photo of the card? I'm curious to see how it looks like)

I'm not surprised at all, I know there are a lot of fake cards around *sigh*. This is my card from a local store. I think I will buy a 128gb Samsung from amazon. Can you confirm my last question about the nand backup? or anyone?
 

Attachments

  • WhatsApp Image 2018-11-26 at 20.58.09.jpeg
    WhatsApp Image 2018-11-26 at 20.58.09.jpeg
    88.3 KB · Views: 204
Last edited by p1w1x,

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
I'm not surprised at all, I know there are a lot of fake cards around *sigh*. This is my card from a local store. I think I will buy a 128gb Samsung from amazon. Can you confirm my last question about the nand backup? or anyone?
Oh god. There are no white sandisks.
Ultras are either black with red letters or Blue-grey/red.
Also there's no A1.

It's a fake :/
Hekate correctly reported errors.

Hekate can restore that backup (If you rename the 2 boot partitions to BOOT0 and BOOT1).
But if you do it, you'll risk of corrupting your eMMC.

EDIT:
Just saw that these white ones are new. Let me research and check your pic again

EDIT2: @piwix
OK, didn't know these exist.
I looked the picture again it seems that it's pretty good to be fake.
Also these cards are rated at max 48MB/s which matches your bus speed.
(Still A1 without U1 is strange)

So, I'm not sure why you have these errors.
It may be from not fully seated sd card reader (so some bits can change).
I would be careful in your case.

--------------------- MERGED ---------------------------

@piwix
Ping for importance
 
Last edited by CTCaer,
  • Like
Reactions: tiliarou and p1w1x

p1w1x

Well-Known Member
Newcomer
Joined
Aug 14, 2018
Messages
68
Trophies
0
XP
1,132
Country
Uruguay
Oh god. There are no white sandisks.
Ultras are either black with red letters or Blue-grey/red.
Also there's no A1.

It's a fake :/
Hekate correctly reported errors.

Hekate can restore that backup (If you rename the 2 boot partitions to BOOT0 and BOOT1).
But if you do it, you'll risk of corrupting your eMMC.

EDIT:
Just saw that these white ones are new. Let me research and check your pic again

I am sad, but I appreciate your help. I was able to get the BOOT0 and BOOT1 with Hekate. Sounds crazy but I need to ask, can I use these boot backups with the nand backup generated with the toolkit?
 

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
amazing loader
question why is the nand back up so slow??
i thought switch hardware was decent??
The actual backup is around 23 minutes.
Depends on your sd card and format.

What takes a long time is that green bar which is the verification process. It basically reads back the data from your sd card and checks it bit for bit.

You can disable it if you know that you have a legit card, or at least you can choose the faster mode.

But if you don't know if your card is OK, I wouldn't do that.

Anyway, that process takes a long time, mostly because the whole process runs on a tiny cpu, called BPMP, which is designed only to boot your console and do power management.
Down the road I plan to port it to the normal cores, so it can have max speed.
 

gundamu

Well-Known Member
Member
Joined
Apr 28, 2016
Messages
251
Trophies
0
Age
33
XP
247
Country
Canada
The actual backup is around 23 minutes.
Depends on your sd card and format.

What takes a long time is that green bar which is the verification process. It basically reads back the data from your sd card and checks it bit for bit.

You can disable it if you know that you have a legit card, or at least you can choose the faster mode.

But if you don't know if your card is OK, I wouldn't do that.

Anyway, that process takes a long time, mostly because the whole process runs on a tiny cpu, called BPMP, which is designed only to boot your console and do power management.
Down the road I plan to port it to the normal cores, so it can have max speed.


wow didn't know it ran on cpu then a tegra
cheers mate
 

Calebotomy

New Member
Newbie
Joined
Nov 27, 2018
Messages
1
Trophies
0
XP
57
Country
United States
So, Ive tried searching through the thread and cant find anyone who had my same issue. I have my boot0.bin and boot1.bin the the correct restore folder. I was able to restore my rawnand.bin just fine but when I try to do the BOOT1 & 2 I get error (4) even though the files are in the correct location.

Am I missing something simple? any help is much appreciated.

Edit1: I've tried 2 different cards. both 200GB sandisk cards onee FAT32 and the other exFAT(which i restored the nand with)

Edit2: Just tried a 32GB samsung card and same thing. What am I doing wrong?
 
Last edited by Calebotomy,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    fluff663 @ fluff663: hoi