Stuck in ClockWork Recovery

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:

[fmonfort@localhost ~]$ adb kill-server
[fmonfort@localhost ~]$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[fmonfort@localhost ~]$ adb devices
List of devices attached 
????????????	no permissions

[fmonfort@localhost ~]$ sudo adb devices
List of devices attached 
????????????	no permissions

[fmonfort@localhost ~]$ adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[fmonfort@localhost ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[fmonfort@localhost ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: insufficient permissions for device
[fmonfort@localhost ~]$ adb kill-server
[fmonfort@localhost ~]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[fmonfort@localhost ~]$ sudo adb push /home/fmonfort/Downloads/cm-11-20140104-SNAPSHOT-M2-maguro.zip /sdcard/
error: device offline
[fmonfort@localhost ~]$ sudo adb devices
List of devices attached 
016B73781101A017	offline

Code:

[fmonfort@localhost ~]$ adb kill-server
[fmonfort@localhost ~]$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[fmonfort@localhost ~]$ sudo adb devices
List of devices attached 
016B73781101A017	recovery

[fmonfort@localhost ~]$ 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