I'm doing this simple guide on how to achieve a logcat when an issue is received
It's very simple but some people on here don't know how to do one.
1. Download Android SDK from here:
Code:
http://developer.android.com/sdk/index.html
2. Extract Android SDK to any area
3. Once Android SDK is extracted, be sure to put the path and download Android SDK Tools:
Examples:
Windows
Open your start menu, right click on 'My Computer' and select 'Properties'
Once another window opens go to 'Advanced settings'
Followed by selecting 'Environmental Variables'
Look for PATH and enter the following:
Code:
C:\Android-sdk-windows; C:\Android-sdk-windows\platform-tools; C:\Android-sdk-windows\tools;
Now java will need to be installed
Go to the following link:
Code:
http://www.java.com/en/
Go into Android SDK folder and open 'SDK Manager.exe'
Only check 'Android SDK Tools' and Android SDK Platform-tools
Linux
Go into your Home folder and Press CTRL+H (This is done to show hidden folders and files)
Look for the file '.bashrc'
Open it and put the following or similar:
Code:
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
You will need to add something for any devices to be recognized:
Open terminal and enter:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Enter the following in the file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Now save and close the file, in terminal enter:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
Now you will need to install java
Open terminal and enter:
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
Now that everything is installed
Open terminal either type:
Code:
android
OR, if that doesn't work
Code:
cd ~/android/sdk/tools
./android
4. How to do a logcat:
This is very simple as now you have installed Android SDK and ADB
First connect the device via USB to your computer
Be sure to have usb debugging enabled
To verify the device is connected type:
Code:
adb devices
Windows
Open Command Prompt
Enter the following (Yes there's a space in between the '>'):
Code:
adb logcat > logcat.txt
Linux
Open Terminal
Enter the following (Yes there's a space in between the '>'):
Code:
adb logcat > logcat.txt
*The logcat.txt is your logcat that you can copy and paste for developers
5. Now that you've created a logcat copy and paste it to:
http://pastebin.com/
Now if someone in any sensation development thread ask you how do create a logcat
Be sure to give them the link to this guide
Thanks
blahbl4hblah said:
Now if someone in any sensation development thread ask you how do create a logcat
Be sure to give them the link to this guide
Thanks
Click to expand...
Click to collapse
Should keep it in your sig too. Good work.
aNYthing24 said:
Should keep it in your sig too. Good work.
Click to expand...
Click to collapse
Good point
I'm tired of people reporting issues and there's no logcat
Now they have no excuse
Be sure to read step by step everyone
blahbl4hblah said:
Now you will need to install java
Open terminal and enter:
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
Click to expand...
Click to collapse
Why not OpenJDK? The Android stuff works fine with it
TamCore said:
Why not OpenJDK? The Android stuff works fine with it
Click to expand...
Click to collapse
When it comes to just adb I don't really care for openjdk but when it comes to compiling a rom I don't want it near my pc
Sent from my HTC Sensation
When I write
adb logcat > logcat.txt
answer is:
Access is denied. Why?
Can you post a screen shot of what you are doing?
GhostXSeries said:
Can you post a screen shot of what you are doing?
Click to expand...
Click to collapse
[Q]First do "adb logcat" then do "adb logcat > logcat.txt" ?
......
and this "Access is denied" is disappear.
now I am waiting to finish "adb logcat" then I well do "adb logcat > logcat.txt".
If doesn't Work I will post a screen shot
---------- Post added at 01:07 PM ---------- Previous post was at 12:42 PM ----------
what is this? :|
https://www.dropbox.com/s/9ubqfwhevpfetqi/Loop.bmp
GhostXSeries said:
Can you post a screen shot of what you are doing?
Click to expand...
Click to collapse
May be, but I don't see the point since it's an EASY GUIDE.
Adb logcat part tells you before to open terminal.
Is that really hard to follow?
Sent from my Sensation
azoz123456 said:
When I write
adb logcat > logcat.txt
answer is:
Access is denied. Why?
Click to expand...
Click to collapse
Probably because you didn't enable us debugging in your phone
Sent from my Sensation
azoz123456 said:
[Q]First do "adb logcat" then do "adb logcat > logcat.txt" ?
......
and this "Access is denied" is disappear.
now I am waiting to finish "adb logcat" then I well do "adb logcat > logcat.txt".
If doesn't Work I will post a screen shot
---------- Post added at 01:07 PM ---------- Previous post was at 12:42 PM ----------
what is this? :|
https://www.dropbox.com/s/9ubqfwhevpfetqi/Loop.bmp
Click to expand...
Click to collapse
You sir don't follow instructions do you?
I said do adb logcat > logcat.txt for a reason. It's to save your logcat to a text file to give developers of your issues
Sent from my Sensation
blahbl4hblah said:
May be, but I don't see the point since it's an EASY GUIDE.
Adb logcat part tells you before to open terminal.
Is that really hard to follow?
Sent from my Sensation
Click to expand...
Click to collapse
sorry
This is what I did:Here
blahbl4hblah said:
Probably because you didn't enable us debugging in your phone
Sent from my Sensation
Click to expand...
Click to collapse
I do it bro.
blahbl4hblah said:
You sir don't follow instructions do you?
I said do adb logcat > logcat.txt for a reason. It's to save your logcat to a text file to give developers of your issues
Sent from my Sensation
Click to expand...
Click to collapse
I do every thing.
My phone is Incredible s.
S-OFF & Rooted $ I have recovery
now I am use this ROM:
[ROM] ★ TSM UltimateKangBang v3.5 Rev. C ★ ICS 4.0.3 • Sense 4.0a • Updated 12/06/12
and I need the adb logcat because I am going to learn how to port ROM HTC one V to my Inc s.
I am use this thread :
http://forum.xda-developers.com/showthread.php?t=1222746
and this:
http://forum.xda-developers.com/showthread.php?t=1563857(although
but the result is:
ROM successfully insulted when I do reboot stay in HTC page.
......................................................
[Q] When I port ROM from ONE v to my phone, must be use ROM ICS4.0 or I can use any ROM "2.3.5"?!
because I use RUU stock for my phone." When I do porting"
[Q] how time take to finsh " adb logcat"?!
I know my English is bad sorry
I hope you get the point
Oh now I see what you did wrong, you didn't put any spaces in between the '>'
Try it with the spaces
adb logcat > logcat.txt
Click to expand...
Click to collapse
Just so I'll be more specific and make this 'noob proof' I'll update it
I'm in a good mood XD
After I enter "adb logcat > logcat.txt" nothing happens. ADB recognizes my devices. I have debugging enabled. It does say adb server is out of date, if that means anything.
Running 8-10-2012 tamcore nightly on HTC sensation. with tamcore kernel. Boot loader is locked with S-off. if that means anything.
how do you do one without a computer
Sent from my HTC Sensation using xda app-developers app
melo563 said:
how do you do one without a computer
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Look in the market. But those aren't as reliable
Sent from my Sensation
Paste bin says my log cat is too big. How can I fix this?
Sent from my HTC Sensation using xda premium
Hello, I'm having some trouble on win 7 . when i type in cmd adb devices i get adb is not recognized as a internal or external command. i installed the sdk manager in c\Android , installed java and i changed the environment variables to, path c:\Android-sdk-windows etc.... per the instructions. but i did something wrong since it's not working...i could use some help.... Thanks...
Related
I'm having trouble with step 4 of the rooting guide. The command prompt says:
data/local/gingerbreakBB: not found
Where should I place the files from the zip? Inside the platform-tools folder? Or inside a different folder?
Thanks in advance for helping a noob.
You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk
Jocelyn said:
You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
All the files were in the platform-tools folder originally. Just making sure because it isn't working.
Cory1234 said:
All the files were in the platform-tools folder originally. Just making sure because it isn't working.
Click to expand...
Click to collapse
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk
Jocelyn said:
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
Do you mean like to: C:\program files (x86)\android\android-sdk\platform-tools
??
I'm going to reinstall everything one more time.
Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?
Cory1234 said:
Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?
Click to expand...
Click to collapse
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9
baseballfanz said:
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9
Click to expand...
Click to collapse
Thanks. I got that info earlier by using google . Now I'm stuck on step 9. I am in a new terminal window. The output I receive after entering "md5sum cwm_blob_retransfer" is "md5sum is not recognized as an internal or external command, etc.
I also tried md5sums as another member commented on. Still no go.
This is starting to get frustrating..Jailbreaking was simple compared to this.
Anyone have any ideas?
Edit: Dur, Finally got it. Apparently, some of the files had write protection on them for some reason, which was causing all the problems. Thanks everyone for the help.
This will setup ADB to work on Ubuntu with your Transformer Tablet.
Step 1: Download the Android SDK.
Step 2: Unzip the Android SDK to /home.
Step 3: Next we will add the SDK to your path, substitue the example will the path to the tools folder of your SDK.
Example Path:
export PATH=/home/USER/android-sdk/tools/:$PATH
Click to expand...
Click to collapse
Step 4: To make 99-android.rules, run the following command.
sudo gedit /etc/udev/rules.d/99-android.rules
Click to expand...
Click to collapse
Step 5: Add the following lines:
#Transformer
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0b05", MODE="0666", OWNER="USER"
Click to expand...
Click to collapse
Step 6: Save the file.
Step 7: To restart udev, run the following command.
sudo restart udev
Click to expand...
Click to collapse
Step 8: Run the following commands:
adb kill-server
adb start-server
adb devices
Click to expand...
Click to collapse
If device is saying 'no permissions', go to step 5 and add those lines to the other .rules files in /etc/udev/rules.d.
Great guide! You could add step three to ~/.profile or /etc/profile (no dot) to make it permanent at each login. You don't need to add it to both profiles. The /etc/profile is for every one that logs on, ~/.profile is just for your ID.
Also, if you are editing the rules files, you might as well add support for APX mode.
Code:
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0955", ATTRS{idProduct}=="7820", MODE="0666"
You probably don't need the product ID.
EDIT: Not sure why the "no permissions" problem would come up, but I suspect it is because of conflicts with other rules in /lib/udev/rules.d/ You want to make changes in /etc/udev/... The rule with the highest number takes precedence. I think specifying the product ID will prevent conflicts too.
Hi thanks for the help, finally I get my adb working with my Transformer thanks to your .rules file (alwways kept me telling i had no permissions).
Perhaps, there is something I think you should specify for newbies:
Step 3: Open terminal and run the following commands.
export PATH=/home/USER/android-sdk/tools/:$PATH
Click to expand...
Click to collapse
Its important to exactly tell ubuntu where adb is.
In my case its not at TOOLS folder, its been move reciently to /android-sdk-linux_x86/platform-tools/
sylar666 said:
Hi thanks for the help, finally I get my adb working with my Transformer thanks to your .rules file (alwways kept me telling i had no permissions).
Perhaps, there is something I think you should specify for newbies:
Its important to exactly tell ubuntu where adb is.
In my case its not at TOOLS folder, its been move reciently to /android-sdk-linux_x86/platform-tools/
Click to expand...
Click to collapse
It was an example path, you have to give the actual location of your sdk because it may vary.
Sorry if I'm missing something obvious, but doesn't the SDK download off the Google site (linked above) not include adb by default?
I've had to go into the actual program:
Code:
cd /home/USER/[B]Android-SDK[/B]/tools/
./android
(substitute the bold for whatever your SDK directory is called)
Then via the GUI:
- click the Available packages menu option
- click the arrow on Android Repository
- choose to install Android SDK Platform-tools, revision X package
Then once the platform-tools package is installed, you can make sure it's in your path as well as "Tools" (shown in original post). I do this in my .bashrc file (in your home directory):
Code:
export PATH=/home/USER/[B]Android-SDK[/B]/platform-tools/:$PATH
(again, the replace the bold with your SDK directory)
Depending on how you do this, the adb command should now work in a terminal by typing 'adb'. If you put the path in your .bashrc or profile, you might like to run the command 'exec bash' first then try.
Confirmed to work on Arch (get it from the AUR) and just did it tonight on Ubuntu 11.04 x86-64. And thanks for the guide, OP Took me ages to work the udev rules out when I first got my TF. Hopefully this helps someone in the same position in the future.
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
mbze430 said:
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
Click to expand...
Click to collapse
Here ya go
oh ok lol thank u i found it dugh
silver03wrx said:
im trying to do this i keep getting the message the process cannot access the file because it is being used by another process?. i did adb kill-server then adb start server it started then i typed in adb logcat -d *:E > dump.txt. and i can not find the dang text file on my sd card lol sorry have not used adb much
Click to expand...
Click to collapse
the text file will be located in the directory where you ran the command from and not in the sdcard or in the phone
ok thanks bud here ya go
Attached my dump file.
I may need to google some of the crap that was in it.
Hi all.
Everyone here on our forum wants to help devs by testing different stuff but devs wants testers to send debug info to them so they can resolve bugs. Notifying bugs without logcats is useless and some users don't know how to collect these debug data.
To collect debug info there is a tool named ADB (Android Debugging Bridge). we r very small community and there are not plenty of sgr users around here so we have to worry about knowledgeable testers. so i m making this basic instructional guide to ADB. about how to set up ADB on windows and some basic usage.
Setting up ADB on windows.
Know this first.
> ADB requires usb drivers. So first of all install kies so that ur pc detects ur phone and ADB can recognise ur phone.
> Android is linux based and in linux commands are case sensitive so while typing these command use propare case otherwise commands won't execute.
> Windows uses back slash [\] and linux uses forward slash [/] so while typing file locations. For location of file in ur pc use back slash and for files in ur phone/sd card use forward slash.
there are two ways to setup adb on ur windows pc.
1 > download the android sdk, it includes the adb
u can download latest android sdk from HERE.
2 > only download adb package, no need of downloading the whole sdk.
look at the end of post to find the zip file of adb package.
now after downloading:
if u have downloaded sdk read this:
> after downloading sdk, extract it to ur desired location.
> after extracting, open that folder and goto "platform-tools" folder.
> now hold the shift key and hit right click in that directory
> click "open command window here"
> u will see command promp, type "adb" in command prompt. if adb executes means u have successfully setup adb on ur windows.
if u r using without sdk:
> just extract the package
> hold shift key, hit right click and choose "open command prompt here"
> type "abd" in command prompt and check if adb executes.
now as we have successfully setup adb lets begin to some basic commands.
first of all connect ur phone using usb cable. make sure u have checked usb debugging in settings>applications>development>check usb debugging.
now open adb as mentioned above and type
Code:
adb devices
u should see
Code:
list of attached devices
xyz device
xyz will be name of ur device, as default it will be some number.
Basic usefull ADB commands
1.
Code:
adb pull
this command can be used copy files from ur device to ur pc.
for eg.
Code:
adb pull /system/app/Camera.apk
this will copy the camera app to the directory where adb is extracted.
if u know the path u can copy anything using this command.
2.
Code:
adb push
this command can be used to push files to ur phone.
type the command, drag and drop the file in command prompt and than type location where u want to push that file and hit enter.
for eg, if i want to push image named android.jpg stored in my C drive.
Code:
adb push C:\android.jpg /sdcard/
this will push that image to sdcard.
sometimes we have to push some packages in specified folders. just type the location after file name.
for eg
Code:
abd push C:\sanim.zip /system/media
3.
Code:
adb install
with help of this command we can install apps to our phone dorectly from pc.
for eg. type "adb install" than leave one space with mouse choose apk file of app u want to install and drag and drop it in command prompt. path of that app will be displayed in command prompt. like this.
Code:
adb install C:\adb\Camera.apk
by executing this command u can install the app u have dragged and dropped in command prompt.
As i have written for windows but these commands can be used on ADB on linux/MacOS as well but i have only mentioned the set-up guide for windows only.
Credits/Source.
http://developer.android.com/tools/help/index.html
Getting Debug Infos (Logcats)
1. logcat
logcat is a report from android logging system which runs in background from the moment u boot ur phone. and it haves all the info what went wrong with system.
generally we can see logcat by typing
Code:
adb logcat
but that will show the constant data flow so better save it as file so can be sent to dev or u can study it later.
Code:
adb logcat > log.txt
this will store the logcat to directory of adb and collect log in text file.
2. bugreport
Code:
adb bugreport
bug report prints dumpsys, dumpstate, and logcat data to the screen. which can be used for bug reporting.
3. Java Debug Wire Protocol
Code:
adb jdwp
this command prints the list of available JDWP processes on connected device in command prompt.
Logcats On Mobileu can directly generate logcat on ur mobile using Terminal Emulator app, there are many terminal apps in market. CM comes with pre-loaded Terminal Emulator.
some terminal apps:
Android Terminal
Terminal Emulator
RomToolbox
u will need root access to generate logs
open terminal app, u will see following screen
Code:
$ export PATH=/data/local/bin:$PATH
$
now type su and hit enter.
allow super user permissions.
now to get a logcat type following command.
Code:
logcat > /mnt/sdcard/logcat.txt
this will generate text file named logcat.txt on root of ur sdcard which is containing logcat.
to get DMESG (Kernel Debug)
open terminal and type following command
Code:
su
dmesg > /mnt/sdcard/dmesg.txt
this will generate text file named dmesg.txt on root of ur sdcard which is containing kernel debug log.
Kernel Debugging.
we can use adb to debug kernel issues.
Code:
adb shell
dmesg
this will generate a log which is very helpful to resolve kernel issues, we just have to send this log to dev, he will look after it.
sometimes after flashing kernel we go into bootloop in that cases generate logcat using this commands and send to dev it will be very helpfull for dev to know and resolve reason causing bootloop.
Code:
adb shell
cat /proc/last_kmsg > /sdcard/last_kmsg
this command should be executed immediately on reboot otherwise it will be over written by new kernel message. the file will be stored on root of ur sdcard named last_kmsg. send this file to kernel dev it will help him great to resolve the problem.
Read this if u dont know how to get files from ur sdcard even if ur phone is not booting and stuck at bootloop.
u must have CWM to do this.
>boot ur phone in recovery mode (by holding VOL UP and HOME key together on boot)
>goto "Mounts and Storage"
>Select "Mount USB Storage" and plug in your data cable.
>Now u can access ur sdcard on ur pc, after ur work is done click "Unmount"
Hi,
Just a noob question... if my phone is stuck in a bootloop, is there anyway for me to get a logcat without flashing a new rom???
Sent from my GT-I9103 using xda app-developers app
JoJo2012 said:
Hi,
Just a noob question... if my phone is stuck in a bootloop, is there anyway for me to get a logcat without flashing a new rom???
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
If you have enabled USB Debugging , yes
"I have to go. It's just....they really need me." - Sora
Re: Toggle mobile data on and off via adb
Does anybody know how to toggle mobile data on and off via ADB?? IM WILLING TO PAY FOR THIS INFO lol I NEED IT THAT BAD!! PM ME PLEEEASE!!!!!
12manytimes said:
Does anybody know how to toggle mobile data on and off via ADB?? IM WILLING TO PAY FOR THIS INFO lol I NEED IT THAT BAD!! PM ME PLEEEASE!!!!!
Click to expand...
Click to collapse
'adb shell su -c "svc data disable"' and 'adb shell su -c "svc data enable"'. You must be rooted.
Sent from my GT-I9103 with CM10
Adam77Root said:
'adb shell su -c "svc data disable"' and 'adb shell su -c "svc data enable"'. You must be rooted.
Sent from my GT-I9103 with CM10
Click to expand...
Click to collapse
Thanks alot, i just sent you a PM but it shows that i didn't send anything, so if you didn't get the message please send me one cuz id like to buy you a beer!
I wish i could hit your thanks button a million times right now lol
Hello I am trying to create a batch file that has an infinite loop and was wondering if there are any adb commands that can do this.
I am also looking for an adb command that waits x amount of seconds before performing the next command.?
Any help would be greatly appreciated
Q. What is a logcat?
Ans. A logcat is a sort of written report for what things(operations like starting processes lot of dev related technical things) the phone is doing at a given time.
this guide shall provide simple step by step method (Will try to be very short and direct)
Why create this guide cause i found a lot of guides on this topic(Really a lot !!!)
But were written in a fairly roundabout manner so here is my attempt to simplify things.
Prerequisites : (Please read before doing anything)
For creating a logcat via computer :
1.ADB(Android Debugging Bridge) you can get a smaller version from here : ADB & logcat tools.zip else you can get it along with android SDK.
For creating a logcat via phone :
1.alogcat/catlog[APP]
OR
2.Terminal Emulator.[APP]
Ok down to business...
Via Computer (ADB) :
very useful cause you can start logcatting(Is there such term) even before booting.
open terminal at the location for ADB example for me its C:/ADB>
so now your teminal should look like this :
Code:
C:/ADB>
now connect your phone via USB and don't forget to tick Android Debugging option under app>development(2.3.x) or Developer Option>usb debugging(4.0.x & above) on your phone
now type this in the terminal
Code:
adb logcat -v long > name of problem.txt
nothing will happen on the terminal don't worry its working to end the logcat press ctrl+c.
you shall have a log file called name of problem.txt or whatever you thought of substituting that name of problem with inside your ADB folder.
Via Phone :
1.Via Terminal Emulator :
its same as for adb except you are already in the shell that is rather than doing adb to reach your phone and then command just enter the command simple
type this in your terminal emulator :
Code:
logcat -v long > name of problem.txt
to finish logging press vol down button + c
you will find a text file on your SD Card.
2.Via logcatting(still don't think its a word) APP
here are the links.
1.CatLog
2.aLogCat(free)
Sources :
http://developer.android.com/tools/help/adb.html
http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
and tutorial by paxChristos just a blatant ripoff by me just Noobyfied(is there such a word ???) by me.
If you have any doubts or problem Private message me ...(I do not reply to hate mail,controversies,or doubts that i feel have been adressed to the best of my knowledge here)
Good Luck and hope this helps you to get other developers address your problems convincingly:good::highfive:
good tutoiral you could add some basic adb commands to the op..
Via Phone don't works for me. Do I need to install something before this?
Can we make a logcat through our phone? ?
brady_4u said:
Can we make a logcat through our phone? ?
Click to expand...
Click to collapse
yes, you can do it from phone using terminal emulator!!!
sudarshan_mehta said:
yes, you can do it from phone using terminal emulator!!!
Click to expand...
Click to collapse
What command?
And then can we copy all the data from there? ?
Brady_4love said:
What command?
And then can we copy all the data from there? ?
Click to expand...
Click to collapse
search from google!!! i am too lazy to type all that commands!!!!
which data are you taking about?
Sent from my GT-S5670 using xda premium
taking logcat via phone (apps and terminal) is explained in the first post please look.
if confused pm me.
thankx
Dark Passenger said:
Q. What is a logcat?
Ans. A logcat is a sort of written report for what things(operations like starting processes lot of dev related technical things) the phone is doing at a given time.
this guide shall provide simple step by step method (Will try to be very short and direct)
Why create this guide cause i found a lot of guides on this topic(Really a lot !!!)
But were written in a fairly roundabout manner so here is my attempt to simplify things.
Prerequisites : (Please read before doing anything)
For creating a logcat via computer :
1.ADB(Android Debugging Bridge) you can get a smaller version from here : ADB & logcat tools.zip else you can get it along with android SDK.
For creating a logcat via phone :
1.alogcat/catlog[APP]
OR
2.Terminal Emulator.[APP]
Ok down to business...
Via Computer (ADB) :
very useful cause you can start logcatting(Is there such term) even before booting.
open terminal at the location for ADB example for me its C:/ADB>
so now your teminal should look like this :
Code:
C:/ADB>
now connect your phone via USB and don't forget to tick Android Debugging option under app>development(2.3.x) or Developer Option>usb debugging(4.0.x & above) on your phone
now type this in the terminal
Code:
adb logcat -v long > name of problem.txt
nothing will happen on the terminal don't worry its working to end the logcat press ctrl+c.
you shall have a log file called name of problem.txt or whatever you thought of substituting that name of problem with inside your ADB folder.
Via Phone :
1.Via Terminal Emulator :
its same as for adb except you are already in the shell that is rather than doing adb to reach your phone and then command just enter the command simple
type this in your terminal emulator :
Code:
logcat -v long > name of problem.txt
to finish logging press vol down button + c
you will find a text file on your SD Card.
2.Via logcatting(still don't think its a word) APP
here are the links.
1.CatLog
2.aLogCat(free)
Sources :
http://developer.android.com/tools/help/adb.html
http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
and tutorial by paxChristos just a blatant ripoff by me just Noobyfied(is there such a word ???) by me.
Click to expand...
Click to collapse
Thankx a lot man . Am a newbie and it helped me a lot!!!!! Thanks !!!:highfive::victory::good:
ADB Push
flasherruts said:
Thankx a lot man . Am a newbie and it helped me a lot!!!!! Thanks !!!:highfive::victory::good:
Click to expand...
Click to collapse
Are there any tricks to using ADB push and install? I hae been trying and cannot get it to work.
thanks a lot
Flashing NC2 Kernel
Installed NC4 firmware via Odin 3.09 version and used the safestrap by Hashcode, 3.75, posted on XDA. Installed "Towel Root" as well, but the problem is everytime I attempt to flash NC2 kernel it fails Looking for advice.
Bluedio777 said:
Installed NC4 firmware via Odin 3.09 version and used the safestrap by Hashcode, 3.75, posted on XDA. Installed "Towel Root" as well, but the problem is everytime I attempt to flash NC2 kernel it fails Looking for advice.
Click to expand...
Click to collapse
Sorry mate, you're on the wrong forum. Do you even check the title of OP before posting anything?
That's good work
please help
Dark Passenger said:
Q. What is a logcat?
Ans. A logcat is a sort of written report for what things(operations like starting processes lot of dev related technical things) the phone is doing at a given time.
this guide shall provide simple step by step method (Will try to be very short and direct)
Why create this guide cause i found a lot of guides on this topic(Really a lot !!!)
But were written in a fairly roundabout manner so here is my attempt to simplify things.
Prerequisites : (Please read before doing anything)
For creating a logcat via computer :
1.ADB(Android Debugging Bridge) you can get a smaller version from here : ADB & logcat tools.zip else you can get it along with android SDK.
For creating a logcat via phone :
1.alogcat/catlog[APP]
OR
2.Terminal Emulator.[APP]
Ok down to business...
Via Computer (ADB) :
very useful cause you can start logcatting(Is there such term) even before booting.
open terminal at the location for ADB example for me its C:/ADB>
so now your teminal should look like this :
Code:
C:/ADB>
now connect your phone via USB and don't forget to tick Android Debugging option under app>development(2.3.x) or Developer Option>usb debugging(4.0.x & above) on your phone
now type this in the terminal
Code:
adb logcat -v long > name of problem.txt
nothing will happen on the terminal don't worry its working to end the logcat press ctrl+c.
you shall have a log file called name of problem.txt or whatever you thought of substituting that name of problem with inside your ADB folder.
Via Phone :
1.Via Terminal Emulator :
its same as for adb except you are already in the shell that is rather than doing adb to reach your phone and then command just enter the command simple
type this in your terminal emulator :
Code:
logcat -v long > name of problem.txt
to finish logging press vol down button + c
you will find a text file on your SD Card.
2.Via logcatting(still don't think its a word) APP
here are the links.
1.CatLog
2.aLogCat(free)
Sources :
http://developer.android.com/tools/help/adb.html
http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
and tutorial by paxChristos just a blatant ripoff by me just Noobyfied(is there such a word ???) by me.
Click to expand...
Click to collapse
I followed the steps you gave, but when I try to open powshell in the ADB folder using "shift+right click" the option to open powershell is not there until 100 attempts later... you please tell me what Im doing wrong?