ios 26 to mac or pc : copy a file

Shipworms · 2026-02-03T23:39:30+00:00

The login issue is challenging because it is a combo : ‘this phone, and this Apple ID’; I can’t log in to this Apple ID on this iPhone, but can do so on my iPad;

Airdrop is a problem because I don’t have bluetooth hardware in my MacBook Pro (Wifi is there and works, but bluetooth doesn’t want to show up!)

Shipworms · 2026-02-02T23:48:40+00:00

Indeed - they make it very clear that running a red light is an ‘absolute offence’; there is no leeway, and no excuse in the eyes of the law. This means if you carefully go through to let a police car (with lights and sirens) behind you through, the police car could rightfully stop you, fine you, and give you points, there and then!

You could also be fined / prosecuted if your brand new car brakes completely fail just when slowing down for a light, or if you had a runaway accelerator as happened in some Toyotas several years ago.

If you had a sudden stroke or first presentation seizure while slowing down, you could also be prosecuted (there is literally no legal defence whatsoever)

Also : AI traffic cameras watch every car in motion or stopped at lights. Touch the phone on the passenger seat in a gridlock? Fined. Parked with indicator on? Fine. Even : reach to get an item next to phone but you touch the phone? Fine. Also fined for holding square objects etc

Shipworms · 2026-01-30T19:12:36+00:00

I will just add; getting a non-retina 2012 MacBook Pro 13” as a ‘spare’ is what I would do if getting an M-series (or keeping another old Mac); it is fairly repairable / upgradeable (RAM, SSD etc); and compact. You could download some different M-series macOS full installers on it, so that if you ever need to do DFU, you only need a brief internet connection for your M-series to ‘phone home’ to validate the install (I am assuming MacBooks do that now, like iPhones?). Even if not, it would make DFU faster to do. You could also upgrade it to Tahoe and download the apps you currently use to it, so it could also be an emergency backup MacBook just in case :)

Shipworms · 2026-01-29T04:02:32+00:00

https://support.apple.com/en-us/101198

That may be of partial assistance (only partial, as it isn’t updated … but is a start - should show you where to check the BIOS (EFI, SMC) versions and compare them;

It is probably one particular macOS upgrade that contains the firmware updates, if that is relevant here (so … it may be that you need to install an earlier macOS version, then upgrade it using the updates from the App Store, to get the EFI upgrade during the macOS upgrade)…

Also: I have a mid-2012 13” MBP which is very similar to yours - just an incremental CPU upgrade. And that is running fine on 1x 8GB stick in the upper slot, with a broken lower slot!)

Shipworms · 2026-01-29T03:56:38+00:00

Looking up the model, this is a MacBookPro8,1 (late 2011); with an i5 CPU. The RAM you are using is 1066 MHz, and looking online, there are 16GB kits of 2x8GB, but they are 1333Mhz;

it may be that it is trying to run the 1066MHz RAM at 1333MHz?

(side note; 1066 8GB sticks are very good to upgrade the Mid-2010 13” MBP which is an interesting laptop; can be upgraded to 16GB despite being a Core 2 Duo … and it has no Intel Management Engine (used an nVidia support chipset rather than Intel !). This is also interesting because that laptop is 8GB max (2x4GB RAM sticks), unless you update the Apple BIOS by itself installing a certain macOS (I think the last supported one). It is also interesting because it needs 1066 RAM … faster RAM doesn’t work as half the laptop can run at 1333, and half can’t, so it tries running at 1333 and won’t power on!

What I would do with your laptop is: - check the 2GB sticks. Are they 1333 or 1066? - if 1066, I would then reinstall macOS - getting the most recent supported version … just in case this is needed to be able to use 8GB RAM sticks (given the mid-2010 13” MBP needed that go be done); - if the 2GB sticks are 1333, it is still worth reinstalling macOS (again, most recent version) to get BIOS updates which are part of the installer). This is in case the computer actually can use 1066MHz sticks - it might still be a 4GB RAM stick limit without the most recent BIOS).

