Database Info

Force Upgrade Check In

Found this article:
http://lifehacker.com/5719682/force-your-android-phone-to-check-for-a-system-update
However when I type in the last * the phone deletes the number from the screen...
Number:
*#*#checkin#*#*
*#*#2432546#*#*
Anyone found a way to force our phones to check for updates?
Most times when I try with the settings way it says cannot connect to AT&T.
And since so many of us cannot get the Kies program to work (win 7 x64 especially) it would be good to have a backup plan.

NinjaCoder said:
Found this article:
http://lifehacker.com/5719682/force-your-android-phone-to-check-for-a-system-update
However when I type in the last * the phone deletes the number from the screen...
Number:
*#*#checkin#*#*
*#*#2432546#*#*
Anyone found a way to force our phones to check for updates?
Most times when I try with the settings way it says cannot connect to AT&T.
And since so many of us cannot get the Kies program to work (win 7 x64 especially) it would be good to have a backup plan.
Click to expand...
Click to collapse
Open up settings, scroll to the bottom, tap software update. This is how you check for a software update OTA. Many of us would not accept any OTA updates due to it bricking phones in the past. I have win7 x64 and I can connect to KIES just fine. Make sure you have the right drivers installed. This may be your issue. If you have to have 2.2 right now download and flash one of the many custom ROMs. If you are waiting for the Oofficial 2.2 update...I would suggest you wait until someone extracts the files from the official update and posts it here and flash it with Odin.

This all would be useful if there were updates in the first place...

Even when I had my "refurb" from ATT after JH7 was released, I never was able to use the phone's internal software to check for server updates (always received the unable to connect error no matter what day/time) - I had to use Kies to get JH7 "officially" - I'm pretty sure that is how they are going to do updates from now on anyhow.
Wish Samsung did things like Apple with their updates - Version x.x is out - everyone gets it- you [email protected]

CB650 Wolf said:
Open up settings, scroll to the bottom, tap software update. This is how you check for a software update OTA. Many of us would not accept any OTA updates due to it bricking phones in the past. I have win7 x64 and I can connect to KIES just fine. Make sure you have the right drivers installed. This may be your issue. If you have to have 2.2 right now download and flash one of the many custom ROMs. If you are waiting for the Oofficial 2.2 update...I would suggest you wait until someone extracts the files from the official update and posts it here and flash it with Odin.
Click to expand...
Click to collapse
I am green with envy! (Purple is as close as I could come.)
What magic have you performed?
What version of Kies Mini are you running? (You are running "mini," yes?)
The only version to download is 10082_8_1 but with an update I cannot dodge I'm running 1.0.0.10104_1. Since that update, Kies Mini has never "seen" my phone (although it does know when I've set USB debugging on... which it wants me to turn off).
Thank you for your response/help.

Picsman said:
I am green with envy! (Purple is as close as I could come.)
What magic have you performed?
What version of Kies Mini are you running? (You are running "mini," yes?)
The only version to download is 10082_8_1 but with an update I cannot dodge I'm running 1.0.0.10104_1. Since that update, Kies Mini has never "seen" my phone (although it does know when I've set USB debugging on... which it wants me to turn off).
Thank you for your response/help.
Click to expand...
Click to collapse
Do you have an alternative launcher loaded? In order for mini kies to see my phone, I had to go back to the stock launcher before it would recognize my phone.

I have the same issue as Picsman running Mini Kies on Win 7 x64. Other than being rooted for Titanium Backup and the simlock removed my phone is stock JH7.
When I try the number to force a check, I get a message box saying "Rejected".

Except for some apps, my phone is a virgin. Still the stock launcher and I'm pretty sure no apps which would tweak the OS, either. BTW, I'm running 32 bit Windows 7 Pro.
I just tried to connect using Kies but this time with no SD card. Same result; Kies does not see the phone when connected. OTOH, Kies knows when the phone is in USB debugging mode and says to turn that off and reconnect in Keis mode.
Device Manager says everything is installed properly, the modem and the composite US device. I can access the phone's storage and SD card from Windows 7. When in Kies mode, the phone says "connected.". Everything seems correct and "normal" except Kies does not see the phone and therefore I cannot even advance to get the dreaded "cannot connect to server" message.
It seems to me the problem is with the auto-updated version of Kies I'm running as before that update I did download and install the 2.1 update using Kies.
How do you scream on XDA? If I scream, will anybody hear me? And, will screaming change anything? So I'll just say "grrrrrrrrrrrrrrrrrrrr."

Please see my 8:10 post below (above?) ...

Sideloading stopped Working Completely

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.

Problem installing 7720 Mango

