Related
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
dsore1218 said:
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
Click to expand...
Click to collapse
I can't get mine to work either. Closest thing I've gotten is using omap4boot-for_optimus-v1.21
its different from some of the others, in that its a blue background and it doesnt actually list the p769. However, after selecting option 5, and following onscreen instructions, I was able to get my front capacitive buttons to light up, but nothing else. I can't enter S/W upgrade mode, I can't get LG recovery tool to recognise my phone, I am absolutely **** out of luck. I dont know if using omap4boot-for_optimus-v1.21 will help or hurt you, but im just explaining my experiences.
Have you installed the omap driver for fastboot?
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
I don't have Windows 8.1 so I'm not sure how to address the driver issue. I reer as wel.commend you uninstall the driver, both of them. The one under Android Phone in the device manager and the one called TI Boards in the device manager.
1. Uninstall all OMAP drives (Two of them)
2. Disconnect from the internet (to preventing Windows update from selecting its own driver.
3. Follow steps to fastboot. When connecting your phone have device manager open and right click the device that is flashing on and off (you will see the device manager refreshing and stuffs. It will dissappear after about two seconds but if you get the right click in and the option to install the driver, do it, point to the fastboot driver.
4. Disconnect phone after driver install and pull the battery.
5. Fastboot again, using option 1.
6. Quickly install same driver on the new device in device manager. Be quick.
7. Disconnect, Pull battery
8. Fastboot again
9. Flash ICS U and X
10. Make sure your LG drivers are installed.
11. Reboot PC.
12. Now you should be able to get into SW UPGRADE MODE with the plugging in of the USB
Should not lock up at 15%, make sure you have drivers installed for this.
13. Should work and reboot to home screen automatically.
14. If you really must, fastboot again and install JB U and X
dsore1218 said:
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
Click to expand...
Click to collapse
I've heard fastboot (and several other programs) aren't working on Windows 8. You need windows 7
Sent from my LGMS769 using XDA Premium 4 mobile app
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Hey guys, new member here but been a lurker off and on for awhile.. not sure what to do, you guys are my last hope.
I have a Samsung Galaxy Core Prime from straighttalk. Android version is 4.4.4 (I think).
Anyway, I was screwing with it trying to speed it up using a few apps I downloaded from the store, the apps let you uninstall apps that the normal manager won't let you and manage what system apps are allowed to run at startup..etc. also I was messing with applock and phone encryption.. So I'm not sure what messed things up.
Well needless to say, I shoulda been more careful, because now my phone is screwed! I can't view my home screen at all so can't call/txt and can't access my settings to try to fix the problem..
Before people tell me to reformat it, I have tried 100 times.. I press volume up + power + home to get to bootloader and tried doing a full reformat as well as wiping the cache partition... Reboot phone the setup screen comes up asking for my name/google account..etc but I can't complete it, it always crashes sayin either "hangouts has stopped working" "setup wizard stopped working" or something about a android.keyguard service.
So next I jumped on Google and read to try the Kies software but I can't for life of me get it to detect my phone.. took awhile but I think I got all the drivers installed.. kies will just say it's connecting to my device but never does. Tried kies 2 and 3 and different cords, I think it's because android isn't even truly fully installed since the setup wizard crashes.. so the MTP capability isn't even there.. under my computer I don't see my phone either like I use to, just a blank drive that has no name and can't be accessed.
So then after more reading I decided to try "ADB sideloading".. I'm a newb is to this stuff so idk if I even did it right but hooked usb up went into bootloader and reformatted/cleared cache then I went to ADB and using cmd on my pc I tried to send a zip of cyanogenmod (got it on xda, suppose to work on galaxy core prime) and it said it was successful but it doesn't do anything.. so idk if it's cuz u can't use custom roms with the stock bootloader? I read about other Rom managers but how am I suppose to install them?
if a stock firmware will work, where can I find one?
Sorry for the wall of text, I'm just stuck here and wanted to add everything I could think of that I tried already.
I dont think it's a physical hardware problem, I think i just screwed some system files up somehow which screwed up the recovery partition..
Extra note:
I am able to use the internet browser though, when the setup gets to the step to link your google, in the top right I can go to "enter browser signin" and then I can bypass the fact there's no search bar by clickin privacy policy and clicking a logo to bring me to Google's homepage.
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Mr.cryptkeeper said:
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Click to expand...
Click to collapse
Get a custom recovery (preferably twrp) and then wipe EVERYTHING in the wipe section except your sdcard and then just adb sideload cyanogenmod or any other CUSTOM rom for your phone.
You should just be able to reload the original firmware with Odin. Or Kies will probably work, but you have to use Download Mode to be able to restore it, not while it is booted into the OS.
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Mr.cryptkeeper said:
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Click to expand...
Click to collapse
Yes you have to be in recovery to actually be able to do adb sideload, try adb reboot recovery.
Good Morning Ladies and Gents;
I am working with an LG G4 H811 (T-Mobile) on 20v (MM 6.0), which I would like to root. I have unlocked the bootloader, which is confirmed every time I start the phone. I then tried to root using LGUP, but the phone wasn't recognized, so I did an error recovery reinstall in LG Bridge, thinking a fresh software install would re-align things.
Now, whenever I connect the phone to the computer, I get a pop-up window on the phone saying "USB Connection - Allow this computer to access your phone data?" CANCEL/ALLOW and the phone does not show up on the PC screen or in Device Drivers until I tap "ALLOW". Therefore, it is not recognized by any software without tapping ALLOW.
More than an inconvenience, this effectively prevents me from any mods on the phone, because I need to shut off the phone and disconnect from the USB port, then reconnect with Volume UP pressed to get to download, and in download mode I have no access to ALLOW the USB connection, so neither ADB nor FastBoot recognize any devices, and the phone is not included in Device Manager.
Of course, the bootloader is unlocked, Developer Options enabled, OEM Unlock on, USB Debugging on. I am using an original LG USB cable. I have tried 4 different computers and three different sets of drivers. I've tried older drivers on older and newer computers, and vice-versa, for every combination available. Each time, I plug in the phone after a fresh computer install and let it install it's own drivers. Two of the computers are Windows 7, two are Windows 10. I've tried connecting in MTP mode and PTP mode, with no difference. I've removed the SD card in case it was affecting things, and done a factory reset on the phone. Auto Play options have been set on the PC to "Do Nothing". I've searched the internet and this forum without results.
Basically, I've spent two days on this before asking for help. Has anyone else had this experience and solved it with something other than drivers? I think I've just about run out of ideas! Thanks.
I don't root however it's probably Developer options>usb default settings>usb tethering
Try connecting directly from Disk Management on the PC. Use the scan for new drives option if it's not visible.
Thanks buddy, appreciate you trying to help out.
Tethering is a way to allow a device connected to your phone to use the phone's data connections. In the tethering instructions:
"You may not be able to access the data files stored in the phone's memory, such as pictures, music etc, or transfer such files between your phone and your PC when USB tethering is on"
However, its worth a try - so I set up tethering, unplugged the phone and plugged it in again - the same Cancel/Allow screen came up, and no device in DM until I tapped Allow.
I then opened Disk Management and plugged in the phone. I still get the Cancel/Allow screen, and rescanning devices didn't show anything new, because the phone is not in the Device Manager until I tap Allow.
The key here is finding out why the phone or computer do not store the "Allow" command. Normally, the phone will show this screen the first time you plug it into a computer, and when you tap Allow, it will store that someplace such that the phone and computer are recognized as safe devices. You should never have to see the permission screen again. My challenge is that I don't know where that permission is stored - is it on the phone, the computer, attached to the driver? Don't know. And I don't know why it's not being saved. If I had those answers, I could probably edit the registry (or whatever) to make this a permanent attachment.
Thanks!
You're welcome.
Maybe debug mode?
Try turning off Developer options.
Obviously there is a way, sorry but I never had to use that function.
Try some Google searches which is how I usually find answers and/or by just playing with it
Well, I wouldn't be able to communicate via ADB with Developer Options off. And I spent two days searching the internet before coming here, and all I found was people updating their drivers, which is why I tried so many combinations of Windows versions and drivers versions.
I'm actually kind of surprised that this seems to be such a unique problem, I was hoping someone would notice the post who had actually had a similar problem and fixed it. But I do appreciate you trying to help!
Sorry I can't help, but I never choose to root.
It's time sucking black holes like this that I deliberately want to avoid.
At least you didn't brick it...
ha ha... you got that exactly right! Every time I do this I end up spending DAYS trying to get up to date on everything that has changed since my last phone!
Well, I appreciate you taking time to try to help.