Develop Bugs

[Q] Want to develop for Windows Phone 7

Let me give some background. I know the very basics of hacking. That's it, not much more. I know how to root Android phones, install homebrew on WebOS, and I have tweaked Blackberry software, installed new os', just basic stuff like that. I have never built an app but I want to learn how to develop applications for Windows Phone 7 as this will be my next phone. Any advice? I went to the site and they have the tools there, I was just looking for any pre-reading I should do, or any advice from those already doing it.
Thanks

Download the free developer tools and play. Expression Blend is pretty easy and made for more visually-oriented people vs. hardcore coders.

The catch is that you can't deploy your apps onto your phone without a developers account.
But fi you're a student you might be able to claim a Student account from Dreamspark.

Sir. Haxalot said:
The catch is that you can't deploy your apps onto your phone without a developers account.
But fi you're a student you might be able to claim a Student account from Dreamspark.
Click to expand...
Click to collapse
Just watch the Dreamspark method as you don't seem to be able to register a device until you have your identity verified which, for students, doesn't happen until you submit an application for certification. I am still waiting to hear back from MS on that and if there is a way round it. It means you cannot test your application on a real device until after you have submitted it for certification which seems rather odd.
The tools themselves are very good it is very easy to produce a good looking functional application. There is quite a bit on http://create.msdn.com/ to get you started.

Omega Point said:
Just watch the Dreamspark method as you don't seem to be able to register a device until you have your identity verified which, for students, doesn't happen until you submit an application for certification. I am still waiting to hear back from MS on that and if there is a way round it. It means you cannot test your application on a real device until after you have submitted it for certification which seems rather odd.
The tools themselves are very good it is very easy to produce a good looking functional application. There is quite a bit on http://create.msdn.com/ to get you started.
Click to expand...
Click to collapse
Thanks for the Dreamspark tip! I just got verified and DLd the software.
Hopefully this developer account will come in handy.

Might want to check out this site too: http://msdn.microsoft.com/en-us/beginner/dd435692.aspx It'll help you get through the basics of programming that you'll need to know

why not
i can give you i got an account
pm me if you need

Free WP7 eBook
If you have some time to read the excellent Charles Petzold 's ebook...
Programming Windows Phone 7 which comes with Sample Code.

ChevronWP7 w/ side limit removed.

Has anyone used the no limit version of chevron over an phone that was allready activated w/ developer account? The reason I'm asking is will this give us the best of both worlds? Since the phone will be legally unlocked according to MS, but unlocked with unlimited # of sideloading apps.

FireSokar said:
Has anyone used the no limit version of chevron over an phone that was allready activated w/ developer account? The reason I'm asking is will this give us the best of both worlds? Since the phone will be legally unlocked according to MS, but unlocked with unlimited # of sideloading apps.
Click to expand...
Click to collapse
If you are a normal dev, paid the $99, you can deploy 10 apps. I write a lot of apps that will never see the light of day, and I really don't have an issue with the 10 limit...
I haven't exchanged any apps with others, but if I do, I may have an issue then.

FireSokar said:
Has anyone used the no limit version of chevron over an phone that was allready activated w/ developer account? The reason I'm asking is will this give us the best of both worlds? Since the phone will be legally unlocked according to MS, but unlocked with unlimited # of sideloading apps.
Click to expand...
Click to collapse
Yeah, I'm having trouble with the limit too. I'm afraid to run Chevron though because I don't want to mess up my legit dev unlock, and the source for Chevron is obfuscated and not worth digging through to figure out if it'd work.

I guess I should toss out, that waiting for a response I used chevron over my unlock. It had to relock, then took installed the cert and unlocked using chevron. I am thinking it will last because the unock is probally verifiying that we are in the MS dev database, not checking certs etc. I think that was an unforseen oversight. I will report any issues btw I am a student so I only get 3 apps. My 3 news readers took up the most part and my game I am deving wouldn't go on until I removed the limit.

FireSokar said:
I guess I should toss out, that waiting for a response I used chevron over my unlock. It had to relock, then took installed the cert and unlocked using chevron. I am thinking it will last because the unock is probally verifiying that we are in the MS dev database, not checking certs etc. I think that was an unforseen oversight. I will report any issues btw I am a student so I only get 3 apps. My 3 news readers took up the most part and my game I am deving wouldn't go on until I removed the limit.
Click to expand...
Click to collapse
Could you give me a walkthrough on what you did? I seem to be having trouble with chevron

