Database Info

[Q] Bootloop, Unable to mount '/cache', '/persist', storage

Hi,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cataclysm ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Android is upgrading' present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Checking through the phone's internal storage with TWRP's file manager showed my internal storage as (0MB) and that the sdcard folder was empty. Other folders such as system and sys had subfolders which also were displayed as empty, though I'm not sure if that would be the case on a normally functioning device.
Any help would be appreciated, thanks
EDIT: I tried restarting my phone again after posting and after spending a long period of time at the Nexus boot animation, the 'Android is upgrading' system popup now just flashes through a few messages before 'Unfortunately, Calendar has stopped working.' appears and the phone restarts. Not sure if this happened initially, or if this usually happens, but the phone loops from the Nexus boot animation.

Try fastboot flashing the cache.img from the factory image
---------- Post added at 07:10 PM ---------- Previous post was at 06:53 PM ----------
So, is it working now?

jd1639 said:
Try fastboot flashing the cache.img from the factory image
---------- Post added at 07:10 PM ---------- Previous post was at 06:53 PM ----------
So, is it working now?
Click to expand...
Click to collapse
Problem still exists, just that the phone now boots till the 'Select language' screen before a flood of '[Insert Google app/service] has stopped working.' system popups appear and the phone restarts.
TWRP still shows same messages when trying to factory reset, and file manager still shows 0MB internal storage.
EDIT: Apparently the phone is now boot-looping to the conditions as stated in the OP after trying to factory reset.

Looks like full return to stock then
Sent from my Nexus 5 using Tapatalk

rootSU said:
Looks like full return to stock then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Seems like there's nothing much I can do now anyways... what an unexpected event

exare said:
Seems like there's nothing much I can do now anyways... what an unexpected event
Click to expand...
Click to collapse
Just flash the stock image and see if you still have problems. What do you mean by there's not much you can do?

Quick question: What should I do if a particular img file keeps getting the <remote: flash write failure> error when trying to flash the stock factory images?
jd1639 said:
Just flash the stock image and see if you still have problems. What do you mean by there's not much you can do?
Click to expand...
Click to collapse
I meant in regards to correcting the problem without going back to stock?

exare said:
Quick question: What should I do if a particular img file keeps getting the <remote: flash write failure> error when trying to flash the stock factory images?
I meant in regards to correcting the problem without going back to stock?
Click to expand...
Click to collapse
Not sure I understand. Did you flash the whole factory image and you're getting that error when one of the image files is flashing? If so which image file?

jd1639 said:
Not sure I understand. Did you flash the whole factory image and you're getting that error when one of the image files is flashing? If so which image file?
Click to expand...
Click to collapse
I was following abaaaabbbb63's guide (http://forum.xda-developers.com/showthread.php?t=2513701), but when using the flash-all.bat file I noticed several img files had the <remote: flash write failure> error, thus I tried to do it the 'long way' as stated in the guide, by flashing each image one by one.
radio.img is not able to be flashed, and it is only the second step in the guide...

exare said:
I was following abaaaabbbb63's guide (http://forum.xda-developers.com/showthread.php?t=2513701), but when using the flash-all.bat file I noticed several img files had the error, thus I tried to do it the 'long way' as stated in the guide, by flashing each image one by one.
radio.img is not able to be flashed, and it is only the second step in the guide...
Click to expand...
Click to collapse
Try a different usb port. A usb 2.0 not 3.0 and user the cable that came with your phone

jd1639 said:
Try a different usb port. A usb 2.0 not 3.0 and user the cable that came with your phone
Click to expand...
Click to collapse
Was not using USB 3.0. Tried a different port but same results. I was able to flash the bootloader before this though.

exare said:
Was not using USB 3.0. Tried a different port but same results. I was able to flash the bootloader before this though.
Click to expand...
Click to collapse
Try this
fastboot oem lock. Then reboot into the bootloader. Does it show the bootloader as locked or is it still unlocked?

jd1639 said:
Try this
fastboot oem lock. Then reboot into the bootloader. Does it show the bootloader as locked or is it still unlocked?
Click to expand...
Click to collapse
unlocked. I tried flashing the bootloader again but now it seems to have the write error too.

