Tag Info

New answers tagged

0

Hint, Google repository. Ah here you go a better example from the past Find your Sdk folder then locate both tools and platform-tools subfolders. Check the Google repository find what version you want to downgrade to and download the .ZIP for both. Unpack the the .ZIP's you just downloaded move the Tools subfolder over to your Android Sdk folder. Then ...


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 ...


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 ...


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

Use this version of busybox, it will have microcom.


0

Have you tried formatting the device using SPFlash tool. If not , do so. If you have followed usual safety rules for flashing you should have your original ROM backups through nandroid. Re-flash them after successfully partitioning the device. The usual procedure is to flash recovery.take nandroid backup, flash your choice of rom. For now please keep device ...


0

For Development you need adb and adb driver. You can download adb driver from http://adbdriver.com/ You can download adb from http://forum.xda-developers.com/showthread.php?t=2588979


-1

try this. This should work. adb pull /sdcard/screen/


0

If the screenshots are getting saved in external SD card then I believe external SD card is set as default write-disk. In that case, you can do, adb pull /sdcard/{YOUR_DIR}/ {TARGET_DIR} I use my custom alias named adbshots which is, /usr/bin/adb pull /sdcard/Pictures/Screenshots/ /root


0

Your version of SDK tools has nothing to do with the parameters input can understand or execute. Input is a binary in Android OS which can be run independently without requiring any set of external tools such as ADB. The reason you receive the error "Error: Unknown command: touchscreen" is because you're running an Android version earlier than Android ...


0

Older versions of android don't have the tap feature of the input command. I have a 4.0 device which lacks it as well.


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 ...


0

