helloo greetings i have a problem with adb i want to connect with IDA pro but i got error
Code:
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\adb>adb shell
[email protected]:/ $ su
2|[email protected]:/ # cd data/tmp/files
[email protected]:/data/tmp/files # ls
android_server
armlinux_server
armuclinux_server
linux_server
linux_serverx64
[email protected]:/data/tmp/files # ./android_server
error: only position independent executables (PIE) are supported.
Thanks in advance sorry for bad english
Related
Hello, I'm using a debian wheezy, I don't manage to start adb
---> sudo ./adb start-server
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
There is nothing running on port 5037. I checked with netstat -a
Any idea ?
Thank you
Hi,
Today wanting to flash Cyanogen 11 to my Galaxy Nexus I completely messed everything.
I got into ClockWork Recovery mode before putting the cyanogen .zip file in the internal storage.
Now I'm stuck in the recovery mode and I can't get access to my internal storage from the terminal.
To give you what I've tried so far ... :
Code:
[[email protected] ~]$ adb kill-server
[[email protected] ~]$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[[email protected] ~]$ adb devices
List of devices attached
???????????? no permissions
[[email protected] ~]$ sudo adb devices
List of devices attached
???????????? no permissions
[[email protected] ~]$ adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[[email protected] ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[[email protected] ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[[email protected] ~]$ adb kill-server
[[email protected] ~]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[[email protected] ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: device offline
[[email protected] ~]$ sudo adb devices
List of devices attached
016B73781101A017 offline
Code:
[[email protected] ~]$ adb kill-server
[[email protected] ~]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[[email protected] ~]$ sudo adb devices
List of devices attached
016B73781101A017 recovery
[[email protected] ~]$ adb shell
~ # mount sdcard
mount: can't find sdcard in /etc/fstab
~ # mount /sdcard
mount: can't find /sdcard in /etc/fstab
~ # echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
/sbin/sh: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory
~ #
I'm becoming really desperate here, if anybody could just help pleeaaasse :'(
maybe this will work
My situation might be unique, but what I did allowed me to use a previous backup made in TWRP and I'm now able to reboot into the system again.
I was stuck in CWM and could not even get to FASTBOOT with the keypress combo. It would also not boot to system, so reboots just took me back to CWM. I was able to talk to the device with adb and reboot into the bootloader. From there I was able to flash a different recovery. (TWRP)
adb:
adb reboot-bootloader
fastboot flash recovery "openrecovery-twrp-2.6.3.3-m7.img"
heymanfromfrance said:
Hi,
Today wanting to flash Cyanogen 11 to my Galaxy Nexus I completely messed everything.
I got into ClockWork Recovery mode before putting the cyanogen .zip file in the internal storage.
Now I'm stuck in the recovery mode and I can't get access to my internal storage from the terminal.
To give you what I've tried so far ... :
Code:
[[email protected] ~]$ adb kill-server
[[email protected] ~]$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[[email protected] ~]$ adb devices
List of devices attached
???????????? no permissions
[[email protected] ~]$ sudo adb devices
List of devices attached
???????????? no permissions
[[email protected] ~]$ adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[[email protected] ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[[email protected] ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[[email protected] ~]$ adb kill-server
[[email protected] ~]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[[email protected] ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: device offline
[[email protected] ~]$ sudo adb devices
List of devices attached
016B73781101A017 offline
Code:
[[email protected] ~]$ adb kill-server
[[email protected] ~]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[[email protected] ~]$ sudo adb devices
List of devices attached
016B73781101A017 recovery
[[email protected] ~]$ adb shell
~ # mount sdcard
mount: can't find sdcard in /etc/fstab
~ # mount /sdcard
mount: can't find /sdcard in /etc/fstab
~ # echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
/sbin/sh: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory
~ #
I'm becoming really desperate here, if anybody could just help pleeaaasse :'(
Click to expand...
Click to collapse
C:\ADBTOOLS>adb devices
List of devices attached
da4d4717 device
C:\ADBTOOLS>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ #
my device connects to adb,
however as soon as I go into adb shell, the device is no longer found.
What is going on here?
mdelaney1986 said:
C:\ADBTOOLS>adb devices
List of devices attached
da4d4717 device
C:\ADBTOOLS>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ #
my device connects to adb,
however as soon as I go into adb shell, the device is no longer found.
What is going on here?
Click to expand...
Click to collapse
Of course that happens when you run adb shell you are entering in your phone using the debbuging shell. You are in your phone. This happens to me also when i am using adb shell no devices will be shown. If you can run any command from adb shell then your device is there. Nothing to worry about. It is normal.
If you disconnect your device when in adb shell you will see it will automatically exit the shell!
Hit Thanks if i helped you!
Hello,
I cannot configure my SD-card for extra memory.
This is what I see:
* daemon not running; starting now at tcp:5037
* daemon started successfully
[email protected]:/ $ adb devices
List of devices attached
[email protected]:/ $ sm list-disks
/system/bin/sh: sm: not found
Can anyone tell me what to do?
PS: device is not rooted, is that necesarry?
Details of my phone:
Samsung Galaxy Grand Prime model SM-G531H
Android 5.1.1.
Thanks!
did you get a fix ???
Hello,
my phone (I think it is not rooted because adb shows the dollar character) is stuck into the recovery for an unknown reason. Is there a way to access the phone folders through ADB / shell commands?
I'm a newbie and I tried to do by myself but unfortunately I cannot reach my objective.
for example, I (think) I successfully reached the sdcard (is this the android folder name where all the personal data si saved?) but when I try the command adb pull -p It doesn't work. Here what it happens:
1|[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ adb pull -p
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/sdcard $
Any Idea? Thanks
Howl55 said:
Hello,
my phone (i think it is not rooted because adb shows the dollar character) is stuck into the recovery for an unknown reason. Is there a way to access to phone folders through ADB / shell commands?
I'm a neewbie and I tried to do by myself. Unfortunately I cannot reach my objective.
for example, I (think) I successfully reached the sdcard (is this the android folder name where all the personal data si saved?)
but when I try the command adb pull -p It doesn't work. Here what it happens:
1|[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ adb pull -p
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/sdcard $
Any Idea? Thanks
Click to expand...
Click to collapse
Is there someone who could help me???