"Package verification failed" notice daily - Moto G 5G Questions & Answers

After rooting my Motorola One 5G Ace to get rid of annoyances... I now get a daily notification "package verification failed" How do I get this to go away? It's very annoying
I have Magisk installed.

Related

[Q] HTC Desire Z Won't Update New Software

So I noticed the other day that there was a software update. So I downloaded the update and when it reboots to install the update I get an error message. I have rooted my phone with visionary. I first did temproot then did permroot. I assume that my phone is rooted correctly and I used visionary to unroot my phone and still have the same issue. When I go to terminal emulator and type su it seems fine. I have also tried unrooting my phone and also tried doing a factory reset in the settings menu. Nothing seems to work. I purchased my HTC Desire Z from a local cell phone shop so it is a legitimate phone. I love my phone but I really want to upgrade to Android 2.3 eventually and if a software update won't work I don't know how I will update to 2.3
I get the red triangle then I get
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaboot to /data/system for customize reload...
Verifying current system...
Assert failed: apply.patch.check ("system/app/facebook.apk", 16ccb41b0a251746c7d903dbf423f57316677456", 5b162a2af40f851c3c040532139738a260a00e9f")
E: Error in /sdcard/download/OTA_vision.BellMobility_MWE_1_84_666_-3_34_665_5_release_17247wagbpno61mgwg4k0.zip
(Status 7)
Installation abborted
Then I reboot and everything is fine. Now I should say that tis phone is unlocked and not on Bell Mobility but on Telus. Also I should say that after rooting the phone I uninstalled a few applications such as facebook. Thanks for any help at all. If I need to I can restore my phone to before I messed with it but I don't know how since a factory reset doesn't put facebook back on

update on p999dwp?

when trying to update using the lg tool still says up to date. then when checking through the phone i get the connection failed caused by authentication error. so has anyone gotten the ota?

authentication error with ota update?!?!

anyone that got an "authentication error" message managed to get the ota gb update?!?!?!?! curious to see if it is possible to update this mess of a phone. if not back to costco I go

Stuck in Beta Please Help

I opted into the Beta a few months ago. After the device began to crash a lot I tried to get out. I un-enrolled from the Beta but never received an update back to stable. I factory reset the phone, but when I swipe down it still shows as in the Android Beta program in the settings page.
After going back and forth with Google support for months, they have told me they can't fix it and that my only hope is to try sideloading the device. I followed the relevant guides to do that using ADB, but when I tried I get an error saying it can't be done.
I'm on a verizon pixel 2 XL. Build number is OPP6.171019.012. I tried sideloading 8.1.0 (OPM1.171019.018, Feb 2018) and 8.0.0 (OPD3.170816.023, Nov 2017, Verizon). Neither worked. Pictures on imgur at gallery/HU4rf
When I tried sideloading taimen-opm1.171019.018 I got the error: E:footer is wrong, Update signature package verification took 0.0 s (result 1)., E:signature verification failed. E:error: 21, Installation aborted.
I can't do any method that relies on OEM unlocking because apparently that's not available under Verizon phones.
I don't really know what I am doing, and I would really appreciate any help. I'd offer a reward for anyone who could get me out of Beta and back into a normal / stable build.
teidurden said:
I opted into the Beta a few months ago. After the device began to crash a lot I tried to get out. I un-enrolled from the Beta but never received an update back to stable. I factory reset the phone, but when I swipe down it still shows as in the Android Beta program in the settings page.
After going back and forth with Google support for months, they have told me they can't fix it and that my only hope is to try sideloading the device. I followed the relevant guides to do that using ADB, but when I tried I get an error saying it can't be done.
I'm on a verizon pixel 2 XL. Build number is OPP6.171019.012. I tried sideloading 8.1.0 (OPM1.171019.018, Feb 2018) and 8.0.0 (OPD3.170816.023, Nov 2017, Verizon). Neither worked. Pictures on imgur at gallery/HU4rf
When I tried sideloading taimen-opm1.171019.018 I got the error: E:footer is wrong, Update signature package verification took 0.0 s (result 1)., E:signature verification failed. E:error: 21, Installation aborted.
I can't do any method that relies on OEM unlocking because apparently that's not available under Verizon phones.
I don't really know what I am doing, and I would really appreciate any help. I'd offer a reward for anyone who could get me out of Beta and back into a normal / stable build.
Click to expand...
Click to collapse
Your in the non-xl forums, however, make sure your using the latest platform tools from google. Also try other cables and another computer if at all possible. Your trying to side load from the recovery correct? Maybe re download the ota image as well from https://developers.google.com/android/ota
teidurden said:
I opted into the Beta a few months ago. After the device began to crash a lot I tried to get out. I un-enrolled from the Beta but never received an update back to stable. I factory reset the phone, but when I swipe down it still shows as in the Android Beta program in the settings page.
After going back and forth with Google support for months, they have told me they can't fix it and that my only hope is to try sideloading the device. I followed the relevant guides to do that using ADB, but when I tried I get an error saying it can't be done.
I'm on a verizon pixel 2 XL. Build number is OPP6.171019.012. I tried sideloading 8.1.0 (OPM1.171019.018, Feb 2018) and 8.0.0 (OPD3.170816.023, Nov 2017, Verizon). Neither worked. Pictures on imgur at gallery/HU4rf
When I tried sideloading taimen-opm1.171019.018 I got the error: E:footer is wrong, Update signature package verification took 0.0 s (result 1)., E:signature verification failed. E:error: 21, Installation aborted.
I can't do any method that relies on OEM unlocking because apparently that's not available under Verizon phones.
I don't really know what I am doing, and I would really appreciate any help. I'd offer a reward for anyone who could get me out of Beta and back into a normal / stable build.
Click to expand...
Click to collapse
This should do the trick for you. I downloaded and installed the correct APK and restarted my P2. Check for update and finally 8.1 February Patch available.
https://www.androidpolice.com/2018/...ix-androids-check-update-button-apk-download/

Question Redmi 8a dual device basic data verification failed

my redmi 8a dual 2-32 showing error "device basic data verification failed" while trying to unlock bootloader
What's status of bootloader?
Run
Code:
fastboot oem-deviceinfo
to get this.
jwoegerbauer said:
What's status of bootloader?
Run
Code:
fastboot oem-deviceinfo
to get this.
Click to expand...
Click to collapse
I am trying official method. It says go to developer options and click on unlock device then add Mi account. At adding my account it gives a toast message "couldn't add. device basic data verification failed"
deepanshu_rohilla said:
I am trying official method. It says go to developer options and click on unlock device then add Mi account. At adding my account it gives a toast message "couldn't add. device basic data verification failed"
Click to expand...
Click to collapse
I have reset the device 3 times at this point. changed Mi account and rolled back to miui 12. it gives same error every time.
my 3-32 variant of same model didn't gave any error and it added Mi account on first try
Facing the same issue. Tried everything. No avail.
deepanshu_rohilla said:
I have reset the device 3 times at this point. changed Mi account and rolled back to miui 12. it gives same error every time.
my 3-32 variant of same model didn't gave any error and it added Mi account on first try
Click to expand...
Click to collapse
Bro how u rolled back to miui 12 ?via edl process ?
pls give me method to downgrade .
you guys got any solution ? this error is too annoying i need solution

Categories

Resources