iamcarl4ever said:
Could you give me a walkthrough on what you did? I seem to be having trouble with chevron
Click to expand...
Click to collapse
You want to go to the topic which describes how to edit the registry. It is the easy one or you can find the Chevron which has side apps limit removed. I doubt that it still available. Both methods will allow unlimited side apps. Also, on the topic of how to edit registry, it also allow you to modify different stuff like preventing re-lock Chevron.

spincel said:
You can find the Chevron which has side apps limit removed. I doubt that it still available.
Click to expand...
Click to collapse
Blog Post
Direct Link (MediaFire)

[Q] Need to create an apps that is for or agents, and not for everybody else

Is there a way of creating and deploying an wp7 app that would be only available to our company agents.
As far As I understand this you can only deploy any app via the Market Place - this is useless for any internal business application.
Do I need to wait for better mobile device management or is there away around this ?
Any pointers appreciated guys.

Two ways to do it, the way I see it...
1. Add the program to marketplace, but require an registration number to be inputted in the program for it to work.
2. Side-load it

tiwas said:
Two ways to do it, the way I see it...
1. Add the program to marketplace, but require an registration number to be inputted in the program for it to work.
2. Side-load it
Click to expand...
Click to collapse
2 won't work, as it could be redistributed.
1 might, but we all know how well registration models work (cracks)
this might be a job for phone-home drm.

tiwas said:
Two ways to do it, the way I see it...
1. Add the program to marketplace, but require an registration number to be inputted in the program for it to work.
Click to expand...
Click to collapse
This would probably be the best, especially considering that your agents probably need to login anyway.
But I think that you won't pass certification if they can't test the app.
I don't know what your company does, but maybe you could release an app that is many targeted at your customers and everyone could use. This app could then have a hidden setting to enable special functions after a agent has logged in.

Microsoft are planning on supporting this in the future, their current suggestion, IIRC, is to use some sort of login though.

[IDEA] Why we don't update chevron?

Do you have a locked phone with Nodo?
So, at this moment your chances are:
Restore the phone to previous version (from Zune)
If your device is LG, you can use the integrated registry editor to unlock it
Buy a developer account subscription
What if your country is not supported by the Marketplace to buy a developer account subscription?
Well, you can ask someone to unlock your phone via remote desktop with their account, then apply any relock prevention
You can use Yallapps unlocking service
I was thinking on update chevron for nodo. There is no marketplace in my country to test and check what is the token used by the developer unlocker application from the phone tools.
Recently I discovered yallaapps (where everyone can register and unlock their phones). It is very unfair compared to the standard marketplace rules (you can upload only free apps, and like 3-4 every 80 dollars).
Anyone here have a yallaapps account to share? (via remote-ethernet usb for example) and unlock my phone to check what is the token, and test if microsoft did something to avoid chevron.cer, etc... I can work some nights trying to get an updated unlocker for us.
Comments?

I've thought about this too. But I have an unlocked Omnia 7 now, with NoDo. And I'm kinda afraid to test for locking/unlocking, because it might lock my phone, while not being able to unlock again. Only a restore of backup or reflash firmware would possibly fix that, but I too busy to risk that now. If it wasn't for that I would've tried a couple of things.
With registry access we can set the value of HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg\PortalUrlProd to anything we like. Set it to something like this: http://www.wp7unlock.com. That site does not exist, but that doesn't matter. Note that I mention "http" and not "https" to make it easier. Then add this url to the hosts-file on your computer. Open a http-server on port 80 which logs all http-requests. Now run ChevronWP7 unlocker and try to lock / unlock. Note: Don't try this if your device is upgraded to NoDo and unlocked, and you wish to keep it like that. You can grab the exact request. That is the first step. But this may already lock your device, if you got it unlocked. You need an unlocked device in the first place to edit the registry. If you got the exact http-request that is sent by the NoDo-device, you can manually try to send it to the original url: https://developerservices.windowsphone.com/Services/WindowsPhoneRegistration.svc/01/2010. Now grab the response. That will be the second step. Having the request and response may already provide very useful information and help us further.
I think the chance of getting your device re-locked is small. But only someone who is doesn't matter restoring a backup or older firmware in order to re-unlock should try this. If someone feels like testing this, we may get a start on unlocking NoDo.
Ciao,
Heathcliff74

