According to the Paranoid Android dev, "f2fs users should switch back to ext4 as f2fs has GC issues which can result in performance issues over time."
Anyone experiencing it and how to switch to ext4?
I tried formatting data, system, cache back to ext4 from f2fs, while installing a CM based ROM. But i got the internal storage formatted.
I used TWRP.
Sent from my OnePlus 3T using Tapatalk
I'm a oneplus 3t user. My file system ext4. My android/obb folder is not showing.
I'm on paranoid android. 7.2.1. Idk why its happening only with pa.
Waiting for a response.
---------- Post added at 03:54 AM ---------- Previous post was at 03:50 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AKA_India said:
I tried formatting data, system, cache back to ext4 from f2fs, while installing a CM based ROM. But i got the internal storage formatted.
I used TWRP.
Sent from my OnePlus 3T using Tapatalk
Click to expand...
Click to collapse
/data = data partition + internal storage memory
if you change file system on it, it will obviously wipe everything.
and you can't use f2fs on /system, it will change back to ext4 once you flash. you can use however f2fs on /cache.
regards.
Abdullll said:
I'm on paranoid android. 7.2.1. Idk why its happening only with pa.
Waiting for a response.
---------- Post added at 03:54 AM ---------- Previous post was at 03:50 AM ----------
Click to expand...
Click to collapse
I too noticed OBB folder missing. But I'm on PAEX, not PA. Switched from f2fs to ext4
is it safe change from f2fs to ext4 and restore a nandroid backup?
Rated R said:
is it safe change from f2fs to ext4 and restore a nandroid backup?
Click to expand...
Click to collapse
Yes this works, but make sure to copy the nandroid backup to your pc before doing the change to ext4.
Or else it will get deleted!
If i make a backup while it is f2fs and then change it to ext4, if i restore the backup will it change it back to f2fs or keep ext4?
kinghaloman said:
If i make a backup while it is f2fs and then change it to ext4, if i restore the backup will it change it back to f2fs or keep ext4?
Click to expand...
Click to collapse
It will keep ext4 and you'll just get a note that the backup was created on a f2fs and you have ext4 at the moment.
przemcio510 said:
It will keep ext4 and you'll just get a note that the backup was created on a f2fs and you have ext4 at the moment.
Click to expand...
Click to collapse
Okay and will that affect anything or should it be changed back? And how do I know which partitions where using which format? (sorry for all the questions)
kinghaloman said:
Okay and will that affect anything or should it be changed back?
Click to expand...
Click to collapse
No, it will boot fine w/o any problems.
kinghaloman said:
And how do I know which partitions where using which format?
Click to expand...
Click to collapse
There are few methods to do it:
1. by entering TWRP > Wipe > Advanced > check partition > change file system
2. by booting the system and using DiskInfo app
3. by executing ADB command
and so on.
kinghaloman said:
sorry for all the questions
Click to expand...
Click to collapse
There is nothing wrong about asking questions, better to ask the way than go astray
przemcio510 said:
No, it will boot fine w/o any problems.
There are few methods to do it:
1. by entering TWRP > Wipe > Advanced > check partition > change file system
2. by booting the system and using DiskInfo app
3. by executing ADB command
and so on.
There is nothing wrong about asking questions, better to ask the way than go astray
Click to expand...
Click to collapse
indeed, and thank you for all the help!!!!:laugh:
Related
Just installed cyanogens rom and started adding apps from an 'appmanager' folder on the SD card- but I cannot see them in a seperate folder on the SD - is it just running them in the 'appmanager' folder? Or is apps2sd not working and installing stuff on my internal memory?
( I have 3 partitions by the way, one ext2 /3 not sure which, the last one a 'swap' from early 'hero' install)
Thanks
you need an ext2/ext3 partition for apps2sd to work. if you have such a partition then cyanogen rom is installing apps there automatically.
open an adb shell and cd to /system/sd
if there are some folders, the apps2sd is running (the ext partition is mounted under /system/sd)
You can also run this in terminal but there you need to run the "su" command first
Sorry, noob!
Ok I opened 'terminal emulator', did 'su' allowed root and then
cd /system/sd
'ls' to see directory right? just shows 'placeholder' so somethings wrong?
Is there an easy fix and can I move all the apps I just installed over?
Thanks!
looks like no apps2sd(the partition might be there, but no apps were moved at this time)
just create an ext3 partition on your sd card and install your favourite rom. cyanogen will move all apps automatic (long long first boot).
on other roms you might have to run the apps2d.sh script to move the apps. just read the corresponding thread for your rom. you will find all information there.
FireFart - you mean cyanogen? That's the one I installed, before adding these apps!
If I flash it again won't it wipe all installed apps?
Is it worth trying to run this apps2d.sh script?
try this guide:
http://forum.xda-developers.com/showthread.php?t=535232
When you just flash another update.zip, your apps wont get deleted(with and without apps2sd).
When nothing works, wipe, delete the ext partition and make a fresh install
To delete the content on the ext partition:
rm -rf /system/sd/*
I would agree with the thread you linked, however the apps2sd section is not necessary. as already stated, cyanogen's rom does this automatically (most do now), and installing apps2sd will (i believe) implement an outdated/slower method of 'symlinks'.
in short: use the thread for a guide, but ignore the app2sd section. its a good guide for the partitioning of your sd card (this part IS necessary)
FireFart said:
try this guide:
http://forum.xda-developers.com/showthread.php?t=535232
When you just flash another update.zip, your apps wont get deleted(with and without apps2sd).
When nothing works, wipe, delete the ext partition and make a fresh install
To delete the content on the ext partition:
rm -rf /system/sd/*
Click to expand...
Click to collapse
Ok , tried reflashing, no effect it seems. ... from what I've seen the thread on partitioning was pretty much the same as the one I used.
FireFart said:
try this guide:
http://forum.xda-developers.com/showthread.php?t=535232
When nothing works, wipe, delete the ext partition and make a fresh install
To delete the content on the ext partition:
rm -rf /system/sd/*
Click to expand...
Click to collapse
you mean wipe it's contents right?
he means do a wipe on the recovery screen (ALT+W) AS WELL AS remove contents from ext partition.
the recovery console wont touch the ext partition when performing an ALT+W.
im not sure thats the issue though. just to verify, the order of your partitions on the SD is: FAT32/ext, correct? the FAT32 partition must be the first partition, and the ext the second.
EDIT: can u post the results of running a 'mount' cmd? you should have a line that reads something like:
Code:
/dev/block/mmcblk0p2 on /system/sd/ type ext3 (rw,noatime,nodiratime,barrier=1,data=ordered)
jomtones said:
Ok , tried reflashing, no effect it seems. ... from what I've seen the thread on partitioning was pretty much the same as the one I used.
you mean wipe it's contents right?
Click to expand...
Click to collapse
phantasm -sorry, noob, not sure what you mean!
partitions currently look like this (as JAC instructions)
http://i70.photobucket.com/albums/i120/jomtones/IMAGE_829.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe having 3 parts is throwing it? confused!
WARNING!!! THIS WILL WIPE EVERYTHING
Found this over at the evo forum by evokings so i took it and made it work for us.
This will most likely prevent problems with installing ROMS. Please Wipe before reporting bugs caused by the User(This means us!)
It will wipe:
Boot
Data (Dalvik-cache is included in Data)
System
Cache
You choose what you want to wipe......
This is great for flashing ROMS. If you are using a custom recovery and it has an "update.zip" option, for quicker access just rename the zip to "update.zip"
Downloads:
WIPE--ALL.zip--> Wipes Boot, System, Cache, & Data
WIPE--System_Data_Cache.zip--> Wipes System, Data, Cache
WIPE--Cache_Dalvik-cache.zip--> Wipes Cache & Dalvik-cache
Thank evokings from evo
So, to be clear, is this is the equivalent of:
Wipe Cache Partition
Factory/Data Reset
Wipe /system
Full dalvik wipe
????
No sd wipe, I assume?
WARNING!!! THIS WILL WIPE EVERYTHING
Found this over at the evo forum by evokings so i took it and made it work for us.
It will wipe:
Boot
Data
System
Cache
Click to expand...
Click to collapse
I dont think it wipes dalvik
Sure it does.
Dalvik is either under /cache or /data.
Hence, "Wipes All"
nickmv said:
So, to be clear, is this is the equivalent of:
Wipe Cache Partition
Factory/Data Reset
Wipe /system
Full dalvik wipe
????
No sd wipe, I assume?
Click to expand...
Click to collapse
Yes. Dalvik is either under the cache partition or the data partition
No sdcard wipe
convenient! Thanks
OP updated with new zip for Wiping ONLY Cache & Dalvik-cache
Is this a hack or mod?
Sent from my Galaxy Nexus using XDA App
I believe a script. Moderators classify it has [HACK]
Laziness ftw!!! I will personally be using the Cache + Dalvik Cache wipe the most. Thanks
I did a wipe before initially using this script, then applied the wipe all* everything seems great.
Sent from my Google Nexus S using XDA App
dalvik is /data/dalvik-cache or /cache/dalvik-cache so wiping both data and cache is the same
also the all does format system and format boot which you can find only under mounts and storage in clockwork recovery
can I ask how this is different from a full wipe in CWM?
dmo580 said:
can I ask how this is different from a full wipe in CWM?
Click to expand...
Click to collapse
I used this before and I think it does a 3x wipe of each so you don't have too.
Sent from my SPH-D710 using xda premium
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NORCALkID said:
I used this before and I think it does a 3x wipe of each so you don't have too.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
but I thought CWM does wipe everything when you do a full wipe there?
A full wipe wipes /data and /cache and dalvik is under /data i thought.... shrug.
Yes your rite. What is so confusing?
frenccw said:
Laziness ftw!!! I will personally be using the Cache + Dalvik Cache wipe the most. Thanks
Click to expand...
Click to collapse
My lazy ass is going to use this right now.
Sent from the bowels of hell
what is the meaning of "wiping the system"? iknow about wiping data,dalvic and boot. i dont know what is "wiping system" all about? does this wipe your sdcard? confussing..>_<
mixtapes08 said:
what is the meaning of "wiping the system"? iknow about wiping data,dalvic and boot. i dont know what is "wiping system" all about? does this wipe your sdcard? confussing..>_<
Click to expand...
Click to collapse
The SD-card itself will not be touched. Anyway don´t forget a nandroid backup before flashing.
Wiping "system" means wiping the entire operating system. Look here for some explanation: http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
ADVANED USERS ONLY!
ONLY TRY THIS WHEN YOU KNOW HOW NVFLASH WORK AND HOW YOU CAN RESTORE YOUR PARTITIONS USING IT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you use cm7 or MIUI you may feel like your internal sdcard is a bit waste of memory
people have been trying to merge the internal sd partition and the data partition sadly without succes
but i tried to mount the internal sd as /data and i did succeed
i recommend you to change the size of your all your partitions using nvflash this is not necessary but you will have have more benefits
here is a link to the TUT on modaco
i used this values:
/system (512 MB): size=536870912
/cache (512 MB): size=536870912
/data (256 MB): size=268435456
Recovery (50 MB): size=52428800
resized system to 512 MB is enough
resized cache to 512 MB to store the dalvik-cache on the cache partition it is more use full then store it on the /data partition
resized data to 256 MB because we don't need it anymore
the remaining space will be used the internal SD well lets say it is a lot in my case it is as you can see on the screen shots above 5.43 GB
WARNING! YOUR SDCARD MUST BE MOUNTED ON /mnt/sdcard AND NOT ON /mnt/emmc OR /mnt/sdcard/_InternalSD OTHERWISE AFTER FLASHING YOU CAN'T ACCES YOUR SDCARD
IN CM7 THE DEFAULT SETTINGS ARE GOOD UNLESS OF COURSE YOU CHANGED THEM TO MOUNT INTERNAL SD CARD ON SDCARD
AND BY DEFAULT ON MIUI THE SETTINGS ARE WRONG THERE IS THE SDCARD MOUNTEDN ON /_ExternalSD
converting the internal sdcard to ext4 is not hard
you can just flash THIS zip for it
when your internal sdcard is formatted as ext4 you can use THIS zip to transfer your data to your internal SD partition
this zip contain 2 script
one will transfer your data over to the internal sd partition
and the other will transfer your dalvik-cache over to the cache partition (when there is enough space to do so if it is not resized it will just leave it on /data)
after this when you boot up the device you will notice you get an notification what will say it is safe to remove the sdcard
this is because it can't mount the internal SD and this will cause a bug you won't be able to mount your external sdcard on the computer
but hey we gonna fix that!
i recommend you to use root explorer for this job
locate /system/build.prop and delete these lines out of the file
for CM7 delete these
Code:
# Mount the internal SD card, too
ro.additionalmounts=/mnt/emmc
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
for MIUI delete there
Code:
# Mount the internal SD card, too
ro.additionalmounts=/mnt/sdcard/whatever-the-text-is-here
now reboot your device and enjoy your huge space
Good Luck!
Owain
Huge thanks to benee for his universal ext4 converter that i used to convert the internal sd partition
i am in no way responsabel for whatever might happen
to your cellphone if you did something wrong don't come
and blame me for it it is your device you did it
I'd appreciate it if you made it a little less complicated for not-so-advanced users like me. :/
Works great! Thanks.
works like a charm...took your suggestion and resize the partition...exact results
dan079 said:
works like a charm...took your suggestion and resize the partition...exact results
Click to expand...
Click to collapse
good to know it is also working for others
I have been using the OxygeN1mod Rom and was working perfectly on the Blackrose 210 / 8 / 218 partition system and had never faced any problems.
I made a NANDROID backup of ALL partitions and installed the MIUI ICS rom and as it was not so smoth for me, i RESTORED ALL partitions of my NANDROID.
After the RESTORE, i cant happen to install the APPS. its giving the Insufficient Memory warning.
Here is the Free Space screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Except the CACHE memory everything looks fine. And If the Problem is somhow related to CACHE memory, howcome i never had issues with BEFORE the NANDROID backup/Restore
I Wiped the CACHE partition and tried but same error
Also the Sense ROM worked well on this partition
please help me
if i repartition the Blackrose i am afraid if my NANDROID backup will work or not
Main problem is that i removed the Titanium Backup app and am not able to intall it
can you sideload titanium?
i suppose aslong as your current /system partition is big enuf than the restore /system partition. you shd be fine. nt sure. may be some1 will help you out.
Sent from my Nexus One using Tapatalk
n1newbie said:
can you sideload titanium?
Click to expand...
Click to collapse
I downloaded the APP and Installed using the File Manager : LOW MEMORY WARNING
i tried th MARKET : LOW MEMORY Warning
So any other way ?
If i atleast have the Titanium Backup i can reformat all partitions and restore.
I was such an idiot not to make a backup (was thinking NANDROID is enough)
hv u tried formatting all partitions(except sd) x3 in recovery. after that restore the nandroid and hopefully ur problems should be gone.
Sent from my Nexus One using Tapatalk
n1newbie said:
hv u tried all formatting partitions(except sd) x3. after that restore the nandroid and hopefully ur problems should be gone.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
i did ONCE. will try that. hope it helps
firoz3321 said:
i did ONCE. will try that. hope it helps
Click to expand...
Click to collapse
It is related to the cache memory. In recovery, wipe the cache and run a fix permissions, and then try again. Also had problems with that a while ago.
Just now wiped 5 times
Now in the process of recovering. hope it helps.
If not will try your method @Race55
thank you
EDIT: 5 wipes didnt work either hope 3 wipes is not a magic number
EDIT 2 : Wiped CACHE (3 times) , FIX PERMISSIONS, Still same error
I want to know , If i repartition with Blackrose, will my NANDROID Backup be able to RESTORE ? will it be a problem with partition size being changed
EDIT: changed the partition to : 210/20/206
Still am not able to install apps from android market and not even from filemanager.
i want a last confirmation before i install a fresh installation is ther no way out ?
no one??
Sent from my Nexus One
I have noticed that i am able to download other apps, but Titanium Backup is giving error that is the app i need the most to install my ROM again
Also my mobile is showing ODD MEMORY info :
Is there a ZIP file for titanium backup please , so i can install from recovery
I finally got the TITANIUM BACKUP INSTALLED !!
After realzing that ONLY the Titanium backup is not getting installed, I searched for "titanium" in ROOT EXPLORER and deleted all files except those on the SD-CARD.
Then installed the APK and its DONE
Thank you All
Using the SD card for Data partition
I was very happy to find that great work has been done to bring CM11 to the Galaxy Ace s5830i.
Thanks to all those involved!
After installing it I found that although CM11 is awesome the Galaxy Ace is crippled by the lack of internal storage.
To fix this I created a boot.img that is a repackage of the boot image that ships CM11.0.0 RC12.
This boot image tries to mount the second partition of the SD card on mount point /Data
Hopefully this work may be useful to others.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: I do not have the credit to post this on the dev board.
Instructions:
1. Backup the phone (all data etc).
2. Configure a SD card with two partitions (see below) and insert it into the phone.
3. Use CWM to get CM11 installed and running (CM11 RC 12 or later) see the XDA forums.
4. Using CWM flash the modified boot image (cm-11-RC12-cooperve-boot_img-sd_data_ext2.zip).
The SD card must be configured to contain two formatted partitions:
1. Partition one should be a FAT32 partition.
2. Partition two must consist of a EXT2 formatted partition.
The first partition will be used in the traditional way and the second partition will be used as the data partition. I use a 32GB sd-card with the first partition (fat32) sized to 24GB and the second (ext2) sized to 8GB.
NOTE:
1. Use at own risk, this may damage your phone and eat your data!
2. If you have data on the original /Data folder you will need to take steps to copy it to the new folder if you want to keep it.
2. The SD card must never be removed while the phone is on.
3. The SD card must always be in the phone when it is on.
4. The recovery CWM will not backup the new Data partition on the SD card, it will backup the original Data partition.
5. If you update the boot image i.e. flashing a new version of CM11 sd-card Data partition will not be used. Reinstalling the modified boot image should fix this (untested).
6. I am not the first to discover this method of using the sd-card to store data.
Attachments:
Modified boot image CWM flashable: cm-11-RC12-cooperve-boot_img-sd_data_ext2.zip
Diffs of changes to the original CM11 RC12 ramdisk.
This solution could be implemented in cm11 in that defy solution was implemented in direct rom cm11. I wonder if someone used this solution in cm11.
Enviado de meu MI 2SC usando Tapatalk
Thanks it worked
I used ext3
Sent from my Nexus 7 using XDA Free mobile app