[Q] The update was downloaded, but couldn't be opened. (8007000d) - Nokia Lumia 820

Hello Everybody,
A few days ago, I tried to check if I have an update possibility. The phone via OTA noted that there is an available update, and started to download it. After the download the preparation went through (it was strange that during the preparation the progress bar from 81% immediately jumped to 95%, but apart from that there was nothing special). After it showed the error message what is in the subject: 'The update was downloaded...' and error code 8007000d.
I've tried to do a search on the net without any luck. I tried to update after a factory reset, of course haven't solved the problem.
Finally, I downloaded care suite, connected to it my phone, and it said that my phone software is up-to-date. So what the f..k? OTA says there is an update, care suite says my phone is up-to-date?
I also tried to find an eligible update from navifirm but for the product code I have (based on the data provided by care suite) there are nothing.
Does anyone have some idea what is going on around my phone?

zsitvayb said:
Hello Everybody,
A few days ago, I tried to check if I have an update possibility. The phone via OTA noted that there is an available update, and started to download it. After the download the preparation went through (it was strange that during the preparation the progress bar from 81% immediately jumped to 95%, but apart from that there was nothing special). After it showed the error message what is in the subject: 'The update was downloaded...' and error code 8007000d.
I've tried to do a search on the net without any luck. I tried to update after a factory reset, of course haven't solved the problem.
Finally, I downloaded care suite, connected to it my phone, and it said that my phone software is up-to-date. So what the f..k? OTA says there is an update, care suite says my phone is up-to-date?
I also tried to find an eligible update from navifirm but for the product code I have (based on the data provided by care suite) there are nothing.
Does anyone have some idea what is going on around my phone?
Click to expand...
Click to collapse
And finally I am on Portico...

Related

[Q] Problems updating to Froyo

**Edit** Sorry just started reading the Rogers 2.2 update thread and can see a lot of people are having the same problem...guess I should have read through that first. Sorry. Will try out anything recommended in there first.
I have a Rogers Captivate, and I'm trying to update to the official Froyo that was just released today.
I've installed Kies version 1.5.3.10113_29 and it finds my phone just fine.
So it pops up to say hey there's a firmware update for your phone and I click on it. It tries to back up my contacts and fails "Failed to Load". Then shows the upgrade window. I click on upgrade and it goes to the first stage of the process "Caution". I hit All information has been verified and the Next and it goes to stage 2 'Information'. I hit Allow saving, (or Proceed without saving, it doesn't matter because i get the same result every time) then Next.
Then I'm greeted with a message saying "MSC.Thunder.FirmwareUpdate has encountered a problem and needs to close."
I've tried every solution I can find and nothing works.
I'm running XP SP3. .NET framework is updated. I even went into the registry and created the Software/Samsung/FUS key that was recommended.
I'm ready to set my face on fire here does anyone have any ideas what's going on?
Thanks.

[Q] Why is my Transformer not updating to 3.2?

Hi everyone!
2 days ago the 3.2 update dutifully popped up on my device. Clapping my hands like a chuffed schoolgirl, I started the update. All seemed to go swimmingly, but on completion and after a reboot I was told the update had failed, and my system had been reverted back to previous state.
Several factory wipes and recovery mode wipes later, and reinstallation to 8.4.4.5 and 8.4.4.11 a few times and I now no longer get ANY updates. I am on 8.4.4.11-WW edition currently which appears to be fine, but not updating. I even tried rooting then undoing the root and starting again - again no luck.
Anyone got any ideas? Other than waiting for Asus to put the new firmware file on their ftp server? Help please or suggestions. Thanks.
+1,
All is the same for me.
Same problem, send technical inquiry to asus, this is the reply:
Dear Valued Customer,
The update should automatically download. If it does not auto down load after a week you can manually install.
From your TF101 you can also try going to Apps/Settings/About Tablet/Check Update, make sure to turn on WiFi and the device can access the internet.
If you continue to experience issues in the future, please do not hesitate to contact us.
Best Regards,
Vivian
ASUS Customer Service
From my experience, once you download the update, it seems you are automatically flagged as having got the update. Reverting to a previous built or in your case, even if the update didnt apply, you wont get the ota again.
Sent from my Transformer TF101 using Tapatalk
Exactly the same experience. Support is useless. Guess we have to wait until asus puts 3.2 on their support site.
I have the same problem my devise has i popup that appers twice a day saying...update failed. try again later.... but clicking on the update button in settings does nothing. Guess we will have to wait for the homepage release.
deeren said:
....once you download the update, it seems you are automatically flagged as having got the update....
Click to expand...
Click to collapse
Me too, it seems (1 tablet with 1 version) is flagged :
I've got one OTA with 8.4.4.5 (failed), and another with 8.4.4.11 (destructed myself).
Now I'm waiting OTA..... nothing.
ftp://ftp.asus.com.tw/pub/asus/EeePAD/TF101/

[Q] KitKat Update Issues

The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
there have been quite a few people with this same issue. i havent seen any direct fix.
if you are locked, i would suggest you wait it out, or wait for the sbf file to get leaked. there is a way to sideload it, but its risky being locked and no sbf to save you if a problem comes up.
if you are unlocked, there are directions in the General forum to sideload the ota. there is no risk if you are unlocked.
if you are locked, the only thing i would suggest to try is re-flashing the stock 9.30.1 with rsd and see if it will pull the update afterwards. there is no guarantee this will work, but your phone will be 100% clean stock after the flash and give you the best chance to grab the ota if available.
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
Did you download it and then said to apply it later? If so, are you rooted? If so, hook up your phone to your PC and adb shell into it. Type "su" and hit enter to go into superuser mode.
Navigate to the /cache directory and you should see the OTA .zip file sitting in there. Copy it to your external SD card and then you can load it manually via the recovery.
If you're not rooted, then you won't be able to navigate into the /cache directory. Or, if you didn't have it download when you got the notice (or couldn't download it), then it won't be there.
More update issues
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
zeb carter said:
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
Click to expand...
Click to collapse
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Factory REst doesn't solve 4.4.2 WIFI issue on Razor MAxx HD
TXKSSnapper said:
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Click to expand...
Click to collapse
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
egutwillig said:
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
Click to expand...
Click to collapse
That's a shame because for me, the FDR fixed the Wifi/Blue-tooth issue as it did for many others. Might have been a hardware issue (faulty radio, etc).

Force OTA after Update Notification was received?

This morning I finally got the notification telling me Lollipop is available for my Moto G 4G.
I wanted to download it however it told me that not enough room was available.
After cleaning up the phone I went into settings-about phone and searched for an update, however now it tells me that I'm up to date.
Tried restarting, tried reconnecting to wifi. Tried everything but I'm not getting a new prompt to update.
Any ideas how to force the OTA?
pseudoheld said:
This morning I finally got the notification telling me Lollipop is available for my Moto G 4G.
I wanted to download it however it told me that not enough room was available.
After cleaning up the phone I went into settings-about phone and searched for an update, however now it tells me that I'm up to date.
Tried restarting, tried reconnecting to wifi. Tried everything but I'm not getting a new prompt to update.
Any ideas how to force the OTA?
Click to expand...
Click to collapse
I have the same issue on my XT1032. I lost the first notification and then when clicking for upgrade (system upgrade) It prompts me I'm up to date when I'm still on 4.4.4.
Waiting for any hint.

Not receiving Google Security Updates

I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.

Categories

Resources