-
Notifications
You must be signed in to change notification settings - Fork 1
Update using Phone Updater
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.
-
Bootloader Locked (Relocking won't work, flash FFU and start from there if you are Unlocked)
-
Download Production Signed Developer Menu, Flight Signing Enabler Script
- 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 are 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.
Use This RCS Checker Script to tell you if RCS (Rich Communication Services) Feature Pack is installed. There is a possibility that some devices will suffer an IPOverUSB bug or something that prevents device logs being fetched
- Plug device in to PC
- Launch 'RCS_Checker.bat' as Administrator
- Wait for result to print on-screen
The reason RCS Feature Pack causes issues, is because Microsoft.MS_RCS_FEATURE_PACK.MainOS.cab
is merged into Microsoft.mobilecore.prod.mainod.cab
in 10.0.16212 so conflicts will happen the update is processing files to replace.
Make sure to enable Advanced Settings
- Flash original FFU (Update to 10586.107 after, if you are on WP8.1)
- 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/replaceresetphone.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 and Time to 4th August 2016
- Update to 14393.16212 (This is just 14393.1066 but Including RCS Feature Removal Cab)
- After Updating to set date to 2nd June 2017. Enable Developer Mode BEFORE updating to allow installing Apps after.
- Open Phone Updater and connect you Phone
- Then choose to upgrade to build 16212.1000
- Wait for packages to be downloaded and send to your phone
- Continue and the Update should be pushed to the device and install.
- 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.
Make sure to enable Advanced Settings
- Flash original FFU
- Manually update 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/replaceresetphone.efi
with the Production Dev Menu, Back 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
- Open Phone Updater again and connect you Phone
- Then choose to upgrade to build 16212.1000
- Wait for packages to be downloaded and send to your phone
- Continue and the Update should be pushed to the device and install.
- 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.
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.
For a full list of iutool errors, go here
- 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.
- 0x802A0006 = Try with another PC.
- 0x80004005 = E_FAIL: Reboot the phone and try again.
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!
-
Splash Shell - This is what everyone already uses, this is the 'normal'/'default' Start menu for W10M 15254 and below
-
CShell XAML - This is the CShell based on XAML start, it includes a new Action Center, Start Menu interactions etc.
-
CShell Splash - This is based on Splash Shell but includes some small visual differences from CShell XAML, just no extra features.