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.

.

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.

Question Flash Error - now phone won't switch off and continually restarts

Having flashed a Redmi Note 9 and a Redmi 9A, I tried to flash my Redmi 10 5G.
I unlocked the phone and proceeded to use MIFlash to flash the phone - the phone was recognised and the flashing began.
{
"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"
}
After about 12 mins the tool displayed a timeout error
When I disconnected the phone it went into a 'boot loop' continually displaying the startup logo, then restarting again and I cannot switch the phone off.
I can use the power and volume down key to get back to fastboot (but the fastboot logo has gone and the word Fastboot is displayed on its own).
If I try to flash again, it sees the phone and starts to flash, but once again times out.
If anyone has any suggestions to resolve this I would appreciate them.
NOTE: The phone had the global ROM and I am trying to flash the Indonesian rom to have call recording - like I did on the other 2 phones.

pewe said:
Having flashed a Redmi Note 9 and a Redmi 9A, I tried to flash my Redmi 10 5G.
I unlocked the phone and proceeded to use MIFlash to flash the phone - the phone was recognised and the flashing began.
Click to expand...
Click to collapse
Can you post the Miflash log?

Here they are

pewe said:
Here they are
Click to expand...
Click to collapse
I don't understand you say " I tried to flash my Redmi 10 5G(code name LIGHT)" and you flash a rom for a Redmi note 10 5g (camellia).

NOSS8 said:
I don't understand you say " I tried to flash my Redmi 10 5G(code name LIGHT)" and you flash a rom for a Redmi note 10 5g (camellia).
Click to expand...
Click to collapse
My mistake - I should have said it is a Redmi Note 10 5g

pewe said:
My mistake - I should have said it is a Redmi Note 10 5g
Click to expand...
Click to collapse
Ok try to flash the rom without Miflash https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/post-84843979

or try with this tool for Mediatek https://xiaomitools.com/sp-flash-tool-en/

NOSS8 said:
Ok try to flash the rom without Miflash https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/post-84843979
Click to expand...
Click to collapse
I'm probably missing something, but when I run flash_all.bat the following is what I get

pewe said:
I'm probably missing something, but when I run flash_all.bat the following is what I get
Click to expand...
Click to collapse
a lot of problem with Mediatek devices.
did you install the drivers with Miflash?
Check here that everything is ok. https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
or
Try with https://xiaomitools.com/sp-flash-tool-en/
or
a newer or older version of Miflash
Always run in administrator

[23:14:57 9c758f3b]:MiFlash 2020.3.14.0
[23:14:57 9c758f3b]:vboytest index:1
[23:14:57 9c758f3b]:idproduct: 53261 idvendor: 6353
[23:14:57 9c758f3b]:Thread id:9 Thread name:9c758f3b
[23:14:57 9c758f3b]:image path:E:\F2\prog\MiFlash2020-3-14-0\curtana_global_images_V11.0.11.0.QJWMIXM
[23:14:57 9c758f3b]:env android path:"E:\F2\prog\MiFlash2020-3-14-0\Source\ThirdParty\Google\Android"
[23:14:57 9c758f3b]:script :E:\F2\prog\MiFlash2020-3-14-0\curtana_global_images_V11.0.11.0.QJWMIXM\flash_all.bat
This is a Miflash log and you will notice that the rom name appears outside your log there is none as if you did not decompress the TGZ file.

NOSS8 said:
[23:14:57 9c758f3b]:MiFlash 2020.3.14.0
[23:14:57 9c758f3b]:vboytest index:1
[23:14:57 9c758f3b]:idproduct: 53261 idvendor: 6353
[23:14:57 9c758f3b]:Thread id:9 Thread name:9c758f3b
[23:14:57 9c758f3b]:image path:E:\F2\prog\MiFlash2020-3-14-0\curtana_global_images_V11.0.11.0.QJWMIXM
[23:14:57 9c758f3b]:env android path:"E:\F2\prog\MiFlash2020-3-14-0\Source\ThirdParty\Google\Android"
[23:14:57 9c758f3b]:script :E:\F2\prog\MiFlash2020-3-14-0\curtana_global_images_V11.0.11.0.QJWMIXM\flash_all.bat
This is a Miflash log and you will notice that the rom name appears outside your log there is none as if you did not decompress the TGZ file.
Click to expand...
Click to collapse
I did extract the TGZ - so not sure what happened. Is there a particular directory structure for storing and running the files - this is the path where the extracted TGZ content is held and it is all there - C:\redmi10\flashtool\MiFlash20220218\rom\ - reflected in the logs. But there is no reference in the logs to the 'flash_all.bat'.