Hi all,
I'm a new owner of a samsung omnia 7 and im trying to install mango build 7720 with no luck. When i open the provision program, after clicking agree I get a white screen with not text. I've been waiting for something to come for 2 hours now. I can sync with zune, so I don't know what the problem is. Any help would be appreciated.
thanks in advance

Great phone!!!
A few things, maybe...
If phone is not 'unlocked', either as a developer or using 'Chevron Method', it won't work. There is a provisioning version that bypasses the unlock requirement. It's on these forums somewhere. Use search..
Is the 'UpdateWP' exe installed??? If not, install it!!!
Anyway, hope this helps.

This happens because you have the wrong zune version installed.
Uninstall i t and reinstall the one with the first Mango release , this solved this issue for me.

With my omnia 7, different problem:
- i have to reboot manually the first time and enter manually in update mode (power camera volup)
- two steps are done and then the next phone reboot gives me an error and the phone is still at previous state

[Q] Bricked problems,I need help!!

Hello, I need help with my Samsung Focus, I flashed but has fallen on the initial screen, someone help me solve this problem please ... thank you.

OK dude, you're gonna have to provide a *LOT* more info than that.
Which hardware revision of the Focus (1.3 or 1.4)?
What ROM was it on, including version?
What ROM were you flashing to it (version, etc.)?
What tool did you use?
What happened (the full explanation, not "it didn't work")?
What does the phone do now when you try and boot it (again, not "fallen on initial screen" but exactly which screen, and does it look normal or not)?
Also, the standard solution for a bad flash is to use Zune to restore the phone from a backup. These backups are created automatically when an official update is installed, and contain the full image including the ROM. They can be restored by going to Settings->Phone->Update when the phone is connected to Zune, or by putting the phone in download mode during bootup (if you can't boot normally) and connecting to the PC with Zune running.

GoodDayToDie said:
OK dude, you're gonna have to provide a *LOT* more info than that.
Which hardware revision of the Focus (1.3 or 1.4)?
What ROM was it on, including version?
What ROM were you flashing to it (version, etc.)?
What tool did you use?
What happened (the full explanation, not "it didn't work")?
What does the phone do now when you try and boot it (again, not "fallen on initial screen" but exactly which screen, and does it look normal or not)?
Also, the standard solution for a bad flash is to use Zune to restore the phone from a backup. These backups are created automatically when an official update is installed, and contain the full image including the ROM. They can be restored by going to Settings->Phone->Update when the phone is connected to Zune, or by putting the phone in download mode during bootup (if you can't boot normally) and connecting to the PC with Zune running.
Click to expand...
Click to collapse
Excuse my ignorance friend. I mean, I bought my Samsung Focus wp7 by second hand to a friend.First, I did a hard reset the phone to restart initials configurations and it wordked correctly.I set it some configuratios like my contact list, my language, i checked camera and made some shoots, the device is perfectly.I put it to load and after few minutes the phone restart!!!. I checked de device and I saw it lost all configurations made by me, exmple: languaje configuration(spanish), my contact list and all the pictures, music and video!!...I decided to probe the camera again...error, dont let me save new pictures or videos, just it blocked when a try to doit.Dont reproduce any video or music!!.....When i saw this problems, started to find solutions in diferents foros like 'windosphoneforos.com', this foro is in spanish, Im cuban,..well,someone told me try to do a hard reset again, i did it, resultss :NOTHING.DONT WORK...the same problems, finally I decided to flash my phone with WP7(no mango or others updates):
hardware revision of the Focus : 1.3
ROM was it on, including version: dont nokw, i suposse was the original.(7004)
ROM were I flashing the phone :Samsung-i917-Focus-firmware-UCJK2-ATT-USA (and then I try whit Samsung-i917R-Focus-firmware-UXJL2-ROGERS-CANADA)
tool I used : WP7 Downloader Ver 7.21 for All Device (Publish version) and WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X)
What happened : Well, I execute the flash process following the steeps like proposed this link http://forum.xda-developers.com/showthread.php?t=973420..(in this tuto appear samsung omnia, Ive focus, but is the same way)...finally, the process end correctly,dont show any errors or something, but in the moment that it restarted to ask me the initial settings after the rebuilding process, it just stopped in Samsung screen...and not pass to At&T screen....I flashed my phone 4 times , and always is the same....
...just I dont nowk to do now, i like the style and prestations of the Focus, i used Iphone, but i want to try with WP7, and the Focus is so nice isnt?...please if you could help me, i think if I cant resolve this problem here, ill never cant...
thanks...

samsung diagnosis update for focus 0210

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.