Database Develop

[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)

Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.​
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -​Just for example - the script would be located in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"​And the firmware files would be in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"​4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P

Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.

Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"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"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post

amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.

bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work

Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!

los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"

bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.

Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0

los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.

bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?

los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.

bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.

los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!

bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.

los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.

bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com

los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.

Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!

los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.

.

Question [CLOSED] Pls help to fix: dm-verify corruption

For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
{
"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"
}
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?

fm663 said:
For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
View attachment 5458547
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?
Click to expand...
Click to collapse
Try with:
adb disable-verity
or flashing blank/null vbmeta:
fastboot --disable-verity flash vbmeta vbmeta.img or:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img

@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?

fm663 said:
@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?
Click to expand...
Click to collapse
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?

SubwayChamp said:
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?
Click to expand...
Click to collapse
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?

fm663 said:
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?
Click to expand...
Click to collapse
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.

SubwayChamp said:
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.
Click to expand...
Click to collapse
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way

fm663 said:
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way
Click to expand...
Click to collapse
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.

SubwayChamp said:
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.
Click to expand...
Click to collapse
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching

simika said:
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching
Click to expand...
Click to collapse
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you

fm663 said:
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you
Click to expand...
Click to collapse
sure:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
here you'll find answers about root, dm-verity and much more, always related to poco m3 pro and redmi note

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
If you want to stay locked no way to disable this warning message but if you decide to unlock your device and root it, it is pretty easy to fix it, one of the methods available is what I indicated, flashing a blank/null vbmeta through specific fastboot commands, there are other methods though, but this is the most universal and easy to use.
In regard to the CTS issue, I don't use GPay, so I can't tell you, but no better place that the Magisk Discussion Thread, it is the appropriate thread where you can find all the info from all the members affected on that, in the meantime you also can take a read on this https://droidholic.com/fix-safetynet-failed-cts-profile-false/

1. Hello friends, there are two ways to fix this problem. First, you need Root, and after using Root, you need to download any file manager and give Root permission. You need to backup your baseband, nvram nvdata nvcfg after backup Save, you also need an MTK Bypass You can search for MTK Auth Bypass Tool through Google. To download, you also need to use SP Flash to flash the machine. You need to download the official firmware package. You can download it through xiaomirom.com, download the corresponding version, and use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for the completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, but you have backed up. Boot through fastboot to unlock the BL lock, and proceed fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. congratulations your baseband is back, i am a newbie and my instructions are very Not comprehensive, such as where is the baseband position, but I have too many characters, I will list the baseband position. 2. Replace a new motherboard, all mobile phone problems are solved.
Hope to help you.

THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/how-to-get-rid-of-dm-verity-corruption-on-boot.4290677/
Regards,
shadowstep
Forum Moderator

General Journal: A brand new OPPO Find X3 Pro (UK/EE) - From new to clean de-bloated android (hopefully)

