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)
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.
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.This one.
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.