Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

Spoekenkieker · 2025-07-28 09:41:32

After making a lot of great and ever improving experiences with Arch Linux and building up some (now newly questioned) confidence, I thought I was in for a treat with this Laptop. But I made a few "not so smart" choices and now I've maneuvered myself somewhat into a corner, although I'm not sure whether it really is one since I seem to have so many options left. To start from the beginning:

This is my computer (I uploaded this back when everything was fine): https://linux-hardware.org/?probe=c367108bad
It comes with pre-installed Windows and seems to be heavily designed towards Windows 11, which I did not realize before buying because I got it mixed up in my head with another model. First mistake. However, I managed to get everything to work to my expectations (although the display was a little strange, for example, I had to insert my decryption password completely blind with a black screen). Not Sending it back was the second mistake. Will stop counting now.

I made some questionable choices in the BIOS (turning off USB boot, setting a password) because there was some strange Windows Bootloader on the firmware. This was, however, fine at first.

Later, I did some updates using fwupdmgr, pretty much as described in the wiki, but probably without the appropriate caution.

The day before yesterday, I noticed that I could not get into the BIOS menu. When I booted into the BIOS menu, I was prompted my Password. The system accepted my password, and after that, the Laptop just got hot and had a black screen. This is still the observed behavior when trying to enter the BIOS in any way (via Lenovo diagnostics, via the bootloader, via F2). Trying to open the Boot Option menu just leads to the Black Screen immediately.

I tried a lot of different things. The boot menu had the same problem, so I installed refind as a bootloader to try and boot from USB. I later realized that it was probably unable to find the USB stick because I had disabled USB in the BIOS. Here are my current bios settings:

# fwupdmgr get-bios-settings

SecureBoot:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          SecureBoot
  Read Only:            False

WirelessLAN:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          WirelessLAN
  Read Only:            False
    0:                  Disable
    1:                  Enable

BootOrder:
  Setting type:         Enumeration
  Current Value:        NVMe0:USBHDD:PCILAN:USBFDD:USBCD
  Description:          BootOrder
  Read Only:            False
    0:                  HDD1
    1:                  HDD2
    2:                  HDD3
    3:                  HDD4
    4:                  HDD0
    5:                  PCILAN_IPV4
    6:                  ATAPICD1
    7:                  ATAPICD2
    8:                  ATAPICD0
    9:                  USBFDD
    10:                 USBCD
    11:                 USBHDD
    12:                 OtherHDD
    13:                 OtherCD
    14:                 NVMe1
    15:                 NVMe0
    16:                 PCILAN_IPV6
    17:                 PCILAN
    18:                 NODEV

ChargeInBattery:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          ChargeInBattery
  Read Only:            False
    0:                  Disable
    1:                  Enable

PxeBootToLAN:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          PxeBootToLAN
  Read Only:            False
    0:                  Disable
    1:                  Enable

PowerOnPassword:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          PowerOnPassword
  Read Only:            False
    0:                  Disable
    1:                  Enable

AbsolutePersistanceModuleActivation:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          AbsolutePersistanceModuleActivation
  Read Only:            False
    0:                  Disable
    1:                  Enable
    2:                  PermanentlyDisable

FlipBoot:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          FlipBoot
  Read Only:            False
    0:                  Disable
    1:                  Enable

BootMode:
  Setting type:         Enumeration
  Current Value:        UEFI
  Description:          BootMode
  Read Only:            False
    0:                  LegacySupport
    1:                  UEFI

FoolProofFnCtrl:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          FoolProofFnCtrl
  Read Only:            False
    0:                  Disable
    1:                  Enable

HotkeyMode:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          HotkeyMode
  Read Only:            False
    0:                  Disable
    1:                  Enable

SATAControllerMode:
  Setting type:         Enumeration
  Current Value:        AHCI
  Description:          SATAControllerMode
  Read Only:            False
    0:                  AHCI
    1:                  RAID

IntelHyperThreading:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          IntelHyperThreading
  Read Only:            False
    0:                  Disable
    1:                  Enable

USBLegacy:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          USBLegacy
  Read Only:            False
    0:                  Disable
    1:                  Enable

USBBoot:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          USBBoot
  Read Only:            False
    0:                  Disable
    1:                  Enable

AMDPlatformSecurityProcessor:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          AMDPlatformSecurityProcessor
  Read Only:            False
    0:                  Disable
    1:                  Enable

