Tutorial  Updated

Switch Unbricking Guide - ProdInfo Fix (PikaFix)

This is an advanced tutorial.Follow this guide at your own risk. I am not responsible if you mess up your switch even more. This Tutorial has only been tested on a RCM Switch. This has not been tested on switch lite, oled or redbox mariko units with chips

The idea of this tutorial is to fix PikaBrick ergo PikaFix, however it can be used for any broken Prodinfo bricks.
This fix *** WILL NOT*** allow you to go online.
The provided files have already had Incognito pre-applied to them.
**METHOD 1 IS THE EASIEST**
Methods 2 and 3 will wipe your previous user partition.
Methods 2 and 3 are now deprecated



Requirements

To follow this tutorial you will need a few things:
ALL METHODS

Your bricked consoles biskeys - Obtain with lockpick_rcm
Your bricked RMC vulnerable switch
A computer/laptop
HacDiskMount or NXNandManager
Hekate Nyx
Atmosphere

Method 1
Prodinfo_Gen
Donor Prodinfo File (or use your own donor)

Methods 2 and 3 - DEPRECATED
PikaFix Pack from xbins or the mirror links (Mirror 1, Mirror 2, Mirror 3)
xbins file location - /SWITCH/PC based software/Utilities/pikabricker repair pack
My custom exosphere.bin file
NXNandManager (Method 2)
Etcher
TegraExplorer

This tutorial has three methods. Method 1 is recommended as Methods 2 and 3 are no longer updated.
Please follow your preferred method and following the appropriate booting section of the guide. I have written this guide as I was following the provided steps.

Before You Start


A few things before you start
  • Make a rawnand and boot0/1 backup, just in case, please? It's how you got into this mess in the first place.
  • Please read the guide carefully and if you have any questions ask them in the thread...

