Hello sorry for my bad English I speak Spanish.
I have a Nexus 5 32 GB but now it is 16GB ...
Last month I updated my smartphone to Android 5.1.0 (manually) from bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz12f.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.25.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot
When I tried to copy my music I received the "Insufficient memory storage" message :crying:. I checked the Storage menu and it says that my smartphone has only 16GB now . I don't understand what happened because I always update my smartphone from bootloader.
Do a factory reset in the stock recovery and clear cache. This is a common problem. Back up first
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Do a factory reset in the stock recovery and clear cache. This is a common problem. Back up first
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot tell you but I tried flashing Android 4.4 and other official ROMs but I still have the same problem.
hectorkrrillo said:
I forgot tell you but I tried flashing Android 4.4 and other official ROMs but I still have the same problem.
Click to expand...
Click to collapse
That is why you have to do a factery reset in stock recovery.
Problem
I have some problem :/
pipo406 said:
I have some problem :/
Click to expand...
Click to collapse
Do a factory reset in stock recovery
If factory reset does not work (didn't for me for some reason), install TWRP recovery, go to Wipe and choose Format Data. This worked for me. Of course all your data will be lost, but if you backed up, no harm done.
eross said:
If factory reset does not work (didn't for me for some reason), install TWRP recovery, go to Wipe and choose Format Data. This worked for me. Of course all your data will be lost, but if you backed up, no harm done.
Click to expand...
Click to collapse
Ohhh!! Thanks! My phone has 32GB again! :good::good::good:.... I had root on my Nexus 5 and TWRP recovery, I did just "Format Data" from TWRP and wala! 32GB is back... I didn't try to apply factory reset from ROM because I have root.
hectorkrrillo said:
Ohhh!! Thanks! My phone has 32GB again! :good::good::good:.... I had root on my Nexus 5 and TWRP recovery, I did just "Format Data" from TWRP and wala! 32GB is back... I didn't try to apply factory reset from ROM because I have root.
Click to expand...
Click to collapse
Glad to hear that :good:
Related
I have a friend who put twrp and cid 111111111 hboot 2.14 had viper couldnt make calls wiped data and he deleted his sdcard now he has no OS
i was able to flash recovery on his phone but thats where i'm at..
scrizo said:
I have a friend who put twrp and cid 111111111 hboot 2.14 had viper couldnt make calls wiped data and he deleted his sdcard now he has no OS
i was able to flash recovery on his phone but thats where i'm at..
Click to expand...
Click to collapse
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
exad said:
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
Click to expand...
Click to collapse
You're too fast man
Sent from my Evita
I flashed 2.5.0.0
S-Off
I don't know he did have problems with TWRP not being able to write to .twrp file. If he corrupted the sdcard is he fubared
exad said:
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
Click to expand...
Click to collapse
*UPDATE*
I am using adb push ViperXL-3.2.7 /sdcard/ and it appears to be pushing the file so far.
I am able to do this in recovery mode
Tried to install ViperXL failed.
Unable to mount '/sdcard'
Unable to mount storage
TWRP 2.5 is full of bugs. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery and try flashing ROM again.
Sent from my Evita
After flashing twrp 2.6 you may have to wipe the SD card within twrp if the SDCARD is corrupt.
problem htc.dialer stops working using viperxl
timmaaa said:
TWRP 2.5 is full of bugs. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery and try flashing ROM again.
Sent from my Evita
Click to expand...
Click to collapse
scrizo said:
problem htc.dialer stops working using viperxl
Click to expand...
Click to collapse
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
I had flashed your 2.6 twrp and wiped everything and did what you said then pushed the viperxl on there and installed and did the wipe data do i still need to reflash the cwm touch and etc
exad said:
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
Click to expand...
Click to collapse
did everything you said still the same error with htc.dialer i have a htc onex can i transfer my dialer to his phone?
exad said:
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
Click to expand...
Click to collapse
No that's the only way to fix it.
Sent from my One X using xda app-developers app
Dang it is not working then. still have the issue with the dialer not working.
exad said:
No that's the only way to fix it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
If this helps he has build # 3.17
Did you flash the three different versions of recovery?
Sent from my Evita
you mean cwm touch
cwm older
twrp?
timmaaa said:
Did you flash the three different versions of recovery?
Sent from my Evita
Click to expand...
Click to collapse
Yeah
Sent from my Evita
yes I flashed CWM touch
I flashed non touch
I flashed twrp 2.6
factory reset
installed viperxl
wiped data
timmaaa said:
Yeah
Sent from my Evita
Click to expand...
Click to collapse
You should have wiped everything (cache/dalvik cache/factory reset/system) before flashing Viper.
Sent from my Evita
Help. I have the this error when I start TWRP
Code:
E:Unable to mount storage.
This stop me from doing backup in TWRP..
I have tried to re-flash TWRP. I have also tried flash the recovery.img from Google, and then flash TWRP. The problem still there.
I even try to nearly did a factory the full factory image by doing
Code:
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
and then restart phone,. booth into phone, and reboot to recovery and flash TWRP...
Are there anything else that I can do? Please help...
Are you using twrp 2.6.3.4? Go into wipe and then format data. Backup first
jd1639 said:
Are you using twrp 2.6.3.4? Go into wipe and then format data. Backup first
Click to expand...
Click to collapse
He's not able to backup. That's the point of his problem. Still trying wiping dalvik and cache first. Then try data. If that don't work trying flashing cwm or Philz's touch recovery.
I tried to wiping dalvik and cache... the problem remains.
I then tried to wipe data but preserve /data/media, which is the default action. The problem remains...
I really don't want to reset my phone to factory state with internal memory completely wiped... any help, please?
leoncheong said:
I tried to wiping dalvik and cache... the problem remains.
I then tried to wipe data but preserve /data/media, which is the default action. The problem remains...
I really don't want to reset my phone to factory state with internal memory completely wiped... any help, please?
Click to expand...
Click to collapse
Don't think you have a choice if you want the phone to work. You're going to have to format the data.
Sound like you missed a reboot before installing custom recovery after unlocking boot.
WR
Sent from my Nexus 5
I solve it flashing to stock rom and re installing the recovery.. It is the only way.. I had the same problem
Inviato dal mio Nexus 7 utilizzando Tapatalk
Thanks for all your suggestions! I took the pain to wipe the phone.
jd1639 said:
Don't think you have a choice if you want the phone to work. You're going to have to format the data.
Click to expand...
Click to collapse
I wanna format my N5, leave it really clean, coz it has the same problem about not mounting storage. But i wanna do it by commands. Can u tell me how can I do that? By adb or fastboot?
tinaag said:
I wanna format my N5, leave it really clean, coz it has the same problem about not mounting storage. But i wanna do it by commands. Can u tell me how can I do that? By adb or fastboot?
Click to expand...
Click to collapse
I'm not sure but you could try adb shell wipe data. Any reason you don't want to do it through twrp?
Sent from my [device_name] using XDA-Developers Legacy app
hello
i flashed lollilop ( google factory image ) via fastboot and the surprise is i've only 16 Giga while my phone is 32
anyone kno how solve this i dont wanna reflash again its the last solution and also it drains battery fast
thanks
I had to factory data reset in stock recovery to fix... Tried clearing cache but no luck.
ok ill try now , tnx
Apparently it was a problem with the userdata.img that came with the stock rom. All I had to do was format the userdata from using fastboot!
For anyone else having the problem, here is the command for formatting userdata:
Code:
fastboot format userdata
Found this in another thread
i did a reset via recovery but still the same and flashed purity kk and still ?
kosaidpo said:
i did a reset via recovery but still the same and flashed purity kk and still ?
Click to expand...
Click to collapse
i got same problem.And cant fix it right now
Jnewell05 said:
Apparently it was a problem with the userdata.img that came with the stock rom. All I had to do was format the userdata from using fastboot!
For anyone else having the problem, here is the command for formatting userdata:
Code:
fastboot format userdata
Found this in another thread
Click to expand...
Click to collapse
thanks just did and its fixed ??
Jnewell05 said:
Apparently it was a problem with the userdata.img that came with the stock rom. All I had to do was format the userdata from using fastboot!
For anyone else having the problem, here is the command for formatting userdata:
Code:
fastboot format userdata
Found this in another thread
Click to expand...
Click to collapse
Thanks mate.Fixed mine problem too
You can also boot into recovery and wipe user data partition that way.
I am thinking of just going on stock android but i like adblock. So i will end up rooting my phone, i was wondering if there is a way to update Lollipop rooted without having to restore. I dont mind loosing my root after every update, i can always re root
thanks guys
rolgar20 said:
I am thinking of just going on stock android but i like adblock. So i will end up rooting my phone, i was wondering if there is a way to update Lollipop rooted without having to restore. I dont mind loosing my root after every update, i can always re root
thanks guys
Click to expand...
Click to collapse
Download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
reboot into your custom recovery
flash the latest SuperSU (http://download.chainfire.eu/supersu)
Elluel said:
Download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
reboot into your custom recovery
flash the latest SuperSU (http://download.chainfire.eu/supersu)
Click to expand...
Click to collapse
Wouldn't that wipe my data?
rolgar20 said:
Wouldn't that wipe my data?
Click to expand...
Click to collapse
The only things that will wipe your data:
unlocking the bootloader (which I assume you already have unlocked due to having root access)
flashing userdata.img (if you read my previous post, I left this out)
wiping the data partition in recovery
factory reset option in Android (which really just boots into recovery and wipes data from there)
Elluel said:
The only things that will wipe your data:
unlocking the bootloader (which I assume you already have unlocked due to having root access)
flashing userdata.img (if you read my previous post, I left this out)
wiping the data partition in recovery
factory reset option in Android (which really just boots into recovery and wipes data from there)
Click to expand...
Click to collapse
Wonderful, thanks!
Hello my Nvidia Shield Tablet (original WIFI) is dead i think
I can get into fastboot and TWRP recovery.
TWRP shows Internal memory as 0mb and is unable to mount anything
I also tried flashing stock images but no luck as it keeps failing and tablet wont boot
Any solution? please help:fingers-crossed:
what did you do to get it to this state? try format data and wipe data in twrp. might take a few tries. could also try flashing stock in twrp rather then fastboot. I've seen similar on my phone (involves encryption error) but never on my shield.
Sent from my SAMSUNG-SM-N900A using Tapatalk
lafester said:
what did you do to get it to this state? try format data and wipe data in twrp. might take a few tries. could also try flashing stock in twrp rather then fastboot. I've seen similar on my phone (involves encryption error) but never on my shield.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Hi this happened after i flashed 5.1 blob from Optimized Rom thread
Try reflashing OTA 5.2 blob as the blob is not just the bootloader but also the GPT partition setup too
Sent from my pa_osprey using Tapatalk
hacktrix2006 said:
Try reflashing OTA 5.2 blob as the blob is not just the bootloader but also the GPT partition setup too
Sent from my pa_osprey using Tapatalk
Click to expand...
Click to collapse
Hello man thanks for the suggestion can you please guide me through this i am not sure about the GPT partition setup?
I just dont want to go wrong thanks
Right using the following commands for flashing the device.
Code:
fastboot flash staging blob
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot format system
fastboot flash system system.img
fastboot format userdata
fastboot format cache
This is how i flash mine when returning to stock.
hacktrix2006 said:
Right using the following commands for flashing the device.
Code:
fastboot flash staging blob
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot format system
fastboot flash system system.img
fastboot format userdata
fastboot format cache
This is how i flash mine when returning to stock.
Click to expand...
Click to collapse
Ok i will try this again and update you
Dalbin Reji said:
Ok i will try this again and update you
Click to expand...
Click to collapse
Ok so i tried flashing this in an unconventional way by rebooting fastboot everytime it failed and then it worked after
but still after i press continue, it says booting failed...
Whats wrong?
Which shield do you have? Original or K1
Sent from my pa_osprey using Tapatalk
Dalbin Reji said:
Ok i will try this again and update you
Click to expand...
Click to collapse
hacktrix2006 said:
Which shield do you have? Original or K1
Sent from my pa_osprey using Tapatalk
Click to expand...
Click to collapse
I have the original WIFI
Make sure your using factory images for that device and not the K1 version
Sent from my pa_osprey using Tapatalk
hacktrix2006 said:
Make sure your using factory images for that device and not the K1 version
Sent from my pa_osprey using Tapatalk
Click to expand...
Click to collapse
Nope man i used the Factory images for Wifi version im sure
Dalbin Reji said:
Nope man i used the Factory images for Wifi version im sure
Click to expand...
Click to collapse
https://developer.nvidia.com/gameworksdownload#?search=Shield Tablet Wifi
Did you use that one?
hacktrix2006 said:
https://developer.nvidia.com/gameworksdownload#?search=Shield Tablet Wifi
Did you use that one?
Click to expand...
Click to collapse
Yep that one exactly, this all happened after i flashed 5.0 blob from an optimized custom rom thread i believe ?
Looks like you have corrupted the boot-loader then hence the issue you have, the chances of recovering from that is very slim. Best to speak to nvidia see if they can help.
hacktrix2006 said:
Looks like you have corrupted the boot-loader then hence the issue you have, the chances of recovering from that is very slim. Best to speak to nvidia see if they can help.
Click to expand...
Click to collapse
Is there no way i can fix it? Probably not then aw
Only Nvidia will be able to fix boot loader issues as they have the magic key for lower level access.
Sent from my SHIELD Tablet K1 using Tapatalk
Maybe you have bricked internal memory eMMC chip
Dalbin Reji said:
I can get into fastboot and TWRP recovery.
TWRP shows Internal memory as 0mb and is unable to mount anything
I also tried flashing stock images but no luck as it keeps failing and tablet wont boot
Click to expand...
Click to collapse
Internal memory as 0mb, and failure to mount anything, often are signs that the internal storage has been corrupted.
Try going to TWRP Wipe section, and tap the button to "Format data". Obviously, you will lose your data. But your data is probably beyond that point, anyway.
Formatting the storage, will often fix corruption issues.
redpoint73 said:
Internal memory as 0mb, and failure to mount anything, often are signs that the internal storage has been corrupted.
Try going to TWRP Wipe section, and tap the button to "Format data". Obviously, you will lose your data. But your data is probably beyond that point, anyway.
Formatting the storage, will often fix corruption issues.
Click to expand...
Click to collapse
Sorry man but when i try @format data it gaves me the same error ''unable to mount.... storage'' etc
Any other method to fix corrupted bootloader?