Skip to content
This repository was archived by the owner on Feb 16, 2025. It is now read-only.

UUPDownload: please provide a way to select HWID #229

Open
lumag opened this issue Sep 2, 2024 · 6 comments · May be fixed by #230
Open

UUPDownload: please provide a way to select HWID #229

lumag opened this issue Sep 2, 2024 · 6 comments · May be fixed by #230
Assignees

Comments

@lumag
Copy link

lumag commented Sep 2, 2024

Please provide a way to select the HWID type used for GUID generation. Some devices (e.g. X13s) use HWID other than the current default (4, Manufacturer + Family + Product + SKU).

@gus33000
Copy link
Owner

gus33000 commented Sep 3, 2024

What other types have the oem chosen to use here? I'm curious as I know each oem can chose what they want in mission control but I hardly saw any other combo.

@lumag
Copy link
Author

lumag commented Sep 3, 2024

X13s uses HWID-11 (just Manufacturer + Family, unless I'm mistaken). And I'm not sure what T14s uses. I wasn't able to get drivers for it by using data from https://github.com/TravMurav/dtbloader/blob/main/scripts/hwids/x1e78100-lenovo-thinkpad-t14s.txt . I found that YogaSlim7x requires build 10.0.26100.1591. Maybe T14s also requires some other build.

Probably I should specify the reason for my questions/requests/issues: I'm using WoA cabinets to create machine-specific firmware packages for Linux installations.

@lumag
Copy link
Author

lumag commented Sep 6, 2024

Update: T14s also uses non-typical GUID, it is HWID-7, Manufacturer + ProductSky

@gus33000
Copy link
Owner

gus33000 commented Sep 6, 2024

Update: T14s also uses non-typical GUID, it is HWID-7, Manufacturer + ProductSky

Ok interesting, im not sure where you are getting this HWID-X naming by the way, im not familiar with it at least (is this standard?) I created a branch and an initial PR to lay the ground work to a proper tool with a list of current thought through features to enable this outside of specific or PoC use cases.

@lumag
Copy link
Author

lumag commented Sep 6, 2024

@gus33000
Copy link
Owner

gus33000 commented Sep 7, 2024

Ok interesting never seen that documentation before but i was familiar with the computerhardwareids.exe tool in itself.

Also quite funny to see the documentation indexes from 0, while the tool indexes hardwareIdsX starting from 1. That explains the discrepency I had

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants