Question Can ReiNX toolkit restore an old NAND backup made with hekate 3.2?

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by Bitsoft, Oct 1, 2018.

  1. Bitsoft
    OP

    Bitsoft Member

    Newcomer
    4
    Apr 24, 2011
    United States
    title
     
  2. thaikhoa

    thaikhoa GBAtemp Advanced Maniac

    Member
    8
    Sep 16, 2008
    AFAIK Reinx toolkit doesn't have any ability to restore nand backup.
     
    Bitsoft likes this.
  3. Adran_Marit

    Adran_Marit Walküre's Hacker

    Member
    8
    Oct 3, 2015
    Australia
    42*South
    No, the toolkit only creates a dump. You still need to use Hekate to restore. A dump made with the toolkit can be restored with Hekate though
     
    Bitsoft likes this.
  4. viejopirulo

    viejopirulo Member

    Newcomer
    1
    Nov 12, 2018
    Chile
    Chile
    How can I do this? I made a NAND backup and it made a bunch of .bin files, of 2 or 3GB size I can't remember since I'm not in my laptop right now.
     
  5. Adran_Marit

    Adran_Marit Walküre's Hacker

    Member
    8
    Oct 3, 2015
    Australia
    42*South
    you need to join the small files with the joiner script, then restore with hekate, sorry I'm not at home so I can't link the script
     
  6. viejopirulo

    viejopirulo Member

    Newcomer
    1
    Nov 12, 2018
    Chile
    Chile
    Alright thanks!! On a side note, I did make the backup after getting the console, connecting it to internet and updating to the last firmware. Then I started launching CFW. Does that mean I I have more risk of getting banned if I connect the console to wifi again?
     
  7. mdmachine

    mdmachine GBAtemp Regular

    Member
    3
    Jun 15, 2009
    United States
    If after the update, you opened OFW even once, the fuses are burnt. So you'd have to inject a payload to even use it, and you'll get banned.
     
  8. viejopirulo

    viejopirulo Member

    Newcomer
    1
    Nov 12, 2018
    Chile
    Chile
    Yeah, I even downloaded some demos and free games. Then I started looking up for hack stuff, THEN I made the NAND backup, and THEN I launched CFW. Still, I haven't connected my console to internet since before I made the backup (deleted all wifi networks and switched to airplane, then backed up). Always airplane mode. Btw, how do I check my burnt fuses? In what cases are burnt fuses risky? (sorry all these questions, I'm new to this).
     
    Last edited by viejopirulo, Nov 13, 2018
  9. mdmachine

    mdmachine GBAtemp Regular

    Member
    3
    Jun 15, 2009
    United States
    OK, well it sounds like you updated then made a NAND backup. So your at whatever FW your at. I would advise using autoRCM now, if you aren't. This is a good habit, and will prevent any burnt fuses in the future.

    So since you disabled all internet since the backup, in theory you "should" be ok upon a restore of the NAND.

    About the fuses, if you want to check them, I believe Hakate payload has fuse-checking as well as the briccmii payload.

    Here is a quote from another thread as its put rather well, in regards to fuses and updating, I edited some parts about the guide it was referring to and put any changes in italic...

     
    viejopirulo likes this.
  10. viejopirulo

    viejopirulo Member

    Newcomer
    1
    Nov 12, 2018
    Chile
    Chile
    Regarding the NAND backup: yes, that's exactly what I did. Thanks for the clear answer!

    I'm afraid since I started using CFW there has been a couple times that I accidentally booted on OFW (due to not inserting the JIG or the SD), which means my fuses are burnt... right? I will run a check when I'm home anyway.

    Sorry for the repeated question but... what exactly is the risk of burning my fuses? I think I don't completely get it :(

    Thanks again for your answers and time!
     
  11. palantine

    palantine GBAtemp Regular

    Member
    4
    Oct 5, 2014
    Italy
    Burning fuses prevents running lower firmwares. The hacks can get around this but it requires rcm. A console that has all fuses burned would not be able to run a lower firmware again without using the rcm hack.
     
  12. mdmachine

    mdmachine GBAtemp Regular

    Member
    3
    Jun 15, 2009
    United States
    OK the point of the fuses is to tell what version of firmware you are on. After they burn you cannot go back.

    For example:
    I officially updated to FW version 3.0.0, it will have 3 fuses burnt.
    Then I officially update to FW version 6.1.0, it will have 7 fuses burnt.

    If I attempt to restore back to 3.0.0 and try to boot my switch normally I will get a black screen since I have 7 fuses burnt, and it was looking for 3. So the "risk" is later on I cannot go back to my older firmware (without using a payload to circumvent the fuse check, which defeats the goal of having "virgin" backup).

    Now in your instance you updated, booted into OFW (which burnt the fuses), then made a backup and started using CFW. So your fuses are burnt in accordance to whatever FW you are on.

    It is, however, never too late to read up about AutoRCM and doing any future updates using ChoiDujourNX which is a tool for applying updates safely and keeping AutoRCM enabled.
     
  13. viejopirulo

    viejopirulo Member

    Newcomer
    1
    Nov 12, 2018
    Chile
    Chile
    Can't thank you enough, I got it crystal clear this time! I don't plan on going back to previous firmware so I think I'm good (I'm currently on 6.1.0).

    I will go on and look up for AutoRCM stuff after I verify if my NAND backup is good to restore in case I mess up (asked on a different thread and I think it's possible). Getting the jig on every time I turn on the console after copying files into the SD is slowly turning into a pain in my back lmao.
     
Loading...