Hello everyone. I have a problem with MSN on my XDA: it doesn't connect. It says that the service is not avaiable at the moment. I'm using XDA-Dev latest rom.
I know the msn service *is* working because if i try with my Pocket PC ViewSonic V35 it works...
Any suggestions?
Thanks,
Daniel
Try installing the MSN Messenger Updates for Pocket PCs
http://www.microsoft.com/windowsmobile/resources/msnmessenger/pocketpc.mspx
HTH
Already done but..
Already Installed. But I still get "service temporarily unavaiable". Any suggestions?
uninstall/reinstall the update
Already tried 10 times. No results...
My friend had that problem, reset the XDA (ie push the stylus in the hole, not hard reset) first, then install the update, reset again, then try signing in.
Related
hi there,
ok i just picked up my xda of a colleague at work but unfortunately he cant find the software. does anyone know where i can download the latest software and drivers so that i can connect this up to my pc?
It also has his settings on it and so i want to erase all his settings and start again from fresh?
i have checked out the 02 site but this only has updates.
I have the o2 xda2
PLEASE HELP!!!!
For connecting to your PC you need ActiveSync. You can get it directly from Microsoft for free.....
Makeing the xda clean can be done by hard reset. After the hard reset all settings will be ghone and you will have a fresh and clean ROM...
HTH
Stefan
Okay i was following the instructions here
http://forum.xda-developers.com/viewtopic.php?t=16916
on my vmware workstation running under Linux
I opened up the himaupgrade.exe put in the apporiate files and then sync my device and click upgrade... shortly after i notice that the usb icon in vmware wasnt active and then my pocket pc went blank
after a while the upgrade reported that it failed, active sync said it had no connected devices and my pocket pc when put infront of light had USB writng on the top and v1.06 writtin on the bottom
now it said in the install to soft restet it plug it back into the cradle and continue the installation. so i soft reset it.. it did nothing -_- so then i hard resetted it and it the writing on the screen starts to fade then it comes back.. so out of desperations i removed the battery and it seams that its still going hard on the backup battery with the same text
now i got nothing.. my pocket pc wont start up at all and thus theres no way to conintue the update to make it work
so im asking you smart xda people out there.. how on earth do i make it work again, do i have to send it into imate to get it repaired!! im lost and have no idea this is my first time doing a new rom on this webpage
PLEASE
*gets on knees and begs*
tama(?),
you are stuck in bootloader mode. The device should still be detected when you put it in the cradle. Once that has happened you can either run the Himaupgrade once more and try it once more or install the original ROM through the executable (on CD?) you should have got from your vendor.
whoa im pretty please with that time it tock for a reply ^_^
anyways iv connected the device to my vmware windows 2000 pro and active sync detects it is there and sits on "connecting"
so far due to it being on connection the updates on this site arent working, im going to try the one on the cd now
okay everythings been working fine now for a while ill just some people advice out there..
you cannot upgrade your rom using a virtal machine in Vmware running on Linux
i had to use another computer running windows and it worked first time..
thanks a lot
Also worked for me!!
Restore back to 1.66
Ladies and gentlemen out there... please help.
I foolishly tried to upgrade my O2 Xda II and now I reset more often. Everytime I reset it says "IIs" on the bottom. Plus the buttons seem configured for the IIs. Further, the unit no longer is recognized by my desktop. I have spoken to the local distributor and local repair center here in Manila and both have said that restoring the unit back to 1.66 is possible BUT it similarly might cause the unit to "die" (be a dead unit). A result that is simply unacceptalbe, given I use my unit heavily for work. Please help.
If you are based in Manila, I would greatly appreciate an SMS response to the question below. Kindly SMS the following mobile numbers; +63920.928.3385 and/ or +63917.855.7599, with my "+63920" number being the primary number to send to.
So, is it possible to restore a unit from a 2.0-something back to 1.66 without the unit dying on me? If yes, how do I do this?
Cheers! Thanks!
so im having alot of problems with my G4 now.
I flashed to pdaviet3
my contact window doesnt pop up
It will not establish a connection to active sync (but it does detect it)
I get the cannot run timewizard.exe message
my g4 tries to use ",usb" to connect. could that be the problem?
bowlopho said:
so im having alot of problems with my G4 now.
I flashed to pdaviet3
my contact window doesnt pop up
It will not establish a connection to active sync (but it does detect it)
I get the cannot run timewizard.exe message
Click to expand...
Click to collapse
I had exactly the same problem! "cannot run timewizard.exe" appeared every time i tried to get off stand-by. Most propably you followed directions in this topic http://forum.xda-developers.com/showthread.php?t=293480&page=10.
Try doing the same thing again(flashing pdaviet3). Start by rerunning enableRAPI(in short follow directions described in the flash tool contained in the above post). I did the same thing and everything went ok second time. Then, i did a hard reset(after i took a backup), by going "start->settings->clear storage".
Hope this helps
I can't reflash if i cant connect to active sync. unless you know a different way...
bowlopho said:
I can't reflash if i cant connect to active sync. unless you know a different way...
Click to expand...
Click to collapse
Most propably, you need ActiveSync 4.5 Beta 2 (Download it easily from M$ site). WM6 doesn't wotk with ActiveSync 4.2. Try it and keep us posted
first time i tried to connect it told me I had to install activesynch 4.4+ or 4.5+ or something, so i dl'd it but i had to run out for a few hours.
So when i got home, still no luck. It starts to detect but then it just wont connect.
Well since i just "cleared storage" things have been working now
I got that timewizard error once but it closed itself real fast, also now get my contact list up
wont know if active sync works for another 8 hours =/ just got to work.
bowlopho said:
first time i tried to connect it told me I had to install activesynch 4.4+ or 4.5+ or something, so i dl'd it but i had to run out for a few hours.
So when i got home, still no luck. It starts to detect but then it just wont connect.
Well since i just "cleared storage" things have been working now
I got that timewizard error once but it closed itself real fast, also now get my contact list up
wont know if active sync works for another 8 hours =/ just got to work.
Click to expand...
Click to collapse
At least things are working now. Activesync beta, becomes unstable sometimes and it fails to connect to the PPC(as you describe). The only solution for me, is to reinstall it(not a big problem for me), but anyway... it's still beta(as all M$ products )
Eagerly awaiting JB update for my unlocked, stock I9300 (UK BTU).
Trying to do things "by the book" and using KIES to check for updates.
Yesterday KIES announced that it needed to do some kind of update related to firmware...
Now, whenever I try to connect it reports "failed to retrieve device information" and doesn't connect.
I've tried re-installing KIES, and it managed to connect once, after which I get the same message whenever I try again.
I've tried disabling antivirus etc and using their connection troubleshooter, all to no avail.
NOT HAPPY; very bad time for this to happen.
OS is windows 7 64 bit.
Anyone else with the same problem? Ideas?
Thanks
fasty said:
Eagerly awaiting JB update for my unlocked, stock I9300 (UK BTU).
Trying to do things "by the book" and using KIES to check for updates.
Yesterday KIES announced that it needed to do some kind of update related to firmware...
Now, whenever I try to connect it reports "failed to retrieve device information" and doesn't connect.
I've tried re-installing KIES, and it managed to connect once, after which I get the same message whenever I try again.
I've tried disabling antivirus etc and using their connection troubleshooter, all to no avail.
NOT HAPPY; very bad time for this to happen.
OS is windows 7 64 bit.
Anyone else with the same problem? Ideas?
Thanks
Click to expand...
Click to collapse
same think happened to me with KIES. I managed to fix it by couple of times applying that fix connectivity problems thingy from the menu. I've had to reboot the phone too.
You might also want to try re-installing samsung drivers for
nolovelust said:
same think happened to me with KIES. I managed to fix it by couple of times applying that fix connectivity problems thingy from the menu. I've had to reboot the phone too.
You might also want to try re-installing samsung drivers for
Click to expand...
Click to collapse
Thanks for the advice. I tried re-installing KIES and the drivers but it only connected once after their "necessary update"
I'm sure that it's this latest KIES update that has screwed it; was fine until today.
When I tried the troubleshooting wizard, it then told me it was an incompatible phone ;-(
Hopefully if it's a common problem, Samsung might eventually recognise and fix it.
I heard KIES was flakey, now I know :laugh:
OK, I think that I have hopefully found a solution.
I started KIES by right-clicking the icon and chosing "run as administrator" instead of the usual way.
Now everything seems back to normal.
I suspect that their "update" may have messed up access rights in some way beyond my understanding:laugh:
Now it apparently connects consistently OK in the usual way.
I have the same problem driving me mad!
For some reason I can't update OTA I get this message
So I thought hey might try that program kies heard the updates are better too because they do a clean install of them. But it is horrendous!!
I want my update!
Sent from my GT-I9300 using xda app-developers app
After much struggle I tried the run as admin a few times. And it worked once! Just got the update I am blown away how good it is soo far!
I hope everyone gets it soon
Sent from my GT-I9300 using xda app-developers app
I am using a Galaxy S9+ running the latest version of SoldierROM (PIE, rooted) and I have been trying to use MirrorLink for a while now but it just refuses to work.
When I connect my phone to my car and choose MirrorLink, a couple of prompts pop-up that I accept and then the certificate fails to download.
I have tried updating to Android 10 and doing that, but the certificate still fails. Is it because I am rooted?
Someone posted about the same issue on XDA, but none of the solutions posted worked for me.
Thanks, guys!
TarekElsakka said:
I am using a Galaxy S9+ running the latest version of SoldierROM (PIE, rooted) and I have been trying to use MirrorLink for a while now but it just refuses to work.
When I connect my phone to my car and choose MirrorLink, a couple of prompts pop-up that I accept and then the certificate fails to download.
I have tried updating to Android 10 and doing that, but the certificate still fails. Is it because I am rooted?
Someone posted about the same issue on XDA, but none of the solutions posted worked for me.
Thanks, guys!
Click to expand...
Click to collapse
Hi, try this:
Go to the app mirrorlink 1.1 and there to the storage. Here you Clear the data and the cache. Then connect once again your mobile with the car. The should ask for download again new fresh certificates. Not every time it works for every app, but then start again.
Hope it will help!
bikerSU said:
Hi, try this:
Go to the app mirrorlink 1.1 and there to the storage. Here you Clear the data and the cache. Then connect once again your mobile with the car. The should ask for download again new fresh certificates. Not every time it works for every app, but then start again.
Hope it will help!
Click to expand...
Click to collapse
Thanks a lot for your reply. Unfortunately, I tried that many times without success, so I am assuming it might have to do with my device always being flagged as rooted even when I restore everything to stock.
I have the same phone with the same problem... did you manage to fix it?
Same issue over here. It would be nice to have a fix for this.
Now that Samsung wisely decide to drop support for MirrorLink, is there any work around this?
I have Note 9 and I just bought my frist car. It was jaw droping to see how bad samsung is! I just connect my phone I see certificate download error for MirrorLink 1.1.