Is it possible to run ADB on the tablet with its dock? For example, to plug in my Galaxy Nexus to the tab and run commands like I would do on my PC.
Sent from my Transformer Pad infinity using xda premium
Use a terminal emulator - there's plenty in the Play Store
danger-rat said:
Use a terminal emulator - there's plenty in the Play Store
Click to expand...
Click to collapse
Ahh, didn't know I could do that. Thanks! Only error I'm getting is whenever I type "adb shell" it turns up with "error, device not found". What am I doing wrong? USB Debugging is enabled on the phone.
Sent from my Transformer Pad TF700T using xda premium
speedygonzo said:
Ahh, didn't know I could do that. Thanks! Only error I'm getting is whenever I type "adb shell" it turns up with "error, device not found". What am I doing wrong? USB Debugging is enabled on the phone.
Sent from my Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Do you have sdk installed?
You don't need adb shell when you are working directly on the local device...
"adb shell" let's you connect to a remote device. When you work in a terminal emulator, you're working on the local device...
danger-rat said:
You don't need adb shell when you are working directly on the local device...
"adb shell" let's you connect to a remote device. When you work in a terminal emulator, you're working on the local device...
Click to expand...
Click to collapse
yeah my bad, did not read all the above, didn't know he's using terminal.
danger-rat said:
You don't need adb shell when you are working directly on the local device...
"adb shell" let's you connect to a remote device. When you work in a terminal emulator, you're working on the local device...
Click to expand...
Click to collapse
Oh, ok. I'm just so used to using it on my computer. Lol. Well I got it working! Thanks again!
Sent from my Transformer Pad TF700T using xda premium
Related
Hello
I installed adb and the android SDK. My Atrix is in usb mode and has usb debugging on. When I type in adb devices, my atrix is there. But when I type in adb shell it says
"daemon not running. Starting it now"
"daemon started successfully"
"daemon still not runningerror: Cannot connect to daemon"
My Atrix is rooted and has Adeo custom rom
Whe you say it is in 'USB mode', what exactly do you mean? If you have mounted storage ADB won't work.
Yeah. You have to plug it in USB Debug mode. It should be under settings >applications.
Sent from my LG-P500 using XDA Premium App
Omnichron said:
Yeah. You have to plug it in USB Debug mode. It should be under settings >applications.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
I did that. I plug my Atrix in and select usb as non or moto portal. It still gives that error.
Hello,
I finally can connect my TF201 to adb but when I type adb shell I got the following message:
adb shell
error: protocol fault <status 73 68 65 6c?!>
Any help?
This is the 101 form not the 201 but you might want to try
adb kill-server
adb start-server
adb devices
adb shell
and see if that fixes it
unfortunately, no difference...
Adb remount?
might be a stupid question but usb debugging and root access over adb enabled?
It's ok now. I'm using Win XP into Virtualbox and after disabling USB 2.0 in the settings, it worked.
My TF201 is rooted!
But still with build .15? No .21 update automatically coming afterwards?
You need to manually flash stock rooted or a custom ROM, head over to the prime section to get you a recovery and ROM. You can't take OTAs when rooted.
Strange, some said they could upgrade? I tried CM9 but it did not convince me. IPS mode, and handy menu by hitting the notification area do not exist.
Sent from my Transformer Prime TF201 using xda premium
adb does not find my nexus 4 on my mac. Here's what I tried:
$ adb kill-server; adb devices
$echo 0x18d1 >> ~/.android/adb_usb.ini
$ adb kill-server; adb devices
Changed usb computer connection type to PTP instead of MTP
Any suggestions on what else I can try?
Try put ./ before any command. See if this works. Sometimes Mac OS wants you to put it in and other times it works without it. I speak from experience with my Mac.
Sent from my HTC One using Tapatalk 4
WildfireDEV said:
Try put ./ before any command. See if this works. Sometimes Mac OS wants you to put it in and other times it works without it. I speak from experience with my Mac.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
./ will look in the current folder. adb is on my path
faulty cable
Looks like it was a faulty cable. The good folks at stackoverflow helped me rule out other options.
Hi can anyone help me plz i am trying to install FLATLINE[ on my tf700t running cromix 5.03 i decided to post in general section since i cant post in development thread as yet.
I have successfully setup fastboot and installed drivers etc on my computer, (im using windows 8)
But every time i enter fastboot command (fastboot -i 0x0b05 flash recovery flatline_tf700) i get error: cannot load flatline_tf700 :no error
I have attached a screen shoot of the fastboot command. I have the flatline_tf700 img in the same folder where i installed minimal ADB and fastboot tool.
techcrazy101 said:
I have the flatline_tf700 img in the same folder where i installed minimal ADB and fastboot tool.
Click to expand...
Click to collapse
Looks like you don't, or you mistyped the file name, or you forgot the file extension.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
_that said:
Looks like you don't, or you mistyped the file name, or you forgot the file extension.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Omg thanks _that the spelling of the file was wrong i got it to work i successfully generated the blobs but i dont know what i should do now
Please adb pull /data/media/AndroidRoot
Where do i type this on the same cmd on computer or do i need to reboot devices and use terminal on device to do this sorry for being so noobie been trying all day to get this working
I tried the adb pull/data/media/AndroidRoot on the miminal fastboot tool but it just says waiting for devices and nothing happens.
techcrazy101 said:
I tried the adb pull/data/media/AndroidRoot on the miminal fastboot tool but it just says waiting for devices and nothing happens.
Click to expand...
Click to collapse
To use adb, the device must be in Android with USB debugging on.
_that said:
To use adb, the device must be in Android with USB debugging on.
Click to expand...
Click to collapse
Wew this thing is harder than i taught, thanks for clearing things up for me.
Ok now another problem adb is running im able to identify that my device is connected by typing adb devices all is good.
The problem now is that when i type adb pull/data/media/AndroidRoot it doesnt work it just list the different adb commands i also tried adb pull /tmp/AndroidRoot from the tutorial but this doesnt work either and i made sure i checked spelling its all good.
Im able to navigate to data/media/AndroidRoot using ES file explorer and the blob.bin file is in there.
So i decided to boot into apx mode and was successful but when i run wheelie.exe from computer the black pop up box (cmd window) just opens for like a sec and closes i think it says specify blob file or something like that. So i copied the blob.bin file from tablet using es explorer and then copied it to my computer where the wheelie.exe file is but still no luck. Im really stressed trying to do this am i doing something wrong?
You don't run wheelie directly.... Put it with your blob file and fastboot, and adb and nvflash than execute it from your terminal. Hope that hleps
Sent from my ASUS Transformer Pad TF700T
techcrazy101 said:
The problem now is that when i type adb pull/data/media/AndroidRoot it doesnt work it just list the different adb commands
Click to expand...
Click to collapse
You forgot the space after "pull".
techcrazy101 said:
i also tried adb pull /tmp/AndroidRoot from the tutorial but this doesnt work either
Click to expand...
Click to collapse
That works only directly after creating the blobs while still booted inside the recovery.
techcrazy101 said:
So i decided to boot into apx mode and was successful but when i run wheelie.exe from computer the black pop up box (cmd window) just opens for like a sec and closes
Click to expand...
Click to collapse
Open the cmd window first, then run wheelie with the correct command line options as described in the guide.
_that said:
You forgot the space after "pull".
Open the cmd window first, then run wheelie with the correct command line options as described in the guide.
Click to expand...
Click to collapse
Finally i am finished thanks again _that:good: one last thing the following command:
nvflash --resume --go Isn't that supposed to continue booting tablet into android it just says resume mode in cmd nothing happens, so i just held the power button to reboot tablet.
I have seen discussions online such as this:
https://stackoverflow.com/questions/12634280/what-is-a-adb-daemon
If I understand the answers give there correctly, whenever I use an adb command on my computer connected to a smartphone, the reason it does anything is because there is a background process adbd, the adb daemon, running on the smartphone. Everything I see on the computer screen when I issue an adb command is the result returned by the adbd daemon.
a) Is this correct? Is this how adb is supposed to work?
b) If it is correct, is there any way to programmatically enable/disable/re-enable the adbd process? Can I programmatically interact with adbd at all (either through Java or NDK)? Can I use adbd from the android phone itself and perform actions performed using adb, without using a computer?
I am hoping to do this on a non rooted device, but if not, any kind of device will do.
mahaju said:
I have seen discussions online such as this:
https://stackoverflow.com/questions/12634280/what-is-a-adb-daemon
If I understand the answers give there correctly, whenever I use an adb command on my computer connected to a smartphone, the reason it does anything is because there is a background process adbd, the adb daemon, running on the smartphone. Everything I see on the computer screen when I issue an adb command is the result returned by the adbd daemon.
a) Is this correct? Is this how adb is supposed to work?
b) If it is correct, is there any way to programmatically enable/disable/re-enable the adbd process? Can I programmatically interact with adbd at all (either through Java or NDK)? Can I use adbd from the android phone itself and perform actions performed using adb, without using a computer?
I am hoping to do this on a non rooted device, but if not, any kind of device will do.
Click to expand...
Click to collapse
Yes, but it requires having a rooted device and the terminal emulator app. Or you can install TWRP and use the terminal emulator that is built into TWRP.
Sent from my SM-S767VL using Tapatalk
reply to answer
Droidriven said:
Yes, but it requires having a rooted device and the terminal emulator app. Or you can install TWRP and use the terminal emulator that is built into TWRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I have an old rooted samsung phone with android 4.2.2
Is there any sample code on how I can interact with the adbd daemon? In the terminal emulator if I type "adb shell" it says starting daemon but then it says device not found. how would I do some basic stuff (like take a screen shot using "adb shell screencap" for example? Can I interact with it programmatically from java or ndk?
mahaju said:
I have an old rooted samsung phone with android 4.2.2
Is there any sample code on how I can interact with the adbd daemon? In the terminal emulator if I type "adb shell" it says starting daemon but then it says device not found. how would I do some basic stuff (like take a screen shot using "adb shell screencap" for example? Can I interact with it programmatically from java or ndk?
Click to expand...
Click to collapse
When using terminal emulator, it uses the same commands as adb shell(not the standard adb), but you remove "adb shell" from the commands. For example, in terminal emulator, it is:
reboot recovery
Instead of:
adb reboot recovery
Or
adb shell reboot recovery
Also, before running your commands in terminal emulator, you need to use the su command by typing:
su (then press enter, grant the app superuser/root permissions)
Then you can run the rest of your commands.
Sent from my SM-S767VL using Tapatalk