guys i'm trying to do this multi touch thing on my x10 mini pro
http://forum.xda-developers.com/showthread.php?t=1064558
i'm a little confuse about the "shell" that he's talking about, can i ask you guys what's shell means? tnx...
guys pls help me on this
He means the terminal application or ADB.
do i have to install ADB on my phone?
tnx for your reply by the way..
i already studied the adb, but the prob is i can't access my phone via cmd why? can anybody help me or teach me pls
Just download the SDK, then go to installdir/platform-tools and launch ADB with "ADB.exe shell" (either from cmd/cygwin or create a shortcut). But if you've got Cyanogenmod, you've got a "Terminal" application right on your phone that can be used as well.
Hans Schmucker said:
Just download the SDK, then go to installdir/platform-tools and launch ADB with "ADB.exe shell" (either from cmd/cygwin or create a shortcut). But if you've got Cyanogenmod, you've got a "Terminal" application right on your phone that can be used as well.
Click to expand...
Click to collapse
everytime i execute the adb.exe it just appears as cmd then it closes why?
i tried studying the adb guides but still i dont understand how to access my sdcard
Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
antonio91282 said:
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
Click to expand...
Click to collapse
Did you put your phone in debug? Settings>Applications>Development
yes. and i been going over the directions repeatedly on theunlockr. im running xp 32 i believe
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
cd C:\Program Files\Droid Explorer\SDK\tools
Click to expand...
Click to collapse
- <type your ADB command here> e.g.
adb shell
Click to expand...
Click to collapse
^ yeah...
adb devices
Click to expand...
Click to collapse
should show your device...
To the OP, I don't know if this is the case for you but I changed my path on my Windows PC like the guides said to and that didnt completely work. (Maybe neede a restart). But in any case if you go to the command prompt, change directories to were you have adb and run your commands from there, it works like a charm.
For example if you unzip the the SDK in your download directory, open up the command line and type:
cd C:\Documents and Settings\<your user name>\Downloads\<whatever-you-named-the-unzipped-folder>\tools
ADB is in the tools directory you just went to. From here you can run the adb command without having to set up the system paths. This is a quick and dirty explanantion and might not even work for you. I was running this on Windows XP when I had this problem. Same thing had to be done on my Ubuntu Linux box b/c I'm to lazy to set up paths on that one, lol.
zephiK said:
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
- <type your ADB command here> e.g.
Click to expand...
Click to collapse
Oops, didnt see that you allready posted this. Yea do what zephiK says and it should work.
i have not been able to get adb to work no matter what i did (i am using xp) and i have been trying since i had the htc magic last year. here is how i recently got it working.
i downloaded the one-click root zip file and unzipped it. inside there is a adb.exe file. i clicked it and then then made sure my phone was in debugging mode and connected to my pc and used the command prompt to point to where adb is in my android sdk which for me is cd\androidsdk\tools
adb devices
i hit enter after tools and enter after devices and now it works. not sure why but it does. i couldnt get my magic, my nexus one or even the galaxy to work until i did this.
i got everything done. i think? only problem is im getting $ sign instead of # sign. any ideas?
i got adb working. thanks everyone.
A thread success story without any casualties. Almost makes me weep.
Win 7 x64
AT&T Xperia X10a
I was trying to root my X10a, using the one click method (X10Root.1.0.8.apk), and got hung up when trying to side load the app. ADB nor SWM could find the device. I finally got ADB to find my device. Here is how I got it to work.
Xperia- have debugging on
- have titanium backup free installed
- have busy body free installed
- do NOT mound SD
- have allow mock locations on
- have stay awake on
PC- have pc companion installed BUT terminate the process
- have the android sdk installed. (when installing I just installed everything)
- have android-sdk_r07-windows folder in C:/
- I changed the folder name above (android-sdk_r07-windows) to sdk
- have X10Root.1.0.8.apk file in C:/
- if google calander sync installed exit it.
With X10 plugged in and all above met.
Open command prompt
Type or copy and paste(if you changed folder name) cd C:\sdk\tools
Hit enter
Type adb kill-server
Hit enter
Type adb shell
Hit enter
Type adb install C:\X10Root.1.0.8.apk
Hit enter
Now the app should be on your phone. I hope this helps some AT&T X10 owners out there. Everyone keep up the good work.
Good info, I bet it will become very usfull to other in case they need to SideLoad. I did mine after 4 hours of time spending and finding the issue couple days ago.
Cheers,
Someone did post a fix for this on a java issue too...I like the adb method though..The sideloader and at&t just don't like each other! Would be awesome if we could use RSDlite to flash it though!
download and install this driver :
http://developer.sonyericsson.com/cws/download/1/825/494/1279522933/X10_drivers.zip
PS : APK files are like setup.exe on wondows... you must to copy it on your X10's SD card, and execute it on the X10, NOT on your PC !!
iam having trouble using ADB with windows XP. i have downloaded superoneclick program and opened the ADB folder inside. then i turned usb debugging on, then connected, then ran the ADB program, it starts with showing how to run commands, but only stays open for about 5 seconds, then closes, i cant read what the rest of it says because it closes to quickly. iam new to android and have never used adb before but i followed all the steps i think. what iam i doing wrong? thanks
RPK925 said:
iam having trouble using ADB with windows XP. i have downloaded superoneclick program and opened the ADB folder inside. then i turned usb debugging on, then connected, then ran the ADB program, it starts with showing how to run commands, but only stays open for about 5 seconds, then closes, i cant read what the rest of it says because it closes to quickly. iam new to android and have never used adb before but i followed all the steps i think. what iam i doing wrong? thanks
Click to expand...
Click to collapse
you have to open a command prompt in the folder where adb.exe is stored. you don't need to run the program itself, just run commands necessary to do whatever hack you're trying to do. if you just put the apk files in the same folder as adb.exe then use "adb push" commands and such (whatever is detailed in the instructions)
to open a command prompt in the folder, i think you can just right click and select "Open command prompt here" (i know that's in win7, not too sure about xp)
also - this is the wrong section to post this. it should be in the Q&A section, not development.
raybond25 said:
you have to open a command prompt in the folder where adb.exe is stored. you don't need to run the program itself, just run commands necessary to do whatever hack you're trying to do. if you just put the apk files in the same folder as adb.exe then use "adb push" commands and such (whatever is detailed in the instructions)
to open a command prompt in the folder, i think you can just right click and select "Open command prompt here" (i know that's in win7, not too sure about xp)
also - this is the wrong section to post this. it should be in the Q&A section, not development.
Click to expand...
Click to collapse
thanks for your help. when i extracted adb from S.O.C. i gave me 5 files
ADB.exe
ADBmac
ADBlinux
ADBWinUsbapi.dll
ADBWinApi.dll
I right clicked on all of them and couldnt find anything about opening command prompt?
RPK925 said:
thanks for your help. when i extracted adb from S.O.C. i gave me 5 files
ADB.exe
ADBmac
ADBlinux
ADBWinUsbapi.dll
ADBWinApi.dll
I right clicked on all of them and couldnt find anything about opening command prompt?
Click to expand...
Click to collapse
start, run and type cmd. this gives you a command prompt
Why are you using super one click on your atrix? Gingerbreak or gladroot is the preferred method for the atrix.
Sent from my Blue Steeled Atrix
Big-A-Rob said:
Why are you using super one click on your atrix? Gingerbreak or gladroot is the preferred method for the atrix.
Sent from my Blue Steeled Atrix
Click to expand...
Click to collapse
Yes I know iam just trying to get the ADB files from.SOC. iam rooted on gingerbreak.
Sent from my MB860 using XDA App
scorneil said:
start, run and type cmd. this gives you a command prompt
Click to expand...
Click to collapse
Start the. Exe? Because it wont allow me to type any commands it just runs for about 2 seconds then closes.
Sent from my MB860 using XDA App
Hello all, I've been really happy with my XPS ever synce I've root it and everything is working clockwork, except there is something eating my battery.
I've used "BetterBatteryStats" app, and i've got a parcial wakelock "AlarmManager" in 1st place.
I've read that to know eacly what app is waking the phone i've got to connect the phone to a Pc, run "ADB" and type "adb shell dumsys alarm > C:\alarm_log.txt".
This will creat a log file that will show what app is generating all those wake numbers, and then unistall or limit it.
The problewm is... what is ADB.EXE??? Where can i get that program for the pc? Does the phone have to be in USB debuggin mode? If someone help me I'll post a guide to anyone in need to find the problematic apps that eat battery for others noobs out there!
Here
Sent from my ST25i using Tapatalk 2
As the above is saying you should search n read a lot... there are guides all over in net in many n here xda as well... Its a good start by learning urself from the help already here..
1. ADB is included in SDK here. get it ...http://developer.android.com/sdk/index.html
2. Here is a guide to set up SDK... http://www.talkandroid.com/guides/developer/android-sdk-install-guide/
4. Browse to folder platform-tools adb.exe is inside... but u can't just click open it.. adb is used via command prompt (cmd)
5. Easy way to open cmd to adb is Shift+ right click -> click open cmd here
6. To connect phone in adb u have to enable usb debugging mode as u said..
7.Then start typing commands....
Thank you a lot for the aswer!
I DID goodle for the answer, but I had an hard time undestanding what I should do, I'm a pharmacist, not a technician.
That beeing said, the other part of the info I posted I found using the search funcion.
Anyway, thank you a lot for that answer, I'll try it now.
s-X-s said:
As the above is saying you should search n read a lot... there are guides all over in net in many in here xda as well... Its a good start by learning urself from the help already here..
1. ADB is included in SDK here. get it ...http://developer.android.com/sdk/index.html
2. Here is a guide to set up SDK... http://www.talkandroid.com/guides/developer/android-sdk-install-guide/
4. Browse to folder platform-tools adb.exe is inside... but u can't just click open it.. adb is used via command prompt (cmd)
5. Easy way to open cmd to adb is Shift+ right click -> click open cmd here
6. To connect phone in adb u have to enable usb debugging mode as u said..
7.Then start typing commands....
Click to expand...
Click to collapse
To perform this actions, is it mandatory that phone needs to be rooted?
Because, i followed all the steps, when i executed the command in cmd prompt, i got below info
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/system/bin/sh: dumsys: not found
What should i need to do now if phone doesn't needed to be rooted?
For using adb not necessarily ur phone rooted... but if u need to get anything insdie system folder ur phone needs root access... you can pull/push files from adb.. but it makes more easier if u do those for sdcard via windows explorer after connecting via usb..
In short its for rooted devices mostly.....
Ok, still need help on this one.
I've followed all the steps, installed SDK, phone in development, command line accepted, but then I check the log file I get this:
/system/bin/sh: dumsys: not found
So... Why is it now finding my phone? any idea? When am i supposed to connect the phone to the pc?
Thank you for the help!
Miguel Pereira said:
Ok, still need help on this one.
I've followed all the steps, installed SDK, phone in development, command line accepted, but then I check the log file I get this:
/system/bin/sh: dumsys: not found
So... Why is it now finding my phone? any idea? When am i supposed to connect the phone to the pc?
Thank you for the help!
Click to expand...
Click to collapse
dumpsys, not dumsys. With a P.