Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,737,354 Members 41,674 Now Online
XDA Developers Android and Mobile Development Forum

Trouble updating to 8.1 (error 80070003)

Tip us?
 
GoodDayToDie
Old
#1  
Recognized Developer - OP
Thanks Meter 2645
Posts: 5,539
Join Date: Jan 2011
Location: Seattle
Default Trouble updating to 8.1 (error 80070003)

TL;DR: I need update logs or an idea what path might be missing that breaks the 8.1 update!

Hi all, strange for me to be asking for help here but it happens...

I've finally gotten my ATIV S (SGH-T899M) into a state where I'm willing to upgrade it to WP8.1. However, I am unable to do so. I've been able to install a few updates, but the actual 8.1 update won't install. The error I get (under the "Update status" line in Settings -> Phone Update: "The update was downloaded, but couldn't be opened. (80070003)"
The error code is an HRESULT or NTSTATUS wrapper around Win32 error code 3, which is ERROR_PATH_NOT_FOUND. Note that this is distinct from FILE_NOT_FOUND (2); you only get error 3 when a part of the path to a given file (or directory) is missing. I've searched online for any information about this error with regards to updates, to no avail. It does sometimes happen with Windows Updates on PC, but the instructions for resolving that aren't easily mappable to the phone.

Phone's current status:
OS version: 8.0.10532.166 (this is the pre-8.1 version; as I said, I did get some updates)
Firmware revision: 2212.13.11.2 (this is the Samsung GDR 3 version, except modified to not overwrite WP8Diag.xap or FCRouter, etc.; see http://forum.xda-developers.com/show....php?t=2537241)
Hardware revision: 15.3.1.0
Radio software: 2212.13.11.2
Radio hardware: 0.0.0.0
Bootloader version: 13.08.14.16
Chip SOC version: 1.5.32

Phone was originally branded for Telus Mobility in Canada, and still has signs of that in DeviceTargetingInfo (language is 0809 instead of 0409, for example, and MobileOperatorName is LUS-CA). It was factory SIM-unlocked and brand new when I got it. It is developer-unlocked, interop-unlocked, capability-unlocked, and has been subjected to numerous additional hacks; I've reversed a few that I can think of which could possibly impact the update (like messing with files in the System32 directory) but I probably missed a few of those.

Here's what happens when I try to update:
If Preview For Developers is not enabled, it does "Checking for updates" then says I'm up to date.
If PFD is enabled, it checks for updates and then, if I'm on WiFi, downloads the update CABs.
It then enters the "Preparing to install" step. This is very slow in some places, stalling for minutes at a time at some percentages, but eventually reaches 97%.
It then stops the update process with the error message in bold above.
It does NOT ever tell me what the update is.
It does NOT reboot, or even offer to reboot, at any point.
The "Check for updates" button re-appears and can be used to start the process over again.

So... any ideas or suggestions? I'd prefer to avoid a hard-reset if possible, simply because of the amount of time it would take to restore the phone to the condition I state I want it in, but I'll do one if nothing else works. Things I'm particularly looking for, in descending order:
1) Anybody else who has experienced this problem and found a solution (and what that solution is).
2) Any log files I could check to see what it was trying to do when the error occurred (ideally with the path that caused the error).
3) Anybody else who has encountered this problem but not gotten past it; we can compare what changes we made to our phones.
4) Anybody else who has a reasonably similarly-modified phone but has not experienced this error and was able to install 8.1 (so we can compare what we did to our phones, and I can possibly crib files off you).

Hope somebody can help! Thanks.
Win8/Windows RT projects:
List of desktop apps for hacked RT devices

WP8 projects:
Native Access WebServer and Libraries
WP8 Interop Unlocks
Storage Cleanup tool

WP7 projects:
XapHandler, Root Webserver, OEM Marketplace XAPs, Bookmarklets collection (Find On Page), Interop-unlock hacks.


Do not private message me with questions that should have been posted on the forum! Not only are you wasting your time - I'm not going to bother writing an answer to such a question for only one person - but I will probably block you from PMing me in the future as well.
 
vihsalvatore
Old
#2  
Junior Member
Thanks Meter 1
Posts: 2
Join Date: Jun 2014
Quote:
Originally Posted by GoodDayToDie View Post
TL;DR: I need update logs or an idea what path might be missing that breaks the 8.1 update!

Hi all, strange for me to be asking for help here but it happens...

