Database Users

How to Root Honor 8 FRD-L09 (NOUGAT 7.0 EMUI 5.0 With Bluetooth, NFC, system apps)

I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson

thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM

omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.

Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?

david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!

Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:

david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.

N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)

After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/

david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day

Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.

fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed

Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!

fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!

Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!

fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!

[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.

On Magisk root, Oreo, I accepted OTA October security patch and did a bit a of a mess

Started the update, phone rebooted to TWRP. Selected system reboot.
It rebooted correctly. Now Magisk appears not to be installed, Magisk Manager asks me if I want to install Magisk 14.0 (the install button is active) but at the same time it says I have 14.0 installed.
I have no root anymore and the system update says "Verification problem", in red, and offers the option to "Try again".
Clearly I did something quite wrong. How can I go back to have Magisk installed correctly, with root, but at the same time take advantage of security updates?
Thanks in advance. I'm starting a new thread because I keep on seeing posts related to Nougat or earlier and I don't know if something has changed with Oreo (plus I'm actually not finding clear instructions on how to proceed, anyway).

Hmmm... ok, I'm back to where I started. I reinstalled Magisk from Magisk Manager, now I'm back to root enabled and Safety Net Check Success.
If there's a clear guide on how to update for monthly security patches, I'd really appreciated a link. Thanks again.

gorman42 said:
Hmmm... ok, I'm back to where I started. I reinstalled Magisk from Magisk Manager, now I'm back to root enabled and Safety Net Check Success.
If there's a clear guide on how to update for monthly security patches, I'd really appreciated a link. Thanks again.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3206928
Option #9
Inviato dal mio Nexus 6P utilizzando Tapatalk

Is it correct to follow point 9 of this guide? https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I am probably simply too thick to understand but when I read "new build of stock ROM" I did not think it could apply to simple monthly security updates.

CyberZeus1977 said:
https://forum.xda-developers.com/showthread.php?t=3206928
Option #9
Click to expand...
Click to collapse
Thanks. So I need to do this for every monthly security update, correct? Sorry for the previous message but I wrote while you were writing.

gorman42 said:
Thanks. So I need to do this for every monthly security update, correct? Sorry for the previous message but I wrote while you were writing.
Click to expand...
Click to collapse
You're welcome. It is what I did every month.
Use thanks button if I helped you! [emoji16]
Inviato dal mio Nexus 6P utilizzando Tapatalk

Things I've discovered that might be useful for people reaching this discussion through a search:
1) Contrary to what the guide linked in previous posts here states, there's no userdata.img file in the factory download. I have angler-opr5.170623.007-factory-b4c75d12.zip and the included image-angler-opr5.170623.007.zip file does not contain userdata.img. This is not so important, considering that you do NOT want to flash that file. But still, if you read the guide and wonder what's wrong, the answer is nothing wrong. I completed the process without any problem.
2) If you follow the guide you'll lose custom recovery (you flash recovery.img after all) and root. I used adb and fastboot to reinstall TWRP (downloaded the latest from here: https://eu.dl.twrp.me/angler/) by using:
adb reboot bootloader
and then once in the bootloader (which must be unlocked):
fastboot flash recovery C:\angler\twrp-3.1.1-0-angler.img
After the custom recovery has been flashed you want to restart the device directly in recovery, otherwise it gets overwritten at first boot (you do that by keeping VOL+ and POWER pressed).
3) After flashing back Magisk, and having Magisk Manager already installed, I found all the modules I had installed were there, root permissions were kept, etc. It's quite likely normal and expected. But, for somebody going through the process for the first time, it was a nice surprise.
I write all this not because it's something new or special... I realize that I might have gathered the relevant information first by searching more thoroughly and being a little bit more brave. But I'm always scared to do something irreparable, so... my findings above are simply a way for me to give something back to the community.
Cheers!

I've found that flashfire from chainfire to be the easiest (not that adb and fastboot are difficult) way to update month to month. I'd still recommend being familiar with adb and fastboot. Having the current factory image on a pc and your device is a good idea as well.
Flashfire
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433

ffejy462 said:
I've found that flashfire from chainfire to be the easiest (not that adb and fastboot are difficult) way to update month to month. I'd still recommend being familiar with adb and fastboot. Having the current factory image on a pc and your device is a good idea as well.
Flashfire
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
Yup, I use flashfire along with 4core boot image fix for bootlooping devices.
It is an absolute delight to be able to flash inbuilt ota without downloading 1gb of stuff just for a security patch.

About GCam and May OTA Update

