TX Presents SX Installer v2.0.0 - Now with Firmware Upgrade/Downgrade Support

The problem has been fixed. AutoRCM was installed, and the latest SX OS wasn't being used.

What are the first nine or ten digits of the serial number?

I'm not sure what you're talking about. With AutoRCM somehow installed onto a patched system, the system will refuse to boot into anything other than RCM, and fusee gelee won't work.

 

Payloads such as hekate aren't signed, rcm still should boot signed code.

 

My serial is Xaj40063963799 but i have checked on div sites, and they claimed it is a patched unit.. So stupid me

 

Definitely patched.

 

Unless they a

I know could they be wrong?? Haha

 

You're really arguing that it's a soft brick until you plug in your dongle?

BTW, I just dug out my switch and the battery was flat. After five minutes charge I was able to use the dongle to boot, I used to hear scare stories that I'd need to charge the switch for days as autoRCM triggered slow battery charging. I don't believe those scare stories either anymore.

 

Or some one want to switch a newer switch for a older one. New is better. hehe

 

It's almost certainly patched. I would recommend getting rid of this Switch and getting an unpatched one. Patched systems on 5.0.0-7.0.1 might be hackable someday in the very distant future, but it would require you to never update and never connect your 7.0.1 Switch to the internet.

There's no publically available "signed code" that would allow you to recover from installing AutoRCM to a patched Switch.

 

They sell those in ebay (cracked screen and only tablet) there are alot of replacement screens as well.

 

It's a matter of perspective. Ten minutes ago, someone in this thread accidentally installed AutoRCM, and since he didn't know what to do, the Switch was bricked and he needed help. Also, if you cannot boot the system without interrupting the bootloop using an exploit, that's arguably a brick.

I'm not particularly interested in arguing semantics. I use AutoRCM and wouldn't consider my Switch bricked, but I acknowledge that AutoRCM technically works by creating a softbrick. AutoRCM solely works by causing BCT-verification to fail. Without fusee gelee (e.g. on ipatched systems), that's a brick.

My main reason for my response to your post was to address your comment about RCM. AutoRCM is safe on unpatched systems. I'm not arguing it isn't.

 

Sell that one and get something like this

https://www.ebay.com/itm/Nintendo-Switch-Tablet-Screen-Console-Only-UNPATCHED/112584335673?

 

Sure, but not knowing how to start something doesn't make it a brick. Battery flat != brick either.

 

As I said, it's a matter of perspective.

By your logic, any repairable software brick isn't a brick.

 

Normally in a TX post fanboys would argue, but here everyone argues about RCM bricks

 

Cool, ask Nintendo to sign your payload, and let us know how you get on.

 

Unnecesary salt.

Also only Nvidia signed code should work.

 

All humans need salt to survive. You're right, asking NVidia instead of Nintendo should go much better.

 

I NEED MORE SALT IN MY POPCORN!!

And Nintendo signed code wouldn't work with iPatched units, Nintendo signed codes only will work with Horizon.