Hi everyone.
I have MacBook Pro A1708 with a confusing issue.
The laptop doesn't turn on. Strangely, the trackpad clicks and fan spins. Caps lock doesn't turn on and no chime.
Initially, the amp meter didn't turn on at all on one of the usb c ports. On the other port, I got 20V and half an amp tho (no battery connected).
I replaced the bad CD3215 chip and now it works as well. Both ports turn on with same amp readings.
The initial issue however remains.
No boot. No backlight. No chime. No keyboard. Only signs of life are clickable trackpad and fan spin.
Amp meter shows 20V and goes up to 0.55 amp and after a few seconds stays at 0.49 amp.
With battery I get same results but ofc since the battery is charging, the amo meter goes to 2.1 amp.
Disconnected trackpad with no luck ofc. SMC reset using keyboard works as the amp goes to zero and back to half an amp again.
Board history not known but the bored was in pristine condition. No marks of water damage or corrosion. No prior repairs most probably as well.
Bad CPU maybe? Anyways to confirm?
I have MacBook Pro A1708 with a confusing issue.
The laptop doesn't turn on. Strangely, the trackpad clicks and fan spins. Caps lock doesn't turn on and no chime.
Initially, the amp meter didn't turn on at all on one of the usb c ports. On the other port, I got 20V and half an amp tho (no battery connected).
I replaced the bad CD3215 chip and now it works as well. Both ports turn on with same amp readings.
The initial issue however remains.
No boot. No backlight. No chime. No keyboard. Only signs of life are clickable trackpad and fan spin.
Amp meter shows 20V and goes up to 0.55 amp and after a few seconds stays at 0.49 amp.
With battery I get same results but ofc since the battery is charging, the amo meter goes to 2.1 amp.
Disconnected trackpad with no luck ofc. SMC reset using keyboard works as the amp goes to zero and back to half an amp again.
Board history not known but the bored was in pristine condition. No marks of water damage or corrosion. No prior repairs most probably as well.
Bad CPU maybe? Anyways to confirm?
Comment