So not sure if we will be able to get help on this. But I thought I might as well ask hoping for some ideas on how best to proceed.
1. Logic Board came in for Data Recovery due to Liquid Damage
2. Most Power & Data Lines were repaired, found shorting on CPU
3. We have now successfully replaced the CPU from another A2251 iCloud Locked Board, Tested and Working
4. Gets 20V
4. Board goes into DFU and have attempted to Revive (not Restore), gives Error 4042
5. 20V-100mA, and power resets after 6 seconds, PP3V3_G3H
PP5VG3S_EN - Signal Missing from PMU - PMU has been replaced from a working motherboard
No Shorting, All Diode Values are Normal in comparison with another A2251.
So we are a little stuck and need some ideas. I'm not sure if the Logic Board is still faulty somewhere OR if the swapped CPU PCH is causing issues.
Colleague had done some research previously and mentioned that maybe some PCH data (ME Firmware) is stored on the NAND. Therefore, maybe replacing the CPU might not work at all. Have your team successfully recovered data in a situation like this previously? (Ofcourse, not two scenarios are the same) - Any, absolutely any advice is appreciated!
1. Logic Board came in for Data Recovery due to Liquid Damage
2. Most Power & Data Lines were repaired, found shorting on CPU
3. We have now successfully replaced the CPU from another A2251 iCloud Locked Board, Tested and Working
4. Gets 20V
4. Board goes into DFU and have attempted to Revive (not Restore), gives Error 4042
5. 20V-100mA, and power resets after 6 seconds, PP3V3_G3H
PP5VG3S_EN - Signal Missing from PMU - PMU has been replaced from a working motherboard
No Shorting, All Diode Values are Normal in comparison with another A2251.
So we are a little stuck and need some ideas. I'm not sure if the Logic Board is still faulty somewhere OR if the swapped CPU PCH is causing issues.
Colleague had done some research previously and mentioned that maybe some PCH data (ME Firmware) is stored on the NAND. Therefore, maybe replacing the CPU might not work at all. Have your team successfully recovered data in a situation like this previously? (Ofcourse, not two scenarios are the same) - Any, absolutely any advice is appreciated!
