Attachments
I updated it several times... and still appears as 1.0.2c in the tesla menu
EDIT: im an idiot... I had renamed the old version as 2_xxxx.ovl, so it appeared on the top of the list. With that prefix, it never got rewritten by the updated version
Last edited by Desconocido90,
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?
Are you sure you're pushing the correct fusee.bin payload? Did you try with clean Atmosphere install?
@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.
However,if i reinstall 1.6.2 with the same procedure,the Switch with Atmosphere starts without problems.
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?
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?
Since 1.6.2 worked for you, I don't see a reason for 1.7.0 not to work if you have just copied the newer files and updated fusee.bin payload on your Rekado. I've checked whether the built-in payloads are up-to-date when you check for updates and they really are.
depends what do you want to do
normally goes on the root of card named PAYLOAD.BIN or on your injector
Sorry @impeeza ,should fusee.bin be placed in the bootloader/payloads folder or just in the bootloader folder without any subdirectories?
You can place it wherever the hekate_ipl points...
Guys i wanted to thank everyone for the help you gave me,in the end i managed to start AMS 1.7.0 correctly.
In a way, when you really think about it, aren't we all Atmosphere?
Do you guys have any idea why i can boot Atmosphere on emunand via fusee.bin but not via hekate?
Since I updated firmware to 17.0.1 and atmosphere to 1.6.2 (hekate 6.0.7), I get the infamous Error 2162-0002 (0x4a2) on either program 0100000000001000 or 010000000000100C (seems to be random) . I already knew these kind of programs referred to custom themes being installed and incompatible with the new release, although i've never been interested in themes and i don't have those folders in atmosphere/contents.
So far I've tried to clean up my atmosphere/contents folder and updating all tesla overlays but to no avail. I also removed tesla menu and the .overlays contents completely, but still getting a crash when loading Atmosphere.
I can boot into atmosphere only by loading fusee.bin from the hekate menu, and everything works as expected (even tesla and all overlays).
The moment I try to reboot and launch the emummc via hekate, I get the same error again and I have to reboot and load fusee.bin to boot into atmosphere.
The hekate_ipl.ini settings I'm trying to load (which worked on earlier atmosphere versions) is this:
Do you have any idea what might be wrong with the way I'm loading atmosphere via hekate?
Since I updated firmware to 17.0.1 and atmosphere to 1.6.2 (hekate 6.0.7), I get the infamous Error 2162-0002 (0x4a2) on either program 0100000000001000 or 010000000000100C (seems to be random) . I already knew these kind of programs referred to custom themes being installed and incompatible with the new release, although i've never been interested in themes and i don't have those folders in atmosphere/contents.
So far I've tried to clean up my atmosphere/contents folder and updating all tesla overlays but to no avail. I also removed tesla menu and the .overlays contents completely, but still getting a crash when loading Atmosphere.
I can boot into atmosphere only by loading fusee.bin from the hekate menu, and everything works as expected (even tesla and all overlays).
The moment I try to reboot and launch the emummc via hekate, I get the same error again and I have to reboot and load fusee.bin to boot into atmosphere.
The hekate_ipl.ini settings I'm trying to load (which worked on earlier atmosphere versions) is this:
Code:
[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.bmpDo you have any idea what might be wrong with the way I'm loading atmosphere via hekate?
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
-
-
-
-
-
-
-
-
@
SylverReZ:
You can make a post on the DS forum about your findings, and they'll do their best to respond. They have a GBAtemp account here, you know. -
@
Materia_tofu:
oh ye i made a post i did forget they had an account i prob shouldve tagged them in the post+1
tbh -
-
-
-
-
@
BakerMan:
Update on my brother: He's home now, tired and hungry, obviously, but other than that, seems to be doing fine.+2 -
-
-
@
BakerMan:
Well, from what I've heard from my parents, he had a seizure last night, perhaps an epileptic episode, fucking died, had a near death experience, my dad called the paramedics, they showed up, took him to the hospital, and he woke up covered in tubes, and started complaining.
-
-
-
-
-
-
-
-
