Disabled Secure boot in Windows 10. Boot settings changed to accept CD/DVD. Inserted DVD with Linux Mint Serena. All went well until updating was nearly completed, at which point the installer crashed.

I don't know how to establish an internet connection at the grub prompt, so instructions that require connectivity online have not been tried.

Laptop is HP 15 Notebook PC, if that helps. At this time, no other information is available because the laptop will not boot at all. Only a grub prompt appears.

After researching potential solutions including these forums, I've spent hours with unsuccessful attempts at trying a boot repair with a USB stick created with the USB Image Writer on a separate laptop. The laptops are both HP notebooks, and the ISO is the same - Linux Mint Cinnamon 18.1 Serena 64 bit. Is this attempt to boot with a USB stick failing because it created on a different laptop?

I don't understand the grub command prompt that keeps appearing no matter what is done:

Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.

Thank you for suggestions and assistance to resolve this.

"nearly completed" isn't.

Re-install Linux.

What is the next step? So far all the instructions that could be found that don't require internet connectivity have been tried. I am at a loss for what to do next.

Check your backups?
What instructions?

The install went well until the installer crashed. Now there is the 'BASH' message in addition to the grub prompt.

I don't know why the installer crashed.

I haven't found instructions for repairing the boot problem without connectivity. This is not for a dual boot. I want only Linux Mint Cinnamon Serena 64 bit installed. So far, online instructions regarding the BASH message and grub prompt have been for dual booting.

A bootable USB and CD are both made.

BIOS / UEFI settings allow booting from USB CD DVD.

After restarting with either the USB or CD, the same BASH message appears, then the grub prompt.

A back up of which? Instructions for which?

I've spent a day and half now, looking online for help all over, and trying to figure out what is wrong and what to do.

We don't know why the installer crashed either but, it did so as suggested above, start over and reinstall.
Which installation option did you select during the install?
If you have windows 10 installed, is it using UEFI?
Did you try to install Mint UEFI?
Grub is a bootloader, you can't connect to the internet with it.
Your installation failed at some point and now you have some Grub boot files installed but it didn't complete. You make reference to using the boot repair utility which has an option to Create BootInfo Summary. Use that and post a link to the output so we have some useful information to work with.

Your attempt to boot from a usb stick will not fail because it was created on another computer but there are many reasons it could fail such as not being written to the usb correctly?

Since the install failed, it seems the simplest solution would be to reinstall. Might be best to use the manual (Something Else) option and select not to download additional software and updates during the install. You can also do that easily after the install.

If you keep getting the grub prompt or some bash message (??)when trying to boot, make sure you have actual set boot priority to the DVD drive or usb drive, whatever you use. If you created a usb with boot repair, did you test boot it on another computer to see if it boots?

Attempts to reinstall have not worked. The USB and CD with the ISO both prompt to install on the other laptop so they must work, yes? The install on the CD worked without any problems on this laptop, and another laptop with Mint installed over Windows 10 without issues.

The selected installation option was erase and overwrite everything.

Windows 10 was installed, and it was UEFI (which still appears if F10 is selected).

Upon startup, there is no menu or options to choose an operating system. When the laptop is turned off then on, all that appears is a black screen with the BASH message followed by the grub prompt.

Regarding internet connectivity, I meant the only instructions found online for a Live USB boot repair, require connectivity.

I did not try to install Mint UEFI. The only instructions found for that so far are:

https://www.lifewire.com/create-uefi...nt-usb-2202084

The tools required to create a UEFI bootable Linux Mint USB drive are as follows:

Linux Mint ISO (this will be downloaded as part of the tutorial)
Win32 Disk Imager (this will be downloaded as part of the tutorial)
A blank USB drive
A laptop with Windows 8.1 or Windows 10 pre-installed

Windows 10 was installed, however now there is no option to choose Windows 10 at startup. I don't have Win32 Disk Imager. The bootable USB and CD were created by the Linux USB Image Writer on a non-UEFI laptop. I do not have a copy of Windows 8 or 10. (At this point, only the 1st and 3rd requirements are met.)

The attempted boot repairs on USB and CD did not work on the laptop (with the BASH message and grub prompt). The laptop does not recognize the USB or CD when they are inserted or after restarting.

Because the laptop being worked on cannot boot up, there is no way to copy / paste output. SO frustrating! All that appears is that minimal BASH message and the grub prompt. Aside allowing F1 and F10 to see BIOS / UEFI options, it does not do anything else.

"not being written to the usb correctly?" Perhaps because the bootable USB and CD were created on a non-UEFI laptop?

Because the laptop isn't recognizing anything, a reinstall hasn't been possible.

What else might be considered at this point?

Thank you.

