So the title pretty much says it all and it's a pretty weird problem. Every time I connect my cyanogenmod via USB to my computer it reboots and wants a firmware update. As far as I can tell, this started happening while I was developing an app. I was using android-studio to run it on my phone when gnome started having problems mounting it.
It shouldn't have been mounting it to begin with because the phone was only connected for usb-debugging. However, because gnome was having problems, it kept trying to mount the phone and I was getting mount notifications every couple of seconds. Because this was so annoying, I disabled auto-mount in the dconf-editor in gnome. The notifications stopped, but at that point, android-studio was also not able to install the app on the phone anymore. Then at some point, the phone "crashed" and restarted, asking me for a firmware update.
I can restart the phone into normal mode by disconnecting the USB cord and holding the power button. Then everything works fine, but still every time I connect the phone to USB, it reboots, wanting a firmware update. I've tried doing adb devices while the phone is in the firmware screen, but adb doesn't find my phone, so I can't even debug like that.
Is there a way to debug or fix this? Or is there a way cancel the firmware update from the firmware screen, so that it won't interpret a usb-connection as a signal to do a firmware update? BTW, the phone is an LG G2, in case that makes a difference.
So I've researched this a little further and found the answer here. This seems to have been a side effect of not having enough space left on the device. It would be cooler if they had said something to that effect, but at least the problem is solved
Related
My goal is to get my Moto G6 phone in Root Mode. I bought a blank phone for this purpose, so no data is at risk. After following the steps on the XDA guide, I only got so before things did not work as they described. If I reboot my phone, I get this blue Moto G6 bootscreen and the phone never boots. I can get TWRP running on the phone though. Right now, my phone is not being recognized by either adb or fastboot. The guide I've been following is at
https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569
c:\Software\MotoG6>adb shell
error: no devices/emulators found
c:\Software\MotoG6>fastboot devices
c:\Software\MotoG6>
I have the latest Moto G6 drivers installed, but I don't think they apply anymore. If I unplug and replug in the USB cable into my Windows machine, it says it does not recognize the device.
The firmware I saw on the device when it did boot was OPSS27.82-87
* I do not know how to go back to stock because it won't recognize the device enough for me to push the stock image to it. *
*** FWIW, even on step 3 of that guide, it would say the boot image was not signed or corrupt. This happened when I tried to do
fastboot flash boot <insert-boot-image-name-here>.img
someone else had that problem and the recommendation was to ignore the message and reboot to recovery.
(https://forum.xda-developers.com/moto-g4-plus/development/wip-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586/page2)
For those who would say, "Read the **** manual", bear in mind that I did read the manual. No manual said where to get the firmware information they asked for. Also, many of the image links were bad. They did not say how to handle the case where the image did not install as they said it would. Somehow these manufacturers make each phone just enough different, and each firmware is different that it's impossible to predict what a phone will say ahead of time with certainty.
When it shows no commands, press and hold the power button then tap volume up button once. Then release the power button.
If this doesn't work mostly likely needs to be sent back to the manufacturer.
Unable to install the drivers for the usb debugging mode on android-system.
The device — Sony Xperia V with Android 4.3, on the PC — Windows 7 Home Premium.
Phone Information in Device Manager. There he defined as "portable device". Sorry for language. It is russian :(
I downloaded the latest ADB drivers from the sit Google, set them manually, and the picture is as follows:
ADB does not see the phone.
Update the Windows driver does not, on the grounds that the best of everything is already.
If remove them when you reconnect a Windows device starts again instantly put all the same his driver.
Disable automatic driver installation failed. In the Home version of Widnows is only possible to disable autostart them with auto-update service, which I did. Set gpedit.msc, where he was to be an item on the prohibition of automatic installation of the device, but it was not there.
You can connect your phone is turned off debug mode and then turn it on. In the Device Manager list is updated, but nothing new in it does not appear.
I faced with this problem for a long time ago when I try to install a custom recovery . Then the phone just was not detected, probably due to lack of drivers. Tried in vain to fix anything, but it was easier to use someone else's car, where the driver got up at once as it should. Now, the problem still want to overcome, for debugging applications on android-emulator inconvenient, it would be nice to do it several times on a real device.
Now I don't know what to do :( Help me please.
You have to install the PC Companion from Sony.
So I've read nearly every stack overflow answer about this issue, but still no solution. My device keeps getting disconnected. I've switched through 12 wires, I've tried every USB port; nothing. Eclipse keeps dropping the connection. It happens most often when I enter debug mode. Has anyone found a solution to this? Is this a bug in the new update? Seriously, this makes debugging and testing so painful. It slows down my testing by at least 3 times. There has to be a better solution.
First thing I tend to try is the following commands in cmd/terminal
adb kill-server
adb start-server
And lastly,
adb devices
To check the device is connected.
Following that I'd try restarting the device, and perhaps as a last resort uninstall/reinstall it's drivers.
Edit: also, do you have access to another device? In the past I've had issues with specific devices constantly dropping out.
I experience that when my nexus7 2012 kept disconnecting; root cause was the USB3 connection.
Changing to a USB2 port fixed my issues; can you try switching to a lower speed port?
I was having a very similar problem but using Android Studio on OS X. By default Android Studio points to an SDK inside it's application bundle so I changed the SDK location setting to point to another version of the Android SDK I had downloaded manually and this seems to have fixed the disconnection issues I was having.
Instructions for changing the SDK location setting can be found in this answer.
My connected device (an Acer) was working a treat until I rebooted my mac. After the reboot, Eclipse dropped the connection every single time I ran the app. I tried two cables and every port in my iMac but nothing worked. I had to disconnect and reconnect the device for every run (a real pain when debugging!).
What worked for me was to run the app. When the window appeared to choose the device to run on (which was empty), I disconnected then reconnected the device, but before clicking to run, I checked the box (bottom left) to use this device for each run. It now runs every time directly on the device.
a unpowered usb hub did fix the problem for me. it was happening on both my samsung s6 and my sony z5 premium.and both on my pc and my mac. (using android studio).
Use short usb cable. The shorter the length of cable, the more stable the adb connection. I had the same problem for long time. I changed the cable to shorter one and I haven't got that problem anymore.
After connecting my device to my real device (Galaxy S / Android 2.3.3) and lauching the DDMS Heap tab, sometimes the device disconnects and is no longer available as vaild Android target for the Android Device Chooser dialog. Un- and re-plugging the USB cable have no effect, killing the adb server process or shut down eclipse does not either. As my last resort I've to reboot the device and re-connect USB, this seems to work but this approach has a lot wrinkles, if you know what i mean.
Is there a better solution available?!
Thank you!
There is nothing you can do about it. It's a known issue with all Android Phones based on the OMAP chipset.
It's not that the chipset is bad in any way, but it is fact that the USB-OTG device driver from OMAP is buggy. The driver works well until you stress it hard enough. Lots of logcat outputs cause this, as well as ADB debugging.
Disabling and re-enabling the usb-debug fixes the problem for a while. You can even see the USB-driver failing on the kernel-log by calling 'dmesg' on the shell.
As far as I know all OMAP3 and OMAP4 based devices suffer from this driver-bug.
I am new to android development and I have been having problems with disconnecting my smartphone from my ubuntu development platform running Eclipse. When I initially plug my phone in with the usb, the system sees it and all is well. However, if I disconnect it from the system and then plug it back in, the system does not recognize it. I have been rebooting the system everytime it does this. Is there a way to "safely" unplug the phone without having to reboot? Should I close Eclipse? Do I need to "unmount" the phone or is there a way to "restart" the android.rules in the rules.d folder?
Any help would be appreciated.
I had the same issue, and simply turning Usb Debugging off, then back on solved the situation -every time-.
After a while, when I set the default connectivity to Charge only, the problem went away.
These are just workarounds based on my experience, but might help you.