I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
ileikpi said:
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
Click to expand...
Click to collapse
either you are not in bootloader mode on the phone or you need to fix your drivers.
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
I got stuck at that step as well, had to do a hard reboot, attempts at reinstalling the drivers only seemed to make it worse!
JP_93 said:
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
Click to expand...
Click to collapse
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
ileikpi said:
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
Click to expand...
Click to collapse
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
JP_93 said:
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
Click to expand...
Click to collapse
Zadig doesn't let me right click to uninstall drivers T-T. I tried reflashing twrp and redoing everything in the guide to make sure I didn't miss anything but I'm still stuck at < waiting for any device >. Unlocked bootloader seems so close yet so far... Thank you very much for your help thus far tho!
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Bucci83 said:
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Click to expand...
Click to collapse
Yep it does.
lafester said:
either you are not in bootloader mode on the phone or you need to fix your drivers.
Click to expand...
Click to collapse
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
ileikpi said:
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
Click to expand...
Click to collapse
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Bucci83 said:
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Click to expand...
Click to collapse
Ok I'll try that when I get home.
Sorry but may I ask if you remember what your phone was called in device manager when you rebooted it into bootloader? Was it "Android", some Qualcomm code (ie. QUSB_BULK), or ADB something? In @JP_93 and my cases, our phones were simply labelled as "Android" in device manager.
Unlocked using a different PC
Ok guys, I managed to unlock my phone using a friend's computer with no problems. The drivers in my own pc were definitely messed up and uninstalling and reinstalling them didn't work.
Thank you very much to everyone for your help and sorry if I blew this out of proportion!
Glad you got it to work!
Related
I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".
I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0
kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.
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
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.
I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.
And just to be certain, do you have USB Debugging enabled in developer options?
Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.
lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now
lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
AOSP100 said:
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
Click to expand...
Click to collapse
Update: Replacing the Google drivers (ADB, bootloader, etc) with Samsung ones in device manager broke everything so I had to reinstall the Samsung USB drivers, and uninstall platform-tools and the Google drivers through Android Studio
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
ninjasinabag said:
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
Click to expand...
Click to collapse
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
AOSP100 said:
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
Click to expand...
Click to collapse
Yeah, sadly the a205u will probably never get root or custom ROMs. We have an extremely small chance since Samsung promised two major updates for the A20.
Either way, https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832/amp/
Has the fastboot drivers if you haven't tried that one yet.
.