exare said:
unlocked. I tried flashing the bootloader again but now it seems to have the write error too.
Click to expand...
Click to collapse
I was afraid of that. I think your emmc has gone bad. Sorry to say but you're going to have to rma the device.
---------- Post added at 09:10 PM ---------- Previous post was at 09:03 PM ----------
Can I ask how you rooted your phone?

jd1639 said:
I was afraid of that. I think your emmc has gone bad. Sorry to say but you're going to have to rma the device.
---------- Post added at 09:10 PM ---------- Previous post was at 09:03 PM ----------
Can I ask how you rooted your phone?
Click to expand...
Click to collapse
:crying: do you think I'll be able to get it repaired/refunded considering I have unlocked the bootloader already?
I followed Chromium_'s guide (http://forum.xda-developers.com/showthread.php?t=2507905) and got it rooted by flashing Cataclysm.

exare said:
:crying: do you think I'll be able to get it repaired/refunded considering I have unlocked the bootloader already?
I followed Chromium_'s guide (http://forum.xda-developers.com/showthread.php?t=2507905) and got it rooted by flashing Cataclysm.
Click to expand...
Click to collapse
There have been others who were able to warranty the phone with the bootloader unlocked. Seems Google has been pretty good about that. Just tell them the phone no longer boots which I'm assuming is the case.

jd1639 said:
There have been others who were able to warranty the phone with the bootloader unlocked. Seems Google has been pretty good about that. Just tell them the phone no longer boots which I'm assuming is the case.
Click to expand...
Click to collapse
Okay then. Thanks for all the help!

exare said:
Okay then. Thanks for all the help!
Click to expand...
Click to collapse
No problem, sorry it didn't turn out better. I feel for you

jd1639 said:
I was afraid of that. I think your emmc has gone bad. Sorry to say but you're going to have to rma the device.
---------- Post added at 09:10 PM ---------- Previous post was at 09:03 PM ----------
Can I ask how you rooted your phone?
Click to expand...
Click to collapse
I don't want to sound like a black sheep, but something seems fishy about the emmc on nexus 5 devices
The cause is the method used to unlock/root? Or that casually, most cases are from Junior members that somehow are missing some important things here and there

exare said:
Hi,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cataclysm ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Android is upgrading' present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Checking through the phone's internal storage with TWRP's file manager showed my internal storage as (0MB) and that the sdcard folder was empty. Other folders such as system and sys had subfolders which also were displayed as empty, though I'm not sure if that would be the case on a normally functioning device.
Any help would be appreciated, thanks
EDIT: I tried restarting my phone again after posting and after spending a long period of time at the Nexus boot animation, the 'Android is upgrading' system popup now just flashes through a few messages before 'Unfortunately, Calendar has stopped working.' appears and the phone restarts. Not sure if this happened initially, or if this usually happens, but the phone loops from the Nexus boot animation.
Click to expand...
Click to collapse
Try to
- Fastboot flash recovery recovery.IMG (twrp)
- wipe everything through twrp
- try to fastboot flash stock image

[Q] Cache issue, bricked. please help me. Reward!

Hey guys and gals, I'm having a huge issue with my nexus 5. Today I used the stock recovery to clear the Cache. It looked like it had froze so like an idiot i forced the phone to restart. Now it says my cache partition is messed up and my storage isn't mounted. I also show an unknown base-band so I cant use cell service. I can however still boot my phone up and go into the bootloader screen and also boot it up normally. I looked up and attempted to fastboot the cache.img file back onto the phone, but every time I try I get an error message saying "failed : remote not supported in locked device" something or other like that in the CMD screen. My phone is stock, bootloader is locked and I do not have root or anything else on it. what do I have to do to flash this cache.img file and get my phone working again? I looked up all the info so far but I'm at a dead end. I can figure out basic things but im no genius unfortunately. I'm at the point where Ill paypal a reward to whoever helps me. Please someone help me. I en

How can you use fastboot on locked bootloader? I don't think it's possible

Try to clear the cache again.it worked for me.
Sent from my Nexus 5 using Tapatalk

geemaan said:
Try to clear the cache again.it worked for me.
did you have the same thing I have wrong? on the recovery screen when I try to clear cache I get this message
Wiping Cache
"E: failed to mount /cache (invalid argument)
formatting /cache
Should I leave it like that for awhile? the longest I have left it like that is like 5 minutes. It doesnt seem like its doing anything.
Click to expand...
Click to collapse

Unlock the bootloader and try
Sent from my Android L Nexus 5 via Tapatalk

