Upgrade to Ubuntu 19.04 on HP Elitebook 840 G1 results in blinking cursor after bootloader

I used to dual boot Windows (on dev/sda1) and Ubuntu 18.04, on my HP Elitebook 840 G1 (SSD). I also have a third partition for most of my files (I believe on dev/sda2 named D:/).

I tried upgrading to 18.10, which worked, after which I wanted to upgrade to 19.04. GRUB still finds the boot options I want, but when I try to boot into Ubuntu, I get a blinking cursor (after the ubuntu logo). Also going into “advanced options” in GRUB and selection 4.15.0-55-generic gives me the blinking cursor (after the ubuntu logo).

I wanted to know if anyone had managed to solve this? I have tried:

  • booting from a stick with Ubuntu 19.04 (most of the times it doesn’t even boot into the stick, and when it does, I also get a flashing underscores)
  • boot into recovery mode and change the GPU settings as proposed by heynnema (gdm3 display manager hangs after booting with Ubuntu 18.10)

The fact that even booting from stick gives an error maybe indicates that it indeed is a graphic error?

Deleted Ubuntu, Windows bootloader is difficult to access

I recently had a separate drive that I tried to install Ubuntu on. Some things happened, and as a result I had to uninstall Ubuntu. Now when I try to boot up my computer, I have to bring up the boot menu as the computer is booting up. From here, I am able to select the Windows boot loader and load up windows. If I don’t press f11 in time, the Ubuntu menu comes up and says its not found. When I go into the BIOS, I try to rearrange the boot order to what I think the correct loader is, it says “please select a proper boot medium” or something to that effect. Is there something I can do so I don’t have to be present to reboot my computer?

Thanks for any help -Dakota

No bootloader menu after a dual boot install

Today I added a second physical disk to my PC on which to install Ubuntu (other disk has Win 10).

I noticed during the installation that no other OS was found on my PC, but I ignored it and kept installing on the new hard drive.

On restarting, I don’t get a GRUB menu, it just boots straight to Ubuntu.

If I press F11 (my PC boot menu) and select the other hard drive, it boots into Win 10.

So I went into the BIOS and made my original HD the first choice for boot, and my PC boots into Windows on reboot.

Can someone help me figure out why the Ubuntu setup didn’t detect Windows during setup?

I installed the grub customizer tool, and that too cannot see Windows.

bootloader on RAID0

So I’m trying to install 18.04.3 from scratch, using a ‘fakeraid’ RAID0 (Legacy ROM) with 2x 32GB SSD’s. I’ve tried a burned DVD ISO and a USB (DD) image from Rufus – and everything works great until the bootloader section, which then generates a fatal error that it cannot install on /sda. Nothing works after that – have to reboot the machine. Been searching and have scoured literally a hundred webpages surrounding this persistent error, that has apparently never been adequately addressed since the early 2000’s. I read that Grub(2) cannot install on RAID0 at all – don’t know if that’s true or not. But just in case, I added another HDD, manually created a 1GB FAT32 partition named /boot and flagged it as both boot and esp. Yet I don’t get the option to select it upon bootloader failure – in fact, once the fatal error displays, it’s game over – can’t even continue or quit installation. Used gparted (and other utilities) to manually wipe existing partitions, and recreate them – still no joy – keep getting the fatal error once it finally hits the bootloader section. Even this page: bootloader location doesn’t offer a working solution – and really – should it come to that, anyway?

So I’m honestly asking the burning question: Why doesn’t this just work out of the box? Shouldn’t an install be intuitive enough to properly manage a bootloader install?

If I’m missing something obvious, please feel free to enlighten.

System Bootloader not found

I have preinstalled windows 10 in my HP Probook 450 G4. Then I installed Ubuntu with manual partition where it shows that EFI system partition is needed. So, I created it. My partition for ubuntu was like this:

/dev/sda7 swap 8191MB

/dev/sda8 efi 256MB

/dev/sda9 ext4 / 34503

