Android Standalone VM install stuck in boot loop (android logo screen)

How can i install it properly? And why isn’t the GUI Qubes-Settings able to adress more than 400MB of RAM? Also it doesn’t starts properly in live mode. It seems that it is stuck in a boot loop. Only “android” displays(but it cycles with shadows over the lettering- sometimes it stops, one time at the above left that “_” displayed(only for a very short period):

Please don’t post links to images with no explanatory text. I have
no idea what you are trying to show.
You don’t say what version of Android you are trying to install, or how
you have configured the qube.

You can find discussion of this topic in the Forum, on the mailing list,
and over at Consider support for Android VMs · Issue #2233 · QubesOS/qubes-issues · GitHub

If your problem is that the installer cant find a device, then a basic
search would help you find the answer, and at least run the install. (The
same solution covers ReactOS installs)
I’ve made some notes here -

1 Like

sadly it doesn’t work.

i build two files(init_patch and patch_init) in /home/aetsch/qemu_dmargs directory in dom0, then executed cp /usr/lib/xen/boot/stubdom-linux-rootfs stubdom-linux-rootfs.orig

then i made patch_init executable and then i launched it.

init_patch contains:

qube_name=$(xenstore-read "/local/domain/$domid/name")
case "$qube_name" in
dm_args=$(echo "$dm_args" | sed "s%-drive\\${IFS}file=/dev/xvda.*wwn=0x352540005175626.%-drive\\${IFS}if=ide,media=disk,file=/dev/xvda,id=disk0,format=host_device,cache=writeback,readonly=off%g")  ;;

and patch_init contains:

umask 077
dname=$(mktemp -d)

cp /usr/lib/xen/boot/stubdom-linux-rootfs $dname/stubdom-linux-rootfs
cd $dname
mv stubdom-linux-rootfs stubdom-linux-rootfs.gz
gunzip stubdom-linux-rootfs.gz 
cpio -i -d -H newc --no-absolute-filenames < stubdom-linux-rootfs 
rm stubdom-linux-rootfs 

sed -i "/IFS=\\$/ r /home/user/patch/init_patch" init

find . -print0 |cpio --null -ov --format=newc |gzip -9 > stubdom-linux-rootfs-new
sudo cp -f stubdom-linux-rootfs-new /usr/lib/xen/boot/stubdom-linux-rootfs

rm -rf $dname

it does not find any drive, don’t i have to made all two files executable too?

If you look close at the first screenshot you can see the .iso that I’m using.

Hi alexander
In the time it took you to type that final sentence, you could have
actually told me. “Looking close” is not an option.
Text is searchable and can be indexed: not so for a link to an image.
What is the name of your new qube?
What is the iso you are using?

Im sorry, i named my qube “android”. I downloaded my android-x86_64-9.0-rc2.iso from there:

For what it’s worth, Android X86 installs without any dom0 stubdomain modifications if using Qubes 4.1.

With R4.0, and @unman’s init_patch, looks like the qube name needs to start with “react”.

Or, change the line react*) in init_patch to the name of your qube.

*android*) will match qubes with names containing “android”.

i thought the same but i havent tried yet because im afraid to ruin everything because im a bloody noob. Can you please tell me where in the script and how do i have to throw the name in instead of the words in the script? only react* to android* ?

thank you !

tried it with that one word changed to android but does not work.

In ‘init_patch’ change the react* case statenment to whatever you
want to use for your Android machines:

qube_name=$(xenstore-read "/local/domain/$domid/name")
case "$qube_name" in
dm_args=$(echo "$dm_args" | sed "s%-drive\\${IFS}file=/dev/xvda.*wwn=0x352540005175626.%-drive\\${IFS}if=ide,media=disk,file=/dev/xvda,id=disk0,format=host_device,cache=writeback,readonly=off%g")  ;;

This will apply the change to all machines whose names begin with
“Androi” - Android, Android1, Androidy etc

So just change that to whatever suits you, and run the scripts again.

I have just one question Ive tried looking in the Docs and in the solution you posted and I can’t seem to understand how to change it. Like I understand what is going on and why you say change it but what commands do I use to do this? cat displays the file but do I use vim or no? or is vim even useable in Qubes

Also im using 4.0

You dont need this in 4.1 at all.

By “change” I mean “edit” - you can use vi for this.
dom0 also has nano.
You can also use sed to change that line in place

so ive followed all the steps and my VM still doesn’t work so can I just explain here or do I make a new post?


sorry for the late reply I’ve been. coding alot

The problem im facing is even though ive downloaded the update and followed the instructions adroidx86 is still not seeing the fille system as it is.

I really dont know how to go into more detail so if you need any just let me know and ill answer them to the best of my ability

sorry for the late reply I’ve been. coding alot

Do you mean that you are unable to install because “no disk found”?
In that case you have done something wrong.
Write down exactly what you did - if you followed instructions, don’t
write them out, just refer to them. If you made changes write down
exactly what changes you made.

We rely on you to provide more detail - no one wants to tease out
relevant information piece by piece.
Just tell us exactly what you did (see above)

Dont miss anything out - I once solved an intractable issue by
travelling a few hundred miles to watch a user go through the steps they
had reported. I just asked “What did you do then?” and they said “What
do you mean? I didn’t do anything.” - they had clicked “OK” on the
warning pop up. Never noticed, never reported.
Anyone who has worked support will have those stories.

I never presume to speak for the Qubes team.

When I comment in the Forum or in the mailing lists I speak for myself.