crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Darren

crwdns2947189:0crwdne2947189:0:

Suggestions on a good approach to fault finding a dead iPhone PCB

crwdns2934249:0crwdne2934249:0:

Hi all

I know fault finding no power faults is a well trodden path, and the cause can be wide and varied. However, after recently fault finding several dead iphone pcbs I want to improve my approach from my current almost random plan of attack. I’ve done a lot of searching online and on this forum as I thought I’d find a best practice method, I appreciate that there is no holy grail approach but I thought I could gather a few ideas together which may be interesting and may help others that stumble across this thread. I know there’s probably a sensible place to stop and give up, but lets say in a situation where there was critical data required from the device and time, effort and replacement parts weren’t an issue, what are peoples thoughts on the best logical approach (assuming there’s no background on what’s wrong with the device).

My current approach:-

# Remove all shields and visually inspect the PCB.
# Connect to DCPS and fault find any shorts/partial shorts that are getting hot. If there’s no short or partial short is not getting hot (say less than 300ma) then continue with step 3.
# Check PP_VCC_Main & PP1V8_ALWAYS for voltage
# Check all main power rails individually and then all sub power rails for a short.
# Check diode reading of each power rail to a known good board (if available)
# Replace Tigris (this is where it becomes random)
# Replace Tristar
# Replace Baseband

Hopefully I can develop this into a good logical approach.

Thanks for reading and thoughts!

crwdns2866306:0crwdne2866306:0:

Electronics Skills

crwdns2915684:0crwdne2915684:0:

open

crwdns2934251:0crwdne2934251:0:

+577848

crwdns2934241:0crwdne2934241:0 Darren

crwdns2947189:0crwdne2947189:0:

Suggestions on a good approach to fault finding a dead iPhone PCB

crwdns2934249:0crwdne2934249:0:

Hi all

I know fault finding no power faults is a well trodden path, and the cause can be wide and varied. However, after recently fault finding several dead iphone pcbs I want to improve my approach from my current almost random plan of attack. I’ve done a lot of searching online and on this forum as I thought I’d find a best practice method, I appreciate that there is no holy grail approach but I thought I could gather a few ideas together which may be interesting and may help others that stumble across this thread. I know there’s probably a sensible place to stop and give up, but lets say in a situation where there was critical data required from the device and time, effort and replacement parts weren’t an issue, what are peoples thoughts on the best logical approach (assuming there’s no background on what’s wrong with the device).

My current approach:-

# Remove all shields and visually inspect the PCB.
# Connect to DCPS and fault find any shorts/partial shorts that are getting hot. If there’s no short or partial short is not getting hot (say less than 300ma) then continue with step 3.
# Check PP_VCC_Main & PP1V8_ALWAYS for voltage
# Check all main power rails individually and then all sub power rails for a short.
# Check diode reading of each power rail to a known good board (if available)
# Replace Tigris (this is where it becomes random)
# Replace Tristar
# Replace Baseband

Hopefully I can develop this into a good logical approach.

Thanks for reading and thoughts!

crwdns2866306:0crwdne2866306:0:

Electronics Skills

crwdns2915684:0crwdne2915684:0:

open