Hi threre,
Yesterday, my WhatsApp kept crashing so I decided to reboot my stock Nexus 4 (4.4.4). Now my phone is stuck in a boot loop. I have access to the recovery menus.
The first thing I tried was wiping my cache. When I open the Android system recovery There is already an error on the bottom half of the screen.:
Code:
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/log
E: Can't open cache/recovery/log
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
)
I have tried wiping the data and cache partitions but when I do that the same errors as above fill up my entire screen and it does not help anything at all.
Next thing I tried was to flash a stock image using this thread http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312. Since I am posting here you can probably guess that this did not work as well.
The problem is that my device is not rooted, and I can not get my bootloader to stay unlocked after a reboot. I have the bootloader drivers installed on my Windows 8.1 pc using the advanced reboot method so I have access to my phone in cmd. fastboot oem unlock does seem to work at first since the "'LOCK STATE" turns to UNLOCKED, but when I do the required reboot for flashing images it turns back to locked.
Perhaps this is a symptom of a bigger cache problem?
I am definitely not a pro at this but I have some experience with rooting phones from my Samsung Galaxy S II.
I really hope that anybody knows an answer other then try you warranty plan because then I will not have my phone for 5 days or more and I am not sure whether they really can fix this...
Lastly, here is the information displayed in my fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16 GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAKOZ30d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1701.03
CARRIER INFO - None
SERIAL NUMBER - xxx wil post this if nescesarry
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Thanks in advance!
If you can't lock the bootloader that is a symptom of your emmc flash memory failure. Afraid there isn't much you can do. Are you still under warranty?
Sent from my Nexus 5 using XDA Free mobile app
I still have warranty but I'm a little worried that they will complain about the damage (unrelated to the crash) of my phone. Is there no way of repairing the flash memory?
SM-G530t FRP LOCK - Stuck at Galaxy Splash screen
Hi All, Im really stuck here. I have ODIN installed on my phone and have tried to install every ROM and image out there and am having trouble with the FRP . I need to unlock it to install a stock rom image ... i have tried the kies method, the smart switch method and they all run fine, but my e: partition is hosed
tried OF8_full.tar.md5
result to android system recovery <3e>
lmy47x.g530tuvu1a0f8
reboot system now
apply update from adb
" from external storage
" from cache
wipe/factory reset
wipe cache partition
reboot to boot loader
power down
recovery logs
--------------------------------------------------------------------
E: failed to mount /efs (invalid argument)
e: failed to mount /efs (invalid argument)
e: failed setting up dirty target
dm-verity failed...
e: failed to mount /system
PLEASE HELP WITH THE FRP LOCK WITHOUT BUYING A BOX
this is seriously affecting my business and cutting into my playing Destiny time!!
thanks in advance Mike
Hi guys i am facing a issue in recovery when select reboot i need to see this error E: CANT MOUNT / DATA (invalid argument) in red line and then restarted but this error did nothing to my phone my phone is working normally but curiosity is that what is this error and it is coming to my phone.........i didnt try custom rom or recovery or root on my phone my phone is completely stock
If any one have info regarding this please guide me why i need to see this line in recovery mode
Thanks
Anbody there to help about this
Help! My phone is now stucked on a boot logo. I tried rooting and flashing via odin on Oreo, after then, it stucks on boot loop, on which I know how to fix, going back to stock rom works, but then signal is gone (boot loop wasn't expected, didn't managed to see bandbased version) I then, flashed this: https://forum.xda-developers.com/showthread.php?t=2420881 through odin via AP, which is a wrong method on which I know I am stupid enough, right after then, OS won't boot up but stuck on boot logo, also tried using TWRP and Official Lineage OS 14.1 and the same thing happened, it starts to boot up, it rebooted after a few mins, then it goes back to TWRP.
HELP, I think the wrong method of flashing of this: https://forum.xda-developers.com/showthread.php?t=2420881 file is the mistake, idk what did I messed up with it, it was supposed to be used for EFS restore app not flash through Odin, what should I do? Any OS just stucks on boot logo but download menu and recovery mode (official/twrp) is still there, also the phone is still viable to be flashed.. Please help.. I just got this phone not even 24 hours ago.. Lol, I know stupid me, that I didn't checked the file carefully, I learnt my lesson, criticize me or anything.. But please, help if you can.
I had not known that the Marshmallow, Nougat and Oreo was pretty harder to do things on, I'm quite new with this new OS release, I was pretty confident because I was doing this all over the years (I only know step by step, not really in-depth information). Way back, odin only requires AP, now it requires 4 columns on which I cannot reflash without unchecking the Bootloader.
P.S. Before boot loop starts to happen I tried rooting on Oreo, downloaded my own country region openline version(I am openline, yes) and also tried Lineage OS 14.1, Now, I am trying to download Russia(not my country) Stock Rom Oreo, it might be the case that it doesn't allow me to flash bootloader as this was the downgrade, and I skipped right through it. But I am worrying about the wrong flash file and after the download finishes, the same thing happens and I won't be able to get passed out of boot
EDIT: I've did everything and ODIN works for the flashing the whole columns including bootloader with russian full stock ROM, but its still stuck on boot logo, EFS not detected on recovery. I'm losing hope, this is not recoverable yeah?
Here's the error code on recovery mode:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [Unknown]#
No Suppport SINGLE-SKU
E:Failed to mount /efs (Invalid argument)
File-Based OTA
E:Failed to mount /efs (Invalid argument)
Supported API: 3
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
dm-verify verification failed...
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
... and so on.
E:failed to clear BCB message: failed to find /misc partition
i have this problem too
SM-G9287C version 7.0(I'm sure 'cause she always turn her things to auto-update)
My friend ask me if I could help with her phone.
Problems
1. Doesn't boot - only download mode, only boots when charged.
2. FRP lock
3. usb debugging & oem unlock is not on
What I've done
1. factory reset didn't work.
2. flashed stock firmware - frp locked <-- fk this
3. flashed twrp didn't worked cockblocked by frp again
4. tried to boot in recovery, safe mode, download - only download mode worked.
5. let the phone boot - *goes installing system update, no command(dead android guy), screen goes black text appeared:
About to do:
I haven't done these stuff because I'm not sure on how it will benefit
1. root
2. flash combination file
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /cache (invalid argument)
#MANUAL MODE v1.0.0#
-- Appling the CSC-code: SMA
Successfuly applied multi-CSC
Successfuly 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:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
Any suggestions guys? Any method will do as long as it will make this **** turn on again
1. No time pressure
2. Wiping it all clean isn't a problem