Hello everyone,
I bought this phone on sale last year and it was advertised as follows...
Refurbished: LG G Flex2 H950 32GB Unlocked GSM 4G LTE Octa-Core Android Phone
In browsing the forums here I see the excitement around this phone has waned quite a bit since it's release, but I'm hoping there's still a few of you left who might be able to help me. I totally love this phone and want to be able to use its full potential.
It's branded as an AT&T phone when the boot-up screen appears. I doubt it was sold as unlocked by AT&T, but rather Newegg, or someone they're reselling for, unlocked it. I've never been an AT&T customer. I bought it knowing I could use any carrier willing to sell me a sim card. I'm currently using Mint.
It came with the 5.01 firmware. I've spent many days reading every thread I can about how to upgrade it, and possibly get Marshmellow as well. The issue is that I can't seem to find any drivers that function properly. Here are all the ones I've tried...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only one that's come close to fully functional is the top one for version 3.11.3.0 It's the only one that recognizes all of the sub-devices no matter how many times I unplug the USB cable and plug it back in. The only other one that came close was version 4.2.0
I use a program called USBDeview, which provides live monitoring of USB connections and shows a great deal of info about each one. In the images I'm going to share, I've shrunk away all of the columns except the ones I think are most relevant. The ones with Green dots mean it sees them as a working, connected device. The ones with Gray dots mean that there is a record of this device connecting, but that it does not see them as currently connected. And the Purple dots mean it sees the device as connected, but that there is some issue with its functionality.
Here's the result when I use the 3.11.3.0 driver...
All 5 devices show green and everything action I've tried to perform from studying guides here works perfectly. And, as I said, it keeps working no matter how often I reconnect it. The only weird thing is that USBDeview reports the version as 3.11.0.0, even as the filename and the file properties report it as 3.11.3.0 It reports correctly for all the other drivers I've tried, but I guess it's nothing to complain about at this point.
The problem is that whenever I put the phone in “Firmware Update/Download Mode” I get this result...
The LGE Mobile Sooner Single ADB Interface driver now shows as disconnected, and as such, I can't send any ADB commands and my device doesn't show up on the list when I type "ADB Devices". It doesn't indicate there is a problem, it just shows it as not there. This issue is thwarting all my efforts to upgrade the phone.
With the 4.2.0.0 driver, I get a similar, but slightly different result. Sometimes I got this when connecting the phone in normal mode...
And other times I got this...
I can't account for the different results because I was trying all kinds of tweaks and fixes between different attempts. But one thing was universal with this version: They would all show green for up to a minute or so and then all but one would start disconnecting until it looked something like this...
The other drivers I tried were similar. Some recognized more devices, some less, and some would look like the above on their first use. Some were consistent and some would look okay for a minute and then disconnect.
When it came to Download Mode, some would see the ADB driver and some would see the USB driver, but I still haven't found one that will see both. When I check the error logs, I most often see something like this...
So if anyone has a driver that they know works on this phone and has definitely used it to upgrade this model in Download mode, please let me know.
Also, if you know of a method to accomplish my goal without using Download mode, please point me to some steps to that method.
Just to avoid the obvious advice, I've tried a great many fixes...
Turned off Fast Startup.
Disabled ability to turn off device for power savings on all USB hubs.
Disabled USB Selective Suspend.
Disabled firewall and all other protection settings in Windows Defender.
Uninstalled my anti-virus.
Disabled Windows automatic device updates in Group Policy.
Made sure all my other devices have the latest drivers.
Update my BIOS to the latest version.
Windows 10 Pro is up to date.
As one person advised, tried to manually update the devices that wouldn't connect using lgx64bus.inf from the driver folder.
And various registry tweaks.
Thanks in advance for any help.
NOTE: In going through all the drivers again, I discovered that version 3.14.1, at least on the surface, is performing exactly as ver 3.11.3 has been. Works perfectly in normal mode, missing ADB device in Download mode. Guess I skipped it in my first few runs. Still doesn't solve my problem, but I strive to be accurate.
NOTE 2: I have found a method for flashing that does not require ABD to flash my phone. I can't find an option to delete this post, so the moderator has my permission to do so at their discretion.
Related
Running CM10 stable on a Telstra One XL.
I have adb drivers installed, and they work fine. But when I enable usb tethering, the device does not install or find drivers. I get these two broken devices in device manager, including a USB hub device that claims it cannot start (and disappears when I disable USB tethering):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So annoying, since wifi tether drains more battery than is charged back into the device via USB.
I believe USB tethering requires HTC sync installed. But I've never got it to work properly either way
Sent from my HTC One XL using xda app-developers app
Maybe you've seen this. If you haven't , hopefully it will help.
http://forum.xda-developers.com/showthread.php?p=26589828
Cheers
Sent from my One X using xda premium
No luck with HTC Sync. It just means that when I enable USB tethering, the HTC Sync window opens up. The device remains with an exclamation mark in device manager.
No one else has gotten USB tether working on Windows 8?
Passa91 said:
No luck with HTC Sync. It just means that when I enable USB tethering, the HTC Sync window opens up. The device remains with an exclamation mark in device manager.
No one else has gotten USB tether working on Windows 8?
Click to expand...
Click to collapse
Hi,
I was having the same issue. Today I got it to work, sort of. I flashed to the latest nightly build (19/12) and also flashed to the EVITA 2.40 Radio for Telstra HOXLs. I'm not sure if this brought a change. What I have found is this:
A standard Mass Storage Device driver is installed when setting the phone to USB Storage mode.
If I then disable USB storage, and enable USB Tethering, the storage driver in Device Manager gets a yellow icon next to it indicating driver failure. Now, if I update the driver for that device (automatically search for updated drivers), or even delete it and scan for hardware changes, Windows finds a Remote NDIS driver for the same device, and tethering starts to work i.e. a new network is found.
If I then disable tethering and switch back to USB storage mode, then the Remote NDIS driver gets the yellow device failure icon next to it. Deleting that and rescanning, or updating the driver gets it back to the storage driver and the drive mounts.
I did not need to have USB Debugging enabled, as that simple enables the ADB interface. It did not impact how tethering worked.
So there seems to be a problem with switching between the two drivers. Like there should be a device ID change to allow 2 separate drivers to exist in Windows. I have posted this issue in the CynogenMod forums for the HT One XL.
I'm on Windows 8.
I tested this out on a fresh flash of CM10 with everything left as default. No backups restored etc. See the same behaviour.
I have raised a ticket with CynogenMod on their Google Code site. Issue 6857. I can't post links yet.
Please vote on it if you are having the same issue.
Thanks!
Wow, super sleuth! I too have a Telstra HOXL. Your instructions were bang on, I've got USB tethering working but only after removing the mass storage device.
Hopefully they get on this and fix it quick - seems straightforward enough. Might be an issue only affecting the Telstra HOXL, maybe because we have the extra storage NAND.
So anyone figure out a permanent fix for this?
hey, sorry for the "necro" but i just wanted to say that i had this same issue with htc doubleshot on cm9/10 and that a fix/workaround is just to set a different idProduct for rndis in the init.usb.rc inside the ramdisk
that way windows will see them as totally different devices and there will be no need to driver swap anymore
I am almost getting to the point of blowing this entire thing off out of pure RAGE. WARNING: LONG POST AHEAD!
Now where to start...
My LG Optimus V via Virgin Mobile has been having every problem in the book lately. I have retrieved a new one from Virgin itself, so that should take care of the problems with calling and whatnot.
However, there are a few pretty major problems with the old one. Okay, QUITE a few.
Here is a list of my old phone's problems:
SD card slot will not read anything
Phone will not connect to computer via USB
Phone's Bluetooth is not recognized by computer ("Unable to get Bluetooth FTP Remote Folder content. Please check that your device is turned on and working properly.")
Phone will at times say my memory is almost full when at other times it says there are 8 more megabytes left
Phone's keypad will disappear in-call and will not return, making it impossible to check voicemail or dial extensions
I have installed the drivers direct from LG. I have tried booting in recovery. I have tried uninstalling and reinstalling those drivers. I have tried booting/rebooting with all kinds of random patterns to the point that my headache has amplified. I have tried to hack the connection settings with an SQLite app. I don't even see an option for USB connections except debug mode. I have tried Bluetooth through Total Commander. Absolutely nothing I find is working to get me anywhere.
For the record: My computer is an ASUS laptop with an i7 processor and Windows 7. I have tried this same USB cord with my previous phone (a Samsung Captivate that also has issues) and it works fine. Also, my phone charges through the USB port, but it isn't recognized by my computer.
Given this entire list of problems, there are a few things that are suddenly becoming impossible to do since the backup routes are blocked off. Firstly, I want to transfer my data to my new phone so it's like nothing happened. Now, this is more a "want" than "need" but it certainly would be nice. Therefore, I need to get my USB setup working. I have Googled extensively for answers... and haven't found any that work. Which is ridiculous because I feel like I'm in an extreme minority... because the answers are working for others.
Eventually, I unpack ADB and...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great. Just bleeping great.
Second, I need to unroot my phone before sending it to Virgin. I don't want to get in trouble with them. So once I have my data backed up, I need to work on reverting the phone to stock - a factory reset and an unroot. That is impossible without being able to connect to my PC. Like... I have these saved but can't start the operation:
http://forum.xda-developers.com/showpost.php?p=27670666&postcount=8
http://androidforums.com/optimus-v-...uide-100-stock-lg-optimus-v-all-versions.html
See, I have found plenty of answers for each individual problem, but everything tends to overlap. I have completely confused myself. I am getting a headache from all of this new terminology to me and all of these different answers...
The first step should be trying to figure out why the phone isn't connecting to the computer. That may resolve a slew of other issues and allow me to run ADB. But I'm fully prepared for that not to get me anywhere.
What can I do? Where should I begin? Is there anything that's even possible with this mess? Anything to go on would be greatly appreciated! And feel free to ask me any questions you have about it - I will do my best to answer
you mentioned that your phone is rooted, and I suppose that you have recovery, so try this, connect phone to pc trough usb, boot into recovery, go to mounts and mount usb and see if your phone is recognized by pc(try LGMDP and if it does, update it, but you must have ADB enabled in phone settings development) and pop up the window with sd card content
grigtm said:
you mentioned that your phone is rooted, and I suppose that you have recovery, so try this, connect phone to pc trough usb, boot into recovery, go to mounts and mount usb and see if your phone is recognized by pc(try LGMDP and if it does, update it, but you must have ADB enabled in phone settings development) and pop up the window with sd card content
Click to expand...
Click to collapse
Booting into recovery and doing that got me this:
E: Unable to write to ums lunfile (No such file or directory)
I couldn't mount "system" either. Well... maybe I did, but it didn't do anything?
Great. Just great. I am lost and confused like a little puppy dog right now... :/
I appreciate your suggestions. Thanks!
read this threads to see if you get a solution, they are related to UMS file
http://forum.xda-developers.com/showthread.php?t=1342769
http://forum.xda-developers.com/showthread.php?t=1710556
I'm having a pretty strange issue with my Nexus 5 in that it no longer shows up on my Windows 7 desktop or Windows 8 laptop (both of which worked perfectly before).
I don't just mean that I can't see it in "My Computer", but it literally shows up nowhere. Not in the device manager (not even as Asus/Acer or any other funky name)... there's just no trace of it.
It doesn't show up on "adb devices" whether booted into the ROM (CM11) or recovery, and it doesn't show up on "fastboot devices" either.
But in spite of all this, it charges via USB without an issue. It almost seems like a hardware issue of some kind, but I'm hoping it isn't.
If anyone has experienced something similar or could offer any suggestions that would be great.
Thanks.
djsubtronic said:
I'm having a pretty strange issue with my Nexus 5 in that it no longer shows up on my Windows 7 desktop or Windows 8 laptop (both of which worked perfectly before).
I don't just mean that I can't see it in "My Computer", but it literally shows up nowhere. Not in the device manager (not even as Asus/Acer or any other funky name)... there's just no trace of it.
It doesn't show up on "adb devices" whether booted into the ROM (CM11) or recovery, and it doesn't show up on "fastboot devices" either.
But in spite of all this, it charges via USB without an issue. It almost seems like a hardware issue of some kind, but I'm hoping it isn't.
If anyone has experienced something similar or could offer any suggestions that would be great.
Thanks.
Click to expand...
Click to collapse
If it's on multiple computers, it's either your phone USB port or the cable. Have you tried another cable?
rootSU said:
If it's on multiple computers, it's either your phone USB port or the cable. Have you tried another cable?
Click to expand...
Click to collapse
I used different cables as the two computers are in different locations. So looks like the phone is busted... but I'm baffled as to how this would suddenly happen, especially since it charges without a problem.
It isn't busted, the drivers have gone mad... Follow THIS guide, and it'll fix it. I had the same issue as did some other people.
Even though your's isn't showing as another device, it'll be there somewhere hidden.
radicalisto said:
It isn't busted, the drivers have gone mad... Follow THIS guide, and it'll fix it. I had the same issue as did some other people.
Even though your's isn't showing as another device, it'll be there somewhere hidden.
Click to expand...
Click to collapse
So his drivers busted on 2 separate computers in different locations simultaneously? It sounds unlikely.
rootSU said:
So his drivers busted on 2 separate computers in different locations simultaneously? It sounds unlikely.
Click to expand...
Click to collapse
Mine didn't show up on my Desktop or Laptop randomly either, on two out of three Nexus devices. A random anomaly.
EDIT: It's possible Windows updates have done it. I've had a few on both machines lately also.
@radicalisto, thanks for your suggestions. The problem is that there is nothing appearing in the device manager at all that I can use to install drivers. At least not on my Windows 7 desktop.
I'm going to check again on Win 8.1 (laptop) when I get home this evening, but from what I remember when I checked over the weekend, there was no joy there either.
I managed to force-install the Google USB drivers for "Android ADB Interface" and "Android Composite ADB Interface" (which are the ones I always used before), and this is what I get for both of them:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OP, did you find a solution? I'm having the exact same problem.
install Wugfresh's nexus root toolkit, follow the instructions on the "full driver installation guide"
i guess its the micro usb port at fault though its charging theres a possibilty thats its gone bad
I tried that! But when I plug the device, absolutely nothing happens. No device is detected. The phone simply starts charging as if it was connected to a wall charger.
Thanks for all the responses guys, I have come to the conclusion the port is faulty. I took the phone apart and reseated all the ribbon cables, cleaned out the inside of the USB port with a toothbrush and some rubbing alcohol, and when I turned it back on and plugged it in, I successfully got a USB connection -- for about 30 seconds! After that it stopped working again, and sometimes would show up on my PC as a malfunctioned USB device. Charging still works fine, and the USB device did work for 30 seconds (so that pretty much rules out it being a motherboard problem) so I'm pretty sure it's a port issue.
I'm going to buy a replacement USB port one of these days (available on eBay, Amazon, etc) and replace it and see if that works. I will report back when I eventually do (not for at least a few weeks though).
In the meantime if anyone else wants to try to do it themselves also, here is a really nice video guide:
Quick update: I think I managed to fix it... so far it's been working for a few minutes even with jiggling the plug around.
How? By using a needle. First I want to add a disclaimer that using a metal needle probably isn't the best idea since obviously it can lead to short circuiting inside the device (use a plastic or wooden toothpick instead, to be safe). I used the needle tip to scrape each individual metal contact terminal inside the USB port. I had to do this quite a few times for each port before it started working, so I'm guessing a very stubborn piece of grime or dirt somehow got in the way of one or more of the terminals, which blocked the plug connecting with the port properly.
Anyway, for you guys having the same problem, give it a try. Metal would obviously be the best choice in terms of the amount of force you can scrape with but to be safe, choose plastic, since it probably won't bend and fray like a wooden one.
I've read other posts, applied some of the suggestions, but have not been able to solve this issue. I have the current Mi Flash, I have added my account to Developer options, enabled USB debugging. added Mi account to Mi Unlock status, and oem unlock, I have turned off wifi and am using cell data. My Mi account is OK, Sim accepted. I hear the Windows notification when I plug in the phone. I don't see the phone in Explorer when I'm in bootloader. I do when the phone is not in bootloader. I have logged into Mi Account with my phone # and email address - same error either way.
Issue, I start Mi Flash and after signing in, this message briefly appears on the screen, "Checking if your Mi Account has permissions". This message disappears and then Mi Flash goes to the next screen. I follow the instructions to the letter and finally plug my phone (several times) in (it is bootloader). The Unlock button on the bottom stays grey.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wait and wait and it doesn't change. I open settings, I click the button to install the drive - I get an error:
At this point I'm stuck. I'm not sure its a driver error - the phone connects to my laptop OK and I have been able to transfer files. MTP is set default to "Transfer Files" vs charging.
As an update, I found the Poco in Device Manager, Portable devices with the following driver:
I'm guessing that this might not be the correct driver, but am not sure.
I would appreciate help with this problem. I hate the bloat Miui serves up and would like to move on to a ROM that it simple and safe. Thanks
I can't unlock too
I'm still trying to figure this out and need help. I connect to the phone through USB OK. I can access it via file explorer as a drive labelled Poco X3 NFC. I can add files via explorer and search through the phone. However, I installed Mi Suite to check drivers and with the phone connected Mi Suite pops a screen that says connect to device to usb. It already is, but I unplug and plug back in anyways, same error then it changes to this:
So its odd that it connects to the PC but does not seem to connect to the internet or Mi Suite. Is there a better USB driver to use for this. I found a Qualcom driver V1 and an adb driver R-13 Windows.
Well you have the needed Windows driver than.
Check Windows app/system error messages for clues. You may be missing a MS library or such.
blackhawk said:
Well you have the needed Windows driver than.
Check Windows app/system error messages for clues. You may be missing a MS library or such.
Click to expand...
Click to collapse
Thanks for your response. Can you be more specific? Where would I find these messages.
jjcdennis said:
Thanks for your response. Can you be more specific? Where would I find these messages.
Click to expand...
Click to collapse
I'm on W7x64. Goggle it. It you use Windows you should have discovered this important system app within you first year.
Example:
Side by side errors used to be common; missing x64 MS library (you need 2, one for 32 bit and one for x64). Sometime the apk developer fails to included in their app software; they don't need as it was needed to code the app. To run the app and get full functionality on a 64 bit system you need both libraries; a simple download from MS.
Perhaps they are now included in the 64 bit OS's unlike the XPx64 days however it's also possible the file got corrupted or deleted if so.
This is the kind of critical information MS Event Viewer can show you. It records App/System/Security events with a time stamp.
OK, this is solved. This time I went through the unlock process on my wife's Win 10 laptop. Drivers loaded, windows setup the Poco. Same thing, greyed out unlock button. I clicked on the button to install the driver and this time the driver install completed, versus the error I posted above. The screen popped back to the Unlock screen, with the Unlock button live. I clicked on one confirmation screen after the other until I got the confirmation to wait 143 hours to unlock. Glad this frustrating event is over. Hope it works at 143 hours too. Of note, I did turn off wifi and used data to unlock. I read somewhere to do do that. No idea if it made a difference.
Yay! Windows can get funny about loading drivers sometimes. You just need to play with it a bit many times to resolve the issue.
Keep Event Viewer in mind though as it can show you errors that are slowing your system down, security issues and more.
Dear all,
Two months after installing a new screen on my OnePlus 5T, the screen basically stopped working (black, sometimes flickering parts).
However: the touch function is still working. For example, I can still operate spotify, as I just know where I would have to press...
As I really wish to retrieve some information from the phone, or initiate data transfer to a new OnePlus, I would like to try screen streaming options.
Since I can't really operate any other app without seeing the screen, I wanted to force it from my computer via adb commands.
The phone is unlocked/rooted, and adb debugging enabled.
There are two approaches I would like try:
GitHub - Genymobile/scrcpy: Display and control your Android device
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com
I am planning to run these approches on a virtual machine for linux/ubuntu on a windows 11 computer, and I got it so far, that the device is being recogniced by the <adb devices> command, showing the device number.
However, the phone is also unauthorized, potentially hindering me from continuing with scrcpy (and potentially any other adb driven approach).
Please find the following output.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Of course, the internet provides solutions to that problem but they all require me to use the screen of my phone. (Which technically is possible, but I just can't see where I am tapping/if popups come up etc.).
So here's my question(s):
Is adb-driven screen streaming the only option I have at that point?
Are these approaches reasonable, or is there an easier solution?
Is there a way to properly set up the adb connection, that is also compatible with the broken screen problem I experience?
As this seems to be a more general question, I wasn't sure where to put this thread, but I could imagine that many approaches could lead to a satisfying result.
Just in case everthing fails, I also ordered a new screen from china, but it will probably take around 3-4 weeks to arrive...
I would greatly appreciate any suggestions or feedback.
Thanks in advance!
Ulrich
TheSlashed said:
Dear all,
Two months after installing a new screen on my OnePlus 5T, the screen basically stopped working (black, sometimes flickering parts).
However: the touch function is still working. For example, I can still operate spotify, as I just know where I would have to press...
As I really wish to retrieve some information from the phone, or initiate data transfer to a new OnePlus, I would like to try screen streaming options.
Since I can't really operate any other app without seeing the screen, I wanted to force it from my computer via adb commands.
The phone is unlocked/rooted, and adb debugging enabled.
There are two approaches I would like try:
GitHub - Genymobile/scrcpy: Display and control your Android device
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com
I am planning to run these approches on a virtual machine for linux/ubuntu on a windows 11 computer, and I got it so far, that the device is being recogniced by the <adb devices> command, showing the device number.
However, the phone is also unauthorized, potentially hindering me from continuing with scrcpy (and potentially any other adb driven approach).
Please find the following output.
View attachment 5756521
Of course, the internet provides solutions to that problem but they all require me to use the screen of my phone. (Which technically is possible, but I just can't see where I am tapping/if popups come up etc.).
So here's my question(s):
Is adb-driven screen streaming the only option I have at that point?
Are these approaches reasonable, or is there an easier solution?
Is there a way to properly set up the adb connection, that is also compatible with the broken screen problem I experience?
As this seems to be a more general question, I wasn't sure where to put this thread, but I could imagine that many approaches could lead to a satisfying result.
Just in case everthing fails, I also ordered a new screen from china, but it will probably take around 3-4 weeks to arrive...
I would greatly appreciate any suggestions or feedback.
Thanks in advance!
Ulrich
Click to expand...
Click to collapse
it could be a hardware issue, most probably loose connection with the LCD Digitizer. you could try fixing it at a service or on your own.
Hey, and thanks!
You're right, it is most definitely a hardware issue. Hence, I ordered already a new screen.
Not sure if I want to break apart the whole phone again to check the connection to the LCD digitizer, if I can first try some software approaches...
The most pressing issue I have right now, is the missing authorization for usb debugging, as I can't answer any confirmation prompts send to the phone.