I need help getting my phone into the correct mode to be recognized by Windows as a Diagnostic PORT, so the phone registers in QPST.
The phone works for ADB and storage in charging mode and MTP mode, respectively.
However, the phone is not detected at all when i choose RNDIS mode, which I understand is the necessary setting to configure a diagnostic port for QPST.
- I have also tried booting in BP TOOLS from fastboot, same results.
Motorola Device Manager is installed, phone is XT1676 3GB/16GB running LineageOS 14.1 with superuser, TWRP.
did uh find any solution bruh same problem is goin on with me !!!???
Related
Hi Guys,
Please help me, i have installed adb, usb drivers also tried with vcom drivers but sp tool not detecting my phone.
when i connect phone switch on and usb debugging on device manager shows it (ADB and device in portable both) but switch off phone does not come in device manager (in my magnus /A1117 mtk preloader device used to come but nothing for this device).
Tried on both win7 and win8.
Not rooted or unlocked bootloader yet, want to get working sptool first before going for root.
Thanks in advance.
did you find solution for this my device on pc mtk preloader also not detecting ... but fastboot works ?? how to get back to total stock
Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
This thread is about the defective installation of the LGE Android mtp device driver. Note that when the phone is on all the drivers seem to work correctly (LGE mobile ADB interface under "android device", G4 driver under "portable devices" and LGE mobile USB serial port).
The issue presents when i switch the phone to "download mode"; in this mode the "G4" driver (which is the LGE Android MTP device) appears not to be working.
The problem persists on three different PCs, either with windows 10 or windows 7 and either with a LG G4 or an LG G3.
I would like to root my G4 device following the firmware flash procedure 10E, but I am not sure that I can flash the device if there is this kind of issue with the drivers. Is it normal that the device appears not to be working?
I am having the same problem as you were. I am using Windows 7 and several versions of the LG drivers with the same result; Everything is fine when my device (a G4) is booted normally but in Download mode I get the same error as you (This device cannot start. (Code 10)).
I have tried everything I can think of, I have uninstalled all the old Android drivers with USBDeview, disconnected the internet to stop windows update installing its own drivers, different USB ports and cables.
Did you ever get your device rooted?
SO... in my case (YMMV - be careful) it turns out there is no need for the device manager to be error free when the phone is in download mode.
I just got root using this procedure from the "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread with no issue. I thought it would work because the LGMobileSupportTool was reporting as being connected to my phone despite the error (This device cannot start. (Code 10)) in device manager. Sure enough everything worked fine. I wish it hadn't taken me (literally) 20 hours of fecking around with drivers to get to this point though...
ETA I have a G4 H815 (EU)
i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?
012512 said:
i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?
Click to expand...
Click to collapse
Edit. Performed a factory reset and it worked as it is.
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
But in my case only greenify is installed module,
Why you only post that After I factory reset my phone. Haha anyway thanks for the information.
PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
This helped me so much when I was trying to upgrade to Android M. After un-checking all my xposed modules, both my pc and laptop were finally able to read my LG G4 and install drivers, mtp, and others correctly without fail.
Same problem here with an AT&T G4. I've tried 2 different Win7 laptops (one of which has never had any Android drivers/tools installed previously), 3 cables, and even performed a factory reset. MTP Drivers work when booted normally, but fail ("Code 10") when in download mode. Any additional suggestions?
EDIT: As suggested by other posts/forums, this issue can be ignored, and isn't an actual problem. ADB works successfully, even if the MTP device isn't working in Windows' Device Manager. (This MTP device appears in Windows' Device Manager the same as it does when a USB Debugging connection hasn't (yet) been authorized on the Android side. My guess is that since Android isn't fully booted while in Download Mode, there's nothing to approve the connection. Either way, it doesn't affect the function of Download Mode, as long as the other Android-related devices in Device Manager have their drivers loaded successfully.)
TL;DR version: When in "Download Mode", as long as the other Android-related device(s) in Windows' Device Manager are working, ignore the "Code 10" error / "yellow triangle" on the MTP device. It's not needed for Download Mode to work.
Hi all,
This is my first thread on this website and I am not that expert of rooting and installing custom ROM's. I am trying to find a solution on your website for 2 days but I couldn't solved although I tried everything.
I have an issue with my LG G Pad 8.3 (LG V500) tablet. It was installed 5.0.2 stock ROM (Korean version) and I decided to root the device and install custom ROM. I used King Root to unlock the device. Then I installed TWRP thing to my tablet and started flashing ROM process. While working the tablet restarted automatically and it was stuck at the startup with a LG icon on the screen.
I decided to make factory hard reset it in order to get rid of this but when I try to make factory reset with button combinations I get the following error;
* Confirmed *
Secure booting Error!
Cause : boot certification verify
Then I searched for the forums and first installed Android Studio, then by using SDK manager tools, I also installed USB drivers.
As the device can connect download mode, I installed adb thing and tried to fix it. But apparently laptop does not recognize the device. I run the command "adb devices" and there is no devices in the list.
I also tried to use twrp recovery tools but again it didn't recognize the device.
When I check the Device Manager when the tablet is connected to laptop on download mode, I can see LGE AndroidNet USB Serial Port (COM4) thing installed. I also tried to install Android Device drivers (Android ADB Interface, Android Bootloader Interface, Android Composite ADB Interface) but they are not working properly and they have question mark on their left side.
So as you can understand I am drawning with the issues and don't know what to do next. Apparently laptop does not recognize the device but although I checked the xda forums and other forums for 2 days, I couldn't solve. I would really appreciate if you can help me.
Best
ironunited said:
Hi all,
This is my first thread on this website and I am not that expert of rooting and installing custom ROM's. I am trying to find a solution on your website for 2 days but I couldn't solved although I tried everything.
I have an issue with my LG G Pad 8.3 (LG V500) tablet. It was installed 5.0.2 stock ROM (Korean version) and I decided to root the device and install custom ROM. I used King Root to unlock the device. Then I installed TWRP thing to my tablet and started flashing ROM process. While working the tablet restarted automatically and it was stuck at the startup with a LG icon on the screen.
I decided to make factory hard reset it in order to get rid of this but when I try to make factory reset with button combinations I get the following error;
* Confirmed *
Secure booting Error!
Cause : boot certification verify
Then I searched for the forums and first installed Android Studio, then by using SDK manager tools, I also installed USB drivers.
As the device can connect download mode, I installed adb thing and tried to fix it. But apparently laptop does not recognize the device. I run the command "adb devices" and there is no devices in the list.
I also tried to use twrp recovery tools but again it didn't recognize the device.
When I check the Device Manager when the tablet is connected to laptop on download mode, I can see LGE AndroidNet USB Serial Port (COM4) thing installed. I also tried to install Android Device drivers (Android ADB Interface, Android Bootloader Interface, Android Composite ADB Interface) but they are not working properly and they have question mark on their left side.
So as you can understand I am drawning with the issues and don't know what to do next. Apparently laptop does not recognize the device but although I checked the xda forums and other forums for 2 days, I couldn't solve. I would really appreciate if you can help me.
Best
Click to expand...
Click to collapse
I couldn't get the computer to recognize one of my LG devices using ADB until I used this...http://forum.xda-developers.com/showthread.php?t=2588979
UPDATE: The issue stands solved [see post 5].
........................................................................................................................................................................
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode as Qualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
ohwarumbloss said:
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
Click to expand...
Click to collapse
I face the same issue on my OnePlus 9 and this help me. Thank you so much.
binary**# said:
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode asQualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
Click to expand...
Click to collapse
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
raoakashyadav said:
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
Click to expand...
Click to collapse
Sorry for the delay in reply. Yup, I fixed this issue via the Disable Driver Signature Verification tweak as shown in this video. In short -->
Install Qualcomm USB Driver and download MSM Tool.
Boot your device to EDL Mode and connect it to your PC.
Then DO NOT disable Driver Signature Verification on your PC.
So as of now, your device will be listed as Qualcomm HS USB QDLoader under Device Manager but will have a yellow exclamation mark [because Drive Signature is enabled]. But at the same time, Windows will hold your device in this ELD Mode and wouldn't let it boot to the OS [which is what we wanted].
So while having your device connected to your PC in EDL Mode, now disable Driver Signature Verification. With this, your device should now stay in EDL Mode and will be listed without any yellow warning sign under Device Manager. You could now proceed ahead with the flashing via MSM Tool without any issues.