HI,
i have Nexus 7 2013 wifi 32gb, stuck on erasing, aventually comes up as dead android, showing me info:
Android system recovery <3e> LMY470
E:failed to mount /data (Invalid argument)
E:can't mount / cache/recovery log
E:can't open / cache/recovery log
E:failed to mount /data (Invalid argument)
E:can't mount / cache/last_log
E:can't open / cache/last_log
E:failed to mount /data (Invalid argument)
E:can't mount / cache/last_install
E:can't open / cache/last_install
E:failed to mount /data (Invalid argument)
E:can't mount / cache/last_kmsg
E:can't open / cache/last_kmsg
E:Failed closing/dev/block/platform/msm_sdcc.1/by-name/misc(I/0 error)
E:failed to mount /data (Invalid argument)
i have tried to apply update via Nexus root kit, tablet will stuck on "unlock bootloader".
what can i do here do rescue my tablet? can anyone point me at right direcion please?
thanks in advance
UPDATE:
tried to applyupdatefrom ADB again.
PS C:\Users\Katy\Desktop\platform-tools> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
katyr said:
HI,
i have Nexus 7 2013 wifi 32gb, stuck on erasing, aventually comes up as dead android, showing me info:
Android system recovery <3e> LMY470
E:failed to mount /data (Invalid argument)
E:can't mount / cache/recovery log
E:can't open / cache/recovery log
E:failed to mount /data (Invalid argument)
E:can't mount / cache/last_log
E:can't open / cache/last_log
E:failed to mount /data (Invalid argument)
E:can't mount / cache/last_install
E:can't open / cache/last_install
E:failed to mount /data (Invalid argument)
E:can't mount / cache/last_kmsg
E:can't open / cache/last_kmsg
E:Failed closing/dev/block/platform/msm_sdcc.1/by-name/misc(I/0 error)
E:failed to mount /data (Invalid argument)
i have tried to apply update via Nexus root kit, tablet will stuck on "unlock bootloader".
what can i do here do rescue my tablet? can anyone point me at right direcion please?
thanks in advance
UPDATE:
tried to applyupdatefrom ADB again.
PS C:\Users\Katy\Desktop\platform-tools> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
Click to expand...
Click to collapse
Hi, if you're getting an error where "adb" is not recognized, it means its not installed on your PC
There's a generic guide here on how to install it
https://www.xda-developers.com/install-adb-windows-macos-linux/
Since the toolkit uses ADB and fastboot to communicate to the tablet (unlock the bootloader), there's a good chance it's failing due to the drivers not being installed on your computer
poondog said:
Hi, if you're getting an error where "adb" is not recognized, it means its not installed on your PC
There's a generic guide here on how to install it
https://www.xda-developers.com/install-adb-windows-macos-linux/
Since the toolkit uses ADB and fastboot to communicate to the tablet (unlock the bootloader), there's a good chance it's failing due to the drivers not being installed on your computer
Click to expand...
Click to collapse
Thanks a lot for your reply! That would make a lot of sense. I am not sure if I installed them or not but I will give it a go today. Fingers crossed!
it doesnt power on now. battery is 100%. i swapped to different (working) logic board, loading no problem. swapping back to faulty, no power
Related
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
So i recently bought a nexus 7. I Unlocked bootloader using fastboot. Rooted. Installed CWM. Now i was trying to flash CM12. But then when i go to CWM and try to wipe/Flash ROM, I get the following message:
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 unable to open ums lunfile (no such file or directory)
E:failed to mount /sdcard (file exists)
E:failed to mount /sdcard (no such file or directory
I tried everything i can do, such as wiping everything using fastboot, changing recovery, using toolkits, but none of them worked. I think this is my last chance to get help. I hope i get this solved.
Try flashing manually?
Hello,
I am trying to load CyanogenMod onto my Nexus 7 2013 (WiFi) via this guide: wiki.cyanogenmod[.]org/w/Install_CM_for_flo
I have successfully flashed the recovery partition (ClockWork Mod 6.0.4.7). However, when I boot into CWM, I am greeted with these errors:
Code:
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (no such file or directory)
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
E:Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (no such file or directory)
I attempted to load CyanogenMod via the "push and install method", which entails mounting the /data partition. CWM errored out when trying to mount any of the following partitions:
Code:
Error mounting /system!
Error mounting /data!
Error mounting /cache!
So instead, I tried the sideloading method ("adb sideload nightly.zip"), and CWM spit back a bunch of mounting/filesystem errors:
Code:
Restarting adbd...
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
Patching system unconditionally...
failed to open /dev/block/platform/msm_sdcc.1/by-name/system: No such file or directory
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Can anybody help me out with this? Thanks!
Update:
I just tried TWRP (2.8.6.0) as an alternative to Clockwork Mod. FYI, my device is currently running stock Android 5.1 Lollipop, if that makes a difference.
I received the following errors:
Code:
E:Unable to find partition size for /boot.
E:Unable to find partition size for /recovery.
E:Unable to find partition size for /misc.
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data/' is not present!
E:Unable to mount /data.
E:Unable to find partition size for /sb11.
More similar mounting issues. Any idea what the problem could be?
Is TWRP 2.8.6.0 not compatible with Android 5.1? (Build: LMY47O)
Resolved -- Use TWRP MultiRom
I had the same issue on a number of new Nexus 7 2013 wifi devices. Turns out Google had made some firmware updates, rendering new N7 devices incompatible with KitKat stock images.
I resolved it by flashing a custom TWRP build (the MultiRom build) onto these devices. Here's the download links that someone uploaded. You need to be familiar with using fastboot on nexus 7 devices in order to flash these onto the recovery partition:
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view
As a refresher, after booting into fastboot mode (hold VolDn+Power), type 'fastboot flash recovery TWRP_multirom_flo_20150328.img'
(Thanks to csmnn for posting the original solution here: https://www.reddit.com/r/cyanogenmo...ng_cyanogenmod_onto_nexus_7_2013_wifi/cscxb93 and to masterchiefb117 for uploading the files in this forum post: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562)
Errr... This the Galaxy Nexus forums, not Nexus 7.
Sent from my Nexus 5 using Tapatalk
Hi Everyone,
I am stuck, I have exhausted all options I know and searched thru the internet and nothing that has helped me, so I am posting my problem here.
I have Nexus 7 (2013) LTE version, Its completely stock, locked bootloader and stock rom. My parents use it.
On try to start the tablet it stays stuck with Google written on the screen, I went into the recovery, The cache partition is not mounting
this is the message on 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)
E:Can't mount /cache/recovery/ last_kmsg
E:Can't open /cache/recovery/last_kmsg
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
E:failed to mount /cache (Invalid argument)
It no longer has warranty
I tried to unlock the bootloader so I could flash the rom, but the moment it just shows the message when you first unlock the bootloader...
on the computer it shows erasing userdata and stays stuck there for a long time and it times out. I cant flash a new rom as the bootloader is locked.
I tried to sideload thats not working.
I have a feeling EMMC is gone.
Can I buy the main board and fix this? Or anything else that I can do?
Thanks in Advance
My phone is Samsung galaxy note II GT-N7105T
Phone is stuck at Samsung galaxy note II GT-N7105T logo
can start the phone in download mode and in recovery mode.
When I start the phone in recovery mode i get the following errors:
E: failed to mount /system (No such file or directory)
E: Can´t mount /system(No such file or directory)
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/command
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
# Manual Mode#
Applying Multi-CSC....
E: failed to mount system (No such file or directory)
Can´t mount ' /system ' (No such file or directory)
E: failed to mount /data (No such file or directory)
Can´t mount '/data ' (No such file or directory)
E: failed to mount /system (No such file or directory)
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/log
E: Can´t open /cache/recovery/log
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_install
E: Can´t open /cache/recovery/last_install
I have tried to wipe cache partition and do a data/factory reset, but without any luck.
When i try to do a data/factory reset it says:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p16
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
I hope someone here can tell me what I can try out to fix it, since I have no clue what caused this or what I can do about it. Flashed Samsung note 2 Stock rom with ODIN many times and used different version of but didn't work.
The stock rom doesn't flash in Odin? If not, what is the Odin error?
audit13 said:
The stock rom doesn't flash in Odin? If not, what is the Odin error?
Click to expand...
Click to collapse
Whenever i flash stock firmware with odin is shows green and pass but the phone is still stuck at Galaxy note 2 logo and the recovery still shows the above error.
got the same problem wiht not fail odin
got the same problem with fail odin
RP SWREV: A2
has been shown
After flashing the full rom, did you do a factory reset before booting the stock rom for the first time?
audit13 said:
After flashing the full rom, did you do a factory reset before booting the stock rom for the first time?
Click to expand...
Click to collapse
Whenever I open recovery i get failed to mount system data ......... So performing full data wipe is useless. I have tried.
abood101 said:
RP SWREV: A2
has been shown
Click to expand...
Click to collapse
NO it does not show that error.