I'm just guessing here, I haven't actually done any research into it, but I believe the patch was relating to the certificate - aimed at the fact that ChevronWP7 relied on WP7 accepting an untrusted certificate being used by the unlocking server if that certificate had been installed to the phone's store. Simply doing some basic checking on the certificate to ensure it's from a trusted authority for example, is probably the route Microsoft took, or something along those lines.
I'm kinda busy with other things right now, but I'll have to get a copy of a NoDo ROM at some point and take a peak at the relevant files.

Another possibility is to hide a registry editor in some app and submit it to the marketplace. But soon or later they will notice the trick.
Pretty convenient the LG devices with their integrated registry editor...

The odds of being able to sneak any app with the InteropServices capability into the marketplace is pretty low, I think. Without that capability, you can't access COM, which means no native code, which means no registry editing.

GoodDayToDie said:
The odds of being able to sneak any app with the InteropServices capability into the marketplace is pretty low, I think. Without that capability, you can't access COM, which means no native code, which means no registry editing.
Click to expand...
Click to collapse
I am just guessing here, but can't you download a dll file to the isolatedStorage, then on the next app start use that file (for example the samsung dll to edit registry keys used by samsung "root" tools)?

hounsell said:
I'm just guessing here, I haven't actually done any research into it, but I believe the patch was relating to the certificate - aimed at the fact that ChevronWP7 relied on WP7 accepting an untrusted certificate being used by the unlocking server if that certificate had been installed to the phone's store. Simply doing some basic checking on the certificate to ensure it's from a trusted authority for example, is probably the route Microsoft took, or something along those lines.
I'm kinda busy with other things right now, but I'll have to get a copy of a NoDo ROM at some point and take a peak at the relevant files.
Click to expand...
Click to collapse
Ok.. Think with me please.. I am by no means a HTTP or SSL expert, but I know a little bit about it. So please correct me if I'm wrong.
HTTPS is HTTP over SSL. SSL does a handshake for encryption keys. Any HttpListener will support this. And SSL with mutual authentication will also do a certificate check. Tom, if what you said is true, then we should install a genuine certificate for developerservices.windowsphone.com. I'm sure some devs have one laying around for us to use. The phone will accept it, because a certified authority has issued it. That would solve things at the end of the WP7 device.
Now the important part. As far as I know, but I may very well be wrong about this, the certificate is only verified on the end of the server. In this case that would be our own HttpListener on the local PC with the hosts-file containing a mapping for developerservices.windowsphone.com to 127.0.0.1. I think the WP7 device does not validate the server, isn't it? So when we let our server accept the certificate, we're done. We can let it accept the certificate with this line of code:
Code:
ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };
Would that do the trick???
Ciao,
Heathcliff74

eried said:
I am just guessing here, but can't you download a dll file to the isolatedStorage, then on the next app start use that file (for example the samsung dll to edit registry keys used by samsung "root" tools)?
Click to expand...
Click to collapse
I'm guessing now. But I think the capabilities are stored somewhere. And if you didn't have the Interop-capability when you installed the app, you will still not be able to load a COM-dll later on. Also, I don't think you will be able to call LoadLibrary on a file in the IsolatedStorage.
And in my WP7 Root Tools, there are NO Samsung dll's. Only my own code. Both native and managed dll's are written 100% by me. No copyrighted dll's from another party in my code. I explicitly avoided that, because my app will never be banned for that reason. I think Julien Schapman's Windows Phone Device Manager does ship the HTC dll's (not 100% sure about that though). I think he might have a problem with that if he ever want to sell his product.
Ciao,
Heathcliff74

