Upgrading caused a low memory condition - 8125, K-JAM, P4300, MDA Vario Software Upgrading

I have a generic Wizard that I upgraded using the T-Mobile update on thier website to flash it to 2.26. I have a T-Mobile SIM.
I flashed my T-Mobile MDA and it works fine. However when I did it to my non-branded Wizard (which is the Cingular form factor) it causes a curious problem. Everything appears to be working fine but for some reason in the background it continually is building log files in the root directory that over about a week causes it to have a low memory problem.
The files that are being generated are XPanelLog11.pco; XPanelLog2.1.pco; etc.
Also DbgToStorageLog1.txt; DBgToStorageLog2.txt; etc
I opened up one of these text files and it is has things like this;
PHP:
Windows CE Kernel for ARM (Thumb Enabled) Built on Oct 25 2005 at 17:27:50
ProcessorType=0926 Revision=3
sp_abt=ffff1000 sp_irq=ffff0800 sp_undef=ffffc800 OEMAddressTable = 8c101084
ModemUartPath from 0 to 0
+InitHtcHookUserDbgTrap
-InitHtcHookUserDbgTrap
Sp=ffffc7cc
CreateProcess(fbb4002,NK.EXE,8c100000)
LoadDLL(ffffffff,8fbb47e0,coredll.dll,03f60000)
LoadDLL(ffffffff,8fbb4524,osaxst0.dll,8c159000)
LoadDLL(ffffffff,8fbb42cc,hd.dll,8c155000)
HtcCeLog: Register logging functions with kernel success
CreateProcess(fba4c1e,filesys.exe,04000000)
LoadDLL(fba4c1e,8fbb47e0,coredll.dll,03f60000)
LoadDLL(ffffffff,8fba4f04,certmod.dll,03f50000)
LoadDLL(fba4c1e,8fba4f04,certmod.dll,03f50000)
LoadDLL(ffffffff,8fba7efc,fsdmgr.dll,03f30000)
LoadDLL(fba4c1e,8fba7efc,fsdmgr.dll,03f30000)
LoadDLL(ffffffff,8fb81ddc,trueffs.dll,03d80000)
LoadDLL(fba4c1e,8fb81ddc,trueffs.dll,03d80000)
MMMAP - gDrvGlobBase = 1c0000
Is there anyway for me to correct this? Do I need to reflash with something else or change a registry setting to get these log files to stop?

Related

Update Rom Radio

