So I've been playing around with the Beta VI build of Gingeritis and was going to change out the bootanimation to go back to the stock one, and adb isn't functioning for me all of the sudden. USB Debugging is flipped on on the device so I'm not sure what's up.... anyone else having this problem?
Flashing a rom won't bork your adb. Use cmd prompt to get into your adb directory & type "adb start-server" (without quotes), connect phone to computer, then type "adb devices". What does it say
Sent from my ADR6400L using XDA App
That's what I thought, however it seems there's something not quite right here:
G:\temp>adb kill-server
G:\temp>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
G:\temp>adb devices
List of devices attached
G:\temp>
Go to settings > wireless & networking, enable internet passthrough mode
Sent from my ADR6400L using XDA App
Yup that's what I was missing - installed the driver and adb picked back up again. Weird that the drivers between the kernels changed, wonder if it's just because that gingersense kernel is based off another device and not the T-Bolt.....
Related
Hi there,
I have a problem and seems all the threads i found are not helpful....
I have a asus transformer (B50), stock Android 3.2, I've unrootet it from
prime 1.7 using ADB for copy blob file, while tablet was turned on in normal mode.
Here is what makes me sick: I see my device in ADB as long as it's not in APX mode. When i boot my device in APX mode (I use System-Profiler to check if it's really there) then the list of devices is empty.
alex$ sudo ./adb kill-server
alex$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
alex$
The same at my Vista PC... device is in APX but not visible for adb...
I used CWM to unroot and install prime, but I don't want to use it again...
Any more ideas? Would be great if someone could help me on that.
thx.
so my tf300 is rooted and unlocked bootloader, im trying to do the disabling journaling
im already at twrp and my tablet is connected to my pc
but everytime im trying the adb shell it says:
daemon could not start, starting at port 5037
daemon started succesfully
error: device not found
what seems to be the problem here? i tried to install my sdk, still no luck.
Using USBDeview (suggested here - comment 7 : http://code.google.com/p/android/issues/detail?id=2676 ) helped me get my TF300 to appear under 'adb devices'.
Still can't seem to access the device via localhost though.
(I'm trying to get access for web-dev purposes - see here : http://forum.xda-developers.com/showthread.php?t=1966358 )
I've recently installed Cyanogenmod 10.1 build RC1 on my Galaxy Gio and I can't find the Performance options or the Developer options which in other builds I've used where found in Settings at the System tab. Help anyone, should I just reflash ?
gosdra said:
I've recently installed Cyanogenmod 10.1 build RC1 on my Galaxy Gio and I can't find the Performance options or the Developer options which in other builds I've used where found in Settings at the System tab. Help anyone, should I just reflash ?
Click to expand...
Click to collapse
Go to about phone go to your build number and tap it 10 times
Sent from my SCH-I500 using Tapatalk 2
after I do 'adb devices' , it gives:
* daemon not running. starting it now on port 5037 *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
hieron123 said:
after I do 'adb devices' , it gives:
* daemon not running. starting it now on port 5037 *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
Try system wide installation ADB/fastboot. Make sure your phone has "USB debugging" enabled and is recognized in windows device manager.
If you have problem with adb you can stop it typing:
adb kill-server
before using any other commands
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.
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