AlwaysOnUsb:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          AlwaysOnUsb
  Read Only:            False
    0:                  Disable
    1:                  Enable

BiosBackFlash:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          BiosBackFlash
  Read Only:            False
    0:                  Disable
    1:                  Enable

pending_reboot:
  Current Value:        0
  Description:          Settings will apply after system reboots
  Read Only:            True

AMDSVMTechnology:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          AMDSVMTechnology
  Read Only:            False
    0:                  Disable
    1:                  Enable

PxeBootPriority:
  Setting type:         Enumeration
  Current Value:        Enable
  Description:          PxeBootPriority
  Read Only:            False
    0:                  Disable
    1:                  Enable

BootPriority:
  Setting type:         Enumeration
  Current Value:        UEFIFirst
  Description:          BootPriority
  Read Only:            False
    0:                  UEFIFirst
    1:                  LegacyFirst

EnhancedWindowsBiometricSecurity:
  Setting type:         Enumeration
  Current Value:        Disable
  Description:          EnhancedWindowsBiometricSecurity
  Read Only:            False
    0:                  Disable
    1:                  Enable

And here are the devices as listed by fwupdmgr:

# fwupdmgr get-devices
LENOVO 83JU
│
├─ELAN06FA:00 04F3:3293:
│     Device ID:          9c25200896802993434e33fef0759312cfe72b4c
│     Summary:            Touchpad
│     Current version:    0x0004
│     Bootloader Version: 0x0001
│     Vendor:             ELAN Microelectronics (HIDRAW:0x04F3)
│     GUIDs:              c06f9c95-16e8-5717-a563-234ff61252c9 ← HIDRAW\VEN_04F3&DEV_3293
│                         66d15ac5-67a6-504c-a7ed-6eea5f4fb0bf ← HIDRAW\VEN_04F3&DEV_3293&MOD_0037
│                         061fe02b-40db-5a7e-b380-c6e1413cbfa0 ← ELANTP\ICTYPE_11&MOD_0037
│                         99c6dd4f-ac5e-54b4-8849-168e7b8ec3aa ← ELANTP\ICTYPE_11&MOD_0037&DRIVER_HID
│     Device Flags:       • Internal device
│                         • Updatable
│                         • Unsigned Payload
│                         • Can tag for emulation
│   
├─Unknown Device:
│     Device ID:          6279f234ed389ab2b10e75b1d9cdc414e91f2b3f
│     Current version:    1536
│     Vendor:             Genesys (USB:0x05E3)
│     GUIDs:              33bf0d51-f87e-54a0-bbfc-efb323601e31 ← BLOCK\VEN_05E3&DEV_0749
│                         a3a4cb07-8f50-594c-abf0-aa474a03dd94 ← BLOCK\VEN_05E3&DEV_0749&VER_15&CID_E3054907
│     Device Flags:       • Updatable
│                         • Cryptographic hash verification is available
│                         • Unsigned Payload
│                         • Can tag for emulation
│   
├─AMD Ryzen AI 7 350 w/ Radeon 860M:
│ │   Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │   Current version:    0x0b60000e
│ │   Vendor:             Advanced Micro Devices, Inc.
│ │   GUIDs:              e18396bd-f52d-58b8-ad26-9c62ab2b812a ← CPUID\PRO_0&FAM_1A&MOD_60
│ │                       9b0249ea-4fbc-5ea6-b0fa-bdf457bef490 ← CPUID\PRO_0&FAM_1A&MOD_60&STP_0
│ │   Device Flags:       • Internal device
│ │ 
│ ├─AMD Radeon 860M Graphics:
│ │     Device ID:        04e17fcf7d3de91da49a163ffe4907855c3648be
│ │     Summary:          AMD STRIX_B0_GENERIC
│ │     Current version:  1
│ │     Vendor:           Advanced Micro Devices, Inc. [AMD/ATI] (PCI:0x1002)
│ │     GUID:             cc72cddc-68ef-5809-afce-bb1e5bcf571f ← AMD\113-STRIXE
│ │     Device Flags:     • Internal device
│ │                       • Can tag for emulation
│ │   
│ └─System Management Unit (SMU):
│       Device ID:        db0330716216c629bb2c07256e5d018f499eb6ce
│       Summary:          Microcontroller used within CPU/APU program 11
│       Current version:  101.4.0
│       Vendor:           Advanced Micro Devices, Inc.
│       GUID:             a0e3c12e-67da-5e9a-94fc-be35467ee328 ← /sys/devices/platform/AMDI000A:00
│       Device Flags:     • Internal device
│                         • Can tag for emulation
│     
├─Generic Billboard Device:
│     Device ID:          464e0f43e0b1233f48c35a622f65e112e89e1df2
│     Current version:    7.99.38.29
│     Vendor:             Fresco Logic (USB:0x1D5C)
│     Install Duration:   15 seconds
│     GUIDs:              4b8e93aa-7207-5706-9e90-b55306343c84 ← USB\VID_1D5C&PID_7102
│                         790a1b00-9cf9-5220-af78-ef690d303fa8 ← USB\VID_1D5C&PID_7102&CID_63
│     Device Flags:       • Updatable
│                         • Unsigned Payload
│                         • Can tag for emulation
│   
├─Integrated Camera:
│     Device ID:          d787669ee4a103fe0b361fe31c10ea037c72f27c
│     Current version:    10.20
│     Vendor:             Luxvisions Innotech Limited (USB:0x30C9)
│     Serial Number:      0001
│     GUID:               b3431ba1-a3f4-5aff-91ec-c6bea0dc5a0c ← USB\VID_30C9&PID_00F7
│     Device Flags:       • Updatable
│                         • Can tag for emulation
│   
├─SKHynix HFS001TEM4X182N:
│     Device ID:          71b677ca0f1bc2c5b804fa1d59e52064ce589293
│     Summary:            NVM Express solid state drive
│     Current version:    61000A31
│     Vendor:             SK hynix (PCI:0x1C5C)
│     Serial Number:      5ME1N002810901J0E
│     GUIDs:              db00a8fd-92ba-5588-a43a-551c40ee9115 ← NVME\VEN_1C5C&DEV_1F69
│                         2a83c11e-4f99-5e82-bd52-d60a207d7aee ← NVME\VEN_1C5C&DEV_1F69&SUBSYS_1C5C1F69
│                         4afe32d6-7826-5afd-9bcb-280a0b0cf34c ← SKHynix_HFS001TEM4X182N
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│                         • Signed Payload
│                         • Can tag for emulation
│   
├─System Firmware:
│ │   Device ID:          0968cfe3c0cf80f24b58bd0a47bb03a401259614
│ │   Summary:            UEFI System Resource Table device (updated via NVRAM)
│ │   Current version:    26428686
│ │   Minimum Version:    26428686
│ │   Vendor:             LENOVO (DMI:LENOVO)
│ │   Update State:       Success
│ │   GUID:               b8d75e48-f954-5e80-5b32-618773f154a0
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • System requires external power source
│ │                       • Needs a reboot after installation
│ │                       • Device is usable for the duration of the update
│ │   Device Requests:    • Message
│ │ 
│ ├─Ideapad Products:
│ │     Device ID:        6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│ │     Summary:          UEFI Platform Key
│ │     Current version:  2012
│ │     Vendor:           Unknown
│ │     GUID:             a02e3c5c-6ee7-5d56-87fa-64f2ac6d3d5c ← UEFI\CRT_AE3BB84D4581781587A40E4315B48DF56938FF6C
│ │     Device Flags:     • Internal device
│ │   
│ ├─UEFI Key Exchange Key:
│ │ │   Device ID:        2a4c23bfb79b5dabe474cb7b1b3e604645d6f9c6
│ │ │   Device Flags:     • Internal device
│ │ │ 
│ │ └─KEK CA:
│ │       Device ID:      b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7
│ │       Current version: 2023
│ │       Vendor:         Microsoft (UEFI:Microsoft)
│ │       GUIDs:          814e950f-1449-566a-a190-42c9d3a3a2df ← UEFI\VENDOR_Microsoft&NAME_Microsoft-KEK-CA
│ │                       cd94ec34-7163-5f27-8549-1bd4b7872ae8 ← UEFI\CRT_DEC64D7746D983DB3774829A00BF829D9F19E9CF
│ │       Device Flags:   • Internal device
│ │                       • Updatable
│ │                       • Needs a reboot after installation
│ │                       • Device is usable for the duration of the update
│ │                       • Signed Payload
│ │                       • Can tag for emulation
│ │     
│ ├─UEFI Signature Database:
│ │ │   Device ID:        0352a8acc949c7df21fec16e566ba9a74e797a97
│ │ │   Device Flags:     • Internal device
│ │ │ 
│ │ ├─UEFI CA:
│ │ │     Device ID:      5bc922b7bd1adb5b6f99592611404036bd9f42d0
│ │ │     Current version: 2023
│ │ │     Vendor:         Microsoft (UEFI:Microsoft)
│ │ │     GUIDs:          26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
│ │ │                     308281c7-d0c5-52e0-8c1a-810540de03df ← UEFI\CRT_7CD7437C555F89E7C2B50E21937E420C4E583E80
│ │ │     Device Flags:   • Internal device
│ │ │                     • Updatable
│ │ │                     • Supported on remote server
│ │ │                     • Needs a reboot after installation
│ │ │                     • Signed Payload
│ │ │                     • Can tag for emulation
│ │ │   
│ │ └─Windows UEFI CA:
│ │       Device ID:      d31da5f926c6d962ed810b284fab5a2ef623007b
│ │       Current version: 2023
│ │       Vendor:         Microsoft (UEFI:Microsoft)
│ │       GUIDs:          914015a8-9d92-5462-9a9b-f2b361e4faae ← UEFI\VENDOR_Microsoft&NAME_Windows-UEFI-CA
│ │                       89a825bf-78b5-5f1c-905b-e982b2f02584 ← UEFI\CRT_A794240D25F0CCB2EC8142DC2F7411890717DEAD
│ │       Device Flags:   • Internal device
│ │                       • Updatable
│ │                       • Needs a reboot after installation
│ │                       • Signed Payload
│ │                       • Can tag for emulation
│ │     
│ └─UEFI dbx:
│       Device ID:        362301da643102b9f38477387e2193e57abaa590
│       Summary:          UEFI revocation database
│       Current version:  20250507
│       Minimum Version:  20250507
│       Vendor:           UEFI:Microsoft
│       Install Duration: 1 second
│       GUIDs:            f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
│                         d07ff664-b0e1-5f4e-a723-d7fbcbfcb94f ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_X64
│       Device Flags:     • Internal device
│                         • Updatable
│                         • Supported on remote server
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│                         • Only version upgrades are allowed
│                         • Signed Payload
│                         • Can tag for emulation
│     
├─UEFI Device Firmware:
│     Device ID:          786aa9903351899de9ddcf6b85dd90b3c7ba4db7
│     Summary:            UEFI System Resource Table device (updated via NVRAM)
│     Current version:    1
│     Minimum Version:    1
│     Vendor:             DMI:LENOVO
│     Update State:       Success
│     GUID:               3d65bf3e-fb39-41f7-9e60-57beb7d231bd
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│     Device Requests:    • Message
│   
├─UEFI Device Firmware:
│     Device ID:          a72e3281a531abfca4a28e838dae6de3a5171526
│     Summary:            UEFI System Resource Table device (updated via NVRAM)
│     Current version:    1
│     Minimum Version:    1
│     Vendor:             DMI:LENOVO
│     Update State:       Success
│     GUID:               fb18fe92-a67a-b1a3-5598-d741a5c825f2
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│     Device Requests:    • Message
│   
├─UEFI Device Firmware:
│     Device ID:          78993b39e01be8744ceb11353516be73d9738343
│     Summary:            UEFI System Resource Table device (updated via NVRAM)
│     Current version:    1
│     Minimum Version:    1
│     Vendor:             DMI:LENOVO
│     Update State:       Success
│     GUID:               833f5f0c-c040-4771-bbd5-b0d0f6ef9dc4
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│     Device Requests:    • Message
│   
└─UEFI Device Firmware:
      Device ID:          ee7908b76a35d47e9930a219a1e0a96ba0da1fd7
      Summary:            UEFI System Resource Table device (updated via NVRAM)
      Current version:    1
      Minimum Version:    1
      Vendor:             DMI:LENOVO
      Update State:       Success
      GUID:               09aae9ff-6fcf-fd34-11dd-cad94b7457c3
      Device Flags:       • Internal device
                          • Updatable
                          • System requires external power source
                          • Needs a reboot after installation
                          • Device is usable for the duration of the update
      Device Requests:    • Message

