Database Users

[OTA] Captured Pure Edition XT1095 update from 23.16.3 to 23.16.6 (stagefright patch)

I received a Motorola OTA notification for a minor maintenance update which patched the "stagefright" vulnerability in my Moto X 2014 Pure Edition xt1095. I captured the OTA ZIP file from my cache folder, and it is attached to this post. Size of OTA ZIP is 4.29MB. (Note that Motorola OTA updates are named for the software version from which you must apply the update, not the software version to which you are upgrading.)
This is for a stock, unrooted xt1095 running Android Lollipop 5.1.
Prerequisite:
System version: 23.16.3
Build number: LPE23.32-21.6 or LPE23.32-21.3
After update:
System version: 23.16.6
Build number: LPE23.32-21.6 or LPE23.32-21.3 (unchanged)
You should be able to adb sideload this from stock recovery if you know how. If you're rooted, you'll need to request the stock 23.16.3 firmware from Motorola, and at least flash system.img and recovery.img to get back to stock system and recovery. After you do that, you might be able to sideload the OTA zip.

Deleted, sorry.

Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.

romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.

Thanks thenestor and Romracer worked perfectly as stated I went with twrp flash -

I just installed this update from the stock recovery and it worked flawlessly. Thanks for uploading this. My wife got it a few days ago and updated before I could grab the the zip file.
Sent from my XT1095 using Tapatalk

Flintberg said:
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Click to expand...
Click to collapse
System.img? Download please

I reflashed system.img of my current version and then flashed the zip in twrp.

romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?

I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?

I'm rooted with adaway applied, I tried flashing romracer's file but I'm stuck on the boot screen saying that my bootloader is unlocked. Is it because of adaway?

romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thank you so much for this! I lost my stock recovery so this is a godsend.

Flintberg said:
I reflashed system.img of my current version and then flashed the zip in twrp.
Click to expand...
Click to collapse
system.img have the backup to download and can flash? Sorry my english

tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
I'm having the same problem! Any idea how to fix it?

Damn. That file from romracer broke my phone
seriously....i can't fix it

@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops

sh33z0r said:
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
Click to expand...
Click to collapse
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
supremekizzle said:
Damn. That file from romracer broke my phone
seriously....i can't fix it
Click to expand...
Click to collapse
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
macravin said:
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
Click to expand...
Click to collapse
RSchmauk said:
I'm having the same problem! Any idea how to fix it?
Click to expand...
Click to collapse
Did you have Xposed install? Reflash the install zip. Otherwise see above.

romracer said:
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
Did you have Xposed install? Reflash the install zip. Otherwise see above.
Click to expand...
Click to collapse
i was rooted with xposed only, and now my phone won't turn on, stuck on the boot screen...
i have two questions,
If i reflash system.img, will that wipe anything?
is there a system.img only file that i can download, downloading 1.1 gbs on my slow connection will take 4 hours, i can't afford 4 hours without a phone....

After the ota, my phone won`t turn on, like many here. What i`m worried about is that my PC is not recognizing my phone in adb. What can I do?

I was also rooted, with stock everything else but hung on the unlocked bootloader warning screen. I'm thinking AdAway or Greenify must have modified /system since that's really the only root stuff I use. For the time being I just restored my /system backup and it's working but I'll eventually need to flash stock system.img I'm guessing. Otherwise I'm gonna end up accidentally tapping the update nag screen and screwing it up again.

OTA Update with systemless root

I just received a notification on my 6P saying that the january security update is available. The thing is that I'm rooted with systemless root, xposed, EX Kernel and TWRP. Can I update using the update button?

With systemless I believe you should be able to.

I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol

Pain-N-Panic said:
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Click to expand...
Click to collapse
No.
If you have TWRP installed you will not be able to take an OTA.
Why bother?
Just flash what you want.

Ok, so if I reboot and my phone tries to install the OTA, what happens?

I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition

This update message won't go away. Can I flash it myself through TWRP with Xposed installed?