Repair Method 1DEPRECATED


  1. Repair Method 1: ProdInfo_Gen + HacDiskMount OR NXNANDMANAGER

    • Place the donor_prodinfo.bin on your microSD card in the switch folder (SD:/switch/donor_prodinfo.bin)
    • Put your switch in RCM
    • Inject prodinfo_gen.bin
    • Choose 'Build PRODINFO file from donor
    • Reboot to RCM
    • Inject the latest hekate (make sure you have all the hekate files on your microSD card)
    • Press Tools
    • Press USB Tools
    • Press SD Card
    • On your pc copy "generated_prodinfo_from_donor.bin" in the switch folder your desktop
    • Eject your microSD Card
    • Turn 'Read Only' to off
    • Press eMMC RAW GPP
    • On your PC open your Nand Manager of choice, either HacDiskMount or NXNandManager, I'll be using the latter
    • Configure your keys from the prod.keys you got from your bricked console
    • Open physical drive and choose your switch's emmc
    • Highlight prodinfo
    • press restore
    • choose the bin you copied to your dekstop
    • resave your keyset
    • Close
    • boot atmosphere

  2. Method 2Method 3


    1. Nand Repair Method 2: NXNandManger + HacDiskMount


      • Extract the contents of the PikaFix Pack archive to your desktop
      • Place the sept folder and hekate bootloader folder and the contents of the "to sd" folder in the PikaFix archive onto the root of your microSD card
      • Inject lockpick_rcm and run it to generate your prod.keys file
      • Place your switch into RCM and inject the hekate bin file
      • Navigate to Tools > USB Tools
      • Select "SD Card"
      • Open your mounted SD card and copy your prod.keys files from your sd card to your desktop
      • Eject your microsd card in windows
      • select "eMMC RAW GPP" (sysNand) - Set read only to off
      • Open NXNand Manager
      • Press Ctrl+D or press File > Open Drive
      • Choose your nand
      • Press Ctrl+K or Click Options > Configure Keyset
      • Choose your prod.keys you copied to your desktop
      • Press Save
      • You will notice it will say Bad Crypto and Keyset Needed, this is normal.
      1. Click Prodinfo then click the following Icon View attachment 235857
      2. Choose Prodinfo.bin from the files you extracted
      3. Press yes on the restore prompt
      4. Close the transfer box
      • Repeat Steps 1 - 4 for the ProdInfoF, Safe and System Partitions
      • Do the same restore process for the BPKG2 partitions
      • Close NXNandManager
      • Run HacDiskMount as an Administrator
      • Open your mounted drive
      • Double click on system, install the driver and mount the partition to a drive letter
      • Navigate to the save folder and delete everything EXCEPT 8000000000000120
      • Unmount the drive
      • Close HacDiskMount and open Etcher
      • Unmount "eMMC RAW GPP" and Mount "BOOT 0" - you may need to unplug the switch from the usb and replug it to continue
        DO NOT CLICK FORMAT - Just close the popup box(s)
      • Choose the boot0.bin file from the Nand files on your desktop
      • Choose your mounted boot0 drive
      • Flash it
      • Repeat for Boot1
      • Reboot to RCM
      • Launch tegra explorer.bin
      • Navigate to the "_FWGEN" folder and run the systemRestore.te script and follow the on screen prompts
      • Reboot back to RCM and relaunch tegra explorer
      • Navigate back to the "_FWGEN" folder and this time run the systemwipe.te script and follow the on screen instructions
      • Reboot back to rcm
      • Proceed to boot section of guide

    2. Nand Repair Method 3: HacDiskMount


      • Extract the contents of the PikaFix Pack archive to your desktop
      • Place the sept folder and hekate bootloader folder and the contents of the "to sd" folder in the PikaFix archive onto the root of your microSD card
      • Inject lockpick_rcm and run it to generate your prod.keys file
      • Place your switch into RCM and inject the hekate bin file
      • Navigate to Tools > USB Tools
      • Select "SD Card"
      • Open your mounted SD card and copy your prod.keys files from your sd card to your desktop
      • Eject your microsd card in windows
      • select "eMMC RAW GPP" (sysNand) - Set read only to off
      • Run HacDiskMount as an Administrator
      • Open your eMMC from physical drives
      • Open your prod.keys
      1. Double click Prodinfo
      2. Enter your biskeys
      3. Test them
      4. Save them
      5. Restore Prodinfo from the Prodinfo.bin file in Nand files on your desktop from the PikaFix files you extracted
      • Repeat steps 1-5 for ProdInfoF, Safe, and System Partitions
      • Double click on each of the BCPKG2 files and restore them from the provided files
      • Double click on system, install the driver and mount the partition to a drive letter
      • Navigate to the save folder and delete everything EXCEPT 8000000000000120
      • Unmount the drive
      • Close HacDiskMount and open Etcher
      • Unmount "eMMC RAW GPP" and Mount "BOOT 0" - you may need to unplug the switch from the usb and replug it to continue
        DO NOT CLICK FORMAT - Just close the popup box(s)
      • Choose the boot0.bin file from the Nand files on your desktop
      • Choose your mounted boot0 drive
      • Flash it
      • Repeat for Boot1
      • Reboot to RCM
      • Launch tegra explorer.bin
      • Navigate to the "_FWGEN" folder and run the systemRestore.te script and follow the on screen prompts
      • Reboot back to RCM and relaunch tegra explorer
      • Navigate back to the "_FWGEN" folder and this time run the systemwipe.te script and follow the on screen instructions
      • Reboot back to rcm
      • Proceed to boot section of guide



Booting Method 1

Download latest atmosphere and launch fusee.bin

Booting method 2 and 3


    • Remount the microSD Card with hekate
    • Copy my modified exosphere.bin to your atmosphere folder on your microSD card
    • For launching with Hekate add the following line to your hekate_ipl.ini
    'secmon=atmosphere/exosphere.bin'​

    [config]​
    autoboot=0​
    autoboot_list=0​
    bootwait=3​
    verification=2​
    backlight=100​
    autohosoff=1​
    autonogc=1​
    {-- Custom Firmwares --}​
    [HekAtmosphere]​
    fss0=atmosphere/package3​
    kip1patch=nosigchk​
    atmosphere=1​
    secmon=atmosphere/exosphere.bin​

    • For launching with Fusee-primary add the following lines to atmosphere/config/BCT.ini (UPDATE FOR NEW RELEASE)

      [stage2]
      exosphere = atmosphere/exosphere.bin
    BCT0​
    [stage1]​
    stage2_path = atmosphere/fusee-secondary.bin​
    stage2_mtc_path = atmosphere/fusee-mtc.bin​
    stage2_addr = 0xF0000000​
    stage2_entrypoint = 0xF0000000​
    [stage2]​
    exosphere = atmosphere/exosphere.bin​


  • Unmount your microSD card, and proceed to launch with your now working switch