You need to get into the EFI boot menu - like you did when you set the CD first in the order. The failed install has probably updated the default boot order. Ahhh - I see now; ok what options do you get when you use F10 ?. Take a photo and post a link to that.

Currently there isn't a way to take a screenshot and I don't have a camera :./ Typed (not copy /pasted):

Main

System Time (current time)
System Date (today)
Notebook Mode I HP 15 Notebook PC
Product Number LOT33UA#ABA
System Board ID 8175
Born On Date 02/22/2016
Processor Type Intel(R) Celeron(R) CPU N3050 @ 1.60GHz

Total Memory 4 GB
BIOS Version F.24
BIOS Vendor Insyde
Serial Number 5CD5422TZP
UUID Number 35444335-3234-5432-5A50-B05ADADIFEC5
System Board CT Number PFKGV038J9L119
Factory installed OS Win10
Primary Battery SN 22010 09/06/2015
WLAN FCC ID TX2-RTL8a88EE
System Log (shows a lot of numbers)
Build ID 15WW3BUT601#SABA#DABA
Feature Byte 3Q3a6b7K7P7WaBapaqasauawbhbpbzcbdUdpdq.gg

Security

Administrator Password <Clear>
Power-On Password <Clear>
TPM Device <Available>
TPM State <Enabled>
Clear TPM <No>
Restore Security settings to Factory Defaults

System Configuration

Language <English>
Virtualization Technology <Disabled>
Action keys Mode <Enabled>
Boot Options:

Post Hotkey Delay (sec) <0>
CD-ROM Boot <Enabled>
Internal Network Adapter Boot <Enabled>
Network Boot Protocol <IPv4+IPv6 (UEFI)>
Legacy Support (Disabled)
Secure Boot (Disabled)
Platform Key Not Enrolled
Pending Action None
Clear All Secure Boot Keys
Load HP Factory Default Keys

UEFI Boot Order
OS Boot Manager (in a blue box) ubuntu (TOSHIBA HQ01ABF050)
Internal CD/DVD ROM Drive
USB Diskette on Key/USB Hard Disk
Network Adapter
USB CD/DVD ROM Drive

Legacy Boot Order
Notebook Hard Drive
Internal CD/DVD ROM Drive
USB Diskette on Key/USB Hard Disk
USB CD/DVD ROM Drive
Network Adapter

Note: When USB CD/DVD ROM Drive is selected and saved before exiting, the boot order above does not change. I don't know what that indicates. Just saying.

Ok, you should also have a key to pop up just a boot list - one that you can scroll down and select the USB on. Maybe F9, <Esc> ...
That's the list I really want to see -especially if it has 2 entries for the USB - one "normal" and one "UEFI". That list gets built dynamically depending on what's physically plugged in at the time.

You really do need to have a UEFI image on that USB for a proper install, but if you can boot anything at least we can get some data about your situation.

Boot Option Menu

OS boot Manager (UEFI) - ubuntu (TOSHIBA MQ01ABF050)
USB Hard Drive (UEFI) - KingstonDataTraveler 2.0
Network Adapter (IPv4 UEFI)
Network Adapter (IPv6 UEFI)
Boot From EFI File

Yay! I selected USB Hard Drive (UEFI) - KingstonDataTraveler 2.0 and was able to choose to install Linux Mint!!

Thank you!!!

I'm not sure what is next since there's not a Windows 10 OS to create a UEFI bootable Mint disk from. Until then, I wonder if allowing the dual boot install instructions or manual install might work. At least until a Windows 10 UEFI is available to create a bootable UEFI USB or CD install disk.

Currently a message during the install says no operating system is detected. I'll give it a try.

F9 was where I needed to be. Thank you!! :.) <3 <3

This machine's firmware has started the installer in UEFI mode but it looks like there may be existing operating systems already installed using "BIOS compatibility mode". If you continue to install Debian in UEFI mode, it might be difficult to reboot the machine into any BIOS-mode operating systems later.

If you wish to install in UEFI mode and don't care about keeping the ability to boot one of the existing sytems, you have the option to force that here. If you wisth to keep the option to boot an existing opertig system, you should choose NOT to force UEFI installation here.

Does this indicate potential success or failure if the install continues? If this won't work, I will wait until a bootable USB / CD can be made on a Windows 10 machine.

Now there seems to be a problem with repositories. Still, the original problem appears to be resolved. The install went well. No errors. Rebooted without any issues after USB install disk was removed. Now to resolve this repository issue.

Thank you so much for putting me on the right track!

The message you posted above in post 12 indicates that while you had a windows 10 UEFI install, your original install of Mint, the one which failed was not installed UEFI and even if the installer hadn't crashed you would have had booting problems. Moot point anyhow now that you have it installed.

Yes and thank you