But after the installation the system can not find the grub menu for dual boot…. it shows no system bootloader found and continues to restart. How can I get the grub menu now?

“Grub loading… Welcome to grub” banner appears before grub bootloader loads

I have a dual boot system with kali and ubuntu. One week ago I did a system update with apt upgrade but interrupted it because kali did not respond if I moved the mouse. Now, when I start my laptop, there is the banner Grub loading... Welcome to grub!. The banner was not there before the update. Actually I did not experienced problems or damages so far but it is really annoying for me. Can I remove it or is it possible that the banner is sign for a possible damage?

How to root an Android 7.1.1 device with a locked bootloader?

I am trying to root an Android 7.1.1 device (specifically a VR headset based on Android), and would be happy about any help/advices in this regard.
Some basic information about it:
– Android 7.1.1 with security patch level 2018-07-05, uses dm-verity and AVB, SDK version is 25
– Linux kernel 4.4.21, full sources are available here: https://github.com/facebookincubator/oculus-linux-kernel
– SnapDragon 835 processor, ARM64 system
– the bootloader is locked and can’t be unlocked by the regular commands such as “oem unlock”
– full list of system props is available here: https://pastebin.com/w32Zh9Lr
– there is an intercepted OTA update available here: https://anonymousfiles.io/mKd428fb/

Obviously rooting a 7.X Android device is a very challenging task these days if the bootloader is locked. So any advice how to approach it best or ideally which exploits for privilege escalation up to the root level could be used/tried best in this case. Many thanks!!!

Tripple-Boot Bootloader Rescue

I have a Dell XPS 15 9560 and I have been using Windows 10 and Ubuntu as a dual-boot system for quite a while. When I heard about the Qubes OS I decided to give it a try. I made some free space on my disk and tried to install it alongside the other two systems. The thing is, I had to switch from UEFI to legacy mode in order to install Qubes OS. I remember when I was creating partitions for Qubes OS, I didn’t make it use the existing /boot partition, I made a new /boot. After the installation, the original Ubuntu grub disappeared and there is only Qubes OS grub. I tried to add Windows menu entry to the new grub but that didn’t worssk, sos I used a Windows repair drive and did bootrec /fixmbr and bootrec /fixboot. After that, even thess new grub disappeared and now it is just “MISSING OPERATING SYSTEM.”

I used boot-repair and generated a boot-info

I know this is a complex problem but I am really hoping someone can help me with this. Thank you all in advance!

Unlock Bootloader from EDL mode via MSMDownloadTool


I’d like to know the proper process of “hacking” emmc_appsboot.mbn in order to flash already an unlocked bootloader from start. I didn’t want to ask for a file from an already unlocked phone because I’m interested in the process and how it works.

What I did

I tried myself editing with a hex editor the line after ANDROID BOOT! and changed the hex from 00 to 01 but the phone was perfectly bricked 😀 and I had to spend some times with the drivers (Qualcomm 9008) and learning how to put it in EDL mode with the phone not even fastbooting, afterwards I was able to “msmdownload” it again reflashing everything. I can now in fastboot and recovery.

I also tried replacing the recovery, with twrp, and actually it failed when going to recovery because of the md5 checksum.

I hex-edited both md5.img and md5sum.md5 files replacing the md5 of recovery.img with the one of twrp (renamed recovery.img of course) but still, it failed nonetheless the md5 checksum.

I suppose there is some other file where these hash’s are stored and are checked during boot.

Is it safe to assume that emmc_appsboot.mbn as well is checksumed and if it fails it doesn’t load at all?

What’s the correct process in:

1) Editing emmc_appsboot.mbn in order to unlock the bootloader

2) Making the system actually boot and work after we edited those files (probably security checks / hash’s are involved).

IMPORTANT: Please do not suggest “how to unlock the bootloader” with usb-debugging etc, the well known methods that are well known, kindly

Reference : You can download here the MSMDownloadTool with all the ROM / OP3 related files.