Database Users

[RECOVERY][M86][UNOFFICIAL] TWRP 3.0 for Meizu PRO5

DISCLAIMER
I'm not responsible for any damage, bootloop, bricked or broken handsets.
Notice
The recovery can't be flashed to the handset with locked bootloader! Unlock it first!
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom and stock (with some remarks) ROMs to your device, repair broken file systems, and root your device.
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Update 29.03.2016
It's alive! First experimental working build published at internal 4pda Russian board.
Download
TWRP 3.0 M86 fastboot flashable image
TWRP 3.0 M86 flashable zip
Stock Recovery flashable zip
Unlocked BL flashable zip
Install
With BL unlocked reboot into fastboot mode and flash:
Code:
fastboot flash recovery TWRP_3.0_m86.img
Cautions
Before flashing stock rom with TWRP replace bootloader file with unlocked one inside rom archive!!!!
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)

JUST IN CASE this is an April fools.... I'll wait ?

Great mate, u've stolen my idea in the end, right ?!
Gooooood work, thank u very much ! Testing wip :highfive:
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
Nein, first step doesn't work
Flashing unlocked BL through stock recovery, I get always the same result :
FIRMWARE CORRUPT
Click to expand...
Click to collapse

faust93 said:
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Click to expand...
Click to collapse
*Working fine
PYCON said:
Nein, first step doesn't work
Click to expand...
Click to collapse
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...

toms157 said:
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
Click to expand...
Click to collapse
Ahahah yes yes but the purpose of BL_UNLOCKED.ZIP is to unlock bootloader. But in order to flash it correctly... we've to have the bootloader already unlocked
Damn it, it's really stupid, right ?

PYCON said:
Damn it, it's really stupid, right ?
Click to expand...
Click to collapse
Filename could lead to confusion, sure... It's needed for this :
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)"
Click to expand...
Click to collapse
Meanning flash 3 files from custom recovery without rebooting
Anyway this is not a catch-22, leaked beta from tutorial is the entry point

Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...

showofdeth said:
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
Click to expand...
Click to collapse
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked

naboleo said:
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
Click to expand...
Click to collapse
Oh man that's great to hear! Thanks. Bought myself a laptop specifically to get my PRO 5 all TWRP'd up.
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?

showofdeth said:
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
Click to expand...
Click to collapse
Never had troubles to downgrade to leaked beta

naboleo said:
Never had troubles to downgrade to leaked beta
Click to expand...
Click to collapse
Brilliant. Thanks a lot. Can't wait to hear people's experiences with this.

mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot

That TWRP works perfectly for me, backup nandroid, restore it, flash ZIP rom and ZIP other ( Xposed, etc ), no problem at all :highfive:
Good job !!! Great, thx !!!

Thank you so much for this!!! could i ask you how you managed to create a recovery for the pro5?

Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
I assume youare still on 5.6.1.19: Thats an error with this version.... put the updatefile manually (in the PC) on the external sd and flash via TWRP... you should later update your modified Pro 5 to 5.1.3.0, the error ist gone then...

Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
Copy UPDATE.ZIP from PC to phone BUT CONNECTING THE PHONE WHEN IT'S OPENED TWRP
MTP mode works great, even u'r on 5.6.1.19 :highfive:

Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!

PYCON said:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
Click to expand...
Click to collapse
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:

cedric3 said:
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
Click to expand...
Click to collapse
Uh I didn't know that a new version was released... Maybe, I could be. I download it again and try... Thx man ! :highfive:

The last version can't read the micro sd.

[STOCK][N] Images and zips for 20a

Short on tons of time, but here you go for your downloading pleasure...
First off, you have the OTA zip from LGE, it only works on stock recovery...
Download From Google
Android File Host Mirror(s)
Working on update zip for twrp users currently.. Stay tuned

