Database Users

[Q] Help flashing ROMs

Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.

sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
I'm stuck too, how did you flash the stock file?

sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2587296
here for 12b recoveries
and search through the thread for edited roms

I have the TMO verison but plenty of my friend have successfully flashed trwp using flashify also what kernals and roms are you trying to flash over? are you clean or dirty flashing?

try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago

zekurosu said:
try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago
Click to expand...
Click to collapse
Can you post a link to the latest twrp recovery for tmo? ive been looking but couldn't find one.

I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...

ceredics said:
I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
Click to expand...
Click to collapse
Have you tried to flash back to the 12A and not use the 12b

tbishop91 said:
Have you tried to flash back to the 12A and not use the 12b
Click to expand...
Click to collapse
Nope, the one i was using i believe was the 10. Also, when it boots it was secure boot unsuccessful. Im seeing a handful of people stuck with this with no solution thread.

You used ioroot did you open a cmd prompt and push a loki file using a adb command

tbishop91 said:
You used ioroot did you open a cmd prompt and push a loki file using a adb command
Click to expand...
Click to collapse
I used ioroot res i did. But no i dont recall EVER using adb....

ceredics said:
I used ioroot res i did. But no i dont recall EVER using adb....
Click to expand...
Click to collapse
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused

tbishop91 said:
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused
Click to expand...
Click to collapse
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.

ceredics said:
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.
Click to expand...
Click to collapse
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370

tbishop91 said:
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370
Click to expand...
Click to collapse
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now

ceredics said:
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now
Click to expand...
Click to collapse
have you tried to use twrp instead of clockwork, I think that's what cwm stands for make sure whatever you do you double check that method does not harm your device.

It didnt work... Fckkkkk. So to make it clearer
VZW
Lg G2
Rooted with io
Rom when rooted was stock latest ota
currently stuck in CWM with nothing to boot into because of consistent abortion then status 7.

can you sideload aboot.img from adb

Id need step by step instructions on how to sideload something because ive never messed with adb. It seems if i adb a different recovery or a specific file it may start to work. Can i sideload TWRP?

let me consult my know it all friend lol

N910F Stuck in boot sequence - HELP PLEASE!!!

Hi Guys, I came on here last week seeking advice as my Note4 has always been seriously laggy and slow. I tried resetting to factory etc however still the same. So the advice I got was to root and try another rom.
I successfully rooted my 910F device (confirmed by running test root app). I then downloaded a new rom to try out. In the instructions it suggested that I should be running the respective versions of Bootloader and Modem - which I downloaded from the links in the instructions. I installed both Bootloader and Modem via Odin successfully however now the device just loops in a boot up sequence. I copied the ROM files to the SD card however the when I try and load the rom from there it says that 'Update from external storage is disabled'.
I've downloaded a few other ROMs however they are zip files and I am guessing not designed to work with odin??
Hoping that there is a headache free way of recovering this.
Apologies in advance. I am an newbie with this stuff, really appreciate any help!!!!!
Thanks,
OB

You need custom recovery use TWRP.
Rom needs to be a zip DO NOT UNZIP IT.
From recovery flash the zip.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
Sorry for the short comment but I just typed a big guide and this useless ****ty xda app said I don't have permission to post. Message to xda fix ur **** useless developers. This app has been buggy as hell since day one.

Zionator said:
You need custom recovery use TWRP.
Rom needs to be a zip DO NOT UNZIP IT.
From recovery flash the zip.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
Sorry for the short comment but I just typed a big guide and this useless ****ty xda app said I don't have permission to post. Message to xda fix ur **** useless developers. This app has been buggy as hell since day one.
Click to expand...
Click to collapse
Really appreciate the reply.
The modem and Bootloader have already been loaded. So to be totally clear, I need to download an app called TWRP and load the ROM file (ZIP) with that right?
Thanks a bunch, really appreciate the help.
Bests,
OB

