Hacking [Confirmed Untrue] Upcoming 8.0 fw bricking systems with auto rcm

  • Thread starter Thread starter oblid
  • Start date Start date
  • Views Views 30,882
  • Replies Replies 174
  • Likes Likes 1
I'd sooner bet this is just cover for the fact that by all indication, the next update will screw with their update plans due to the need to once again figure out how to get the keys or brute force them out of Sept (assuming N/Scires change some things to fix up possible key-leaks to brute forcing).
 
  • Like
Reactions: PHiLiPZ
It's from a VIP user, not officially announced by TX. But drama is fun, back on after 2 weeks.
Well it's certainly a great start from them after only being online for a few hours :^)

--------------------- MERGED ---------------------------

I'd sooner bet this is just cover for the fact that by all indication, the next update will screw with their update plans due to the need to once again figure out how to get the keys or brute force them out of Sept (assuming N/Scires change some things to fix up possible key-leaks to brute forcing).
The community have identified a bug that TX (likely) used to glitch Sept. It'll be a lot harder for them now if that is true.
 
TX 'vip members' aren't even staff, let alone have unreleased dev firmware. TX itself is not competent enough to analyze said firrmware. AutoRCM is removable and RCM itself is a hardware mode. The worst case scenario is having to use a jig to boot unmodified 8.X. The real world worse case scenario is modifying the firmware to restore AutoRCM functionality.
 
Last edited by blahblah,
  • Like
Reactions: Deleted User
Nah. Devkits and testkits get updates super early. Even if it did leak it’d be impossible to run on retail
Atleast analyze it would be intresting. I wonder how the anti-cfw implementation will be. Since they need to try to counter Sept some how.
 

Site & Scene News

Popular threads in this forum