For anyone using Devmenu 0.8.5 broke itnew atmosphere and edizon have been released
For anyone using Devmenu 0.8.5 broke it
Or so it's being reported
You should do that because many modules are different this time.
Yes you can, but I don't now the exactly steps to it.Change log says ldn_mitm has been removed, can I still add it my self ?
Put newest Kosmos on SD first.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!
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
Change log says ldn_mitm has been removed, can I still add it my self ?
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.
Ok, here is hekate_4.9.bin converted to boot.dat for everyone.
Yupp, and of course you need the rest of the kosmos-stuff on your sdcard.
Just rename your old boot.dat to have a backup.