Alright guys, I was on an irc channel when I considered posting this since it's rather important. There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat
This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right.
How to get a dmesg:
This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
I'm glad to have written this and devs, feel free to link to this guide as a "bug reporting FAQ"
HALP! I BRICKD MY FONE!!1!
I JAILBROKED IT LAST NIGHT AND NOW I NO GET SIGNEL!! PLASE HALP!!!1
but on a more serious note, good tut
Thanks dude!!! I was looking for some kind of guide. Only thing I still don't understand is when are we supposed to give dmesg and when do we give the logcat? I understand the last_kmsg is for kernel panics and random reboots, but the rest two are still ambiguous to me... Could you please explain the other two in a simpler way with an easy example for each?... Sorry.. I'm a noob... but am trying to learn these things..
There also is this app called 'Bootlog Uptime' that tries to auto-detect a crash and subsequently exports the log to sdcard.
When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?
If you're in boot loader mode, that's not adb.
Sent from my Full Android on Crespo4G using xda premium
anshumandash said:
When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?
Click to expand...
Click to collapse
You need to boot into the ROM, then grab the logs.
Sent from my GT-I9100 using xda app-developers app
Thank you for this
Sent from my Nexus 4 using Xparent BlueTapatalk 2
Can someone help me please.
I am from the HTC One S (Ville C2) community. I am testing a new kernel by one of the devs who doesnt have the phone. Now after installing the new kernel the phone is on bootloop. I need to extract the last_kmsg. the only way I can get out of the boot loop to do anything is by pressing the power button and simulate battery out. This it seems erases the last_kmsg cuz when I enter recovery to get it. It either says no such file or sometimes ends up showing me the recovery kernels last_kmsg. I am at a total loss as to how I the last_kmsg file.
There is also no way to install a working boot image as the kernel uses a zip to install files on the phone so we must use recovery to restore to previous state. This leads to the original condition. I tried looking for a solution but cant find it anywhere.
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
piyush_soni said:
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
Click to expand...
Click to collapse
I have the same problem.
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
Just solved the last kmsg problem. Instead of making the terminal do the job and getting "there is no such directory", just go above one level from sdcard and find proc folder. There will be a file named last_kmsg.
Hope it helps someone
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
---------- Post added at 10:13 AM ---------- Previous post was at 10:08 AM ----------
piyush_soni said:
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
Click to expand...
Click to collapse
Wait a few minutes it will be there
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
Kaiyes said:
Just solved the last kmsg problem. Instead of making the terminal do the job and getting "there is no such directory", just go above one level from sdcard and find proc folder. There will be a file named last_kmsg.
Click to expand...
Click to collapse
Kaiyes said:
Wait a few minutes it will be there
Click to expand...
Click to collapse
Nope. It's still not there for me ... I have a file called kmsg, but not last_kmsg.
Good stuff!
I'm on JB 4.3, Galaxy Note 2 and I've Flash Davil Kernel.
Two Bugs for me:
1) when the Phone, in switch off, is charging... the LED will not light. No Red Light (when in charging), nor Green one, when it has reached the 100%.
2) When Phone is connect to PC it isn't recognized by the PC in any way. To transfer files I have to use some app via Wi-Fi.
Are Two knows Bugs? Thanks in advance.
Hey glowerita I have this same problem minus the devil kernel. I don't think devil works with the FTW rom
Sent from my SPH-L900 using Tapatalk
Aquarius169 said:
Hey glowerita I have this same problem minus the devil kernel. I don't think devil works with the FTW rom
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Hi! About PC recognize I've done so and now it's ok.
With Terminal emulator digit;
su
Press Enter.
Now digit; setprop persist.sys.usb.config mtp,adb
Enter, exit and reboot device and PC. [emoji1]
About led light... have you same problem like me?
Inviato dal mio GT-I9100 utilizzando Tapatalk
Take a look at
https://play.google.com/store/apps/details?id=com.bassel.andylog
... [email protected]
dmesg kmsg not permitted
Here's the dmesg.txt file when issuing C:\platform-tools>adb shell dmesg > dmesg.txt
"klogctl: Operation not permitted"
So I tried:
"C:\platform-tools>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # dmesg > dmesg.txt
dmesg > dmesg.txt
sh: can't create dmesg.txt: Read-only file system"
Results of issuing "C:\platform-tools>cat /proc/last_kmsg > /sdcard/last_kmsg.txt
The system cannot find the path specified.
C:\platform-tools>adb shell cat /proc/last_kmsg > kmsg.txt
/system/bin/sh: cat: /proc/last_kmsg: Operation not permitted"
Same results running terminal on phone also.
-Running PecanCM's CM11 Beta10 on LG L5 e610-
So neat and simple. Thanks for clarifying that.
Related
First off I want to thank everyone for the hard work that has been put into making the NC such an awesome little toy.
I successfully installed the Phiremod / Honeycomb dual boot via this thread (http://forum.xda-developers.com/show....php?t=1045018) I thought everything was working great until I decided to install Cool Reader from the market. No luck, it won't let me install...so after reading some posts I installed the .apk via adb (along with zinio, which is working perfect). However when i try to open Cool Reader it automatically closes, almost before it opens. Not sure how to get a "log" but any and all help is appreciated.
Got a cruise coming up and would like to have it for some girl watching....err "reading" by the pool.
**Edit: I have tried with a few different versions of Cool Reader including the one that works with CM7 as well the one that installed successfully on the HC boot.
Anyone, someone has to have an idea or at least something to try...
You can get a log by running "adb logcat > log.txt" without quotes, but you'll want to kill it (press ctrl-c) right after you've reproduced the bug as the log will get large very quickly.
C0deMaver1ck said:
You can get a log by running "adb logcat > log.txt" without quotes, but you'll want to kill it (press ctrl-c) right after you've reproduced the bug as the log will get large very quickly.
Click to expand...
Click to collapse
Thanks, I will give it a try when I get off work and to make sure I'll be doing this right..
cd\
cd android-sdk-windows\platform-tools
adb kill-server
adb devices
adb logcat > log.txt
>>try to open cool reader<<
Control C after crash.
I'll do some more reading on this as well but does it make a file or just dump it to the cmd box for me to copy and past?
correct, and it will write it to the file log.txt whereas without the "> log.txt" part it would just output to the terminal.
I learned something new today...go me
Here is the log file
http://pastebin.com/j630JWXB
The problem is near the end where it can't find a required library.
Code:
E/AndroidRuntime( 2393): java.lang.UnsatisfiedLinkError: Couldn't load cr3engine-45-15: findLibrary returned null
Now how to fix it is another issue
This root was rendered unusable at this time due to AT&T disabling the Ready2Go app installation feature. Working on a work around now.
Original content:
http://www.androidpolice.com/2012/0...the-att-htc-one-x-on-version-1-85-or-earlier/
Hope you get your One X soon dude!
Confirmation number: 8PH11891CA483914J
In! Thanks Justin!
Billy
Damn, thanks a lot!
jcase said:
Now comes the timing critical part, you have to use ATT Ready2Go to Download "AT&T Mark the Spot", and interrupt the install process right after the download has finished. Easiest way is to reboot the device, but we have found other ways to do it.
Click to expand...
Click to collapse
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
jcase said:
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
Click to expand...
Click to collapse
Hah, well now I just feel dumb as I am on try 10 or so. I must not be able to hit the timing right at all. I'll keep at it, as I am constant as the northern star.
Don't feel dumb, it is very timing critical, with few real indicators of when to pull it off.
Maybe xfinrodx or designgears can chime in on this one
noobsquared said:
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
Click to expand...
Click to collapse
Turn your ringer off, it will silence the startup sound. At least I can help with that!
id10terrordfw said:
Turn your ringer off, it will silence the startup sound. At least I can help with that!
Click to expand...
Click to collapse
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
I have been deleting the file from data/install
adb shell
cd data/install
rm com.att.android.markthespot.apk
exit
then repeat the process...i'm in double digits on attempts...going to have to walk away from it for a bit.
going on 10x for me and still nothing. Any suggestions?
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
noobsquared said:
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
Click to expand...
Click to collapse
Um, why are you doing a factory reset?
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
I will give that a shot, and I should have thought of that. Thanks!
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Good advice, was the first person to test it for me. I confirmed it with 4 users before posting, and all got it eventually.
id10terrordfw said:
I will give that a shot, and I should have thought of that. Thanks!
Click to expand...
Click to collapse
I was the first one I'm aware of who used this exploit a couple weeks ago. I won't claim that the process is clean, but it should work for you if you do it the way I intended the instructions to read... Good luck!
Thanks for all the help but I think this red bull is not working today.
Here is what I did:
First CMD:
Code:
adb shell
cd /data/install
ls -l <- it only gives me the file name..it doesn't tell me the size.
Also, I delete the file and run the first command in second CMD and right after that I see this in ls -l:
[email protected]:/data/install $ ls -l
ls -l
lrwxrwxrwx shell shell 2012-05-25 12:16 com.att.android.markthesp
ot.apk -> /data/local.prop
Second CMD:
Execute:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
Wait to execute:
Code:
adb reboot
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $4}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
dharani1234 said:
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $5}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
Click to expand...
Click to collapse
If you can get a working script, that was reliable I would love to post it in the OP. To get an idea of the size, you could install the app, and do adb shell ls -l /data/app/<filename>
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?
I know there are a few threads seemingly related but please bare with me. There's nothing wrong with my rom at all. I'm looking for a way to mount my sdcard as a usb disk on the computer to play with the files. Because JB 4.2 only allows mtp, this can't be done anymore. I figured if I mounted the sdcard in twrp, I should be ok. However, the button is unclickable. The reason I want to play with it is because I've flashed CM10 a couple of times and each time, it has moved all of my files into a subfolder called zero as per this page. I can't seem to get TiBu to properly restore because of this so I wanted to move them all back to the root folder as they should be and it would be fine because I did it before I switched to 4.2. So, any ideas as to why I can't click it?
Edit. Im using twrp 2.3.1.1
You can do the same thing from terminal.
Code:
su
cd /data/media/0/0
mv * ../
cd ../
rm -rf 0
No idea why you can't click the button though.
You can do the same thing from terminal.
Click to expand...
Click to collapse
Wow I never thought of that. It failed though because a directory wasn't empty.
It probably failed because there was a directory with the same name when you moved it.
I guess to be sure you could do something like...
Code:
su
cd /data/media/0/0
cp -R * ../
cd ../
rm -rf 0
but before you rm -rf make sure the CP worked. I know android commands sometimes don't have the normal options that linux commands do, so the "cp -R" part may not have worked.
Worst case, you can "adb pull" the files to your computer, remove everything then adb push them back.
Lethe6 said:
It probably failed because there was a directory with the same name when you moved it.
I guess to be sure you could do something like...
Code:
su
cd /data/media/0/0
cp -R * ../
cd ../
rm -rf 0
but before you rm -rf make sure the CP worked. I know android commands sometimes don't have the normal options that linux commands do, so the "cp -R" part may not have worked.
Worst case, you can "adb pull" the files to your computer, remove everything then adb push them back.
Click to expand...
Click to collapse
I'll give it a shot. I wish I could just use my computer dammit.
Edit. Still fails with that original error.
Edit 2: I tried using adb and it fails too. Says adb is in "/usr/bin" but not thats not included in $PATH environment variable.
adb will only be in $PATH if you added it, otherwise you need to manually run the full path or from the directory.
Something like:
adb pull /data/media/0/0 .
Then with adb shell you can cd to that directory:
adb shell
cd /data/media/0/
and remove 0
rm -rf 0
I thought i had gone into the adb folder and just ran ./adb pull yada yada. Im off to work now so ill have to try again laterm
Sent from my HTC One XL using Tapatalk 2
If you did I'm wondering what the $PATH issue is then? On the device itself, cp and rm will be in $PATH unless maybe you forgot to su?
I'm not entirely sure. I was using my laptop to run the adb command. Or am I doing it wrong? I could've forgotten. Anyway this thing's really got me confused. This morning I flashed back to JB 4.1.2 to see if I could fix it using usb. Well I rebooted to recovery to flash gapps and another kernel but I couldn't find the files on my sdcard anywhere. So I tried to reboot and it wouldn't get past the CyanogenMod loading screen (their logo). I've flashed JB 4.2 again and got it back up. This thing is really freaking confusing. I'm gonna try to flash back once again and see what happens.
Edit: Apparently I was wrong in thinking that 4.1 still had the ability to use USM
Using your laptop for adb was correct. It happened to me a few times until I got TWRP installed that I had to flash a couple of times for things to work properly, not sure why but I've seen other people report the same here. Once it was installed most the issues went away.
So I've got 4.1.2 back on it and still can't get USM to work. I thought it was removed in 4.2? I'm using the same rom I had used back in December which can be found here
Ok so yes, I had forgotten to run as root on my laptop. It tells me that it can't find the device though.
Edit: Updating the SDK, making sure I have everything I need.
Edit 2: Ok I've updated the SDK but it's still not detecting the tablet. When I run adb devices, it comes up blank. I set the rules using this page. I'm wondering is this something like having to run modprobe or maybe a reboot to initialize it?
Edit 3: I forgot to enable debugging. Now it says the remote file does not exist.
Kreuger said:
I know there are a few threads seemingly related but please bare with me. There's nothing wrong with my rom at all. I'm looking for a way to mount my sdcard as a usb disk on the computer to play with the files. Because JB 4.2 only allows mtp, this can't be done anymore. I figured if I mounted the sdcard in twrp, I should be ok. However, the button is unclickable. The reason I want to play with it is because I've flashed CM10 a couple of times and each time, it has moved all of my files into a subfolder called zero as per this page. I can't seem to get TiBu to properly restore because of this so I wanted to move them all back to the root folder as they should be and it would be fine because I did it before I switched to 4.2. So, any ideas as to why I can't click it?
Edit. Im using twrp 2.3.1.1
Click to expand...
Click to collapse
You need to update to twrp 2.3.2.3 for proper flashing of 4.2 roms. If you don't you will get the nested 0/0/0 directory copies each time you flash.
Sent from my SGH-I997 using xda premium
I have updated now. Ive gone back to ics to correct it. I may just stick with it to keep ums support.
Sent from my HTC One XL using Tapatalk 2
I did a superwipe and installed cm10 but i have no sound.
Sent from my Transformer using Tapatalk 2
Got the "insufficient storage" bug for the Google Play Store? Then you're in the right place!
First of all, a couple disclaimers:
This is not a magic cure-all! If you have less than 1 MB, nothing is going to help you. Sorry, it's not us and we can't do anything about it. The Android OS requires a small reserve for data and updates.
We are not responsible for any damages, loss of data, etc. incurred from misuse, failure, or any other unexpected cause.
Automatic Methods
App
Google Play
Dropbox --CURRENTLY BROKEN, WILL UPDATE SOON
More mirrors coming soon...
Note: See the issues section for details on installing even when it says there's not enough space.
Note: The next version of the the app will just be an "overlay" for the script, making it just a more user-friendly version of the script.
Using the app is pretty self-explanatory. You open it and choose a fix.
Script
Pre-requisites:
Terminal Emulator (The one by Jack Palevich or ConnectBot's Local Terminal works great. Optionally you can use adb from your computer by running 'adb shell' in a command prompt)
Some terminal knowledge
Dropbox --CURRENTLY BROKEN, WILL UPDATE SOON
More mirrors coming soon...
You can get a list of fixes and their descriptions by running 'bash fms.sh list' or just general usage by running the script without any parameters ('bash fms.sh').
Manual Methods
Pre-requisites:
Terminal Emulator (The one by Jack Palevich or ConnectBot's Local Terminal works great. Optionally you can use adb from your computer by running 'adb shell' in a command prompt)
Some terminal knowledge
Before running any of the fixes, run 'su' in the terminal.
Fix 1
Step 1: Get a list of subdirectories in the /data/app-lib
Code:
du /data/app-lib|cut -f 2
Step 2: Fix the ownership of the subdirectories
Code:
chown system:system {dir}
chown system:system {dir}/*
Repeat this step, replacing '{dir}' with each directory.
Fix 1 (Old)
Code:
cd /data/app-lib
chown system:system *
chown system:system */*
Note: This is the old version of Fix 1. It may be easier, but it's less thorough. It will most likely be enough though.
Fix 2
Code:
chmod -R 755 /data/app-lib
chmod 771 /data/app-lib
Issues
1. App failed to install!
Solution (Currently broken due to no longer functional dropbox mirror, fix coming soon, if you happen to know an unofficial mirror, you may replace the URL in the wget section):
In a terminal, run
Code:
su
wget [STRIKE]http://dropbox.com/s/wcgrk0qxvg7hhcx/FixMeStorage.apk -O /data/app/com.TWP.Project.Fixes.FS.IS-1.apk[/STRIKE]
Then reboot your device.
2. None of them worked!
We'll try to help you fix it, but we need you to contact us.
3. It said I don't have root!
Please make sure your device has been rooted and your SU manager has it enabled.
Please make sure you granted the app root access.
If everything is good there, then contact us and we will try to help you.
Contact Us
Send an email.
Send a PM to zenforic or wolfgentleman here on XDA.
Post a reply on this thread. (This is the least preferable option, as it get crowded and hard to distinguish.)
Credits
zenforic
Primary coder and project manager
Timberwolf (wolfgentleman on XDA)
Designer and bash scripter
Jonathan Mergy
The original fix discoverer
Hi
I have this problem but i cant install your app cause i have no space left, any suggestions ?
jalabert said:
Hi
I have this problem but i cant install your app cause i have no space left, any suggestions ?
Click to expand...
Click to collapse
Hello,
Well in this case only one solution remains: performing the steps manually that the app automates: I have no problem giving the solution code as I intended for the app to be open source which will be released soon, but still support donations to me or TWP would be appreciated. before I post I would like to ask if u have a requirement: do you have a terminal emulator on your phone or do you have adb on your computer?
EDIT: I will be posting on main post the manual steps.
Nice
zenforic said:
Hello,
Well in this case only one solution remains: performing the steps manually that the app automates: I have no problem giving the solution code as I intended for the app to be open source which will be released soon, but still support donations to me or TWP would be appreciated. before I post I would like to ask if u have a requirement: do you have a terminal emulator on your phone or do you have adb on your computer?
EDIT: I will be posting on main post the manual steps.
Click to expand...
Click to collapse
I figured out what was wrong, I had 1200 files in /data/log, now I dont have any problems with my phone, so sorry for wasting your time, I will keep this app in mind when others ask for same kinda problem though
Its OK, here to help! And thanks for keeping it in mind!
Thx works fine
alonsoe said:
Thx works fine
Click to expand...
Click to collapse
Glad it helped!
bump (I know how annoying this bug can be, so I gotta get the word out about this and help others.)
This worked for my tablet, thank you for this app... 5 star! by far!
Jack 147 said:
This worked for my tablet, thank you for this app... 5 star! by far!
Click to expand...
Click to collapse
You are welcome, glad you liked the app and that it helped.
729
Thanks, very nice.
Can we have this stickied?
Can we get a mod to sticky this?
Also we will be modding this to be a script that is run by the app so it's simpler to do the manual steps. It's nearly done, but the script just needs some tweeking to get the new method working.
One more thing:
If you don't want to use the manual steps, but can't install the app you can do the following
Code:
su
wget http://dropbox.com/s/wcgrk0qxvg7hhcx/FixMeStorage.apk -O /data/app/com.TWP.Project.Fixes.FS.IS-1.apk
then reboot your device.
wolfgentleman said:
Can we get a mod to sticky this?
Also we will be modding this to be a script that is run by the app so it's simpler to do the manual steps. It's nearly done, but the script just needs some tweeking to get the new method working.
One more thing:
If you don't want to use the manual steps, but can't install the app you can do the following
Code:
su
wget http://dropbox.com/s/wcgrk0qxvg7hhcx/FixMeStorage.apk -O /data/app/com.TWP.Project.Fixes.FS.IS-1.apk
then reboot your device.
Click to expand...
Click to collapse
Thanks for posting that, wolfgentleman! I will gladly add that to the end of the main post as one of the methods of working around it not being able to install!
Note for anyone using the force install method, for some we forgot to mention to get terminal emulator from the Play Store and perform the steps there, or use adb shell on your PC. (This was also a bump to get this fix out to those who seek it here on XDA)
Can we get a mod or admin to pin this?
Just a bump to keep it up top while it's not pinned...
Sent from Tapatalk
Sticky/Pin?
Can we get this stickied/pinned?
P.S.: As I look back at the first post, I realize it does need some work. There's a lot of unnecessary bloat and such to the post. I will have him rewrite it in the when I get up out of bed.
Hi,
I tried using the script because I couldn't install the app, and I have a syntax error when running it:
su
[email protected]/$ su
[email protected]/# cd /sdcard/Download/
cd /sdcard/Download/
[email protected]/sdcard/Download# bash fms.sh list
bash fms.sh list
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Success
fms.sh: line 6: syntax error near unexpected token `;;'
fms.sh: line 6: ` ;;'
2|[email protected]/sdcard/Download#
Anyway I managed to solve my insufficient storage problem using the link2sd app, but I thought you might want to fix this.
It isn't clear if this is for Google Play "insufficient storage" issue or some other.
Vyacheslav V. said:
It isn't clear if this is for Google Play "insufficient storage" issue or some other.
Click to expand...
Click to collapse
Thanks I'll clear that up!