Yesterday i bougth my MI A1 and it's a really amazing device, i just want to install the gcam but i don't know if for the May Update the gcam doesn't install, I am using a tool from here in XDA thah allow to install it without root but it just wiped my phone and doesn't install the cam, any sugestion? Should I install it with root?
Sorry for my bad english

Are you able to read and do just a little research that doesn't take as much as 5 minutes? There is something written in big red letters right at the top of that thread, you should read it before making new thread. Flash ROM with April Security patch, install Gcam and update to May Security patch.
Don't get me wrong, I don't mean to offend you, but at least do some research before posting a question that is answered million times in last few days, especially in that thread where you found tool for Gcam without root.

MaCls98 said:
Yesterday i bougth my MI A1 and it's a really amazing device, i just want to install the gcam but i don't know if for the May Update the gcam doesn't install, I am using a tool from here in XDA thah allow to install it without root but it just wiped my phone and doesn't install the cam, any sugestion? Should I install it with root?
Sorry for my bad english
Click to expand...
Click to collapse
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
TOOL

sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
TOOL
Click to expand...
Click to collapse
hello just opened that download that application and is the same procedure?

TheMartinexX said:
hello just opened that download that application and is the same procedure?
Click to expand...
Click to collapse
First select 0-Install drivers (if not already done).
If you have a locked bootloader:
Select 1 (Phone will reboot to fastboot mode).
Then 2 (If your bootloader is locked) Phone will be rebooted.
Then 3 (phone will boot temporary TWRP mounting system read-only).
When TWRP has booted select option 4: Phone will be rebooted.
Done.
You will have Camera2 Api enabled and bootloader unlocked (OTAs will work fine)
Unlocked bootloader:
If you have already unlocked the bootloader you can choose option 3 (boot TWRP) with phone connected with USB debug ON (no fastboot).
When TWRP has booted select option 4.
Done
WARNING:
Use option 5 (relock bootloader) ONLY IF you are on April firmware (or older) AND you have an unmodified system.

sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
TOOL
Click to expand...
Click to collapse
Thanks men! It works really great, it was little tricky with the language but nothing than google translate doesn't fix, just one question, with that recovery can i install magisk and the OTAs will still working? Great job with this, thanks

MaCls98 said:
Thanks men! It works really great, it was little tricky with the language but nothing than google translate doesn't fix, just one question, with that recovery can i install magisk and the OTAs will still working? Great job with this, thanks
Click to expand...
Click to collapse
Sorry, I linked ita version...
ENG version
https://1drv.ms/u/s!AnNVEh3KeCSVj9dKhn2Zpx-DRI0Esw
You can install Magisk with that booted recovery but you will have to uninstall it before install OTAs.
Don't mount system read-write and don't alter system files or OTAs will fail.

sipollo said:
First select 0-Install drivers (if not already done).
If you have a locked bootloader:
Select 1 (Phone will reboot to fastboot mode).
Then 2 (If your bootloader is locked) Phone will be rebooted.
Then 3 (phone will boot temporary TWRP mounting system read-only).
When TWRP has booted select option 4: Phone will be rebooted.
Done.
You will have Camera2 Api enabled and bootloader unlocked (OTAs will work fine)
Unlocked bootloader:
If you have already unlocked the bootloader you can choose option 3 (boot TWRP) with phone connected with USB debug ON (no fastboot).
When TWRP has booted select option 4.
Done
WARNING:
Use option 5 (relock bootloader) ONLY IF you are on April firmware (or older) AND you have an unmodified system.
Click to expand...
Click to collapse
Doing these steps would install the gcam or the tool does not come the apk

TheMartinexX said:
Doing these steps would install the gcam or the tool does not come the apk
Click to expand...
Click to collapse
It enables camera2 API, then you can install the apk you want.
Here you can find (almost) all versions.
https://www.celsoazevedo.com/files/android/google-camera/

sipollo said:
It enables camera2 API, then you can install the apk you want.
Here you can find (almost) all versions.
https://www.celsoazevedo.com/files/android/google-camera/
Click to expand...
Click to collapse
what would be the best version for xiaomi mi a1 any recommendation?

TheMartinexX said:
what would be the best version for xiaomi mi a1 any recommendation?
Click to expand...
Click to collapse
https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.5.apk

HPRG said:
https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.5.apk
Click to expand...
Click to collapse
One last question I do not have to do option 5 or I have to use it if or if

TheMartinexX said:
One last question I do not have to do option 5 or I have to use it if or if
Click to expand...
Click to collapse
Ad I said you can relock bootloader only if you haven't already installed May update and you haven't modified system partition.

Relocked bootloader
After installing gcam can we relock the bootloader???
Will it wipe data after may security patch???

