Skip to content

Update using Universal Updater

Empyreal96 edited this page Sep 4, 2021 · 30 revisions

Windows 10 Mobile Build 16212 Upgrade Guide (Universal Updater).

Currently work in progress/not complete. Updates will be applied frequently to this guide

Very important note to acknowledge: This is still PROOF OF CONCEPT, You will encounter some bugs/issues/lack of features! this is not a Daily Driver build!

I will not be responsible for any damage done to devices, as with all test builds there is a risk.

The 16212 update cabs are hosted by me on Dropbox/Mega, if you have issues with dead links let me know so I can fix the links and updater lists

Please read Known Issues (WIP) before continuing.

Tools needed:

Notes:

  • I recommend copying all cabs in your chosen pack into a single folder. i.e: copy the contents of "Merged" "mobilecore" and "retail" into a single folder.
  • I recommend removing the 3 Platform Manifest cabs mentioned below from your cab pack for ease.
  • A Hard reset is required to make Microsoft Edge work, but breaks Action Center and Developer Mode being active
  • Upgrading to 16212 with CShell XAML will cause any applications previously installed to not show on the Start menu. Only 'New' apps show
  • Microsoft Store does NOT work, we've tried several versions and no joy
  • Developer Mode cannot be toggled through settings
  • Text artifacts will occur on non en-US locale
  • No Silverlight (XAP) support
  • Use Device Portal to install an app like Interop, W10M Group App or UWP Package Installer to make installing apps easier
  • There is no Notification Gesture. tap the Notification bar to open.
  • If you are using Windows 8/8.1 and not using the Flight Enabler Script, you need this bcdedit.exe from Windows 10
  • Root Access is not yet supported
  • DO NOT UNLOCK BOOTLOADER ONCE UPGRADED TO 16212, YOU WILL GET BSOD.

Non-x50 Device Guide:

  • Flash original FFU
  • Upgrade to 14393.1066+
  • Interop Unlock your device and enable System access over MTP USB or deploy Storage Explorer XAP if you cannot use MTP
  • Navigate to C:\EFIESP\Windows\System32\Boot on the device and copy/replace resetphone.efi with the Production Dev Menu , backing up the original file.
  • Shut Down the Device, when the manufacturer logo is shown, keep pressing Volume - button until Developer menu appears, then use Power button to select USB Mass Storage Mode
  • Extract and run as Administrator Flight Signing Enabler Script
  • Set date to 2nd June 2017. Enable Developer Mode BEFORE updating to allow installing Apps after.
  • Open Universal Updater and connect you Phone
  • Then choose to Manually select files. Find where you keep 16212 cabs
  • Wait for packages to filter to the Updater
  • Before sending update to the device: Copy the Shell cabs to the Universal Updater\device\Packages directory for your phone. (More on this below).
  • Before sending update to the device: Make sure these 3 are NOT going to be pushed to the phone (read notes for a tip)
    • Microsoft.MICROSOFTPHONEFM.PlatformManifest.EFIESP.cab Microsoft.MICROSOFTPHONEFM.PlatformManifest.MainOS.cab Microsoft.MICROSOFTPHONEFM.PlatformManifest.UpdateOS.cab
  • Continue and the Update should be pushed to the device and install.

Suggested Post-Install Actions/Notes

  • Interop Unlock is recommended, Interop Tools Beta v1.9 works atm
  • If the Production Developer Menu didn't persist after Update, Interop Unlock and re-copy it as above.
  • If you need to enable Developer Mode and have access to Mass Storage Mode, Use the 16212_Patches Script to manually enable Developer Mode
  • Use Device Portal over USB/Local Wifi to Install Interop Tools or W10M Group App to allow App Installation on device. Windows App Installer doesn't show/work.
  • After connecting to the Internet, some Apps will still update/install. This can take a while so let the phone complete app installation for better results.

