Separate names with a comma.
Discussion in 'Other Guest OS Types Discussion' started by Mark Fine, Dec 28, 2019.
hey, I switched to Virtual Box too and there I faced this problem several times.
4. Mount the grub partition to /mnt/USB: # mount /dev/block/sda1 /mnt/USB
This doesn't work in RC2. First it complains it doesn't know the type (needs -t), then if I supply ext2 it complains the filesystem is busy. I don't know of a work-around.
Sounds like the problem I had at first. Did you su to root first?
After a second try it did mount like in rc1 and I was able to get rc2 working. Not sure what happened the first time.
Maybe that's what I remembered. It was kind of weird in that it didn't work at first, then it did.
At least you're in... hopefully.
Apparently when I wasn't looking, A9 r1 was released on 27 Feb...
System Update won't recognise the new release on 27 Feb.
I've tried loops of img files. I've tried tricking grub to start/boot the r1 update iso... no joy.
Am getting close to backing up sda1 then replacing it with the contents of the iso file, then rebooting if I thought I could get back to the original sda1 contents somehow.
this is nuts.
1. Download the iso on your Mac, not within Android (duh).
2. Find a semi-disposable USB drive, back it up, and install the iso file on the main partition, e.g.:
# dd if=android-x86_64-9.0-r1.iso of=/dev/disk4 bs=1m
3. Go to your Android configuration in Parallels and under Hardware -> Boot Order, set the External Device above the Hard Disk, and make sure it's checked.
4. You can optionally select the External Boot device by name (and drive#) underneath.
5. Start the Android VM in Parallels and it should boot into the grub menu from the USB Drive.
6. Select "Advanced Options..." then "Auto_Update - Auto update Android-x86" on the next screen. It should then proceed to update sda1.
7. Don't forget to de-select the USB drive from the Boot Order when restarting.
8. Definitely don't forget to add nomodeset to the grub menu (see earlier post) otherwise you'll never get past the command prompt.
What a discovery process.
So what you're saying is, just using the built-in Android installer really doesn't work? I tried it once and either didn't understand how to control the interface or something else was going on.
The built-in installer works with the prescribed distribution of Android 8 and only 8. This is for the Android-x86 distribution of Android 9 (and 10 when finally released).