Develop Bugs

Android 10 Stock Fastboot

Fastboot:
V11.0.15.0.QFQMIXM
TGZ
laurel_sprout_global_images_V11.0.15.0.QFQMIXM_10.0.tgz
https://www.androidfilehost.com/?fid=4349826312261807505
RAR
laurel_sprout_global_images_V11.0.15.0.QFQMIXM_10.0.rar
https://www.androidfilehost.com/?fid=4349826312261807506
V11.0.15.0.QFQMIXM
TGZ
laurel_sprout_global_images_V11.0.14.0.QFQMIXM_10. 0.tgz
https://androidfilehost.com/?fid=4349826312261783904
MD5: d6dc459e6cdb5f2b39c06be17090a455
RAR
laurel_sprout_global_images_V11.0.14.0.QFQMIXM_10.0.rar
https://www.androidfilehost.com/?fid=4349826312261785200
MD5: 5e7a3635661663db4c8953fca27f3be3
Note: Extracted from OTA zip & compiled back using maximum compression

edwaine said:
Fastboot:
laurel_sprout_global_images_V11.0.14.0.QFQMIXM_10. 0.tgz
https://www.androidfilehost.com/?fid...26312261783904
MD5: d6dc459e6cdb5f2b39c06be17090a455
Note: Extracted from OTA zip & compiled back using maximum compression
Click to expand...
Click to collapse
I extracted it but I didn't find the flash_all except data/bat script. Should not be?

papafan said:
I extracted it but I didn't find the flash_all except data/bat script. Should not be?
Click to expand...
Click to collapse
What program did you use to open the file? All the needed files are there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure you wait for the load to complete as this is a highly compressed zip file.

edwaine said:
What program did you use to open the file? All the needed files are there.
Make sure you wait for the load to complete as this is a highly compressed zip file.
Click to expand...
Click to collapse
Here in the first photo I don't see the " flash_all _except storage / bat " script. In a similar case when I flashed the stock A9 .tgz file, I also had this ability, to flash rom without lose data.

link not working :crying:

sunny3503 said:
link not working :crying:
Click to expand...
Click to collapse
Works fine for me.
Anyways, will post another link under RAR file.
Update: File uploaded, OP updated. Please check.

What about EU version PFQEUXM. Is it also available?
and another question... Will High Brightness Mode be available in android 10 for Mi A3?

tomiasx22 said:
What about EU version PFQEUXM. Is it also available?
and another question... Will High Brightness Mode be available in android 10 for Mi A3?
Click to expand...
Click to collapse
Eu version wasn't released by xiaomi yet so you will have to wait for it to be released.
And as for high brightness that's an issue with the Android one program. Being apart of the Android one program limits max brightness to 350 nits (actually just slightly less than 350 nits)
Xiaomi cc9e is basically the same device with miui and has max manual brightness of 530 nits.
It's a result of being part of Android one. Just Google it

tgz link not work

garylawwd said:
Eu version wasn't released by xiaomi yet so you will have to wait for it to be released.
And as for high brightness that's an issue with the Android one program. Being apart of the Android one program limits max brightness to 350 nits (actually just slightly less than 350 nits)
Xiaomi cc9e is basically the same device with miui and has max manual brightness of 530 nits.
It's a result of being part of Android one. Just Google it
Click to expand...
Click to collapse
Thanks for this answer. Of course I checked it before writing this post, sorry that I didn't mention that.
There are some rankinkgs on the web, where much older devices have brighter display, which put Mi A3 in the end of theese rankings...
Maybe stupid question, but do you think this may change in new Android One based on android 10?
Or is any other solution to improve brightness?
Applications to improve brightness on Google Play doesn't work with this phone (of course rooted).
but maybe Magisk module etc. ?
e.g. in Google Pixel 4 they explain how to enable this mode...
https://hothardware.com/news/google-pixel-4-high-brightness-mode

alcopsy said:
tgz link not work
Click to expand...
Click to collapse
The correct link:
https://androidfilehost.com/?fid=4349826312261783904
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
sunny3503 said:
link not working :crying:
Click to expand...
Click to collapse
I found the correct link:
https://androidfilehost.com/?fid=4349826312261783904