x50 Device Guide:

  • Flash original FFU
  • Interop Unlock your device and enable System access over MTP USB or deploy Storage Explorer XAP.
  • Navigate to C:\EFIESP\Windows\System32\Boot on the device and copy/replace resetphone.efi with the Production Dev Menu
  • Shut Down the Device, when the manufacturer logo is shown, keep pressing Volume - button until Developer menu appears, then use Power button to select USB Mass Storage Mode
  • Extract and run as Administrator Flight Signing Enabler Script
  • Set Date to 4th August 2016
  • Manually update to 14393.1066 including the RCS Removal cab when you push the update.. make sure to remove Microsoft.MS_RCS_FEATURE_PACK.MainOS.cab if it's already in your 14393 cab folder before deploying. Replace if it asks.
  • After Updating to set date to 2nd June 2017. Enable Developer Mode BEFORE updating to allow installing Apps after.
  • Open Universal Updater and connect you Phone
  • Then choose to Manually select files. Find where you keep 16212 cabs
  • Wait for packages to filter to the Updater
  • Before sending update to the device: Copy the Shell cabs to the Phone Updater/Universal Updater Packages directory for your phone. (More on this below).
  • Before sending update to the device: Make sure these 3 are NOT going to be pushed to the phone
    • Microsoft.MICROSOFTPHONEFM.PlatformManifest.EFIESP.cab Microsoft.MICROSOFTPHONEFM.PlatformManifest.MainOS.cab Microsoft.MICROSOFTPHONEFM.PlatformManifest.UpdateOS.cab
  • Continue and the Update should be pushed to the device and install.

Suggested Post-Install Actions/Notes

  • Interop Unlock is recommended, Interop Tools Beta v1.9 works atm
  • If the Production Developer Menu didn't persist after Update, Interop Unlock and re-copy it as above.
  • If you need to enable Developer Mode and have access to Mass Storage Mode, Use the 16212_Patches Script to manually enable Developer Mode
  • Use Device Portal over USB/Local Wifi to Install Interop Tools or W10M Group App to allow App Installation on device. Windows App Installer doesn't show/work.
  • After connecting to the Internet, some Apps will still update/install. This can take a while so let the phone complete app installation for better results.

Errors:

If you receive error Preparing the update in the phone, send your "ImgUpd*.log" files:

  • Open iutool's folder in Admin Command Prompt
  • getdulogs -o .\DevLogs.cab && .\DevLogs.cab
  • Explorer will open the log cab, extract ImgUpd*.log(s), then send here.
  • If you boot to a black screen (bootloop) you may have left the Platform Manifests, restore with WPInternals.

Update Errors

  • 0x800b010a = Signature Verification Issue: enable flight signing
  • 0x800b0101 = Incorrect Date and Time: Change date
  • 0x80188306 = File Collision Detected or Files Not Found: Include the RCS cab when updating to 14393 and/or Make sure cab list is complete and matches InstalledPackages.csv.

Shell Cabs:

We can choose from 3 Packages: CShell XAML, CShell Splash, and Splash Shell. It's down to you what you want, just don't apply all 3 shells! These are located in the "Merged" folder of the Downloaded Pack

  • Splash Shell - This is what everyone already uses, this is the 'normal'/'default' Start menu for W10M 15254 and below

    Microsoft.MS_SPLASHSHELL.MainOS.cab
    
  • CShell XAML - This is the CShell based on XAML start, it includes a new Action Center, Start Menu interactions etc.

    Microsoft.MS_CSHELL.MainOS.cab
    Microsoft.MS_CSHELL.MainOS_Lang_en-US.cab
    Microsoft.MS_CSHELLXAMLSTART.MainOS.cab
    
  • CShell Splash - This is based on Splash Shell but includes some small visual differences from CShell XAML, just no extra features.

    Microsoft.MS_CSHELL.MainOS.cab
    Microsoft.MS_CSHELL.MainOS_Lang_en-US.cab
    Microsoft.MS_CSHELLSPLASHSTART.MainOS.cab
    

FAQ

Q) How to enable Developer Mode?

A) Use the 16212_Patches Script with the Device in Mass Storage Mode

Q) Microsoft Edge doesn't work, how to fix?

A) For now we have to Hard Reset to fix Edge, but you will loose Action Center (See FAQ)

Q) My Action Center Toggle are missing after Hard Reset, What can I do?

A) No much at the moment, we are working on how to restore the toggles

Q) Does this build allow Whatsapp etc?

A) No.