cannot update Omnia 7 after 7740 - Windows Phone 7 Q&A, Help & Troubleshooting

I can't update my phone after installing the 7.10.7740 back in november 2011. Zune tells me my phone is up to date, but i know two other updates were released in 2012 including Tango. I also seem to have the IE tabs problem described earlier in the forum. What could be the problem? Any solutions? Thanks in advance.
BTW it's an unlocked T-Mobile Omnia 7 8GB

What method did you use to update? Have you ever done anything to "force" an update in any way? Some of those break future updatability of the phone. Also, have you ever messed with the DeviceTargetingInfo registry key? The values there control updating, and messing with them can (among other unpleasant things) break it.
There's a tool that can send the CAB updates directly to your phone, along with a list of the CAB files for download and info on how to use the tool, available on teh Dev&Hacking sub-forum. Be cautious if using this (make backups for sure) but it works for situations where there's no official update available.

I updated via Zune and never tweaked the registry. Could a hard reset help before trying custom ROMs?

If you inadvvertently applied any hacks, a hard reset will clear them. However, if you want to avoid losing data, you can certainly use the CAB sender to install updates directly. Just be sure you follow the instructions regarding language packs and such!

Well, I tried the hard reset and that got rid of the IE tabs problem. Oddly enough, battery life seems improved. Still not getting the updates, though. I guess I'll have to upload the CABs, but can I go straight from 7740 to Tango? Or do I have to flash updates in chronological order?

Better to update them in order. also be careful to install all the necessary language packs. Plus, there is some update for Omnia that locks the phone. Be careful of that too.

Related

NEW WP7 Update disable unlock??????

