Hacking FW Updating and Hacking 1.0.0 Switch?

  • Thread starter Thread starter metaphz
  • Start date Start date
  • Views Views 8,463
  • Replies Replies 48
  • Likes Likes 1
Th


Thanks, I appreciate all you help along with everyone else here.

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

@Draxzelex

I did some GoogleFu and found what you were talking about. I don't have that many entries in my Keys.txt. I feel like I may be missing some (ie SSL is missing). Should I just go back and try to dump this again? Does it matter what Firmware version I am on? Do I need this to restore a previous NAND backup?
You can try dumping it again. I would recommend clearing out the kezplez folder before trying again as older files stuck in the folder can disrupt repeated dumps. Also firmware only affects the number of masterkeys dumped; all other keys will remain the same on all firmware. No, you do not need these keys to restore the NAND; they are used for a variety of different things such as decrypting games and converting .XCI files
 
You can try dumping it again. I would recommend clearing out the kezplez folder before trying again as older files stuck in the folder can disrupt repeated dumps. Also firmware only affects the number of masterkeys dumped; all other keys will remain the same on all firmware. No, you do not need these keys to restore the NAND; they are used for a variety of different things such as decrypting games and converting .XCI files

Got it to work...Deleted the release from Github and reused the release from the SDCard File pack from Backup/Restore guide...
 
Last edited by metaphz,
Otherwise, you would have to install them into your system as .XCI files using ZeroTwoXCI/dOPUS or converting them to .NSP format (with 4NXCI/dOPUS). To dump your cartridges, you will have to use a homebrew application such as gcdumptool or WAIN Cart Dumper. .

I'm attempting to do this. 4NXCI gives me the following error;

[WARN]: Failed to match key "eticket_rsa_kek", (value "nokey")

I look at my prod.keys that's been renamed to keys.dat for the application and of course I see this;

eticket_rsa_kek = nokey

What have I missed this time? With screwing up with the 1.0.0 Cart Slot firmware should I just abandon all of this and use the SXOS and it's dongle?
 
I'm attempting to do this. 4NXCI gives me the following error;

[WARN]: Failed to match key "eticket_rsa_kek", (value "nokey")

I look at my prod.keys that's been renamed to keys.dat for the application and of course I see this;

eticket_rsa_kek = nokey

What have I missed this time? With screwing up with the 1.0.0 Cart Slot firmware should I just abandon all of this and use the SXOS and it's dongle?
That key's not even necessary for converting an .XCI to an .NSP file. Plus, its just a warning; a warning is not an error, a warning is a warning and an error is an error. You can just get the appropriate key online but its not going to affect whether or not the tool works.
 
Please tell me you fully backed up first ??

https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/



You can use sx os if you wish making sure to use the latest payload/boot.dat files from there website tho so you dont burn ya fuses ....

Or run hekate payload first then run the sxos payload from hekate if u want...

Or use a free open source cfw reinx reijx etc...with hekate..

Aslong as you take a fuse check bypass method you may revert back to 1.0

Also systems 1.0 dont have as many keys as say a 5.1.0 system,

In my backup guide your get everything you need,, to get your keys and backup your emmc/nand
 
Last edited by Canna,
Please tell me you fully backed up first ??

https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/



You can use sx os if you wish making sure to use the latest payload/boot.dat files from there website tho so you dont burn ya fuses ....

Or run hekate payload first then run the sxos payload from hekate if u want...

Or use a free open source cfw reinx reijx etc...with hekate..

Aslong as you take a fuse check bypass method you may revert back to 1.0

Also systems 1.0 dont have as many keys as say a 5.1.0 system,

In my backup guide your get everything you need,, to get your keys and backup your emmc/nand

I followed your guide and ran in to a myriad of issues. Mainly getting the Keys from the device with kezplez-nx and HBMenu kept crashing when I tried to do anything. I finally finished, including updating to 5.1.0 with ChoiDujour. My Fuse count is still at 1 but I accidently updated the Game Card slot firmware through ReiNX. I still seem to be having minor issues.
 
Last edited by metaphz,
I followed your guide and ran in to a myriad of issues. Mainly getting the Keys from the device with kezplez-nx and HBMenu kept crashing when I tried to do anything. I finally finished, including updating to 5.1.0 with ChoiDujour. My Fuse count is still at 1 but I accidently updated the Game Card slot firmware through ReiNX. I still seem to be having minor issues.
What do you mean minor issues ?

What are the minor issues,,?
When you updated to 5.1.0 with choidujournx did you install the exfat also ?

sounds like you may have a partially corrupt sd card

need to copy your backup folder on your sd card to your pc,
then reformat your sd card to what ever your 5.1.0 supports so exfat or fat 32
then just drop the files from my guide onto the root of your sd card, i checked those today and made sure there updated with latest kezplez and tomger sd files.. so they should work ok for you...
 
What do you mean minor issues ?

What are the minor issues,,?
When you updated to 5.1.0 with choidujournx did you install the exfat also ?

sounds like you may have a partially corrupt sd card

need to copy your backup folder on your sd card to your pc,
then reformat your sd card to what ever your 5.1.0 supports so exfat or fat 32
then just drop the files from my guide onto the root of your sd card, i checked those today and made sure there updated with latest kezplez and tomger sd files.. so they should work ok for you...

Already ahead of you, thanks for the reply though! That is exactly what I have done. Is there any reason to join the rawnand.bin prior to actually needing it to restore?

As an aside, do you know where I can find instructions on modding my SX Pro Dongle to boot the Hekate or ReiNX payloads instead of SXOS?
 
Already ahead of you, thanks for the reply though! That is exactly what I have done. Is there any reason to join the rawnand.bin prior to actually needing it to restore?

As an aside, do you know where I can find instructions on modding my SX Pro Dongle to boot the Hekate or ReiNX payloads instead of SXOS?
two options

Personally i would join those partial files now so you have 1 file backup..
Use the mini fat32 guide in my post to join the files into 1 rawnand.bin and store it somewere safe with a copy of boot1 and boot0 and say a txt file of your biskeys


SXOS

option1 for manual use...........
place the payload hekate or reinx on the root of your sd card, and press and hold volume up when booting up sxpro dongle to get into the sx os menu, then select options i believe and launch hekate or reinx payload..

option2 for automatic use.........
Go to the official website and download the SXGEAR boot.dat and place it onto the root of your sd card overwriting the sxpro boot.dat.. Then place any payload you wish to use hekate or Reinx on the root of the sd card and rename it to payload.bin.....
 
Last edited by Canna,

Site & Scene News

Popular threads in this forum