Unable to Flash Custom Recovery - OP3 Open Beta 30

[anandpandey]

Hi All,

I am facing issues with flashing any custom recovery on my oneplus 3 device running on open beta 30.
Everytime I flash a recovery, it says finished without an error but throw me back to stock recovery, After searching some available option I can across several links and tried following suggestions so far:

1) used "Fastboot boot recovery.img": Error "FAILED (remote: bootimage header fields are invalid)"
Thought the downloaded recovery file is corrupted, downloaded it from official site and other locations, all with same hash value and same problem

2) Searched an option to disable "update cm recovery", unable to location this setting on my device

3) Tried to flash recovery then poweroff and then reboot to recovery using power button and volume down key, did not worked.

recoveries I have tried:
blu_spark TWRP and original TWRP

device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
(bootloader) force_training: false

Anyone faced similar issue or found a way to fix this ?

Note: Device not rooted, bootloader unlocked.

 

[oopstairs]

You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.

 

[Puddi_Puddin]

You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.

Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.

 

[anandpandey]

Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.

Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.

 

[Puddi_Puddin]

Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.

Which recovery are you trying to flash?

 

[anandpandey]

Which recovery are you trying to flash?

recoveries I have tried:
blu_spark TWRP and official TWRP

 

[cmnaka]

Try:
fastboot flash recovery recovery.img

 

[anandpandey]

Try:
fastboot flash recovery recovery.img

Thanks, that was the first thing i tried.

 

[TNSMANI]

Thanks, that was the first thing i tried.

Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?

When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.

 

[anandpandey]

Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?

When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.

The problem with this approach is that I cound never reach to TWRP so to flash SuperSu or Magisk.
Soon after I flash TWRP, the repory enters into a loop.

 

[anandpandey]

Still not able to flash a custom rom, any other suggested options ?

 

[drmuruga]

This is a nonsense answer but can try , Rename to twrp or anything else other than recovery.img ( may be stock confused with same name )

 

[TNSMANI]

Still not able to flash a custom rom, any other suggested options ?

Told you already to flash SuperSu. Don't use TWRP to flash SuperSu. Use adb.

If I were you, I would wipe system, data, Dalvik and cache and flash the ROM first, all using adb. Then boot into the ROM. Then using adb, flash blu_spark's TWRP v 8.61 and immediately thereafter flash SuperSu v 2.79 SR5, again using adb. Then boot into TWRP and then into system.

 

[pcesar.cercal]

I after getting the beta31 I ran out of dash charger and also could not get the recovery oos

so I went back to 5.0.1 and did not go back to giving the cherzer dash. I got now I put the beta 31 and firmware of beta 30