Hello!
What am I doing wrong?
1. Write "adb logcat".
2. It says "-waiting for device-".
3. I turn on my device.
4. After it have boot-looped like 2 times (this is the error im trying to fix), I press CTRL-C.
And there is no log?
I have also tried "adb logcat > logcat.txt but the logcat.txt is empty. :S
Please help!
"Solved!" .
Related
I was woken up last night at 3:30am this morning to the sound of my phone rebooting itself.
Is there anyway to determine why it rebooted? I've never seen it do it before on its own! I'm running CM6 rom.
"adb logcat" would probably do it.
open your command prompt, navigate to your c:\android-sdk-windows\tools folder and run the following command
Code:
adb remount
adb logcat
and it should return a bunch of stuff to you. scrolling through this log will probably show you some kind of error, failure, termination, etc. at some point.
So i am modding my own widgetlocker for the first time and would like to push it back into my device.
See screenshot first.
and i am using clockworkmod recovery 2.5.0.1.
Problem, as you can see, i think i've successfully push it right? but when i reboot why i still cant see the app?
and for adb shell, when i entered that, yes it passed, then when i entered "su" , it says not found. why is it?
i tried installing but got the error as you see in screens.
adb remount, failed? why?
You are using adb wrong!
For pushing you have to use this template:
"adb push *file* *directory*"
e.g.: (without quotes)
"adb push com.teslacoilsw.widgetlocker-1.apk system/app/"
not:
"adb push com.teslacoilsw.widgetlocker-1.apk /system/app/com.teslacoilsw.widgetlocker-1.apk"
Also make sure, that your SDK is installed correctly, because you used "adb install" correctly, but it gives you an error.
I hope it can help you, had got the same issues..
Hi mate, thanks for the reply. I got it working just before you posted.
this is what i did.
1) adb remount (i did it first and it succeeded! yay!)
2) adb push (still using the same template as i did)
but still very much thanks for replying. will keep your info in mind!
yay my first adb!
cool that you figured it out!
I am sure this has been asked and answered, but I am not finding the answer. Anyone have a good method for backing up CWM backups to MAC? I know the CWM backups are stored at /data/media/clockworkmod which is not accessible to the MAC. I guess I could copy them to /data/media/0 and then access them from my mac. I guess I could also use ADB, but am looking for something simpler and less data manipulation. If this has been answered, please link me.
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Pirateghost said:
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Click to expand...
Click to collapse
I have done it with ADB. Was hoping for something more elegant. Thank you.
Sent from my Nexus 7 using xda app-developers app
Pirateghost said:
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Click to expand...
Click to collapse
Could you please write it in a more specific way? I'm a noob
I explain what I did:
I opened the terminal and I went in the folder were I keep the fastboot and adb etc..
I tried first with "./adb pull.." but nothing happened (aka: -bash: ./adb: No such file or directory)
Then I tried "./adb-mac pull.." and it didn't work either but I got the following long message:
"Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
etc..."
I tried both commands at first with the mobile on, then I reset it and I went in recovery mode with the same results..
I'm going insane, I even tried to copy the whole folder of clockworkmod with my backup to another folder, but I couldn't see it with my computer.
I'm running mac OS X, I could eventually try also to my PC windows 7.. I just need to copy my backup to a safe place :crying:
After the pull command you need to tell it what to pull
Sent from my Galaxy Nexus
Pirateghost said:
After the pull command you need to tell it what to pull
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry Pirateghost, I meant that I wrote as you said:
./adb-mac pull /data/media{0, clockworkmod, twrp}
and I got just the long message from the Terminal and it doesn't work (even when using ./adb without the "-mac")
edit: ok I solved it:
I used this and it seems working (finally)
./adb-mac pull /data/media clockworkmod
ziovelvet said:
Sorry Pirateghost, I meant that I wrote as you said:
./adb-mac pull /data/media{0, clockworkmod, twrp}
and I got just the long message from the Terminal and it doesn't work (even when using ./adb without the "-mac")
edit: ok I solved it:
I used this and it seems working (finally)
./adb-mac pull /data/media clockworkmod
Click to expand...
Click to collapse
the {0, clockworkmod, twrp} was to indicate that you can pull ONE of those folders at a time, or pull /data/media and get ALL of them at once
I tried to change from the rom CW11 to Pardous and the phone stuck at the LG symbol and don't coming up. Everything deleted and even the custom roms, Debugging desable, the root deleted and just TWRP stayed, the backups deleted and the roms installers too.
I tried the adb but when I am doing "adb sideload" it's doing "Error:closed" and when I amd doing "adb push" its telling "can't read".
So my question is if there is any way to fix it? if yes how? (If I can get guide please).
I tried and thing in the internet so if you can help me in anyway I will be glad.
Thanks.
If Someone can help I am lost. The phone not working for 3 days.
adb push rom.zip /sdcard/rom.zip
then install(no need to activate adb sideload)
bender_007 said:
adb push rom.zip /sdcard/rom.zip
then install(no need to activate adb sideload)
Click to expand...
Click to collapse
Its telling "Cannot stat romname.zip : no such a file or directory"
What to do?
Provide the full path or use adb pusher from my sig
Sent from my LG-D802 using XDA Premium 4 mobile app
Hi,
I've just set up a new handset.
Since changes ive made over night im getting;
- unfortunately, 'app name' has stopped.
I'm trying to generate a logcat, having no joy.
- handset; SGSV
- rom; XTRESTROLITE
- kernel; blaze
I have turned logging on via 'pimp my rom' tweaks.
Upon adb logcat command i get;
- Unable to open log device '/dev/log/main': No such file or directory
So i set about tying to manually ensure logcat is enabled.
First with ADB;
> adb shell
> logcat-enable
Result;
C:\android-sdk\platform-tools>adb shell
[email protected]:/ $ logcat-enable
logcat-enable
/system/bin/sh: logcat-enable: not found
Then via USSD code;
> *#*#2846579#*#*
Result;
Number dialled, no code.
Then i attempted to follow as per these instructions;
http://bitmote.com/index.php?post/2013/02/19/Enabling-Logcat-in-Custom-Android-Roms
I found system set to ro, remounted rw ok.
But ran into a dead end here;
"First you need to locate the logger kernel module...
logger.ko located in...your /system folder...
Try these locations:
/system/lib/modules/logger.ko
/system/modules/logger.ko"
The folder "modules" does not exist in system or lib/system.
Help would be much appreciated.
Cheers.