• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root NEXUS 5 Internal Memory 0mb

A

Apurba007

Lurker
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 Cayanogen Mod 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 'Cayanogen logo" 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 :)
Please.... please...please
please mail me How to Recover..
Please Help me..........Please....
 
Incakola said:
Time to update twrp: http://teamw.in/project/twrp2/205

Are you having the same error with mounting data or system?

To test it go to mount option and tick either and check the output screen to see if there's an error.
Click to expand...
Same problem
E: Unable to mount /data
E: Unable to mount /storage

Please Please Please ...Other method..
My Phone is ON but internal memory is 124mb.. and this is a root phone so i open file manager in root access only then i see 1 folder /storage/emulated/0/storage/secure This folder icon are Key sign.. I open this folder then show me error...
 
If you can get in to TWRP recovery and bootloader and/or fastboot mode... With a Nexus device then there's almost always a really good chance to restore your device... at worst you may lose some of your personal data along the way, I'd take that over a working N5 any day!

I do agree that updating TWRP to a newer and better version is a good idea and it now has much better feature's and support.
Not the same issue as you, but a similar one at that. After installing 5.0, I had a few bugs, decided I wanted a clean install and after booting into recovery, I couldn't chose to select and wipe the "System Partition" through TWRP recovery. (Believe I was on TWRP 2.7.1. I Upgraded to TWRP 2.8.1 (5.0 compatible) and still couldn't mount the System partition.
I connect the device to my PC in all the USB connection modes, MTP, PTP, USB Debugging and even USB tethering.
Established adb connection, then adb Rebooted to recovery through adb commands. Made a MTP connection through recovery. Backed out to the main TWRP screen and chosee to reboot
Recovery, selected /advanced wipe/ and system partition and the others partitions where available to select now.

Point is if you can gain access to these partitions then you can try and reflash you're ROM or a different ROM, restore a nandroid backup and/or flash back to the Google factory images.
Your best bet is to probably try and manually fastboot flash the stock Google factory images and return your N5/to stock.

Or you may want to look at this thread that runs a batch script and autoflashes Android 5.0 in 2/mins even if your N5 is sutck in a bootloop, or in bootloader mode and/or if your bootloader is locked or unlocked. Worth checking out - http://forum.xda-developers.com/goo...o-flash-5-0-lrx21o-flash-5-0-n5-tool-t2957801
 
xdrc45 said:
If you can get in to TWRP recovery and bootloader and/or fastboot mode... With a Nexus device then there's almost always a really good chance to restore your device... at worst you may lose some of your personal data along the way, I'd take that over a working N5 any day!

I do agree that updating TWRP to a newer and better version is a good idea and it now has much better feature's and support.
Not the same issue as you, but a similar one at that. After installing 5.0, I had a few bugs, decided I wanted a clean install and after booting into recovery, I couldn't chose to select and wipe the "System Partition" through TWRP recovery. (Believe I was on TWRP 2.7.1. I Upgraded to TWRP 2.8.1 (5.0 compatible) and still couldn't mount the System partition.
I connect the device to my PC in all the USB connection modes, MTP, PTP, USB Debugging and even USB tethering.
Established adb connection, then adb Rebooted to recovery through adb commands. Made a MTP connection through recovery. Backed out to the main TWRP screen and chosee to reboot
Recovery, selected /advanced wipe/ and system partition and the others partitions where available to select now.

Point is if you can gain access to these partitions then you can try and reflash you're ROM or a different ROM, restore a nandroid backup and/or flash back to the Google factory images.
Your best bet is to probably try and manually fastboot flash the stock Google factory images and return your N5/to stock.

Or you may want to look at this thread that runs a batch script and autoflashes Android 5.0 in 2/mins even if your N5 is sutck in a bootloop, or in bootloader mode and/or if your bootloader is locked or unlocked. Worth checking out - http://forum.xda-developers.com/goo...o-flash-5-0-lrx21o-flash-5-0-n5-tool-t2957801
Click to expand...
Do not Flash
Same problem
E: Unable to mount /data
E: Unable to mount /storage

Please Help..
 
Apurba007 said:
Do not Flash
Same problem
E: Unable to mount /data
E: Unable to mount /storage

Please Help..
Click to expand...

In TWRP did you use factory wipe or advance wipe? Try checking the box "Use rm -rf instead of formatting" under advance-settings? (I use a themed TWRP so it's all switched around so I don't remember stock ui) Then try advanced wipe and tick: dalvik, data, cache. Then untick "Use rm -rf instead of formatting". Perform another wipe with factory wipe.

Second option:
a9bdb449736fc9774c1abd0ffeed7f40.jpg
 
Last edited:
Interesting...there seems to be a lot of this type of problem happening frequently. You may need to download the cm rom and gapps you use to the PC.
-Put your phone in fastboot.
-Open cmd (in PC) and type in your plate-form tools directory or use AF mini sdk tools (http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/) click the "MINI-SDK" link
(Don't close your cmd prompt throughout the process)
-Plug in your phone via usb and have your cmd already set under the directory of the adb stuff (see attachment)
-Type "fastboot devices" and see if your device is seen by the pc via usb connection
-If you see it, type "fastboot oem format"
-If that doesn't work do
fastboot format system
fastboot format data (THIS WILL ERASE SD CARD)
fastboot format cache
-If all goes well, boot to your recovery and flip it on to sideload mode
-In cmd type adb devices and you will see your device's S/N
-Move your ROM and GAPPS that you want to use inside the folder of adb stuff and rename them "cm" for rom and "gapps" for your gapps
-Type "adb sideload cm.zip" if successful proceed sideloading gapps "adb sideload gapps.zip"
-Try and boot into rom...

If your getting error closed messages, try and reinstall the google driver. Wug fresh toolkit has a great driver install guide that ensures a clean install of the driver.
 

Attachments

  • Untitled.png
    Untitled.png
    23.7 KB · Views: 277
Last edited:
Ufwewentitled.jpg
Incakola said:
Interesting...there seems to be a lot of this type of problem happening frequently. You may need to download the cm rom and gapps you use to the PC.
-Put your phone in fastboot.
-Open cmd (in PC) and type in your plate-form tools directory or use AF mini sdk tools (http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/) click the "MINI-SDK" link
(Don't close your cmd prompt throughout the process)
-Plug in your phone via usb and have your cmd already set under the directory of the adb stuff (see attachment)
-Type "fastboot devices" and see if your device is seen by the pc via usb connection
-If you see it, type "fastboot oem format"
-If that doesn't work do
fastboot format system
fastboot format data (THIS WILL ERASE SD CARD)
fastboot format cache
-If all goes well, boot to your recovery and flip it on to sideload mode
-In cmd type adb devices and you will see your device's S/N
-Move your ROM and GAPPS that you want to use inside the folder of adb stuff and rename them "cm" for rom and "gapps" for your gapps
-Type "adb sideload cm.zip" if successful proceed sideloading gapps "adb sideload gapps.zip"
-Try and boot into rom...

If your getting error closed messages, try and reinstall the google driver. Wug fresh toolkit has a great driver install guide that ensures a clean install of the driver.
Click to expand...
In Dos mode "failed (write memory failed)"
System data , user data all are show me Failed..
please other...option
 
Last edited:
Can you update your twrp recovery? 2.8.3.0
These posts keep pointing to having a corrupted emmc. XDA has some guides for corrupted portitions but it may touch on emmc problems as well.
 
Last edited:
i had the same problem with my moto g3 mobile
the userdata storage got corrupted and it shows 0mb at available space
i format the userdata by using custom recovery(TWRP) and it helped me
 
You must log in or register to reply here.
Back
Top Bottom