Did some tests, different browsers, connections, cleared cookies.
Apparently it's a problem with the download accelerator, without it it worked.
Thanks for your attention, you can close/delete this topic.
Anyone else having this problem?
In the last days I've not been able to download anything from the website.
A message states I don't have permission, error 403 forbidden.
I'm on Windows 10, Switch 1.0.0.
Can get to the PegaScape screen, but Nereba keeps loading and nothings happens..
Tried several times with no luck.
Did you change anything?
------------
Nevermind, my fault, it's working now!
Jesus Christ!
WIth two emunand in you can do whatever you want, play clean (OFW) and dirty (CFW).
PLUS you can still keep your real sysnand intact and your fuses intact for the sake of one day who knows maybe a coldboot solution will come along.
PegaSwitch > scripts (e.g. Nereba) just can't...
You don't need to burn any fuse, you just need two emuMMC.
Check my guide:
https://gbatemp.net/threads/multiple-emummc-setup-including-restoring-a-clean-nand-for-online-use.562188/
It's a bit old/outdated but this setup still works for me (latest OFW/Atmosphere).
I can play online, no ban...
I wrote the tutorial teaching how to create two partitions at that time, and you had to dd only the second partition initially (you were unable to do so just because you didn't follow the instructions).
I believe that the latest versions of Hekate allow the creation of partitions in any order...
Replace Atmosphere's original "reboot_payload.bin" with Hekate's latest .bin ("hekate_ctcaer_5.5.0.bin" as I write).
And rename it to "reboot_payload.bin".
It powers off.
AutoRCM is disabled in my case.
1.0.0 Switch boots into the original sysnand, wich I use to start PegaScape.
You can find...
I meant pure and not a "packaged" version of it (Kosmos, BPack, Deep Sea, etc).
It' ok to go online with the default Atmosphere config.
These two lines on system_settings.ini are useful:
[atmosphere]
power_menu_reboot_function = str!payload
enable_deprecated_hid_mitm = u8!0x1
And these two on...
That's odd..
In my case the clean emuMMC only boots with "fss0=bootloader/payloads/fusee-secondary.bin", but the dirty emuMMC is ok with "payload=bootloader/payloads/fusee-primary.bin".
I see no reason for you not to be able to boot any of the emuMMC with fusee-primary.
Well, problably that's...