Database Develop

recovery will not stick on 6.0.1

I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks

jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.

all i have now is stock recovery. whats the best way to manually install twrp

go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.

Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse

Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk

when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.

arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp

jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.

This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.

scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.

simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help

jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine

I need help 😞

i flash stock MOB31E rom using official TWRP 3.0.2.2 after i flash it my boot recovery was gone and only appeared is broken android with exclamation point

Can your device boot? maybe it replaced twrp with stock recovery, try flashing twrp again
Good Luck?

avie14 said:
i flash stock MOB31E rom using official TWRP 3.0.2.2 after i flash it my boot recovery was gone and only appeared is broken android with exclamation point
Click to expand...
Click to collapse
Probably your device's recovery replaced by stock recovery.
Inorder to prevent this , you shouldve uncheck mount system read-only.
Anyhow, now you can still root your phone and install a custom recovery with a tool!
if you wish I'll link it here!
BTW, your device isn't booting now?

Pls its ok to me but i dont have a pc

sachin n said:
Probably your device's recovery replaced by stock recovery.
Inorder to prevent this , you shouldve uncheck mount system read-only.
Anyhow, now you can still root your phone and install a custom recovery with a tool!
if you wish I'll link it here!
BTW, your device isn't booting now?
Click to expand...
Click to collapse
Its still booting no stock recovery and custom recovery

How to disable stock recovery

Hey guys,
I`m using x526. The other day I rooted the device with TWRP and flashed AOSP extended. But now I can`t seem to enter into TWRP. When I try to enter the recovery mode using the hard keys, it loads into the stock recovery. Even when using the option to boot into recovery in the AOSP extended restart option, it still boots into the stock recovery.So is there any way to remove/disable the stock recovery.Or even any other methods to enter TWRP?. I flashed the latest twrp (3.1.1) from the official site via ADB. Also AEX was pre-rooted with magisk

zeeka# said:
Hey guys,
I`m using x526. The other day I rooted the device with TWRP and flashed AOSP extended. But now I can`t seem to enter into TWRP. When I try to enter the recovery mode using the hard keys, it loads into the stock recovery. Even when using the option to boot into recovery in the AOSP extended restart option, it still boots into the stock recovery.So is there any way to remove/disable the stock recovery.Or even any other methods to enter TWRP?. I flashed the latest twrp (3.1.1) from the official site via ADB. Also AEX was pre-rooted with magisk
Click to expand...
Click to collapse
Flash twrp once again.. Use the code fastboot flash recovery whateverthenameis.img

zeeka# said:
Hey guys,
I`m using x526. The other day I rooted the device with TWRP and flashed AOSP extended. But now I can`t seem to enter into TWRP. When I try to enter the recovery mode using the hard keys, it loads into the stock recovery. Even when using the option to boot into recovery in the AOSP extended restart option, it still boots into the stock recovery.So is there any way to remove/disable the stock recovery.Or even any other methods to enter TWRP?. I flashed the latest twrp (3.1.1) from the official site via ADB. Also AEX was pre-rooted with magisk
Click to expand...
Click to collapse
If your phone is rooted you can flash TWRP from app TWRP found in playstore

sydtek said:
Flash twrp once again.. Use the code fastboot flash recovery whateverthenameis.img
Click to expand...
Click to collapse
Twrp is already there, I can't just access it due to stock recovery. I flashed twrp twice and can enter the twrp just after flashing. If I exit twrp I can't access it again unless I reflash it

zeeka# said:
Twrp is already there, I can't just access it due to stock recovery. I flashed twrp twice and can enter the twrp just after flashing. If I exit twrp I can't access it again unless I reflash it
Click to expand...
Click to collapse
When you flash a new recovery the old one will be replaced. If you used the code fastboot boot recovery recovery.img the phone just boots to the recovery and not flash it. So please use the code fastboot flash recovery recovery.img.

sydtek said:
When you flash a new recovery the old one will be replaced. If you used the code fastboot boot recovery recovery.img the phone just boots to the recovery and not flash it. So please use the code fastboot flash recovery recovery.img.
Click to expand...
Click to collapse
I'll try

Thank you guys, everything is fine now. I flashed twrp using the official app . Sorry for asking stupid question

zeeka# said:
Thank you guys, everything is fine now. I flashed twrp using the official app . Sorry for asking stupid question
Click to expand...
Click to collapse
:highfive:

unable to flash twrp.

I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.

shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later

Sudhanshu030299 said:
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later
Click to expand...
Click to collapse
Are you will it be successful L?

shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Click to expand...
Click to collapse
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?

shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Sent from my OnePlus3T using XDA Labs

shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img

BillGoss said:
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Click to expand...
Click to collapse
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk? I am confused what to do?

redpoint73 said:
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img
Click to expand...
Click to collapse
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.

shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
Temporarily boot into twrp with fastboot, copy zip files to memory using MTP (it will activate automatically, when TWRP boots successfully you can see the phone on your PC), flash them in TWRP, profit.
^ assuming you have already made a backup

Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Click to expand...
Click to collapse
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?