TheMartinexX said:
what would be the best version for xiaomi mi a1 any recommendation?
Click to expand...
Click to collapse
for me >>> https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.7.apk

farzeenzack said:
After installing gcam can we relock the bootloader???
Will it wipe data after may security patch???
Click to expand...
Click to collapse
If you relock bootloader data will be wiped after May update.
You can:
downgrade to April (or older) firmware, enable API, relock THEN do OTAs
or
enable API and leave unlocked bootloader (OTA will work)

Question regarding may seruity patch
sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
So I have read that if i try to install GCam with May security patch, it would wipe away my data. Does this happen through this method?
Click to expand...
Click to collapse

Mruthyu said:
sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
So I have read that if i try to install GCam with May security patch, it would wipe away my data. Does this happen through this method?
Click to expand...
Click to collapse
If you have a locked bootloader you can't enable Camera2Api without losing data.
If it's already unlocked you can use my tool to enable Camera2Api without locking the bootloader.
Click to expand...
Click to collapse

Please guys I need your help, have been on April security patch for awhile now and have received May security patch but it's not installing. I went on YouTube and found out that if I'm too install may security patch through miflash tool by flashing the ROM I won't be able to install gcam. So i did factory reset on my April security patch, installed gcam through the gcam tool and then tried to update it again, but it's still giving me the same error. So I then downloaded the full April security patch so I could flash it through miflash tool,but I noticed when I open the app on my PC and connect my phone through fastboot it connects, but when I click flash the app says "success" so quick and it force closes, my phone remains on fastboot,nothing happens. Please guys I don't know what to do anymore. Need your help.

chuckychux said:
Please guys I need your help, have been on April security patch for awhile now and have received May security patch but it's not installing. I went on YouTube and found out that if I'm too install may security patch through miflash tool by flashing the ROM I won't be able to install gcam. So i did factory reset on my April security patch, installed gcam through the gcam tool and then tried to update it again, but it's still giving me the same error. So I then downloaded the full April security patch so I could flash it through miflash tool,but I noticed when I open the app on my PC and connect my phone through fastboot it connects, but when I click flash the app says "success" so quick and it force closes, my phone remains on fastboot,nothing happens. Please guys I don't know what to do anymore. Need your help.
Click to expand...
Click to collapse
Probably you have wrong/corrupted adb drivers.
Try reinstalling them or use another version.

OTA Update for Rooted/Bootloader Unlocked

Hey all, just wanted to try and combine the bits and pieces of the "how to update OTA for rooted/BL unlocked" phones into one place as a quick run down for myself (and others who might have the same question) for the OTA:
Grab OTA update manually
Uninstall Edge Sense Mod from Magisk
Plug in phone into PC
adb reboot recovery
adb fastboot flash "stock boot.img"
adb sideload "OTA file name"
Reboot to bootloader using the volume and power button
adb fastboot flash "patched image to inactive slot (no idea how yet, sorry! Will add command)"
Reboot phone
Go back into Magisk and install manager for root
Re-install Edge Sense Mod within Magisk
*Optional*Re-apply Magisk Hide
Please let me know if there's any steps I'm missing or how it could be made easier for others to understand and if there's credit(s) missing (10+ hr shift and running on strong tea only 11 hr shift arguing with doctors to actually provide care instead of leeching insurance, and insurance to pay the damn medical claims instead of baton passing them to patients).
Disclaimer:
I'm no developer, just a common user that wants to make it a bit more convenient for other Pixel 3a owners to OTA update while rooted/BL unlocked. If it didn't work, or you encountered error(s), let me know and I can link them in so others can learn.
Disclaimer 2:
The above step(s) is assuming you've used pbanj's method for getting Magisk. Apparently I should add this as there's the "conventional" and "unconventional" method for Magisk. Had no idea since there was no guide available informing people otherwise at the time of making this step-by-step guide.
Credits:
pbanj for Pixel 3a root and Magisk images saving a MASSIVE some time, and its thread for the above steps.
googlephoneFKLenAsh for details of what I was missing in my initial steps.
sic0048 for making the root confusion apparent, and making a modified boot image method (the pbanj Magisk) here and his guide for rooting here.

