Unlikely. The USB protocol requires one master and one or more slaves (or whatever less charged nomenclature you prefer). In all likelihood UEFI will blindly assume to be the master while Android and iOS require negotiation to figure out who’s boss and what interface to present.
Although given UEFI it might be possible to patch that functionality in.
i had this feature when i installed ubports (ubuntu touch) on my phone in 2021.
much before that in 2013 my phone’s stock rom had a ‘driver install’ mode that presents an iso file in the system partition to the computer as a virtual cdrom, i could swap out that file with a linux iso and it would boot
The USB protocol and UEFI aren’t a problem, but Android/iOS might be. I’ve booted various PCs from a raspberry pi (USB-OTG), but the last time I tried to boot an iso from my android phone I couldn’t get it to work. It’s been a while so I can’t remember exactly what the issue was.
Unlikely. The USB protocol requires one master and one or more slaves (or whatever less charged nomenclature you prefer). In all likelihood UEFI will blindly assume to be the master while Android and iOS require negotiation to figure out who’s boss and what interface to present.
Although given UEFI it might be possible to patch that functionality in.
i had this feature when i installed ubports (ubuntu touch) on my phone in 2021.
much before that in 2013 my phone’s stock rom had a ‘driver install’ mode that presents an iso file in the system partition to the computer as a virtual cdrom, i could swap out that file with a linux iso and it would boot
The USB protocol and UEFI aren’t a problem, but Android/iOS might be. I’ve booted various PCs from a raspberry pi (USB-OTG), but the last time I tried to boot an iso from my android phone I couldn’t get it to work. It’s been a while so I can’t remember exactly what the issue was.
My guess the issue is that phones don’t just show up as simple drives, they rely on MTP support
That’s what I was referring to with “which interface to present.”