For $29/mo, we provide access to advanced level technicians who will answer your questions on any Macbook board related matter to the best of their knowledge promptly & walk you through how to solve your problem so you can deliver a working board to your customer.
Diode mode on J4401/2, traces and related components are all fine, also inspected and cleaned J9600 but same issue, installing the requiered update fails asking for the update again.
After replacing UB300 and UB400 mac starts fine, but now I have critical software error, I isolated this error to the board since it also happens with just the LCD and power cable connected, normally I replace U4200 and most of the time this fixes it, but not on this one.
Yes OG 87w and OG cable, same thing with a different charger.
Checked U7000 resistors and diode mode around but all seem ok.
Also replaced U5000 but same thing.
If I leave the board alone for a long while the board will start but only that one time, if I unplug and plug again the problem...
This board did boost to 20V a few times and started up in my bench alone a few times but not it is back to the original problem, ports only take 5V and PPBUS stays at 0V, clean board.
R7020 5V in all pads
U7000 replaced already from same board just in case
Q7030 and Q7040 replaced and same.
Thanks, UF980 was shorted, replaced it and short is gone, all LDO lines are on par with with board and surrounding components also measure same as good board, but I still get the same behavior bad port 0.021A other ports 0.250A no restarts, I installed another UF980 and also UG400 but same thing...
Board came with a short on PP5V_S2SW_USBC23 both UG400 and UG800 were shorted, after replacing both of those from same donating board I now get 5V on all ports, but in the port where I replaced UG400 if I connect the power cable there PPBUS is 2V the other ports give me 12V PPBUS, I tried 2...
The reason I am here is because that is what I was expecting, but not in this model, I tried with another one that is also working, but same problem. I will report back if I get any findings.
Clean board, when you try to use the keyboard to move the volume up or down the audio icons comes up with a forbidden sign.
I already replaced the Audio IC U6300 and have tried with the audio jack connected and disconnected and same thing.
I'm trying to put a MacBook Air M4 in DFU mode using the onboard pads SWV011 (SOC_FORCE_DFU_DBG to PP1V25_S2) following the same steps here https://logi.wiki/index.php/DFU_Mode_Restore_(Macs)#How_to_put_Mac_into_the_DFU_mode but no luck, Im doing this with board alone on bench, using both power...
Board had a little bit of corrosion 3 ports restart at 5V every few seconds except U3100 that one stays at 5V I replaced U3100 3 times and same thing, also only on that port PP1V1_UPC_XA_LDO_BMC is 0V, PPBUS is 0V, I also replaced U7000 but same thing.
Clean board, USB-C port had some corrosion, I replaced it now I get 20V with board alone or with everything connected, however Mac wont charge, battery is recognized and percentage is shown, but no charge, tried new battery and same problem.
Client states that Mac had liquid damage but after inspecting the board and all other components all looks clean.
Board alone stays at 20V and 0.200A but nothing happens
With battery and trackpad connected I get 20V and around 1A but not USB activity or power.
Wont enter DFU
This Mac drove me crazy, even changed the T2 chip and after some more testing and research I found out that the problem is the RAM, lots of this model Mac and some other newer ones are having the same issue, the symptoms described here along with and OS error message about hash mismatch have to...
Clean board, fan spins fast right before it reboots this happens after 2-5 minutes of it being turn on.
Installed clean OS after T2 restore, same problem and it was very difficult to install OS since it will error out, only completed installation after several tries.
Installed new NANDs and...
But only one port is cycling, all others stay at 5V solid.
All SSD lines are not shorted.
Replaced U9080 and same thing, could this be NAND problem youre saying?