Search results

Bad cable can manifest in many ways. I didn't see you mention it, so wanted to rule it out first. Delayed chime could be a BIOS issue. Can you try a new BIOS? You can hot-swap a chip over for testing purposes (only!). If chime is normal, then load up a clean BIOS on the old chip. If issue...

Did you try several new SATA/HDD cables? Big issue on the 3115 units, of course.

2informaticos : Not to derail the thread at all, but for general knowledge and future reference: what leads you to suspect the BIOS/ME is the issue in this case? Why would the ME region be related to a random-shutdown issue, without any additional information? Why not suspect bad RAM, faulty...

OK, a bit of an update, as behavior has changed: 1. I think ppbus being 12.6v is fine. I think this might be acceptable, and have found threads previous with the 15" Touchbar boards having ppbus at 12.6v. I'm going to assume this is unrelated to the issue. Also, I don't believe I'd see any sign...

Thanks so much, I appreciate it! The PCH does not get warm, no; nothing gets warm really at all--CPU has a very, very, very slight warmth (5% of normal), but not much at all. Just to confirm: PPBUS_G3H on this model should definitely be 13.1v, correct? And it being 12.6v indicates an...

Also, if someone happens to have a working BIOS dump for the 00820 and could post it, that would be very, very appreciated!

OK, some more measurements: ppbus_g3h: 12.6v (should be 13.1v?) pp3v3_s5: 3.3v pp3v3_g3h: 3.42v pp5v_s5: 5v pp3v0_g3h: 3v pp1v0_sus: 1v pp5v_s4: 0v p5vs4_pgood: 0v pm_slp_s5_l: 0v (primary issue I believe--I can't get into s4 because of no pm_slp_s5_l) s5_pwrgd: 3.3v pp2v9_sysclk: 3v At U7650...

Have an 820-00281 that's actually powering on (fan spins), but then it cuts off soon after. CPU isn't getting very warm (oh no), and ppbus_g3h is at 12.67v, but should be closer to 13.1v I believe. I'd normally suspect a CPU or BIOS issue with these symptoms, but aren't so sure on newer models...

Anything? I just was curious if I could "trust" this battery in a customer repair unit. Don't want to risk it if it might cause issues. Any input appreciated...

Bought a ?genuine? A1417 battery from eBay and it works fine, but it fails the ATV data table test in ASD. Will this cause any functionality or performance issues to be concerned with? Thanks in advance for any help.

Thanks so much. Yes, that's what I figured. I've combed over the board extremely thoroughly and things are "beautiful"--no damage at all. I honestly don't even think the liquid contacted/damaged U5110 originally, but I did note a tiny drop there so replaced anyway (despite U5110 signals all...

Thanks for the help as always. Tried all of that--no DC-In cable, etc. SMC bypass does nothing. We always use 85W Magsafe2 charger. You can assume it won't be an "obvious" or simple thing like wrong charger or JTAG...we know to check all of this. I just want to prevent the preliminary...

JTAG is fine, no liquid near it, but removed just for the hell of it and no change. Charger light constant, no crap under SMC. Confident the issue isn't the SMC, but went ahead and replaced it to eliminate, and no change. Exact same behavior. Suspecting PCH at this point. I also noted that...

Working on a frustrating 820-00165 board with symptoms that are...not ideal: 1. Board powers briefly and all rails (ALL_SYS_PWRGD & VCORE included) pulse for <1 second. 2. Brief fan spin accompanies power pulse, then nothing. Fan stops, all rails after S5 drop completely (S5 rails remain...

Just run AHT and see if fan spins...takes 2 minutes.

SPI ROM chip might be bad/damaged. Try with a new/different chip and see how it does.

8-year-old board + drop + likely torn/snapped traces in board = junk pile. If board was working fine prior to drop, and then stopped after the drop, it's very, very likely damage inside board or underneath CPU/PCH/RAM/etc. You can try a new BIOS...but probably not going to help anything. Check...

Replace those power supplies ASAP and maybe the board will be saved. I bet that CPU is damaged, though. See if the unit crashes coming out of (or during) deep sleep and/or under stress. Liquid to that area is not good news.

Let's take a step back here for just a second. Your original post is confusing in several ways; first, your thread title is "SSD Recall 2016 13" MacBook Pro...". The SSD recall was for non-touchbar models (A1708). You then go on to ask a random, unrelated question about fixing the 2017 13" MBP...

Bad screen from the sounds of it. Try a new one.