-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Hardware and Upgrade Questions
- envy x360 15-cp0053cl screen/shutdown issues

Create an account on the HP Community to personalize your profile and ask a question
03-29-2021 05:45 PM
Hello. My laptop has started having issues with the touchscreen and shutting off ... and they started happening at the same time. I suspect the system is waiting for a signal that everything is shutdown before powering off and it's not getting it from some device that draws power along that connector. The touchscreen has also just completely stopped working.
I suspect the video cable that runs from the motherboard through the hinge and into the controller board is at fault... It's the 30 pin connector with touchscreen.
I'm unable to find the part number for this part to order... Is it available separately or do I need to try and order a full screen at a cost over half the cost of the laptop itself?
Also, a part number for the rubber feet (or a link to them) would be awesome.. thanks.
03-29-2021 10:14 PM
Please use the following list
https://partsurfer.hp.com/Search.aspx?searchText=6EH45UA
As you can see, most of them are N/A from HP Part store, you have to use part # to search online, including eBay
Regards.
***
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
04-04-2021 05:58 PM
The cable isn't listed on that parts list with a part #
That said, I pulled the glass today on my system and noticed that the second connector (the small one, not the30 pin connector) had somehow backed itself out of the socket. I reseated it and not only does my touchscreen work again, it shuts down properly again. It must have been waiting for the "device has been shut down " signal... and never got it.