Credits
SciresM and the ReSwitched team for Atmosphere
PabloZaiden for their deviceid exosphere builder
Rajkosto for HacDiskMount
Eliboa for NXNandManager
SuchMemeManySkill for eMMC Hacc Gen and TegraExplorer
CTCaer for Hekate
Shchmue for Lockpick_RCM
ScandalUK for Incognito_RCM
Anyone else who helped out on these projects
Linuxares for help with Method 2

Finally I would like to have a massive thanks to
Anonymous who donated their nand to me for experimenting with and saying it can be used publicly for this fix
 
Last edited by Adran_Marit,

kickmeh

Well-Known Member
Newcomer
Joined
Jun 16, 2020
Messages
53
Trophies
0
Age
34
XP
302
Country
Switzerland
Yup that figures, I'll be interested in the history of console 2 to see what's causing that lol
incognito put on sysnand/emmc, then prodinfo.bin/prodinfo.dat gone, then idk, what my friend do to those console, so error code appears like that, lol
lucky is not mine
 

linuxares

The inadequate, autocratic beast!
Global Moderator
Joined
Aug 5, 2007
Messages
13,151
Trophies
2
XP
17,884
Country
Sweden

Adran_Marit

Walküre's Hacker
OP
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,538
Country
Australia
by any chance a G drive / 1fichier / mega link. I am getting 275 kb/s, gonna take 3 hours

There's an anonfiles mirror up as linuxares Siad, I'm working on a 1f mirror but am busy af this week


incognito put on sysnand/emmc, then prodinfo.bin/prodinfo.dat gone, then idk, what my friend do to those console, so error code appears like that, lol
lucky is not mine

Did you generate the prodkeys again with lockpick and test and so they have an older backup?
 

de9ed

Well-Known Member
Member
Joined
Oct 22, 2020
Messages
278
Trophies
0
Age
30
XP
919
Country
Canada
Sorry, I forgot to say I was downloading from anonfiles. I'm reuploading to google drive now.

Thanks for the guide

Gdrive 1fichier

There's an anonfiles mirror up as linuxares Siad, I'm working on a 1f mirror but am busy af this week




Did you generate the prodkeys again with lockpick and test and so they have an older backup?
 
Last edited by de9ed,

Adran_Marit

Walküre's Hacker
OP
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,538
Country
Australia
Does pikabrick do more than corrupting the prodinfo?

AFAIK it only corrupted prodinfo, however, at the time we had no way of repair this until recently unless you had a prior backup. The wiping of user partitions and the main firmware partitions will be tested and the guide refined in the coming weeks.
 

iCRON

Well-Known Member
Newcomer
Joined
Mar 6, 2018
Messages
95
Trophies
0
XP
1,173
Country
Germany
Hi Guys. I have a bigger problem. It has become completely strange. My bricked switch gives 3 different error messages. In Hekate at CFW he gives a PKG2 error, in Atmosphere a key derivation error and in Hekate StockFW a PKG1 error. I am now wondering which of the errors is the right one that is causing the brick. Have one of you can confirm that‘s this method have fix this errors because i have tryed two other methods there didn‘t works
 

Adran_Marit

Walküre's Hacker
OP
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,538
Country
Australia
Hi Guys. I have a bigger problem. It has become completely strange. My bricked switch gives 3 different error messages. In Hekate at CFW he gives a PKG2 error, in Atmosphere a key derivation error and in Hekate StockFW a PKG1 error. I am now wondering which of the errors is the right one that is causing the brick. Have one of you can confirm that‘s this method have fix this errors because i have tryed two other methods there didn‘t works

That sounds like either your cfw isn't updated or a file wasn't copied properly.

If you do want to try this method make a current rawnand + boot0/1 backup as well as your consoles biskeys, and then proceed with this guide. I can't say for sure if it will fix it but there is a good chance it may.
 

dytri

Active Member
Newcomer
Joined
Apr 24, 2020
Messages
38
Trophies
0
Age
40
XP
101
Country
United States
Really was hoping this guide would work for me but sadly nope...
Im still stuck on the Nintendo logo no matter if I boot in stock or CFW.

