Database Info

Problems with ADB

Trying to do some push/pull and do the new lag fix to no avail. After adb devices, the phone shows up as attached, but after adb remount I get "remount failed: No such file or directory" I'm not able to execute a push or pull command, and therefore I'm not able to run the lag fix.
I have USB Debugging selected, and I was able to delete the bloatware via adb shell, but none of the other commands go through for me...

Which version of Windows are you running?

Windows 7 64 bit

Still haven't found a fix to this, so I'll post up what I'm inputting and what I'm getting in return.
Here is the code I use to get into ADB and then attempt a remount:
Code:
cd C:\android-sdk-windows
cd tools
adb remount
remount failed: No such file or directory
When I try to push and/or pull, I get this:
Code:
adb push ./smoothcalendar.apk /system/app
failed to copy './smoothcalendar.apk' to '/system/app/smoothcalendar.apk': Permission denied
I've tried adb kill-server, then adb remount with the same issues.

currently experiencing the same problem...

Do you have BusyBox Installer installed on your phone? I believe you have to have it installed in order to use Android SDK.

I've got Busybox 1.17.1 on mine.

I'm wondering, is this a problem at the computer level or at the phone level? I know the Vibrant had some issues with push/pull, but I see some stuff here in the dev thread (lagfixes, sideloader stuff) that if I run from my computer attempt push/pull commands that fail and therefore the thing I'm running (lagfix most recently) doesn't actually work and I'm stuck with a slower phone.
If its a phone issues, I can just exchange it under warranty, since I'm out of my 30 days. But I'm hoping it's not as I'd like to keep this one that other than this has worked great for me.

When I first starting using ADB, I was connecting my phone like when I was using Windows Explorer to muck around on it. I had mounted the usb connection in the notification window. I kept getting errors when I tried to push/pull. I reconnected once and forgot to mount the usb connection and everything worked perfectly. Make sure the usb debugging is check marked in Applications in settings. Try to do the push/pull without using remount command and don't click on the USB connected notification option when you plug it in. I'm really new at this linux stuff so I could be wrong. I'm just trying to share my experience in hopes that maybe you're doing the same things I was doing before I stumbled onto the right way to do it.

Hmm, odd, I've tried that very method many times before, to no avail.
I try it just now, and having no problems with push or pull. Works for me! Thanks!

[Q] Is it possible to run adb logcat while at bootscreen?

I'm trying my hand at porting a ROM and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Does adb not work at this point in the boot process or am I doing something else wrong? If I can't use adb to check logs, what can I use to debug?

I'm pretty sure you can only communicate with Adb while the phone is fully booted or while in recovery

If that's the case, how would I go about figuring out why the phone's stuck at the bootscreen? Can I add a line in an init.d script or elsewhere to write a log to the sdcard during boot?
edit: Found this on StackExchange: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.

[Q] NVflash

Hi! I'm running CM 10.2 Android 4.3+.. My firmware is over 10.6.. i installed flatline NVflash for tf300t and after installing Android Root bootloader I chose from the flatline recovery the generate bloobs( I followed the tutorial)The blobs generating was Done and the recovery sad something like bloobs ware uploaded to server. On that menu I tried to run the adb pull comment...that don't work..adb says no device.I booted in Android and I tried again the adb pull.This time adb sad remote object doesn't exist.I checked with Rooted Explorer if the Android Root folder exist in /dara/media/AndrooidRoot. IT DOES! After that I tried to copy that folder on my SD card. On PC shows it a 1 KB file. How I can extract that folder with adb? Adb says something like remote object doesn't exist! Please Help..Sorry for my bad English!

TheKid1997x said:
Hi! I'm running CM 10.2 Android 4.3+.. My firmware is over 10.6.. i installed flatline NVflash for tf300t and after installing Android Root bootloader I chose from the flatline recovery the generate bloobs( I followed the tutorial)The blobs generating was Done and the recovery sad something like bloobs ware uploaded to server. On that menu I tried to run the adb pull comment...that don't work..adb says no device.I booted in Android and I tried again the adb pull.This time adb sad remote object doesn't exist.I checked with Rooted Explorer if the Android Root folder exist in /dara/media/AndrooidRoot. IT DOES! After that I tried to copy that folder on my SD card. On PC shows it a 1 KB file. How I can extract that folder with adb? Adb says something like remote object doesn't exist! Please Help..Sorry for my bad English!
Click to expand...
Click to collapse
More details needed to figure out what your problem is. What OS are you using on your PC? Right now, it sounds like your ADB drivers aren't working correctly. Can you post a screenshot of your cmd commands? At the upload server screen, you should try the command "adb devices" on your pc. If that does not return a serial number, your PC is not communicating with your tab. Likely cause: bad ADB drivers. You can certainly copy the folder to your SD card, but make sure you have permission to do so with your explorer.

graphdarnell said:
More details needed to figure out what your problem is. What OS are you using on your PC? Right now, it sounds like your ADB drivers aren't working correctly. Can you post a screenshot of your cmd commands? At the upload server screen, you should try the command "adb devices" on your pc. If that does not return a serial number, your PC is not communicating with your tab. Likely cause: bad ADB drivers. You can certainly copy the folder to your SD card, but make sure you have permission to do so with your explorer.
Click to expand...
Click to collapse
I'm running windows 8. When the tablet is in Android the pc reconize adb device. I tried this command adb pull/data/media/AndroidRoot ( the comand that is on the tutorial. Can you mace a screenshot of that read and write permisions? I don't understand that r/w....I will try this on Ubuntu 13.xx ( 04 or 10) It's ok in linux to try this...In linux the adb commands are different?

