April 2020 security update for Nokia 7.1 has been pulled back by Nokia.
As this update is causing the phone to factory reset , Nokia has pulled back this update...
The March security update was causing the same infamous "enablecryptofile" error as well.
I'm sick of the software blunders, thought buying a Nokia would be the end of it.
I was so wrong!
Related
Hello, i have the phone around a month now and never have any problems until april update. The last couple days the phone restarted randomly twice - once while i was using it and the other while not. Both times it was connected to power.
When updated i also deleted the cache from the storage menu, i will also do it from system restore and hope it will fix it. Any other ideas?
Nothing wrong with April update.
April update has been quite stable for me.
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
hbkekko said:
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
Click to expand...
Click to collapse
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Jammol said:
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Click to expand...
Click to collapse
I tried to wipe cache from settings, storage but didn't work. Yes I've unlocked bootloader but no root. Could this be the problem?
No, shouldn't affect anything just being unlocked. Now if you installed TWRP, that might cause this. I didn't use an OTA to go to the march update so idk if it might be at fault, I was on pure Nexus so chose to flash the factory image and haven't had any issues so far.
Sent from my Pixel XL using Tapatalk
Solved flashing the latest factory image via fastboot
My z2 play (bootloader unlocked) just received an update: NPS26.118-19. I tried to install the update but 10 minutes into the installation I got the famous Android update message "Error!" (with the green Android guy on black background).
This came as a surprise since I have not rooted the z2 play yet, and only "temporarily booted TWRP" to backup the partitions. I have always mounted the system partition as read-only. Have not flash anything. So everything should have been stock, right !?
I had to long-press the power button to reset the device and after the reboot I got the confirmation "Update unsuccessful". But I still checked the system info and to my surprise (again!) the system info had been updated.
Before Update:
7.1.1
Security patch level April 1, 2017
Baseband M8953P_14.21.07.22R
Kernel 3.18.31-perf-gc281c92a April 18
Build NPS26.74-16-1
After Update:
7.1.1
Security patch level July 1, 2017
Baseband M8953P_23.33.07.34R
Kernel 3.18.31-perf-g3b78496 Jun 30
Build NPS26.118-19
Please send us a screenshot
romhippo.com said:
My z2 play (bootloader unlocked) just received an update: NPS26.118-19. I tried to install the update but 10 minutes into the installation I got the famous Android update message "Error!" (with the green Android guy on black background).
This came as a surprise since I have not rooted the z2 play yet, and only "temporarily booted TWRP" to backup the partitions. I have always mounted the system partition as read-only. Have not flash anything. So everything should have been stock, right !?
I had to long-press the power button to reset the device and after the reboot I got the confirmation "Update unsuccessful". But I still checked the system info and to my surprise (again!) the system info had been updated.
Before Update:
7.1.1
Security patch level April 1, 2017
Baseband M8953P_14.21.07.22R
Kernel 3.18.31-perf-gc281c92a April 18
Build NPS26.74-16-1
After Update:
7.1.1
Security patch level July 1, 2017
Baseband M8953P_23.33.07.34R
Kernel 3.18.31-perf-g3b78496 Jun 30
Build NPS26.118-19
Click to expand...
Click to collapse
Updated mine today,and after rebooting my downloaded apps aren't starting (showing blank screen).
Also i have the infamous " Your device has failed verification problem",if there's anyone who could help will be great .
I received the OTA yesterday, applied without any issue.
But of course I didn't do any modification.
no issue either
Motorola released another update yesterday (RETBR).
Before Update:
7.1.1
Security patch level July 1, 2017
Baseband M8953P_23.33.07.34R
Kernel 3.18.31-perf-g3b78496 Jun 30
Build NPS26.118-19
After Update:
7.1.1
Security patch level August 1, 2017
Baseband M8953P_23.33.07.34R
Kernel 3.18.31-perf-ga5d85c2 Jul 31
Build NPSS26.118-19-4
Hi friend,
I Am a Moto z2 play user from India obviously.
I mistakenly lost my stock Rom, and it is difficult to find indian built can you send your stock rom through twrp backup please.
yours faithfully a Motto user
new owner here..
I just received the S4, installed some apps, searched for updates, got the november update, installed it and it did a complete factory reset!!
Something wrong with the OTA update??
All I did was the update, it never asked me anything about a full wipe
common problem?
I read about this problem in spanish forum but we don t understand if it is a ota problem or something else.
Jakke102 said:
new owner here..
I just received the S4, installed some apps, searched for updates, got the november update, installed it and it did a complete factory reset!!
Something wrong with the OTA update??
All I did was the update, it never asked me anything about a full wipe
common problem?
Click to expand...
Click to collapse
I just checked my Tab S4 and it only has the Sep 2019 update and says that is the current update. No factory reset when that update was installed.
The november OTA caused factory resets for some users and isn't available anymore (lots of posts in german android-hilfe.de). I guess a new version without this problem will be available soon.
Spanish version here... For me, a recent update did a factory reset. I was really angry about that, but I think that was in September.
I didn't get a factory reset but I'm experiencing touch screen problems since the november update. Sometimes part (or whole) of the screen becomes unresponsive. Reboot fixes it so I suspect it is a software issue.
Mine to here in the states...anyone have any suggestions, not trying to reset
Happened to me.
yes, he did it to me in three firmware I tried....
(spain PHE, france XEF ,Greece)
I've been following the S22 release, and already knew there were a few updates dropped at this point. I just received my new S22 Ultra from AT&T, during setup I saw a popup that said I had an update available. Great. However immediately after setting it up I had to factory reset and start over, and when I finally got all set up again, it says there's no update available. I'm currently on an S908U running the January update, S908USQU1AVA6.