New answers tagged boot
1
Thanks to this answer https://apple.stackexchange.com/a/295805/300460 from https://apple.stackexchange.com/users/251859/langlangc. I followed it when I had this issue in last Sep2018. However I struggled a bit to figure out the exact delta steps to be performed for the second time, when I came across the same issue yesterday again when I did the OSX Security ...
1
Considering the age of your MacBook (it's 12 or so years old), it's highly likely your hard drive has died.
There is also the possibility that something else could be wrong with your MacBook, so there is the risk that you'll end up spending money on a new hard drive only to find that you still run into problems.
However, if this is a MacBook that you've ...
1
From Windows, you can open a Command Prompt window as an Administrator. Next, you could enter the commands given below to change disk0s2 to an APFS type.
diskpart
select disk 0
select partition 2
set id=7C3457EF-0000-11AA-AA11-00306543ECAC override
gpt attributes=0x0000000000000000
exit
Update
The output from dd if=/dev/disk0s2 count=1 bs=512 | vis -c ...
1
Try discharging the battery (plug in an iPhone or iPad or whatever and drain the battery by charging it). Then reset the PRAM and SMC. Finally start up in verbose mode (hold V while booting) and try to capture what gets displayed (iPhone or iPad video works well).
After the battery has been effectively dead for a day (it should be dead enough that when you ...
1
Use Startup Manager
When you use Startup Manager to select a startup disk, your Mac starts up from that disk once, then returns to using the disk selected in Startup Disk preferences.
Press and hold the option key immediately after turning on or restarting your Mac.
Release the Option key when you see the Startup Manager window.
If your Mac is protected ...
0
There is a very good possibility that if you had a external drive with a version of OS X (macOS) that is compatible with your Mac, then your Mac would boot from this external drive. The reason is that when the default operating system is not bootable, then the firmware will try to find an alternate operating system to boot. This would happen without you ...
3
Unless you jailbreak the phone, no...can't be done.
The startup screen even ignores the accessibility settings.
0
You put in your answer that you entered the command gpt -r show disk0, but the screen shots you posted do not reflect this. The funny thing is that the output from this command would have provided the information needed to fix your Mac. Unfortunately, entering this command now would be pointless, since you have destroyed the needed values when you ...
1
The Boot Camp Assistant will not accept Windows 7 because your Mac is a 2015 model. Starting in 2015, Apple eliminated including a legacy BIOS with the Mac firmware. Windows 7 can only BIOS boot and therefore can not be installed on your Mac. It does not matter how you create the flash drive or what method you use in an attempt to install.
1
From what I understand, I think that this is a trackpad driver issue. Try booting up while holding the Command and R keys, and then re-installing macOS.
If that doesn't fix it, then you may need to install a new trackpad. You can find instructions on how to do this here. As for buying a trackpad, you can probably find one on eBay here, like this one.
1
I am relieved (and embarrassed) to report that the fault was a poor USB connection between the wired keyboard and the iMac USB port. A little unplugging and re-plugging solved everything. The iMac now boots correctly, in whatever mode I select.
The keyboard connection was only faulty in the computer's un-booted state. When booted, the computer accepted ...
1
I think I had one such MacBook Air. was permanently resolved by replacing the LCD assembly at AASP as the warranty was really fresh - it did essentially qualify for DOA (wtf? - still do not know the possible answer to that)
Semi-permanent / temporal resolution/workaround was to get the system in a target mode ([T] at startup and connect with a Thunderbolt ...
8
According to everymac.com, your Mac is a 2006 model which was discontinued January 8, 2008. (I made the assumption 2.66QX means 2.66 GHz Quad Core Xeon) This model originally was designed to run OS X 10.4.7. Since the
Mac OS X v10.6.2 Update is dated Nov 9, 2009, I doubt the disc you have is the correct one for this model Mac.
The OS X 10.7.5 (Lion) was ...
3
I would guess 10.6.2 would be just fine to boot most MacPro with that model, so you might have a hardware issue or bad DVD.
More specifically, there are 8 models with A1186 - so you might need to try OS between 10.4 but most of them would work with 10.6.8 - so I’d start with any 10.6 media you can get your hands on if you can’t get a serial number or more ...
1
Macs can usually only go back to the version each one shipped with. So even if the model can go back to 10.13 if it was bought earlier, if yours had 10.14 factory installed, it will refuse to go back to 10.13.
However, there are ways around that.
Besides making sure that you create install media with the complete install (5-6 GB, not 20MB, as mentioned by ...
3
What you have posted in your comments to your question, the download of High Sierra from the App Store is only c. 20mb. I have High Sierra on a iMac (21.5-inch, Mid 2011) and Get Info on my High Sierra download shows a size of 22,697,095 bytes (15.1 MB on disk). However, when downloading High Sierra from a iMac (21.5-inch, Late 2013) running Mojave results ...
1
I have found the problem, the BIOS firmware was badly corrupt from a failed macOS update, i had to fix it hardware removing the BIOS chip and flashing it again, now it's working perfectly!
0
It is possible but not all the time. Here's why:
Latest macOS might have features that won't run on the older Macs(hardware wise. eg: fingerprint reader on new MacBook but older macOS won't have support for that)
Drivers might be outdated
The bootloader and other parts of the hardware might outright restrict this due to security issues.
Is it possible to ...
0
@Imael Oooo that is serious. I have had this problem with 10.12, which I believe stemmed from I installed an old Epsilon print driver and the kext file reaped havoc, causing exactly the error you described.
To resolve this I booted into the start-up/recovery drive, (turn the machine on and hit "Alt") and opened Terminal. I then went to the two system ...
1
I was able to fix this by using a bootable Ubuntu usb to boot my system, and choosing the option for formatting the SSD. Then after installing Ubuntu I was able to use a bootable MacOS usb drive to reinstall MacOS Mojave successfully.
As mentioned above, absolutely nothing was working including the disk utility, internet recovery, or using a bootable MacOS ...
1
Doesn't appear to be a direct way to do this. Part of the problem is that your changes to the NVRAM, if you were to clear it (nvram -c), will not take effect until after a reboot.
You could try this method which will perform a side-by-side diff of the contents of NVRAM prior to running a nvram -c.
For example:
$ sdiff <(nvram -xp) <(nvram -c &&...
Top 50 recent answers are included
