Tag Info

New answers tagged

0

So there are many different threads and posts all over the internet trying to solve this issue for various Android devices. It seems that sometimes these work, but not always. I think I've finally found a step that works most of the time (it excludes hardware issues for example). Start off with your device connected. Essentially, there is an issue with the ...


0

I didn't realize it right away, but there are different ADB drivers and Fastboot drivers. I had installed the google usb drivers with the SDK extras and ADB worked great but I got the "waiting for device" trying to flash in fastboot mode. I went to device manager from the control panel and saw the "Android 1.0" device with the yellow icon showing it wasn't ...


0

I know Windows doesn't recognize the phone but I still want to try something. Download Wugfresh toolkit from here: (For download links just scroll down, there are some mirrors) http://www.wugfresh.com/nrt/ Once you install it, click "Full driver installation guide...". This will give you a thorough guide to uninstalling remaining drivers and installing ...


0

I had tried tons of proposed solution and it seem doesn't work for my Samsung Note 3. However i finally solve without installing/uninstalling anything. Problem Solved as following; 1) Reboot phone to Recovery Mode. 2) Wipe Cache Partition. 3) Restart phone and connect to PC. Bum!!! Window successfully installed your MTP driver.


0

Yes it should include the contacts. Your syntax appears incorrect though. It should be adb backup -all -f backup.ab rather than adb backup .all -f backup.ab Also the -f backup.ab is optional as that is the default.


0

Yes, it does. You can get it via: adb pull /data/data/com.android.providers.contacts/databases/contacts2.db


-1

Do this : adb shell su mount -o remount,rw /system /system if you have problems adding data into it through adb do this and remember to revert to the original. chown system /system ......do your adb stuf..... chown root /system thats it goodluck


2

Looks like there is a way: adb shell dumpsys location > dumpsys.txt This will give you a file with all location service information. In this file search for 'Last Known Locations' and you should see something like: passive: Location[network 92.915479,55.610965 acc=22 et=+1d4h10m34s255ms {Bundle[{noGPSLocation=Location[network 92.915479,55.610965 ...


0

In this situation, since you have rooted your phone and can access the device via recovery adb, create a startup init.d script to set adb to wifi listening and then connect via wifi. /system/etc/init.d/97adb #!/system/bin/sh if [ -e /sdcard/adb_wifi ]; then /system/bin/adb_to_tcp & fi; /system/bin/adb_to_tcp #!/system/bin/sh # Close STDOUT ...


0

The problem is that the quotes are being interpreted twice: once by the Windows shell when it parses the adb command, and again by the Android shell. Remember that adb shell foo opens a shell on the device and runs the foo command there. When you run adb shell rm -r "sdcard/music/SomeArtist - (good stuff)" Windows is using the quotes to see the whole path ...


0

After a lot of messing around I think I've nailed it. It was an application called "Sony Smart Connect". Like most things that contain the oxymoronic phrase "Sony Smart" is anything but smart. Instantly everything went back to working and I can now get on with coding until the next update stops me for a month... I hope this is of help to someone in the ...


0

I found! I followed the article Configuring ADB for Nexus 4 on Ubuntu 11.10 adding a find and a row for my smartphone, inserting its VID e PID. Then I restarted the adb. Now the smartphone is visible to Eclipse! Next I'll try with the tablet inserting its VID and PID ..


0

The adb sync command is for people to use while developing Android ROMs. The "product directory" mentioned is part of the Android source tree, and adb sync can only be used with a ROM you've compiled yourself. It has nothing to do with syncing contacts or any other app data.


-1

You need to run screenrecord as root, type su to switch to root (your phone needs to be rooted obviously)


1

If you have a rooted phone with a custom recovery, you can do it: Reboot to recovery Go into Sideload (might be under advanced - if your recovery doesn't have this feature, then you need to update your recovery. On your computer, run adb sideload <gapps-version.zip> Reboot.


0

If you are on Android 4.2.2 there is a way of unlocking the bootloader without wiping the device. Use towelroot to root your device. (It works on a neuxs 7 as long as you have a kernel build < Jun 3). Afterwards you can use the following app to unlock the bootloader (It doesn't wipe the device). Then you can use titanium backup to backup everything on ...


1

I use macbook and encountered exactly the same problem. Finally I successfully flash my phone (Flame). The key is to enter "Fastboot mode" by pressing down Volume Down and Power buttons together(Detail is in the section of official guide). When you're in Fastboot mode and your device is connected to computer, run fastboot devices again. This time the ...


0

What I ended up doing was starting another ssh server in the android environment using another port, from which I then can stop and start the adb daemon. Not nice, but it gets the job done.


0

Using the Android SDK Platform Tools, with adb. Connect your device via USB to your PC, and open a command prompt. adb devices Once your device is recognized, continue. adb backup -all -f C:\backup.ab This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'. To include system ...


1

well wait-for-device, as you already realized only waits until the adb daemon properly started. This is already at init time. In order to check for a complete boot you cann ad to your script something like: in pseudo: 1) wait-for-device 2) as long as getprop sys.boot_completed != 1 sleep some seconds check getprop sys.boot_completed again 3)shell input ...


0

If you're on Android 4.4, write permissions to sd card for apps have been disabled. If you're rooted, you can try SD Fix to permanently fix permissions.


0

Turns out it works to just remount the system partition as read-write: In a shell instance: su mount -o remount,rw /system /system I had read before, somewhere, that this didn't work and caused some people issues. But I tried it as a last-ditch effort. It worked for me, at the very least.


0

Find a recovery, such as CWM or TWRP, and download an image. Then use "fastboot boot recovery.img" to boot into the recovery file and reflash a stock ROM, which should solve the problem. Note that even if you don't have a sd card, you should have a partition called /sdcard on the internal memory, which you usually can push files to. Also note that adb access ...


1

May have been USB power management. This would have affected recently updated Windows 7 and Windows 8.x. This issue can come from both the Windows OS and the Android OS. For Windows, try http://superuser.com/q/749982/ For Android, try using the developer option "Stay awake", and turn off screen timeout. However, none of the options will keep USB powered up ...


1

You could try to find an ftp server app that supports rooted devices to access system folders. If you don't have to use ftp, you could use airdroid, which also has a remote file manager. Another option (if your device is rooted) would be to symlink the folder so that it's stored on /sdcard, which you can easily access



Top 50 recent answers are included