Tag Info

Hot answers tagged

4

I got it to work :) NOTE: This also requires your device to be rooted. (Thankfully, mine was rooted) Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken). Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery ...


2

To my knowledge if you do not have USB debugging ADB is not running and any tools that rely on ADB will fail to work.


2

Try the 15-seconds ADB/drivers all-in-one installer. You could also install the Samsung drivers rather than conventional OnePlus drivers. I installed these drivers and I've had mine working since the upgrade. You could also try following this guide on how to set it up.


2

Could try downloading a custom recovery, such as Clockworkmod for the device and flash it via odin. I think Clockwork mod has adb shell built into it. Then you can run the commands that way. And as far as I know, odin doesn't require USB debugging. It doesn't need it when the phone is in download mode.


1

If you have ADB debugging turned on, you can give Vysor a try: http://www.vysor.io/ PS: If you can't get to it because the phone is locked, attach a computer keyboard to the phone and unlock it.


1

For the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Your private key is saved in computer. In Linux the directory location is $HOME/.android/. On Windows that usually translates to ...


1

In your command line example, you are running the ADB command from the Android terminal with / as current directory. So Android tries to write the output to /logcat.txt, which fails. Keep in mind that after you execute adb shell everything you type happens on the phone. The command adb logcat then runs on your phone, and the creation of the text file also ...


1

adb logcat on your phone launches an ADB server on your phone (which is also running on your PC) and connects to itself. Then you try to write everything to /logcat.txt (/ is the the root of your filesystem; you can't write there). Try routing your output to something like /sdcard/logcat.txt or run it directly on your PC, where it gets saved in the ...


1

since i'm not able to comment, i'll make an answer. i've been in this exact spot with this device before. you won't be able to flash the recovery w/o triggering knox and voiding the warranty. if that's not a concern, you should be in the clear. keep in mind, you could lose the data at any point in the process. samsung has notoriously unreliable USB ...


1

One thing I noticed not mentioned in what you have tried that will make your device invisible. Have you enabled USB debugging on your Nexus 5. USB debugging helps operating systems communicate with each other and without it things get lost in translation. To enable USB debugging Go into Android settings menu and scroll down to the about phone menu next go ...


1

No, it would not backup Contacts. Yes, it would backup Contacts. Confused, eh! Yes, it would backup Contacts. See this question: Backup/Restore SMS/MMS via ADB on a non-rooted device? The author of it was able to backup contacts. It was later revealed that the device on which the backup was performed ran Android 4.1.2. It was a bizarre revelation for ...


1

The fix for me was using a different micro-usb cable. No software change, no drivers to update, just the usb cable. Apparently they aren't all created equal.


1

Non-Rooted Solution: Enable USB-debugging in the developer setting and connect your phone to your computer via USB. Run the adb command, adb tcpip 5555 (Make sure port 5555 is not blocked by any firewall programs) Get your Wi-Fi IP address assigned to your device and run the adb command adb connect <IP_ADDRESS>.For example, adb connect 192.168.1.133 ...



Only top voted, non community-wiki answers of a minimum length are eligible