My power button died on my phone. Or got less and less responsive. Last time I was lucky that trying a long time I managed to start up my phone. Since then I kept my phone on perpetually or restarting it if that was required. However, now my phone just suddenly turned off out of nowhere. I tried to turn it on again but had no luck. I had previously turned on USB debugging since I thought that was enough to turn it on from the pc if it ever got turned off. Now it seems that was not enough as it shows up as unauthorized in adb (I never tried actually connecting, very stupid on my part). Is there any hope for turning my device on through adb.
Phone: Nokia 7.1
There are some questions on problems with unauthorized devices (ADB Android Device Unauthorized) but those seem to assume I can still turn on my phone to change settings. Is it impossible otherwise?
tldr; Here is a detailed list of instructions if you want to try your luck with fastboot. Your touchscreen and volume buttons must be functional for this to work.
Make sure the phone is turned off.
Press and hold the Volume Down button. Don't release it.
Plug in a USB charging cable
When the screen turns on and shows a message saying "Download" or "Fastboot" mode, release the Volume Down button.
Charge your phone like this for 2 minutes, to make sure it has enough charge.
Move your phone's USB cable and connect it to a PC.
Download the binary for fastboot.
Run fastboot continue.
Related
and happy holidays. Apologies if this question is more appropriate for SuperUser, I ask here in case there is a programmatic solution to my problem.
In summary: On an Android device with a broken screen, assuming that USB Debugging is enabled or that the connected device is not trusted, is there any way to perform remote control?
So I have a Pixel 3a which I used to control just fine via scrcpy 1.21. Today the screen broke to the point that I only see a few glitchy lines, even though it looks like I can theoretically control it (based on the sounds, I managed to enter the log-in pattern).
The problem is that adb devices does not recognize it, even though the system (Ubuntu or Windows) recognizes that a Pixel 3a was connected for charging.
Is there any way I can salvage this situation?
ADB commands failed. scrcpy failed.
Very strange issue, no results that I could find from google searches.
I am running Windows 7 64 bit. Everything Windows related is up to date, and so are all USB drivers. My computer is a laptop from Puget Systems.
My computer has three USB inputs; one USB 2.0, and two USB 3.0s. 2.0 versus 3.0 doesn't really matter though, because this issue happens with all three drives.
Heres the issue: When connected, USB devices are found, and recognized. 5-30 sec later, they disconnect, only to reconnect in a couple seconds. The cycle of disconnecting/reconnecting continues indefinitely. I have not been successful with keeping USB devices connected for more than ~30 seconds.
At this point, it could be any number of things causing this issue. But this is where it gets weird. This issue ONLY happens with mobile devices, and it happens with ALL mobile devices. By mobile devices I mean phones and iPods. I have tested my Samsung Galaxy S4, an iPod Classic, an iPod touch, an iPod nano, a Droid Turbo, and an iPhone 5. This issue occurred with all of these devices. The issue did NOT occur at all with my 2TB Seagate backup harddrive, my 1TB WD harddrive, several USB pen drives, my external keyboard, or my wireless mouse USB receiver that is plugged in nearly 24/7 in my USB 2.0 drive. My Xbox One controller disconnected 3 times in a row once, but that only happened once so it might have been a fluke...?
Anyways, what could be the reason for this strangely specific issue? Does anyone have any answers or has anyone experienced something similar?
Improper drive installation? Make sure your drivers are installed correctly. Try uninstalling and reinstalling them. If this does not work try to see if it is your USB cable or mobile device's port. (Test by altering to charge the device from a wall adapter) It could also be your computers port but you said in the title that it is only happening for mobile devices.
Reinstall the drivers to the devices you are having problems with. (Oh someone beat me too it.)
I am having a problem with adb not finding my evo 4g lte. I have USB debugging selected. The phone is updated to 3.17, so some of the options, like charge only/disk drive have changed (now i think my only options are HTC Sync and disk drive). I am using the most updated version of the Android SDK. I'm running a fully updated windows 7 box. I have tried all of my USB ports, adb kill-server/adb start-server. I even created an .ini file with the hex version of the device USB/VID id (based on the HTC Sync setting, the phone shows only as Android Phone in my windows device manager. I have not yet tried switching it to disk drive), and nothing has worked. The phone's bootloader is unlocked via htcdev, but is otherwise stock. And, oddly enough, my old evo 4g which is rooted and running CM9 can be found, so I think it's got to be something with the new phone, I am just not sure what. I've been researching this over the last few days and have tried everything I have found, all to no avail. Any advice would be greatly appreciated!
Internal port is faulty. Two terminals for charging ,two for data, the data one(s) may have fractured from.the board.
When I connect my Arduino Mega ADK board to an AOA Android app everything is fine (initially), the connection to the ADK board is fully functional in both directions. However, if the screen rotates, someone hits back, the screen locks, etc, when the app restarts the openAccessory call to the USB manager always returns null. So students have to unplug the USB before the connection can be made again.
I've figured out the problem is related to the Input Stream, because if I don't start the Thread to receive commands then there is no issue. However that's not really a useful fix. :)
My code is here:
https://github.com/ME435/AndroidLibraries_v01/blob/master/src/edu/rosehulman/me435/AccessoryActivity.java
I just subclass my AccessoryActivity in apps like this...
https://github.com/ME435/LED-Toggle/blob/master/src/edu/rosehulman/ledtoggle/LedToggleActivity.java
It's not robust, but it's very simple for students. Thoughts on my issue?
I have a problem about the gamecenter,I am developing a multiply-player game, I have finished the connecting part, good luck, I can connect the another device to play the game over the local wifi, but I tried to do it through the 3G network and external wifi, it didn't work, it appeared that the interface stopped at the view of connecting the counterpart, that means they found each other, but they didn't found the match(maybe).Sometimes, one found the match,another one still stop at the view of connecting, it didn't enter the game, I read the log information, that told me the expected number of players was one, that mean there was only one player entered the game,another one did not, the max number was two.I found many website, but no answer, maybe is that because of the sandbox? I have tried in ios5 vs ios5,ios5 vs ios6 ,ios6 vs ios6,