Here's the sit: A very good developer is trying to blind port a JB ROM to his sister device which happens to be my device. There's some issues and he needs a logcat starting as early as possible. I tried to run logcat from terminal emulator but it didn't output a log to the directory I specified. In the logcat tutorial thread it says to end logcat by pressing control+c; obviously that's not possible on the phone itself. So, is it even possible for a shell script to start logcat, end it via terminal emulator and the log then created?
Sent from my LG-P999 using xda premium
Волк said:
Here's the sit: A very good developer is trying to blind port a JB ROM to his sister device which happens to be my device. There's some issues and he needs a logcat starting as early as possible. I tried to run logcat from terminal emulator but it didn't output a log to the directory I specified. In the logcat tutorial thread it says to end logcat by pressing control+c; obviously that's not possible on the phone itself. So, is it even possible for a shell script to start logcat, end it via terminal emulator and the log then created?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Download and install the android SDK
Then in terminal or cmd prompt type
Adb logcat
Sent from my HTC PH39100 using Tapatalk 2
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
ok im rooted and can access my sdcard from my pc. how do i do the same with the internal memory of the phone?
thanks
mark
Check out androidcommander.
Sent from my ThunderBolt using XDA Premium App
ADB is all you need.
Sent from my ADR6400L using XDA Premium App
keith.mcintyre26 said:
ADB is all you need.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
i know i can adb pull but what would be the command to actually browse the system...
Use the command "adb shell" and browse as you would on your OS through the command prompt.
ex: for PCs for listing use the command "dir" and "cd" to navigate through folders
ex: for Macs you would have to use "ls"
tflogic said:
Use the command "adb shell" and browse as you would on your OS through the command prompt.
ex: for PCs for listing use the command "dir" and "cd" to navigate through folders
ex: for Macs you would have to use "ls"
Click to expand...
Click to collapse
does anyone know of a graphical interface...ive tried droid commander and another i just forgot the name but were laggy and wouldnt display everything correctly
B3L13V3 said:
does anyone know of a graphical interface...ive tried droid commander and another i just forgot the name but were laggy and wouldnt display everything correctly
Click to expand...
Click to collapse
im also hoping for something with a gui. i stopped using dos commands or whatever when i scrapped my ibm 286 with it's 10mb hd.
It's ridiculously easy to use lol
tflogic said:
It's ridiculously easy to use lol
Click to expand...
Click to collapse
ok, so i'm attempting to post an adb logcat output at another forum regarding an app. at the cmd prompt (of course directed to the proper tools folder) i use the following
adb logcat -f /sdcard/output.txt
hit return and i get a blinking cursor. nothing else appears to happen. am i mssing something? is there another way to create and view/save the logcat output?
thanks
mark
wouldn't it be:
Code:
adb shell
logcat > /sdcard/logcat.txt
markkal123 said:
ok im rooted and can access my sdcard from my pc. how do i do the same with the internal memory of the phone?
thanks
mark
Click to expand...
Click to collapse
http://www.appbrain.com/app/sshdroid/berserker.android.apps.sshdroid
http://www.netsarang.com/forum/xshell/list
http://filezilla-project.org/
*method only works on wifi since your phone is behind NAT
Code:
c:\logcat>adb logcat > logcat.txt
- waiting for device -
error: protocol fault (no status)
- waiting for device -
c:\logcat>
what does that suppose to mean? i need logcat for my miui port and i get this message.
the logcat.txt is saved in logcat folder
butr the file is blank.
Do adb devices and see if it can actually see your phone.
Sent from my HTC6435LVW using xda app-developers app
no it doesnt not while booting. does how ever see phone in recovery fastboot and adb sideload strange
well nevermind i lost all adb functions im dead in the water.
wheres that adb.ro.sercure=0 maybe thats the issue
Hi all,
I'm rooted and running Cyanogenmod 10.2.0. I'm trying to access some files on my device through ADB that require root access. I can change to the directory but when I attempt to list the contents of the directory I get a "permission denied" error.
I did enable Root access for "Apps and ADB" in the developer options on the phone.
Any ideas what's going wrong or (most likely) what I'm doing wrong?
TIA!
Sailing_Nut said:
Hi all,
I'm rooted and running Cyanogenmod 10.2.0. I'm trying to access some files on my device through ADB that require root access. I can change to the directory but when I attempt to list the contents of the directory
Click to expand...
Click to collapse
Will you please provide which command did you execute in cmd?
Please write it in same syntax as in adb
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Here are the commands I executed
Code:
adb shell
CD data/data/com.whatabou.pixeldungeon/files/
ls
The ls is where I get the error. It does change to the directory but it won't list the files. I have verified that I can see the files with root explorer.
Sailing_Nut said:
Here are the commands I executed
Code:
adb shell
CD data/data/com.whatabou.pixeldungeon/files/
ls
The ls is where I get the error. It does change to the directory but it won't list the files. I have verified that I can see the files with root explorer.
Click to expand...
Click to collapse
I have 2 answers. First - Go to adb
Code:
adb start-server
adb devices
adb shell
su
cd data/data/com.whatabou.pixeldungeon/files/
ls
Don't forget "su" command
When you give "su" command (depending on your phone) screen shows toast message or Superuser access for shell. In latter case give access.
Second- if above doesn't help
Then this will help to pinpoint problem.
Install terminal emulator from Play Store. Open and give Superuser access.
Code:
su
cd data/ /data/com.whatabou.pixeldungeon/files/
ls
Don't forget "su" command.
If 2nd method works then there is a problem with adb. If second method doesn't work then problem in phone.
Press thanks if helped
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Thanks for the response.
I KNOW the problem was that I forgot the su. Stupid me! I was assuming that since I was rooted that the shell was automatically elevated.
But now I have a different problem. I'm unable to use the original PC that I was working with and I've switched to another. Now I can't seem to get ADB to connect to my device. As first it showed no devices when I did the devices command. I realized it was likley because I didn't have the Samsung drivers installed, so I installed those and now I see the phone but it shows offline.
Any ideas what might be going wrong now?
I'm going to do a bunch of Googling to try to figure it out, but if I'm not successful maybe someone here will have an answer.
Thanks tons!
OK all solved!
I'm not sure what along the way I did that fixed my device offline problem. (It may just be that I never saw the RSA fingerprint notification on the phone the first bunch of times.)
The su took care of not being able to see the files when executing ls.
Thanks @hnkotnis
Sailing_Nut said:
OK all solved!
I'm not sure what along the way I did that fixed my device offline problem. (It may just be that I never saw the RSA fingerprint notification on the phone the first bunch of times.)
The su took care of not being able to see the files when executing ls.
Thanks @hnkotnis
Click to expand...
Click to collapse
Glad to help you.
I also had the adb saying offline problem. First it wouldn't show device. Then after Computer and phone reboot, it showed offline. I reinstalled Samsung adb drivers. It said I already have drivers. I said yes still install and rebooted. Problem solved. It occurred once again, but was repaired automatically.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Hey all I hope I'm not in the wrong section and I tried searching for an already similar if not identical thread but couldn't find one(probably not looking too hard) but I have a rooted LG G2 and I have ADB up and running but I don't know the commands I'm assuming. I type "ADB shell" and it connects and finds device but the only command that works for me is "reboot system". I've tried "boot recovery" and a few iterations but no luck.. Do I just not know the correct commands to tell it?
Sent from my LG-D801
DurbanPoison24 said:
Hey all I hope I'm not in the wrong section and I tried searching for an already similar if not identical thread but couldn't find one(probably not looking too hard) but I have a rooted LG G2 and I have ADB up and running but I don't know the commands I'm assuming. I type "ADB shell" and it connects and finds device but the only command that works for me is "reboot system". I've tried "boot recovery" and a few iterations but no luck.. Do I just not know the correct commands to tell it?
Sent from my LG-D801
Click to expand...
Click to collapse
It would help if you told us what it is you're trying to do. If you just want a full list of every command then there's threads and websites that have it all. If you're trying to do something specific then let us know and we'll try and give you the correct commands.
The most common you'll use are:
adb devices - To ensure phone is connected correctly.
adb shell - To access the phone shell (?).
adb push [filename] /path/to/destination - Send a file from PC to phone, usually the sdcard.
Mr_JMM said:
It would help if you told us what it is you're trying to do. If you just want a full list of every command then there's threads and websites that have it all. If you're trying to do something specific then let us know and we'll try and give you the correct commands.
The most common you'll use are:
adb devices - To ensure phone is connected correctly.
adb shell - To access the phone shell (?).
adb push [filename] /path/to/destination - Send a file from PC to phone, usually the sdcard.
Click to expand...
Click to collapse
If it makes any sense I really wasn't trying to do anything specific I just wanted to make sure everything was working right. And as for what wasn't working for me was telling the phone to go into recovery. That's honestly the only thing I was trying.
Sent from my LG-D801 using xda app-developers app
You don't need a shell for this
adb reboot recovery
Should do the trick, opening a shell gets you into the phones file system which is not needed to reboot to recovery
Just do a quick Google search and you will find many guides on this, especially here in xda
Sent from my Nexus 7 using XDA Premium 4 mobile app