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/showthread.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.
GoodDayToDie said:
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/showthread.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.
Click to expand...
Click to collapse
I've seen this happening with many people. The only way is reset.
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.
I had almost the same problem getting the error 80070003.
view those two posts if you are interested
post 217
post 218
Thanks, but that's.. mot actually very encouraging. I have the SGH-T899M, and as far as I know we still don't have a leaked ROM from one of those.
I also got the "Your phone couldn't be updated" message. But the code was: 80188308.
Any takers?
Phone's current status:
OS version: 8.0.10532.166 (with the three xml files....)
Firmware revision: 2216.14.01.2
Hardware revision: 3.19.1.0
Radio software: 1621.14.11.2
Radio hardware: 0.0.0.7
Bootloader version: 13.07.12.14
Chip SOC version: 2.0.15
-tdecision10
GoodDayToDie said:
Thanks, but that's.. mot actually very encouraging. I have the SGH-T899M, and as far as I know we still don't have a leaked ROM from one of those.
Click to expand...
Click to collapse
I've been trying to look into what's going on with the error message.
I found the particular error string within DuErrorsUIRes.dll. IDS_DU_ERROR_PREINSTALL_FAILED.
With that said, the only files that use the DuErrorsUIRes.dll are \PROGRAMS\DUACLIENT\DuaClientSettings.dll and \PROGRAMS\DUACLIENT\DuaNotification.exe.
I'm not good AT ALL with ASM, but you can either grab those files from your phone or grab them from the emu and load them into IDA and track it down.
I know that the code is the 6th code in the list that corresponds with the update error text.
Sorry I'm not able to help much, but hopefully this is of SOME value to you.
Thanks, Snickler. That's an approach I hadn't considered. Since the error code just means "Path not found" I was trying to think of paths it might attempt to access which could, for some reason, be missing from my phone... but working from the other end might work better.
Related
So, i'm the guy who has been constantly trying to figure out why my camera all of a sudden died when I did my first ROM flash some time back. I have tried just about everything and it has led me to this point.
If you're wondering what everything is here you go.
1. Tried 3 or 4 different ROMS
2. Reverted back to unrooted RC29
3. Tried different camera software
4. Formatted and repartitioned my SD Card
5. UID repair under Amon's recovery.
Okay, back to my point.
When doing a logcat during an attempt at booting my camera (which always results in an FC) I noticed that the system was attempting to access a directory that wasn't there *dev/msm_camera/control0* after investigating I've found that the directory contains device files that work in conjunction or are part of the hardware driver itself.
Searching further, i found this post on the Android Wiki as to whether or not the Cupcake OS would work on the G1 (before it was released): "Need confirmation: Currently there are a number of closed source drivers that are not included. Someone with access to the source to these drivers will have to compile them with the 2.6.27 kernel that cupcake includes. Chances are that until there is an official OTA release for the G1 that is based on the changes in cupcake it will be very difficult to get it running on the G1/ADP1. These drivers include: The Qualcomm camera driver, frontend HW accel codec, h264, libhgl."
So, what I'm thinking is that i somehow have corrupted my drivers, and, the only way I am going to get them back, is if someone knows how to install them manually, or, if there is way to get back to RC30 or 33 without waiting for the OTA from T-Mobile. I went back to RC29, but, the check for system update option didn't appear in my settings window and after 5hrs I still didn't have the update. Any help with the camera driver install or with getting RC30 or 33. Please Help
thaquestion said:
When doing a logcat during an attempt at booting my camera (which always results in an FC) I noticed that the system was attempting to access a directory that wasn't there *dev/msm_camera/control0* after investigating I've found that the directory contains device files that work in conjunction or are part of the hardware driver itself.
Click to expand...
Click to collapse
I think You have bigger problems then that. Every rom includes drivers, even your RC29. Furthermore, you can rip them out of any rom and copy them into corresponding directory. If your camera doesn't work in multiple roms and after flashing DREAIMG.nbh - then it doesn't work, i.e hardware issue.
Good luck.
If all of the sufficient Camera drivers are present, then why isn't the directory specified recreated upon flashing ? Permissions issue maybe ? I'm just trying to figure it out. Also, when going from a custom ROM to RC29, I get different behavior, the camera doesn't force close, it just hangs on a backlit black screen.
You are missing the point. It was a COINCIDENCE that your camera stopped when you tried a custom rom. The camera circuit itself is FRIED WITHOUT CHANCE OF RECOVERY.
Virtually *ALL* of the DREAM/32B ROMs include the camera drivers appropriate to that device.
If the device files aren't being created, it has NOTHING to do with permissions since those device files are being created by the driver itself, which runs within the KERNEL == full control.
The differing behavior of the camera app with respect to lack of available camera is a result of differences between the two different versions of the camera APP itself and is nothing to get excited about.
The device files are created by the camera driver (kernel) when the camera hardware is initialized. The reason the device files aren't appearing is either because the kernel is unable to detect the presence of the hardware, or the driver is unable to initialize it. This is caused by a HARDWARE FAILURE.
FURTHER, the /dev path is NOT a disk filesystem. It is NOT created by adding files into your root filesystem. It is a VIRTUAL REPRESENTATION OF THE AVAILABLE HARDWARE THAT IS PRESENTED BY THE KERNEL.
Thank you very much, that is explanation I've been looking for all along, time to pack this phone back up and get a new one.
I have the exact described issues here, I have gone through the same tests except I found that my camera does work if I load the JacHeroski2.7.4r2.zip ROM.
So the camera actually functions. Any ideas what else this could be.
I did run a logcat of the Camera Start on the Hero ROM and I do not see any calls to /dev/msm_camera. which still does not exist.
~~~ Problem ~~~
On my Windows 8.1 x64 machine I was finding that when running any of the following HTC RUU (ROM Update Utility) apps for my Sprint HTC One M7_WLS they would start then disappear after accepting the terms:
RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.6_Radio_1.01.20.1225_CNV_CNV_SPCS_4.38_003_release_425282_signed_2.exe (my version - file name matches my phone status exactly)
RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe (newest version)
~~~ Short answer ~~~
check Windows Event Logs (run eventvwr.exe & go to Windows Logs -> Application) to confirm error type (SideBySide, Dependent Assembly Microsoft.VC90, x86)
install "Visual C++ Redistributatble Package (x86)" package from Microsoft (I'm too new to post URLs so try something like microsoft.com/en-us/download/details.aspx?id=29)
try RUU again
~~~ Long answer ~~~
In both cases:
the app would start (sucking up a bunch of disk IO)
the "RUU - InstallShield Wizard" window would eventually show (agonizingly slowly advancing the progress bar)
upon clicking the "accept the terms" option and clicking the Next button, the app would end with no further message (but as far as I can tell the C:\Users\<my user name>\AppData\Local\Temp\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\ folder has been cleaned up)
I tried various fixes suggested by other sites including "Compatibility mode" changes, running as administrator, even disabling driver protection! (That reminds me, I should turn that back on.)
In the end I finally worked on this when it wasn't in the wee hours of the morning and realized that if something was crashing, it should be leaving an Event Log entry.
So, in looking at the Application Events log I found a SideBySide "Dependent Assembly Microsoft.VC90" error on architecture "x86" for version "9.0.21022.8" when running ARUWizard.exe (which must be what InstallShield called after unpacking all the files).
A quick web search for "VC90" told me I was missing a Visual C++ 2008 library and the "x86" architecture told me I needed the x86 (32 bit) version of the library even though (or perhaps BECUASE) I'm running on a 64 bit OS.
Microsoft kindly provided that library for me in their downloads at microsoft.com/en-us/download/details.aspx?id=29 (wow - id=29...how old IS this library?!?).
After installing "Visual C++ 2008 Redistributable Package (x86)" [yes, x86 even though I'm on x64 OS] I WAS able to run the RUU exe past the "accept terms" screen - I didn't even need to reboot!
In the end I was able to succesfully unbrick AND update my phone to the 6.23.651.10 firmware giving me the latest (to-date) version including the "Stagefright" patch AND network improvements.
I have no idea why in this 64 bit world HTC would put out an updater expecting to find a 32 bit library, but hey - at least they provide an awesome tool for those of us idiotic enough to brick our own awesome devices!
Hopefully this helps others who are running into the same issue I did - good luck!
This is great! I had this issue and couldn't figure it out. You win one Internet for today.
Do you mind if I include this information in my RUU guide? I've already submitted it to be included in the FAQ.
coal686 said:
This is great! I had this issue and couldn't figure it out. You win one Internet for today.
Do you mind if I include this information in my RUU guide? I've already submitted it to be included in the FAQ.
Click to expand...
Click to collapse
@coal686 - feel free to include this (in whole or part) wherever you think it will do the most good. Thanks for thinking it's worth repeating!
Thank You
you saved my phone lol
I relocked my bootloader and was like oh crap i forgot the other steps
TheKookieGuy said:
you saved my phone lol
I relocked my bootloader and was like oh crap i forgot the other steps
Click to expand...
Click to collapse
Glad it helped!
[Wow - I didn't realize I've had my HTC One for 2 years now. ]
Hi there,
I have a nearly three year old Lumia 1320 that I have as my daily driver, and have been using the Windows 10 DP since early days. Recently, the W10 release it had was the one that stuffed up SD card storage (and was getting random reboots) so I decided to go back to 8.1 and updated it to the Update 2 release.
So far so good. However, the newest W10 release came out so I decided to give it another go (especially as SD card issue resolved) so ran the appropriate software, it downloaded, and applied the image, then it failed. It said to try again, so I did and then started saying things like I didn't have enough storage. The Storage app wouldn't load, nor would Store, Phone, Messages etc. so tried the recovery tool to reflash it back to stock 8.1
This tool failed during the process and said it couldn't flash the device.
Tried various reset techniques and they all failed to get a good result. The symptom was to get the red NOKIA screen for a split second then it loaded the OS.
Now I'm getting concerned and bring out the big guns! Read the XDA tutorial on Windows Phone flashing, downloaded the tools, installed the unsigned driver, downloaded the appropriate image for my phone and went to flash.
Got to 2% and failed:
Sorry! Your device could not be flashed with the image you selected.
Please correct the following error and try again:
Failed to flash with device error { 0xd, 0x0, 0x0, 0x2, 0x0, 0x0 } : Status: 0x80000008
I looked up this 0xd code on the MS site and the error is this:
0xD While applying the image to disk, a block write operation failed.
So now to the ultimate question - does this mean my phone has a hardware error that prevents flashing, or can anyone suggest a workaround to get past this?
The model is RM-994 - the image is 059V5K2 (Australia/NZ Vodafone)
PC I am flashing with is a Core i7 2600, 8GB, Windows 10 Pro x64 with latest November update.
Any advice much appreciated.
Darren
No one?
Really no replies? Anyone on here know more low-level details or tests I can perform?
Even if someone confirms my suspicions that there is a hardware fault that simply can't be overcome, I can move on.
The phone is still running, alarms work, lock screen works (even updates Bing photo), but no Store, Storage Sense, Messages, plus many others and if I delete apps listed as unavailable, or even current apps, such as Tweetium, they disappear and return after a reboot of the device.
I have even tried remote wipe from the web and the device reboots and goes straight back to where it was.
Regards
Darren
I have a 2011 NordicTrack 1750 with a 7" android tablet that is mechanically just fine. Recently an automatic update must have failed, because now it's stuck in a low level boot loop. Unlike the other threads I've found on the net, none of the iCON applications ever load. I only get to the blue generic android screen and no farther before it eventually reboots.
The symptom is that after the system boots it eventually throws the error "Process System is not responding" and whiter I select force quit or wait, the system eventually reboots.
I have both latest.apk file that I downloaded from a bit.ly link I found in a NordicTrack thread that I assume holds the latest icon application. I also have the $93 USB drive that I purchased from Icon fitness that has the if it-video.tgz and mp10.tgz files. I also have a mini-SD card formatted as FAT32.
I can boot the tablet into safe mode, but it eventually throws that error and then eventually reboots again.
I have been able to get to the Applications and Files menu selection and the iCon Fitness application is completely missing, though I do have the icon fitness keyboard. I think I have the icon application in the latest.apk file.
It seems like I need to do a full factory reset and reinstallation to fix the android problems and then reinstall the icon application. But, I don't know how to do that or if I have the right files for that.
Through various combinations of putting the files I have on the miniSD card and rebooting, I've seen it attempt to update the firmware, but eventually go back into the reboot loop. I also watched it try to verify the checksum of the iCON USB key only to eventually reboot and go back to the loop.
There is a thread that looks promising talking about hacking the elite 9500 pro, but I'm not a developer, so I can't post directly to that thread.
I think the tablet is a Hannstar JMV-7 (from a thread I found on the Net)
From the About screen here are some specifics:
Model: sec_smdkv210
Kernel: 2.6.32.9
Build: sec_smdkv 210-eng 2.2 FRF91 eng.android.20110301.153856 test-keys
Does anyone have an image of such a device that I could just blast onto this thing -- if so how would I do that? Any help figuring out how to get this thing back up and running will be greatly appreciated. All the icon helpline offers to do is sell me a whole new 7" replacement tablet for $1300. Not something I'm thrilled about.
Hi everyone.
I have bricked my phone and I don't know how to fix it. When I turn it on, it shows a green screen with two rectangles (one blue, one red).
Sometimes, after that screen with the rectangles, there is a menu to configure my device, ant it says "welcome to device D188" , and when I choose the language, setting as new phone, it tries to connect to network but it never does. So I'm stuck there.
Before this mess, I made a backup of the oem info with twrp, but I think something went wrong because it seems that this oem info has a one ".bin" archive (that i what I've seen looking in the internet), and my twrp backup is a folder with a lot of files(with .win, .sha2, .in extensions). I have two called oeminfo.emmc (one is .win, one is .sha2).
I've tried creating a dload folder with the update.app file in my micro sdcard, and then try to update but it shows "failed".
I was going to try and flash my phone via ADB but then I realised that I have to extract this update.app and I cannot do it because appears the error: RECOVERY_RAMDIS.img: Invlid header crc - Expected: 36587 Got: 6910.
PD: all this comes because I have the Huawei P10 chinese version, and Android Pay wasn't working in Europe (I had some problems adding my card). I thought that was a problem of the chinese ROM in Europe (because when I was in China, I dind't have that problem). So, what I did is rebrand my phone, but Android was still not working (this time because android pay detected a custom rom), and anyway, I didn't like it because the update system option disappeared, in system was a lot of information that wasn't about my phone, that it was wrong (things as processor, ram, etc.). And here is the crazy thing, I went to TWRP, and I restored, when I only had a backup of OEM, system and something else...
I think my phone is now usless and canoot be fixed, but I had to try posting this, just in case someone can help me.
Thanks.