I think my meddling with fwupdmgr caused this whole problem. But as I can still boot stuff from my HDD, It somehow feels like I'm still in control. I'm writing this from said Laptop after all.
Here are the boot options efibootmgr can find:

# efibootmgr

BootCurrent: 0002
Timeout: 2 seconds
BootOrder: 0002,0013,0014,0015,0016,0017,0018,0001,0000
Boot0000* Linux-Firmware-Updater        HD(1,GPT,cd000e48-dc73-48b6-9f97-a4df7b6f3d5c,0x800,0x200000)/\EFI\systemd\fwupdx64.efi
Boot0001* Windows Boot Manager  HD(1,GPT,cd000e48-dc73-48b6-9f97-a4df7b6f3d5c,0x800,0x200000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0002* rEFInd Boot Manager   HD(1,GPT,cd000e48-dc73-48b6-9f97-a4df7b6f3d5c,0x800,0x200000)/\EFI\refind\refind_x64.efi
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012  UEFI Diagnostics      FvFile(f8397897-e203-4a62-b977-9e7e5d94d91b)
Boot0013* NVMe: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a4)
Boot0014* USB HDD:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0015* PCI LAN:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0016* USB FDD:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0017* USB CD:       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB LAN:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,e854bca4cae7704ca322b00da0376322)
Boot0019* Reinstall Windows from Cloud  FvFile(3edbaac4-5017-4870-8cc4-721f9ef1974f)2d004100700070000000