You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.

dratsablive said:
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.

Pain-N-Panic said:
Ok, so if I reboot and my phone tries to install the OTA, what happens?
Click to expand...
Click to collapse
Nothing happens. it'll just fail to flash the update. It'll reboot to twrp, attempt to flash the update, and it'll fail the flash. So it just won't flash. Then you'll just reboot the system and nothing will be changed. I think you can flash these minor changes, but if you try to flash a major update through OTA it won't work with out stock recovery because that's part of the flash I think
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
regenwurm16 said:
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
Click to expand...
Click to collapse
It does not bored because of mismatched kernel. Because I tried flashing the stock kernel and then OTA and it still did not work

kirkgbolton said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Click to expand...
Click to collapse
This. At this time it's the only fix. I did it as well. Never flashed a factory image via fastboot before so I was a little intimidated but Heisenberg's guide is so smooth and easy to follow I did it in about 5 minutes lol. Plus it was a great learning experience for me.

Is it likely that eventually TWRP flashable zips will make this process easier? Or is there some sort of restriction with these updates for Nexus phones that will always require fastboot?

Not sure. I do know that the above method only took me about 10 minutes. Yeah it sucks you have to utilize a PC to do it but its really not that bad. Maybe in the future someone will figure out how to implement the updates via flashable zip in recovery.

I struggle with this too. I really hope that someone will find a solution to flash it via .zip (sadly I'm more a programmer than an Android-hacker, otherwise I would try my very best right now ).

Just to point it out, it looks like the article you are referring to has been updated since it was linked. I wouldn't want to wipe userdata, so I think 11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact) is what you were referring to at the time. Apologies for the resurrection.

I just used the FlashFire app to update my Nexus 6p with the February update and it worked like a charm.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/

{Guide} How to Root ONEPLUS 3T (Unlock bootloader, TWRP Recovery, SuperSu)

Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao

Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.

Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.

*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?

Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!

Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.

Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/

I'm having the same problem

respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?

Try this SuperSU

I heard only SuperSU SR3 works

Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.

I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help

nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp

hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)

respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find

[Tutorial][OOS]Proper Way to Update OOS Through OTA on Rooted OnePlus 3/3T

This is what I found accidentally by myself. There is actually an easy way to flash the OTA update if you are too lazy to find a download link for the zip file(like me).
Required: TWRP(Always use the latest version to avoid problems), Any file manager
1. Download the update in settings through OTA. (Make sure full zip file is downloaded which normally exceeds 1GB.)
2. After finishing the download, open your file manager and enable the Show Hidden Files function.
3. Go to Internal Storage and find the folder named .Ota then copy the zip file to any directory you like.(Visible one which is not hidden.)
4. Reboot to TWRP and flash the zip file you downloaded, Magisk/SuperSU and other mods you like.
5. Wipe Dalvik and Cache
6. Reboot
7. Enjoy the update.
Ps: You should root your device before rebooting to prevent the TWRP from getting overwritten by stock recovery.

Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4

counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4
Click to expand...
Click to collapse
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.

DawoodSahi said:
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.
Click to expand...
Click to collapse
The DM Verity is usually okay because of magisk patching the boot image

counterfeit187 said:
The DM Verity is usually okay because of magisk patching the boot image
Click to expand...
Click to collapse
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?

DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, usually. Just make sure you don't let it reboot before you flash magisk or SuperSU

what if we have flashed a kernel?

DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Ramith96 said:
what if we have flashed a kernel?
Click to expand...
Click to collapse
You mean you're currently on a custom kernel? If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.

Diatomix98 said:
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Click to expand...
Click to collapse
Yup I updated last night, just flashing the open beta 14 zip and magisk in TWRP before reboot.

counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct?
Click to expand...
Click to collapse
If you root before rebooting (after flashing the full update zip), TWRP will remain. If you don't root, it will overwrite TWRP with stock recovery.
The whole process is already described (and in better detail) here: https://forum.xda-developers.com/showpost.php?p=70084260&postcount=3
Although admittedly, the info is not that obvious to find.
---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------
Diatomix98 said:
This is what I found accidentally by myself. It's been told countless time that we should not update through OTA if our phone is rooted which will most probably brick the phone. However there is actually an easy way to flash the OTA update
Click to expand...
Click to collapse
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
Diatomix98 said:
If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.
Click to expand...
Click to collapse
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.

When we flash again doesn't it replace the twrp with the stock recovery?

redpoint73 said:
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.
Click to expand...
Click to collapse
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here. That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.

Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
If by "it" you mean the recovery, then as it was mentioned a few posts earlier, NO, TWRP remains.
Unleashed by ONEPLUS 3T rooted

Diatomix98 said:
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here.
Click to expand...
Click to collapse
No worries. I understand the confusion, as I agree the info in some threads isn't specific enough.
Diatomix98 said:
That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.
Click to expand...
Click to collapse
You're certainly welcome. Again, your tutorial will most certainly be useful to a lot of folks; as it will make the info easier to find. So having the best info (and easy to understand) is good all around. :good:
---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------
Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
Already answered a couple times in this thread.
If you update and immediately root, TWRP will remain.
If you update, and don't root, then yes TWRP may be replaced with stock recovery.

failed
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.

thesishir said:
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.
Click to expand...
Click to collapse
Did you verify the downloaded update file was larger than 1 GB?

redpoint73 said:
Did you verify the downloaded update file was larger than 1 GB?
Click to expand...
Click to collapse
Yes I did! The file size is 1.43 gb to be exact but still no luck

thesishir said:
Yes I did! The file size is 1.43 gb to be exact but still no luck
Click to expand...
Click to collapse
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/

redpoint73 said:
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
Click to expand...
Click to collapse
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.

thesishir said:
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.
Click to expand...
Click to collapse
Only other think I can think of, is to do a full wipe (data, Dalvik, cache - the default wipe in TWRP). But you may not like that.
Or make sure you are on latest TWRP 3.1.1-2, or reflash TWRP.

[guide] how to dirty flash open beta on 5/5t ( compitibility & magisk solution)

Hello there,
Although we have done these things tens of times recently we are having some issues with the updates if we are rooted and have magisk modules installed.
I just want to write a small guide to overcome these things which might be helpful.
1) Download the full update zip form Settings/system/system updates/ it is downloaded inside Internal/.ota folder which is hidden by default. or download from anywhere and keep in your storage.
2)Install and Open Mixplorer file manager (MANDATORY) from HERE (Trust me its the best file manager Thanks to @HootanParsa ) if you are already on Pie Be on latest blu_spark TWRP V9.100 HERE Thanks to @eng.stk and skip #3
3) Go to .ota folder open the update zip and delete Compitibility.zip (extracting and repacking is not necessary)
4) Go to Magisk Manager and disable all magisk modules. (Mandatory else there will be reboot issue)
5) Reboot to recovery and flash Full update.zip
6) Flash latest Magisk Zip HERE Thanks to @topjohnwu (it keeps your TWRP alive)
7) Reboot System
8) Open Magisk Manager and Enable all modules and reboot your phone
Cheers!!
Note: if you still get reboot issues just keep a latest magisk modules remover in your storage HERE reboot to TWRP and flash it and reboot to system.
Don't forget to smash Thanks Button ??

I believe you need to delete the compatibility zip also to flash in TWRP ?

benny3 said:
I believe you need to delete the compatibility zip also to flash in TWRP ?
Click to expand...
Click to collapse
Yeah it's a must read no 3

intoxicated.mad said:
Yeah it's a must read no 3
Click to expand...
Click to collapse
My bad i missed #3. I'm installing beta 22 as we speak.

benny3 said:
My bad i missed #3. I'm installing beta 22 as we speak.
Click to expand...
Click to collapse
I made it bold for you lol

Might want to fix the link to MiXplorer. It takes you to the the thread, but opens it in reply mode.