To start this journal I will begin by stating, I am not actually sure if it will be possible to finish this journal; from what I have read there can be quite a number of obstacles with international versions of the OPPO, some of which can be quite troublesome, but I thought it would be an interesting and hopefully helpful (for my self and anyone else wanting to do the same) way of going through the process with such a modern device.
The device arrives tomorrow, I wanted to get the initial post in without knowing precise details about the device.
I will update this primary post with the journal entries and post into the main thread when I update it going forwards
-- Entry 1 29/01/2022 00:21 (Dellivery today at some point!)
So far I have found out that cpw means car phone warehouse, which used(still is?) a store in the uk, 'EE' a network provider in the UK releases of the Oppo x3 find pro are apparently identical to releases from this store.
I have asked the user who informed me of this if they could possible put any information they are aware of within this thread.
Also, I will be doing the unboxing and initial looking at what it is via youtube I hope this is ok? I could not see a way to embed video onto this platform!
-- Entry 2 29/01/2022 10:53 (Delivery)
This is just a few images of the arrived device, simply unboxed and put on charge nothing has been set on the device what so ever.
{
"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"
}
Also note that this image showing the build number is by @alvydas it is not from my device yet! just some more information to add to the journal, this is believed to be the same as mine should show later on when I decide to video/start the phone up
Also for note the CPH (Possible related to CarPhoneWarehouse) prefix in the build number)
-- Entry 3 29/01/2022 13:11 (Turning on, Bootloader unlock, USB Debugging enabled)
Youtube video:
- May still be processing the HD version in google HQ!
-- Entry 4 30/01/2022 10:53 (Getting sorted)
Ok so we can't root it and we can't change the boot laoder .... however we can get novo launcher to start by default! The pro version at least!
Not exactly an amazing feat but hey its progress, I also removed the gmail mail application as I preffer outlook (mainly because I have 3 email accounts):
And boy .... you can really remove everything including:
130|OP4F57L1:/ $ pm uninstall --user 0 com.oppo.launcher
The coloros launcher its self X_X, so it seems you cannot get root, but there is no protected package, you can remove ANYTHING.
so this bodes the question .... other than wanting lineage OS of course, how thin can we get it ....
-- Entry 3 10/02/2022 10:53 (Hackery and cleaning)
.... So there is no fastboot on the international model, it is simply not there I even got EE them self to confirm this.
However, I have made some progress in discovering a way to get to the qualcomm flashable download mode, that is it will show up as a:
One of those (if you have the Qualcomm drivers installed), some information I put in the forum about this mode was this:
1) Turn the phone off (shutdown)
2) Hold the power button and the Vol up/down (I Forget which) down all the way through the phone starting, you will feel a little Bzzzzz
3) you will be presented with a menu probably in chinese, this is because you held down the power button and it auto selected the first language (its not a biggie), just press the back touch screen button in the top left <--
4) Select english (or chinese if you preffer!)
5) you will be presented with a menu that has 3 options, Format, Reboot, .... something else ...
6) Select none of the options! look to the bottom of the screen you will see a version mine was v12 o3 v1.2 - double tap this
7) you will get a warning you are entering 'customer service mode', and wallah .... you will get the device show up in device manager.
I was going to shoot a video of this, I still might! but its rather redundant at this point as I am now at a brick wall, I need to figure out how to deal with this mode, can I flash something to it .... how?
I am scrubbing the phone of all the bloatware I can and to be honest I have it pretty damn clean .... but still the fastmode is elusive and what else could be loaded onto this lovely phone.

Entry 1 added - nothing really important

Entry 2 added, initial unboxing simply for charging, video to come soon: looking for details!

The CPW in the build number is more of a guess than anything else we all could be wrong

alvydasd2 said:
The CPW in the build number is more of a guess than anything else we all could be wrong
Click to expand...
Click to collapse
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.

PaulGWebster said:
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
Click to expand...
Click to collapse
Yh that's fine

Entry 3 uploaded, many thanks @alvydasd2 We do have slightly different builds it seems!

So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this

Also have to figure out if all the fancy camera things will work with a custom rom, such as the microscope mode and all the advanced functionalities
Maybe the best initial tangent is to simply root the phone and remove any bloatware as well as installing novolauncher, followed by re-rooting it
That way I will not lose the ability to use the special camera functions and in turn still receive updates, I believe I can actually freeze certain packages too so they are effectively immutable, so they show up but can never run or be changed ... hmmm

PaulGWebster said:
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Click to expand...
Click to collapse
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle

alvydasd2 said:
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
Click to expand...
Click to collapse
Check the youtube video, I appear to have lol ... though I did notice that going into the recovery menu is all in chinese ... so I assume its the chinese version:

The only problem being ... I have no idea idea what this menu says -_-

I guess that is tomorrows episode though, connecting it via ADB+TWRP

Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that

alvydasd2 said:
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
Click to expand...
Click to collapse
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options

