Are you kindly invited to post here all news about this porting project.
Thanks
Alpine state of art
So today we have:
1) a kernel "zalp" that doesn't boot (http://jornada820.sf.net/files/uni)
2) a lot of tests by haret (in "xanadux: linux for xda" topic)
the last of them said that Alpine, maybe, hasn't an ASIC3 chip
3) we need an Alpine motherboard picture (can anyone help ?)
And we wait for instructions/corrections to make kernel boot asap.
Thanks for every contributions. Bye
Hello renatostore
I found some pictures in the www
I'm not shure if they are good enough :?
http://www.modaco.com/lofiversion/index.php/t232579.html
Im always waiting good news about Linux on Alpine...... any good news? cr2?
So I have found som e Linux files but how'd you get them to boot up?
I dont care if it works or not at the moment. I just want to get booting for now before I start fiddling.
hi,
if Alpine hasn't an ASIC3 chip, then what it got????
symondavis said:
So I have found som e Linux files but how'd you get them to boot up?
I dont care if it works or not at the moment. I just want to get booting for now before I start fiddling.
Click to expand...
Click to collapse
I tried to boot kernel zuni-20060421 in this way:
1- download from http://jornada820.sf.net/files/uni some files (zuni-20060421, rd, startup.txt, gnuharet)
2- I changed startup.txt in this way
set KERNEL "zuni-20060421"
3- I upload all these files in pda storage card
4- I started gnuharet from pda
5- I changed default.txt with startup.txt and pushed run
Results:
only a black box in the middle of the screen within an horizontal line that changed color from blue to red. That's it.
After a soft reset to unlock the pda I had to reinstall OS (like hard reset).
Any suggestions?
Can anyone help us to leave this stall state ?
Only Alpine is still without a booting Linux today.
renatostore said:
Can anyone help us to leave this stall state ?
Only Alpine is still without a booting Linux today.
Click to expand...
Click to collapse
I agree with you..... could anyone help us????
clustered said:
I agree with you..... could anyone help us????
Click to expand...
Click to collapse
The new test image is closer than you think
cool!!!!
clustered said:
cool!!!!
Click to expand...
Click to collapse
zalp-2.6.16-hh2
at the same location. Test it and let me know about the
results.
I need to know if my startup.txt file is correct:
Code:
set KERNEL "zalp-2.6.16-hh2"
set MTYPE 855
set INITRD "Storage Card\rd"
set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitrd console=tty0 mem=63M"
boot2
the first line is for kernel name
the second ??
the third is the location of the ramdisk image
the forth looks like parameters for kernel
the fifth ??
Could anyone explain it to me ?
Thanks
renatostore said:
Code:
set KERNEL "zalp-2.6.16-hh2"
set MTYPE 855
set INITRD "Storage Card\rd"
set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitrd console=tty0 mem=63M"
boot2
Click to expand...
Click to collapse
the first line is for kernel name
Click to expand...
Click to collapse
Yes. It is called 'zImage' because it is the compressed
kernel combined with the decompressor.
the second ??
Click to expand...
Click to collapse
MachineTYPE:
Code:
himalaya -> 448
blueangel -> 766
universal -> 855
magician -> 875
apache -> 959
alpine -> 999
beetles -> 1003
Newer haret versions autodetect the MTYPE
and set it to the correct value regardless of what you
have provided (or not provided).
If you want to override this autodetected value
(usually for testing, if you know what you are doing),
use FORCEMTYPE
the third is the location of the ramdisk image
Click to expand...
Click to collapse
Yes. If you need the ramdisk. You don't need it if your
Linux system is already on the MMC/SD card and you boot from the MMC/SD card.
the forth looks like parameters for kernel
Click to expand...
Click to collapse
Yes. There are usually two combinations:
one for the ramdisk, another for the MMC/SD card.
the fifth ??
Click to expand...
Click to collapse
Boot linux command.
According to you, which should be the correct startup.txt file for a linux first booting ?
Could you type a sample ? Thanks
This is my experince running the new kernel with this startup.txt file:
Code:
set KERNEL "zalp-2.6.16-hh2"
set MTYPE 999
set INITRD "Storage Card\rd"
set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitrd console=tty0 mem=63M"
boot2
A black square in the bottom of the screen with a blue horizontal line in the mids becaming red. Then appear an output from gnuharet saying:
Code:
detected cpu family: PXA2xx
boot MTYPE=999
RAM: [email protected]
and the xda started vibrating. I stoped it by a soft reset and, this time, no reinstall of OS was needed.
It says nothing to me ...
renatostore said:
and the xda started vibrating.
Click to expand...
Click to collapse
Vibrating is a good sign, but you need to know how
to switch it off.
Please, replace the kernel parameter string by
Code:
set CMDLINE "root=/dev/mmc/blk0/part2 console=tty0 mem=63M"
and try again.
It will probably crash, but i'd like to know if you will see
the penguin and kernel boot messages on the LCD.
Same result
After the usual black box with blue/red lines I saw a penguin sliding fastly form the top to the bottom of my display. I used this startup.txt file:
Code:
set KERNEL "zalp-2.6.16-hh2"
set MTYPE 999
set CMDLINE "root=/dev/mmc/blk0/part2 console=tty0 mem=63M"
boot2
then xda started vibrating and I had to hard reset to stop it.
renatostore said:
After the usual black box with blue/red lines I saw a penguin sliding fastly form the top to the bottom of my display.
Click to expand...
Click to collapse
Ok. penguin was sliding ? or the text ?
Can you see the text ?
then xda started vibrating and I had to hard reset to stop it.
Click to expand...
Click to collapse
Vibrating is not a problem, i can switch it off.
If you see the text on the screen, try to partiton your SD
card like it is described in the Universal wiki, and
install the opie image from universal.
Then boot again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Bliss is pleased to present to you
Bliss based on Android Oreo
Our focus is to bring the Open Source community a quality OS that can run as a daily driver, syncing your apps, settings and customizations across all platforms you run Bliss on.
Bliss OS comes with a wide selection of customization options, functions, and is even themable out of the box using rootless Substratum. With so many options available, you will soon find out why we call it Bliss.
Notice
- Please do not ask for ETA's;
- We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts;
- We will do our best to answer your questions or concerns as soon as possible.
AIO Thread
Bliss Source
https://github.com/BlissRoms
Bliss-x86 Source
https://github.com/BlissRoms-x86
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
BlissRoms Kernel Source
https://github.com/BlissRoms-Kernels
BlissRoms Vendor Source
https://github.com/BlissRoms-Vendor
OpenGapps are included in Bliss-x86. YAY!!
Our Official downloads have been cleaned in preparation for Android Pie
Bliss OS x86 - Current Releases
All recent builds have been moved to Sourceforge
Bliss OS x86 - Sourceforge Archived Releases
Bliss OS x86 - AFH Archived Releases
Team Bliss is not responsible in any way for anything that happens to your device in the process of flashing.
Please familiarize yourself with flashing and custom rom use before attempting to flash the rom.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Please scroll down to second and third posts for install instructions and downloads
one build, thousands of potential component combinations, so not everything will be working on every machine, and we know this.
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
-You can also open trouble tickets on our website for bugs.
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
If someone takes it upon themselves to donate to us, of course it will be appreciated, and all funds will be used to pay our server and upkeep fees.
If someone wants to donate, our PayPal link is below.
PayPal Link
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads.
Please post in the general forums for off-topic comments and/or questions.
Overall, please keep comments relevant to development, as this better helps you and our team
when trying to determine problems that users are having.
We appreciate all levels of knowledge in our threads, and therefore we ask that
the seasoned members be helpful to those with less knowledge.
Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts.
We thank you for adhering to our thread rules.
Thank you for using Bliss! And have a Blissful Experience!
XDA:DevDB Information
Bliss-x86, ROM for all devices (see above for details)
Contributors
electrikjesus, rwaterspf1, ElfinJNoty
Source Code: https://github.com/BlissRoms-x86/kernel_common
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Read the Instructions
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: Bliss-x86 7.1.x Stab
Stable Release Date: 2017-03-19
Current Beta Version: Bliss OS 10.0 PC Bet
Beta Release Date: 2017-03-21
Created 2017-01-09
Last Updated 2018-09-01
Reserved
The Instructions
**These instructions are based on the Android-x86 project's installation guide. We have not changed the installer, so all actions still apply. Also thanks to @bg260 for his contributions, this guide was adapted partially from his work**
*** Team Bliss will not accept any responsibility for users who have not read or understand the instructions, or any damage done to user machines due to lack of understanding all risks involved. You accept all responsibility by continuing beyond this point. ***
*** Any questions, install issues, bug reports, etc will be delightfully ignored unless accompanied with a log, device info, build info, install method, and any other information required to diagnose your issue as NOT user error ***
Please note that our Archived build instructions can be found in the fourth post. Many of the processes may still apply to our newer builds too, so please read and follow the links provided to learn more about each step. Thank You
Easy Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)
** This method might be the easiest currently **
For the overall instructions on using this method, please refer to the tools original thread: https://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
I have taken some time to update the tool for easy install on UEFI/ESP machines. The builds I produce can be found here:
https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows/tree/master/bin
And the source for those builds can be found here: https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows
This tool should work on RemixOS as well, but I have not tested it yet (been too busy on this project)
Part 1 - Using the Installer
The installer has been updated, and it will accept the .iso files for our 8.x/10.x releases. Just follow the prompts the installer gives. Refer to the orig thread for any questions, and please search before asking.
Part 2- Switching the UEFI/EFS boot entry
Open the EasyUEFI tool mentioned above, then switch the UEFI/EFI entry it created to boot first. Close and reboot.
How to "prep" a USB using syslinux EFI to run Bliss 7.x/10.x
Thanks to @IcedCube
IcedCube said:
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://forum.xda-developers.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:
Code:
unsquashfs ./system.sqs
This will make a new directory called "squashfs_root".
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.
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
The sync process might take some time. Now copy the /tmp/system.img file to your USB's android folder.
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:
Code:
cd /media/icedcube/DROIDUSB/android
. 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:
truncate data.img --size=3G
mkfs.ext4 -m0 data.img
sync
This will be an completely empty ext4 disk image, but will be enough to kickstart Bliss.
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.
Click to expand...
Click to collapse
Custom Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)
***Again, Team Bliss is not responsible for any damage, tears, lost time, alien abductions, experimental relationships or anything else if things go south with this install. Don't even think about blaming us. You automatically agree to these terms upon continuing the install.***
Part 1 - Mounting Your UEFI/ESP Partition
You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window image attached to this post.
Once that is open, type in:
Code:
mountvol X: /S
Then check to see if it is mounted already
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (X or type in "x:" in the filepath bar"
If you cannot access X:, then that could mean one of three things. 1) You have an ESP setup, and just need to scroll down to the ESP System Partition setups section, or 2) You have a legacy MBR setup and just don't know it. or 3) Your setup falls within the other category. Check below for some insight, or the second post for more links to help you figure things out.
ESP System Partition setups
Windows 10 has EFI partition sometimes already mounted under Z: letter, but it's hidden.
A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z or type in "z:" in the filepath bar"
Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor
Save the file and your're ready to go
If this still doesn't work - try this:
Run CMD.exe as Admin <- IMPORTANT Then enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Code:
Code:
mountvol X: /s
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Then type:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Part 2 - Run Explorer as Admin
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Then type:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
Part 3 - Roll You Own UEFI Install
Let's start by downloading the needed files. Here is a customized UEFI boot for 32 & 64 bit machines. https://www.androidfilehost.com/?w=files&flid=143191
**NOTE: If you came from our nougat builds to our Bliss-x86 8.x builds, you will have to edit the grub.cfga bit. Please see below **
If you are using Bliss-x86 8.x/10.x, please use the grub entry below as a guide:
Code:
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
}
(EXT3/EXT4 installs) (NOTE: Due to a bug on ext3/ext4 installs, please use the grub setup below)
Code:
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
}
Now that we have the partition mounted, we can copy that BOOT dir to your UEFI partition using Explorer as admin or using the New Task dialog from Task Manager. (look up for a refresher on both of those) Once it is copied, go back to the admin CMD prompt and type:
Code:
mountvol X: /D
or if you used Z:, type:
Code:
mountvol Z: /D
This will dismount the UEFI/ESP volume for safe reboot. we then suggest you use EasyUEFI here to create the UEFI boot entry. Open the app, and create a new entry. Select your UEFI partition, and in the File Path, click Browse and use the file manager window to browse to your BOOT/grub/grubx64.efi file. Click OK, and then choose the new grub entry and move it to the top. Make sure secure boot is turned off or else it likely will just boot back to Windows.
Part 4 - The Manual Blissification of Your PC
To do a manual "Wubi like" install of Bliss-x86 after you install the UEFI entry, you will need to open the Bliss-x86 .iso/img with 7zip, and then drag all the .img & .sfs files to C:/android-x86 or whatever your target drive is (make sure your grub entries match where you are putting these). Then create your data.img, we suggest using a tool like one from XDA called RMXtools (use ver 1.7) to create it. Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside that android-x86 folder.
You can now reboot, if you have installed the custom UEFI entry right and selected it using EasyUEFI, you should boot right to the Android-x86 grub theme. There you can use up and down to select, and return to boot that entry. You can also hit e to edit the selected entry. You will want to pay attention to which entry you select, since there will be one for Bliss-x86(32bit) and one or Bliss-x86_64(64bit).
Install Bliss-x86 using a VM (virtualbox)
This method does require some beefy PC specs, so it might not work for all. (Info provided by Chih-Wei Huang, from Android-x86 Project)
We could fill up an entire section on this part alone, so here's a couple videos to help you figure things out.
If things still aren't working right for you, chances are it's hardware related.
( check cat /proc/cpuinfo )
USB based install of Bliss-x86 8.0/10.x (32bit or 64bit)
Part 1 - Gather Your Tools
** Please note that our Bliss-x86 builds do not currently support this install method for all machines **
For this method, we are going to want to download Rufus, and the 32bit .iso or 64bit .iso/.img file of Bliss-x86. And you are going to need a decent speed USB drive (4gb or larger is recommended). Once we have those tools, we can move on.
Part 2 - Flashing Bliss-x86 to the USB drive
Plug in your USB drive, and load up Rufus. Once loaded, click on the icon next to the ISO Image dropdown menu. Now browse to where you have your Bliss-x86 (32bit) .ISO, or your Bliss-x86_64 (64bit) .ISO/.IMG file. Once chosen, the dropdown should switch to the correct image type, and fill the rest in for you. Once you are ready, click Start.
Part 3 - Testing Bliss on your system !!IMPORTANT STEP!!
### If you as a user do not test the OS first to make sure it is compatible with your device, please do not expect us to support you if you happen to just install it and something goes wrong. You continued to scroll past all of our warnings about reading and understanding what you are doing, so it's all on you###
From here, you can choose to reboot your machine, and make sure it can boot to USB from BIOS. Once that is set, reboot and choose the USB. If everything went smoothly on the install process, you should see a Grub boot screen. Select the "Live CD" option, and if your machine is compatible, you should then see a little bit of text, and then the Bliss bootanimation. This will go on for a few minutes, but should eventually boot to Bliss-x86. If the system never boots to Bliss-x86, this is a good sign that your system might not be able to run it. If it does boot, and you would like to install it, continue to the next step.
Part 3.5 - Using Bliss-x86 from your USB drive
If you so choose to use Bliss from the USB drive, your data will be saved in a temporary state unless you create a data.img to store the data. We can create a data.img in the root dir of the USB drive (make sure you have a minimum 4-5gb free). We suggest using a tool like one from XDA called RMXtools to create it (we suggest you use version 1.7). Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside the root directory of your USB drive, with all the other .img files. From there, just boot into live mode, setup your system the way you want. and the data should be persistant across a reboot now.
Part 4 - Setting up and Installing Bliss-x86 on your HDD/SSD/SDcard
***Team Bliss is not responsible for any damage, tears, lost time, broken marriages, hallucinations or anything of the sort if things go south with this install. Don't even think about blaming us. You automatically agree to these terms upon continuing the install.***
This is where things start to get a little tricky, especially with how PC's vary. Make sure you have a backup plan in case something goes wrong.
Start off by opening your favorite Partition Management software, and create a new partition, making it the size you want (suggested minimum is 8gb.). Just format it to NTFS for now, because it will be changed by the installer later anyways. Remember what drive you setup here, it's important. For Windows machines, it will typically be Sda4 or Sda5. Also create another 300mb FAT32 partition for Grub to install to. (This part might require a third-party partition manager, Windows disk manager won't let it be that small)
Boot up the Bliss-x86 USB, and select the Installation option from Grub. (second one down)
The installer will load, and you will have an option to choose which partition you created earlier. Pick it, and select Ext4. ***You don't want to get this step wrong. If you are unsure, please boot back to Windows, and write it down this time. It will be Sd** typically.***
When it asks if you want to install System as R/W, select YES.
When it asks if you want to install Grub, select Grub for Legacy BIOS boot type, Grub2 for UEFI boot type, or neither if you are already running a Linux system.
If you chose to install a Grub option, the installer will allow you to choose. Make sure you select the 300mb partition you setup earlier for Grub.
The process will install and create the data directory/img, so go get a drink or something and come back to it.
When finished, the installer will then ask if you want to run Android-x86, you can just reboot here, and make sure you remove the USB drive.
If we have followed all the directions correctly, you should be presented with a Grub boot menu. You can choose your bliss_android_x86 option (or android-x86), and it will boot into Bliss-x86. If you feel the need to customize your grub boot entry, please search the web first. We use the same grub setup that Android-x86 project uses. so their forums will contain just about all the info you will need.
Common command line options (Grub commands)
With Bliss OS on the PC, we tend to use quite a few command line options to get things working right. we've gathered a few of them here to explain them a little bit.
sleep=1
This will enable the system.prop value for sleep.earlysuspend=1, and on some machines, it enables the proper sleep state.
acpi_sleep=s3_bios,s3_mode
Sometimes needed for older machines to enter sleep mode properly
SETUPWIZARD=0
This command will skip SetupWizard on boot. (Only needs to be run once)
AUTO_LOAD=old
This will load android-x86 variants using the old modprobe method to init devices. We sometimes use this to debug devices not starting.
DEBUG=1 & DEBUG=2
These enable verbose console debugging, giving another command shell after loading kernel modules, but before Android init
vga=xxx & video=
These are the common video modes that you can boot into if it doesn't pick the best choice automagically
You can also use video= as resolution parameters: video=LVDS-1:d video=1366x800 , learn more from our own
Henri Koivuneva: https://groups.google.com/forum/#!msg/android-x86/jSF3RnADnqA/1sfYdGV_AQAJ
nomodeset
This will load mostly everything in software rendering/support mode. No hardware acceleration. Good for debugging.
HWACCELL=1
This will disable graphics hardware acceleration, enabling rendering through Swiftshader. (Must use this if running headless)
buildvariant=eng, user, userdebug
This is the command line perimeter to run the current build as eng, userdebug, or user
DPI=xxx
This will manually set the DPI on init. Use this if things are too big/small for you.
As an example, here are a few of the boot options I use in testing:
Code:
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
}
Downloads:
!!!!BEFORE YOU SCROLL DOWN!!!
We offer a few different types of downloads for Bliss-x86. Stable, EDU, & Bleeding Edge builds. Below is a short run-down of what that means to you.
Stable Builds - kernel-4.9.x/etc
These builds use the most stable branches we have for the kernel & OS. This is usually right in line with what the Android-x86 project has unless there are some incompatibilities. These are updated regularly, but least often.
EDU Builds (discontinued for now) - Kernel-4.4.x/kernel-4.9.x/4.11.x
These builds are a rootless version of Bliss, packaged with rootless Substratum and a ton of features to still allow customization without compromising security. Perfect for not only the classroom, but the corporate environment as well. These builds are released with both kernel-4.4 & kernel-4.10/4.11 for a broad compatibility range. This branch is still a work in progress
Bleeding Edge Builds - kernel-4.9.x/Kernel-4.10.x/4.11.x/4.12.x/4.14x/4.15x/4.16x/4.17x
These builds will usually contain one of the newer kernels we are working on, and these builds could be almost weekly, as this will be used as our testing branch. This also means, these builds will see features that may or may not be included in the stable releases. Eventually, once this branch is stable enough, it is what gets pushed to the Stable branch for release.
Nightlies - kernel-4.9.x/4.15x/4.16x/4.17x
These are where our most recent changes can be seen. We use Jenkins for tasking these builds, so some may have issues, some may not. !!These builds may break things!! So please tread carefully when testing the nigltlies.
What do all the extra things in the filenames mean?
Our builds include a ton of changes between each build, so to make things easier for all of you, we try to add some extra info to the filenames.
Typical build name: Bliss-v10.0-Beta-android_x86_64-OFFICIAL-20180312-1933_k4.15-sb-ga-jwd_m17.3.6_surface-book.iso
So, we will break this down into parts for you. We always list it by Kernel ver, then Mesa ver, followed by abreviations for the changes in that build or trailed with a target device label.
Kernel ver: k4.15-sb-ga-jwd
This represents the kernel branch name used in this build. But what do the acronyms mean? Well, when I add any number of commits from a given remote, I usually use a three letter acronym for the remote. For example, jwd stands for this remote: https://github.com/jwrdegoede/linux-sunxi Or when I use ga, it is short for GalliumOS: https://github.com/GalliumOS/linux
Mesa ver: 17.3.6
This represents also, the branch name for mesa
Trailing notes (not always)
These are usually the last word or two of the filename. The represent any device specific commits that have been added to the builds.
!!Please Note!!
Just because you see a target device in the filename, doesn't mean that build won't work for other devices. It only means that that build contains specific commits or firmware files for that target device. In the case of our Surface builds, they will ALL work on other devices. The drivers and firmware is still there for those to work.
Bliss OS for PC Downloads - Stable, EDU, Nightlies & Bleeding Edge Builds
Current Releases: https://downloads.blissroms.com/BlissOS/
Archived Releases: https://sourceforge.net/projects/blissos-x86/files/Official
https://www.androidfilehost.com/?w=files&flid=136638
n7x / mm6.0 - Bliss-x86 - 6.4-7.x - NO LONGER SUPPORTED
**Development on our Bliss-6.4 through 7.x builds have stopped in favor for oreo builds. Please do not ask for any further development on our marshmallow builds. You will be answered with sarcasm**
Archived Released: https://www.androidfilehost.com/?w=files&flid=127970
LATEST UPDATE:
https://forum.xda-developers.com/showpost.php?p=77160012&postcount=2209
!!New Bliss-x86 v10.1 PC Beta - 07/16/2018
We have a somewhat transitional update for you all today. I rebased BlissOS off our GSI project (Bliss-Bass), and the outcome is actually pretty stable. Some old issues have returned, and some have been resolved. Most of the details can be found below in the Updates/Additions or the Changelog. Build might take a while to upload, so keep checking back.
Have FUN!!
Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180716-1838_k4.15.18-ipts_18.1.0-devel_w14_dev-kernel.org.iso - This contains firmware for all current devices included in kernel.org. - THIS BUILD INCLUDES OpenGapps
Updates / Additions:
Kernel 4.15.18 - reworked for all devices, and added IPTS commits *Surface devices will require manual firmware update*
Moved to old way of packaging the system image. (for root to work, you must extract the system.img file from within the system.sfs, then delete the system.sfs file)
Rooted with Superuser. Access Superuser settings from Settings>Users (R/W works if you extract system.img, read above)
Substratum Service mode enabled (now fully working, but reboot required after you build/enable a theme. select from Settings>Display>Advanced>Themes)
A few fixes and updates for Bluetooth
Fixes for some devices that didn't boot right
Using Android-x86's newest updates to bootable/newinstaller (this comes with a new UEFI grub menu)
Maybe more... I've been busy
Bugs / Issues:
Android Service Has Stopped dialog is back. It does not harm anything though.
Bluetooth issues still exist on some devices
you will get Play Store and process crashes until WiFi is connected. Just dismiss these for now. Once connected to WiFi, things should work properly. **ONLY ON OPENGAPPS BUILDS**
Sound or keyboard might not work, try to boot using the secondary modprobe option
Expect more. It's only a beta release. Report your issues, but make sure you SEARCH the thread first to make sure it hasn't been answered. And post logs too (I know, WTF are logs anyways??)
As always, check the Bliss download site for the newest builds. The rest are all on AFH as a backup archive. Hope you all enjoy this one
https://downloads.blissroms.com/BlissOS/bleeding_edge/
Archived Instructions for old versions of Bliss OS for PC
**These instructions are based on the Android-x86 project's installation guide. We have not changed the installer, so all actions still apply. Also thanks to @bg260 for his contributions, this guide was adapted partially from his work**
*** Team Bliss will not accept any responsibility for users who have not read or understand the instructions, or any damage done to user machines due to lack of understanding all risks involved. You accept all responsibility by continuing beyond this point. ***
*** Any questions, install issues, bug reports, etc will be delightfully ignored unless accompanied with a log, device info, build info, install method, and any other information required to diagnose your issue as NOT user error ***
For Bliss-x86 6.4/7.x USB based installs (32bit or 64bit)
Part 1 - Gather Your Tools
** Please note that our Bliss-x86 n7.x builds do not currently support this install method for all machines **
For this method, we are going to want to download Rufus, and the 32bit .iso or 64bit .iso/.img file of Bliss-x86. And you are going to need a decent speed USB drive (4gb or larger is recommended). Once we have those tools, we can move on.
Part 2 - Flashing Bliss-x86 to the USB drive
Plug in your USB drive, and load up Rufus. Once loaded, click on the icon next to the ISO Image dropdown menu. Now browse to where you have your Bliss-x86 (32bit) .ISO, or your Bliss-x86_64 (64bit) .ISO/.IMG file. Once chosen, the dropdown should switch to the correct image type, and fill the rest in for you. Once you are ready, click Start.
Part 3 - Testing Bliss on your system
From here, you can choose to reboot your machine, and make sure it can boot to USB from BIOS. Once that is set, reboot and choose the USB. If everything went smoothly on the install process, you should see a Grub boot screen. Select the "Live CD" option, and if your machine is compatible, you should then see a little bit of text, and then the Bliss mm6.0 bootanimation. This will go on for a few minutes, but should eventually boot to Bliss-x86. If the system never boots to Bliss-x86, this is a good sign that your system might not be able to run it. If it does boot, and you would like to install it, continue to the next step.
Part 3.5 - Using Bliss-x86 from your USB drive
If you so choose to use Bliss from the USB drive, your data will be saved in a temporary state unless you create a data.img to store the data. We can create a data.img in the root dir of the USB drive (make sure you have a minimum 4-5gb free). We suggest using a tool like one from XDA called RMXtools to create it (we suggest you use version 1.7). Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside the root directory of your USB drive, with all the other .img files. From there, just boot into live mode, setup your system the way you want. and the data should be persistant across a reboot now.
Part 4 - Setting up and Installing Bliss-x86 on your HDD/SSD/SDcard
***Team Bliss is not responsible for any damage, tears, lost time, broken marriages, hallucinations or anything of the sort if things go south with this install. Don't even think about blaming us. You automatically agree to these terms upon continuing the install.***
This is where things start to get a little tricky, especially with how PC's vary. Make sure you have a backup plan in case something goes wrong.
Start off by opening your favorite Partition Management software, and create a new partition, making it the size you want (suggested minimum is 8gb.). Just format it to NTFS for now, because it will be changed by the installer later anyways. Remember what drive you setup here, it's important. For Windows machines, it will typically be Sda4 or Sda5. Also create another 300mb FAT32 partition for Grub to install to. (This part might require a third-party partition manager, Windows disk manager won't let it be that small)
Boot up the Bliss-x86 USB, and select the Installation option from Grub. (second one down)
The installer will load, and you will have an option to choose which partition you created earlier. Pick it, and select Ext4. ***You don't want to get this step wrong. If you are unsure, please boot back to Windows, and write it down this time. It will be Sd** typically.***
When it asks if you want to install System as R/W, select YES.
When it asks if you want to install Grub, select Grub for Legacy BIOS boot type, Grub2 for UEFI boot type, or neither if you are already running a Linux system.
If you chose to install a Grub option, the installer will allow you to choose. Make sure you select the 300mb partition you setup earlier for Grub.
The process will install and create the data directory/img, so go get a drink or something and come back to it.
When finished, the installer will then ask if you want to run Android-x86, you can just reboot here, and make sure you remove the USB drive.
If we have followed all the directions correctly, you should be presented with a Grub boot menu. You can choose your bliss_android_x86 option (or android-x86), and it will boot into Bliss-x86. If you feel the need to customize your grub boot entry, please search the web first. We use the same grub setup that Android-x86 project uses. so their forums will contain just about all the info you will need.
Easy Install For Bliss-x86 6.4/7.x MBR (32bit or 64bit)
** This method is the easiest install method for MBR/GPT boot setups, but it does require Windows to install. **
For the overall instructions on using this method, please refer to the tools original thread: https://forum.xda-developers.com/showthread.php?t=2142563
I have taken some time to update the tool for easy install on UEFI/ESP machines. The builds I modified can be found here: https://www.androidfilehost.com/?w=files&flid=185778
Part 1 - Using the Installer
The installer has been modified, and will read and install any 32bit or 64bit Bliss-x86 build onto a GPT/MBR type setup. Just run the installer, pick the Bliss-x86 .iso file, and select your size data.img. If you require a size data.img larger than what is available, please use the RMXtools v1.7 mentioned in this post elsewhere.
Easy Install For Bliss-x86 6.4/7.x UEFI/ESP (32bit or 64bit)
** This method might be the easiest currently, but there's a trick to get proper root for now. **
For the overall instructions on using this method, please refer to the tools original thread: https://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
I have taken some time to update the tool for easy install on UEFI/ESP machines. The builds I produce can be found here:
https://www.androidfilehost.com/?w=files&flid=140019
And the source for those builds can be found here: https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows
This tool should work on RemixOS as well, but I have not tested it yet (been too busy on this project)
Part 1 - Using the Installer
The installer has been updated, and it will accept the .iso files just fine now, as well as allow proper root with one simple trick. If you do not want to use root (which is needed for Substratum to work), then just install as normal.
If you do want root, go through the directions like normal, and after install is finished, browse to the AndroidOS directory it created and delete the system.sfs file.
Part 2- Switching the UEFI/EFS boot entry
Open the EasyUEFI tool mentioned above, then switch the UEFI/EFI entry it created to boot first. Close and reboot.
Custom Install For Bliss-x86 6.4/7.x UEFI/ESP (32bit or 64bit)
***Again, Team Bliss is not responsible for any damage, tears, lost time, alien abductions, experimental relationships or anything else if things go south with this install. Don't even think about blaming us. You automatically agree to these terms upon continuing the install.***
Part 1 - Mounting Your UEFI/ESP Partition
You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window image attached to this post.
Once that is open, type in:
Code:
mountvol X: /S
Then check to see if it is mounted already
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (X or type in "x:" in the filepath bar"
If you cannot access X:, then that could mean one of three things. 1) You have an ESP setup, and just need to scroll down to the ESP System Partition setups section, or 2) You have a legacy MBR setup and just don't know it. or 3) Your setup falls within the other category. Check below for some insight, or the second post for more links to help you figure things out.
ESP System Partition setups
Windows 10 has EFI partition sometimes already mounted under Z: letter, but it's hidden.
A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z or type in "z:" in the filepath bar"
Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor
Save the file and your're ready to go
If this still doesn't work - try this:
Run CMD.exe as Admin <- IMPORTANT Then enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Code:
Code:
mountvol X: /s
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Then type:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Part 2 - Run Explorer as Admin
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Then type:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
Part 3 - Roll You Own UEFI Install
Let's start by downloading the needed files. Here is a customized UEFI boot for 32 & 64 bit machines. https://www.androidfilehost.com/?w=files&flid=143191
**NOTE: For our Bliss-x86 n7.x builds, you will have to editr the grub.cfg and remove the androidboot.hardware... command. I will update this post more in the future with more details **
If you are using Bliss-x86 n7.x, please use the grub entry below as a guide:
Code:
menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.img
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/AndroidOS
initrd /AndroidOS/initrd.img
}
(EXT3/EXT4 installs) (NOTE: Due to a bug on ext3/ext4 installs, please use the grub setup below)
Code:
menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.img
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=
initrd /AndroidOS/initrd.img
}
Now that we have the partition mounted, we can copy that BOOT dir to your UEFI partition using Explorer as admin or using the New Task dialog from Task Manager. (look up for a refresher on both of those) Once it is coppied, go back to the admin CMD prompt and type:
Code:
mountvol X: /D
or if you used Z:, type:
Code:
mountvol Z: /D
This will dismount the UEFI/ESP volume for safe reboot. we then suggest you use EasyUEFI here to create the UEFI boot entry. Open the app, and create a new entry. Select your UEFI partition, and in the File Path, click Browse and use the file manager window to browse to your BOOT/grub/grubx64.efi file. Click OK, and then choose the new grub entry and move it to the top. Make sure secure boot is turned off or else it likely will just boot back to Windows.
Part 4 - The Manual Blissification of Your PC
To do a manual "Wubi like" install of Bliss-x86 after you install the UEFI entry, you will need to open the Bliss-x86 .iso/img with 7zip, and then open the system.sfs inside 7zip, and extract the system.img file to C:/android-x86 or whatever your target drive is. After that, extract the rest rest of the contents to the android-x86 folder. Then create your data.img, we suggest using a tool like one from XDA called RMXtools (use ver 1.7) to create it. Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside that android-x86 folder.
You can now reboot, if you have installed the custom UEFI entry right and selected it using EasyUEFI, you should boot right to the Android-x86 grub theme. There you can use up and down to select, and return to boot that entry. You can also hit e to edit the selected entry. You will want to pay attention to which entry you select, since there will be one for Bliss-x86(32bit) and one bor Bliss-x86_64(64bit).
Bliss-x86 6.4/7.x Custom UEFI/ESP Method Update Instructions:
To do this you will have to make some sacrifices to let this go through successfully. This will of course cause a few of your ROOT apps and tweaks that were written to system to vanish, so after we are done, you will have to reapply/reinstall those
Using the .iso/.img from the Bliss website
You need to grab the .iso/img file for the updated version of Bliss-x86, then we can upgrade manually with no issues usually, but you will have to do this from Windows (or your OS of choice). Open the Bliss-x86 .iso/img with 7zip, and then open the system.sfs inside 7zip, and extract the system.img file to C:/android-x86 or whatever your target drive is, overrighting the existing file. After that, extract the rest rest of the contents to the android-x86 folder:
initrd.img
ramdisk.img
kernel
I also replace the install.img and isolinux.sys files, but I don't think they are needed. I'm just lazy and drag it all over from the .zip
Once that is done, you can reboot
Bliss-x86 6.4 Xposed Install Instructions (32bit or 64bit):
*** There is the potential to screw up your Bliss-x86 install by installing Xposed. Do not continue if you do not know what you are doing. Team Bliss will not be held responsible.***
Part 1 - Installing Xposed APK:
Start off from your Bliss-x86 installation by heading to this thread and downloading DVDandroid's XposedInstaller. Once you have it downloaded, install the .apk file.
Part 2 - 32bit Xposed Install (scroll down for 64bit):
You need to grab this Xposed.zip while using the 32bit Bliss-x86 (Thanks to Martin over on the Android-x86 Google Groups for this). Once you have the download, use SolidExplorer or a simular file explorer to extract the contents to your data partition. We recommend extracting it to sdcard/xposed . Now we need to open a terminal app, and type:
Code:
su
Grand it permissions, and then type:
Code:
cd sdcard/xposed
Then type:
Code:
sh flash-script.sh && reboot
If everything goes smoothly, your PC should finish the install, and reboot. Choose your version of Bliss-x86 upon reboot, and wait. It might take a little longer to boot up this time. **Please note that this does not work on all machines. There are some that it will not work for. If you are using one, you will need to extract the system.img file from the iso back to the system partition or directory you have Bliss-x86 installed on**
Part 2 - 64bit Xposed Install:
You need to grab this Xposed64.zip while using the 64bit Bliss-x86 (This one comes from HypoTurtle over on XDA). Once you have the download, use SolidExplorer or a simular file explorer to extract the contents to your data partition. We recommend extracting it to sdcard/xposed . Now we need to open a terminal app, and type:
Code:
su
Grand it permissions, and then type:
Code:
cd sdcard/xposed64
Then type:
Code:
sh flash-script.sh && reboot
If everything goes smoothly, your PC should finish the install, and reboot. Choose your version of Bliss-x86 upon reboot, and wait. It might take a little longer to boot up this time. **Please note that this does not work on all machines. There are some that it will not work for. If you are using one, you will need to extract the system.img file from the iso back to the system partition or directory you have Bliss-x86 installed on**
Adding ARISE Sound Systems to Bliss-x86 n7.1.1 (64bit only)
**NOTE: This might not work as intended on some 32bit installs, and it also will break standard AOSP audio visualization. You have been warned!! **
(Basic Tutorial)
To start off, I would like to state that this can mess things up if you don't know what you're doing, or if you have already added stuff to your system.img, or if you copy/delete the wrong files, etc. You get the point. Team Bliss is not responsible for your mistakes. If your having second thoughts, please ask first and provide as much detail as possible. This isn't a Twitter post.
Now that we're through the ugly part, let's get on to making Bliss-x86 sound better First you will need to grab the files. [URL]https://www.androidfilehost.com/?fid=24651430732237629
All the work done on this is due to A.R.I.S.E. Sound Systems™, so make sure you thank them properly if you like what you hear
PART 1
Once you download the .Zip, use a root file manager, like SolidExplorer to extract it to a folder on your SD. Open that folder up and navigate to the numbers directory. Select all the contents of that directory and copy it to the /root/system/ folder. Overight and files and merge any folders needed.
View attachment 4023464
PART 2
Now we have to navigate to the priv-app folder in /root/system/, and create a new folder called ViPER4Arise . Then navigate back to the root of the extracted zip, and go to /customize/app. Copy the two .apk's there, along with the x86 folder to the new directory you created in /root/system/ then install each one and reboot.
View attachment 4023478
PART 3
Once reboot is complete, load up the ViPER4Arise app, and it will ask to install the driver. Grant it su permissions and any other permissions it might ask. Install might take a few, but it will complete if you let it. Once it completes, it will tell you to reboot. Do it. And when you come back to Bliss, it will have some nice sound controls
View attachment 4023486
Enjoy!!
Setting Taskbar v3.3+ as default navbar in Bliss-x86 n7.1.x
!!WARNING!! This must be done after first boot and setup is complete. Setup wizard uses default navbar.
Follow this link to read the walkthrough: https://forum.xda-developers.com/showpost.php?p=71757350&postcount=290
https://drive.google.com/open?id=0B2hjuvxuncgYQ3Z2dUE1YUo3TX not found
Can I use D:\android-x86 ?
Dunard said:
https://drive.google.com/open?id=0B2hjuvxuncgYQ3Z2dUE1YUo3TX not found
Can I use D:\android-x86 ?
Click to expand...
Click to collapse
My bad... I will move that to my AFH as well. And yes, you can use whatever folder/drive combo you want. Just make sure you edit the grub.cfg to match the location, or keep the folder name the same as I describe, and change the drive. It will search the mounted drives for the first folder matching that name
EDIT: Updated the link
@social-design-concepts would this work on baytrail android tablets?
Wow looks great. Thanks for all the hard work. @electrikjesus et al.
---------- Post added at 06:48 AM ---------- Previous post was at 06:15 AM ----------
Madlad003 said:
would this work on baytrail android tablets?
Click to expand...
Click to collapse
There's only one way to find out. My guess is you'll have a few minor incompatibilities.
Thank you very much @electrikjesus . All working fine. Amazing rom.
UPDATE
I have pushed an update to the Android-x86 UEFI installer, it should work for root now with one simple trick. I updated the second post accordingly as well. Thanks peeps for all the support on this project so far
Second Update:
There is now also a 32bit n7.1.1 build in the download folder. Only known difference so far is root is not working right. I'll fix that here soon.
UPDATES:
Bliss-x86 32bit - I have fix the issue with how supersu is integrated on the 32bit builds, so a new build can be found in the Bliss-x86 n7.1.x folder
I also had a couple people asking questions about how to use Taskbar and Substratum. So I went and made a couple short videos on that too.
Taskbar:
Substratum:
UPDATE - 01.11.17 - OS is now in line with 7.1.1r12, all the Surface patches have been correctly applied. So support for all M$ Surface product up to Surface Book should be there. 32-bit version didn't have any touch issues on my end. 64-bit still did eventually though. Could be my hardware I'm testing with though too. (I'll eventually be able to afford something new)
Builds are available in the Bliss-x86 n7.1x folder for my AFH. ENJOY!!
Xposed instructions are a bit wrong - despite the screenshots from groups
As you are replacing critical system files, you need to run the script in debug mode: DEBUG=1 rather than from a running system.
Feel free to verify but pretty sure on that.
Getting reboots as soon as android text on black screen appears, checked debug option and it got stuck at this point
It happens after I update apps or install new apps
HypoTurtle said:
Xposed instructions are a bit wrong - despite the screenshots from groups
As you are replacing critical system files, you need to run the script in debug mode: DEBUG=1 rather than from a running system.
Feel free to verify but pretty sure on that.
Click to expand...
Click to collapse
I use the local terminal accessed from Dev Options. My instructions work fine from there once I request su
muzab a said:
Getting reboots as soon as android text on black screen appears, checked debug option and it got stuck at this point
Click to expand...
Click to collapse
How odd. It says it can't access the local time... Never seen that before. Try to change persist.rtc_local_time in build.prop to persist.rtc_local_time = 0
electrikjesus said:
I use the local terminal accessed from Dev Options. My instructions work fine from there once I request su
Click to expand...
Click to collapse
You sure? Xposed installed and running correctly. There are some system libs and bins that I'm pretty sure can't be replaced while in use.
HypoTurtle said:
You sure? Xposed installed and running correctly. There are some system libs and bins that I'm pretty sure can't be replaced while in use.
Click to expand...
Click to collapse
I've done it my way since I put them up there. Just make sure you're superuser and reboot afterwards. If it gives you trouble, then do it your way. If they both work, I'll add your method to the instructions as well.
If I had to guess, it is because of how we reworked how SuperSU is built into Bliss-x86. Android-x86 Project uses a variation of CM's AppOps/Privacy Manager, and that was tied to the root terminal like you describe, as well as the filesystem, buildtype, etc. You likely had to access it using DEBUG=1 grub boot option. With Bliss-x86 (and remixOS I think) just using the root terminal with proper su access should do the trick.
@HypoTurtleI installed xposed as @electrikjesus mentioned. All fine, no problem to install. After reboot I could install youtube adaway. I tried it in Remix os for pc as well. It worked.
Phoenix OS alongside with windows 10 & ubuntu. Total 3 OS=Windows + Ubuntu + Phoenix?
I need to install phoenix OS 7.1.1 in my pc.
It already has Windows 10 and Linux Ubuntu 17.04 in it.
Thru grub loader I'm able to choose whether Windows 10 or Ubuntu.
Now I need to install Phoenix OS too along with these two OSs. I tried installing it thru "PhoenixOSInstaller-v2.0.0-Alpha-60.exe" on my hard disk partition (tried NTFS & FAT32). But after installation, there is no boot entry for phoenix os in the GRUB menu.
I tried EasyBCD to add entry for this OS, but same ended in vein.
Note: When installed the same on my pen drive, it is working fine.
Requirement: Either I need to use my installed Phoenix OS by adding a boot entry or other possible to way to install & use.
Thanks
rajan1052 said:
I need to install phoenix OS 7.1.1 in my pc.
It already has Windows 10 and Linux Ubuntu 17.04 in it.
Thru grub loader I'm able to choose whether Windows 10 or Ubuntu.
Now I need to install Phoenix OS too along with these two OSs. I tried installing it thru "PhoenixOSInstaller-v2.0.0-Alpha-60.exe" on my hard disk partition (tried NTFS & FAT32). But after installation, there is no boot entry for phoenix os in the GRUB menu.
I tried EasyBCD to add entry for this OS, but same ended in vein.
Note: When installed the same on my pen drive, it is working fine.
Requirement: Either I need to use my installed Phoenix OS by adding a boot entry or other possible to way to install & use.
Thanks
Click to expand...
Click to collapse
In Ubuntu, google how to install grub customizer. Once installed, you can add Phoenix to grubs boot options. I have Windows 10, Ubuntu 17.04, Phoenix OS and Remix all booting correctly from grub. Give me just a bit and once I'm to my laptop where the files are, I'll post the boot parameters for phoenix that you need to put in Grub customizer.
EDIT:Here is a screenshot of how to set it up, and I'll give a brief tutorial on using Grub Customizer to add Phoenix.
First in grub customizer, is to add entry. A window will pop up. Here is a screenshot of how it should look and be filled out. Part of the boot sequence is out of screen, so I'll paste the whole thing here.
search --set=root --file /efi/PhoenixOS/kernel
linux /efi/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS vga=788
initrd /efi/PhoenixOS/initrd.img
Click ok on that window. Next, hit the save button. Once is saves successfuly, hit File in upper left, and click write to mbr. Confirm and let it write. Once done, you should be able to reboot and find Phoenix OS in your grub. Should boot fine. Good Luck!
@rebel1699 hi brother i am configuring my laptop to different operating systems
i want to have 5 operating systems install on my laptop i have searched and looked for it all over the internet but couldn't find the exact method..
the os i need are
windows, following by ubuntu then phoenix and remix then mac os (which is optional)
tell me what order i have to follow and how to install all of them..
i want phoenix and remix to be installed on a separate partition not within ubuntu.. i have already install windows and ubuntu both are working great now when i install phoenix from the installer exe (via windows) it creates a boot file for windows and phoenix i just need the phoenix not windows because i will be booting all the os through grub even when i configure or add phoenix in grub (came with ubuntu) the phoenix os does show up in grub and boots as well but when i select phoenix os it opens another grub menu with windows and phoenix options i just want phoenix os to boot when i select it from main grub (ubuntu one)
please guide i have to ready it for monday
rebel1699 said:
In Ubuntu, google how to install grub customizer. Once installed, you can add Phoenix to grubs boot options. I have Windows 10, Ubuntu 17.04, Phoenix OS and Remix all booting correctly from grub. Give me just a bit and once I'm to my laptop where the files are, I'll post the boot parameters for phoenix that you need to put in Grub customizer.
EDIT:Here is a screenshot of how to set it up, and I'll give a brief tutorial on using Grub Customizer to add Phoenix.
First in grub customizer, is to add entry. A window will pop up. Here is a screenshot of how it should look and be filled out. Part of the boot sequence is out of screen, so I'll paste the whole thing here.
search --set=root --file /efi/PhoenixOS/kernel
linux /efi/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS vga=788
initrd /efi/PhoenixOS/initrd.img
Click ok on that window. Next, hit the save button. Once is saves successfuly, hit File in upper left, and click write to mbr. Confirm and let it write. Once done, you should be able to reboot and find Phoenix OS in your grub. Should boot fine. Good Luck!
Click to expand...
Click to collapse
Hello .
I installed Phoenix os 2.2 Android 7. 1 on Teclast x98 air 3G and on Pipo X7 here is a small video of display Phoenix os on Pipo and very fluid internet connection by WIFI works very well.
https://youtu.be/fYpLOBjnYxM
You can try this script i made 50_PhoenixOS
thanks
rebel1699 said:
in ubuntu, google how to install grub customizer. Once installed, you can add phoenix to grubs boot options. I have windows 10, ubuntu 17.04, phoenix os and remix all booting correctly from grub. Give me just a bit and once i'm to my laptop where the files are, i'll post the boot parameters for phoenix that you need to put in grub customizer.
Edit:here is a screenshot of how to set it up, and i'll give a brief tutorial on using grub customizer to add phoenix.
First in grub customizer, is to add entry. A window will pop up. Here is a screenshot of how it should look and be filled out. Part of the boot sequence is out of screen, so i'll paste the whole thing here.
Search --set=root --file /efi/phoenixos/kernel
linux /efi/phoenixos/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 remount_rw=1 src=/phoenixos vga=788
initrd /efi/phoenixos/initrd.img
click ok on that window. Next, hit the save button. Once is saves successfuly, hit file in upper left, and click write to mbr. Confirm and let it write. Once done, you should be able to reboot and find phoenix os in your grub. Should boot fine. Good luck!
Click to expand...
Click to collapse
worked for me bro!!!! <3
How 2 increase fsb speed or base clock of i3 arrandale in phoenix os ??
install POS with exe from Windows then boot to UBUNTU ,Now cd to /etc/grub.d and add this code to your 40_custom (manke one if not available) then grub update (-rwxr-xr-x 1 root root 1.2K Dec 21 16:15 40_custom)
Code:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### BEGIN /etc/grub.d/20_linux_xen ###
menuentry 'Phoenix OS--no ext display' --class android-x86 {
insmod part_gpt
insmod fat
search --file --set=root /EFI/PhoenixOS/kernel
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
initrd /EFI/PhoenixOS/initrd.img
}
menuentry 'Phoenix OS--ext display' --class android-x86 {
insmod part_gpt
insmod fat
search --file --set=root /EFI/PhoenixOS/kernel
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788 video=1920x1080 video=eDP-1:d
initrd /EFI/PhoenixOS/initrd.img
}
menuentry 'test Pheonix' --class android_x86{
load_video
insmod part_gpt
insmod fat
search --file --set=root /EFI/PhoenixOS/kernel
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
initrd /EFI/PhoenixOS/initrd.img
}
### END /etc/grub.d/20_linux_xen ###
Triple Booting in BIOS
rebel1699 said:
In Ubuntu, google how to install grub customizer. Once installed, you can add Phoenix to grubs boot options. I have Windows 10, Ubuntu 17.04, Phoenix OS and Remix all booting correctly from grub. Give me just a bit and once I'm to my laptop where the files are, I'll post the boot parameters for phoenix that you need to put in Grub customizer.
EDIT:Here is a screenshot of how to set it up, and I'll give a brief tutorial on using Grub Customizer to add Phoenix.
First in grub customizer, is to add entry. A window will pop up. Here is a screenshot of how it should look and be filled out. Part of the boot sequence is out of screen, so I'll paste the whole thing here.
search --set=root --file /efi/PhoenixOS/kernel
linux /efi/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS vga=788
initrd /efi/PhoenixOS/initrd.img
Click ok on that window. Next, hit the save button. Once is saves successfuly, hit File in upper left, and click write to mbr. Confirm and let it write. Once done, you should be able to reboot and find Phoenix OS in your grub. Should boot fine. Good Luck!
Click to expand...
Click to collapse
Hi, Brother @rebel1699, I copied your boot sequence and pasted in the Grub Customizer, but it didn't work
I'm a Newbie, but I think this boot sequence is for UEFI-GPT and that's why it didn't work
I'm trying to triple boot (Windows7,Ubuntu,PhoenixOS) in BIOS-MBR
What should be the boot sequence for Phoneix OS in BIOS-MBR?
Help me out,Please
NOTE: I'm doing a fresh install of all three operating systems, so I don't need any data on my HDD
Thank You!
Option
jibrail1212 said:
Hi, Brother @rebel1699, I copied your boot sequence and pasted in the Grub Customizer, but it didn't work
I'm a Newbie, but I think this boot sequence is for UEFI-GPT and that's why it didn't work
I'm trying to triple boot (Windows7,Ubuntu,PhoenixOS) in BIOS-MBR
What should be the boot sequence for Phoneix OS in BIOS-MBR?
Help me out,Please
NOTE: I'm doing a fresh install of all three operating systems, so I don't need any data on my HDD
Thank You!
Click to expand...
Click to collapse
Hi. I had the same problem, but maybe this will help you...
Install Phoenix OS on an ext4 partition. (Or any other fs type partition.)
Use a Linux distro to do this. I used Ubuntu. It can be installed on an MBR and on a UEFI computer. I installed it on a UEFI laptop first, later on an MBR laptop.
1) Download Phoenix OS iso for PC from http://www.phoenixos.com/en/download_x86
2) Unarchive it.
3) Unsquashfs the system.sfs file. Look in the resulting squashfs_root folder to find the system.img file there.
4) Use a free ext4 partition or create one. (Any size.)
5) Create a folder phoenix in that partition. (/dev/sdaX/phoenix, where X is the number of the partition.)
6) Move files initrd.img, kernel, ramdisk.img and system.img to the phoenix folder.
7) Create a folder data in that phoenix folder. (dev/sdaX/phoenix/data)
8) In terminal,
Code:
sudo nano /etc/grub.d/40_custom
add,
Code:
menuentry 'Phoenix OS' --class android-x86 {
insmod part_gpt
set root='hd0,gptX'
search --file --no-floppy --set=root /phoenix/system.img
linux /phoenix/kernel root=/dev/ram0 androidboot.hardware=Android_x86 androidboot.selinux=permissive CMDLINE
initrd /phoenix/initrd.img
}
Here X is the number of your partition. If your partition system is older, change
Code:
insmod part_gpt
set root='hd0,gptX'
to
insmod part_msdos
set root='hd0,msdosX'
Code:
sudo update-grub
9) Reboot and boot into Phoenix OS. Wait for while until it'd fill the /dev/sdaX/data
Enjoy!
Updated to v3.0.2.64
POS got updated to v3.0.2.64 today.
I'd like to get this running on the Nintendo Switch.
Would you be able to assist in any way?
Leonidas87 said:
I'd like to get this running on the Nintendo Switch.
Would you be able to assist in any way?
Click to expand...
Click to collapse
I've never used any of these game consoles, so don't know how. If you know a way to create a partition and put in there those 4 files, and create a data folder and then call it to boot, maybe you can get it going.
Hello!
Perhaps this is not the appropriate topic where I could trouble you with a quick question, but since I'm already here, I was wondering if you could perhaps offer me a better insight about what my problem could be. I've searched left and right for an answer to this but I've yet to find one.
So I've been trying to install Phoenix OS alongside Ubuntu, however the system won't boot at all with this current version, it freezes at "Detecting Phoenix OS... found at (etc)" and nothing. The only one that seems to be working is v 2.0.2 but it's really unresponsive towards installing .apk files and buggy sort of speak.
I've also tried USB installation and yet again the same concept; I'm beginning to think it's because of my laptop perhaps?
It's a relatively old machine, but here are the specs:
System Model: X553MA
Processor: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz (2 CPUs), ~2.2GHz
Memory: 4096MB RAM
Display: Intel(R) HD GRAPHICS
Thank you in advance!
why i always get emergency remount r/o when phoenix is booting up, and then it crashed and just restart all the time
firmantr3 said:
why i always get emergency remount r/o when phoenix is booting up, and then it crashed and just restart all the time
Click to expand...
Click to collapse
If you've installed POS the same way as I had, you won't get any crashes. I am writing from an MBR laptop from 2011 with Win7/Debian/Deepin/POS multi-boot.
ostrolk said:
Install Phoenix OS on an ext4 partition. (Or any other fs type partition.)
Use a Linux distro to do this. I used Ubuntu. It can be installed on an MBR and on a UEFI computer. I installed it on a UEFI laptop first, later on an MBR laptop.
1) Download Phoenix OS iso for PC from http://www.phoenixos.com/en/download_x86
2) Unarchive it.
3) Unsquashfs the system.sfs file. Look in the resulting squashfs_root folder to find the system.img file there.
4) Use a free ext4 partition or create one. (Any size.)
5) Create a folder phoenix in that partition. (/dev/sdaX/phoenix, where X is the number of the partition.)
6) Move files initrd.img, kernel, ramdisk.img and system.img to the phoenix folder.
7) Create a folder data in that phoenix folder. (dev/sdaX/phoenix/data)
8) In terminal,
Code:
sudo nano /etc/grub.d/40_custom
add,
Code:
menuentry 'Phoenix OS' --class android-x86 {
insmod part_gpt
set root='hd0,gptX'
search --file --no-floppy --set=root /phoenix/system.img
linux /phoenix/kernel root=/dev/ram0 androidboot.hardware=Android_x86 androidboot.selinux=permissive CMDLINE
initrd /phoenix/initrd.img
}
Here X is the number of your partition. If your partition system is older, change
Code:
insmod part_gpt
set root='hd0,gptX'
to
insmod part_msdos
set root='hd0,msdosX'
Code:
sudo update-grub
9) Reboot and boot into Phoenix OS. Wait for while until it'd fill the /dev/sdaX/data
Enjoy!
Click to expand...
Click to collapse
Pls help. I dont know how to unsquash?
install to decompresses partition
I installed Phoenix OS parallel to Win7 in an own (NTFS) partition with theses *.img files for each Phoenix partition.
Q: is it possible to install to real ext4 partitions instead using compressed img partition?
Need Help
My GPU is damaged and keep shutting down by itself when I play games and the only way fix this is to limit my gpu speed clock to 555mhz from 725mhz..
I know how to do it on Windows, but not on Phoenix os-ROC
My GPU is ATI radeon 6730m.
The only way I know my current speed is in terminal, accessing radeon_pm_info.
Power level at 2, speed 725mhz and memory speed 900mhz at load.
No overheat issue.
Please help
Terminal problem
Sudo nano/etc/grub/40_custom: command not found.
I don't understand why it is happening. Can you assist? Please.
the file is located in /etc/grub.d/40_custom, not in /etc/grub/40_custom
Hello, just a quick question before i try it out. There is a tutorial over internet which dual boots phoenix from ubuntu root partition without the need to make a separate partition. The grub code provided is as follows:
insmod part_gpt
search --file --no-floppy --set=root /phoenix/system.sfs
linux /phoenix/kernel root=/dev/ram0 androidboot.hardware=android_x86 SRC=phoenix/
initrd /phoenix/initrd.img
this method doesnt unsquash the sfs file, and hence after booting to phoenix you cant change filesystem files as they are protected.
Question: can I use a system.img using this method? I find this easy and non destructive to my existing harddisk partition scheme. my guess is, all i have to do is change the code from system.sfs to system.img. Is there anything else i need to take care of?
Hey can you telle that where to find the terminal?