Oh nohs...
Today i updated my phone with the new security update from zune.
from: v7.0.7000.8 to v7.0.7392.0
and now i cant unlock my phone anymore?!?!??!
FIX MS the chevronwp7 Hack??????
oh nos.... :/
why i updated my phone ((((
hope anybody can help me???
if i want to update i became the notice:
Sorry, I'm having trouble communicationg with the phone.
-Please make sure it's connected using USB
-Please start the Zune application
but it worked nice after the update....?
NEEED HELP! and have any other the same problem???
big thx
Yeah just flash your ROM there are some posts about that in here, but be carefull and chose the right ROM for the right device PS i have not test this but i belive its safe as long you know what your doing by reading every step. i hope that this will help you out
MS fixed the hole that the ChevronWP7 unlocker was using in the NoDo update (7390). You seem to have skipped NoDo and gone straight to the minor security update (7392) but updates are cumulative, so you will have gotten the Chevron hole closed too.
There are a few options here, though.
1) Get an official unlock. If you're a student with a .edu email address, this is free (through Dreamspark, I think). Otherwise, it costs $99. http://create.msdn.com has more info.
2) Restore your phone to 7008 using the Zune software (Settings -> Device -> Update). Then unlock using Chevron, and apply the hacks to prevent it from re-locking. Then re-update.
thx for your fast reply's !
that are bad news for me -.-
is anybody here who have also the same problem like me and have a solution witch worked?
or is it maybe possible to unlock the phone with the new update?
i dont't want to hard reset my phone -.-
We need another method
What we need, especially those of us running Windows XP on disk space restricted PC's, with a Samsung Focus, is a method to unlock that does not require the installation and use of that disk hog Windows Phone Developers Tools. There must be another method that does not require this full install, but possible just some of the connectivity files. Wish someone would come up with it. I have no interest in stealing apps or anything like that. I would just like to be able to load custom ringtones and make some registry changes. Such a simple thing that has proven to be a nightmare using Windows XP.
@JamesAllen:
*WHY* would you run a 10-year-old OS, on a computer with such a restricted disk space that the tools are a burden (agreed they're large, but hard drives are about $0.04 USD / GB right now), and then want to hack on a cutting-edge smartphone OS?
Working to provide a low-footprint, downlevel-OS-compatible tool yourself is great, and I'm sure some people would love to have it. If you want somebody else to do it, though, you may get a better response if you provide a better reason than "my computer is so out-of-date that I could get a 3x better one for less than the cost of my new smartphone."
Oh, and for the record, I'm pretty sure the Developer Registration tool (used for official unlock) and its dependencies, including Zune, comes to less than 200 MB (the Zune install folder is <80 MB).
gore23 said:
thx for your fast reply's !
that are bad news for me -.-
is anybody here who have also the same problem like me and have a solution witch worked?
or is it maybe possible to unlock the phone with the new update?
i dont't want to hard reset my phone -.-
Click to expand...
Click to collapse
What phone do you have?

March Diagnosis update on Samsung phones?

On Focus we're getting the Diagnosis 1.9.0.0 update.
Any other Samsung phones getting the update from Marketplace?
I'm wondering if this is another way of delivering the KK2...
Changes
EnderPsp said:
On Focus we're getting the Diagnosis 1.9.0.0 update.
Any other Samsung phones getting the update from Marketplace?
I'm wondering if this is another way of delivering the KK2...
Click to expand...
Click to collapse
I am wondering if changes made with a previous version will be retained after the update? Also, will there be access to all of the fields that were available in previous versions?
Ok, time to address some common misunderstandings:
Is this another way to get KK2?
No, that's quite literally impossible. Neither a running app, nor the app installer, can modify the ROM. KK2 is a firmware update, which is part of the ROM. The ROM can't be updated while the OS is running.
Is this going to revert existing changes?
No, that's incredibly unlikely. Hypothetically, it could make some specific changes, some of which (like setting MaxUnsignedApp to 10) might be bad... unless you're on a student account and you MaxUnsignedApp is supposed to be 3 (or something else similar). There's no way to just "revert" the changes though, short of forcibly hard-resetting your phone.
Is it going to break existing apps?
No. Interop apps rely on OEM drivers, which are in the firmware. As mentioned before, an app (or app update) is completely incapable of modifying this.
Is this going to break the ability to use WindowBreak and similar hacks in the future?
It's possible that it will, yes. All that would be required is to remove the user interface for sending provisiioning files to the driver. However, it's more likely that they will rely on the KK2 update to do that... although it's no guarantee.
since today i also have a notification on my omnia7 with v1.9.0.0.
not updated yet.
Propagating the info from Focus thread (thanks ZeBond):
The new Samsung Diagnostics app attempts to block GPRS profile switching (provisioning)
Works for me
I was already interop and WP7 Token unlocked, upgraded to 8107 by cab sender method, upgraded to current Diagnosis and *#9908# works for me and I can still sideload xaps.
The update showed up for me a few days ago but I haven't updated it yet.
Strange
I received the update on my Focus S (dev unlocked) and installed it. If I go into the diagnosis and put in #*9908# it closes the app... deleting it and and putting ##634# installs the old version. Ideas??
Yeah, don't install that update! Samsun have decided to remove that mode from the app. However, the original XAP (the one intalled via the dialer) is actually baked into the ROM of the phone, so removing the Marketplace-updated version and reinstalling the in-ROM xap gets you the un-updated version of the app...

Podcast settings gone?

Hello,
back in September when I updated to Mango, i was able to change settings for podcasts I subscribed to via the phone itself. This included that the phone would automatically download new episodes via Wifi without the need of the Zune Software. (see the top section of this site: http://www.wingadgetnews.com/subscribe-podcasts-windows-phone-7/ )
I am now running version 7.10.8773.98 on my phone (Custom Nextgen+ ROM) and this setting has gone missing. Did Microsoft remove this option in later versions of Windows Phone? Is there some way I can get it back? I do not want to have to boot my PC and start the Zune software to sync my podcasts, I want my phone to do this on it's own like it used to to back in October.
So, I figured this out a while ago through intensive searching and trial, but I figured I post the sollution in this thread for future reference.
all that is needed is a registry change in
HKLM\Software\Microsoft\Zune\Settings
here you'll find a registry entry called "XuidLocale". For me, the value was DE-DE as I live in germany. I changed this to us-EN and the podcast settings came back.
After I reboot my phone, the value changes back to DE-DE, but the podcast settings are still accessible, so that's a good thing
I just upgraded to Tango 7.10.8773.98 (legit) as well as the .12220 firmware for my Lumia 800, and I seem to have lost these features as well. I tried searching for a solution here on the forums and this seemed to be the most relevant and helpful.
However, I can find neither the settings folder nor "XuidLocale" when going through my registries. Any help would be appreciated...
Edit: Or is this fix only for rooted/unlocked phones?
I've just upgraded to Tango and lost the ability to manage podcasts from the handset too. I thought this was a feature of low-end handsets, not my Lumia. As this is one of my primary uses of my phone it could be enough to drive me back to Android and Jellybean.
Gloamin said:
I just upgraded to Tango 7.10.8773.98 (legit) as well as the .12220 firmware for my Lumia 800, and I seem to have lost these features as well. I tried searching for a solution here on the forums and this seemed to be the most relevant and helpful.
However, I can find neither the settings folder nor "XuidLocale" when going through my registries. Any help would be appreciated...
Edit: Or is this fix only for rooted/unlocked phones?
Click to expand...
Click to collapse
you need to be at least interop unlocked, I think.
Localhorst86 said:
you need to be at least interop unlocked, I think.
Click to expand...
Click to collapse
Yeah, makes sense. I misinterpreted OP's post.
Has anyone (non-US) retained their podcast settings after updating to Tango? Perhaps particularly someone from Sweden with a Lumia device? I got the advice to simply just master reset the phone and just re-sync everything again, but I don't really want to do so if it won't amount to anything.
Gloamin said:
Yeah, makes sense. I misinterpreted OP's post.
Has anyone (non-US) retained their podcast settings after updating to Tango? Perhaps particularly someone from Sweden with a Lumia device? I got the advice to simply just master reset the phone and just re-sync everything again, but I don't really want to do so if it won't amount to anything.
Click to expand...
Click to collapse
I wiped when I installed (Zune wouldn't put Tango on so I flashed it using the Nokia care suite - Vodafone UK PAYG version same as my Mango). I have lost my podcast management abilities - I had them in Mango.
Has anyone managed to find the fix for this for non-unlocked devices?
I was able to subscribe to podcasts before on my Lumia 800 but as soon as I installed 12220 the options has gone.
Unfortunately, this happened to me too. Couldn't subscribe to new podcast feeds on the phone (although previously-added feeds still updated). There isn't a registry editor that works with my phone either.
As over-the-air podcast syncing is one of my most-used features, I have reverted back to a pre-Tango backup (using Zune). Everything works fine now, albeit on an older OS version.
Sounds like MS added a region check to Tango to make sure you're in a region that has podcasts in the Zune store before allowing you to manage them on your phone. I hope this gets fixed
I think you are out of luck. Unless MS decides to magically bring these features back, if you don't have the ability to edit the registry, you wont be able to manage podcasts on the device
Sorry.
On Tango it worked for me too.
Now i´m an wp7.8 and there it didn´t work
Any idea?

Is there any way to re-interop? Focus S.

Hello,
In all my excitement over Tango, I neglected to read any of the warnings posted around the forums/web. I installed Tango via the cab sender method (neglected to make a backup) and everything still worked, or at least the homebrew apps I launched still did. Searching the forums, I found the Samsung firmware somewhere in the replies to the cab thread, and pushed it also. This was late at night and it wasn't until the next day I noticed I can't launch almost half of my homebrew apps. It's said restoring from a backup (don't have one) or flashing back to Mango is the only way to fix this. Is that true? Well ****. Because there is no ROMs (stock nor custom) for the Focus S..
What should I do?
Thanks in advance,
6-4.
64GUNSHIP said:
Hello,
In all my excitement over Tango, I neglected to read any of the warnings posted around the forums/web. I installed Tango via the cab sender method (neglected to make a backup) and everything still worked, or at least the homebrew apps I launched still did. Searching the forums, I found the Samsung firmware somewhere in the replies to the cab thread, and pushed it also. This was late at night and it wasn't until the next day I noticed I can't launch almost half of my homebrew apps. It's said restoring from a backup (don't have one) or flashing back to Mango is the only way to fix this. Is that true? Well ****. Because there is no ROMs (stock nor custom) for the Focus S..
What should I do?
Thanks in advance,
6-4.
Click to expand...
Click to collapse
Yeah... I want to say you're unfortunately screwed :-\.
To make matters worse, the Wireless manager no longer appears to work for configuring MMS when carrier unlocked. I guess I'll just go back my Quantum's for hacking and hard reset this device ..ill wait a while though.
Sent from my SGH-i937 using XDA Windows Phone 7 App
Do you have *any* homebrew apps that
A) you can still run
B) you marked as Trusted in WP7 Root Tools?
It sounds like what happened is that your phone reverted from interop-unlock to simple dev-unlock (you presumably have an AppHub account?). However, this does *not* revert root-unlock as applied by WP7 Root Tools. Root Tools itself requires ID_CAP_INTEROPSERIVCES, and as such can't be run without interop-unlock. However, the apps that it has marked as Trusted will continue to run with full permissions (root unlock).
So, here's what you do.
First, identify an app that you can run (i.e. that isn't interop) and that is marked as Trusted.
Second, take the GUID of that app, and use that GUID to replace the ProductId of the Tango-update-workaround app (which essentially just restores interop-unlock).
Third, remove homebrew apps from your phone (but not the target app, the trusted one you can still run) until you are able to deploy an app (usually, this means reduce to 9 homebrew apps).
Fourth, use a XAP deployer that supports updating, and do an update-install of the workaround app (upgrade, because it's using the GUID of the already-installed target).
Fifth, run the workaround app, and then re-install your normal apps.
I did as you instructed, however I still have the 10 sideload limit and am unable to deploy any interop services.By tango workaround app, you meant relockprevent, correct?
Is there something I may have missed?
Like I said, I installed the Samsung LE2 update for the Focus S which is basically the KK2 equivalent, so provxml will no longer work.
Also, I do not have an apphub account.
Bump. Anyone have any ideas? A friend put a support ticket in with Samsung internal support to see if they can get the ROM.
64GUNSHIP said:
Bump. Anyone have any ideas? A friend put a support ticket in with Samsung internal support to see if they can get the ROM.
Click to expand...
Click to collapse
Oh so it was that firmware update that just broke interop. Yeah I want to say at this point you are stuck. I doubt that Samsung will give the ROM since it isn't an issue that is preventing you from doing out of the box functionality.
Sent from my SGH-i917 using XDA Windows Phone 7 App
snickler said:
Oh so it was that firmware update that just broke interop. Yeah I want to say at this point you are stuck. I doubt that Samsung will give the ROM since it isn't an issue that is preventing you from doing out of the box functionality.
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
isnt the provxml method using diagnostic tools the reason for this no longer working, what i mean by that is if you were to install the older version of the diag tool would that not restore functionality, or has the lock down of that gone much deeper? if you are able to install XAPs then find an older OEM update version pre KK2/LE2, open it up and rip out the diagnostic tool XAP, remove any previous installed version then send over the XAP....
just a thought, it might not work, but essentially i think thats what happens unless of course there are other dlls or drivers that the tool needs that have also been updated....
course it would be great to find someone willing and able to help crack the bootloader
dazza9075 said:
isnt the provxml method using diagnostic tools the reason for this no longer working, what i mean by that is if you were to install the older version of the diag tool would that not restore functionality, or has the lock down of that gone much deeper? if you are able to install XAPs then find an older OEM update version pre KK2/LE2, open it up and rip out the diagnostic tool XAP, remove any previous installed version then send over the XAP....
just a thought, it might not work, but essentially i think thats what happens unless of course there are other dlls or drivers that the tool needs that have also been updated....
course it would be great to find someone willing and able to help crack the bootloader
Click to expand...
Click to collapse
Yeah I gave the suggestion to him in the Cab Sender thread to try and look on here for the Diag v 0109 or even 0210. That's the version that I have. Actually in the Cab Sender thread, I posted the cab file to the samsung firmware for Mango that should have that diagnostics version in the cab. You may be able to push that to your device
The old version was still installed after updating, it didn't work.
64GUNSHIP said:
The old version was still installed after updating, it didn't work.
Click to expand...
Click to collapse
Ok, that means that the firmware also pushed out new Dlls to prevent proxvml. You are stuck unfortunately :-\
Ive been asking around and doing some research and as of today your stuck, sorry!
I did some poking around on DFTs website as well and there is absolutely ZERO work being done on it, mostly because it seems like the focus S is an AT&T only phone, there just isnt a pressing needed to do anything, plus most folk dont have a focus S to work with.
i dont know what it would take to get some help or even guidance on getting the bootloader replaced but at the moment, until another method is found, thats all there is.
Tho This might be interesting to look in to but DONT DO IT!
did i read somewhere else you dont have a preupdated backup or was it that the backup didnt work?
snickler said:
Ok, that means that the firmware also pushed out new Dlls to prevent proxvml. You are stuck unfortunately :-\
Click to expand...
Click to collapse
There is a lot of changes in those updates, if we could insert our own certificate to allow us to build our own signed cabs we could probably work it out, but alas we can only add a cert in to a custom ROM then flash it...
Yes, unfortunately I bought the phone from a guy here on XDA in May, never had to update it (had been cab updated to 8107 before I got it), never made a backup before installing tango (it's a small update, what could it possibly **** up, right?) Anyway the Focus S was announced yesterday as being available online at some Australian website so maybe there will be ROMs available in the future. I still haven't heard back from internal Samsung support, but have also asked the user I purchased the phone from if he has any backups, which I would restore from and immediately reset again to ensure his privacy.
Honestly, I wouldn't mind losing interop-unlock until 7.8 comes around, or WP8 (whichever I can afford first), but MMS also can't be configured using the Wireless Manager anymore, and that's an absolutely vital feature for me. Although, the WM has been known to not work for a lot of people, even pre-tango, but it worked flawlessly OOB for me prior to updating.
64GUNSHIP said:
Yes, unfortunately I bought the phone from a guy here on XDA in May, never had to update it (had been cab updated to 8107 before I got it), never made a backup before installing tango (it's a small update, what could it possibly **** up, right?) Anyway the Focus S was announced yesterday as being available online at some Australian website so maybe there will be ROMs available in the future. I still haven't heard back from internal Samsung support, but have also asked the user I purchased the phone from if he has any backups, which I would restore from and immediately reset again to ensure his privacy.
Honestly, I wouldn't mind losing interop-unlock until 7.8 comes around, or WP8 (whichever I can afford first), but MMS also can't be configured using the Wireless Manager anymore, and that's an absolutely vital feature for me. Although, the WM has been known to not work for a lot of people, even pre-tango, but it worked flawlessly OOB for me prior to updating.
Click to expand...
Click to collapse
so you updated to the LE2 samsung update, was that via zune? (the last update it does in a row 3rd or 4th perhaps!) or did you cab send that as well?
if you went via zune then it does a backup as well, settings>update>restore
It was all done through the cab sender. There is no backup.
Just wanted to mention here... you know that CAB Sender is perfectly capable of making backups, right? It's one of the core operations the tool is capable of. Don't blame CAB Sender for you pressing S instead of B.
I just don't want people getting the impression that "through the cab sender" implies "there is no backup."
Fully aware, thank you.
?
Hello guys!
Got my device on the 8773 and did the samsung update...
Is there anyway to get my interop back ?
I have my backups (one the last 8773 without samsung update and the other is 7740 without anything =] )
Thanks a lot.
Restore your backup, do a little bit more reading on the subject of Tango with Interop Unlock, install the prevention app and mark it as trusted, and have at it. (Specifically, Tango will reset the "prevent relock" registry values, so you have to avoid the phone connecting to Microsoft until you have cleared them again).

[Q] Titan not working correctly after forced update to WP7.8

Hi, I was hoping someone could help me!
I had a Titan which I successfully updated to WP7.8 earlier this year using the 78er tool. Unfortunately I dropped that phone and smashed the screen but my insurance company just sent me a new handset so, naturally, the first thing I did was attempt to update to 7.8 again.
I realise now that I should probably have let the default WP7.5 ROM fully update through Zune before running 78er but, alas, I did not. Now, since updating to WP7.8, some aspects of my phone's functionality are working fine but other aspects are not.
For instance I cannot access a variety of settings: the WiFi menu, the accounts menus (email, Facebook, etc), the lock + wallpaper menu, mobile network menu and others. Every time I select one of these nothing happens.
I don't know what to do to resolve this - I cannot re-run 78er as it tells me that it has already updated, so I can only assume that I need to flash an earlier (stable) ROM and then re-run 78er again. But, I must confess I don't know how to do this.
Something that puzzles me is that the OS is otherwise operating normally.
Any thoughts?
Many thanks.
[RESOLVED]
RESOLVED!
After some searching I discovered that this was due to my selecting the wrong language during the Seven-Eighter update (I selected US English instead of UK English). It seems this is quite a common problem and the solution was to use Cab Sender to send the relevant UK English files to my phone from this page: http://forum.xda-developers.com/showthread.php?t=1306415
I had to start from the first update and work my way through. It didn't start working until I had updated to "WP 7.8 OS UPDATES (7.10.8779.8 - 7.10.8779.8)"
Patience is necessary!

Categories

Resources