pewe said:
Having flashed a Redmi Note 9 and a Redmi 9A, I tried to flash my Redmi 10 5G.
I unlocked the phone and proceeded to use MIFlash to flash the phone - the phone was recognised and the flashing began.
View attachment 5676565
After about 12 mins the tool displayed a timeout error
View attachment 5676569
When I disconnected the phone it went into a 'boot loop' continually displaying the startup logo, then restarting again and I cannot switch the phone off.
I can use the power and volume down key to get back to fastboot (but the fastboot logo has gone and the word Fastboot is displayed on its own).
If I try to flash again, it sees the phone and starts to flash, but once again times out.
If anyone has any suggestions to resolve this I would appreciate them.
NOTE: The phone had the global ROM and I am trying to flash the Indonesian rom to have call recording - like I did on the other 2 phones.
Click to expand...
Click to collapse
WELLLLL!! i THINK ITS TIME FOR A NEW phone.because is most likely broke or old to the point it doesn't work that's all i have to say right now but notify me when there's an update on whats happening.

koryonp10 said:
WELLLLL!! i THINK ITS TIME FOR A NEW phone.because is most likely broke or old to the point it doesn't work that's all i have to say right now but notify me when there's an update on whats happening.
Click to expand...
Click to collapse
I hope not - it's only 2 weeks old.

koryonp10 said:
WELLLLL!! i THINK ITS TIME FOR A NEW phone.because is most likely broke or old to the point it doesn't work that's all i have to say right now but notify me when there's an update on whats happening.
Click to expand...
Click to collapse
send me your broke phone simy you have flashed a wrong firmware. is not a mediatek issue. simply you have made a lot of useless procedures for recover it. and the result is a soft brick. reflash the right firmware have should solve your problem. but if u can enter into fastboot, you can easy unbrick your phone. but if u want to trash, i give u my adress. send to me , two phones could be helpfull my phone is the same of yours. i have updated frim 12 to 12.5 to 13. rooted and unrooted at least five times. zero bricks. ia the best phone i ever buyed

pewe said:
I hope not - it's only 2 weeks old.
Click to expand...
Click to collapse
try with a newer or older version of Miflash
or
Try with https://xiaomitools.com/sp-flash-tool-en/

NOSS8 said:
try with a newer or older version of Miflash
Click to expand...
Click to collapse
Thanks for all your input - the problem is now solved.
Although I could not switch the phone off, if I caught it right between reboots I could get it into fastboot mode.
I then, as you suggested, tried an older version of MIFlash with current versions of MIUI 13 - both the Indonesian and then the Global ROMs - with no luck. Same problem with bootloop and unable to switch off the phone.
I then tried again with an older version of the Indonesian ROM. It finished with a timeout error again, BUT this time I could re-boot the phone and there it was, fully installed V12 of the ROM.
Once I set up the phone, an update of the Indonesian ROM was notified, and I managed to update with no problem and I now have what I wanted, the latest MIUI with call recording capability.
So although not as smooth a process as I experienced with the other 2 phones, I got there eventually.

Of course the xiaomi with soc Mediatek are less expensive than those in Qualcomm but there is little or no development for these phones and what is a routine with a Qualcomm sometimes turning into an obstacle course with a Mediatek.

May be of interest to you
https://www.patreon.com/xiaomieu

pewe said:
Thanks for all your input - the problem is now solved.
Although I could not switch the phone off, if I caught it right between reboots I could get it into fastboot mode.
I then, as you suggested, tried an older version of MIFlash with current versions of MIUI 13 - both the Indonesian and then the Global ROMs - with no luck. Same problem with bootloop and unable to switch off the phone.
I then tried again with an older version of the Indonesian ROM. It finished with a timeout error again, BUT this time I could re-boot the phone and there it was, fully installed V12 of the ROM.
Once I set up the phone, an update of the Indonesian ROM was notified, and I managed to update with no problem and I now have what I wanted, the latest MIUI with call recording capability.
So although not as smooth a process as I experienced with the other 2 phones, I got there eventually.
Click to expand...
Click to collapse
pewe said:
Thanks for all your input - the problem is now solved.
Although I could not switch the phone off, if I caught it right between reboots I could get it into fastboot mode.
I then, as you suggested, tried an older version of MIFlash with current versions of MIUI 13 - both the Indonesian and then the Global ROMs - with no luck. Same problem with bootloop and unable to switch off the phone.
I then tried again with an older version of the Indonesian ROM. It finished with a timeout error again, BUT this time I could re-boot the phone and there it was, fully installed V12 of the ROM.
Once I set up the phone, an update of the Indonesian ROM was notified, and I managed to update with no problem and I now have what I wanted, the latest MIUI with call recording capability.
So although not as smooth a process as I experienced with the other 2 phones, I got there eventually.
Click to expand...
Click to collapse
I was sure you would solve it, nice news!

Question [SOLVED] cant get past thru Mi account verification

