New answers tagged

0

You're looking in wrong direction. insufficient-memory error shows up when you're running low in space under data partition (named: userdata; mounted at /data). It stores user installed apps (APKs), updated system apps (APKs), their data files inter alia. System apps by-default are stored in system partition (named: system; mounted at /system). That ...


2

I figured this out on my own. I solved this by installing Airdroid using an OTG USB adapter and a wired mouse. I then used the airmirror capability of the software to control a virtual mouse on the device. I do have root on the device, this may be significant to the operation of Airmirror. I could then accept the debug confirmation on the screen and complete ...


0

Just do this one thing, flash/install CWM recovery using Odin or other flashing method suitable for your device. From there, it will cakewalk to install any custom rom on your device.


0

Use this simple one command to get going without stuck! # setprop persist.sys.usb.config mtp,adb Awaiting your response!


0

Which phone is it? You have to download stock firmware for it and flash it via flashtool, adb or fastboot (depends on phone). If you have Samsung phone, then download firmware and Odin from sammobile.com and flash.


0

OK, this is how I fixed mine. I tried Hunter Perrin's solution: adb backup -apk\ -shared\ -all\ -system But it just returned immediately with no error, no backup screen on the phone. Through trial and error this worked for me: adb backup -all\


0

Figured it out - seems like you just can't change permissions for files on sdcard. Moved it to data/local and chmod worked like a charm.


1

Installing Universal naked drivers shall solve your problem. Assuming you are skillful enough installing drivers manually as you intend to make use of ADB, here's a reference link to Universal Naked Drivers: http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339 It generally supports all Nexus devices(probably ...


0

I would highly advise to install Universal naked drivers on your Windows system as in windows only we encounter such driver issues. Refer this link for Universal naked drivers: http://www.xda-developers.com/universal-naked-driver-solves-your-adb-driver-problems-on-windows/ Being a Nexus 5 user, I have encountered this problem and after great efforts, UND ...


0

Get "adbd insecure" from google play store, it helps give write access to custom roms that have it secured my the manufacturers.


-1

That's too easy :) Find the location : android-sdk-windows\platform-tools open cmd and then do these: cd c:\android\sdk\android-sdk-windows\platform-tools adb.exe kill-server adb.exe start-server These steps may solve your problem. Good Luck.


1

So I downloaded the OS zip given on the Acer website and trawled the /system/app and /system/priv-app files looking for image files that matched the lockscreen. They turned up in /system/priv-app/AcerLiquid.apk. From there I did adb install ./AcerLiquid.apk (initially I tried with adb shell pm install ... but that failed with a permission error). On ...


2

Now that you have USB debugging enabled, you can try resetting some of the database flags associated with the lockscreen... You will have to adb push sqlite3 to your device, the only independent binary that worked for my devices I pulled from here: XDA - sqlite3 binary June 2015 adb shell cd /data/data/com.android.providers.setting­s/databases sqlite3 ...


3

As Firelord asked me to sum things up, here we go: First, you cannot do a backup using fastboot. Fastboot is like a one-way road: you can only use it to write partitions (either by flashing a corresponding image, or by wiping it) – but you cannot "pull" a partition. Which leaves ADB. Yes, it's possible via ADB – but it will require root. As Firelord ...


-1

Try using the -a option to copy all file attributes: adb pull -p -a /sdcard


0

Since the phone can still boot into Odin mode the best thing to do here is to flash a stock firmware and start all over again. You could have flashed a wrong recovery hence the boot failure; it happens. Just get and flash a full stock firmware in Odin. Make sure the firmware is for your device model and network/region. Samsung phones have a tendency to ...


-1

As far as I know , you have to connect it via usb first before attempting the tcpip command.


0

