The solution of the second generation WP upgrade FCU error 0x80070273

Time:2019-12-2

As we all know, when Microsoft released windows 10 mobile, it abandoned a large number of Second Generation Windows Phone models, the most representative of which is Nokia lumia X2X series. Later, a god released a method to upgrade windows 10 mobile directly by pushing it to a mobile phone with an offline package, so that the unsupported old model can be upgraded to version 1511 through offline push, and then it can easily modify the device that the model camouflage can upgrade, and continue to get the annual update version 1607 and the creator update version 1703.

However, after some second-generation devices are upgraded to build 15063.297 of 1703 in this way, and then try to get the creator to update the autumn version 1709, the system will continue to report an error 0x80070273, which can not be updated, and the modification of the model, the addition of preview and the reset of the mobile phone can not be solved. This problem occurs because an oeminput.xml file used to describe hardware platform, language and other related information in the system is inherently incomplete, or because of some reasons, it is damaged, resulting in the subsequent upgrade unable to read the required information. Under normal circumstances, this error will only occur on some specific second-generation models with a 100% recurrence probability (congenital incompleteness), and also on other windows 10 mobile devices with a certain probability (it will be destroyed the day after tomorrow, and the solution is the same in theory, so you can take a reference).

▲ 0x80070273 error prompt when the second generation machine tries to upgrade FCU

All the existing solutions on the Internet are to swipe back to Windows Phone 8.1 and try to upgrade, but this solution is very random, not necessarily successful, and time-consuming. For those users who still encounter problems in win10m and do not want to swipe back to wp8.1, the author here provides you with a different solution. The advantage of this solution is that it does not need to roll back the system and can operate under the current win10m version.

Before you start, it’s a common saying: all operations on the system are risky, so please be careful. Remember that if you don’t operate properly, you may encounter problems such as unable to start, need to hard reset or even re brush the system, so as to lose all data. Therefore, please back up important data before you operate.

Install interop tools (RC): I won’t go into details here (I think if you can upgrade to creators update on a second-generation model, you should install it or have it already installed).

Unlock the access right of the complete file system: open interop tools (RC), select “this device”, click “three” in the upper left corner to expand the hamburger menu, find “interop unlock”, open the “full filesystem access” switch (if one time is unsuccessful, try several times more), and then restart the phone.

▲ use interop tools to unlock full file system access

Tip: this process is irreversible. That is to say, after you successfully unlock the full file system access rights, the switch cannot be closed again in interop tools. If you want to find common folders (documents, photos, etc.) that previously existed in the root directory, go to phone \ data \ users \ public. If you can’t stand this, please reset your phone after completing the next steps and installing all the updates, and then it will return to normal.

Connect your mobile phone to a computer with USB data cable (use windows 10 for demonstration here, if you use Linux or Mac OS, make sure you can access and modify the data in the MTP device): open your device, enter the phone drive, and you will see all the system directories. Please be careful not to delete or modify any files without understanding, otherwise you may damage the operating system of the phone.

Enter phone \ windows \ imageupdate, find the oeminput.xml file of the current version of the original machine, copy it to a place you can find on the computer, rename and add a prefix or suffix to mark it (for example, if my machine is lumia 520t, mark it as oeminput.xml).

▲ location of oeminput.xml in the mobile phone system directory

Find the oeminput.xml file you just copied to your computer, right-click “Edit” to open it with “NOTEPAD”, and then put it aside for backup (you can also use Notepad + + and other more code friendly editing tools; if you use Linux or MacOS, make sure you have the same software installed).

The oeminput.xml file copied from Nokia lumia 520t has only two lines of code

Visit Microsoft’s technical documentation page,

The website is as follows

:https://docs.microsoft.com/en-us/previous-versions/windows/hardware/flashing/dn756630(v=vs.85)

In the open web page, check the directory tree on the left, make sure that the topic “build a mobile image using imggen. CMD” is currently open, and then scroll down to the title “oeminput file example” (you can press Ctrl + F and search for the keyword “productionoeminput. XML”, which can be found in the second place where the keyword appears). Click the top right of the lower code pane The copy button in the corner copies the contents of the sample file.

▲ copy the complete code of oeminput.xml sample file from Microsoft’s technical documents

Open Notepad (or create a new text document) and paste in the code you just copied.

▲ the oeminput.xml file we created and the location to be modified

1) change “{processor {name}” to the SOC model of your mobile phone in “{processor {name}”. You can find a string of numbers (some models may have letter suffixes) in “Settings” – “system” – “about” – “device information” – “SOC chip version” of your mobile phone. Adding the letter “QC” before these numbers (and letter suffixes) is the one to be filled here For example, if Nokia lumia 520t is used by the author, qc8827 should be filled in here; if lumia 920 (non state bank) / 925 / 1020, qc8960 should be filled in, and if lumia 920 (State Bank), qc8260a should be filled in.

2) change “480×800” to the screen resolution of your mobile phone at “480×800”. You can find it in “Settings” – “system” – “about” – “device information” – “screen resolution” of your mobile phone (for example, the screen of my mobile phone is exactly this resolution, so it doesn’t need to be modified; the lumia 920 / 925 / 1020 needs to be changed to 768×1280, and so on for other models).

▲ find the data needed to modify the code in “equipment information”

3) at all “< language > en US < / language >”, change “en US” to “zh CN” (or your main language But I think the readers of this article are all Chinese, right

4) at “< bootlocale > en US < / bootlocale > and” < bootuilanguage > en US < / bootuilanguage > “, change” en US “to the data in your original machine file (if you don’t have these two lines of code in your original machine file, you can also keep the same).

▲ contents of the modified self-made full version of oeminput.xml file

Save the modified code document as “oeminput. XML”: select “file” – “save as”, select “save type” as “all files”, fill in “oeminput. XML” in “file name” (pay attention to case), save to the place you can find (if you have directly created a new text document before, please directly save the file and close “NOTEPAD”, and then“ Change “new text document. TXT” to “oeminput. XML”. Be sure to modify the extension).

▲ save the text document as oeminput.xml file

▲ comparison between oeminput.xml file of self-made complete version and incomplete version of original machine

Connect the target device with full file system access unlocked in the first step to the computer, open the MTP device, and navigate to the directory phone \ windows \ imageupdate.

Copy and paste the full version of oeminput.xml you just made into this directory, and then choose to replace it.

Open the replaced oeminput.xml to check its contents and confirm that the replacement has been completed correctly.

Unplug the data cable, restart the phone, make sure that the model has been changed and pretended to be an upgrade model, and then recheck the update in the phone settings, you should be able to get the fall creators update update correctly.

This file has been successfully repaired by us. Even if it is reset, it will not be restored. That is to say, it can be upgraded successfully in the future. It can be described as once and for all. Have fun!

If the download of the update is completed and the installation is in progress, an error will be reported and the message “we can’t install the update because there is a problem with the date and time information on your device” will be prompted. This may be because the certificate of Microsoft Server has expired again (just like the wp8.1 app store a few days ago), please temporarily change the time zone of the mobile phone to the eastern time of the United States and the date to February 16, 2018 (the time does not need to be modified) can be updated smoothly, and can be changed back after the update is completed.

Well, that’s the end of the tutorial. Remember: wper never gives up. Good luck!

Tips:

IV. replace the original version with the self-made full version oeminput.xml

Now modify the code you just pasted:

III. make a complete oeminput.xml to replace the incomplete version of the original machine

II. Extract and backup oeminput.xml file of the original computer

I. use interop tools to enable MTP’s full file system access rights

are you ready? OK, let’s start!