Lol that has nothing to do with the topic. It's just an obvious thing about how autoRCM has always worked.https://twitter.com/SciresM/status/1117956835456061440
Also, a big warning: If you are on a unit which has the RCM bug (fusee gelee) patched, and start playing with Atmosphere using Deja Vu: do not install AutoRCM. This will brick your unit, and you will need to use hardware to fix corrupted the BOOT0 partition.
Applies for patched units.
Lol that has nothing to do with the topic. It's just an obvious thing about how autoRCM has always worked.
"This firmware is UNHACKABLE! All Switches will be bricked! Even unmodded switches!"
-Garyopa, probably.
Good jobIt was me that mentioned bricking, Was a mistake on my behalf about bricking in auto rcm, Not been well and not thinking straight and forgot to mention it actually only applied to patched units
All autoRCM does is it changes a bit in BOOT0 so the signature gets fucked, the systems sees it as invalid and has nothing to boot from, and when the Tegra has nothing to boot from it goes into RCM. Current autoRCM can and does work just fine on 8.0.0The AutoRMC is a permanent patch that is made in the system, from which it can be reversed, but the warning is always there. And in 8.x what they have done is change the way they should be patched, so AutoRMC as we know it is not only unusable, but it also causes a brick. You can perform AutoRMC but changing the address that corresponds to the new system.
In short, the old or current version of RMC is obsolete, it must be updated.
Exactly, it just corrupts boot0, so it panics and goes to RCM. It's on all these Nvidia units, not just Switches.All autoRCM does is it changes a bit in BOOT0 so the signature gets fucked, the systems sees it as invalid and has nothing to boot from, and when the Tegra has nothing to boot from it goes into RCM. Current autoRCM can and does work just fine on 8.0.0
So, what causes the brick ?. Do you think it's worth upgrading, will Atmosphere still work without using AutoRMC?All autoRCM does is it changes a bit in BOOT0 so the signature gets fucked, the systems sees it as invalid and has nothing to boot from, and when the Tegra has nothing to boot from it goes into RCM. Current autoRCM can and does work just fine on 8.0.0
So, what causes the brick ?. Do you think it's worth upgrading, will Atmosphere still work without using AutoRMC?
The brick is BS. Uneducated guess by two people.So, what causes the brick ?. Do you think it's worth upgrading, will Atmosphere still work without using AutoRMC?
So, I just have to be more cautious when modifying my console.Atmo does not support 8.0 yet, so updating now will leave you without CFW. Unless you want to mess with downgrading and if you didn't prepare to be able to downgrade it's a headache. Just wait till they have a working version.
You always have to be. Just have a full backup and you should be fine for the most.So, I just have to be more cautious when modifying my console.
In a nutshell yes.So, I just have to be more cautious when modifying my console.