you can just reflash the cache using fastboot. yes, you can use fastboot on any locked or unlocked device.
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
MARKOZD15 said:
How can you use fastboot on locked bootloader? I don't think it's possible
Click to expand...
Click to collapse
how did you unlock your bootloader with fastboot when your device was locked when you used fadtboot? yea. any locked or unlocked nexus device.

Lol. I guess that makes perfect sense!
Sent from my Android L Nexus 5 via Tapatalk

[Q] nexus 5 stuck in boot animation

my nexus 5 is stuck in the boot animation screen. i dont have the usb debugging enabled on it. i tried to wipe cache and do a factory reset but both didnot work. i am getting error messages
E: failed to mount /cache (invalid argument)
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
what should i do?

jabinmb said:
my nexus 5 is stuck in the boot animation screen. i dont have the usb debugging enabled on it. i tried to wipe cache and do a factory reset but both didnot work. i am getting error messages
E: failed to mount /cache (invalid argument)
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
what should i do?
Click to expand...
Click to collapse
USB Debugging has absolutely nothing to do with fastboot in bootloader or ADB while in recovery.
It is ONLY used with ADB while booted into Android. NOTHING else.
Flash factory images using fastboot while in bootloader or reflash your ROM in recovery.

Lethargy said:
USB Debugging has absolutely nothing to do with fastboot in bootloader or ADB while in recovery.
It is ONLY used with ADB while booted into Android. NOTHING else.
Flash factory images using fastboot while in bootloader or reflash your ROM in recovery.
Click to expand...
Click to collapse
can you please tell me how to do it. thankyou