PaulGWebster said:
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
Click to expand...
Click to collapse
Oppo has a weird bootloader cuz it can only be unlocked with an app that only works on Chinese version and to access fastboot u need a unlocked bootloader

just read this .... so there is no way to even fastboot the device https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/

I wonder if you could flash on the chinese version of the firmware

it seems that the device is really a 'realme gt 5g' .... trying to verify this

PaulGWebster said:
it seems that the device is really a 'realme gt 5g' .... trying to verify this
Click to expand...
Click to collapse
It's not -_-

Question Update OnePlus 10 Pro from HydrogenOS (CN) to OxygenOS (EU/GL/IN) without rooting

This process uses Oxygen Updater as I haven't found the full EU/GL/IN stock ROMs anywhere else.
Update OnePlus 10 Pro NE2210 (CN) from HydrogenOS (NE2210_11_A.12) to OxygenOS EU (NE2213_11_A.12)
Download [Play Store] apk and install
[Play Store] install [Oxygen Updater]
[Oxygen Updater] Device: One Plus 10 Pro EU
[Oxygen Updater] Update method: Stable (full)
[Oxygen Updater] Settings > Advanced Mode - activate
[Oxygen Updater] Update > Download the full stock ROM (4.15 GB)
Activate Developer Options
Update > Local install
CURRENT STATUS: Verification failed
I've done this process before for other OnePlus phones and it was very straightforward. For some reason is not working with this OnePlus 10 Pro. Any insight on how to continue?
Thanks!

Bump, redownloaded again the EU version, resetted phone, still fails. Whyyy! Anyone can advise how to go from Hydrogen to Oxygen? Thanks!

Short description for "How to switch from ColorOS (Chinese version) to OxygenOS (IND/EU) on OnePlus 10 Pro". I did the flash under Windows 10, even if I'm usually a Linux guy...
BEFORE DOING THIS MANUAL, MAKE A BACKUP OF THE DATA OF YOUR DEVICE! Your phone will be DELETED completely!
1.)
- Download the desired ROM (Oxygen OS 12.1 A11 (IND) or Oxygen OS 12.1 A12 (EU) (Auntie Google has the answer, effective April 2022) -> extract
- download OnePlus_USB_driver.zip:
https://oneplususbdrivers.com/download-oneplus-usb-driver/ -> extract
- download Android Platform SDK:
https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062 -> extract
- download "Fastboot Enhance Tool": https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ -> extract
2.) First of all, disable driver signature check for Windows 10, because the OnePlus drivers are not signed (yet).
3.) After restarting Windows, install the OnePlus drivers by executing the .exe file from the extracted folder.
4.) Copy the payload.bin file from the downloaded ROM into the folder where the fastbootenhance tool is located
5.) Enable Developer Options on your phone
6.) Enter the Developer Options, enable OEM unlock and USB debugging there
7.) Now connect your OnePlus 10 Pro to your computer by a USB cable. Make sure it's started, screen unlocked and charged over 60%
8.) On your computer, open File Explorer and switch to the Android SDK folder. Click in the address line above and type CMD [Enter]. A CMD window opens in the SDK folder.
9.) In CMD, type "adb devices". A new line should appear with the encrypted name of your device. When an empty line is returned, check the driver installation. If this line returns the name, but the suffix "not allowed", you must first allow this connection ON YOUR PHONE. Disconnect and reconnect your device and confirm the popup that appears on your phone! (Best is to enable "Always allow connections from this computer"!)
10.) Now type "adb reboot bootloader" in CMD. Your telephone restarts automatically to bootloader mode. In this mode your phone should tshow you it's name and beside of some other information you don't need, that the bootloader is LOCKED.
11.) Type in CMD "adb flashing unlock [Enter]". Now your phone should restart and ask you, if you want to unlock the bootloader or do not unlock the bootloader. With the volume buttons, switch to "UNLOCK BOOTLOADER" and confirm by pressing the Power Button.
12.) After doing so, restart your phone. After rebooting, go back to CMD and type "adb reboot fastboot". Your phone now should restart to "FASTBOOTD MODE". You are asked to choose a language (I recommend english after all... ;-) )
13.) Open the "Device Manager" on your computer.
14.) If device manager shows you some unknown device like "Android: ! 'ossi'" or similar, your device is not recognized in fastbootd mode. In that case continue with pt. 15. Otherwise continue with pt. 19
15.) Right-click on the unknown Android device and choose "Update driver..." -> "Search my computer for drivers" -> "Pick from a list of available drivers on my computer"
16.) When OnePlus drivers where installed correctly some steps above, Device Manager should suggest you 3 different possible drivers. Choose "OnePlus ADB Interface Manager" and confirm your choice. Windows will warn you that a wrong choice will crash Windows. Confirm also this warning.
17.) If everything went good, the before unknown device will change to an Android ADB Interface Device. When that happend, everything is good and you're good to go on.
18.) Just to be really sure: Type in CMD again "fastboot devices" and your computer should tell you the s/n of your phone with the suffix "fastboot". This will tell you your device is recognized in fastboot mode.
19.) Start "FASTBOOTENHANCE" tool from the respective folder (Folder name "release")
20.) Now you can follow the instructiions here at pt. 8.:
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
Puuuuuuh! That was enoying..! Maybe I have missed something... If so, please tell me by PN and I will complement this manual. But at this time, I guess it should work. I did it right like that this day - and it works fine! Finally I have my foremost chinese OP10Pro with a EU ROM in (swiss) german!
And if it works just like that (after my manual), please let me know as well!
Have fun! Oliver
Oh, there's something I forgot: I had after flashing still about a dozen of chinese apps I had to delete manually. Don't be surprised by that!