Wdenton said:
Hey all, just wanted to try and combine the bits and pieces of the "how to update OTA for rooted/BL unlocked" phones into one place as a quick run down for myself (and others who might have the same question) for the OTA:
Grab OTA update manually
Uninstall Edge Sense Mod from Magisk
Plug in phone into PC
adb reboot recovery
adb sideload "OTA file name"
Reboot to bootloader using the volume and power button
fastboot flash "patched image"
Reboot phone
Go back into Magisk and install manager for root
Re-install Edge Sense Mod within Magisk
*Optional*Re-apply Magisk Hide
Please let me know if there's any steps I'm missing or how it could be made easier for others to understand and if there's credit(s) missing (10+ hr shift and running on strong tea only).
Disclaimer:
I'm no developer, just a common user that wants to make it a bit more convenient for other Pixel 3a owners to OTA update while rooted/BL unlocked.
Credits:
pbanj for Pixel 3a root and Magisk images saving a MASSIVE amount of time, and its thread for the above steps.
Click to expand...
Click to collapse
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".

I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?

I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.

sic0048 said:
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
Click to expand...
Click to collapse
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.

alliance1975 said:
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
Click to expand...
Click to collapse
Great point, difference between downloading a patched boot image vs patching yourself is not clear as to how it affects the OTA update...

alliance1975 said:
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
Click to expand...
Click to collapse
I totally understand the confusion......
If you use normal Magisk installation method where you let Magisk modify the stock boot.img file, then the OTA update method that I described above should work. Because you let Magisk modify the stock boot image, it will be able to use the stock image in the first step - Magisk: Click “Uninstall” → “restore images” → NO REBOOT
If you used the "modified boot image" method, you were able to skip the step where you let Magisk modify the stock boot image. This saves time initially, but it comes back to bit you during an OTA update because Magisk is unable to use the stock image to uninstall itself. You are correct that the normal Magisk "How to Take an OTA Update" instructions will fail if you used the modified boot image to gain root initially.
I guess I didn't realize that you had used the "modified boot image" method. Here is my recommendation to all those that have used the modified boot image method - start over.........
- use the Magisk manager app to Uninstall Magisk using the "Complete Uninstall" method.
- Pull the stock boot.img from the applicable factory image (whatever OS version/update you are currently on). Downloads are available here https://developers.google.com/android/images
- Using your computer, flash the stock boot.img file by using the command "fastboot flash boot boot.img"
- Reinstall Magisk using the "normal" method....
- Put the stock boot.img file on your phone's root SD card location
- Use the Magisk manager app to modify the stock boot.img
- move the magisk_modified boot image to your computer
- flash the magisk_modified boot image to the boot partition using the command "fastboot flash boot <patched_boot.img file name>"
- reboot
Then follow the instructions I gave for the normal OTA update process listed a couple posts above.
---------- Post added at 02:25 PM ---------- Previous post was at 02:14 PM ----------
duh1 said:
Unless I'm misunderstanding the process, seems like Magisk is missing a checkbox to backup the unpatched boot image prior to creating a patched image, for future OTA updates...
Click to expand...
Click to collapse
Magisk isn't missing this option, it's just that the method suggested by pbanj in this thread bypasses the normal method. It's not an issue with Magisk, it's an issue with the root method being suggested.
What I really need to do is create another "How to Root" thread and list the normal and recommended method. The confusion comes from people coming to this site and reading pbanj's thread and thinking that is the correct way to root. It is not the correct way to root.

alliance1975 said:
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ----------
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
Click to expand...
Click to collapse
Normally you would flash the stock boot image to the active slot to unroot the phone prior to installing the OTA.
Confused as to why flashing stock boot is no longer necessary. If this works as stated, it would appear the OTA is no longer patching the phone's boot and system partitions as had been done in the past. So perhaps the OTA now installs full boot and system images?

duh1 said:
Normally you would flash the stock boot image to the active slot to unroot the phone prior to installing the OTA.
Confused as to why flashing stock boot is no longer necessary. If this works as stated, it would appear the OTA is no longer patching the phone's boot and system partitions as had been done in the past. So perhaps the OTA now installs full boot and system images.
If that is indeed the case we should be able to just install the OTA normally through the system update button without having to uninstall Magisk and get rid of root first. Then as the Magisk tutorial states cancel the reboot go into the Magisk manager and reroot. Has anyone tried this on a rooted phone?
Click to expand...
Click to collapse
I had read, but have not confirmed myself, that the OTA images did include the boot and system img. However I just checked and the factory image for the June update on Bonito is 1.6gb while the "full OTA" image is only 1.1gb. So the two images are not identical. It's not like you saving a bunch of time by not uninstalling Magisk first and I don't think I would skip this simple step with the hope it would work. I'll continue to follow the recommended procedure that the Magisk developer has come up with and I would recommend to others that they do the same.

