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?
Hello,
I hand need friends because I do not date me.
Phone my friend will not start, I wanted to do in recovery mode a data factory reset to reset it but now, formatting and started to ca lasted for ages until appear full of phrases English course and all this red. I understood that something was going on but what ?? I do not know.
I downloaded the latest rom but Odin shows me a beautiful fail.
I understand only one thing, that memory can not be erased. Why ???
Example:
E: faileid to mount / cache (Invalid argument)
E: cant't mount / cache / recovery / install last
E: Can not open / cache / recovery / last install *
FORMATING / SbF
E: unknown volume for path
And many other lines failed to mount / cache and cant mount
Do you know where can come from these mistakes and are there a way to remedy it
Thank you in advance
so, I have a Oneplus 2 phone that is 5 months old... I wanted to root it so in 10th December, I downloaded and flashed supersu (I have TWRP and bootloader working C: ) but When I rebooted, It was boot looping (does that make sense) so I backed up data and did a factory reset, still the boot loop, so I decided to do an advanced wipe but when I was choosing which to wipe I accidentally wiped the whole internal storage, I realized it later when I rebooted, the boot was not showing up, just the oneplus 2 logo :c
so I decided to download Oxygen OS, GAPPS ARM64 6.0 STOCK.
after downloading them I copied them to oneplus 2 by TWRP (thank god)
then I installed them, after installing, The boot logo was working, when it finally booted it said encryption error: internal storage damaged and some other text
so What should I do?
install a new rom? buy a new phone (hopefully not)
Projonmo112 said:
so, I have a Oneplus 2 phone that is 5 months old... I wanted to root it so in 10th December, I downloaded and flashed supersu (I have TWRP and bootloader working C: ) but When I rebooted, It was boot looping (does that make sense) so I backed up data and did a factory reset, still the boot loop, so I decided to do an advanced wipe but when I was choosing which to wipe I accidentally wiped the whole internal storage, I realized it later when I rebooted, the boot was not showing up, just the oneplus 2 logo :c
so I decided to download Oxygen OS, GAPPS ARM64 6.0 STOCK.
after downloading them I copied them to oneplus 2 by TWRP (thank god)
then I installed them, after installing, The boot logo was working, when it finally booted it said encryption error: internal storage damaged and some other text
so What should I do?
install a new rom? buy a new phone (hopefully not)
Click to expand...
Click to collapse
Go to advanced wipe and format data
Confirm and do not tell me that you have data there. I'm assuming you have already made the necessary backups. This is the only way to fix it
anupritaisno1 said:
Go to advanced wipe and format data
Confirm and do not tell me that you have data there. I'm assuming you have already made the necessary backups. This is the only way to fix it
Click to expand...
Click to collapse
I don't have the backup :c
is there any way to fix it without a backup?
anupritaisno1 said:
Go to advanced wipe and format data
Confirm and do not tell me that you have data there. I'm assuming you have already made the necessary backups. This is the only way to fix it
Click to expand...
Click to collapse
I don't have the backup
halp meh pls
I flashed cm 13, Now in a boot loop :/
I then went to stock rom, still the unsuccessful encryption
sorry I am a noob :c
Projonmo112 said:
I don't have the backup
halp meh pls
I flashed cm 13, Now in a boot loop :/
I then went to stock rom, still the unsuccessful encryption
sorry I am a noob :c
Click to expand...
Click to collapse
Format data
Any solution?
anupritaisno1 said:
Format data
Click to expand...
Click to collapse
I was talking on a phone and suddenly my OP2 got restarted and what I see is "Encryption Unsuccessful".
I don't know what has gone wrong, maybe when on call it just got mistakenly browsed into encryption option or something?
I am on Oxygen OS 3.5.6 and rooted with TWRP 3.0.2-2.
Now whenever I boot my phone it shows
"Encryption unsuccessful
Your phone storage has been damaged, please download the firmware package to brush".
It appears that some part of OS is loaded because when I change the volume the android styled indicator bar and the settings gear appears but nothing happens when I tap it.
I entered TWRP to erase data (again because I'm sure had checked it) and it says (in red):
E:Unable to load '/twres/languages/en-US.xml'
Could not mount /data and unable to find crypto footer.
Failed to mount '/cache' (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)
Full SELinux is present.
Failed to mount '/cache' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
Formatting cache using make_ext4fs...
Failed to mount '/cache' (Invalid argument)
Updating partition details...
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage
When I go to Wipe / Repair File System selecting Data partition it shows me:
Present: Yes
Removable: No
Size 0MB
Used: 0MB
Free: 0MB
Backup Size: 0MB
When I select Internal Storage and tap Repair or Change File System it says Invalid partition selection (in red).
Tried this: https://forum.xda-developers.com/one...oos-3-t3402020
but I am stuck at recovery tool. After clicking the square button it shows ok and then pressing start it starts some procedure and then stuck on something called FirehoseCheckRSPE and some Chinese thing written ahead of it.
https://drive.google.com/file/d/0B_l...ew?usp=sharing
Tried fastboot comands to check whether it works and it does work.
Like when entered comand fastboot devices, it does shows the device.
I tried to flash stock recovery by --> fastboot flash recovery recovery.img
It succeeds like this
target reported max download size of 536870912 bytes
sending 'recovery' (17013 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.086s]
finished. total time: 0.490s
But when i restart to recovery it still shows TWRP.
What should I do?
I just need my phone to work.
Please help me out
I really don't know how it even happened suddenly.
Thank-you in advance.
Hello.
I have a Nexus 7 and doesn't work. The battery gone out and when I turn it on it hangs a screen with Google logo.
I have tried everthing. To enter in bootloader, try to restore the tablet and I have an error:
E: can't open file
E: failed to mount /cache (Invalid argument)
I have tried to reinstall Android from pc, but it hangs the tablet.
Do you know what can I do? I don't mind if I have to delete everything, I just want the tablet works again.
Thank you very much.
Regards.
I'm having issues booting into my innjoo device.
It all started one morning, I woke up and saw some errors on my screen like (android.process has stopped working) I switched off the phone and turned it back on, but it got stuck on the innjoo logo and never booting up.
I decided to boot into recovery, where I encountered a list errors saying
(E: failed to mount /cache - invalid argument)
(E: cant mount /cache/recovery/log)
(E: cant open /cache/recovery/log)
And some other similar errors.
Choosing the wipe cache partition and the factory format option resulted in the same error. Which led me to believe my internal memory may be corrupted somehow (the data partition perhaps).
Is there a fix for this? And does anyone know of a way to correctly partition an Sdcard so it can be bootable and recognised by the device?