8 CPU sockets are counted. The expected result is 1 socket / 8 cores.

The Lumia 950 and XL have a Lattice UC120 chip for USB-C negotiation and USB-PD.
Right now, it appears that this chip loses its configuration at some point during boot (likely when the SoC is switched to 64-bit mode), requiring a reupload of the bitstream.

The bitstream upload protocol for the UC120 uses a modified SPI bus that the MSM SPI controllers don't support, thus requiring GPIO bitbanging. Unfortunately Windows' GPIO stack isn't fast enough to upload the whole 72KB bitstream over bitbanged SPI (~1KHz is the maximum achievable), so this needs to be done in the UEFI instead.

This unblocks further Windows versions

Apologies if this isn't the right place to enquire.

I'd just like to know how you have managed to run a custom boot-oader on these devices, assuming that Qualcom's boot process is the same as that on their android counterparts.

I've been looking for a way to unlock the bootloader on my Galaxy S5, and have come up short (there is a way to change the CID on the internal storage so that the phone thinks it's a 'developer edition' device, but mine is incompatible.

After deploying the latest version of Windows, it brings up a BSOD that has the error "INACCESSIBLE_BOOT_DEVICE"... any suggestions?
Image

Edit: I just remembered I can use older versions of windows, so I'm trying 1803
Edit 2: 1803 doesn't work either, but I get a different error: SDBUS_INTERNAL_ERROR
Edit 3: After rebooting that error seemed to fix itself. It's now at "Getting Devices Ready". I guess I'll just update it to 1903 when it gets fully set up.
Edit 4 ugh: I keep getting SDBUS_INTERNAL_ERROR
Edit 5: I guess it only wants to start when it wants to. Works now, I guess I just have to restart it about 5 or 6 times if my device decides it has better things to do than, yn, work

When to support HDMI ?

/home/vsts/work/1/edk2/Lumia950XLPkg/Lumia950.dsc(...): error 4000: Instance of library class [ImagePropertiesRecordLib] is not found
log:
log.txt

With gus' Secure Boot unlock flaw making it possible to exploit MSM8996 devices like the HP Elite X3, would it be possible to port this UEFI firmware to MSM8996? Does the MSM8994 used in the 950s share a significant amount of code with the MSM8996?

When deployed install.wim to Lumia 950 XL, after few seconds ther is a message with FILE NOT FOUND

The file is this

https://github.com/WOA-Project/Deployment-Scripts-master

How I continue?

Thanks in advanced
D

Revert changes for the patched table

The branch of msm8994 is kept for historical reasons. From the engineering perspective, we might want to move everything back to the master branch.

• Create master branch
• Reconfigure CI trigger rules and build validation workflow

Win10 Build 17763 cannot bootstrap on my Lumia 950 XL (RM-1116) through your latest UEFI and bootshim, but Build 17134 can. What's the problem with it?
BTW, can WLAN, USB and Camera driver work through your latest UEFI?

This AArch64 uefi can't detect external sdcard.However the original arm32 one can.Will it possible to add sd driver and boot from sdcard?

• Mask log output
• Test boot

When I was building uefi from the latest source code, I was troubled. The error message says "/mnt/e/zengxianxi/uefi/lumia/edk2/Lumia950XLPkg/Lumia950XL.dsc(79): error F001: Pcd (gEmbeddedTokenSpaceGuid.PcdPrePiCpuMemorySize) defined in DSC is not declared in DEC files referenced in INF files in FDF. Arch: ['AARCH64']". How can I solve it?

Reported by @ADeltaX.

As titled said

Would it be very difficult to do this on an HP Elite X3?

Recent Windows arm64 builds brick the device. The symptom is observed on at least Lumia 950, 950XL, NovaGo and Envy x2. While the ongoing investigation continues, it is a good idea to write-protect certain regions on the eMMC.

Protected regions

• GPT header
• SBL1 to TZAPPS, as well as PLAT

Hello! I know what you can boot windows 10 ARM on old Lumia.
I have a question: can i boot it on my phone(2 core qualcomm armv7, 1 GB RAM). I port on my phone efidroid(edk2 uefi, but with GUI). Can i use it to install windows on sd card and boot?
Please, write answer! Thanks.

In another word, which drivers we don't have yet?
If i want to contribute to this project, what knowledge should I have? thx

Mentioned in README.md.

Since we are targeting multiple devices, it is not feasible to set a fixed 3GB assumption for memory configuration. Apart from fixed subsystem regions, we should retrieve other usable memory regions from the memory module information in SRAM.