Btw, downloading a CD (.iso) on the phone to boot it, because your Linux broke while you had no bootable thumbdrive around. Is something a lot of people here did sometime.
That looks like a program that is using your phone to write an ISO to a USB using your phone, not using your phone as a bootable source. But, still useful.
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.
There’s a tool, whose name I forget, which is included in Kali NetHunter to do just that. It does whatever trickery is needed to present the phone/tablet as a bootable thumb drive. It requires root and, to my dismay when I needed it, I never owned a device that was rootable to fully use NetHunter. It could do a lot of other cool stuff via USB too; phone as a Bad USB, Rubber Ducky, automated Windows login bypasses, etc.
Just a couple days ago I needed a microsd to usb adapter. Couldn’t find one, so I loaded the files to a memory with fat usb(I don’t know what it’s called) and usb c connections. Then connected the memory to my phone and on my phone I moved the files to the microsd card.
Not the same but similar vibes I think.
It’s sad that several phones are removing the memory slot.
Fat USB is called USB A. The one you use for printers is USB B. Then there are mini-A, mini-B, micro-A, micro-B and USB 3.0 micro-B which are all different shapes physically. And USB A 3.0 has slightly different contacts from USB A 1.0/2.0
Anyway, that was when USB nomenclature was still simple. Don’t google anything they did past version 3.0, for your own sanity. We’re now down to mostly the USB C and A shapes, but USB 3.2 gen 1x1 is the same thing as USB 3.1 gen 1 is the same thing as USB 3.0.
USB 4 simplified things a bit, but now you can get things like Gen 4asymmetric3:1
And also
Btw, downloading a CD (.iso) on the phone to boot it, because your Linux broke while you had no bootable thumbdrive around. Is something a lot of people here did sometime.
I had that exact situation but simply went to the library to fix it. Modern phones scare me.
PSA: get a cheap thumb drive and install ventoy. You’ll never regret it!
Plus you can technically still use it to store files if you make a directory in the ventoy dump partition.
I keep memtest86+, clonezilla, Ubuntu 24.04lts, gparted, and boot-repair on the drive.
maybe not ventoy specifically since it’s full of binary blobs that are virtually unvettable
I’ve got a binary blob right here 🥵
Eh, good enough. Your Linux install also has binary blobs.
Yeah, I need to find a better way. Been trying to setup pxe boot in docker
Always been partial to this one
I never even thought of that - you then plug in your phone as a thumb drive? Makes sense.
I mean I’m not sure I could actually boot off of my phone as a USB drive. That would be an interesting concept.
It does, though with an app that exposes the iso.
Edit: Right, i thought it was EtchDroid. I think it was DriveDroid (with a broken cert)? There’s also SimpleBoot now.
That looks like a program that is using your phone to write an ISO to a USB using your phone, not using your phone as a bootable source. But, still useful.
Edited, thanks.
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.”
There’s a tool, whose name I forget, which is included in Kali NetHunter to do just that. It does whatever trickery is needed to present the phone/tablet as a bootable thumb drive. It requires root and, to my dismay when I needed it, I never owned a device that was rootable to fully use NetHunter. It could do a lot of other cool stuff via USB too; phone as a Bad USB, Rubber Ducky, automated Windows login bypasses, etc.
Been there, done that
Just a couple days ago I needed a microsd to usb adapter. Couldn’t find one, so I loaded the files to a memory with fat usb(I don’t know what it’s called) and usb c connections. Then connected the memory to my phone and on my phone I moved the files to the microsd card.
Not the same but similar vibes I think.
It’s sad that several phones are removing the memory slot.
Fat USB is called USB A. The one you use for printers is USB B. Then there are mini-A, mini-B, micro-A, micro-B and USB 3.0 micro-B which are all different shapes physically. And USB A 3.0 has slightly different contacts from USB A 1.0/2.0
Anyway, that was when USB nomenclature was still simple. Don’t google anything they did past version 3.0, for your own sanity. We’re now down to mostly the USB C and A shapes, but USB 3.2 gen 1x1 is the same thing as USB 3.1 gen 1 is the same thing as USB 3.0.
USB 4 simplified things a bit, but now you can get things like
Gen 4 asymmetric 3:1It seems we need a new standard to prevent all this confusion…
What have we done…