Develop Bugs

[Q] Root With OTA?

Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk

ahmadsraj said:
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete or change any files and apps that is build-in on system.
Even you want to delete apps made from telecom operators IS NOT PERMITTED!
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.

missile0407 said:
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete any files and apps that is build-in on system.
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
Click to expand...
Click to collapse
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.

craig0r said:
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
Click to expand...
Click to collapse
Hello,
I have the same question as the OP. Everything seems to make sense when following this post. My question is even though I will just boot into recovery without ever flashing the recovery am I really able to disconnect my phone from the computer? It seems like the recovery files are actually on the computer so I would need to keep the phone connected while I install the supersu.zip
Thank you for the help

I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/

exad said:
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
Click to expand...
Click to collapse
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?

SouthBayBruin said:
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
Click to expand...
Click to collapse
There's no reason you *can't* leave it plugged in, but yeah, when you run the fastboot command it loads the custom recovery into RAM, and the connection to your computer is doing nothing for you. I give my personal guarantee that it's 100% safe to disconnect after recovery's loaded. But again, if leaving it plugged in makes you more comfortable, it won't hurt.

I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip

zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.

SouthBayBruin said:
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
Click to expand...
Click to collapse
http://download.chainfire.eu/396/SuperSU

zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.

KaranNavani said:
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
Click to expand...
Click to collapse
Dude, do the research yourself. I don't know how many more times this has to be said. There's nothing special you have to do, just apply the OTA update when prompted

How to go from prerooted to stock rom ?

Hi I m really new to this so excuse me ...
i got many updates by flashing with fastboot prerooted system.img i was on 2.19.40.18 prerooted but i would like to go to a stock no rooted to be able to apply OTA now
I tried an erase of my phone, but i came back to prerooted ...
I tried to install tethered TWRP and to install the.zip from asus download page but it was stuck on updating IFWI .... ( 2.19.40.20 zip file from asus )
What can i do ?
Plz help me

You need to go into the SuperSU settings, scroll to near the bottom and choose "Full unroot."

I did all on this post : http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
I did unroot, flashed all 4 line before but i think my recovery is corrupted, it end in error with the green guy instantly and flashin via fastboot recovery.img isnt doing anybetter ...
I m really stuck ..

i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...

shinjy87 said:
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
Click to expand...
Click to collapse
Protocol fault is because you don't use latest ADB. Google it.

i successfully did this but now adb is stuck on serving 13 % and on the phone : verifying update package , it stopped like 15 min ago ...

