Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.
The write process with dd most likely worked just fine. However, the system you're inserting it into probably doesn't know what to do with it.
The write process with dd most likely worked just fine.
Not on my end. For some reason it (only) works when I write said image on a sketchy/suspicious chinese third party windows software.
Your gonna need to provide a lot more information, because what your saying sounds very wrong.
Is the img file an android OS? What are you hoping to boot it on?
AFAIK, no phone can boot from external USB, so what exactly are you trying to do?
Is the Android you copied to the external drive compiled for, i.e. compatible with, your hardware architecture, e.g. x86, x86_64, arm64, ...?
Yep. It's an official image, not from third parties.
Nevertheless, the information which exact image you dd'ed and what the actual hardware you want to run it on is would be helpful (also to others).
Based on your other comment: Did you try to dd on Linux or just on Windows? (Idk if Windows has a native version of dd instead of the suspicious Chinese Windows exe you've used)
Only on Linux. The command was simply sudo dd if=image.img of=/dev/sda bs=1M.
which exact image you dd’ed
So, you dd'ed the Android image for Orange Pi 5 to an external drive and want to boot your OPi5 from that drive. As far as I remember, in order to do that for a Raspberry Pi, you need to 'tell' the system where to boot from. For OPi, I found some information on how achieve that for Debian/Ubuntu. For Android the steps should be somewhat similar.
I've tried setting it to boot from an nvme, microsd and external and the result was the same -- the board just sits there with no boot. But, as I said previously, writing it to disk with their sketchy software worked as intended.
...I'm starting to think there is something wrong with the image file.
No