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.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?
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.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.
Booting to bootPos 0 should boot to hekates menu and temporarily overwrite autoboot.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 ?
DeepSea seems to replace the reboot payload.bin from atmosphere with hekate, to automatically reboot you to hekate.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
true ! that's the problem !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.
[ATMOSPHERE]
name=atmosphere
path=/atmosphere/reboot_payload.bin
bootPos=1
[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
Yeah, you could also add stock with bootPos 3, if I interpreted the config correctly.@RednaxelaNnamtra thank you very much
so ...
this should be the "universal" configuration for this type of package. correct !?
like this ?Yeah, you could also add stock with bootPos 3, if I interpreted the config correctly.
[STOCK]
name=Stock (Firmware)
path=/atmosphere/reboot_payload.bin
bootPos=3
Yeah, with that fastCFWSwitch should include all default hekate config entrys, and a way to boot into hekate itselflike this ?
Depends on what CFW/bootloader you use, and what you define as stock.what code if we want to boot on stock ofw??