Database Develop

[GUIDE] Flash SBF to Motorola Atrix 4G

WARNING
DO NOT FLASH ON BELL ATRIX
​If you appreciate this guide, please visit my website (maybe check out my sponsors!), subscribe on Twitter, press the thanks button below, or donate to Fixter, DesignGears, Fenny and other great helpers/devs for the Atrix 4G.
Download
1.2.6
http://bandbinnovations.com/Atrix.7z
Password: atrixbl
1.5.2
HTTP (Rename from .rar to .gz)
HTTP (Rename from .rar to .gz)
MultiUpload
Hotfile.com
DepositFiles
UPDATE: Linux SBF guide here --> http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html --> Thank you "relaxed"
Flash Guide (Instructions)
Prerequisites
Download RSDLite 5.0 (MediaFire mirror)
Install the program
Download SBF file from above links
Bricked phone or test device
Fully charged device
Drivers installed (if you rooted your phone, your computer has the necessary drivers)
32-bit
64-bit
Problems
Some users experiencing WiFi connectivity weirdness
SIM-unlocked devices may still have WiFi problems
Market might not show all applications (easy fix on the way)
Do not flash this file unless absolutely necessary. It will help those who’ve bricked their device to recover, but this is not for flashing just for fun. BriefMobile cannot be held responsible for device damage due to this guide.
Make sure your phone is turned off
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Load up the SBF file
The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .gz file on your computer
Plug your device into your computer
Use the USB ports on the back side of your computer for safety
RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
Press the “Start” button
Be patient while the phone reboots. It will take a long time.
Congratulations!

Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.

designgears said:
Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.
Click to expand...
Click to collapse
Good tip! Didn't know that!

Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?

tianqi said:
Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?
Click to expand...
Click to collapse
Yes. This isn't a confirmed issue, but others have experienced WiFi problems with this SBF flash over their SIM unlocked devices.

Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.

cellzealot said:
Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.
Click to expand...
Click to collapse
That's very odd. Mine most definitely shows as "NS Flash Olympus."

im a noob sorry, but what does this actually do?

fRenZy-_- said:
im a noob sorry, but what does this actually do?
Click to expand...
Click to collapse
If you mess around with your device and break it, this can save your life by unbreaking it!

I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.

kennethpenn said:
That's very odd. Mine most definitely shows as "NS Flash Olympus."
Click to expand...
Click to collapse
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.

cellzealot said:
I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.
Click to expand...
Click to collapse
Thanks for the info! Duly noted... editing the post.

jimmydafish said:
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.
Click to expand...
Click to collapse
100% positive I purchased my device retail. I'll screenshot the RSD Lite for you in a moment when I recover from my soft brick (screwed up framework-res).

RSD Lite reports "NS Flash" for me too
{
"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"
}
purchased through Amazon

kmiller8 said:
RSD Lite reports "NS Flash" for me too
purchased through Amazon
Click to expand...
Click to collapse
Perhaps "NS Flash" does not mean developer phone on the Atrix?

kennethpenn said:
Perhaps "NS Flash" does not mean developer phone on the Atrix?
Click to expand...
Click to collapse
Or maybe we both got incredibly lucky is there any way to further verify if RSD Lite is reporting incorrectly?
Also off topic, why is the "Start" grayed out for me?

mine also says NS, purchased directly from AT&T
start is greyed out if there is no file/an incorrect file to flash, notice that the file properties pane is blank, it has not actually loaded the file in the select box in that screenshot

Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
Mainly just recovers you from a soft-bricked or improperly hacked device. It flashes you back to stock (or as close to stock as we have right now.)
No new features. No bug fixes. Nothing different from stock except a few new possible issues.

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
It changes some stuff, but I can hardly see anything different at face value.

Unbricking "Service Required Code Corrupt"