Hi, I have an hw6515 with a corrupted original Rom (0.92) and that it is imposible to upgrade via USB using the Huu rom upgrade application from HP. Then I´ve tried many things and discover that I can upgrade an entire image. I tried a hw6515c image, bigrom, Ipaqdisk from file farmer and everything works. Except my radio rom that is not recognized when I use the HP asset application.
So, how can I upgrade the original NBF files from HP not using activesync connection and not using HUU rom update utility from HP? How can I use the Romupdate utility (mtty) to update only Rom radio OS and Radio File system? Is there any command in DOS, Windows or Linux. How can I map the entire rom?
this cant be done with a corrupted rom i think the only thing can you do is reboot the device in bootloader mode and try it
enjoy it!!!!
***nEuEzIeL***
I have the same problem.
After flash my 6515d to change from ENG to ITA, the update is go bad.
so I have reset it in engineering mode ( pressed powerON - camera - Joystic -Soft-Reset ) and reflashed with sp33246 downloaded from HP.
When reflash the device, it stop at 0,1% at upgrade Radio Stack.
I have removed radioOS.nbf and radioFS.nbf writing ";" at the beginning of them line in the file hpRUU.ini and reflashed the device.
This time the flashing is go on and my device is good started but the part of radio is off.
I have seen in many forum and the problem seems being that in the servicepack downloaded from HP the files radio are only upgrade and not working if in the device there isn't already a software radio.
So the only way for reset completely the device is to restore an backup,
but I don't have any backup of my device.
Can anyone share the backup of its device?
Tank...
ok!!
tk3w said:
I have the same problem.
After flash my 6515d to change from ENG to ITA, the update is go bad.
so I have reset it in engineering mode ( pressed powerON - camera - Joystic -Soft-Reset ) and reflashed with sp33246 downloaded from HP.
When reflash the device, it stop at 0,1% at upgrade Radio Stack.
I have removed radioOS.nbf and radioFS.nbf writing ";" at the beginning of them line in the file hpRUU.ini and reflashed the device.
This time the flashing is go on and my device is good started but the part of radio is off.
I have seen in many forum and the problem seems being that in the servicepack downloaded from HP the files radio are only upgrade and not working if in the device there isn't already a software radio.
So the only way for reset completely the device is to restore an backup,
but I don't have any backup of my device.
Can anyone share the backup of its device?
Tank...
Click to expand...
Click to collapse
Tell me how can you change your language ??(becouse i know this cant be done )
try it with th same language of your device
enjoy it
***nEuEzIeL***
Yes, the change of language dont can be done.
but I did not know it and I have forced the flashing with an crakked program.
The flashing is go bad and now I have no image of old device.
The reflashing of the rom with upgrade of HP fail at %1 and the only way for to return at the old operative system is the restore the OS from the SD.
Please, can you share a backup of 6515d (english ) ?
Tank.
ups
no i dont have the 6515d i have the 6515b and your device are bricked you need to send to hp for a warranty or mailme to [email protected] and the topic need 6515 im from mexico and you can send me your device if you want but your device are briked
I have the same problem, i need help because i investigate a lot but don't know what to do now exactly...If you go Hp, they ask you for 300$ motherboard.
I Everytime stucked at 0,1% : I Try a lot of HPRompackage,
Modified rom, modified installer Hpruu, etc..
The Rom dump via d2s : doesn't include the gsm parts
We need arguments and specify a adress range :
if you want i have a radiorom dump of the
Adress : d2s 60000000 800000,
and the radiobeetlespatch.
But i don't know exactly how to investigate more the good adress.
I think we have to delete and rewrite manually good adress range.
I can find you a lot of rominstall to change language,
( not the problem just modifications in nbf files with winhex)
I investigate a lot the bootloader, have password pass 1, etc...
Try to listen with Usbmonitor, look dump of ram memory with winhex,
etc... So a lot of way to investigate and a lot of solutions for other device very close to our 6515.
So I send to everybody ask me a complete packages of the tools & rom who can help, and my extended info.
dim920 said:
I have the same problem, i need help because i investigate a lot but don't know what to do now exactly...If you go Hp, they ask you for 300$ motherboard.
I Everytime stucked at 0,1% : I Try a lot of HPRompackage,
Modified rom, modified installer Hpruu, etc..
The Rom dump via d2s : doesn't include the gsm parts
We need arguments and specify a adress range :
if you want i have a radiorom dump of the
Adress : d2s 60000000 800000,
and the radiobeetlespatch.
But i don't know exactly how to investigate more the good adress.
I think we have to delete and rewrite manually good adress range.
I can find you a lot of rominstall to change language,
( not the problem just modifications in nbf files with winhex)
I investigate a lot the bootloader, have password pass 1, etc...
Try to listen with Usbmonitor, look dump of ram memory with winhex,
etc... So a lot of way to investigate and a lot of solutions for other device very close to our 6515.
So I send to everybody ask me a complete packages of the tools & rom who can help, and my extended info.
Click to expand...
Click to collapse
Is better Honestly buy a new Morher Card or a New Device SEll That in a Spare pices
Hi, dim920.
I would be pleasing you of to receive material and informations about.
My email is [email protected] but you can share your package of tools also
elsewhere on the web.
Tank
Radio package 6515
For download my package with :
- Radiodump (adress 60000000 800000)
- Special hpruu for incorrect device sku or other error messages
- Beetles Radio Patch
- Bigrom
- Ntrw to write to sd
- Romupdate & mtty
- usb monitor trial
- winhex trial
- Hx 4700 bootloader to modify the header
- At command guide
go here : http://dl.free.fr/TOErXwWr/package6515rom.rar
THE Bootloader PASSWORD level 0 is : "BOOTLOADER"
the level 1 (pass1) is 0000000000000000 (zero x 16)
I exclude all official Hp rom package,
my device is french and a 6515a.
For change Your phone language,
Download special rom & read here :
http://mobilitytoday.com/forum/showthread.php?t=12231
I post in few moments all an short description of what i do
,what i think and what are the solutions for the same problem
on other device.
I try to regroup all i have for tomorrow night if you want to
speak before and have msn :
[email protected]
Tank you for your share.
I am trying to flash the rom from sd card.
I have downloaded a rom image of 6515 and I must put it in the SD card.
After to backup the PDA over SD with romupdate.exe dowloaded from :
http://www.filefarmer.com/2/dmc8742
with d2s, I have put the card ( SD 512 MB ) into card reader and ran
ntrw ( hw6515_bigrom112.zip in the link above ) for write bigrom112.nb1
into SD, but something does not work!!! My SD is blank.
I have an image of rom : IPAQROM.img and I could also try to mount it on the SD but I know that I have to use IPAQDISK.
I have tried to find it for many days on the web but I have not found it!!!!
I think that the single way for to resolve the problem is to make the flash from the SD card.
Makes to know your news me.
The single way that we have to resolve the problem is to work together.
Excuse for my English
Hi.
- For the problem of Dead Radio, nos gsm, and asset info blank,
A Classic Rom dump doesn't take the radio Gsm part.
- Flashing Bigrom or RomDump of a working device can only help you
to have extended memory on External rom, or to change language.
- When you do d2s, Romupdate format the sd in a special format when writing your rom. After copy backuped rom to your pc and finish by copy the new Rom on Sd via Ntrw. Move the sd from pc to pda, Finish via hard reset (1/Power 2/joystick down 3/Reset stay 5 sec, you see bootloader lightly, unpress in good order
1/ Reset 2/ Others. You see bootloader HP v0.21.
After few seconds "press action buttons to flash"
It's normal that the sd is blank, because it's a special formatted via d2s
for the pda can boot so pda os & os pc ask you if you wat to format.
So you can't see the file writed by ntrw, but she is ready for flash, if you follow steps & the bootloader stuck in bootloader and don't propose to flash, it's a problem of rom compatibility.
- So the D2s command don't take the gsm part.
I think we have to specify the good adress range, it's why
the file radiorom in my package is a rom dump d2s 60000000 800000 of a working device. If i copy back on the working device, he says upgrade radio stack and ok so solution is not too far.
Try it but my device don't wan't to take back this rom, stucked on "calculate checksum" on the pda and nothing never happen. If i do checksum command it's ok, but if i do a checksum 60000000 800000 he stuck too on "cal checksum".
So i think we have to erase manually with erase command & wdata, but really not sure to not brick more the devices but it's how they can solve the problem on other device...
Can't access bootloader menu on my hp 6515
How can I access bootloader menu on my hp ipaq hw 6515?
I tried all combinations POWER + Joystick + Camera + Reset
I only get a screen with message: Serial - hp - v0.21
This was because a ROM update went wrong...
Thx,
shaker308
That screen you see with Serial -HP - v0.21 IS the bootloader screen. You need to then connect the ipaq to a computer and use a terminal software to access the bootloader menu
ok... I didn't know that was the bootloader screen. I'll try what you told me.
Thanks cluurk.
shaker308
iPAQDISK.exe
Can anyone tell me where can I find iPAQDISK.exe.
If you can please send it to my e-mail.
[email protected]
Thnx,
Shaker308
shaker308 said:
Can anyone tell me where can I find iPAQDISK.exe.
If you can please send it to my e-mail.
[email protected]
Thnx,
Shaker308
Click to expand...
Click to collapse
http://blogs.unbolt.net/media/blogs/brinley/iPAQDISK.zip
found it just now.. Trying to play around with a H6365.
ipaq hw6515 dead
hi,
please help restore my device(spanish movistar hp),
it doesn't recognize Radio GSM after upgrading to 1.29sp
Radio presente: Si
Version del firmware:
Version protocolo de la radio:
Version de Cargador de inicializacion:
Version del sistema de archivo de la Radio:
Version GDFS predefinida de la radio:
Numero IMEI:
anything i can do please?
i need radio rom file to restore from sd card

Downgrade from WM6 to WM2003SE activesync problem

i'm really keen to get this issue fixed.. any suggestions would be appreciated.
i have just downgraded from WM6 to WM2003SE (o2 XDA offical rom 1.40 for AUS) and i cannot sync the device anymore.
i have completely set the device back to it's original state, ext rom, main rom, radio rom. the PDA itself works fine, no issues there.
i receive an error when i try to sync with my laptop.. (which it used to sync with when i put WM6 on the device).
the error is - cannot verify the version of activesync on your device, a program such as a firewall may be blocking a port activesync uses to connect to your device, you may need to upgrade to a more recent version or activesync
i have removed activesync, deleted all the registry entries, folders and files relating to activesync that i could find. reinstalled activesync, still no luck.
-> i can get the device to sync with my desktop without any problems (i never used the desktop to sync to it when WM6 was installed)
however all my data is on the laptop.
Any ideas ?
update
here is an extract from the log..
**** ActiveSync (4.5.5096 RETAIL) started, Cmd line: '/onconnect'
10/08/2007 16:07:14.324 Creating new partnership for device 0x0 (Pocket_PC, PocketPC).
10/08/2007 16:07:14.324 Error 0x8000BADD: Failed to get version number from device.
10/08/2007 16:07:15.927 Creating a guest connection for device of type 'PocketPC'
-> i can't get into the screen to clear the storage and hive..
i can get into bootloader.. can't get it to work when i press power, reset, camera and record.. just goes into bootloader.. or the numbers come up on the bottom..
could there be some residual information left behind from the previous install of WM6 ??
how do i set the version no manually ? is this done in the PDA registry ??
I don't remeber having this problem. All you can do it try to downgrade ActiveSync to one of the older versions.

Oracle PushMailClient Install Failure on WM6.1

My work uses Oracle PushMailClient, however I'm unable to install this on any WM6.1 ROM either on the Device or on the Storage Card. Tried a few Dutty flavors, and now L26's latest. No dice. Keep seeing the following in the generated log:
2008/05/08 10:43:13:000 [Thread: 0000000079183310] PIMAPSetup:llMain>>> DLL_PROCESS_ATTACH: [RELEASE] Build at Jun 3 2007 10:38:58 PST.
2008/05/08 10:43:13:000 [Thread: 0000000079183310] CreateToolhelp32Snapshot failed. Error [8] at ..\..\..\src\common\Win32Util.cpp:291
2008/05/08 10:43:13:000 [Thread: 0000000079183310] Formatted Error Message: Not enough storage is available to process this command.
2008/05/08 10:43:13:000 [Thread: 0000000079183310] Unable to kill PIMAPMonitor.
There is PLENTY of space on this Device, and on the Storage Card. I know some folks around here have had no trouble installing this on WM6.0. Do I need to drop back to WM6.0 too? Hope not. Thanks for any pointers.
UPDATE: My mistake, this will not install on the Tilt even at WM6.0. Must be a Tilt (or Kaiser?) specific issue. My coworkers have successfully installed this on Wizards using WM6.0. Some sort of C Interpreter difference? (way above my head, so apologies if that sounds dumb).
G.
You should try to configure your client to use IMAP4 for WM6.x.
There is a link on how to do this (pass Oracle firewall):
http://itsource.oraclecorp.com/owc_wiki/page/show.jz?page=PushMailSmartPhone

[Q] X1i HardSPL Error 262

Hi,
I cannot flash 0.78.OliNex Hard-SPL on my new X1i: The progress bar stays at 0% until the timeout, then Error 262. I tried everything (no sd-card, no sim, hard reset, compability mode etc.), no avail.
My new X1i has the image version 1.05.932.7 (03/24/09), the bootloader reads:
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
The type is AAD-380001-BV.
Radio is 1.14.25.55, protocol 52.65.25.34J, extended protocol 1.0.11809.7229.
Software ID is 1213-6439, version R3AA007, user id 1215-3303, user version R15A, content version PA10.
I noticed that the installed WME 6.1 is modified compared to the old X1. In particular, during my first attempt, a WM6.1 warning message with a red boundary popped up, indicating that proceeding could harm the phone (yes/no). I checked yes, and since then, the message does not come up anymore. Probably the ROM is not in Olis compatibility list, so I looked for unsigned HardSPL, but found only the Image Version 1.00.Diamond, so I did not flash it (probably it would brick my X1i). Any idea would be very much welcomed, I want to get rid of WM6.1 and flash WM6.5.3.
Thanks a lot for any hints.
BTW, I've posted this thread alredy in the X1 General forum and realised only now that this forum might be a better choice, sorry for that.
Next try
Hi,
I found the recommendation below and tried, but no avail as well.
Does anyone know an unsigned HardSPL by Oli for the SE X1?
Any help appreciated.
_________________________________________
xidesu
3rd August 2010, 09:33 PM
Default HTC Touch Pro, Fuze HardSPL Error 262 FIX
Alright, this is how i fixed my 262 error after ripping out all my hair for a week.
- Plug your phone into any working usb port (make sure Active sync is up and running)
- Run RaphaelHardSPL-Unsigned_190_1_3.exe and on the first screen pop up, 9 files will be created in the directory you run the .exe from.
- Copy these 9 files to another folder because you will be clicking cancel on the pop up which will in turn erase the 9 files it created.
- Click cancel on the pop up.
- Go to the folder in which you copied these 9 files to.
- Run ROMUpdateUtility.exe and the same screen pop will appear as before.
- Follow the prompts and it should work.
don't flash bootloader-stuff from other devices, never! Oo
try flashing hardspl 0.72 via usb first (the old one), then flash 0.78 as an "update".
Next step, but still not working
Well, I was able to flash APP_SW_X1i_GENERIC_UK_1213-6450_CDF1215-1832_KOV_R1AA017
from the SD card, and I have now SPL0.72.0000 on my X1.
ROM Version:1.02.931.3
Date: 08/29/08
Radio: 1.06.25.29
Protocol: 52.43.25.24U
Software ID: 1213-6450
Version: R1AA017
However, X1_HardSPL still terminates with Error 262 as before. Flashing OliNex's HardSPL via SD card (RUU_Signed.nbh renamed to kovsimg.nbh) does not work either. I still cannot flash my Dynamics GTX 2.3.5 GER ROM.
Any ideas?
BTW, I tried with a desktop and a laptop, both XP SP3 and Active Sync 4.5 on various USB ports. I disabled Security Options via X1_Tweaks. Everything seems to work, only flashing HardSPL still fails.
At least, I am a step back now ;-)
Bingo!
I succeeded. The solution has been:
- Establish an Active Sync connection via USB.
- Copy the file Xperia-SSPL-Manual.exe to the root directory of a FAT32-formatted SD card (no SDHC, an elder one). SSPL-Manual is the basic part of OliNex bootloader.
- Unpack HardSPL by starting it or use RUU_Kovsky files in a directory of the PC hard disk. Make sure that the proper RUU_Signed.nbh file is in this directory (the HardSPL image by Olimex in the version you whish to complete the basic SPL started onthe X1)..
- On the X1, open the file manager and start Xperia-SSPL-Manual.exe by clicking on it. The X1 switches to the boot loader mode indicating HardSPL 0.52 by OliNex.
- On the PC connected to the X1, start ROMUpdateUtility.exe.
In my case, the flashing went very quickly to 100%, and I have now HardSPL0.78OliNex on my X1. Now I can proceed (Task29, image flashing). At least I hope so.
My assumption about the the problems I faced: My X1 had a quite recent firmware which probably blocked any change of the SPL and allowed only generic signed images to be flashed, no cooked ones. Xperia-SSPL-Manual.exe bypasses this lock by applying an OliNex cracked routine, thus allowing to overwrite the SPL. At least I think so.
Done.
My Dynamics GTX 2.3.5 GER ROM is now up and running. THX a lot for the great support of this forum!
Thanks for instructions I have same problem with my X1.
You're welcome.
It has been worth the troubles - the Dynamics ROM is great, and until now, I found no hickups.

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/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.

Categories

Resources