Question. If I'm using TWRP, is it possible to just flash the stock recovery with one of those .IMG flashing apps to regain stock recovery and flash the update? Or would I just be better off waiting for a TWRP flashable zip?

carnivalrejectq said:
Question. If I'm using TWRP, is it possible to just flash the stock recovery with one of those .IMG flashing apps to regain stock recovery and flash the update? Or would I just be better off waiting for a TWRP flashable zip?
Click to expand...
Click to collapse
Wait for the TWRP zip if you want to keep recovery. Flashing stock recovery will probably lock you out without an updated TOT as the fuses likely have been changed

simonsickle said:
Wait for the TWRP zip if you want to keep recovery. Flashing stock recovery will probably lock you out without an updated TOT as the fuses likely have been changed
Click to expand...
Click to collapse
I see.....I just have no access to a PC anymore is all lol. You're the first person to have responded to me about this so thanks for that haha.

simonsickle said:
Short on tons of time, but here you go for your downloading pleasure...
First off, you have the OTA zip from LGE, it only works on stock recovery...
Download From Google
Android File Host Mirror(s)
Working on update zip for twrp users currently.. Stay tuned
Click to expand...
Click to collapse
will this work with ¨LGUP¨ ? if any one has the .kdz or tot please share i will need that to recovery my phone it got brick load only firmware update all the time i cant boot or load to the stock recovery firmware update or boot load.
thanks you.

Any headway on the flashable zip file

mrchaos429 said:
Any headway on the flashable zip file
Click to expand...
Click to collapse
yeah he pmed it to everyone else. it's been done for hours but you personally have to wait.

First it was a simple question second I wasn't trying to rush third no need to be a **** fourth stay on topic and fifth quit being a ****

mrchaos429 said:
First it was a simple question second I wasn't trying to rush third no need to be a **** fourth stay on topic and fifth quit being a ****
Click to expand...
Click to collapse
Lol dude do you read at all look at the op he said he's working on it. The golden rule of xda is never ask for updates. Your the one being a **** by annoying someone who's trying to make a flashable zip for you. If you can't wait then make it yourself this a development forum.

Wuuuusaaba...

ronald11 said:
will this work with ¨LGUP¨ ? if any one has the .kdz or tot please share i will need that to recovery my phone it got brick load only firmware update all the time i cant boot or load to the stock recovery firmware update or boot load.
thanks you.
Click to expand...
Click to collapse
if have problem with the boot here is the .kdz steps..
http://forum.xda-developers.com/tmo...-zips-imgs-t3511294/post69896212#post69896212

carnivalrejectq said:
I see.....I just have no access to a PC anymore is all lol. You're the first person to have responded to me about this so thanks for that haha.
Click to expand...
Click to collapse
Go to the Google Play store.....get an app called Flashify...... Select Recovery Image, select/download TWRP 3.0.2.1 (latest version) and it will flash the recovery to your previously rooted phone in a few seconds. Enjoy. :laugh:

Project deleted.

Projector permanently suspended.

reserved for updated links.