If you use "xFSTK-SoC-Driver-Setup" and "unbrick.bat" to "Unbrick your phone, and you got the "Service code corrupt" error..., This method is untested but i think it is the problem...​You need This:
Original ICS FIRMWARE that come with your phone.
xFSTK-SoC-Driver-Setup Installed (read How Install "xFSTK-SoC-Driver-Setup")
Unbrick.bat and respective folders.
Motorola Handset USB Drivers (x86 or x64).
ADB/ FASTBOOT or SDK.
Steps to revive:
Extract Unbrick.zip in "C:\atomSOC"
Go to unbrick folder. "C:\atomSOC\unbrick"
Go to your firmware folder and copy this files (dnx; ifwi)
Replace this files in "C:\atomSOC\unbrick".
Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
Run unbrick.bat in "C:\atomSOC"
How Install "xFSTK-SoC-Driver-Setup":
Run Setup
When Say "Intel Soc Is about to begin" Click OK
When Say "In Order to Complete (...) Will a device be attached (...)" Press Yes.
When Say "Step 1 (...)" Plug In your USB Cable to the pc. and click ok
When Say "Step 2 (...)" Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
¿How know if my phone go to the medfield flash method?
release the camera button, your phone will stay in a black screen with the green led.
And your pc says "New hardware recognized"
Name of hardware: MEDFIELD
Before the driver install:
{
"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"
}
Downloads:
Unbrick.bat + xFSTK-SoC-Driver-Setup Download
If it works.. please, let me know​

Nope.
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen

1994deano said:
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen
Click to expand...
Click to collapse
Try again, your phone is not going to medfield flash mode correctly

I did not get the part - Go to your firmware folder and copy this files (dnx; ifwi)
How to go to firmware folder?,
I do not understand how to copy

i just re tried it and its got rid of the service required screen but now the screen is just black with the green led on

Me too samething, any sugestion?

gmpdri said:
Me too samething, any sugestion?
Click to expand...
Click to collapse
csn you boot to bootloader?? (power+vol.down)?

Nope
pangyaaaaaa said:
csn you boot to bootloader?? (power+vol.down)?
Click to expand...
Click to collapse
no that is why we are trying to use the medfield flash, as the bootloader is screwed up

1994deano said:
no that is why we are trying to use the medfield flash, as the bootloader is screwed up
Click to expand...
Click to collapse
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...

Boss442 said:
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...
Click to expand...
Click to collapse
ooh nice, let us know how you get on with it

S***, REALLY GOOD NEWS.....
RDS recognizes your phone on Medfield Mode...
Someone try to flash a firmware
Flashing Firmware dont work... ¿Maybe a custom XML Work?

HELP
For that ADB / Fastboot or SDK.?
Copying pro firmware?

saiko.sensei said:
For that ADB / Fastboot or SDK.?
Copying pro firmware?
Click to expand...
Click to collapse
if i found a way for bypass the "service required" error.. maybe you need fastboot... I am working with a lenovo pad (Intel SoC) maybe can use his flash tool to work (need fastboot). But dont recognize my phone, ¿Maybe need a custom driver? i am working in that

Yes, RSD lite recognises bricked phones, but it tries to enter fastboot mode to flash anything, so we're stuck...
Good luck!

Bricked while flashing JB Radio to ICS
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.

Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.

mercurio. said:
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.
Click to expand...
Click to collapse
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
SharpnShiny said:
Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.
Is your phone bricked in this condition right now? If it is, feel free to PM me.
Click to expand...
Click to collapse
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.

Boss442 said:
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.
Click to expand...
Click to collapse
I found out that the tool I ment is the xFSTK-Downloader ( rghost.net/44421368 ) that was alreaddy linked here at xda by U1138 in: http://forum.xda-developers.com/showthread.php?t=2184877
And yes, i suppose the black screen only and the service required brick are the same. they probably are due to a not working combination of firmware (ifwi & dnx) and flashed OS (i suppose the fastboot, no idea how where to get the dnx file needed for flashing it). you can try different ifwi and dnx files and get different results (so far i think there are only two types, the ones for JB fw and the others for ICS).
If you flash your rom with RSD going from JB to ICS you also flash the ifwi & dnx files, but not the bootloader. Therefore you end up with a non working combination of firmware (ifwi) and OS (fastboot) => nothing starts at all.
This problem was easy to fix for me flashing the appropriate JB firmware.
Then I did the mistake of flashing the JB radio before flashing a JB rom. This lead to a situation where neither the JB (leads to service required warning) nor the ICS (black screen, green led on) firmware works anymore and I have no idea how i could change the situation.
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?

mercurio. said:
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?
Click to expand...
Click to collapse
+ 1
Everything else I was try with U 1138`s help - without result

St.Noigel said:
+ 1
Everything else I was try with U 1138`s help - without result
Click to expand...
Click to collapse
I read more than 120 pages in forums, and... NOTHING!
But i'm triyng to port a "flash tool" from lenovo pad... :silly:

[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.

.

Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL

Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?

AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers

Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?

OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.

AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck

Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?

AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck

OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"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"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.

AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers

Ok, definitely will do that. Thank You very much for Your help

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.