Related
After @Envious_Data and me discovered that there is no real collection for the most up-to-date recoveryimages, for both stock and AOSP based Roms we decided to create this thread in order to change this.
Recoverys:
CWM Recovery 6.0.5.1
PhilZ Touch Recovery 6.59.0 (CWM Version 6.0.5.1)
TWRP 2.8.3.0 (2.8.1.0 recommend as 2.8.3.0 is not starting on some Roms)
Installation
Download the recovery images in the Download section reboot your phone into fastboot mode and execute the command
Code:
fastboot flash recovery *name of the recoveryimage you downloaded*.img
in fastboot.
When you want to flash it from your phone, navigate into the folder where you downloaded the recoveryimage and execute the command:
Code:
dd if="*name of the recoveryimage you downloaded*.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
as root in Terminal Emulator.
If you are lazy you can also use my App, M5-Settings. It automatically downloads the most up-to-date recoveryimage to your externel SD Card and flashes the recoveryimage to your FOTAKernel Partition.
Download:
CWM Recovery
PhilZ Touch Recovery
TWRP
M5-Settings
Sources:
CWM Recovery
PhilZ Touch Recovery
TWRP (download currently linking to the reupload prebuilt 2.8.1.0 official recoveryimage, never builds will be compiled from source)
M5-Settings​
XDA:DevDB Information
Recovery Collection, Tool/Utility for the Sony Xperia Z2
Contributors
Myself5, Envious_Data
Version Information
Status: Stable
Created 2015-01-10
Last Updated 2015-01-12
Reserved
Ding
Reserve post incase i want to post anything
Hi Both,
I want to get the M5Kernal and flash it on a CM12 that has cyanogenmod recovery
So which Recovery do you suggest and which version which will make this process an easy one.
I tried to flash TWRP (forgot the version) but it would show everything pixelated with horizontal lines making nothing readable nor functional.
Edit: I have flashed Philz, flashed M5KernelV2 and guess what, phone stuck at "Android is upgrading.. Starting apps" for the past 3 minutes.
I'll give it some time and update
Edit: So it wouldn't boot and I had to wipe it fully and tried again, all good.
Best of all, the recovery actually "sticks"
Regards
Hmm, you should probably mention that you need to unlock your bootloader first? unless I'm mistaken..
behelit said:
Hmm, you should probably mention that you need to unlock your bootloader first? unless I'm mistaken..
Click to expand...
Click to collapse
Not exactly
You cant use fastboot on xperias if the bootloader is locked
I dont think fotakernel/recovery is a part of the bootloader (likely hence why we cant boot right into recovery)
You do need a custom kernel to use recovery
But to install it i think is a different case, im not experianced all too much with locked bootloaders so this info is based off of a conversation between a bunch of devs
can I use this one on a ROOTED STOCK ROM in 4.4.2 and build .137?!
mcjez15 said:
can I use this one on a ROOTED STOCK ROM in 4.4.2 and build .137?!
Click to expand...
Click to collapse
as the post above yours says, you need a custom Kernel to use a FOTAKernel Partition. I'd recommend Advanced Stock Kernel by AndroPlus or AndroPlusKernel
@Myself5 i tried instal twrp from your awesome app after an format and updated my device to lollipop stock and back to cm12 but anytime the device boot in cyanogenmod recovery its somthing with bootloader changed at lollipop?
Will any of the recoveries work on Locked Bootloader running Android 5.0.2?
CrazyGamerGR said:
Myself5 i tried instal twrp from your awesome app after an format and updated my device to lollipop stock and back to cm12 but anytime the device boot in cyanogenmod recovery its somthing with bootloader changed at lollipop?
Click to expand...
Click to collapse
Hum should be working fine... I'll take a look at it, got to update the recovery anyways.
yavhin said:
Reserved
Click to expand...
Click to collapse
Dafuq ?
When will there be a recovery for lollipop?
All recoverys are already compatible with Lollipop.
I thought the "fastboot flash recovery...." command is not valid on Sony's world as the recovery partition is combined in kernel? I always thought the kernel and the recovery must be united then flashed with "fastboot flash boot ....." command? Am I wrong?
Sent from my Xperia Z2 using XDA Free mobile app
_delice_doluca_ said:
I thought the "fastboot flash recovery...." command is not valid on Sony's world as the recovery partition is combined in kernel? I always thought the kernel and the recovery must be united then flashed with "fastboot flash boot ....." command? Am I wrong?
Sent from my Xperia Z2 using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
the recovery partition isnt 100% independant so you need a kernel that supports fotakernel (recovery partition)
but they are separate, boot and recovery
Myself5 said:
All recoverys are already compatible with Lollipop.
Click to expand...
Click to collapse
wut? So you mean philz recovery is working for locked bootloaders if I update to lollipop? Is there any guide on how to flash the recovery when updated?
really ?
Myself5 said:
All recoverys are already compatible with Lollipop.
Click to expand...
Click to collapse
hey so can you tell me where to find a compatible one with my z2 5.0.2
thx
romdroid. said:
wut? So you mean philz recovery is working for locked bootloaders if I update to lollipop? Is there any guide on how to flash the recovery when updated?
Click to expand...
Click to collapse
As the post right above yours says, you need a kernel which supports loading Recoverys from FOTAKernel Partition (if you run stock, I'd recommend either advanced Stock Kernel or AndroPlus Kernel, both made by @AndroPlus), which both need a unlocked bootloader in order to work, so the answer to your question is no, it does NOT work on locked bootloader, for LB you might want to try XZDualRecovery.
ryan42680 said:
hey so can you tell me where to find a compatible one with my z2 5.0.2
thx
Click to expand...
Click to collapse
You are kidding me, right? READ THE OP!
I did and i didnt find nothing. As far as i know we need to run a bat file to fix it if you are running stock xperia lp. You can find a link in their thread.
http://forum.xda-developers.com/showthread.php?p=59879026
Recovery doesn't stick
So I downloaded your awsome m5-settings app and tryed to installed twrp recovery on my z2, running cm12. Booted into recovery, and twrp came up (instead of cm recovery). But it doesn't "stick". I can't press any buttons, and after approximately 10-20 seconds the phone reboot normal again. I've tried to use cwm also, but twrp still shows up and doesn't work. Last resort I tried philz, but still got twrp.
I also tried to run fotacwm img, thru terminal emulator. But nothing works.
All I want is a custom recovery that works, since CM 12 recovery is useless!!
Btw. I'm a noob, so please be gentle against me
Ps: I added a screenshot of the phone details. It's in Norwegian, but I guess you understand (sorry)
I've made fota twrp recovery for z3c
install through fastboot
fastboot flash recovery fotaZ3C_2.8.5.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ3C_2.8.5.img
Can this be installed on rooted stock ROM/kernel?
hamsup1o said:
Can this be installed on rooted stock ROM/kernel?
Click to expand...
Click to collapse
if you have androplus kernel - yes, press power button, clean stock kernel - never tested
but ub is mandatory
ok thanks anyway...was hoping not to have to unlock bootloader.
funiewski said:
I've made fota twrp recovery for z3c
Click to expand...
Click to collapse
Great.
Were you able to compile it yourself?
If yes, could you point to source code.
I was unable to compile it before and would love to try again.
m0d said:
Great.
Were you able to compile it yourself?
If yes, could you point to source code.
I was unable to compile it before and would love to try again.
Click to expand...
Click to collapse
No compiling, here is description how to do it http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719
This one reverts my recovery to stock CM. Fota 2.8.4.0 worked though, glad I didn't delete it.
Zwulf said:
This one reverts my recovery to stock CM. Fota 2.8.4.0 worked though, glad I didn't delete it.
Click to expand...
Click to collapse
recovery is working wp on stock with androplus kernel, haven't tested with cm bcs for me cm isn't good enough for now
Zwulf said:
This one reverts my recovery to stock CM. Fota 2.8.4.0 worked though, glad I didn't delete it.
Click to expand...
Click to collapse
funiewski said:
recovery is working wp on stock with androplus kernel, haven't tested with cm bcs for me cm isn't good enough for now
Click to expand...
Click to collapse
I have the same issue. It flashes CM recovery not TWRP.
Androplus kernel has TWRP already, it is integrated, there is no need to flash TWRP over it.
The one below ( have not tested the latest, but the old one worked) flashes TWRP correctly,
kyasu said:
I have made twrp 2.8.5.0 recovery for flashing on fota partition.
This is just packing the zImage of CM12 and the ramdisk of Fota TWRP 2.8.5.0 recovery for amami <http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719>,
plus default.prop modification: 'ro.product.device' is defined as 'z3c' ('ro.build.product' is defined as 'aries').
You can directly flush CM12.
Installation:
fastboot flash recovery fota-twrp2.8.5.0-z3c.img
Download:
https://www.androidfilehost.com/?fid=95916177934529111
Previous Version:
http://forum.xda-developers.com/showpost.php?p=58530843&postcount=217
Click to expand...
Click to collapse
m0d said:
I have the same issue. It flashes CM recovery not TWRP.
Androplus kernel has TWRP already, it is integrated, there is no need to flash TWRP over it.
The one below ( have not tested the latest, but the old one worked) flashes TWRP correctly,
Click to expand...
Click to collapse
It's correct that androplus has TWRP but it's not on fota partition, androversion is 2.8.4. You can rich andros twrp by pressing vol +, fota by pressing power button. Advantage of fota is that recovery persist different kernels. For now there is no other kernel but hopefully there will be in the future
and it does not flash cm recovery, it is there in boot.img from beginning
Does it work with cm12.1?
Does this unlock the bootloader?
Does installing this unlock the bootloader?
I see that the install is taking place through fastboot mode. Does this result in the bootloader becoming unlocked?
Is there a way to install the recovery without unlocking the bootloader?
Thanks.
qaqarox said:
Does installing this unlock the bootloader?
I see that the install is taking place through fastboot mode. Does this result in the bootloader becoming unlocked?
Is there a way to install the recovery without unlocking the bootloader?
Thanks.
Click to expand...
Click to collapse
No cause it only can be installed on a partition that is free after bootloader unlock
fastboot flash recovery fota-twrp2.8.5.0-z3c.img
operation successful, but cant get to recovery either way (power button + clicking on bottom/upper part of volume button
Edit: Resolved. After flashing fota-twrp, i "batted" lockeddualrecovery, then flashed Cyanogen Recovery. For some reason fota-twrp recovery is still present. Accessable via power button + clicking on volume up.
Guys, I need a recovery I can use to make nandroid backup of my current ROM, format /system and flash any CM12.1 version without having to hack into the updater-script and remove the first line to make it flash. Also, it would be perfect if it was persistent no matter which ROM I flash.
Can this one do that? Can anyone advice please? This recovery thing on Sony devices is still a very confusing topic to me, especially coming from Samsung phones, on which you do have a default recovery and flashing a custom one won't be deleted when flashing a custom ROM.
Looking forward to your replies.
IceTi said:
Does it work with cm12.1?
Click to expand...
Click to collapse
+1 here
im on cm 12.1 nightly. and wanna make a nandroid. but have only cyanogen recovery ....
can i flash this recovery "over" my existing ?
will the nightly updater still work then ?!
+1 Here as well. For reasons I don't understand, there's no backup option in the CM 12.1 recovery. The AndroPlus kernel isn't a solution as the developer says it does NOT work with CM. Despite trying a few different recovery options, I can't seem to get anything but CM recovery which is part of CM's boot.img. The CM recovery/bootloader/kernel gets flashed with:
fastboot flash boot boot.img
While this, and most other recoveries I can find, get flashed with:
fastboot flash recovery xxxx.img
I realize the Z3C doesn't have a conventional recovery partition. And, from what I understand, it essentially has two locations for a recovery utility with one designed for OTA use. I've tried three different methods:
Flashing recoveries with: fastboot flash recovery xxxx.img but I still get only the CM recovery (as others have reported in this thread).
Installing a ZIP recovery from within the CM recovery, but I still get only the CM recovery
Installing the TWRP app, letting it download TWRP for the Z3C, and the install fails.
What many of us seem to need is a boot.img file with TWRP that works with CM. Based on my experience that's the only way to replace the CM recovery.
Has anyone found a solution?
dev_guy said:
+1 Here as well. For reasons I don't understand, there's no backup option in the CM 12.1 recovery. The AndroPlus kernel isn't a solution as the developer says it does NOT work with CM. Despite trying a few different recovery options, I can't seem to get anything but CM recovery which is part of CM's boot.img. The CM recovery/bootloader/kernel gets flashed with:
fastboot flash boot boot.img
While this, and most other recoveries I can find, get flashed with:
fastboot flash recovery xxxx.img
I realize the Z3C doesn't have a conventional recovery partition. And, from what I understand, it essentially has two locations for a recovery utility with one designed for OTA use. I've tried three different methods:
Flashing recoveries with: fastboot flash recovery xxxx.img but I still get only the CM recovery (as others have reported in this thread).
Installing a ZIP recovery from within the CM recovery, but I still get only the CM recovery
Installing the TWRP app, letting it download TWRP for the Z3C, and the install fails.
What many of us seem to need is a boot.img file with TWRP that works with CM. Based on my experience that's the only way to replace the CM recovery.
Has anyone found a solution?
Click to expand...
Click to collapse
Yes i do. I asked and got link to dual recovery page where u upload your boot.img and then it lets u download it with philz.touch injected
Sent from my D5803 using XDA Free mobile app
polykoma said:
Yes i do. I asked and got link to dual recovery page where u upload your boot.img and then it lets u download it with philz.touch injected
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. I found a TWRP that actually works with CM12.1 when you flash it from fastboot here.
It's a common enough request you would think someone would have made it available for CM?
I'm currently running 6.0.3 paranoid version. And I did obviously have root before installing this ROM. I have tried looking in the developer options to see if it wasn't turned on, but the option isn't available anymore. I'm not sure what information i need to supply. Will I need to root again?
Thanks for reading,
Evitov.
The ROM doesn't ship with root. It isn't needed for the ROM to work.
If you want to root it, just flash SuperSU zip in recovery.
Pirateghost said:
The ROM doesn't ship with root. It isn't needed for the ROM to work.
If you want to root it, just flash SuperSU zip in recovery.
Click to expand...
Click to collapse
It made me lose my custom recovery which was twrp. Which is why i cannot flash it.
Evitov said:
It made me lose my custom recovery which was twrp. Which is why i cannot flash it.
Click to expand...
Click to collapse
You should go ask in your device forum. I've never heard of recovery being removed after flashing a ROM
Pirateghost said:
The ROM doesn't ship with root. It isn't needed for the ROM to work.
If you want to root it, just flash SuperSU zip in recovery.
Click to expand...
Click to collapse
Pirateghost said:
You should go ask in your device forum. I've never heard of recovery being removed after flashing a ROM
Click to expand...
Click to collapse
Okay thanks for your help anyway, i'll try that then.
@Evitov
There may be two reasons for losing recovery:
1.You had dual recovery for stock locked bootloader.
2.You had kernel with built in recovery.
And to get recovery:
Just download twrp for z2
And flash through flashtool.
Thats it
Evitov said:
It made me lose my custom recovery which was twrp. Which is why i cannot flash it.
Click to expand...
Click to collapse
Did you have the latest marshmallow stock build(.291) before this? If so , then connect to computer in fastboot mode, download twrp image for your phone, copy to fastboot folder and type,
Code:
fastboot flash recovery (the twrp image name).img
To get into recovery, hold power and vol down buttons together until sony logo.
I cannot be sure if this will work with your device bc i have a z3 compact
but still, try!
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t
Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...
maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image
maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.
maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...
We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.
5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful
so i'm going thru the same thing as OP.
I need help.
Hi guys, I'm on 8.1 right now wanting to go on 11 AOSP.
I flashed both orangefox and latest twrp, but I get black screen after going into recovery. System boots though.
What do? I have no recovery ATM. I can try going back to my latest version (2.8) but how do I actually manage to run latest versions without getting black screen?
I've been reading that It might be due to matching kernel that is missing, could it be? What should I do in this case?
Thanks!
Go to fastboot mode and
Fastboot flash recovery "twrp.img"
Via PC
or just type
fastboot boot "twrp.img"
That's how I flashed, through fastboot. Still getting black screen.
Haven't tried booting straight to IMG, I'll try when I get to
You said system is booting. Do you mean aosp11 or 8.1?
I didn't get to flash aosp11 yet, because I failed to boot into required recovery. So I'm still booting to my current 8.1 rom
Im sorry if this is too obvious, but do you have an unlocked bootloader?
SirRGB said:
Im sorry if this is too obvious, but do you have an unlocked bootloader?
Click to expand...
Click to collapse
Yes I do brother
HeLp Me
Same issue here
quick05 said:
Same issue here
Click to expand...
Click to collapse
It's the firmware bro, flash latest firmware and then flash recovery.
So you dirty flashed the latest oos ROM and then you flashed the recovery again ?
quick05 said:
So you dirty flashed the latest oos ROM and then you flashed the recovery again ?
Click to expand...
Click to collapse
I flashed latest working twrp for my device (was 3.2) from fastboot, booted to working recovery and then flashed android 10 firmware, then (before rebooting) flashed latest recovery. It then booted.
xradium said:
I flashed latest working twrp for my device (was 3.2) from fastboot, booted to working recovery and then flashed android 10 firmware, then (before rebooting) flashed latest recovery. It then booted.
Click to expand...
Click to collapse
Nice thank you ! I flashed 3.2 twrp and now it is booting in recovery
Another problem: when I try to flash the latest OTA of android 10 I can't: error 7 can't load vendor partition...
Any solution ?
quick05 said:
Nice thank you ! I flashed 3.2 twrp and now it is booting in recovery
Another problem: when I try to flash the latest OTA of android 10 I can't: error 7 can't load vendor partition...
Any solution ?
Click to expand...
Click to collapse
u need to flash the firmware that creates the vendor partition, and I guess that it's OOS 5.1.7 (Android 8)
afterwards u can flash whatever latest firmware.
please ask again, as I'm not so sure about which firmware that creates vendor partition.