Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849
Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.
having the same problem.. so should i try to wipe the cache and see what happens?
I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.
I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?
What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?
@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?
Hi guys,
Had a thread open on modaco for this issue but had no joy. I'm having exactly the same issues as the thread starter in the link below, you guys have helped me before and wondered if you had any suggestions on a way forward?
http://www.modaco.com/topic/358071-phone-near-bricked-help-needed/
Basically I've had ics updated on the phone with the boot loader unlocked and of course the phone rooted. The update went through fine and I've been using the phone for a couple of days until it crashed and stuck on the splash screen since then it will only go into recovery mode with the following errors:
E: Can't mount /cache/recovery/command
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
Have tried wiping cache, formatting cache and numerous other things as per the thread on modaco but no joy. I've literally had the phone a few days and think it's unlikely to be a hardware fault unless it's exactly the same as the OP had.
Willing to try anything!
Thanks
Hello Developers
Yesterday, i tried to do a CWM back up of my ROM and it stopped in the middle with below errors
E:Can't open/cache/recovery/log
E:Can't open /cache/recovery/log
[Read Only File System
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I Know there are many threads with this question, however mine is litte different; How?
1. I am able to mount my SD CARDs to PC
2. ADB works fine
3. Format Cache - Works fine
4. Wipe / Factory Data Reset - Works fine
5. Format System Works Fine
6. Wipe Dalvik Cache - Exits without any error
When the system reboots, I get a message "ENCRYPTION UNSUCCESSFUL" Reset phone, when clicked on Reset, phone reboots into Recovery.
ADB works fine, but i am not able to use Flash_image - Error Message file not found [it was placed in root of the memory card]
Tried to flash recovery through SP flash tools, i get an error Message - SDA SDMMC write failed
MTK Root tool does not recognize phone.
Please let me know if this is a permanent brick or is there any work around to resolve this.
My phone is only 6 months old, but cannot claim warranty because of CWM and Boot logo changed
I was on Android 4.4.2, and was going to sideload the 4.4.3 update. I went into recovery, moved one step below the sideload update option, and landed on clear cache. My volume up button wouldn't take me back up to the ADB Sideload option, so I figured clearing the cache would bring me back up to the top. The phone was stuck on the "Wiping cache..." loading bar for 20 minutes until I finally force rebooted it. On completing the reboot, my phone wouldn't connect to the cell network, and all of my gapps crashed. I tried going back into recovery, and got errors saying;
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
I really don't know how to go forward from here, so I'm hoping somebody can point me in the right direction. Thanks!
darthsentinel said:
I was on Android 4.4.2, and was going to sideload the 4.4.3 update. I went into recovery, moved one step below the sideload update option, and landed on clear cache. My volume up button wouldn't take me back up to the ADB Sideload option, so I figured clearing the cache would bring me back up to the top. The phone was stuck on the "Wiping cache..." loading bar for 20 minutes until I finally force rebooted it. On completing the reboot, my phone wouldn't connect to the cell network, and all of my gapps crashed. I tried going back into recovery, and got errors saying;
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
I really don't know how to go forward from here, so I'm hoping somebody can point me in the right direction. Thanks!
Click to expand...
Click to collapse
If bootloader is unlocked, try flashing the cache file from the ktu84m package.
Aerowinder said:
If bootloader is unlocked, try flashing the cache file from the ktu84m package.
Click to expand...
Click to collapse
Sadly, the bootloader is locked.
This same thing happened to me the other day. I ended up having to reflash the factory image
Sent from my Nexus 5 using Tapatalk
the cache partition got messed up because you didn't let it finish the cache formatting process.
Head over to the stock recovery and keep formatting the cache partition few times.. If it gives the same error, erase it again!
I've faced similar errors and formatting cache a few times solved it!
- Sent from an IceCold Hammerhead!
Happen to me this morning as well. Just let be until completed. Should take approximately 10-15 minutes. Be patient. :victory:
Hello people of XDA developers,
One fine day, my nexus 5 started hanging up while booting. After the google Logo, the Marshmallow animation would show up and then it would hang and power off. I have no problem in doing a factory reset/wipe of my phone. But the only thing i want to save is my contacts. I have tried erasing and re-flashing system, cache, boot and boot-loader. Using ADB, flashing the cache always fails........ However, i have not touched userdata as i think it would affect the contacts too. I have even tried using different custom recoveries such as CWM, TWRP and even Philz Touch to use adb to pull my SD card files to my PC. Even flashing the system is not working now.... (atleast that's what my results were) .
Philz touch error messages....
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Driven to the point of desperation now........ Thanx a lot in advance... BTW, i'm a complete noob, so plz bear with me and my questions
A223D said:
Hello people of XDA developers,
One fine day, my nexus 5 started hanging up while booting. After the google Logo, the Marshmallow animation would show up and then it would hang and power off. I have no problem in doing a factory reset/wipe of my phone. But the only thing i want to save is my contacts. I have tried erasing and re-flashing system, cache, boot and boot-loader. Using ADB, flashing the cache always fails........ However, i have not touched userdata as i think it would affect the contacts too. I have even tried using different custom recoveries such as CWM, TWRP and even Philz Touch to use adb to pull my SD card files to my PC. Even flashing the system is not working now.... (atleast that's what my results were) .
Philz touch error messages....
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Driven to the point of desperation now........ Thanx a lot in advance... BTW, i'm a complete noob, so plz bear with me and my questions
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible help for your issue, I'm going to move this thread to your device's Q&A forum. Good luck!
Did you check your Google or gmail account to see if the contacts have been synced?