Version 2310.1 - Sunflower 🌻
Surface Duo UEFI BSP - Version 2310.1 (Sunflower)
General information
**Released:** 10/01/2023 11:00 PM UTC+1
Quality: Preview
You can view compatibility for this release, along with important information and what works, and what doesn't at this link: https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/Status.md
Important information
-
-
⚠️ For users who are updating from an earlier release than version 2301.93, please follow the following migration guidance: https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/Update/MigrationGuidanceForSecureBoot.md and please download the latest DriverUpdater release as well: https://github.com/WOA-Project/DriverUpdater/releases/tag/v1.9.0.0 -
⚠️ If you need dual boot, you will have to make your own image. Please follow this guidance: https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/DualBoot.md -
⚠️ You need to backup your original boot image for OTAs to work with Android. When you get an OTA, you will want to revert your boot image for the update to work, or you'll have to use an official OTA recovery package.
Release notes
What's new?
-
General Updates
-
Enables support for the latest Driver Set version
-
Bigger text size for the debug / device information on boot to help with readability (font isn't fixed yet, we know)
-
Fixes an invalid date format in smbios for the UEFI release date that could have broke specific OSes or apps (like msinfo32 or the Surface App in Windows)
Dual Boot Information
Important!: These images currently target the following Android OTA update versions from Microsoft. These images can only be used on a phone that had as latest the following OTA versions from microsoft even if you are currently running a custom android system image. Using these images will work with a custom Android System Image but the device bootloader and firmware must be from the same Microsoft OTA version as shipped from the stock Microsoft Android Updates!
Device Name | Device Variant | Dual Boot Compatible with the following firmware/bootloader version only |
---|---|---|
Surface Duo | United States of America (GEN) | 2022.902.48 |
Surface Duo | United States of America (AT&T) | Currently unsupported, please make your own images using the guide to do so |
Surface Duo | Europe | Currently unsupported, please make your own images using the guide to do so |
Surface Duo 2 | United States of America (mmWave) | 2023.429.67 |
Surface Duo 2 | Europe (5G NR) | Currently unsupported, please make your own images using the guide to do so |
Flashing these images on any other version may brick your phone or render touch unusable! Make backups of your original boot partitions and ALWAYS test before flashing permanently using "fastboot boot image.img"!.
We hope to provide support for AT&T Surface Duo 1 users and European Surface Duo 1 and 2 users with a future update. If your device is one of these, please follow the manual dual boot guide on https://github.com/WOA-Project/SurfaceDuo-Guides.
If you do not currently run above firmware versions, please also follow https://github.com/WOA-Project/SurfaceDuo-Guides.
For more information on dual boot, manual steps on how to craft such image file, and how to flash it, and use it, please visit https://github.com/WOA-Project/SurfaceDuo-Guides.
We do not recommend inexperienced users without advanced knowledge of IT/Command prompts to do this ever. You may find it very hard and mess up your device easily if you do it wrong. Also important to note Android OTAs will not work anymore with a custom boot.img flashed onto the device and you will need to reflash your original backup for them to work or else, you'll be forced to recover with an OTA zip package from https://aka.ms/sri if one is even available for your current version or higher.
Some examples about what above warning means for you when running custom operating systems on your surface duo and if you are willing to run dual boot images
To clarify above bullet point
If for example you flashed the Pixel Experience Android 13 Android System Image on your Surface Duo, and previously you were running Microsoft Stock Android OTA version 2022.123.45, your device firmware and bootloader are still version 2022.123.45 and will not be compatible with these images targeting 2022.902.48
In another example, you flashed the Pixel Experience Android 13 Android System Image on your Surface Duo, and previously you were running Microsoft Stock Android OTA version 2022.902.48, your device firmware and bootloader are still version 2022.902.48 and you are compatible with these images.
You are currently running stock microsoft android version 2022.902.48; you are compatible
You are currently not running stock microsoft android version 2022.902.48; you are not compatible
Hey wow, that's a lot of images right here! Which one do I even download?
Ok so we're going to have a proper guide and documentation on the guide repository at one point, but for now please follow this guidance without thinking too much about it.
-
I am booting Windows 10X on my device, please use the secure boot disabled variants
-
I am booting Windows 10 build 18363 or lower on my device, please use the secure boot disabled variants and make sure testsigning is enabled in BCD on your ESP partition (Currently there's a bug with the SSDE driver requiring SB to be off on these older builds, sorry!)
-
I am booting a version of Windows higher than build 18363 (the latest Windows 10 feature update, Windows 11, Windows 11 Version 22H2 etc..), use the normal variants (ie the ones that do not say "SecureBoot disabled" in their file names)
-
I am running Arch Linux, ok use SB off and please stop saying you use arch linux, we get it
-
I am booting a linux distribution, use the SecureBoot disabled variants
-
The dual boot images and FD files are described in the dual boot section above, if you're following the install guide and not doing dual boot for now, use the normal UEFI zips for your model!
Bug reporting
This release is a Preview release. Bug exists and may happen. If you notice a bug not present in the following bug list, please report them on our Telegram Group.
Seems Faster(TM)
-- The DuoWoA authors