AutoRCM when booting to Sysnand (8.0.1) when using SXOS doesn't work. Emunand boots perfectly fine for me since its on 7.0.1. I have to disable AutoRCM to boot into Sysnand
Right, but that isn't the same as autorcm bricking your unit. That is that SXOS doesn't work with 8.0.1 and you refuse to use anything other than SX OS. You could also use atmosphere to boot your 8.0.1 sysnand.
The fact you can boot your system into rcm, disable autorcm and everything loads fine means it's not a brick.
What TX said is sort of misleading. It implies that 8.0 introduces an issue with AutoRCM and patched units.
You should re-read it, the post said "This applies to patched and non patched units". TX have deleted the post by rory2005 now, I'm not sure it was ever an official piece of information. It seems more likely he just misunderstood what he'd heard.
Hey im on 8.0.0 and i want to ask if AutoRCM now bricks on this Firmware because i thought that TX said that
I'm not convinced that TX did say that. There was a post by someone on their forums that said that, which has now been deleted.
Autorcm has worked fine with atmosphere on 8.0.0 and 8.0.1 and there are no changes reported that fixed it.
I think the post was a mistake by someone who wanted to sound important but didn't understand what he'd heard.
1. autorcm on patched units is a bad move no matter what firmware you are running, atmosphere have recently added a block to you installing autorcm if you're using dejavu on a patched switch. This won't change until someone invents fusee gelee 2.0 (which may never happen)
2. autorcm prevents you loading sysnand with SX OS if you have updated to 8.0.0, this is because they haven't updated their code yet & isn't even a brick. You can load sysnand if you use an alternate payload with 8.0.0 support.
In short, the answer is: yes autorcm works on 8.0.0, but then it always did. Your favourite payload may not work with 8.0.0, but then it wouldn't matter whether you used AutoRCM or RCM.