Sands207 said:
I just made a ROM for Boost/Sprint SM-J327P J3 Emerge that should be flashable in TWRP. I have 2 versions, One that should be Odin flashable and the other being a zip that should be easily flashed in TWRP once we work out the kinks ... I worked primarily on LG's before this and Samsungs long before that. Anyway these are the features I've added so far:
Deodexed
Pre-rooted
Deknoxed
Busybox included
init enabled
Csc debloated (not exactly sure what to remove for bloat but I need feedback on what can be kept etc...
zip aligned on boot
xposed
links coming later today....
lemme know if I missed anything!!
I need testers! Chime in if you would like to help, we have a way to unbrick easily via Odin
*Update* 7.11.17 Flashed it on my phone but may have gotten steps CONFUSED? Installs perfectly... No loops just either takes forever to load initially or hangs on my device. I got sick of waiting but I'm curious if others know, when we flash a new pre rooted stock rom do we need to wipe data, then supersu & dm verity patch? Will removing csc stuff brick this device?
*FLASH AT YOUR OWN RISK!* I am not responsible for ANY damage to your device. ALWAYS MAKE A BACKUP FIRST, I can link to Odin and firmware files if needed til we get this right.
Flash rom
Mount DATA
Format data in TWRP this will wipe internal storage
Reboot recovery
Flash Supersu
Flash dm verity patch and *possibly* Xposed?
Credit goes to @[email protected]@[email protected] for TWRP Recovery and Root https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Wait for device to boot first boot may take awhile!!
Initial Alpha Release: https://drive.google.com/file/d/0Bz99NuhE3Xwmd2c4d3ZDV3dPcTA/view?usp=drivesdk
Signed Version
https://drive.google.com/file/d/0Bz99NuhE3XwmWXZHdWxCalBNcWM/view?usp=drivesdk
Please Report back with failure, success or bugs or feature requests.
Click to expand...
Click to collapse
Ill download and get back to you with sucess/failure or w.e i might encounter that can be tweakes.
Regards
Doctur

I'm downloading it now, I'll flash it as soon as I'm done. I just wiped my J327P after having root, no more knox, and Xposed running smooth. It accidentally had a pocket party with my keys and some of the seedier Xposed modules one night and then after that, it was never the same. I think I pretty got no more USB besides Odin. TWRP can't even use it.
But hey, listen Sands. This better not be some bull****. Don't you ever **** me Sands. You hear me? Don't you ever **** me. :good:

IdealInShade said:
I'm downloading it now, I'll flash it as soon as I'm done. I just wiped my J327P after having root, no more knox, and Xposed running smooth. It accidentally had a pocket party with my keys and some of the seedier Xposed modules one night and then after that, it was never the same. I think I pretty got no more USB besides Odin. TWRP can't even use it.
But hey, listen Sands. This better not be some bull****. Don't you ever **** me Sands. You hear me? Don't you ever **** me. :good:
Click to expand...
Click to collapse
ANYTHING

Sands207 said:
I just made a ROM for Boost/Sprint SM-J327P J3 Emerge that should be flashable in TWRP. I have 2 versions, One that should be Odin flashable and the other being a zip that should be easily flashed in TWRP once we work out the kinks ... I worked primarily on LG's before this and Samsungs long before that. Anyway these are the features I've added so far:
Deodexed
Pre-rooted
Deknoxed
Busybox included
init enabled
Csc debloated (not exactly sure what to remove for bloat but I need feedback on what can be kept etc...
zip aligned on boot
xposed
links coming later today....
lemme know if I missed anything!!
I need testers! Chime in if you would like to help, we have a way to unbrick easily via Odin
*Update* 7.11.17 Flashed it on my phone but may have gotten steps CONFUSED? Installs perfectly... No loops just either takes forever to load initially or hangs on my device. I got sick of waiting but I'm curious if others know, when we flash a new pre rooted stock rom do we need to wipe data, then supersu & dm verity patch? Will removing csc stuff brick this device?
*FLASH AT YOUR OWN RISK!* I am not responsible for ANY damage to your device. ALWAYS MAKE A BACKUP FIRST, I can link to Odin and firmware files if needed til we get this right.
Flash rom
Mount DATA
Format data in TWRP this will wipe internal storage
Reboot recovery
Flash Supersu
Flash dm verity patch and *possibly* Xposed?
Credit goes to @[email protected]@[email protected] for TWRP Recovery and Root https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Wait for device to boot first boot may take awhile!!
Initial Alpha Release: https://drive.google.com/file/d/0Bz99NuhE3Xwmd2c4d3ZDV3dPcTA/view?usp=drivesdk
Signed Version
https://drive.google.com/file/d/0Bz99NuhE3XwmWXZHdWxCalBNcWM/view?usp=drivesdk
Please Report back with failure, success or bugs or feature requests.
Click to expand...
Click to collapse
DM Verity is better if you flash it before instead of after root method. Instead of flashing SuperSU use magisk because a lot of apps are starting to reject rooted devices using SuperSU. After flashing magisk, wipe cache and dalvik

SonderTech said:
DM Verity is better if you flash it before instead of after root method. Instead of flashing SuperSU use magisk because a lot of apps are starting to reject rooted devices using SuperSU. After flashing magisk, wipe cache and dalvik
Click to expand...
Click to collapse
Should i make a new build with magisk incorporated? I've never used it before but my lady uses snapchat and will likely need this to root hers as well. i didn't update mine but she did so has the second to newest ota build on hers, i can use her system dump for an update. Can you link me to the recommended version for ours? xposed seems ok too but seems limited. thanks for your input
Sent from my SM-J327P using Tapatalk

Sands207 said:
Should i make a new build with magisk incorporated? I've never used it before but my lady uses snapchat and will likely need this to root hers as well. i didn't update mine but she did so has the second to newest ota build on hers, i can use her system dump for an update. Can you link me to the recommended version for ours? xposed seems ok too but seems limited. thanks for your input
Click to expand...
Click to collapse
She definitely will need magisk then, they are all the way on 13.2 . I could try to help you through the installation if you would like.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3

SonderTech said:
She definitely will need magisk then, they are all the way on 13.2 . I could try to help you through the installation if you would like.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3
Click to expand...
Click to collapse
Definitely, ill be back at my pc tonight or tomorrow i really appreciate it. hoping to make the next one smoother magisk sounds pretty interesting, do we have a safe list of what we can remove? or what needs to be flashed w the rom?

Sands207 said:
Definitely, ill be back at my pc tonight or tomorrow i really appreciate it. hoping to make the next one smoother magisk sounds pretty interesting, do we have a safe list of what we can remove? or what needs to be flashed w the rom?
Click to expand...
Click to collapse
Knox files are good to remove. Samsung device manager and samsung+ is a no go. That's all I know at the moment. Before I forget, if your gonna flash gapps do it before rooting but after DM Verity

SonderTech said:
Knox files
are good to remove. Samsung device manager and samsung+ is a no go. That's all I know at the moment. Before I forget, if your gonna flash gapps do it before rooting but after DM Verity
Click to expand...
Click to collapse
Cool, so from what ive gathered so far im going to make the next rom unrooted but deodexed as as debloated as i possibly can safely and we will flash the newest MM gapps first, then dm verity and a reboot to recovery per the directions, then magisk and finally xposed and clear cache and dalvik at the end... sound about right? I did try flashing magisk on my device as is but it failed because the boot image was already patched and stock was needed instead. Is dm verity absolutely needed or could magisk accomplish in theory what our patch does?

Sands207 said:
Cool, so from what ive gathered so far im going to make the next rom unrooted but deodexed and we will flash the newest MM gapps first, then dm verity and a reboot to recovery per the directions, then magisk and finally xposed and clear cache and dalvik at the end... sound about right? I did try flashing magisk on my device as is but it failed because the boot image was already patched and stock was needed instead. Is dm verity absolutely needed or could magisk accomplish in theory what our patch does?
Click to expand...
Click to collapse
I think it's better to flash Dm Verity and you would do it before you flash gapps because to flash Dm Verity you have to format data so you can mount the data partition

SonderTech said:
I think it's better to flash Dm Verity and you would do it before you flash gapps because to flash Dm Verity you have to format data so you can mount the data partition
Click to expand...
Click to collapse
ok excellent. I appreciate your help ?
Sent from my SM-J327P using Tapatalk

Sands207 said:
ok excellent. I appreciate your help ?
Click to expand...
Click to collapse
No problem, and when your flashing it on your device just flash stock ROM flash twrp recovery and then do the Dev mode and OEM unlock setup and then wipe data once again flash Dm Verity and clear cache and dalvik and then setup your device and then flash magisk and then wipe cache and dalvik once again

SonderTech said:
No problem, and when your flashing it on your device just flash stock ROM flash twrp recovery and then do the Dev mode and OEM unlock setup and then wipe data once again flash Dm Verity and clear cache and dalvik and then setup your device and then flash magisk and then wipe cache and dalvik once again
Click to expand...
Click to collapse
Excellent. I'll update the OP when i post the second build.

Sands207 said:
Excellent. I'll update the OP when i post the second build.
Click to expand...
Click to collapse
Coolio and if you need a boot animation just pm me. I have a couple zips that need converting and resizing.

SonderTech said:
Coolio and if you need a boot animation just pm me. I have a couple zips that need converting and resizing.
Click to expand...
Click to collapse
Awesome, I just finished the second build. My upload speed is insanely slow so it may take all night for me but i did manage to cut the size down considerably ? im sure there will be stuff to remove still but everyone is different. Definitely about a new boot animation tho stock is pretty blah lol

Sands207 said:
Awesome, I just finished the second build. My upload speed is insanely slow so it may take all night for me but i did manage to cut the size down considerably ? im sure there will be stuff to remove still but everyone is different. Definitely about a new boot animation tho stock is pretty blah lol
Click to expand...
Click to collapse
I have a batman sonar animation I got from bhoot.co.uk that I converted to a QMG for our device, just need to upload it to the drive with the rest of them

Alpha 2 released: https://drive.google.com/folderview?id=0Bz99NuhE3XwmWGN5ejBqMDlNUVU
Will update OP in a few to reflect changes ?

Is it going to be possible to port Lineage OS to this device ?

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

Cant seem to flash rom

https://drive.google.com/file/d/0B3W1wsYle4wla29SRjgzSlBfVm8/view?usp=drivesdk
I just got the phone (OnePlus 5). I have rooted it and installed twrp. I couldnt update due to signature verification error. I was told to flash the zip with twrp, and I did. Now it has been running for hours but the bar hasnt moved. Can anyone help me?

PowerOfDerp said:
https://drive.google.com/file/d/0B3W1wsYle4wla29SRjgzSlBfVm8/view?usp=drivesdk
I just got the phone (OnePlus 5). I have rooted it and installed twrp. I couldnt update due to signature verification error. I was told to flash the zip with twrp, and I did. Now it has been running for hours but the bar hasnt moved. Can anyone help me?
Click to expand...
Click to collapse
Did you wipe before you flash?

You need to flash the full ROM zip, not just the OTA zip.

Pwnycorn said:
You need to flash the full ROM zip, not just the OTA zip.
Click to expand...
Click to collapse
Ok, its my first time flashing an ota, so bare with me. I got the file from here. First of all, how do I get out of this state? And if thats not the full ROM, where can I get it?

PowerOfDerp said:
Ok, its my first time flashing an ota, so bare with me. I got the file from here. First of all, how do I get out of this state? And if thats not the full ROM, where can I get it?
Click to expand...
Click to collapse
Well, I've never flashed one either. This is my first OnePlus device.
The link you posted is the official one for downloads and the size of the full ROM I understood is 1.5 - 2GB. So it seems you do have the right file.
You could flash the stock recovery img with TWRP - it can be obtained from the same link - and flash the OTA zip with that.
During the flashing process of the OTA you would've lost TWRP anyway, so it's not a big loss.

Pwnycorn said:
Well, I've never flashed one either. This is my first OnePlus device.
The link you posted is the official one for downloads and the size of the full ROM I understood is 1.5 - 2GB. So it seems you do have the right file.
You could flash the stock recovery img with TWRP - it can be obtained from the same link - and flash the OTA zip with that.
During the flashing process of the OTA you would've lost TWRP anyway, so it's not a big loss.
Click to expand...
Click to collapse
ok, but should i just try and shut down the device?