Ok, If you are thinking about flashing one of Ansars ROMs then consider this first.
You may never be able to update your phone via Zune again..
Many users are experiencing Error 80180048 when attempting to update via zune from version 7008.
One thing they seem to have in common is that they have flashed one of Ansars ROM's
Here are some examples...
http://forum.xda-developers.com/archive/index.php/t-1034962.html
http://answers.microsoft.com/en-us/...80180048/ceb86673-e65a-e011-8dfc-68b599b31bf5
http://simonwilkins.wordpress.com/2011/04/02/march-update-nodo-for-wp7-arrives/
http://www.pocketpc.ch/windows-phone-7-allgemein/128982-fehlercode-80180048-update-7-0-7392-0-a.html
Plus a number of others on this site...
I have asked for assistance from ansar, and he provided another ROM, which caused even more problems and caused my device to not be detected by Zune or windows.
I know ansar works hard on these ROM's, but I think its important they you all know the risk and don't get stuck in the situation I am in, where I will now have to purchase a new handset.
Ansar: If you can at least acknowledge this issue and confirm that you are working on a fix that would be great, otherwise I believe this Thread is important as a warning to others.
Thanks
WP
Agreed. Verizon Trophy users flashing 0.82.605.02_Radio_1.25.00 are left with unusable devices until an official ROM is able to be flashed.
Be warned.
I flashed my trophy a few times ..
1. RUU_Spark_HTC_Europe_1.10.401.04_Radio_5.52.09.16_22.33a.50.10U_by_ansar
2.to NoDo via zune
3. Zune (nodo) to mango
4. forgot to unlock it before
5. We are back at RUU_Spark_HTC_Europe_1.10.401.04_Radio_5.52.09.16_22.33a.50.10U_by_ansar
6. NoDo via Zune
7. Zune (nodo) to mango (unlocked this time)
So i guess everything fine here
Ok, So the solution for me here was to Unbrand my device with a "Y" Cable and flash
RUU_Spark_HTC_Europe_1.20.401.00_Spark_5.54.09_RELEASE.
Once I was on this rom, I was able to update no problem through Zune to 7392.
Basically the ROMS by Ansar seem to be problematic and he isn't willing to provide any support. So, I suggest avoiding flashing them, unless you want problems in the future.
Related
My phone currently updating to version 7008 - needs update to Zune too which is downloading first.
Was on 7004.
Will let you know what happens!
I can't see any changes...
Also no saving of the changes you make in Camera or so on...
Is this the update before March Update!?
Yeah, this is just an update to pave the way for future updates. You'll find nothing new here.
skycamefalling said:
Yeah, this is just an update to pave the way for future updates. You'll find nothing new here.
Click to expand...
Click to collapse
Is the Camera any better...? could be into the realms of imagination here but took a photo and it seemed clearer than previous efforts on standard settings. Phone also 'seems' a little zippier.
Not totally sure so guess things aren't that different.
Backup worked nicely though.
Mine is in the process of updating. The backup process takes a while.
I wonder if we can use someone elses backup to restore a phone? I only ask because I flashed my UK T-Mobile device with the unbranded Samsung one because it was said that it fixed Bluetooth problems. However, it has had no effect, and now I can't take my phone back to T-Mo because it's not running the original firmware. If I can get it back to UK spec, then I can take it back to a shop and swap it for a (hopefully) working one...
Done. It is only a preparatory update for the actual update containing copy and paste, improvements to Windows Phone Marketplace et.al. Ergo, it doesn't contain any new functionality and won't remove or hinder any installed jailbreak functionality.
Yup, more playing, definitely no changes I can find...camera taking a better photo just happened to be a picture in better light.
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Sorry for that. I was afraid of this happening to me when the update stalled at the 7th step
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
Sorry about that. I was afraid of this happening to me, after the update stalled for an hour at the 7th step, so I disconnected. Luckily nothing happened to my device. But apparently several Omnia 7 are experiencing this.
Sort it out, MS.
First things first. I was updated Zune to the recent version, because I was curious it will resolve a problem with login user on one of my computers. One (Windows Vista) works fine, but another one, Windows 7 (both 32-bits versions) works fine with Zune + Market.
Silent Shark said:
I wonder if we can use someone elses backup to restore a phone? I only ask because I flashed my UK T-Mobile device with the unbranded Samsung one because it was said that it fixed Bluetooth problems. However, it has had no effect, and now I can't take my phone back to T-Mo because it's not running the original firmware. If I can get it back to UK spec, then I can take it back to a shop and swap it for a (hopefully) working one...
Click to expand...
Click to collapse
I've done the same. I have (branded) T-Mobile UK phone and decided update to unbranded one. I choose version I8700XENJK1 (but I tried another one before) - for me, one difference is language Dutch / Belgium if I remember correctly.
I've read this thread and I was wondering if my phone will find update... I had no information about this.
I return home, connect Omnia to computer and update process start immediately. I had no problem with update at all. Phone during update reboots twice (or more) and it looks stable. I haven't noticed any changes or improvements... maybe it's working a little bit faster, but maybe it's a auto-suggestion.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. (...)
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
Sorry for that mate. I really had not problem with update.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
have you tried taking back battery and then reboot again?
http://twitter.com/#!/WinPhoneSupport
hard-reset Focus, should be similar to omnia 7
http://www.technipages.com/samsung-focus-hard-reset-using-hardware-keys.html
Update error
801012DD Error code - we couldnt create a backup of your phone
Help !!!!!
Have you got samsung tools installed?
I have tried twice to install the update. Both times I got stuck at 7 or of 100 with 100%.
The only thing I have done my phone is to unlock it with chevron.
Altough I did have it in flight mode at the time to prevent relocking.
Do you think that would have affected anything?
Still nothing showing up for me yet. Those who got the mini update does your 3 button combo into download mode now work if you had a phone that didnt let it happen before?
Lordao
lordao said:
Still nothing showing up for me yet. Those who got the mini update does your 3 button combo into download mode now work if you had a phone that didnt let it happen before?
Lordao
Click to expand...
Click to collapse
Three button combo now gives me the rather scary option to Format or Cancel. I thought Cancel would be the way to go....
Successful Updaters: Please post your Firmware revisions
For those who have managed to get the update installed without error, can you please post here your firmware revisions. We may be able to work out which models are affected by the issue.
There are rumours that this update only affects firmware versions JI9 and JJ4 while the JK1 firmware is unaffected.
http://www.zdnet.com/blog/hardware/windows-phone-7-update-bricking-some-samsung-omnia-handsets/11501
gc48067 said:
Three button combo now gives me the rather scary option to Format or Cancel. I thought Cancel would be the way to go....
Click to expand...
Click to collapse
Are you saying the Download Mode is no longer accessible after updating?
scoob101 said:
For those who have managed to get the update installed without error, can you please post here your firmware revisions. We may be able to work out which models are affected by the issue.
There are rumours that this update only affects firmware versions JI9 and JJ4 while the JK1 firmware is unaffected.
http://www.zdnet.com/blog/hardware/windows-phone-7-update-bricking-some-samsung-omnia-handsets/11501
Click to expand...
Click to collapse
How can I check which firmware revision I am using?
Hey all. I am currently an android user looking into trading for a focus.
Problem is, the phone had WP7 chevron run on it and now has the nodo update.
My question is; since MS said no more updating for phones with chevron run on them, can I remove or revert to a non chevron installed state? From what I have read here, nodo "breaks" chevron, does that mean I can install future updates?
I just want to make sure I dont trade for a crippled phone...
I got the Samsung update after the NODO. Mine was Chevron 7 updated for NODO.
Where did you get the Samsung update? How did you apply it?
Also, is there a way to flash the original OEM firmware to get a "stock" phone?
Waiting to see
I used Chevron on my Focus so I could debrand it and used the timing trick to get NoDo myself, so after the MS release, I spent a while poking around online. As near as I can tell, what MS was warning against was the use of the chevron updater tool, not the original unlocker. MS had already said NoDo would basically "fix" the original chevron hack, so, I think they had that covered. If it was just an unlocked phone that got the update naturally through Zune (even if by trickery), it should be within what they expected. But, the updater apparently forced the NoDo update using some other function on the phone, and that seems to be where the worry is coming from.
But, in the end, if you don;t have a Zune backup from before the update (mine didn't successfully keep them, so, no rolling back for me) the only thing any of us can do is wait for either the next release and see what happens, or for someone to figure out how to get a rom. So far, I'm expecting to see the update first, but, you never know.
I am new to WP7 and would hate to get a crippled phone. Thank you both for your info.
I used the chevron ulocker. It ran in a DOS command window. It did the pre NODO, then it did the NODO. A few days later, I connected it to ZUNE and it announced there was a Sansung update. It went fine.
1.Chevron actually will not affect ur update. What MS said was using Chevron Updater MIGHT prevent you from further update, but what actually happened is that people used Chevron Updater still got Samsung Firmware update.
2.Get rid of Chevron unlock, is easy, just do a factory reset.
amtrakcn said:
1.Chevron actually will not affect ur update. What MS said was using Chevron Updater MIGHT prevent you from further update, but what actually happened is that people used Chevron Updater still got Samsung Firmware update.
2.Get rid of Chevron unlock, is easy, just do a factory reset.
Click to expand...
Click to collapse
Pretty much what this guy said. I did the NODO timing update on my debranded Focus. Samsung update wouldn't show up in Zune until I did a Factory Reset.
While I was busy stumbling through threads and deployments of xaps to try and get my marketplace to work, I somehow managed to click 'Relock' on my Chevron unlocker, and now I can't get it to unlock again! I get "
-Sorry, I'm having trouble communicating with the phone.
-Please make sure it's connect using USB
-Please start the Zune application" Zune's running and it even says the phone's connected, but I can't sync anything to it because i get a C00D2772 error, and can't get that fixed either. So the problem really is, Zune is connected to the phone, and so is the USB. I also can't deploy anything.
I saw this thread, http://forum.xda-developers.com/showthread.php?t=922853, but I have NO idea what its saying.
I recommend to flash a newer ROM, not the "original" Leo70 ROM from DFT. Most other "custom" ROMs come with Chevron cooked in.
Maybe you even opt for a "NoDo" ROM, from May/June, they are also completely "free"...
I have a HD2 running wp7 7392. Really want to get mango. Have tried to force (phone airplan mode, laptop wifi off, plug and unplug ethernet cable). I have tried for 3 days and I have done this maybe 200 times. If I pull too quickly,
within a second, I get connection error. If too slow, 2 or 3 sec, I get "your phone is up to date" And I have tried every ms in between but never was able to get the upgrade! Does anyone else have this problem? Do I have to push deviceprovisioning.cab? I did not have to push this cab and was able to get 7008, then 7392 all through zune. But this time I just cant force. Also looking at the microsoft site, t-mobile phone are already in delivery phase! Drive me nuts! Any advise?
Let's see if I got it right you're on NODO with back to the future v2 and waiting for the official mango update?
Then the solution is quite simple: READ the rom thread! It's in the second or third post...
Anyway, here's the solution:
If you can wait for the official update (it's not out yet!), wait
If not (very likely!!), you've got to send deviceprovisioning.cab to get developer updates and then: just continue updating with zune and it should work just fine...
(or you can use the update cabs provide by xbmod...)
But however you're going to do this, read the rom thread. It's better for you, for your phone (much safer!!!)
upate: I can't wait any longer, so I pushed the deviceprovisioning.cab onto the phone. Right away, zune tells me that there is an update available (7403).
I am in the middle of the 7403. Looks hopeful. Just want to update so other who are stuck at the same place could benefit.
HD2 stuck at 7403, fix!
Hi All! Since august 15th 2012 my HD2 has been stuck at WP7 7403. Tried the force Mango trick very often, but didn't succeed. Very frustrating.
I found my solution in this topic, thank you chabun!
With WP7 Cab Sender I send Deviceprovisioning.cab wich I found here: http://forum.xda-developers.com/showpost.php?p=20696473&postcount=4498
After sending Deviceprovisioning.cab Zune showed an update (7720) wich I am installing right now. XDA did it again for me, tnx folks!
Still have not received the mango update. I've been searching and researching this issue for more than 4 months with no luck.
When connecting to zune, it says my phone is up to date with current software version: 7.0 (7392)
i have tried the "walshed" phone fix but that was not the issue.
also, the phone doesnt seem to have full functionality with WPDM and whenever i try and install a .xap file, the application wont launch after being installed on my phone.
the reason i am this desperate is because i want to back up all of my text messages on this phone. my mother passed away recently and it would means a great deal to me that i keep those conversations. if i am able to do this without installing mango, then that is fine by me.
my logic in installing mango is that all of the latest apps such as smsbackup require an unlocked mango device.
i have tried installing WP7 Root Tools so that smsbackup is able to operate on this lg device.
any input would be greatly appreciated, thank you in advance
mmoustafa111 said:
Still have not received the mango update. I've been searching and researching this issue for more than 4 months with no luck.
When connecting to zune, it says my phone is up to date with current software version: 7.0 (7392)
i have tried the "walshed" phone fix but that was not the issue.
also, the phone doesnt seem to have full functionality with WPDM and whenever i try and install a .xap file, the application wont launch after being installed on my phone.
the reason i am this desperate is because i want to back up all of my text messages on this phone. my mother passed away recently and it would means a great deal to me that i keep those conversations. if i am able to do this without installing mango, then that is fine by me.
my logic in installing mango is that all of the latest apps such as smsbackup require an unlocked mango device.
i have tried installing WP7 Root Tools so that smsbackup is able to operate on this lg device.
any input would be greatly appreciated, thank you in advance
Click to expand...
Click to collapse
To backup all SMS and all messages in Messages tile, use SMSBackup. Then try to flash your phone with Telstra ROM, here is the guide.
Note #1: Your phone must be network unlocked first before flashing because you might not be able to enter unlock code once you flashed it to Telstra ROM. The only solution is re-flash to its original ROM then enter unlock code then flash it to Telstra ROM again. You can buy unlock in Ebay.com and price is as cheap as chip.
Note #2: The reason that I suggested Telstra ROM is because it is the only network that give the latest Mango update for LG Quantum, but no sign of Tango.