I've had many problems with my cache partition. I was going to try and install a new ROM since my phone was working fine for a while. So I installed TWRP and rooted it. I noticed inside TWRP it said
E:\ Unable to mount cache".
I tried to mount it in TWRP and it wouldn't let me select it. I tried formatting/wiping the cache and it seemed to complete but then it displayed the same error message. After I tried to wipe the cache partition my phone was unable to boot. It was stuck on the swirling balloons before the android logo displays. So I downloaded the cache.img for 5.1 and flashed it. When I gave the command fastboot flash cache.img it starts erasing the cache and gets stuck there. The phone freezes and doesn't do anything until I power it off. So I am unable to flash the cache.img. My phone was stuck in a boot loop and doesn't get fixed into I going into TWRP and input this command from shell:
mkfs.ext2 /dev/block/mmcblk0p27
After I use that command the phone boots fine and everything seems okay. So now my question(s) is, does anyone know what is up with my cache partition? Why doesn't TWRP mount it? And when I do anything with the cache partition my phone stops working.....
I am on stock 5.1 with no custom kernels.
Exactly the same problem , the phone works, but does not wipe the cache , please help:crying:
Anyone have any ideas what is up with my cache partition?
Same here, phone working with no prob, but can't flash anything on twrp: fail with message Unable to mount /cache
Already tried:
-flash cache.img
-fastboot erase/format cache
Curiously, twrp can wipe the cache.
Go into Recovery and do a wipe cache again and wait for it to finish, it could last like 5~30mins so i recommend connecting the charger just in case then you'll be fine. If it doesn't work try with another custom recovery or go back to stock recovery.
This happened to me a while back and to a friend of mine a few weeks back thank god he called me since we both got a N5. :good::highfive:
It's a bug in the latest TWRP... Go back to 2.8.5.3 for the while.
I solved this problem in such a way:
write to the console on the PC or TWRP
PHP:
adb shell
make_ext4fs /dev/block/mmcblk0p27
exit
Now , the cache is working , you can put whatever you want, but do not wipe cache dies again , this command is essentially wipe . Good luck
ZloKira said:
I solved this problem in such a way:
write to the console on the PC or TWRP
PHP:
adb shell
make_ext4fs /dev/block/mmcblk0p27
exit
Now , the cache is working , you can put whatever you want, but do not wipe cache dies again , this command is essentially wipe . Good luck
Click to expand...
Click to collapse
I have been able to boot into TWRP, however my pc doesnt detect the phone. Whats the solution ? No way to backup my data also now.
Related
I was trying to install CM11 on my Stock unrooted xoom, so I went ahead and followed cyanogenmod.org's guide.
It was great until the flashing CM part. And then, I got this error: System is not bigpart . (something along those lines.)
I found a same guy who had posted a solution to this.
So I go ahead and follow this, and when I flash BigPart TWRP 2700, I get this error on the device: Installation aborted. I used the sideload method for this.
I looked up some forum threads on how to fix this, and there was a thread which told me to install another version of TWRP BigPart, the R.A.H version. I did that by sideload, it installed, and I rebooted into recovery (after wiping dalvik cache). Teamwin loaded up fine, and I headed into the wipe section. According to the solution at ditoforge.com (link above), I had to go to advanced wipe and wipe everything BUT the sdcard. I did that, and I got this error: E: Can't mount /cache. I went ahead and flashed CWM through fastboot again, repeated the process, and no luck. Then, I went into fastboot and flashed TWRP Bigpart 2.7 directly using adb. It worked, though I got a series of errors upon trying to wipe (unable to mount /system, /cache, /data, etc)
I panicked, fearing a brick, and flashed back CWM. Luckily, I had taken a backup of Stock 4.1 and I restored back to that, thankfully finding it working. *phew*
I also tried fastboot format cache but I got this error on cmd:
Code:
C:\Users\User\Desktop\adb>fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
Strangely, fastboot erase cache seemed to work.
I wanted to call quits, but I love CM11 and I would really like to give this a shot. Any help and tips would be really appreciated. Thank you all in advance.
Bump. Tried to use CWM recovery again after flashing, but now ADB doesnt work in recov. :\
Bump..
Any help would be appreciated..
I formated all partitions individually in TWRP and it worked... I.E, managed to flash CM11.
Hope that helps.
Now I'm back on CM10.1
Sent from my Nexus 5 using XDA Free mobile app
ATZ-007 said:
I formated all partitions individually in TWRP and it worked... I.E, managed to flash CM11.
Hope that helps.
Now I'm back on CM10.1
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I've tried that too, but I can't wipe any partition with TWRP. I get the error "E: Unable to mount /cache" with any partition. Thanks for the help though.
Bump.. help needed please..
Is no one active on the XOOM forums anymore? :|
Bump.
bumping a year later help pls
Same issue... Can't mount /cache
How can I manually format it?
Solved:
fastboot erase cache
I have a galaxy pro 12.2 rooted with CM12.1.
I tried to install a nightly but I couldnt wipe the cache. The console always says "can't mount cache"
I tried it 300 times and rebooted 300 times and it wouldn't mount.
After googling for a little bit, a majority of the pages I found said TWRP isnt stable with partitions and I was supposed to choose rm -f instead of formatting the partition or it corrupts the partition.
I'm assuming this is what happened to me because I just wiped the cache instead.
I wiped the cache and dalvik and system and did a factory reset and then I installed the nightly. It would boot but then it got stuck on the boot screen. So I tried to clear the cache again but I got the same error.
Then I reset my phone and wiped /system and data but not cache because I couldnt mount cache. And then I installed a stock rom. This rom also gets stuck on the boot screen. So now I have a tablet with a stock rom installed and what I'm assuming is a corrupt cache partition.
Also, I did back up before I installed the nightly. I have a working backup on my phone. It worked fine when I used it and it gave no errors when I backed it up and I got no errors when I restored it other than cant mount cache.
So I tried to boot into my working backup too. Still didnt work.
How do I fix this?
So I've encountered the issue once again where I get a message saying "System UI Has Crashed" and then a crash loop occurs continuously after each boot. So I went to restore my phone from a backup and found that /system, /cache, and /data were all corrupted and could not be mounted by TWRP.
Flashing the BLU_SYSTEM_0.img file using SP Flash Tool fixed the issue with /system, and wiping the cache seems to have fixed it, but I still am getting messages that TWRP can not mount /data and storage and it has been sitting on "Formatting Data using make_ext4fs..." for an extended period. I had attempted "fastboot format userdata" and that didn't fix the issue.
Will TWRP eventually correct this on its own, is there something else I should do, or is my phone just a brick?
Ive had luck letting it sit for LONG time;
but i find TWRP 2.8 seems much better and quicker with wiping...
also Ive had luck using SP FLASH tool flashing ALL parts, (using allview or gionnee complete roms)
reflashing all the partitions to fix corruptions was a pain; but it worked... then I restored a nandroid back to BLU
uchua said:
So I've encountered the issue once again where I get a message saying "System UI Has Crashed" and then a crash loop occurs continuously after each boot. So I went to restore my phone from a backup and found that /system, /cache, and /data were all corrupted and could not be mounted by TWRP.
Flashing the BLU_SYSTEM_0.img file using SP Flash Tool fixed the issue with /system, and wiping the cache seems to have fixed it, but I still am getting messages that TWRP can not mount /data and storage and it has been sitting on "Formatting Data using make_ext4fs..." for an extended period. I had attempted "fastboot format userdata" and that didn't fix the issue.
Will TWRP eventually correct this on its own, is there something else I should do, or is my phone just a brick?
Click to expand...
Click to collapse
Reboot your phone and boot to TWRP again, then try to Wipe > Advanced Wipe > Tick "Data" only > Swipe to Wipe. If it doesn't work, reboot and keep trying until you get tired of it or it eventually works, whichever comes first.
Hi all,
I tried to flash GoldEagle on to my S6, however, a problem has ensued.
I'm stuck at A recovery screen (Blue screen appears) as I dont think the recovery image wrote to the phone properly but it did do the wipe/factory reset. Now I dont think there's an OS on the phone.
Options I've got in the recovery menu...
Reboot system now...
Reboot to bootloader....
Apply update from ADB
Apply update from SD Card
WIpe data / factory reset
Wipe cache partition
Mount /system
View recovery logs
Run Graphics Test
Power off
Any ideas ?
How do I get an OS back on the phone?
Thanks all
Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.
Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.
Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .