[Q] How install XAP on LG E900? - Windows Phone 7 Q&A, Help & Troubleshooting

Hey,
My LG E900 is the OS version: 7.10.8107.79. And I want to unlock it take to install applications and games XAP. I used the method by MFG, I put XAP in a Tom XAP Installer to install, and gives me this error when installing:
-Please Make sure your phone was unlocked !
-Please Make sure you connected device to PC and Zune launched
Try again?
What happening? This method does not it? You can get the original ROM and remain the ChevronWP7 up to this latest version? I have another way?
Thanks in advance and sorry my english!
PS: I can put original Rom, install ChevronWP7 and remain to Last Version (7.10.7740/7.10.8107, or other)?

Use the official Xap installer tool "Application Deployment" that comes with the SDK. The third-party installers are plagued with bugs and bad error messages. Many of them also require at least a few components from the SDK, even if they say otherwise.
If you want to make sure that the phone is ready to receive apps, try synching a file to it from Zune - Zune must be running and synched with the phone for XAP deployment.

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

dev unlocked omnia 7 - can't sideload - help appreciated

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.

How to unlock Mango

I have a trophy with stock FW 7.004
How do i unlock mango?
(when i upgrade to it,i know how to do it)
- Email chevronwp7.cer, open and install.
- Plug in phone and leave Zune running.
- Run chevronwp7.exe, click both checkboxes and unlock
- Install Prevent Relock.xap
- After running uninstall it.
---------------------------
- Update to NoDo via Zune.
---------------------------
- Install TouchXplorer.xap
- Install HTC Connection Setup (from market!)
- Run HTC Connection Setup
- Deploy CustClear.provxml (I've done via mass storage enabler..)
- Open TouchXplorer
- Copy \My Documents\Zune\Content\0400\00\CustClear.provxml to \Windows\
---------------------------
- Update Mango
- Run HTC Connection Setup
- Done!
Thats pretty much it.. this is how i've done it with my trophy =)
7.10.7720.68 I have this version updated last night. How to Unlock phone now ?
FTP4 said:
7.10.7720.68 I have this version updated last night. How to Unlock phone now ?
Click to expand...
Click to collapse
Depends, what phone?
HTC HD7. Everything would be ok and I could use to new design, but none of games isnt working - MS Revoked
Developer-unlocking a Mango phone (dev-unlock is what ChevronWP7 Unlocker did) is possible with an official marketplace developer account, or (soon) through ChevronWP7 Labs. If you have a restore point for NoDo, there are ways to carry the unlock forward if you don't have an official one (although for HTC it's more difficult than for Samsung or LG, and the methods keep getting closed off).
"Application has been revoked by Microsoft" message usually means that you're trying to run a sideloaded app on a non-dev-unlocked phone. This can be fixed by dev-unlocking. Now, I'm going to avoid jumping to any conclusions, but there aren't that many games publicly available for sideloading. XDA-Developers is about using our phones without artificial restrictions, not about using other people's work without paying for it. Discussion of software piracy is not accepted here. Just... thought you should know.
I restored my phone back to nodo with backup. Maybe will try to update with unlock someday.
ps. maybe someone can tell me privately how to reinstall (install android) if there is no exe files but only system files in extracted folder ?

How to tell my phone is unlocked or not

I've just bought a second-hand Samsung Focus (SGH-i917) from a local cellphone vendor for developement purpose. From settings, about, it reports software version Windows Phone 7.5 and OS version 7.10.7720.68. Is there a way to find out if my phone is unlocked or not. If unlocked, how can I load XAP onto the phone? If locked, how can I unlock it. BTW, I do not pirate, just for developement.
Hi
You can see if your phone is locked or not trying to deploy a XAP file on it.
You can do this using a deployer like Tom XAP Installer.
You also need the Windows Phone SDK (download it HERE) which is necessary to develop applications and deploy them.
After installed, download a XAP file (or use your own), connect your phone and run WPConnect (C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.1\Tools\WPConnect) and open Tom XAP Installer, select Add XAP files and click on Install. If the installations finishes correctly, your phone is unlocked, otherwise you have to unlock it.
You have two ways to do this:
- Official jailbreak by Microsoft (HERE), It costs 9$ and allows you to deploy 10 applications. You won't lose warranty.
- Downgrade to the 7004 firmware (VIDEO) and unlock it using ChevronWP7 (Download HERE), then before updating to Mango you have to send a file (unlock.xml) to your phone (Tutorial Here), otherwise you'll lose the unlock.
Thanks, I'll try your instructions.
@AshleyT: A couple of minor corrections:
The official ChevronWP7 Labs unlock is not by MS, though they permit it (thus "official"). They don't get the $9, though you do have to use a Live ID.
There is another official way to dev-unlock your phone: get a Marketplace developer ("AppHub") account. http://create.msdn.com ($99, goes to MS) or http://dreamspark.com (requires student email address, free). For these methods, use the Windows Phone Developer Registration tool that comes with the SDK download.
The reason I point out the apphub account option is that, if the OP wants to develop apps, he or she may want to publish them to the marketplace at some point. You can't do that with a ChevronWP7 unlock, official or otherwise, but you can with AppHub.
Chevron can check whether your phone is unlocked, or u can try to install one simple xap application to test this.
It seems that my phone is locked.
First I tried Tom XAP installer, it said:
-Please Make sure your phone was unlocked!
-Please Make sure you connected device to PC and Zune launched
Try again?
Then I tried Application deployment from Windows Phone SDK 7.1, which said
Error - Failed to connect to device as it is pin locked.
I am sure my phone is connected to PC as I can see music/video/picture in Zune.
Could someone explain to me what is "pin locked"?
leonard2010 said:
Could someone explain to me what is "pin locked"?
Click to expand...
Click to collapse
To remove the error of pin locked u just need to swipe up the lockscreen and try to deploy the xap file.. it will be successfully deployed..
I countered the same problem earlier..
Hope this helps
i have successfully unlocked my Dell Venue Pro and i have 5 applications installed. Now when i do Hard reset I'd be able to install only 5 or 10 applications?¨
PS Sorry for my english

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