I was on Crdroid and wanted to get back into Miui since there was weekly miui 12 version now. Downloaded it and flashed it but it would not boot. I remembered on poco i had that i needed to flash latest miui andro 9 before flashing latest miui andro 10 for some reason so i got back into twrp and did it. After reboot it went into some sort of boot loot and i lost any recovery and fastboot. Cant get into edl for that matter also. Anyone has any suggestion?
Can you elaborate a bit more, when you try to boot into fastboot with the button combination, does it work?
Do you get any indications when trying to turn on your phone?
malimukk said:
Can you elaborate a bit more, when you try to boot into fastboot with the button combination, does it work?
Do you get any indications when trying to turn on your phone?
Click to expand...
Click to collapse
Button combination gives me blank screen and revovery gives MI logo and just that until it rebots and stays like that in some loop. I can get into test mode after opening it to try QFill flashing but i forgot about account authorisation thing. I do not have any type of service center in my country that wants to deal with this. Issue is probably due to anti rollback policy in 2s. So i need solution to flash somehow thru qualcomm port but aparently only wth that account that has authorisation.
Thats where i got till now. Spent a whole day also at 4pda trying to find solution but nothing there worked for me
scudteshka said:
Button combination gives me blank screen and revovery gives MI logo and just that until it rebots and stays like that in some loop. I can get into test mode after opening it to try QFill flashing but i forgot about account authorisation thing. I do not have any type of service center in my country that wants to deal with this. Issue is probably due to anti rollback policy in 2s. So i need solution to flash somehow thru qualcomm port but aparently only wth that account that has authorisation.
Thats where i got till now. Spent a whole day also at 4pda trying to find solution but nothing there worked for me
Click to expand...
Click to collapse
Oh that's unfortunate! I think that in this case you will need to find someone with an authorized account that will flash it for you remotely. There have been some people around here offering that service for a small fee but it might be worth paying as that might be the only way to fix it.
Same thing happend to me, first time i tried using custom rom. i dont know what exactly happened. i think its have something common with anti-rollback feature. I sent the divice to OFFICIAL service center.... I told them "use mi flash tool and authorised account to flash fastboot rom in edl" These OFFICIAL trained technicians... ehm idiots... change whole mother board.... atleast they count it as warrasnty repair.... there is one guy on reddit who succesfull unbricked his device via "shady bussines" (there is also contact on reddit page)... some guys offer xiaomi unbrick services via teamviewer. you can give it a try: https://www.reddit.com/r/Xiaomi/comments/ftix9v/shady_services_unbrick_with_mi_authorised_account/ EDIT: its last reply reddit (hope its allowed to post links)
note: you can put yr device in edl mode by pressing powerbutton. im not sure if its pressing or holding. (yr phone need to by connected to pc, then mi flash detect the phone if all drivers are instaled, it should be shown in "windows device manager" as PORT named "qualcomm hs-usb qdloader 9008")
if you dont have authorised acc. this will happen https://imgur.com/a/oJVpKEl so you need someone with authorised account who will unbrick yr phone via teamviewer [Sorry for my bad english]
Ijust dont understand why xiaomi dont allow user flashing in edl mode... or just make harder to brick phone... i had oneplus and i never bricked it. bricking xiaomi is just super easy thank to their stupid anti-rollback and other b****its. i will never use custom rom on xiaomi again. i will dont buy xiaomi again
Did you try the MI Flash app? ...try to fastboot and check if mi flash works
Also try fastboot(combo-buttons only) and see if you can see the phone (cmd -> fastboot devices) ...if you see a device then you are good to go
If you have a fastboot miui rom you can use my guide: https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/weird-behavior-boot-loop-random-t4086703
It's like using MI flash program but doing it manually - if mi flash gives you issues or else
P.S. CMD MUST be with administrator rights of course!
Hi Guys,
got a big problem here today. after installing on orangefox a miui11 stable rom suddenly flashlight went on and it stopped to install it... i was like WTF? so i have go to reboot to the recovery and my mix 2s DIED.
now
1) battery is drained
2) no fastboot (black screen on vol down + power key)
3) no recovery (black screen on vol up + power key)
4) bootloop on miui logo
any idea?
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin
Got it all figured out!
Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors
Hello!
Sorry, I don't know vell ENG, so I use a translator.
Problem with Xiaomi Poco X3 Pro phone (Global Update 12.0.6.0.RJURUXM) + device unlocked
Unsuccessfully decided to flash the phone... I got the POCO X3 PRO and POCO X3 NFC phones mixed up a bit. I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery. Then I tried to return everything as it was, but I couldn't. Accidentally via the TWRP menu formatted the System + partition Cache + Data and a few more sections, I don't really remember. At this stage, the phone was still functioning, turned on and rebooted in the recovery - TWRP menu. Then I tried to return the old recovery menu and connect Fastboot, but I couldn't. The phone turned into a brick. The phone does not turn on, does not work, the "POCO" logo does not appear, there is no way to go to recovery and Fastboot. The battery charge at that time was 46%...
HOWEVER, my computer sees the device as an emergency communication channel through the COM4 port - Qualcomm HS-USB QDLoader 9008 port
I'm already desperate and don't know what to do or what the instructions are... I don't want to open the phone and put it in EDL mode (if it helps at all)
I contacted a person with a service account, tried to restore the phone through the application "MiFlash_1212" by bypassing authorization and obtaining KEYS and access (I did not quite understand this point and how it works).
As a result, the firmware was able to run and the device began to be requested. But the following problem appeared, which I do not know how to solve, and that person stopped helping me (he has no time and simply does not want to, even though I paid him with money)
I read a lot of information on the form. Many tips and instructions did not help me.
What do I need to do? Who can I contact for help?
I wanted to get ROOT access (Magisc + YouTube Vanced + remove ads)
PS : But first I need to bring my phone back to life...
"I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery."
-Why you put x3 nfc firm on x3 pro?
I guessed that you would ask about this moment.
It was my mistake and I thought they were the same.
And when the phone did not turn on properly, only THEN DID I REALIZE that I had downloaded the wrong files.
But what should I do?
Nitritus said:
"I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery."
-Why you put x3 nfc firm on x3 pro?
Click to expand...
Click to collapse
I hope you find some help here
abood.mhd said:
I hope you find some help here
Click to expand...
Click to collapse
As they say : "Hope dies last" =((
Chances are you will still be able to unbrick it by playing with fastboot and using normal miflash
For the firmware go and search on mifirm device code vayu or poco x3 pro download the fastboot rom it should be in .tgz format
Unzip it and then put it into miflash l, switch the phone to fastboot mode by pressing volume up + power button at the same time
Hopefully that would do the trick or you can just go and ask xiaomi repair center since this case should still be within warranty
Contact your nearest Customer Support Center. They will fix the problem
Hassle free, just go straight to customer service.
If you still want to work on this, fine.
Its a stretch but is fastboot function restored?
If yes, download the fastboot image (not recovery) of your phone region, skip the miflash application and run the flash_all+lock script. The .bat file.
Make sure you get the right version for your phone and your region.
From the logs, wouldn't really be surprised if you still have no fastboot access.
Looks like the guy scammed you.
Sure he indeed have the right edl authentication but he only did his job halfway and bailed as your phone are still loading in edl mode.
thenameisJEFF said:
Chances are you will still be able to unbrick it by playing with fastboot and using normal miflash
For the firmware go and search on mifirm device code vayu or poco x3 pro download the fastboot rom it should be in .tgz format
Unzip it and then put it into miflash l, switch the phone to fastboot mode by pressing volume up + power button at the same time
Hopefully that would do the trick or you can just go and ask xiaomi repair center since this case should still be within warranty
Click to expand...
Click to collapse
I wrote that it does not turn on, does not go to fastoot, does not go to recovery, does not respond to charging, the indicators do not blink
xelrix said:
Hassle free, just go straight to customer service.
If you still want to work on this, fine.
Its a stretch but is fastboot function restored?
If yes, download the fastboot image (not recovery) of your phone region, skip the miflash application and run the flash_all+lock script. The .bat file.
Make sure you get the right version for your phone and your region.
From the logs, wouldn't really be surprised if you still have no fastboot access.
Looks like the guy scammed you.
Sure he indeed have the right edl authentication but he only did his job halfway and bailed as your phone are still loading in edl mode.
Click to expand...
Click to collapse
The phone did not turn on and fastboot and recovery do not enter any mode. The service can accept it, but it is clearly no longer under warranty and the price can be set very high.
WoodenSKY said:
The phone did not turn on and fastboot and recovery do not enter any mode. The service can accept it, but it is clearly no longer under warranty and the price can be set very high.
Click to expand...
Click to collapse
This is likely because you might have format some important part as IMEI number. Like this guy said: https://forum.xda-developers.com/t/no-imei-and-no-wifi-plss-help.4276823/post-85014473
In this state, no matter what you do, you have to pay.
https://forum.xda-developers.com/t/poco-x3-pro-hard-bricked.4277803/post-85025433
The most safe way is Xiaomi repair support center. High charge, but for sure a working phone.
my poco x3 pro global stable(VAYU) is stuck in miui log i tired to flash it with magisk method now its stuck ther. any one can help me with it
WoodenSKY said:
I wrote that it does not turn on, does not go to fastoot, does not go to recovery, does not respond to charging, the indicators do not blink
Click to expand...
Click to collapse
Straight to service center you go then )
It should still be within warranty becuz they only refuse hardware error not software brick
Beside it shouldn't cost much tbh
i did this mistake with my brand new galaxy s6 when it came out but the only solution i had was going to repair shop and the dude used a hardware tool called octoplus and he flashed it and worked but i lost my original imei adress but it worked i did search for you i found the tool you need is ufi box google it contact them and see if you get one or find a repair shop by the way i repaired that s6 with 10bucks
unfortunately, your only option is service centre as they are the only one who can get access to phone via edl mode and flash what was formatted
Just to be sure, I asked customer support and they said the following... "By installing custom ROM, Recovery, and/or Rooting your phone, the warranty is not void. However if your phone bricks while installing a custom ROM, then the warranty is considered void". They adding insult to injury for you
My Vayu is stuck on QUSB_BULK in device manager, I don't even know what to do?
True ayush Kushwaha said:
My Vayu is stuck on QUSB_BULK in device manager, I don't even know what to do?
Click to expand...
Click to collapse
same here, did you manage to fix yours?
Hi all
I had just finished installed Lineage and twrp succesfully to setup this phone, but I then discovered that the unlocked bootleader was preventing me to install Netflix.
I then tried to re-lock it via "fastboot oem lock" which apparently worked, but the side effect was that my main system is now not booting at all.
And when I've then tried to unlocking it again, it just fails, so I'm currently closed out.
Right now I can only access fastboot mode.
Any idea if this can be saved?
thank you
It can be saved but you need to use EDL mode (Emergency Download Mode). This mode is locked by Xiaomi and you Need an authorized account to use It.
You have 2 options:
- Pay a man that have an authorized account and can flash the stock rom from EDL.
- Go to an authorized Xiaomi center.
Thank you. Luckily that was not the right answer.
I've managed to put the phone in EDL mode via hardware, after opening it up.
After bypassing also the lack of helo message error, I've finally manage to flash with Xiaomi Flash tool and regained access to it.
Hello,
First, some context:
After a factory reset of my Xiaomi Mi 10 Lite 5G (the phone is more than 2 years old, the warranty expired), the phone worked fine for a few days, but while playing a video game it suddenly crashed, then it showed up the following error: "Your device is corrupted. It cannot be trusted and will not boot."
Then the phone started displaying random white and black horizontal lines everywhere on the screen before shutting itself down again.
As of now, the screen stays completely dark, no sound, no vibration, no LED flashing, nothing shows on the screen whatever key combinaison I press.
Nothing happens when charging the phone either.
However, the device is recognized as "Qualcomm HS-USB QDLoader 9008" when plugged into my PC, so it is in EDL mode.
The phone has never been unlocked, nor flashed, and was (before this incident) running on the official MIUI 13 (Developer options had never been activated, nor ADB and it never entered into fastboot mode).
tl;dr; The device crashed without notice and put itself in EDL mode after displaying a worrying error message.
I tried draining the battery, no luck, nothing changed.
The phone is recognized by MiFlashPro (latest version: 7.3.706.21) but it shows a forseen error saying i need a authorized Mi account to flash it (but I don't want to pay 25$ a random guy on the Internet to flash it for me, knowing the device might be dead).
It is also recognized by QFIL, and I got my hands on a "patched Firehose" to bypass the authorized Mi account, but it always ends up showing the QSahara error (the error remains the same whatever firehose I select, patched or not, and whatever rawprogram*.xml too).
So, does anyone know how to flash a hard bricked Xiaomi in EDL mode using QFIL?
Anyway, I tried to be precise and concise, I hope someone has a working solution.
Thanks in advance for your answers!
PS: I tried to flash Monet EEA Global V13.0.4.0 (MIUI 13).
I have had the exact same problem happen to me with a Xiaomi Mi Note 10 Pro (tujana).it's just that I bought the device already bricked by the previous owner who flashed it with the ROM for the wrong device, namely the Redmi Note 10 Pro(sunny/mojito)I've since then succumbed to giving money to strangers online to flash it, but the flashing kept throwing an error(couple of guys tried it) and I couldn't flash it myself with QFIL as well, getting the same error messages as you. So I decided to dig a bit deeper and found out that the primary bootloader that is bar unflashable in those devices(please someone correct me if i'm wrong here) is different on the Xiaomi Mi Note 10 Pro that has version 2 primary BL and the Redmi Note 10 Pro has version 3. I do not know why and how the previous owner flashed the device to hardbrick it like that. I can't seem to figure it out. If anyone comes up with a solution I'm buying.