Heathcliff74 said:
Now the important part. As far as I know, but I may very well be wrong about this, the certificate is only verified on the end of the server. In this case that would be our own HttpListener on the local PC with the hosts-file containing a mapping for developerservices.windowsphone.com to 127.0.0.1. I think the WP7 device does not validate the server, isn't it? So when we let our server accept the certificate, we're done. We can let it accept the certificate with this line of code:
Code:
ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };
Would that do the trick???
Ciao,
Heathcliff74
Click to expand...
Click to collapse
Just a guess here, but I would say that it's the phone who verify the certificate, not the server. That's why you had to install the chevron cert on the phone.

Im not up to date on how these certificates work and where or how they are approved and if there is a difference between certain certs but i was wondering about the cert that we used by xboxmod when he released those omnia apps for all devices or was that just another way to get xaps to work instead of resigning them? Could it be used if not?

I did a bit of reading up on SSL and certificates. I'm still not sure about alot of things, but this is what I get from it:
SSL sets up a secure transport layer by exchanging encryption-keys. And it also supports client-authentication and server-authentication. Authentication can take place by letting one party send its certificate and let the other verify it. For a client this usually means that the issuing party sent a generated certificate against which it can be authenticated. A server is authenticated by its certificate. The certificate needs to be verified. The verification is done by checking the certification-path. The issuers must be trusted by the verifying device. I'm not sure, but I don't think it is normally necessary to install a certificate when you genuine unlock your device. If it is necessary, then that means that the unlock server from Microsoft does client-authentication too. But that is not important when we want to spoof that server with a http-server on our localhost (like ChevronWP7), because we can just skip the client-authentication. We simply don't care about that.
(nico) said:
Just a guess here, but I would say that it's the phone who verify the certificate, not the server. That's why you had to install the chevron cert on the phone.
Click to expand...
Click to collapse
I think the unlocking software on the WP7 device probably does something like this (pseudo-code):
Code:
if (!SecureConnection.Server.IsTrusted())
{
LockDevice();
return;
}
If the server is not trusted, the unlock will fail. So Chevron has its own built-in http-server. With its own certificate. Except that certificate is normally not trusted by the WP7 device, because that certificate is not signed/issued by one of the Certified Authorities that is known by the device. So in order to let the IsTrusted() succeed, a certificate must be installed on the device first. That certificate adds the signing authority (self-signed by Chevron) to the trusted authorities.
Now in NoDo, if Tom is right, Microsoft changed it into something like this:
Code:
if (!SecureConnection.Server.IsTrustedByCertifiedAutority())
{
LockDevice();
return;
}
That means, that it does not only verify if it is trusted, but the top of the certification-path must be a Certified Authority. In this case a self-signed certificate is not accepted anymore.
I have access to the certificate-stores on my Samsung Omnia 7. But for that the device needs to be unlocked. So, that is not useful for unlocking devices. And that exploit only works on Samsung devices.
Now that I understand this better, I see that my previous proposal won't work. But it gives me something to think about. Got to get a way around that.
lucasryan said:
Im not up to date on how these certificates work and where or how they are approved and if there is a difference between certain certs but i was wondering about the cert that we used by xboxmod when he released those omnia apps for all devices. Was that a cert that just allowed us to use those apps to work on other devices just like we do now by resigning a xap to work from another brand, or is it a cert that might could be used?
Click to expand...
Click to collapse
That was some developer-certificate from the WinMo 6.5 SDK or something. It didn't really do anything other than invalidating the signature, which in combination with removal of the DRM file in the XAP would remove the DRM-protection. It works even better to simply remove the certificate from the file. The certificate was simply to replace the valid certificate with an invalid one. The certificate from xboxmod is not of any use here.
Ciao,
Heathcliff74

ok I understand now how they work and what it needs to be. Alot more to it than i was thinking, so there is a chance to find a cert somewhere. somehow.

