i cannot find this in the marketplace.. anyone have a link to the xap?
professorwol said:
i cannot find this in the marketplace.. Anyone have a link to the xap?
Click to expand...
Click to collapse
yes but it will not run the setup when you upgrade to mango
It is not working in mango anymore..... Just side loaded it when you click it it goes black then closes..... I think mango blacklisted it?????
It was there a few days ago when I first upgraded to Mango. It installed but would not run (said carrier not found). Hopefully they pulled it until they get it upgraded and it comes back.
i can´t find Compass too..
Did you look in the system settings, thats where I found it
Just did the HTC Hub update and it is still not there.
LiFePo4 said:
Just did the HTC Hub update and it is still not there.
Click to expand...
Click to collapse
it has been removed
only God knows the reason why it was removed
HTC Surround originally on Telus, used Connection Setup to reconfigure for Rogers. Updated to Mango, now I've lost 3G. With no access to Connection Setup, I can't re-enable data. Any ideas?
JBC2005 said:
HTC Surround originally on Telus, used Connection Setup to reconfigure for Rogers. Updated to Mango, now I've lost 3G. With no access to Connection Setup, I can't re-enable data. Any ideas?
Click to expand...
Click to collapse
Go back to your backup made right before the update, then uninstall Connection Setup before you update. If it is installed it tries to run when the update finishes and you lose 3G. This is probably the main reason it has been pulled as it does not work on final Mango.
Could not restore to backup because I replaced the 16 GB SD card with an 8GB! I flashed stock Telus Rom with Nodo, and then flashed DFT 7720 Rom. Phone now works great (my wife is currently enjoying Angry Birds on it!)
LiFePo4 said:
It was there a few days ago when I first upgraded to Mango. It installed but would not run (said carrier not found). Hopefully they pulled it until they get it upgraded and it comes back.
Click to expand...
Click to collapse
Yea, if you updated to the newest version, it gives that error.
If you ran the older version (non updated), it will run your provxmls BUT, on verizon you would lose 3G service totaly, Hard reset or reflash rom would be the only fix (tried a lot of stuff).
It needs to be upgraded for mango but, the good old days of doing reg edits I think is over for HTC devices with this.
DavidinCT said:
Yea, if you updated to the newest version, it gives that error.
If you ran the older version (non updated), it will run your provxmls BUT, on verizon you would lose 3G service totaly, Hard reset or reflash rom would be the only fix (tried a lot of stuff).
It needs to be upgraded for mango but, the good old days of doing reg edits I think is over for HTC devices with this.
Click to expand...
Click to collapse
At this point I am going to wait and see if they release an updated version and then hope my provxml file is still sitting there. I had uninstalled it before upgrading so it did not try to run and I have 3G, then went to the HTC Hub and downloaded what was there which failed to run (and has since been pulled).
AFAIK the provxml file should still be sitting there waiting to get "provisioned"
Is there anyway to get connection setup back on without using marketplace?
Im wanting to upgrade to mango keeping unlock through zune but i cant without this.
dingodog said:
Is there anyway to get connection setup back on without using marketplace?
Im wanting to upgrade to mango keeping unlock through zune but i cant without this.
Click to expand...
Click to collapse
is this what you are looking for? The package contains HTC Connection Setup v. 1.5.0.0.
derausgewanderte said:
is this what you are looking for? The package contains HTC Connection Setup v. 1.5.0.0.
Click to expand...
Click to collapse
Hi derausgewanderte,
Yes this is the correct packages although would "HTC connection setup" still work after it has been sideloaded if i upgrade to mango and the device relocks?
I think ill have to wait it out untill it becomes available in marketplace again or another way is found to unlock mango.
Hi ALL,
Here is a step by step guide that have all u need to update to Mango and still Sideload and still have HTC Connection Setup working:::
http://forum.xda-developers.com/showthread.php?t=1287505
Hope I Have Been Of Help. PEACE!!!
Related
I have previously upgraded to RWE wm6, now the official ATT upgrader says "you have a newer version of this software" and wont update to the latest ROM. Any suggestions to fool the updater and install official WM6 release?
Thanks in advance- this forum always amazes me!!
Is a simple edit of the payload file all thats needed here?
File Edit
DocKill said:
I have previously upgraded to RWE wm6, now the official ATT upgrader says "you have a newer version of this software" and wont update to the latest ROM. Any suggestions to fool the updater and install official WM6 release?
Thanks in advance- this forum always amazes me!!
Is a simple edit of the payload file all thats needed here?
Click to expand...
Click to collapse
Yes.
http://forum.xda-developers.com/showthread.php?t=345531
Thanks
Awesome as always!! Thanks!!!!
Next question....Installer gets through initial phase, treo gets 4 dark colored bars, then connection is lost and install cant complete. I tried removing the SD card-no luck. Advice ?
Thanks again
I got the same problem , after the erase all data it just froze up ..... is it bricked. hopefully someone can help
I also had the same problem with my device but what i did is switch computers with Windows xp and with Activesync 4.5 that should do the trick
fixed
installed from XP instead of Vista...no problem at all. Appears Vista has trouble with recognizing the treo after loses activesync connection
seems my problem had to do with the unit, i did the sdupdater recovery tool from palm to no avail, finally i removed the battery and reinserted it and bam WM6 appeared after numerous attempt at upgrade and different ROMS tried. I asume the original upgrade got stuck and the removal of the battery, helped it finish. Who knows at least its not bricked
sideloading has suddenly stop working for me, the Chevron app shows that I am unlock but I keep receiving the same error as if the device had never been connected to my PC. the only thing that has changed to my system (PC) was the Mango update. I uninstalled and reverted back to the old zune software to in case it was the new update. I even started over with a different phone that is currently pre NoDo and still no luck. and no skype running
alijahg34 said:
sideloading has suddenly stop working for me, the Chevron app shows that I am unlock but I keep receiving the same error as if the device had never been connected to my PC. the only thing that has changed to my system (PC) was the Mango update. I uninstalled and reverted back to the old zune software to in case it was the new update. I even started over with a different phone that is currently pre NoDo and still no luck. and no skype running
Click to expand...
Click to collapse
When you update to mango you had installed and the Windows Phone DevTools 7.1 beta
You must remove it and install the previous version with all the patches and updates as it was before mango to be able to sideload apps from your system again.
first of all, you will want to post the error code message and/or look for it to find some help.
also here we have the problem that sideloading does not work anymore, after mango update.
now, you say that another different phone is also not working?
interresting...
change usb port, or use another computer/ reinstall windows.
i maybe would try in vm too...
colossus_r said:
When you update to mango you had installed and the Windows Phone DevTools 7.1 beta
You must remove it and install the previous version with all the patches and updates as it was before mango to be able to sideload apps from your system again.
Click to expand...
Click to collapse
that is wrong
- i successfully downgraded to 7004, unlocked, protected, deployed & updated to nodo & mango with mango sdk 7.1 installed, i only used zune 4.7 because of backups...
also in the thread i mentiond someone already reinstalled sdk & zune and nothing has changed for him.
Hi all,
I have a Samsung focus, 1.3 rev, and I am still waiting for the official update. I have already tried the check update trick by disabling the internet connection and Zune was able to find the mango update ready.
So is it ok to update the device via that method? I have many important stuff in my mobile, mainly SMSs, and i don't want to them to be deleted by official post-mango updates if i use this hack (much like the Walshed fix for forcing mango update via his utility)
Any help is appreciated...
Yes its fine. And nothing will be erased.
Sent from my T7575 using XDA Windows Phone 7 App
I forced the official update via zune yesterday, worked fine first time, no errors or issues.
Affar said:
Any help is appreciated...
Click to expand...
Click to collapse
Is OK, i update my HTC Mozart and work fine.
Can anyone help me force update my HTC hd7?
Thanks
I have a Mozart.
A few weeks ago, i updated to Mango via the leaked version.
A couple of days ago, i plugged my phone in and there was a "HTC update" available.
When i update, it downloads the update, creates a backup, and then fails with the code "80181103".
I assume this is because i have the leaked Mango installed?
I was going to restore to my NoDo version (i saved the backup folder) but i cannot find any way to restore via Zune.
Has anyone else had this problem?
Surely i'm not the only person that has a Mozart that had installed the leaked mango update?
What's the version of your OS on PC?
I'm in a similar position - I have flashed to official prenodo rom supplied by ansar but this didn't fix it either, my PC OS is win 7
РомаN said:
What's the version of your OS on PC?
Click to expand...
Click to collapse
As I see u start here compaign for helping but not only on 4pda.ru
Thanks!!!
Windows 7 x64
Just tried again the other day and it worked fine.
No idea what the cause of the problem was though.
This just showed up on my Focus 1.3. Installed it, says version 0210, I can still access the provxml menus.
dendron said:
This just showed up on my Focus 1.3. Installed it, says version 0210, I can still access the provxml menus.
Click to expand...
Click to collapse
Same here, Focus 1.3 (KI4) Diagnosis v0628, getting Diagnosis 1.9.0.0 update from Marketplace.
I'm not updating yet, I need to see if applying of provxml actually works.
Do you see any changes in firmware *#1234# or revisions?
1.3 Focus, I'm sitting on the update too.
Sent from my SGH-i917 using XDA Windows Phone 7 App
Previous Changes
Will previous changes made through an earlier version of Diagnosis be preserved through the new version, or do they have to be done again with the new version?
For some people can't get it:
Go to zune://navigate?phoneAppID=d881566c-f6ae-df11-8a2f-00237de2db9e from your Windowsphone device
For developer:
http://www.mediafire.com/download.php?1b6i5p1ntmfugoc ( patched)
vt2912 said:
For some people can't get it:
Go to zune://navigate?phoneAppID=d881566c-f6ae-df11-8a2f-00237de2db9e from your Windowsphone device
For developer:
http://www.mediafire.com/download.php?1b6i5p1ntmfugoc ( patched)
Click to expand...
Click to collapse
You mean "patched" as in digital certificate removed (that's what I see) ?
EnderPsp said:
Same here, Focus 1.3 (KI4) Diagnosis v0628, getting Diagnosis 1.9.0.0 update from Marketplace.
I'm not updating yet, I need to see if applying of provxml actually works.
Do you see any changes in firmware *#1234# or revisions?
Click to expand...
Click to collapse
nope, no changes
EnderPsp said:
You mean "patched" as in digital certificate removed (that's what I see) ?
Click to expand...
Click to collapse
yes, removed certificate
It looks to me that they just added location services to it. Did we have to sign off on using location services with previous updates?
It appears that there might be a number of devices affected by the update:
http://dennisdel.com/blog/windows-p...appears-to-be-blocking-gprs-profile-switching
Would be interesting to get a list of FW/OS Build combos to see where it is crashing and where it is not.
That's what I suspected too. Samsung didn't do a Diagnosis update in quite a while and generally, they can remove provisioning in the "regular" "Samsung Update"s.
It might turn out that this Diagnosis update does something more, for which the fix would be a hard reset. Indeed, you can revert (delete the newly installed and re-entering the code will bring the old one) but the damage would be done and hassle/fix could be too much.
I recommend staying away from this one for now, if you want to keep your unlock.
Seems OK
All of my previous changes using prior versions are still there and I can still sideload xaps as before.
JamesAllen said:
All of my previous changes using prior versions are still there and I can still sideload xaps as before.
Click to expand...
Click to collapse
It attempts to block provisioning, not sideloading.
It will not affect your ROM files so you can even delete it, but just the fact that it attempts to tamper with provisioning on some phones should be enough concern.
EnderPsp said:
That's what I suspected too. Samsung didn't do a Diagnosis update in quite a while and generally, they can remove provisioning in the "regular" "Samsung Update"s.
It might turn out that this Diagnosis update does something more, for which the fix would be a hard reset. Indeed, you can revert (delete the newly installed and re-entering the code will bring the old one) but the damage would be done and hassle/fix could be too much.
I recommend staying away from this one for now, if you want to keep your unlock.
Click to expand...
Click to collapse
I can still access the gprs provxml menu and load everything on focus 1.3 unlocked 8107
My Samsung Focus 1.3 with: [ROM] Clean ROM - DFT based - Samsung Focus v1.3 - build 1.20a By: voluptuary
Still has access to GPRS
I updated this few days back it caused a strange problem. I couldn't hear anyone on the call nor could they hear me. Texting worked fine, but not the calls. Reboot didn't help either. Then I ran the diagnosis app and then tried calling, and it worked fine.
I had interop unlocked my phone and am on 8107 build as well.