1. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Hi,
    After putting myself in a situation where nothing is working anymore I am desperate for help. I have run sysnand CFW for several years. The goal now was instead to achieve emunand on SDcard and OFW on sysnand. Also hopefully without having to reinstall games or loosing any saves. I want sysnand OFW for being able to play online.

    Setup before begining:
    Unpatched switch.
    exfat formated sd-card
    Firmware 10.1.0
    Atmosphere 0.13.0
    The error message about game cart slot appearing now and then.
    Auto RCM
    Probably some burnt fuses

    So this is how it went down. I hope I remember to write all the crutial steps and the order which i did them in.

    1. I located the necessary rawnand.bin, boot0 and boot1 for making the nand restore. This is a backup I made before going CFW. I dont know what firmware version I was on when I made this backup but I can see that the files are dated december 2017.

    2. I downloaded hekate_ctcaer_5.3.2_Nyx_0.9.3 and put the bootloader folder on the SD card root.

    3. I transferred a copy off all my SD files to my computer.

    4. I started hekate by using hekate_ctcaer_5.3.2.bin.

    5. I used "partition SD Card" in Hekate and created a HOS (FAT32) and emuMMC (RAW).

    6. I created emuMMC SD Partion in Hekate and it says Enabled!.

    7. Copied back all the backuped SD card files to the root off the SD card.

    8. Tried to launch by entering RCM-mode and injecting fusee-primary.bin. It worked and I checked system firmware and saw that I was on E (emunand).

    9. Tried going in to hekate again to launch from there but at first it did not work. Tried a bit and I think what got it working was when I added fusee-primary.bin to the payloads folder in bootloader folder (it was empty before) and also adding code to the hekate.ipl.ini. The code I added was some lines found in a forum thread. One for starting CFW (EMUNAND) and one for Stock (SYSNAND).

    10. Renamed the hekate_ctcaer_5.3.2.bit to reboot_payload.bin and overwrote the file in the atmosphere folder (for being able to reboot to hekate).

    11. Copied the backuped Nintendo-folder to emuMMC\RAW1 and comfirmed that my installed games was working again on emunand.

    12. Now when emunand was working I was convinced it was safe to restore my nand backup. I followed this guide https://suchmememanyskill.github.io/guides/nandrestore/ and did not get into any trouble.

    13. Entered RCM-mode and injected (the same) fusee-primary.bin as before sysnand restore but now nothing happens. The screen is black and TegraRcmGui shows that it is ready to inject again after like 2 seconds.

    14. Trying to inject hekate_ctcaer_5.3.2.bin again and it works.

    15. Trying to launch CFW (emunand) through Hekate exactly as I did before restoring the sysnand. Now it seems to start up, it shows the Atmoshpere logo, it shows the Nintendo Switch logo, it shows the battery status symbol and then for a short moment the sleep screen (the screen where you have to press a button 3 times for it to wake up) but then the Switch goes to black screen and I see that Tegra rcmGUI shows that it is ready to be injected again.

    Usually the error about the game cart slot comes up when the switch starts up so I was thinking that it might have something to do with nogc. But I tried fiddling a bit with the .ini-code turning it off and on but it does not seem to make any difference. The console keeps crashing.

    When trying to boot sysnand trough hekate I get Unknown pkg1 version. Hos version not supported! Failed to launch HOS". But I have not yet looked in to this any further. Step 1 seems to be to get emunand CFW working again.

    So what happend? I can't understand how I could go from from working emunand to not working emunand just by restoring sysnand. Any thoughts and recommendations for further troubleshooting are highly appreciated.

    Please tell me if you need to know the ini-file code or anything else.
     
    Last edited by MatteKalle, Sep 19, 2020
  2. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Okey, so today I tried some more myself but to no success =(.
    What I did was that I removed the bootloader folder from the SD card and instead placed the bootloader folder from the latest Hekate (5.3.3) release.
    I also removed the Atmosphere folder and downloaded and placed the latest official Atmosphere instead + the matching sigpatches.
    Then I placed the new fusee-primary in the bootloader > payloads folder.
    I also tried with a completely new Hekate ini-file. I downloaded and used the file found here -

    So, after I changed everything above I tried starting up using the hekate 5.3.3.bin -file and got to Hekate.
    The following happens when I try to launch...

    Atmosphere CFW - Hekate IPL logo, then black screen and TegraRcmGUI tells me that it is ready to inject again. Nothing more happens.

    Stock SYS - The same error message as before =
    "
    Unknown pkg1 version.
    HOS version not supported!
    Trying to backup bootloader...
    Found pkg1 <´´>.
    Unknown pkg1 version.
    HOS version not supported!
    Failed to launch HOS!
    "

    So again I am out off luck.
    Still hoping for some help =).
     
  3. mesmeriize

    mesmeriize Advanced Member
    Newcomer

    Joined:
    Aug 2, 2020
    Messages:
    80
    Country:
    United States
    Try this.
    Make sure your sd card is formatted in fat32. If not backup all your files, format it using a program then transfer back.

    Delete the atmosphere, bootloader and sept folder and re-download from https://www.sdsetup.com/

    Go to the ini file and delete the other 2 profiles. You just need fusee for emummc and stock.

    Test it. If it's good, you can put the sigpatches in then. If still not good, maybe try deleting the config folder too on the root.

    — Posts automatically merged - Please don't double post! —

    Ignore my last post. I know your problem. Your backup that you restored is on a old firmware and your fuses match a new firmware. I went through same issue before.

    I think what I did was inject the regular hekate.bin not the ctcaer hekate. I think it's in the bootloader folder that you can download from https://www.sdsetup.com/ so inject that. Then I believe I clicked boot ofw or boot sysnand bypass fusee check or something like that which bypasses fuse check then I immediately went to update it officially to the latest.
     
    Last edited by mesmeriize, Sep 16, 2020
    MatteKalle likes this.
  4. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Thank you for trying to help!
    I have gone to the sdsetup-page and downloaded "Recommended defaults" but there are only the hekate_ctcaer_5.3.3.bin in the payloads -folder and fusee-primary.bin in the sd > bootloader > payloads.
    I have googled for hekate.bin but I can't find any sign off it.
     
    Last edited by MatteKalle, Sep 17, 2020
  5. mesmeriize

    mesmeriize Advanced Member
    Newcomer

    Joined:
    Aug 2, 2020
    Messages:
    80
    Country:
    United States
    You need to get an old version of sdfiles. That will contain hekate.bin it might be in old cfw set up guides.

    Another way you should be able to do it is through sx os. Download the boot.dat from their website and put it on your sd card and also download the sx payload both from sx.xecuter.com. Inject that payload then click boot ofw then immediately update the system.

    Edited: you need both boot.dat and the payload from sx website
     
    Last edited by mesmeriize, Sep 18, 2020
  6. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Great, thank you. I will begin to look into the SX OS variant tonight. And do you mean that the new version will work or should I search for something older?
     
  7. mesmeriize

    mesmeriize Advanced Member
    Newcomer

    Joined:
    Aug 2, 2020
    Messages:
    80
    Country:
    United States
    Sx os new version is fine. For the hekate.bin you need to find the old version. Sx should work so try that first
     
  8. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Sorry to say but it did not work. It booted to SX OS menu but when I tried to boot OFW from there it went to black screen immediately.
    I will try to find the hekate-file now and try with that.
     
  9. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Before starting the searching for the hekate.bin I downloaded a partition tool to check how my SD card is partitioned.
    As you may remember I did the partition directly from the tool in hekate.
    I suppose there is nothing wrong with this?
    upload_2020-9-18_23-27-9.png
     
    Last edited by MatteKalle, Sep 18, 2020
  10. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Another update.
    I found SDfile 2.0 in one forum thread and a payload in another one.
    I suppose they matched because I got in to the menu.
    Although when trying to boot stock firmware I get the same package1 error again.
    I googled this for a while and found this answer from CTCaer on another guy with this error message (sep 2018).

    "
    BOOT0/BOOT1 must match the version of rawnand.
    Also because it is showing '' as version, it means that the restored boot0/1 were initially corrupt.

    You sd card or your backup had problems.
    "

    So there we are. I suppose my next step will have to be reformatting the SD card and restoring the boot1 and boot2.
    Or what do you think?
     
  11. mesmeriize

    mesmeriize Advanced Member
    Newcomer

    Joined:
    Aug 2, 2020
    Messages:
    80
    Country:
    United States
    Your sd card looks fine. No need for format. When you were restoring the rawnand. Did you restore the old boot0/ and 1 that came with it because you need it. Maybe that's why you keep getting the error. Try to restore the full rawnand and both boot files and try to boot through sx again
     
  12. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    I did it as told in this guide -https://suchmememanyskill.github.io/guides/nandrestore/ . I first restored my backuped boot1 and boot2 and then the backuped rawnand.bin. I did not get any error message or anything. But I can try to do it again to see if it makes any difference
     
    Last edited by MatteKalle, Sep 19, 2020
  13. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Sorry to say but nothing changed after I tried redoing the restore off boot0 boot1 and rawnand.
    I have tried both SXOS and Hekate with the same result as stated before.

    Do you have any other ideas?
    I don't know if I should try to restore sysnand from emunand to see if I can get back too where I was before.
    Another thought is this - https://switch.homebrew.guide/usingcfw/manualchoiupgrade.html .
    What do you think? Or do you have any other thoughts?

    Again, big thanks for trying to help!
     
  14. mesmeriize

    mesmeriize Advanced Member
    Newcomer

    Joined:
    Aug 2, 2020
    Messages:
    80
    Country:
    United States
    That's weird. Try using that that guide to upgrade the sysnand to 10.1 or 10.2. I don't recommend using your emunand to create sysnand because it's dirty.
     
  15. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    I allready was on a dirty Sysnand before all this so at least I hopefully would be back to where I started with a working switch.
    But I can try to upgrade the Sysnand firmware as told in the guide first.
     
    Last edited by MatteKalle, Sep 20, 2020
  16. Slajmer

    Slajmer Newbie
    Newcomer

    Joined:
    Sep 14, 2020
    Messages:
    3
    Country:
    Sweden
    How can emunand stop working after a nand restore? As far as i know those are not connected?. Wierd.
     
  17. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Beats me. I have not been able to find any posts mentioning this.

    Anyhow. Finally I've had some sort off breakthrough.
    As stated before...
    Now I started up as stated above but when seeing the sleep screen (after the battery symbol) I started spamming the home button. When I did that I got the game cart slot error message and after pressing OK on that I could access my Switch and start up games. Although if I press the power button once the Switch dies again.

    So there seems to be some kind off crash when it tries to go into sleep mode, right?
    Now that I at least now a way to get in I'm thinking off updating to the latest (hackable) firmware to see if that solves the problem.

    I'm still welcoming all suggestions and thoughts about this unique (?) situation that I've gotten myself into =).
     
    Last edited by MatteKalle, Sep 24, 2020
  18. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Updated emunand to 10.2.0 but the same problem remains.
    Would really appreciate some help figuring this out.
    If nobody is able to point me in the right direction I suppose my next step will be to try to repair the boot0 and boot1 and also test to backup and restore everything to another sd card.
     
  19. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Now I also tried another SD card with a copy off the same emummc that is working (except sleep).
    This was the result:

    I backed up my emummc with Hekate (boot-files + rawnand).
    Then I used another SD card and this time made the partitions with tegraexplorer.bin.
    After that I placed the latest atmo and hekate and started with the latest hekate bin-file.
    In Hekate I Created the emuMMC as SD Raw Partition.
    I then restored the boot-files + rawnand to the SD-card.
    When I now try to boot up cfw emummc I get hekate boot logo and then it goes directly in to RCM again.
    After that I copied everything (except emummc folder) from my other SD card.
    Tried again but the same thing happens when trying to go to emuMMC.
    When I put in my other SD card again it is working as before = emuMMC boots but crash at sleep.
     
  20. MatteKalle

    OP MatteKalle Member
    Newcomer

    Joined:
    Nov 9, 2009
    Messages:
    34
    Country:
    Finally got sysnand working by getting live support from a kind person on Discord.
    My backup off boot0 was faulty so that was the problem. When we looked at the file in a hexeditor it only showed zeros.
    He helped me updating my firmware and to repair and restore.
    Sysnand with online working as it should now =).

    Next step will be to get emunand working. Will see if I can achieve that without needing to reinstall my games.
    I'm thinking that I will start by doing a backup off my working boot0, boot1 and rawnand.bin.
    Then I will try to restore only boot0 and boot1 to my emunand to see if that fixes the sleep error in emunand.
    If not I suppose I will have to backup my game saves and create a completely new emunand from my working sysnand.
    Please advice if you have any advice regarding this.
     
Draft saved Draft deleted
Loading...

Hide similar threads Similar threads with keywords - Emunand, Sysnand, stopped