-
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.Subscribe Now
A2289 2020 13" MBP with Logic Board 820-01987
- Thread starter Thomas
- Start date
Data data can be recovered in DFU mode by Apple authorized service.
If DFU revive can be completed, that is viable way for data recovery.
Don't try restore, as it erase data!
If DFU revive can be completed, that is viable way for data recovery.
Don't try restore, as it erase data!
Thomas
Member
I’m confident the board will accept a DFU revive.
What I’m trying to determine is the correct repair path for data recovery. Should I be transferring the T2, T2 ROM, and NANDs to another board, or replacing the CPU?
I’ve tried both approaches in the past, but I always end up with the same result. It feels like there’s an additional step I’m missing. Do you happen to know what that step might be?
A DFU revive after the component transfers doesn’t seem to clear or rebuild the ME region properly. However, if I perform a DFU restore, the board functions perfectly afterward—but, of course, all of the data is lost.
What I’m trying to determine is the correct repair path for data recovery. Should I be transferring the T2, T2 ROM, and NANDs to another board, or replacing the CPU?
I’ve tried both approaches in the past, but I always end up with the same result. It feels like there’s an additional step I’m missing. Do you happen to know what that step might be?
A DFU revive after the component transfers doesn’t seem to clear or rebuild the ME region properly. However, if I perform a DFU restore, the board functions perfectly afterward—but, of course, all of the data is lost.
Successfully completed DFU revive can confirm data is safe.
But failed DFU revive wouldn't mean data is lost.
Just contact authorized service and try to get data out in DFU mode.
But failed DFU revive wouldn't mean data is lost.
Just contact authorized service and try to get data out in DFU mode.
Thomas
Member
I'm not looking to send it to an authorized service center. I'm trying to understand the process so I can recover the data myself.
I've already tried moving the T2, T2 ROM, and NANDs, as well as replacing the CPU. No matter which method I use, I end up in the same place. A DFU revive doesn't seem to fix it, but a DFU restore brings the board back to life at the expense of the data.
What I'm trying to figure out is what step I'm missing. Is there something else that needs to be transferred, paired, programmed, or rebuilt after the swaps? Is there a firmware region that needs to be repaired or regenerated before the board will boot with the original data intact?
What's interesting is that I only seem to run into this on the A2159, A2179, and A1932 models. Basically anything where the CPU and PCH are combined into a single package. I don't have this issue on the A1990 or A2141 because the CPU and PCH are separate chips.
I'm not looking for DFU instructions or recommendations to contact Apple. I'm looking for input from someone who has actually solved this problem. I've already been through the obvious troubleshooting steps and continue to get the same result, which makes me think there's an additional step involved that I'm missing.
Have you personally and successfully recovered data in this exact scenario? If so, what was the missing step? If not, that's completely fine, but I'd appreciate hearing from someone who has actually done it. I'm trying to understand the process, not guess my way through it.
I've already tried moving the T2, T2 ROM, and NANDs, as well as replacing the CPU. No matter which method I use, I end up in the same place. A DFU revive doesn't seem to fix it, but a DFU restore brings the board back to life at the expense of the data.
What I'm trying to figure out is what step I'm missing. Is there something else that needs to be transferred, paired, programmed, or rebuilt after the swaps? Is there a firmware region that needs to be repaired or regenerated before the board will boot with the original data intact?
What's interesting is that I only seem to run into this on the A2159, A2179, and A1932 models. Basically anything where the CPU and PCH are combined into a single package. I don't have this issue on the A1990 or A2141 because the CPU and PCH are separate chips.
I'm not looking for DFU instructions or recommendations to contact Apple. I'm looking for input from someone who has actually solved this problem. I've already been through the obvious troubleshooting steps and continue to get the same result, which makes me think there's an additional step involved that I'm missing.
Have you personally and successfully recovered data in this exact scenario? If so, what was the missing step? If not, that's completely fine, but I'd appreciate hearing from someone who has actually done it. I'm trying to understand the process, not guess my way through it.