Database Info

Boot stops at 'Google', can't mout sdcard in cwm

Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!

PedroBustamonte said:
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
Click to expand...
Click to collapse
flasgh stock via fastboot and wipe everything DONE!

i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,

Cascabreu said:
flasgh stock via fastboot and wipe everything DONE!
Click to expand...
Click to collapse
So there's no way to get the content of the sdcard before I wipe everything?
ej8989 said:
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Click to expand...
Click to collapse
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)

PedroBustamonte said:
So there's no way to get the content of the sdcard before I wipe everything?
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
Click to expand...
Click to collapse
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.

mdean1981 said:
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
Click to expand...
Click to collapse
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...

It will also wipe everything if I remember well
Envoyé depuis mon Nexus S avec Tapatalk

PedroBustamonte said:
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
Click to expand...
Click to collapse
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue

Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
Yes you're right. But I really can't think of any thing I could try.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a

Blissfull said:
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Click to expand...
Click to collapse
Factory Images for Nexus Devices
https://developers.google.com/android/nexus/images

Hi ^^
I had the same problem with my Nexus S a long time ago and never found out how to solve it. It seems that the internal memory is corrupted and nothing but replacing the motherboard can solve it. Since I bought mine in the USA but I live in Belgium I never got mine repaired. Sometimes I come back here to see if there is still no solution but each time I'm disappointed...
Sorry.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
I can confirm this. I had the same thing happen to my Nexus S 4G recently. I was never able to salvage any data off the sdcard no matter what I tried (various mounting attempts in recovery, any adb command I thought might be helpful, etc.). As a last resort I tried to lock/unlock the bootloader - once I locked it, I was unable to unlock it again, it just froze up after asking me if I was sure I wanted to unlock. I guess that's what happens when the internal sdcard goes to hell. I ended up taking it to my local Sprint store and they replaced the phone with a refurbished one from Samsung (for approximately $35).

[Q] My Nexus 5's Cyanogen Isn't Updating.

Hey!
It's really hard to explain my issue, but I'll try my best.
So here it goes..
My Nexus 5 keeps telling me I have a system update to download and install, so I wait for it to download and then it tells me to install the update from CM-Hammerhead-46e2abd61c to 1f023a4eca-signed.
It shows the Install update option right below, and everything seems fine till now.
When I press this Install update button, it reboots the phone, shows me an android popped open and something indicating that there're being changes which are not shown in normal reboots ofc.
The phone reboots and start, tells me it;s optimizing apps since I use Android Run-time Cache instead of Dalvik.
Now the issue is, it's not updated at all.
It shows me the same Cyan and Android version, 4.4.2 and 46e2abd61c, and when I check for update, it shows me the same thing that I have to update from CM-Hammerhead-46e2abd61c to 1f023a4eca-signed.
I tried this like 10 times and it happens over and over again.
This is bugging me for like a day now.
Any solutions to this?
Thanks.

What recovery are you using?
Sent from my Nexus 5 using Tapatalk

If you're using cwm I don't think it'll work

Lethargy said:
If you're using cwm I don't think it'll work
Click to expand...
Click to collapse
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk

rootSU said:
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Dunno then, I guess OP can try a different recovery to the one he's using now

Lethargy said:
Dunno then, I guess OP can try a different recovery to the one he's using now
Click to expand...
Click to collapse
Maybe. Thats why I'm trying to find out which one he is using
Sent from my Nexus 5 using Tapatalk

HeyIamSmiley said:
Hey!
The phone reboots and start, tells me it;s optimizing apps since I use Android Run-time Cache instead of Dalvik.
Thanks.
Click to expand...
Click to collapse
Not that it matters, but I'm kind of curious which runtime you're using =P

I'm having the same problem as well.

californiamaki said:
I'm having the same problem as well.
Click to expand...
Click to collapse
Then can you answer my question also please?
Sent from my Nexus 5 using Tapatalk

Try to download the latest update on your PC and flash it on your phone and if that doesn't work change recoveries.

rootSU said:
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not even sure, really new to this rooting stuff.
How do I check?

ClockworkMod
rootSU said:
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm using ClockworkMod.
And if it doesn;t work with Cwm, then what should I do to install that update?

Lethargy said:
If you're using cwm I don't think it'll work
Click to expand...
Click to collapse
Yes, I'm using ClockworkMod, so what do I do now?

