Hello,
since march 2019 update, my phone Nokia 5 TA-1053, cannot "see" any further updates. It's June by now, and I was unable to update my phone by OTA with april and may 2019 updates.
What have I done, and didn't work:
1) clear cache partition from recovery mode
2) clear cache and data for Carrier Services app
3) clear cache and data for update service
4) trying all above without SIM card(s) inside the phone
Nothing is working. I'have bought this phone in November 2017 (in shop, without branding of any sort), and had no problems with system to this day. What can I do to update my phone, except wiping all system and data? @edit:
1) never rooted
2) never installed custom firmware
3) only official updates
grimHog said:
Hello,
since march 2019 update, my phone Nokia 5 TA-1053, cannot "see" any further updates. It's June by now, and I was unable to update my phone by OTA with april and may 2019 updates.
What have I done, and didn't work:
1) clear cache partition from recovery mode
2) clear cache and data for Carrier Services app
3) clear cache and data for update service
4) trying all above without SIM card(s) inside the phone
Nothing is working. I'have bought this phone in November 2017 (in shop, without branding of any sort), and had no problems with system to this day. What can I do to update my phone, except wiping all system and data? @edit:
1) never rooted
2) never installed custom firmware
3) only official updates
Click to expand...
Click to collapse
well, it kinda strange.. mine already installed june 2019 update.
FauzanAdli said:
well, it kinda strange.. mine already installed june 2019 update.
Click to expand...
Click to collapse
My phone says that there is no new updates, and my system is up to date.
Fix for missing OTAs
1. Backup any photos etc you want to keep
2. Switch off phone.
3. Remove SIM.
4. Switch phone back on.
5. Factory restore/erase (without SIM).
6. When phone restarts, set location as India, connect to wifi (do not insert SIM yet), download all updates, OTAs should appear
7. Once all OTAs installed, reinsert SIM
This worked for me.
I have been seeing a similar issue of delayed OTA update availability. In my case it seems to help to reboot the device, then it sometimes finds the new update.
Related
Just got my Axon 7, shipped from DE to UK, thought I'd try manual software update.
Current version listed as ZTE A2017GV1.0.0B06
It times out with Network Unavailable despite the fact it is connected to WiFi and Chrome works fine as well as everything else needing internet connections.
I am on Three UK, haven't tried updating without a SIM ... is that worth trying? I did see at initial setup I was prompted to accept some sort of 3UK profile though I assumed this is just APN/MMS stuff.
Anyone else having similar problem trying to update?
I see talk of updating to B08 etc, from 2017G --- is 2017G same as 2017GV1... wouldn't want to assume anything this early on in my game
TIA for any tips/advice.
Am really liking this phone though, might be nice to get latest update for security mainly, not sure if many features are added?
Same issue here as it happens, though I'm currently trying to update WITHOUT a sim (didn't appreciate it was nano so new one on order!).
I was thinking it maybe needed one to be present to update, but clearly that's not the case.
nstirton said:
Same issue here as it happens, though I'm currently trying to update WITHOUT a sim (didn't appreciate it was nano so new one on order!).
I was thinking it maybe needed one to be present to update, but clearly that's not the case.
Click to expand...
Click to collapse
Can't speak to the EU version, but I was surprised when my A2017U would not complete initial setup (& update) without the SIM, although wifi was strong. All completed quickly as soon as I popped in the SIM.
Hi,
I have the same issue here.
I've just bought A2017G from Italy (Amazon) and I live in France. Can't have the upade to B08. There is always this message "No network" after a minute of searching. I tried with 4G and Wifi and there is the same issue!
Also can't connect
Same issue here. I am already on B.08 and have wifi/Sim in place.
Mysterious problem
I have tried many solutions but I wasn't able to update :
- used three different sim cards from 3 operators
- removed sim card and worked only on wifi
- used VPN
- tried to update via SD card form the update page and from recovery
... Unsuccessful !
Anyone have idea?
I'm also having the same problem. I live in Sweden and I just got the phone today. Would be nice if I could update sometime soon.
A2017g b06
Greenland here, I also have problems with the connectivity
Maybe ZTE is updating its servers so that the updates can finally deploy at the same time, the same version, for everyone.
Or, maybe... they are silently getting rid of Adups and moving to another kind of upload process, before **** hits the proverbial fan.
Also, Global Axon 7 here, brought via Amazon.es, sent from Germany and now used across Portugal/Spain. Running 0B08.
deoki said:
Maybe ZTE is updating its servers so that the updates can finally deploy at the same time, the same version, for everyone.
Or, maybe... they are silently getting rid of Adups and moving to another kind of upload process, before **** hits the proverbial fan.
Also, Global Axon 7 here, brought via Amazon.es, sent from Germany and now used across Portugal/Spain. Running 0B08.
Click to expand...
Click to collapse
I can understand that, but even if we put the B08 update file downloaded from ZTE support in SD card, the update can't be processed.
Hello, I had the same problem, I reinitialized the Axon 7, and I copied the file update.zip B09 on the phone, it recognized and installed the file (I was on the b08 before)
Hallo, i have the same problem with update, I have B06, somebody can give me a link to download the latest firmware and how to install it.
Yansin said:
I can understand that, but even if we put the B08 update file downloaded from ZTE support in SD card, the update can't be processed.
Click to expand...
Click to collapse
hmm I put a b09 in the sd card and it updated no problem
Solution found!
I’ve already found the solution for the manual upadate from SD card and it’s easy to do.
Theses instructions are not mine and I’m not responsible of what you do with your phone. I found them inside the update file that I Downloaded then I unzipped.
You will find a PDF document called “ZTE A2017G Upgrade Guide (through an SD Card).pdf”. You can use it to do the upgrade step by step.
Till now, all was OKEY: backup is very quickly with Zte app. The update take about 5 minutes, than the phone restarts automatically.
If you cannot find the B08 update file, try to download it from here: http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6
Here are the steps (exactly as mentioned in ZTE Upgrade Guide)
ZTE V7 Upgrade Guide (Through an SD Card)
1. Backing Up the Data
1) Download the upgrade package.
Open http://www.ztedevice.com.cn/support and download the upgrade package (update.zip) that matches your phone model. If the downloaded package is not update.zip, unzip the package to obtain update.zip.
Ensure that your micro SD card is at least 3GB.
2) Remove the SIM card before the upgrade. Back up the data and APPs in your phone by using the built-in Backup function. To enable the built-in Backup function of your phone (an SD card must be inserted), select
Backup and Restore from the main menu。
3) Perform data backup.
Note:
You should not remove the SD card during the backup process. To avoid data lost, it is not recommended to cancel the backup process.
4) Verify that the update.zip file in the root directory of the SD card
matches the model of the phone. Do not modify the file name and extension name of the files in the upgrade package.
5) Verify that your phone has enough (at least 30%) power. Charge the phone if required. To avoid data lost or upgrade failure, it is not recommended to upgrade your phone through an SD card when the phone is being charged.
Note:
You should not perform any other operation on the phone during the upgrade process. To avoid upgrade failure, do not forcibly remove the battery.
A normal upgrade should be completed in 2-3 minutes. If the phone does not reboot or show any response in three minutes, you should perform the upgrade process again. If the phone cannot be started, perform a forced upgrade. If the forced upgrade does not work, you should contact an after-sale service agent for support.
2. Upgrade Description
There are two upgrade methods: normal upgrade and forced upgrade.
If the phone cannot be started properly, for example, the phone cannot be started, or the phone does not enter stand-by state, perform a forced upgrade. If the phone can be started properly and the Settings menu can be selected, perform a normal upgrade.
3. Upgrade Steps
A. Normal upgrade (the primary upgrade method)
1) Download the upgrade package that matches the phone model from ZTE official website (http://www.ztedevice.com.cn/support/), extract update.zip from the package, and copy update.zip to the root directory of the SD card (the file name must be update.zip
2) Select System Manager > File Manager> SD Card from the main menu, and verify that the update.zip file in the root directory of the SD card is proper.
3) Tap the main screen is displayed. Tap and select SETTINGS >All setting > Updates>,
4) Click INSTALL, The phone automatically powers off and reboots. the SD
card upgrade screen is displayed,
After the phone is upgraded, it is rebooted again. After the phone starts properly, it is recommended to manually restore the phone to its original factory default settings. The phone is upgraded properly and can be used.
B. Forced upgrade (for the phones that cannot be started or the phones that cannot enter standby state)
1) For a powered-off phone, press and hold both the volume key + and power
key to enter into Recovery mode.
2) Press the volume key - to select apply update from sdcard, and press the power key to confirm it.
3) Press the volume key - to select the update.zip file, and press the power key to confirm it. The phone completes the upgrade process in about three minutes.
4) On the Upgrade Complete screen, select reboot system now and press the power key to confirm it.
4. (Optional) Restoring the Data
If you have backed up data before upgrading your phone, restore the data.
1) Backup and Restore important user information.
2) Perform data restoration.
Note:
Do not remove the SD card during the restoration process. To avoid data lost, it is not recommended to cancel the restoration process.
An interesting thread: http://forum.xda-developers.com/axon-7/how-to/manual-updating-a2017g-t3519104 !
Thanks, but i tryed to install this update but I get an error that it is not for my phone, i have ZTE A2017G_1817 buildnr. ZTE A2017GV1.1.0B06
Have I don anything wrong or do I need an other file
Regards
Same problem on my axon 7 a2017g - updated via updater from b06 to b08 - network unavailable trying to check update to b09
Same white me, then I tryed it with the downloaded updat.zip from B08 and he start the update bute later stopt whit the message this file is not for my phone ??
Where can I download the B09 update.
keesvl55 said:
Same white me, then I tryed it with the downloaded updat.zip from B08 and he start the update bute later stopt whit the message this file is not for my phone ??
Where can I download the B09 update.
Click to expand...
Click to collapse
The file is on ztedevice (link in thread) but i think (as some of other users) that this patch is only for Spain - don't know that for 100% but most ppl that can upadate it with OTA are located in Spain. Also I still get "network unavailable" when I trying to check update (location Poland, phone from UK). But you should can update from B06 to B08 as I can without any doubts via OTA.
MrMD69 said:
The file is on ztedevice (link in thread) but i think (as some of other users) that this patch is only for Spain - don't know that for 100% but most ppl that can upadate it with OTA are located in Spain. Also I still get "network unavailable" when I trying to check update (location Poland, phone from UK). But you should can update from B06 to B08 as I can without any doubts via OTA.
Click to expand...
Click to collapse
Here the problem is solved, this morning the ota update worked en now he is installing B08.
I downloaded B09 en wanted to go install it and than the give me the original B08 update in the screen, let see how it works.
As for 1.01.2017 update check start working for me - no more "network unavailable" just "up to date" at B08 a2017g.
Hi all,
Recently we find a way to go back to 8.1.0 from Android P DP1 with Verizon locked bootloader on the Android Beta Program community. Thanks Ziauddin Sameer for try it.
All you need is:
1- Google Pixel or Pixel XL with locked bootloader (Don't know if it work on Pixel 2 or Pixel 2 XL but it may work)
2- Android P DP1 installed on your device
3- Full April 2018 OTA link here https://developers.google.com/android/ota
4- ADB/FASTBOOT drivers link here https://forum.xda-developers.com/showthread.php?t=2588979
Now that you have all that and the drivers intalled let's do this:
You'll lose all your data after this, so backup before continue
1- Install the drivers
2- Put the Full April OTA zip on the adb folder located on C:/
3- Turn you Pixel off and go to recovery mode
4- Select "Apply update from ADB"
5- Plug in your Pixel via USB to the computer
6- Inside the adb folder Hold "Shift" and right click, select Open Powershell/CMD here"
7- Inside the Powershell/CMD type
Code:
abd sideload filename.zip
8- When its done your Pixel will try to boot and since it has the Android P data (cause sideloads dont erase data) it would said that the data is corrupted and it will suggest you to factory reset.
9- Select factory resert and it will boot on Android 8.1.0
Psdt: Sorry for my bad english.
You can confirm it in here https://plus.google.com/101606265756083327418/posts/cshGmedy5ZX
I can confirm that this does work! THANKS! I am happily back to 8.1! Don't get me wrong "P" is awesome and stable, but having the WiFi Calling feature broke in "P" is a deal breaker for me. I will just have to wait until DP2 to see if it gets sorted out.
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
I tried this after going to Android P beta. It did not work for me.
I followed the steps and when I ran adb sideload xxx.zip I received this...
verifying update package
E:footer is wrong
update package verification took 0.2 s (result 1)
E:Signature verification failed
E:error: 21
Installation aborted.
Any help would be greatly appreciated, basically I opted into beta and then opted out but never received the image to go back and apps are not working for me...gear s3, libby and some others.
whreed said:
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
.
Click to expand...
Click to collapse
So for downgrading from Android P DP2 we need to use 8.1 April OTA, right?
I ultimately did get the push of the image to my device to pass but the image didn't work for me... When I wiped and rebooted and after initial setup up I received the message to go back to Oreo from Google....I was previously in the beta but opted out.
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
caloysilva said:
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
Click to expand...
Click to collapse
Just opt out of the beta and an OTA will appear to go back to Oreo
It doesn't seem this method will work to downgrade the OTA 9.0 update? My phone has been completely unusable since the 9.0 update applied (the radio modem has worked all of about 2 days since the update). I've tried everything and have been on the phone with google many times over this. When I try to place a call, I'll either get the message "Radio off" or " Cannot place calls in Airplane mode" errors. Rebooting, cycling data and airplane modes have no effect, resetting networking does nothing, even factory resetting does nothing. My phone is completely useless without mobile data. I'll never purchase anything from Verizon again, with their opting to lock the bootloader on their phones!
I was also curious if this method would work for an OTA 9.0 device ?
So are the updates good to go now? I did the full updates to unlock my phone after the sim card issue (Rooted as well) but i haven't gone back to it and the phone keeps asking me to update to PPR1.180905.036 and i'm just wondering if that update is good to go OTA if you've rooted your phone and done the roll back to get the sim unlock off.
Pesti13nce said:
So are the updates good to go now? I did the full updates to unlock my phone after the sim card issue (Rooted as well) but i haven't gone back to it and the phone keeps asking me to update to PPR1.180905.036 and i'm just wondering if that update is good to go OTA if you've rooted your phone and done the roll back to get the sim unlock off.
Click to expand...
Click to collapse
36. Is fine. Just careful with Oct update. Not sure yet
backed up my data. grabbed Oct 2018 OTA from Essential's site
rebooted in recovery, sideloaded OTA
after reboot, SIM still unlocked
I can't speak for downloading the OTA from the phone itself, but the above steps worked for me
Hy,
December Update out now.
Greets
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Wondering if people stuck on September version can finally update without resetting data.
Please let us know if you're in this group.
laviniu_c said:
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Click to expand...
Click to collapse
I would say the same. Can't expect anything better than this from these system updates.
until when mi a2 will receive updates? will this be the last?
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
birdflesh said:
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
Click to expand...
Click to collapse
thanks for the info! Mi A2 security patches until Aug 2021 (Mi A2 release August 2018)
Since that update my battery drains way faster.
Since that update my battery drains way faster.
+1
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
ota should work with an unlocked bl, IF you have not changed the system. unlocking means you could change it, it doesnt in itself deny ota updates
salmonthefish said:
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
Click to expand...
Click to collapse
I´m also waiting for anyone that reported that made the update. I have Setember Update with bootloader unlocked because of camera2api, i don´t made any system changes, and i get all the updates until september without problemes. After that i get Bootloop on October and don´t update anymore. If anyone upgrade from setember with sucess please report.
ki69 said:
because of camera2api
Click to expand...
Click to collapse
you answered your own question. if you've unlocked AND made ANY changes to the system ota can bootloop ofcourse.
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Aerobatic said:
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you.
A question, if i unlock the bootloader afterwards will the same issue pop up again?
salmonthefish said:
A question, if i unlock the bootloader afterwards will the same issue pop up again?
Click to expand...
Click to collapse
I believe neither Xiaomi nor Google can answer this question.
Anyway,
1) right now factory reset for unlocked MiA2 is needed only once when updating from any previous ROM version to any currently available ROM version >= 11.0.15.0;
2) having unlocked phone one is sure that his data can be restored in any future mishap;
3) unfortunately unlocked phone prevents usage of most of banking apps unless Magisk + Riru + edXposed installed with MagishHide On and GooglePlayServices in Blocked List (SafetyNet issue).
So everyone decides himself whether to
a) keep phone untampered (with risk of loosing data with next OTA bootloop),
b) or unblock phone and then stay with updating stock (spending some time to get root, make SafetyNet passable, remove annoying settings suggestions, customize UI, etc.) ,
c) or unblock phone and then revert to Android 9 10.0.17.0 (disabling updates),
d) or unblock phone and then escape to a Custom ROM.
I personally prefer option (b) since my first Android gadgets (never bought a phone/tablet which had problems with rooting).
19Gerhard85 said:
Since that update my battery drains way faster.
Click to expand...
Click to collapse
19Gerhard85
after updating "Google Find my Device" app battery holds like before all ok now but i never use that app not even logged in calendar app also updated at same time but i don't thin it was calendar
My Nokia 5. has two Problems.
1. I recently got October 2020 Patch Update notification and i downloaded and during installing the "Installing Security Update stage gets stuck". after reboot my device update Failed Comes.
2. and from now i got only HSPA Network even though i enabled the 4g roaming, but i got only HSPA. give solution ASAP. this is my Personal Mobile.
* My OS Version Android 9 Pie
1. Is your phone functional now? You should have ejected your SD Card out of the device prior to downloading the update package and installing it.
2. There's an app called “4G Only Switch” on Play Store which might solve your connectivity issue