I deleted the Now App because it was acting up so i uninstalled it and tried to reinstall it, but now it says your phone is not up to date...but I do have mango RTM and it was working before, what's going on??
Same problem
I did a hard rest and tried to reinstall the Samsung Now app, but was unable to install. This was after I updated to Mango. I hard rest the phone 2 more time with no luck. When I first updated I was able to install the Now App to the Mango Version. I now get the marketplace error (80330011). Also when in the Samsung Zone the Now App now states That (This app is not available for your device. Tap here for more info. When I tap I get the (App. not Available. This might be because your phone software needs to be updated, the app is exclusive to a different mobile provider, or the app is not available in you region.)
OS Version 7.10.7720.68
Firmware 2103.11.81
Samsung Focus 1.3 AT&T
you can sideload the latest Mango enabled Now xap if you are unlocked.
follow this post.
i am dev-unlocked, but sideloading the app doesn't seem to work. Any idea why this is happening?
There is a non-patched version of Now posted by @derausgewanderte (thank you man)
Take it @mmian : Now - v2.3.0.1 (patched).xap
poloche said:
There is a non-patched version of Now posted by @derausgewanderte (thank you man)
Take it @mmian : Now - v2.3.0.1 (patched).xap
Click to expand...
Click to collapse
you can use this to sideload the app. Once you have this application you also don't need to search the net for a patched version of the xaps you find. it works
I'm experiencing this too. My phone isn't dev-unlocked so I'm hoping it's a temporary marketplace issue.
When I first updated to Mango (right after a reset) I downloaded the new Now app without any issues. I've since reset again to add an SD card and now cannot update it. Argh.
Also, I wish they'd use the same font for the temperatures on the Now Live Tile as the rest of the OS.
I have the same problem.
I upgraded my phone (not unlocked) all the way from its original version 7004 through mango RTM to mango and could update samsung now to the latest version. I saw the new features they introduced.
Then I wanted to unlock the phone -> reflash to 7004 and go to mango again. samsung now wouldn't update in marketplace (don't remember exact error code) but other apps like diary could be installed. I uninstalled 'now' and when i tried to install it it said (is not compatible with your phone".
The only difference between the first and the second version of mango on the phone:
- the first time I flashed the firmware using signed_CSC_Cetus_Europe_I8700BSEJK1.csc
- the second time I flashed the firmware using signed_CSC_Cetus_Europe_I8700DBTJK1.csc because I was told this is the right file for an unbranded omnia7 for germany
- after I've flashed the second time, zune did not find an update after I had 7008 on my phone -> needed to use the "disconnect from internet" solution to upgrade
However, in the end all drivers have been updated:
Os: 7.10.7720.68
firmware: 2424.11.8.5
radio: 2424.11.7.2
bootloader: 5.8.1.9
Does it really depend on the .csc and the active region that "now" can't be installed? but why should it be disabled for germany, I already used it in my unlocked mango version and they have german news and all that stuff.
with WP7Downloader, I could flash the csc to BSEJK1, probably I'll give it a try.
probably related:
IIRC, the unlocked mango installed a version of the diagnosis app starting with 1,
now (mango unlocked) I have "diagnosis_DU (ver. 0628). Is this the correct one? when I start the GPRS manager, I don't get a nice combobox for "select GPRS" anymore, the options are displayed in a listbox which is too small to show all entries. in "unlocked mango" the UI looked nicer, now it looks kind of ugly or just wrong however, it still works and unlocked mango as intended
And yes, I uninstalled the app, rebooted the phone and installed it again using ##634#.
Related
I just flashed my Omnia 7 from a T-Mobile branded one to the XXJL3 RETAIL UNITED KINGDOM one but am unable to update past 7008. Any one else running in the same problem?
yeah.. i had the same problem.. i was on uk retail rom and was not getting past 7.0.7008.. heres what i did to get my mango update.
1) flash a nodo rom from here http://forum.xda-developers.com/showthread.php?t=1131891 ..
2) u will be on nodo(7389 or 7392) after that
3) next use this guide to update to mango beta 1 (7403 build) http://koolmobile.net/windows-phone-7-mango-7720-rtm-leakedhow-to-install/
4)once 7403 is installed.. zune will automatically give u notification that ur phone will now be updated to final build of 7720(official mang0)
5)after that it again check for updates and then will install samsung updates for correct drivers for ur device..
done!! full official mango in ur device
Will give it a try.Thanks
It seems that the links for the beta mango rom is not available but with the nodo rom its pushing out the 7392 version. Will install that and check if maybe mango pops up on its own
ok quick update. Using the WLAN disconnect trick I seem to have managed to get Zune to detect the 7403 update
Thanks a lot for your help
AlthalusDgr8 said:
ok quick update. Using the WLAN disconnect trick I seem to have managed to get Zune to detect the 7403 update
Thanks a lot for your help
Click to expand...
Click to collapse
if it doesnt go through here is the alternate link for beta build
http://thepiratebay.org/torrent/6601278/Windows_Phone_7_Mango_Build_7720_RTM_Update_(7720.rar
I'm facing the exact same problem. Flashed German T-Mobile NoDo Omnia 7 16GB to a unbranded 7004 with W7 Downloader. Next, I unlocked the device with Chevron WP7 and installed Samsung Tools to keep the lock when connecting with Zune.
Zune installed the 7008 February update succesfully, but now reports that my phone is up-to-date. What a bummer. Why does it let you update to 7008 and not beyond if the removed all the other update up to Mango!? It's a real bummer
I couldn't even restore the backup made with wpupdater.exe
I have an un-branded Samsung Omnia 7 (Deutsche Telekom I believe). I did the force update for mango and was able to update to 7403 just fine. However, at the last step 2 of 2 of updating to 7720 it gave me the error code 80180048. I do not have a walshed phone because I tried using the walshed fix and the program said my phone wasn't walshed. Any one having this issue or have fix for this? Thanks.
All Languages
I was having a problem with failled Mango update and I discovered I used the Walsh tool wrong. I only selected the language that was "checked" in my keyboard settings and not ALL languages that were available on my phone. Once I selected all languages, the update went flawlessly.
---------- Post added at 08:43 PM ---------- Previous post was at 08:25 PM ----------
Did you also install the Windows Phone Support Tool? It may be needed for the Walsh Tool.
I have samsung focus (from Rogers Canada) and am facing exactly the same problem, I have reset my phone a couple of times but still receiving the same error, am not sure what to do now, can someone suggest following steps? I don't have walshed phone and walsh tool gave me missing clsid exception.
frazrasheed said:
I have samsung focus (from Rogers Canada) and am facing exactly the same problem, I have reset my phone a couple of times but still receiving the same error, am not sure what to do now, can someone suggest following steps? I don't have walshed phone and walsh tool gave me missing clsid exception.
Click to expand...
Click to collapse
Samsung Focus has two hardware revisions.
You will not be able to get passed the last steps to update to Mango if you have rev. 1.4
rev 1.3(Micron): Windows 7.5 update will be available through Zune on 9/27.
rev 1.4(LSI) : Update has not entered the AT&T SPE lab yet; however, Samsung is targeting for 10/17 lab entry and 10/31 TA"
you can check which revision you have by pulling out the battery. there should be a revision number on on a white sticker on the device.
I have checked the focus revision number on my phone and it is 1.3, I found that one may use windows phone support tool to solve the issue, but it always gave me the 'the device not in connect to pc mode' error while I am pretty sure the device is infact that mode, so somehow it doesn't see that. I am still confused what to do now?
frazrasheed said:
I have checked the focus revision number on my phone and it is 1.3, I found that one may use windows phone support tool to solve the issue, but it always gave me the 'the device not in connect to pc mode' error while I am pretty sure the device is infact that mode, so somehow it doesn't see that. I am still confused what to do now?
Click to expand...
Click to collapse
sounds like a USB driver issue.
open Device Manager
open Zune
plug in the phone into the USB
In the device manager you should see Windows Phone USB Device at the very bottom come in.
Double click and double click Windows Phone USB. Got to Driver tab and make sure it reads Deiver Version 4.8.2345.0
if you have something older, uninstall the driver, unplug the phone, then plug it back in and hopefully it will pick up the new one.
I have exactly the same problem as Starsyde.
Forced update managed to get me through to 7403 and then on step 2 of 2 I get error 80180048. Tried at least 6 or 7 times and always get the same result.
My phone is also an Omnia 7 (bought it unlocked but has the Orange UK logo and apps preloaded).
It's not Walshed (I didn't even have an idea what that even meant until a couple hours ago but still tried that tool, just in case - it says "Good news, your phone isn't Walshed!") and the Windows Phone Support Tool says the phone's not in a "Connect to PC state", even though it is.
To sum up: nothing works.
Oh, almost forgot: I then saw the post about the USB drivers, it's version is 4.8.2148.0 but it says it's the last version so it won't update, and when I unsinstalled it, it automatically installed the same version.
mrrtt said:
I have exactly the same problem as Starsyde.
Forced update managed to get me through to 7403 and then on step 2 of 2 I get error 80180048. Tried at least 6 or 7 times and always get the same result.
My phone is also an Omnia 7 (bought it unlocked but has the Orange UK logo and apps preloaded).
It's not Walshed (I didn't even have an idea what that even meant until a couple hours ago but still tried that tool, just in case - it says "Good news, your phone isn't Walshed!") and the Windows Phone Support Tool says the phone's not in a "Connect to PC state", even though it is.
To sum up: nothing works.
Oh, almost forgot: I then saw the post about the USB drivers, it's version is 4.8.2148.0 but it says it's the last version so it won't update, and when I unsinstalled it, it automatically installed the same version.
Click to expand...
Click to collapse
odd, the latest drivers are 4.8.2345.0 and these were installed a week before Mango was released to prepare the phones for Mango. Not sure why it would give you an older USB driver....
I updated the USB driver but the problem stays the same, not sure what else could be done
derausgewanderte said:
sounds like a USB driver issue.
open Device Manager
open Zune
plug in the phone into the USB
In the device manager you should see Windows Phone USB Device at the very bottom come in.
Double click and double click Windows Phone USB. Got to Driver tab and make sure it reads Deiver Version 4.8.2345.0
if you have something older, uninstall the driver, unplug the phone, then plug it back in and hopefully it will pick up the new one.
Click to expand...
Click to collapse
I'm been have the same problem with a samsung focus v1.3, i've tried everthing i could find, but nothing worked. I hope someone has an answer to what causing this.
I've reflashed the phone with both the rogers and at&t roms(many times) but can only get to 7403.
Also i have tried 4 different computers, one was ever XP.
i am getting the same update error with my Branded HTC HD7
Same error Omnia 7.
Posted it at MS forums: http://answers.microsoft.com/en-us/...-omnia-7/779a50b6-2080-40da-b106-c8b365c25372
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
DesiChoza said:
Same error Omnia 7.
Posted it at MS forums:
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
Click to expand...
Click to collapse
how did u revert back to 7392 update and which registry settings did you tweaked? would u mind sharing it with us? i have done hard reset on my phone but the os version is still 7.0.7043 and since i reset, there is no backup in zune to revert
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Try This?
fouros said:
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Click to expand...
Click to collapse
Not to be insulting, but did you try the Walsh Tool and select ALL languages that are on your phone. Most people who have gotten to the end of the MANGO update and failed with this error code fixed this with the Walsh Tool. Please don't dismiss it out of hand, it has solved this error code issue with a lot of people.
JamesAllen said:
Not to be insulting, but did you try the Walsh Tool and select ALL languages that are on your phone. Most people who have gotten to the end of the MANGO update and failed with this error code fixed this with the Walsh Tool. Please don't dismiss it out of hand, it has solved this error code issue with a lot of people.
Click to expand...
Click to collapse
i am not insuted and yes i did use the Walsh tool with the program saying my HD7 was not in a walshed state
pretty confused at the moment on what next to try
DesiChoza said:
Same error Omnia 7.
Posted it at MS forums:
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
Click to expand...
Click to collapse
Could you please elaborate?
Just to add to this, my brother inlaws focus, which i flashed with the rogers rom(It was a gift), installed the mango update yesterday morning. His phone is identical to mine.
fouros said:
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Click to expand...
Click to collapse
I am now on Mango
i had to use another telstra ROM for the HD7
http://forum.xda-developers.com/showthread.php?t=993186
installed this , forced update and now Mango tastes sweet
Hello all,
like many users i've forced the mango update on my Omnia 7.I ended up with firmware version 2424.11.8.2.
However, i read that most of the users that got the update the "normal" way got firmware version 2424.11.8.5, so i rolled back to NoDo and updated again - still i get 2424.11.8.2.
So my question is - is my firmware ( 11.2 ) mango, or do i need to update my phone manually somehow?
Anyone knows what's the difference between 2424.11.8.5 and 2424.11.8.2 ?
My samsung now app doesnt auto-refresh also..could this be related to the firmware ver?
When you say "forced" the update, what do you mean?
Also, when you rolled back and then re-installed, did you need to do anything special to re-install?
Bocko92 said:
Hello all,
like many users i've forced the mango update on my Omnia 7.I ended up with firmware version 2424.11.8.2.
However, i read that most of the users that got the update the "normal" way got firmware version 2424.11.8.5, so i rolled back to NoDo and updated again - still i get 2424.11.8.2.
So my question is - is my firmware ( 11.2 ) mango, or do i need to update my phone manually somehow?
Anyone knows what's the difference between 2424.11.8.5 and 2424.11.8.2 ?
My samsung now app doesnt auto-refresh also..could this be related to the firmware ver?
Click to expand...
Click to collapse
2424.11.8.5 is the Mango update with Samsung drivers and 2424.11.8.2 without.
If you wanna enable Internet Sharing feature you need firmware 2424.11.8.5, this you can also do manually with Cab sender... just search here in the forum.
I flashed back to a branded T-Mobile rom for getting firmware 2424.11.9.4, with my unbranded Samsung rom I couldn´t update the firmware.
GoodDayToDie said:
When you say "forced" the update, what do you mean?
Also, when you rolled back and then re-installed, did you need to do anything special to re-install?
Click to expand...
Click to collapse
I mean i used the cable trick (google it) to get the update b4 it was available for my phone through zune.
After i rolled back i installed in the normal way - didnt use tricks, zune said there's an update, so i updated.I guess this is the official update for my phone.But i dont get it, why it comes without samsung drivers..
Unbranded phone
As I understand it if you have an unbranded Omnia 7 then you will only have 11.8.5 and that does not give you tethering. For me to get tethering I need the firmware update that only seems to come from the carriers themselves which leaves me in the lurch.
I do not want to faff about with unlocking them especially as I have 3 unbranded phones I guess I will just have to wait and see what Microsoft push out to us plebs. You can of course install the firmware if you phone is unlocked and you will find plenty of instructions on how to do this.
Hello,
After following the following thread http://forum.xda-developers.com/showthread.php?t=1306415 ([CAB] Official WP7 Updates List: 7.10.8107 + ALL LANGUAGES complete + OEM updates) to the letter I repeatedly receive the same error on two different PC's. UpdateWP: (Device ID Left Out) Update Error C00D070A There's a communication error with your phone.
If I run UpdateWP.exe /list I can see my device.
I read through the entire thread, all 75 pages and could not find an answer to my problem. I also scoured the rest of the site for two days to no avail. @jellenl post: Problem with 'WP7 Update Cab Sender' http://forum.xda-developers.com/showthread.php?t=1291536 was the closest reported issue similar to mine. I have replied to that post and am waiting for additional information.
Any help would be greatly appreciated, the newer software is needed to address the Exchange 2003 bug on our phones.
Verizon HTC Trophy MWP6985
OS Version: 7.10.7720.68
Firmware revision number: 2305.13.20110.605
Hardware revision number: 0003
Radio software version: 1.53.00.12.01_23.17w.05.13U
Radio hardware version: 3.2.3.D4
Bootloader version: 2.1.230513.10
Chip SOC version: 2.3.0.5.13
PCs: Windows 7 Professional SP1 (tried 64bit and 32bit)
Thanks -Airstream
Problem Solved!
After manually backing up my data (there are automated tools you can use) I factory reset my phone and attempted an update to 7740 using the following tool http://forum.xda-developers.com/showthread.php?t=1315179 with a custom CabData.xml that I created for my phone (VZW Trophy). I updated my OS (7720) and Languages (English - United States (0409) and Spanish (0C0A), the two languages installed by the default) to 7740 successfully, and then updated OS and Languages to 8107 succesfully. After the update process I reseated my battery and factory reset the phone once again, and as expected the latest OS 7.10.8107.79 (8107) is still present on my phone.
It's important to note that I have a factory ROM and my phone already had it's firmware updated automatically (via Zune) to the levels noted in my original post. I believe the WP7 Update Cab Sender would have worked as well but preferred the slick interface wCabSender provided, thanks guys!
No thanks Verizon and HTC, a BIG Thanks to all at xda-developers!
How does your phone work using this method? I attempted to cook a rom with 8107, but Phone app would't load anymore. XD
Also, using this method, can you dial ##PST# without the phone freezing? The current DFT Freedom V1 from Verizon Wireless Trophy can't use ##PST# with their cooked 8107.
I have yet to try to manually update to 7740+ and beyond. I wish VZW would get off their butts and support our phone, but I'd wager that we've seen the last updates. Verizon isn't even interested in putting more WP7's on the network last I knew.
Also, how did you edit CabData.xml?
@TheXev, Thanks for your post
As I mentioned earlier I have a factory ROM (at no time did I ever attempt to alter the phone), We purchased the phone a month ago to test in our enterprise (as a BlackBerry alternative - we had already tested iPhone and Android and were not happy with the results) and it wasn't until we rolled out a second device (beta group) that we discovered the Exchange 2003 bug (email responses had original data removed) and determined via the Windows Phone Website that OS 7740 had corrected that bug. I still am not clear on why my phone would not upgrade without a factory reset, but it was a small price to pay for the bug fixes and enhancements brought through to OS 8107.
I wasn't aware that I could dial ##778 for field diagnostics (thank you for that information) my phone dials the number correctly and without freezing.
If you decide to upgrade I would encourage you to use the wCabSender, it can be found at this forum http://forum.xda-developers.com/showthread.php?t=1315179 I have uploaded my updated CabData.xml at the end of the thread.
On a side note I already had the Windows Phone Engineering Flash Tool installed on my machine when I attempted my upgrades using WP7 Update Cab Sender, this tool is not installed with wCabSender and I'm not certain if it's necessary, if you run into trouble using wCabSender (it not launching) you can download WPEFT from this forum http://forum.xda-developers.com/showthread.php?t=1306415 also keep in mind that wCabSender has prequisites (I believe) .NET Framework 4.x, etc.
As I mentioned earlier I have uploaded the edited CabData.xml via another forum, my updated version includes the latest Firmware: 2305.13.20110.605
and Radio software version: 1.53.00.12.01_23.17w.05.13U and all OS updates and Language packs (Eng. and Esp.) needed for a Verizon Trophy. The wCabSender's slick interface allows you to download the updates into the /Downloaded directory. The CabData.xml can be found in the /Models directory and can be updated by a text editor, I used notepad.
It is unfortunate regarding Verizon and their apparent lack of enthusiasm for WP7, we have hundreds of devices (mostly BB Not WP7) and even their T2 Enterprise Technical Support was unable to confirm if they had received notification for the update. HTC reported the same information and redirected me back to Verizon. Hopefully in the future MS can push the updates directly to the phones, until then I will continue to use invaluable resources like xda-developers to overcome these issues. Thanks Again!
I believe MS has a hit on their hands with the Windows Phone, which I believe will become more apparent with the release of Windows 8.
I concur on all points. Last night I was able to upgrade the stock 7720 rom to 8107 and have a working phone (I missed the language pack between 7740 and 8107). I used cooking methods and HSPL, so I didn't have to modify any files after tinkering.
In an enterprise environment, it isn't a good idea to void the warranty of the equipment with HSPL (or open up another can of wax my using an a unlocked phone).
I'm glad to see the phone fully works with 8107, but I have to wonder why Verizon didn't at least push the 7740 update for the reasons you stated.
I'll have to continue to work with DFT to see if we can figure out why their testing rom doesn't run ##PST#. My current 8107 build works fine with ##PST# now, but I haven't been able to fully unlock it (here is to tonight's digging).
So I used the disconnect internet trick and got Tango to install on my phone. Problem is, it stopped with the 3 updates and did not install (or find) the Samsung one that I know was supposed to be installed (for firmware), so my firmware is now 2103.11.10.1 instead of what it is supposed to be.
Does anyone know a way to force the OEM firmware to be sent to Zune. The internet disconnect trick isn't work now, so I'm stuck. Also, my backups aren't showing up, even though during the update process it said it was creating a backup (for all the OS updates it installed all the way up to 8773).
If there is no way to get the OEM firmware to be pushed, does anyone know how to get the Focus Flash to stock? I know I have a backup on my computer, but Zune isn't recognizing it (I had forced 8107 on my phone, and Zune made a backup of that ROM).
I just updated to Tango using the cab sender on my Focus Flash. Everything worked fine. My firmware ver. is the same as yours. It has been that rev since as far as i can remember. I don't think there is a firmware newer than that for the Focus Flash.
Firmware is 2103.11.10.1
OS ver is 7.10.8773.98
b4malevolent said:
I just updated to Tango using the cab sender on my Focus Flash. Everything worked fine. My firmware ver. is the same as yours. It has been that rev since as far as i can remember. I don't think there is a firmware newer than that for the Focus Flash.
Firmware is 2103.11.10.1
OS ver is 7.10.8773.98
Click to expand...
Click to collapse
Someone at wpcentral posted this for their Focus Flash:
Look like Firmware Update, Radio Software, BootLoader
Firmware Revision 2103.12.05.04
Hardware Revision Number 23.1.0.8
Radio Software Version: 2103.12.5.4
Radio Hardware Version: 0.0.0.6
BootLoader Version 6.5.17.0
Chip SOC Version 0.74.21.1
So there must be one out there (plus, everyone else has been receiving firmware updates, like Nokia, so I can't see Samsung not making one).
Since you used the debrand trick to update to 8107, you'll most likely have to reset your phone to get the Samsung update. I did the same thing & then did the cab send method to update to 8773. Didn't have any problems. Kept trying to get the Samsung update via the disconnect trick. No luck. As soon as I reset my phone, it popped right up. I'm installing it now. Good luck.
Steve