Hello. I have installed BlissOS 10.1 nightly build on a Dell Venue 11 Pro 7139. The iso used was Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso. The installer completed succeffuly and I installed to my C: partition as an image partition, not as a separate partition. When I try to boot the OS, it starts as usual saying android found at sda sth, then after a very quick dump of echoes I don't know how to capture, the boot logo animation appears and stays there forever. After a number of attempts, I realized that the console is active and I can type commands like logcat. Unfortunately they only appear as they scroll because apparently the boot animation refreshes the screen, so I can't see the output and don't know if there is any command to stop the animation or redirect the output of the command to a log file that I can read through Windows. I had successfully installed BlissOS in the past in the same notebook, but had to resort to PhoenixOS, because touchscreen input didn't work. In PhoenixOS everything worked, but now I need Widevine DRM support and read that BlissOS currently supports it.
Any help would be appreciated.
slazaris said:
Hello. I have installed BlissOS 10.1 nightly build on a Dell Venue 11 Pro 7139. The iso used was Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso. …… Any help would be appreciated.
Click to expand...
Click to collapse
I have never installed BLISS; but, I had the same thing happened with Android X 86 install. I did a quick reinstall And when prompted to run Android or reboot I chose the reboot option. The operating system booted up just fine after that.
I met the similar probem on Qemu
It's very strange. It does work at the begining, and i used it for some days, but suddendly can not boot into the desktop, just stuck at the boot logo.
And i met this problem on three different PCs with Qemu.
BTW: I am using Bliss-v11.10--OFFICIAL-20191214-2253_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-undefined_gms.iso
i have same (lingeageos) on virtualbox
Related
Earlier this week, I posted a thread here asking for help with my hybrid android/windows tablet (Neo Shift N81) that wouldn't boot anymore into Windows. Nobody was able to help here and I ended up going back to the store where I got myself a windows recovery USB. After several attempts, it finally loaded the thumb drive. It reinstalled windows, but what the installation ended up doing was reformat the WHOLE disk on my tablet thereby effectively erasing the partition containing android as well. crying: FML)
So now I have the opposite problem. Windows boots and android doesn't. A little bit of googling led me to Android x86, which is able to run on Intel processors like the one on my tablet. I ended up downloading the 4.4 rc5 iso since it said that would compatible with my 32-bit EFI firmware. I created a 7gb partition by shrinking the main windows one and formatted it as ext4. I placed the iso onto a 2GB fat-32 USB using UNetbootin. I was able to boot it by going into the BIOS and force booting it. I tried testing it by running the live option, but it didn't boot although I suspect that may have also been because the thumb drive I used was ancient (from 2008). Then I installed it to the partition I created earlier. I initially tried to select "do not format", but when I got to the GRUB install windows it wouldn't proceed when I selected "yes" (it just started what looks like a command prompt, except no commands were accepted and would just continue creating multiple lines). Reboot and I selected it to format the partition into ext3. This time, it would proceed beyond "yes" and installed normally. Except it still didn't boot into Android. There was no grub menu or anything and the tablet just automatically boots into Windows 10. (I do have secure boot and fast boot disabled in BIOS) When I check the BIOS, it also doesn't have Grub as one of the options.
What I then tried was the instructions at this link where I select "skip" upon the grub install window during android installation. Grub2Win does show up upon the boot options, but even if I try to force boot that option, it doesn't do anything.
So what now? is there another bootloader I could try? Did I even install android correctly or did I select an .iso not compatible with my hardware?? (Prior to android being erased by the windows installation, the android on my tablet was 4.4) The info page mentioned that the "second" is an EFI image, does that mean I should download the .img file? Please help.
I followed instructions mostly from here.
I'm running slackware 14.1
it doesn't show up in adb -devices
nether dose it show up for fdisk -l or lsusb -vv
this was BEFORE it crashed
my only version of windoze is vista there no galaxy drivers for vistoole
It crashed and powered off now it just has a dim blank screen on boot
tried to installed other roms and back up copys it just powers down half way through
have left it over night thinking it just went in to screen saver but no
I can flash recovery roms and kernels but not working systems it just keeps powering down at what looks like the extraction of files (from reading the updater scripts)
one option might be to extract a ROM and convert it to an image
or install the rom by adb
better option would be to install linux natively
don't like droid at all it's screwed up linux
I tried to install android 7.1 86x firstly for BIOS(legacy) mode because i like to keep the second OS hidden then I can boot directly to Windows 8.1 on EFI, then I selected to install grub however my stock bootloader was still starting and nothing of grub and therefore I cannot boot into android. Then I decided to install for EFI because I was a whole day trying to work that out and couldn't find any answer on Internet, however seems like the stock bootloader starts instead of grub after I restart the pc.
Extra information:
My pc has an E1-2000 AMD processor, it is 64 bits (and yes, i downloaded the right iso file).
Windows boots from EFI, and I had Kali Linux previously installed with grub and worked fine.After I removed kali I also removed grub with "bootrec /fixmbr" and "/fixboot" on command prompt.
Windows is working fine.
Try downloading the easyUEFI tool (check google) and on windows set a partition for Grub + setting it as the default over MBR
LilAnt530 said:
Try downloading the easyUEFI tool (check google) and on windows set a partition for Grub + setting it as the default over MBR
Click to expand...
Click to collapse
What if I don't have windows there anymore? Is there a similar solution, inside a command line maybe?
I think I'm in a similar situation where I can install and run Androidx86 from my USB, but if I restart the laptop it won't find any boot option.
Hello everybody! I tried to install True Image on my Cenovo MiniPC but after the restart asked by the setup the dualboot (Androdi/Windows 10) is no longer working.
After a while I remembered that True Image add proprietary dual-boot for system recovery and probably this is the problem.
How can I restore the orginal dual boot screen?
I can boot Windows 10 from an USB Drive but the command "bootrec /fixMbr" gave me a "permission denied".
I read that someone solved with "Grub2Win" but Windows was still working, because that tool is not usable from a bootable USB drive.
Im not a newbie but I am not so good in GRUB and boot menu menu editing so please have mercy
Thanks for any help
The device I'm trying to do this on isn't your typical x86 device. The device mentioned in the description ships with a dual boot of android 5 and windows 10. Normally plugging in a USB stick with a flashed ISO into most other devices would make it boot into the flashed OS install options or a liveCD, but in this case, it still boots into the default boot meant to choose between windows and android, and yes trying to boot into either OS from there still boots it into the selected OS. I've tried with the micro USB, USB C, and the 2 ports on the keyboard that comes with package C or D, none of them make it boot into the Live CD. The image was flashed with Rufus if that helps any.