Atmosphere-NX - Custom Firmware in development by SciresM

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by Waze0613, Feb 17, 2018.

  1. RattletraPM

    RattletraPM GBATemp's official 蒸気イーブイ

    pip Reporter
    15
    Jan 18, 2017
    Italy
    Shinjuku Station
    SciresM is done reimplementing the boot sysmodule, that giant sudden list of commits was caused by a merge of the boot_dev branch into master.
     
    peteruk likes this.
  2. xenon

    xenon GBAtemp Regular

    Member
    2
    May 19, 2006
    Italy
    Cool, thanks.
     
  3. Krude

    Krude GBAtemp Fan

    Member
    5
    May 18, 2013
    Gambia, The
    Had a very scary moment there, thought i had bricked my switch.
    My switch was still on FW 7.0.1 ( was using hekate 4.10.1 and atmo 0.8.9 already tho) and i thought it was time for an update for the faster laod times in Zelda/Mario. So i went online and into system settings to hit that update button.

    Update downloaded, installed, switch rebooted into hekate into atmosphere, and... the console froze on the Switch logo. After a hard shutfown and reboot, the console was still stuck on the Switch logo.

    So i went and removed all custom sys modules and stuff from the SD card and booted pure hekate + atmo.
    Still froze on boot-up during the logo. This is where i sorta started to panic, thinking "THE ONE TIME YOU DON'T DO A NAND UPDATE BEFORE UPDATING, FUUUUUU"

    Eventually i had to boot stock firmware through hekate (had to find an up-to-date custom warmboot and secmon on the internet first, thanks 7.x+) to get the switch to go past the Switch logo and boot into the OS. Giant load off my shoulders that it still booted at all.

    I then checked to see if atmosphere booted at all, and launched it through fusee-primary instead of hekate. It works!
    Curiously, i then went back to launch atmosphere through hekate like i did earlier, and now it suddenly works again whereas earlier it jsut froze. Completely the same setup and everything, nothing changed.


    There was probably something during the update process from 7.0.1 to 8.0.1 that didn't work on atmosphere, and that booting stock through hekate resolved? Might be worth looking into, but i don't know how reproducable that is.

    Well if someone else has that problem, that's one way to resolve it i guess.
     
  4. BaamAlex

    BaamAlex GBAtemp Maniac

    Member
    5
    Jul 23, 2018
    Germany
    When you do this you will burn fuses.
     
  5. Krude

    Krude GBAtemp Fan

    Member
    5
    May 18, 2013
    Gambia, The
    No that's what hekate is for. My console is still on 5 fuses burnt.
     
  6. BaamAlex

    BaamAlex GBAtemp Maniac

    Member
    5
    Jul 23, 2018
    Germany
    I mean when you boot stock firmware ;)
     
  7. Trice

    Trice GBAtemp Regular

    Member
    5
    Jan 20, 2009
    Switzerland
    Not if he uses Hekate to boot it.
     
  8. hippy dave

    hippy dave BBMB

    Member
    15
    Apr 30, 2012
    United Kingdom
    It might have worked if you'd used fusee primary the first time instead of hekate -> atmosphere. And maybe whatever you changed before booting stock from hekate was what made booting atmos from hekate work the next time.
    Glad it's all working for you now anyway.
     
  9. ZachyCatGames

    ZachyCatGames GBAtemp Advanced Maniac

    Member
    8
    Jun 19, 2018
    United States
    Hell
    If you use "stock" with hekate on 7.0+, it's not true stock
     
  10. Krude

    Krude GBAtemp Fan

    Member
    5
    May 18, 2013
    Gambia, The
    I didn't actually change anything in between booting atmo (not working) to stock (working) to atmo (working). I really just selected a different launch option in hekate. Didn't change anything in regards to files or whatever on the SD card.
     
  11. PHiLiPZ

    PHiLiPZ GBAtemp Regular

    Member
    2
    Mar 8, 2019
    Slovakia
    Could it be your SD was exFAT and you lost support of that filesystem by upgrading online?
     
  12. onehexedupman

    onehexedupman Member

    Newcomer
    2
    Jul 20, 2018
    United States
    Can you explain this? So booting stock from hekate burns fuses on 7.0+?
     
  13. BaamAlex

    BaamAlex GBAtemp Maniac

    Member
    5
    Jul 23, 2018
    Germany
    When you reboot to stock you burn fuses.
     
  14. Trice

    Trice GBAtemp Regular

    Member
    5
    Jan 20, 2009
    Switzerland
    It's the bootloader that checks and burns the fuses, not the actual OS, so as long as you don't use Nintendo's bootloader and instead use a custom one like Hekate or Fusée you won't burn fuses regardless if you boot into CFW or OFW afterwards.
     
    loler55 and PHiLiPZ like this.
  15. ZachyCatGames

    ZachyCatGames GBAtemp Advanced Maniac

    Member
    8
    Jun 19, 2018
    United States
    Hell
    On 7.0.0+ you have to use exosphere and AMS lp0fw if you’re booting with hekate even for “stock” since it’s impossible to decrypt package1 which contains secmon, warmboot, and nxboot
     
  16. xenocard

    xenocard Advanced Member

    Newcomer
    3
    Sep 13, 2009
    United States
    is it worth updating from FW 6.2.0 to 8.0.1?

    i am only using my switch for Emulators but Team Sonic Racing is tempting me to upgrade its a day one switch release.

    will i regret it later? is there any permanent CFW in progress which will work for lower FW's or that 8.0.1 FW blocks ?
     
    Last edited by xenocard, May 18, 2019
  17. stick267

    stick267 GBAtemp Advanced Fan

    Member
    4
    Dec 17, 2018
    United States
    If you want to update, update. Who knows if/when "permanent" CFW will come.
     
  18. NFates

    NFates Wants to understand™

    Member
    7
    Mar 13, 2016
    Dominican Republic
    Probably home.
    If you're using vanilla Atmosphere and don't pirate stuff, just make sure to have AutoRCM on to avoid burning fuses.
     
  19. xenocard

    xenocard Advanced Member

    Newcomer
    3
    Sep 13, 2009
    United States
    [QUOTE="If you're using vanilla Atmosphere and don't pirate stuff, just make sure to have AutoRCM on to avoid burning fuses..[/QUOTE]

    i have 2 Switch consoles, have Mario Kart 8 and Smash Ultimate on Pirated console now i cant do local multiplayer anymore with other, i don't care about burnt fuses, just the fact that i want to be on a FW that supports permanent CFW plus its nice to be able to play FF7 with Fan Mods

    i read that 8.0+ FW breaks some exploits regardless of patched units or not and it was recommended to not go past 7.0.1, hence i am asking here, i have been out of the loop for 3 months, normally i would just update to latest FW, the only reason i would update my console is if emulators perform better.

    anyway, ill just update to 7.0.1 with ChoiDujourNX
     
    Last edited by xenocard, May 18, 2019
  20. NFates

    NFates Wants to understand™

    Member
    7
    Mar 13, 2016
    Dominican Republic
    Probably home.
    https://twitter.com/sciresm/status/1117956347536953344
     
Loading...