-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diagnostic tools don't start MacBook5,2 Mac-F22788AA #9
Comments
Similar issue with I downloaded and mounted |
Same thing with MacBookPro6,2 Mac-F22586C8 MBP Mid-2010. |
Same thing with iMac6,1 Mac-F4218FC8 |
@aristidesfl
Apple Hardware Test does not use
@freetonik, I verify 022-4597-A.dmg is a working distribution of AHT for MacBookPro6,2 Mac-F22586C8. Did you bless parent directory of .diagnostics? example: |
@3ji7ja0jb9c |
I have same issue with MacBookPro5,5 ... I followed those steps many times, to be sure its not working. (For example even tried different startup shortcuts, which works fine, to see if i am not pressing keys wrongly :) but nothing ...) |
@Jones-S Use just about any USB MSC or IEEE 1394 SBP-2, block size 512 octet, should work. In this example, /dev/rdisk1. Try:
A suggestion how better to style this instruction is appreciated. |
um, maybe it's because I'm a dolt, but in downloading any of these core services folders, there's nothing in those folders to put in my current core services folder. No .diagnostics file. What am I missing here? (with apologies in advance if I am betraying my obtuseness) I've downloaded 022-4294 and -4297 both. Neither have the .diagnostics file in the core services folder. |
Similar issue here getting it to work on Mac Pro 1,1. I restored the diagnostics by doing (in Unix shell): cp -r [foo]/System/Library/CoreServices/.diagnostics /System/Library/CoreServices/. ... where 'foo" is the dmg file downloaded here and mounted. But when I restart with 'D' depressed, the machine just starts up normally. No special diagnostic environment. |
What worked much better for me was to create a bootable thumb-drive, as described here: http://rivenbyfive.blogspot.co.uk/2012/01/download-and-run-apple-hardware-test.html The short version is: 1. Download the dmg for your model (the collection of links here is still VERY useful in this regard). 2. Copy the System folder to a clean USB drive, and copy the diags.efi file to its root level. 3. Bless the USB drive in mount mode and reboot (as described in #6 of the link). |
I had the same issue with a MacPro5,1 with a USB drive. The USB drive would boot into AHT without issue. I would then get to the language selector where I would select English. It would then either hang immediately after clicking the OK button, but not enter the actual AHT dialog, or it would sometimes enter the actual AHT dialog only to hang there. I could not get it to probe the hardware so it could run. I have another MacPro2,1 (or MacPro3,1) to test with so I added the rest of the Mac Pro AHT images to my AHT USB drive, which worked normally. So now I went back to the MacPro5,1 and now AHT works normally. |
This is how I solved it. (No need bootable USB but Highly Risky) System information:
|
Any Idea? |
I followed GordonWei's instructions and it did not enter AHT as he indicates in Step 5. After pressing D, it entered Internet Recovery, asked for my wifi network and password, went back to the internet recovery screen for a moment, and then went to a black screen saying only "cannot load efi/drivers/testsupport.efi". This is the same exact thing it did before I downloaded the correct DMG and followed the instructions. This whole procedure made no difference. I double-checked to make sure I did everything right, downloaded the right DMG for my computer and followed the instructions. |
I highly recommend using a USB drive to do the diagnostics. It seems to be the most reliable on all of my Mac testing. But please note that you have to start USB Diagnostics by pressing the |
Downloaded from the right link, added CoreServices/.dianostics to /Library, restarted, pressed D, the screen stays grey longer than usual, but eventually it just boots normally. Is there something missing?
The text was updated successfully, but these errors were encountered: