Problem sideloading June update QQ3A.200605.001 - Google Pixel 2 XL Guides, News, & Discussion

Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.

SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I downloaded the OTA package from the Google page,and dirty flashed over my qq2a with no problems.
Sent from my Pixel 2 XL using Tapatalk

That's what I've always done. And this time it won't take it
Sent from my Pixel 2 XL using Tapatalk

I must have screwed something up at some point. I figured it out. I upgraded using the factory image and eliminated the -w command from the flash all script so it didn't wipe my phone.

SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I was having the same issue. I was running a stock rom with the may update . After several tries I desisted and check for updates in the phone and the june ota installed successfully

SuperShadow1021 said:
I must have screwed something up at some point. I figured it out. I upgraded using the factory image and eliminated the -w command from the flash all script so it didn't wipe my phone.
Click to expand...
Click to collapse
I've been removing the -w from the factory images for a few months now. Too much trouble to do a clean flash and I saw no real benefit from the clean flash so I stopped. June update flashed for me just fine.

I was having the same issue. I was running a stock rom with the may update

Check and see that platform tools and all of your driver's are upto date

Solution that work for me
SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I have also face same issue while sideloading June OTA than after lot of searching i found fully working solution.
I am assuming you have not flashed Custom recovery (i usually only boot Custom recovery so that i can sideload ota update using Stock Recovery)
Now connect you phone (USB Debugging: On)
Command: adb devices
Your device must show up in Command prompt
2nd command: adb reboot bootloader
Must be boot into fastboot mode
Now as pixel 2 xl has A/B partition so we have to check active partition first then have to change to another.
To check active slot
3rd command: fastboot getvar current-slot
To change active slot
4th command:
if your active slot is "a"
fastboot --set-active=b
OR
if your active slot is "b"
fastboot --set-active=a
Now reboot to stock recovery (please do not boot into system)
5th Command: fastboot reboot recovery
Now select "apply update from adb"
Once again check for device connection, must show as sideload, then....
Command: adb sideload [filename]
Please replace [filename] with the OTA .zip file you have downloaded.
Ex: adb sideload c:\user\name\Desktop\taimen-ota-qq3a.200605.001-992633c8.zip
Now this should work, as it works for me.
Sorry for detailed instructions, i am pretty sure you already know the basic commands but I just want to post it as guide for everyone.
My First reply on XDA, Happy to help you.

Related

[marmite] Android 7.1.2 TOS163B official OTA link grabbed!

Hi everyone,
Since Wileyfox didn't want to supply us with Recovery and Fastboot images, and the update has arrived to my phone already, I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
INCREMENTAL UPDATE (OFFICIAL LINK) (DRIVE MIRROR LINK by me) (from TOS118C to TOS163B / from aa4d5d86bc to 8eec3af77b)
Just as I have commented earlier,
linuxct said:
If you directly click (the official download link), it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX wfotaagent/2.3 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
Click to expand...
Click to collapse
Please, note the UA string has changed from rsotaua 1.0 to wfotaagent/2.3, which makes a bit more sense. Enjoy!
Thank you!
Can I update my phone with the OTA-File with TWRP?
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
BTW, if you are using Linux (or any other OS providing wget, I have actually only used it for Linux so I'm not sure if it's available for other OS) you can easily download the package:
Code:
wget --user-agent="wfotaagent/2.3" LINK_TO_OTA_AS_I_HAVE_TO_REMOVE_TO_BE_ALLOWED_TO_POST_UNTIL_I_REMOVE_THE_LINK
I am currently downloading it although I don't know if it will be useful to me.
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Cappucinto said:
Thank you!
Can I update my phone with the OTA-File with TWRP?
Click to expand...
Click to collapse
mdosch said:
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
Click to expand...
Click to collapse
You will need to reflash AOSP's recovery in order to install this update, but please do note it's an accumulative patch, not a "Patching system image unconditionally" kind of installation. If the contents of the system partition, or the boot image (yes, that's for us magisk users out there) are unexpected, it will stop the update, and probably try to roll it back.
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
mdosch said:
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Click to expand...
Click to collapse
It's sad that XDA does that to junior members, tbh. With ten posts they'll remove all those restrictions, though. At least to me, it'd feel bad losing the interest of advanced users that might be new to the forum, yet are experienced in the topic.
linuxct said:
Since Wileyfox didn't want to supply us with Recovery and Fastboot images
Click to expand...
Click to collapse
I'm guessing they will release those eventually, right?
linuxct said:
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
Click to expand...
Click to collapse
Hi can I have a link to the AOSP recovery please
Ok, I'll give this site a new try using a temporary fresh profile to not have to spoil my browsers settings.
After some playing around I got 7.1.2 installed and rooted. I'll write down what I did to get it finally work, but YMMV so be aware you might brick your phone.
I was using Debian 9 with fastboot and adb installed.
The steps I did:
Download and unzip the fastboot image from this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Boot to stock recovery and choose "apply update from adb"
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
After successful install wipe cache and dalvik/arts cache and reboot to system with the following command:
Code:
adb reboot "dm-verity enforcing"
When the update is configured let the phone switched on for a while (I don't know why, but it ended in a bootloop and I had to start again when I instantly rebooted)
After a while boot to bootloader.
Boot (not flash) twrp: http://twrp.me/devices/wileyfoxswift2.html
Code:
fastboot boot twrp-3.1.1-0-marmite.img
Go to "ADB -> Sideload" and install Superuser: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Code:
adb sideload superuser.zip
Wipe cache and dalvik/arts cache and finally reboot with this command:
Code:
adb reboot "dm-verity enforcing"
I am not 100% sure if all steps are necessary but finally this worked for me and I am enjoying an up-to-date OS without loosing root.
I've downloaded the update as my 2X still hasn't updated.
I just cant get it to update via the recovery, my phone is default, no mods. I go to update from SD and it just errors with failed to mount SD. Even tried another SD card, same issue.
Am I missing something here? Cant be anything extra needed surely?
linuxct said:
I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
Click to expand...
Click to collapse
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
boa05 said:
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
Click to expand...
Click to collapse
I put my windows pc in router mode using the wifi adapter, and ethernet bringing internet connection. Then it was as easy as capturing just that traffic.
Deleted due to development of Android ROM version

[marmite] Official Wileyfox Swift 2+ Updates (also for root) - Repository

Hi!
As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.
But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.
1. The official update links from Wileyfox (partially from here, here and myself):
TOS118C (Recovery Image)
TOS163B (Recovery Image) Deleted by Wileyfox
TOS208G (Recovery Image) Deleted by Wileyfox
TOS249H (Recovery Image)
TOS319I (Recovery Image) Deleted by Wileyfox
TOS373J missing
UOS224B missing
UOS273C (Recovery Image)
TOS118C (Fastboot Image) Deleted by Wileyfox
TOS163B (Fastboot Image) Deleted by Wileyfox
TOS208G (Fastboot Image) Deleted by Wileyfox
TOS249H (Fastboot Image)
TOS319I (Fastboot Image)
TOS373J (Fastboot Image)
UOS224B missing
UOS273C missing
TOS089A to TOS118C (OTA Update)
TOS118C to TOS163B (OTA Update)
TOS163B to TOS208G (OTA Update)
TOS208G to TOS249H (OTA Update)
TOS249H to TOS319I (OTA Update)
TOS319I to TOS373J (OTA Update)
TOS373J to UOS224B (OTA Update to OREO 1)
UOS224B to UOS273C (OTA Update)
TOS373J to UOS273C (OTA Update to OREO 2)
2. The instructions how to make the OTA links work (taken from here):
If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
As I just found out: The "User Agent Switcher" for Chrome works just as fine.
3. The instructions how to update a rooted phone (taken from here):
I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.
3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.
3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):
Code:
adb reboot "dm-verity enforcing"
3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).
3.5. Then boot to bootloader and BOOT (not flash) TWRP
Code:
fastboot boot twrp-3.1.1-0-marmite.img
3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there
Code:
adb sideload superuser.zip
3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::
Code:
adb reboot "dm-verity enforcing"
This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...
BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.
Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.
Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?
The images from TOS208G are not available.?
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
(... I dream about Lineage 14.1)
H2Oxide said:
Thanks for this.
(... I dream about Lineage 14.1)
Click to expand...
Click to collapse
We all do, I tried an unofficial build however no WiFi yet :crying:
Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs
I am sure there is some ADB the resolve this for the oneplusone phones.
After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.
I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
quixoticduck said:
Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
Click to expand...
Click to collapse
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
However like I said at start of post what do you need from your phone/ android version?
image45 said:
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
Click to expand...
Click to collapse
Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
quixoticduck said:
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
Click to expand...
Click to collapse
You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.
Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?
Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at
http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/
H2Oxide said:
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
Click to expand...
Click to collapse
Any thoughts on this? Can I force a sideload or would that be unwise...
der_dkw said:
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
Click to expand...
Click to collapse
Sure that's fine.
I really appreciate you collected all the information and created this overview.
Well I finally managed to try the adb sideload and this is what I got.
What's wrong here?
I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G
Any help is much appreciated
Jack3volution said:
What's wrong here?
Click to expand...
Click to collapse
You are using TWRP not stock recovery.
The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).
After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Thanks! my mistake. Yeah I still have stock recovery
Cheers
mdosch said:
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Click to expand...
Click to collapse
What's the actual different between booting TWRP and flashing please?
image45 said:
What's the actual different between booting TWRP and flashing please?
Click to expand...
Click to collapse
Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.
mdosch said:
You are using TWRP not stock recovery.
Click to expand...
Click to collapse
Hmm it didn't work in stock recovery either
Jack3volution said:
Hmm it didn't work in stock recovery either
Click to expand...
Click to collapse
Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?
You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.