thx!

I had no recovery and used flash_all.bat expecting to factory reset (including data), but it just updated my room and all my data (files, accounts, lockscreen, fingers, logins etc) was keeped.. Device is "ok" is this normal?

when I run the script flash.all.bat nothing happens how it does
Envoyé de mon Mi A3 en utilisant Tapatalk

Did you put your files in adb folder?

I unzipped the folder and I put it on my desktop in the same folder or I have minimal adb and fastboot
Envoyé de mon Mi A3 en utilisant Tapatalk
View attachment 5010703
I succeeded by installing Platforms tools on my pc and putting everything in the corresponding folder

Hello, can I install the .tgz version with MiFlash Tool?
Edit: I tried to flash the .tgz firmware with MiFlashTool but apparently it can't be installed this way. I'm going to try fastboot now. Let's see how it goes.
Edit 2: I ended up flashing the .tgz official April update of EU ROM. Switched from global to EU using miflash tool.

all instruction to run in cmd
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase vendor_a
fastboot erase vendor_b
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash product_a product.img
fastboot flash product_b product.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

Post updated to include Fastboot V11.0.15.0.QFQMIXM

edwaine said:
Post updated to include Fastboot V11.0.15.0.QFQMIXM
Click to expand...
Click to collapse
I am in stock A10 11.0.1.0 euro version. Can I install the global stock fastboot 11.0.15.0 without lose data?

[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12

As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
Massive Update! Someone found a way to recover the phone using EDL Deep Flash Cable.
XDA Thread Link
(Even though I tried it when it happened to me all this time ago and it didn't work, but it does seem to work for few people who used a Black & White cable from AliExpress (maybe there's some hidden tech inside) so give it a try and report, there's also a chance that maybe some devices don't get burned out but simply refuse to boot because voltage is too high, and others might be fried forever, we will see with time I guess. Nonetheless, Good Luck!)
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
Update: Double check Your RAM just in case!
Post #3
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.

ProtoDeVNan0 said:
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
View attachment 5578875
View attachment 5578877
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.
Click to expand...
Click to collapse
This is so F'ing insane

Some extra warnings:
1. OnePlus 8T/9R also has LPDDR4x variant, make sure the variants before flashing.
2. The DDR detection process was artificially killed, stay away from the Magisk modules to keep safe.
3. TWRP is no longer recommended, use OxygenOS modified recovery or other ROM's recovery instead.
4. Flash/Root has huge risks, all operations need to be careful.
OnePlus 8 - LPDDR4x
OnePlus 8 Pro - LPDDR5
OnePlus 8T - LPDDR4x/LPDDR5
OnePlus 9R - LPDDR4x/LPDDR5

Thank you

Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.

Holy ****...
These are the images of IN2025_11_C_OTA_1100
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
product.img
qupfw.img
recovery.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
xbl_config_lp5.img
xbl_lp5.img
And these are the images of 11.0.11.11
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
odm.img
product.img
qupfw.img
recovery.img
reserve.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
Usually i use this script after changing a rom and after using MSM tool.
Code:
fastboot -w
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 cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.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 mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.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
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
If i would have used this with OOS12 i would have bricked my phone on both slots instantly.....
Im so glad that i was sceptical because OOS12 had more .img files compared to OOS11 and i did not use the script.
People need to know this...
Am i right that as long as we stay on OOS11 and dont use anything from OOS12 we are good to go like before?

FYI. This is what I did to kill my phone, link below
"Warning" Total Brick After Flashing Android 12 Beta
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot. I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from...
forum.xda-developers.com

ProfEngr said:
Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.
Click to expand...
Click to collapse
Don't go to 12, it's LAME, Stay on 11, might even consider Samsung over OOS12

Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)

Niekdeg said:
Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)
Click to expand...
Click to collapse
Are you on Android 12 or 11?

nkhater said:
Are you on Android 12 or 11?
Click to expand...
Click to collapse
android 12