hi everyone,
i was wiping data off my redmi note 10 5g, i was completely aware about the mi account lock (this):
{
"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 to log in then it let me in into setup wizard and immediately reappeared the same screen of the mi account lock. So, I basically put the right verification code and credentials of my MI Account and it wouldnt let me in to setup my phone.
I tried logging in more 3 times and the same thing over and over again, I even tried flashing a GSI just to realize the mi account lock is either connected to the phone's IMEI - as i have read somewhere in xda - or whatever Xiaomi decided to make up in their heads.
This has happened to me when I did the same thing - and the most weird thing is that, few months ago, I was testing a GSI coming from miui with my MI account, and then reflashed MIUI back again and no MI account lock popped up, being the same account since I ever got the phone, even though I tried to flash a GSI to see if it would solve it.
I even locked it by trying out the Find My Device and it let me in perfectly fine.
And yes, this has unlocked bootloader, but the 2 phrases above also was when I had it unlocked, and even with root.
I dont know what to do anymore, recovery flashing just doesnt work too, it doesnt detect my device, and I please ask for some help to be fast too, I appreciate it.

1lopes said:
hi everyone,
i was wiping data off my redmi note 10 5g, i was completely aware about the mi account lock (this):
View attachment 5721901
I tried to log in then it let me in into setup wizard and immediately reappeared the same screen of the mi account lock. So, I basically put the right verification code and credentials of my MI Account and it wouldnt let me in to setup my phone.
I tried logging in more 3 times and the same thing over and over again, I even tried flashing a GSI just to realize the mi account lock is either connected to the phone's IMEI - as i have read somewhere in xda - or whatever Xiaomi decided to make up in their heads.
This has happened to me when I did the same thing - and the most weird thing is that, few months ago, I was testing a GSI coming from miui with my MI account, and then reflashed MIUI back again and no MI account lock popped up, being the same account since I ever got the phone, even though I tried to flash a GSI to see if it would solve it.
I even locked it by trying out the Find My Device and it let me in perfectly fine.
And yes, this has unlocked bootloader, but the 2 phrases above also was when I had it unlocked, and even with root.
I dont know what to do anymore, recovery flashing just doesnt work too, it doesnt detect my device, and I please ask for some help to be fast too, I appreciate it.
Click to expand...
Click to collapse
Just in case, you should connect to the Wi-Fi. and then activate your Mi account, the Mobile data doesn´t work.
Open Mi account in a PC, and check if you are not missing something.

Connect tu eifi, and after insert mi password. Is simply

its not about that. i cant verify it, I put the right code, my mi account credentials, and it doesnt work. it just re-appears the same screen after I do everything right, even changed my mi account password 3 times, verified both with phone and email
check the gif for example below
https://imgur.com/a/VVZ7zaH
(its imgur and only the gif just for you guys to understand)

1lopes said:
its not about that. i cant verify it, I put the right code, my mi account credentials, and it doesnt work. it just re-appears the same screen after I do everything right, even changed my mi account password 3 times, verified both with phone and email
check the gif for example below
https://imgur.com/a/VVZ7zaH
(its imgur and only the gif just for you guys to understand)
Click to expand...
Click to collapse
Sign in Xiaomi/Mi account, go to /Signing in and Security/Manage Devices/Your device, then click on it, and Delete device, you will sign in out from your Xiaomi account, and you have to restart your device.
Just keep in mind, that the same that it could be, actually happening, if your device was linked to another Mi account, in the past, being for a previous user, or the seller did need to unlock it by any means, it won't work, otherwise, definitely, it has to work.

SubwayChamp said:
Sign in Xiaomi/Mi account, go to /Signing in and Security/Manage Devices/Your device, then click on it, and Delete device, you will sign in out from your Xiaomi account, and you have to restart your device.
Just keep in mind, that the same that it could be, actually happening, if your device was linked to another Mi account, in the past, being for a previous user, or the seller did need to unlock it by any means, it won't work, otherwise, definitely, it has to work.
Click to expand...
Click to collapse
nope, sadly no work, it had the device on my mi account but even after removing it, it did the same thing where I verified and it would reapper the same screen.
this is the only account of xiaomi i have, that ive ever used since i first got this phone, and it wasnt bought from anyone nor even used (i dont know where it was bought tho since it was a gift, but it came with the box and everything in it normally and was never mi locked)

1lopes said:
nope, sadly no work, it had the device on my mi account but even after removing it, it did the same thing where I verified and it would reapper the same screen.
this is the only account of xiaomi i have, that ive ever used since i first got this phone, and it wasnt bought from anyone nor even used (i dont know where it was bought tho since it was a gift, but it came with the box and everything in it normally and was never mi locked)
Click to expand...
Click to collapse
Check the IMEI from the box, and compare with https://www.mi.com/global/verify/#/en/tab/imei, if the model is the same as it is supposed to.
Try to go to recovery mode, for that, power off device, then press volume up + PWR buttons, and wipe data, see if it helps.

SubwayChamp said:
Check the IMEI from the box, and compare with https://www.mi.com/global/verify/#/en/tab/imei, if the model is the same as it is supposed to.
Try to go to recovery mode, for that, power off device, then press volume up + PWR buttons, and wipe data, see if it helps.
Click to expand...
Click to collapse
it is the same model and i know about it, also wiping data does absolutely nothing, did it over 3 times, this is probably connected to the phone's imei or whatever. its probably unrecoverable without going to a service center anyways or using a GSI rather than miui.
wonder why your solution to remove the device from my mi account didnt work, even after verifying its the same.
anyways, ill see what i can do with it, unless you or someone else can get it to work, would be alot thankful, but dont go out there looking for it as probably most of what you can find probably I have used to do it, so yea leaves us with little to no options in the end afterall and solution is either go to the service center.
thanks alot for the help tho, appreciate it

1lopes said:
it is the same model and i know about it, also wiping data does absolutely nothing, did it over 3 times, this is probably connected to the phone's imei or whatever. its probably unrecoverable without going to a service center anyways or using a GSI rather than miui.
wonder why your solution to remove the device from my mi account didnt work, even after verifying its the same.
anyways, ill see what i can do with it, unless you or someone else can get it to work, would be alot thankful, but dont go out there looking for it as probably most of what you can find probably I have used to do it, so yea leaves us with little to no options in the end afterall and solution is either go to the service center.
thanks alot for the help tho, appreciate it
Click to expand...
Click to collapse
The only thing I can think of, is that, some kind of protection was triggered, after a non-authorized action to the user side. Also, the vendor partition could get corrupt, after flash other image.
With this tool, https://github.com/bkerler/mtkclient you should back up every partition, it doesn't matter super image, and data also occupy a lot of space.
After backup every partition, try erasing the FRP partition, and try to boot.

SubwayChamp said:
The only thing I can think of, is that, some kind of protection was triggered, after a non-authorized action to the user side. Also, the vendor partition could get corrupt, after flash other image.
With this tool, https://github.com/bkerler/mtkclient you should back up every partition, it doesn't matter super image, and data also occupy a lot of space.
After backup every partition, try erasing the FRP partition, and try to boot.
Click to expand...
Click to collapse
Thanks for that one, seems risky, right?
Ill see if i can, since ive sent it to someone i know of, idk if i have it since im not home rn.

SubwayChamp said:
The only thing I can think of, is that, some kind of protection was triggered, after a non-authorized action to the user side. Also, the vendor partition could get corrupt, after flash other image.
With this tool, https://github.com/bkerler/mtkclient you should back up every partition, it doesn't matter super image, and data also occupy a lot of space.
After backup every partition, try erasing the FRP partition, and try to boot.
Click to expand...
Click to collapse
ok, could you do a quick explanation to use mtkclient? just to backup etc, i know the erase partitions, in general, ive never used or touched this phone partitions.

1lopes said:
ok, could you do a quick explanation to use mtkclient? just to backup etc, i know the erase partitions, in general, ive never used or touched this phone partitions.
Click to expand...
Click to collapse
You have to set it up the usual mtk drivers, the UsbDk installer, the Lib USB drivers, then, inside the mtkclient-main.zip, you'll find a README.md, open it with some text reader of your preference, it contains the main commands that you can use.
python mtk r boot boot.img will back up your boot partition, this is using the CLI tool, you also have the GUI tool with an interface, to interact more easily, I prefer the command line, but it's up to you.
The GUI tool lists the partitions, your device has, if you prefer to use the command line, to know them, you can run a bad command like python mtk r bot (instead of boot) boot.img, and the tool will tell you the partitions available.

SubwayChamp said:
You have to set it up the usual mtk drivers, the UsbDk installer, the Lib USB drivers, then, inside the mtkclient-main.zip, you'll find a README.md, open it with some text reader of your preference, it contains the main commands that you can use.
python mtk r boot boot.img will back up your boot partition, this is using the CLI tool, you also have the GUI tool with an interface, to interact more easily, I prefer the command line, but it's up to you.
The GUI tool lists the partitions, your device has, if you prefer to use the command line, to know them, you can run a bad command like python mtk r bot (instead of boot) boot.img, and the tool will tell you the partitions available.
Click to expand...
Click to collapse
so if im correct, i found out a way, but comes out as 3 files each one. i tried dumping (as gpt) and writing vbmeta_a and i got it, i used mtkgui too. so now i do everything you said then erase the frp partition and it should work?

1lopes said:
so if im correct, i found out a way, but comes out as 3 files each one. i tried dumping (as gpt) and writing vbmeta_a and i got it, i used mtkgui too. so now i do everything you said then erase the frp partition and it should work?
Click to expand...
Click to collapse
Now that you have a backup from this partition, you can try it.

SubwayChamp said:
Now that you have a backup from this partition, you can try it.
Click to expand...
Click to collapse
alright thank you so much for your help, ill see soon if i can

1lopes said:
alright thank you so much for your help, ill see soon if i can
Click to expand...
Click to collapse
SubwayChamp said:
Now that you have a backup from this partition, you can try it.
Click to expand...
Click to collapse
sadly its still locked even after erasing the frp partition

1lopes said:
sadly its still locked even after erasing the frp partition
Click to expand...
Click to collapse
Well, the other two partitions that can store credentials are persist and vendor, you can try with them, if you have a backup.
And, flashing a GSI, I wouldn't recommend an official image from a Pixel device in Google site, but some of the custom GSI available in the net.
And, probably, flashing a different fastboot ROM, may make a difference.
Also, finally, flashing a Miui based custom ROM like miui.eu ROM, may get you out of this. It's probable that some flashing process just corrupted a specific partition, and re-flashing it, may restore it, as it seems not an issue from the servers but from your device.

SubwayChamp said:
Well, the other two partitions that can store credentials are persist and vendor, you can try with them, if you have a backup.
And, flashing a GSI, I wouldn't recommend an official image from a Pixel device in Google site, but some of the custom GSI available in the net.
And, probably, flashing a different fastboot ROM, may make a difference.
Also, finally, flashing a Miui based custom ROM like miui.eu ROM, may get you out of this. It's probable that some flashing process just corrupted a specific partition, and re-flashing it, may restore it, as it seems not an issue from the servers but from your device.
Click to expand...
Click to collapse
ok, that works, it disables the lock till i connect to an wifi. what can i do now?

1lopes said:
ok, that works, it disables the lock till i connect to an wifi. what can i do now?
Click to expand...
Click to collapse
Mm, what do you mean with "till I connect to a Wi-Fi?" Could you boot to system?

SubwayChamp said:
Mm, what do you mean with "till I connect to a Wi-Fi?" Could you boot to system?
Click to expand...
Click to collapse
Yes, i could, even set it up and go to the home screen, but if i connect to any wifi it will relock itself till I delete the persist partition once again and I dont connect to a wifi