I might have mistaken it for OC Suite which wasn't working until recently. Thanks for the updated info. ^^AMS 1.7.0
FW 18.0.0
sys-clk works as expected.
I might have mistaken it for OC Suite which wasn't working until recently. Thanks for the updated info. ^^AMS 1.7.0
FW 18.0.0
sys-clk works as expected.
Same firmware and atmosphere, I get this messageAMS 1.7.0
FW 18.0.0
sys-clk works as expected.
I updated it several times... and still appears as 1.0.2c in the tesla menu
Are you sure you're pushing the correct fusee.bin payload? Did you try with clean Atmosphere install?Sorry guys,i downloaded the latest version of Atmosphere and fusse.bin from here https://github.com/Atmosphere-NX/Atmosphere/releases ,but when i restart the Switch it gives me the error that the fusee.bin is wrong and not for this version and pressing power,i had to go back to 1.6.2 doing the same procedure and this works,the latest 1.7.0 however always gives the same error and i did it several times why?
@Blythe93 of course,i downloaded the fusee.bin under the 1.7.0 pre-release from the link i put in the previous post,i unpacked everything and inserted fusee.bin in the atmosphere folder and when i restart from hekate 6.1.1 it gives me the error i wrote.Are you sure you're pushing the correct fusee.bin payload? Did you try with clean Atmosphere install?
You've probably installed the latest Atmosphere correctly, it's just that you should put your fusee.bin onto device that's pushing those payloads, like Rekado (for Android), TegraRCM (for Windows) and other dongle-like devices (except for those Chinese knock-offs). If you've selected fusee.bin payload from Hekate, which I've admittedly never done, it should probably go into bootloader/payloads folder instead, like Lockpick_RCM and other payloads go. Maybe I'm wrong?@Blythe93 of course,i downloaded the fusee.bin under the 1.7.0 pre-release from the link i put in the previous post,i unpacked everything and inserted fusee.bin in the atmosphere folder and when i restart from hekate 6.1.1 it gives me the error i wrote.
You're probably still pushing the old payload. What do you use to push your fusee.bin file? Here are the recommended methods.However,if i reinstall 1.6.2 with the same procedure,the Switch with Atmosphere starts without problems.
@Blythe93 ,i use Rekado since i got the Switch,and i already have the latest Hekate installedYou've probably installed the latest Atmosphere correctly, it's just that you should put your fusee.bin onto device that's pushing those payloads, like Rekado (for Android), TegraRCM (for Windows) and other dongle-like devices (except for those Chinese knock-offs). If you've selected fusee.bin payload from Hekate, which I've admittedly never done, it should probably go into bootloader/payloads folder instead, like Lockpick_RCM and other payloads go. Maybe I'm wrong?
Still, you've mentioned that you're loading through Hekate, did you update your Hekate to the latest as well? You'll need the latest 6.1.1 version for the latest Atmosphere to work.
You're probably still pushing the old payload. What do you use to push your fusee.bin file? Here are the recommended methods.
That's really strange, then. Are your sys-modules up-to-date? Can you take a picture of the error you're facing?@Blythe93 ,i use Rekado since i got the Switch,and i already have the latest Hekate installed
depends what do you want to doFusee.bin goes in sd/bootloader/payloads.
Sorry @impeeza ,should fusee.bin be placed in the bootloader/payloads folder or just in the bootloader folder without any subdirectories?depends what do you want to do
normally goes on the root of card named PAYLOAD.BIN or on your injector
You can place it wherever the hekate_ipl points...Sorry @impeeza ,should fusee.bin be placed in the bootloader/payloads folder or just in the bootloader folder without any subdirectories?
[Atmosphere (emuMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
cal0blank=1
atmosphere=1
logopath=bootloader/res/bootlogo-emunand-f.bmp
icon=bootloader/res/icon_payload.bmp