Zip verification Failed (updater service)! - Xiaomi Mi A2 / 6X Questions & Answers

I recently downloaded OTA update on my RR rom, after full downloading it showed Zip verification failed? Why does this happen and how to fix it..I really want to update my custom Rom.

dextercrypt said:
I recently downloaded OTA update on my RR rom, after full downloading it showed Zip verification failed? Why does this happen and how to fix it..I really want to update my custom Rom.
Click to expand...
Click to collapse
use old twrp. Latest TWRP has some problems

[email protected] said:
use old twrp. Latest TWRP has some problems
Click to expand...
Click to collapse
Not through TWRP , Its showing this error in settings - Udpate section . I'm not trying to update using TWRP.

dextercrypt said:
Not through TWRP , Its showing this error in settings - Udpate section . I'm not trying to update using TWRP.
Click to expand...
Click to collapse
Delete and redownload ota. It may be due to corrupted files.

[email protected] said:
Delete and redownload ota. It may be due to corrupted files.
Click to expand...
Click to collapse
And after that will TWRP and magisk be gone? And how to save them?

If you update via system updater app twrp and magisk stays. Or use twrp retention script module from magisk repo

[email protected] said:
If you update via system updater app twrp and magisk stays. Or use twrp retention script module from magisk repo
Click to expand...
Click to collapse
Ok will try that

Related

Can't update magisk to v17

I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?
Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info
Ty for now I'll wait
same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great
Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks
On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16
Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.
Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...
Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..

February security patch installation problem

Received the update but my phone shows error as "installation problem" l have unlocked boot loader and magisk installed.is this causing errors in installation?
U can't update with magisk installed
But there is no stock boot available for v 10.0.3.0 so i cant uninstall magisk
There is no boot stock for the January build to remove root?
unroot and relock bootloader, flash factory image through mi flash .
deepr702 said:
But there is no stock boot available for v 10.0.3.0 so i cant uninstall magisk
Click to expand...
Click to collapse
Haven't tried it, but there is an option to remove Magisk through own Magisk. It should restore boot.img to stock. As I have said, haven't tested but should work.
Someone can confirm it?
I need some help. I am on the January update. Didnt get bootloop when I installed it after unrooting before they stopped the update. This time I tried unrooting but unfortunately OTA still fails. I tried the Magisk uninstall with automatic restoring the error still persist. I also tried manually installing the boot.img for 10.3 but i get stuck on the android logo with only fastboot access. Flashing the patched 10.3 boot image lets me boot again. Any ideas to try except restoring (and wipping ) ?
Varun.Shanbhag said:
U can't update with magisk installed
Click to expand...
Click to collapse
Nandeh said:
Haven't tried it, but there is an option to remove Magisk through own Magisk. It should restore boot.img to stock. As I have said, haven't tested but should work.
Someone can confirm it?
Click to expand...
Click to collapse
Removing magisk trough uninstall magisk will send phone to bootloop and stuck on android logo
Varun.Shanbhag said:
U can't update with magisk installed
Click to expand...
Click to collapse
Nandeh said:
Haven't tried it, but there is an option to remove Magisk through own Magisk. It should restore boot.img to stock. As I have said, haven't tested but should work.
Someone can confirm it?
Click to expand...
Click to collapse
Doing this will send phone to bootloop and stuck on android logo
brayancm28 said:
There is no boot stock for the January build to remove root?
Click to expand...
Click to collapse
No and i dont know how to get ota to get working

How to update Resurrection Remix OTA update on Mi A2?

