dev unlocked omnia 7 - can't sideload - help appreciated - Windows Phone 7 Q&A, Help & Troubleshooting

hello,
i installed the mango beta on my omnia 7 prior to dev unlocking it (b/c i did't want to wait for mango any longer).
after registering my phone with microsoft i still can't sideload apps via .xap deployment. the software tells me that the remotehost closed the connection whenever i try to deploy a xap to my phone.
anyone know what i can do to solve this?
cheers
phil

oh, this should've gone to the wp7 q&a board...please move it over there. cheers.

What app are you trying to Sideload? Apps with ID_CAP_INTERSERVICES in them can't be side loaded anymore in Mango. The installer sees this capability in the WMAppManifest.xml file in the XAP & refuses to install it. I have found a way to get them to load by editing this file & removing that line, but the apps still won't run on the device. They just crash (except TouchXperience, but it needs to be sideloaded before upgrading as my hack breaks it). I have a thread describing all this.

thx, mate.

the error message with the remote host having closed the connection appears regardless of which app i try to deploy.
weird.

Related

[Q] Deployment issue

Hi i have been trying to deploy a xap that is 80mb size lately, but no matter what i do i kept getting the
"Error 0x8007274c" - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
If i deploy smaller sized xap (10mb 20mb) it works perfectly, but cant seem to deploy larger ones. And i have tried the official deployment tool, Tom XAP deployer, and XAP deploy X. All the same result
BTW, i have updated to NoDo, im guessing it has something to do with that....
Thank you all for helping!!~
Is there no solution?
toothfish said:
Hi i have been trying to deploy a xap that is 80mb size lately, but no matter what i do i kept getting the
"Error 0x8007274c" - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
If i deploy smaller sized xap (10mb 20mb) it works perfectly, but cant seem to deploy larger ones. And i have tried the official deployment tool, Tom XAP deployer, and XAP deploy X. All the same result
BTW, i have updated to NoDo, im guessing it has something to do with that....
Thank you all for helping!!~
Click to expand...
Click to collapse
Problem has been discussed in this thread. There is no real known cause and no real solution. There are workarounds but they are a pain in the @$$.
Ciao,
Heathcliff74
Heathcliff74 said:
Problem has been discussed in this thread. There is no real known cause and no real solution. There are workarounds but they are a pain in the @$$.
Ciao,
Heathcliff74
Click to expand...
Click to collapse
In my trophy i had the same problem when i was in 7390 (nodo) verison of the rom...
After the 7392 update the problem is gone and i can deploy big xap files
colossus if you do further testing I'm sure you'll find out that this depends on the xap itself. 7392 was just security updates as far as I understand so there's no reason that this update should have magically fixed this problem. Test other xaps and report back if you can.
blindpet said:
colossus if you do further testing I'm sure you'll find out that this depends on the xap itself. 7392 was just security updates as far as I understand so there's no reason that this update should have magically fixed this problem. Test other xaps and report back if you can.
Click to expand...
Click to collapse
Hi m8..
I did make those test so far no big xap that i cant install....
I had the same problem with 7390 rom and i was under the impression that the problem was there after the 7392 update.
And i had a long discussion about this in another forum ..
After that i try to install 2-3 big games +100mb and the installed just fine ...
If there is a specific xap you want me to try please let me know ...(i send you a PM)
I have a XAP that installed fine before Nodo. It won't install now. It failed on 7.0.7390.0 and it also fail now that I have 7.0.7392.0. When the files are being installed they are written in this location:
\Application Data\Phone Tools\10.0\Install\{AppID Guid}\
The XAP I try to install is way over 100 mb. But when I look in that folder I see that after the failed install the XAP is always between 66 and 68 MB. I use my own WP7 Root Tools to look there. And in the new version I'm working on I can also copy and delete files and folders (this version will probably ready for release in a couple of days). So when I delete the complete folder with defective install and try it again it always has the same result. I tried all the appdeployers I know (MS App deployer, Tom's installer, WPDM, XAPDeployX), no difference. I also tried to copy the XAP to the phone first and place it in the Install folder. That works and the complete file is present. But when I try to deploy, it just gets overwritten and it fails again.
I also tried to disable Firewall and Antivirus temporary, but it didn't make any difference.
I'm on Omnia7 with JK1 firmware. OS 7.0.7392.0. I have the RTM version of Windows Phone Developer Tools. Would it possibly help if I upgrade to a newer version of the Windows Phone Developer Tools? With the release of NoDo there was also a new release of the Windows Phone Developer Tools. And there is a new beta version for Mango now. I think I'm going to try to install the Nodo version of the Windows Phone Developer Tools and see if that helps.
Ciao,
Heathcliff74
Windows Phone Device Manager for WP7
first move some content out of the xap
deploy
now use wp7devicemanager to copy the "moved content" into installation folder.
does currently not work with mango beta tools
SOLVED!!
Finally got it fixed. You need to install the January update of the Windows Phone Developer Tools (that's version 1.0.1, which is meant to go with the NoDo update on the phone).
You can download the updates HERE.
After I installed the updates I could immediately deploy large XAP's.
Ciao,
Heathliff74
Heathcliff74 said:
Finally got it fixed. You need to install the January update of the Windows Phone Developer Tools (that's version 1.0.1, which is meant to go with the NoDo update on the phone).
You can download the updates HERE.
After I installed the updates I could immediately deploy large XAP's.
Ciao,
Heathliff74
Click to expand...
Click to collapse
I have installed this in my pc from day 1 ..
Maybe that's why i dont have probs with deploying big xaps
I have the Dev-Tools also installed from day 1.
But it does not work.
I've reinstalled the Dev tools now, and it still not work.
Chatfix said:
I have the Dev-Tools also installed from day 1.
But it does not work.
I've reinstalled the Dev tools now, and it still not work.
Click to expand...
Click to collapse
M8 this is not the dev tools ..ist an update/patch and the file name is VS10-KB2486994-x86.exe.
Try to install this once again., and then reboot your pc before you try
colossus_r said:
M8 this is not the dev tools ..ist an update/patch and the file name is VS10-KB2486994-x86.exe.
Try to install this once again., and then reboot your pc before you try
Click to expand...
Click to collapse
There's actually 2 updates on that page:
1. VS10-KB2486994-x86.exe = update for the VS-plugin. The page actually states that this is a fix for deploying packages over 64 MB.
2. Window Phone Developer Tools v1.0.1 (January update including Deployment Tool, Connection Tool, Emulator, etc).
I tried to install only the small Visual Studio fix first. But it didn't fix the deployment apps. I guess this only fixes the 64 MB package limit for when you deploy from within Visual Studio. After I installed the big update for Windows Phone Developer Tools v1.0.1 I could deploy big XAP's. In my case no reboot was necessary (I did close all deployments apps and Zune etc before I started the setup). Windows Phone Developer Tools 1.0 RTW must be installed first if you had not already.
Hope this helps!
Ciao,
Heathcliff74
Heathcliff74 said:
There's actually 2 updates on that page:
1. VS10-KB2486994-x86.exe = update for the VS-plugin. The page actually states that this is a fix for deploying packages over 64 MB.
2. Window Phone Developer Tools v1.0.1 (January update including Deployment Tool, Connection Tool, Emulator, etc).
I tried to install only the small Visual Studio fix first. But it didn't fix the deployment apps. I guess this only fixes the 64 MB package limit for when you deploy from within Visual Studio. After I installed the big update for Windows Phone Developer Tools v1.0.1 I could deploy big XAP's. In my case no reboot was necessary (I did close all deployments apps and Zune etc before I started the setup). Windows Phone Developer Tools 1.0 RTW must be installed first if you had not already.
Hope this helps!
Ciao,
Heathcliff74
Click to expand...
Click to collapse
Holly crap........
I have been in that page about 20 times before and i never read the small print ...
WPDT Fix includes:
Windows Phone Developer Tools Fix allowing deployment of XAP files over 64 MB in size to physical phone devices for testing and debugging.
Yes you are right m8...
colossus_r said:
M8 this is not the dev tools ..ist an update/patch and the file name is VS10-KB2486994-x86.exe.
Try to install this once again., and then reboot your pc before you try
Click to expand...
Click to collapse
Sorry I wrote dev tools, but I mean the patch.
I used the german dev tools and the german patch.
At this time, I uninstall the german dev tools complete try with the english version.
Heathcliff74 said:
Finally got it fixed. You need to install the January update of the Windows Phone Developer Tools (that's version 1.0.1, which is meant to go with the NoDo update on the phone).
You can download the updates HERE.
After I installed the updates I could immediately deploy large XAP's.
Ciao,
Heathliff74
Click to expand...
Click to collapse
i think i had that installed, befor mango tools i had no problem with large xaps
cant install the patch on mango beta tools
webwalk® said:
i think i had that installed, befor mango tools i had no problem with large xaps
cant install the patch on mango beta tools
Click to expand...
Click to collapse
Ok. So you're saying you have the Mango beta tools installed and you're experiencing the deployment problem? That's weird. That probably means that the Nodo fixes in version 1.0.1 are in a branch. Or the mango tools are branched from the 1.0.0 version. Either way. The fix is not in the same branch as the Mango tools. That means that if you have Nodo on your phone, you should use the 1.0.0 version (RTW) of the tools and then apply the 1.0.1 fixes. But you shouldn't use the mango tools, or else you will still suffer from the deployment issue.
Ciao,
Heathcliff74
yes exactly
currently there is no public deployer working on mango beta tools exept the one that comes with the tools, but i cant deploy large xap's with it.
Ok, I give up.
I tried everything. It will not work.
Chatfix said:
Ok, I give up.
I tried everything. It will not work.
Click to expand...
Click to collapse
Did you first install WPDT 1.0 and then upgrade to 1.0.1?
Sent from my OMNIA7 using XDA Windows Phone 7 App

[Mango] Cant Deploy XAP anymore: Error Code 0x89731812

ive tried a new version of navigon, i quote what happend:
webwalk® said:
aww man, whats with this version...
deploy, start server -> check your internetconnection (3g still enabled but no net, shut it down after)
replug phone, restart server, start navigon.. connecting....
but then my phone connected and disconnected from usb 5 or 6 times quickly and zune couldnt find device anymore..
replug, restart... still connecting screen..
ill try one last time... the usb disconnecting freaks me out...
error deploying... 0x89731812
WTF! now replug phone: ZUNE READ ERROR, CANT READ IMPORTANT PARTS FROM DEVICE!
i hope its mango error.. phone restart seems to have fixxed it...
tried one last time.. cant connect to server, forever " connecting " dont know whats up... maybe pc restart, but chance is too low to try out..
device is tmode mozart UK language
ow shhhh... cant deploy anything anymore... error deploying... 0x89731812
Click to expand...
Click to collapse
i rememberd zune had visual problems when i came out of hibernation mode, so ive restarted PC, same problem...
dont know much more yet, maybe a phone restart fixxes it... trying now.. /edit, didnt fix it, CRY
//more info:
while the sudden disconnecting happend,
windows tried to install unknown drivers, but failed,
maybe thats causing the trouble..
i really hope its mango not hardware issue
btw, still unlocked, can start homebrew & sync zune
freaks me out.. next up:
reinstall zune & mango sdk
if not working, nodo backup
ive also read about a hd2 guy with this error but also couldnt sync with zune,
he also had the unknown drivers installed, but never got a fix,
he couldnt even flash a rom, also not after reinstalling everything...
a little scary story, surfing in dangerous grounds
homebrew Xaps in mango
Microsoft doesn't support ID_CAP_INTEROPSERVICES" in mango, but not all xaps require it, I removed it from the Navigon xap and then re-deployed it and it ran fine all my maps work on mango
A question here, what did you package .xap with?
CP-Geek said:
A question here, what did you package .xap with?
Click to expand...
Click to collapse
Use either WinRAR or 7zip to unzip the XAP. Edit the file, compress to a zip, rename zip to XAP. I have a thread on this already...
drkfngthdragnlrd said:
Use either WinRAR or 7zip to unzip the XAP. Edit the file, compress to a zip, rename zip to XAP. I have a thread on this already...
Click to expand...
Click to collapse
There's no need to decompress the archive in order to be able to edit a certain file. At least if it's text based. I for one open the xap with 7zip, then right click the xml file and choose "edit". I can then edit the file to my needs, save it and when I close 7zip it asks me to write the changes to the archive. Once this is done I can deploy the xap to my device and all is fine.
True, the result is exactly the same, but this way you save some time and reduce the amount of possible mistakes.
dkp1977 said:
There's no need to decompress the archive in order to be able to edit a certain file. At least if it's text based. I for one open the xap with 7zip, then right click the xml file and choose "edit". I can then edit the file to my needs, save it and when I close 7zip it asks me to write the changes to the archive. Once this is done I can deploy the xap to my device and all is fine.
True, the result is exactly the same, but this way you save some time and reduce the amount of possible mistakes.
Click to expand...
Click to collapse
True, never thought about that. Sometimes we just overlook the simple solutions lol...
a little offtopic
however, i successfully deployed other versions of the same app earlier on mango so i dont think it had something to do with ID_CAP_INTEROPSERVICES
it seems mango with tmode spl needs more work.
it get lots of different small bugs..
like i had 5x the same call in multitasking..
aborting calls almost crashed my phone today..
im thinking it was alround more stable on htceu spl
but i didnt try to fix anything yet..
maybe when i want to deploy something next time,
ill keep reporting..
mcsc said:
Microsoft doesn't support ID_CAP_INTEROPSERVICES" in mango, but not all xaps require it, I removed it from the Navigon xap and then re-deployed it and it ran fine all my maps work on mango
Click to expand...
Click to collapse
Did someone tried to use IC_CAP_INTEROPSERVICES in apps? Heard that too about the deactivation but I'm still looking for proof.
I have the same error 0x89731812 !
I can't deploy any XAP with Application Deployment. I can't debug too with Visual Studio Express (Failed to connect to device. Ensure the device is completly booted and connected to PC).
I have restarted PC and telephone and reinstalled SDK and Zune but the error is still here !
As far as I know the Mango update removes your unlock. I think the only method to keep it unlocked is to use the provxml method. I've got a Omnia 7 which got relocked after Mango beta update - then I restored my unlocked NoDo backup. I'll try the provxml method and tell you if it worked for me
yes its not that the device is not unlocked, it still is.
@zuifon:
did you notice at some point that windows tried to install drivers for your phone but couldnt find any?
it looks like only restore will resolve this error.. its still a beta..
but i dont know yet, i still didnt try it but thx for reporting,
so i wont have to check if reinstall the windows software fixxes it
My phone is unlocked by APPMFG.
Applications installed before Mango still work.
The message is the same if I disconnect the USB Cable, it's very curious !
Zune detects the phone but not the deployer.
I have deleted the phone in the periphal manager in Windows and driver have been redownloaded from Windows Update but the problem is the same.
zuifon said:
I have deleted the phone in the periphal manager in Windows and driver have been redownloaded from Windows Update but the problem is the same.
Click to expand...
Click to collapse
the unknown driver? or the phone driver?
my device manager does not show any unknown driver..
but it found unknown (the phone) hardware at some point..
now someone over here
reported that he also had used a different phone but can not deploy with the computer anymore. not sure if he has the same error code.
It's a phone problem. I have the same problem with a second computer.
hey guys,
i updated my dev unlocked omnia 7 to mango and re-unlocked it after having finished the update process.
for some reason, i cannot deploy any .xap to my phone, regardless of having ID_CAP_INTEROPSERVICES or not.
the software deployment software keeps telling me "the remotehost has closed the connection".
anyone have an idea? this is majorly annoying for me.
cheers,
phil
hey,I just think we have the same problem as you described,and i resolved it by my friends help. It's really easy, hey hey, just try to change it on another Universal Serial Bus. Hope can help you~~
heh actually i never tried using another usb port..
i have zuned the backup, everything working again.
maybe update to mango in some days
What on earth could be causing this? My phone (Optimus7) was in service and it got new mainboard. After it came back i did the usual tricks to unlock it etc. but now the deploying ends to this 0x89731812 error no matter what i try. Could anyone have an idea on where to start looking for the cause?
tkay564 said:
What on earth could be causing this? My phone (Optimus7) was in service and it got new mainboard. After it came back i did the usual tricks to unlock it etc. but now the deploying ends to this 0x89731812 error no matter what i try. Could anyone have an idea on where to start looking for the cause?
Click to expand...
Click to collapse
Same here, i don't know if it's warranty repair-related, i don't remember if i unlocked it after that (i relocked it way before mango, that's for sure)...but i got no new mainboard, they just replaced some components (based on repair list sheet), it seems strange they changed something so important to break developer connectivity
°Dexter° said:
Same here, i don't know if it's warranty repair-related, i don't remember if i unlocked it after that (i relocked it way before mango, that's for sure)...but i got no new mainboard, they just replaced some components (based on repair list sheet), it seems strange they changed something so important to break developer connectivity
Click to expand...
Click to collapse
Does anyone know if this could be repair-related or just software? i tried last chewron tool too, no changes, phone doesn't connect to "developer" tools.
I guess if there is any registry key related to developer connectivity, to check if they changed anything through some strange sw flash (hoping it's not really hw)

Device not connected - Help, can't deploy apps anymore

Hi,
I have an unbranded HTC 7 Mozart T8696 Device running NoDo 7392.
It was chevron unlocked before I upgraded to NoDo and I was able to install apps aferwards. Currently sideloaded apps still work, so I assume the chevron unlock is still active. After about one month I wanted to sideload another app, but I always get an error telling me the device is not connected to the PC (I tried XAP Deploy and "Windows Phone Device Manager" even though Zune is running and showing the device as connected.
Any Ideas what might be wrong? I already tried uninstalling .net framework 4 and windows phone developer tools and re-installing, but it still shows "device not connected"
try this ... go to C\windows\system32\drivers\etc , open the file named "hosts" with notepad and delete any lines that say windowsphonedevelopement...
Hi,
thanks for your feedback. my hosts file is empty, still not working.
I am still using Zune 4.7 should I update to 4.8?
i had this same problem with my hd7 before and it worked after deleting that ... thats weird , yea 4.8 is now officially released u should update ..hopefully it will solve ur problem
still no luck, even with Zune 4.8
check this out ...
http://phone7.wordpress.com/2010/12/01/wp7-deployment-error-codes-explained/
http://msdn.microsoft.com/en-us/library/gg588381(v=vs.92).aspx
thanks, but this just doesn't help me
Failed to connect to the device. Ensure that the device is completely booted and is connected to the PC.
This can be caused by several reasons, including if the device is off. If the device is already connected, sometimes disconnecting and then reconnecting the device may fix the problem. Rebooting the device may also fix this problem.
This is what i tried multiple times. Rebooting the PC, rebooting the phone, re-installing .NET Framework 4, re-installing WP7 developer tools... all to no avail...
did u make sure the phones sync relationship with zune is not guest
Yes, I made sure it is. Nothing has changed on my PC really, except i switched routers. I am not sure what's happened...
hmmm maybe u can try going into device manager and uninstalling then reinstalling the phone drivers
I also went along and tried that. Still no luck.
EDIT: to clarify, I selected to uninstall the device and delete the driver files along with it. When I connected the phone it was re-installing the drivers.
tbh, i give up now. It's probably my phone and I can't be bothered to start from scratch again.
sorry i couldnt help u fix the problem
Instead of zune. Try using wpconnect.exe instead.
Thats all I use and its alot quicker that opening up zune and everything.
If you have Developer Tools 7.0 and the January Update wpconnect can be found here
C:\program files\microsoft sdk's\windows phone\v7.0\tools\wpconnect\
Restart your computer then connect your phone via usb wait for computer to recognize the phone. Then run wpconnect.exe... Dont run zune at all.
Hello,
thanks for your feedback, but wpconnect is giving me the same error as all deployment apps:
Failed to connect to the device.
It suggests i open zune and close it again. Zune itself recognises my phone and is able to sync data to it. WPconnect and deployment apps keep on telling me the phone is not connected...
*Bump* Anyone else have this problem?
could it be a pc registry problem ?
*bump* Still can't sideload
Hello !
Actually I've got the same problem.
Reparing .NET does nothing.
I've tried many things, as uninstalling programs that could interact on USB (VM Ware Workstation, Oracle VirtualBox, Kaspersky Internet Security 2012 and so on).
None of the XAP Deploy application works... And ChevronUnlocker is concerned to.
I don't know what to do.
Here I am too...same problem with my gf's optimus 7, no deplyment tool can connect to device, error 0x89731812, Zune works flawlessly.
Did you guys find the problem after warranty repair?
So, I seem to be running into this problem every 4 weeks... I am starting to hate this, I can never fix the issue aside from hard resetting my phone with a new ROM...
Anyone found a solution to this problem yet? I am currently on DFT v2 and I can't deploy xaps via PC. I can still deploy with the built in XAP deployer, but I have 2 xaps that I can't deploy using this method...

[Q] INTEROP-UNLOCK for MANGO - No revert to NoDo - is it possible for HTC devices?

Hi there, I've read several guides and tutorials around how to allow InteropServices on Mango (beta2) devices by changing MaxUnsignedApp value, but so far there was no working solution for HTC devices, only Samsung ang LG(?).
So does anybody know how to enable interop services on HTC device running Mango Beta 2 and regular Dev unlock? I really don't want to revert to NoDo once Mango RTM is available in Zune.
Thanks in advance!
N3croman said:
Hi there, I've read several guides and tutorials around how to allow InteropServices on Mango (beta2) devices by changing MaxUnsignedApp value, but so far there was no working solution for HTC devices, only Samsung ang LG(?).
So does anybody know how to enable interop services on HTC device running Mango Beta 2 and regular Dev unlock? I really don't want to revert to NoDo once Mango RTM is available in Zune.
Thanks in advance!
Click to expand...
Click to collapse
If you continue reading, you should have read that there is no way yet, but its still being figured out. Hopefully real soon.
If you are already unlocked, have TouchXplorer already Sideloaded, USB Storage Enabler install on your PC, & HTC Connection Setup, than you can do this registry hack with CustClear.ProvXML. Create the ProvXML, copy it into \Windows\ of your device & run HTC Connection Setup. If you are own NoDo, I suggest installing Registry Editor & Advanced Configuration Tool by Schaps as he now has Mango compatible versions available.
It might be possible to patch a network selection app for everybody with an unlocked device.
You will download the app legally from the marketplace, than use heatcliffs method to replace a provsion file from one of the providers by deploying the app. This provision file now contains all the keys to unlock, run your legally downloaded network selection app, select the patched network and bam unlocked.
If somebody is willing to test I might give it a shot, PM me.
drkfngthdragnlrd said:
If you are already unlocked, have TouchXplorer already Sideloaded, USB Storage Enabler install on your PC, & HTC Connection Setup, than you can do this registry hack with CustClear.ProvXML. Create the ProvXML, copy it into \Windows\ of your device & run HTC Connection Setup. If you are own NoDo, I suggest installing Registry Editor & Advanced Configuration Tool by Schaps as he now has Mango compatible versions available.
Click to expand...
Click to collapse
I tried TouchXplorer on my HTC HD7, but it won't work, because of InteropServices limitations - with the capabality in manifest it won't install, without it it installs, but does not work. I've tried several file system managers, ho success. I don't know, what is USB Storage Enabler, but if it's some kind of homemade USB jig I'm not interested.
Well, it looks like NoDo revert is the only way
N3croman said:
I tried TouchXplorer on my HTC HD7, but it won't work, because of InteropServices limitations - with the capabality in manifest it won't install, without it it installs, but does not work. I've tried several file system managers, ho success. I don't know, what is USB Storage Enabler, but if it's some kind of homemade USB jig I'm not interested.
Well, it looks like NoDo revert is the only way
Click to expand...
Click to collapse
This is why I said if you have TouchXplorer Sideloaded before Mango. Then, it'll work. I have TouchXplorer/Registry Editor (Mango Version)/Advanced Configuration Tool (Mango Version already Sideloaded & waiting for official update to come through so I'll be ready. My only concern is I might need to use the unlock hack when i update to Mango even though I have an official AppHub account. When I tried upgrading to the Beta & RTM, the unlock tool wouldn't connect due to apps/registry changes I have installed.
If that is the case does that mean screen capture app based on dll will work?
Sent from my HD7 using XDA Windows Phone 7 App
drkfngthdragnlrd said:
This is why I said if you have TouchXplorer Sideloaded before Mango. Then, it'll work. I have TouchXplorer/Registry Editor (Mango Version)/Advanced Configuration Tool (Mango Version already Sideloaded & waiting for official update to come through so I'll be ready. My only concern is I might need to use the unlock hack when i update to Mango even though I have an official AppHub account. When I tried upgrading to the Beta & RTM, the unlock tool wouldn't connect due to apps/registry changes I have installed.
Click to expand...
Click to collapse
So I rolled back to NoDo today, dev unlocked, installed TouchXplorer, Advanced config. and DiagProvXML, uploaded CustClear.provxml file to Windows file and runned Connection setup... but after updating to final Mango nothing works, all three apps are not working, so I guess it's no go for me with interop services.
This is an absolute no-go. Of course I tried this, but Interop-dependent apps installed before the update didn't launch after the update. Interop-dependent apps in Mango won't install. With the capability commented out they install, but don't work. Especially TouchXPlorer, which does not show any files, Registry Editor seems to be working, but cannot acces the right keys (same as on NoDo), Advanced Config works, but does not actually apply the settings. I also wasn't able to make any of the ProvXML deployers work.
ProvXML I prepared to the Windows folder was not applied by Connection setup (however this method NEVER worked for me before Mango, I'm actually quite surprised, I've been that dumm to try it).
Heatcliff says he's working on HTC-compatible Root Tools, so let's just wait for it

can't install XAPs

hi..
i used to use MultiXapInstall to install XAPs but from two week ago.. i'm unable to install XAPs through MultiXapInstall (and the others xap installers )..
when i try to install a xap i get this error :
Code:
Connect() :: Class not registered
at first i get :" parameter is incorrect " error so i use some Registery Cleaner programs and after that i got this class not registered error..
What should i do?!
sry for my weak EN
any help?!
Reinstall the official SDK. One of the required components was probably removed or corrupted. I also tend to recommend against running any of those "registry cleaner"-type programs...
Just for the record, I assume the official XAP deploying tool isn't working right now either?
thank you for reply.. i reinstalled WPSDK but nothing changed. i still "get class not registered" error..
what should i do next?
There's apparently a leap day bug affecting Zune; it might be related? Try again tomorrow. If that doesn't work, the only thing I can think of is to either try a different PC, or to completley remove WPSDK and Zune, reboot, then re-install them.
i reinstall both WPSK and zune several times. and now when i try install an app or a game with Multi Xap Install the application Stops Working and making me close it..
this bug is killing me!!
Try using the official XAP deployment tool, and see what error it gives.
excuse me.. what is Official XAP Deployment Tools? i searched but nothing found
if you mean installing via Zune.. it's ok with no problem.
P.S: when i try with WPV XAP Deployer i got this error :
Specified Cast is not valid
Click to expand...
Click to collapse
Something like this happened to me a while back. Are you sure your installing the right developer tools. I'm assuming you have mango. Dev tools should be 7.1
Sent from my HD7 T9292 using XDA Windows Phone 7 App
thank you for answering.. yes i have mango and also WPSK 7.1 is installed..
I mean the "Application Deployment" tool (xapdeploy.exe) that comes with the SDK. I don't think you can get much more official than that. It's relatively feature-poor, but it's also both less buggy and gives better error messages than most of the third-party deployers.
You should try using the official XAP deployment tool installed with the SDK. It's on your start menu Also make sure that Zune is launched.
found the solution xap deployer parameter error (fixed)
H_R_V said:
hi..
I changed my devices name to lumia and tried deplying a game and it worked so i guess
changing the name is the solution. I got suspicious about the name because usually my phone's name appears as windows phone but this time it was windows phone 09832 or something i dont remember the exact numbers but it works for me.
To fix parameter error in deploying tool Just rename your device to lumie or anything else
Click to expand...
Click to collapse

Categories

Resources