Hey everyone.
I have a bizzare problem?
I have no computer connection when in recovery mode with my Poco?
It happened after I logged out of my miaccount following youtube flash instructions in an online guide.
At first I thought avast on the PC had removed my android drivers. Or that it was the TWRP (3.4.0-15-surya-mauronofrio). i uninstalled avast an replaced it with IObit an reinstalled Xiaomi android drivers.
The cell has windows access when booted an transfer option is chosen on the Poco.
I cannot get windows access for transferring files when in recovery?
does anyone know how I can restore my recovery mode windows access so i can transfer files an see what I'm doing?
Ive never had this happen before. I will never log out of Miui before flahing a custom recovery ever again thats for sure.
Wierd?
Bryceicle1971 said:
Hey everyone.
I have a bizzare problem?
I have no computer connection when in recovery mode with my Poco?
It happened after I logged out of my miaccount following youtube flash instructions in an online guide.
At first I thought avast on the PC had removed my android drivers. Or that it was the TWRP (3.4.0-15-surya-mauronofrio). i uninstalled avast an replaced it with IObit an reinstalled Xiaomi android drivers.
The cell has windows access when booted an transfer option is chosen on the Poco.
I cannot get windows access for transferring files when in recovery?
does anyone know how I can restore my recovery mode windows access so i can transfer files an see what I'm doing?
Ive never had this happen before. I will never log out of Miui before flahing a custom recovery ever again thats for sure.
Wierd?
Click to expand...
Click to collapse
check if you have Enable MTP switched ON in Ofox or TWRP, if not turn it on, should help
or reflash Ofox again and reboot recovery and see if that helps
jeryll said:
check if you have Enable MTP switched ON in Ofox or TWRP, if not turn it on, should help
or reflash Ofox again and reboot recovery and see if that helps
Click to expand...
Click to collapse
Yeah I tried that. It was a simple issue. The owner of the laptop recently got a gaming rig with windows 10. An Acer. An I was using her gaming laptop. A HP. She is logged into windows on both computers. During the night windows got a bit stupid an installed adb drivers as system that were Acer drivers on both computers. Hense no adb connect in fastboot was possible on the HP. She remembered her HP update driver password an activated her HP account. I have removed the Acer android drivers but cannot install any. Hoping to using HP driver install to remedy this.
What a nightmare lol.
I am currently on Pixel Experience 10 official beta with twrp an ANX camera. Luckily I had some ROMs on my SD card lol. I was in the middle of formatting data with no Rom installed when I discovered it.
Always have a relaible easy to flash Rom.
I thought I was soft bricked. Very scary
it could be easy if the available recoveries support adb sideload or adb push so you can transfer files to /sdcard
I have never tried side load. Maybe I should learn. An if you want a terrific anx camera inbuilt then switch to Pixel Experience Beta Android 10. I don't know as much about photography as you. I just know I suck at it lol. Same procedure an Evox 5.2. flash 12.0.3.0 firmware then PE then format data. Bang. Everything works I've tested so far unlike Evox 5.2. Similar experience but not a power Rom. Strong an steady. Antutus in the 282-287k range. Mind you after nearly bricking my Poco last night for safety I made data an Cache ext4 an not f2fs.
Probably why it's a little slower.
Xiaomi Poco X3 (surya) - Pixel Experience
Xiaomi Poco X3 (surya) - Pixel Experience
download.pixelexperience.org
Bryceicle1971 said:
Xiaomi Poco X3 (surya) - Pixel Experience
Xiaomi Poco X3 (surya) - Pixel Experience
download.pixelexperience.org
Click to expand...
Click to collapse
What if I use A11 instead of A10 of PE?
Related
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
joao.m.neto said:
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
Click to expand...
Click to collapse
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Mr.Ak said:
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Click to expand...
Click to collapse
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
joao.m.neto said:
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Yes,as I said, could be a battery issue but we are still not sure yet.I can give you the link for winxp or win7 if you need and then you can dual-boot it alongside windows10.You should install drivers from cm11s restore toolkit thread(executable drivers),maybe then your device will show up in device manager though it is highly advised to do this on Xp or 7 since 8,8.1 and 10 has driver signing issues.
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.
Hello,
I am trying to unlock my bootloader. did everything "by the book" however it seems that my PC does not recognize my Poco when in fastboot (and actually at all - it never responses to the Poco).
I enabled debugging, tried to install poco driver (but it was not recognized so the installation was not succesful), I tried to use mi flash but it also won't recognize the phone. I also tried to install other ADB and fastboot apps but they also trough the command line cannot detect it. I even tried everything on another computer that I have...
I would mention that I have never tried to connect my Poco trough USB but it seems to be not normal.
I am using the 8gb version with global ROM ver 12.0.4.0.
What can I do? maybe something with my phone?
Please help I want to unlock and install xiaomi.EU so much
Thanks!
VIP1 said:
Hello,
I am trying to unlock my bootloader. did everything "by the book" however it seems that my PC does not recognize my Poco when in fastboot (and actually at all - it never responses to the Poco).
I enabled debugging, tried to install poco driver (but it was not recognized so the installation was not succesful), I tried to use mi flash but it also won't recognize the phone. I also tried to install other ADB and fastboot apps but they also trough the command line cannot detect it. I even tried everything on another computer that I have...
I would mention that I have never tried to connect my Poco trough USB but it seems to be not normal.
I am using the 8gb version with global ROM ver 12.0.4.0.
What can I do? maybe something with my phone?
Please help I want to unlock and install xiaomi.EU so much
Thanks!
Click to expand...
Click to collapse
2 things ..
1. Try different cable...
2. Try different port....
Best of luck bro....
Hunteres said:
2 things ..
1. Try different cable...
2. Try different port....
Best of luck bro....
Click to expand...
Click to collapse
After so many tries. Eventually it really was the cable...
Thanks mate
I have a similar Issue.
I cannot get PC to detect the phone unless it's in Official Firmware and then only once it's booted up. It won't detect fastboot or recovery mode.
It's as if I got blocked from their services.
I have a similar Issue.
I used another older pc and it worked.
Chipsets in Mainboard
The Poco F1 (Fastbootmodus) was not beeing on my system with a x370 Plattform (AMD). Switching to an old Intel-System (P35 Chipset) helped.
What kind of PC-System do you have?
I have an Intel system 2 different machines, otg drives, nothing gets detected
The original cable in the box is not work for connect to PC, find another cable to try. That work for my case.
oreokung said:
The original cable in the box is not work for connect to PC, find another cable to try. That work for my case.
Click to expand...
Click to collapse
I tried about 5 different cables on 3 different machines. All cables work when booted but nothing when recovery or fastboot.
I have come to realize Xiaomi is just an inferior product, with inferior internals when compared to OnePlus. it's the old adage "You get what you pay for".
I liked the design, Pop Up camera, Amoled, 865. Dreamy specs I just wished it had a rear fingerprint scanner. It would have been perfect. But 3 or 4 months and dud. Disappointing.
Found this https://c.mi.com/thread-3124380-2-1.html
yes:
my desktop (cause im in bootloader mode i'll need to use it) is artix linux with kde. sadly i cant install on it adb/fastboot and other drivers due to lack of systemd and empty repos so will do it probably from a random linux-based bootable usb...
my mobile is (as was in title) - xiaomi redmi go - european version.
what means ? my mobile have encryption after removing system what makes me unable to boot things... for the now i can still boot stock ROM. although i wanted to remove all associations with google in system (all google apps, bugs caused by removal etc...)
any ideas what i should do with it? wanna have it to tomorrow cause we use our mobiles at work and my current mobile got "marked as over outdated" by boss so i cant use
why noone ?
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go DinarGuru.com
Christinakim said:
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go
Click to expand...
Click to collapse
this i actually know. i have one heavily modded lg so im not a newbie. its more about "encryption unsuccesful" broked roms leading to non-booting state (bootloop) etc... nothing from xda surely doesnt work, yep
surely nothing from : https://forum.xda-developers.com/m/techyminati.8245761/ works. was trying loads of times always bootloop. recovery posible to load but then tends to not make factory reset and lock in "encryption unusccesful", and thats worst... im in europe but have global version btw...
dead chat ?
Hello.
I own a Poco X3 Pro and was asked to updated my MIUI version after rebooting my smartphone. After updating it, the wireless lan stopped working. I can't enable it. Also the phone is very unstable now and crashes a lot.
I searched for way to downgrade and downloaded V12.5.5.0.RJUEUXM from downmi. When trying to downgrade I have to connect to the internet. I can't because the MIUI upgrade broke WiFi.
I also tried factory resetting it, but it requires me to have an internet connection for that.
I tried usb tethering but it also doesn't work.
So I need to know how to install the old MIUI version without WiFi or how to factory reset the phone without Wireless Lan.
I hope I didn't forget anything.
Cheers.
Xiaomi Poco X3 Pro
The Xiaomi Poco X3 Pro is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm Snapdragon 860 chipset is paired with 6/8GB of RAM and 128/256GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 20MP. The battery has a 5160mAh capacity.
forum.xda-developers.com
Leguron said:
Hello.
I own a Poco X3 Pro and was asked to updated my MIUI version after rebooting my smartphone. After updating it, the wireless lan stopped working. I can't enable it. Also the phone is very unstable now and crashes a lot.
I searched for way to downgrade and downloaded V12.5.5.0.RJUEUXM from downmi. When trying to downgrade I have to connect to the internet. I can't because the MIUI upgrade broke WiFi.
I also tried factory resetting it, but it requires me to have an internet connection for that.
I tried usb tethering but it also doesn't work.
So I need to know how to install the old MIUI version without WiFi or how to factory reset the phone without Wireless Lan.
I hope I didn't forget anything.
Cheers.
Click to expand...
Click to collapse
Well, 1st off let me apologise for being ...!!!! So forgive me if I don't explain correctly... I think you need to use Xiaomi MiFlash tool to re-flash your firmware. Head to this link for your rom, then flash using PC/laptop and miflash software. Remember to select 'clean all' and NOT 'clean all and lock' when flashing otherwise you will lock your bootloader. But, this forum is for Poco F3 etc, not Poco X3 Pro, search your forum for further assistance.
{Mod edit: Inappropriate language removed. Oswald Boelcke, Moderator}
I'm sorry for posting in the wrong section. May I continue posting in the thread or do you want me to recreate this post at the correct section?
Anyway. I was able to bypass the Mi-account locking by buying a USB-C to ethernet cable. That way I had an internet connection and was able to enter my My-account password.
Now it wants me to set up everything as if I bought it recently. At the last step I'm told that I have to redo everything since my google credentials haven't been added. I had a google and a mi account on the phone.
Sadly google isn't asking about my login credentials when setting the phone up.
Any idea how to remove the phone from my google account or how to add my google credentials?
It might take some time for me to answer and update stuff because I might be buying hardware like the cable which takes some time.
Mi unlock doesn't work. I get a chinese error that I translated online. Any idea how I can proceed?
I also bought that white/red EDL cable but pressing that button on the cable doesn't put my phone into EDL mode.
I was able to bypass my MI account with the usb-c to ethernet cable and entering the password. Now I want to set up my phone and since the wifi is broken I can't set that one up and can't enter my google credentials. It doesn't show me the screen for it.
I can get into Fastboot btw.
With MiFLash 2022.5.7.0 I can't flash V13.0.3.0.SJUEUXM Fastboot on my device. I get the Failed message with "Erase is not allowed in Lock State"
Is there a V13.0.4.0.SJUEUXM Fastboot? 13.0.4.0 was the version that crashed my phone because that one must have been incorrectly downloaded or something. So I had to download 13.03.0 Fastboot.
Leguron said:
Mi unlock doesn't work. I get a chinese error that I translated online. Any idea how I can proceed?
I also bought that white/red EDL cable but pressing that button on the cable doesn't put my phone into EDL mode.
I was able to bypass my MI account with the usb-c to ethernet cable and entering the password. Now I want to set up my phone and since the wifi is broken I can't set that one up and can't enter my google credentials. It doesn't show me the screen for it.
I can get into Fastboot btw.
With MiFLash 2022.5.7.0 I can't flash V13.0.3.0.SJUEUXM Fastboot on my device. I get the Failed message with "Erase is not allowed in Lock State"
Is there a V13.0.4.0.SJUEUXM Fastboot? 13.0.4.0 was the version that crashed my phone because that one must have been incorrectly downloaded or something. So I had to download 13.03.0 Fastboot.
Click to expand...
Click to collapse
Can try this:
Install Xiaomi EU, IN, ID ROMs instead of Global without Unlocking Bootloader!
This Guide is for any Xiaomi device with any 'Stock ROM'. Please do the following steps carefully, especially from step 7 to the last step: Check the current MIUI version on your device, and to do this do the following: Go to settings> About...
forum.xda-developers.com
Or find Xiaomi custom service store/ repair center in your country or region to help you flash an official ROM. Since the bootloader is still locked, they might do it free of charge, ask though. Another reason is that you lost WIFI, and there is chance that is a hardware problem, so better let them check if it's hardware issue or not.
Since it bricked by updating to V13.0.4.0.SJUEUXM
I was waiting for V13.0.4.0.SJUEUXM to be released as Fast Boot.
For some reason only V13.0.6.0.SJUEUXM was released as Fast Boot. Do you think V13.0.6.0.SJUEUXM will ever be released as Fast Boot?
Can I use the V13.0.6.0 as Fast Boot to short circuit my phone to install it in ELD Mode?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com