Stuck in ClockWork Recovery - Android Q&A, Help & Troubleshooting
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
Related
Starting adb ?!
Hi all! I was using Modaco 2.9 before and it was amazing stable. Later on I tryied [email protected] worked well, but not as stable as the modaco, so I thought lets change to the 3.0. Since that I have al lot system crashes, so I thought I need to do "deldalv and/or ext_wipe" with the RA-recovery-1.2.3 Figured out that it didnt work, it says I should use "adb deldalv" I couldnt get the adb to run on my ubuntu linux, so I tried to find an update for the RA-recovery. And there is RA-recovery-1.5.1 and I can just install it (cause I have a previous version) via adb. Now My Question: How does it work?!? Code: [email protected]:~$ adb usb error: insufficient permissions for device [email protected]:~$ adb devices List of devices attached ???????????? no permissions [email protected]:~$ adb kill-server [email protected]:~$ adb start-server * daemon not running. starting it now * * daemon started successfully * [email protected]:~$ adb usb error: insufficient permissions for device [email protected]:~$ adb devices List of devices attached ???????????? no permissions Code: [email protected]:~$ cat /etc/udev/rules.d/50-android.rules #Bus 001 Device 005: ID 0bb4:0c02 SUBSYSTEM=="usb", SYSFS(idVendor)=="0bb4",MODE="0666" How do I connect the device then, if not like that? How can I test if everything works? Thanks in advance
Unicate said: How do I connect the device then, if not like that? How can I test if everything works? Thanks in advance Click to expand... Click to collapse afaik this looks good, try starting adb as root. this is what adb devices says for me: Code: [email protected]:~$ adb devices List of devices attached HT98XXXX427 device
Code: ./adb start-server ./adb shell works for me (with root ofcourse )
I set up my system so that the adb deamon starts at boot. Created a script in the /etc/init.d directory called adb: Code: #! /bin/sh case "$1" in start) /home/joeblow/AndroidSDK/tools/adb start-server ;; stop) /home/joeblow/AndroidSDK/tools/adb kill-server ;; *) echo "Usage: $0 start|stop" >&2 exit 3 ;; esac Created a link to it in /etc/rc2.d: Code: lrwxrwxrwx 1 root root 13 2010-01-09 19:17 S10adb -> ../init.d/adb
Off Topic... Am sorry to be a little off topic.. I just got my Hero and was trying to figure out all the stuff about it here on XDA.. Can anybody tell me what is ADB ??.. Whats it used for ??.. As far as I have understood, I think its some sorta software to connect hero to the computer to transfer files and stuff.. Is it right ??.. If yes.. Then what is the difference between this and HTC SYNC ??.. Thanks in advance.. Cheers !!!
if You want only transfer files, You don't need ADB. htc sync is for synchronizing phone (contacts, calendar, etc) with PC (i guess, i don't use it ) and for upgrading SW.
device not available, only in adb shell
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!
error: only position independent executables (PIE) are supported. andriod 6.0
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
HELP: error: no devices/emulators found
I want to create a script that installs twrp recovery and then installs Magisk without doing any further actions on a Mac. Code: #!/bin/bash # filename run.command cd ~/platform-tools adb devices adb reboot bootloader fastboot devices fastboot flash recovery recovery-20181012.img fastboot boot recovery-20181012.img # adb wait-for-recovery # adb wait-for-device # adb kill-server && sudo adb start-server adb shell twrp install /sdcart1/Magisk-v19.0.zip adb shell twrp reboot After twrp has been installed and booted I get this message Code: error: no devices/emulators found If I make two files out of it then it works Code: #!/bin/bash # filename step1.command cd ~/platform-tools adb devices adb reboot bootloader fastboot devices fastboot flash recovery recovery-20181012.img fastboot boot recovery-20181012.img Code: #!/bin/bash # filename step2.command cd ~/platform-tools adb devices adb shell twrp install /sdcart1/Magisk-v19.0.zip adb shell twrp reboot What else can I do?
I found it Code: #!/bin/bash cd ~/platform-tools adb devices adb reboot bootloader fastboot devices fastboot flash recovery recovery-20181012.img fastboot boot recovery-20181012.img sleep 35 adb -d shell twrp install /sdcart1/Magisk-v19.0.zip adb -d shell twrp reboot
Can I recover my personal files (audio and photo) by usiing ADB?
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???