Does the data partition formatted to F2FS cause random reboots? I cant seem to narrow it down to anything else. Every nougat rom i tried so far seems to random reboot 3-4 times a day with clean installs. What file format is recommended for custom roms on this phone?
you need a custom kernel for that i think, i thin firekernel has support.
idk tho i dont have experience with it
I believe that ext4 is the stock filesystem type for the data partition, I've never changed it.
Actually, the stock ROM has the data partition formatted as F2FS. It's one of the factors in making the lower end processor seem as fast and snappy as it is.
You can check it in TWRP recovery. Go to advanced wipe and check the formatting for the data partition.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
Actually, the stock ROM has the data partition formatted as F2FS. It's one of the factors in making the lower end processor seem as fast and snappy as it is.
You can check it in TWRP recovery. Go to advanced wipe and check the formatting for the data partition.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hmm... Your right, a quick look at mount in the terminal confirms that. Sorry, my bad.
Now that we know that, I guess the F2FS file system type is probably not the cause of your issues.
acejavelin said:
Hmm... Your right, a quick look at mount in the terminal confirms that. Sorry, my bad.
Now that we know that, I guess the F2FS file system type is probably not the cause of your issues.
Click to expand...
Click to collapse
Yes. I've tried different combinations of partitions formatted to f2fs and it would only work using data as F2FS. Im using the newest aosp extended. Maybe this rom will fix my reboot problems. I am new to this phone coming from a falcon. I know one thing, i am not enjoying moto display. The screen seems to turn on when you dont want it to all the time. I miss my notification LED.
Related
Just flash in clockwork and it will format your system and data partitions back to ext3. Faster than dealing with nandroid restores.
Useful for reverting from installs using Dragon or Trinity kernels that convert you to ext4.
NOTE: This FORMATS your partitions, you WILL lose all data held on them. Your phone will NOT boot until you install a ROM ZIP file or restore a nandroid backup. YOU HAVE BEEN WARNED.
CREDIT: @paulobrien from Modaco wrote this for the O2x. I just changed the partition names to match our setup. I left his original banner in there as a result. My change amounts to about 4 bytes. If you have issues, please don't bother him, post here.
This is great...I always hesitate trying out updated or experimental kernels because of the amount of time it takes to nandroid....the cm7 kernel has been really good as of late so I've been sticking with that
Sent from my LG-P999 using XDA App
Hmmm Let the confusing questions begin in 5,4,3,2....
Thanks man!
Sent From My Stock G2x
Reminder: NONE of my kernels and ROMs require the use of this utility. All of my kernels and ROMs are ALL NATIVE EXT3 only mounted as ext4.
faux123 said:
Reminder: NONE of my kernels and ROMs require the use of this utility. All of my kernels and ROMs are ALL NATIVE EXT3 only mounted as ext4.
Click to expand...
Click to collapse
wow, i never knew that. so if we are using one of your cm7 ext4 kernels and then flash a new nightly/kang we could go back to using the stock cm kernel and wouldn't have to necessarily flash your kernel again?
mattyg151 said:
wow, i never knew that. so if we are using one of your cm7 ext4 kernels and then flash a new nightly/kang we could go back to using the stock cm kernel and wouldn't have to necessarily flash your kernel again?
Click to expand...
Click to collapse
Yeap... should be no issues.
Is there a difference between this and just wiping, formating system and data, in cwm?
Sent from my LG-P999 using Tapatalk
billydroid said:
Is there a difference between this and just wiping, formating system and data, in cwm?
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
cwm is set up to keep whatever format you have at the time you run it, so if you are on ext4, the format command will format to ext4. It makes sense, you wouldn't want to write an ext4 fs onto a partition with vfat on it, for example. Not automatically anyway. And most users wouldn't know what to tell it to use if it were to give you the option. The forum would be full of "What file system do I use?!?!?"... The usual method is to restore a nandroid backup from stock or a stock file system. This is significantly faster.
It is of somewhat limited usefulness as many kernels/roms don't change the filesystem. However, as I switch around a lot with running tests for the cm guys, my own stuff, etc., it's nice to have a fast way to deal with it.
ttabbal said:
cwm is set up to keep whatever format you have at the time you run it, so if you are on ext4, the format command will format to ext4. It makes sense, you wouldn't want to write an ext4 fs onto a partition with vfat on it, for example. Not automatically anyway. And most users wouldn't know what to tell it to use if it were to give you the option. The forum would be full of "What file system do I use?!?!?"... The usual method is to restore a nandroid backup from stock or a stock file system. This is significantly faster.
It is of somewhat limited usefulness as many kernels/roms don't change the filesystem. However, as I switch around a lot with running tests for the cm guys, my own stuff, etc., it's nice to have a fast way to deal with it.
Click to expand...
Click to collapse
Thanks
Sent from my LG-P999 using Tapatalk
EDIT: nvm. looked over the files and got my answer.
Works great thanks for putting this together. Will come in handy.
Sent from my LG-P999 using XDA App
is this utility gonna wipe out all my data (meaning I will have to install all the apps again, setting up my phone again, signing in to google again and stuff) ?
te_quiero_forever_girl said:
is this utility gonna wipe out all my data (meaning I will have to install all the apps again, setting up my phone again, signing in to google again and stuff) ?
Click to expand...
Click to collapse
Yes it will wipe.
Upgrading EXT3 to EXT4 will preserve data but downgrading from EXT4 to EXT3 won't.
With cm going ext4 this is priceless.
Sent from my LG-P999 using xda premium
xsteven77x said:
With cm going ext4 this is priceless.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
A nandroid of ext3 is the same thing also I have installed an ext3 rom over ext4 works great
Sent from my LG-P999 using XDA App
Why do we people want to go back to ext3 when ext4 is much faster and stable than all the other filesystems.
Sent from my LG-P999 using xda premium
Hello all,
I would like to reflash CROMi-X and the MAX kernel but this time I want to do it as cleanly as possible. What are the steps to do this. I see it referenced all over that it is best to do a clean install but I can't find out exactly how to do it.
Sorry if this is a stupid question or if it is detailed somewhere that I could not find it but I want a good procedure that I can use whenever flashing new ROMS and kernels to be sure there is nothing hanging around that would cause variability in the install.
Thanks in advance for any help
Jeff
gixxer340 said:
Hello all,
I would like to reflash CROMi-X and the MAX kernel but this time I want to do it as cleanly as possible. What are the steps to do this. I see it referenced all over that it is best to do a clean install but I can't find out exactly how to do it.
Sorry if this is a stupid question or if it is detailed somewhere that I could not find it but I want a good procedure that I can use whenever flashing new ROMS and kernels to be sure there is nothing hanging around that would cause variability in the install.
Thanks in advance for any help
Jeff
Click to expand...
Click to collapse
Depends on which recovery you have installed -- the most often recommended sequence seems to be "wipe data/factory reset, wipe cache, wipe Dalvik cache, reinstall". Obviously, you may need to remove some apps' data folders from /sdcard by hand.
The opinions are divided as far as wiping the caches is concerned -- some do, some don't.
MartyHulskemper said:
Depends on which recovery you have installed -- the most often recommended sequence seems to be "wipe data/factory reset, wipe cache, wipe Dalvik cache, reinstall". Obviously, you may need to remove some apps' data folders from /sdcard by hand.
The opinions are divided as far as wiping the caches is concerned -- some do, some don't.
Click to expand...
Click to collapse
I have TWRP 2.5 installed. Is the above the process for TWRP
Thanks
Jeff
gixxer340 said:
I have TWRP 2.5 installed. Is the above the process for TWRP
Thanks
Jeff
Click to expand...
Click to collapse
In TWRP select 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
[Q=berndblb;43602193]In TWRP MI lect 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD[/QUOTE]
I dont seem to be able to see my microSD card from TWRP. It is formatted as ntfs, I wonder if that is the issue. What should it be formatted as?
Thanks
Jeff
gixxer340 said:
[Q=berndblb;43602193]In TWRP MI lect 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I dont seem to be able to see my microSD card from TWRP. It is formatted as ntfs, I wonder if that is the issue. What should it be formatted as?
Thanks
Jeff[/QUOTE]
Yeah, it has to be FAT32. Actually exFAT seems to work too. Just tried it, and TWRP sees the nandroid on a 8gb exFAT fine. Didn't try to restore though...
Sent from my DROID4 using Tapatalk 2
berndblb said:
I dont seem to be able to see my microSD card from TWRP. It is formatted as ntfs, I wonder if that is the issue. What should it be formatted as?
Thanks
Jeff
Click to expand...
Click to collapse
Yeah, it has to be FAT32. Actually exFAT seems to work too. Just tried it, and TWRP sees the nandroid on a 8gb exFAT fine. Didn't try to restore though...
Sent from my DROID4 using Tapatalk 2[/QUOTE]
Reformatting exFAT right now. Hopefully that will work.
Thanks again,
Jeff
berndblb said:
In TWRP select 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Hi, without hijacking this thread - i've installed Cromix and everything is running great, but i can still see folders and files i had created when my 700 was stock. Am i doing something wrong here? I would have thought that wiping everything except for the microsd card would have given me a blank slate to start with but it seems there is a fair amount of data left over after the ROM flash.
Actually as i'm typing this i've just had a thought, is it a case that the documents, pics, wallpapers etc are on a separate partition (for want of a better definition) and they're just visible after the installation?
thanks,
sean
2Droidswalking said:
Hi, without hijacking this thread - i've installed Cromix and everything is running great, but i can still see folders and files i had created when my 700 was stock. Am i doing something wrong here? I would have thought that wiping everything except for the microsd card would have given me a blank slate to start with but it seems there is a fair amount of data left over after the ROM flash.
Actually as i'm typing this i've just had a thought, is it a case that the documents, pics, wallpapers etc are on a separate partition (for want of a better definition) and they're just visible after the installation?
thanks,
sean
Click to expand...
Click to collapse
I have noticed that problems a while back when I am using TWRP 2.5.0.0. Therefore, I always prefer to use Format instead of Wipe.
2Droidswalking said:
Hi, without hijacking this thread - i've installed Cromix and everything is running great, but i can still see folders and files i had created when my 700 was stock. Am i doing something wrong here? I would have thought that wiping everything except for the microsd card would have given me a blank slate to start with but it seems there is a fair amount of data left over after the ROM flash.
Actually as i'm typing this i've just had a thought, is it a case that the documents, pics, wallpapers etc are on a separate partition (for want of a better definition) and they're just visible after the installation?
thanks,
sean
Click to expand...
Click to collapse
If you wipe or factory reset in TWRP, it erases everything except the /data/media folder, and that is where your data lives.... You have to manually erase those files if you want to get rid of them.
Interestingly, you'll find symlinks to the contents of /data/media in 4!! locations:
/sdcard
/storage/sdcard0
/storage /emulated/0
/storage /emulated /legacy
This crazy structure is due to the multi user support in JB 4.2. I still have a hard time to get my head around it....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
If you wipe or factory reset in TWRP, it erases everything except the /data/media folder, and that is where your data lives.... You have to manually erase those files if you want to get rid of them.
Interestingly, you'll find symlinks to the contents of /data/media in 4!! locations:
/sdcard
/storage/sdcard0
/storage /emulated/0
/storage /emulated /legacy
This crazy structure is due to the multi user support in JB 4.2. I still have a hard time to get my head around it....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
:good: Thanks, it is good to know.
berndblb said:
If you wipe or factory reset in TWRP, it erases everything except the /data/media folder, and that is where your data lives.... You have to manually erase those files if you want to get rid of them.
Interestingly, you'll find symlinks to the contents of /data/media in 4!! locations:
/sdcard
/storage/sdcard0
/storage /emulated/0
/storage /emulated /legacy
This crazy structure is due to the multi user support in JB 4.2. I still have a hard time to get my head around it....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
How incredibly bizarre....but interesting nonetheless. 23 years in IT and it's time to start learning again. I kept going back to Settings>About and could see that the ROM was flashed, but the sight of the old files was making me think 'maybe it just reinstalled over the top of the stock ROM without deleting any data'....sort of like when windoze does a repair and keeps the data. Now that i understand user data is stored in a separate place away from the ROM itself, it makes it easier to upgrade and mess around. Backups are important, but it's nice to know you don't have to constantly relocate data and files when you're doing an upgrade.
Thanks for the info.....these forums are an absolute boon for people willing to ask questions and i'm amazed at the knowledge base that's been accumulated and is being shared - for the first time in a long time, tech toys are fun again. Now to choose a Kernel!!!!
The rom gets flashed to it's own partition: /system/...
If you watch the script when flashing CromiX, the installer formats the system partition automatically before flashing the rom. So you did not install over the old rom. The Data partition is different.
I'm now backing up data/media and then I will use the "Format Data" option in TWRP. Wanna know what exactly happens
Sent from my DROID4 using Tapatalk 2
Just an update...i haven't changed kernels at all and i'm not going to be. This thing is faster and more stable than i could have wished for. Since the ROM was flashed i've stopped messing around with it and it just runs like a dream. It never reboots unless i tell it to, doesn't hang when i have multiple apps open and the battery life is fantastic.
Thanks for the advice berndblb :good:
2Droidswalking said:
Just an update...i haven't changed kernels at all and i'm not going to be. This thing is faster and more stable than i could have wished for. Since the ROM was flashed i've stopped messing around with it and it just runs like a dream. It never reboots unless i tell it to, doesn't hang when i have multiple apps open and the battery life is fantastic.
Thanks for the advice berndblb :good:
Click to expand...
Click to collapse
:GOOD:
Glad I could help.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
So, I'm trying to understand how and why the file system acts the way it does.
Example. I have
/sdcard
and this has a bunch of stuff under it
then i have
/sdcard/0
this has some of the same stuff under it as /sdcard, but is a different file system
Why can I not just have a simple file system that I can understand! I seem to have issues with space because sometimes wiping the phone does not wipe the /sdcard/0 so I am working out of /sdcard/0 as opposed to the base of /sdcard
Any help? I am an idiot so explain like I'm 5, if possible.
Thanks in advance.
n0xide said:
So, I'm trying to understand how and why the file system acts the way it does.
Example. I have
/sdcard
and this has a bunch of stuff under it
then i have
/sdcard/0
this has some of the same stuff under it as /sdcard, but is a different file system
Why can I not just have a simple file system that I can understand! I seem to have issues with space because sometimes wiping the phone does not wipe the /sdcard/0 so I am working out of /sdcard/0 as opposed to the base of /sdcard
Any help? I am an idiot so explain like I'm 5, if possible.
Thanks in advance.
Click to expand...
Click to collapse
5 year old explanation.
4.3 and above Android systems implement a multi user file setup similar to what Windows and OSx uses. The 0 folder is your account, your significant other could be 1, your dog could be 2, this keeps going depending how many users are registered to the device. It's actual intent is to use multi user on a tablet interface, not a phone, but because jellybean is used on both phones and tablets the file structure is the same.
Normally you don't have to worry about much of this, but if you came from 4.1 jellybean then multiuser wasn't implemented yet. This would double up your data in both places.
To me it sounds like you're OK, it's going to show double files because it's essentially reading the exact same folder, the format isn't going to understand what you're trying to do because it doesn't really know where to look for your data files. Basically, leave your 0 folder alone because that's where your data is supposed to be stored.
Was that 5 year old enough?
Edit: if you format your internal SD card in your recovery, then you'll erase the doubled data, and your folder structure will be repopulated under the 0 folder system. If you're running out of internal storage that's what you should do. Then clean flash the rom of your choice following the format.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
5 year old explanation.
4.3 and above Android systems implement a multi user file setup similar to what Windows and OSx uses. The 0 folder is your account, your significant other could be 1, your dog could be 2, this keeps going depending how many users are registered to the device. It's actual intent is to use multi user on a tablet interface, not a phone, but because jellybean is used on both phones and tablets the file structure is the same.
Normally you don't have to worry about much of this, but if you came from 4.1 jellybean then multiuser wasn't implemented yet. This would double up your data in both places.
To me it sounds like you're OK, it's going to show double files because it's essentially reading the exact same folder, the format isn't going to understand what you're trying to do because it doesn't really know where to look for your data files. Basically, leave your 0 folder alone because that's where your data is supposed to be stored.
Was that 5 year old enough?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yeah! That's a pretty solid explanation! I couldn't seem to find anywhere that broke it down that way.
So let me ask one more 5 year old question.
I seem to have TONS of space used up on my SD card, that I cannot free up.
I have a 16Gig GSIII, when I attach my phone to windows, I have 7gb free of 12gb. I just wiped system, cache, and dalvik, and have a clean version of Beanstalk 4.4.2.
How am I using 5gb when the OS itself is only, ~199Mb.
Is there anyway to have a completely clean install? Even when I soft bricked, and then revived w/odin and an old kernal, I don't think it was totally clean.
n0xide said:
Yeah! That's a pretty solid explanation! I couldn't seem to find anywhere that broke it down that way.
So let me ask one more 5 year old question.
I seem to have TONS of space used up on my SD card, that I cannot free up.
I have a 16Gig GSIII, when I attach my phone to windows, I have 7gb free of 12gb. I just wiped system, cache, and dalvik, and have a clean version of Beanstalk 4.4.2.
How am I using 5gb when the OS itself is only, ~199Mb.
Is there anyway to have a completely clean install? Even when I soft bricked, and then revived w/odin and an old kernal, I don't think it was totally clean.
Click to expand...
Click to collapse
Yup! I just told you in my post edit, left that out by accident.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yup! I just told you in my post edit, left that out by accident.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks again! Great answers, and just the info I need!
So, to format it in CWM. I would go to
Mounts and Storage
format /data
or
format /data and /data/media (/sdcard)
i assume I don't touch
format /cache or format /system
and.. last thing I promise, how do I make sure I keep a copy of gaaps and a rom on the sdcard, if I format it?
n0xide said:
Thanks again! Great answers, and just the info I need!
So, to format it in CWM. I would go to
Mounts and Storage
format /data
or
format /data and /data/media (/sdcard)
i assume I don't touch
format /cache or format /system
and.. last thing I promise, how do I make sure I keep a copy of gaaps and a rom on the sdcard, if I format it?
Click to expand...
Click to collapse
You can't keep anything on the SD card after formatting, it'll be completely wiped clean, but you should do the second option. Also you should always format system when you clean flash a rom anyway.
I'd use an external SD card to flash the rom from. Alternatively, you could sideload the rom (if you know how). I don't know how.
Sent from my SCH-I535 using Tapatalk 2
So I'm pretty sure I have my Wingray Xoom updated and using the new partitions because I have the new CM installed and running. But my issue is when I went to do the BigPart procedure the data partition wouldn't mount after switching over to F2FS so I have it in ext4. How do I get it over to F2FS because without it the tablet seems to run slow and choppy.
Beeko said:
So I'm pretty sure I have my Wingray Xoom updated and using the new partitions because I have the new CM installed and running. But my issue is when I went to do the BigPart procedure the data partition wouldn't mount after switching over to F2FS so I have it in ext4. How do I get it over to F2FS because without it the tablet seems to run slow and choppy.
Click to expand...
Click to collapse
I'm am nowhere near an expert, but my understanding is that, while the BigPart TWRP is F2FS compatible, there are not yet any Xoom ROMS (or kernels???) that are F2FS compatible. Therefore there is no way to get F2FS to work on the Xoom at this time.
Beeko said:
So I'm pretty sure I have my Wingray Xoom updated and using the new partitions because I have the new CM installed and running. But my issue is when I went to do the BigPart procedure the data partition wouldn't mount after switching over to F2FS so I have it in ext4. How do I get it over to F2FS because without it the tablet seems to run slow and choppy.
Click to expand...
Click to collapse
slow1234 said:
I'm am nowhere near an expert, but my understanding is that, while the BigPart TWRP is F2FS compatible, there are not yet any Xoom ROMS (or kernels???) that are F2FS compatible. Therefore there is no way to get F2FS to work on the Xoom at this time.
Click to expand...
Click to collapse
F2FS needs support in the kernel. F2FS is currently only supported in 3.0+ linux kernels. As I'm sure you are both aware we have a 2.6 kernel which is now prehistoric!
BRD looked into it and from what I gather said it couldn't be done without extensive work, schischu was looking into it last month I believe and deciding whether to take on the task.
We haven't heard anything since.
I would assume we will not get F2FS but we can always hope
Well even if there aren't any ROMs or kernels that support F2FS why is it that I can't mount data partition after re-partitioning it. Shouldn't I be able to format it and mount it anyway?
Beeko said:
Well even if there aren't any ROMs or kernels that support F2FS why is it that I can't mount data partition after re-partitioning it. Shouldn't I be able to format it and mount it anyway?
Click to expand...
Click to collapse
That's probably an indication that the repartition went wrong. Hop over to the bigPart thread and ask for assistance there. You may want to start over.
Hi guys can you say to me how I can run f2fs file system on s6? and is worth comparing vs ext4 on s6?tnks :highfive:
marceloz5 said:
Hi guys can you say to me how I can run f2fs file system on s6? and is worth comparing vs ext4 on s6?tnks :highfive:
Click to expand...
Click to collapse
Firstly you need to have a kernel installed which supports f2fs, I think only arters kernel supports it right now. The process involves converting the different partitions from ext4 to f2fs within twrp, so like data and system, if you look at benchmarks f2fs is better than ext4 but I've never done it personally so cannot give too much info, but the above is a quick rundown in what's involved
sofir786 said:
Firstly you need to have a kernel installed which supports f2fs, I think only arters kernel supports it right now. The process involves converting the different partitions from ext4 to f2fs within twrp, so like data and system, if you look at benchmarks f2fs is better than ext4 but I've never done it personally so cannot give too much info, but the above is a quick rundown in what's involved
Click to expand...
Click to collapse
but its stable or secure/safe do it?
marceloz5 said:
but its stable or secure/safe do it?
Click to expand...
Click to collapse
It is safe to do, but as with all mods there maybe instances where you might get hiccups. Just be aware that you are formatting the partitions so you will lose data, so make sure you do a full back up