I've also downloaded the .exe for the BIOS update from Lenovo, extracted the BIOS.cap and installed it with fwupdtool install-blob. This seems to have fixed a few quirks, like the black screen during start up, but otherwise everything seems unchanged. I'm not even sure whether the update really truly worked or whether that was just some sort of reset triggered by my attempt to flash the update.
If anyone could help me with any of the following (or any other related) tasks:
do any CMOS-stuff before I absolutely have to.

Booting via USB
Resetting the BIOS Admin PW
Changing BIOS settings with a known password (I know the password after all)
Finding a more appropriate place to post this - I thought Lenovo probably would not help me since Linux is not really supported
Finding the cause of the problem

Great Laptop, if it wasn't for all this Windows-stuff. Any ideas and suggestions sould be appreciated. I don't think I will open the Laptop and disconnect any batteries before I absolutely have to however.

UPDATE: I managed to use the interface under /sys/class/firmware-attributes/thinklmi/authentication/Admin to change BIOS settings and to set the password to empty. Still cannot boot from a stick - in fact, the computer just hangs when a stick is connected during boot. The upgrades with fwupd do not work, probably because the old BIOS does not work properly anymore.

Last edited by Spoekenkieker (2025-07-28 16:28:32)

rogerwegmanneit · 2025-08-01 10:37:01