TheKid1997x said:
I'm running windows 8. When the tablet is in Android the pc reconize adb device. I tried this command adb pull/data/media/AndroidRoot ( the comand that is on the tutorial. Can you mace a screenshot of that read and write permisions? I don't understand that r/w....I will try this on Ubuntu 13.xx ( 04 or 10) It's ok in linux to try this...In linux the adb commands are different?
Click to expand...
Click to collapse
They're the same in Linux, but you've gotta to have those ADB drivers in there too. Are you using the 64-bit version? When you say the pc recognized the device, does it return a serial number when you query "adb devices"? If it does, you don't need Ubuntu. If the problem persists, then issue of compatibility with Win 8.

Hi,
I am using this thread since my question is about NVflash
I am new to custom roms/fw on TF300T. I have latest Android 4.2.1 and bootloader (10.6.1.27.5) and it's still locked.
Do I have to do anything else than unlock my bootloader with app provided by ASUS before starting this NVflash procedure? Is root access required?
Do I need specific drivers for Win7 32-bit? I am familiar with ADB/Fastboot..
Thanks for advance!

Moto G 2013 (xt1033) with no OS, can't adb push/sideload rom.

I have a Moto G xt1033 with no operating system.
I can recognize the device using fastboot devices and adb devices. (drivers are installed properly)
CWM recovery is installed properly.
There's no operating system and the sdcard is empty.
When I try to use the command adb push to get the rom.zip into the sd card (or data/media folder) it just won't work, it will give me a 'protocol failure' after a couple of seconds.
When I try to use the command adb sideload it will immediately crash (at 2%) and give me the error: failed to write data 'protocol fault <no status>'.
I've also tried to install a stock rom using flashing through fastboot, but it also failed.
Anyone has any idea of how I can save this phone?

It sounds like something is not right with your ADB / Fastboot setup. What operating system is on the PC / Laptop?
You might want to try reinstalling ADB:
http://forum.xda-developers.com/showthread.php?t=2317790​
Alternatively, a quick way to get access to Recovery Mode ADB is to use Linux, either as a LiveCD or full install. The command to install ADB / Fastboot on Ubuntu is:
sudo apt-get install android-tools-adb android-tools-fastboot​

Thanks for the tips, my computer's OS is Windows 7, but the problem was related to my computer's front USB ports, all 6 of them. As soon as I connected to one of my back USB port it worked.. Most likely because my front ports are 2.0 and the back ones 3.0. Never thought it would make a difference in this case, kinda feel stupid for having wasted so much time looking for a solution when it was so simple.
Thanks for the reply anyway @lost101.

XT1032
Am experiencing the same problem,
unable to sideload/push stock rom gets stuck on push at 31%
Recovery CMW, able to boot into recovery
getvar=all, i don't even have imei shown in that!
pls help me fix it...
Thanks a load in advance

As soon as I select 'ADB sideload' on TWRP, the phone is no longer recognized by the desktop computer nor ADB.exe...
But when I select cancel, the device is then recognized. This is version 3.3.1-0
Edit: It seems to only logical solution is to use 'adb push [image_name] /sdcard/.'

ADB not recognized

So I finally undated my PC from Ubuntu 12.04 to 16.04. The good new is I have full MTP access to my G3 now. However, ADB is no longer recognized. ADB and Fastboot are located on a separate drive from the OS, so I am trying to run the same file from the same HD. Any suggestions?

You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app

How are you trying to use ADB? It doesn't work when your phone is on fastboot mode

Tel864 said:
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
I did try that without success even though I successfully ran ADB without root with 12.04. Only Fastboot needed root.
For some reason the file is not recognized as an executable file. Below is a screen copy:
Code:
$ ls
adb fastboot twrp-osprey-3.0.0-r2.img
commands.txt twrp-osprey-2.8.7-r5.img twrp-osprey-3.0.2-r1.img
$ adb
The program 'adb' can be found in the following packages:
* adb
* android-tools-adb
Try: sudo apt install <selected package>
$

Henriquefeira said:
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Click to expand...
Click to collapse
I have not even got that far. See post above, "adb" is not recognized. I would rather not install the adb development package if I can avoid it.

Its fastboot flash recovery not adb flash

Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
The commands is not my issue. I have a list of commands I have run successfully many times. My issue is with the new OS (in the same PC) not recognizing adb. When I boot to the old OS, no issue, back to the new OS, command is not recognized..
My list of commands is as follows:
Code:
adb devices
adb reboot bootloader
sudo fastboot devices
sudo fastboot boot twrp-osprey-3.0.2-r1.img

Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
Re-reading your reply, I think you mis-read my code box. Next to the dollar sign my command "ls". Below is the OS response. Next $, command is "adb", and below the OS response.

I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.

MrTooPhone said:
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
Click to expand...
Click to collapse
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk

acejavelin said:
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Pretty sure I had multiple 'adb' executables in 12.04.

i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates

steffano said:
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
Click to expand...
Click to collapse
adb doesn't work in bootloader mode, that is when you use fastboot... I think you should review the process involved in installing recovery.
Sent from my MotoG3 using Tapatalk