Question [URGENT]Console stuck on Switch logo after trying SX OS

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by Psychoteddy, Dec 4, 2018.

  1. Khar00f

    Khar00f GBAtemp Regular

    Member
    5
    Mar 12, 2006
    Canada
    So after you said No to the update, you restarted the console on your own, is that correct?

    Also check your PM.
     
  2. Psychoteddy
    OP

    Psychoteddy Member

    Newcomer
    1
    Dec 4, 2018
    Afghanistan
    Yes, correct.
     
    Last edited by Psychoteddy, Dec 4, 2018
  3. Khar00f

    Khar00f GBAtemp Regular

    Member
    5
    Mar 12, 2006
    Canada
    .
     
    mikefor20 likes this.
  4. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom
    Try maintenance mode again. Initialize without deleting user information.
     
  5. Psychoteddy
    OP

    Psychoteddy Member

    Newcomer
    1
    Dec 4, 2018
    Afghanistan
    Maintenance mode (volume - and + and hit power) gets it stuck in switch logo.
     
  6. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom
    Any luck> I haven't been able to spend any time on this the last couple days. Damn Adulthood!!
     
  7. Psychoteddy
    OP

    Psychoteddy Member

    Newcomer
    1
    Dec 4, 2018
    Afghanistan
    My friend shipped his console to Nintendo for repair. I hope they'll be nice and do it.

    He got a new console meanwhile, on 4.1.0 too. I am backing up his NAND and boot0/1. I'll also dump the bis keys, then use a fat32 sd card to install 5.1.0 with exFAT support, via ChoiDuJour.

    We want to use the dongle we already have with a new SX OS license, but I'm afraid this might brick it, as the dongle comes with a license...
     
  8. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom
    You'll be fine. Aafter you set activate the new license on the TX site your License file will work fine. IDK why you bricked before. Like I said, there is usually something the user thought was nothing that was actually something. A quick install of some save editor NSP... Maybe a homebrew app that isn't fully understood.by the user Good luck with the new one. If you want help PM me. NAND backup is key.
    I made a SXOS backup and Hekate backup for mine. Upload a copy to the cloud as well.
     
  9. Psychoteddy
    OP

    Psychoteddy Member

    Newcomer
    1
    Dec 4, 2018
    Afghanistan
    Thank you for your help. Much appreciated.
     
    mikefor20 likes this.
  10. josephdin

    josephdin Advanced Member

    Newcomer
    2
    Jun 20, 2018
    United States
    the fact that this is unsolved makes me feel some type of way. Feelsweirdman, Also keeping an eye on this cuz this is some type of stuff i could have gotten myself into, i hacked my switch when sx-pro 2nd batch shipments were received, and I JUST BARELY BACKED UP MY NAND ON THE 13TH WHEN LETS GO WAS LEAKED. Yikes. It was the .nsp's with brick code that finally made me remember to do it. Once again yikes, i should have remembered, also to be fair before that day i only used .xci's so that was the first time i was gonna install a .nsp
     
  11. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom

    I bet this could have been resolved. The amount of effort put forth may have something to do with it. You would have to read and follow instructions. Some of the methods are not straight forward. IF they had a NAND Backup like they were supposed to in the first place it would be no big deal. Also the PC method can write directly to the NAND. More than likely could have fixed it there. I am pretty sure there was more than meets the eye. When people read partial instructions, don't know what they are doing, and make decisions they have no business making, they tend to have these results. Read, backup and don't say yes to anything you don't fully understand. You should be fine. Your late backup may not be safe to go online with. Probably has remnants of the tempering you did since it was made so late. Far from clean.
     
    Last edited by mikefor20, Dec 6, 2018
  12. josephdin

    josephdin Advanced Member

    Newcomer
    2
    Jun 20, 2018
    United States
    yes, i completely get that my backup may not be as clean, but i will tell you that i did try going online to test if i was banned at the time(did not care at this point if i was) and surprisingly i was not banned so even if i am banned in the future (will be cuz .nsps installed) As long as i can restore that backup to make a switch function again is enough for me you know? I can accept that i will be banned soon and if anything i kinda want it to happen already so i can just use FTP app without any worry. Once again my point is i was lucky enough to make A backup instead of having no backup at all. Now you got me thinking though, how would i go about completely wiping everything and then making a clean backup? I would have to wait until some better tool comes out to help assist with that correct? Like deleting tickets and all of that stuff that is usually done via restoring to a clean backup. Cuz this nand backup has no .nsp's installed at all, but then again i did run homebrew

     
  13. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom
    Ninty has records on their server. Who knows what is "safe". I don't know if there will be a way to unban or clean a backup ever.. Time will tell.
     
    josephdin likes this.
  14. Emeraldman94

    Emeraldman94 GBAtemp Fan

    Member
    3
    Dec 22, 2008
    United States
    Im having the same problem!!!

    Help. I HAD a 6.1 sysNAND and 6.1 emuNAND. Never used sysNAND. Only made backup of 4.1 sysNAND before hacks

    the Switch boots up into RCM mode. Then I click emunand or custom firmware. Then the Nintendo screen flashes. Then Black screen. Then Nintendo Switch screen. IT then freezes on this screen and never moves on. I noticed this after I installed a fire emblem game update and DLC from a site I was pretty familiar with. Once I backed out to home screen it froze. Then my switch could never turn on properly.

    I turn off my switch my holding the power for 15 seconds. Charge the SX pro. Then try again and always get the same results.

    Auto RCM was on. I turned it off just in case.

    Booting into Original firmware doesnt work anymore EITHER!!!! I never used original firmware

    Even though AutoRCM is off, If I turn on the console without dongle, RCM jig and SD card it wont boot up. screen doesnt even light up.

    I used Hekate to restore my eMMC BOOT0/1 and eMMC RAW GPP (Exfat only) from my original backup. It still doesnt work. RCM is uninstalled. Booting the system with no SD card, No SXPro dongle, and No Jig results in No boot.

    Booting into CFW from SXpro still has same Nintendo Switch logo hang. HELP

    I thought it was a fuse issue since I have burned 7 fuses (6.1) but restored to 4.1

    However I followed the guide (https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/)

    And patched it to 4.1 including BOOT0/1 that didn’t work. Then tried patching to 5.1 and 6.1 that didn’t w ork and I didn’t even see the switch logo when I did those.

    Im lost for what to do really. Booting into Hekate then loading Original FW doesn’t work. Loading CFW from SX OS and Atmosphere payload still hangs.

    Also I noticed when I dump my keys BISKey2 and 3 are both the same. Not sure if that matters.

    Hekate also shows TSEC Key 3 as 0000000000000000000000000000000

    What do I do?
     
  15. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom
    Sounds like a bad NSP. IF you followed that guide, the most important part was leaving AutoRCM on... It protects fuses. You are on 6.1 fuses now though so who cares? If you turned off AutoRCM and booted to stock firmware you burned your fuses. You can't ever boot stock firmware below 6.1 again without cfw. You should try maintenance mode (COMPLETELY POWER OFF BY HOLDING POWER 20 SECONDS. hold both vol+ and vol-, tap power.) then select the initialize without deleting save and user data. IF that doesn't work, restore your backup, If the backup is on 4.1, stock loader won't work. No reason to leave it on 4.1. at that point So IF the backup works, update to 6.1 with ChoiDuJourNX... Stop guessing. Your "Turned off AutoRCM just in case" move was bad. Stop tinkering before you understand what you are doing and why you are doing it. Most mistakes on this board are from newbies thinking they have some kind of right to make decisions. Bad move. Just stop it.

    This is basically the same solution I suggested earlier in this thread to the other Newbie expert who bricked. He had no success but I don't think he follows instructions well either. Google is your friend.
     
  16. stephrk398

    stephrk398 GBAtemp Regular

    Member
    4
    May 29, 2018
    United States
    You must be a trustworthy person for him to give you another go on his second new console.
     
  17. Emeraldman94

    Emeraldman94 GBAtemp Fan

    Member
    3
    Dec 22, 2008
    United States
    I cannot use Choi NX. That must be loaded through Homebrew Loader. I also had 6.1 fuses burned before all of this. I wanted to be on 6.1, but never backed up on 6.1

    I did upgrade using Choi program on Windows Command prompt following the guide (https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/). That didnt help

    I cannot boot into maintanence mode, it doesnt work, when I use Hekate to boot into Stock once on 6.1 it just goes to black screen if I hold down Volume up and down.
    Im only turning on and off AutoRCM now to try to get my console to boot, since that could also be a variable in the problem list. Any other ideas. I followed the above guide to a tee. doesnt work for me. Some people think its a hardware problem
     
  18. mikefor20

    mikefor20 GBAtemp Advanced Fan

    Member
    6
    Jan 12, 2009
    United States
    Mushroom Kingdom
    There was a lot of IFs there. I have seen this more than once. Since you burnt your fuses already, turn off autoRCM, try maintenance mode. IF you can't get in to Maintenance mode then restore your backup, Try maintenance mode, initialize keeping saves... . load a CFW , No reason to leave it on 4.1. at that point so update to 6.1 with ChoiDuJourNX...

    Like I said. I fixed a stuck at switch logo issue with those exact steps. Bad NSP

    no need for AutoRCM if your fuses are equal or less then your installed firmware

    Or you can try that guide again. It should work.
     
    Last edited by mikefor20, Dec 9, 2018
  19. 210modz

    210modz Suspended

    Suspended
    5
    Aug 11, 2017
    United States
    You obviously did more than you are wanting to admit. Lying about what you did won't get it fixed. Just booting sx os will not brick your console. I don't give a shit what you say.
     
    mikefor20 likes this.
  20. Elguster95

    Elguster95 Newbie

    Newcomer
    1
    Dec 27, 2018
    Argentina
    Hi, i got stuck at switch logo too, here is a resume of the history. I used atmosphere in my console when it was 5.2, i needed to install the super smash but i didn't parched the console before of use the atmosphere, so i restored without save the profile and parched the console to use a sd of 64gb and update to 6.2 in the process, puted atmosphere again and installed and played the super smash for 4 days, in the last day i was playing until the console stop the game and show a problem screen of atmosphere, i only read the sentence "push the power botton to restart" and do it, but when it restart the console start to stuck at switch logo, i didn't do a backup before, i dont know what to do, pls help. and if i use a backup of another console, would it solucione the problem? that is the reason because i quoted you
     
Loading...