Here's what I did to go from pre-rooted system back to stock.
1. Download the official latest image from Asus http://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
2. Rename the zip to MOFD_SDUPDATE.zip
3. Unroot via SU
4. Uninstall Xposed and modules if you have them busybox etc. (uninstall.bat for xposed it's easy)
5. Copy MOFD_SDUPDATE.zip to an SD card and insert into phone or copy to internal memory
6. Boot into recovery by holding power and volume up
7. If you get dead android press power button and volume up button and release.
8. Auto installs new image
I went this route after unrooting via SU and uninstalling xposed framework still wouldn't let me run OTA updates for some reason. I imagine I did something along the road or removed a system app or something. It wouldn't let me manually sideload or update and would error out halfway through the process. I cleared fastboot cache and even reset the device to no avail. I was on 2.19.40.18. I installed the 2.19.40.20 image then the OTA update to .22 yesterday.
If I root the device again which is likely I'll use method 3 and the rootkit tool.

i will try your way, installing the 22 now.
But i dont remember in recovery the auto installs new image ?

error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?

shinjy87 said:
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
Click to expand...
Click to collapse
I installed the 2.19.40.20 full system image (1.1GB) from Asus yesterday. They didn't have the full image for .22 up but they do now. I was on the .18 pre-rooted image. When you hold power and volume up choose recovery and it should install the MOFD_SDUPDATE.zip automatically (mine did). I had issues trying to manually update the phone from .18 to .20 and .22 via ADB (the patches are like 30MB). It would start the update with the android robot then fail about halfway.
Download the correct system image for your device. The new update is available as a full image now so download the .22 image from Asus and then rename it to MOFD_SDUPDATE.zip. Copy it to an SD card and insert it back into your phone. Phone is powered off so hold power and volume up to get the recovery screen. It will say Normal in a big green arrow. Change it to recovery via the volume buttons then hit power button and it should find and automatically install the MOFD_SDUPDATE.zip image.
FYI this is on a ZE551ML 4GB/64GB US WW firmware based phone. I imagine the other models are the same or very similar.
I wish I could articulate this better. Hopefully someone more knowledgeable comes along and lends a hand.

Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?

wlbwlb said:
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
Click to expand...
Click to collapse
Yes.

Induced_Apathy said:
Yes.
Click to expand...
Click to collapse
Thank, another question. will it wipe all my data?

wlbwlb said:
Thank, another question. will it wipe all my data?
Click to expand...
Click to collapse
Flashing the entire system image you want to wipe everything anyways in this case. If you mean using the one click rootkit (method 3) to root then no it will not.

Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.

madmike23 said:
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
Click to expand...
Click to collapse
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.

Harfainx said:
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Click to expand...
Click to collapse
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.

madmike23 said:
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
Click to expand...
Click to collapse
What does the recovery log say?

Harfainx said:
What does the recovery log say?
Click to expand...
Click to collapse
Only thing that caught my attention is: Unable to open '/sdcard/MOFD_SDUPDATE.zip': No such file or directory.
This was last attempt unrooted and this morning's OTA

update problem

Hi, I have bought used here in Italy a op3, when turn on in the display I can see a message about the bootloader unlock, and so I think that the previously owner have unlocked the unit. Now I have a problem with the update, I have tried with ota and with USB but the phone stop the update and show me the message installation failed, then I can only reboot. How I can relock the Bootloader? Thanks in advance for your help.

before you re-lock the bootloader you should make sure that you are running the stock oxygenOS rom and receovery, see below:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/

thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?

alchemist76 said:
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
Click to expand...
Click to collapse
you might be running OOS 3.2.2 stock but still have a custom recovery - boot into recovery first just to confirm that you have the stock recovery as well

still if you have a custom recovery, it's easier to get update. Just download the full rom and flash it with TWRP (I don't think there is another custom recovery), it won't wipe the data. Even if the previous owner did a slight modification on OOS 3.2.2, it will overwrite it.
updates can be downloaded many days before the OTA appear on the phone.

Ok I think that I have a custom recovery, TWRP working with non rooted phone? I have checked and my phone not have root. Please can you explain how I can update through TWRP?

if you want to stay unlocked and use TWRP that's fine, but note that you will need to MANUALLY UPDATE every time if you're on the stock OOS ROM.
if you are not comfortable with this, follow the instructions on the link i sent you to get back to full stock with stock recovery as well, so updates OTA work correctly.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/

2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.

alchemist76 said:
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
Click to expand...
Click to collapse
sorry, im not really sure what you mean, but if you're following the instructions on that post step by step and verifying what you get it should work.
You need to successfully flash the full zip to get the stock rom+recovery on there

ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?

alchemist76 said:
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
Click to expand...
Click to collapse
the bootloader being locked or unlocked is irrelevant - your issue is your non-stock recovery.
the full Oxygen OS zip includes the stock recovery from OnePlus, which OTA updates are programmed to use to automatically update your phone.
since you have TWRP recovery instead, you'll need to download and manually flash OxygenOS
download the full ZIP for 3.2.4 from this thread and flash it via TWRP recovery:
http://forum.xda-developers.com/oneplus-3/how-to/oxygen-os-3-2-4-released-t3437911

Phone keeps asking me to install an OTA update I already installed

So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.

Cyber Akuma said:
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Click to expand...
Click to collapse
If you have twrp installed it wont update the firmware only software. You need to flash firmware seperatly with fastboot.

So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?

Cyber Akuma said:
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Click to expand...
Click to collapse
Correct.:good:

Can somebody please explain how to flash the firmware with fastboot?
So I have to flash the OTA with TWRP, afterwards I have to extract the firmware file out of the OTA.zip and flash it with fastboot. But which commands are necessary in fastboot?

To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.

kjjejones42 said:
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
Click to expand...
Click to collapse
Thats not true. You flash in ruu mode when S - ON. If your are S - Off you can do it from download mode. I think you are a little confused with that thread. Those firmwares are modified and for S -Off phones only.

yldlj said:
Thats not true. You flash in ruu mode. If soff you can do it from download mode.
Click to expand...
Click to collapse
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?

kjjejones42 said:
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
Click to expand...
Click to collapse
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.

yldlj said:
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
Click to expand...
Click to collapse
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery

kjjejones42 said:
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
Click to expand...
Click to collapse
Correct. Also unmodified boot. But if your flashing unmodified system image, boot and stock recovery you may aswell just boot to android and take the ota.

help neededOneplus3 DECRYPTION UNSUCCESSFULL - RESET PHONE black screen, recoverymode

Hi,
Problem starting oneplus 3, let me explain.
1) purchased oneplus3, 4 months ago.
2) Rooted,updated oxygen 3.2.8 with TWRP recovery3021 and super SU 2.74-2
3) updated oxygen4.00 with twrp32128 and super SU 2.79SR2 everything was fine.
4) Received OTA update through VPN for oxygen 4.0.1 (30mb), installed but unable start instead it was always going into twrp mode.
5) i changed twrp recovery back to 3021 and install stock oxygen 3.2.8,was working fine.
6) Now i wanted to UNROOT the device and back to stock so that i can get OTA Oxygen 4 and 4.0.1.
7) i followed steps below,
a) downloaded oxygen 3.2.1 and stock recovery.img
a) fastbootloader, and connect device.
b) fastboot devices
c) fastboot fastboot flash recovery recovery.img
d) fastboot oem lock - when i used this command and accept YES, screen got black and no further instruction for ADBsideload.
8) i used to restart the device in recovery but black screen, fastboot loader working.
FASTBOOT MODE
PRODUCT NAME - ....
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - .....
SECURE BOOT - enabled
DEVICE STATE - locked
9) and if i start the device in normal it asked for screen pattern lock but my existing unlock pattern doesnt work.
10) by using all the chance for screen pattern unlock it showed DECRYPTION UNSUCCESSFULL, clicked on RESET PHONE but again screen black in recovery mode.
11) NOW if i start my device it again shows DECRYPTION UNSUCCESSFULL and asking for RESET PHONE......
What to do now.....
regards,
Zahir

use the mega unbrick guide method 2, always work

Don't panic mate!

mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
Thanks mirko8054, I will let you know soon......

mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir

samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:

mirko8054 said:
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
Click to expand...
Click to collapse
thanks a lot, I will do accordingly.

samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
just wanted to highlight the things you did that caused the issue
1- flashing the stock rom through twrp, it's possible specially with the latest TWR0-11 but not advisable, you better always flash stock recovery and then sideload rom (full rom not update) and then fast boot TWRP back and reflash root... any other method always causes issues...
2- the 30mg updates do not work on a rooted device
3- unrooting without immediately sideloading rom will always cause the black screen and loop to recovery, it's not required to unroot unless you want to go back to full stock experience...
4- this the biggest problem you made, you relocked the devices bootloader, you also did it while the device has a lot of issues (some mentioned above) so the device bricked instantly, if you are planning on unlocking the device again ...NEVER NEVER relock the device again , there's no need to do that , all you need to do to go back to a full stock experience is to wipe everything in TWRP , flash stock recovery then wipe everything again from there, then sideload full rom (latest stable version) , then for good majors in the new rom recovery wipe everything agian and boot to system and from system do a factory reset. then recharge your device to 100% and re encrypt it if it's not...after that you're 100% on a full stock exerience and will receive ota and it'll work... and at that state only (without root or TWRP) you can relock the bootloader (which is gain not necessary at all, there's no benefit to it)