HI @ all..HELP NEEDED
In TRWP i did a data format but did not help.
I have the x829 version with 64 G storage capacity. With about 55 G to use. Normaly
Now that i flashed it with pure nexus. I only am able to use 10Gig of the 55. because the system uses about 44 Gig... how can I get my storage capacity back. System normaly only uses about 6 gig not 44 GIG
anyone help me ?? Please...
are you mental? why did you opened 3 threads for this issue?
nosidefcp said:
are you mental? why did you opened 3 threads for this issue?
Click to expand...
Click to collapse
More threads = more help :laugh:
At least this is what our guy thought.
For the guy: try the unbrick method, it will retard your phone to EUI 5.6 014s, format internal memory from settings - storage, install TWRP, put latest EUI or whichever ROM you like and flash. If this won't work, I don't know what will.
valy_cta said:
More threads = more help :laugh:
At least this is what our guy thought.
For the guy: try the unbrick method, it will retard your phone to EUI 5.6 014s, format internal memory from settings - storage, install TWRP, put latest EUI or whichever ROM you like and flash. If this won't work, I don't know what will.
Click to expand...
Click to collapse
:silly: yeah sorry for that... Am kind of noobish back here.. tryd al options nothing seems to work
Three of the same threads, but you must be an idiot
Wysłane z mojego Le X820 przy użyciu Tapatalka
S3V3N said:
Three of the same threads, but you must be an idiot
Wysłane z mojego Le X820 przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes idiot idd.
Problem solved.. at each restock with dev eui I forgot to use format internal SD option. By going to factory reset and use option format. Before reflashing recovery trwp and so on.
chetermaat said:
Yes idiot idd.
Problem solved.. at each restock with dev eui I forgot to use format internal SD option. By going to factory reset and use option format. Before reflashing recovery trwp and so on.
Click to expand...
Click to collapse
It's a bit unclear how you managed to solve the issue but as I can barely understand, you formatted internal memory after unbricking and installed TWRP. Am I right?
valy_cta said:
It's a bit unclear how you managed to solve the issue but as I can barely understand, you formatted internal memory after unbricking and installed TWRP. Am I right?
Click to expand...
Click to collapse
I used the unbrick method because that flashes the EUI DEV version. In that specific version under settings backup and restore there is the option to erase data when you perform a Factory reset. After that booted back in EUI to check if storage space indeed went back and it did. From there on I could reinstall TRWP and flash back to PURE NEXUS ROCKING ROM :good: and flashed super user via TRWP to get root back again.
The option of erasing data in TRWP works but doesn't give back storage space that was lost and given to system. The option to erase data storage in other roms isn't there. So therefore you have unbrick and do factory reset with option erase user data...
I was sure this will work, and it will work on almost all problems. Alright, glad to hear that you fixed it.
Related
I was trying to flash jellybomb rom and keep getting this error in
twrp recovery
Unable to mount '/usbstorage
Any one have a solution?
im getting the same issue with trying to bump up from m13 to m15 wont change baseband version or software version.
onemanruler said:
im getting the same issue with trying to bump up from m13 to m15 wont change baseband version or software version.
Click to expand...
Click to collapse
Same here with any rom it seems, even when doing a wipe of any kind.
Im going to try a older version of TWRP, smells like the recovery isnt right in some way, not the roms.
svghost said:
Same here with any rom it seems, even when doing a wipe of any kind.
Im going to try a older version of TWRP, smells like the recovery isnt right in some way, not the roms.
Click to expand...
Click to collapse
Found the fix for it. I followed one of the posts from chain fire who was referred to this method by someone I believe. (I apologize if I'm not giving credit to who referred)
1.Turn phone off
2. Remove sd card
3. Flash mi5 stock recovery( you can find a link in the general form in the let's figure this out guys forum on page 7 or so)
4. Keep sd card out while you boot the phone back up.
5. Update to new mj4
Hope this helps. I take no credit for this I just sumerized the genius devs of this forum who I have come to love since I found this place on my s3. Thanks devs
Sent from my SM-N900P using xda app-developers app
cocaineblunts said:
I was trying to flash jellybomb rom and keep getting this error in
twrp recovery
Unable to mount '/usbstorage
Any one have a solution?
Click to expand...
Click to collapse
Folks, this is NOT an error. It's support for OTG USB storage. Disregard unless you're using a USB OTG adapter and a USB Thumbdrive. Confirmed with the devs. (Which is where this question should have been posted)
Compusmurf said:
Folks, this is NOT an error. It's support for OTG USB storage. Disregard unless you're using a USB OTG adapter and a USB Thumbdrive. Confirmed with the devs. (Which is where this question should have been posted)
Click to expand...
Click to collapse
No this is an error.. It fails to install the rom and the only explanation at the end of the log is Unable to mount USBSTORAGE.. Whether it has anything to do with usbstorage or not that is the error we are getting. I am also getting this error. I wipe everything, go to install a rom and it fails.. I can nandroid back to my stock but that is about all I can do aside from flash some mods.
And for the record.. he's trying to get help and Troubleshoot which is the topic of this portion of the forum so I think it's perfectly placed..
xsisbest said:
No this is an error.. It fails to install the rom and the only explanation at the end of the log is Unable to mount USBSTORAGE.. Whether it has anything to do with usbstorage or not that is the error we are getting. I am also getting this error. I wipe everything, go to install a rom and it fails.. I can nandroid back to my stock but that is about all I can do aside from flash some mods.
And for the record.. he's trying to get help and Troubleshoot which is the topic of this portion of the forum so I think it's perfectly placed..
Click to expand...
Click to collapse
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
The one thing I haven't done is wipe internal .. I was afraid of losing some stuff on my internal card.. I'll back anything up and give it a go. Thank you so much for your help and recommendation! I'll let you know how it goes.. I gotta download Jellybomb again as I tried moving it to my sdcard in recovery and it seems to have disappeared somehow.. . Thanks again!
xsisbest said:
The one thing I haven't done is wipe internal .. I was afraid of losing some stuff on my internal card.. I'll back anything up and give it a go. Thank you so much for your help and recommendation! I'll let you know how it goes.. I gotta download Jellybomb again as I tried moving it to my sdcard in recovery and it seems to have disappeared somehow.. . Thanks again!
Click to expand...
Click to collapse
Sure thing,if somebody that has MJ4 with passwords sticking can do a factory reset then TWRP back up their system partition and post it I may be able to make a zip that fixes this issue. Of course this is exactly what freeza did I am sure so it may not work but I could give it a try. I will pull system from the girlfriends phone but she is on a plane and gone for the weekend so it may be next week before I can get hers.
ifly4vamerica said:
Sure thing,if somebody that has MJ4 with passwords sticking can do a factory reset then TWRP back up their system partition and post it I may be able to make a zip that fixes this issue. Of course this is exactly what freeza did I am sure so it may not work but I could give it a try. I will pull system from the girlfriends phone but she is on a plane and gone for the weekend so it may be next week before I can get hers.
Click to expand...
Click to collapse
So I put the rom on my card, rebooted, wiped ONLY cache and dalvik and flashed the rom and it worked.. lol. This is what is called a dirty flash coming from the Evo LTE.. I would never have done this lol.. But if it works whatever lol. Thanks again for the recommendation. It actually installs more like a theme than a rom. Always interesting to learn the changes from phone to phone. Excited to see what's to come!
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
thank you kind sir.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
Tried this, still get the error, at least on the Tmobile Note 3.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
Did ya have the backup on your external? If I'm reading this right, you wiped your internal storage. I've yet to successfully get a clean backup onto my external. It sounds like this could come in very handy, I just want to make sure I understand the steps in case I want to use this. Thanks, bro.
Sent from my Nexus 7 using Xparent BlueTapatalk 2
micmars said:
Did ya have the backup on your external? If I'm reading this right, you wiped your internal storage. I've yet to successfully get a clean backup onto my external. It sounds like this could come in very handy, I just want to make sure I understand the steps in case I want to use this. Thanks, bro.
Sent from my Nexus 7 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yep had the backup on external. When this happened to me it was after taking the OTA to MJ4. Basically I had odined to full stock, factory reset and wiped internal. Then I removed external SD. Rebooted and took the MJ4 update. After this I flashed TWRP before CF auto root, this took me to an endless boot loop. I couldn't flash anything and anything I tried to run in Odin failed. So I wiped everything again, formatted system and data, tossed in the external SD and restored a nan droid. Presto I was back in business. I think having twrp flashed before cf auto root may have been the culprit. After I restored the nan droid I reran cf first then twrp. Since then no issues at all. In fact I have restored several nan droids from external and have had no problems.
Those nan droids were only of system, data and boot. I am using the latest TWRP with a scan disk 64gb external. I can't remember if it is formatted NTFS or fat32.... I will have to check that for you if you need the info. I am pretty sure it is NTFS but I did have it formatted fat32 for a while so like I said I will have to check that to be sure.
Break.....
In reply to the other post, if you have a T-Mobile version I would try the efs partition restore. I don't have the link anymore but it is in xda forum somewhere, if you search or ask around somebody is bound to know what thread it is in.
Last thing to try is wiping in recovery first then if the flash fails just reboot back to recovery with the twrp menu. Then don't wipe and try the flash again.
I have kind of jumped around a bit with the explanation and couple more things to try, hopefully it makes sense.
Note 3 or Gear Sent
ifly4vamerica said:
Yep had the backup on external. When this happened to me it was after taking the OTA to MJ4. Basically I had odined to full stock, factory reset and wiped internal. Then I removed external SD. Rebooted and took the MJ4 update. After this I flashed TWRP before CF auto root, this took me to an endless boot loop. I couldn't flash anything and anything I tried to run in Odin failed. So I wiped everything again, formatted system and data, tossed in the external SD and restored a nan droid. Presto I was back in business. I think having twrp flashed before cf auto root may have been the culprit. After I restored the nan droid I reran cf first then twrp. Since then no issues at all. In fact I have restored several nan droids from external and have had no problems.
Those nan droids were only of system, data and boot. I am using the latest TWRP with a scan disk 64gb external. I can't remember if it is formatted NTFS or fat32.... I will have to check that for you if you need the info. I am pretty sure it is NTFS but I did have it formatted fat32 for a while so like I said I will have to check that to be sure.
Break.....
In reply to the other post, if you have a T-Mobile version I would try the efs partition restore. I don't have the link anymore but it is in xda forum somewhere, if you search or ask around somebody is bound to know what thread it is in.
Last thing to try is wiping in recovery first then if the flash fails just reboot back to recovery with the twrp menu. Then don't wipe and try the flash again.
I have kind of jumped around a bit with the explanation and couple more things to try, hopefully it makes sense.
Note 3 or Gear Sent
Click to expand...
Click to collapse
I believe that the T-Mobile efs partition fix works great on this phone, if it's the miracle zip to which you are referring (small zip file labeled brick bootloop fix after restoring backup, or something to that effect).
The external SD card I'm using is only 16 GB (yeah, I know), so definitely not a problem with the way it's formatted (it's the one I had on my E4GT). It just fails on backup. I may try it again sometime, but just got tired of that red fail message.
Your explanation is clear and useful.
FWIW, I believe that boot, system and data comprise a complete backup, unless the efs gets fried. Also, I think that you may be right, that the TWRP then autoroot may have been the culprit, but back in business is way awesome (pain while in the mire, though).
In preparation for KitKat, I think a large external SD card is my next purchase, along with a complete wiping of internal, clean start and all.
Thanks for the info. Very helpful.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I believe that the T-Mobile efs partition fix works great on this phone, if it's the miracle zip to which you are referring (small zip file labeled brick bootloop fix after restoring backup, or something to that effect).
The external SD card I'm using is only 16 GB (yeah, I know), so definitely not a problem with the way it's formatted (it's the one I had on my E4GT). It just fails on backup. I may try it again sometime, but just got tired of that red fail message.
Your explanation is clear and useful.
FWIW, I believe that boot, system and data comprise a complete backup, unless the efs gets fried. Also, I think that you may be right, that the TWRP then autoroot may have been the culprit, but back in business is way awesome (pain while in the mire, though).
In preparation for KitKat, I think a large external SD card is my next purchase, along with a complete wiping of internal, clean start and all.
Thanks for the info. Very helpful.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I'm sure the 64gb cards are much cheaper now. I think I got mine on amazon for like 50 over a year ago.
Every time I want to do a "clean" install I format the internal memory. I usually have backups of apps/data/rom on the sd card which makes using mybackup pro awesome to restore apps/data. But for whatever reason I am having trouble using mybackup with this phone..
So I've kinda been chillen on freezas rom / kernel waiting for development to increase more (it's coming along great)
Sent from my SM-N900P using Tapatalk
tt281gt said:
I'm sure the 64gb cards are much cheaper now. I think I got mine on amazon for like 50 over a year ago.
Every time I want to do a "clean" install I format the internal memory. I usually have backups of apps/data/rom on the sd card which makes using mybackup pro awesome to restore apps/data. But for whatever reason I am having trouble using mybackup with this phone..
So I've kinda been chillen on freezas rom / kernel waiting for development to increase more (it's coming along great)
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Been running that rom for quite a long time.
Yeah, I was looking at prices for 64 GB cards. Prices look quite good.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I have run into this same problem. This is my first time tyring to flash on my note 3 and when I wipe or try to flash the rom I get the error that it is unable to mount usbstorage. I don't fully understand how you fixed this? Is there a stock image I need to flash?
Also a friend of my said that there is an issue with doing restores on the note 3, that it causes a bootloop. Is this true? It's the first I've heard of it
mike208 said:
I have run into this same problem. This is my first time tyring to flash on my note 3 and when I wipe or try to flash the rom I get the error that it is unable to mount usbstorage. I don't fully understand how you fixed this? Is there a stock image I need to flash?
Also a friend of my said that there is an issue with doing restores on the note 3, that it causes a bootloop. Is this true? It's the first I've heard of it
Click to expand...
Click to collapse
I have personally been switching back and forth between maximus ROM and AOSP and have had no issues with restoring backups through TWRP. As far as the unable to mount USB storage error I believe everyone gets that but it has never caused me an issue with flashing a ROM. It is looking for a mass storage device if I am correct. Sometimes after I do a factory reset I rebbot twrp back into recovery before I flash a new ROM and have not had any issues. Someone please chime in if you know better than I.
Hope this helps in some way.
Sent from my SM-N900P using Tapatalk
mhutton said:
I have personally been switching back and forth between maximus ROM and AOSP and have had no issues with restoring backups through TWRP. As far as the unable to mount USB storage error I believe everyone gets that but it has never caused me an issue with flashing a ROM. It is looking for a mass storage device if I am correct. Sometimes after I do a factory reset I rebbot twrp back into recovery before I flash a new ROM and have not had any issues. Someone please chime in if you know better than I.
Hope this helps in some way.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Not sure if it affected the wip or not, but I got that error pretty quick during the flash. I don't see how the rom could have flashed in under 10 seconds, so I do think it is affecting it from flashing and possibly wiping. Thanks for the info about the restore though
My oncle offers me an international galaxy S3 but only with 547 mb total space.
I want to know if it is a bad partition issue or a manufacturing defect .
I'm living in Africa an in my country there is no samsung repair center.
The phone is rooted and runs a 4.2.2 custom rom (Carbon) with Boeffla-Kernel
Sorry for my english, i speak french
Thanks
edmalou33 said:
My oncle offers me an international galaxy S3 but only with 547 mb total space.
I want to know if it is a bad partition issue or a manufacturing defect .
I'm living in Africa an in my country there is no samsung repair center.
The phone is rooted and runs a 4.2.2 custom rom (Carbon) with Boeffla-Kernel
Sorry for my english, i speak french
Thanks
Click to expand...
Click to collapse
maybe its full of nandroid backups, have you checked for the nandroid backup. you you have clockworkmod recovery installed try to see if any nandroid backups are stored in /data/media/clockworkmod/backup/, it there are any you may backup them to your pc and delete them and get the free space. this happens when backup in internal storage is performed.. one backup may be from 1-3 GBs depending upon different partitions.
suyash1629 said:
maybe its full of nandroid backups, have you checked for the nandroid backup. you you have clockworkmod recovery installed try to see if any nandroid backups are stored in /data/media/clockworkmod/backup/, it there are any you may backup them to your pc and delete them and get the free space. this happens when backup in internal storage is performed.. one backup may be from 1-3 GBs depending upon different partitions.
Click to expand...
Click to collapse
No nandroid backup found in clockworkmod recovery, il also try to browse folders manually with root explorer. if found 3 folder in /data/media : /data/media/0 ; /data/media/legacy and /data/media/obb
To get all the storage space back go to settings, security and factory reset. This will wipe the phone data and format the internal storage.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
To get all the storage space back go to settings, security and factory reset. This will wipe the phone data and format the internal storage.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
but that won't delete the backups made, i have tried that so m telling this.. we have to manually delete the backups..
boomboomer said:
To get all the storage space back go to settings, security and factory reset. This will wipe the phone data and format the internal storage.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I've tried an also tried to wipe from CWM recovery but the problem remains.
edmalou33 said:
I've tried an also tried to wipe from CWM recovery but the problem remains.
Click to expand...
Click to collapse
Have you tried what i said? have you checked for backups made by CWM in internal storage?
suyash1629 said:
Have you tried what i said? have you checked for backups made by CWM in internal storage?
Click to expand...
Click to collapse
Yes i have tried, and unfortunatelly don't find any backup.
edmalou33 said:
Yes i have tried, and unfortunatelly don't find any backup.
Click to expand...
Click to collapse
can you tell whats your total space.. i think you it would be better if you once try to Firmware Upgrade and Initialization from Kies..
suyash1629 said:
can you tell whats your total space.. i think you it would be better if you once try to Firmware Upgrade and Initialization from Kies..
Click to expand...
Click to collapse
My total space is 547MB
I've flash several stock roms via Odin and get IMEI ans SN 000xxx issues. Carbon CFW + Boeffla kernel + zuluman patched modem.bin just save my life. so I'm really scared about flashing a stock rom again
edmalou33 said:
My total space is 547MB
I've flash several stock roms via Odin and get IMEI ans SN 000xxx issues. Carbon CFW + Boeffla kernel + zuluman patched modem.bin just save my life. so I'm really scared about flashing a stock rom again
Click to expand...
Click to collapse
this is because u didn't read the Faq's and Guides first.Why all beginners nowdays don't read the faqs and guides nowdays... and let me tell you what is giving this problem, its because of flashing lots of firmware and roms even without knowing what wrong that would do, this is not a manufacture defect.. and as you said there is no repair center,this would be nearly impossible to find out the solution to your problem.. have you visited other repair shops or centers, who sell samsung's phone and repair too, maybe they can solve this problem..
suyash1629 said:
this is because u didn't read the Faq's and Guides first.Why all beginners nowdays don't read the faqs and guides nowdays... and let me tell you what is giving this problem, its because of flashing lots of firmware and roms even without knowing what wrong that would do, this is not a manufacture defect.. and as you said there is no repair center,this would be nearly impossible to find out the solution to your problem.. have you visited other repair shops or centers, who sell samsung's phone and repair too, maybe they can solve this problem..
Click to expand...
Click to collapse
I've flashed stock firmwares just to try to fix my 547Mb storage pb, not for fun...
As a good GS3 beginner, i've read the FAQ, that's why i've backed up my efs partition and restore it when i face the IMEI + SN issue.
No there is not such repair shops or centers in my country.
I have no choice, i think i would rather buy a 16 or 32gb sdcard and find a way to put my apps on external sdcard
Thank you for your replies :good:
edmalou33 said:
I've flashed stock firmwares just to try to fix my 547Mb storage pb, not for fun...
As a good GS3 beginner, i've read the FAQ, that's why i've backed up my efs partition and restore it when i face the IMEI + SN issue.
No there is not such repair shops or centers in my country.
I have no choice, i think i would rather buy a 16 or 32gb sdcard and find a way to put my apps on external sdcard
Thank you for your replies :good:
Click to expand...
Click to collapse
i said that because you said "Carbon CFW + Boeffla kernel + zuluman patched modem.bin just save my life.".. well, using a external sd card is only the last choice for you..
Or install Philz recovery and mount then format internal sd.
Sent from my GT-I9300 using Tapatalk
I've got the latest version of TWRP and trying to make a backup. It says there's not enough room. I have the SD card selected and it has 7 free GB of space. 13.3GB of internal storage is used. Is there no compression? This was working fine until I upgraded to Marshmallow.
Also I'm a bit surprised to see internal storage so full, I just installed Marshmallow.
lightningglasses said:
I've got the latest version of TWRP and trying to make a backup. It says there's not enough room. I have the SD card selected and it has 7 free GB of space. 13.3GB of internal storage is used. Is there no compression? This was working fine until I upgraded to Marshmallow.
Also I'm a bit surprised to see internal storage so full, I just installed Marshmallow.
Click to expand...
Click to collapse
Which partition(s) did you wish to back up?
iXaidyiu said:
Which partition(s) did you wish to back up?
Click to expand...
Click to collapse
That's a good question. I guess all of them but the cache? How do I decide which need to be backed up if the goal is to be able to restore from a damaged device?
lightningglasses said:
That's a good question. I guess all of them but the cache? How do I decide which need to be backed up if the goal is to be able to restore from a damaged device?
Click to expand...
Click to collapse
Usually /system, /data, and /boot. And these partition usually exceed 7GB, which in your case 13GB. That means your SD card is too small to handle the backup.
Sent from my Sony Xperia Z2 using XDA Labs
I have Redmi Note 3 , 3GB ram and 32 internal storage.
When using MIUI ROM I got 24 GB of internal storage.
But after using custom ROM my available internal storage reduce to 9.47gb. Is it common problem?
I'm unofficially unlocked , using Orion OS ROM with dominator kernel.
CopyMasta said:
I have Redmi Note 3 , 3GB ram and 32 internal storage.
When using MIUI ROM I got 24 GB of internal storage.
But after using custom ROM my available internal storage reduce to 9.47gb. Is it common problem?
I'm unofficially unlocked , using Orion OS ROM with dominator kernel.
Click to expand...
Click to collapse
No, it happened because you had not wiped your "internal storage" before flashing the ROM. I don't blame you for that. This things happen. You have your data which was earlier in your phone to some other directory in /data/media/0/ or in /mnt somewhere, I don't exactly remember. You can just delete that data, or copy it back
sasukay said:
No, it happened because you had not wiped your "internal storage" before flashing the ROM. I don't blame you for that. This things happen. You have your data which was earlier in your phone to some other directory in /data/media/0/ or in /mnt somewhere, I don't exactly remember. You can just delete that data, or copy it back
Click to expand...
Click to collapse
Thank you for the explanation, later tonight I will reflash again with wiping the internal storage.
CopyMasta said:
Thank you for the explanation, later tonight I will reflash again with wiping the internal storage.
Click to expand...
Click to collapse
If it don't work, flash MIUI again with unofficial bootloader unlock method, unlock the bootloader and BEFORE INSTALL TWRP OR ANY CUSTOM ROM, boot into MIUI and check if you has entire internal storage. If yes, you're done to go!
I have exactly the same problem. I tried both nexus experiene and exodus rom. Also unofficially unlocked with twrp installed. I have the Kate 32gb variant, but even when I wipe internal storage beforehand I always get 8gb out of 9gb free space. Any help, because I am completely out of ideas.
Jacques10111 said:
I have exactly the same problem. I tried both nexus experiene and exodus rom. Also unofficially unlocked with twrp installed. I have the Kate 32gb variant, but even when I wipe internal storage beforehand I always get 8gb out of 9gb free space. Any help, because I am completely out of ideas.
Click to expand...
Click to collapse
hi have you fixed this problem?. please let me know how to fix this problem if you have fixed this problem.
Flash MIUI and boot into MIUI (complete setup) before you wipe anything
Like title says.
After flashing Xpower 5, I realised my internal storage is now only 16gb.
It was working fine, but went to try that kryptonian Rom, failed to I restored back to Xpower.
But apparently, not my internal storage is missing 16gb.
nzzane said:
Like title says.
After flashing Xpower 5, I realised my internal storage is now only 16gb.
It was working fine, but went to try that kryptonian Rom, failed to I restored back to Xpower.
But apparently, not my internal storage is missing 16gb.
Click to expand...
Click to collapse
Check from here.
http://forum.xda-developers.com/showpost.php?p=69424379&postcount=844
mele80 said:
Check from here.
http://forum.xda-developers.com/showpost.php?p=69424379&postcount=844
Click to expand...
Click to collapse
Saved my life, thanks!
I had this issue, but fixed it with a clean install. Now, a week or two later it's back. Any ideas on how to permanently fix this?
Procrustinator said:
I had this issue, but fixed it with a clean install. Now, a week or two later it's back. Any ideas on how to permanently fix this?
Click to expand...
Click to collapse
Using TWRP to resize the /system partition seemed to fix mine, maybe try that?
nzzane said:
Using TWRP to resize the /system partition seemed to fix mine, maybe try that?
Click to expand...
Click to collapse
This time, I actually got by with just doing a restart. Thanks for the suggestion, though. I might have to use it in the future.