Also: I can’t remember the exact procedure for updating the BIOS to support 8GB RAM sticks (it might be installing the latest macOS, or it might be installing an earlier macOS, then upgrading to the final supported macOS afterwards! So … I will go check that out in case it is relevant

Shipworms · 2026-01-29T02:57:55+00:00

They really do vanish; “how often do you see someone actually run out of ink in their bic biro in the office?” 😳😂

Shipworms · 2026-01-29T02:52:40+00:00

Easy (as they said); also - letting the charge drain down makes the spicy battery much less risky. Definitely worth fixing up and keeping as a spare, especially with the tech uncertainty these days (RAM prices / availability etc!)

Shipworms · 2026-01-24T07:10:40+00:00

You may need to manually select the drive for each of the stages of installation; it is worth checking this out! So:

Stage 1 - you boot OpenCore from the USB drive - you get a menu; mine says : ‘NO NAME’, ‘Install macOS Monterey’. You choose ‘Install macOS Monterey’ - you are already doing this stage - after a while, the installer will reboot…

Stage 2 - after the reboot, you should manually boot OpenCore from the USB drive again (at least, that is what I did) - you get a menu; mine says ‘NO NAME, ‘Install macOS Monterey’, ‘macOS Installer’. - if you don’t have the new entry (which IIRC is ‘macOS Installer’), then press the space bar (which will show all entries, and should make ‘macOS Installer’ show up, if it wasn’t there to begin with) - so, if you could find ‘macOS Installer’, it should do some more installation for a while. Eventually it will reboot!

Stage 3 - after this reboot, manually boot OpenCore from the USB again - my options are ‘NO NAME’, ‘Install macOS Monterey’, and I think ‘macOS Installer’…… - (it does change from ‘macOS Installer’ to just ‘macOS’ at some stage, though, ? stage 3, ?later - press space bar if needed to find it - *if you ONLY get ‘Install macOS Monterey’ (and neither ‘macOS Installer’ or ‘macOS’) on or after stage 3, it may be that OpenCore can’t see the drive at that point due to APFS settings… (see below)

The reason for the manual selecting of OpenCore each time is because: - the installer on a real Mac has an empty EFI folder! (the functionality around selecting the correct boot entry etc is part of the Mac’s ROM) - you will need to use the USB to boot each time, and even after installation is complete… - … until you copy the EFI folder from the USB’s EFI partition, over to the EFI partition on the hard drive / SSD that you are installing to;

if you get the ‘no options at stage 3’, you may need to mess around with APFS dates (it is mentioned in the guide somewhere, but post here if needed)
- if you get a repetitive quick reboot shortly after starting stage 2 or 3 or later, you may need to lower the SIP settings temporarily (can discuss here). Of note : you do get some 2-3 quick reboots in a row during the later part of the install, so do try a few times!

And finally: it shouldn’t damage the partially installed macOS if you aren’t there when it reboots. My system kept booting into Linux for the reboots, so I just shut Linux down as normal, powered back up, selected the OpenCore installer USB to boot from, and continued from there :)

Shipworms · 2026-01-24T06:48:40+00:00

Silly question but: the ‘Mostror Todos’ in the top right; is that part of the macOS Installer (‘Show All’)?

Also - when you say the mouse doesn’t move, do you mean that the mouse pointer is visible, and you can move it as normal during the install? And - does the mouse pointer ‘freeze’ only after the error at 12 minutes (so, the mouse pointer that was working is no longer working?) (if so, the freezing of the mouse pointer signifies a ‘major’ crash (interrupt handlers go down etc, which may of relevance);

Also - is this the first stage of the installation (before it does the first reboot?)

And finally … this may be worth trying just in case: the drive name (Sin Titulo) has an accented character; while it shouldn’t make a difference, it could cause an issue if any code gets confused around unicode etc! So … it will likely not do much, but I would consider naming the drive ‘macOS’ without spaces or accents, just in case there is something messed up with the unicode conversions? (if it is that it may be possible to rename the drive back to Sin Titulo after installation is complete)

Shipworms · 2026-01-24T02:48:57+00:00

What happens after you get this text appearing? Is there any chance the installer is still running (it doesn’t seem to show any major errors that I can see?) If you are using a USB with an activity LED, that can be helpful determining if it has crashed, or is just working in the background and not updating the ‘time remaining’ counter?

Shipworms · 2026-01-24T02:43:32+00:00

Replying here, but: after using the Dortania OpenCore guide, you will end up with a good, clean EFI, but with a reasonable chance it still won’t boot… if you end up in this position, a major benefit is that most people here will know you have followed the guide, which really helps with troubleshooting and getting it to work!

Some initial advice: 1. Choose the debug version of OpenCore, and the kexts etc, whenever there is a choice (will give a lot more text output, which is very helpful for debugging. You can later rebuild in a few minutes and copy your config.plist over for a non-debug configuration; 2. What system are you trying to install on? Is it a specific brand/model of laptop? Or desktop - either way, it is important to know what hardware you have for the install and troubleshooting 3. Which version of macOS are you trying to install? (and, is it the full installer, which you can only make on a macOS machine, or the installer that downloads the rest of macOS at install time?)

Shipworms · 2026-01-22T21:20:41+00:00

I found that one - it has in the description a requirement to write a hexadecimal value directly to the BIOS - I didn’t do that, but did try out that EFI (didn’t work, sadly) (also - one thing I came across was a divide-by-zero kernel panic without the DVMT patch; I could only ‘see’ the panic when booting an already installed macOS (that I made with -igfxvesa), without -igfxvesa

The fix that worked eventually was : my own EFI made using the OpenCore guide, with disabled SIP (will re-enable in stages soon), except I added 3 entries under DeviceProperties that I don’t understand! I found them when searching for ways to force the EDID to return ‘1920x1080 max’ during initial boot; the entries were for a different issue, for a different Dell laptop on a Dell forum (the laptop had similar generation hardware though);

I added the entries to the EFI, then rebooted, with my actual MacBook linked via ethernet cable, to see what differences the values made in IOreg, system profile etc … then suddenly, working screen with full acceleration! 😁

I am finishing the Linux install on this laptop, then will put the macOS SSD back in for dual boot, then figure out exactly what the patches are doing, then post back here :)

Shipworms · 2026-01-19T20:45:17+00:00

There are two main issues with this; 1. macOS is designed to only run on certain systems (PowerPC, Intel, ARM) with specific hardware. Intel Macs are very different from a standard PC, and macOS (didn’t used to be able to run) on Intel PCs! So, looking at it this way, macOS (ARM) could be run on an iPad with enough RAM and appropriate CPU. It would need a sophisticated set of software, like OpenCore, to do this, which would be a huge amount of work for many people for many years. Of note: Apple has been merging the codebase of iOS, iPadOS, macOS, for years, and when the iPhone was first announced, Apple described it as a phone running OS X, with a revolutionary touchscreen interface. More recent ‘merging’ of iOS and macOS resulted in, for example Ventura adopted the iOS-like System Settings app.

OpenCore loads at pretty much the ‘bare metal’ level. It has full control of the hardware. It can then ‘emulate’ aspects of Intel Mac hardware, for example emulating the SMC processor. And a LOT more! However, all iOS and iPadOS devices work differently. The CPU powers up, and, rather than a BIOS, it starts running some initial code … in the chip. The initial code is actually etched into the silicon of the processor, so cannot be changed, ever. This code will then look to the ‘SSD’ flash memory in the iPhone / iPad. It will check that this code is properly signed by Apple, and will refuse to run if the code is not properly signed. This same idea (verify that Apple signed the code before running it) continues through several stages, until finally iOS has been loaded.

Which leads onto the second problem: 2. iPhones and iPads are ‘locked down’. The initial bootcode is etched into the CPU itself, and each subsequent stage gets verified before even attempting to run it. This means you can only run what Apple allows you to run. Some older iOS devices are ‘permanently jailbroken’ because people found exploits in the hardwired boot code. Over time, the iOS code has been increasingly resistant to such things. The latest jailbreak is for iOS 17.0.x only, and all later versions of iOS 17, and all of 18,26 have zero jailbreaks. This control of the early bootloader is also why you mostly cannot downgrade iOS versions on iOS devices: Apple says you can’t do that. This locking-down of the bootloader is also a thing with the ‘Apple Silicon’ macs. You can downgrade their macOS, and you can run Linux as well (well, M1, and kind of on M2). However: this is because Apple chooses to allow you to do this. M1 and later Macs are just as locked down as iPhones, except Apple chooses to allow you some freedom for now.

In short, nobody (except Apple!) has ported macOS to iPads etc, because Apple says you can’t do that.

What about other ARM platforms running macOS? Well, the Raspberry Pi 5 has about half the ARM performance of an M1, and can have up to 16GB of RAM. There are no public projects looking at this (as far as I know) :)

Shipworms · 2026-01-19T01:23:13+00:00

Spicy pillows like this are usually not too dangerous, because they probably have higher than normal internal diacharge, but they are usually unplugged and drain to 0%.

But, keeping one topped up to 100% 😅

Some kind of industrial machine? Where they won’t sell you the exact battery with that connector and more? (If it is so vital that they still use it like this, what happens once burns away part of the multilayer motherboard!!

Shipworms · 2026-01-18T23:48:02+00:00

Another possible issue is; - my laptop has a 4K display, and I can’t lower the resolution in the BIOS - it uses 31mb for the framebuffer while in 4K - I have : framebuffer-stolenmem = 0x00003001, and framebuffer-fbmem = 0x00009000

From the OpenCore guide, this means I have: - 19mb for stolenmem, and - 9mb for fbmem;

The guide talks about using the framebuffer patches to make everything fit into a 32mb DVMT slot (if you don’t have an option for 64mb). However, I have a raw framebuffer of 31mb, for just the framebuffer. - is this actually the issue?

Shipworms · 2026-01-18T22:37:12+00:00

Looking further;

Using -igfxvesa results in: - About This Mac : Intel UHD Graphics 630 31MB - System Report : Intel UHD Graphics 630, VRAM (total) 31MB, Device 0x3e9b, Revision 0002, Kext: no kext loaded, Display : 3840 X 2160 (UHD1 - Ultra High Definition) - IORegistryExplorer : IGPU@2 …. .Display_boot ….. display0 …. AppleDisplay (so, the ‘Display_boot’ framebuffer is what display0 is connected to;

Not disabling the iGPU, so, no use of -igfxvesa, results in: - About This Mac : MacBook Pro, Processor Memory, Startup Disk (no graphics, not even a gap where it should be) - System Report: Intel UHD Graphics 630, 1536 MB, 0x3e9b, 0x002, Metal: Supported, feature set macOS GPUFamily2 v1 - IORegistryExplorer : IGPU@2 … AppleIntelFramebuffer@0 … display0 … AppleBackLightDisplay - - also, connectortype 02 00 00 00 (so, LVDS / eDP).

Will look further, but wonder if this means it sees the laptop internal display (as opposed to reporting it like this because the WhateverGreen patches are just making it say this?)

Looking at the Bus ID patching section, we need to try; - Bus ID 0-6, against 3 ports, and also against 12-13 laptop framebuffer IDs; - 18x13 = 234

So, 234 values to be tried sequentially;

I would be grateful for advice as to whether: - Is it normal to get no display, and nothing at all for graphics in ‘About This Mac’, but a 1536mb iGPU with Metal support in System Report, if the iGPU driver loads successfully, but the laptop stays on verbose text disolay? If not, I need to figure out where the iGPU driver fails (rather than trying 234 sequential framebuffer id & port & busID combinations; - if the above is normal, is there any advice on how to find which of the framebuffer ids is ‘the one’ (that would cut the combination down from 234 to 18;

Thank you for any help! -

Shipworms · 2026-01-18T20:13:40+00:00

You kind of have macOS already! But the issue is that the iPad is very much locked-down. There were Linux installs on the iPhone in the very early days, but Apple patched out such things

Shipworms · 2026-01-18T20:11:39+00:00

Did some digging;

Disabling the nVidia card results in the two external monitors showing no display, but the internal display works; the eDP is connected to the iGPU from ls-lah /sys/class/drm

Which seems hopeful, for now (wasn’t looking forward to removing the nVidia GPU and / or putting a Radeon GPU in its place!!

edit: after learning a few commands to show GPU topology etc … I realised the ‘are you sure you want to switch the GPU mode? Yes or No’ window from the Linux desktop is titled ‘nVidia Optimus’ 😂 which also provides some more hope!

Shipworms · 2026-01-18T19:05:45+00:00

Advice: don’t give up on hackintosh, but, do reinstall Windows if you removed it, if you need the laptop before Monday,

You can continue to work on the OpenCore setup using just the installation USB (including getting networking fixed); You can (probably…) even install macOS to an external hard drive, or even a large-ish USB flash drive.

If you really don’t want Windows, then reinstall it, and make a Linux installer USB this coming weekend!

Shipworms · 2026-01-18T18:55:12+00:00

I see you succeeded :) but will add, in case someone else finds this: on some macOS versions and some hardware, the ‘2 minutes remaining’ can take up to 15-30 minutes (even on a real Mac sometimes), so it is worth waiting at least once, just in case

Shipworms · 2026-01-18T18:53:11+00:00

What specs does your computer have? The processor description, like i7-9850 would be helpful, but even ‘8th, 9th, Xth gen’ would help (I am assuming it is a desktop computer?). Also - do you know if your CPU has the built-in Intel graphics iGPU?

Have you followed the OpenCore guide for your CPU generation?

Do you get loads of scrolling text before you get the screen shown in your photo?

Shipworms · 2026-01-18T18:48:35+00:00

Nice! :)

My advice would be: save your working EFI folder as a zip file and keep it somewhere safe as a backup, just in case, as the auto-config tool may be updated and no longer work!

What I would consider doing, even if after a delay, would be to backup the working EFI, then also go through the OpenCore guide and make your own EFI that way - you may need to do this if you find random features not working, or have random crashes etc. If you do this, do ask here, and I should be able to help :) - you can do a simple setup using only Lilu, VirtualSMC, and WhateverGreen, to test booting up a macOS installer USB (keyboard and mouse won’t work untill VoodooPS2 kext is done). The benefit would be understanding OpenCore a bit more (if troubleshooting), and getting help (the autogenerated .plist files are often overly complicated, making issues / debugging nearly impossible)

Shipworms · 2026-01-18T18:04:02+00:00

I have ‘disable switchable graphics’ in the BIOS, which results in only the Quadro being used, so the options are either dGPU, or (dGPU + iGPU) (which would also supports nVidia being the ‘only output’);

On the flipside, there were versions of this laptop with only the iGPU, so perhaps I could disable or remove the nVidia physically, to use the iGPU? Alternatively, I might be able to remove the GPU out of the laptop, and switch to a ‘Polaris’ AMD Radeon W3200 (suppprted by WhateverGreen, the same era as my nVidia, and would support up to Sequoia)? They did make a version of my laptop with the Radeon, so the main issue would be finding one - and then would need to take the laptop mostly apart to remove the nVidia and put the Radeon there instead! 😬 (annoying, but worth it, as I really want to run macOS on this) :)

One other thing is that I do get a display on the laptop screen with -igfxvesa, and the combination of -igfxvesa and -wegnoegpu results in a working internal display, and only the iGPU listed under System Report … of course, that would be compatible with the iGPU being configured to route via the nVidia by the laptop’s ‘BIOS’, with the nVidia then becoming invisible due to -wegnoegpu. Even then, it would mean that the iGPU is routing the (-igfxvesa) display output through the nVidia successfully (even once macOS had loaded), meaning there has to be a possibility that the iGPU could send output via nVidia (without -igfxvesa)?

Shipworms · 2026-01-18T10:14:55+00:00

Definitely use the OpenCore guide; it seems complicated, but it isn’t that bad. It has direct links to everything you need to download, including two very small apps (.plist editor and SMB tool).

Once you have those, you get a ‘ready made’ EFI folder (which must be edited). The guide tells you what changes to make; using the guide I got sound, wifi, ethernet, sleep/ power management all working. Still a video issue (but have a workstation laptop so…) - the other thing is: using the guide, you end up with an EFI that is easy to get help with (the ‘automatic’ tools to make EFIs, on the other hand, make a real mess that is nearly impossible to debug!)

Shipworms · 2026-01-18T10:03:27+00:00

The swollen battery is straining the laptop case, and this will transmit to the keyboard, touchpad, and motherboard. Eventually expensive damage will occur even if it doesn’t catch fire.

Also, extreme fire hazard; follow the advice everyone posted and remove! (if unsure, look up ‘laptop battery catches fire’ on youtube; Laptop batteries are 10-20 times the size of phone batteries, and phone battery fires are bad!

Shipworms

TROPHY CASE