An EASY(but a bit more risky) way to update Switch Firmware WITHOUT burning any fuses

Discussion in 'Switch - Tutorials' started by quantumboy, Jul 18, 2018.

  1. Rune

    Rune GBAtemp Advanced Fan

    Member
    7
    Feb 15, 2017
    I'm about to try this now, going from a low OFW to 5.1.0. But I don't have the exFAT driver update, so I'm not entirely sure how I'm going to do this.

    I know I need to have a exFAT card in the device to trigger the prompt for the driver update, which tells me to go online for the update. Will this then do the firmware update first and then the driver update? Or vice versa? Or is it all packaged together in a single update?
    How will I do this without risking burning the fuses?
     
  2. Maiken

    Maiken Member

    Newcomer
    6
    Dec 27, 2008
    Netherlands
    The Netherlands

    I updated yesterday from 4.1.0. to 5.1.0. with this method. Just inserting the exFAT formattd card worked. It updated the console and applied the exFAT update.
     
  3. Rune

    Rune GBAtemp Advanced Fan

    Member
    7
    Feb 15, 2017
    Did it do it in one update? or was it a couple of separate updates with two reboots of the device?
     
  4. Maiken

    Maiken Member

    Newcomer
    6
    Dec 27, 2008
    Netherlands
    The Netherlands
    It was just 1 update. After installing, I made sure to reboot into RCM and install auto RCM. Checked Hekate afterwards and the fuses weren’t burned.
     
    Rune likes this.
  5. nickolaslr

    nickolaslr Newbie

    Newcomer
    1
    Mar 6, 2010
    Brazil
    Thanks for the tutorial. Unfortunately it didn't work for me. I followed all the steps but also:
    1- removed the auto rcm before entering the OFW to update,
    2- don't have the SX dongle (using pc to inject the payload).
    I did hold the volume + when the completed message appeared and my jig was working, but it booted in the ofw. Checked and now I have 6 burnt fuses. No problem at all, as long I can play games.
     
  6. LH1980

    LH1980 Member

    Newcomer
    4
    Apr 28, 2016
    Canada
    The long guide mentioned cart slot not working after update. What about this guide, any issues with cart slot?
     
  7. Kryptide

    Kryptide Newbie

    Newcomer
    1
    Jul 7, 2018
    United States
    I did this successfully about an hour ago. I have tested all my game carts and they still work without issues.
    Wanted to say thank you for this tutorial as I've been wanting to play some newer games without completely destroying the little hope of cold boot someday :)
     
  8. AlexMCS

    AlexMCS Advanced Member

    Newcomer
    5
    Jul 3, 2018
    Brazil
    They won't work only if you boot without a nogc kip and only after you downgrade back to a fw under 4.0.
     
  9. efxonly123

    efxonly123 Advanced Member

    Newcomer
    3
    Jul 13, 2018
    United States
    I think you were supposed to hold the volume + button prior to the completed message.
     
  10. annson24

    annson24 The Patient One

    Member
    7
    May 5, 2016
    Philippines
    I've updated from 3.0.2 to 5.1.0 using this method and checking via hekate, it says that I've 4 fuses burnt, so does that mean I can still downgrade back to 3.0.2, right? I've a full backup of my 3.0.2 nand.
     
  11. Draxzelex

    Draxzelex GBAtemp Legend

    Member
    18
    Aug 6, 2017
    United States
    New York City
    http://switchbrew.org/index.php?title=Fuses indicates 3.0.2 has 4 burnt fuses so you are correct. You can also make another backup of your 5.1 NAND in case you want to easily return to 5.1 without going through the whole update process.
     
    annson24 likes this.
  12. Myron49485

    Myron49485 Advanced Member

    Newcomer
    3
    Aug 23, 2015
    Singapore
    I have some questions reguarding this process..

    1. How do you boot into official firmware (OFW) with Hekate (CTCaer's mod)?

    The only related options I see in Hekate are "Launch Firmware", which is to launch custom firmware, and "Reboot (Normal)", which actually puts me back into RCM mode since I have autoRCM enabled. I would like to know how to boot into OFW to install future updates.

    2. What exactly happens when I select "Launch Firmware" without providing Hekate with a Hekate_ipl.ini file?

    When I select that option, it tells me that I am missing the ini file (which I am), then proceeds to boot into an OS which I don't know whether is CFW or OFW. Is this potentially dangerous for burning fuses?

    3. Is it safe to boot with the latest ReiNX CWF (ReiNX.bin) after updating without burning fuses?

    4. I'm currently on 4.1.0 and have not done this procedure yet. Let's say that I make a backup of 4.1.0, update to 5.1.0 without burning fuses and enable autRCM, and make a backup of 5.1.0. Then, I decide to restore back to 4.1.0 and do so by restoring the 4.1.0 backup.

    Now, if I want to go back to 5.1.0, is it as simple as restoring the 5.1.0 backup?

    The 5.1.0 backup should contain autoRCM as I would have enabled it before backing up, but would restoring it be safe? (Also, the 4.1.0 file does not contain autoRCM as it is a clean backup, but that shouldn't matter as the fuses match the FW version)

    (I think 4 has been answered in the post above)

    Thanks for reading :)
     
    Last edited by Myron49485, Aug 4, 2018
  13. Sephirosu

    Sephirosu GBAtemp Regular

    Member
    4
    Jan 28, 2015
    Boca Raton, Florida

    As far as I know when you do "launch firmware" it goes into OFW. No idea if that will burn your fuses or not. All I know is that as long as you boot into hekate you won't burn your fuses (according to someone on this thread).
     
  14. Myron49485

    Myron49485 Advanced Member

    Newcomer
    3
    Aug 23, 2015
    Singapore
    I see. I would like to know for sure before proceeding.

    Edit: Sephirosu was right, Hekate will never burn fuses.
     
    Last edited by Myron49485, Sep 27, 2018
  15. shchmue

    shchmue Developer

    pip Developer
    8
    Dec 23, 2013
    United States
    when you select launch firmware it gives you the menu dictated by your ini file. when it fails to find one it boots OFW of course since hekate doesn't technically know anything about any CFWs unless you tell it through the ini
     
  16. ravihpa

    ravihpa GBAtemp Advanced Fan

    Member
    7
    Apr 11, 2007
    India
    Am thinking of using this method to update to 6.1.0 official and linking a Nintendo account. Apparently it's required to check your play times and some games require a linked Nintendo account.

    Maybe Nintendo will make it mandatory for all games in the future to require a linked account. It's better to do it now than later, right?

    Edit: By the way, I haven't even started playing any games on the Switch yet. So am thinking better do it now. Any advice?

    Edit II: Just used this method to update to 6.1.0 without burning efuses, booted into Hekate, enabled AutoRCM, then booted into stock firmware, connected to internet, created and linked a Nintendo account.

    Thanx a lot for this awesome guide. It was of tremendous help. Keep up the amazing work.
     
    Last edited by ravihpa, Nov 7, 2018
  17. yonasz

    yonasz Advanced Member

    Newcomer
    3
    Jul 26, 2015
    Poland
    @ravihpa you booted into stock firmware ?? Does it means OFW ?? I think you cant boot ofw if you dont want burn fuses ??
     
  18. Draxzelex

    Draxzelex GBAtemp Legend

    Member
    18
    Aug 6, 2017
    United States
    New York City
    Non-RCM OFW burns fuses. OFW with RCM will not burn fuses if you use a bootloader that does not burn fuses such as Hekate, ReiNX, Fusee, etc.
     
    yonasz likes this.
  19. ravihpa

    ravihpa GBAtemp Advanced Fan

    Member
    7
    Apr 11, 2007
    India
    Yes booting into stock firmware via Hekate (Launch > More config options > Stock) doesn't burn your efuses. I double checked and can confirm 100% that my efuses aren't burnt. Am still at 5 fuses burnt = 4.1.0
     
    Last edited by ravihpa, Nov 9, 2018
  20. XaneTenshi

    XaneTenshi GBAtemp Fan

    Member
    5
    Nov 24, 2013
    Denmark
    Just used this method to try and prevent my fuses from burning and keeping my FW 4.1.0 compatibility. It did NOT work!!!!

    I did almost exactly as described in the OP. Difference was that I forgot to enable autoRCM when I booted into hekate after the update and proceeded to launch "OFW" (stock, through the config options).

    I realized my mistake immediately, shut down the console, SUCCESSFULLY manually booted into RCM and then enabled AutoRCM in the option. But when I went to check for burnt fuses. it said 7 burned. It should have been 5.

    This shouldn't have happened, since even if I forgot to enable autoRCM, the Switch never got the chance to boot with the official bootloader.

    Yet, here we are. FW 6.1.0. 7 Burned fuses and Sleep mode now ruined on my 5.10 hacked Nand.

    **** this!
     
  21. movietime

    movietime Member

    Newcomer
    3
    Jul 28, 2009
    Canada
    Has anyone tried this method to upgrade to 6.2? If yes please share details at what point you hold the +button to boot into CFW. Also is there any issue doing so? Thx
     
Quick Reply
Draft saved Draft deleted
Loading...