rootSU said:
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://www.cyandelta.com/index2213.html?q=FAQ
HeyIamSmiley said:
Yes, I'm using ClockworkMod, so what do I do now?
Click to expand...
Click to collapse
Try flashing one of these two recoveries with fastboot in bootloader
TWRP: http://techerrata.com/browse/twrp2/hammerhead
PhilZ Touch: http://forum.xda-developers.com/goo...t/hammerhead-philz-touch-6-43-6-f2fs-t2565174
Read a couple threads in the first linked thread of my signature if you're not sure how.

Lethargy said:
http://www.cyandelta.com/index2213.html?q=FAQ
Try flashing one of these two recoveries with fastboot in bootloader
TWRP: http://techerrata.com/browse/twrp2/hammerhead
PhilZ Touch: http://forum.xda-developers.com/goo...t/hammerhead-philz-touch-6-43-6-f2fs-t2565174
Read a couple threads in the first linked thread of my signature if you're not sure how.
Click to expand...
Click to collapse
Guess they've updated it recently then. This certainly was not the case recently, because Phil threads often get asked why it doesn't work and teh answer is the /sdcard/0.
Who knows, Maybe CM finally saw the light, 12 months after everyone else? I wont hold my breath though. Until very recently, it only worked in CWM. It was written that way

rootSU said:
Guess they've updated it recently then. This certainly was not the case recently, because Phil threads often get asked why it doesn't work and teh answer is the /sdcard/0.
Who knows, Maybe CM finally saw the light, 12 months after everyone else? I wont hold my breath though. Until very recently, it only worked in CWM. It was written that way
Click to expand...
Click to collapse
Dunno. Omni says OpenDelta only works with TWRP: http://omnirom.org/general/opendelta-brings-incremental-system-updates-omni/
I've never used Delta since I build my ROMs myself
Edit: CyanDelta seems to be 3rd party, not CyanogenMod's version of OpenDelta. Does the same thing though, I guess using TWRP is most likely to work for this? But you say it only worked in CWM.. so I have no idea lol

Lethargy said:
Dunno. Omni says OpenDelta only works with TWRP: http://omnirom.org/general/opendelta-brings-incremental-system-updates-omni/
I've never used Delta since I build my ROMs myself
Edit: CyanDelta seems to be 3rd party, not CyanogenMod's version of OpenDelta. Does the same thing though, I guess using TWRP is most likely to work for this? But you say it only worked in CWM.. so I have no idea lol
Click to expand...
Click to collapse
The whole thing came about where when 4.2 came out, they moved /sdcard from /data/media/ to /data/media/0. CWM left it as /data/media - which even today, is why you cant see your nandroids taken with CWM in /sdcard
So what the updater app did was put in the updater-script /sdcard/0 as the path, leaving the /data/media mountpoint in CWM in tact... In Philz and TWRP, you would see the error in recovery log (cannot find /sdcard/0/whatever.zip) because on proper recoveries, that is actually /data/media/0/0/whatever.zip).
So Kudos if they changed it to support real recoveries instead of legacy, antiquated CWM builds.

rootSU said:
The whole thing came about where when 4.2 came out, they moved /sdcard from /data/media/ to /data/media/0. CWM left it as /data/media - which even today, is why you cant see your nandroids taken with CWM in /sdcard
So what the updater app did was put in the updater-script /sdcard/0 as the path, leaving the /data/media mountpoint in CWM in tact... In Philz and TWRP, you would see the error in recovery log (cannot find /sdcard/0/whatever.zip) because on proper recoveries, that is actually /data/media/0/0/whatever.zip).
So Kudos if they changed it to support real recoveries instead of legacy, antiquated CWM builds.
Click to expand...
Click to collapse
Yeah, it's probably something related to that.. Several people I know had related issues with certain recoveries and complained about it. Solution was using a different recovery lol
Anyways, if it doesn't work for the OP in one recovery he can try another.

Lethargy said:
Anyways, if it doesn't work for the OP in one recovery he can try another.
Click to expand...
Click to collapse
How many euros will you bet that we never find out the answer?

rootSU said:
How many euros will you bet that we never find out the answer?
Click to expand...
Click to collapse
Euros? Psh :silly:

[Q] make_ext4fs function?

I'm trying to go back from f2fs to ext4fs because my tf300t has been having a lot of freezing issues and what not on roms that use to be stable. My question is, how long should TWRP 2.8.3.0 take to convert /data back to ext4? I let it run for over 5 minutes and it still going... Any idea how long this process should take?
Thanks for the help!

