Database Users

Losing ADB Device when going into recovery

So ADB was working (I thought?) and ADB recognizes my phone when I just plug it in, but when I go to do the steps for rooting, it no longer recognizes it.
I got it to say offline ONCE after the loop, but the on the unplug re-plug, it went away. I'm bummed...

cmon now http://forum.xda-developers.com/showthread.php?t=703429

You must have misread my post. I've looked thoroughly through that post, actually.
What I am needing help with is after that loop, going from offline in ADB to recovery...
thanks!

Can A Mod PLease Lock this thread, thee is Multi Post in Multi threads Reading this!
The Answer you are Looking for.... UN-PLug the the USB wait 5 second if that and plug it back into the Phone..

I did that, on several different occasions, but alright, will try again. Thanks.

missxoash said:
You must have misread my post. I've looked thoroughly through that post, actually.
What I am needing help with is after that loop, going from offline in ADB to recovery...
thanks!
Click to expand...
Click to collapse
ITs not recognizing your phone when in recovery thought correct? if so thats the same thing discussed there. If it did recognize it as offline in recovery then do as eugene said.

missxoash said:
I did that, on several different occasions, but alright, will try again. Thanks.
Click to expand...
Click to collapse
it needs to stick to offline, not just say it onec or twice. itll say offline many times not just once then disappear. Once it does it and sticks, it doesnt turn off, you dont need to rush and hit ctrl c

I'm having a issue that's somewhat related. I have a tmo mts3g and I had it rooted with no issues following the instructions provided in eugene's previous posts on the matter. Tmobile recently dropped a OTA update for 2.1 and it relocked my phone. Now that I'm trying to reroot it I'm having issues getting the phone to be adb online in recovery mode. I do adb reboot recovery and when it starts I have the loop going and I have no problem getting it to say "device offline" but when I unplug the device (no matter how long I wait) and plug it back in it still remains in "offline" status under adb devices. I've heard about driver issues and all kinds of other madness but I'm using the same computer that I used when I rooted it previously. My question is; is this something tmobile might have fixed in their ota update and am I just wasting my time continuing to try this method? If not i'm more than happy to continue to try but not if it's with no point.

Thing is you did the OTA update, so instead of following the old guide, you follow the one in the rom bible in the development section. Hope that helps.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

Yeah, I found my way there eventually. I got it all straightened out and currently on Eugene's MyFroyo6 with no complaints. Thanks

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

ATT update 2-9-16?

Just got a notification of an update on my ATT h810.. Can't check it out bc of no WiFi... Can anyone chime in on this one? I briefly scoured the forums and haven't seen anything on it. Forgive me if I'm late to the party.
EDIT: http://m.androidcentral.com/marshmallow-finally-hitting-lg-g4-att States the update rolling out.
http://www.att.com/esupport/article.html#!/wireless/KB426794

InflatedTitan said:
Just got a notification of an update on my ATT h810.. Can't check it out bc of no WiFi... Can anyone chime in on this one? I briefly scoured the forums and haven't seen anything on it. Forgive me if I'm late to the party.
Click to expand...
Click to collapse
it is indeed MM. https://www.att.com/esupport/article.html#!/wireless/KB426794

Awesome. I been wanting to factory reset my phone to have it fresh again. Good thing I waited.
I take it I should hold off until its rooted eh

Working on actually capturing this OTA although I'm sure someone beat me to it already. Using download mode to hijack root since I never rooted my device. Found an easy way into download mode while I was at it. XD
EDIT: Looks like it is one of AT&T's dlpkgfile bits. It is what I got so I'm going to post it on mediafire when I get a chance. Still not noticing if someone already did it. Looks like you can use it to force ota update like on the G2 or similar with AT&T.
For those wondering I found you can enter download mode while in the OS by running Send_Command against the diag port that is still open even in normal mode. You have to be in MTP usb mode to see it though. When you run the command type ENTER and press enter. It will quit and a few minutes later it will reboot to download/diagnostic mode on its own. After that run the command again and copy whatever you want to keep to /data/local/tmp. chmod the files to 777 so that it can be read/retrieved in normal mode then type LEAVE to reboot back to normal (no battery pull needed). When accessing files in diagnostic mode you must use full path locations. For some reason cd command doesn't do anything. In theory you could upload my ota files back to the phone then copy them to /cache/fota and execute the task from the system when in the android OS.
EDIT: OTA capture upload -- http://www.mediafire.com/download/cc86c5dx6xzz2pt/LG_G4_H810_ATT_Android_6.0_OTA.zip

can anyone confirm that the MM build can be rooted with the normal method: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
and is xposed working on 6.0?

Root isn't possible on 6.0 without a bootloader unlock. LG closed the loophole in download mode.

I'll just have to live with the annoying notification until we find root I suppose..

