I'm trying to unbrick my x720 by QFIL but my pc won't recognize Qualcomm 9008 port - LeEco Le Pro3 Questions & Answers

My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.

Bad cable or need to reinstall drivers...

marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.

Say sth more about your phone state and history...

marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.

I've no idea how to help you... Sorry.

gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c

tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.

Is yours 722?
Sent from my SM-A730F using xda premium

mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.

gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium

mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.

gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.

So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium

Related

[Q] Really Bricked?

I had an Asylum Custom Rom installed.
I also had TWRP as the recovery installed.
I decided to try the new COLOR ROM public beta that I got from the OPPO forums.
I went into TWRP recovery, did a full wipe and then proceeded to install the new COLOR ROM.
When I rebooted, the phone never turned on again.
Now I cannot get to fastboot, recovery, or turn on the phone at all.
I browsed through many forums and tried
1. Charging phone for 5 hours (no led light when plugged in) -> nothing
2. Holding Power button for 30 secs, (5 times to try a hard reset) -> nothing
3. Holding Down button for 10 secs -> nothing
4. Power and up volume -> nothing
5. Power and down volume -> nothing
6. Plugged into computer USB and tried all button combos -> nothing
Is my phone really bricked now?
I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?
killerskincanoe said:
I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?
Click to expand...
Click to collapse
Nothing. no response whatsoever. I've worked with many different phones before starting with the Nexus One and I've always been able to get out of a potentially bad situation because I could at least always get to fastboot or recovery, but in this case, nothing. It really is like working with a brick, hence the term "brick". Now i can really understand the meaning of the term.
such a bummer. it certainly makes me think twice about trying other ROMS now jeez
update
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
good to hear !!
I couldnt really believe that flashing a rom using recovery affects fastboot let alone button combos/charging...
btw what were the costs of replacing the battery ? or was it free of charge under warranty...
dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
Glad to hear it turned out that way. Really strange situation.
Oualcomm HS-USB Diagnostics 9008
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.
olezhek1975 said:
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.
Click to expand...
Click to collapse
I suggest you to ask addel in oppo forum, she can help you just pm her and tell your problem, because she has an app like odin in samsung to totally flash new rom inage from pc like odin did. But its not officially released by oppo and its hard to find, so i suggest you to contact her
Sent from my GT-I9205 using XDA Free mobile app

I have totally bricked my zte axon 7 a2017g and i seriously need help!!

So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//
@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.
Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?
choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this

Bricked my Xiaomi Mi A1, Stuck in EDL 9008.

