Develop Bugs

[Q] Anything else I can try? Can't mount /cache, can't unlock bootloader, won't boot

I had been using my tablet normally and set it aside for a while. When I went back to it, it was stuck at the boot splash screen that is black with the white Google text on it. I tried rebooting several times and it would return to this state.
I booted into fastboot mode and went to recovery mode. The following errors were displayed at the bottom of the screen:
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)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
E:failed to mount /cache (Invalid argument)
I tried doing "wipe data/factory reset". It says:
-- Wiping data...
Formatting /data...
... and then goes into many more errors regarding failures mount/open /cache
Thinking maybe the cache partition was bad, I went back to fastboot mode and issued the following command from my pc:
fastboot format cache
... but the command never returns (after an hour, it had not returned, so I cancelled)
The same happens if I try
fastboot format userdata
... it never returns.
I can't unlock the bootloader to attempt to flash a new image. I can issue command
fastboot oem unlock
and get the correct screen, but selecting unlock just locks up the tablet. I left it this way for a couple hours, no change.
So to summarize: I can access fastboot, I can access recovery, but I can't seem to affect any change that will recover the system.
I've exhausted everything I know to try. Any thoughts?
It's ironic because I hack on these all the time at work, but this was my personal unit that was stock and unrooted.

Yours is not a common situation, but there have been a few reported just this last week. Unless someone knows of a solution, like why the bootloader hangs at unlocking or if it can be reflashed (not possible AFAIK without unlocking), your only option seems to be warranty service. Sorry.

Pandae said:
Yours is not a common situation, but there have been a few reported just this last week. Unless someone knows of a solution, like why the bootloader hangs at unlocking or if it can be reflashed (not possible AFAIK without unlocking), your only option seems to be warranty service. Sorry.
Click to expand...
Click to collapse
Not what I wanted to hear, but thanks. I wonder if a recent update has stressed the file system or ECCM.
Someone posted a way to test the ECCM chip via command line, but I can't find it. Do you recall?

I've only heard of Android apps that test the eMMC's integrity, nothing that can be run from a PC.

I had a similar problem and when I used to enter 'fastboot devices" I used to get '?????? fastboot'. and the bootloader used to freeze but recovery mode (TWRP) was fine.
I then realized that I wasn't using the USB cable that came with the Nexus 7. When I switched cables. It recognized the device using 'fastboot devices'. Then I just ran the .bat file in the factory image files. I hope this helps.

I have the exact same issue that just started as of Tuesday, January 7th. I feel like I've exhausted all options and continue to get the mount cache error. I secretly suspect the storage went bad on that very cold day in NYC. My old Nexus 7 was off at the time and still works but the new one might have been on in my backpack walking around.

BootlegZani said:
I have the exact same issue that just started as of Tuesday, January 7th. I feel like I've exhausted all options and continue to get the mount cache error. I secretly suspect the storage went bad on that very cold day in NYC. My old Nexus 7 was off at the time and still works but the new one might have been on in my backpack walking around.
Click to expand...
Click to collapse
I'm on the same boat as you, guys. what a coincidence, even on the same date, January 7th. I was browsing on chrome and it froze a second, rebooted and got stuck at the Google Logo. Official KitKat, not rooted.
Nothing works, wiping data via Recovery gives a tonne of "mount /x" errors and flashing through fastboot is impossible because it gets stuck trying to unlock the bootloader.
I, too, think it's a hardware issue, probably with the storage. The only difference is that I am in the very warm Venezuela, so I think the NYC cold wasn't the problem!
The sad thing is my uncle bought it for me in Italy a month back because prices here are ridiculous, so now it's going to be a bit of a problem to return it to Amazon.it :crying::crying:
If any of you find a solution please post it!
Sorry for any misspellings.

Febo00 said:
I'm on the same boat as you, guys. what a coincidence, even on the same date, January 7th. I was browsing on chrome and it froze a second, rebooted and got stuck at the Google Logo. Official KitKat, not rooted.
Nothing works, wiping data via Recovery gives a tonne of "mount /x" errors and flashing through fastboot is impossible because it gets stuck trying to unlock the bootloader.
I, too, think it's a hardware issue, probably with the storage. The only difference is that I am in the very warm Venezuela, so I think the NYC cold wasn't the problem!
The sad thing is my uncle bought it for me in Italy a month back because prices here are ridiculous, so now it's going to be a bit of a problem to return it to Amazon.it :crying::crying:
If any of you find a solution please post it!
Sorry for any misspellings.
Click to expand...
Click to collapse
I honestly don't think there is a solution. I just contacted ASUS support via their website and started a RMA warranty repair.

