This Multi-Guide provides instruction for the following:

Back up your NAND,
Backup your system information,
Restore your NAND,
Make exFAT work on lower system versions
​

Please read and follow the following disclaimer before attempting to follow this guide:

Only use the files attached, I update these when needed to ensure that they are functioning. Failure to use the attached files may result in issues.

I take no responsibility for issues you may have as a result of the use of the files or instructions contained within these guides. You execute this/these guide(s) at your own risk. I'm happy to help with any questions. Please review the comments and answers on this thread as well. I try to provide assistance when requested.

Before any modification of your system, I recommend you back-up your NAND (to make yourself a clean back-up and/or a virgin NAND). Don’t use Auto RCM until after you complete your back-up.​

To follow the below guides, you will need the following:

• A micro SD card formatted to exFAT or FAT32 with at least 32 GB of free space
• All files attached at end of this guide, extracted to your PC
• Fully charged Switch (or the ability to keep the Switch plugged into a power source during the restore process)
• USB to USB-c cable (short is better)

This guide assumes you have some method of entering into RCM. (e.g. RCM jig installed or shorting pins 1+10 on the Joy-Con rail.)
You may also run the "Hekate.bin" from your own dongle or method from the
"Payloads to be used with tegra.zip" if you do not wish to use TegraGUI​

For Fat32 users only >>Join RawNand Parts Mini Guide​

Spoiler: Join or Merge RawNand Parts guide into 1 file

Download this first click here > >joiner_scripts_for_windows_linux_macos.zip
to combine the 15 parts or 30 parts of rawnand00.bin etc into 1 rawnand.bin file
Place the correct script into the folder where you have the 15 or 30 parts backed up.
example
If you have 15 parts rawnand files use the join_15_2GBparts_linux_macosx.bat For Mac
or for windows use the join_15_2GBparts_windows.bat
Simply move the desired script that matches your system windows or mac 15 or 30 parts to the folder where you have your rawnand in parts 15 or 30 double click the bat file and it will merge/join those into one file called rawnand.bin

Backup Guide ​

Spoiler: Click show to view Backup Guide

In order to run the "Hekate.bin", you first need to setup and install a payload sender and the apx driver. I have provided an application (TegraRcmGUI) in the zip files at the end of this post.

You may also run the "Hekate.bin" from your own dongle or method from the "Payloads to be used with tegra.zip" if you do not wish to use TegraGUI



Steps for this are as follows:

1. Extract TegraRcmGUI_v#.#_Installer.zip on your PC and install
   
   
2. In TegraRcmGUI, select the “Settings” tab and then click “Install Driver”
   
   
   
   
   
   
3. Place the contents of “SDFILES PART 1.zip” and “SDFILES PART 2.zip” and also “SDFILES PART 3.zip” onto the root of the SD card
   - Remember to format your 32 GB SD card to exFAT or FAT32 first
   
   
4. Place the SD card into the Switch
   
   
5. Put your Switch into RCM by holding volume up + power
   - Click this link for instructions for entering >RCM<
   
   
6. With TegraRcmGUI open, connect the Switch to the PC
   - Before injecting, the Switch Icon will change to green and indicate “RCM OK” if Switch was connected correctly in RCM mode
   
   
   
7. In TegraRcmGUI: Payload tab, navigate to the location of the hekate.bin on your PC and Inject payload
   (the hekate.bin is in the payloads to be used with tegra.zip)
   
   - The Switch Icon in TegraRcmGUI will change to orange hourglass during injection
   - If payload is sent correctly, Switch Icon in TegraRcmGUI will change to green checkmark
   - If the payload is not sent, try using a different (shorter) cable and repeat from step 5.
   
   