Very good information, I am not too much into SSL security also. I have an Idea for a new unlocker (not based in chevron's method):
Someone in a Marketplace-enabled country buys a subscription
An application uses that subscription + the code inside the Developer unlock application to unlock a phone
Then the same application deploys (and executes) a xap (like samsung tools) to prevent the device relocking
The same application then deletes the device from the developer account
So, with a minor cost, we can have unlocked phones. I don't know if the dev account can get blocked if the user unlocks and "relocks" a lot of devices, but if one account is good for 10 phones, its fine ($10 usd each unlock)

lucasryan said:
ok I understand now how they work and what it needs to be. Alot more to it than i was thinking, so there is a chance to find a cert somewhere. somehow.
Click to expand...
Click to collapse
No. These are the best kept secrets in the industry. When those key leak a lot of DRM is compromised. And in most systems certificates, once compromised, can be revoked (through updates that are pushed or pulled). The ChevronWP7 guys did a brilliant job in finding the loophole in the server-authentication. I think Microsoft has closed that one now. But maybe there's another loophole in the unlocking system.
There might also be other attack-vectors. If we can get XML-provisioning working from outside the device we can set the registry-values to unlock the device. Maybe OTA Provisioning can be done with WP7 devices.
Another possibility for XML provisioning can be found in this dll:
Code:
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
You can open it in Reflector. There's a class called DevicePackageClass. It has a method called ProvisionDeviceXML(). So I tried using it, but when I instantiate the DevicePackageClass it gives me an error:
Retrieving the COM class factory for component with CLSID {E987B9DE-8471-11DB-96A9-00E08161165F} failed due to the following error: 80040154 Class not registered (REGDB_E_CLASSNOTREG)
The class is actually a wrapper for a COM class. So I looked it up in the registry. It seemed to be found in this dll:
Code:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\dip.dll (VSD Device Integration Package)
But is actually part of Visual Studio 2008, not Visual Studio 2010. The dip.dll is not installed with Visual Studio 2010. So I figured I might have a better chance with this dll:
Code:
C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.DeviceConnectivity.Interop.9.0\9.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.DeviceConnectivity.Interop.9.0.dll
But it gives me the same error. I also tried to register dip.dll with regsvr32. The registration worked, but the error was still the same. I even tried to access dip.dll directly, but I still couldn't create the COM class DevicePackageClass ("Can't create object").
So if we can somehow instantiate that class we might get XML provisioning working and unlock the device directly in the registry. Needs more research.
Ciao,
Heathcliff74

eried said:
Very good information, I am not too much into SSL security also. I have an Idea for a new unlocker (not based in chevron's method):
Someone in a Marketplace-enabled country buys a subscription
An application uses that subscription + the code inside the Developer unlock application to unlock a phone
Then the same application deploys (and executes) a xap (like samsung tools) to prevent the device relocking
The same application then deletes the device from the developer account
So, with a minor cost, we can have unlocked phones. I don't know if the dev account can get blocked if the user unlocks and "relocks" a lot of devices, but if one account is good for 10 phones, its fine ($10 usd each unlock)
Click to expand...
Click to collapse
Microsoft scans the apps that are submitted for the marketplace. I doubt very much this will ever pass through. And if it will Microsoft will block it as soon as they find out. And it also needs the InteropService capability, which will never be allowed in the Marketplace.

Heathcliff74 said:
Microsoft scans the apps that are submitted for the marketplace. I doubt very much this will ever pass through. And if it will Microsoft will block it as soon as they find out. And it also needs the InteropService capability, which will never be allowed in the Marketplace.
Click to expand...
Click to collapse
My idea was not an app for the marketplace but a desktop app like Chevron

eried said:
My idea was not an app for the marketplace but a desktop app like Chevron
Click to expand...
Click to collapse
Ohw. Sorry. Misunderstood. I get what you meant. But you're gonna need new dev-accounts all the time. Everytime Microsoft will block one dev-account after a certain amount of unlocks, you'll have to get a new one. Who is willing to get all these accounts? This will probably run out very fast.

Heathcliff74 said:
Ohw. Sorry. Misunderstood. I get what you meant. But you're gonna need new dev-accounts all the time. Everytime Microsoft will block one dev-account after a certain amount of unlocks, you'll have to get a new one. Who is willing to get all these accounts? This will probably run out very fast.
Click to expand...
Click to collapse
Of course, but I personally don't have a problem about paying $10-$40 usd to unlock my device. Even $100-$200 seems fair to me for the complete developer account, but I can't pay here in Chile

eried said:
Of course, but I personally don't have a problem about paying $10-$40 usd to unlock my device. Even $100-$200 seems fair to me for the complete developer account, but I can't pay here in Chile
Click to expand...
Click to collapse
Personally I don't like the idea, that I just bought a device of €550 and I have to pay another €100 to actually be able to have control over the device. I also needed to put in countless hours of work to get access to my system and to be able to set the colordepth for instance.
To be real honest, I really don't like the locked-down nature of the device. I liked Microsoft for their open systems (not open source, but highly customizable etc). And I also highly appreciate their developer tools and SDKs. And I love Silverlight. But if I would have known that the phone was so much locked down, I may have considered a Samsung Galaxy S instead of Samsung Omnia 7. Both great phones with super AMOLED etc. WP7 looks much better than Android, but Android is an open OS, which I would prefer. I think Microsoft should have made 2 flavors of WP7; one locked down version for the privacy-freaks and an open version for the tweakers. Anyway, I have the Omnia 7 now with WP7. And I will get it open, even if I have to break it open myself.

Heathcliff74 said:
Personally I don't like the idea, that I just bought a device of €550 and I have to pay another €100 to actually be able to have control over the device. I also needed to put in countless hours of work to get access to my system and to be able to set the colordepth for instance.
To be real honest, I really don't like the locked-down nature of the device. I liked Microsoft for their open systems (not open source, but highly customizable etc). And I also highly appreciate their developer tools and SDKs. And I love Silverlight. But if I would have known that the phone was so much locked down, I may have considered a Samsung Galaxy S instead of Samsung Omnia 7. Both great phones with super AMOLED etc. WP7 looks much better than Android, but Android is an open OS, which I would prefer. I think Microsoft should have made 2 flavors of WP7; one locked down version for the privacy-freaks and an open version for the tweakers. Anyway, I have the Omnia 7 now with WP7. And I will get it open, even if I have to break it open myself.
Click to expand...
Click to collapse
Nobody likes a locked device.
But I do understand the Microsoft posture about this.

[Q] PREVIEW Mango update with student developer account?

As the title suggests... i have a student developer account with APP HUB, can I update PREVIEW mango version (released/releasing these few days) with my phone still?
As i know, currently its the "paid" developers that have access to Preview mango update.
Let me know~ really hoping this works!!

i want to know too please

toothfish said:
As the title suggests... i have a student developer account with APP HUB, can I update PREVIEW mango version (released/releasing these few days) with my phone still?
As i know, currently its the "paid" developers that have access to Preview mango update.
Let me know~ really hoping this works!!
Click to expand...
Click to collapse
Student App Hub accounts are identical to normal App Hub accounts.

nop they are not, they are similair but different.

I dont think the beta is coming as soon as they said
https://twitter.com/#!/BrandonWatson/status/83158862823297025

Rats...... but thanks for the update~

The update is indeed for paid and registered mango beta testers. So you do not only have to have a paid account, but you also need to be registered for beta testing Mango.
Further more, if you are such developer and you upgrade to Mango, be aware that there are new limitations to sideloading! Many homebrew tools and OEM tools won't be possible to sideload anymore.
When the moment is there that the update is available (not tomorrow), and you do decide to upgrade, I really want to ask everyone to capture the traffic during the update-process with Wireshark. If we have as much captures as possible, we can possibly create our own updater, like Chris Walsh did with NoDo. But we do need as much captures as possible to see which phones get which rom-packages. We should avoid half updates like in the original tool from Chris Walsh.
If you have a capture of the update, please post here.
Thanks,
Heathcliff74

Heathcliff74 said:
The update is indeed for paid and registered mango beta testers. So you do not only have to have a paid account, but you also need to be registered for beta testing Mango.
Further more, if you are such developer and you upgrade to Mango, be aware that there are new limitations to sideloading! Many homebrew tools and OEM tools won't be possible to sideload anymore.
When the moment is there that the update is available (not tomorrow), and you do decide to upgrade, I really want to ask everyone to capture the traffic during the update-process with Wireshark. If we have as much captures as possible, we can possibly create our own updater, like Chris Walsh did with NoDo. But we do need as much captures as possible to see which phones get which rom-packages. We should avoid half updates like in the original tool from Chris Walsh.
If you have a capture of the update, please post here.
Thanks,
Heathcliff74
Click to expand...
Click to collapse
Any How to for capturing the traffic, I'm sure tons of people would like to participate if it was easy. Just start Wireshark and upload the log and that's it?

Yeah man, I'm willing to give this a shot when the update comes out, more than willing for the community... jejeje
I would like to know how to do this. I can post whatever comes out... I have an Arrive... We shall see... jejeje
Sent from my []D[][]V[][]D ARRIVE using Board Express

Heathcliff74 said:
The update is indeed for paid and registered mango beta testers. So you do not only have to have a paid account, but you also need to be registered for beta testing Mango.
Further more, if you are such developer and you upgrade to Mango, be aware that there are new limitations to sideloading! Many homebrew tools and OEM tools won't be possible to sideload anymore.
When the moment is there that the update is available (not tomorrow), and you do decide to upgrade, I really want to ask everyone to capture the traffic during the update-process with Wireshark. If we have as much captures as possible, we can possibly create our own updater, like Chris Walsh did with NoDo. But we do need as much captures as possible to see which phones get which rom-packages. We should avoid half updates like in the original tool from Chris Walsh.
If you have a capture of the update, please post here.
Thanks,
Heathcliff74
Click to expand...
Click to collapse
ok,i'm with an apphub account(student) so the mango update for developers will be available on the dowload section directly on apphub(like the mango SDK 7.1) or i have to register my device ID to my account?
i couldn't myself,it's microsoft to register my device ID to my apphub account it is?

Heathcliff74 said:
When the moment is there that the update is available (not tomorrow), and you do decide to upgrade, I really want to ask everyone to capture the traffic during the update-process with Wireshark. If we have as much captures as possible, we can possibly create our own updater, like Chris Walsh did with NoDo. But we do need as much captures as possible to see which phones get which rom-packages. We should avoid half updates like in the original tool from Chris Walsh.
If you have a capture of the update, please post here.
Thanks,
Heathcliff74
Click to expand...
Click to collapse
I think they'll do something similar to the XBox Dashboard Previews, meaning that ultimately you'll be able to install mango preview on any device, but they'll enable Windows Live sign-in only for registered devices, server side.
Unfortunately Microsoft has always been *****y about these preview things.

blindpet said:
Any How to for capturing the traffic, I'm sure tons of people would like to participate if it was easy. Just start Wireshark and upload the log and that's it?
Click to expand...
Click to collapse
I'm no expert in Wireshark. I know how to use it for my own purposes. So this is what I would do, but if someone else has additional suggestions, feel free to help. The updates are over standard http, not https, so that makes it easier.
- Connect your phone to your computer and wait for Zune to be ready with sync.
- Download and start Wireshark.
- Select the network-interface you want to log (to be sure keep only one network-interface enabled, just to be sure you'll capture the correct interface).
- To be sure you capture the traffic from the phone too, go to menu Edit / Preferences. Select User Interface / Capture. And enable option Capture packets in Promiscuous Mode.
- To filter all unwanted data type this in the Filter textbox: http && !tcp.analysis.out_of_order && !tcp.analysis.retransmission
- Start update with Zune.
- When the update is ready, stop the capture and save it to a file.
To test if this works, do the above and use Internet Explorer on your phone. You should see the traffic in Wireshark.

hd2leo_fusion said:
ok,i'm with an apphub account(student) so the mango update for developers will be available on the dowload section directly on apphub(like the mango SDK 7.1) or i have to register my device ID to my account?
i couldn't myself,it's microsoft to register my device ID to my apphub account it is?
Click to expand...
Click to collapse
I clearly said it was for paid and registered developers. Have you paid for your student account? Guess not. So unfortunately this beta is not going available for you. Even if you would register as a beta-tester. I wouldn't know how to do that anyway, because I haven't done that.

Heathcliff74 said:
I clearly said it was for paid and registered developers. Have you paid for your student account? Guess not. So unfortunately this beta is not going available for you. Even if you would register as a beta-tester. I wouldn't know how to do that anyway, because I haven't done that.
Click to expand...
Click to collapse
Thats interesting... May I ask where you have that information from? I could not find anything on the create.msdn.com (app hub) forums about it. Was it in the news section somewhere?
Quite odd they wont give it to students.

Marvin_S said:
Thats interesting... May I ask where you have that information from? I could not find anything on the create.msdn.com (app hub) forums about it. Was it in the news section somewhere?
Quite odd they wont give it to students.
Click to expand...
Click to collapse
Many sources:
one
two
three
four
......
Ciao,
Heathcliff74

Heathcliff74 said:
Many sources:
one
two
three
four
......
Ciao,
Heathcliff74
Click to expand...
Click to collapse
Yes read those, it does not specifically says student accounts wont get it. Brandon watson also tweeted "@arnehelseth Every developer matters. Every. Single. One. Deep breath everyone". Don't know if this means something and is in the right context or not.
The articles just say it will be released to developer unlocked apphub account, which you can normally get by paying 99$ (they dont speak about student unlocks in particular).
"Neowin has received multiple independent tips that the beta will be made available for all devices through the MSDN Create hub for those with developer accounts, on June 22/23, with Microsoft set to make the announcement sometime during the next 24 hours. The beta will not be restricted to "favorite" developers but will be generally available to anyone with a paid subscription, and will be able to be loaded on any of the production devices."
Yes it indicates paid subscription, however does not really rule out student subscriptions since they are pretty much equal to MS. I dont know if we have to take these words literally or if its quickly written.
"The software giant will also offer beta bits for developers to load directly onto their devices, reports Neowin. Mango ROMs will be made available to existing Windows Phone developers via Microsoft’s App Hub development program. Access to the developer program is charged at $99 per year."
Students have free access to the App Hub development program.
I could not find where you need to sign up for the beta, have not read a mention about this. I could not find it in these sources.
You are probably right though that its only for paid subscriptions, since its easier to check who is a ginuine dev. I just wondered since I have not seen a clear "No to student account" post so I was not really sure about what to believe. Thank you for the clearification.

All sources I read stated that you need to have a paid registration. So it does not say 'no students' but students don't pay, so I guess that rules it out.
About the registered Mango beta tester, I don't see it right now, but I'm sure I've read that.
Anyway, we'll wait and see. Speculating now is not of much use.

Heathcliff74 said:
All sources I read stated that you need to have a paid registration. So it does not say 'no students' but students don't pay, so I guess that rules it out.
About the registered Mango beta tester, I don't see it right now, but I'm sure I've read that.
Anyway, we'll wait and see. Speculating now is not of much use.
Click to expand...
Click to collapse
True, and they can always make a change of heart. Thanks we will see. If students get it, ill try and log the process with wireshark.

Marvin_S said:
True, and they can always make a change of heart. Thanks we will see. If students get it, ill try and log the process with wireshark.
Click to expand...
Click to collapse
Ok. That would be cool. But I have to stress again: If you upgrade to Mango, be aware that there are new limitations to sideloading! Many homebrew tools and OEM tools won't be possible to sideload anymore. So if that is a problem for you, then you shouldn't upgrade. What would be interesting to know is, if you have such software that uses native code (like WP7 Root Tools, TouchXplorer, Screencam, etc) already on your phone, will it still be possible to use it after the upgrade?? And.. will the ChevronWP7 unlock survive the upgrade if you have to "prevent relock tweak" applied??

Heathcliff74 said:
Ok. That would be cool. But I have to stress again: If you upgrade to Mango, be aware that there are new limitations to sideloading! Many homebrew tools and OEM tools won't be possible to sideload anymore. So if that is a problem for you, then you shouldn't upgrade. What would be interesting to know is, if you have such software that uses native code (like WP7 Root Tools, TouchXplorer, Screencam, etc) already on your phone, will it still be possible to use it after the upgrade?? And.. will the ChevronWP7 unlock survive the upgrade if you have to "prevent relock tweak" applied??
Click to expand...
Click to collapse
Yes I know. Thats what I wonder as well. Since we could use OEM apps added trough the marketplace. So upgrading with these apps in place might work. Ill also make a few zune backups so I can roll back just in case.
If roottools still works we might be able to set the prevent relock again. Im wondering about the sideload limit, because thats the most annoying thing for me. 3 is not much to sideload and I like to keep the apps Im developing on my phone to test them on the road.
Well Im trying not to get my hopes up for Mango anytime soon, but if its for students also Ill give it a shot. And I can maybe PM you before, if you can think of some things you want me to test out for you.