To add, the phone is not booting up (stuck in the boot up sequence) so I cant download and install any apps on it? Is TWRP a PC app?
Thanks,
OB

Nope, TWRP is not an App. It's a Recovery. You will find it in the development section. It's an img which you flash via ODIN. After that, you shut down the Phone and reboot via holding vol up + Home + Power. It will Boot you into the TWRP Recovery. from there you can then Install the Roms. They are provided as Zip. Don't Unzip them. Just select the zip to be installed via TWRP.

Honor 7 ROM problem

Hello guys,
long time i had no problem (even that i couldnt make photos , use google play and had 4GB max space). I accidentaly erased system and through posts here i got custom chinese ROM with twrp(PLK-C00B618_Kangvip;EMUI 3.1; android 5.1.1). But now i want to make photos and use google play soo...any solutions ? I hope yes.
Thank you guys atleast for viewing this post.

You need to flash Google Framework and Google Play app, because most Chinese ROM removed those. You can flash a gapps package from Opengapps.
ARM-Android 5.1-Micro/Pico/Nano should do.

First get back to stock and then flash a custom ROM, this might help. Steps are below, follow them.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.

Thank you, just got time to try it so ill inform in 2h(slow download speed).

OMG!! man, tell me your adress so i can visit you and hug you, i tried so many times according to lot of posts and it havent worked. I gave up once, but now i finally, god bless, finally back to stock firmware, yaaaaaaaaaaaaaaay. Iam so happy, nothing can breaky my happiness for today.

Dont know why but i have only 4GB allocated storage(before accidental system remove i had 10). Can you help me with that too ?

Pixell9 said:
Dont know why but i have only 4GB allocated storage(before accidental system remove i had 10). Can you help me with that too ?
Click to expand...
Click to collapse
Did you flashed the UPDATE.APP again with three button reset method??

DigiGoon said:
Did you flashed the UPDATE.APP again with three button reset method??
Click to expand...
Click to collapse
Yes I did.

Pixell9 said:
Yes I did.
Click to expand...
Click to collapse
Those who followed this method didn't have this kinda problem.
Try to flash a custom ROM and see if anything changes.
---------- Post added at 01:02 AM ---------- Previous post was at 12:21 AM ----------
To flash custom ROM, you need to unlock your bootloader first, then flash TWRP recovery, and download any custom ROM of your choice and flash it via TWRP recovery.

DigiGoon said:
Those who followed this method didn't have this kinda problem.
Try to flash a custom ROM and see if anything changes.
---------- Post added at 01:02 AM ---------- Previous post was at 12:21 AM ----------
To flash custom ROM, you need to unlock your bootloader first, then flash TWRP recovery, and download any custom ROM of your choice and flash it via TWRP recovery.
Click to expand...
Click to collapse
Sorry that i havent responded for some time, but i dont have now much time, ill try it tommorow. Thx.

Pixell9 said:
Dont know why but i have only 4GB allocated storage(before accidental system remove i had 10). Can you help me with that too ?
Click to expand...
Click to collapse
Usually because partition is corrupted.
Reflash again boot, recovery, cust and system img files.
If still persists go down to B100 ROM and use its img files.

DigiGoon said:
Those who followed this method didn't have this kinda problem.
Try to flash a custom ROM and see if anything changes.
---------- Post added at 01:02 AM ---------- Previous post was at 12:21 AM ----------
To flash custom ROM, you need to unlock your bootloader first, then flash TWRP recovery, and download any custom ROM of your choice and flash it via TWRP recovery.
Click to expand...
Click to collapse
zinko_pt said:
Usually because partition is corrupted.
Reflash again boot, recovery, cust and system img files.
If still persists go down to B100 ROM and use its img files.
Click to expand...
Click to collapse
Thank you guys both, i just tried to manual flash update.app again through EMUi and it worked ^^.

Pixell9 said:
Thank you guys both, i just tried to manual flash update.app again through EMUi and it worked ^^.
Click to expand...
Click to collapse
No problem. Factory reset is also very important.