Is any other AT&T user having trouble with their physical power button working after the update? I updated last night at three times so far I've had to repeatedly hit the power button before the screen would turn on.

InflatedTitan said:
I'll just have to live with the annoying notification until we find root I suppose..
Click to expand...
Click to collapse
why don't you just restore using the 10o TOT? that will get rid of any traces of root then take the MM OTA.
http://forum.xda-developers.com/att-g4/general/att-h810-to-stock-guide-tot-method-t3248532

uly609 said:
why don't you just restore using the 10o TOT? that will get rid of any traces of root then take the MM OTA.
http://forum.xda-developers.com/att-g4/general/att-h810-to-stock-guide-tot-method-t3248532
Click to expand...
Click to collapse
Can anyone confirm that this update to Marshmallow for the G4 H810, will allow the FM Radio to work? I know sometime ago they talked about this http://www.techtimes.com/articles/7...artphone-makers-to-turn-on-fm-radio-chips.htm

No. This update does not enable access to an FM Radio chip in the phone. Either there isn't one or it is still inactive inside the device.
Tested using NextRadio from Google Play.

shinji257 said:
EDIT: OTA capture upload -- http://www.mediafire.com/download/cc86c5dx6xzz2pt/LG_G4_H810_ATT_Android_6.0_OTA.zip
Click to expand...
Click to collapse
How can we flash this its manually that you captured? I'm not getting the update as being available for me.

Been a while since I've been here, as when I got my G4 there were hardly any threads in the forum for this device. Got the Marshmallow update yesterday from LG (software version H81020N). So far, things appear to be working normally. Noticed the touch screen is more sensitive, but not much else yet.
I haven't reset the phone yet, as I was at work when it updated and I didn't have time to reinstall everything. Is a reset required?

Spectre51 said:
How can we flash this its manually that you captured? I'm not getting the update as being available for me.
Click to expand...
Click to collapse
I think we can flash it via cache/fota folder , in older LG G version phones thats was an option, but you need to have rooted your G4 , my G4 is virgin never rooted, you think can we use "CACHE FOLDER" method this time ?

You should be able to use the diagnostics mode route that is used to root the device in the first place as long as you are still on lollipop. Just keep in mind that hole gets closed as soon as you go to marshmallow. Same steps apply except you would adb push the files to /data/local/tmp before going into diagnostics mode then move the files to /cache/fota once in diagnostics mode.
EDIT: You have root while in diagnostics mode which is probably why LG closed it up in the marshmallow release in the first place.

you suggest that I can use the method of diagnosis mode, to force the update using which commands? i have the dlpkgfile with their propers permissions same as /Cache/recovery folder permission
Which command you suggest to use ?
Code:
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart

So I assume I'm the only one having issues with Marshmallow?
I have trouble turning my screen on and off, my Gmail will not sync up, and my mobile data is struggling to work. Pages barely load, taking much longer than before and I constantly get a no connection error with my Gmail.

uly609 said:
why don't you just restore using the 10o TOT? that will get rid of any traces of root then take the MM OTA.
http://forum.xda-developers.com/att-g4/general/att-h810-to-stock-guide-tot-method-t3248532
Click to expand...
Click to collapse
Bc I want root lol... Ive forced myself to live with locked bootloader and no development... But I refuse to go without root....

shinji257 said:
Working on actually capturing this OTA although I'm sure someone beat me to it already. Using download mode to hijack root since I never rooted my device. Found an easy way into download mode while I was at it. XD
EDIT: Looks like it is one of AT&T's dlpkgfile bits. It is what I got so I'm going to post it on mediafire when I get a chance. Still not noticing if someone already did it. Looks like you can use it to force ota update like on the G2 or similar with AT&T.
For those wondering I found you can enter download mode while in the OS by running Send_Command against the diag port that is still open even in normal mode. You have to be in MTP usb mode to see it though. When you run the command type ENTER and press enter. It will quit and a few minutes later it will reboot to download/diagnostic mode on its own. After that run the command again and copy whatever you want to keep to /data/local/tmp. chmod the files to 777 so that it can be read/retrieved in normal mode then type LEAVE to reboot back to normal (no battery pull needed). When accessing files in diagnostic mode you must use full path locations. For some reason cd command doesn't do anything. In theory you could upload my ota files back to the phone then copy them to /cache/fota and execute the task from the system when in the android OS.
EDIT: OTA capture upload -- http://www.mediafire.com/download/cc86c5dx6xzz2pt/LG_G4_H810_ATT_Android_6.0_OTA.zip
Click to expand...
Click to collapse
Shinji hello, Excuse me, what do you mean execute task in the android os? which task?

