In the op downloads section its has vbmeta_vendor.img instead of vendor_boot.img. Is this right?
No worries. I ended up snagging vendor_boot via payload which worked flawlessly! And now that the sim issue seems fixed with the oos12dt. I can now allow CorvusOS to compete with CherishOS as my number 1.
It's the screen cast directly under android/system settings(I believe it should be in qs tiles by default, if not its under Connected Devices in system settings). Third party apps work fine to screen cast but whenever I tried the default, it would just force close when connecting to a device.
#include <std_disclaimer.h> /* * Your warranty is... still valid? * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
It happens to me also. I have Verizon service. Some roms work every time. Some updates break data. It's just something we users have to deal with using CDMA based service.It's a reoccurring issue I face only with few select roms out of the many roms I flash quite frequently. Most roms I flash do so flawlessly, regardless of whether or not I MSM prior to, as long as I'm already on a custom rom. I've tried several times, following OP instructions to a tee.
this Last time I MSMed back to OOS 11 I was able to retain L1. So I'm confident I followed directions pertaining to OOS 184.108.40.206 being on both slots prior to flashing custom boot.img for recovery.