Hacking Question PegaScape, emuMMC and ipatched units

[jadelabe]

oh bois, i have a lot of questions

First of all, i have a ipatched unit with 4.1.0.


1. My switch tells me that i need to update the console for using my exfat sd, i have never connected it to the internet so this shouldn't be a nag right? i guess it should read fat32 with no problems, but as i need 4.1.0 for launching Caffeine is there any work around for using exfat?

2. On the PegaScape HomebreGuide they state that you should wait for the guide being update with emuMMC information. Will any other guide for creating emuMMC work or do we need something specific for ipatched units? i've saw this SceneFolks Guide

3. If i can follow this two guides and manage to get emuMMC will a configuration like this be viable:
- "SysNAND" on 4.1.0 for launching Caffeine and emuMMC images
- First image:Atmosphere with sigpatches on last version for homebrew, nsp and the like, always offline
- Second image: Clean copy of sysNAND updated to the last version for online funcionality

4. With the above configuration will i be able to run lakka/retroarch from Atmosphere or will i need a third image?

Thank you all

 

[ZachyCatGames]

1. Just use fat32, it has no downsides and is more stable

2. Any guide should work fine.

3. Yea, that’s possible. Just flash multiple emummc images to your sd card and edit your emummc.ini file when you want to switch between the two

4. Retroarch is just a regular homebrew app, so yea you can use it. And lakka is launched using hekate, which you can reboot to using caffeine

 

[jadelabe]

Two more questions:

Wouldn't file size limit be a downside?

Is there any difference between lakka and retroarch (functionality/performance)?

I might start hacking my switch now, thank you

 

[ZachyCatGames]

Two more questions:

Wouldn't file size limit be a downside?

Is there any difference between lakka and retroarch (functionality/performance)?

I might start hacking my switch now, thank you

FS has a built in splitting system, which makes the file size limit a non-issue

Lakka has Dolphin which lets you play gamecube and wii games, performance isn't great most of the time. Lakka also lets you bump the CPU to higher clock speed (normal Retroarch has a max of 1785mhz, and Lakka can go to 2091) which may help with performance in a few cases. Lakka also is able to use official nvidia GPU drivers, which may also help with performance in some cases

 

[Bst22322]

My question for #3b
Would you use the official system updater to update your 4.1.0 emunand to latest for online play? This is how I've been considering doing it
Edit: would this burn fuses making your 4.1.0 sysNAND unusable?

 

[masagrator]

My question for #3b
Would you use the official system updater to update your 4.1.0 emunand to latest for online play? This is how I've been considering doing it
Edit: would this burn fuses making your 4.1.0 sysNAND unusable?

Don't use emunand to connect to internet. You can ban your unit this way.

 

[Bst22322]

Don't use emunand to connect to internet. You can ban your unit.

I understand that, that's not what I mean.
How would you update a "clean" emunand? Thorough the system updater I presume?

 

[ZachyCatGames]

I understand that, that's not what I mean.
How would you update a "clean" emunand? Thorough the system updater I presume?

yea, system updater works fine on emummc.

 

[Draxzelex]

Don't use emunand to connect to internet. You can ban your unit this way.

Users of patched units disagree

 

[Ericthegreat]

Two more questions:

Wouldn't file size limit be a downside?

Is there any difference between lakka and retroarch (functionality/performance)?

I might start hacking my switch now, thank you

Exfat has a problem on the switch that your sd card will eventually become corrupt, best to use fat32 then find splitters for transferring your files that are over 4 gb.

 

[tglaria]

Don't use emunand to connect to internet. You can ban your unit this way.

This would mean no online on clean emuMMC so no update.
So ¿what would the use to keep use a clean emuMMC?

I want to do this exact thing:
- keep sysNAND on low firmware to be able to use Pegascape
- have enuMMC CFW for homebrew/emulators
- have emuMMC clean OFW for online functionality.

 

[masagrator]

This would mean no online on clean emuMMC so no update.
So ¿what would the use to keep use a clean emuMMC?

I want to do this exact thing:
- keep sysNAND on low firmware to be able to use Pegascape
- have enuMMC CFW for homebrew/emulators
- have emuMMC clean OFW for online functionality.

There is nothing called "emuMMC clean OFW" and never will be, because emuMMC = CFW.

 

[tglaria]

There is nothing called "emuMMC clean OFW" and never will be, because emuMMC = CFW.

¿what?
You can have your NAND backup as emuMMC.
How would that be "CFW"?

 

[masagrator]

¿what?
You can have your NAND backup as emuMMC.
How would that be "CFW"?

If you want to run emuMMC, you need to run Atmosphere, which means CFW.

 

[The Real Jdbye]

¿what?
You can have your NAND backup as emuMMC.
How would that be "CFW"?

At minimum patches are required to disable fuse checks and redirect NAND, these require some sort of CFW.

 

[tglaria]

If you want to run emuMMC, you need to run Atmosphere, which means CFW.

Atmosphere is the CFW, and you don't need that, you can boot a emuMMC directly with the hekate payload, can't you?
CFW = Custom Firmware.
If the emulated filesystem is a stock NAND, then there's no CFW involved.

At minimum patches are required to disable fuse checks and redirect NAND, these require some sort of CFW.

But those checks and redirects are done before the firware is loaded, right?
So then, the stock firmware shouldn't check the fuse so no burn fuses.
Or I'm wrong?

UPDATE: So, the fuses are checked by the bootloader, not the firmware, so the stock firmware shouldn't burn any fuses if loading as emuMMC through hekate.

 

[masagrator]

Atmosphere is the CFW, and you don't need that, you can boot a emuMMC directly with the hekate payload, can't you?
CFW = Custom Firmware.
If the emulated filesystem is a stock NAND, then there's no CFW involved.

Hekate is only a bootloader. It creates emuMMC, but it uses Atmosphere to run it.
Just check hekate_ipl.ini if you are using Launch menu for emummc. There is under emummc line with fusee-secondary of atmosphere to run it.

--------------------- MERGED ---------------------------

Or go to System in System Settings, next to Current system version will be version of atmosphere.

 

[tglaria]

Hekate is only a bootloader. It creates emuMMC, but it uses Atmosphere to run it.
Just check hekate_ipl.ini if you are using Launch menu for emummc. There is under emummc line with fusee-secondary of atmosphere to run it.

--------------------- MERGED ---------------------------

Or go to System in System Settings, next to Current system version will be version of atmosphere.

So, the emulated MMC uses atmosphere to boot it or during run?
Are you saying that when using a stock emulated MMC, there's still the "Atmosphere version" on the "System version" section ?

 

[masagrator]

there is nothing like "stock emulated". It will always run with Atmosphere. Period. And is working always.