BIOS with cleared ME does not helped.
Back to the “original” BIOS (after “breaking” update, i don`t have an earlier one). Changed screen again to an other one (with touch board).
No effect (
Intel(R) MEInfo Version: 11.8.92.4189
Copyright(C) 2005 - 2020, Intel Corporation. All rights reserved.
Intel(R) ME code versions:
BIOS Version 239.871.768
MEBx Version
GbE Version Unknown
Vendor ID 8086
PCH Version 21
FW Version 11.8.94.4494 LP
Security Version (SVN) 3
LMS Version Not Available
MEI Driver Version 2251.4.2.0
Wireless Hardware Version Not Available
Wireless Driver Version Not Available
FW Capabilities 0x11111650
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Intel(R) Precise Touch Technology - PRESENT/ENABLED
Re-key needed False
Platform is re-key capable True
TLS Disabled
Last ME reset reason Power up
Local FWUpdate Disabled
BIOS Config Lock Enabled
GbE Config Lock Enabled
Host Read Access to ME Enabled
Host Write Access to ME Disabled
Host Read Access to EC Disabled
Host Write Access to EC Disabled
SPI Flash ID 1 EF4018
SPI Flash ID 2 Unknown
BIOS boot State Post Boot
OEM ID 00000000-0000-0000-0000-000000000000
Capability Licensing Service Enabled
OEM Tag 0x00000000
Slot 1 Board Manufacturer 0x00000000
Slot 2 System Assembler 0x00000000
Slot 3 Reserved 0x00000000
M3 Autotest Disabled
C-link Status Disabled
Independent Firmware Recovery Disabled
EPID Group ID 0x200F
LSPCON Ports None
5K Ports None
OEM Public Key Hash FPF E411ABDD342436C68E614C7452858EF509339D2B22E338151CEF5ACECFF19740
OEM Public Key Hash ME E411ABDD342436C68E614C7452858EF509339D2B22E338151CEF5ACECFF19740
ACM SVN FPF 0x2
KM SVN FPF 0x2
BSMM SVN FPF 0x0
GuC Encryption Key FPF 0000000000000000000000000000000000000000000000000000000000000000
GuC Encryption Key ME 0000000000000000000000000000000000000000000000000000000000000000
FPF ME
--- --
Force Boot Guard ACM Enabled Enabled
Protect BIOS Environment Enabled Enabled
CPU Debugging Enabled Enabled
BSP Initialization Enabled Enabled
Measured Boot Enabled Enabled
Verified Boot Enabled Enabled
Key Manifest ID 0x1 0x1
Enforcement Policy 0x3 0x3
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - Vendor ID Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - Device ID Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - HW Revision ID Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - FW Revision ID Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - Frame Size Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - Feedback Size Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - Sensor Mode Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - Maximum Number of Touch Point Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - SPI Frequency Not Available
Error 483: Communication error between application and Intel(R) ME module (Intel(R) Precise Technology client).
Touch - SPI I/O Mode Not Available
Seems ME doesn’t see the touch. Either firmware of the touch, maybe connection/ cable, maybe hardware
Been refurbishing Surface Pro’s for years and this is my experience with the Pro 5. I have bricked I do not know how many of the damn touch boards because of that stupid Microsoft forced firmware update. I honestly think this was deliberate to brick these devices so you buy a new one. Whatever this firmware update does it bricks the daughter board that is attached to the touch screen. The board under the L shaped EMI shield on the back of the LCD. The touch screen is still perfectly fine but the actual touch board is dead. I have just been finding them and replacing them on these models. But even if it works for a little bit Windows will force the update and again bricking the touch board again. I have tried to stay away from the Pro 5’s because of this reason.
I have read some posts that say that the update affects the ME region of the UEFI/BIOS or something else and that is not the case as replacing the touch board restores touch until the update is forced again.
I have about 20 of these dead touch boards that will not work on any Surface Pro now not on the 4, 5, 6, or 7. I do notice a 8 pin chip on these boards that I am assuming is where the firmware is stored. I was thinking about doing a dump from a non updated working board and trying to reflash these dead ones to see if I can revive them again. If not it is such a waste.
Welcome to the forum and by sharing this experience, it is indeed a very “strange” behaviour from MS firmware update, i hope it can help users and for sure a shared dump will be handy, all the best.