Anyone successfully remove webview? Titanium shows Frozen and won't defrost. Debloater works great otherwise.
Sent from my OnePlus5T using XDA Labs

tcat007 said:
Anyone successfully remove webview? Titanium shows Frozen and won't defrost. Debloater works great otherwise.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
On H2OS I did delete that manually and installed bromite webview but it didn't work on OOS, BTW if you keep Chrome you won't have issues I guess.

intoxicated.mad said:
4) Go to Magisk Manager and disable all magisk modules. (Mandatory else there will be reboot issue)
Click to expand...
Click to collapse
And if you forgot to disable the magisk modules(like i did :angel: ), just flash "Magisk Uninstaller" - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, then the Magisk installer and then.... nooo more rebooting problem.
Thanks for the guide :good:

getting error 7 on twrp you got the link the the stock boot image of pie by any chance??

Dragonlord07 said:
getting error 7 on twrp you got the link the the stock boot image of pie by any chance??
Click to expand...
Click to collapse
Did you use Mixplorer to delete the compatibility.zip??
boot.img will be of no use if you have a corrupted zip

intoxicated.mad said:
Did you use Mixplorer to delete the compatibility.zip??
boot.img will be of no use if you have a corrupted zip
Click to expand...
Click to collapse
did it on a desktop so using 7 zip
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
Dragonlord07 said:
did it on a desktop so using 7 zip
Click to expand...
Click to collapse
nvm it worked

Dragonlord07 said:
did it on a desktop so using 7 zip
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
nvm it worked
Click to expand...
Click to collapse
I had problem with 7 zip that's why I didn't mention,
Glad it worked for you :good:

@intoxicated.mad, FYI I took the Telegram link out of the OP as doing so is no longer allowed.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse

the Doctor said:
@intoxicated.mad, FYI I took the Telegram link out of the OP as doing so is no longer allowed.
Click to expand...
Click to collapse
Nevermind, I'm sorry for including it

Guide updated with blu_spark TWRP V9.91 link no need to delete compitibility.zip now!! Cheers

Hello, after installing blu_spark TWRP V9.91 i cannot get into Recovery anymore, the screen remains black and the led turns on. I need to restart and then reflash TWRP thru their update application. Im disabling Magisk modules and have even tried setting the core only mode but nothing seem to work. I have tried installing blu_sparks kernel and it works fine, only recovery TWRP does not work. Im stuck not being able to install the ltest update since normal TWRP does not support it and for some reason the process explained in this forum does not work for me. Any ideas? I must be doing something wrong. Thanks in advance.

mestradab said:
Hello, after installing blu_spark TWRP V9.91 i cannot get into Recovery anymore, the screen remains black and the led turns on. I need to restart and then reflash TWRP thru their update application. Im disabling Magisk modules and have even tried setting the core only mode but nothing seem to work. I have tried installing blu_sparks kernel and it works fine, only recovery TWRP does not work. Im stuck not being able to install the ltest update since normal TWRP does not support it and for some reason the process explained in this forum does not work for me. Any ideas? I must be doing something wrong. Thanks in advance.
Click to expand...
Click to collapse
I think you are on Oreo or decrypted and blu_spark TWRP v9.91 isn't compatible with that as far as I know, so ignore that part and try using previous version.

Hi, yes, I'm on Oreo but encrypted. Anyway, I tried with bluspark TWRP 9.85 which actually boots fine but when installing the update I get the same error as with official twrp, some zip compatibility error. I did delete compatibility.zip from the zip file but still doesn't doesnt do the trick.
Regards

mestradab said:
Hi, yes, I'm on Oreo but encrypted. Anyway, I tried with bluspark TWRP 9.85 which actually boots fine but when installing the update I get the same error as with official twrp, some zip compatibility error. I did delete compatibility.zip from the zip file but still doesn't doesnt do the trick.
Regards
Click to expand...
Click to collapse
Did you delete using Mixplorer??
Make sure you follow every word properly