Since you can neither boot the phone nor access recovery or bootloader, you can try the following1. Download latest SP Flash tool. 2. Download this stock ROM: S9201_4.2_MP_F3F8_B1_IN_MMX_13_FLASHER_USER.zip 3. Extract it, open flash_tool.exe and load the scatter file 4. Now connect your phone and flash by clicking 'Download'. Source: [Upd Stock ROM] [MMX ...


1

15 seconds minimal ADB, fastboot and drivers installer. No need to navigate to the installation folder in CMD. It can be installed system-wide. No need to check for manufacturer specific drivers. Everything included in 9MB.


0

I removed the clean master app data from the backup and re-created the backup.ab file again using the Android Backup Extractor(ABE). It seems that the backed up file was corrupted and couldn't able to restore it properly. So I suggest to, use the adb backup command atleast twice to make sure the backup is fully completed and compare both file are same ...


0

Ok fixed the problem by installing firmware from sammobile.com. The Odin flash failed at the hidden.img, but I could recover the thing by running the instructions here: http://www.s4miniarchive.com/2014/07/solution-what-to-do-when-odin-fails-at-hidden.img.ext4.html And I have my wifi back but lost root (but that's not a big deal).


0

Use KeyEvent to do the job. adb shell input keyevent 85 85 corresponds to KEYCODE_MEDIA_PLAY_PAUSE. More keycodes can be found here or here. Alternatively, if the activity featuring Play/Pause options is in foreground then you can do: adb shell input touchscreen tap <X> <Y> where <X> and <Y> are the coordinates of the tap that ...


0

To solve this you can do it like this: Create an empty zip file (and name it, for example "sideload"). Install adb drivers (adb setup 1.4.2 for example) or MTKdroid tools. Open CMD (or open MTK droid tools and click on "adb terminal") Type "adb sideload + the directory name of the empty zip file ("sideload.zip" for example) Like this: adb sideload ...


0

I had similar problems, adb devices didn't list any devices once I'd upgraded to Windows 10. I happened to have an Intel-powered Android phone connected over USB. I ended up removing the Intel-specific Android Driver (downloaded yesterday, version 1.9 which doesn't explicitly support Windows 10) and then used the universal Android USB driver ...


0

I have tested multi connection with another device (Samsung Galaxy Note4), then it works... :d I think that the solution may be compatibility between devices or device connection sequence.


0

this means that recovery doesn't recognize the google drive apk inside the update package. most ROMs don't come with google drive pre-installed, so i assume you're trying to use a factory image, which needs to be decompressed and flashed via fastboot. factory images cannot be installed via recovery. first, you'll need the android SDK. here is a link to get ...


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

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 ...


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.


0

Depending on the type of device you use, you can install a custom recovery and flash this file to unlock without data loss


0

Yeah, just about killed mine too. Battery life went from excellent to abysmal, which was the most maddening change. I finally settled for the nuclear option and did a factory reset. That did restore the battery life. I'm not sure if it cleared the caches as well, but I should think it did. Just be sure to back up your files, photos and address book before ...


0

My guess at your problem: the versions you have downloaded are 32-bit, and you have a 64-bit OS. The error message when trying to run a 32-bit executable on a 64-bit OS which does not have compat. libraries installed is very bad. It's "No such file or directory".


0

although it's open in your lan, it is still adb. it's the same as over usb. you have to acknowledge every device which want to connect once before it can connect. if you think, there is a acknowledged device which should not be there, you could reset that list in developer settings.


0

This is one example, you have to make the split, it's doesn't seem to be an option, root@kali:# adb devices List of devices attached 4fddcdd8054fc421 device 5cf4b0890675d95c device root@kali:# export DEVA=4fddcdd8054fc421 && export DEVB=5cf4b0890675d95c root@kali:# adb -s $DEVA shell uname -a && adb -s $DEVB shell uname -a ...


0

As suggested by @Izzy I am going for the "firewall-solution": Block all connections for the adb-port (5555), except from my trusted devices. Thanks again!


0

This can work. Though your mileage may vary. I just restored a nandroid backup from an old Galaxy S4 (which I dropped and the LCD failed) to a new Galaxy S4. The new Galaxy S4 arrived completely stock and it took a while to get it rooted and TWR installed - getting around Knox etc. But then I restored a nandroid backup from the old Galaxy S4 (which was at ...


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.


0

you can boot into Recovery, then adb should be enabled by default. but I don't know what you want to do to reset your code. if you would have rooted the phone, then you may be able to do that but I think you can't reset the code from adb. the only thing you may do is, first make an adb backup, then do a factory reset and get the data back from your backup.


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 ...


0

It doesn't seem to be the case. I tried with both the following commands adb backup -all -apk -shared -nosystem -f adb_backup.ab adb backup -all -apk -shared -system -f adb_backup.ab and neither my photos, SMS nor contacts were backed-up.


0

Ok here's what you need to do: 1) First follow this guide to erase evrything on your tab http://forum.xda-developers.com/showthread.php?t=2610757 for this you would need latest odin, find it online or use the version given in thread. You also need a pit file and stock rom for your device. a) Pit file: Use the SM-T700 pit file from here ...


0

Assuming you have the wifi-variant of the tablet. Download the stock firmware from here. This file can be flashed via Odin when you're in Download-Mode. From there on you can restart your process of flashing TWRP and then the new ROM.


0

Just figured it out, pretty easy actually. If the bootloader is unlocked and the device is powered off and plugged into your computer, you can just use ADB. Typing >adb devices will result in You can then run adb shell "ps" and it'll output the process list while in charge mode, like seen below:


0

Samsung always make things difficult. When I had my Note 4(Now Nexus 6) and was trying to do things via ADB. I did pretty much everything you did. It wasn't until I uninstalled the universal drivers and installed the Samsung ones that can be found here. I assume you downloaded the universal ones from Google as well. Those have never worked for any Samsung ...


0

Try installing "Kies", for some old phones i remember that was the solution, maybe still is. Also try another computer, maybe a Mac and see what it does there. The USB ports have more power. Or try a high power external USB hub, anker or similar. What cable are you using? Crappy ones are often not working. Try a new short(!) USB3.0 cable. Does your PC ...


-1

On my Nexus, the USB mode has to be in Camera in order for ADB to work. I am not sure why. In that mode, I cannot copy files, but the ADB connection works just fine.


0

adbd in normal operation defaulted in it's source code to /system/bin/sh and, in recovery to /sbin/sh trying to get bash scrollback may succeed by first passing export SHELL=/system/bin/bash or xbin/bash as the case may be. It could be on completion of the command executed in bash without exporting the $SHELL variable adbd kicks back to sh and crashes. I'm ...


0

Easy to do – as in any Linux system: Connect your device as usual log into it using adb shell use the ls command to list files in the current directory, and the cd command to change directories (i.e. walk the tree / navigate through directories) For details on the commands, check for the corresponding Linux man pages – e.g. man ls and man cd. Edit: If ...


0

May be your phone is bricked. Try downloading the StockRom or some CustomRom that is compatible to your phone and flash it. This might help you. If you are wandering about all these terms Bricked, StockRom, CustomRom and flash. Here is a good article that might help you to understand.


0

in recovery and like this root@kali:~/Downloads# adb shell ~ # parted /dev/block/mmcblk0 GNU Parted 1.8.8.1.179-aef3 Using /dev/block/mmcblk0 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print all print all Model: MMC 016GE2 (sd/mmc) Disk /dev/block/mmcblk0: 15.8GB Sector ...


0

This may still be true, many routers by brand have a default admin user name and password as well as ip address netgear defaults for my router anyway was admin admin 192.168.254.254 as an example if you have a device with wireless access to the router use an app from fdroid called Network Discovery to determine the router address, then punch that addy ...


0

When in recovery mount your /system using adb shell mount /system though twrp can be twitchy otherwise use in-twrp mount function to mount system and you should have full room to do what you need. In recovery you have a functioning kernel, so after mounting your system you should have every thing at your disposal adb shell mount /system adb shell ~ # mount ...


0

Try adb reboot fastboot or adb reboot download this is the command for Samsung devices.



Top 50 recent answers are included