shinji257 said:
You should be able to use the diagnostics mode route that is used to root the device in the first place as long as you are still on lollipop. Just keep in mind that hole gets closed as soon as you go to marshmallow. Same steps apply except you would adb push the files to /data/local/tmp before going into diagnostics mode then move the files to /cache/fota once in diagnostics mode.
EDIT: You have root while in diagnostics mode which is probably why LG closed it up in the marshmallow release in the first place.
Click to expand...
Click to collapse
can you make a post or tell us how to upgrade by dlpkgfile for H810? I don't know how to upgrade my phone

Stuck at fastboot/LG Logo

I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.

codman2728 said:
I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.
Click to expand...
Click to collapse
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "

If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.

Fixed!
jinkerz9430 said:
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "
Click to expand...
Click to collapse
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.

Thanks
androiddiego said:
If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.
Click to expand...
Click to collapse
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.

codman2728 said:
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.
Click to expand...
Click to collapse
If you flashed stock with lgup then everything is back to factory settings. Is this is the case, then the autorization you gave to your computer via usb debbug (where the prompt appears if the device is connected to a other device without authorization asking you whether you want to authorize it or not). Is also back to factory settings. Which means not even developer mode is on. But after you turn developer mode on and usb debbug then connect the phone to the computer and it will ask you once again for authorization

[/B]
codman2728 said:
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.
Click to expand...
Click to collapse
That's it!

How Unlock USCellular LGUS997

I tried searching for "us997", but the search came back with an error, even though I know there are threads with "us997" in the thread title. So, forgive me for posting this new thread.
Now that the warranty has expired for my LG-US997 phone, I'd like to unlock it so that I can install Android 10 in it. It currently has 8.0.0.
I'm assuming that there is a thread specific to this phone. I'd appreciate said link.
Thanks.

Try this thread : https://forum.xda-developers.com/lg-g6/help/us997-cellular-brightpoint-bootloader-t4102267

challenger07 said:
Try this thread : https://forum.xda-developers.com/lg-g6/help/us997-cellular-brightpoint-bootloader-t4102267
Click to expand...
Click to collapse
I saw that, but dismissed it because it is about brightpoint. I have no clue as to if I have a brightpoint device. I tried using the IMEI info website, but my number is only 14 digits and they wanted 15. I filled out their contact form about it, but I've not received a response.
Even if I can unlock the phone, is Android 10 even available as a custom ROM for the phone?

I think I found custom Android 10 for the US997: https://forum.xda-developers.com/lg-g6/development/rom-havocos-v2-1-t3893668
I've downloaded the zip file.

Next step was to unlock the phone. That did not go well at all. Followed the steps from here: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
When I did this step: adb reboot bootloader
I got: no devices/emulators found
The Win7 box sees the phone, because "G6" shows up in explorer so that I can get at the SD data, internal and external.
Sigh! No fun, no fun at all.

I assume you have read the guide I wrote when I moved mine to Havos? https://forum.xda-developers.com/lg-g6/how-to/guide-step-step-install-android-10-t4141901
I would check your cable I've had issues in the past where I didn't have a quality cable, the normal reason your PC doesn't respond is that you have not turned on ADB in developer settings.

challenger07 said:
I assume you have read the guide I wrote when I moved mine to Havos? https://forum.xda-developers.com/lg-g6/how-to/guide-step-step-install-android-10-t4141901
Click to expand...
Click to collapse
Sorry, no. I had not seen that.
I would check your cable I've had issues in the past where I didn't have a quality cable, the normal reason your PC doesn't respond is that you have not turned on ADB in developer settings.
Click to expand...
Click to collapse
The cables are fine. As noted, Win7 mounts the phone and it shows up in explorer as "G6". ADB Developer settings were indeed turned on. Phone even welcomed me.
I'll be going thru your steps and will report back.

Well, looks like I am stuck until LG gets back to me as to why I am getting the error message. The LG instructions didn't have the user download the device driver, which your instructions did. I downloaded and installed and re-entered debugging mode. I re-ran the adb command, but it still comes back no devices found.
The device driver poped up a message that it did not successfully install. Of the five items in the list, it failed to install the MTP device. Looking in the device manager, I can see the MTP device, but is marked that it cannot start. Code 10. Device driver is up-to-date.

I don't know about the device driver but I searched Google and there was a useful article on unlockunit website under blog / 14-digit-imei/

In another thread, I wrote that I found the 15 digit IMEI number on the box. Unfortunately, because the adb program can't find the device, I can't get the device ID in order to get the unlock.bin file from LG. LG still has not responded to my query via their website. It looks like my attempt to unlock this phone is for naught.

Doing a little more reading, I've discovered that U.S.Cellular phones, sold after Feb 2016, are unlocked. Meaning that I can take the LG G6, in theory, to another carrier. But, that doesn't appear to mean that I can put a different Android release on it. Is the term "unlocked" being used to define more than one thing?

Since LG has not called me back, I've placed an order for the Pixel 4a.