Related
Hello,
I'm trying to troubleshoot why some kernels result in bootloops on my phone and others work just fine. (For example, KingxKernel CFS #8 would work, but not #9-#11)
I read somewhere about running a logcat during boot, but I have no idea how to successfully do this.
Any Suggestions?
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Cool man thanks for the tips.
This is def. A needed logcat command.
Sent from my PC36100 using XDA App
Try using ddbt, very useful for debugging in real time
Sent from my PC36100 using XDA App
sqeet said:
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Click to expand...
Click to collapse
Just to expand...
adb -d logcat>mylogfile.txt
if you want to save your output to a file. Though you are not going to see anything on the screen until you breakout (control c). Just type...
type mylogfile.txt|more
to view the file (or you could use notepad).
sorry meant ddms, not ddbt. It should be in the tools directory along with adb
Just to add that if you want to save the log file and see the output to the screen in real time you can
Code:
adb -d logcat &> log.txt
and then run
Code:
tail -f log.txt
provided that the command tail is available to your system.
Great stuff
sqeet said:
Nevermind, I figured it out.
But, for general information:
run this command on your computer before booting your phone up, and it will wait for the device:
adb -d logcat
Also, make sure you can connect to adb with your phone in working order before trying to logcat during boot:
1. android sdk installed
2. proper usb driver installed
2. phone in usb debug mode
Sorry for the pointless post.
Click to expand...
Click to collapse
Not a useless post at all. I landed here because I was searching for it. Thanks.
hi my htc desire keeps restarting when i flash any gingerbread miui rom i have tired data2ext and a2sd and have wiped and also formated my sdcard and stil have same problem with both but it works fine with all other roms and the froyo version of miui. please help
What hboot are you using and how did you root your phone?
Sent from my HTC Desire using xda premium
hi im using normal hboot-0.93.0001 i used unrevoked to root my phone i am not really a noob i have flashed and rooted many phones but for some strange reason all other roms including miui froyo work on my phone but gingerbread miui wont it loads up to the home screen and then just reboots ive tried data2et version and a2sd version and same thing happens with both versions.i have also tried using diffrent recoverys amon-ra,clockwork etc and still get the same problem.
You need to understand what is going on under the hood.. Getting an adb logcat is the way to go..
Code:
Windows>Start>Run
echo "null" > log.txt
start log.txt
adb logcat > log.txt
Use Notepad++ to associate with the txt file and reload the file every couple of seconds while keeping the cmd shell in the background.. See what's happening just before it reboots. It could be anything from a bad script to a bad module
Have you tried gingerbread 2.8, its simple and a very plain ROM, I have had issues with miui roms with my desire, if that doesn't work I will keep looking my self, sorry I'm not very insightful, you have an odd problem.
Sent from my HTC Pyramid using xda premium
Nice one Droidzone, I will have to try that also.
Sent from my HTC Pyramid using xda premium
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
casanova786 said:
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
Click to expand...
Click to collapse
Once you open a command line prompt in the folder where adb is installed (or anywhere else, if the file adb.exe is in your Windows path variable-Dont worry about that if you dont know), you can directly type each line of the commands starting from step 2.
Before that, install Notepad+, and associate .txt file to open with it by default..
By the way, you have to start typing those commands directly after rebooting from recovery after installing the Rom..
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.also i typed the commands u gave me once in adb and it says "the process cannot access the file because it is being used by another process."
casanova786 said:
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.
Click to expand...
Click to collapse
Hmm.. I seem to be offering more Windows support than Android!
I meant Notepad+. Hold Shift, rightclick any text file, Choose Open with Notepad+ as default. You can go to your adb folder like you normally do and then type each line I posted and hit Enter after each time. You can also make a batch file with all those commands (search Google for that if you dont know how)
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
casanova786 said:
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
Click to expand...
Click to collapse
Hmm yes, that can happen if you have more than one adb.exe process running in the background because you exited it by closing the command shell with the close button instead of typing
Code:
exit
after done with it.
Use Ctrl+Alt+Del or Process Explorer to terminate the background adb.exe processes
I have been having trouble trying to extract my htc desire(cm7.1) Proprietary Files. i am no expert on ubuntu and wanted to have a go at compiling a cyanogenmod rom.
My problem is i have adb to recognise my device but im having trouble to get the './extract-files.sh' command to work .
i have uses this guide to help me set up adb : http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
And following this guide to compile cyanogenmod: http://wiki.cyanogenmod.com/wiki/HTC_Desire_(GSM):_Compile_CyanogenMod_(Linux)
Heres a screenshot of the problem i get when i try to excute this command and try get extract the Proprietary Files.
Any tips or advice how to get this working ?
Hi!
i assume you didnt setup the path to adb in bashrc, as you use adb only in the folder where it is by ./adb... i think the script needs the adb path setup to run. i am not sure though
you could try resyncing the repo too.
Droidzone is right, how could i have missed that. maybe the path just doesnt exist. it exists only after the work tree is synced completely, and the repo is quite unstable. try again
Isn't it quite obvious that you have typed the path wrong? re check the path and type it correctly. You're still executing it from your adb directory. Don't just copy and paste commands. Think, and modify them according to the situation, and error messages.
Thanks guys for the help. Really appreciate it.
Sent from my HTC Desire using XDA App
rom puzzle freezes many times and after long waiting the only option left is to pull out the battery and restart the phone.
I have flashed this rom second time but again the same error.
pls help..
Would it be possible to post a logcat? (adb logcat > C:\Users\Example\Desktop\
Hi, I have the exact same problem.
I already tried to read logcat, but the system freezes before logging anything!
The only message in the log is:
Code:
logcat /system/xbin/busybox terminated by exit(0)
Thank you in advance for your help!
Folks, i really don't know what to do to get a specific problem log file to be sent/showed to someone to fix my problem, any help or suggestions will be really appreciated here
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /proc/kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Edit: /proc was missing 3 lines above
eyosen said:
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Hossam.Abdelsalam said:
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Click to expand...
Click to collapse
use "adb logcat -b radio"
Press the thanks button if you want to thank me
You are welcome.
Just send the whole log. Best practice is to post it to pastebin and post the link in the forum.
After every reboot you will lose the previous last_ksmg.
Sent from a gadget on my balcony.
wcypierre said:
use "adb logcat -b radio"
Press the thanks button if you want to thank me
Click to expand...
Click to collapse
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
No that's not possible. You can start a logcat, repeat the steps that caused the problem, after the problem , post logcat and kmsg.
Sent from a gadget on my balcony.
Hossam.Abdelsalam said:
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
Click to expand...
Click to collapse
well, it should be able to trace back if the time duration is not that long, but you can just try and do what eyosen had suggested