![]() Now the 16 inch is in RECOVERY mode (the T2 chip is in that mode I'm guessing, MB it self won't boot to anything) and I can still put it in DFU mode.īUT, neither reviving or restoring is working!!! every time I try it goes to the same mode, the apple logo shows up, loading goes to the very end (doesn't fill, its filled from the beginning), then I get an AMRestoreErrorDomain error 9. after 5 minutes I hold the power button to shut it down. like I have never heard the fans sound that way. So the 16 inch brought up the apple logo, had a filled loading screen under it, then the screen goes black with the backlight fully on and the fans start at FULL SPEED. The process was happening and then I got an error 9 on Apple Configurator 2 that the operation could not be completed, might be a connection problem with USB host. so I went to revive the T2 chip in DFU mode using my MacBook Pro 13 inch (running Big Sur). Any help would be appreciated!Ĭan't restore/revive MacBook Pro 16 inch using Apple Configurator 2 My MacBook Pro 16 inch (running Catalina) T2 chip was having a problem with the bridgeOS not allowing me to install any MacOS version, I couldn't update nor downgrade to anything. I am so desperate that I am even willing to beg for help on a forum. I've scoured all of the Mac Forums and videos about reviving and restoring and tried it all, nothing has worked. No life on the computer and the same errors persist. I've tried all the keyboard combinations to restart it and to safe boot it and everything it! Nothing works. It comes up into recover mode on configurator after attempting to restore or revive it. I also tried Restoring it and I get the same errors. Putting the bricked mac into DFU mode again from recovery each time I tried to revive it. ![]() I've tried it all, restating the host device, trying different USB-C cables ensuring that they are plugged into the correct ports. (AMRestoreErrorDomain error 75 - Failed to handle message type StatusMsg (Missing data volume)) " After wiping away my tears I initiated it again and would get the same error and then another error every now and then Error 75 "The operation couldn’t be completed. My eyes were glued in anticipation of my Macbook coming back to life, however, my efforts were not rewarded and a heart shattering error appeared. I then proceeded to begin the revive and watched that lovely status bar flow along left to right. "Oh Goody" I thought thinking that my woes were behind me and that all would be smooth sailing from there. So, with the help of YouTube University I put it into DFU mode and sure enough it worked and came up right away on the host mac as being in DFU mode. Sure enough it came right up in recovery mode on configurator. boy was I wrong! I installed Configurator on the host Macbook Pro (2020 13") and connected the computers via a USB C cable. So here I am all happy thinking that we will just revive it and reinstall the os and be off down the road. I was like "oh good we have another mac that can do that!". I looked it up and found that you can "revive" it with another mac. ![]() I went to sleep and when I got up in the morning went to use it and it was entirely unresponsive. So I tried repairing the disc from disc utility and reinstalling the os from disc utility and it was good for a day so I figured it was all fixed. It would crash and then I was having a difficult time getting it to power on again. Well I just updated it again and it came back with a vengeance. It would do this continually and then I was able to update it again and it got better. My Macbook Pro A1990 was having issues after updating (I think it was in November) it a while back, it would crash and then I could turn it on again. ![]() Macbook Pro T2 2018 15" A1990 Bricked After Update - Won't Turn On Hey guys I need help.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |