Database Info

i9305t can't connect to Odin

I have bought a i9305t with a broken screen through a private sale. After connecting it to a working screen, I discover a few strange problems:
1. I can't get the phone into download mode or recovery mode by the normal key combinations. So I can't do any factory reset.
2. The phone can power up, but it stops at a log in screen requesting a pin input, although when I asked the previous owner about it, he said he never had set up any locking pins.
3. In that pin-entering mode, when I connect the phone to my PC (windows 7), the PC recognise the connection and displayed a i9305t in windows explorer, but the explorer can't show any content details of the phone. When I run the Odin with the phone in this mode, the COM window changes colour, but any attempts to flash any tar file stops at 'SetupConnection..' step, and after a while, it comes back with a 'FAIL!'.
4. I have a usb jig, and with that, I can force the phone in download mode. However, when the phone is in that mode, Odin doesn't recognise the connection at all when I plug the phone in, so I can't do any flashing in that mode.
So I am totally stuck! I thought about going through ALL the pin combinations to try to unlock the phone (assuming the pin is a 4 digit number). After spending one and a half hours to go from '0000' to '0500', I thought this is rediculous! There must be a better way! So I hope some guru out there would be able to help me, as I have exhausted all my tricks (which is not that many!).
If anyone can show me a way to get around my problems, it would be most appreciated!!!

Missing IMEI
tdrinker said:
I have bought a i9305t with a broken screen through a private sale. After connecting it to a working screen, I discover a few strange problems:
1. I can't get the phone into download mode or recovery mode by the normal key combinations. So I can't do any factory reset.
2. The phone can power up, but it stops at a log in screen requesting a pin input, although when I asked the previous owner about it, he said he never had set up any locking pins.
3. In that pin-entering mode, when I connect the phone to my PC (windows 7), the PC recognise the connection and displayed a i9305t in windows explorer, but the explorer can't show any content details of the phone. When I run the Odin with the phone in this mode, the COM window changes colour, but any attempts to flash any tar file stops at 'SetupConnection..' step, and after a while, it comes back with a 'FAIL!'.
4. I have a usb jig, and with that, I can force the phone in download mode. However, when the phone is in that mode, Odin doesn't recognise the connection at all when I plug the phone in, so I can't do any flashing in that mode.
So I am totally stuck! I thought about going through ALL the pin combinations to try to unlock the phone (assuming the pin is a 4 digit number). After spending one and a half hours to go from '0000' to '0500', I thought this is rediculous! There must be a better way! So I hope some guru out there would be able to help me, as I have exhausted all my tricks (which is not that many!).
If anyone can show me a way to get around my problems, it would be most appreciated!!!
Click to expand...
Click to collapse
----------
Problems solved! Well, most of them anyway. I found I got the wrong usb driver on my PC. After updating with the correct Samsung usb driver, I could connect to Odin, thus I could flash a CWM recovery rom, so I could do a factory reset.
However, after the phone has booted up, for some reason, I found the IMEI is missing, so I couldn't connect to any network when I insert my sim card. I don't know how that happened. Can anyone help me with that? Many thanks.

Updated Mate 9 via firmware finder now bricked - screen won't initialise

Hi folks.
I updated my mate 9 last night using firmware finder, phone rebooted, did the update thingy and then switched off. It didn't boot back up so tried turning on - nothing. Plugged in the charging cable, no light came on to indicate it was charging.
I have tried connecting to my computer using the USB 3 port and the computer does seem to recognise it as it makes that jungle sounds when connected (computer) and again when disconnected. I have tried doing the power vol down and that seems to create the PC to make the sounds again but there is nothing displaying on the phone itself. If you looked it at you'd think it was off.
So I guess it's a positive that the PC is getting some kind of response, and the phone must be working.
Can anybody suggest as to how I can get things back up and running? Remember the screen doesn't work on the phone since the update. I am on C636 converted from AL00 early last year.
Have tried HiSuite just in case but phone isn't recognised.
Thanks.
DT.

adb commands
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.

dwcasey said:
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
Click to expand...
Click to collapse
Thanks for the reply.
Nope - doesn't seem to work. No idea what's happend but it appears to be kaput. Other than my PC recognising that I am connecting something when I plug it in to a USB socket, there is no other way of knowing if the device is even on. I've left it on charge over night, tried the power up/down (even though I can't see the screen) and have tried the appove. It did list a port that was open but no devices appeared as listed.
Will continue having a look to see if there are any other methods. Appreciate your help dwcasey.
DT

Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.

I've come to the conclusion that the phone is dead and that I have a few options.
1 hope for a repair but it'll cost a fair bit given it's a Chinese model and I'm in the UK.
2 sell it on fleabay, but it contains personal data.
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Phone is definitely toast. When I connect to a PC it loads as USB SER. It still makes some sort of connection but it's impossible to access the phone Absolutely no response from ADB/Fastboot.
Clearly an issue with the update using FF given It was this that caused things to go tits up.
Back to my Note 4. First time I've ever had this happen. Fingers burned, dammit.

btblue said:
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Click to expand...
Click to collapse
If you leave it long enough for the battery to go down (no idea how long that might be) then from a 'drained' phone state to plugging in, you might see a 'powered off charging' screen which would be nice. At least you might have a starting place once again.

Happened to me if you have no warranty ,then it will cost about 200-300 dollars to replace your motherboard.

btblue said:
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
Click to expand...
Click to collapse
Instead of binning it I suggest you disassemble your phone completely with the help of video guides and some fine screw drivers and replace the motherboard yourself. They shouldn't be too expensive on AliExpress. The phone and its components are quite easy to wrap ones head around. Just be wary of the glue they use to stick the battery to the case. It can be a bit of a bastard to get off, but it's worth trying for sure! I've opened it up for screen and camera replacement myself. And I don't count myself as a "phone repair geek" Best of luck on this endeavor!

Unable to enter EDL

xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.

kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.
Click to expand...
Click to collapse
Download Qualcomm qloader drivers....see if device shows up as Qualcomm 9008 In Windows Device manager or maybe it says Qualcomm bulk hub...if it is you are in edl mode and you need to download blank flash file from the rom archive on lionnet moto firmware under our device...unzip the file and run the .bat file with admin privileges it will run the file and reload the critical bootloader files to get you to bootloader screen ...then reflash STOCK...I did this last week because I rebooted to edl from TWRP...

Nothing shows up. I get a few led blinks but nothing in device manager or otherwise.

Anyone found the answer to this? Im having the same issue

kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do som
Shane8705 said:
Anyone found the answer to this? Im having the same issue
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hi there! I myself have a hard-bricked G Stylus (US model). After reading this and related threads, as well as doing a LOT of independent research on this. I have a feeling that the only hope lies in potential EDL test points located on the motherboard. I've looked at a teardown video on Youtube, and I see several sets of potential test points. From further research, it appears that test points for EDL are always located right next to each other.
I'm purchasing some iFixit tools this month, which include the required T3 driver bit. Once I get access to the motherboard, I fully intend to test every possible set of EDL points. I'll post my findings on this and any related thread in the G Stylus forums here on XDA. If I'm successful in restoring the phone, I will post a photo of the points that need to be bridged to enter EDL mode.
Wish me luck!

Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?

moorevineyard said:
Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?
Click to expand...
Click to collapse
Hi there! I actually did find some more potential EDL points underneath the speaker grill (underneath the black plastic piece below the battery).
I've tested them all... and no luck so far... The only reproducible result I can share is:
When the battery is unplugged, attempting to use any two points results in an LED flash every 15 seconds or so. No other behaviors.
Motorola came so close to having a perfectly repairable phone... What a disappointment.

This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.

moorevineyard said:
This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.
Click to expand...
Click to collapse
It appears that certain models aren't failproof. Similar situation with a mislabled black-flash. Flashed it multiple times and ended up unable to do anything going forward. I saw the edl points on a similar phone the moto g power on youtube and hoped that they were somewhat easily identified. Unfortunately doesn't seem to be the case, I too have tried every combo that I saw on the board. Same blinking lights as described, but nothing shows on the PC. I am able to get it working on other devices however as I have two.

Today I started researching repairing a hard brick of a moto g stylus after letting it sit around for a couple months. I came across the android doctor video that shows how to do this on a g8+ but unfortunately I found out that the mobos aren't laid out similarly. Subsequently found this thread. Bummed to find out the EDL points haven't been discovered. Hopefully someone does find them and posts here. I guess I'll do a little more research but otherwise I guess it's back to the shelf this phone goes.

FWIW I found this thread, but the points illustrated here don't seem to work for me: https://forum.xda-developers.com/t/sofia-edl-points-found.4457105/

Well I tried most points on the board. I was cycling through when I hit either I-J or J-K and my pc said there was a short on a USB port. I removed the ribbon cable to reveal that the jumper I made had melted. The led no longer flashes and the phone is now totally dead jim. Charging for a while doesn't seem to have any effect, nor letting it sit. Whatever shorted killed it. I was incredibly careful but clearly not careful enough.
That said I have another 2020 stylus (bootlocked unfortunately). So I'll be part harvesting as my current phone degrades. Thank you all for your help and good luck to you on this phone! Shame on Moto for really trying to keep people out of it... The glue, the edl cable not working, the points being potentially behind the battery ribbon. Just unnecessary nonsense imo.

EDL es el 10 y 12 me pasa que no se mantiene se desconecta despues de 5 segundos

Possibly Bricked

Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.

Riverseo said:
Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.
Click to expand...
Click to collapse
I actually start the MSM tool ,wait until it boots up, position my cursor close to the start button on the tool, then I connect my phone to cable make sure it's attached to both PC and phone , put phone in edl ( hold power button and both vol up and vol down at same time) phone should go blank and you should see a connect on the MSM tool, hit start,,,, hth

My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc

Riverseo said:
My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc
Click to expand...
Click to collapse
When I go into edl it's a completely blank ,,,screen is black

Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.

Riverseo said:
Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.
Click to expand...
Click to collapse
I would just make sure you have all the correct drivers, especially l2, other than that iam out of ideas maybe someone with more experience will reply,, good luck

No worries cheers for the help though!

Question Poco X3 suddenly bricked

Hi folks,
I really hope someone is able to help. I got a Poco X3 from a friend which is causing issues. According to her the phone started to lag and shut down yesterday. No pending updates. The phone had about 10% battery left.
After the phone died she plugged it into the charger and the battery symbole appeared. after that the phone went black again and never came back to life.
I tried doing the usual "let's try to fix it" but nothing seems to work here.
I've tried the following things:
pressing the power button for 10+ seconds
pressing power + vol down for 10+ seconds
pressing power + vol up for 10+ seconds
pressing power + vol up + vol down for 10+ seconds
plugging it into the pc and checking if the device can be accessed using the explorer
plugging it into the pc and checking for adb weather or not the device can be accessed
the phone hasn't developer settings enabled as far as I'm able to guess.
the strange thing that I noticed:
when plugging it into the pc the windows sound for a connected device plays. within the device manager a new entry appears:
Code:
QUSB_BULK_CID:0404_SN:812DDxxx
Any ideas how to fix this issue?

is it deadboot like no sign of life?, are you using your phone in gaming or occasionally gets overheat while playing? because if so, must be a cpu solder melt and got shorted which is the alot of cases of poco x3 pro being deadboot, mine as well experienced this and need to brought it to technician for a "cpu reball" check in youtube many people did reballing and solved their problem.

absolutely no sign of life except the listing within the windows device manager.
as for overheating: it's not my phone and is primeraly used for social media, surfing and ocasionally providing the hotspot for a notebook. I woudln't bet that it was an issue previously.
Interesting nevertheless.
So, in short, if I understood this correctly after watching some videos, without reballing the change of getting the data from the phone is.. non existent?
I mean, it looks doable if you are a fine motorist

lechnerio said:
absolutely no sign of life except the listing within the windows device manager.
as for overheating: it's not my phone and is primeraly used for social media, surfing and ocasionally providing the hotspot for a notebook. I woudln't bet that it was an issue previously.
Interesting nevertheless.
So, in short, if I understood this correctly after watching some videos, without reballing the change of getting the data from the phone is.. non existent?
I mean, it looks doable if you are a fine motorist
Click to expand...
Click to collapse
Make sure to distinguish whether it is "POCO X3 Pro" or "POCO X3 (NFC)". These are 2 different phones.
This is not your phone, and if you had never done reballing the CPU, better not risk it. You could try to reball the CPU, with the risk of upsetting your friend when failing to do so.
Find shops that can do it and let them take the risk.
This phone has 2 year warranty in Europe. It is possible that the phone is still under warranty. Hardware issue could be repaired by Xiaomi/Redmi/Poco official repair center or customer service. However, there's chance that the data in the phone may be wiped.
If you find a non-official shop to try the repair, the warranty might be void.

