Related
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone
ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help
I have had my Axon 7 for about 48 hours. I was super excited to get into as it has a great price/feature ratio.
As I usually do with a new handset, I set about unlocking, rooting, etc. This turned out to be massively annoying and not nearly as easy as I would have liked. After a couple of hours, I managed to get the bootloader unlocked, TWRP installed, and the stock firmware up to B25. When I couldn't get root to work properly (after another few hours), I decided to throw in the towel. I set about reverting everything back to factory so I could reevaluate. There is where my problems started...
In the middle of rolling back everything, somehow I am no longer able to boot the phone at all.
All the guides I have read online say to enter EDL mode but it never seems to work? I have tried using MiFlash as well as the Axon7Toolkit and both do not see the device. I have installed the Qualcomm USB drivers and I see the COM port in device manager, but it says the device isn't connected.
I get the blue ZTE logo then a split-second flash of the open chest android with the red triangle before the screen goes black. The phone is still powered on however.
BUT 'adb devices' command yields: d69520e recovery
So, I know the phone has some degree of communication with the computer.
Is all hope lost for me at this point? Or is there something else I'm missing?
Please let me know if there is any additional information needed to help figure out what's going; I will do my best to provide it.
Thanks in advance for any assistance!!
This is similar to what has happened to me. Have a look here. There are some advises, but I couldn't get it to work anymore.
https://forum.xda-developers.com/showthread.php?p=72223036
Gesendet von meinem Lenovo K3 Note mit Tapatalk
@frustratedaxon7user
You said :
> I see the COM port in device manager, but it says the device isn't connected.
> BUT 'adb devices' command yields: d69520e recovery
It looks like that the recovery is broken (open check Android screen).
Do you mean that the phone is detected as "Qualcomm HS-USB QDLoader 9008 (COM10) in device manager?
And you got response to "adb devices" command?
I think there is a conflict here. If you got "adb devices" answer as "d69520e recovery" then the phone is in recovery
mode, not EDL mode. You must try to get in EDL by entering "adb reboot edl" command. Keep the Windows Device manager always on,
it should emit beep sound and refresh display to show the phone as "Qualcomm HS-USB QDLoader 9008" (or "QUSB_BULK") depending on your installed driver.
and if the phone is really in EDL mode, "adb devices" should no longer work (empty attached devices in answer to command). Note that in EDL mode there is nothing on the screen
so you must rely on the Device manager to deduce the status of the phone (In item USB devices), and to issue "adb devices" comand to check.
If Qualcomm HS-USB QDLoader 9008, you can flash TWRP 3.1.0-0 with MiFlash : https://forum.xda-developers.com/showpost.php?p=72313753&postcount=44
and https://forum.xda-developers.com/showpost.php?p=72316949&postcount=52 . You may havy to refresh several times in MiFlash for connection with the phone.
If QUSB_BULK, you can flash TWRP (tenfar signed TWRP 3.0.2) using axon7tool https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 (section A).
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit
daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible
i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!
A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted
The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.
i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
crank_girl said:
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
Click to expand...
Click to collapse
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
p.s. can you actually flash something with adb??
Lots of people seem to confuse adb with fastboot. Is that what you want to use?
Thanks both for responding. I think I've gotten myself a bit confused over what is supposed to be working at any given time.
I can get the phone into EDL mode and fastboot. Fastboot devices finds my phone. MiFlash doesn't find my phone despite having the QHSUSB driver installed.
What's the easiest way to return my phone to stock? I have MiFlash and Axon7toolkit installed.
Cheers!
Choose an username... said:
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
Click to expand...
Click to collapse
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
Click to expand...
Click to collapse
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
You have the wrong drivers.
crank_girl said:
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
Click to expand...
Click to collapse
I tried to post yesterday and for some reason the XDA app didn't post the answer... Basically this:
-Forget ADB and that program that you're using to see the devices. EDL uses COM protocol, has nothing to do with adb at all.
-Go to Device manager and find where QUSB_BULK is. If it is in Unknown devices, either right click on it and try to install the driver automatically, or search for "Qualcomm HS-USB QDLoader 9008 drivers", download, install and try to install it on QUSB_BULK. If it is in an "USB devices" tab or on Ports "COM & LPT" simply right click, Uninstall device, Delete driver software for this device
I've done that several times over but miflash still isn't detecting it.
crank_girl said:
I've done that several times over but miflash still isn't detecting it.
Click to expand...
Click to collapse
all right. Try EDL Tool by djkuz. I don't know if the same packages work but just download another edl package
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
crank_girl said:
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
Click to expand...
Click to collapse
How come? The right driver literally appears on the last photo...
Choose an username... said:
How come? The right driver literally appears on the last photo...
Click to expand...
Click to collapse
I know, right? It's a mystery. Never had this happen before.
crank_girl said:
I know, right? It's a mystery. Never had this happen before.
Click to expand...
Click to collapse
If it doesn't work try MiFlash on another PC, it sometimes happens that it won't detect it by any means
Hi, I have (or used to) the GSI Android P Rom on my A1, I saw that an update was avalible for it on the official Telegram group so I decided to download and install it, I wiped vendor as it said and flash the zip files, but I forgot to flash the vendor image again, I rebooted and now the screen is completely black, the phone is dead, the led is not making anything aswell, not even blinking, I'm trying to reboot into fastboot or TWRP with the volume keys but doesn't make anything, I tried to connect it to the PC and it recognizes it as Qualcomm HS-USB Diagnostics 900E (COM10).
I don't know what to do, I'm so worried about this, any idea?
Try to flash stock rom via miflash
If it says Qualcomm HS-USB Diagnostics 900E its not even dead. Lol
What to do next? Stop panicking & use that thing on top of your neck. It'll be fine. (& Use search button in xda, everything is here?)
https://forum.xda-developers.com/mi-a1/help/bricked-mi-a1-qualcom-hs-usb-t3784681
.:Addicted:. said:
If it says Qualcomm HS-USB Diagnostics 900E its not even dead. Lol
What to do next? Stop panicking & use that thing on top of your neck. It'll be fine. (& Use search button in xda, everything is here)
Click to expand...
Click to collapse
Hi, what if now the PC recognize it as an unknown device?
Before your reply I tried to use Qualcomm emmc studio to fix it because MiFlash wasn't recognizing it, Qualcomm did, so I tried to flash the stock ROM but it gave me an error (something about couldn't found ram), I disconected it and it appeared as an unkown device, now not even Qualcomm can recognize the phone, help
Use edl method and you should be good