Oreo Beta Build

I tried to install the beta build of Oreo, following the specific instructions (by Essential Phone web site)
but at the end of adb sideload i get this error
E:Update package is older than the current build, exprected a build ne than timestamp 1511207272 but package has timestamp 1509919834 and dgrade not allowed.
E:unkonwn volume for path [/cache/recovery/uncrypt_status]
Installation aborted
Ad I'm running Android 7.1.1 and the Oreo build image is the (only) one downloaded from Essential Phone web side how is possible such an error?
https://forum.xda-developers.com/es...o-beta-1-sideload-fails-build-nmj51b-t3716066
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 just install a previous update the same way and you will be able to install the Oreo beta. I can confirm it works.
if you are running into unknown volume issues ive been able to resolve them by running "fastboot -w" from the bootloader menu and then installing the rom after. Ive also had better luck using adb push vs adb sideload with the essential phone. But as others indicate this specific issue apepars to require you to install an earlier version of stock prior to trying beta there is a thread that has all of the dumps posted.

[DEC 2017 to JAN 2018 Update] How I updated successfully

UPDATE:
In the thread @Pianobeats and @Telperion have successfully updated with less steps.
They flashed the newest Jan update flash-all without removing Magisk, Kernel, or TWRP. This eliminates the need to flash the current security update you are on and reduces the number of steps dramatically.
Clarification:
In the factory image zip you'll drill down through the files until you find flash-all.
Open that in a text editor.
Near the end you'll find "-w"
Delete it and save the flash-all.
This will make it so the update does not wipe your device.
_______________________​
I felt adventurous and decided to try updating.
I updated to latest adb & fastboot from here: SDK Platform Tools Release Notes
At first I tried using the Magisk Uninstaller Zip; it did not work.
In bootloader, I used the DEC 2017 flash-all (-w removed). This worked to get me out of the bootloader and Magisk was uninstalled.
I recommend just uninstalling Magisk from the app.
EDIT: On my second Pixel 2 ( I have two), uninstalling Magisk from the app did not work.
It stuck me into the same error in the bootloader as my first phone.
Flash-all (-w removed) worked to return me to the system.
No need to flash stock boot or dtbo.
In cmd window:
Code:
adb devices
Verify serial number (working adb & fastboot)
Code:
adb reboot bootloader
Cycle through to recovery.
Once in recovery hold PWR and press volume up once
Volume down to highlight "Apply update from ADB"
Code:
adb sideload <walleye-ota-opm1.171019.013.zip>
NOTE: Go to the where you saved the OTA zip "walleye-ota-opm1.171019.013". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: adb sideload and *Ctrl +v* to paste (Much easier)​
I rebooted to bootloader; I verified the change from boot slot b to boot slot a.
After boot > Notification: Android System - "Finishing Android Update..."
System is sluggish. Probable background processes.
Code:
adb reboot
Significantly longer reboot at Google Icon with Progress bar than normal (about 4 full minutes)
Code:
adb reboot bootloader
Code:
fastboot boot "twrp-3.2.1-0-walleye.img"
NOTE: Go to the where you saved the OTA zip "twrp-3.2.1-0-walleye.img". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: fastboot boot and *Ctrl +v* to paste (Much easier)​
TWRP > Install > twrp-pixel2-installer-walleye-3.2.1-0.ZIP
Wipe cache > Reboot system
Code:
adb reboot recovery
TWRP > Install > Snoke R1
Wipe cache > Reboot system
Code:
adb reboot recovery
TWRP > Install > Magisk V15.2
Wipe cache > Reboot system
After reboot > "Android is starting" for a half second
NOTES:​
Magisk = V15.2
ctsProfile: true
basicIntegrity: true
(Screen shot attached)
Viper4Android 2.5.0.4 = Installed and Processing properly (Screen shot attached)
Magisk Notification > DTBO Patched, please reboot > "Android System internal problem pop up"
(No, this does not affect anything.)
Also, this proves that even after mounting /system via TWRP OTAs are still usable.
NOTES #2:​
I have two Pixel 2 phones.
One for work and one for personal.
I performed the above on my personal, though havrt not had the time to update my work phone.
An OTA pushed to your device will not work on phones that have TWRP, Magisk, custom Kernel.
Screen shots attached.
Diesel_Jeremiah said:
I felt adventurous and decided to try updating.
I updated to latest adb & fastboot from here: SDK Platform Tools Release Notes
At first I tried using the Magisk Uninstaller Zip; it did not work.
In bootloader, I used the DEC 2017 flash-all (-w removed). This worked to get me out of the bootloader and Magisk was uninstalled.
I recommend just uninstalling Magisk from the app.
In cmd window:
Verify serial number (working adb & fastboot)
Cycle through to recovery.
Once in recovery hold PWR and press volume up once
Volume down to highlight "Apply update from ADB"
NOTE: Go to the where you saved the OTA zip "walleye-ota-opm1.171019.013". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: adb sideload and *Ctrl +v* to paste (Much easier)
I rebooted to bootloader; changed from boot slot b to boot slot a
After boot > Notification: Android System - "Finishing Android Update..."
System is sluggish. Probable background processes.
Significantly longer reboot at Google Icon with Progress bar than normal (about 4 full minutes)
NOTE: Go to the where you saved the OTA zip "twrp-3.2.1-0-walleye.img". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: fastboot boot and *Ctrl +v* to paste (Much easier)
TWRP > Install > twrp-pixel2-installer-walleye-3.2.1-0.ZIP
Wipe cache > Reboot system
TWRP > Install > Snoke R1
Wipe cache > Reboot system
TWRP > Install > Magisk V15.2
Wipe cache > Reboot system
After reboot > "Android is starting" for a half second
NOTES:
Magisk = V15.2
ctsProfile: true
basicIntegrity: true
(Screen shot attached)
Viper4Android 2.5.0.4 = Installed and Processing properly (Screen shot attached)
Magisk Notification > DTBO Patched, please reboot > "Android System internal problem pop up"
(No, this does not affect anything.)
Also, this proves that even after mounting /system via TWRP OTAs are still usable.
Click to expand...
Click to collapse
Are you on a Verizon branded one? Or Google Store came unlocked?
Google unlocked with Verizon SIM.
Sent from my Pixel 2 using Tapatalk
Thanks a ton for this tutorial. This is my first Google device and I'm really worried that I'm going to mess something up. I came from an HTC 10 which seemed so much easier to navigate around and flash on. I plan on using your method tomorrow morning once I have all of the related files downloaded and some quality time to spare.
I have the same set up as you. Google bought with a Verizon Sim. I currently have TWRP and Magisk 15.2 installed so I think your instructions should apply to me perfectly.
Thanks again.
jascolli said:
Thanks a ton for this tutorial. This is my first Google device and I'm really worried that I'm going to mess something up. I came from an HTC 10 which seemed so much easier to navigate around and flash on. I plan on using your method tomorrow morning once I have all of the related files downloaded and some quality time to spare.
I have the same set up as you. Google bought with a Verizon Sim. I currently have TWRP and Magisk 15.2 installed so I think your instructions should apply to me perfectly.
Thanks again.
Click to expand...
Click to collapse
Best thing to do is download the factory image and remove -w from flash-all. (removing -w keeps your device from wiping)
This gives you something to fall back on if all else fails.
Ensure you use the flash-all for your current build & security patch.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Best thing to do is download the factory image and remove -w from flash-all. (removing -w keeps your device from wiping)
This gives you something to fall back on if all else fails.
Ensure you use the flash-all for your current build & security patch.
Click to expand...
Click to collapse
Does flashing the factory image replace the kernel too?
doublej713 said:
Does flashing the factory image replace the kernel too?
Click to expand...
Click to collapse
Yes.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Yes.
Click to expand...
Click to collapse
If I flash-all with the -w included, is that basically a factory reset? Also, does that flash both slots and/or do you need to flash both slots?
doublej713 said:
If I flash-all with the -w included, is that basically a factory reset? Also, does that flash both slots and/or do you need to flash both slots?
Click to expand...
Click to collapse
Yes, if you do not remove the -w, it will reset your device.
It flashes both slots A & B.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Yes, if you do not remove the -w, it will reset your device.
It flashes both slots A & B.
Click to expand...
Click to collapse
Last question, if I'm willing to lose all my data, can I just flash the latest factory image? This is my first pixel device, and while all of this seems the same as other phones, the terminology seems to be a little different.
doublej713 said:
Last question, if I'm willing to lose all my data, can I just flash the latest factory image? This is my first pixel device, and while all of this seems the same as other phones, the terminology seems to be a little different.
Click to expand...
Click to collapse
Yes
Sent from my [device_name] using XDA-Developers Legacy app
Edited original post with Note #2.
OTAs will not work on modified phones.
Screenshots added.
I'm kind of new so here are some questions.
So the first step is essentially getting rid of Magisk by flashing the December patch by using the "flash-all.bat" batch file, right? This is essentially unrooting your phone.
Then you sideloaded the January OTA. But it says that you switched from Boot Slot B to Boot Slot A. Is there a reason for that?
Also is Snoke R1 a custom kernel? If we're not installing a custom kernel we just skip that step right?
Sorry for all the questions. You're the only person who actually made a proper guide. Thanks!
Pianobeats said:
I'm kind of new so here are some questions.
Click to expand...
Click to collapse
Welcome, and questions are always ok.
Pianobeats said:
So the first step is essentially getting rid of Magisk by flashing the December patch by using the "flash-all.bat" batch file, right? This is essentially unrooting your phone.
Click to expand...
Click to collapse
You are mostly correct. OTA cannot verify the system with Magisk installed. OTA cannot install without the stock recovery.
Flash-all is returning your system boot & dtbo, and returning the stock recovery.
This must happen so when the new OTA verifies the system it will meet all of the checks.
Pianobeats said:
Then you sideloaded the January OTA. But it says that you switched from Boot Slot B to Boot Slot A. Is there a reason for that?
Click to expand...
Click to collapse
I will update the OP to say I verified the boot slot switched.
Before you start, your phone will be on Boot slot B or slot A.
Google improved the OTA system; there are two boot slots. When the OTA is installed, it installs first on the non-booting slot. Once it's complete, your phone switches the boot slot until the next OTA it will switch again. So, it will go A to B, or B to A, depending on the current slot. This makes the transition to new OTA easier and faster.
Pianobeats said:
Also is Snoke R1 a custom kernel? If we're not installing a custom kernel we just skip that step right?
Click to expand...
Click to collapse
The Snoke kernel is a custom kernel. R1 is the build for 8.1
If you do not want a custom kernel, yes you will skip it.
Alternatively, you will have to use Magisk patched boot method with the Stock boot image.
Look here if that's what you want to do: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Steps and process are the same for patching the stock boot.
Pianobeats said:
Sorry for all the questions. You're the only person who actually made a proper guide. Thanks!
Click to expand...
Click to collapse
:good:
Diesel_Jeremiah said:
Welcome, and questions are always ok.
You are mostly correct. OTA cannot verify the system with Magisk installed. OTA cannot install without the stock recovery.
Flash-all is returning your system boot & dtbo, and returning the stock recovery.
This must happen so when the new OTA verifies the system it will meet all of the checks.
I will update the OP to say I verified the boot slot switched.
Before you start, your phone will be on Boot slot B or slot A.
Google improved the OTA system; there are two boot slots. When the OTA is installed, it installs first on the non-booting slot. Once it's complete, your phone switches the boot slot until the next OTA it will switch again. So, it will go A to B, or B to A, depending on the current slot. This makes the transition to new OTA easier and faster.
The Snoke kernel is a custom kernel. R1 is the build for 8.1
If you do not want a custom kernel, yes you will skip it.
Alternatively, you will have to use Magisk patched boot method with the Stock boot image.
Look here if that's what you want to do: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Steps and process are the same for patching the stock boot.
:good:
Click to expand...
Click to collapse
I am on december version, what if i download january factory image and flash this with flash-all (without -W) on my pixel 2? I am rooted , no twrp and using flash kernel.
Is this important to flash december factory image again before flashing updating to newer one ?
I want to keep my data and settings.
Billion THX for your great help, i am really learning a lot here.
Daandofreak said:
I am on december version, what if i download january factory image and flash this with flash-all (without -W) on my pixel 2? I am rooted , no twrp and using flash kernel.
Is this important to flash december factory image again before flashing updating to newer one ?
I want to keep my data and settings.
Billion THX for your great help, i am really learning a lot here.
Click to expand...
Click to collapse
I did not try to go straight to the JAN update. I needed to use flash-all to restore stock recovery because of TWRP.
Safest:
Either flash the DEC from flash-all (without -w) or fastboot flash boot & dtbo.
Then you should be successful updating from DEC to JAN.
Guinea pig:
Flash the JAN flash-all (without -w) and see what happens.
I have not tried this (because TWRP).
Removing the -w in the factory image keeps data and settings.
OTAs will keep data and settings.
OTAs are the best way to update.
If you're going to flash a factory image, you're better off just flashing the January factory image (sans -w) and getting it all done in one step. That's the method I used, and it worked just fine and kept my data intact. OTA's are flashed with ADB commands from the stock recovery, factory images are flashed through the bootloader, so TWRP doesn't interfere at all.
You'll of course still need to boot the TWRP and flash the TWRP zip afterwards, but the preceding steps are much easier.
Telperion said:
If you're going to flash a factory image, you're better off just flashing the January factory image (sans -w) and getting it all done in one step. That's the method I used, and it worked just fine and kept my data intact. OTA's are flashed with ADB commands from the stock recovery, factory images are flashed through the bootloader, so TWRP doesn't interfere at all.
You'll of course still need to boot TWRP and re-flash the zip afterwards, but the preceding steps are much easier.
Click to expand...
Click to collapse
So your saying: Flash Jan factory image (-w removed) on top of Dec will not require removal of TWRP and won't break anything?
Diesel_Jeremiah said:
So your saying: Flash Jan factory image (-w removed) on top of Dec will not require removal of TWRP and won't break anything?
Click to expand...
Click to collapse
Correct.
The recovery is part of the boot image, so the only time you'd need to remove TWRP is if you're trying to flash something that requires the stock recovery. OTA's require the stock recovery; factory system images don't, they flash a stock boot and dtbo as part of the flashing process.
The one caveat is that for Verizon users, there may be a possibility that flashing a factory image complete with updated bootloader may re-lock the bootloader on them. But for everyone else, it's fine. Even the Verizon users could just extract the factory image and flash the components in the script, minus the bootloader:
Code:
[STRIKE]fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img[/STRIKE]
[STRIKE]fastboot reboot bootloader[/STRIKE]
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.013.zip
Can someone explain in more detail how to remove the "w" from the factory image? TIA

