yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] MASTERXS:
it worked the first time then i deleted the unnamed-missed entries in easyuefi

now it doesnt work anymore how do i get it to work again heres the log

===============Installer Info================

Installer Directory:C:\Users\Van\Downloads\Androidx86-Installv25.0004

Installer Version:2.4.5800.0

Secure Boot ... Disabled

Manufacturer: HP

Model: HP 250 G5 Notebook PC

Product: 81F1

BIOS info:

HPQOEM - 3

F.09

INSYDE Corp. - F090000

Available GPU(s):

GPU: Intel(R) HD Graphics

=============[REQUIREMENTS CHECK]============

Administrator privilege ... ok

CPU Architecture: 9

CPU Name: Intel(R) Celeron(R) CPU N3060 @ 1.60GHz

OSVer: Microsoft Windows NT 10.0.14393.0

OperatingSystem Version ... ok

Windows Security: Access NVRAM Privilege ... Not All Set

System Firmware: UEFI

==========================================

====Install Started on 7/06/2017 6:13:56 PM====

-ISO File: C:\Users\Van\Downloads\Androidx86-Installv25.0004\Bliss-v7.1-android_x86_64-OFFICIAL-20170402-1108_k4.4_01.iso

-TargetDrive: C

-UserData: 71345111

-Setup Directories...

-Folder Created: C:\AndroidOS

-Extract ISO

#Launch:C:\Users\Van\Downloads\Androidx86-Installv25.0004\7z.exe x "C:\Users\Van\Downloads\Androidx86-Installv25.0004\Bliss-v7.1-android_x86_64-OFFICIAL-20170402-1108_k4.4_01.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS

-Extract SFS

#Launch:C:\Users\Van\Downloads\Androidx86-Installv25.0004\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS

#Launch:C:\Users\Van\Downloads\Androidx86-Installv25.0004\7z.exe e "C:\Users\Van\Downloads\Androidx86-Installv25.0004\Bliss-v7.1-android_x86_64-OFFICIAL-20170402-1108_k4.4_01.iso" "boot\grub\grub.cfg" -oC:\AndroidOS

-Create Data.img

#Launch:C:\Users\Van\Downloads\Androidx86-Installv25.0004\dd.exeif=/dev/zero of=C:\AndroidOS\data.img count=71345111

-Initialize Data.img

#Launch:C:\Users\Van\Downloads\Androidx86-Installv25.0004\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"

===Installing Boot Objects===

-Mounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /S

-Setup Boot Directory...

-Boot Folder Created: Z:\EFI\boot\

-Copy Boot files

-Add UEFI Entry

UEFI Init Fail

==============Revert Installation==============

-Cleaning up Android Directory ... C:\AndroidOS

===Removing Boot Objects===

-Mounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /S

Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S

Error output:

The directory is not empty.

-UEFI Init ... fail

-Cleaning up Android Directory ... Z:\EFI\boot\

-UnMounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /D
[BLISS ROMS Development] franzli:
Oh indeed, I had forgotten that there was a new easy method for non-uefi devices. Sorry for the confusion, don't know about that one since I've always been using uefi setups.

---------- Post added at 12:13 PM ---------- Previous post was at 12:01 PM ----------

Hm, not an expert, but from the output there seems to be a problem with accessing your nvram, which is responsible for the efi entries. This prevents the installer from setting up a new entry for Bliss.

I had some problem of that sort with a Linux install a year ago or so, unfortunately I don't remember how I got rid of it (retired Linux tools anyway). There should be a way to reset the nvram in windows as well, I suspect, maybe someone else knows more here?

I'd suggest also trying to install from the boot menu to see if that solves the issue (for me that always have better working installations in general). It might not, of there's really a problem with writing to your nvram, but this might be a way to verify if that's the case. Disadvantage might be that updating to a newer version might be trickier of you install to an ext4 partition and don't have an os that allowed you accessing that partition later on (of you have Linux, all is fine). I don't remember if you can choose to format to ntfs as well, if so, you should be able to update from windows as well by just replacing the files as describes in post 2.
[BLISS ROMS Development] MASTERXS:
thanks

