Hello xda teams
My name is Dereje even i don't know how and where i started about my phone problems, first I trying to open but it will start again off frequently then I trying to reboot again it will not then I decided to make flash by using ODIN again not even ODIN successfully completed all the threads but when I tried to reboot it says....
E: Error in /cache/recovery/log (I/O error0
# Manual mode v1.0.0#
----Applying multi-csc....
Applying the csc-code :EGY
successfully applied multi-csc.
successfully verify for dmverity hash tree
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: can't mount /cache recovery/last kernel manual
E: Can't open /cache /recovery/ last kernel manual
E: faild to find /misc partition.
this is it so please help me how to fix this problems.
my phone model is J7 (2016) SM-J710F
Thanks a lot
Related
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (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_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_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
djillusion954 said:
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (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_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_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
Click to expand...
Click to collapse
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
beekay201 said:
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
Click to expand...
Click to collapse
MRA56K factory image???????????? what is that and where can I find it???
Maybe the op meant to say mra58k?
Hey. So, same problem here (same errors), but a faulty power button caused the reboot in the middle of the update.
Replaced the power button but now can't flash anything since my USB debugging was off (unrooted- from day one just auto-updated).
Can I do something or I'm screwed? we don't have here google services and I bought the device from US (google store website).
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
Just this morning as i put on my phone ,it went on upgrading but couldn't finished and cant resurrect any longer it seems like a joke as i did every thing but no avail i quite for that day...Have to use my SD card to wake it and now this what i "ve got.... Although is not a rooted device, flashed firmware KIES also with CWM/TWRP but this report still exist please someone give me a hand.
E: Failed to mount /cache (Invalid argument)
Can't mount '/cache '(Invalid argument)
E: Can't mount /cache/recovery/Last_recovery
E: Failed to mount /data (Invalid argument)
E: Can't /data/log/recovery_log . txt
E: Can't mount /cache/recovery/last_locale
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed to mount /cache (Invalid argument)
I'm spanish speaking so I translate everything with google hehe
You will see I have a Huawei P10 lite WAS-LX3 with EMUI and android 8.0.0
I have opened the bootloader to root with TWRP and even there I guess
use TWRP v. 3.2.1 if I'm not wrong, since it was the only one that Huawei Multi tool accepted, I suppose that by updating recently
download Magisk v16 to root it (I am a new medium in this, some time ago I did it with a much easier j1) to be able to flash it with twrp but I get the following error (it even seems to have errors in previous processes, I get this:
Failed to mount ´/cache´ (invalid argument)
Failed to mount ´/data´ (invalid argument)
Unable to recreate /data/media Folder.
Updating partition details...
Failed to mount ´/cache´ (invalid argument)
Failed to mount ´/cust´ (invalid argument)
Failed to mount ´/data´ (invalid argument)
Failed to mount ´/system´ (invalid argument)
Failed to mount ´/vendor´ (invalid argument)
.. done
Unable to mount storage
Failed to mount ´/data´ (invalid argument)
Full SELinux support is present.
E:
unable to mount/data7media/TWRP/.twrps
Installing zip file ´/external_sd/Maigsk-v16.0.zip´
Checking for digest file...
Skipping digest check: no digest file found
***Magisk v16.0 installer***
!unable to mount partitions
- unmounting partitions
updater process ended with error: 1
error installing zip file ´/external_sd/Magisk-v16.0.zip´
Updating partition details...
Failed to mount ´/cache´ (invalid argument)
Failed to mount ´/cust´ (invalid argument)
Failed to mount ´/data´ (invalid argument)
Failed to mount ´/system´ (invalid argument)
Failed to mount ´/vendor´ (invalid argument)
...done
sorry if it was much, but I'm new I do not know if I can upload ss
but that is all the process history that I get when I want to install magisk
something similar I get with super your v2.82
help, I would really like to have the root access but with neither one of them allows me to install them and I really do not know what to do
This is a year old but may still work:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
(Google is your friend)
I can use every rom just fine. However, I need to flash stock rom but when I boot to stock rom it says "No Command". After a minute or so, the screen changes to installing system update, which flashes to black every second.
Stock firmware that I flashed is "J710MNUBS4CSF1_J710MNICE4CSD4_J710MNUBS4CSG2_HOME.tar.md5"
When I press Power + Vol up in the "No command" screen, this is what the text reads:
apping: device or resource busy
E:[libfs_mgr]Couldnt create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE: [libfs_mgr] Error creating device mapping: device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E: [libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rwE:failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: can't open /cache/recovery/log: (invalid argument)
E: failed to mount /cache/ (invalid argument)
E: can't mount /cache/recovery/last_log
E: can't mount /cache/recovery/last_log: invalid argument
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install:invalid argument