How to OTA a Moto G6 plus when rooted with Magisk?

My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following:
- Magisk Manager > Uninstall > Restore Images
- Settings > System > System Update
The phone started to download the OTA (about 300 MB), but afterwards said something like "sorry, that didn't work out".
I then did:
- Magisk Manager > Install > Install
and then phone is fine for now.
I can probably catch the download URL for the OTA by using the logcat method. But what would I do with an OTA zip? The OTA is significantly smaller than a complete firmware (about 2 GB).
bornheim2 said:
My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following:
- Magisk Manager > Uninstall > Restore Images
- Settings > System > System Update
The phone started to download the OTA (about 300 MB), but afterwards said something like "sorry, that didn't work out".
I then did:
- Magisk Manager > Install > Install
and then phone is fine for now.
I can probably catch the download URL for the OTA by using the logcat method. But what would I do with an OTA zip? The OTA is significantly smaller than a complete firmware (about 2 GB).
Click to expand...
Click to collapse
I'm not sure if that's possible, but I wouldn't try it. The best way is to reflash stock and then accept the OTA. Afterwards, you can reinstall Magisk.
See if the firmware update has been posted here. In either case do a backup with Titanium Backup first. If the complete firmware update has been posted, flash it with fastboot in the bootloader. If it had not been posted, flash the latest version available and then Ota. After your up to date reflash magisk in twrp.
Sent from my moto g(6) plus using Tapatalk
Hi,
At time, is no solution to update with OTA with a rooted MotoG6+ with Magisk.
I'm working on a workaround.
Regards.
You can also use Lenovo Moto Smart Assistant and "Rescue" your device. It basically downloads the firmware and flashes it for you (wiping everything on the device (excluding External SD). That's what I did.
New OTA update arrived today. Is there already a solution for this? I thought that the new systemless Magisk would "fix" this, but OTA update still fails. No clue why. I even ended up in a bootloop, but switching active partition back to b fixed that...
I don't get why we should be excluded from updates, just because we want to be root on the devices we own. It just doesn't make sense.
This time I tried removing Magisk and restoring boot and system partition (from backup before installing Magisk) before starting the OTA because someone said that when you start the OTA it switches A_B partitions and restoring from backup doen't restore them in the right place and thats why it might fail (or something like that) BUT same result. OTA fails! I guest every month I'll have to flash stock (losing everything on the phone in the process) -> install OTA -> reinstall everything.
WHY exactly the OTA fails? It shouldn't detect that the partitions are modified because they're not (restored from backup before Magisk).
ivailogeimara said:
You can also use Lenovo Moto Smart Assistant and "Rescue" your device. It basically downloads the firmware and flashes it for you (wiping everything on the device (excluding External SD). That's what I did.
Click to expand...
Click to collapse
I have XT1926-3 and Lenovo Moto Smart Assistant says that my device is not supported. Do you have the same device?
joris1977 said:
I have XT1926-3 and Lenovo Moto Smart Assistant says that my device is not supported. Do you have the same device?
Click to expand...
Click to collapse
I used LMSA when I was running OPW113.89 to update to OPW113.89-2 (via the Recovery option). It asked me to select the product and model of the phone. I selected "Moto G Plus (6th Gen)" for the product and for the "Model Name" I had XT1926-2,XT1926-3,XT1926-5,XT1926-6,XT1926-7,XT1926-8,XT1926-9. The new version of the LMSA has 3 buttons at the top of the rescue screen: "Lenovo Phone", "Lenovo Tablet", "MOTO Phone". Make sure that you select "MOTO Phone"
I'll try it again because I just tried to recover system partition backup (made with TWRP) with TWRP and bricked my phone. And for some reason I can't flash the images from the firmware with fastboot. For some of the images that have A and B partitions it tries to flash them to non existent partitions. For example:
Code:
fastboot flash boot boot.img
or
Code:
fastboot flash system system.img_sparsechunk.0
tries to flash them to boot__b or boot__a or system__b or system__a (with double '_')
The annoying thing is that I don't have Windows outside VM so every time I need to run LMSA I have to create WINTOGO usb just to run LMSA.
ivailogeimara said:
I used LMSA when I was running OPW113.89 to update to OPW113.89-2 (via the Recovery option). It asked me to select the product and model of the phone. I selected "Moto G Plus (6th Gen)" for the product and for the "Model Name" I had XT1926-2,XT1926-3,XT1926-5,XT1926-6,XT1926-7,XT1926-8,XT1926-9. The new version of the LMSA has 3 buttons at the top of the rescue screen: "Lenovo Phone", "Lenovo Tablet", "MOTO Phone". Make sure that you select "MOTO Phone"
I'll try it again because I just tried to recover system partition backup (made with TWRP) with TWRP and bricked my phone. And for some reason I can't flash the images from the firmware with fastboot. For some of the images that have A and B partitions it tries to flash them to non existent partitions. For example: or tries to flash them to boot__b or boot__a or system__b or system__a (with double '_')
The anoying thing is that I don't have Windows outside VM so every time I need to run LMSA I have to create WINTOGO usb just to run LMSA.
Click to expand...
Click to collapse
Why did you try to update with lenovo assist? Was your rom clean as in no Magisk?
What TWRP did you use, and was your device encrypted?
Need much more info to be able to help, also what is your main OS because you don't need windows for fastboot.
Have you tried booting original boot.img through fastboot?
Maybe changed active slot?
Coldstream said:
Why did you try to update with lenovo assist? Was your rom clean as in no Magisk?
What TWRP did you use, and was your device encrypted?
Need much more info to be able to help, also what is your main OS because you don't need windows for fastboot.
Have you tried booting original boot.img through fastboot?
Maybe changed active slot?
Click to expand...
Click to collapse
Uninstalled Magisk from Magisk manager. Device is encrypted. The TWRP I use is from this thread.
The previous time I used LMSA was because uninstalling Magisk (which flashed boot partition backup) didn't help with installing the OTA (it still failed). And flashing the images from firmware with fastboot gave error. It tried to flash them to boot__a or boot__b, system__a or system__b (with double underscore). I was gonna try updating with LMSA again but decided to try flashing images from the firmware manually with mfastboot this time and it worked. It'll be good if in the guide for "how to return to stock" it said that the included fastboot is mfastboot.
I just flashed the stock images (without data,cache) with mfastboot and I'm trying to update again via OTA.
Update: OTA installed successfully!
PS: Can I check if some partition is modified in some way like OTA does?
ivailogeimara said:
WHY exactly the OTA fails? It shouldn't detect that the partitions are modified because they're not (restored from backup before Magisk).
Click to expand...
Click to collapse
Yeah I am asking myself the same question. I grabbed a log file and it shows a lot of:
Code:
/system/bin/update_engine: [libfs_mgr]Error finding 'slot' in device tree
I am clueless, but it seems that Magisk somehow disabled the ability for the phone to see slot A. An error that stays even after Magisk is fully removed; I even flashed the untouched boot.img back. But that made no difference.
I also tried sideloading the OTA with ADB on the recovery screen, but that fails too & I see the same error on the screen.
BTW You can grab the OTA with help of this website: http://erfanoabdi.000webhostapp.com/
I am always a bit hesitant in posting log files with a lot of stuff that I don't understand, but as an attachment I add here the lines of the log that contain messages about the update_engine.
joris1977 said:
Yeah I am asking myself the same question. I grabbed a log file and it shows a lot of:
Code:
/system/bin/update_engine: [libfs_mgr]Error finding 'slot' in device tree
I am clueless, but it seems that Magisk somehow disabled the ability for the phone to see slot A. An error that stays even after Magisk is fully removed; I even flashed the untouched boot.img back. But that made no difference.
I also tried sideloading the OTA with ADB on the recovery screen, but that fails too & I see the same error on the screen.
BTW You can grab the OTA with help of this website: http://erfanoabdi.000webhostapp.com/
I am always a bit hesitant in posting log files with a lot of stuff that I don't understand, but as an attachment I add here the lines of the log that contain messages about the update_engine.
Click to expand...
Click to collapse
I think this:
Code:
12-20 13:31:48.480 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1099)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
12-20 13:31:48.480 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1104)] Expected: sha256|hex = 66305C30BC5570791036FFC5B57E620D516B35664C3EE5B27F97FBFD5E288817
12-20 13:31:48.481 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1107)] Calculated: sha256|hex = E2D46DB42162711333E99BF1CBD0224F5867F6E7387FA276D30EC54755AF454B
is where the update fails. I'm not sure though what partitions is the OTA checking.
I flashed every partition listed in servicefile.xml (in the stock firmware files that you can flash) and after that I was able to install the OTA. Next I made backups/images (not restorable though) with dd of all the partitions that are listed in servicefile.xml because clearly one or multiple of those get changed after installing Magisk and that's why the OTA fails. After that I installed magisk and made backups with dd again and compared the two to see what changes after installing Magisk. These are the partitions that were changed after Magisk and are in servicefile.xml:
Code:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
I guess uninstalling Magisk only restores the boot partition and one of the others fails the check. Probably oem_b.
PS: Well I guess for now the solution will be to flash everything listed in servicefile.xml (except system and system_b) via mfastboot before each OTA.
Thanks for your informative post @ivailogeimara
Lenovo fixed their Lenovo MOTO smart assistance, so now you can reflash your device. with the help of this app. I just reflashed my device and everything is working as expected.
If you use LMSA it downloads a zip file with the full OS where the new OTA is already included. Probably you can cut off the rescue operation after the full zip has arrived and you can just use that zip to flash the boot partition and that oem_b. partition I didn't try that, because I had limited time, had already backed up all my data and I needed a working phone. This is probably what I will try next time an OTA arrives.
Maybe we should make the magister developers aware about the troubles with the Moto G6 plus. It is probably I bug somewhere that uninstalling Magister does not fully restore the old install.
ivailogeimara said:
These are the partitions that were changed after Magisk and are in servicefile.xml:
Code:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
I guess uninstalling Magisk only restores the boot partition and one of the others fails the check.
Click to expand...
Click to collapse
This is exactly what I get on my phone. For the last two OTAs these are the partitions that fail the checksum verification. As you mentioned this is fixed by flashing the partitions from a known good source.
I used TWRP via "mfastboot boot twrp.img" to dump boot.img, modify it via Magisk-Manger and then flash it using mfastboot. I don't see any way how I would modify the other partitions (except boot, of course) this way.
I looked into the oem-partition and it has its "last mounted" timestamp changed to something very, very recent. This is why I rule out TWRP. My best guess is that Magisk mounts those partitions shortly as rw maybe on boot? That would already be enough to make the hash fail
So basically to be able to install the OTA:
1. after clean stock reinstall (before magisk installation) backup the above mentioned partitions
2. install magisk, etc.
3. later when an OTA update comes restore the backed up partitions + remove magisk and then install the OTA
4. back to step 1
I suppose the partitions can also be restored if you find the firmware that is identical to what the phone is currently running.
Or???
axsdenied1 said:
I suppose the partitions can also be restored if you find the firmware that is identical to what the phone is currently running.
Or???
Click to expand...
Click to collapse
Yes, that's what I did. Never thought to pull a backup of a partition that would only "ever" be changed by the OTA process I googled a bit for my version number until I found a matching stock ROM.
Moto g6 + rooted with twrp and magisk. I have an OTA update.
The OTA gets errored out right after I download the update and it tries to install it.
Phone version: XT1926-7
Using latest twrp 3.2.3
Magisk v18.0 installed.
Successfully enabled root just the other day.
Now I get the OTA update ppw29.116-11 wanting there pie update to rollout, was so happy. Except it keeps saying unsuccessful right after it's done downloading and tries to install I guess.
Has anyone found a safe workout for this?
It is outlined in the post just before the one you made...
So
before installing Magisk you should have made a backup from the following partitions:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
when an OTA update comes, remove magisk and restore the backed up partitions.
then install the OTA
make a backup again.
This should work, but I didn't test it yet.

Categories

Resources