so u ur saying that i should try install from boot menu how do i do that is it that boot menu when u choose which os to run
[BLISS ROMS Development] franzli:
You write the image file to a USB stick (on Linux etcher is good, on windows you could user Rufus) and boot from there. You are then presented with a boot menu and I think the third option is to install (it's described in the second post of this thread in more detail), although it makes sense to first try out booting into the system if you haven't already.
[BLISS ROMS Development] Ichijou Raku:
I've successfully installing Bleeding Edge build using quick mbr method.. everything running perfectly but i encounter 2 problem

1.The screen look weird,i mean screen is less sharp..

2.its so laggy,i dont know what wrong..

Btw this my laptop spec..

-HP 14-af118au

-Quadcore Amd Apu 8 with Radeon R5 2.2ghz

-8gb Ram (7gb usable)

-Amd Radeon R5 1gb graphic..

-Windows 10 Creator Update

? Please any help??
[BLISS ROMS Development] Rawwrius01:
Works on surftab Duo w1 ?? Remixos Phönixos and x86 wont Work

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[BLISS ROMS Development] ElfinJNoty:
The best way to find your answer would be to follow the instructions to install via a USB. If your device will run from a live boot, then should be installable.

There are far too many devices capable of running Bliss-x86 that we have not created a list yet. But we are thinking about a way to keep track.
[BLISS ROMS Development] electrikjesus:
For the GPT/MBR boot setups, once I find the grub config that works, I'll load up StickMount and edit my grub.cfg directly from Bliss-x86. Easiest method IMO ;)
[BLISS ROMS Development] electrikjesus:
This sounds like lack of support for either graphics hardware or CPU hardware... My AMD Brazos machine also suffers from a sluggish experience, but it's still better than it used to be ;)

Let me know what bleeding edge build you tried too, cause a different one with a different kernel might yield better results.
[BLISS ROMS Development] Ichijou Raku:
Thanks for your reply.. ? im using latest edge build..hmm ok i'll try another build,hope much better than last ? goodwork..
[BLISS ROMS Development] MASTERXS:
fixed

i used PizzaG Windows 10 EFI Partition Helper but im still having problems sometimes it works then sometimes it does
[BLISS ROMS Development] electrikjesus:
Got a link to that so I can check it out?
[BLISS ROMS Development] MASTERXS:
uefi problems

https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk

heres the link have a look bliss is only worked 3times for me and i keep on getting that problem where it goes directory not empty

---------- Post added at 03:22 AM ---------- Previous post was at 03:16 AM ----------

"i used PizzaG Windows 10 EFI Partition Helper but im still having problems sometimes it works then sometimes it does"

wat i meant to say that sometimes it works then sometimes it doesnt
[BLISS ROMS Development] ElfinJNoty:
I believe he is referring to this op:

https://xdaforums.com/remix/remix-os/custom-remixos-grub-theme-grub-cfg-tips-t3549928
[BLISS ROMS Development] YIMSHING:
I follow your xposed‘s installation steps，but i can't install xposed successfully.

It indicates that /system and /vendor can't be writed

I can't upload the picture in this place. u can see my albums,i upload the picture in there.

it is always read-only.

I downloaded ReExplorer for changing the 'read-only' . but it doesn't work .

So I can't install xposed so far.

Can u teach me how to install the xposed?
[BLISS ROMS Development] FriendlyNeighborhoodShane:
you have to extract system.img from the system.sfs and delete the system.sfs.
[BLISS ROMS Development] JrLD:
I will try this
[BLISS ROMS Development] jrk190:
Anyone had any luck with baytrail tablets?
[BLISS ROMS Development] ElfinJNoty:
You also cannot be trying to install Xposed on a nougat 7.1 build
[BLISS ROMS Development] harkaman:
Is it possible for you(anyone) to make small video clip to show us how to do manually(Custom Install For Bliss-x86 6.4/7.x UEFI/ESP (32bit or 64bit))? Thanks in advance.
[BLISS ROMS Development] ElfinJNoty:
Have you tried to use the uefi windows installer? Is the easiest method and I believe the safest.

But perhaps you have some specific reason for a manual installation?
[BLISS ROMS Development] harkaman:
I tried many time uefi installer, but no success. It used to work, but not any more, at least for me. I did try many time manually installing way, but no success. Maybe I am missing something?

upload images
[BLISS ROMS Development] ElfinJNoty:
In the Windows Installer, are you selecting "clean Android" prior to attempting to install the latest .iso from downloads?

It would appear that you have no grub 2 menu entries as option to boot to Windows or boot to Bliss.

I have used the Windows install tool just a few days ago after someone here in the thread mentioned it "wasn't working".... But the installation went fine for me. No issue at all on my end anytime I use the WinTool. [MENTION=928479]electrikjesus[/MENTION] has reported the same successful testing attempts recently. The grub menu you are showing in your photos does not resemble mine after a successful install. Is the installer reporting no errors? Is it pop up and say "install complete" and then a second pop up that says "do report any errors..." That would indicated a successful install upon completion. Any other errors would abort the install, create a log in the root of your C: drive(or other install directory)

If you are able to boot to Windows still, look for a log file at C:\ with the recent time modified for the file. (I cannot remember the name of the file off the top of my head, but it will be there). In the log file will show where, if any, your device is ha going during install.

Also may need to mount your efi partition and verify that your grub.cfg file is present and has the correct menu entries
[BLISS ROMS Development] franzli:
Looks a but like grub, or more likely grub.cfg, is not copied into the correct location on the EFI partition? I fiddled with that at one point, I think I had one grub.cfg in /efi/boot and another one in the corresponding subfolder for android. Unfortunately, I don't remember right now which one was the right one, but you might just try out. The screen you get suggests that grub cannot find a config in any case.

So essentially you need to mount your EFI partition (on windows that involves some command in an admin shell and then using a file explorer with admin rights) and have a look around there and possibly copy grub.cfg to the position it's missing (or if you have it in both positions, you might have a look at the contents and compare).
[BLISS ROMS Development] electrikjesus:
I worked with Harkaman over the last few days to try to work through his issue and we finally were able to get Bliss to boot, but we had to use the remix OS installer and then replace remix OS with Bliss-x86. It seems that the version of UEFI we are using is not compatible with all UEFI machines
[BLISS ROMS Development] ElfinJNoty:
Interesting find!

I recall using that installation method the first time I ran an android-x86 MM build.

Glad you guys figured it out.

Are we able to integrate a different Uefi for better compatibility or is this a rare case scenario?
[BLISS ROMS Development] electrikjesus:
Kinda thinking we play this out to see how often it happens and on what machines. This is where we need to start mapping out our compatibility
[BLISS ROMS Development] harkaman:
I did my best.
[BLISS ROMS Development] franzli:
Just an idea, maybe try out if it helps of you copy grub.cfg from EFI/boot/grub into the higher folder where you've only got the bootx64.efi, i.e. into EFI/boot.

Also have a look at what is in grub.cfg just to make sure.
[BLISS ROMS Development] wizmart:
Finally, I got WiFi running on the latest bleeding edge, but I noticed some multitask limits with video on one window and another app on second window: the video(twitch, youtube) stop running as soon as you go on the other app...
[BLISS ROMS Development] mattbaker:
Asus T102HA Blackscreen on boot

Hello gentlemen,

after hassling with installing some version, any version of android x86 on my Asus T102HA, for an entire day, I finally stumbled upon your great and easy to use windows application and finally managed to install your stable 7.1 64bit android x86 onto the device. In the booting process, I can select the Android OS in the UEFI menu, then select Android x86 in the GRUB loader and then... well nothing unfortunately, the screen stays black, left it there for 30 minutes now with no change...

Where have I gone wrong? Maybe this is a known issue? I must admit, my eyes are getting tired and I've only taken the time to scroll through a few of this topics pages, haven't found anything on black screens yet.
[BLISS ROMS Development] electrikjesus:
Try adding nomodeset to the grub command right before "quiet". This is a known issue on the newer 4.12x kernels
[BLISS ROMS Development] kanttii:
Hey guys! I found a way to use an external display with this, by disabling the internal display and telling it to use the external one only!

Install Bliss-x86

Boot Ubuntu USB stick or any linux that can run the "xrandr" command

Do "xrandr" in terminal to find out what display interface name your internal display has. For example mine is eDP-1 (Surface Pro 3 screen). It's the part before (example) "NAME connected primary 2160x1440".

In another terminal window, do "sudo nano /etc/grub.d/40_custom" and find the Bliss-x86 boot entry

Add the following command for example to the end of the linux row (connection = the name of your connection/display interface name, :d disables that display):

video=connection:d video=

Example: "video=eDP-1:d video="

If you're unsure what your laptop/tablet display ID is, you can try with this (not tested):

video=eDP-1:d video=eDP1:d video=LVDS1:d video=LVDS-1:d video=

Press CTRL-X to save changes, then do this command:

sudo update-grub

Reboot to Bliss-x86 and enjoy... If the elements are too big for your taste, go to Settings and change the display density from there, or go to developer options and tune the .

If you want, you can also add your external monitor's resolution to the second video= command, for example video=3440x1440 but it shouldn't be needed as it worked very well for me without any set resolution. Android and Linux are intelligent in that way.

I also tried whether it'd work if I defined both the internal resolution and external resolution, but it mirrored the image as it normally does without the above hack to disable the internal display. I haven't yet found a way to use both the internal and external displays on Android. This is great if you want to connect your Bliss-x86/Android-x86 laptop/tablet to your TV or bigger monitor and use only that, with the laptop/tablet acting as a "desktop" PC. Games, movies, web browsing, YouTube, anything... And with the freeform windows and taskbar on Bliss-x86, you have a new open-source Android PC experience on the bigger screen!
[BLISS ROMS Development] electrikjesus:
UPDATE - 06/15/2017 - BLEEDING EDGE

Hello again, I have uploaded a couple new bleeding_edge builds to our team downloads server. These are using kernel-4.12rc5, and on some of my tests, I have had to add "nomodeset" to my grub command (or use the nomodeset boot entry from the Custome UEFI bootloader), but this is only on a couple test machines so far, not all.

Updates include:

New updates to Taskbar & TSL, allowing us to use [MENTION=4289533]farmerbb[/MENTION] 's Taskbar as the Navbar automatically once SetupWizard is complete

Updated kernel-4.12rc5 & firmware

Bluetooth now works for many machines. (most machines work using kernel-4.9, some might work with kernel-4.12x. Please report back)

Added fixes for wifi and wifi reconnect

and as usual, there's likely more, but I forgot...

Known Bugs:

- Changelog from AboutBliss STILL not working ( I am still working on it)

- reverse or 90° orientation on some touchscreens

- Some wifi reconnect issues still

Enjoy!!

https://downloads.blissroms.com/Bliss/Official/x86/
[BLISS ROMS Development] mattbaker:
Hi,

thanks for the quick reply. So I tried that, it did indeed work and got the mesmerizing Team Bliss animation to start, but its been going for about a half hour now, with nothing really happening except the black ribbon going round and round in a looping 8. Does that mean my thing isnt compatible? Or does it neet some more tweeking?

Edit: and at minute 31, the set up screen came alive :D :D I'll report back once I have it set up.
[BLISS ROMS Development] electrikjesus:
UPDATE #2!! - 06/15/2017 - STABLE BRANCH

Ok, I know this might seem crazy to see all these updates all in one day. But this is good news because with this update, Bluetooth is working, Wi-Fi is working, as well as many many many other issues that were in the previous builds. Only difference between this build and today's previous bleeding edge build is the kernel. This one's using kernel-4.9, and in our tests, it provides a very smooth experience.

32bit and 64bit builds uploading now!!

Updates include:

New updates to Taskbar & TSL, allowing us to use [MENTION=4289533]farmerbb[/MENTION] 's Taskbar as the Navbar automatically once SetupWizard is complete

Updated kernel-4.9 & firmware

Bluetooth now works for many machines. (most machines work using kernel-4.9)

Added fixes for wifi and wifi reconnect

and as usual, there's likely more, but I forgot...

Known Bugs:

- Changelog from AboutBliss STILL not working ( I am still working on it)

- reverse or 90° orientation on some touchscreens

Enjoy!!

https://downloads.blissroms.com/Bliss/Official/x86/
[BLISS ROMS Development] mattbaker:
Ah well, there you go, I actually got the install working with the nomodeset command, but then the WIFI wasn't working and I was like damnit, what now :D Thanks for the great work!
[BLISS ROMS Development] electrikjesus:
Might want to try giving the kernel-4.9 build a try
[BLISS ROMS Development] mattbaker:
Yeah that's what I meant, just after my 7.1 install I saw you posted about the new 7.2 update, installed that and then it worked fine :)

I do have one isse though now, I'm doing all this actually just to run one single app, Jeppesen JeppTC, and that now tells me it won't run on rooted devices... I found a way to make it run (although the post is several years old, I hope this workaround might still work):

However, whenever I try to uninstall Superuser, it just comes right back on the next startup, so I'm guessing its tied into the Bliss package somehow?
[BLISS ROMS Development] scabs:
The latest bleeding edge is working the best! Everything is working except for BT and WiFi.
[BLISS ROMS Development] kanttii:
What install method did you use? If you have system.sfs or system.img file, you can try with the installer directions from 2nd post and choose system r/w yes when it asks, so that you can actually edit the system partition and remove the root-related stuff:

https://xdaforums.com/showpost.php?p=70462761&postcount=2

Alternatively, if you're already on an ext4 partition, you can manually extract the system.sfs file, then the system.img file to a system folder.. but a clean install with system r/w is the best way.
[BLISS ROMS Development] mattbaker:
Hey man,

I used the windows tool installation (easy method). However, in the end, I installed memu android emulator on the windows partition, ran xposed framework with rootcloak, and, after a stunning 20 hours of work invested and far too little sleep last night, I managed to get the stupid fking app to work. Also, after messing with 8 different android installs, 4 different install methods, roots and roms, I now proudly feel like a true hacker lol:D

Anyhow, I appreciate the quick support here, and also the work you guys are doing with the Bliss software, even if it wasn't for me in the end, I see the value and immense workload you have put into it! :good:
[BLISS ROMS Development] farmerbb:
For anyone that is still experiencing the reverse / 90° orientation bug, Android-x86 has shortcut keys for manually changing the screen orientation that might help:

Also, [MENTION=928479]electrikjesus[/MENTION], I noticed that the Setup Wizard crash is still present even on the latest stable build. Just FYI :)
[BLISS ROMS Development] electrikjesus:
This could be an issue with the data.img in some cases as well. I was able to go through setupwizard with no issues. This has been the bane of Bliss for a while now. Not able to figure out why, and the only thing that's helped was enabling wifi by default

