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
Related
how can I select the resident mode by default without waiting the 60 seconds ?
good question, looking for a solution too.
neoissa said:
how can I select the resident mode by default without waiting the 60 seconds ?
Click to expand...
Click to collapse
yes you can
open Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img with 7z
\efi\boot\
Right click edit grub.cfg
set timeout=0
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Resident mode - All your data and apps are saved ' --class android-x86 {
search --file --no-floppy --set=root /system.sfs
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= CREATE_DATA_IMG=1
initrdefi /initrd.img
}
Remove from here
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /system.sfs
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
to here
save
close notepad
imadlatch said:
yes you can
open Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img with 7z
\efi\boot\
Right click edit grub.cfg
set timeout=0
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Resident mode - All your data and apps are saved ' --class android-x86 {
search --file --no-floppy --set=root /system.sfs
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= CREATE_DATA_IMG=1
initrdefi /initrd.img
}
Remove from here
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /system.sfs
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
to here
save
close notepad
Click to expand...
Click to collapse
thank you so much Kind sir this worked for me
Please Hit Thanks when I help you
imadlatch said:
Please Hit Thanks when I help you
Click to expand...
Click to collapse
you deserve it, and I am so sorry checking the site from work ... super busy but you still got it
thank you again
neoissa said:
you deserve it, and I am so sorry checking the site from work ... super busy but you still got it
thank you again
Click to expand...
Click to collapse
I think it was a little good natured trolling, that matches your signature all the way down to the capitalizations.
adfurgerson said:
I think it was a little good natured trolling, that matches your signature all the way down to the capitalizations.
Click to expand...
Click to collapse
good one lol
neoissa said:
good one lol
Click to expand...
Click to collapse
Is that Dogbone Hgts. MI you have for your location? I grew up there in the south end of the city by Annapolis and Pelham. Annapolis H.S. class of "86".
adfurgerson said:
Is that Dogbone Hgts. MI you have for your location? I grew up there in the south end of the city by Annapolis and Pelham. Annapolis H.S. class of "86".
Click to expand...
Click to collapse
yeah true ... Dearborn heights is a good city I like this city and I live there
:good:
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...
Hello,
I installed Remix OS on my Samsung Tablet PC (Intel Core i5). This tablet is placed on a support and the display is copied on an external display via HDMI. It works well with Windows 10, when I remove the shelf support, I can continue to work in touch mode where I was.
With Remix OS, in beta, it does not work. The screen is copied but low resolution and too little on my 24 "screen.
Do you think it will work with the final version of Remix OS?
I only got my second screen working but it's picture is a bit offset, still haven't got the dual screen thing fixed.
After editing the menu.lst , I can choose to start on the screen of the tablet or on the external display 24 " .
Stegue said:
After editing the menu.lst , I can choose to start on the screen of the tablet or on the external display 24 " .
Click to expand...
Click to collapse
What exactly did you change in the menu.lst
And how did you do it?
With Windows , replace the code with it in menu.lst adapting to his version of Remix OS , 32 or 64 bit.
default 0
timeout 10
title Boot to screen tablet
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64
androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Boot to External Monitor
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64
androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1 video=LVDS-1:d
initrd /RemixOS/initrd.img
boot
Click to expand...
Click to collapse
Stegue said:
With Windows , replace the code with it in menu.lst adapting to his version of Remix OS , 32 or 64 bit.
Click to expand...
Click to collapse
So I can just copy and paste this code into the menu.lst file and I'm good to go?
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).
First of all , Hi im dew and this is my first post :laugh:
this is from my personal experiance, I reinstall my windows and i got Error 15 file not found remix os & 0x00000f \ubnldr.mbr Problem, Im too lazy to reinstall the remix os, soo yeah , and finally i found out how to fix it (Might Not Work For Everyone but try it!)
ALL YOU NEED IS:
1. Easybcd (i dont have the link, sorry)
Step by step:
1.Open Easybcd
2.click add new entry
3.click neogrub bar
4.and hit instal (if you already did this you can skip this)
5.after that hit configure
6.delete the previous text and copy this text :
PHP:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Verbose Mode - Save log files for debugging
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1 SAVE_LOGS=1
initrd /RemixOS/initrd.img
boot[/COLOR][/COLOR]
7.hit save on notepad
8.and back to easybcd
9.click edit boot menu
10.and change the name to Remix OS ( if you see another Remix OS name there , you better delete it first)
11.restart
(Might Not Work For Everyone but Worth to try.)
and yeah, Lets be friend after this :v