Can you take a picture with another phone or something of the errors?
Also, can you try to mount the partitions manually in recovery
or go into recovery with adb shell and try to mount the partitions manually.
Also, what recovery do you have?
vaughnsphotoart said:
I had been using my tablet normally and set it aside for a while. When I went back to it, it was stuck at the boot splash screen that is black with the white Google text on it. I tried rebooting several times and it would return to this state.
I booted into fastboot mode and went to recovery mode. The following errors were displayed at the bottom of the screen:
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)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
I tried doing "wipe data/factory reset". It says:
-- Wiping data...
Formatting /data...
... and then goes into many more errors regarding failures mount/open /cache
Thinking maybe the cache partition was bad, I went back to fastboot mode and issued the following command from my pc:
fastboot format cache
... but the command never returns (after an hour, it had not returned, so I cancelled)
The same happens if I try
fastboot format userdata
... it never returns.
I can't unlock the bootloader to attempt to flash a new image. I can issue command
fastboot oem unlock
and get the correct screen, but selecting unlock just locks up the tablet. I left it this way for a couple hours, no change.
So to summarize: I can access fastboot, I can access recovery, but I can't seem to affect any change that will recover the system.
I've exhausted everything I know to try. Any thoughts?
It's ironic because I hack on these all the time at work, but this was my personal unit that was stock and unrooted.
Click to expand...
Click to collapse

mine also
Mine developed this same problem on January 5th while watching a video. I just sent it off for warranty yesterday (Thursday). Was anyone using ART. I know I was

latenighter49 said:
Mine developed this same problem on January 5th while watching a video. I just sent it off for warranty yesterday (Thursday). Was anyone using ART. I know I was
Click to expand...
Click to collapse
I was using Dalvik.

I had a similar issue as you guys therefore I decided to use the factory images to solve the issue. Be warned: using it will erase everything on your device. Photos, music etc.
If you do not mind, proceed on to download the factory images but please download the correct ones and put them into your fastboot folder which will contain these files:
api
image-razor-jss15q(unzipped file)
systrace
adb
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-flo-flo-03.14.img
fastboot
flash-all
flash-all.sh
image razor-jss15q (this is the zip file)
notice
source.properties
Once everything is all in there, open command window by left shirt and right click on your mouse and select command window and put your devices into fastboot and type into the command window: flash-all .bat
And it'll restore your device back to stock
---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------
Here's the link to the factory images for the Nexus 7 2013: https://developers.google.com/android/nexus/images#razor

Bobbi lim said:
I had a similar issue as you guys therefore I decided to use the factory images to solve the issue. Be warned: using it will erase everything on your device. Photos, music etc.
If you do not mind, proceed on to download the factory images but please download the correct ones and put them into your fastboot folder which will contain these files:
api
image-razor-jss15q(unzipped file)
systrace
adb
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-flo-flo-03.14.img
fastboot
flash-all
flash-all.sh
image razor-jss15q (this is the zip file)
notice
source.properties
Once everything is all in there, open command window by left shirt and right click on your mouse and select command window and put your devices into fastboot and type into the command window: flash-all .bat
And it'll restore your device back to stock
Click to expand...
Click to collapse
Hi, thanks for replying.
Correct me if I'm wrong, but you need to unlock the bootloader before flashing an image right? I tried it and it gets stuck trying to unlock it.
Code:
>fastboot oem unlock
<bootloader> Unlocking bootloader...
<bootloader> erasing userdata...
It got stuck trying to erase the data. Whic would be similar to the errors on recovery where it couldn't access the storage.

Febo00 said:
Hi, thanks for replying.
Correct me if I'm wrong, but you need to unlock the bootloader before flashing an image right? I tried it and it gets stuck trying to unlock it.
Code:
>fastboot oem unlock
<bootloader> Unlocking bootloader...
<bootloader> erasing userdata...
It got stuck trying to erase the data. Whic would be similar to the errors on recovery where it couldn't access the storage.
Click to expand...
Click to collapse
You are correct, flashing anything requires unlocking the bootloader. You aren't the only one who's getting stuck at unlocking, which could be a corrupted bootloader or a bad eMMC. I've never heard of solutions except to call for warranty repair.

Hy,
Today, i've the same issue. Nothing to do, i tried a lot of things like you.
Can't wipe cache or data, always failed to mount /cache.
My nexus was on stock rom locked, no root.
I'll go to the store, hope they can repair or change it quickly.
Lexso

Same here in middle east.
I also saw similar post several days ago.
http://forum.xda-developers.com/showthread.php?t=2644981
Anyway, I have exact the same symptom as you guys; locked bootloader and couldn't pass that stage.
I sent it to dubai for a RMA. Hope they will fix it and send it back to me ASAP.

Exactly the same thing just happened to me right now. The tablet restarted itself and do not pass the Google Logo. I did not unlock or whatever else my tablet.
In fact a week go i got a system update and since, my tablet is freezing or restarting without reasons. But that time it is for good. Is the ASUS warranty international ? Cause I bought my tablet in France (I am french) but I am living in Czech Republic.

donatien said:
Exactly the same thing just happened to me right now. The tablet restarted itself and do not pass the Google Logo. I did not unlock or whatever else my tablet.
In fact a week go i got a system update and since, my tablet is freezing or restarting without reasons. But that time it is for good. Is the ASUS warranty international ? Cause I bought my tablet in France (I am french) but I am living in Czech Republic.
Click to expand...
Click to collapse
Yes, it is global warranty. There must be a ASUS local service partner in Czech Republic.
Contact http://vip.asus.com/VIP2/Services/QuestionForm/TechQuery
and the customer service will let you know where you should contact.
I bought my N7 at Italy, but I'm fixing it in middle east.