lechnerio said:
Hi folks,
I really hope someone is able to help. I got a Poco X3 from a friend which is causing issues. According to her the phone started to lag and shut down yesterday. No pending updates. The phone had about 10% battery left.
After the phone died she plugged it into the charger and the battery symbole appeared. after that the phone went black again and never came back to life.
I tried doing the usual "let's try to fix it" but nothing seems to work here.
I've tried the following things:
pressing the power button for 10+ seconds
pressing power + vol down for 10+ seconds
pressing power + vol up for 10+ seconds
pressing power + vol up + vol down for 10+ seconds
plugging it into the pc and checking if the device can be accessed using the explorer
plugging it into the pc and checking for adb weather or not the device can be accessed
the phone hasn't developer settings enabled as far as I'm able to guess.
the strange thing that I noticed:
when plugging it into the pc the windows sound for a connected device plays. within the device manager a new entry appears:
Code:
QUSB_BULK_CID:0404_SN:812DDxxx
Any ideas how to fix this issue?
Click to expand...
Click to collapse
I have the same issue. Mine suddenly stopped working on Tuesday, May 30th. It had around 79% battery and I have been trying to find a solution since.

Your phone is on the "EDL" mode aka Emergency DownLoad mode. From what I've seen I don't think that's actually possible to flash anything again with it since Xiaomi encrypted some stuff.
Link that may be useful :
Xiaomi POCO X3 Pro - Прошивки MIUI - 4PDA
Xiaomi POCO X3 Pro - Прошивки MIUI
4pda.to
https://xiaomitools.com/download/poco-x3-pro-qcn-file/
[GUIDE] How to return to Stock/Flash Images with QFIL
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image. Download and install the Qualcomm drivers from here Download either of the firmware from here Download the support files...
forum.xda-developers.com
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com
Good luck finding stuff inside these.

The same happened on my Poco x3 pro. is there anyway to flash stock using edl mode for FREE?

Haynzu said:
The same happened on my Poco x3 pro. is there anyway to flash stock using edl mode for FREE?
Click to expand...
Click to collapse
I too have a Poco X3 Pro and the EDL tool by bkerler (it's a FOSS project) automatically loads this particular loader which is in an EDLAuth folder so I think it's totallly worth a shot.
Mind you I'm rather out of touch on Xiaomi's EDL authentication implementation so I cannot guarantee you anything.

lechnerio said:
absolutely no sign of life except the listing within the windows device manager.
as for overheating: it's not my phone and is primeraly used for social media, surfing and ocasionally providing the hotspot for a notebook. I woudln't bet that it was an issue previously.
Interesting nevertheless.
So, in short, if I understood this correctly after watching some videos, without reballing the change of getting the data from the phone is.. non existent?
I mean, it looks doable if you are a fine motorist
Click to expand...
Click to collapse
If you manage to reboot it in EDL you can dump the userdata partition with a tool such as the one I linked above, although I don't really know how you could decrypt it if needed.
The only way to reboot it in EDL (VID: 05C6 , PID: 9008) probably is shorting the proper test points (pins) on its motherboard while the device is booting.
Here at XDA someone provided a photo to point them, however I cannot confirm whether they are the correct ones.

Micky99 said:
I too have a Poco X3 Pro and the EDL tool by bkerler (it's a FOSS project) automatically loads this particular loader which is in an EDLAuth folder so I think it's totallly worth a shot.
Mind you I'm rather out of touch on Xiaomi's EDL authentication implementation so I cannot guarantee you anything.
Click to expand...
Click to collapse
Hi there! Thanks for this infomation i'm willing to try this. Is there any video tutorial for this out there? I'm such a noob when it comes to these stuffs

Haynzu said:
Hi there! Thanks for this infomation i'm willing to try this. Is there any video tutorial for this out there? I'm such a noob when it comes to these stuffs
Click to expand...
Click to collapse
Just follow the readme in the repo to setup everything needed (possibly on baremetal linux I'd suggest) or boot the ISO provided by its dev and run ./edl printgpt --memory=ufs, if the device enters the firehose mode you can then use ./edl r <rest of the command, according to the readme> to dump any partition.
Unfortunately the loader linked to our device might not work , so you might have to wait an indefinite amount of time before we get a fully working one.
Don't forget you're gonna have to decrypt the dump of the userdata partition, and I don't know how to help you with that.

NotesOfReality said:
Just follow the readme in the repo to setup everything needed (possibly on baremetal linux I'd suggest) or boot the ISO provided by its dev and run ./edl printgpt --memory=ufs, if the device enters the firehose mode you can then use ./edl r <rest of the command, according to the readme> to dump any partition.
Unfortunately the loader linked to our device might not work , so you might have to wait an indefinite amount of time before we get a fully working one.
Don't forget you're gonna have to decrypt the dump of the userdata partition, and I don't know how to help you with that.
Click to expand...
Click to collapse
Thanks! I'll give this a try