Database Info

[Q] Can't get my Diagnosis App to Update [Omnia 7]

Hi,
I'm trying to maintain a jailbroken phone through the Mango update via the following method:
http://forum.xda-developers.com/showthread.php?t=1152422
My only trouble, is that I haven't been able to update my Diagnosis app.
It's on 0.922, which will not allow the xml files to be found.
I have tried uninstalling and then hitting "##634#" but each time, it only brings back the same 0.922 app.
I am also unable to find it in the marketplace.
I am currently running OS 7.0.7392 - and Zune tells me there are no further updates (not sure what 7932 is?).
Can anyone help?
Cheers.

I'm having the same problem. I was on 7390 with 0.922 and couldn't update it, so just updated to 7392 and it's still on 0.922 (have tried uninstalling and reinstalling it with no luck either).
There are a few other solutions I've yet to have tried, but it's not looking likely so far...
Note: In regards of this "If your phone is updated to 7392 with the OEM registry information (ATT-US) deleted, the Diagnosis won't be updated." - I think I had deleted the registry while on 7390 (I'm with 3, not AT&T), but I'm not sure how to re-add it. Re-flashing maybe? Though it'll be a pain adding everything back.

How would you have deleted the registry?
I'm from Australia, so my phone was bough on Optus, but is now unlocked on 3.

I can't remember exactly but it's something to do with the SamsungRegistry tool I used when first unlocking my phone. I vaguely remember reading a STRING value and then overwriting it as a blank value.
I was following a guide very closely but now I can't remember what it was for so I can't find it to undo it.

Racxie said:
I can't remember exactly but it's something to do with the SamsungRegistry tool I used when first unlocking my phone. I vaguely remember reading a STRING value and then overwriting it as a blank value.
I was following a guide very closely but now I can't remember what it was for so I can't find it to undo it.
Click to expand...
Click to collapse
I remembered it seems like HKLM\System\Platform\DeviceTargetingInfo\MobileOperator, maybe you can have a try.
it is heard that if the WP7 updated to mango, the Diagnosis will be upgraded too. I don't know whether it is true. Or you can flash another ROM, such as DTMJJ6, I'm using it and it works well.

hello
i have the same problem , cant update the diagnosis. i tried everithing , but nothing works.
i installed the 7720 mango rtm , and there is no update for diagnosis so far )
i think the only way is flashing another rom.
the DTMJJ6 will update the diagnosis ? is this an branded rom ? 7004 ?
Edit : DTMJJ6 is not an public rom.(samfirmware) what about the november rom?
EDIT2 ": the november rom contains the 1027 versin of diagnosis app .. it works.. its unbranded too..
thanks for all

sun10 said:
hello
i have the same problem , cant update the diagnosis. i tried everithing , but nothing works.
i installed the 7720 mango rtm , and there is no update for diagnosis so far )
i think the only way is flashing another rom.
the DTMJJ6 will update the diagnosis ? is this an branded rom ? 7004 ?
Edit : DTMJJ6 is not an public rom.(samfirmware) what about the november rom?
EDIT2 ": the november rom contains the 1027 versin of diagnosis app .. it works.. its unbranded too..
thanks for all
Click to expand...
Click to collapse
That sounds great! Do you think you'd be able to give a link to where you got the November rom from? And if you can a tutorial on how to flash it. Those two would be very much appreciated as I can't seem to find them (or don't know what to search for)
Edit: Found it, thanks very much! Hopefully I'll now be able to update to Mango without losing my unlock.

[Q] Update Mango fails every time

Today Zune prompted that the update is available so I started the update. It fails every time I try to update my phone :-(
I am already om 7720 but still Zune (and my Phone) pop up the update message.
I even did a full reset of my phone but still the update fails.
At step 5 it stays on 0% and the phone restarts.
Then step 6 and 7 (installing updates) ... again the reboot ..
Message on the phone:
Update Unsuccesfull
Unfortunately , we weren't able to update your phone. Refer to the Zune software or Mac Connector on your computer to find out what happened. Or if your're already closed this software, go to windowsphone.com for guidance.
See attached pictures.
Error code which I get is: 8018001E.
Need Help!

If you already did a full reset you can as well roll back to NoDo from your backup and try from an offically support version (7392).

How do I roll back?

rudma said:
How do I roll back?
Click to expand...
Click to collapse
Friend, if you have to ask this question, then I'm wondering if you truly knew what you were doing.
---------- Post added at 03:02 AM ---------- Previous post was at 02:58 AM ----------
Ok, I used to get this error when I tried to update my firmware by changing my carrier code using Samsung Registry editor. As it turns out, Samsung firmwares are kinda locked to carriers. I tried Tmobile, Orange but the firmware would not install, getting the same error code as you did.
I had to wait for Samsung to release the firmware for my carrier.
Did you do anything to your LG phone? Like changing carrier code? If you did, you'll have to change it back.

Seems to be pretty common problem for LG E900: answers .microsoft .com/en-us/winphone/forum/wp7-sync/lg-e900-update-error-code-8018001e/1ec8d54d-0ee8-4db6-ab62-4ca26b3fbbe7?page=1&tm=1317157055038
(can't post links yet)
I'm experiencing it too... ;/

Ok, I will chech the link later.
Thanks!

Hmmm
I think I figured out what is going on. Apparently Mango needs the latest firmware from LG to be installed on the phone. This was given to branded phones but not to unlocked/unbranded phones like mine, a few months back. With the firmware update the LG Optimus 7 will jump from:
Firmware Rev 1.0.7.10
Hardware Rev 1.0.0.0
Radio Software 1.0.7.10
Radio Hardware 0.3.5.0
Bootloader Ver 1.5.0.0
Chip SOC 0.30.2.0
to:
Firmware Rev 1.0.10.10
Hardware Rev 1.0.0.0
Radio Software 1.0.10.10
Radio Hardware 0.3.5.0
Bootloader Ver 1.5.1.0
Chip SOC 0.30.2.0
People who successfully updated their LG E900 to Mango already had that phone, from the little research I have been doing in the past few hours. So all we need is the firmware update from LG to be installed and I am hoping that this will allow us to go ahead and install Mango.
______
Marios
www.kariosgames.com

Error code 80180048 when updating to mango

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

[Q] No service or just for a seconds :(

Hey guys Ima need your help here:
Yesterday I was updating my Samsung Omnia 7, it has Mango installed but SFR-FR made a new OEM update available with improved firmware and bootloader. So I changed my carrier from 000-88 to SFR-FR, and started updating. From here everything went wrong: error codes floating around, workarounds wouldn't work either, so I thought: let's take a fresh start.
I flashed a UK retail rom (pre-NoDo or something), updated my device to Mango, did the same as I did above and now I was able to install the update successfully. But since everything went wrong, I am stuck with one problem: I have no service, or just service for a few seconds.
With my SIM card is nothing wrong, tried it out in other devices. So I guess it has to do with those updates: maybe one screwed up my firmware a bit? I have no clue. It probably doesn't have anything to do with the hardware, I didn't drop the phone or anything else.
I hope you guys have any idea to see what causes this problem, maybe I can do some tests from the Diagnosis app? Maybe there is a registery value that I need to check? Help is really appreciated

Omnia 7 firmware update question

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.