Pixell9 said:
Thank you guys both, i just tried to manual flash update.app again through EMUi and it worked ^^.
Click to expand...
Click to collapse
Glad it worked for you.

No OS, can't mount vendor/product/

Hi there
Today I bought a pair of Bluetooth earphones and noticed that Bluetooth wasn't working anymore, so I decided to factory reset my vanilla ROM (EMUI 5.0).
That didn't work out and eventually I had to unlock the bootloader, flash a custom recovery (so far I tried both TWRP and Revolution) and a custom ROM.
However, something must have gone seriously bad because I now can't mount /product and /version.
When I try to install a rom (EliteROM by HassanMirza), it also tells me it couldn't load /cust and /data as well.
- cust: invalid argument
- data: invalid argument
- product: no such file or directory
- version: no such file or directory
I also tried moving an update.app version to my internal memory but doing that through gives me an error saying there's not enough space.
Pretty much at a loss here, no idea what to do. Anyone got an idea? Even willing to pay to get this fixed.

Can you access fastboot?

maartenw8 said:
Can you access fastboot?
Click to expand...
Click to collapse
I have access to fastboot and the Revolution recovery.
(thanks a lot in advance fellow Belgian )

LordInfernu said:
I have access to fastboot and the Revolution recovery.
(thanks a lot in advance fellow Belgian )
Click to expand...
Click to collapse
Great!! Use huawei update extractor (HERE) to extract all the .img files from the UPDATE.APP and try to flash them via fastboot.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
and so on
This should help you and your phone should boot.
------
Belgium ftw . Are you from the flanders?

maartenw8 said:
Great!! Use huawei update extractor (HERE) to extract all the .img files from the UPDATE.APP and try to flash them via fastboot.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
and so on
This should help you and your phone should boot.
------
Belgium ftw . Are you from the flanders?
Click to expand...
Click to collapse
I tried that yesterday, but flashing the system.img file gave an error, something like "sparse flash write failed".
Would you have any idea what the correct build would be for a Belgian VNS-L31 which was previously on EMUI 5.0.
I got my phone with a subscription from Proximus and after the update, it just completely broke (the software I mean).
I'm from Bruges! And you?

LordInfernu said:
I tried that yesterday, but flashing the system.img file gave an error, something like "sparse flash write failed".
Would you have any idea what the correct build would be for a Belgian VNS-L31 which was previously on EMUI 5.0.
I got my phone with a subscription from Proximus and after the update, it just completely broke (the software I mean).
I'm from Bruges! And you?
Click to expand...
Click to collapse
Hmmm.. Can you flash stock recovery and dload the firmware?
The build depends on your Cxxx. What is it? I also got my phone from proximus! Assuming you didn't debrand your phone, it should be C02, but maybe you did debrand. However, I would suggest trying to dload the rollback package because you were on nougat. You can find it here. Follow the instructions in the PDF file of the zip package. But first, extract the recovery from UPDATE.APP
---------------
Nice! I'm from Genk

maartenw8 said:
Hmmm.. Can you flash stock recovery and dload the firmware?
The build depends on your Cxxx. What is it? I also got my phone from proximus! Assuming you didn't debrand your phone, it should be C02, but maybe you did debrand. However, I would suggest trying to dload the rollback package because you were on nougat. You can find it here. Follow the instructions in the PDF file of the zip package. But first, extract the recovery from UPDATE.APP
---------------
Nice! I'm from Genk
Click to expand...
Click to collapse
Hmm so I've currently moved the update.app file to my external sd (if I'm correct this is the /external_sd/ folder - had to do this through adb because I don't have a card reader atm) and then tried to update by pressing on/off button, volume down, volume up. However, this just brings me back to my Revolution recovery. Should I flash the stock recovery first?

