Hi, today I tried to update my phone to LOS 15.1. I got a tad lazy, because I've flashed many roms in different phones so many times that maybe I skipped a step. Have in mind that I was on NFound's 3.2.1-7 recovery and AOSIP 8.1 rom with B32 Bootstack.
This is what I did:
1. I flashed the Bootstack and Modem that was on the official thread.
2. Went to Fastboot to flash the newest Recovery (3.2.3.0).
Then when I tried to get into recovery to flash the rom, I knew I ****ed up :cyclops:; It reboots instantly as soon as I try to get into recovery mode . I can boot into Fastboot and launch commands from my PC just fine, tried flashing many recoveries to see if I could get in, but I can't.
Tried getting into EDL, but the phone shows in the Device Manager as ZTE Diagnostic Interface (DFU).
Is there something I can do without opening the phone? Maybe there's a way to flash my old bootstack through Fastboot? Maybe it's because I'm on Windows 10 that it shows as UDF in the Device Manager? Any ideas?
There's this tool for the Redmi Note 4 that can get your phone recognized by MiFlash if you can get into Fastboot. Is there something like this for the Axon 7? I couldn't find anything.
https://forum.xda-developers.com/re...ool-redmi-note-4-edl-mode-o-removing-t3684024
Penoro123 said:
Hi, today I tried to update my phone to LOS 15.1. I got a tad lazy, because I've flashed many roms in different phones so many times that maybe I skipped a step. Have in mind that I was on NFound's 3.2.1-7 recovery and AOSIP 8.1 rom with B32 Bootstack.
This is what I did:
1. I flashed the Bootstack and Modem that was on the official thread.
2. Went to Fastboot to flash the newest Recovery (3.2.3.0).
Then when I tried to get into recovery to flash the rom, I knew I ****ed up :cyclops:; It reboots instantly as soon as I try to get into recovery mode . I can boot into Fastboot and launch commands from my PC just fine, tried flashing many recoveries to see if I could get in, but I can't.
Tried getting into EDL, but the phone shows in the Device Manager as ZTE Diagnostic Interface (DFU).
Is there something I can do without opening the phone? Maybe there's a way to flash my old bootstack through Fastboot? Maybe it's because I'm on Windows 10 that it shows as UDF in the Device Manager? Any ideas?
Click to expand...
Click to collapse
The problem is the bootstack. The universal bootstack linked in the OP of the LOS15.1 doesn't support EDL mode. I recommend NFound or mine to avoid these kind of issues. With these other bootstacks there is always the EDL mode available by using the key combo or the EDL cable, so there is no risk of brick your device in DFU mode.
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Oki said:
The problem is the bootstack. The universal bootstack linked in the OP of the LOS15.1 doesn't support EDL mode. I recommend NFound or mine to avoid these kind of issues. With these other bootstacks there is always the EDL mode available by using the key combo or the EDL cable, so there is no risk of brick your device in DFU mode.
Click to expand...
Click to collapse
If it didn't support EDL mode, would there be anything I could do? It seems that I need to put the phone on EDL to be able to flash and unbrick it. If I press vol+ and vol- while booting the phone I can get to EDL mode, but the phone shows as DFU in the Device Manager., so it isn't recognized in MiFlash.
tdm said:
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Click to expand...
Click to collapse
I'll try this and I'll try using a deep flash cable.
There's a guy that went through the very same thing and was able to get it working again using an homemade cable.
https://www.reddit.com/r/Axon7/comments/9hc9gu/your_device_is_corrupt_it_cant_be_trusted_and_may/
Penoro123 said:
If it didn't support EDL mode, would there be anything I could do? It seems that I need to put the phone on EDL to be able to flash and unbrick it. If I press vol+ and vol- while booting the phone I can get to EDL mode, but the phone shows as DFU in the Device Manager., so it isn't recognized in MiFlash.
Click to expand...
Click to collapse
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Oki said:
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Click to expand...
Click to collapse
Thank you, Oki. I'll surely try tomorrow and post again if that one or any method works for me.
You can try enter the FTM mode: https://forum.xda-developers.com/showpost.php?p=69604257&postcount=7
It worked for me when I did the same like you. I also had the universal bootstack linked in the OP of the LOS15.1 and flashed a wrong recovery.
tdm said:
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Click to expand...
Click to collapse
Oki said:
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Click to expand...
Click to collapse
I got the phone to be recognized in MiFlash. I even flashed the B19 EDL package, but now the phone boots into recovery for a second (I can see the splash screen), then shuts down. I'll try downloading another EDL package.
Penoro123 said:
I got the phone to be recognized in MiFlash. I even flashed the B19 EDL package, but now the phone boots into recovery for a second (I can see the splash screen), then shuts down. I'll try downloading another EDL package.
Click to expand...
Click to collapse
Nice. So just to confirm, you have a G model and the wire trick worked?
tdm said:
Nice. So just to confirm, you have a G model and the wire trick worked?
Click to expand...
Click to collapse
Yeah, it did, but now I can't even get into fastboot to shut down the phone or let it discharge. It boots into MiFlavor, then the screen goes black but it's still on.
I finally got the phone working again. Jesus Christ, I was about to go out and spend $600 to just buy another phone.
I"m in a rush, so if I sound vague in any part, you can just ask.
This is what I did:
1. I discharged my phone completely by leaving it overnight in the Fastboot screen.
2. I cut a black ground cable from a mouse cable I had lying around.
3. I used one of those things to cut fingernails to expose the copper cable / remove the insulation plastic.
4. I bent it to form an "u".
5. I put it inside the usb port touching the 2nd "electric track" (that's how they are called here, at least).
6. I connected the cable to the PC (the phone didn't boot nor started charging).
7. I removed the cable from the usb port and connected the phone to the pc again.
8. It was recognized in MiFlash 2016.08.30, then I proceeded to flash the B19 Nougat room.
After I flashed the phone, It always booted into recovery mode for a second, then the screen went black. I couldn't even boot into Fastboot to discharge the phone or flash a new recovery, but after many tries, I could. I instantly deleted cache and userdata from Fastboot, flashed TWRP 3.2.3.0 recovery and was able to get in. Then I flashed AOSIP again, as I got error 6 trying to install LOS bootstack.
I think if I had deleted the Cache and Userdata the first time I wouldn't have had to go through all of this, so try that first before flashing another recovery, if you are able to boot into fastboot.
An important thing to note, before trying it with a deepflash cable or if you are lazy like me, by putting a copper ground cable into the usb port, is to DISCHARGE your phone completely, otherwise your phone will just charge if you try to unbrick it using one of those 2 methods.
I'll upload pics later, if anyone wants. It's pretty simple, just cut a black ground cable, expose the copper cable / remove the insulation plastic, and put it inside the usb port lining it up with the second metallic track.
Penoro123 said:
I finally got the phone working again. Jesus Christ, I was about to go out and spend $600 to just buy another phone.
I"m in a rush, so if I sound vague in any part, you can just ask.
This is what I did:
1. I discharged my phone completely by leaving it overnight in the Fastboot screen.
2. I cut a black ground cable from a mouse cable I had lying around.
3. I used one of those things to cut fingernails to expose the copper cable / remove the insulation plastic.
4. I bent it to form an "u".
5. I put it inside the usb port touching the 2nd "electric track" (that's how they are called here, at least).
6. I connected the cable to the PC (the phone didn't boot nor started charging).
7. I removed the cable from the usb port and connected the phone to the pc again.
8. It was recognized in MiFlash 2016.08.30, then I proceeded to flash the B19 Nougat room.
After I flashed the phone, It always booted into recovery mode for a second, then the screen went black. I couldn't even boot into Fastboot to discharge the phone or flash a new recovery, but after many tries, I could. I instantly deleted cache and userdata from Fastboot, flashed TWRP 3.2.3.0 recovery and was able to get in. Then I flashed AOSIP again, as I got error 6 trying to install LOS bootstack.
I think if I had deleted the Cache and Userdata the first time I wouldn't have had to go through all of this, so try that first before flashing another recovery, if you are able to boot into fastboot.
An important thing to note, before trying it with a deepflash cable or if you are lazy like me, by putting a copper ground cable into the usb port, is to DISCHARGE your phone completely, otherwise your phone will just charge if you try to unbrick it using one of those 2 methods.
I'll upload pics later, if anyone wants. It's pretty simple, just cut a black ground cable, expose the copper cable / remove the insulation plastic, and put it inside the usb port lining it up with the second metallic track.
Click to expand...
Click to collapse
Bro please put the all the details briefly here so that everyone can learn and save their device from brick
Related
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
I'm right there with you. Literally did the exact same thing. I'm stuck in DFU mode on my 2017U.
UnsecWifi said:
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
Click to expand...
Click to collapse
Use this thead https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
And remember NOT USE ZADIG DRIVER FOR MIFLASH, use the driver from the thead.
Tell me if it work
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
use another computer have windows 7 32 bit(try use windows 10 32 bit)
UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
If it sees it you should be alright, just close the MiFlash, or even better reboot your computer. Then try to reset ur axon by holding power button and then when it fails enter EDL again using the combo.
The MiFlash works best on a freshly booted EDL where u did not attempt and fail to flash stuff before. So always reboot the EDL fresh before using the tool.
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory::laugh::victory: Awesome. Thanks to everyone.
UnsecWifi said:
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory:[emoji23]:victory: Awesome. Thanks to everyone.
Click to expand...
Click to collapse
Did it work on win 10 or 7?
Also what drivers did you have installed? I'm afraid mine is a lost cause
Did it on my desktop with Win7. Used qualcom bulk drivers. And the only file to work for me was B15-NEW_FULL (Nougat). Unpack it and select the A2017U_B15-New_twrp_edl folder, refresh so you see your COM port and flash it.
If it doesnt work try going back into EDL mode, closing and reopening the MiFlash utility, switch USB ports etc. And use the cable that came with your phone. Make sure to charge it first with the original charger.
Help please
When I try to flash the edl rom folder I get a error in miflash "cannot receive hello packet" and "can not read from port com9".
I tried almost all of the different official miflash versions including betas and still the same error.
I've never had this problem with any other edl roms.
Rooted,twrp, and unlocked bootloader.
What am I doing wrong?
Thank you
You can try using the MiFlash and Qualcomm drivers in @jcadduono's EDL thread (pinned at the top of the Development subforum). Just make sure you uninstall MiFlash first, and also uninstall the Qualcomm drivers from Device Management (cant remember what it's called, QUSBBulk or something). Enable the viewing of hidden devices and check all categories, should be under Ports or USB.
To install the drivers, first go into EDL while plugged in. Extract the Qualcomm zip, then right click on the files that end with .inf, then click Install. There are 3.
If you have ever used Zadig, then its' WinUSB drivers must be removed too.
Another thing, power off the phone with cable unplugged from it, then go into EDL with VolUp+VolDown+Power (in that order). When the light at upper left of screen blinks red, you're in EDL. Just to be safe, restart EDL again with the button combo before plugging cable into phone.
I have no plans to flash stock Oreo, but I figured I could help anyway. I personally have never gotten errors with EDL, by doing the above.
AnonVendetta said:
You can try using the MiFlash and Qualcomm drivers in @jcadduono's EDL thread (pinned at the top of the Development subforum). Just make sure you uninstall MiFlash first, and also uninstall the Qualcomm drivers from Device Management (cant remember what it's called, QUSBBulk or something). Enable the viewing of hidden devices and check all categories, should be under Ports or USB.
To install the drivers, first go into EDL while plugged in. Extract the Qualcomm zip, then right click on the files that end with .inf, then click Install. There are 3.
If you have ever used Zadig, then its' WinUSB drivers must be removed too.
Another thing, power off the phone with cable unplugged from it, then go into EDL with VolUp+VolDown+Power (in that order). When the light at upper left of screen blinks red, you're in EDL. Just to be safe, restart EDL again with the button combo before plugging cable into phone.
I have no plans to flash stock Oreo, but I figured I could help anyway. I personally have never gotten errors with EDL, by doing the above.
Click to expand...
Click to collapse
I tried all of that and still getting same error.
Thank you though
I never had this problem
did ya ever get it sorted out? i ask bc i have been in edl hell with two boards, neither of which will accept a full flash. ive tried axon 7 edl tool, and the two most prevalent versions of miflash. the flashes go through, but do not completely flash back to stock. both boards are bl unlocked. one runs hot enough to cook an egg, the other works perfectly in TWRP, but has no touch in booted systems. ive spent two days flashing and resetting both. i say they dont completely flash bc even after wiping and cleaning files that are not system files persist on internal storage. maybe im missing something.
kitcostantino said:
did ya ever get it sorted out? i ask bc i have been in edl hell with two boards, neither of which will accept a full flash. ive tried axon 7 edl tool, and the two most prevalent versions of miflash. the flashes go through, but do not completely flash back to stock. both boards are bl unlocked. one runs hot enough to cook an egg, the other works perfectly in TWRP, but has no touch in booted systems. ive spent two days flashing and resetting both. i say they dont completely flash bc even after wiping and cleaning files that are not system files persist on internal storage. maybe im missing something.
Click to expand...
Click to collapse
well, i guess you didn't try EDL Tool?
Choose an username... said:
well, i guess you didn't try EDL Tool?
Click to expand...
Click to collapse
oh yes, many times. ive given up on all the edl files i have access to. i deleted all of them and am trying to find the ZTE provided ones. i have started redownloading the ones i can find. really, i want to go to a clean, unadulterated stock and start fresh. b32 doesnt work on either. i also am reinstalling axon7edltool and killer off the miflashes (i had two versions). full axon flash setup reset. atm, im trying to figure out how id apply mm b20 full properly from an old (necro'd by me today) thread. b15 and b32 fail. im going to re-evaluate every step of my installs and redownload all of my edls.
edit: after redownloading and installing miflash 2017.4.25 i flashed the initial twrp b29 edl. then, using twrp, i installed the stock recovery image. then, and only then, i was able to flash the b29 marshmallow full edl. good news? it all works. still hot though.
Update: making all my pointless updates in one day. lol.
I hard bricked the hot board experimenting with flashing a2017 edl (although when reflashed, it actually ran at normal temp). i managed to restore the serial of my other spare board, but still could not regain the imei. unless i discover a guide to pull imei from some hidden partition or qfuses or wherever it is stored locally, if such a thing even exists, it is doomed to not have service. im tempted to try to find somewhere or someone that can flash the board fully (like a proper factory reflash beyond what edl is. Qfil files for the axon 7 dont seem to exist. but i'd love to see someone flash one like that. maybe ill find a river of knowledge one day.
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screwdriver.
I did NOT have success with deep flash cable myself, I had to use testpoint method (and sadly broke my LCD in the process). The deep flash issue might of been because I was in Windows 10 x64 or on a USB3 port. If you do go that route and can't get it working, try with a Windows 7 x86 VM and USB2 passthrough mode before last resort of taking device apart.
Hold power button for 20 sec then volume down and fastboot will apear
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
CosmicDan said:
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
Click to expand...
Click to collapse
Actually I think I got scammed. It is Mi5x sold as MiA1. ****ing chinks! Anyway, I managed to install (Tiffany) on it and now it is booting to boot logo and bootlooping. I can get to fastboot and default (MIUI's) recovery by pressing button combos. But OEM is locked now so I cannot flash TWRP or other ROMs in it. I will have to EDL flash back to that MIA1 ROM to get it unlocked from fastboot. Otherwise MIUI unlocker asks me to link my miui account to this phone by going to settings, which I can't do because it is not booting up.
funny situation.
Bruce666 said:
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Click to expand...
Click to collapse
Facing The same Issue
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Phone Showing Charging Only
Can't Even Transfer Data
Not Detected on Pc
udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Im sorry, exactly with which ROM did you get to the fastboot?
Press power button for 15 sec
If you feel vibration then you are so lucky
boshell said:
Im sorry, exactly with which ROM did you get to the fastboot?
Click to expand...
Click to collapse
Fastboot rom for Mi5x because the phone is Mi5x.
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
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.