EDIT: I guess I should spin that to also say that if your machine/install type doesn't have working wifi, SetupWizard might still FC on you.
[BLISS ROMS Development] youling257:
https://github.com/BlissRoms-x86/kernel_common/commits/k4.12rc5-jwd

Update SafetyNet bypass + proc: Remove verifiedbootstate flag from /proc/cmdline + rootless ，can bypass safetynet check ?

do you success ?
[BLISS ROMS Development] electrikjesus:
I haven't had a chance to fully test this yet
[BLISS ROMS Development] georgekav33:
4.12r5 works fine concerning the Wifi and bluetooth, however the screen is off-center and not aligned with the touch.

Any ideas?
[BLISS ROMS Development] karlnorth:
I have a 1st gen Surface Pro. I have the latest Bleeding Edge ROM installed. I have noticed a few issues.

One, how do I create a recovery partition during install so that I can install TWRP or CWM? Has anyone actually built TWRP for the 1st gen Surface Pro?

Two, SU seems flakey in this build. In Root Explorer, it shows as gaining root. I can mount the root of the FS as RW. If I go into System (or any other sub folder) I cannot mount it as RW. Maybe it is related to the fact that the su binary fails to update via the normal method.

Thinking I may have gottten a dirty flash, I formatted the partitions and reinstalled. No difference.

