FastCFWswitch for Mariko?
Opened this issue · 6 comments
Dear hartie95,
Would it be possible, with the new r2p that is now used for l4t and provided by hekate since 6.0.0,to make a working version of fastCFWswitch for Mariko consoles?
Take a look into the config readme that comes with the l4t Ubuntu Bionic from switchroot!
README_CONFIG.txt
Maybe it's nothing, but if = wow!
I have made it my mission to make fastCFWswitch with Mariko support 😉
hmm i have tried with mariko (hwfly) to boot directy from cfw into cfw "reboot".
i have set within HEKATE id=EMUMMC
{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 id=EMUMMC logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmp
and thought it should work while triggering this into fastcfw:
[ATMOSPHERE] name=ATMOSPHERE path=/atmosphere/reboot_payload.bin bootId=EMUMMC
but just boots into hekate again.
did i did something wrong?
// it seems nothing is working or beeing passed through the HWFLY and it ends up everytime in hekate no matter what...
just reboots all time to hekate nevertheless what configured.
tegra explorer ... lockpick ... ???
hmm i have tried with mariko (hwfly) to boot directy from cfw into cfw "reboot".
i have set within HEKATE id=EMUMMC
{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 id=EMUMMC logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmpand thought it should work while triggering this into fastcfw:
[ATMOSPHERE] name=ATMOSPHERE path=/atmosphere/reboot_payload.bin bootId=EMUMMCbut just boots into hekate again. did i did something wrong?
// it seems nothing is working or beeing passed through the HWFLY and it ends up everytime in hekate no matter what... just reboots all time to hekate nevertheless what configured. tegra explorer ... lockpick ... ???
As mentioned here it's doesn't seem possible to support mariko yet. The fork he linked also didn't add mariko support via hekate register hack, it just removed the block stating that mariko is not supported, so it is effectively just a reboot, like the os or reboot to payload app from a atmosphere does.
hmm i have tried with mariko (hwfly) to boot directy from cfw into cfw "reboot".
i have set within HEKATE id=EMUMMC{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 id=EMUMMC logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmp
and thought it should work while triggering this into fastcfw:[ATMOSPHERE] name=ATMOSPHERE path=/atmosphere/reboot_payload.bin bootId=EMUMMC
but just boots into hekate again. did i did something wrong?
// it seems nothing is working or beeing passed through the HWFLY and it ends up everytime in hekate no matter what... just reboots all time to hekate nevertheless what configured. tegra explorer ... lockpick ... ???As mentioned here it's doesn't seem possible to support mariko yet. The fork he linked also didn't add mariko support via hekate register hack, it just removed the block stating that mariko is not supported, so it is effectively just a reboot, like the os or reboot to payload app from a atmosphere does.
hi there this is a great works alt on oled it works perfect for me reboots to stock through the overay, boots to ums etc just like fast cfw switch does on v1 switches https://github.com/HookedBehemoth/studious-pancake/releases/tag/v1.0.0
hmm i have tried with mariko (hwfly) to boot directy from cfw into cfw "reboot".
i have set within HEKATE id=EMUMMC{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 id=EMUMMC logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmp
and thought it should work while triggering this into fastcfw:[ATMOSPHERE] name=ATMOSPHERE path=/atmosphere/reboot_payload.bin bootId=EMUMMC
but just boots into hekate again. did i did something wrong?
// it seems nothing is working or beeing passed through the HWFLY and it ends up everytime in hekate no matter what... just reboots all time to hekate nevertheless what configured. tegra explorer ... lockpick ... ???As mentioned here it's doesn't seem possible to support mariko yet. The fork he linked also didn't add mariko support via hekate register hack, it just removed the block stating that mariko is not supported, so it is effectively just a reboot, like the os or reboot to payload app from a atmosphere does.
hi there this is a great works alt on oled it works perfect for me reboots to stock through the overay, boots to ums etc just like fast cfw switch does on v1 switches https://github.com/HookedBehemoth/studious-pancake/releases/tag/v1.0.0
It's only possible since a recent atmosphere update, to actually do it, before that the register was overwritten in hos.
When I have some time, I will look into it for fastCFWswitch and enable support, as long as hekate is the target payload.
hmm i have tried with mariko (hwfly) to boot directy from cfw into cfw "reboot".
i have set within HEKATE id=EMUMMC{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 id=EMUMMC logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmp
and thought it should work while triggering this into fastcfw:[ATMOSPHERE] name=ATMOSPHERE path=/atmosphere/reboot_payload.bin bootId=EMUMMC
but just boots into hekate again. did i did something wrong?
// it seems nothing is working or beeing passed through the HWFLY and it ends up everytime in hekate no matter what... just reboots all time to hekate nevertheless what configured. tegra explorer ... lockpick ... ???As mentioned here it's doesn't seem possible to support mariko yet. The fork he linked also didn't add mariko support via hekate register hack, it just removed the block stating that mariko is not supported, so it is effectively just a reboot, like the os or reboot to payload app from a atmosphere does.
hi there this is a great works alt on oled it works perfect for me reboots to stock through the overay, boots to ums etc just like fast cfw switch does on v1 switches https://github.com/HookedBehemoth/studious-pancake/releases/tag/v1.0.0
It's only possible since a recent atmosphere update, to actually do it, before that the register was overwritten in hos. When I have some time, I will look into it for fastCFWswitch and enable support, as long as hekate is the target payload.
okay no problem and yes i was aware of it - only posted to allow others to know that there is an alt out there for the time being :)