I got an 820 from Nokia, the one they've sent to me lists itself as an "NV EURO TRIAL" on the packaging.
The firmware running on it is 1232.2107.1241.1000 which is quite outdated now.
I tried to update it many times from phone update option in phone settings but it just says phone is updated.
Whereas Nokia website shows that latest version is SW 1232.5957.1308.00xx
I got a method of updating via nokia software updater for retail.
Is it safe to use it?
My phone is out of warranty and has no problems right now.
should I try it?
Related
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
I just replaced my LG Optimus 7 for a new one, after it died. Unfortunately I now do not receive any updates and can't really figure out why.
I looked through xdadevelopers and other boards already but could not find any help.
My problem: Zune searches for updates but ends in telling me that my phone is up to date 7.0 (7004). On my old phone I received all updates as I should have received them... But not on the new one.
What I already tried without any success:
- Tried the update on two different machines with latest Zune
- Tried it already for half a week to see if it just takes a while
- Rest the phone to defaults
- Also tried the trick to disconnect the PC from the network that worked for the Mango update. Also not successful
Phone: LG Optimus 7
FW: 7.0 (7004)
Carrierbranding: OPN
Carrier used: Swisscom, in Switzerland
I am really grateful for any kind of advice! Thanks so much!
Maybe your carrier hasnt provided updates after 7004 update
amritpal2489 said:
Maybe your carrier hasnt provided updates after 7004 update
Click to expand...
Click to collapse
I am using an unbranded phone now (OPN). The one before was Swisscom-branded and I got all updates.
I suggest you flash your phone with a different ROM.
http://forum.xda-developers.com/showthread.php?t=935578
day2die said:
I suggest you flash your phone with a different ROM.
http://forum.xda-developers.com/showthread.php?t=935578
Click to expand...
Click to collapse
Thanks! Flashed to a branded ROM, now everything is working fine again, must have had a weird SW image...
So as you know 3 days ago a small OTA update came out for Verizon which is pretty much the same one AT&T received last month. On wifi I tried to download the update via OTA on the phone, my phone is not rooted and when I tried to download it it just failed in the middle of downloading and I got the error code 503. The wifi I'm using is very fast and steady and nothing else on the phone is having an issue at the moment. So I tried to download it again and it told me that the software currently installed on the phone(original phone release date software) is the newest up to date software. So I called Samsung and told them the situation along with the new build number "VRU1AOD5"(from the new OTA not installed on my phone yet) and software version number currently installed on the phone(5.0.2) and they told me that I'm up to date 5.0.2 and that to their knowledge they never heard of the update or build number I gave them and there was no update for Verizon. So how I can redownload the OTA? because for 3 days now I'm unable to download the OTA due to the 503 error from the very first time I tried to download the update.
What is mind boggling to me is how Samsung the creator of the device has no idea of this update so they can't even help me out. Then they're basically telling me how the hell am I getting the 503 error when I have the latest build(according to them) and software update which is not the case here and I told them that.
Use the Odin file in the return to stock thread
I currently have an Ascend Mate 7 with firmware version B331, and I am in Europe. This morning my phone started downloading the update to B571, it asked for a reboot, started updating and gave an error at 4%, that it cannot unzip the file (or something like that) and that I must redownload. I performed this operation 3 times, with the same result? Is Huawei incapable of providing an update for their own phones? Is there another way to perform the update?
Also, my phone's certification is Serbia, although I bought it from Mediamarkt in Germany.... ?
Ok, so for anyone with the same issue, this solved it : http://forum.xda-developers.com/showpost.php?p=68093722&postcount=4
Just recently bought this phone, and after scouring this forums the past few days I found that the EMUI that shipped with my phone is 4-5 months old (Dec '16) and that there have been multiple updates since, even though the OTA on my phone says I'm using the latest version. This scares me, not so much for features, but because of potentially missing security patches.
Looking at hwmt.ru's listings, there's a lot of updates, and for my specific model the latest OTA is B181, and the latest "full" update (I assume these are whole images) is B156.
Can I download the B156 updates (basically the same way used when rooting the phone) to update the stock ROM?
And if that is correct, what are all the listings on that site under the "A" (or "Тип") column with "OTA" for?
Download the firmware finder app for android and update through it: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You probably won't be able to update to 181 though... You'll have to test which ones you can install. Huawei needs to approve each firmware version before we can install through system update.
B181 didn't work, authentication error, gonna try the other way and work my way up instead.
Nice that someone made a tool to automate this though, even though it's a hacky way
Nevermind that, every single version gets that authentication error, even the ones older than the one I have currently installed.