For an older Windoze tablet, the 1st gen Surface Pro seems to make a great Android device.

Please Help!

Karl N.
[BLISS ROMS Development] franzli:
My understanding is that a recovery doesn't actually make a lot of sense for an x86 system, since it's essentially just a very limited operating system allowing modification of the android partitions. Since there's no problem installing a full scale OS on x86, in fact usually Linux or windows will typically already be installed, anything you could do with a recovery, you should be able to do from that os. It may, of course, be a matter of convenience, since twrp relieves you of the need to figure out the actual commands for what you want to do (also, windows might admittedly not be ideal as a "recovery", I'm not sure if there's a simple way of working with ext4 partitions on win).

For your second question, how did you install? I think if you install using the windows program, you'll need to delete a file on the android partition afterwards (I think system.sfs, but double check on the second post). That's if you don't get root at all, if it's really just patchy, I don't kbit what might be happening.
[BLISS ROMS Development] karlnorth:
Hi,

Thanks for replying. Yes, I'm aware that at this point TWRP is a convenience. My interest is driven by the fact that in-place backups are dead simple and so many of our wonderful 3rd party modules are easily flashable via TWRP.

Would Flashify suffice to flash apps such as Magisk? Is there an in-OS backup app which createa backups capable of true "Bare Metal" recovery?

After my earlier post, I downloaded a different and newer Bliss bleeding edge x86 64 build from a different server I found by going to their wonderfully retro site. After completely deleting all partitions, and reinstalling with that ISO, life is much better. Root seems to be stable across the board.

Other than my stated issues, I'm currently a very happy dev.

-Karl North