Is there any way to do with the ADB, which file is using or scanning the mediaserver process?
I tried a logcat without result, the same goes with a bugreport.
Does anyone know?
Related
I'm attempting to get webtop from HDMI to work and attempted the install.bat thing but still nothing so I went to
http://forum.xda-developers.com/showpost.php?p=12580345&postcount=634
I can push those files but can not SU in adb shell
I am able to SU in terminal on my phone but not the adb shell
What can I do to get this working? I'm not sure what info you need from my phone to better assist but ask.
I'm running 2.2.2 rooted with gingerbreak I tried to reroot but no go don't think i need too and superuser app is there and works since i use TB and bloat freeze
I just get permission denied thanks for any help. I have googled this but can't find anything.
could you maybe have a problem with ADB itself? Maybe try reinstalling your SDK and setting up ADB again? You said you already tried to re-root and that didnt fix the issue. Maybe someone with more knowledge of ADB could provide more assistance...
I managed to get it working. I noticed when I had my screen set to not turn off i received a message to all access and I granted SU now it works fine.
I'm having some problems with adb recently and adb.exe keeps crashing. The strange thing is, something immediately restarts adb.exe. I looked through the services and couldn't find anything Android related.
Does anyone know how adb.exe keeps restarting after the process got killed?
This is on Windows 7.
Is logcat using it? Logcat will auto start adb if it's killed.
So the phone is able to start adb.exe on the PC? That would happen through the driver then?
edit: Nevermind, I forgot I had Eclipse running and the Android Plugin restarts adb whenever it's killed...
Can anyone confirm that it's actually the phone's driver that's retarting adb? I don't think I have logcat running on the phone though.
bur2000 said:
edit: Nevermind, I forgot I had Eclipse running and the Android Plugin restarts adb whenever it's killed...
Can anyone confirm that it's actually the phone's driver that's retarting adb? I don't think I have logcat running on the phone though.
Click to expand...
Click to collapse
The phone driver won't start ADB, it's only used for connecting to the phone in adb.
have you installed droidexplorer or myphonexplorer?
my problem was droidexplorer, after i uninstalled and delete it, adb.exe was killed and dont restart anymore
Droid Explorer kept adb.exe restarting
ignos said:
have you installed droidexplorer or myphonexplorer?
my problem was droidexplorer, after i uninstalled and delete it, adb.exe was killed and dont restart anymore
Click to expand...
Click to collapse
Thanks @bur2000 for posing the question, and thanks @ignos for posting my answer.
I got the same issue. Look if the process doesn't start at boot (with CCleaner for exemple) and loop kill it with a batch, it will finally stop I think.
Code:
c:\logcat>adb logcat > logcat.txt
- waiting for device -
error: protocol fault (no status)
- waiting for device -
c:\logcat>
what does that suppose to mean? i need logcat for my miui port and i get this message.
the logcat.txt is saved in logcat folder
butr the file is blank.
Do adb devices and see if it can actually see your phone.
Sent from my HTC6435LVW using xda app-developers app
no it doesnt not while booting. does how ever see phone in recovery fastboot and adb sideload strange
well nevermind i lost all adb functions im dead in the water.
wheres that adb.ro.sercure=0 maybe thats the issue
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
Hi all,
Is it possible to grab a logcat from when I segfault in the kernel? I'm connected over gdb to my remote target, but I can't connect to adb since I'm segfaulting. Is it possible to do through gdb to get the logcat ring buffers or something?
Thanks