I've finally gotten my ATIV S (SGH-T899M) into a state where I'm willing to upgrade it to WP8.1. However, I am unable to do so. I've been able to install a few updates, but the actual 8.1 update won't install. The error I get (under the "Update status" line in Settings -> Phone Update: "The update was downloaded, but couldn't be opened. (80070003)"
The error code is an HRESULT or NTSTATUS wrapper around Win32 error code 3, which is ERROR_PATH_NOT_FOUND. Note that this is distinct from FILE_NOT_FOUND (2); you only get error 3 when a part of the path to a given file (or directory) is missing. I've searched online for any information about this error with regards to updates, to no avail. It does sometimes happen with Windows Updates on PC, but the instructions for resolving that aren't easily mappable to the phone.

Phone's current status:
OS version: 8.0.10532.166 (this is the pre-8.1 version; as I said, I did get some updates)
Firmware revision: 2212.13.11.2 (this is the Samsung GDR 3 version, except modified to not overwrite WP8Diag.xap or FCRouter, etc.; see http://forum.xda-developers.com/show....php?t=2537241)
Hardware revision: 15.3.1.0
Radio software: 2212.13.11.2
Radio hardware: 0.0.0.0
Bootloader version: 13.08.14.16
Chip SOC version: 1.5.32

Phone was originally branded for Telus Mobility in Canada, and still has signs of that in DeviceTargetingInfo (language is 0809 instead of 0409, for example, and MobileOperatorName is LUS-CA). It was factory SIM-unlocked and brand new when I got it. It is developer-unlocked, interop-unlocked, capability-unlocked, and has been subjected to numerous additional hacks; I've reversed a few that I can think of which could possibly impact the update (like messing with files in the System32 directory) but I probably missed a few of those.

Here's what happens when I try to update:
If Preview For Developers is not enabled, it does "Checking for updates" then says I'm up to date.
If PFD is enabled, it checks for updates and then, if I'm on WiFi, downloads the update CABs.
It then enters the "Preparing to install" step. This is very slow in some places, stalling for minutes at a time at some percentages, but eventually reaches 97%.
It then stops the update process with the error message in bold above.
It does NOT ever tell me what the update is.
It does NOT reboot, or even offer to reboot, at any point.
The "Check for updates" button re-appears and can be used to start the process over again.

So... any ideas or suggestions? I'd prefer to avoid a hard-reset if possible, simply because of the amount of time it would take to restore the phone to the condition I state I want it in, but I'll do one if nothing else works. Things I'm particularly looking for, in descending order:
1) Anybody else who has experienced this problem and found a solution (and what that solution is).
2) Any log files I could check to see what it was trying to do when the error occurred (ideally with the path that caused the error).
3) Anybody else who has encountered this problem but not gotten past it; we can compare what changes we made to our phones.
4) Anybody else who has a reasonably similarly-modified phone but has not experienced this error and was able to install 8.1 (so we can compare what we did to our phones, and I can possibly crib files off you).

Hope somebody can help! Thanks.
I've seen this happening with many people. The only way is reset.
The Following User Says Thank You to vihsalvatore For This Useful Post: [ Click to Expand ]
 
GoodDayToDie
Old
#3  
Recognized Developer - OP
Thanks Meter 2645
Posts: 5,539
Join Date: Jan 2011
Location: Seattle
Huh. I didn't see any news about it, at all, when I searched. Lots of stories about *other* update errors for WP8.1. Lots of stories about this particular error when installing Windows updates on normal Windows (none of which, sadly, had helpful suggestions for the phone). When you say "many people" do you mean in general, or just lots of people with interop-unlocked ATIVs?

I would really like it if the source of the problem could be identified and fixed, but Microsoft seems unlikely to be helpful here. It's probably a really simple problem - a config file that needs to be edited, a folder created (we can do that), a registry value changed, something like that - but oh well. I can back up my app data, and my SMS are backed up automatically, so I suppose in the big scheme of things there's no reason *not* to do this... I just don't like it, and consider it a waste of time.

On the other hand, if I have to hard reset anyhow, I might take the opportunity to install a custom CSC. I normally try to stick as close to stock ROM as possible - making only runtime changes, basically - but it's quite possible that some of the changes I've made will *already* persist after reboot (part of why I'm hesitant to blindly hard-reset; what if it doesn't fix anything and is just a waste of time?). It would be nice to get some of the feature perks of the custom CSC though.
Win8/Windows RT projects:
List of desktop apps for hacked RT devices

WP8 projects:
Native Access WebServer and Libraries
WP8 Interop Unlocks
Storage Cleanup tool

WP7 projects:
XapHandler, Root Webserver, OEM Marketplace XAPs, Bookmarklets collection (Find On Page), Interop-unlock hacks.


Do not private message me with questions that should have been posted on the forum! Not only are you wasting your time - I'm not going to bother writing an answer to such a question for only one person - but I will probably block you from PMing me in the future as well.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes