I have downloaded at least 6 copies of lates rom from orange site but whenever I try to upgrade my imate it shows error
upon extraction of ROM (nk.nbf is extracted only 15.2MB Vs actual 63MB)and shows integrity error
Upon direct run give error on (self integrity check) and says it is a corrupt version of exe file.
Can anybody help me to resolve the issue
Are you running the whole .exe file as it is downloaded?
Have you tried extracting the .exe file first to see if the file sizes are correct?
If there is still a problem try downloading from xda-developers ftp I think some one has uploaded it to there.
Yes i did the same thing after getting error and then ultimately downloaded xda ftp version and observed
this is the correct version
[ 3:55:32.78] MachinaGod lokiwiz start
Copying C:\aWizard\lib\itsutils.dll to WCE:\windows\itsutils.dll
ERROR: Error !!! Writing WinCE file - There is not enough space on the disk.
opening: lock_backup.bin: No such file or directory
This exe file was created with the evaluation version of Perl2Exe.
For more information visit http://www.indigostar.com
(The full version does not display this message with a 2 second delay.)
...
Copying C:\aWizard\lib\itsutils.dll to WCE:\windows\itsutils.dll
ERROR: Error !!! Writing WinCE file - There is not enough space on the disk.
Copying C:\aWizard\lib\itsutils.dll to WCE:\windows\itsutils.dll
ERROR: Error !!! Writing WinCE file - There is not enough space on the disk.
[ 3:55:36.50] Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
* Press [Enter] to continue
I forgot to clean some crap up first... how can I check if it's really unlocked before i try to do it again ?
From the error message, your phone doesn't seems to have been unlocked. There isn't any software/method that I know of that can check if your phone has been unlocked. The only way to do it is to get another SIM (of other operator) and try it on your phone, see if it works.
Anywya, i bet yours aren't unlocked yet. Check if you have the "lock_backup.bin" file in your aWizard directory. If yes, copy this file to somewhere or rename it (e.g. back up the file) and performa another unlock process. It doesn't damage your phone running unlock twice (or multiple times). The only problem is that you may loose your lock file (e.g. lock_backup.bin) that you may need to have your phone back into the lock state (e.g. for warranty claiming purposes)
BuildOS appear with a message: 1c866f27-3fc5-4c9d-a159-9fd4175b8980.rgu Already exist. Now you think just delete the duplicate file but there's no file only 1 in the /temp map. Does someone know how i can get off this error ?
simply use the package creator in order to generate a new GUID name intsead of this one ...
Okay the zip thing didn't work..
How about:
Create C# command line executable.
Reference following dlls:
Microsoft.Smartdevice.Connectivity.dll
( C:\Program Files\Common Files\microsoft shared\Phone Tools\CoreCon\10.0\Bin\Microsoft.Smartdevice.Connectivity.dll )
Microsoft.VisualStudio.DeviceConnectivity.Interop.10.0.dll
( C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.DeviceConnectivity.Interop.10.0\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.DeviceConnectivity.Interop.10.0.dll )
and add following code:
Code:
using System.IO;
using System.Linq;
using System.Reflection;
using Microsoft.SmartDevice.Connectivity;
using Microsoft.VisualStudio.DeviceConnectivity.Interop;
namespace Conn
{
class Program
{
static void Main(string[] args)
{
Platform plat = new DatastoreManager(1033).GetPlatforms().Single(p => p.Name == "Windows Phone 7");
uint proc;
uint handle;
bool useEmulator = true;
Device dev = null;
if (useEmulator)
dev = plat.GetDevices().Single(d => d.Name == "Windows Phone 7 Emulator");
else
dev = plat.GetDevices().Single(d => d.Name == "Windows Phone 7 Device");
dev.Connect();
ConManServer con = dev.GetType().GetField("mConmanServer", BindingFlags.NonPublic | BindingFlags.Instance).GetValue(dev) as ConManServer;
con.LaunchProcess("", "", (uint)FileMode.Open, out proc, out handle);
}
}
}
the launchprocess is the interesting part here. Apparently you can launch executables with parameters.
and some executables to start:
"\Windows\Calc7.exe" (yay)
"\Windows\CertInstaller.exe" install custom cert?
("Content Type"="application/x-x509-ca-cert")
"\Windows\AppPreInstaller.exe" - does nothing?
"\Windows\devicereg.exe"
"\Windows\FileBrowser.exe" - not found?
"\Windows\NativeInstallerHost.exe" - Cannot run \Windows\NativeInstallerHost.exe in Win32 mode.
and some exes cannot be started with following error:
"This program is blocked by group policy. For more information, contact your system administrator."
"\Windows\OBEXParser.exe" - Operation failed. Failed to Save. Received data may be incomplete. - parse obex data here?
"\Windows\PolicyLoader.exe" - does nothing?
"\Windows\Pxl.exe" - tries to start something
"\Windows\CFPreloadClient.exe" and "\Windows\CFLauncher.exe" - worth checking out?
Also worth mentioning:
I added executable to windows phone project and saved it to the isolated storage, then used launchprocess to start it but only got following error:
"An attempt was made to load a program with an incorrect format."
Did you compile it as a x86 exe or with the wm sdk? But excellent job it looks like ConManServer can copy files to and from the phone...
Also \\windows\\iexplore.exe
It's a normal x86 console application.
I tried the file copying too but always got access denied exception.
Another thing worth trying is cooking up compact framework 3.7 dll with all the normal stuff you find in windows phone 7 dll and then making a xap file with all needed files (like mscorlib.dll) and deploying it to the phone.
- phone says invalid license when trying to execute it.
Not the console app the app you tried to copy to the phone is it a X86 exe or ARM?
Does it through that message with a custom app or with a XAP with cooked .net modules? I doubt you can put .net modules with the XAP and expect it to load properly...where is the exact path for isolated storage? We should be able to copy anything there.
crozzbreed23 said:
where is the exact path for isolated storage? We should be able to copy anything there.
Click to expand...
Click to collapse
Your application is installed (essentially by decompressing it) in \Applications\Install\{GUID}\Install\ where {GUID} is the ProductID found in your WMAppMinfest.xml.
I tried running a native EXE I copied to the Emulator inside a XAP by running the LaunchProcess(@"\Applications\Install\{GUID}\Install\application.exe"...) and it finds the file, but throws an Error saying I don't have permissions (I'll get the exact error tomorrow). It seems it'll only run files from certain locations, such as in the Windows Folder, but I'm yet to find a way to copy a file into there.
Is it the same function that XNA uses to deploy a XAP to the emulator? I doubt it only runs apps from the windows folder, sense Office is a native application which doesn't reside in the iwndows folder.
hounsell said:
I tried running a native EXE I copied to the Emulator inside a XAP by running the LaunchProcess(@"\Applications\Install\{GUID}\Install\application.exe"...) and it finds the file, but throws an Error saying I don't have permissions (I'll get the exact error tomorrow). It seems it'll only run files from certain locations, such as in the Windows Folder, but I'm yet to find a way to copy a file into there.
Click to expand...
Click to collapse
Did you ever find a way to get this to work, hounsell? Where did you get the application.exe in WP7 native code?
crozzbreed23 said:
Is it the same function that XNA uses to deploy a XAP to the emulator? I doubt it only runs apps from the windows folder, sense Office is a native application which doesn't reside in the iwndows folder.
Click to expand...
Click to collapse
The system doesn't install your app as an exe, it installs it as a C# DLL (managed code). Thus it doesn't need permission to execute files in that directory, it just needs permission to load a DLL from that directory.
That said, the problem could be the DLL hounsell used wasn't signed.....
athompson said:
Did you ever find a way to get this to work, hounsell? Where did you get the application.exe in WP7 native code?
The system doesn't install your app as an exe, it installs it as a C# DLL (managed code). Thus it doesn't need permission to execute files in that directory, it just needs permission to load a DLL from that directory.
That said, the problem could be the DLL hounsell used wasn't signed.....
Click to expand...
Click to collapse
I haven't got it to work. I think I might have got the EXE from one of those pre-release HTC ROMs. Probably wouldn't have run, but it was throwing errors anyway.
Exactly, And there's a "LaunchApplication" in the same Interface as LaunchProcess, where you just pass the GUID anyway.
Got an interesting error today: Tried running PacmanInstaller.exe (Which appears to be the XAP installer, where Pacman is "Package Manger", rather than an amusing game), and it thew a COMException saying that the application couldn't be run in Win32 mode. (COMException because this trick uses a COM DLL on the desktop, rather than any COM on the mobile)
Code:
Cannot run \Windows\PacmanInstaller.exe in Win32 mode
Was most surprised. Not sure what that's all about. Still trying to get something happening with that "MediaCenterFinal.xap" on the Omnia 7 ROM.
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.