draky said:
I'm trying to go back from f2fs to ext4fs because my tf300t has been having a lot of freezing issues and what not on roms that use to be stable. My question is, how long should TWRP 2.8.3.0 take to convert /data back to ext4? I let it run for over 5 minutes and it still going... Any idea how long this process should take?
Thanks for the help!
Click to expand...
Click to collapse
90 mins plus... Do not interrupt the process .... :good:
Thx Josh

lj50036 said:
90 mins plus... Do not interrupt the process .... :good:
Thx Josh
Click to expand...
Click to collapse
Thanks for the answer, I let it run and it took close to 60 minutes but it finally finished. I thought it was a faster process so I was getting worried.

draky said:
Thanks for the answer, I let it run and it took close to 60 minutes but it finally finished. I thought it was a faster process so I was getting worried.
Click to expand...
Click to collapse
TWRP as of 2.7.0.0 has used what is called a secure erase ...
This is a good thing except for the time it takes ... :good:
Can you add 'SOLVED' to the thread title .....
Thx Josh

[Q] Nexus 5 Bootloop

So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.

Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.

bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.

Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.

Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.

bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.

Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.

ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?

Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.

AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.

Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.

bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?

Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.

bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.

bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.

Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]

[SOLVED] Nexus 5 32Gb won't go back to full internal storage. Tried everything!

So after a few weeks after the launch of the Marshmallow uptade, I flashed the stock image with fastboot using a Mac and everything gone flawlessly, until I saw my internal storage. My 32Gb nexus became a 16Gb model.
I search in EVERY Forum I found on the internet, and I have good skills on recovering android phones with software problems, all the "how-to's" I found were with very easy instructions, but NONE of then worked for me.
Ive tried EVERYTHING I found on the internet. Do a factory reset, tried to resize the partition using TWRP, flashed manually all the partitions, flashed the stock image again and again many times, flashed customs roms, tried to erase the userdata, cache and system partitions tons of times using flashtool on windows, mac and linux and NOTHING worked. In all the process my phone started with no problems, but my internal storage stayed 12,55gb. My Bootloader shows 32Gb model, the IMEI on LG database shows 32Gb model AND the logic board indicates a 32Gb model... I really don't know what to do! Anyone can save me???? Thanks!
In advance information, I followed every step on this guide at least 10 times, and didn't work:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I was thinking in the possibility of an custom Userdata partition, only for the 32Gb model, that I can flash manually or a program, like GParted, that I can manually resize the data partition.
I'm really desesperate here, so sorry for any english mistakes, since I speak portuguese, or any dumb idea.
Thanks for any help!
-------------------------------------- FOUND THE SOLUTION! ----------------------------------------------
After WEEKS trying to realize what the hell happened and rethinking every possible form to regain my full storage, I've found the solution.
Fiddling with the partitions on the phone, i learned that there is a partition on the system, that "informs" the userdata that the phone is a 16Gb or a 32Gb variant, and it's called "Primary GPT".
I realized that the guy who sold to me, recovered the phone from an brick it suffered, but he used a 16Gb model GTP partition to reinstall the bootloaders and the system, so, no matter how many different process I tried, I would NEVER recognizes the 32Gb, because THIS partition was telling the system that it was a 16Gb model.
(Little of a noob explain but that was the way I got it...)
So all I had to do was use this thread to reflash the correct GPT partition:
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
And then, reflash the complete system image file, and after the boot, my phone recognized the 32Gb internal storage again!
Thank you guys for the effort in sorting out any way to help me, I hope this thread can help someone else facing the same problem in the future!
Peace!

Did you flash the userdata.img file too?

audit13 said:
Did you flash the userdata.img file too?
Click to expand...
Click to collapse
Tried everything I could do... Flashed userdata partition, erased the partition with fastboot then entered in recovery mode (stock and custom) and then format the userdata from there, doing that by doing a factory reset and wiping cache partition and nothing...
Any other idea what it could be?

Unfortunately, I have no idea why this happened or how to fix it as I only have the 16 GB version.

seriously guys, anybody to save my day?

audit13 said:
Unfortunately, I have no idea why this happened or how to fix it as I only have the 16 GB version.
Click to expand...
Click to collapse
Thanks anyway bro!

Have you tried factory reset and wiping cache from STOCK recovery? That always works for me.

Try using flash-all.bat in Windows. Part of the stock favor image. Make sure to take backup before doing it though

