Hi Guys.
I have an Nexus 5 that was left alone on for a long time, when i got it back, it was Redlight. (battery)
After solving it, it became the most weard problem that i've ever saw.
/data partition just wont format as ext.
it freezes and become corrupt.
But twrp manage to format as F2FS, and it works just fine.
But i want to get stock lollipop in it, and it doesn't work.
Anyone can help me?
tried a lot of tutorials from xda already =\
Did you tried to restore to factory default?
Related
Hi All,
First of all, I'm posting here because I don't have 10 posts to post in development threads.
I have TWRP 2.5.0.2 on my AT&T Galaxy S4, and the 5/30 nightly build of CM10.1. I wanted to make a backup to update to a newer nightly build, but TWRP told me I didn't have enough space to make the backup on my SD.
I looked again and it showed my data partition at 5,272,881 MB, which is obviously incorrect. Anybody have any ideas of what to do from here? I kind of want to do a wipe from TWRP, but I'm afraid of what might happen if I do that.
Thanks in advance
If someone could do me a favor and link my thread in the following thread, it would be much appreciated!
http://forum.xda-developers.com/showthread.php?p=42133601
:crying:
fyirty time
did a full format of the data partition and reflashed the rom, and now it shows up ok.
I've been having this issue also and thought it was 2.5.0.3 that was buggy, I flashed back to 2.5.0.2 and it still showed my /data partition as 68 GB. I'll give your solution a shot, thanks!
Edit: yep that fixed it!
brando56894 said:
I've been having this issue also and thought it was 2.5.0.3 that was buggy, I flashed back to 2.5.0.2 and it still showed my /data partition as 68 GB. I'll give your solution a shot, thanks!
Edit: yep that fixed it!
Click to expand...
Click to collapse
I'm having the same issue with my sprint gs4 and found this thread thru a google search. How do you format your data partition?
Edit: Found the option to format /data in twrp. That worked for me too.
Will formatting data lose the setup? I don't understand why you'd do that if you're trying to make a backup??
Deutch said:
I'm having the same issue with my sprint gs4 and found this thread thru a google search. How do you format your data partition?
Edit: Found the option to format /data in twrp. That worked for me too.
Click to expand...
Click to collapse
Murphy71984 said:
Will formatting data lose the setup? I don't understand why you'd do that if you're trying to make a backup??
Click to expand...
Click to collapse
Yes, you will lose your data, so back it up by other means. The point is to fix the partition so it can be backed up in the future. The problem is that the size is showing incorrectly, not allowing you to backup at all. Once it is fixed, you can back it up normally.
terahertz5k said:
Yes, you will lose your data, so back it up by other means. The point is to fix the partition so it can be backed up in the future. The problem is that the size is showing incorrectly, not allowing you to backup at all. Once it is fixed, you can back it up normally.
Click to expand...
Click to collapse
I have this problem. How was this fixed? I want to be able to backup via TWRP but it is coming up as 81240 MB which I know it isn't.
EDIT: I see that formatting your /data partition can fix it but it hasn't for me. I did a fresh flash a few days ago and formatted it but it is showing up as way too big again.
yeah it's a problem with twrp. formatting data worked for me on cm 10.1, but with cm 10.2 it would go back to insane sizes after installing the rom. i switched to clockworkmod and it works fine now.
Thanks u helped me fix mine
Sent from my SPH-L720 using xda app-developers app
Hey guys,
I searched through here and online, and can't seem to find a solution or REASON for this to have happened, so I made an account! Woo.
I flashed my rooted, cyanogenmod running N5's modem from 4.4.4 to KOT49E and after rebooting the phone, it proudly states I have low storage, that the external storage can't be found, and then swiftkey loses its ****, google play store crashes over and over even though I've not opened it etc etc.
I've wiped the partition cache and the dalvik cache, but it's still not doing ****. I'd really like to avoid reloading a rom on there if I can help it as I've not backed up in a week or so, and I'm sure you all know how much of a ballache THAT is!
so...Thoughts?
First, your should always make a nandriod before flashing anything new.
Can you flash the same modem as you had before?
Sent from my Nexus 5 using XDA Free mobile app
myles_dobson said:
Hey guys,
I searched through here and online, and can't seem to find a solution or REASON for this to have happened, so I made an account! Woo.
I flashed my rooted, cyanogenmod running N5's modem from 4.4.4 to KOT49E and after rebooting the phone, it proudly states I have low storage, that the external storage can't be found, and then swiftkey loses its ****, google play store crashes over and over even though I've not opened it etc etc.
I've wiped the partition cache and the dalvik cache, but it's still not doing ****. I'd really like to avoid reloading a rom on there if I can help it as I've not backed up in a week or so, and I'm sure you all know how much of a ballache THAT is!
so...Thoughts?
Click to expand...
Click to collapse
Are you using CWM recovery? CWM has a bug that reduce your storage to 250mbish size. If that is the case then switch to twrp or philz touch and do a factory reset.
I had some problems after upgrading to OptimizedCM-13-20161224-jflte-AROMA (Update Baseband etc, full wipe, fresh install, restore apps + data using Titanium Backup).
Before I did the upgrade, I converted the internal storage to F2FS-filesystem for extra speed.
The phone constantly froze randomly. I tried to reinstall twice because i thought I'd done something wrong when installing the ROM and restoring my apps etc, but the problem with the phone freezing continued.
After reading this thread: An Explanation of why SuperSU has Trouble with F2FS Data Partitions I tried to revert to EXT4 and do another fresh install and restore of my apps and data. This seems to have solved the problem and my phone now works without any problems.
Just thought I'd let you all know in case someone else encounters this problem.
Hello,
You might want to forward your post to JDCTeam's thread with arter97's explanation...
Sent from my ASUS_Z00A using XDA Labs
Well, i've been using F2FS since 2 releases of opt cm 13 ago, i'm currently on 20161224, and I also face some random freezes, wich didn't happend on the previous build, i'll go back to EXT4 on the next release anyways, starts to annoy me
Hello xda Community,
Yesterday, I reset my nexus 4 device and flash the miui 8 Rom after reboot i discovered that my sytem storage(~800mb) is nearly full... so I am unable to flash any zip or someting like that.
can anyone help me?
Does anyone know how I can fix this problem?
So last night I installed TWRP and flashed a stock rom for my neighbor's phone because it had a bootloop. I made it start again and gave it back to him.
Today, he brought it back saying it had these errors popping up all the time, and that he couldn't use the phone. When I took it, I noticed that it had a constant error saying "the Launcher process has stopped", or something to that extent.
The answer everyone on the web said, was to install Nova Launcher, however, I couldn't even get to the Play Store because of the error popping up all the time, so I decided to reflash the same stock firmware that I had flashed yesterday, in order to buy enough time to get to the store and download Nova Launcher before all the errors came back.
However, this time before attemtpting to flash the phone, I did a complete wipe of user data, since I suspected it may have been what started the errors on the first place.
The thing is that after I wiped the phone, I got some errors while trying to reflash the firmware, errors such as "E: unable to mount /system", the same with /data, /cache and /storage.
Since I was already deep in the mud, I searched for some answers to my problem, and made the mistake of following a peculiar solution: go to wipe, then advanced wipe options, and change the file system from ext4, to ext2 or 3, and then BACK to ext4. People were claiming that it worked and they didn't get the "unable to mount" errors again.
In my case, it didn't seem to work, and now my system and data partitions don't appear to be in the ext4 format, therefore I can't install the stock firmware back into the phone.
Can anyone help me? I hope I explained my case correctly, and I really hope this isn't as scary as it looks.
Please help me
I thought this place was full of experts... please, someone give me a hand!
Bump...
Rockolate said:
Bump...
Click to expand...
Click to collapse
I have exactly the same problem. Did you find any solution?