Hi Guys,
I recently installed an Ansar Rom for Vodafone New Zealand, which was 7004.
I then updated to 7008 through zune no problem, but when I attempted 7392 that when I ran into problems.
I have tried about 5 times, Hard Reset, Walsh Tool, Reinstalled Original Rom but still I get Error 80180048
I did unlock the device with Chevron7 via the cert hack, but that is now removed.
I have spent the last week searching forums and reading hundreds of posts, but nothing to fix my current issue.
Can anyone assist?
Thanks in advance.
Anyone else experiencing this issue?
I have the same problem
I have done everything including wash toll could not update it
oguz25 said:
I have done everything including wash toll could not update it
Click to expand...
Click to collapse
So, you getting the same error? What ROM did you flash ?
same issue
am getting same error...
I have HTC Surround I used RUU_Surround_Cingular_US_1.03.502.07_Radio_5.51.09.06_22.30.50.09U_by_ansar for flash. My current version is 7390 but could not upgrade it. I also have problem with touchxperience (WP Device manager) I could not install it.
Related
Hi,
Hope you can help me out here because it is driving me nuts.
I have a Trophy here Rom 1.20 officially build 7389. After install it updated fine to 7392.
After that I developer unlocked the phone and edited the registry for additional languages. I started provisioning and in a few steps I was at 7403.
After that the phone will not update to 7712. The update starts, downloads updates, restarts the phone and that's it. After a 5 minute time-out the phone reboots and it quits with an error. Whatever I do it won't upgrade.
Have you guys seen this before and is there a solution ?
Thanks a lot !
Maybe stupid question....but... Did you hspl ?
No, it's not HSPL-ed. Just a stock ROM.
I not sure, that is it stock ROM. So, try to another way. Unlock phone, do hspl and flash it. Where is problem ?
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.
As many of you probably know there is an issue with the DFT HSPL and the Mango update resulting in the device no being able to be detected in bootloader mode (one line on the tri-colour screen). Is there a fix available alredy or not yet? Because I can't flash the official mango update for my Vodafone Trophy because of the abovesaid reason. Any suggestions or help would be really appreciated.
I got the same Problem.. hope there is some genius soon that has a solution
so... noone? not even a clue? a lot of people have this problem..
iconata said:
so... noone? not even a clue? a lot of people have this problem..
Click to expand...
Click to collapse
probably the easiest method will bee having a ffu file to use with the updatewp or in alternative the cab.pks file with the spl
these are the files signed by ms to be deployed using updatewp
... ultimately we shall wait for the next official update that will be deployed from Zune
decebal said:
probably the easiest method will bee having a ffu file to use with the updatewp or in alternative the cab.pks file with the spl
these are the files signed by ms to be deployed using updatewp
... ultimately we shall wait for the next official update that will be deployed from Zune
Click to expand...
Click to collapse
I've received the HTC update for Windows Phone through Zune yesterday, update that contains SPL and radio, phone rebooted twice immediately after the update and still no good bootloader, so no luck with that.
thats all bad news.. for now we are stucked with this problem
same problem here
note to self.. never use custom rom until someone has the solutions to ALL of the problems.
Did you already tried goldcard method. This flashes also the bootloader.
herlek said:
Did you already tried goldcard method. This flashes also the bootloader.
Click to expand...
Click to collapse
a guy in HD7 forums have already tried this, without success.
http://forum.xda-developers.com/showpost.php?p=17764002&postcount=11
The only way I see after all this attempts is directly flashing mermoy with JTAG
only way to fix this is by " http://gsm-technix.de/shop/produkte/19/1/10/htc/ "
I used this after testing custom spl/radios and ofcause **** can happen
20 euro + 6.90 euro and your phone is fixed for German people
(it worked for me and got my phone back in only 2 day's )
iconata said:
note to self.. never use custom rom until someone has the solutions to ALL of the problems.
Click to expand...
Click to collapse
Correction:
Never use Custom ROMs without reading the forum or read the chef instructions first. If people are too lasy to read dont mess with your phones.
jup correct.
And if you want to test/dump/build/cook be prepared to get a bricked phone
iwas have same proplem an i tried all those methods :
*fomat device
*restore backup
*creat goldcard
*replace card
*flashing rom via xtc Clip Box
*Y-Cable Method
And all failed
at end i relpaced the device
Have any of you recieved the Mango update?
new news pls help us
Not new info
Hi friends. I have found this forum thread too late, then I have made big discovery myself. My results are on http://forum.xda-developers.com/showthread.php?p=19345839#post19345839 , but probably nothing new for you.
solve
Dar all
I had use DFT mango coustem Room till the mango update comes in market from microsoft
use same DFT program 1- DFT_RSPL_WP7FG1_LAUNCH / 2- DFT_HSPL_WP7FG1_INSTALL """but select the 1 option""" then install orgenal shipped ROM (old V. WP 7) to get back the orginal HSPL
then it be easy to update to WP 7.5 by Zune
(my HD7 worke fine and normal update by Zune)
Sorry for my English
yeah.. if i repair my phone i plan on using the RSPL, not HSPL.. but i have to wait a few more days till my cables arrive and i'll try to goldcard flash it.. and hope it works.. thnx for the info by the way
iconata said:
yeah.. if i repair my phone i plan on using the RSPL, not HSPL.. but i have to wait a few more days till my cables arrive and i'll try to goldcard flash it.. and hope it works.. thnx for the info by the way
Click to expand...
Click to collapse
If you are going to using stock or shipped ROM you will not needs Gold card "only if your phone is louked then you needs gold card)
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
8018004D, is the error I get when I try updating through CAB Sender.
I'm already on the newest update, Mango, but according to heathcliff, my rom and samsung firmware was too old, so I needed it anyway, but well that's not really working. My device is Interop unlocked, but the Rooting will not work because "my device is not supported, whilst I'm on an Omnia 7.
I got kk2 update, so i flashed back to november 2010 or something liked that, than update to mango, unlocked it, and it updated through zune, without me really noticing ... But well Rooting is the problem here... and the CAB sender
Who can help me out?
Kristan