shree alwaz said:
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?
Click to expand...
Click to collapse
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Click to expand...
Click to collapse
Boot password is nothing but forced encryption on?

You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Sent from my OnePlus3T using XDA Labs

shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
As you've now figured out, your mistake is rebooting. As I already described, rebooting before flashing root (Magisk or SuperSU) or patched boot image (or custom ROM w. patched boot image) will by definition wipe TWRP. This is normal and expected.
Fastboot flash TWRP. Then in bootloader screen, select recovery, and it should go to TWRP. Then flash one of the above described files to make TWRP "stick".
---------- Post added at 09:25 AM ---------- Previous post was at 09:20 AM ----------
shree alwaz said:
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk?
Click to expand...
Click to collapse
No, that is not what he is saying. Yes, you need TWRP to flash a custom kernel or Magisk. Fastboot flash TWRP, then immediately select "recovery" from the bootloader menu and do not reboot the phone.
You don't need custom kernel/Magisk to flash TWRP (that would be a cart before the horse type situation, as you somewhat figured out). But doing so, makes TWRP "stick" and not get wiped (replaced with stock recovery).
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
shree alwaz said:
Boot password is nothing but forced encryption on?
Click to expand...
Click to collapse
Encryption is not the same as forced encryption.
Forced encryption means that if your phone is decrypted, flashing an update will (I believe) "force" it back to being encrypted. For folks that want to stay decrypted, they will want to disable forced encryption. If your phone is encrypted, it doesn't matter if you have forced encryption or not. It will stay encrypyted in either case.

BillGoss said:
You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Click to expand...
Click to collapse
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.

shree alwaz said:
Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
Encryption is always useful if paired with bootup password - in case of theft no one can read your data.
You will be asked for password, if you explicitly set it up in OS.
And what option do you mean?

shree alwaz said:
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
Click to expand...
Click to collapse
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
shree alwaz said:
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?

redpoint73 said:
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?
Click to expand...
Click to collapse
Thanks you clarification. After reading your explanation even I got the same question 3 and 4.

help to lock bootloader

My OnePlus 3T is currently rooted unlocked bootloader nd on TWRP recovery
So now I want to move my phone to stock condition pls help

Simplest way would be to just run the Qualcomm restore tool/unbrick tool. This will restore everything back to unrooted and locked bootloader as you've requested.
Skickat från min ONEPLUS A3003 via Tapatalk

You could do a factory reset in TWRP and flash the latest OnePlus stock image from https://downloads.oneplus.com
Then reboot, which will restore the stock recovery and re-encrypt your phone (if you've decrypted it). Check that this is so in Settings>Security. Also check that recovery is now stock.
Then you can relock the bootloader from fastboot.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
You could do a factory reset in TWRP and flash the latest OnePlus stock image from https://downloads.oneplus.com
Then reboot, which will restore the stock recovery and re-encrypt your phone (if you've decrypted it). Check that this is so in Settings>Security. Also check that recovery is now stock.
Then you can relock the bootloader from fastboot.
Click to expand...
Click to collapse
Pls gimme link to download stock recovery
nd do I need to encrypt or decrypt phone before locking bootloader ?
I heard that flashing stock ROM from twrp recovery will bring stock recovery to the phone is it true?

BillGoss said:
You could do a factory reset in TWRP and flash the latest OnePlus stock image from https://downloads.oneplus.com
Then reboot, which will restore the stock recovery and re-encrypt your phone (if you've decrypted it). Check that this is so in Settings>Security. Also check that recovery is now stock.
Then you can relock the bootloader from fastboot.
Click to expand...
Click to collapse
Pls gimme link to download stock recovery
nd do I need to encrypt or decrypt phone before locking bootloader ?
I heard that flashing stock ROM from twrp recovery will bring stock recovery to the phone is it true?

mannulko said:
Pls gimme link to download stock recovery
nd do I need to encrypt or decrypt phone before locking bootloader ?
I heard that flashing stock ROM from twrp recovery will bring stock recovery to the phone is it true?
Click to expand...
Click to collapse
Link to downloading recovery is there along with link to download the ROM, just check the website.
If you flash stock ROM through TWRP, your phone will be automatically encrypted and stock recovery will be installed after reboot from TWRP.

przemcio510 said:
Link to downloading recovery is there along with link to download the ROM, just check the website.
If you flash stock ROM through TWRP, your phone will be automatically encrypted and stock recovery will be installed after reboot from TWRP.
Click to expand...
Click to collapse
So what do you suggest should I flash stock recovery or I should install full ROM from twrp nd automatically get stock recovery.

mannulko said:
So what do you suggest should I flash stock recovery or I should install full ROM from twrp nd automatically get stock recovery.
Click to expand...
Click to collapse
If you flash the full stock image in TWRP and nothing else, then when you reboot the stock recovery will replace TWRP. This is the way I would do it.
You can verify this by booting back into recovery after the phone has booted up on OOS. Note that if your phone was decrypted, then the first boot up will take a while to re-encrypt the phone.
I would not relock the bootloader until you've verified that the phone is encrypted and the stock recovery is installed.
Sent from my OnePlus3T using XDA Labs