Develop Bugs

Help Z2 PLAY XT1710-11 + Testing

Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"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"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends

I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .

[Tutorial] Splash Image Maker

Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed)
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
{
"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"
}
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Code:
fastboot flash splash splash.img

Chrono Leggionaire said:
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed)
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Code:
fastboot flash splash splash.img
Click to expand...
Click to collapse
WORKS !! THANKS search0123 :fingers-crossed: :good:

anyone have cool splash img? do share ty

Dark images included work well with paranoid boot animation, thanks! No more blinding mornings...

Good to know... Custom splash does not affect OTA to 10.0.7.0.

mi logo

I don't have a Windows but python should be cross-platform...
Because I have a Mac, I had to run xcode-select --install to get zlib in place for Pillow.
I had to pip2.7 install Pillow to get the PIL library that the script wanted.
Then I could run python2.7 splash_gen.py and it produced a splash.img for me.

no more full screen unlocked bootloader warning. thanks

I conpreased the image file as a zip when I go to twrp which should I select boot or something else

rob420p said:
I conpreased the image file as a zip when I go to twrp which should I select boot or something else
Click to expand...
Click to collapse
This is a bootloader splash. Flash from fastboot.
fastboot flash splash splash.img

a1291762 said:
This is a bootloader splash. Flash from fastboot.
fastboot flash splash splash.img
Click to expand...
Click to collapse
I understand that but I can't for the life of me get this to work on fastboot idk what I'm doing wrong I know how to use fast boot so I'm loat

rob420p said:
I understand that but I can't for the life of me get this to work on fastboot idk what I'm doing wrong I know how to use fast boot so I'm loat
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
What errors do you get from fastboot?

a1291762 said:
Do you have an unlocked bootloader?
What errors do you get from fastboot?
Click to expand...
Click to collapse
Unlocked custom rom when I type the commands its always saying no file

rob420p said:
Unlocked custom rom when I type the commands its always saying no file
Click to expand...
Click to collapse
So you don't have a splash.img then?

a1291762 said:
So you don't have a splash.img then?
Click to expand...
Click to collapse
I've downloaded them from this pafe

rob420p said:
I've downloaded them from this pafe
Click to expand...
Click to collapse
Is your phone in fastboot mode? Showing the rabbit with the blowtorch?
Do you have the fastboot program on your computer?

a1291762 said:
Is your phone in fastboot mode? Showing the rabbit with the blowtorch?
Do you have the fastboot program on your computer?
Click to expand...
Click to collapse
Yes I know all that.I got that

Ok, let's try something else. Here's what I see when I flash.
Code:
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ adb reboot bootloader
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot flash splash splash_stock_dark.img
Sending 'splash' (1460 KB) OKAY [ 0.080s]
Writing 'splash' OKAY [ 0.032s]
Finished. Total time: 0.159s
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
Can you please include what you see when you flash the splash image?

Chrono Leggionaire said:
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Click to expand...
Click to collapse
Hi great Dev can you explain me how to remove the " unlocked bootloader warn" whit your app? Sorry for my English thanks for your time and your work

rob420p said:
I've downloaded them from this pafe
Click to expand...
Click to collapse
taht is the correct comman as he said
fastboot flash splash splash.img

the system has been destroyed

Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
{
"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"
}
_20200214.0000.00_9.0_in_8e42c719e

Flash vbmeta file or try to move files to root directory.

shovan.cc said:
Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
_20200214.0000.00_9.0_in_8e42c719e
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.

if you solve the problem, here the vbmeta: https://mega.nz/#!bUwliDDS!PNCWo68avE9GsyK4JeJgV1zoVIiejh0-gIs1X6MCEPk

Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img

Thx.
CommieColin said:
Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img
Click to expand...
Click to collapse
Thanks For Your Suggestion.. & i Am done This flash Properly.

thank you
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
thank you you saved me

the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I am trying my best to perform this action and i cant

Janelas said:
I am trying my best to perform this action and i cant
Click to expand...
Click to collapse
All commands worked but stil stuck on fastboot

Janelas said:
All commands worked but stil stuck on fastboot
Click to expand...
Click to collapse
sorry for the late reply...after vbmeta is successful, did you flash recovery.img?? if after flashing recovery it doesn't enter recovery mode, press vol up + power button then check.

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?