I recently installed RR rom and now I got notification saying Update is available (about 800mb). I don't know how to install it . So can anyone tell me the full procedure to update Resurrection Remix (or any custom) Rom on Mi a2. I downloaded the update Zip file once but after completing it says Zip verification faield so I thought it's maybe I don't know how to install it.?? So please tell me the full procedure. Thank you
dextercrypt said:
I recently installed RR rom and now I got notification saying Update is available (about 800mb). I don't know how to install it . So can anyone tell me the full procedure to update Resurrection Remix (or any custom) Rom on Mi a2. I downloaded the update Zip file once but after completing it says Zip verification faield so I thought it's maybe I don't know how to install it.?? So please tell me the full procedure. Thank you
Click to expand...
Click to collapse
Whats this XDA noones replying to my thread
try from twrp
can you tell me how you installed the rom please, for reasons I do not know I can not install the rom on my phone
laviniu_c said:
try from twrp
Click to expand...
Click to collapse
I don't the TWRP method and I want to update through system updater.
ferk42 said:
can you tell me how you installed the rom please, for reasons I do not know I can not install the rom on my phone
Click to expand...
Click to collapse
Tell me where i cancontact you so I can tell you step by step . Or pm me in XDA. Whichever u like
Go to updater in setting and hit install button. First it will download the update and then update it.
But keep these things in mind.
1.After update is finished your Twrp will be gone if you had permanent twrp before.
2.All app permissions will he reset.
3.And updating through system update takes around 2-3 hrs(,may take more or less)
Abhishekshuklapolice said:
Go to updater in setting and hit install button. First it will download the update and then update it.
But keep these things in mind.
1.After update is finished your Twrp will be gone if you had permanent twrp before.
2.All app permissions will he reset.
3.And updating through system update takes around 2-3 hrs(,may take more or less)
Click to expand...
Click to collapse
So after updating, what should I do? And how to keep magisk too... ?? ( Bhai bata de where can I contact you about full procedure kyuki main bhi indian hu hun) ?
How to update OTA in RR
dextercrypt said:
I recently installed RR rom and now I got notification saying Update is available (about 800mb). I don't know how to install it . So can anyone tell me the full procedure to update Resurrection Remix (or any custom) Rom on Mi a2. I downloaded the update Zip file once but after completing it says Zip verification faield so I thought it's maybe I don't know how to install it.?? So please tell me the full procedure. Thank you
Click to expand...
Click to collapse
Boot into TWRP
Wipe cache/Art and system partition
flash ota of RR and latest Gapps
Thats it :good:

7 Pro OB6 is out, uploaded ZIP on my google drive

https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Thanks, I was testing.
---------- Post added at 03:53 AM ---------- Previous post was at 03:16 AM ----------
สุรินทร์ พลโธา said:
Thanks, I was testing.
Click to expand...
Click to collapse
From testing hours than typical usage, better 0.2 overview and notifications improved. The battery cannot be dictated at this time.
I can't install from twrp, too. Same error.
=。= said:
I can't install from twrp, too. Same error.
Click to expand...
Click to collapse
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
I installed through an app system. I tested it now, it's better to use a stable battery enough to say it's saving
aNGERY said:
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Click to expand...
Click to collapse
After activating magisk modules my device is not booting. continuously booting to twrp and showing Rescueparty. i had tried magisk untinstaller but nothing happen.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
I'm wondering if there is any advantage to installing the update twice, so that it's on both slots?
This Walkthrough works with me perfectly
Updating from open beta 5 to open Beta 6 successfully
Rooted 20.1 & Twrp 72 no issues
Thanks a lot
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
null0seven said:
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
Click to expand...
Click to collapse
This works like a charm. Just did it to install it to the other slot being slot a. I'm ocd so I like both slots flashed. Easy solution to not being able to flash it in twrp. I'm kind of curious why it won't flash in twrp though. Maybe something to do with the security patch
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Account login in settings:
I was able to flash in TWRP using version -74, downloading OB6 using oxygen updater
Gordietm said:
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Click to expand...
Click to collapse
Not up at the top but yes can add in through settings.View attachment 4883201
Aporzio said:
Not up at the top but yes can add in through settings.
Click to expand...
Click to collapse
So why do I have in the main settings and others don't?
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
Not really sure
If anybody wants official download link for OB6 Global:
https://otafsg1.h2os.com/patch/amaz...13.W.17_OTA_017_all_1911152150_5b8908ba7b.zip
ZoiraP said:
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
Click to expand...
Click to collapse
this is the first one i couldn't flash in TWRP
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
I updated from twrp and got the same popup in my settings. Also, xXx has been affected, the debloat doesn't work properly on ob6. Hopefully things will get figured out soon.

doubt about updating firmware

hey i have an OTA update but im root, if i wanna update my phone what i have to do? just uninstalling magisk through magisk manager or i need to install the original boot.img as well?
thanks
drcarlox said:
hey i have an OTA update but im root, if i wanna update my phone what i have to do? just uninstalling magisk through magisk manager or i need to install the original boot.img as well?
thanks
Click to expand...
Click to collapse
quick one,go to twrp and wipe system and flash stock rom through odin.long one and less error prone if you time->remove root->flash stock rom->lock bootloader(update will fail if bootloader is unlocked)reset is needed->update->unlock bootloader->flash twrp & magisk.

Categories

Resources