crwdns2933423:0crwdne2933423:0

{A1706 / EMC 3071}—Released in June 2017, this 13" Macbook Pro features Kaby Lake processors up to 3.5 GHz Core i7 with Turbo Boost up to 4.0 GHz.

white touch bar problem

Hi can you help me cut corners cost wise I aim to do the repair my self but want advice please.

so my Mac Book Pro has a touch bar issue the display on the bar is now permanently white but after a short period it used to fliker with sqaures.

the touch bar functions are still working so does the fingerprint id too.

but the display is white is there a way to fix this with out replacing the hole touch touch bar Bar please

crwdns2934081:0crwdne2934081:0 crwdns2934083:0crwdne2934083:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2933313:01crwdne2933313:0

crwdns2934051:0crwdne2934051:0

So the question is… Is the TouchBar or the cable between the logic board and the TouchBar the issue?

You could try replacing the cable MacBook Pro 13" Retina (Late 2016-2019) Touch Bar Display Cable it’s a fair amount of work. Otherwise the TouchBar OLED panel it’s self is bad MacBook Pro 13" Retina (Late 2016-2017) Touch Bar Assembly which is much harder to replace.

crwdns2886500:0Replace the cable that connects the display portion of the touch bar to the logic board.crwdne2886500:0

crwdns2934075:0crwdne2934075:0

MacBook Pro 13" Retina (Late 2016-2019) Touch Bar Display Cable

$9.99

crwdns2886500:0Replace a damaged or malfunctioning touch bar assembly compatible with a Late 2016 or 2017 13" MacBook Pro with Retina display.crwdne2886500:0

crwdns2934075:0crwdne2934075:0

MacBook Pro 13" Retina (Late 2016-2017) Touch Bar Assembly

$54.99

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0

crwdns2944067:03crwdne2944067:0:

Hi many thanks for getting back to me. So I suppose it's a process of elimination thing. ill get a new cable first fingers crossed its only the cable.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

Any luck fixing this issue?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

@shermyg - I'm sure bseth got things working, likely just needed a new cable and the driver logic within it likely failed.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

bseth1975 crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 1

crwdns2936753:07crwdne2936753:0 4

crwdns2936753:030crwdne2936753:0 21

crwdns2942667:0crwdne2942667:0 606