Niekdeg said:
android 12
Click to expand...
Click to collapse
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?

Niekdeg said:
android 12
Click to expand...
Click to collapse
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.

nkhater said:
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?
Click to expand...
Click to collapse
i have that but my device isn't there... i have install the driver but noting..

FreshlyBaked 420 said:
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.
Click to expand...
Click to collapse
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same

Niekdeg said:
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same
Click to expand...
Click to collapse
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4

nkhater said:
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Click to expand...
Click to collapse
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so

Niekdeg said:
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so
Click to expand...
Click to collapse
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
here

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
i do but problem is my phone don't boot to edl mode

Development ROM ❯ 12L ❯ UNOFFICIAL ❯ LEMONADEP ❯ 01-08-2022 ❯ CorvusOS S3.2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#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.
*/
https://github.com/Corvus-R
https://github.com/LineageOS/android_kernel_oneplus_sm8350
Select build corresponding to your device's codename ( OnePlus 9 Pro = lemonadep )
Corvus_vS3.2-Vindicate-lemonadep-gabriel_UNOFFICIAL-20220801.zip
drive.google.com
Corvus_vS3.2-Vindicate-lemonadep-dtbo.img
drive.google.com
Corvus_vS3.2-Vindicate-lemonadep-boot.img
drive.google.com
Corvus_vS3.2-Vindicate-lemonadep-vendor_boot.img
drive.google.com
NikGapps - Browse /Releases at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
- Backup your personal data [IMPORTANT]
- Be on latest firmware OOS 12 (C.61)
- Download CorvusOS rom & boot & vendor_boot & dtbo for your variant
- Boot to Bootloader
- Flash the boot Image
- Flash the vendor_boot Image
- Flash the dtbo Image
- Reboot to Recovery Mode
- “Apply Update” and select “Apply from ADB”
- Adb sideload CorvusOS.zip
- "Advanced" and select "Reboot to recovery"
- “Apply Update” and select “Apply from ADB”
- Adb sideload NikGapps.zip
This build was only possible thanks to:​@pranavasri​@Ivan_Meler​@expressluke​@kumar akarsh​@chandu dyavanapelli
https://t.me/cyberAkhi
If you like my work buy me a gin & tonic cocktail
Donate to Gabriel Sousa
Help support Gabriel Sousa by donating or sharing with your friends.
www.paypal.com
XDA:DevDB Information
CorvusOS vS3.2 - Android12L, ROM for the OnePlus 9 Pro
Builder
GabrielSousa
ROM OS Version: Android 12L
ROM Kernel: Linux 5.4.x
Created 2022-06-03
Last Updated 2022-08-01

Select build corresponding to your device's codename ( OnePlus 9 Pro = lemonadep )
C61_imgs-lemonadep.zip
drive.google.com
- Download C61_imgs for your variant
- Boot to Bootloader
- Run flash-all.bat
Spoiler: flash-all.bat
Code:
fastboot flash vendor_boot_a pex-vendor_boot.img
fastboot flash vendor_boot_b pex-vendor_boot.img
fastboot flash boot_a pex-boot.img
fastboot flash boot_b pex-boot.img
fastboot flash dtbo_a pex-dtbo.img
fastboot flash dtbo_b pex-dtbo.img
fastboot flash --slot=all modem modem.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cpucp cpucp.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all engineering_cdt engineering_cdt.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all oplus_sec oplus_sec.img
fastboot flash --slot=all oplusstanvbk oplusstanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all qweslicstore qweslicstore.img
fastboot flash --slot=all shrm shrm.img
fastboot flash --slot=all splash splash.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all vm-bootsys vm-bootsys.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img

DL now

Nice! Screenshots?

can i flash this rom directly from crdroid rom. or i need to first msm to a11 and then flash it. currently using crdroid 8.5 A12

vsinha71 said:
can i flash this rom directly from crdroid rom. or i need to first msm to a11 and then flash it. currently using crdroid 8.5 A12
Click to expand...
Click to collapse
Clean install (format data) prior to flashing should suffice. No need to MSM back to a11.

