Nope. Started everytime from scratch.
The only thing I got left to try is get rid of the R4 Dongle and use TegraRCM to inject the payloads, but I really dont think that's the issue.
I have the Crash Report here:
EDIT: Thanks everyone, specially @BaamAlex and @stick267. I ran using full ram, with R trigger, and it worked.
Last edited by El.James,
- Joined
- Jul 23, 2018
- Messages
- 6,051
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,162
- Country
I did, but the folder doesnt exist.
Anyway I ran HB and Retroarch in full RAM (select title, hold R), and it seems to be running fine.
I havent stress-tested it bc I left my house but when I get back, will try some more.
I been using sxos since the beginning but now i am trying to dual boot sxos/atmosphere because of the flycast. When I am in atmosphere the physical power button is not working so I had a hard time turning off the system to remove the sd card. I do a hard power off and reboot into sx os and the power button is working again. Any idea what's going on?
Could anyone help the switch crashs on most of my backup games , i tried lot cfw even on ofw with my original card it crash is a tried downgrade and ipgrade to different firmwares , picture of crash code error
I have seen several posts about firmware 9 and atmosphere 9.4 having issues. I have not updated yet because of the issues but now there are a couple of games coming out like Death Squared that need firmware 9. Have all of the bugs been fixed or is it something that I should wait for to be fixed?
Do you have any backup of a working state? Restore the latest, update to 9.0.1 using ChoiDujourNX and Darthsternie’s fw, get KosmosNX package with patches and try your original game cart or any game that worked previously. Maybe check your sd card or try using another one. I have no more issues with 9.0.1 and latest Atmosphere than with any previous releases.
Staying on older firmware is the best, i see a lot of changes with 9.0 firm for switch but i also fear the fact that future upcoming games wont launch without newer firmware 
Having an up-to-date firmware in emunand and having a backup of an earlier sysnand are the best options. I don’t understand why so many people use obsolete fw and then always keep asking, whether something runs on it. Especially after it’s been confirmed by multiple sources that everything works at least as fine as it did with previous fw.
Last edited by PHiLiPZ,
@SciresM
Sorry for tagging you chief but I figured you would be the appropriete guy to ask this:
Since it might be not wise to use a "full" CFW on a sysNAND which we don't have to get banned, wouldn't it be possible to have kind of a slim AMS that only has those two features enabled:
Sorry for tagging you chief but I figured you would be the appropriete guy to ask this:
Since it might be not wise to use a "full" CFW on a sysNAND which we don't have to get banned, wouldn't it be possible to have kind of a slim AMS that only has those two features enabled:
- restarting from the menu boots directly into the reboot_payload.bin
- an error screen does the same after hitting a VOL button
The only time I've ever seen the exception handler/ vol to restart thing is for homebrew crashes. Only time I managed to take down the system with a commercial game was hard lock FFVII with some layeredFS mods. So I'm not sure that that function does anything outside of homebrew?
Only worth if you want to play games which require 9.0.1. I don't think many games require 9.X yet.
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
-
-
-
-
@
RedColoredStars:
Never even seen a tiger crust pizza in any stores around here. Walmart, Cub, or otherwise. -
-
-
@
RedColoredStars:
Last thing I told her is how much I love her, and that Im not leaving her there forever and I promise to come back and take her back home with me.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