Thank you! Can you relock the bootloader afterwards? What model shows in the phone info screen?

This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?

Lynxy0 said:
This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?
Click to expand...
Click to collapse
If you relock the bootloader and reset, does it behave like a normal non-rooted phone with EU firmware?

Ultimatum99 said:
If you relock the bootloader and reset, does it behave like a normal non-rooted phone with EU firmware?
Click to expand...
Click to collapse
Good shout - Let me try that and get back to you.

Yes, this worked

Lynxy0 said:
Yes, this worked
Click to expand...
Click to collapse
Did the Chinese apps disappear once you locked the bootloader and resetted? Which method did you use to relock? What model is being shown in the phone info page? Thanks!!!

No they did not. After the first flash, the OP Launcher was back (previously it was Google Phone Launcher) . I factory reset and Chinese apps were back.

Ultimatum99 said:
Thank you! Can you relock the bootloader afterwards? What model shows in the phone info screen?
Click to expand...
Click to collapse
Hi Ultimatum99
I didn't relock my bootloader yet, but I'll do it in the next days, I'll post the update here. (Speaking technically it's possible, yes, but I don't know yet what happens...) And my model shows "NE2213" after the update.

Lynxy0 said:
This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?
Click to expand...
Click to collapse
Hi Lynxy0
No, your phone is not rooted, but the bootloader is still unlocked, even after the update. And that means your phone is vulnerable to attacks from outside. So Google Pay tells you your phone is rooted, just to keep you safe. Try to relock your bootloader, this should solve the problem. (I didn't do it yet, but I'll post the update when I've done it.)

Lynxy0 said:
Yes, this worked
Click to expand...
Click to collapse
Haha... I was too late then!(See my last replay...) But thanks for the feedback!

Lynxy0 said:
No they did not. After the first flash, the OP Launcher was back (previously it was Google Phone Launcher) . I factory reset and Chinese apps were back.
Click to expand...
Click to collapse
This is unfortunately a bad thing... Some chinese apps are really back, even after flashing and resetting the device. But I could delete them manually. Yeah, it took me a few minutes, but at least, I had (finally) my beloved OxygenOS back! (After I crashed my OP6T almost 2 years ago, I chose a Oppo FindX 2 Pro - and after almost 2 years I still regret to have paid for this phone... The hardware was really cool, but ColorOS is ... So I was really terrified when I learned my brand new [chinese] OP10Pro had ColorOS installed by default..!)

Loba74 said:
This is unfortunately a bad thing... Some chinese apps are really back, even after flashing and resetting the device. But I could delete them manually. Yeah, it took me a few minutes, but at least, I had (finally) my beloved OxygenOS back! (After I crashed my OP6T almost 2 years ago, I chose a Oppo FindX 2 Pro - and after almost 2 years I still regret to have paid for this phone... The hardware was really cool, but ColorOS is ... So I was really terrified when I learned my brand new [chinese] OP10Pro had ColorOS installed by default..!)
Click to expand...
Click to collapse
Let us know if you manage to relock the bootloader and share the full process please, I can update the guide with your findings. Thanks!

Loba74 said:
Hi Lynxy0
No, your phone is not rooted, but the bootloader is still unlocked, even after the update. And that means your phone is vulnerable to attacks from outside. So Google Pay tells you your phone is rooted, just to keep you safe. Try to relock your bootloader, this should solve the problem. (I didn't do it yet, but I'll post the update when I've done it.)
Click to expand...
Click to collapse
It was pretty straight forward, unroot by uninstalling Magisk. adb into the bootloader and send the adb bootloader lock command, then boom, its locked. It wipes your phone in doing so, so you will have to everything again.

Lynxy0 said:
It was pretty straight forward, unroot by uninstalling Magisk. adb into the bootloader and send the adb bootloader lock command, then boom, its locked. It wipes your phone in doing so, so you will have to everything again.
Click to expand...
Click to collapse
Thanks @Lynxy0
So, just to clarify, after relocking the bootloader (which causes a full wipe) Google Pay works again?
Also, do you know if Netflix installs after relocking the bootloader? (Because in most phones once the bootloader is unlocked the status changes from "L1" and doesn't change back again after locking. Netflix reads that status, and Netflix will only install if it is L1.)
Many thanks

Hi Guys
It seems like a straight forward process, It was all good until I try flash it. . When I loaded the downloaded zip file, I couldn't get the payload file in fastbootd and flash it those buttons are missing(after I load it to payloadDumper .) . I thought it might be file download has some issue. I tried different ones , the same thing.
any ideas?
{
"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"
}
C.

never mind , I figured it out . My case is the ADB driver problem , even u unlocked the bootloader , somehow the fastbootenhance wont work correctly , strange , ... but.
C

@Loba74 I think there is an error in your guide, in step 11 maybe it should say "fastboot flashing unlock" rather than "adb flashing unlock" ?

Question Cannot register a new fingerprint in OnePlus 10 PRO

Hi
I bought a new OnePlus 10 PRO from Aliexpress. Its a CH version that the seller installed on it a global rom.
In the first setup of the phone, When I get to setting the fingerprint, I am unable to set it. I get the following:
{
"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"
}
I tried updating the phone, I tried factory reset... its always the same.
Any idea?
Thanks !

Are you sure that he installed the global rom? With model is yours NE2213 ? I bought from them also but I don't have this issue.
Anyway, you can try to use Oxygen Updater, to check if there is an update for your device or since your device is reseted, you can install ColorOS back

Hi,
I am on NE2215. Using Oxygen Updater I see that I have the most up to date version.
Not sure exactly how to install ColorOS.. I do want to have the regular OS that I would have as if I bought the global version (which i guess this is what the global rom mean..)

Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.

ok, and now for someone that have no idea how to do it?

If yours is NE2215 A13 you can download the ota file from this link: https://android.googleapis.com/packages/ota-api/package/7548d30abac02bde85a403bcc3a218df868e1910.zip
Then put it in your phone root and from your device Settings -> About the device -> Click on the option to check for the update -> 3 dots menu -> local installation and chose this package. It will start the installation.

Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
What am I missing?

I think it's obvious that something went wrong during the region change, this issue was prevalent on the 8 pro and was extremely difficult to fix.
Check out the 8 pro threads you'll be sure to see it. It's a partition iirc and if it's borked then it simply will not work..
I can't remember the name of it off hand but have a look and I'm sure you can get an idea of what may be wrong, specifically that partition.
Overall it's difficult to say as you've got a region changed phone, have you asked the seller what they did? If it is indeed as difficult as it was on the 8 pro to fix and seeing as you may be the only person experiencing this (far as I know) then I'd consider returning it.
You could re-flash the entire OS via fastboot enhance but that would also bring with it inherent problem's, if it's new then I guess the question you need to ask yourself is it worth it?
Did you save much money getting that converted variant?

dkaro said:
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
View attachment 5624305
What am I missing?
Click to expand...
Click to collapse
This page is from android play services. You need to click on the first banner

@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless

If that is the page showing I'm assuming you're on a gsi ROM and not oxygen os.
Now it's better to reinstall OxygenOS completely because it doesn't seem to be the ROM you're running.
Search here on xda to unlock your bootloader and then you need to find the zip with the full ROM for you device and install it from fastboot as mentioned.

OK, i'm trying to unlock my bootloader but as I mentioned:
dkaro said:
and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
Click to expand...
Click to collapse
Any idea what am I doing wrong?
I tried several tutorials online and so far I found no tutorial that will actually give me step by step that each step is actually working..

Maybe it's missing the drivers. Try this https://gsmusbdriver.com/oneplus-10-pro

dkaro said:
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
Click to expand...
Click to collapse
I feel you buddy.
You can use the app in my Magisk guide to do local installs.
Unlocking the bootloader you need to type fastboot flashing unlock
I haven't had to change region myself, but I did make a thread for someone else where the process was listed, think I called it changing Chinese firmware iirc.
If it's just a case of a re-flash of the firmware you're on, it's not that difficult.
Just use oxygen updater and grab the full firmware then do the local update using the app I mentioned above (listed in my Magisk/root guide)
I've never done this when not having the bootloader unlocked personally, but you can unlock and that'll wipe your phone with the recovery already on your device.
Only issue I have going down these routes is what else is missing? Do any of these processes stand up if we can't rely on the integrity of the OS that someone has put on and made a balls of it?
Sorry I know you may not agree but 30% is a small price to pay to avoid a brick and bring stability..
But that's me

zopostyle said:
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
Click to expand...
Click to collapse
That is a seriously good shout and would explain the fingerprint.

Hi guys, thank you again for helping me.
I tried installing again the uSB drivers, and ran again "fastboot flashing unlock" - it still telling me:
As far as I understand I have to unlock it for next step, right? (either for resetting back to colorOS or reinstalling oxygen)
I will try later tonight the other method (this magisk thing) - is this the link you're talking about?
Can you please also give me a link to download the full most up to date global Oxygen version and the CH Color one? i'll try both
Thanks !

For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585

zopostyle said:
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
Click to expand...
Click to collapse
Really is odd about them not being full... They're massive compared to conventional incremental updates. 4.05GB that's a hell of an incremental.
Haven't had to do it myself and it's sightly off topic but is the full version you'd use to recover a phone albeit without a functional MSM?
So fastboot flashing?
Cheers

Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?

dkaro said:
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
View attachment 5624521
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
Click to expand...
Click to collapse
As @zopostyle said earlier.. you'd need to use 12 mate. As that's the only full version available...13 won't cut it...you can extract the images using the button that says allow incremental, that's useful for extracting boot images for rooting.
But there's a reason why that's there, it's so you don't go ahead and flash it.... According to @zopostyle 12 is the only full version so that's what you would need.
Again I've not done this myself so perhaps wait for someone else to chime in what to do next.