8. Switch will automatically boot into Hekate bootloader (steps 9-24 take place on the Switch)
   
   
9. From the hekate main menu, select “Console Info”
   
   
   
   
   
   
10. Select “Ipatches & bootrom info” (this isn’t in the screenshot above but should be in the Hekate Console info menu.)
    
    
11. Follow the instructions to dump to SD card
    
    
12. Return to Console info menu
    
    
13. Repeat steps 10-12 for “Print fuse info”, “Print kfuse info” and “Print TSEC keys”
    
    
14. Return to Hekate main menu (by selecting “Back” at the top)
    
    
15. From the hekate main menu, Select “Tools”
    
    
    
    
    
    
16. Select “Dump package1/2” and allow this to run
    
    
17. When complete, return to Tools menu
    
    
18. “Select “Backup”
    
    
    
    
    
    
19. Select “Backup eMMC BOOT0/1” and allow this to run
    
    
20. When complete, return to “Backup options” menu (by selecting “Back” at the top)
    
    
21. Repeat steps 19 & 20, selecting “Backup eMMC RAW GPP”, “Backup eMMC SYS” & “Backup eMMC USER” instead of “Backup eMMC BOOT0/1”
    - These may take some time so be patient. The result will be a
    - dump of Full NAND Minus the boot0/1
    
    
    - (I RECOMMEND YOU BACKUP EMMC SYS , YOU WILL NEED A EXTRA 2.61GB ON SD CARD FOR THIS..
    Used so you can recover switch in case of bad rawnand)
    ANOTHER COPY OF YOUR SYS FILES THE SAME IN YOUR RAWNAND.BIN Basically
    
    
    - (Backing up EMMC USER is Your Choice as it requires 26gb Extra)
    Used to backup your User files saves games etc
    
    
    emmc user and emmc sys are in your rawnand.bin > (eMMC RAW GPP)
    
    
    
    
22. Return to Hekate main menu (by selecting “Back” at the top)
    
    
    
23. From the hekate main menu, Select “Launch”
    
    
    
    
    
    
24. Select “BisKeyDump" from the Tools section
    
    
25. Your keys will display on the screen. Follow the onscreen instructions to dump keys to SD card
    - Resulting file, on the root of the SD card, will be named device.keys
    - Rename to “biskeys.txt” if you wish.
    
    
26. With TegraRcmGUI open, connect the Switch to the PC
    
    
27. In TegraRcmGUI: Payload tab, navigate to the location of the Lockpick_RCM.bin on your PC and Inject payload... (Lockpick_RCM.bin is in the payloads to be used with tegra.zip)
    - You should now be presented with a freaking rainbow
    - It will automatically dump your keys to your SD card to the "switch folder" the file will be named "prod.keys"
    
    
28. Press the power button on your switch.
    - Once powered off remove your SD card and put it into your pc.
    -You can now close Tegra and remove USB cable from switch to pc, if still connected.

You could also read the exFAT guide on my main post if you're having trouble running CFW or accessing Homebrew menu to update your lower system version to have exFAT support​

If you have an error when trying to use Goldleaf, please try the Goldleaf Error Guide below.
If you don't, you can skip Goldleaf Error Guide

Goldleaf error guide ​

A Big Thanks @shchmue for sorting out the bugs and for her work on the Goldleaf issues.
​

Spoiler: Click Here to show [B]Goldleaf[/B] error guide

Ensure you have a complete set of dump files:

Dump all the console info using the payload I included hekate.bin
(the hekate.bin is in the payloads to be used with tegra.zip)

1. From the hekate main menu, select “Console Info”
   
   
   
   - Console Info -> Print fuse info -> Press power button
   - Console Info -> Print kfuse info -> Press power button
   - Console Info -> Print TSEC keys -> Press power button
   
   
2. From the hekate main menu, Select “Tools"
   
   
   - Tools -> Backup -> Backup eMMC BOOT0/1
   - Tools -> Dump package1/2
   
3. Ensure all of the following files are on your SD card:
   - /switch/Goldleaf.nro
   
   
4. In the backup folder on the SD card, inside the letter and number folder, open folder dumps. Confirm the following files are present:
   
   
   - fuses.bin
   - kfuses.bin
   - tsec_key.bin
   
   
   If you’re missing one of the above .bin files, follow the Console Info instructions (above) to dump them again.
5. In the pckg1 and pckg 2 folders on the SD card, confirm the following files are present:
   
   
   pckg1 folder
   - nxloader.bin
   - pkg1_decr.bin
   - secmon.bin
   - warmboot.bin
   
   pckg2 folder
   - ini1.bin
   - kernel.bin
   - pkg2_decr.bin
   
   
   If you’re missing one of the above .bin files, follow the Tools -> Dump package 1/2 instructions (above) to dump them again.
