Database Users

Clockworkmod recovery E:Can't find MISC:

Just recently got a streak and have been tinkering to get it ready for rom flashing when a froyo or two appear and just want to check my clockworkmod recovery has worked correctly.
A brief history of what i've got and done:-
Device is an o2 uk model with 2.1 update 1 on it.
Used androot to root it then root explorer to remove the recovery-install.sh then terminal emulator to install clockworkmod 2.5.0.1.
(didn't use adb as i'm on win7 x64 and it doesn't want to work )
When i enter clockworkmod recovery the screen displays and at the bottom after the menu it says:-
ClockworkMod Recovery v2.5.0.1
E:Can't find MISC:
E:Can't find MISC:
E:Can't find MISC:
So question is is this ok or should i try an earlier version?
Cheers
Paul

Johnston411 said:
(didn't use adb as i'm on win7 x64 and it doesn't want to work )
Click to expand...
Click to collapse
Download PDAnet for android and use the driver included with that package instead of the dell driver.
I am using Win7 x64 also. My adb works fine now.

r00tcause said:
Download PDAnet for android and use the driver included with that package instead of the dell driver.
I am using Win7 x64 also. My adb works fine now.
Click to expand...
Click to collapse
Cheers i'll give that a bash
What clockwork recovery are you using?

i get the same error..
clockwork still worked for me even with the that error.
i found out by accident, scrolled around, pressed power button a couple of times, scrolled up and down and press the camera button a few times on the option and it worked. weird. i noticed like maybe i didn't press the button in deep enough.

I see that error too. Despite it, flashed to Froyo using update_new.zip with no major issues.

That is normal behaviour, wrong is to see a message "Can't mount" so you are all set up to roll on froyo, good luck you won't regret.

Johnston411 said:
Cheers i'll give that a bash
What clockwork recovery are you using?
Click to expand...
Click to collapse
None of the above at the moment since I went back to 1.6 from 2.1 build 6941. 1.8.1.7 is the only one that seems to work on 1.6 and it doesn't work that well (buggy).
The new one should work on 2.1, so I hear.
I'll be swapping to the new 2.2 beta soon so we shall see.

What can you do, if you have the can't mount error?
e: can't mount cache:recovery/command

same here
i wondered the same but as my clockwork works i havent worried too much about it... however everytime i attempt a nandroid backup, its fine till near the end when it says data failed, then if i try to restore the backup i get md5**** mismatch?
ive got used to starting from scratch everytime i do anything but it would be nice to have it working properly!

Don't bother with Clockwork, as Nandroid doesn't work! Use the recovery from http://forum.xda-developers.com/showthread.php?t=840326 instead as the Nandroid on this works perfectly! Saves a lot of time not having to re-install everything when something goes wrong

odyseus said:
Don't bother with Clockwork, as Nandroid doesn't work! Use the recovery from http://forum.xda-developers.com/showthread.php?t=840326 instead as the Nandroid on this works perfectly! Saves a lot of time not having to re-install everything when something goes wrong
Click to expand...
Click to collapse
brilliant...thank you!

Sorry for the wrong model, but i'm having this issue on a Desire too. I've routed the Device with unrevoked without a problem, then wanted to create a Nandroid, which doesn't work.
Also i've tried to wipe data and cache, CWM said all good, but after restart all Data is still there.
Could that be ROM related, the Rom is T-Mobile, not any official HTC Rom.

[Q] samsung fascinate xxxx up

samsung fascinate dl09 radio, rom and 2.6.29.6 kernal i tryed to ryan lagfix it said to reboot i tried and now it stuck on samsung no matter what i try and it says
E:can't mount /dev/block/still
(invalid argument)
E:can't mount /dev/block/still
(invalid argument)
when i try to reboot i have tried to odin it and nothing should i get my motorola droid out cause i fried this samsung please help

Head over to the fascinate irc channel for real time help (irc.droid-life.com #fascinate). Ryan lagfix is outdated and has been known to brick phones. Hopefully that is not the case for you.
Sent from my Vanilla Froyo Fascinate

Take your phone back and buy John's phone.

i have tired to get on irc.droid-life.com and it said i have no permission

alusher said:
i have tired to get on irc.droid-life.com and it said i have no permission
Click to expand...
Click to collapse
Have you tried using ODIN to flash stock DL01/DJ05 or DL09 .tar's to restore to bone stock yet

i have tried dl09 and im downloading the stock dl01 bone stock

i used odin with dl01 v3 and it works thank you two guys for your help

Yeah... Don't use that lag fix. It is completely outdated, and you probably don't need it.

[Q] cant mount /system cwm

I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.

gamershadow said:
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
Click to expand...
Click to collapse
This issue has cropped up a lot recently. I'm sorry to say it but you might have bricked it. There is a chance though. 2 questions:
1. did you use gfree to root?
2. do you have the engineering Hboot? (.85.2007?)

I did use gfree to root. and i dont have the engineering Hboot.

gamershadow said:
I did use gfree to root. and i dont have the engineering Hboot.
Click to expand...
Click to collapse
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier

mark manning said:
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
Click to expand...
Click to collapse
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?

gamershadow said:
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
Click to expand...
Click to collapse
Ya you shouldn't have a prob

Yeah, they should give you a brand new in the box, depending on which state you're in, you have either 14 days or 30 to return the phone
Sent from my HTC Glacier using XDA App

I'm stuck as well.
Don't know WTF happened. Was running Iced Glacier for a couple of months, then decided to try one of the new ROMs, so took CM7 for a spin, then went to RoyalGinger for a day or two. Things were working, but RG started freezing up, etc. so tried going back to CM7. Once I started through the flash process I hit an error when trying to format /system.
Now when I even attempt a wipe (or most anything) via CWM I continuously get errors like:
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
...and this latest time, I now got this as well:
E:\Can't mount /cache/recovery/command
I had CWM 3.0.2.4 through all of this, so should be able to flash 2.2 and 2.3 ROMs, as I understand. I can only get into CWMR and HBOOT.
I used gfree to root & have engineering HBOOT (.85.2007).
I can't get device listed in ADB, but can under fastboot. Tried flash command using fastboot to try and re-flash CWM (no idea if it would do any good), but it says cannot open the .img file.
The ONLY thing I got to work was mounting SD to USB in CWM and putting PD15IMG.zip in the root of the SD card, then rebooting and letting it run an auto update as it looks for this by default. That worked and took me back to stock...nothing else I tried would work.
Now I'm afraid of doing anything else or risk creating an expensive @ss paperweight.
Any help or suggestions appreciated as to HOW this happened, and next steps.

help please

i got a rooted mytouch 4g with clockwork 3.0.2.4 and miui rom and everything was fine till today it just froze on me and i toke the battery out to restart and i just stayed on the my touch 4g screen so i toke the bat out and went into recovery and its giving me this error
E:cant mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
i tried wipe data/factory settings and reinstalling the rom and it still says that and i still get stuck on the my touch 4g screen
i also tried to restore and still getting that and getting stuck in the my touch 4g screen
does anyone know how i can fix this
what do i need to do
thank you

There dozens of threads on this issue now. Do a little search and you'll find a lot of information on the problem. I'm sorry to say, but it sounds like you have a bad eMMC and it's essentially bricked.

thanks for the reply im a noob when it comes to this but i followed all the steps in rooting and installing roms everything was working fine for a good 3months i used to have cm7 and then switched to miui and had that ever since
so im pretty much screwed lol
i googled and i cant find nothing on how to fix :-/

drocha86 said:
thanks for the reply im a noob when it comes to this but i followed all the steps in rooting and installing roms everything was working fine for a good 3months i used to have cm7 and then switched to miui and had that ever since
so im pretty much screwed lol
i googled and i cant find nothing on how to fix :-/
Click to expand...
Click to collapse
Unfortunately nobody has been able to fix this yet. You could attempt to exchange it at t-mobile.

well now i think i got a full brink i tried doing the pd15img.zip trick and the only thing that turns on is the orange led wtf lol
if i send it back will they know that i rooted it can i just say i dont know what happend lol ??

[Q] Help! Nexus 10 Stuck at Google Logo, tried all solutions nothing works

Please help me, this is really frustrating .
I have a rooted nexus 10 running the latest CM10 with Clockwork Recovery. One day it ran out of battery and when I charged and booted it up, it got stuck at the Google logo. I went into CW Recovery and wiped everything, but I realized it wouldn't mount anything. I got messages saying:
"E: Can't mount /cache/recovery/command
E:failed closing /dev/block/platform/dw_mmc.0/by-name/missc
(I/O error)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/last_log
E:failed closing /dev/block/platform/dw_mmc.0/by-name/misc
(I/O Error)"
I tried Wug's toolkit, I tried nexus root toolkit, and tried downloading adb to my pc with fastboot commands.
Someone please help !

If I were you, I'd try to flash the stock recovery using Wug's Toolkit (somewhere in the advanced tools menu). Then, unbrick it and install everything custom from the scratch. However, always remember to be careful with advice from pingguo! I'm not a dev, but I have quite some experience in softbricking devices and finding a way to get them running again. :silly:

All you need to do is download the fastboot files, use the flash all file and then go into the stock recovery and wipe data/factory reset. It will boot after that.
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
All you need to do is download the fastboot files, use the flash all file and then go into the stock recovery and wipe data/factory reset. It will boot after that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the reply!
I have tried that. It doesn't seem to work :crying:.
I get messages like
"archive doesn't have boot.sig
archive doesnt have recovery.sig.."
Any other ideas?

Try to download the stock 4.2.0 image manually from goo.im
I remember having that issue with some automatically fetched image...

Those two errors are fine, they always happen.
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Those two errors are fine, they always happen.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yep, I agree.
I have seen this problem a few times recently, I think this can help: http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
I think the problem you are having is relating to fastboot.exes interaction w/ your specific device. Good luck!
Edit: But one thing I'm unsure of in your case is - I think I remember reading on these forums about if you do a full wipe off both /all areas and one other condition, you could have a real bad situation. Perhaps a pro knows on that?

bigmatty said:
Yep, I agree.
I have seen this problem a few times recently, I think this can help: http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
I think the problem you are having is relating to fastboot.exes interaction w/ your specific device. Good luck!
Edit: But one thing I'm unsure of in your case is - I think I remember reading on these forums about if you do a full wipe off both /all areas and one other condition, you could have a real bad situation. Perhaps a pro knows on that?
Click to expand...
Click to collapse
Thanks for the reply. Do you know how I am having problems relating to the fastboot.exes?
I was able to run flash-all.bat, but it reboots and i'm still stuck at the Google logo.

brianiswu said:
Thanks for the reply. Do you know how I am having problems relating to the fastboot.exes?
I was able to run flash-all.bat, but it reboots and i'm still stuck at the Google logo.
Click to expand...
Click to collapse
If you are able to get into the stock recovery do the factory reset option and it should boot up
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
If you are able to get into the stock recovery do the factory reset option and it should boot up
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
when I boot into recovery, it's still clockwork. When I use wug's toolkit to flash stock recovery or stock kernel, it temporarily boots into the Sentinel Rom (I said CM10 before but I got the roms mixed up), but all messed up. Once I hard reset that it goes back to being stuck at the Google logo.

brianiswu said:
when I boot into recovery, it's still clockwork. When I use wug's toolkit to flash stock recovery or stock kernel, it temporarily boots into the Sentinel Rom (I said CM10 before but I got the roms mixed up), but all messed up. Once I hard reset that it goes back to being stuck at the Google logo.
Click to expand...
Click to collapse
Well, usually when someone reports "stuck at Google (nexus) logo" the fix is just "factory wipe". And it gets reported a lot because it seems to happen after fastboot oem unlock (at least on 4.2.1) almost always.
The behavior you describe is certainly weird. But even if its not stock recovery, can you use any of them to do a "factory wipe"?
Im pretty new to all of this myself, but everyone always touts the "flash-all back to stock" as a way to fix everything. If you poke around in those threads I linked to you will find one of the vets here walks someone through something similar to what you are describing... but not 100% exact same...
I think it is possible to re-flash just the stock recovery, if flash-all is not getting you to that point. I'd look into that (I think that's even talked about on the links I did above.) If you could flash JUST the stock recovery first, then maybe you could use flash-all to completion?

You need to flash the stock recovery to get it to work
Sent from my Nexus 10 using Tapatalk HD