Hello guys,
I have bought a Lenovo Yoga Tablet 2 10" and installed Remix OS 32-bit through provided tool. Unfortunately, I have Bluetooth keyboard which doesn't work before full system loading, therefore I can't choose Remix OS on boot screen.
Installation of Remix OS also created the second "Windows Bootloader" entry in EFI Boot from menu (which is operable by touch). When I choose the first Win Bootloader, it throws me directly to Windows 10 loading screen without displaying the boot choice between Windows 10 and Remix OS (which is present on second Win Bootloader option).
So I've got an idea to edit the boot file of Remix OS to boot directly without asking me, whether I want to load Remix or Windows. Therefore I will be able to boot Remix without keyboard when choosing second bootloader, and Windows when choosing the first one.
When I used the live version of Remix OS, I edited grub.cfg to load system directly without waiting for confirmation from keyboard:
set timeout=0
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
Is this also possible on installed version of Remix OS? I have tried to edit grub.cfg located in D:/RemixOS/efi/boot to match the code above, but after restart I was greeted with choice screen (so it didn't work).
Thank you in advance for any replies!
Cleo1 said:
Hello guys,
I have bought a Lenovo Yoga Tablet 2 10" and installed Remix OS 32-bit through provided tool. Unfortunately, I have Bluetooth keyboard which doesn't work before full system loading, therefore I can't choose Remix OS on boot screen.
Installation of Remix OS also created the second "Windows Bootloader" entry in EFI Boot from menu (which is operable by touch). When I choose the first Win Bootloader, it throws me directly to Windows 10 loading screen without displaying the boot choice between Windows 10 and Remix OS (which is present on second Win Bootloader option).
So I've got an idea to edit the boot file of Remix OS to boot directly without asking me, whether I want to load Remix or Windows. Therefore I will be able to boot Remix without keyboard when choosing second bootloader, and Windows when choosing the first one.
When I used the live version of Remix OS, I edited grub.cfg to load system directly without waiting for confirmation from keyboard:
set timeout=0
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
Is this also possible on installed version of Remix OS? I have tried to edit grub.cfg located in D:/RemixOS/efi/boot to match the code above, but after restart I was greeted with choice screen (so it didn't work).
Thank you in advance for any replies!
Click to expand...
Click to collapse
Hi Cleo ....
Did you ever figure out how to do this, ? cause I would like to do the same boot straight into remix without a dual boot option...
Related
Downloading and installing remix on a usb stick posed no problem, but installing it on a ssd in my desktop is a real pain in the neck.
I made a bootable usb stick using unetbootin with the latest iso and started the installation. So far so good, but installing the data took a long time. The os started with this peautiful picture but was very unstable adressing the usb stick all the time. On restart a nice entry appeared in my windows bootloader. When I clicked the computer restarted searching for the remix os, getting stuck at an ext 2 partition
Now I had created a 37 GB primary partition after my ubuntu partitions, because there the remix should install.
Gparted showed that 50 MB was written to this partition but not a sign of remix.
Is this all due to ubuntu that I have next to windows 10?
Or am I doing something terribly wrong?
I have 2 linux+w10+Remix on 3 hdd. Remix beside Linux Mint 18.
I create ext4 partition 40Gb (Gparted; need remember "sda1", or other name partition). Boot from usb, Resident mode + INSTALL=1 option. Choose 40Gb partition, "Do not format", grub - NO, EFI GRUB - Skip, Read\Write - Yes. Reboot on Mint. Install Grub Customizer and add entry for Remix. Its look like this:
(all coments i wrote for you started $$$$ - not for Grub Customizer =))
Code:
set root='(hd2,2)' $$$$ Disk account starts with 0, so if you have sda4 - (hd0,4)
search --no-floppy --fs-uuid --set=root 033e8fc7-4cfe-9454-bc59-df7329ca862d $$$$ this unique number partition has change after format from remix installer. Can take it from fstab.
linux /android-2016-06-30/kernel root=UUID=033e8fc7-4cfe-9454-bc59-df7329ca862d androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA=/android-2016-06-30/data $$$$ change number too and check path to kernel
initrd /android-2016-06-30/initrd.img $$$$ check path
Done.
Hi Slawdos,
Thanks for the instruction. Remix is installed now, but the ubuntu bootloader can't find the uuid= (the number I found with Gparted).*
I have found the uuid and path of the remix partition in Gparted and implemented it in the codes of the remix entry in grub optimizer.
But obviously I have made one ore more errors in these codelines.
These are the codes I used:
set root='(hd7,1)'
search --no-floppy --fs-uuid --set=root 6947dc76-11cf-4fa3-a6d2-18637c404be2
linux /android-2016-06-30/kernel
root=UUID=6947dc76-11cf-4fa3-a6d2-18637c404be2
androidboot.hardware=remix_x86_64
androidboot.selinux=permissive quiet DATA=/dev/sdh2/android-2016-06-30/data
initrd /dev/sdh2/android-2016-06-30/initrd.img
Could you please give me some more instructions
eekie64 said:
set root='(hd7,1)'
----
androidboot.selinux=permissive quiet DATA=/dev/sdh2/android-2016-06-30/data
initrd /dev/sdh2/android-2016-06-30/initrd.img ^^^^^^^
^^^^^^
Could you please give me some more instructions
Click to expand...
Click to collapse
Hi. Looks like right, but partitions account start from 1 (grub2 feature). Try use first line
Code:
set root='(hd7,2)'
if you have some errors on loading, will be nice to look at it.
ps: i use x64 remixos. and you?
Hi Slawdos,
Your suggestion didn do the trick. Alas!
When I click remix in the grub2 bootloader, it tells me:
error : disk ' UUID=6947dc76-11cf-4fa3-a6d2-18637c404be2 ' has not been found
push any key to continue
Then while shutting down the whole operation is echoed
Somewhere close to the end it says:
kernel panic not syncing VFS: unable to mount filesystem on unknown block (0,0)
Still puzzled
Check UUID.
Other method for installing Remix OS alongside Ubuntu
Perhaps you should try the method I have described in "How to install Remix OS alongside Ubuntu (dual boot)".
Basic information about tools and updating your dual boot installation you'll find in "Remix OS on Hard Drive or Virtual Machine - Installation and (OTA) Update".
I am trying to add remix OS as a 2nd boot option to a machine that is currently single booting Mint 18 with full disk encryption.
I followed the tutorial for the new marshmallow Remix installed alongside Mint and it worked great on a non-encrypted test box, but I'm having issues doing it on my primary laptop that was installed with full disk encryption option at install time for Mint 18.
How do I need to modify the grub entry for Remix to make it work? For reference here is the grub setup for my Mint installation:
Code:
menuentry 'Linux Mint 18 Cinnamon 64-bit, with Linux 4.4.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-21-generic-advanced-1e6da0b0-6645-4904-a8f7-0c2e7ddbce83' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 ffd7222b-aa1e-44d6-a010-e33cefd386d1
else
search --no-floppy --fs-uuid --set=root ffd7222b-aa1e-44d6-a010-e33cefd386d1
fi
echo 'Loading Linux 4.4.0-21-generic ...'
linux /vmlinuz-4.4.0-21-generic root=/dev/mapper/mint--vg-root ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-21-generic
}
Here is the default Remix OS entry that I need to modify so that the encrypted volume is mounted first the same way it is for Mint. I have no idea what I need to do to achieve this. Looking above I see the set root options many times... evidently that doesn't do what I thought it did because I've tried every version of setting the root below and getting it badly wrong. My remix lives in /remix just like in the tutorial except that my / is on the encrypted volume.
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/system.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
Bump... pleeze haaalp
getut said:
I am trying to add remix OS as a 2nd boot option to a machine that is currently single booting Mint 18 with full disk encryption.
I followed the tutorial for the new marshmallow Remix installed alongside Mint and it worked great on a non-encrypted test box, but I'm having issues doing it on my primary laptop that was installed with full disk encryption option at install time for Mint 18.
How do I need to modify the grub entry for Remix to make it work? For reference here is the grub setup for my Mint installation:
Code:
menuentry 'Linux Mint 18 Cinnamon 64-bit, with Linux 4.4.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-21-generic-advanced-1e6da0b0-6645-4904-a8f7-0c2e7ddbce83' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 ffd7222b-aa1e-44d6-a010-e33cefd386d1
else
search --no-floppy --fs-uuid --set=root ffd7222b-aa1e-44d6-a010-e33cefd386d1
fi
echo 'Loading Linux 4.4.0-21-generic ...'
linux /vmlinuz-4.4.0-21-generic root=/dev/mapper/mint--vg-root ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-21-generic
}
Here is the default Remix OS entry that I need to modify so that the encrypted volume is mounted first the same way it is for Mint. I have no idea what I need to do to achieve this. Looking above I see the set root options many times... evidently that doesn't do what I thought it did because I've tried every version of setting the root below and getting it badly wrong. My remix lives in /remix just like in the tutorial except that my / is on the encrypted volume.
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/system.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
Click to expand...
Click to collapse
See whether this helps http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
You'll have to instruct grub to decrypt volume at the boot time.
Thisu said:
See whether this helps http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
You'll have to instruct grub to decrypt volume at the boot time.
Click to expand...
Click to collapse
Thanks for the reply. Unless I am missing something, this isn't relevant since I don't have an encrypted boot. I have a normal run of the mill encrypted SSD using stock encryption options when you choose encrypt my whole disk during a Mint or Ubuntu fresh, whole disk installation.
My disk has a NON encrypted boot, then another encrypted partition that everything else lives in.
I just need to know how to kick off the encryption the same way the Mint install does so that the remix os boot can continue. With my poking at the grub cfg I think it has something to do with where I specify the "root" parameters. But until this point I haven't gotten it right... or I may be barking up the wrong tree.
getut said:
Thanks for the reply. Unless I am missing something, this isn't relevant since I don't have an encrypted boot. I have a normal run of the mill encrypted SSD using stock encryption options when you choose encrypt my whole disk during a Mint or Ubuntu fresh, whole disk installation.
My disk has a NON encrypted boot, then another encrypted partition that everything else lives in.
I just need to know how to kick off the encryption the same way the Mint install does so that the remix os boot can continue. With my poking at the grub cfg I think it has something to do with where I specify the "root" parameters. But until this point I haven't gotten it right... or I may be barking up the wrong tree.
Click to expand...
Click to collapse
So does that mean all your RemixOs stuff,including kernel,initrd,ramdisk reside within the encrypted partition?
I would suggest you to use something like EFISTUB booting,if you are using UEFI. You'll have to place kernel and initrd in ESP(EFI system partition).
Basically I've tried installing every build of RemixOs 3.0.X (2.0 worked). but with 3.0 I get no errors, it also does not actually install grub, so it is unbootable.
Now I can see the values in the EFI partition and everything on disk is correct, secure boot is disabled, but I do not get the grub boot loader to execute so I have no way to access RemixOS. Now I've tried installs in without AV and FW running, and every build, but simply put I can not get it to actually install Grub is impossible. I do not see why it is not running grub, as I stated everything looks correct, but for some reason the last step of triggering it to run on boot is not being executed, and I've yet to discover any way to manually force the process (or even a log of what went wrong).
How do I force RemixOS install to not only configure grub, but install it, if I had Linux installed I'd use setup-grub, but with only windows I'm at a loss. Also any idea why 2.0 worked and installed the bootloader, but 3.0 does not as far as I can see the boot loader is the same.
Finally I've gone as far as forcing the boot order to run grub, however then I'm stuck as the grub config from remixOS does not work from GRUB, when I copy it to the custom config, so obviously something else is required to boot RemixOS using grub2win, other than the EFI partition grub.cfg configuration, as that begins loading the OS, but does not succeed.
If I remove Quite and set " logo.showlogo=0", then I've been able to get remixos to start booting, however once the remixos's load screen appears it hangs, never completes. It also warns about ntfs module already being loaded, but that is just annoying nothing else. Still some progress, now if only I could see what was happening when it shows remixos instead of staring at a logo, which I might mention I disabled.
Thanks,
ERIC
Finally got it booting, but while it run, I can not get a keyboard so it is useless. Best I can do is Swiftkey Neural which shows 3 words, but no keyboard. It is as if it think I have a physical one connected even when I do not.
ERIC
egandt said:
Finally got it booting, but while it run, I can not get a keyboard so it is useless. Best I can do is Swiftkey Neural which shows 3 words, but no keyboard. It is as if it think I have a physical one connected even when I do not.
ERIC
Click to expand...
Click to collapse
Could you help me by showcasing how to Dual Boot Remix OS 3.0 on efi system Using Grub2win and by making different partition. i m just stuck at the remix os boot logo.
iamvishalattri said:
Could you help me by showcasing how to Dual Boot Remix OS 3.0 on efi system Using Grub2win and by making different partition. i m just stuck at the remix os boot logo.
Click to expand...
Click to collapse
First I installed Remix OS with Windows 10 (Dualboot), I restarted my laptop, booted Windows 10 and at the OS Selection screen I chose Remix OS, it restarted, booted into Remix OS! Then I added Remix OS to my dualbooted Ubuntu Grub configuration with Grub-Customiser! Voila, I can boot from Grub from Ubuntu!
It should be similar for Grub2Win, but I wouldn't recommend it!
iamvishalattri said:
Could you help me by showcasing how to Dual Boot Remix OS 3.0 on efi system Using Grub2win and by making different partition. i m just stuck at the remix os boot logo.
Click to expand...
Click to collapse
If RemixOS is installed, desintall it.
Create a new NTFS partition with sufficient space (H in my case)
Install Remix OS in the new partition (H), don't reboot!
Open Grub2win , manage a new entry. Choose Remix, and modify the "Linux Boot Parms" like this:
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
(quiet SERIAL=random is for open Google Play, REMOUNT_RW=1 is for having a RW system, if you don't want, don't put this option, androidboot.swrast=1 is for going further than the Remix logo)
Next, in the directory where Grub2win is (ie C:\), install AS ADMINISTRATOR a symlink (right click on Start, command prompt as administrator, cd C:\ and type mklink RemixOS H:\RemixOS), it's H in my case, change for your choice.
Reboot, and launch Remix in the Grub2win screen, and be happy
Yadegun said:
If RemixOS is installed, desintall it.
Create a new NTFS partition with sufficient space (H in my case)
Install Remix OS in the new partition (H), don't reboot!
Open Grub2win , manage a new entry. Choose Remix, and modify the "Linux Boot Parms" like this:
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
(quiet SERIAL=random is for open Google Play, REMOUNT_RW=1 is for having a RW system, if you don't want, don't put this option, androidboot.swrast=1 is for going further than the Remix logo)
Next, in the directory where Grub2win is (ie C:\), install AS ADMINISTRATOR a symlink (right click on Start, command prompt as administrator, cd C:\ and type mklink RemixOS H:\RemixOS), it's H in my case, change for your choice.
Reboot, and launch Remix in the Grub2win screen, and be happy
Click to expand...
Click to collapse
ahhhh thanks alot man You made my day. that worked like charm... but to be true Remix OS 3.0 204 lagged alot after booting up if we take a look at its performance even on my i5 processor laptop ..... is this the commands issue that made it lag sometimes or its their bugs
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
and can you help me booting up my Android 6.0 r1 becoz that too stuck at boot logo using Grub2win ... After installation if i run directly than it works like cham bt after after reboot it stuck same like Remix Os please provide the same gurb config for android 6.0 r1 will the above commands work for Android 6.0r1 too ???
iamvishalattri said:
ahhhh thanks alot man You made my day. that worked like charm... but to be true Remix OS 3.0 204 lagged alot after booting up if we take a look at its performance even on my i5 processor laptop ..... is this the commands issue that made it lag sometimes or its their bugs
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
I own a core i5 PC and do not have notice such behavior
and can you help me booting up my Android 6.0 r1 becoz that too stuck at boot logo using Grub2win ... After installation if i run directly than it works like cham bt after after reboot it stuck same like Remix Os please provide the same gurb config for android 6.0 r1 will the above commands work for Android 6.0r1 too ???
Click to expand...
Click to collapse
I have tried to boot with Grub2win and Android 6.0 r1, but, If in the Linux Boot Parms, I let "video=-16", the screen is yellow, only the letters "and" are visible and white on the right side, while I put vga=791 in place, the screen is black, but stuck at the flashing logo. I don't know, at this time, what to do!
Is there a list somewhere (that I could access) of the Android kernel command line (boot) parameters that are supported by the RemixOS kernel???
I am trying to get the latest build (207) to boot on my Intel i5 tablet. I fould that with the lastest build, I was about to boot RemixOS (for PC) from a USB driver. However, when I tried to install it to my UEFI based Inel i5 tabet, the install failed.
I see to have this UEFI related problem with all Androidx-86 based OSs. I was about about to get Android-x86 6.0 to boot by copying the files from the ISO to a folder on my hard drive, installing the Grub2Win EFI boot loader files, and manually creating a "Grub.cfg" file.
I tried this same method with RemixOS (for PC), but the kernel command line parameters in the RemixOS build of the Android kernel seem to be different than Android-x86, and the parameters using in the USB Grub config file don't seem to translate directly to a hard drive install.
In lieu of that, perhaps someone could provide me with the text from the Grub config file on their hard drive install of RemixOS (for PC) ???
I was able to get it to boot by adding CREATE_DATA_IMG=1 to the boot parameters.
The kernel then creates a data.img and proceeds to boot. At least, it did for me.
Hope that helps.
Hi
Ive just managed to get RemixOS installed on my Dell Inspiron 11 it has Win10, Fedora24,Manjaro, Deepin and a couple of other distros I was checking out all coexisting, booting on UEFI and sharing a 300GB Data partition. Now I swapped out Elementary and a CLI Arch and put in Remix it all seems to work pretty good, I have tested WiFi, bluetooth, Camera, Google Play, USB, The bluetooth seems at least as solid as the best linux distros Ive tried and way better than Windows 10.
I first burnt the ISO (Remix_OS_for_PC_Android_M_64bit_B2016112101) onto a USB stick
Then booted from the stick and edited the boot script to add INSTALL=1 to the end of the Linux Command.
This fires up the Android_x86 installer. I installed it onto a partition I prepared for it (Ext4 29GB).
I told it to format the partition and said no to both the grub installs and chose a readwrite system.
It ran without error and I rebooted into Fedora24 that has grub2 and grub-customizer.
That is my goto grub, it has menu items for all my installed distros.
I tried the OS-Probe generated script which failed but was useful because it had the UUID of my partition.
Then its a bit of trial and error but eventually it booted.
That first boot seems to take forever, but after a times it seems to be booting much quicker.
Here is the script fragment that works the best so far (I have Replaced my Partition number and UUID with (hdX, GPTXX) and XX respectively:
set root='(hdX,GPTXX)'
search --no-floppy --fs-uuid --set=root XX
linuxefi /kernel initrd=/initrd.img root=UUID= XX androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1 REWRITE=1
initrdefi /initrd.img
I thought I had downloaded 207 but now im not so sure, Remix just said it had an update to build 207 but didnt recommend updating because it detected I had installed with an unapproved installer.
Thank you!!
flurbius said:
Hi
Ive just managed to get RemixOS installed on my Dell Inspiron 11 it has Win10, Fedora24,Manjaro, Deepin and a couple of other distros I was checking out all coexisting, booting on UEFI and sharing a 300GB Data partition. Now I swapped out Elementary and a CLI Arch and put in Remix it all seems to work pretty good, I have tested WiFi, bluetooth, Camera, Google Play, USB, The bluetooth seems at least as solid as the best linux distros Ive tried and way better than Windows 10.
I first burnt the ISO (Remix_OS_for_PC_Android_M_64bit_B2016112101) onto a USB stick
Then booted from the stick and edited the boot script to add INSTALL=1 to the end of the Linux Command.
This fires up the Android_x86 installer. I installed it onto a partition I prepared for it (Ext4 29GB).
I told it to format the partition and said no to both the grub installs and chose a readwrite system.
It ran without error and I rebooted into Fedora24 that has grub2 and grub-customizer.
That is my goto grub, it has menu items for all my installed distros.
I tried the OS-Probe generated script which failed but was useful because it had the UUID of my partition.
Then its a bit of trial and error but eventually it booted.
That first boot seems to take forever, but after a times it seems to be booting much quicker.
Here is the script fragment that works the best so far (I have Replaced my Partition number and UUID with (hdX, GPTXX) and XX respectively:
set root='(hdX,GPTXX)'
search --no-floppy --fs-uuid --set=root XX
linuxefi /kernel initrd=/initrd.img root=UUID= XX androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1 REWRITE=1
initrdefi /initrd.img
I thought I had downloaded 207 but now im not so sure, Remix just said it had an update to build 207 but didnt recommend updating because it detected I had installed with an unapproved installer.
Click to expand...
Click to collapse
Really appreciate your help!! XD I was trying to find that boot parameter edit to get back to that setup page!! The boot parameter INSTALL=1!! Thank you for your help!! XD
I am trying to install Android on a Lenovo Yoga 9i with an i7 10th generation processor which dual boots Win 11 and Kubuntu 22.04. I have been able to install PrimeOS, Android-x86 and BlissOS to the kubuntu root using the following isos – PrimeOS-2.1.3-64-bit-20220719-BETA.iso -- android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso and
BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd.iso manually for linux where I copy the kernel, initrd and system files to the appropriate folder. I create a data folder rather than a data.img file as this is marginally more flexible for my use. I use the following 40_custom grub file to allow me to start the different OS.
menuentry "BlissOS" { set SOURCE_NAME="dev/nvme0n1p8/blissos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SDCARD=dev/nvme0n1p6 SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Primeos" { set SOURCE_NAME="primeos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 SDCARD=dev/nvme0n1p6 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Android" { set SOURCE_NAME="android-x86" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive SDCARD=dev/nvme0n1p6 set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
I have three issues common to all three Oss which I have cannot solve.
1. I am unable to permanently set a lockscreen password or pin. I can enter a password or pin but the system immediately reverts to none saved.
2. Unlike with earlier versions of Android-x86 (used on a Sony Vaio with touch and a lenovo yoga 3-11) I am unable to set an NTFS data partition as the external SD card. I have tried to find advice as to how I should adapt SDCARD=dev/nvme0n1p6 as it does not seem to work. Strangly PrimeOS mounts the Windows partition unasked.
3. Finally, I would like to run the BlissOS from a separate partition but it fails to find the partition with the kernel. I have tried using the UUID unsuccessfully.
/dev/nvme0n1p8: LABEL="blissos" UUID="69d92f25-8e97-46b8-b0d4-675106fafc60" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="blissos" PARTU
UID="72a75f11-668e-bb48-8c14-6dce6e9ed391"
I have a minor problem with the Android-x86 iso in that it loads an initial screen with bright white lines in the lower part of the screen although I can get past this.
divotee said:
I am trying to install Android on a Lenovo Yoga 9i with an i7 10th generation processor which dual boots Win 11 and Kubuntu 22.04. I have been able to install PrimeOS, Android-x86 and BlissOS to the kubuntu root using the following isos – PrimeOS-2.1.3-64-bit-20220719-BETA.iso -- android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso and
BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd.iso manually for linux where I copy the kernel, initrd and system files to the appropriate folder. I create a data folder rather than a data.img file as this is marginally more flexible for my use. I use the following 40_custom grub file to allow me to start the different OS.
menuentry "BlissOS" { set SOURCE_NAME="dev/nvme0n1p8/blissos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SDCARD=dev/nvme0n1p6 SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Primeos" { set SOURCE_NAME="primeos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 SDCARD=dev/nvme0n1p6 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Android" { set SOURCE_NAME="android-x86" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive SDCARD=dev/nvme0n1p6 set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
I have three issues common to all three Oss which I have cannot solve.
Click to expand...
Click to collapse
As I have removed these three ROM and replaced them with the stable Pie based ROM, 11 which I have installed at root, I have happily got rid of 2 of my three problems as follows:-
divotee said:
1. I am unable to permanently set a lockscreen password or pin. I can enter a password or pin but the system immediately reverts to none saved.
Click to expand...
Click to collapse
I can now set a lockscreen
divotee said:
2. Unlike with earlier versions of Android-x86 (used on a Sony Vaio with touch and a lenovo yoga 3-11) I am unable to set an NTFS data partition as the external SD card. I have tried to find advice as to how I should adapt SDCARD=dev/nvme0n1p6 as it does not seem to work.
Click to expand...
Click to collapse
Still a problem . Trying to mount using termux - get 'device not found ' after making a directory as /mnt/newvol.
divotee said:
3. Finally, I would like to run the BlissOS from a separate partition but it fails to find the partition with the kernel. I have tried using the UUID unsuccessfully.
Click to expand...
Click to collapse
Given up trying to do this
divotee said:
/dev/nvme0n1p8: LABEL="blissos" UUID="69d92f25-8e97-46b8-b0d4-675106fafc60" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="blissos" PARTU
UID="72a75f11-668e-bb48-8c14-6dce6e9ed391"
I have a minor problem with the Android-x86 iso in that it loads an initial screen with bright white lines in the lower part of the screen although I can get past this.
Click to expand...
Click to collapse
No longer relevant as I have removed the ROM