6. On the SD Root, confirm the following files are present:
   
   
   - Boot0
   - Boot1
   
7. In the backup random number letters folder, confirm the above files are present as well.
   
   
   
   If you’re missing one of the above files, follow the Tools -> backup emmc BOOT0/1 instructions (above) to dump them again.
   
   If they are missing from one location or the other, they can be copied to the location where they are missing.

Try the Goldleaf.nro again

Before you continue

It has come to my attention that some windows 10 operating systems with builds 1507/1511/1607 will experience an issue transferring nand or switch system files from PC to your SD card or Switch. This issue results in missing bits in the copies of the archive bits, needed for the switch to operate correctly or restore of nand to work.

Our member here @Draxzelex was nice to point this out , so I thought I would add it to the guide.

If you’re on one of the affected versions of Windows 10, before transferring your files, it is recommended to use a third party application called Total commander to transfer the backups to your SD card or even when you’re moving the backup folders on PC

To check your windows 10 version:

Go to windows search by clicking the windows key (start)

Search for ‘about your PC’ in the search bar, and select ‘About your PC’ in the search results

On the right-hand side scroll down to Windows Specifications

In this section, you will see your build version

If you are above build 1607 you can ignore this information in blue.
If you are not above version 1607 then either please use Windows Update to update your build or use Total commander to move your backups around your PC or to SD card

Instead of using Total commander, you could try a method of using a compression zip/rar program like WinRAR to archive or compress the backup folder on your SD before you even think about transferring to PC, and when you go to move backup back to SD card transfer your zip or RAR to SD then extract it from there

(Not tested )

You may Continue


29. On your PC make a folder where you're going to place your backup switch nand and files



30. If you used lockpick to backup your prod.keys then Open your SD card on your PC and copy the prod.keys from the switch folder on the SD card to the folder.



31. Copy the entire backup folder from SD card to your backup folder on PC.



32. Please zip or rar the backup folder once you have transferred it on your PC
this will also save space.



Also, save the biskey.txt and prod.keys You made earlier to your backup folder
Once you backed up to your PC

And that's it.


I hope this may of helped you all or i just wasted hours of my life here


You can skip the guide below if your only backing up your nand and keys

Restore Nand Guide​

I take no responsibility for issues you may have or if your system fails to boot after restoring your NAND.
You do this at your own risk!

Please make sure to read the blue text in my Backup guide above when you made your backup

To follow the below guide, you will need the following:

Make sure your battery is charged (at least enough to complete the restore process) or keep the switch plugged into a power source (USB cable should be fine)

Spoiler: Click show to view Restore Nand Guide

Restoring your nand.....