cave.man1908 said:
Clean install (format data) prior to flashing should suffice. No need to MSM back to a11.
Click to expand...
Click to collapse
Thank you so much.

for magisk rooting which magisk_boot.img should i use. thank you.

Reporting that aptx adaptive audio codec not working properly

vsinha71 said:
for magisk rooting which magisk_boot.img should i use. thank you.
Click to expand...
Click to collapse
You need to extract boot.img from payload.bin file located within rom zip . Then patch boot.img via Magisk app.
Or...Simply adb sideload Magisk.zip via recovery. Reboot and install directly within Magisk app.

Clean installed Corvus. No data connection. Attempted manual APN setup but could not because my SIM is not recognized.
LE2125 and Visible as my carrier.

cave.man1908 said:
You need to extract boot.img from payload.bin file located within rom zip . Then patch boot.img via Magisk app.
Or...Simply adb sideload Magisk.zip via recovery. Reboot and install directly within Magisk app.
Click to expand...
Click to collapse
thank you

cave.man1908 said:
Clean installed Corvus. No data connection. Attempted manual APN setup but could not because my SIM is not recognized.
LE2125 and Visible as my carrier.
Click to expand...
Click to collapse
Make sure you do a clean install after MSM back to stock. Usually fixes most sim problems. If that don't fix it then it's a source issue.

kushsix said:
Make sure you do a clean install after MSM back to stock. Usually fixes most sim problems. If that don't fix it then it's a source issue.
Click to expand...
Click to collapse
Are you on it? How is it

kushsix said:
Make sure you do a clean install after MSM back to stock. Usually fixes most sim problems. If that don't fix it then it's a source issue.
Click to expand...
Click to collapse
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 11.2.10.10 being on both slots prior to flashing custom boot.img for recovery.

gillim74 said:
Are you on it? How is it
Click to expand...
Click to collapse
I'm on spark.

cave.man1908 said:
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 11.2.10.10 being on both slots prior to flashing custom boot.img for recovery.
Click to expand...
Click to collapse
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.

kushsix said:
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.
Click to expand...
Click to collapse
I actually don't mind when I encounter mishaps. it allows me to exercise my infant like troubleshooting tactics lol. In hopes of expanding my knowledge base.
-much love & respect to all the souls that make the android community a reality!\m/

GabrielSousa said:
reserved
Click to expand...
Click to collapse
Doesn't work for verizon.doesnt even register there is a sim card in it

gillim74 said:
Doesn't work for verizon.doesnt even register there is a sim card in it
Click to expand...
Click to collapse
gonna check it out

How To Guide Convert ColorOS to OxygenOS (OFP & OTA | Bootloader reLock & PIN working)

