Database Info

Can't mount /cache/recovery/

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?

bricked device?

hi,
I tried upgrading my tf300t from cm10.1 to cm10.2 . after a few failed attempts during which I am not exectly sure what I did wrong i got the device into a condition in which it only boots directly into CWM v6.0.2.3 without any option to do anything else. pressing power+volume down does not stop it from directly booting into recovery.
inside the recovery it says:
"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/",
and i cannot mount any partition on the device. trying to access it from fastboot\adb has not been successful.
Any help would be appreciated.
thanks a lot,
guy

I now recall that at some point after trying to flash cm10.2 didn't work I tried flashing the offical asus firmware blob. after that the device successfully booted but when I tried to return to the recovery mode I still could not mount the /data partition. after that I tried some more flashing which brought me to the current situation.

new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.

Ghtm said:
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Click to expand...
Click to collapse
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.

cmendonc2 said:
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
Click to expand...
Click to collapse
how do i flash a rom using fastboot?

Ghtm said:
how do i flash a rom using fastboot?
Click to expand...
Click to collapse
like this:
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
Code:
fastboot -i 0x0B05 flash system blob

cmendonc2 said:
like this:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.

Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"

Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Ghtm said:
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Click to expand...
Click to collapse
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.

cmendonc2 said:
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
Click to expand...
Click to collapse
it says permission denied (cause i do not have root access?)

Ghtm said:
it says permission denied (cause i do not have root access?)
Click to expand...
Click to collapse
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.

cmendonc2 said:
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
Click to expand...
Click to collapse
the /data prevents me from accessing anything on the sdcard so i cant flash anything from inside the recovery itself.

so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy

Ghtm said:
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Click to expand...
Click to collapse
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.

cmendonc2 said:
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
Click to expand...
Click to collapse
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.

Ghtm said:
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Click to expand...
Click to collapse
Using twrp 2.6.3.0 -4.2 ? Or -jb?

cmendonc2 said:
Using twrp 2.6.3.0 -4.2 ? Or -jb?
Click to expand...
Click to collapse
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"

Ghtm said:
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Click to expand...
Click to collapse
Use the 4.2 one. The jb will result in a very bad brick.

cmendonc2 said:
Use the 4.2 one. The jb will result in a very bad brick.
Click to expand...
Click to collapse
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:

Ghtm said:
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Click to expand...
Click to collapse
No problem, Merry Christmas!

[Q] OnePlus Bootloop / access to partition lost

2 weeks ago, my oneplus stucked in a bootloop. it just restarted itself and after the oneplus logo, endless bootanimation
Infos: Oneplus china version 64 GB black, not rooted, before error no twrp installed
I think I tried everything, different versions of twrp and via adb sideload tried to flash different official .zip versions of cygnmod. always the same error:
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount /data/meida/TWRP/ . twrps when trying to read settings file.
E: No valid storage partitions found for MTP.
E: Unable to mount '/data'
E: Unable to mount '/data'
I also tried different toolboxes (chinese omnipotent toolbox; oneplus one toolkit) flashing process was ok, but then it restarted and still bootloop.
does anyone know this problem and has a solution? thanks in advance...

+1

n J o y said:
+1
Click to expand...
Click to collapse
This sounds serious,
@timmaaa @timmaaa

waterdaan said:
This sounds serious,
@timmaaa @timmaaa
Click to expand...
Click to collapse
E: Unable to mount ' /data'
E: Unable to mount ' /cache'
E: Unable to mount storage.
E: Unable to mount /data/media during GUI start up.
and in fastboot trying to flash userdata (or anything)--> "FAILED (remote: failed to erase partition)".
The phone works only in fastboot or recovery, also with otg.
I think that OPO needs a script to recreate the partition in storage (?)

This is way over my head, you should wait for timmaaa to respond

n J o y said:
E: Unable to mount ' /data'
E: Unable to mount ' /cache'
E: Unable to mount storage.
E: Unable to mount /data/media during GUI start up.
and in fastboot trying to flash userdata (or anything)--> "FAILED (remote: failed to erase partition)".
The phone works only in fastboot or recovery, also with otg.
I think that OPO needs a script to recreate the partition in storage (?)
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.

timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
Click to expand...
Click to collapse
Thank you very much for helping everybody out
Much appreciated!!!
You're the best

timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
Click to expand...
Click to collapse
If i try to flash something on fastboot it says --> "FAILED (remote: failed to erase partition)".

hi,
i already have 2 opos with this issue, one which is my own and one i ordered for a friend. the phone just rebooted itself at some point and was stuck in a bootloop. access to recovery and fastboot work, but recovery cant mount /system, /data, /persist, and /firmware. formatting doesnt help, flashing factory images gets stuck when flashing either system.img or userdata.img,
the first phone is already shipped out for rma and the second one will soon be shipped out.
maybe there is a problem with the memory chips themselves?

n J o y said:
If i try to flash something on fastboot it says --> "FAILED (remote: failed to erase partition)".
Click to expand...
Click to collapse
Ok, you might need to try one of these:
http://forum.xda-developers.com/showthread.php?t=2970390
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon

Mutlirom Recovery Update---->Bootloop

Hello all
I just updated the multirom recovery after a year of successfully using it with 4 different roms, which 1 of them is ubuntu and now am stuck in a bootloop.
Whatever rom I try to boot it kicks me back to the rom selection screen. It must be something wrong with multirom recovery because even when I select to boot into bootloader or even Shutdown the phone from the multirom menu it just bootloops to the same screen again.
I'd really appreciate any kind of help you can give, it's extremely important I don't lose my roms. I want to save the phone as is.
Any ideas? Would really appreciate it.
-Regards.

I can't install any version of Multirom through twrp recovery. It always gives me error 7.
I also can't install a new rom. It says "Failed to create rom folder(Read only file system)".
I flash the AK kernel succesfully but at the end it gives me these errors:
E: Unable to mount '/data'
Failed to mount /data partition!
Updating partition details...
E: Unable to mount '/data'
...done
E: Unable to mount storage
Click to expand...
Click to collapse
Is there something rom with my file system?
Please, any idea would be really appreciated.

Encryption failed - device will not work

Hi,
Im noob at this so please bear with me.
Ive got this Tab2 which will not work. Im interested in fixing it(if at all possible)
I have no idea what had happen to it prior to this error.
Problem:
When starting and went trhough the boot logo the device shows "Encryption failed" page.
with further text:
Code:
Unable to complete encryption due to interruption. Perform factory data reset(erasing all your data) before use. After resetting, try encrypting device again.
Tried:
booting into recovery and resetting data/factory, no result.
when entering recovery it says:
Code:
"installing system update, no command" and enters the recovery.
then it lists:
Code:
Android system recovery <3e>
under menu there are some errors:
Code:
"Manual mode"
e:failed to mount /data (invalid argument)
can't mount '/data' (invalid argument)
E:failed to mount /data (invalid argument)
E:can't mount /data/log/recovery_log.txt
and a lying robot...
--------------
when trying to delete/factory reset the unit
it show all ok:
Code:
-- Wiping data...
Formatting /data...
Formatting /cache...
Data wipe complete.
Rebooting gets device into previous "Encryption failed" page.
I tried to flash custom recovery with odin but even when saying pass it does not work, I cannot boot into either twrp or cwm.
tried the trick without rebooting and going straight to the recovery from Odin.
did try with sdcard and flashing the recovery but it fails to flash that way.
also tried to apply the stock rom with odin but it fails evry time.
is there hope for this tab?
please assist.
regards, DMB.

Forgot to add the device:
Code:
GT-P5100
3G
16GB

dmdb said:
Forgot to add the device:
Click to expand...
Click to collapse
sounds like a broken emmc. read http://andi34.github.io/faq.html for more info. scroll down to the bottom of that page.

ok
smart-t78 said:
sounds like a broken emmc. read for more info. scroll down to the bottom of that page.
Click to expand...
Click to collapse
ok, will not be doing anything more about this.
thanks