Help to ASUS K00E - Asus Fonepad 7

I have here a tablet of the brand asus that does not boot and does not pass the boot and wanted to know how to get firmware and restore because it only boots in recovery mode
IFWI Version: 54.57
S/N: DAOKCT013060
Image Version: 7.6.0.0
Droidboot Version: 2.0
Product: K00E
Security: 1
It gives an error
E: failed to mount /cache (invalid argument)
E: Unable to mount /cache! we skip check debricking
E: failed to mount /cache (invalid argument)
E: Unable to mount /cache! we skip check debricking
FASTBOOT INIT...
Someone can help me
Try Factory Reset
E: failed to mount /cache (invalid argument)
E: Unable to mount /cache! we reformat now!
E: Format COMPLET.
E: failed to mount /cache (invalid argument)
E: Unable to mount /cache! give up!
Result: FAIL (problem with write cache command!)

I know it's too late! but I have the same problem.
Did you fix it?

Me too, any news on the topic?

I don't have Droidboot any more but it still alive because I can plug it as cloverview. Now I need the debrick files. I can't find all the files in the firmware (zip/raw)!

Related

[Q] Cannot mount bricked nexus 7 2013 storage

Hello all,
I'll give a quick introduction of what my situation is, and then my problem:
I have a Nexus 7 32g wifi model with:
Product name - flo
Variant - flo 32g
HW version - rev_e
Bootloader version - flo-04.02
Carrier info - none
signing - yes
secure boot - enabled
LOCK STATE - locked
All of the following attempts are made by my macbook air - I can try with my windows machine but I personally do not think that this will help. please tell me if you believe that using a windows machine will fix it and I will go with it.
Recently I was using my nexus as an ftp server and was transferring some videos to it. when I left the shower I noticed it was stuck on the google logo, so I left it in case it was frozen etc. I then went to work and came back around 11 hours later to see it on the same logo (it was charging so naturally didn't run out of battery and go to a blank screen).
I therefore decided to see what was going on, clearly it wouldn't boot. I went into the boot loader and also successfully went into recovery mode. Following some instructions from google, the first thing to do was to wipe the cache partition. This returned the following:
--Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache
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
Cache wipe complete.
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)
Click to expand...
Click to collapse
When I tried to wipe the data, it returned the following:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
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
Data wipe complete.
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)
Click to expand...
Click to collapse
Following this I tried the 'apply update from ADB' option and this also was unsuccessful. After adb sends the image (and I've tried a few such as the stock one from google and CM10) to the nexus 7, my nexus says the following:
Now send the package you want to apply
to the device with "adb sideload <filename>"...
E: failed to mount /cache (Invalid argument)
E: failed to set up expected mounts for install; aborting
Installation aborted.
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)
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)
Click to expand...
Click to collapse
I returned to google to see what I can find and, although I can't find an identical situation to mine, I saw suggestions to unlock the bootloader, so I used fastboot with the following command:
./fastboot oem unlock
Click to expand...
Click to collapse
My terminal was stuck on "erasing userdata" for a very long time. judging by some of the screenshots I've seen, this shouldn't take more than a couple of minutes - I waited approximately 2 hours and then restarted my nexus.
I think it's worth mentioning that fastboot can see my device (matching my serial no) but running the adb devices command shows nothing under the list of devices. I have also tried to flash a recovery image, but this was also unsuccessful. I know there's a flash.bat file as part of the stock compressed folder, however I haven't touched that yet.
As a result, I think that the issue is with my storage and that it is not mountable. I may be incorrect here but I tried to remount the device through ADB - as mentioned above however, it can't detect the device so this never worked. I do not know how to get mount this using fastboot (I took a look at fastboot help but didn't find anything for that) so I'm not sure where to go now.
I believe that my device is now out of warranty (or very close to it) and I don't think the department store I purchased this from would help me so I'd rather not go down that route.
I hope the information I gave above was sufficient and I'd appreciate any input you have for this. I'm pretty average at terminal commands and have a good understanding of Unix, however I'm not an expert, so excuse me if I'm missing something that is under my nose.
Many thanks,
Ehab
Have you tried different USB cables? USB ports? Check if there is an update for the sdk available? If all else fails, try the Windows machine.
I was using the Twitter app and then my N7 rebooted. Now I have the same error on my device!
Do you think the internal drive is dead?
I need to check my warranty now!
Hello all,
So I tried the above but no success. This leads me to believe even further that it's an issue with unmounted storage. Has anyone had anything like this?
Thanks,
Ehab

Stuck at the Samsung logo

Hey guys, so my girlfriend's S4 mini won't turn on and its stuck on the Samsung booting logo. I did a hard reset, but with no luck, wiping the cache didn't help either. I flashed a stock rom with but that also didn't work. When i enter recovery mode this is what I get:
did not match sized ' /system/csc/common/system/csc/others.xml ' (No data available)
E: failed to mount /cache (Invalid argument)
can't mount '/cache' (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: Cab't mount /cache/recovery/last_recovery
E: failed to mount /data (Invalid argument)
E: Can't mount /data/log/recovery_log.txt
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)
Click to expand...
Click to collapse
mlakov said:
Hey guys, so my girlfriend's S4 mini won't turn on and its stuck on the Samsung booting logo. I did a hard reset, but with no luck, wiping the cache didn't help either. I flashed a stock rom with but that also didn't work. When i enter recovery mode this is what I get:
Click to expand...
Click to collapse
I have bad news for you. If none of those methods that you tried worked, it probably means you have a fried storage which is probably the cause of the Recovery not being able to mount the partitions as it cannot find any.
Sayrian said:
I have bad news for you. If none of those methods that you tried worked, it probably means you have a fried storage which is probably the cause of the Recovery not being able to mount the partitions as it cannot find any.
Click to expand...
Click to collapse
So i should replace the motherboard ?
mlakov said:
So i should replace the motherboard ?
Click to expand...
Click to collapse
That could be one solution, however, What problem are you encountering while flashing a stock OS?
Sayrian said:
That could be one solution, however, What problem are you encountering while flashing a stock OS?
Click to expand...
Click to collapse
I flash stock os without encountering problems, but the phone still doesnt turn on
mlakov said:
I flash stock os without encountering problems, but the phone still doesnt turn on
Click to expand...
Click to collapse
Have you tried to flash a custom recovery to see if that does the trick?
I flash a custom recovery but when i go in recovery mode it takes me to the stock recovery

Help Me, My Phone Huawei Ascend P6 Stuck on Logo, wipe Recovery mount failed

Hi, XDA community
When trying to wipe, stock recovery prompted:
Code:
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument)
What solutions ann Tutorial fastboot?

Unable to mount storage in TWRP, unable to open '' to wipe crypto key

Hello everybody,
I'm facing an issue with my phone. I was running Fulmics Rom 6.1 on my LG G3 for a few days, when, this morning, I woke up to find my device caught in a bootloop. I had a recent TWRP backup, so I tried to restore it, but it failed with the error : "Unable to wipe System".
I tried to wipe everything but my SD Card and got :
Code:
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
I tried to use "Format Data" in TWRP Wipe Section, but got :
Code:
[B]Unable to open '' to wipe crypto key[/B]
Unable to wipe Data.
[B]Unable to format to remove encryption.[/B]
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Flashing the Rom again fails as well as it stays stuck at this step :
Code:
Install new system
Extract:/tmp/unpackbootimg
I'm using TWRP 3.0.0-0.
Any idea about what I could do next ?
Thanks a lot.

asus z00ud bootloop (unable to mount /asdf)

after a normal restart my phone get stuck in a bootloop.
i've restarted in rescue mode to wipe data/factory reset but when i've tried i receive this error message:
formatting /data
formatting /cache
E: failed to mount /asdf (invalid argument)
E: can't mount /asdf/recovery/last_log
E: can't open /asdf/recovery/last_log
data wipe complete
E: failed to mount /asdf (invalid argument)
E: can't mount /asdf/recovery/last_log
E: can't open /asdf/recovery/last_log
i've download the stock firmware WW_21.40.0.1999 and with fastboot i've flash recovery, boot and system but i've get the same error. i've also tried to apply the firmware via sd card and adb but i get the same error
i've boot lock and usb debug not active.
some ideas?
tnx in advance and forgive my bad english
Same problem
I have this problem too. How to fix thjs?!

Categories

Resources