Question Blue-screen after restoring nand.

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by igorakou, Apr 14, 2019.

  1. igorakou
    OP

    igorakou Member

    Newcomer
    1
    Apr 14, 2019
    Portugal
    Portugal
    For some reason I was able to boot it this time using RaiNX, but I can't really boot it without it, the screen just stay black, is there any way too just use the OFW? I also noticed that I can't get into Maintenance Mode (Power + Vol Up + Vol Down)
     
    Last edited by igorakou, Apr 15, 2019
  2. igorakou
    OP

    igorakou Member

    Newcomer
    1
    Apr 14, 2019
    Portugal
    Portugal
    I somehow did it, tryed using briccmii and see if it did anything, I thought it didn't but then I accidantly used ReiNX without my microSD card and it still booted but it had no Homebrew Menu, and after updating the console it can just boot normally, it does say now that I'm banned, I was banned before I got the blue screen, but I could still update right now to 7.0.1, maybe it got re-banned or something.
    I might try restoring my nand again just to test things.

    Thanks for the help.
     
    Last edited by igorakou, Apr 15, 2019
  3. Draxzelex

    Draxzelex GBAtemp Guru

    Member
    18
    Aug 6, 2017
    United States
    New York City
    The vast majority of bans do not prevent system updates. Only CDN bans stop you from updating your firmware online which have now ceased from being distributed on account of CDN downloading being dead.
     
  4. igorakou
    OP

    igorakou Member

    Newcomer
    1
    Apr 14, 2019
    Portugal
    Portugal
    Sorry but what do you mean by CDN?
     
  5. Draxzelex

    Draxzelex GBAtemp Guru

    Member
    18
    Aug 6, 2017
    United States
    New York City
    CDN stands for Content Distribution Network. Think of it as the place where Nintendo stores stuff for people to download. As a countermeasure to Freeshop running rampant on the 3DS, Nintendo only allowed any downloads from their Switch CDN if you had an unbanned Switch certificate (the certificate being the item that enables online functionality for the console). Tools were made to download from Nintendo's Switch CDN provided you had a certificate. Nintendo didn't like this. They banned any certificates that were abusing CDN downloading. However this wasn't sufficient to prevent them from downloading through the CDN on account of another server that could be used to download from Nintendo's Switch CDN. So as what we can now call a temporary countermeasure, they upgraded all bans to CDN bans.

    If you're curious why I call it a temporary countermeasure, that is because Nintendo recently started enforcing certificates to have edge tokens in order to download from the CDN. There is no public way to generate edge tokens but there are in private. The reason it is being kept in private is because if it is leaked to the public, Nintendo will step up their CDN security again harming the people who download from the CDN for the good of the scene.
     
    damiano2712, Philliyxx and igorakou like this.
  6. igorakou
    OP

    igorakou Member

    Newcomer
    1
    Apr 14, 2019
    Portugal
    Portugal
    Sounds interesting, I'm curious to see how all of this develops.
     
    Draxzelex likes this.
  7. Philliyxx

    Philliyxx GBAtemp Regular

    Member
    3
    Sep 21, 2018
    United States
    Glad it worked. FYI can't get into maintenance mode with RCM enabled. Unless you boot stock through hekate and then trigger the button combination.
     
  8. fredinator

    fredinator Member

    Newcomer
    1
    Apr 22, 2019
    Germany
    Hi. It seems I did the same mistake but I'm really new to this and don't understand half the things you guys are talking about. Can someone give me an easy explanation what I need to do?
    I made a rawnand backup of fw 6.2.0 but not of boot0/1
    Failed update to 7.0.1 with choidojour
    I panicked and restored nand and then got blue screen.
    I can still access rcm and hekate via argon
     
  9. Draxzelex

    Draxzelex GBAtemp Guru

    Member
    18
    Aug 6, 2017
    United States
    New York City
    You didn't do a complete backup of your NAND. You needed to dump boot0/boot1 along with your NAND because boot0/boot1 are firmware-specific. Because you restored a NAND dump of firmware 6.2, you are getting a blue screen because your boot0/boot1 are still on firmware 7.1. Unfortunately, you cannot create boot0/boot1 files of firmware 6.2 so you will have to downgrade again to firmware 6.1 or lower with ChoiDujour.
     
  10. Philliyxx

    Philliyxx GBAtemp Regular

    Member
    3
    Sep 21, 2018
    United States
  11. fredinator

    fredinator Member

    Newcomer
    1
    Apr 22, 2019
    Germany
    I found this thread as well but I cant get that modded hekate to run since I don't understand how. Also is that the safer way? Or would updating to 7.0,1 easoer?
    As far as I understand I get 2 options:
    1. update to 7.0.1 with external software like choidojour via pc
    2. restore boot with the files from that thread and later update to 7.0.1 in another way ... maybe a game that brings it with it
    Is this right?
     
  12. Draxzelex

    Draxzelex GBAtemp Guru

    Member
    18
    Aug 6, 2017
    United States
    New York City
    ChoiDujour doesn't support any firmware above 6.1. If you were to use ChoiDujour, you would have to downgrade to a firmware of 6.1 or lower. I think mattytrog's method would be safer but if you don't know how to boot the modded Hekate, you might be better off using ChoiDujour.
     
  13. fredinator

    fredinator Member

    Newcomer
    1
    Apr 22, 2019
    Germany
    How did you restore the boot files then?
     
  14. Draxzelex

    Draxzelex GBAtemp Guru

    Member
    18
    Aug 6, 2017
    United States
    New York City
    Your actual 2 options are:
    1. Restore the 6.2 boot0/boot1 that mattytrog made so you have a boot0/boot1 that matches your current firmware
    2. Downgrade to 6.1 with ChoiDujour
     
  15. fredinator

    fredinator Member

    Newcomer
    1
    Apr 22, 2019
    Germany
    Ok so my current FW should be 6.2.0 because I restored the rawnand from before the failed update. That means I only need to restore the boot files from mattytrog somehow, right? But how if I cant run the hekate he provided? I added the .bin-file to argon and it shows up in rcm but I cant run it. Normal hekate works but that does not allow me to restore the files he provided because of missmatching file sizes. Is there another way?
     
  16. Philliyxx

    Philliyxx GBAtemp Regular

    Member
    3
    Sep 21, 2018
    United States
    Can you use tegragui to push the modified hekate.bin(switch boot)? I think this would be easisest way to fix your boot problems rather than do the whole manual downgrade process
     
    Last edited by Philliyxx, Apr 22, 2019
  17. igorakou
    OP

    igorakou Member

    Newcomer
    1
    Apr 14, 2019
    Portugal
    Portugal
    If the sizes don't match you'll need to use Etcher, the normal size is usually 4mb I think, use this guide and do step 6 and 7 to restore the boot0/1, all the files you need are at the top of the guide and step 4 tells you how to use memeloader (except for 4.5) https://guide.sdsetup.com/usingcfw/manualchoiupgrade check if the sizes of the boot0/1 you got from that other post are the same as the ones showen in the guide first though.
     
    Last edited by igorakou, Apr 23, 2019
  18. fredinator

    fredinator Member

    Newcomer
    1
    Apr 22, 2019
    Germany
    I need a USB 3C cable for this right? I ordered one but it has not arrived yet.

    Will I loose my keyblob (whatever that is) with this method?
     
  19. masterzero

    masterzero GBAtemp Advanced Fan

    Member
    3
    Apr 20, 2007
  20. Philliyxx

    Philliyxx GBAtemp Regular

    Member
    3
    Sep 21, 2018
    United States
    Yes you need a USB cable that can plug into your computer on one end and your switch (c) on the other

    You will only lose keyblobs if you restore the boot files in the blob killer folder that are 4mb each, don't restore those use the ones on the root of the folder
     
Loading...