Homebrew RELEASE [Overlay]fastCFWswitch

[jnl1]

Do I need anything more? Is there any risk? Do I have to backup anything, do I need more SD card storage for any other atmosphere stuff? Can I have all the atmosphere homebrews on the same SD card?

 

[RednaxelaNnamtra]

Do I need anything more? Is there any risk? Do I have to backup anything, do I need more SD card storage for any other atmosphere stuff? Can I have all the atmosphere homebrews on the same SD card?

Yeah, you can have atmosphere and sxos on the same sd without a problem, only homebrews that need an installation for each cfw are system modules, like teslas loader, everything else shares the same folder, and is cfw independent.

 

[jnl1]

Thank you! Works great!

 

[OldGnashburg]

What do I put for Lakka, Android, and Ubuntu?

 

[RednaxelaNnamtra]

What do I put for Lakka, Android, and Ubuntu?

Depends on your hekate config to boot them, either the position of the entry in the config, or the ID you set for the entry in the hekate config.

 

[Muxi]

Depends on your hekate config to boot them, either the position of the entry in the config, or the ID you set for the entry in the hekate config.

Could you please explain this using the example of "Lakka"?
This is the entry of the ini file under bootloader/ini for Lakka:

[Lakka]
payload=lakka/boot/coreboot.rom
logopath=lacca/boot/splash.bmp

What should the entry in the config.ini of fastCFWswitch look like so that Lakka can be booted over it?

 

[RednaxelaNnamtra]

simpliest way would be this in your hekates config:

[Lakka]
payload=lakka/boot/coreboot.rom
logopath=lacca/boot/splash.bmp
id=lakka

and this in fastCFWswitch config:

[LAKKA]
name=Lakka
path=[path to your hekate.bin]
bootId=lakka

 

[Muxi]

Thanks a lot! That helped!

 

[deejay87]

ok now i see how bootId work i can try with 2 emummc now

 

[mikifantastik98]

really useful. Thanks! @RednaxelaNnamtra
there is a way to launch Hekate when the autoboot is configured ?
if I launch hekate it starts Atmosphere

*kosmos/DeepSea toolbox ... boot Hekate directly ( with the autoboot configured )
how does he do it ?

 

[RednaxelaNnamtra]

really useful. Thanks! @RednaxelaNnamtra
there is a way to launch Hekate when the autoboot is configured ?
if I launch hekate it starts Atmosphere

*kosmos/DeepSea toolbox ... boot Hekate directly ( with the autoboot configured )
how does he do it ?

Booting to bootPos 0 should boot to hekates menu and temporarily overwrite autoboot.

 

[mikifantastik98]

now ... im on new version 1.1.0
how to chain Atmosphere correctly ? ( cfw sysnand )
if I launch Atmosphere from fastCFWSwitch start Hekate (with autoboot configured)
* im on DeepSea Aio Package

 

[RednaxelaNnamtra]

now ... im on new version 1.1.0
how to chain Atmosphere correctly ? ( cfw sysnand )
if I launch Atmosphere from fastCFWSwitch start Hekate (with autoboot configured)
* im on DeepSea Aio Package

DeepSea seems to replace the reboot payload.bin from atmosphere with hekate, to automatically reboot you to hekate.
To boot atmosphere with it, either put atmospheres fusee-primary or reboot payload.bin to your SD, and modify the atmosphere entry in the fastCFWswitch config to point to its path, or set the bootPos in it to, I think, 1 for sysnand or 2 for emunand atmosphere to boot deepSeas default hekate config.

 

[mikifantastik98]

DeepSea seems to replace the reboot payload.bin from atmosphere with hekate, to automatically reboot you to hekate.
To boot atmosphere with it, either put atmospheres fusee-primary or reboot payload.bin to your SD, and modify the atmosphere entry in the fastCFWswitch config to point to its path, or set the bootPos in it to, I think, 1 for sysnand or 2 for emunand atmosphere to boot deepSeas default hekate config.

true ! that's the problem !
everything is perfect now ( cfw sysnand ):

[ATMOSPHERE]
name=atmosphere
path=/atmosphere/reboot_payload.bin
bootPos=1

 

[mikifantastik98]

@RednaxelaNnamtra thank you very much
so ...
this should be the "universal" configuration for this type of package. correct !?

[CFWS]
type=section
name=Custom Firmwares

[SYSNAND]
name=atmosphere (SYSNAND)
path=/atmosphere/reboot_payload.bin
bootPos=1

[EMUNAND]
name=atmosphere (EMUNAND)
path=/atmosphere/reboot_payload.bin
bootPos=2

[TOOLS]
name=Tools

[HEKATE]
name=Hekate
path=/atmosphere/reboot_payload.bin
bootPos=0

 

[RednaxelaNnamtra]

@RednaxelaNnamtra thank you very much
so ...
this should be the "universal" configuration for this type of package. correct !?

Yeah, you could also add stock with bootPos 3, if I interpreted the config correctly.

 

[mikifantastik98]

Yeah, you could also add stock with bootPos 3, if I interpreted the config correctly.

like this ?

[STOCK]
name=Stock (Firmware)
path=/atmosphere/reboot_payload.bin
bootPos=3

 

[RednaxelaNnamtra]

like this ?

Yeah, with that fastCFWSwitch should include all default hekate config entrys, and a way to boot into hekate itself

 

[kickmeh]

what code if we want to boot on stock ofw??

 

[RednaxelaNnamtra]

what code if we want to boot on stock ofw??

Depends on what CFW/bootloader you use, and what you define as stock.
If you mean stock, as in hekates stock mode, with only the cfw elements needed to be able to boot, its possible, by adding an entry to your hekate config and telling fastCFWswitch to boot it.
If you mean stock, as in no custom code runs, and it boots normaly, I don't think there is a simple way out there.