I'm new to the rooting and flashing scene, and i decided to root my lg g6 to remove all the bloatware and stuff, but when i need the device id to put it on the lg development site i cant get it since the cmd window doesnt recognize my phone in fastboot and keeps returning the waiting for device message, i already updated all the drivers and reinstalled android studio and sdk tools, and still have that message, any help would be appreciated !
Drivers are not installed correctly. Uninstall current ones and use the all in one ADB and fastboot install drivers.
Related
So I deleted everything in my phone, including the Rom I wanted to flash (smart, right?) and all I have is TWRP Recovery mode and Download Mode. When I put my phone into any mode, my PC does not recognize it and I therefor cannot fix it... I've tried it on three computers with downloading and updating the drivers. The first time it works after installing and updating the drivers, but when I put it in the second time it does not work. I need to unplug my phone in download mode while doing the LG program, and the computer won't recognize or find my phone. All help is greatly appreciated and thanks to repliers in advance
Day 2 of not having a phone: I can't do this xD I need to fix it somehow, if anyone can help me please do
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
x714x said:
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
Click to expand...
Click to collapse
Tried that and it would say "device not found." and other error codes. One time I was able to load my device onto the computer and after it completed the CM 11 transfer it stopped. I may have to order an OTG cable or something...
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
Hi guys,
I'm having problems unlocking bootloader.
The phone enter into fastboot mode but when I type "fastboot oem unlock-go" in the cmd of windows it doesn't recognize my device.
I have installed Minimal ADB and Fastboot and I have installed ADB Driver installer too but it doesn't recognize the device.
Can anybody help me with this please?
I need to unlock it because I want to root it.
Thanks
Have you tried unplugging and replugging when the phone goes into fastboot mode?
I just got my pro 3, did the OTA to the .19 software and unlocked and rooted just today and my girlfriend's very very fresh windows 10 install.
If that doesn't work just delete the adb driver, replug the device and windows should install the same drivers I used.
Device LG G6
Model : G600LR30c
I was thinking of installing a custom os which requires TWRP recovery installed in the device which recuires the device to be bootloader unlocked. But when I use the command "adb reboot bootloader" in minimal adb the device never goes to boot menu, instead it simply restarts and then if I put the command "fastboot oem device-id", it never shows the id and keeps showing "waiting for a device" instead. Please help me resolve this.
P.S: I also tried to access boot menu using key combo. but in vain
If you can put the phone in Fastboot mode during powerup or restart, it's a Windows issue if it don't work. Windows must recognize the device via PnP and install a different set of drivers each time the usb mode changes. If it don't work when the phone is already in Fastboot mode, try different drivers.
I once had two sets installed, that from the device manufacturer and that ripped from the Google SDK(on XDA). This way all usb modes worked, but Windows couldn't perform the Reboot Fastboot/Recovery commands fom ADB like is the case here and the Windows software had, suitable drivers installed, to be able to access the phone if it was already set to Fastboot/Download etc mode.
That was a TI OMAP based LG L9 under Win7. Starting with Windows 8.1, Fastboot was no longer working at all, you could only perform disaster recovery via D/L mode with a stock image and then root the thing with a one-click rooter to be able to install a recovery from Android etc etc, but that was due to the no longer supported TI SoC. But Qualcomm also tends to completely abandon older SoCs.
I'm dumbfounded. I have unlocked bootloaders and rooted for years. Just got my OP8P.
I also have a new Microsoft Surface Pro with Windows 10.
I installed ADB, installed Fastboot.
Unlocked developer options and turned on USB Debugging and Developer Unlock.
Windows device manager shows ADB INTERFACE for the my device in device manager.
I can open can open Power Shell and/or the CMD prompt. I've done both.
I can type adb devices in the command prompt and I CAN see my device.
I can reboot it fastboot from the CMD prompt so I KNOW Wndows sees my phone.
BUT ONCE I'M IN FASTBOOT, the problem starts.
Fastboot does NOT see my device. Commands return the words "Waiting for Device..."
I BELIEVE the issue is with the drivers. When I boot into Fastboot, my device location changes in Device Manager from USB>ADB Interface to Portable Devices>Android.
The Android Device icon has a yellow triangle with an exclamation mark. It's says the driver for this device is not installed. But everything was working fine and the drivers were fine while the device was powered up normally.
If I try to manually install the driver it fails and says "cannot update drivers for your Android".
What heck is going on? What did I do wrong?
I've uninstall and reinstalled the drivers direct from Oneplus. I've uninstall and reinstalled the drivers direct from Google. 'I ve uninstall and reinstalled the drivers direct from Windows.
Why can't device and drivers be recognized in Fastboot. And why can't I update the drivers for the "Android" device?