Hello everybody,
First off, I hate people who don't search on google before making a post, I have been searching for 4 days and I feel that it's appropriate to ask now.
I will make 2 parts to this thread, one will be a very fast explanation of what I did and the second part will be the same but a very thorough with a step by step process of what I messed up...
TL;DR: I was tired, late in the evening I flashed for some reason a Partition table of a Mi Note 3 on my Mi A1... I am now bricked and cannot access anything, fastboot, ADB, recovery nothing! I guess my phone is in EDL mode cause when I plug it in it flashes its led. "Qualcomm HS-USB QDLoader 9008" Is what I see in my device manager.
What do? oh, I forgot! I cannot access anything through any combination of buttons. I am stuck here, where I am!
The full thorough explanation for people who are bothered to read fully. (Includes my excuses for making noob mistakes, might be fun to read idk.)
Young me on a Sunday evening decides to reinstall magisk but this time with twrp cause I did it without twrp (yeah yeah I know). I was left without OTA's and after uninstalling anything that had something to do with Xposed or magisk I trashed it all. and stupid me thought that maybe? maybe? just maybe deleting Dalvik Cache would help me get my OTA's back after injecting my original ROM. This is where the fun begins.
I was not wanting to go through reinstalling magisk and all that to wipe the Dalvik Cache, I thought that that was my mission now, so I decided to search for methods that don't require root or being in the system, so some kind of fastboot or ADB command or something idk. I tried installing twrp and without my understanding that failed miserably and then I read some post where someone said that they flashed a mi note 3 partition table on their phone and something worked. Being the naïve little boii that I am, let's do that hey? Bam! bricked! I read somewhere I can open the phone and remove the battery and not having the tools is a mess, having to ask friends for some and voiding my warranty for something that probably won't work and after reading I understood that I'm in "EDL 9008 recovery" or something like that. I cannot boot into anything, I only have EDL 9008 to work with. I tried using Xiaomi's flasher tool and it would never respond to the initial hello packet (duuhh! I can't use ADB nor fastboot).
I know that this was stupid, I know! I learnt my lesson. If there is nothing we can do can I at least somehow get my internal storage data back? I deleted the backups from google drive for a short amount of time but randomly 5hrs prior to this sad story. All I have safe are now my contacts.
I hope you guys have some ideas! I feel like I'm fked but maybe with EDL 9008, there is a little glimmer of light?
P.S. If you guys somehow get me into fastboot I can flash a correct partition table back. My PC has all drivers so I can do this!
Sincerely, Micheal.
There is a way although i did tried it yet.
First of all sorry for my English.
Download latest MiFlash tool and qualcomm driver, this package contain both but not latest MiFlash so you should download lastest version from official site.
https://www.fshare.vn/file/H3R8M6OMRP2R
Download lastest stock rom.
You will need a good USB type C cable, dont use the one come with phone because you dont want to cut it in half.
Yes, that exactly what i said. Cut it in half, there are 4 small wire (or maybe 5 with type C?), remove it outer plastic and reconnect them.
Join the green and black cable, like you short circuit them, then plug your phone into PC with that cable without release green and black, wait for 5 sec then seperate them, the green and black.
Check device manager on your PC, you should hear device connect sound and qualcomm HS-USB QDLoader show up under Ports.
Open MiFlash and try to flash it.
You may want to check this video, although it in Vietnamese but you should understand the usb cable part.
https://www.youtube.com/watch?v=d5-1I9rWTiw
Hi, interesting situation. What about following this guide: http://en.miui.com/thread-235865-1-1.html ?
Its for some other phone, but try instaliing some drivers and you may get some signal of life.
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
m1shka said:
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
Click to expand...
Click to collapse
Yes, thats what I meant. Well, I dont know how to help you, wish you luck. I remember how I flashed wrong ROM for my S3 Mini and it was completly trashed, I'm glad that Xiaomi gives us at least some signs of life and hope.
And btw. I would rather charge the phone somehow - I hope it charges even in EDL mode, because if your phone dies while flashing with MiFlash, things can be even worse.
EDIT: I also found this guide, you can try it out: https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
m1shka said:
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
Click to expand...
Click to collapse
Wish you luck:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
did you try to hold more than 30 second ? and also , do you have flash log ?
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
So did you flash official stock ROM? Because I dont understand why doesnt it work... btw. when you flashed the ROM, did you lock bootloader?
Cant be battery dead?
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
EDIT: Maybe consider locking bootloader? Try it if youre on official stock.
EDIT 2: By flashing that ROM I guess you lost all data, but you can try to boot in TWRP without installing it and browse in file manager to see, if there is any data.
TrueMS said:
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
Click to expand...
Click to collapse
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
m1shka said:
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
Click to expand...
Click to collapse
As I said, you can try it, but when I flashed my Nougat stock ROM, i lost all the data. Or you can boot into TWRP and connect with USB to your computer to see the data in phone.
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
GVN.Gallus said:
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
Click to expand...
Click to collapse
None of the passwords I used worked.. I just factory reset it, thanks alot everybody. And now I will be more careful, don't flash anything weird. And backup!
I understood why I can't get the data back, if android fails at the encryption it jsut deletes everything!
My fone also in 9008 please can you guide me
I did the same what you have and it's on 9008 my flashing is successful but still my fone is not opening help me
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
How did you fixed i'm stuck in EDL?
SevenSlevin said:
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
Click to expand...
Click to collapse
i am in Qualcomm HS-USB QDLoader 9008 but i can't flash, it doesn't matter if the phone is on fastboot mode or turned off (i can't even turn it on)

Phone bricked, cannot flash because it randomly plugs/unplugs when connected to PC

Hey, first time posting here but a long time lurker. Amazing community from what I've experienced.
Yesterday, my phone bricked out of the blue, not turning on and showing a rapidly blinking LED. It refuses to charge, and when plugged to a computer, it displays in the device manager as a Qualcomm 9008 device.
So far I've tried unplugging the battery once, holding down the power button for three minutes straight, holding down volume- and power button, and none worked.
Apparently, flashing the phone seems to work for a lot of people, but I cannot do it because my phone randomly disconnects and then reconnects to my computer, repeatedly. This happens every 20 seconds or so.
I've tried using different ports, uninstalling then reinstalling drivers, resetting my PC, using a different cable, but nothing helps.
I've got a big trip tomorrow, and I don't want to go away with a dead phone. What can I do?
Update: tried cleaning the phone's USB port and the USB itself, no luck.
You got into EDL mode, search for guides how to use it (basically install correct drivers, flash ROM, reboot).
_mysiak_ said:
You got into EDL mode, search for guides how to use it (basically install correct drivers, flash ROM, reboot).
Click to expand...
Click to collapse
I know it's in EDL mode and I've looked into every single guide I could find, that's why I'm posting here.
Nothing so far has worked and I'm trying to flash the phone to see if it works, since an user here posted a youtube video of someone using MiFlash to get the phone back working.
The issue is that my phone has micro-disconnects when USB plugged to my computer every 20-30 seconds, and because of that I cannot flash it.
Do you have correct drivers installed? Fastboot mode reboots after ~30s if there are no drivers installed. Might be the same for EDL.
_mysiak_ said:
Do you have correct drivers installed? Fastboot mode reboots after ~30s if there are no drivers installed. Might be the same for EDL.
Click to expand...
Click to collapse
I downloaded them from xiaomigeek (cannot share the link due to post count), as suggested in another thread.
Also I tried installing them automatically through Windows device manager, but I still have the same issue.
Hm, don't know then.. Maybe someone else experienced something similar and can help.
Small update, cleaning both the device and the USB ports with a brush and alcohol does nothing to prevent the "micro-disconnects".
KurisuSama said:
Small update, cleaning both the device and the USB ports with a brush and alcohol does nothing to prevent the "micro-disconnects".
Click to expand...
Click to collapse
Buddy those disconnects are not because of dirty port.. cleaning wont help..i actually had this problem with my first gen android phone it disconnects every 5 secs.. but once i hit flash in sp flash tool(mtk flasher) it stops disconnecting and starts receiving rom packets without problem
apexashwin said:
Buddy those disconnects are not because of dirty port.. cleaning wont help..i actually had this problem with my first gen android phone it disconnects every 5 secs.. but once i hit flash in sp flash tool(mtk flasher) it stops disconnecting and starts receiving rom packets without problem
Click to expand...
Click to collapse
Any resources where I could try this on the Mi A1?
Edit: correct me if I'm wrong, but after a bit of searching it seems I'm not unable to find a guide because there isn't one, but because sp flash tool isn't compatible with my phone.
Use another pc may be. Or another USB cable
.:Addicted:. said:
Use another pc may be. Or another USB cable
Click to expand...
Click to collapse
Tried both.
The cable doesn't seem to be the issue as a different cable yields the same results and another phone I've tested doesn't have any issues with it.
And I tried doing this on my laptop instead of my desktop PC, then on my roomate's PC, but the same thing happens.
KurisuSama said:
Any resources where I could try this on the Mi A1?
Edit: correct me if I'm wrong, but after a bit of searching it seems I'm not unable to find a guide because there isn't one, but because sp flash tool isn't compatible with my phone.
Click to expand...
Click to collapse
Sp flash tool is for phones with mtk CPU's only brother.. could u try different pc? Or try flashing via cmd?
---------- Post added at 04:25 AM ---------- Previous post was at 04:21 AM ----------
Btwn have u tried flashing the phon via miflash? Or u didn't cuz it disconnects? Well what happened to me is *I didn't even try to flash the phone with sp flash tool for 5 straight months cuz i thought its impossible to flash when it disconnects like this...but when i finally consoled myself to give it a try it flashed all the way to 100% without any problem..uh the phone stops disconnecting once the software pushes few packets to the phone
I have the same problem :/
If take to warranty they ill help or not?
Go into edl mode. Edit xml file that store info about partitions. Select few necessary. (like bootloader & idk about what other partition needed for sure, but just telling you to exclude big partition like system. You do your research on that. May be cosmicDan can tell you what partition you need to enter fastboot)
Im hoping you will be able to flash small partition.
So you can get into fastboot. Then try to boot twrp in fastboot to flash all partition from twrp image shared in xda. (May be use memory card & flash twrp image from there)
Good luck
this help me without remove battery http://en.miui.com/thread-1680467-1-1.html
i install driver qualcoom, after flashed rom and after i hold button power and work

Major help needed

OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?
SteveHebe said:
OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?
Click to expand...
Click to collapse
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
HolyHog said:
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.
Click to expand...
Click to collapse
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
SteveHebe said:
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
Click to expand...
Click to collapse
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
xtcislove said:
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I have current drivers, tried different machines, different ports and different cables.
SteveHebe said:
I have current drivers, tried different machines, different ports and different cables.
Click to expand...
Click to collapse
Is your phone regognized in device manager?
No, it is not
SteveHebe said:
No, it is not
Click to expand...
Click to collapse
Your phone boots ot fastboot and your pc does not regonize it? You need to make sure to install the drivers correctly imo.
Please read this sections carefully https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/

Categories

Resources