Update: 18th March 2023
**** Give Up ****
I got so fedup and decided to goto HK and get my OnePlus 11, a real CPH2449 GLO. Paid and waiting to collect.
I will not be update and maintaining this post from now on.
Why give up?
Minor issue like auto brightness and things is still something i can live along with.
Some othe rmajor issue are just impossible to make this chiniese converted 1+11 to be my daily driver:
- Auto reboot randomly
- Lagging randomly, screen lag, video recording lag.
- OTA update issue, refreshing/reinstall at every update is just anonying
My advice? just get a proper non chinese version or if you own a Chinese version just stick with colorOS.
**** Flash at your own risk ****
**** Flash at your own risk ****
**** Flash at your own risk ****
*** DO NOT OTA UPDATA Your Phone After Convert. It will brick and only Official MSM Tool can save you ***
A Oneplus user since OnePlus one. Give up Oneplus and swtiched to Nothing phone since Oneplus 10. Decided to try out OnePlus 11 and ColorOS is really pain in the a**
This post tested converting from PHB110 to CPH2447 / CPH2449. I did not test CPH2451.
Model:
CPH2447 - Indian
CPH2449_EEA - EU
CPH2449_GLO - International
CPH2451 - North America
PHB110 - China
Credits：
Thanks for their feedback
[email protected]
wtywtykk
mark332
alexander宇
daxiaamu
Following is the steps to flash the OTA updates:​
Step 1:
Download all the usual tools
Download Fastboot Enhance
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449 Global A07: eea73728a1b945ea8e3ff6b628495af5.zip
ColorOS: Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin
Step 4:
Boot into fastbootd (Phone Screen: The one with language selection)
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Step 5:
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img exits
Boot into fastbootd (Phone Screen: The one with language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
Step 6:
Follow step 6 from "flash the OFP/EDL Packages"
Following is the steps to flash the OFP/EDL Packages:​
Step 1:
Download all the usual tools
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449GDPR_11_A.06_2023010723370128.zip
Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
fastboot flash --slot=all modem radio/modem.img
fastboot flash --slot=all boot images/boot.img
fastboot flash vbmeta_system_a images/vbmeta_system.img
fastboot flash vbmeta_system_b images/vbmeta_system.img
fastboot flash vbmeta_a images/vbmeta.img
fastboot flash vbmeta_b images/vbmeta.img
fastboot flash vendor_boot_a images/vendor_boot.img
fastboot flash vendor_boot_b images/vendor_boot.img
fastboot flash vbmeta_vendor_a images/vbmeta_vendor.img
fastboot flash vbmeta_vendor_b images/vbmeta_vendor.img
Step 4:
Go into fastbootd (Phone Screen: The one with language selection)
fastboot reboot fastboot
fastboot flash --slot=all init_boot images/init_boot.img
fastboot flash --slot=all abl radio/abl.img
fastboot flash --slot=all aop radio/aop.img
fastboot flash --slot=all aop_config radio/aop_config.img
fastboot flash --slot=all bluetooth radio/bluetooth.img
fastboot flash --slot=all cpucp radio/cpucp.img
fastboot flash --slot=all devcfg radio/devcfg.img
fastboot flash --slot=all dsp radio/dsp.img
fastboot flash --slot=all dtbo images/dtbo.img
fastboot flash --slot=all engineering_cdt images/engineering_cdt.img
fastboot flash --slot=all featenabler radio/featenabler.img
fastboot flash --slot=all hyp radio/hyp.img
fastboot flash --slot=all imagefv radio/imagefv.img
fastboot flash --slot=all keymaster radio/keymaster.img
fastboot flash --slot=all oplus_sec radio/oplus_sec.img
# Flash the ColorOS version A.08 # fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
fastboot flash --slot=all qupfw radio/qupfw.img
fastboot flash --slot=all recovery images/recovery.img
fastboot flash --slot=all shrm radio/shrm.img
fastboot flash --slot=all splash images/splash.img
fastboot flash --slot=all tz radio/tz.img
fastboot flash --slot=all uefi radio/uefi.img
fastboot flash --slot=all uefisecapp radio/uefisecapp.img
fastboot flash --slot=all xbl radio/xbl.img
fastboot flash --slot=all xbl_ramdump radio/xbl_ramdump.img
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img
Step 5:
From the fastbootd screen (with language selection),
English
Format Data
Step 6:
From daxiaamu blog post,
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Go into bootloader again. follow step 2
Run $ fastboot flashing lock
Again, go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Once passed the setup screen. Goto settings and set the pin
Additional Tips:
If your phone goes into bootloop with oneplus logo. Most likely its not brick. Just need to do a factory reset in fastboot or QLMFlasher.
As mention by mark332 use the free edition. Goto the fastboot tab and unbrick your phone.
I also paid for the commercial edition. Received username/password which can never login to the commercial editon. Commercial edition allows flash in EDL which i wanted to try.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.

sth_safal said:
Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.
Click to expand...
Click to collapse
i tried to, after locking the bootloader. the system not able to set the screenlock pattern

kaijern said:
i tried to, after locking the bootloader. the system not able to set the screenlock pattern
Click to expand...
Click to collapse
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..

sth_safal said:
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..
Click to expand...
Click to collapse
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
I am the same.
Can I recover with relock?

sth_safal said:
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?
Click to expand...
Click to collapse
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
Since its worling. I will wait for the international version to be avilable after Feb 7 and try to do a complete flash again. By that time is just all about from Oxygen to Oxygen nothing risky.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
I tried to relock it.
fastboot oem lock、fastboot flashing lock、fastboot oem unlock、fastboot flashing unlock
Every command gives me an error.

It seems I brick my phone.
After I typed in "fastboot flash --slot=all abl abl.elf", I got this error:
ERROR: usb_write failed with status e00002ed
fastboot: error: Could not check if partition abl has slot all
In a poor attempt to fix it, I locked BL, and now it stuck in a bootloop to FASTBOOTD
I couldn't get back to FASTBOOT with pressing physical key. Please help!
P.S. I am using mac

if you can give a step by step, or actually a video, that would actually be amazing. i fear for my phone haha

Is this version of package able to receive the OTP update of OOS?

I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file

sunxutian said:
I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file
Click to expand...
Click to collapse
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
Why can't you boot into fastbood? Did you try fastboot reboot fastboot?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver

sunxutian said:
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver
Click to expand...
Click to collapse
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?

oprocks said:
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?
Click to expand...
Click to collapse
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader

sunxutian said:
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader
Click to expand...
Click to collapse
tried that a few times, something about "userdata" not working right..
platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.063s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
any idea if there is a way to get fastboot to get userdata partition to proper state first? maybe?

Question oneplus 11 stuck on bootloader

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help, this just happened to me, I was determined to try a covert from color os (phb110) to oxygen os, but what I experienced was difficulty so I was confused about returning the old stock rom? here I'm just stuck on the bootloader and can't access fastbootd, really just restarting the bootloader, is there a solution to fix it ??

Did you try researching this before doing this. https://forum.xda-developers.com/t/...fp-ota-bootloader-relock-pin-working.4546967/

M
MrSteelX said:
Did you try researching this before doing this. https://forum.xda-developers.com/t/...fp-ota-bootloader-relock-pin-working.4546967/
Click to expand...
Click to collapse
at first I followed the method above to convert color os to oxygen, only a few of my parts failed, and then I used another method but at that moment my fastbootd suddenly disappeared and couldn't be accessed, at this time my OnePlus just repeated to bootloader as in the photo

lhyyo06 said:
M
at first I followed the method above to convert color os to oxygen, only a few of my parts failed, and then I used another method but at that moment my fastbootd suddenly disappeared and couldn't be accessed, at this time my OnePlus just repeated to bootloader as in the photo
Click to expand...
Click to collapse
Start from step 3 again to restore fastbootd

MrSteelX said:
Start from step 3 again to restore fastbootd
Click to expand...
Click to collapse
I don't understand this step
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img comes out
Boot into fastbootd (Phone Screen: Which has language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
after I unzipped the file then what did I do with the file radio/oplusstanvbk.img ??

lhyyo06 said:
I don't understand this step
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img comes out
Boot into fastbootd (Phone Screen: Which has language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
after I unzipped the file then what did I do with the file radio/oplusstanvbk.img ??
Click to expand...
Click to collapse
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin

MrSteelX said:
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin
Click to expand...
Click to collapse
no no, I have succeeded with step 3, I asked again above for step 5 I don't understand. after unzipping the file, what should I do with this file radio/oplusstanvbk.img?

lhyyo06 said:
no no, I have succeeded with step 3, I asked again above for step 5 I don't understand. after unzipping the file, what should I do with this file radio/oplusstanvbk.img?
Click to expand...
Click to collapse
In fastbootd mode fastboot flash oplusstanvbk radio/oplusstanvbk.img

MrSteelX said:
In fastbootd mode fastboot flash oplusstanvbk radio/oplusstanvbk.img
Click to expand...
Click to collapse
and I always fail during this flash
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img

lhyyo06 said:
and I always fail during this flash
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img
Click to expand...
Click to collapse
Remove --slot=all

MrSteelX said:
Remove --slot=all
Click to expand...
Click to collapse
all existing --slot=all deleted ?

lhyyo06 said:
all existing --slot=all deleted ?
Click to expand...
Click to collapse
fastboot flash system images/system.img