sic0048 said:
I had read, but have not confirmed myself, that the OTA images did include the boot and system img. However I just checked and the factory image for the June update on Bonito is 1.6gb while the "full OTA" image is only 1.1gb. So the two images are not identical. It's not like you saving a bunch of time by not uninstalling Magisk first and I don't think I would skip this simple step with the hope it would work. I'll continue to follow the recommended procedure that the Magisk developer has come up with and I would recommend to others that they do the same.
Click to expand...
Click to collapse
It's smaller as the OTA only contains the partitions that have changed such as system and boot. The other partitions are probably cloned over from the active slot to the inactive slot.
As I mentioned previously, the Magisk tutorial does not account for not having a backup of the stock boot image when you download the patched boot, so to remove boot prior to installing the OTA, you must manually flash the stock boot.

googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
alliance1975 said:
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
Click to expand...
Click to collapse
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Then in step 7, flash patched boot.img to slot b (after ota, the active changes to slot b. If there is new ota in the future, just use getvar to find out the active slot)

sic0048 said:
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
Click to expand...
Click to collapse
sic0048 said:
I totally understand the confusion......
If you use normal Magisk installation method where you let Magisk modify the stock boot.img file, then the OTA update method that I described above should work. Because you let Magisk modify the stock boot image, it will be able to use the stock image in the first step - Magisk: Click “Uninstall” → “restore images” → NO REBOOT
If you used the "modified boot image" method, you were able to skip the step where you let Magisk modify the stock boot image. This saves time initially, but it comes back to bit you during an OTA update because Magisk is unable to use the stock image to uninstall itself. You are correct that the normal Magisk "How to Take an OTA Update" instructions will fail if you used the modified boot image to gain root initially.
I guess I didn't realize that you had used the "modified boot image" method. Here is my recommendation to all those that have used the modified boot image method - start over.........
- use the Magisk manager app to Uninstall Magisk using the "Complete Uninstall" method.
- Pull the stock boot.img from the applicable factory image (whatever OS version/update you are currently on). Downloads are available here https://developers.google.com/android/images
- Using your computer, flash the stock boot.img file by using the command "fastboot flash boot boot.img"
- Reinstall Magisk using the "normal" method....
- Put the stock boot.img file on your phone's root SD card location
- Use the Magisk manager app to modify the stock boot.img
- move the magisk_modified boot image to your computer
- flash the magisk_modified boot image to the boot partition using the command "fastboot flash boot <patched_boot.img file name>"
- reboot
Then follow the instructions I gave for the normal OTA update process listed a couple posts above.
---------- Post added at 02:25 PM ---------- Previous post was at 02:14 PM ----------
Magisk isn't missing this option, it's just that the method suggested by pbanj in this thread bypasses the normal method. It's not an issue with Magisk, it's an issue with the root method being suggested.
What I really need to do is create another "How to Root" thread and list the normal and recommended method. The confusion comes from people coming to this site and reading pbanj's thread and thinking that is the correct way to root. It is not the correct way to root.
Click to expand...
Click to collapse
googlephoneFKLenAsh said:
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Then in step 7, flash patched boot.img to slot b (after ota, the active changes to slot b. If there is new ota in the future, just use getvar to find out the active slot)
Click to expand...
Click to collapse
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
Thanks to all, was not expecting this much reply in this short amount of time, at all.
I made this step by step guide because no dedicated thread really was readily accessible in one place. Hopefully this inspires others to make guides.

googlephoneFKLenAsh said:
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Click to expand...
Click to collapse
How else could the phone have been rooted besides flashing a patched boot image on a device without a custom recovery, such that Magisk on his device knows where to find the stock boot image?

duh1 said:
How else could the phone have been rooted besides flashing a patched boot image on a device without a custom recovery, such that Magisk on his device knows where to find the stock boot image?
Click to expand...
Click to collapse
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.

googlephoneFKLenAsh said:
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
Click to expand...
Click to collapse
Difference is downloading the patched image vs patching it yourself. Wasn't clear how that created the issue. Well written, thx for pointing it out.
So if anyone patches the new version boot image before uninstalling Magisk, they'll get an error. Likewise, patching the current boot image in the manager will allow the uninstall to work correctly...

googlephoneFKLenAsh said:
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
Click to expand...
Click to collapse
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.

pbanj said:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
Click to expand...
Click to collapse
Sorry for the health issues. Take care and get well soon.
Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.
If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.

ritchea said:
Sorry for the health issues. Take care and get well soon.
Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.
If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.
Click to expand...
Click to collapse
ya pretty much. every time the phone updates the active slot changes. I'm currently updating my root thread so everything is clearer and in one place.

pbanj said:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
Click to expand...
Click to collapse
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?

duh1 said:
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?
Click to expand...
Click to collapse
correct. i had no issue with it, and i friend is the one who told me about it as that's how she installs her updates even though she could use the magisk method