Good morning,
I have a nexus 7. my tablet makes bootlooping, I tried to remove the cache, but nothing works, always the same answer :
Supported API: 3
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)
E:failed to mount /cache (Invalid argument)
and when I use the option "Wipe cache partition" or "Mount /system"
the tablet answers :
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)
E:failed to mount /cache (Invalid argument)
and
E:failed to mount /system (invalid argument)
so if you can help me
rcraftgamers said:
Good morning, I have a nexus 7. my tablet makes bootlooping,.....
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2051789
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Related
My phone somehow got stuck in a boot loop and I can't fix it. I don't know what to do. I cant get pass the start up animation no matter what I do.
I've tried the fast boot commands to flash and keep getting the error (i dont really know alot about flashing and never done it before but the that what i found suggested in the web..)
FAILED < remote: flash write failure >
I've tried the flash-all.bat file, but the lock state goes back to LOCKED when it reboots the device and I get the error
not supported on lock device
I can unlock the device when I type fastboot oem unlock, but if the device is restarted it goes back to LOCKED.
I've tried recovery mode and I see the below statements:
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
E:failed to mount /cache (Invalid argument)
I've tried wipe data/factory reset
--Wiping data...
Formatting /data...
E:failed to mount /cache (Invalid argument)
Formatting /cache...
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
Data wipe complete
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
E:failed to mount /cache (Invalid argument)
It sounds like your emmc is fried. not being able to lock/unlock your bootloader is a classic symptom
Sent from my Nexus 5 using XDA Free mobile app
and what do i do with that?
yyelf said:
and what do i do with that?
Click to expand...
Click to collapse
Get a new device/motherboard swap
thanks....:crying::crying::crying:
noob here. long time reader, first time poster. first off, you have a fantastic site that has educated me immensely, and allowed me to properly root many devices.
now onto my problem. i have a galaxy s4 4.4.4 i337 (NOT rooted at the time) that unfortunately went belly up the other day with the seemingly typical message of "...data corrupted....perform factory reset...". after a number of restart attempts, including pulling the battery, i decided to check out the recovery mode. it had an image of a passed out android with a statement No command right below it. before undertaking the reset, i chose the reboot system now from the menu on the upper left which resulted in No command changing to Error! while the following entries appeared (exactly as shown, including the repeat statements) at the bottom in red:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_last_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/emmc_checksum_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
i could not find any suggestion other than to reset, so i went ahead with it. everything seemed to be fine afterwards and i was event able to root it. at some point, however, i decided to revisit the system recovery screen, only to be greeted by the passed out android image with No command below it! whatta?! when i selected reboot system now menu, No command once again changed to Error!, but nothing appeared at the bottom this time around, and the phone booted up without a problem. i reset the phone one more time, but it still continues to exhibit the same exact behavior as i have described. the phone itself seems to be functioning properly, yet i cannot let go of the fact that something is still not kosher under the hood, especially since it died on me so suddenly. please help! thank you.
Mr Bottomtooth said:
noob here. long time reader, first time poster. first off, you have a fantastic site that has educated me immensely, and allowed me to properly root many devices.
now onto my problem. i have a galaxy s4 4.4.4 i337 (NOT rooted at the time) that unfortunately went belly up the other day with the seemingly typical message of "...data corrupted....perform factory reset...". after a number of restart attempts, including pulling the battery, i decided to check out the recovery mode. it had an image of a passed out android with a statement No command right below it. before undertaking the reset, i chose the reboot system now from the menu on the upper left which resulted in No command changing to Error! while the following entries appeared (exactly as shown, including the repeat statements) at the bottom in red:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_last_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/emmc_checksum_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
i could not find any suggestion other than to reset, so i went ahead with it. everything seemed to be fine afterwards and i was event able to root it. at some point, however, i decided to revisit the system recovery screen, only to be greeted by the passed out android image with No command below it! whatta?! when i selected reboot system now menu, No command once again changed to Error!, but nothing appeared at the bottom this time around, and the phone booted up without a problem. i reset the phone one more time, but it still continues to exhibit the same exact behavior as i have described. the phone itself seems to be functioning properly, yet i cannot let go of the fact that something is still not kosher under the hood, especially since it died on me so suddenly. please help! thank you.
Click to expand...
Click to collapse
bump
verifying internal MMC block
not need checksum confirmation already executed
E: failed to mount /data (invalid argument)
E: can't mount /data/fota/ipth-muc.prop
E: failed to mount /efs (invalid argument)
E: failed to mount /system (invalid argument)
# MANUAL MODE #
E: failed to mount /data (invalid argument)
E: failed to mount /system (invalid argument)
john-ammu said:
verifying internal MMC block
not need checksum confirmation already executed
E: failed to mount /data (invalid argument)
E: can't mount /data/fota/ipth-muc.prop
E: failed to mount /efs (invalid argument)
E: failed to mount /system (invalid argument)
# MANUAL MODE #
E: failed to mount /data (invalid argument)
E: failed to mount /system (invalid argument)
Click to expand...
Click to collapse
Hello,
What device do you have?
___
v7
XDA Assist
v7 said:
Hello,
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HI,
i have 2 devices they have little bit similar issues
SHV-E120L
and SCH-i535
So...I'm a little bit of a newbie when it comes to fixing technology, so I hope to be as clear as possible. All of a sudden my Samsung Galaxy s4 died few hours ago. It would just boot and get stuck at the "Samsung Galaxy s4 GT-I9505" screen (If I plug it to charge it remains stuck at the screen where the battery is grey and it has a white circle in it). Before that it normally booted up for like 20-30 seconds. Then it rebooted that way. Now, I can get to recovery mode, and what I get is the following text when entering:
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (invalid argument)
can't mount '/system' (invalid argument)
E:failed to mount /cache (invalid argument)
can't mount '/cache' (invalid argument)
E:failed to mount /cache (invalid argument)
E:can'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 /system (invalid argument)
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 didn't perform any root or flashing since I barely know what they are, I tried an emergency recovery and initialization with Kies by booting the phone into download mode but it says that my phone doesn't support it, which is weird. How big of a problem is this? I brought the phone to a local technician which said I should contact Samsung assistance because "the internal memory is gone" (as for damaged, I assume) but I don't think it can be right since again, I booted it up in the morning and for 30 seconds it was perfectly fine, I am thinking more of a corruption, somehow, of the files. Is there any way I can get out of this state? Can I recover any data from it? I underestimated the situation and I've never done a backup of the phone sadly... If it can help, when this happened I was on firmware 4.4.2. Thanks in advantage for any reply.
dariomrk said:
Do you have your warranty? I suppose that the hardware is damaged. In that case you will probably need a motherboard replacement.
Click to expand...
Click to collapse
Phone was bought in November 2013 so I suppose it's not eligible for warranty replacement
CrashRatchet008 said:
So...I'm a little bit of a newbie when it comes to fixing technology, so I hope to be as clear as possible. All of a sudden my Samsung Galaxy s4 died few hours ago. It would just boot and get stuck at the "Samsung Galaxy s4 GT-I9505" screen (If I plug it to charge it remains stuck at the screen where the battery is grey and it has a white circle in it). Before that it normally booted up for like 20-30 seconds. Then it rebooted that way. Now, I can get to recovery mode, and what I get is the following text when entering:
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (invalid argument)
can't mount '/system' (invalid argument)
E:failed to mount /cache (invalid argument)
can't mount '/cache' (invalid argument)
E:failed to mount /cache (invalid argument)
E:can'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 /system (invalid argument)
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 didn't perform any root or flashing since I barely know what they are, I tried an emergency recovery and initialization with Kies by booting the phone into download mode but it says that my phone doesn't support it, which is weird. How big of a problem is this? I brought the phone to a local technician which said I should contact Samsung assistance because "the internal memory is gone" (as for damaged, I assume) but I don't think it can be right since again, I booted it up in the morning and for 30 seconds it was perfectly fine, I am thinking more of a corruption, somehow, of the files. Is there any way I can get out of this state? Can I recover any data from it? I underestimated the situation and I've never done a backup of the phone sadly... If it can help, when this happened I was on firmware 4.4.2. Thanks in advantage for any reply.
Click to expand...
Click to collapse
Greetings and welcome to assist. It sounds like your partition table is corrupt, can you get into download mode ? If you can try kies/smartswitch emergency firmware recovery
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. It sounds like your partition table is corrupt, can you get into download mode ? If you can try kies/smartswitch emergency firmware recovery
Good Luck
Sawdoctor
Click to expand...
Click to collapse
As I mentioned in the OP, I already tried the emergency firmware recovery, but both Kies, Kies 3 and SmartSwitch claim that the phone is not eligible for the emergency recovery. Of course, I tried performing these operations by entering in download mode and then connecting the phone to the pc to perform the operation but no luck so far. Other options? Do I need to flash a new firmware?
CrashRatchet008 said:
As I mentioned in the OP, I already tried the emergency firmware recovery, but both Kies, Kies 3 and SmartSwitch claim that the phone is not eligible for the emergency recovery. Of course, I tried performing these operations by entering in download mode and then connecting the phone to the pc to perform the operation but no luck so far. Other options? Do I need to flash a new firmware?
Click to expand...
Click to collapse
Try this thread, if the firmware doesn't work you could try mskips toolkit, that has an emergency firmware recovery. As a last resort you could flash a pitfile
https://forum.xda-developers.com/showthread.php?t=2751515
Good luck
Sawdoctor
Hi to everyone,
I would like to ask for your help, i want to restore a motorola xoom tablet for my nephew. But trying to restarod i found an error with the TWRP Recovery 3.0.2 at the moment to wipe the /data & /cache partitions pops this errors.
Failed to mount "/data (invalid argument)
unable to recreate /data/media folder.
Updating partition details...
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
...done
Unable to mount storage
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
kernel does not have support for reading SELinux contexts.
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
Unable to mount /data/media/TWRP/ . twrp
MTP Enable
Failed to mount "/data (invalid argument)
Failed to wipe dalvik
updating partition details...
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
...done
unable to mount storage
I already try to install the rom.zip but i got stuck in the bootscreen logo. Looking in different blogs and forum i try the "Change file system" method to convert from ext4 to fat and go back to ext4 but it gave me the same error.
Thank you for the time to read me and to the incoming answers that i can get from all of you.