Providing you have followed my guide above to back-up your NAND, you should have the 3 required files in your backup folder
(Plus some other files we won't be using for your restore)

- boot 0 ​

- boot 1​

- rawnand.bin
​

If you do not have these files please do not continue

1. From your number and letters folder inside the backup folder on pc, copy the below files to the restore folder on your SD card
   
   
   - Boot 0
   - Boot 1
   - rawnand.bin
   
   
   Example on sd card
   inside The folder on SD card Backup>numberletter folder>restore folder <....place files here...
2. Place the SD card into the Switch
   
   
3. Put your Switch into Rcm Mode
   
   
4. Boot into the hekate bootloader *Hekate.bin* By using tegrarcmsmashGUI
   
   
   
   
   
5. From the bootloader hekate main screen, select tools option with the volume +/- buttons and press power button to select
   
   
   
   
   
6. In the tools section, Select Restore
   
   
   
   
   
   
   
   
7. In the restore options screen, select “Restore eMMC BOOT 0/1”
   - You will be warned and asked if you are sure. To continue, press the power button and wait for the process to finish.
   - Once finished press any key to go back (do not power off at any time)
   
   
   
   
   
   
   
   
8. Still in the restore options screen, select “Restore eMMC RAW GPP”
   - You will be warned and asked if you are sure. To continue, press the power button and wait for the process to finish. This will take some time.
   - Once finished press any key to go back (do not power off at any time)
   
   
   
   
   
   
   
   Now assuming all the processes went smoothly and you got no errors you should now be restored!
9. Go back to the Hekate main menu by selecting back
   
   
   
   
   
   
   
   
10. On the main menu select power off.
    
    
    
    
    
11. Reboot your switch as normal with the power button

If all went well, you should now see the Nintendo logo and should boot back into the main OS of the switch.


Well done you successfully restored your NAND!!

Did you sh*t your pants ???


Again I take no responsibility For backing up and or restoring your NAND, this is a dangerous process and you do it at your own risk.


If I have helped you and this worked for you please hit that like button.


Thanks, and have a good day!

Exfat Update Guide For
Lower System Versions​

Spoiler: Click here to view exfat update guide

At this time I have not made the exFAT guide myself so until I do I thought I’d link to another exFAT guide,
Please like his thread if it helps you and mine if you like the information I’ve provided

Method 1 (Not as easy but doable)
Method 1 Link
Method 2 (A lot easier)
Method 2 Link


Info taken from Method 2


Q: I just want to install exFAT on the current firmware version I already have. Can I do this using ChoiDujourNX?


A: Absolutely, just place a folder containing the exFAT version of the firmware you are currently running and choose it inside ChoiDujourNX. It will only install the required couple of packages needed for exFAT, and you can even disable the AutoRCM option (if you are sure the firmware you are installing is the same burned fuse count as the one you are currently running).

​

If i have helped you, Or you like my post
Then Please hit that like button it will help me a'lot thank you

​

 

[Canna]

I have succesfully downgraded to 3.02 but ofcourse my cart slot is no worky
So my next step is to update to 4.x factory update to enable it again.
Choidujournx nro ..

Good for you now you either replace slot with one you buy on a lower update, or update to 4.0.1..

On 4.0.1 some of your games might not work if they need 5.0 + update..

I just went to 5.1.0 and said fck it lol anyway good luck hope i helped

 

[Draxzelex]

Wow.. this is a crucial detail that shouldn't be omitted.. I'm using Win 10 pro build 1803 when I did the transfer of my nand from sdcard to PC.. shouldn't have any issues right?

What happens if you try to restore a nand with the archive bits missing? It bricks the console?

Ok, looks like backing up the nand whether it's on an older build of windows 10 or not won't affect the integrity of the file. Just that the nand backup file properties for "file is ready for archiving" needs to be unchecked before transferring back to the sdcard for a nand restore?

I would like to know too if the integrity is affect.

Also is this usefull if after doing a fw update avoiding burnt fuses I can downgrade back using this method

In the ReiSwitched Discord server, we had not one but 2 users who updated without burning fuses the old way but had a "bricked" console after they were done. They repeatedly kept restoring their NAND backups they made to no avail. After discovering that both users were using Windows 10, we realized that their consoles were soft-bricked because it could not read any of the folders transferred. Once they used a tool such as Total Commander, their units came back to life and we now recommend anyone with a Windows 10 computer to just use Total Commander to avoid any possible problems.

 

[Bloodlust]

How did they manage to restore the nand again after soft bricking the unit? So assuming that the nand backup wasn't working only because they tried using the default Windows 10 file explorer to transfer the file over and it didn't work but using total commander did?

In the ReiSwitched Discord server, we had not one but 2 users who updated without burning fuses the old way but had a "bricked" console after they were done. They repeatedly kept restoring their NAND backups they made to no avail. After discovering that both users were using Windows 10, we realized that their consoles were soft-bricked because it could not read any of the folders transferred. Once they used a tool such as Total Commander, their units came back to life and we now recommend anyone with a Windows 10 computer to just use Total Commander to avoid any possible problems.

Sent from my MI MAX using Tapatalk

 

[daltononline]

Hello every one
first of all i would love to thanks you guys for your detail tutorial and your amazing contribution to the hacking community

my switch OFW is on 5.1.0 my Micro sd is formatted into EXFAT . i follow the tutorial step by step and every thing works perfectly however it seems i am having problem with the last stage where i need to back up my console keys . i run the CFw run the program and rainbow appear how even the count down reach to 6 i will receive a error massage ask me to shout down the switch . i have no idea why since i check my micro SD and it seems i have all the necessary files . any one how any idea why i am getting this message and what shoud i do next to over come it ????

 

[afra]

In the ReiSwitched Discord server, we had not one but 2 users who updated without burning fuses the old way but had a "bricked" console after they were done. They repeatedly kept restoring their NAND backups they made to no avail. After discovering that both users were using Windows 10, we realized that their consoles were soft-bricked because it could not read any of the folders transferred. Once they used a tool such as Total Commander, their units came back to life and we now recommend anyone with a Windows 10 computer to just use Total Commander to avoid any possible problems.

I guess I am really lucky using old build 2015 windows 10 and it copied everything just fine

 

[jasonrye]

So I was able to follow this guide and get everything backed up, but I'm not sure I understand how it's used.

I opened up a BNIB Switch with 4.1 firmware, went through initial setup, and then did all the backups.
If I'm planning on updating to 5.1 and I don't care about nogc/fuses/downgrading - are the backups I just made useless (should I have done the backups on 5.1?) or can they still be used in emergencies?

 

[DeathGrind]

Hmm interesting... boot 0 boot 1 on sd root and in the backup folder ?

When is it you see a error message, number 17 or 19..
what does the error say.
and post for me the contents of the keys.txt minus the keys/value

If it reaches 19 its normally finished
Should say all keys extracted then press + to exit

But i believe thats when it throws the error or freezes switch cause it cant exit correctly back to home brew or menu

Hello again. My attempts at using kezplez continually fail at 17. The error is as follows:

"Error Code: 2345-0021

An error has occurred.

Please hold the POWER Butoon for 12 seconds and turn off the console.

If the problem persists, refer to the nintendo Support Website."

etc...

I have read and run through the guide multiple times, making sure everything is in the correct place. Kezplez always errors out

I would post what keys.txt is created before the error occurs, but I'm not sure What keys/values to minus out...

EDIT....keys.txt posted with keys values erased, all had values

 

[Canna]

Hello again. My attempts at using kezplez continually fail at 17. The error is as follows:

"Error Code: 2345-0021

An error has occurred.

Please hold the POWER Butoon for 12 seconds and turn off the console.

If the problem persists, refer to the nintendo Support Website."

etc...

I have read and run through the guide multiple times, making sure everything is in the correct place. Kezplez always errors out

I would post what keys.txt is created before the error occurs, but I'm not sure What keys/values to minus out...

EDIT....keys.txt posted with keys values erased, all had values

some how dude i think all your gonna need. not sure why your still experiencing the error

Like i said it errors on exit or 19 sometimes...

Il look into it alittle more. and get back to you at some point, if anyone knows the solution to this please let us know, all files are in correct places.

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

So I was able to follow this guide and get everything backed up, but I'm not sure I understand how it's used.

I opened up a BNIB Switch with 4.1 firmware, went through initial setup, and then did all the backups.
If I'm planning on updating to 5.1 and I don't care about nogc/fuses/downgrading - are the backups I just made useless (should I have done the backups on 5.1?) or can they still be used in emergencies?

Your backups are never useless ,You can still restore this,

but

If you update to 5.1

1st
make a backup of 5.1 same process, name ya backup folder like 4.1 or 5.1 etc
2nd
If you update to 5.1 officially the only way to run 4.1 again is with say hekate bootloader
following the no fuse burned update/downgrade guide
3rd
You could also use the no fuse burned guide to update to 5.1 from 4.1, but you must always use the bootloader
If you do not want to blow fuses
4th
If you really dont care make update to the latest and make a full backup again with keys

Hope this helps

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

I guess I am really lucky using old build 2015 windows 10 and it copied everything just fine

But have you restored :s risky

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

Hello every one
first of all i would love to thanks you guys for your detail tutorial and your amazing contribution to the hacking community

my switch OFW is on 5.1.0 my Micro sd is formatted into EXFAT . i follow the tutorial step by step and every thing works perfectly however it seems i am having problem with the last stage where i need to back up my console keys . i run the CFw run the program and rainbow appear how even the count down reach to 6 i will receive a error massage ask me to shout down the switch . i have no idea why since i check my micro SD and it seems i have all the necessary files . any one how any idea why i am getting this message and what shoud i do next to over come it ????

Your welcome for the guide , just me tho no one else
using information from others here at gba and making a guide to try assist you all.


Verify the files in your folders, i did attach information in the kezplez error guide
that show what files you should have and what needs to be dump please re check..

also what system update is your console on atm ?

Probably missing a file if your at 6

 

[daltononline]

some how dude i think all your gonna need. not sure why your still experiencing the error

Like i said it errors on exit or 19 sometimes...

Il look into it alittle more. and get back to you at some point, if anyone knows the solution to this please let us know, all files are in correct places.

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



Your backups are never useless ,You can still restore this,

but

If you update to 5.1

1st
make a backup of 5.1 same process, name ya backup folder like 4.1 or 5.1 etc
2nd
If you update to 5.1 officially the only way to run 4.1 again is with say hekate bootloader
following the no fuse burned update/downgrade guide
3rd
You could also use the no fuse burned guide to update to 5.1 from 4.1, but you must always use the bootloader
If you do not want to blow fuses
4th
If you really dont care make update to the latest and make a full backup again with keys

Hope this helps

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


But have you restored :s risky

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



Your welcome for the guide , just me tho no one else
using information from others here at gba and making a guide to try assist you all.


Verify the files in your folders, i did attach information in the kezplez error guide
that show what files you should have and what needs to be dump please re check..

also what system update is your console on atm ?

Probably missing a file if your at 6

thanks for reply i will check it again and will let u know i am on 5.1.0

 

[Canna]

thanks for reply i will check it again and will let u know i am on 5.1.0

Yes same as me and i followed my own tutorial and used same files last night to check for use guys and its working...
You are missing files..

As for the error at 17-19 im still thinking on a solution for use guys sorry at this time im not very helpfull
as i did not write the kezplez program or script

 

[afra]

Yes same as me and i followed my own tutorial and used same files last night to check for use guys and its working...
You are missing files..

As for the error at 17-19 im still thinking on a solution for use guys sorry at this time im not very helpfull
as i did not write the kezplez program or script

yeah İ told my friend that my guess is somwthing wrong with files .

Oh did you really tried it again LOL .

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

thanks for reply i will check it again and will let u know i am on 5.1.0

download and put files again inside SD bro

 

[Canna]

yeah İ told my friend that my guess is somwthing wrong with files .

Oh did you really tried it again LOL .

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


download and put files again inside SD bro

I had to retest make sure i was not hosting bad files.

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

Guys with issues,,
After checking you have all the correct files in the correct folders
By checking with the kezplez error guide.would you please copy the keys.txt on your sd to pc some were safe
and delete the keys.txt on the sd and in the kezplez-nx folder and try again
but only try 1 time and post your keys.txt file without the values
Cause it looks like the kezplez puts the entry in again and again if you reuse ...

And looking at the keys.txt some keys may not be copied from your system if you never installed a title aka demo or game...

Still working on this but backup your keys.txt then remove from sd card root.
and also the keys.txt in kezplez-nx folder

Then post to me

 

[Canna]

Right so i think those guys having key errors from 17-19 Should not worry so much
The same guys or girls that are on lower system version..
These keys.txt file is only for decryption of titles games etc

Im thinking that the errors are cause by
some of you not having games or demos installed.
and some of you on lower system updates and not 5.1.0

So from what it looks like
Certain systems have certain available keys to be dumped.

5.1.0 seems to have more then 4.1.0 for instance
which would make sence

From my knowledge the keys files seem to be the same with the same system versions of different people except for certain keys. Dont trust me on this as its just a observation..

so im thinking the errors we are receiving or failures with kezplez
are due to kezplez not finding the information or key it needs in your system
and due to some of you not dumping the required files
tsec keys boot 0 pck1/2 etc...

If someone with the knowledge of the keys.txt decryption keys could clear this up for me that be great thanks ..
Im sure these are the same or close across systems with minor differences ...

But for know guys im really sorry i cannot assist you further until someone confirms

If those with errors could post there system version before the post about the error this may help clear things up some more.


From what we know if you dont make it to number 17 in the kezplez programme, or cant start the program. then you are missing files or did not dump a file from guide.

 

[jasonrye]

4th
If you really dont care make update to the latest and make a full backup again with keys

Hope this helps

Yup, thanks for the reply and the guide overall!

 

[daltononline]

hi again i hecked i have all the files on my sd still when count down reach 4 i receives an error how ever i realized some thing u asked me to delete keys.text from keplez folder when i wanted to do that i realized there is nothing in keys.text technically its just blank page i was wonder is this normal ????

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

I had to retest make sure i was not hosting bad files.

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

Guys with issues,,
After checking you have all the correct files in the correct folders
By checking with the kezplez error guide.would you please copy the keys.txt on your sd to pc some were safe
and delete the keys.txt on the sd and in the kezplez-nx folder and try again
but only try 1 time and post your keys.txt file without the values
Cause it looks like the kezplez puts the entry in again and again if you reuse ...

And looking at the keys.txt some keys may not be copied from your system if you never installed a title aka demo or game...

Still working on this but backup your keys.txt then remove from sd card root.
and also the keys.txt in kezplez-nx folder

Then post to me

hi again i hecked i have all the files on my sd still when count down reach 4 i receives an error how ever i realized some thing u asked me to delete keys.text from keplez folder when i wanted to do that i realized there is nothing in keys.text technically its just blank page i was wonder is this normal ????

 

[Canna]

hi again i hecked i have all the files on my sd still when count down reach 4 i receives an error how ever i realized some thing u asked me to delete keys.text from keplez folder when i wanted to do that i realized there is nothing in keys.text technically its just blank page i was wonder is this normal ????

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


hi again i hecked i have all the files on my sd still when count down reach 4 i receives an error how ever i realized some thing u asked me to delete keys.text from keplez folder when i wanted to do that i realized there is nothing in keys.text technically its just blank page i was wonder is this normal ????

Because it looking for a file your missing and it cant take the keys cause files not there ...

Yes make sure you dump all the console info use the payload i included ipl.bin

In the IPL.BIN Bootloader

Goto Console Info

• Console Info -> Print fuse info -> Press power button Dump These Again
• Console Info -> Print kfuse info -> Press power button Dump These Again
• Console Info -> Print TSEC keys -> Press power button Dump These Again

Then Goto tools in bootloader menu

• Tools -> Backup -> Backup eMMC BOOT0/1 Dump These Again
• Tools -> Dump package1/2 Dump These Again

In green are the most important parts and files for kezplez
In red is what you must do

Male sure to use only the ipl.bin attached
and the sd files i attached

Try again Double check your files..

If You fail again post the contents of your folders or list them so i may see

 

[DeathGrind]

Right so i think those guys having key errors from 17-19 Should not worry so much
The same guys or girls that are on lower system version..
These keys.txt file is only for decryption of titles games etc

Im thinking that the errors are cause by
some of you not having games or demos installed.
and some of you on lower system updates and not 5.1.0

So from what it looks like
Certain systems have certain available keys to be dumped.

That may explain my error. I am on firmware 1.00, and have never installed any game or demo, the only thing i have played is zelda from the cart. Console has also never been online.

I've never had the keys.txt file populate on root of the sd card, alway found it in the kezplez folder .

I appreciate the help in trying to get this sorted. Is there anything you wanted me to try and post the results of?

Thanks

 

[Draxzelex]

How did they manage to restore the nand again after soft bricking the unit? So assuming that the nand backup wasn't working only because they tried using the default Windows 10 file explorer to transfer the file over and it didn't work but using total commander did?

Sent from my MI MAX using Tapatalk

Like I said, it was just a "soft brick" meaning the console won't load anymore but RCM still works. This is why bricks aren't that big of a deal with the Switch because as long as we have access to RCM, we can fix most bricks. The only ones we would be unable to recover from would be those that fry the Switch's battery (such as through third party docks). And with RCM, we can send a payload that will allow us to restore the NAND and fix whatever brick we are experiencing.

 

[Canna]

That may explain my error. I am on firmware 1.00, and have never installed any game or demo, the only thing i have played is zelda from the cart. Console has also never been online.

I've never had the keys.txt file populate on root of the sd card, alway found it in the kezplez folder .

I appreciate the help in trying to get this sorted. Is there anything you wanted me to try and post the results of?

Thanks

at this time im sure that its because it doesnt have the required information to output a correct keys.txt..
whilst @Draxzelex is here he maybe able to shed some light on it as hes got more knowledge then i do

 

[Draxzelex]

All I can think of is that firmware 1.0 has the least keys out of all of the firmwares so maybe its causing some sort of issue? Like, it only has access to masterkey revision 0. All of the other masterkeys can be found in higher firmwares.