Do you have any news on this? I ran in exactly the same issue with my 14" version.

Spoekenkieker · 2025-08-01 11:36:07

Yes, I actually managed to fix it 1-2 hours ago with the crisis recovery feature, so shortly after you asked. I did not even have to re-do the setup or install Windows or anything like that. Only the bootmanager had to be re-installed afterwards, which was no problem, since I could boot from a stick again. But Lenovo does warn against this method.

I roughly followed the steps outlined here: https://github.com/nonkerdoob/Smokeless … _CRISIS.md

I downloaded the most recent BIOS from Lenovo, qxcn16ww.exe for me.
I extracted it with 7z x qxcn16ww.exe. I re-named the extracted LenovoBiosUpdateTool/Rfs/Fw/Yoga/BIOS.cap file to qxcn.bin
I put that renamed file and only that file on an otherwise clean FAT32/GPT USB key. And then I did this re-boot as described in the guide while holding fn+R throughout. No beeping (which the guide warns about). No long black-screen. A Lenovo install display that seemed mildly re-assuring. Afterwards, I got into the diagnostics. I re-booted and I could get into the BIOS menu. Then I disabled safe-boot again. I booted from an arch stick. I re-installed the bootloader. Checked that I could see it via efibootmgr. And now everything is working fine again.

EDIT: About the time you asked, wrong time zone. I think I should mention that some BIOS settings might have enabled that success. So maybe you have to try around with them. I don't know which ones I had before I flashed the BIOS, since that process seems to have reset the settings to default for me.

