HTC Desire S :/ ClockworkMod Recovery (Status 1)Support


Last Updated:

  1. dweebdogg

    dweebdogg New Member

    Hello,

    I'm having a problem with restoring my phone to life.
    Since yesterday he stays in the white htc screen when power on.
    I read many topics about that situation but non of them really solved it for me.

    I have the phone S-OFF and rooted with Revolutionar.
    SAGA PVT SHIP S-OFF RL
    HBOOT-6.98.1002
    RADIO-3805.06.02.03_M
    eMMC-boot
    Mar 10 2011, 14:58:38


    I want to install CyanogenMod 7 for the HTC Desire S :: V7.1.0
    So i press volume down / power into the -Revolutionary- screen.
    Then RECOVERY, the phone then reboots in to clockworkmod recovery 5.0.2.0
    I get the folowing messages:

    E: Can't open /cache/recovery/log
    E: Can't open /cache/recovery/log
    E: Can't open /cache/recovery/last_log
    E: Can't open /cache/recovery/last_log

    I ignore the messenges en choose to wipe cache.
    I takes a long time and then i get a message:

    Cache wipe complete.
    E: Can't mount /case/recovery/log
    E: Can't open /case/recovery/log
    E: Can't mount /case/recovery/last_log
    E: Can't open /case/recovery/last_log

    Now i choose to wipe data/factory reset.
    Again i takes awile and then i get a message:

    --Wiping data..
    Formating /data..
    Formating / cache..
    Formating / sd-ext..
    Formating / sdcard/.android_secure
    Data whipe complete.
    E: Can't mount /cache/recovery/log
    E: Can't open /cache/recovery/log
    E: Can't mount /cache/recovery/last_log
    E: Can't open /cache/recovery/last_log

    Now i choose advanced to wipe Dalvik Cache.
    I don't get any message after this.
    Now i choose to reboot recovery.
    The phone reboots.
    Now i choose to Wipe Data/Factory Reset once more.
    Again the same messages as before - Data wipe complete.

    I think the phone is empty by now.
    So i choose instal zip from sdcard - choose zip from sd card.
    i choose update-cm-7.1.0-DesireS-signed.zip
    Confirm install - Yes install update-cm-7.1.0-DesireS-signed.zip
    I get the message:
    Finding update package...
    opening update package...
    Installing update...
    E:Error in /sdcard/update-cm-7.1.0-DesireS-signed.zip
    (Status 1)
    Instalation aborted.

    I get this message all the time even with diverent mods.
    What does this meen? Please help me out of this mess.

    Advertisement
  2. notebook

    notebook Well-Known Member

    Are you using a PC or Mac?

    The zip file may be corrupted.
  3. dweebdogg

    dweebdogg New Member

    I am using a windows 7 pc.
    I also tried other zip versions of CyanogenMod 7 but non of them work.
  4. notebook

    notebook Well-Known Member

    Ensure you're using the latest version of ROM Manager, then 'flash ClockworkMod Recovery' from the menu.

    Try rebooting into ClockworkMod Recovery and installing the zip from the SD card. Avoid doing any of the 'advanced' wiping/formatting of data and cache.

    Have you had any success with flashing a ROM on your phone with Clockwork Mod Recovery?

    You could also try downloading and installing the zip from another SD card, in case there is a problem with the SD card itself.
  5. dweebdogg

    dweebdogg New Member

    I use the latest version of ClockworkMod Recovery 5.0.2.0 from hboot. but i have no acces to ROM Manager because i need to be in android os to use that program.

    I have used 3 sd cards with no change..

    I read this articles:
    1] [GUIDE] Read this before going for eMMC replacement. - xda-developers
    2] [solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log - xda-developers
    3] Recovery error information thread (E:Cant mount /cache/recovery/command) - xda-developers

    It is the same problem i have... i hope there is another solution.
  6. notebook

    notebook Well-Known Member

    If you're stuck on the HBoot menu and can't install a ROM or do a factory reset, then I think taking your question to the XDA forum will yield more ideas to help you. It may seem like the same problem as those you cite, but there might be something which makes yours different. If applicable, they may be able to solve your problem with adb commands. My knowledge of that tool is basic.

Share This Page