Question Boot Emummc by default

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

  1. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    I'm on a panic mode right now. Wanted to install incognito using Kosmos/Atmosphere and followed the sysmodule to write to Prodinfo temporarily. The question is which storage does payload (fusee-primary) booting? Sysnand or emummc? I'm aware of the config.ini for this and I've checked that the value is enabled=1. After I've run the payload, I noticed there's a diffrence in settings because I have a theme when booting to cfw(emummc) via launch in hekate. The theme looks normal but the games/nsps installed in my emummc are there. I'm confused, maybe the payload boots the cfw in Sysnand???? :( Can someone enlighten me about this. Thank you in advance.
     
  2. lordelan

    lordelan GBAtemp Psycho!

    Member
    11
    Jan 4, 2015
    Germany
    First off: When booting into emuMMC there should be an E next to the FW version in system settings.
    Second, you can apply one of your hekate launch entries as autoboot (if you're using hekate/KOSMOS).
     
  3. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    So it means that I'm not running into emummc by that time? Isn't it config.ini you're referring to? It is set as enabled=1. Am I missing something?
     
  4. lordelan

    lordelan GBAtemp Psycho!

    Member
    11
    Jan 4, 2015
    Germany
    1. How did you create your emuMMC?
    2. Please post the content of your sd:\bootloader\hekate_ipl.ini here or are you really just using "bare Atmosphère"?
    3. Please post the content of your sd:\emuMMC\emummc.ini here.
     
  5. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    Everything is default for those config. Kosmos v13.2
     
  6. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    [emummc]
    enabled=1
    sector=0xb288800
    path=emuMMC/RAW1
    id=0x0000
    nintendo_path=emuMMC/RAW1/Nintendo
     
  7. lordelan

    lordelan GBAtemp Psycho!

    Member
    11
    Jan 4, 2015
    Germany
    What about my "1."? :)
     
  8. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    Created 2 partitions in my sd. Then created emummc via hekate, pointed to RAW1 to enable emummc. Always booting bia launch in hekate cfw(emummc) no problem at all. I feel different when choosing to boot via payload(hekate).
     
  9. lordelan

    lordelan GBAtemp Psycho!

    Member
    11
    Jan 4, 2015
    Germany
    Huh? That means CFW emuMMC is working?
     
  10. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    I mean this is what I always do for booting. But for the sake of installing incognito, I booted my switch using payload (fusee-primary). The behavior of launching via LAUNCH and via PAYLOAD is totally different.
     
  11. Zkajavier

    Zkajavier Advanced Member

    Newcomer
    2
    Sep 13, 2009
    Costa Rica
    I'm actually having the same questions...

    Here with Auto Boot to emummc CFW, emumand is enabled, I'm using emuMMC through hekate Launch option.

    BUT if you instead use the Payload menu and select fusee-primary, even with emumand enabled, when it launches and you go to system you cannot see the "AMS [VERSION] E", it definitely looks like sysnand. But all my titles, the theme and configurations are definitely those from the emunand, not sysnand. I installed incognito, and can even confirm the serial number is not present, but still, the version looks like you are in sysnand.

    So I'm quite unclear about if fusee-primary payload can launch Sysnand even with emunand enabled. Or if it's just a bug that removes all the affixes from the system version.
     
    Last edited by Zkajavier, Aug 15, 2019
  12. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    Wow! this is exactly what I'm going through. I still don't have clear answers about it.

    Now I'm in the middle of restoring clean nand OR hoping that my Sysnand is clear from cfw. Additionally, my fuses burnt because I updated my clean nand to latest firmware and didn't back it up(rip).
     
    Last edited by Rhaven, Aug 15, 2019
  13. lisko

    lisko Member

    Newcomer
    2
    Oct 28, 2018
    Italy
    To know if you have booted in emummc or sysnand:
    1) boot using hekate "launch" OR payload
    2) go to settings
    3) scroll down until you select system
    4) here you should see your system version followed by atmosphere (AMS) version
    5) if after atmosphere version (0.9.3) there is an "E" you are in emummc otherwise not.
     
  14. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    I believed it boots on sysnand. But the question is why? Hekate should know that if emummc is enabled, it should boot to emummc first.
     
  15. lisko

    lisko Member

    Newcomer
    2
    Oct 28, 2018
    Italy
    Are you sure? You checked in system settings like I said? If emummc is enabled it should boot in emummc from hekate and from fusee-primary
     
  16. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    Zkajavier posted exactly what happened to my switch. Booting using payload(fusee-primary) doesn't use emummc. Pretty sure that in setting firmware, no AMS Version|E, just firmware 8.1.0. But what's weird is that all may nsps installed are there which is residing in emummc. Hoping just a bug.
     
    Last edited by Rhaven, Aug 15, 2019
  17. xabier

    xabier GBAtemp Fan

    Member
    5
    Dec 10, 2006
    United States
    Fuse primary and hekate share emummc configs at least on 0.9.2. To be sure if you are using emummc or normal mmc use a different theme for each memory. I use white for sysnand and black for emunand. Works well.
     
  18. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    Exactly what I did, my ofw is white and my emummc is black with theming. When I boot using payload(fusee-primary.bin) it booted to black theme but without my custom theme, nsps installed are there, but no AMS|E in firmware version. So confusing.
     
  19. xabier

    xabier GBAtemp Fan

    Member
    5
    Dec 10, 2006
    United States
    Ams | E appears on latest atmosphere 0.9.3, older versions don't show anything
     
  20. Rhaven
    OP

    Rhaven Member

    Newcomer
    1
    Aug 13, 2019
    Philippines
    Yes I'm on 0.9.3
     
Loading...