Related
Nexus 6p update 7.1.1 verificaton failed??? New to droid and not a developer I bought from pawn shop this summer. Showed software up to date and sim worked calls/data on cricket network. Phone running dirty unicorns? ROM? SuperSU? No clue DU? Read about Nexus/google sending monthly security patches/updates but nothing here since may,1 patch phone showed being done week before i bought the phone? Finally like 12/6?7? received a system update "7.1.1" day after they began rolling out to 6p's from what I think I maybe understand:/? So clicked on update which " fixes crucial bugs and improves stability and performance for your nexus 6p." 1270.1mb file "OK" starts the "downloading" showing as status bar slowly showing progress moving left to right. Half hour later+/- download completes "Verification failed" ??? Nothing updated goes back to update screen loops thru the process downloading 30+/- minutes or so then same " verification failed" Need help securing phone/personal data etc making it my own praying my privates life still private (besides google) and that I'm not owned!?! Hoped update would return me to factory settings along with my peace of mind but without verification maybe unicorns have a point:/
Suggest you follow this link... http://www.wugfresh.com/nrt/ The safest way to fix your issue. Seams you have custom rom in the phone, and you are trying to update with a factory rom. This website will help you get the phone back to a factory stock rom and from then on you will be able to get OTA updates without issues.
I just got an OTA update for Nougat (BTU) on my S7 edge.
68MB, small update, so I let it install
I've had Secure Startup enabled on my device all along, never had an issue, but after this latest update had finished installing, device rebooted, asking for my device pin as usual, but it will not accept my PIN! I've been very very very careful in entering the 4 digit device pin correctly, but it just won't verify! Please help, I'm desperate, have 4 attempts left before it resets the device!
My last reboot was about 2 or 3 days ago, same pin worked, but broken after the OTA update.. I don't want to factory reset if I can help it, haven't done a Smart Switch backup in about 2 months, so my app data will be well out of date if I do
So I eventually gave in and did a factory reset (no choice)
Samsung Cloud FTW - restored my apps, home screen settings (even folders and shortcuts) from the nightly cloud backup! All I missed was this morning's WhatsApp texts (also nightly backup to Google Drive - WhatsApp detected that backup without any prompting, awesome!)
So all that I lost in the end was a good chunk of my day (letting nearly 200 apps reinstall is a slow process, and then anything with TFA needed to be re-logged-in, and my code gen app for TFA reconfigured, but overall it was pretty painless, all considering!
AngelaRI said:
I just got an OTA update for Nougat (BTU) on my S7 edge.
68MB, small update, so I let it install
I've had Secure Startup enabled on my device all along, never had an issue, but after this latest update had finished installing, device rebooted, asking for my device pin as usual, but it will not accept my PIN! I've been very very very careful in entering the 4 digit device pin correctly, but it just won't verify! Please help, I'm desperate, have 4 attempts left before it resets the device!
My last reboot was about 2 or 3 days ago, same pin worked, but broken after the OTA update.. I don't want to factory reset if I can help it, haven't done a Smart Switch backup in about 2 months, so my app data will be well out of date if I do
Click to expand...
Click to collapse
Is anyone else having this issue?
What I read from the stock FW thread, if a firmware is flashed using odin (not OTA) there are a lot of comments to have Secure PIN enabled because a PIN is required afterwards?!
So what to do when updating with OTA? pin enable? disable?
Hi I have a S7 Edge SM-G935F and I followed the TWRP and Root guide here on XDA, but i still got dm-verity triggered and I cant boot into Android without that motherf%&king error popping up about resetting. I am running the Latest stock Android 8 update, cause I just got the phone a couple of days ago so I havent tampered with it, but as soon as I try to tamper, it softbricks...
I have never had a phone with dm-verity before so yeah does anyone know a method without wiping to factory?
I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Someone?
up.
costafabiof said:
I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Click to expand...
Click to collapse
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
I just got it to work. I'm just testing the procedure again to make sure and put it here.
I arranged this item like this.
In Android 9, installing TWRP soon after installing Android no longer works, after installing TWRP, it appears in red "only official realease binaries are allowed to be flashed" and restarting in the download mode appears KG STATE PRENORMAL.
To fix I installed Android 9 again without the TWRP, Magisk, etc, that is, pure. I entered the system and started the updates by Google, when I came back to check in download mode KG STATE was with CHECKING which is normal.
With this I returned everything to normal, I installed TWRP, Magisk, etc. and I continued.
spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
DSMB said:
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
Click to expand...
Click to collapse
Have a look here
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post79745844
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