I recently received my XT1540. I was going to wait the 14 day window I have to return the device prior to unlocking bootloader. In the mean time, are there any ADB commands I can run to gain familiarity of ADB and to ensure I have the proper Motorola drivers?
'adb devices' will let you know if the device is recognized (drivers installed, etc).
Plug in to PC, turn on USB debugging on phone, run the above command. The phone should prompt for you to accept your computer's RSA key, adb should list your device as 'device'.
There is also this: http://developer.android.com/tools/help/adb.html
use the following command to print all adb commands
adb --help
So I get the following:
Code:
C:\Desktop\adb-fastboot-latest_win_linux>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
ZY333TKQ99 unauthorized
I assume this means my drivers are installed correctly and that "unauthorized" is because bootloader is not unlocked. Is this correct?
MrTooPhone said:
So I get the following:
Code:
C:\Desktop\adb-fastboot-latest_win_linux>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
ZY333TKQ99 unauthorized
I assume this means my drivers are installed correctly and that "unauthorized" is because bootloader is not unlocked. Is this correct?
Click to expand...
Click to collapse
Probably unauthorized because you need to accept RSA key request on your phone. You should see a dialog on your phone like this.
quakeaz said:
Probably unauthorized because you need to accept RSA key request on your phone. You should see a dialog on your phone like this.
Click to expand...
Click to collapse
That was it. I did not even look at the phone.
Related
Hi,
I rooted my TF101 using Razorclaw, then i installed Recovery Installer, i can enter CWM and make nandbackup, everything is ok.
BUT
When i want to use ADB in APX mode, the TF doesn't appear in the devices list.
Asus Sync is installed, the USB Debugging option is checked (i unchecked and checked it again) and when the TF is booted in normal mode, i can see it in ADB :
D:\android\Eeepad\scripts>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
37c708940c041d7 device
Click to expand...
Click to collapse
I can see it in the device manager :
Asus Android Composite ADB Interface
Click to expand...
Click to collapse
When i switch to APX mode, in the device manager i have :
NVIDIA USB Boot-recovery driver for Mobile devices
Click to expand...
Click to collapse
(it seems the drivers are ok ?)
D:\android\Eeepad\scripts>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
=> no device listed
I made "adb kill-server", "adb start-server", no more device listed
As soon as i reboot the TF, it appears again in the device list and i can go to the shell :
D:\android\Eeepad\scripts>adb devices
List of devices attached
37c708940c041d7 device
D:\android\Eeepad\scripts>adb shell
$ su
su
#
Click to expand...
Click to collapse
Is there an issue with B70 sbkv2 or CWM ?
Do you still access ADB in APX mode with the same config ?
Thanks
there is no ADB in APX (bootloader) mode
Hi,
Sorry for that, i was thinking i should at least see the device.
But I understand now, bootloader mode does what it's made for and nothing more
Thanks
I'm trying to root my phone using the method here: http://forum.xda-developers.com/showthread.php?t=1709424
without much luck... On page 33 one person mentioned getting to Daemon successfully started and having it just hang there, which is my problem, then said it was just dumb user error with never explaining what it was. Several people followed up with the same problem but no answer. Initially I started it up and it would just start up the daemon and sit, so I rebooted my phone to try again and now it doesn't even do that, it just spits out Exploit by beaups, script by designgears and sits there with a blinking cursor.
Phone is in charge only mode, USB Debugging enabled, HTC sync not running, have tried multiple USB cables and ports. I have a mac and am trying this through VirtualBox (and yes, the USB device for the phone is attached - not mounted as a disk). I can only guess this is what's causing the problem but I don't really see why it shouldn't work. Anything I can try?
Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.
redpoint73 said:
Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.
Click to expand...
Click to collapse
Date doesn't really come into play since the installer doesn't go anywhere. What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted, I do get farther but don't seem to really get anywhere still. It does more stuff but seems like it keeps killing the server and a check for software updates finds nothing to update.
Exploit by beaups, script by designgears
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Done! Rebooting...
error: more than one device and emulator
Press any key to continue . . .
Click to expand...
Click to collapse
Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.
chadcf said:
What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted.
Click to expand...
Click to collapse
The drivers get installed with HTC Sync. So re-installing Sync would have fixed the drivers, if that was causing the issue. Sorry I can't help you anymore than the suggestions I've already made. Hopefully, somebody else can help.
chadcf said:
Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.
Click to expand...
Click to collapse
That's a typical VM issue. You can run right from linux or mac with the manual method. Just get the right version of ADB for your O/S and add a ./ before each command that starts with "adb".
I don't image the adb command is able to access that sector of the device but for the record, when I connect, I can see the device but
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb kill-server
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully *
List of devices attached
51cfe754 offline
I can connect to the device with Odin in download mode, but I do not see a 'pull' or extract feature on Odin, only push.
What is the trick to extracting the boot files from the device? All drivers and sdks are installed and using the current adb.
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.
ADB appears to be working just fine for me.
When using adb make sure you have debugging enabled and grant the popup on screen
adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.
Also need to make sure that the proper USB drivers on the computer are installed/updated.
Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do
a second adb server was running.
TNX
Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Hello,
I have a display malfunction with my Pixel 3a: the display is black
I can boot the device and connect with PC.
However, when I try to use adb commands a confirmation is pending:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
9BMAY1KGP2 unauthorized
Is there any option to fetch all data from the device (adb pull)?
THX
c.monty said:
Hello,
I have a display malfunction with my Pixel 3a: the display is black
I can boot the device and connect with PC.
However, when I try to use adb commands a confirmation is pending:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
9BMAY1KGP2 unauthorized
Is there any option to fetch all data from the device (adb pull)?
THX
Click to expand...
Click to collapse
Not if you haven't enabled usb debugging in developer settings.
Actually I did enable "USB debugging" in developer settings.
However, I do remember that I always had to confirm the request on the device.
With the broken display I cannot confirm.
Question:
Is there anything like SSH with Android devices?
I mean if I setup SSH on a PC I always can connect remotely although there's no display connected to the PC.