Aquinus
Resident Wat-man
- Joined
- Jan 28, 2012
- Messages
- 13,147 (2.95/day)
- Location
- Concord, NH, USA
System Name | Apollo |
---|---|
Processor | Intel Core i9 9880H |
Motherboard | Some proprietary Apple thing. |
Memory | 64GB DDR4-2667 |
Video Card(s) | AMD Radeon Pro 5600M, 8GB HBM2 |
Storage | 1TB Apple NVMe, 4TB External |
Display(s) | Laptop @ 3072x1920 + 2x LG 5k Ultrafine TB3 displays |
Case | MacBook Pro (16", 2019) |
Audio Device(s) | AirPods Pro, Sennheiser HD 380s w/ FIIO Alpen 2, or Logitech 2.1 Speakers |
Power Supply | 96w Power Adapter |
Mouse | Logitech MX Master 3 |
Keyboard | Logitech G915, GL Clicky |
Software | MacOS 12.1 |
Dude. The FX initially worked as he said on "initial boot and it got detected as an 8320" - Reading comprehension dude
Exactly, then he flashed to 1.70 and it appeared to be bricked immediately after restarting. You can't tell me that isn't coincidence because it's a dead giveaway of a bad flash. Not to say that he did it wrong but that it's possible for EEPROM programming to fail and it's recommended not to do it too often since it (like flash,) has limited write longevity.
My guess would be that the flash didn't fully work, in that case it's a defect with the BIOS chip which would require at least replacing the BIOS chip with one with a working version of the BIOS assuming the bad flash didn't do anything permanent.