Did you flash it to inactive slot or over active slot?It's taken care of by fastboot flash, I did it 2 weeks ago without issue, no data wipe, remained rooted
Did you flash it to inactive slot or over active slot?It's taken care of by fastboot flash, I did it 2 weeks ago without issue, no data wipe, remained rooted
I also followed a similar fastboot flash command to flash a full ota rom. It has a slight difference on these two commands. Why?It's taken care of by fastboot flash, I did it 2 weeks ago without issue, no data wipe, remained rooted
I've checked back and I did:I also followed a similar fastboot flash command to flash a full ota rom. It has a slight difference on these two commands. Why?
The one I followed:
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
The one you followed has:
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
Fastboot Method commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash boot magisk_patchedc21eu-25100_shnKf.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash qupfw qupfw.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash abl abl.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash my_bigball my_bigball.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_manifest my_manifest.img
fastboot flash my_preload my_preload.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash tz tz.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
Did you flash it to inactive slot or over active slot?I've checked back and I did:
Code:fastboot --disable-verity flash vbmeta vbmeta.img fastboot --disable-verity flash vbmeta_system vbmeta_system.img
I had 43 partitions:
Code:fastboot flash boot magisk_patchedc21eu-25100_shnKf.img fastboot flash dtbo dtbo.img fastboot flash modem modem.img fastboot --disable-verity flash vbmeta vbmeta.img fastboot --disable-verity flash vbmeta_system vbmeta_system.img fastboot reboot fastboot fastboot flash cmnlib cmnlib.img fastboot flash cmnlib64 cmnlib64.img fastboot flash logo logo.img fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img fastboot flash aop aop.img fastboot flash bluetooth bluetooth.img fastboot flash dsp dsp.img fastboot flash dtbo dtbo.img fastboot flash modem modem.img fastboot flash qupfw qupfw.img fastboot flash multiimgoem multiimgoem.img fastboot flash uefisecapp uefisecapp.img fastboot flash abl abl.img fastboot flash bluetooth bluetooth.img fastboot flash devcfg devcfg.img fastboot flash featenabler featenabler.img fastboot flash hyp hyp.img fastboot flash imagefv imagefv.img fastboot flash keymaster keymaster.img fastboot flash my_bigball my_bigball.img fastboot flash my_carrier my_carrier.img fastboot flash my_company my_company.img fastboot flash my_engineering my_engineering.img fastboot flash my_heytap my_heytap.img fastboot flash my_manifest my_manifest.img fastboot flash my_preload my_preload.img fastboot flash my_product my_product.img fastboot flash my_region my_region.img fastboot flash my_stock my_stock.img fastboot flash tz tz.img fastboot flash vm-bootsys vm-bootsys.img fastboot flash xbl xbl.img fastboot flash xbl_config xbl_config.img fastboot flash product product.img fastboot flash system system.img fastboot flash system_ext system_ext.img fastboot flash vendor vendor.img fastboot flash odm odm.img
I simply issued those commands, no other, so whichever fastboot defaults to
Thank you very much for your help.... It did clarify and corrected some things I was doing wrong. Hope it helps other in the same situation. I was only flashing the commands on the list and not adding more fastboot commands for the partitions I had. Basically I left many partitions out and that's why it did not update correctly.I simply issued those commands, no other, so whichever fastboot defaults to
Some have tried this and said that it works. It did not work for me, but I'll post it here in case it does help someone.I simply issued those commands, no other, so whichever fastboot defaults to
It did work and now the About device Update check displays the correct version and this time it says OFFICIAL. The Version says the correct build number, but the Android security stayed on 05/05/2022 and it did not change to June security. Did yours update to the June security? I will see if I can flash the Full OTA locally and have it flash on the new slot and use magisk to patch the new slot and see if that fixes everything. I posted screenshots of before and after the fastboot flash.I simply issued those commands, no other, so whichever fastboot defaults to
I did the install of the Full OTA in the about device local update. It did it the update and installed in inactive slot. The only issue I am having it that the security update is still on May and I thought it included the June security. Does yours have the June security?I simply issued those commands, no other, so whichever fastboot defaults to
May/22I did the install of the Full OTA in the about device local update. It did it the update and installed in inactive slot. The only issue I am having it that the security update is still on May and I thought it included the June security. Does yours have the June security?
It's a joke. We are a couple of days away from August and they could not include the June security with this update? I think COVID has affected the OnePlus developers.
It's taken care of by fastboot flash, I did it 2 weeks ago without issue, no data wipe, remained rootedI did that yesterday, but if I go to about device, then update version it says I have the C.20. Now if I go to the build.... It says I have C.21. I have done the fastboot flash ROM over the a current version to fix boot loop or other fixes, but I have never used it to update. I think updating in the same partition it doesn't work as intended. I think is intended to be done on a formatted partition.
I've checked back and I did:I also followed a similar fastboot flash command to flash a full ota rom. It has a slight difference on these two commands. Why?
The one I followed:
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
The one you followed has:
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
Fastboot Method commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash boot magisk_patchedc21eu-25100_shnKf.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash qupfw qupfw.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash abl abl.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash my_bigball my_bigball.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_manifest my_manifest.img
fastboot flash my_preload my_preload.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash tz tz.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
I simply issued those commands, no other, so whichever fastboot defaults to
Thank you very much for your help.... It did clarify and corrected some things I was doing wrong. Hope it helps other in the same situation. I was only flashing the commands on the list and not adding more fastboot commands for the partitions I had. Basically I left many partitions out and that's why it did not update correctly.I simply issued those commands, no other, so whichever fastboot defaults to
Some have tried this and said that it works. It did not work for me, but I'll post it here in case it does help someone.I simply issued those commands, no other, so whichever fastboot defaults to
My OP8 (UK) just updated to 10.5.7 from .6 today (courtesy of Oxygen Updater). Seems to be lots of new optimised stuff.