I tried following the guide step by step... and I STILL get stuck on the Nintendo logo... even worst...
The screen goes black the moment it shows the logo when I boot up Stock :(
4 years with this switch. GONE. Cant find any solution to fix this.
 

Adran_Marit

Walküre's Hacker
OP
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,538
Country
Australia
Really was hoping this guide would work for me but sadly nope...
Im still stuck on the Nintendo logo no matter if I boot in stock or CFW.

I tried following the guide step by step... and I STILL get stuck on the Nintendo logo... even worst...
The screen goes black the moment it shows the logo when I boot up Stock :(
4 years with this switch. GONE. Cant find any solution to fix this.

Did you have any form of backup including your own keys? I feel like something wasn't quite adding up when trying to boot it wasn't reading the custom exosphere...

I'm more than happy to try and assist you via discord inbetween work and other things - adran#5747
 

dytri

Active Member
Newcomer
Joined
Apr 24, 2020
Messages
38
Trophies
0
Age
40
XP
101
Country
United States
Did you have any form of backup including your own keys? I feel like something wasn't quite adding up when trying to boot it wasn't reading the custom exosphere...

I'm more than happy to try and assist you via discord inbetween work and other things - adran#5747

Only back up I did prior to the guide, was a Boot0/1 and rawnand.
Although I dont know how much help it would have been to back up since I mistakenly hit the update button by mistake and ruin my CFW. (forgot to do a nand/boot backup before ever homebrewing my switch)
Been trying to fix it ever since, for awhile now... every time I booted in Stock or CFW. My screen would display an error message right before showing a black screen. Turned out..
My emmc was fuck, so by using gptrestore. I restored the original Switch GPT to my eMMC.
Manage to get my switch to boot up around the Nintendo logo now, but that's about it...
Found out a few days ago my prodinfo was ruin (Im not sure if was because I was using HacDiskMount, when trying to downgrade but I dont remember ever touching my prodinfo)
So I've been trying to find a solution to fix it, or at least do a full clean wipe on my switch so I can boot up the damn thing.
Follow the guide exactly how you presented yesterday, but I get the same results.
Probably even worst now... since it doesnt even get stuck on the Nintendo logo screen anymore.
Just a quick glimpse of the logo right before the screen go total dark.

Any help would be appreciated, but at this point... I dont have any hope anymore.
 

Adran_Marit

Walküre's Hacker
OP
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,538
Country
Australia
Only back up I did prior to the guide, was a Boot0/1 and rawnand.
Although I dont know how much help it would have been to back up since I mistakenly hit the update button by mistake and ruin my CFW. (forgot to do a nand/boot backup before ever homebrewing my switch)
Been trying to fix it ever since, for awhile now... every time I booted in Stock or CFW. My screen would display an error message right before showing a black screen. Turned out..
My emmc was fuck, so by using gptrestore. I restored the original Switch GPT to my eMMC.
Manage to get my switch to boot up around the Nintendo logo now, but that's about it...
Found out a few days ago my prodinfo was ruin (Im not sure if was because I was using HacDiskMount, when trying to downgrade but I dont remember ever touching my prodinfo)
So I've been trying to find a solution to fix it, or at least do a full clean wipe on my switch so I can boot up the damn thing.
Follow the guide exactly how you presented yesterday, but I get the same results.
Probably even worst now... since it doesnt even get stuck on the Nintendo logo screen anymore.
Just a quick glimpse of the logo right before the screen go total dark.

Any help would be appreciated, but at this point... I dont have any hope anymore.
Did you try restoring anyone else nand backup at some point?

What format is your sd card?

Did your biskeys match your nand?

As I said message me on discord it's going to be a quicker reply
 

guyman70718

Well-Known Member
Member
Joined
May 31, 2017
Messages
168
Trophies
0
Age
24
XP
505
Country
United States
Hey, just curious, why do you need a custom exosphere.bin? The way I rebuilt my nand I am able to use normal unmodified OS and normal Atmosphere just fine.

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

Is this tutorial suitable for repairing my lite

I have only tried and tested on a RCM vunerable unit. If your lite is modded with the chip and you can get the console keys and launch Hekate it may work but I take no responsibility of it doesn't and breaks your console more.

someone I know tried to fix a patched switch with a sx core, but the sx core doesn't allow for tsec keys to be dumped so it wasn't possible to get it working.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: My phone has 13% battery