You try unlocking its bootloader manually and don't use and program to do so
---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------
If you return the device back for warranty , you'll come back with a reconditioned device.
So I'm hoping that you try unlocking its bootloader manually yourself.
Boot the nexus into fastboot and type into fastboot (cmd) : fastboot oem unlock
Than it'll unlock the device than use the factory images with the links I provided earlier to flash them

Are you adverse to completely wiping it?
If you aren't then maybe hard reset it, fastboot oem unlock, and then flash it with Kit-Kat?

Twrp bootloop

Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML

I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...

TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?

Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.

mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done

TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!

Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read

wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!

i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.

i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed

Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course

what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!

Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?

ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!

colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work

i tryed it, i get the same error :/

Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?

colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again

You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!

Soft bricked Nexus7 can't get through "Can't mount" errors

Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!

I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.

E: failed to mount / efs (invalid argument) and ADB issues

HI!
I have an ATT Note 2 that I'm trying to get to work. It's in a boot loop on the ATT logo. While trying a factory reset and cache clear, I discovered that there was an error code in recovery mode: E: failed to mount / efs (invalid argument).
I looked on the internet and found a few potential solutions, so here's what I have done: flashed stock version 4.4.2 and TWRP version 3.0.2-0 onto the phone using Odin 3. I also rooted it by flashing (CF auto root?) as well. I then installed ADB version 1.4.3 onto my PC.
So I put the phone in recovery (TWRP) mode and went into "Mount," then "Mount/System." --and plugged it into the PC USB port. Next, I opened the Command Prompt and input: "adb devices"--perfect, it found the phone and knew it was in recovery mode.
Here's where I ran into trouble. When I input "adb shell," the next line came up, ~ # (backspace symbol)[6n with the cursor blinking next to the "n". That's as far as I have been able to go in the tutorials I have read/watched. I can find nothing about this code I am getting-- what it is, what it means, or what to do about it.
Now I don't know if where I was supposed to be headed would solve my problem but I would sure like to try. And the only way that will happen is if one of you guys either knows what this code is and what to do about it or has another approach to getting my etf files back.
I would appreciate any input you might offer. I want to finish messing with this phone one way or another--my struggling Note 4 is waiting in the wings!:laugh:

Soft bricked. phone not coming back

Okay so my phone was acting up a little where it was working fine and after a few days apps would start crashing so I would reflash the ROM I was using and it would be fine again for a few days and then it would happen again.
So I decided ill just go back to full stock and I went through the path of using the MSMdownloadtool.
So I put my phone into download mode and restored it. the first strange thing is when it was fully complete the device wouldnt reboot. it would seemingly go off and then default back to download mode and then the software would try and redo the process again even though it succeed.
So anyway I unplugged the device and booted it up. It got to the OOS boot animation and it just kept going and never booted. so I booted to Fastboot and flashed TWRP Blu-Spark and it just shows "Failed to mount '/system' (Invalid Arguement" (It shows it for cache, data etc.. aswell) and it also says "Updater process ended with ERROR: 7" when I try to flash anything.
Ive done this entire process like 5 times and it seems like no matter what i do I just cant get my phone booted into anything. Also whenever I turn my device off it seems to enter download mode as it shows up on my PC under COM connections and it takes holding down the power button for ages for it to come out of it
Am I screwed. thanks

LJAM96 said:
Okay so my phone was acting up a little where it was working fine and after a few days apps would start crashing so I would reflash the ROM I was using and it would be fine again for a few days and then it would happen again.
So I decided ill just go back to full stock and I went through the path of using the MSMdownloadtool.
So I put my phone into download mode and restored it. the first strange thing is when it was fully complete the device wouldnt reboot. it would seemingly go off and then default back to download mode and then the software would try and redo the process again even though it succeed.
So anyway I unplugged the device and booted it up. It got to the OOS boot animation and it just kept going and never booted. so I booted to Fastboot and flashed TWRP Blu-Spark and it just shows "Failed to mount '/system' (Invalid Arguement" (It shows it for cache, data etc.. aswell) and it also says "Updater process ended with ERROR: 7" when I try to flash anything.
Ive done this entire process like 5 times and it seems like no matter what i do I just cant get my phone booted into anything. Also whenever I turn my device off it seems to enter download mode as it shows up on my PC under COM connections and it takes holding down the power button for ages for it to come out of it
Am I screwed. thanks
Click to expand...
Click to collapse
Try the other versions of TWRP too, including the official.

tnsmani said:
Try the other versions of TWRP too, including the official.
Click to expand...
Click to collapse
Ive tried a modified TWRP, Blu-Spark and the latest official TWRP from their website and I still get failed to mount on all of the partitions.
When I look at any of the partitions it says
"/system File system: ext4 . Present: Yes . Removable: No . Size: 2913MB . Used: 4MB . Free: 2909MB . Backup Size: 4MB" I tried to change the file system but cant mount. any of them to even format" I get an ERROR code 8 if I try to repair the partition
If I try to flash anything I get "E1001: Failed to update system image" "Updater: process ended with ERROR: 7"