Start a Conversation

Unsolved

S

1 Rookie

 • 

3 Posts

38

June 19th, 2025 10:53

Stuck in GRUB Shell — Cannot Boot Windows USB or Enter BIOS (Dell XPS 13 7390)

I'm facing a frustrating boot issue on my Dell XPS 13 7390. Here's the full situation:


🔹 Background:

  • My laptop runs in UEFI mode with Secure Boot disabled.

  • GRUB is installed (likely from a previous Linux installation).

  • I’m trying to boot into a Windows 10/11 Setup USB to reinstall or repair Windows.


🔹 Issue:

  • When I power on and press F12, the system shows the "Entering Boot Menu" loading bar but still goes straight into the GRUB shell.

  • It refuses to enter BIOS or the Boot Menu under any condition if a bootable USB is connected.

  • GRUB shell is the only thing that loads.


🔹 What I’ve Tried:

  1. Windows USB:

    • Created with Rufus (GPT, UEFI, FAT32 and NTFS variants).

    • The USB is detected in GRUB (ls confirms it), and I can see /efi/boot/bootx64.efi.

    • When I try:

      bash
      Copy Edit
      chainloader (hd1,gpt1)/efi/boot/bootx64.efiboot

      I get: "cannot load image", even though the file is present.

  2. Old Windows on NVMe:

    • If I boot without the USB, I can chainload and successfully boot into my existing Windows installation:

      swift
      Copy Edit
      chainloader (hd0,gpt1)/EFI/Microsoft/Boot/bootmgfw.efiboot
    • However, after attempting to chainload the USB once, even booting the old Windows gives “cannot load image” — until I reboot.

  3. BIOS Access:

    • When USB is plugged in, I can't access BIOS at all (F2 or F12 → always drops to GRUB).

    • Even when USB is first in boot priority, it still goes straight to GRUB shell.

  4. Rufus USB:

    • Rufus-created USB (GPT + UEFI) does show up and partially boots but gives:

      java
      Copy Edit
      Load unsupported (3)
    • Same with NTFS and FAT32 variants.


🔹 Conclusion:

  • It feels like GRUB has hijacked booting, and the Dell UEFI firmware refuses to override it.

  • Chainloading the USB bootx64.efi fails with cannot load image.

  • BIOS cannot be entered when USB is present.

  • After trying to chainload USB once, GRUB breaks the context and can’t load any EFI file until reboot.

  • I suspect a firmware/NVRAM issue or UEFI boot context conflict.


🔹 What I Need:

  • A reliable way to:

    • Boot directly into BIOS (even with USB inserted).

    • Reset NVRAM/boot entries so GRUB doesn't override everything.

    • Successfully boot into Windows Setup from USB on UEFI.


Let me know if more hardware info is needed. Thanks!

3 Apprentice

 • 

649 Posts

June 19th, 2025 13:32

Hi

I would consider deleting the uEFI boot partition, which should wipe out any and all GRuB's.

It is then possible to use a windows install disk to repiar the boot partition.

A coupla caveats, GRuB may be installed into the primary partition, a grub bug error?

Also in the BIOS there should be a BOOT MANAGER list that you can select.

and not just a list of bootable devices.

1 Rookie

 • 

3 Posts

June 19th, 2025 15:03

@anne_droid​ 

Hey, thanks for your reply!

Firstly, if I delete the UEFI boot partition, then I would not be able to access my old Windows install at all. To mimic this, I had disabled booting from the NVMe drive using the BIOS (by disabling boot only and disabling the drive entirely). In both cases, even when the USB is plugged in, it does not boot from it and goes for the pre-boot system checks and looping endlessly. Moreover, there is no 'boot manager' option in the BIOS, since it detects grub only and the USB (yes, the USB shows up as a bootable option in the BIOS, but isn't used for booting i.e it is ignored entirely).

Secondly, sometimes when the USB is plugged in and I turn the computer on, the backlight comes on and it hangs for like 30+ seconds. In this case, if I unplug the USB, it immediately proceeds (i.e showing the Dell Logo and into grub shell). If I keep the USB plugged in, it can take upto a minute before it shows the Dell Logo and then boots to grub.


3 Apprentice

 • 

649 Posts

June 20th, 2025 11:08

Hi

If you have a coupla USB sticks handy, make

1 a W11 install disk and use it to repair the boot area.

2 install linux mint live and run a coupla commands to check the boot status

fdisk -l

efibootmgr -V

Then you may have to mount the \efi partition and edit it.

So if we can establish what you have, where, maybe we can modify it.

EG:

root@SLap             
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7ABF9C04-13E9-4D6B-B6EF-60C24B3F0B81

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     534527    532480   260M EFI System
/dev/nvme0n1p2    534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296  418666495 418099200 199.4G Microsoft basic data
/dev/nvme0n1p4 418666496  419997695   1331200   650M Windows recovery environment
/dev/nvme0n1p5 419999744  732499967 312500224   149G Linux filesystem
/dev/nvme0n1p6 732499968  997736447 265236480 126.5G Microsoft basic data
/dev/nvme0n1p7 997736448  999682047   1945600   950M Windows recovery environment
/dev/nvme0n1p8 999682048 1000214527    532480   260M Windows recovery environment
root@SLap5  2023  DroidSansFallback.atf
drwx------ 5 root root    4096 May  1 19:44  EFI
drwx------ 2 root root    4096 Apr  1 15:28 'System Volume Information'
root@SLap9 14:00 Boot
drwx------ 4 root root 4096 May  1 19:44 Microsoft
drwx------ 2 root root 4096 Apr  9 14:00 ubuntu
root@SLap1 19:44 Boot
drwx------  2 root root 4096 Apr  1 15:26 Recovery

If you can achieve any of the above please ask again.

No Events found!

Top