Develop Bugs

[HELP GUIDE] - Can't flash TWRP on Oxygen OS 3.2.1

Today I have faced a strange situation, I installed TWRP (after unlocking the bootloader) on my OP3 as soon as I received the device then I flashed custom ROM by @Grarak http://forum.xda-developers.com/oneplus-3/development/rom-unofficial-cyanogenmod-13-t3399089.
After using for some days I decided to give Oxygen OS another try, so I wiped the cache,data,system and Flashed full OTA provided by @namanbhalla https://forums.oneplus.net/threads/...ficial-oxygen-os-roms-and-ota-updates.450783/
Every thing went smooth but after starting up I wasn't able to goto twrp, for some strange reason twrp was automatically replaced with stock recovery. OK, I decided to reflash twrp, but bang! after so many flashing I wasn't able to boot into twrp, still there was stock recovery.
Solution:
1) fastboot oem unlock (re run even if it says already unlocked)
2) fastboot flash recovery twrp-3.0.2-0-oneplus3.img
now TWRP is installed.
I not Android Developer and cant guarantee above will work and wont harm your device. Try at your own risk.

that is all not needed, i have had this happen to me multiple times reflashing Stock and Stock recovery replaces TWRP, all u have to do is boot up to fastboot mode and flash TWRP, do not reboot, use Power + Vol + and when the Unlocked bootloader screen comes up press the VOL key and click recovery and TWRP is back. no need to do the unlock bootloader again, unless u unchecked it, just make sure it is checked when flashing the Stock rom again or u can just use flashify if u rooted stock before the recovery got replaced somehow, i have even had this happen on FreedomOS 3.2.1

Flash ROM - i'm going crazy here!

Hi,
i have a Helium 128G and got some problems with the radio. Currently i was on 8.1.5 following the guide
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
and i also officially unlocked the bootloader after this.
So i thought - to flash a new radio - it would be fine to just flash the 8.1.9 over the updater method. Unfortunately the phone rebooted in TWRP and flashed something. After this the reboot took >10 Minutes so i rebooted into TWRP and found the internal storage is encrypted now. So all data lost. Great!
Nevertheless i tried to flash 8.1.9 via Mi Flash. This worked and the phone booted but after i flashed TWRP it won't boot anymore. What is this? Is it even possible to run 8.1.9 rooted with twrp?
Thanks for your suggestions, i'm really pissed at the moment
EDIT: My TWRP Backup with 8.1.5 worked and now i have the radio from 8.1.9 and the rom 8.1.5. Nevertheless i would like to have 8.1.9 rooted with twrp

Hi! I've also experience your problem, did your phone entered recovery mode after flashing TWRP? if not try flashing the 8.1.2 ROM through EDL (power+vol up+vol down) then after letting the first boot finish flash TWRP. Hope this help

I'm not sure but at one point i saw the xiaomi recovery picture!? Now it works with my 8.1.5 backup again but is it really that heavy to just install a current version when on twrp and root!? i'm officially unlocked for that.

Unable to Install TWRP Recovery

Hello everyone, I have LG G3 D851 T-Mobile.
I was on 5.0.1 and wanted to install custom ROM and for this I needed to install custom recovery first so I used Flashify to install TWRP (twrp-3.1.0-0-d851.img) , installation works fine it says installation complete, but when I restart the phone it starts bootloop.
So I restored my phone back to stock (4.4.2), rooted and again repeat flashify process this time again the same issue of bootloop.
Can Anyone here help me in this matter.
Thanks

Ha ha ha. If you had searched/looked here on xda you would know twrp 3.1 does not work only bootloops. Also twrp 3.0.2 is no good either. You should use the unofficial builds. Also a restore is not needed just pull battery for a minute and then it will boot back to the installed rom.

Goes back to stock recovery

Hi Guys !
Im on Open beta 35 (OP3). I Unclocked the bootloader and flashed the Official TWRP recovery right after that I could able go to TWRP but after I restart the Phone again it goes back to stock recovery. Can someone let me know the what went wrong?
Do I need to flash the blu spark's TWRP?

werty733 said:
Hi Guys !
Im on Open beta 35 (OP3). I Unclocked the bootloader and flashed the Official TWRP recovery right after that I could able go to TWRP but after I restart the Phone again it goes back to stock recovery. Can someone let me know the what went wrong?
Do I need to flash the blu spark's TWRP?
Click to expand...
Click to collapse
You have to flash Magisk, if you are on Oreo, immediately after flashing TWRP before booting into system.
If you are on previous android versions, you can flash SuperSU or Magisk.

[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP

[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:

I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.

Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?