jabinmb said:
can you please tell me how to do it. thankyou
Click to expand...
Click to collapse
[noob-read] adb and fastboot. What is it? How can it help you?
[FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5

Lethargy said:
[noob-read] adb and fastboot. What is it? How can it help you?
[FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Click to expand...
Click to collapse
thankyou. i ll try it and get back.

Lethargy said:
[noob-read] adb and fastboot. What is it? How can it help you?
[FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Click to expand...
Click to collapse
please check this

jabinmb said:
please check this
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

Lethargy said:
Try this:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
what will hapen if i try fastboot boot system.img or cache.img in cmd

after you unlocked , did you reboot to bootloader ? if so , does it stay unlocked ? if it doesn't it's warranty time.

Niflheimer said:
after you unlocked , did you reboot to bootloader ? if so , does it stay unlocked ? if it doesn't it's warranty time.
Click to expand...
Click to collapse
once i reboot bootloader it goes back to locked. is that a board issue?

jabinmb said:
once i reboot bootloader it goes back to locked. is that a board issue?
Click to expand...
Click to collapse
RMA or get a replacement. Your NAND is damaged/dead. Nothing you can do about it.

Lethargy said:
RMA or get a replacement. Your NAND is damaged/dead. Nothing you can do about it.
Click to expand...
Click to collapse
i should probably contact lg customer service point then. thank you.

i got my nexus 5's board replaced but there is new problem. the imei number that they were able to detect on their system is different from the one that is being shown when i dial *#06# and in 'about phone'. what is the reason for this discrepancy

How to recover Moto G?

Hi!
I updated my moto g when the official OTA 5.0.2 arrived, It worked properly more or less, for some days. It began to fail some apps and suddenly to black screen. When I push the power button only appears the logo of Motorola.
I can enter in fastboot mode and recovery mode, but when I tried to flash a stock ROM or anything like a custom recovery It does not work. (with mfastboot).
In fastboot mode appears this:
writing logo
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
And in recovery mode appears this:
E: Can´t mount /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
E: Can´t mount /cache/recovery/log
E: Can´t open /cache/recovery/log
E: Can´t mount /cache/recovery/last_install
E: Can´t open /cache/recovery/last_install
E: FAiled closing /dev/block/platform/ms_sdcc.1/by-name/misc
(I/O error)
The moto g is a XT1032.
The bootloader version is 41.18
Can anyone help me?

You should flash a recovery for Lollipop bootloader

Feche said:
You should flash a recovery for Lollipop bootloader
Click to expand...
Click to collapse
Like which one?

Like this one https://mega.co.nz/#!14knFRxA!u3vZglvRSICmlknJNbxA1AKEQGXx0aWu8Oke58E4mX8

Feche said:
Like this one https://mega.co.nz/#!14knFRxA!u3vZglvRSICmlknJNbxA1AKEQGXx0aWu8Oke58E4mX8
Click to expand...
Click to collapse
I tried with this one and did not allowed to install it.
From TWRP web > openrecovery-twrp-2.8.5.0-xt1032.img
Is the same?

Try flashing Philz for the falcon from here: http://forum.xda-developers.com/showthread.php?t=2639583
I used Philz on my xt1032 because I was having problems with TWRP whereby it was giving me strange errors.

I have the same problem - any solution?
After the OTA update to a higher Android version (I believe it was Lollipop) I started to face WIFI / WLAN connection issues.
But now the XT1032 / Moto 1st gen totally died in the same way that you are describing.
"I/O error" tells me there is something fundamentally wrong.
Sames messages, and tried factory reset multiple times.
Additionally, after "Power down" the phone still seems to be alive, since the display flashes every 4 seconds briefly, showing the Android logo which is also shown in recovery mode.
And the battery is at 0% after a couple of hours - so the phone is still "on", even while powered off (officially).
-> Have you found a solution to your problem?
I have not dared to flash the phone with anything up to now in order to keep the warranty.
So I will send it to Motorola unless someone has a hint regarding a software solution...

Hi Motorino . i have moto g2 with exactly the same problem. Have tried everything......may also send it to motorola

How about fastboot flashing the 5.0.2 full factory firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
@melbfc - Here is the forum for your Model: http://forum.xda-developers.com/moto-g-2014

[Q] Nexus 5 stuck at screen of the eternally spinning balls

I'm going to start off by saying I'm the noobiest of noobs, so please be gentle with your replies.
I was watching Youtube on my Nexus 5 yesterday when it suddenly shut down and attempted to restart itself. I watched it go very slowly from the white Google logo to the colourful spinning balls screen, and it got stuck there.
Status right now:
Phone stuck at spinning balls screen
I can get to fastboot and factory recovery screen
Factory reset doesn't work
Power button appears to be working fine
Charging is fine and I can see the battery icon when it's off
Phone is not rooted, bootloader has not been unlocked
What I did so far:
Someone posted a thread with a similar problem and said to flash the factory image a few times, so I followed these instructions. Except to do that I need to unlock my (currently locked) bootloader first. I then tried to follow these instructions of unlocking bootloader, but got stuck at the last step of "fastboot reboot“ because my phone still won't get past the screen of spinning balls, no unlocking the bootloader for me. HELP!
This is what's at the bottom of the system recovery 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 to mount /cache (Invalid argument)

So. Have you tried the fastboot commands to fastboot flash system system.img and boot and cache etc etc?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
So. Have you tried the fastboot commands to fastboot flash system system.img and boot and cache etc etc ?
Click to expand...
Click to collapse
I think I have, it didn't work because the bootloader is locked, and if I am able to unlock it right now, there would be no problem.

laughingcloud said:
"fastboot reboot“
Click to expand...
Click to collapse
Not surprising. We already know your phone won't boot and that what that command tries to do. Use the command "fastboot reboot-bootloader".

Wakamatsu said:
Not surprising. We already know your phone won't boot and that what that command tries to do. Use the command "fastboot reboot-bootloader".
Click to expand...
Click to collapse
Tried it, then when the fastboot screen came on, it's "Lock State - Locked" again.

laughingcloud said:
Tried it, then when the fastboot screen came on, it's "Lock State - Locked" again.
Click to expand...
Click to collapse
Not a good sign. Points to a physical problem, not software.

And you have done fastboot oem unlock yea?
Sent from my Nexus 5 using Tapatalk

Wakamatsu said:
Not a good sign. Points to a physical problem, not software.
Click to expand...
Click to collapse
Does that mean I have to take it to a repair shop? Or is it irrepairable?

Ben36 said:
And you have done fastboot oem unlock yea?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, the status shows as unlocked right after I do fastboot oem unlock, but as soon as I reboot it, goes back to locked again.

laughingcloud said:
Yes, the status shows as unlocked right after I do fastboot oem unlock, but as soon as I reboot it, goes back to locked again.
Click to expand...
Click to collapse
Yup, does sound like pooped nand. Nothing you can do about unlocking. But can you not flash the img's locked tho still as they're Google img's. I can't remember now
Sent from my Nexus 5 using Tapatalk