Cant Flash Recovery or ROM

[dvaibhavd]

I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.

 

[Fap4k]

I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.

Bro wait....!!!
Is this real?
You are using too old recovery(as your ss says 2.8.7)+old boot loader..you need some work on your phone to be able to flash new cm 13/14.1.
Just head over to general thread and find how to upgrade boot loader and install latest twrp.
After that you can flash all latest available ROM.

 

[utkhirodka]

Boot logo Problem

Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.

I was able to flash stock Oxygen Rom .I want to flash CM 14 please help

 

[RichusX]

Same

Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.

I was able to flash stock Oxygen Rom .I want to flash CM 14 please help

Same here with the TZ issues. As for the recovery, the TWRP version 3.0.2-0 is the most latest one that I can flash & boot into successfully. If I flash anything newer than 3.0.0-1 my OPX is stuck on OP logo as well.

 

[amgh]

My phone is stuck at one plus boot logo when i tried to go into recovery mode or tried to start it the oneplus logo popped and goes out again and again and when i tried to flash twrp through fastboot mode it say the device is locked cant change or erase the recovery what should i do please guide me

 

[blackknightavalon]

The only recovery that will flash on mine is 3.0.2-0. I've tried flashing through Fastboot. I've even tried to use the dd command for both 3.0.3-0 official and blu sparkz v41 and it gets stuck at the OnePlus logo.

Phone still boots into OOS just fine and 3.0.2-0 flashes through the old JMZ TWRP app just fine. It's just any other method that doesn't work.

 

[Exodusche]

The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.

 

[blackknightavalon]

The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.

Again, I tried flashing 3.0.3 and it wouldn't stick.

 

[Exodusche]

Again, I tried flashing 3.0.3 and it wouldn't stick.

After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?

 

[blackknightavalon]

After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?

As stated above, all it does is hang at the OnePlus logo.
Also...

fastboot boot drive:\path\to\twrp-3.0.3-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.540s

 

[Exodusche]

As stated above, all it does is hang at the OnePlus logo.

Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.

 

[blackknightavalon]

Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.

2.2.3 flashed successfully. I already know 3.1.4 will work. I'll post again if your plan completely works.

 

[blackknightavalon]

...and I'm still getting the same errors after flashing 3.1.4 through stock recovery. o.0

I'm going to start from the earliest firmware available and flash progressively from there and see if that works.