LordInfernu said:
Hmm so I've currently moved the update.app file to my external sd (if I'm correct this is the /external_sd/ folder - had to do this through adb because I don't have a card reader atm) and then tried to update by pressing on/off button, volume down, volume up. However, this just brings me back to my Revolution recovery. Should I flash the stock recovery first?
Click to expand...
Click to collapse
Yes flash stock recovery first! That way you'll have dload back

maartenw8 said:
Yes flash stock recovery first! That way you'll have dload back
Click to expand...
Click to collapse
Oh ok never gotten that far, great! So right now I did that but obviously I can't boot now.
I believe I now have to flash the full OS? Would it be ok if I flash TWRP or Revolution back just to use ADB and transfer the other update.app file, flash back to stock recovery and then use DLOAD method again?
Thanks so far for all the help, very much appreciated!

LordInfernu said:
Oh ok never gotten that far, great! So right now I did that but obviously I can't boot now.
I believe I now have to flash the full OS? Would it be ok if I flash TWRP or Revolution back just to use ADB and transfer the other update.app file, flash back to stock recovery and then use DLOAD method again?
Thanks so far for all the help, very much appreciated!
Click to expand...
Click to collapse
So you flashed the stock ROM and then you dload the Huawei Rollback package? Because if you flashed the rollback package you should be able to boot...
-----
Let me pm you to find a more easy way to communicate

maartenw8 said:
So you flashed the stock ROM and then you dload the Huawei Rollback package? Because if you flashed the rollback package you should be able to boot...
-----
Let me pm you to find a more easy way to communicate
Click to expand...
Click to collapse
Ah no I probably made a mistake. I'd definitely appreciate that!

LordInfernu said:
Ah no I probably made a mistake. I'd definitely appreciate that!
Click to expand...
Click to collapse
I sent you a message

i'm having the same problem here (also from Belgium)
anyone willing to guide me through?
thanks

Same problem here, the link to rollback package is invalid. Is there someone kind enough to help us out?

lepraook said:
i'm having the same problem here (also from Belgium)
anyone willing to guide me through?
thanks
Click to expand...
Click to collapse
What recovery are you using?
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
VonHornmeister said:
Same problem here, the link to rollback package is invalid. Is there someone kind enough to help us out?
Click to expand...
Click to collapse
What recovery are you using?

maartenw8 said:
What recovery are you using?
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
What recovery are you using?
Click to expand...
Click to collapse
Twrp
Exact version.have to check
Also after reflashing recovery system boot i can.reboot
I'm on android 6 now with dual.sim instead of single
Had to flash this info to phone to get him.going

lepraook said:
Twrp
Exact version.have to check
Also after reflashing recovery system boot i can.reboot
I'm on android 6 now with dual.sim instead of single
Had to flash this info to phone to get him.going
Click to expand...
Click to collapse
Hi there. I am stuck. Are you willing to help me please?
---------- Post added at 12:55 AM ---------- Previous post was at 12:28 AM ----------
LordInfernu said:
Hi there
Today I bought a pair of Bluetooth earphones and noticed that Bluetooth wasn't working anymore, so I decided to factory reset my vanilla ROM (EMUI 5.0).
That didn't work out and eventually I had to unlock the bootloader, flash a custom recovery (so far I tried both TWRP and Revolution) and a custom ROM.
However, something must have gone seriously bad because I now can't mount /product and /version.
When I try to install a rom (EliteROM by HassanMirza), it also tells me it couldn't load /cust and /data as well.
- cust: invalid argument
- data: invalid argument
- product: no such file or directory
- version: no such file or directory
I also tried moving an update.app version to my internal memory but doing that through gives me an error saying there's not enough space.
Pretty much at a loss here, no idea what to do. Anyone got an idea? Even willing to pay to get this fixed.
Click to expand...
Click to collapse
hey dude. I have a similar problem and I just can't solve it. Did you ever get your phone working again?

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

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

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

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

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

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

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

what if we have flashed a kernel?

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

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

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

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

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

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

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

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

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

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

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

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

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