Had this happen once and had to factory reset from stock recovery like he said above. Worked like a charm!

redsmith said:
Have you tried factory reset and wiping cache from STOCK recovery? That always works for me.
Click to expand...
Click to collapse
shri_chanakya said:
Try using flash-all.bat in Windows. Part of the stock favor image. Make sure to take backup before doing it though
Click to expand...
Click to collapse
Nevermindthelabel said:
Had this happen once and had to factory reset from stock recovery like he said above. Worked like a charm!
Click to expand...
Click to collapse
Ive tried with stock recovery, custom recovery, CWM, TWRP Resize partition and no use...
I lost the count of times Ive tried to flash manually, flash-all.bat in windows, flash-all.sh on mac and linux, really nothing work.
There is no toolkit, even knowing its a bad idea to use those things but, since Im out of options, anyone can tell me one that can help me?
Thanks guys btw!

I had this problem with a couple devices on lollipop, typing the command below in a terminal fixed it. Reboot afterwards.
su
restorecon -FR /data/media/0

lynnux said:
I had this problem with a couple devices on lollipop, typing the command below in a terminal fixed it. Reboot afterwards.
su
restorecon -FR /data/media/0
Click to expand...
Click to collapse
can you explain what is the function of this line? Tried here and everything stayed the same
Thanks!

Damn... that's weird.
Is it possible to format userdata? Like, for example, "fastboot format userdata"? I don't really know, just shooting in the dark by this point now.

nameless-- said:
can you explain what is the function of this line? Tried here and everything stayed the same
Thanks!
Click to expand...
Click to collapse
I believe it's a way of restoring data or storage to it's original configuration. Also had this problem on my 32gb N5 early on, unfortunately I can't remember what I did that time to get it back.

redsmith said:
Damn... that's weird.
Is it possible to format userdata? Like, for example, "fastboot format userdata"? I don't really know, just shooting in the dark by this point now.
Click to expand...
Click to collapse
Yes, I did this process three times I think, format userdata and erase userdata, none of then resolved the issue
lynnux said:
I believe it's a way of restoring data or storage to it's original configuration. Also had this problem on my 32gb N5 early on, unfortunately I can't remember what I did that time to get it back.
Click to expand...
Click to collapse
I tried this code using the terminal on the phone, rebooted and the storage stayed the same, I'll try to do the same process using adb shell from my windows computer, since I have the "light"version of adb and fastboot installed on my mac and the adb shell comand is giving me the "offline" error...
I'll get back here with any updates.
thanks in advance guys! Hope this comand works! :highfive:

Well... Tried with my windows computer, and next with my Mac, with the command line given and.... Nope. Nothing changed.

I know it's not great but if your desperate....
I've always done things manually but there comes a time when your willing to try whatever to fix your phone as they don't come cheap, so if I could recommend a toolkit that has saved my ass more than once and has worked flawlessly for me every time maybe it could help you too.
http://www.wugfresh.com/nrt/
It's called Nexus Root Toolkit and its by the developer wugfresh. Try this if you'd like, if not I hope you find a solution. This kit has everything you can think of that could help you with rooting, or returning to stock and relocking. Best of luck with your journey!

MechanicalMecca said:
I've always done things manually but there comes a time when your willing to try whatever to fix your phone as they don't come cheap, so if I could recommend a toolkit that has saved my ass more than once and has worked flawlessly for me every time maybe it could help you too.
http://www.wugfresh.com/nrt/
It's called Nexus Root Toolkit and its by the developer wugfresh. Try this if you'd like, if not I hope you find a solution. This kit has everything you can think of that could help you with rooting, or returning to stock and relocking. Best of luck with your journey!
Click to expand...
Click to collapse
I'll try this as soon as possible, thanks!

Hey Nameless--,
I tried everything possible as you did, but when i tried your steps i am facing an issue. I cannot see Qualcomm HS-USB QDLoader 9008 under device manager
Can you help me?

Dhaval Raichura said:
Hey Nameless--,
I tried everything possible as you did, but when i tried your steps i am facing an issue. I cannot see Qualcomm HS-USB QDLoader 9008 under device manager
Can you help me?
Click to expand...
Click to collapse
The wrong size memory issue, 16 Gb instead of 32, is an old issue. It can be solved by booting into the stock recovery then clearing cache and then doing a factory reset. Note, this will wipe your device.
Sent from my Nexus 9 using XDA Free mobile app