What's the long-teased released you guys are counting down for in the next version of Kosmos?
hello,
for the previous release, it was asked to delete /modules from the SD card to prevent any risk of error while booting
Is this done automatically when we update Kosmos with Kosmos updater?
Is it still necessary with the last version of Kosmos (v11.11)? There is no warning anymore
thanks
for the previous release, it was asked to delete /modules from the SD card to prevent any risk of error while booting
Is this done automatically when we update Kosmos with Kosmos updater?
Is it still necessary with the last version of Kosmos (v11.11)? There is no warning anymore
thanks
Does goldleaf 0.5 nightlies still work?
Also will investigate the dev menu claims. Worst case scenario we wait for the next version of dev menu
I always get the no configs found error with no entry in the launch section.
Since SX Pro is my only dongle it's my only choice for now. Don't tell me chainloading through SX OS bootmenu doesn't work
Since SX Pro is my only dongle it's my only choice for now. Don't tell me chainloading through SX OS bootmenu doesn't work
D
Deleted User
Guest
@lordelan
It didn't work through the menu for me neither.
You have to convert hekate.bin to boot.dat, then chainloading will work.
I did it yesterday because a buddy of mine updatet to 7.0 and only had the dongle.
There is a python script just for the conversion
Install Python on your PC, rename the file to .py and drag hekate.bin to it.
Rename the outcome boot.dat and place it on the root of your sd.
It didn't work through the menu for me neither.
You have to convert hekate.bin to boot.dat, then chainloading will work.
I did it yesterday because a buddy of mine updatet to 7.0 and only had the dongle.
There is a python script just for the conversion
Install Python on your PC, rename the file to .py and drag hekate.bin to it.
Rename the outcome boot.dat and place it on the root of your sd.
Last edited by ,
Yes you can, but I don't now the exactly steps to it.
Looking it for myself.
I still don't understand why this is not in Kosmos anymore, it's essential and much more important then some cheat engine stuff.
Can someone please explain to me, how I can upgrade my switch from Hekate 4.2/Atmosphère 7.5
to the latest version? (Original Firmware is 3.1 -> updated via ChoiDujourNX to 5.1 -> RCM-Mode=On)
Do I just have to use the new Kosmos release, start my switch and install firmware 7.1 using ChoiDujourNX
or do I have to start my switch with my current Kosmos version (old one), update to version 7.1 using ChoiDujourNX, and then
update my SD-Card setup with the new Kosmos release?
Back in time there was something about the autonogc thing, do i have to enable it?
Which Atmosphère version is integrated to the new release of Kosmos, the 8.5 release or the newest one with the two new
commits?
Thx!
to the latest version? (Original Firmware is 3.1 -> updated via ChoiDujourNX to 5.1 -> RCM-Mode=On)
Do I just have to use the new Kosmos release, start my switch and install firmware 7.1 using ChoiDujourNX
or do I have to start my switch with my current Kosmos version (old one), update to version 7.1 using ChoiDujourNX, and then
update my SD-Card setup with the new Kosmos release?
Back in time there was something about the autonogc thing, do i have to enable it?
Which Atmosphère version is integrated to the new release of Kosmos, the 8.5 release or the newest one with the two new
commits?
Thx!
Put newest Kosmos on SD first.
Remove old atmosphere, bootloader and modules folder first, don't just overwrite.
Then update through ChoiDujourNX.
--------------------- MERGED ---------------------------
Turned out the error came from a bug from ES file explorer on my mobile phone.I always get the no configs found error with no entry in the launch section.
Since SX Pro is my only dongle it's my only choice for now. Don't tell me chainloading through SX OS bootmenu doesn't work
While copying everything to the SD that stupid app decided to rename hekate.ini to hekate.ini.txt (don't know why). Now it's all working again.
i made a quick copy and paste solution for this now:
https://gbatemp.net/threads/ldn_mitm-lan-play-kip-for-kosmos-11-11.533255/
D
Deleted User
Guest
Turned out the error came from a bug from ES file explorer on my mobile phone.
While copying everything to the SD that stupid app decided to rename hekate.ini to hekate.ini.txt (don't know why). Now it's all working again.
As a Android User I would recommend NXloader.apk & hekate.bin over SX-Pro dongle.
You only need a cheap cable and usb-otg support on your phone.
D
Deleted User
Guest
There will be a new boot.dat downloadable on sx xecuter com if they ever will release >7.00 support. Their current 2.5.3 SX OS only supports 6.2.
I by myself switched completely to Kosmos or maybe ReiNX in the future.
Just keep a backup of your license.dat if you ever want to use SX again.
I by myself switched completely to Kosmos or maybe ReiNX in the future.
Just keep a backup of your license.dat if you ever want to use SX again.
Similar threads