For your Android 4.4.2 device the command to add a contact is (replace the Bo Lawson and #123.. to whatever you want): adb shell am start -a android.intent.action.INSERT -t vnd.android.cursor.dir/contact -e name 'Bo Lawson' -e phone 123456789 Now to get it to save. This is Android 4.4.2 specific. Pressing back will save it. For this you need to use key ...


0

I think there is not direct way to do that. I would recomend for you to make a simple app to insert a contact or contact list and then use it with adb. You can find an example here http://www.codeproject.com/Articles/578823/Android-Contact-Operations-Insert-Search-Delete


0

Below is the google translation: hope it works for you. [Abstract] to install the driver, is the beginning of our wire brush, brush machine process is a very important step, but also a lot of local friends easily qualify problem areas. Just use a USB cable can not be achieved mobile phone and computer information exchange, but also need to drive. ...


0

It is a mount-option that the fs is remounted readonly if an error occurs. But for you problem with the folder: Could it be that the foldername contains special characters (that includes spaces or backspaces)? Check it with ls -b * or ls -q * if your ls supports it.


0

If you have a busybox you can try busybox mount /system -o rw,remount or use system mount command: mount -w -o remount -t ext4 /dev/block/bootdevice/by-name/system /system


0

Current Situation I am afraid you have messed up things in a big way by flashing a ROM not meant for the device ,see this to get more understanding Can I install a ROM made for a different device? Also surprised that you were actually able to successfully install CM meant for another device I am not conversant with "dd" commands, but the probable reason it ...


-1

I was having similar issue with my S6 Edge(+). Found to be junkie usb cable. Switched to a quality cable and device showed up.


2

For rooted Android devices You can consider installing BusyBox app by Stephen. Per Play Store, the minimum Android version supported by app is Android 1.6 and it is a well-updated app. In essence, it installs the busybox binary into /system/xbin and places symlinks in the same directory for all the utilities it has. What is BusyBox (not the app)? ...


0

I found that on my Moto MB865 (Atrix 2) sending menu key event turns the screen back on: adb shell input keyevent 82


0

Source: Factory Resettin an Android Device from a Computer Step 7 Turn on your Android phone and connect it to a USB port on your computer. Type “adb shell” and press “Enter.” When ADB connects to your device, type “--wipe_data” and press “Enter.” Your phone restarts in recovery mode and restores Android to factory settings. But judging from your ...


2

The arguments which may be supplied in the recovery.command file: * --send_intent=anystring - write the text out to recovery.intent * --update_package=path - verify install an OTA package file * --wipe_data - erase user data (and cache), then reboot * --wipe_cache - wipe cache (but not user data), then reboot * ...


1

You can try this while the phones is on. (You MUST have USB debugging enabled and authorized) adb shell recovery --wipe_data


0

Uninstall old adb. Get this, https://packages.debian.org/sid/android-tools-adb Install android-tools-adb and its dependencies manually from the above link, (sudo dpkg -i xxxxxxx.deb) This will install adb with version 1.0.32 . Hope this helps.


0

I had a similar issue (with a Nexus S, but I don't think it matters here). I could manually install the Google driver and it started without reporting problems. Nevertheless, adb devices did not list any device. Two things looked suspicious (and are probably related), but I could not use them to get a clue to the solution: The hardware ID reported in ...


0

Normally you need to copy de data folder from app. Every app cotains cache to restore you own data. If you run your app > generates a shared prefs > minimize/close app > and remove that shared prefs. When you open/resume the app, the system restore that sessiom data from the cache. Somethimes, this depends of the size and content from sharedprefs. If you ...


0

Have you tried changing between MTP and PTP. Tap the USB debugging sybol and it gives you the option.


0

from the adb shell cat /etc/fstab or cat /fstab.qcom ~ # cat fstab.qcom # Android fstab file. # The filesystem that contains the filesystem checker binary (typically /system) cannot # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK #<src> <mnt_point> <type> ...


0

Step 1. Open command prompt (CMD) and change directory to your "c:\apps" Example: Code: cd.. cd.. cd apps Now you should see your path set as "C:\apps" in CMD. Step 2. Create directory print. In CMD "C:\apps" run: Code: dir /s /b > print.txt This will print all directory files and extensions but nothing else, like size and attributes into your ...


0

That's not possible – as in Bootloader mode, there's no real OS loaded yet (see XDA Wiki and AddictiveTips). Quoting from AddictiveTips: In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, ...


0

I've resolved it. Used a different USB cable and got everything fixed!



Top 50 recent answers are included