Last edited by Spoekenkieker (2025-08-01 11:38:53)

rogerwegmanneit · 2025-08-01 11:38:49

Thank you very much. I will try this too.

Spoekenkieker · 2025-08-01 11:44:58

No guarantee from my side obviously I just felt like that could work and tried it. I couldn't even find the qxcn.bin-string via uefitool as suggested in the guide. I did find some functions that seemed to suggest that the image does check for its name however. So I just hoped that they went with the more logical naming scheme on the newer model and it worked.
Good luck!

rogerwegmanneit · 2025-08-01 12:12:20

I placed also this file on an empty FAT32 USB stick but I see this "AMD PEI GOP" and it doesn't go away.

rogerwegmanneit · 2025-08-01 12:15:09

I cannot enter the BIOS. I set a password. After I enter the password for the BIOS the screen stays black.

Spoekenkieker · 2025-08-01 12:27:04

I'm sorry, I don't know what that is. If you look at the first post, I mentioned in my 1st EDIT that I also had a BIOS password set. I managed to reset it via my running Linux system. You can access the settings there after writing the current password to the writable password file and writing an empty string to the new_password file.

Can you still get any OS to boot on your system or has that ship now sailed?

rogerwegmanneit · 2025-08-01 12:34:10

Ahhhhh ... this would be the way to set a new password. And I always asked my why writing an empty string to any of the password files didn't work. But this ship is gone :-( I hoped removing all bootable partitions (EFI) from the NVMe would trigger the BIOS to always boot from an Linux-USB stick. But this didn't work and now I am ...

rogerwegmanneit · 2025-08-01 12:34:51

But thank you for your help. May be someone else sees this before he makes my wrong steps.

Spoekenkieker · 2025-08-01 12:46:06

If you can still access your system, you can try to at least fix the BIOS PW problem.

As root, you can reset your PW by first writing your current_password to the corresponding file:

# echo 'YOURPW' > /sys/class/firmware-attributes/thinklmi/authentication/Admin/current_password

Note that you have to be root I think for redirecting with > like that, sudo does not propagate privilege like that, or you have to use tee or something similar. After doing that, you can change settings, either via a similar process, or with fwupdmgr:

# fwupdmgr get-bios-settings

# fwupdmgr set-bios-setting USBBoot Enable

You can delete the password by doing

# echo '' > /sys/class/firmware-attributes/thinklmi/authentication/Admin/new_password

and rebooting.

This is only the admin password for the BIOS. I did not try out the case where you have to enter a PW to even boot, neither did I look at disks encrypted on the BIOS level.

What did you rename the BIOS.cap file to in your case? What is the name of the exe-file for you?

EDIT:
This was based on ljrk0's suggestions here: https://github.com/fwupd/fwupd/issues/4948

Last edited by Spoekenkieker (2025-08-01 12:57:48)

Spoekenkieker · 2025-08-01 12:46:52

Ah okay, hm, I'm sorry...
Yeah, same goes for that guide I guess.

rogerwegmanneit · 2025-08-01 12:55:05

But maybe you can help others with this guide.

rogerwegmanneit · 2025-08-01 13:53:36

I am back and I have a bootable linux. But did you manage this:
I've also downloaded the .exe for the BIOS update from Lenovo, extracted the BIOS.cap and installed it with fwupdtool install-blob.
I get error message when I try to install the BIOS.cap with the command you mentioned.

rogerwegmanneit · 2025-08-01 14:04:50

I still have my black screen ... now the Fn+R doesn't work ... I don't see the AMD neither the Yoga logo.

Arch Linux

#1 2025-07-28 09:41:32

Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#2 2025-08-01 10:37:01

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#3 2025-08-01 11:36:07

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#4 2025-08-01 11:38:49

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#5 2025-08-01 11:44:58

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#6 2025-08-01 12:12:20

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#7 2025-08-01 12:15:09

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#8 2025-08-01 12:27:04

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#9 2025-08-01 12:34:10

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#10 2025-08-01 12:34:51

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#11 2025-08-01 12:46:06

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#12 2025-08-01 12:46:52

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#13 2025-08-01 12:55:05

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#14 2025-08-01 13:53:36

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

#15 2025-08-01 14:04:50

Re: Semi-Soft-Bricked Yoga 7 2-in-1 16AKP10 - Type 83JU BIOS Black Screen

Board footer