I am not responsible for anything that may happen to your PC/Laptop/Tab as a result of installing and using this script. you do so at your own risk and take the responsibility upon yourself.
Note: Backup your custom.cfg file if you are dual booting with other os if not then proceed further.
custom.cfg should be in /boot/grub/custom.cfg if EFI install then /boot/efi/EFI/yourdistroname/custom.cfg
p7zip-full should be installed its need for extracting ISO file.
Script should be placed where desired files or ISO is present.
--> This is tested and working fine in kde neon lts on MBR and GPT disks & EFI is not tested as I don't have that installation so it should work.
--> Other then Debian based distros IDK if my script works on them or not, so please test it yourself and inform.
--> If your home folder is defined on other disk or partition please add insmod part_gpt insmod ext2 OR insmod part_msdos insmod ext2 according to disk partition table to grub entry in custom.cfg
Features
Path defined root and home only.
- Method defined FILES and ISO only.
- Has Uninstall options.
- Data folder is created in os folder
chmod +x Bliss-x86-Installer-Linux
./Bliss-x86-Installer-Linux
Yes, I have an account on GitHub and often post bugs there for various projects.Are you on GitHub? And do you know how to submit a pull request?
These are the originals. I just wrote them from scratch. They are nothing more than config files for input devices.If you can please direct us to the original file and it's source
If you would like to PM myself or @electikjesus... We can assist you with the above. We also have one team member who will be returning from a development break who owns a SP3 a and can verify functionality
If it in fact works as you described, great benefit to the SP3 owners! And we are definitely interested in adding this support/feature to Bliss-x86
This has been an ongoing issue, and I'm afraid it won't progress any faster until I have an IPTS device in my hands to test with. Sorry folks
Something like video=LVDS-1:1920x1080 in boot config file. LVDS-1 is for notebook, so you may need to use other name.I used the nomodeset entry in the boot config file to get it to boot but would now like to set the video resolution to 1920 x 1080 for my AOC monitor. Is this possible and how can I do this - code in boot config file or somewhere I havnt found in settings?
Something like video=LVDS-1:1920x1080 in boot config file. LVDS-1 is for notebook, so you may need to use other name.
Hello I've Created installer script for bliss x86 7.x.xx with help of grub installer script taken from remixos deb package file.
Make script executable
Then RunCode:chmod +x Bliss-x86-Installer-Linux
Code:./Bliss-x86-Installer-Linux
After much experimentation finally got Bliss x86 7.2 installed and running on my intel B75H2-TI motherboard. This ROM is brilliant and now replaces Remix OS. I used the nomodeset entry in the boot config file to get it to boot but would now like to set the video resolution to 1920 x 1080 for my AOC monitor. Is this possible and how can I do this - code in boot config file or somewhere I havnt found in settings?
Also Bluetooth isnt working for me. Any tips?
If you are using nomodeset, then it is likely not possible to use full resolutions of your graphics hardware. I would try to see if some of our other bleeding edge builds with the newer kernels might boot without needing to set nomodeset.
Surface book uses an IPTS screen, and none of our builds are compatible with those touchscreens yeti would like install this rom on my surface book but i tested any file but have not boot or no screen touch.
what file work for surface book?
thanks
This has been covered before, but it has to do with how Windows hibernate doesn't properly shut down hardware. It kinda just suspends the hardware state for easy resume. This messes with Linux/Android when it boots up and tried to modprobe the hardwareIll try this tommorrow. In the meantime I noticed a weird boot issue. Sometimes Bliss x86 7.2 stable with nomodeset boots to logo and hangs, i discovered that if I boot from a completely powered down boot and booted back into Win7 then shutdown to power off, then rebooted back into Bliss x86 I could get back to the home screen ( Root / SU updated). I was able to reproduce this, but can't fathom why. I installed from SD card onto a empty partition on a SSD. Any ideas?
Surface book uses an IPTS screen, and none of our builds are compatible with those touchscreens yet
Hi, I want to install this but I have a doubt if I could do it with my AMD E350
For those who are a little too bleeding edge and like to adventure outside the recommended method that @electrikjesus recommends, here's how to "prep" a USB using syslinux EFI to run Bliss 7.x/10.x.
Also, I'd appreciate it if he could link it in the first post as a "experimental syslinux EFI" method, because this is what I recommend if some Chinese tablets don't want to boot grub.
DO NOT BLAME HIM IF YOUR DEVICE CATCHES FIRE AFTER DOING THIS. BLAME ME INSTEAD.
I strongly recommend using a Linux VM or a Linux box for this. Ensure you have the latest version of unsquashfs (part of squashfs-tools) too. Grab the latest build of Bliss x86 7.x/10.x before continuing!
- Grab the ZIP file from my original post, https://xdaforums.com/showpost.php?p=74977694&postcount=1237, and extract it to the root of your USB drive. This will bootstrap syslinux EFI onto it.
- Make a folder, if you haven't already done so, called "android".
- Now, open up the ISO in an archiver. Extract from the root directory of the ISO image the following to your USB drive's "android" folder: initrd.img, ramdisk.img, kernel.
- Extract system.sfs to a folder somewhere, maybe in /tmp.
- Open a terminal and change directory (using 'cd') to /tmp. Run 'ls' and confirm you see system.sfs shown in the file list. If you get no output, start over as you misplaced a file.
Code:cd /tmp && ls -al system.sqs
- Run the following code:
This will make a new directory called "squashfs_root".Code:unsquashfs ./system.sqs
- Bliss 7.x users, this is important: If you are using Bliss 10.x then skip just this step. Change directory to squashfs_root and run a 'ls'. You should have only one file, a system.img inside that directory. Copy that file to your USB's "android" folder.
- Bliss 10.x users, this is important: If you are using Bliss 7.x then skip just this step. If you take a look inside squashfs_root, you will notice it's a complete android root filesystem. What we need to do is to move the stuff into a system image. The following will make a 2GB system.img file, format it, mount it and copy the contents of the extracted squashfs into that new disk image.
The sync process might take some time. Now copy the /tmp/system.img file to your USB's android folder.Code:mkdir /mnt/tempMount truncate /tmp/system.img --size=2G mkfs.ext4 -m0 /tmp/system.img sudo mount -o loop /tmp/system.img /mnt/tempMount sudo cp -prv /tmp/squashfs_root/* /mnt/tempMount/ sync sudo umount /mnt/tempMount
- Alright, now that's the system image done. Now you need to make a data image. That's easier than system image. First, find where your USB drive is mounted, it might be at "/media/icedcube/DROIDUSB" or something and cd to the android folder on it:
. If you're using Ubuntu or any other good distro and have a "Open location in Terminal" option in your File Manager, use that as a shortcut. Now run these commands to make a 3GB data image file - you could try with 4GB but FAT32 maxes out at 4GB per file and I prefer using FAT32 as I'm not sure if the kernel supports exFAT or NTFS properly.Code:cd /media/icedcube/DROIDUSB/android
This will be an completely empty ext4 disk image, but will be enough to kickstart Bliss.Code:truncate data.img --size=3G mkfs.ext4 -m0 data.img sync
- Finally, check to ensure everything is in check like so:
Code:<ROOT> - syslinux.cfg - android/ -- kernel -- system.img -- data.img -- ramdisk.img -- initrd.img - EFI/ -- BOOT/ --- bootia32.efi --- bootx64.efi --- ldlinux.e32 --- ldlinux.e64
- Need to add some kernel parameters? Don't panic. Just open syslinux.cfg and add them onto the append before the "initrd=/android/initrd.img" statement.
- Unmount the USB from your computer. Carefully plug it into your tablet or laptop and use the BIOS to boot UEFI from USB Drive, partition 1. If all goes well, you will get a black screen with small white text saying "Booting Android..." followed by loading files. You should get the Linux kernel text, then see the Bliss Oreo animation play after a few seconds/minutes depending on your USB drive read/write speed.
mountvol X: /S
taskkill /im explorer.exe /f
mountvol X: /s
explorer
taskkill /im explorer.exe /f
explorer
menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.sfs
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive quiet DATA=
initrd /AndroidOS/initrd.img
}
menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.sfs
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive quiet DATA=
initrd /AndroidOS/initrd.img
}
mountvol X: /D
mountvol Z: /D
menuentry 'Bliss-x86 Test-Oreo' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng quiet sleep.earlysuspend=2 DATA=
initrd /AndroidOS/initrd.img
}
menuentry 'Bliss-x86 Test-Oreo AUTO_LOAD=old' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng quiet DATA= AUTO_LOAD=old
initrd /AndroidOS/initrd.img
}
menuentry 'Bliss-x86 Test-Oreo - SETUP_WIZARD=0' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng SETUPWIZARD=0 quiet DATA=
initrd /AndroidOS/initrd.img
}
menuentry 'Bliss-x86 Test-Oreo - debug=1' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng SETUPWIZARD=0 quiet DATA= DEBUG=1
initrd /AndroidOS/initrd.img
}
menuentry 'Bliss-x86 Test-Oreo - debug=2' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng SETUPWIZARD=0 quiet DATA= DEBUG=2
initrd /AndroidOS/initrd.img
}
DATA=AndroidOS/
DATA=