I just rooted my archos 70h with the urukdroid's easy installer.
Seems like everything went fine, except that my data partition appears to be fat32 and not ext4 like I expected.
Code:
fdisk -l
Disk /dev/sdd: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 2988090 488392064 242701987+ c W95 FAT32 (LBA)
/dev/sdd2 63 1012094 506016 83 Linux
/dev/sdd3 1012095 2988089 987997+ 83 Linux
The storage settings in the archos tell me that the partition is ext3, but it is definately fat32 since I wasn't able to copy a 4gb+ file to the archos.
Did I do something wrong?
Or did I maby misunderstand? Was the ext4 only supposed to be for the apps partition?
Sorry for not posting this in the urukdroids thread, but I cannot post there because I haven't made enough posts.
You missunderstood it wrong..
See : Storage have to be fat32 otherwise you wouldnt be able to mount it on windows
The system partition of urukdroid is ext4 formatted you can mount the system partition on linux
If the storage partition would be ext4 it wont be so much performance boost.
Greets
Lenn
Is it possible to mount the ext4 partition in Linux running in virtual machine (VMware) running on Windows?
Instead of asking, why don't you try it?
Lenn said:
You missunderstood it wrong..
See : Storage have to be fat32 otherwise you wouldnt be able to mount it on windows
The system partition of urukdroid is ext4 formatted you can mount the system partition on linux
If the storage partition would be ext4 it wont be so much performance boost.
Greets
Lenn
Click to expand...
Click to collapse
Well I have been a linux user since 2004 so I have no need for the long-outdated fat32 filesystem.
My storage partition was ext3 formatted with the stock archos/android firmware, but now when I select ext3 from the menu the device just reboots and nothing happens to the partition.
Is there any way of getting ext4 or even ext3 for the storage partition? Would it be safe to format it just like any other partition or is there something special that needs to be done?
lordofazeroth said:
Is it possible to mount the ext4 partition in Linux running in virtual machine (VMware) running on Windows?
Click to expand...
Click to collapse
I am not familiar with proprietary virtual machines like vmware but as long as the virtual machine can talk directly to the hardware it can mount the drive without needing windows drivers.
For software emulated virtual machines you would need a windows driver to be able to mount the drive.
Of course you can format the data partition with ext3/4 yourself, just keep in mind
that the android ext4 implementation doesn't allow hugefile.
And fat32 will "never" be outdated as it is very easy to implement for device vendors, so it will allways be there for cameras and stuff.
fzelle said:
Of course you can format the data partition with ext3/4 yourself, just keep in mind
that the android ext4 implementation doesn't allow hugefile.
And fat32 will "never" be outdated as it is very easy to implement for device vendors, so it will allways be there for cameras and stuff.
Click to expand...
Click to collapse
I'll try and format it to ext4 then... Hope it doesn't get screwed up.
Yes you are right, fat32 will be continued to use, but as for features it's long outdated compared to superior filesystems like ext, xfs, etc.
gardar said:
I'll try and format it to ext4 then... Hope it doesn't get screwed up.
Yes you are right, fat32 will be continued to use, but as for features it's long outdated compared to superior filesystems like ext, xfs, etc.
Click to expand...
Click to collapse
You should format it with angstrom (SDE on Archos)
just a tip
Lenn said:
You should format it with angstrom (SDE on Archos)
just a tip
Click to expand...
Click to collapse
Might be worth a shot
I'm going to take a clonezilla image of the current setup, just in case the archos doesn't like me formatting the partition
Seems like android does not like the storage partition to be ext4
Damaged internal storage
Internal storage damaged. You may have to reformat it.
Click to expand...
Click to collapse
I tried both with urukdroid and stock archos firmware.
But I was able to format back to ext3, so that will have to do for now
gardar said:
Seems like android does not like the storage partition to be ext4
Click to expand...
Click to collapse
That was i thought, because of the mounting on windows
Lenn said:
That was i thought, because of the mounting on windows
Click to expand...
Click to collapse
Well ext3 works fine so your theory is invalid
Sent from my Archos 70 using Tapatalk
Related
I accidentally made an extra partition on my sd that i want to remove
im not looking to spend money on partition software
can anyone help me out
TIA
gparted should work and is free.
had no luck with that one......
Ra recovery can partion
The sd card for you if you're root
-------------------------------------
Sent via the XDA Tapatalk App
format the card in your phone from settings
format the card in your phone from settings
Click to expand...
Click to collapse
This fill only format the fat partition not any others. I thought the same when I partitioned my card with ext2, then formatted and my ext2 wad still there while the fat was clean.
-------------------------------------
Sent via the XDA Tapatalk App
t2noob said:
This fill only format the fat partition not any others. I thought the same when I partitioned my card with ext2, then formatted and my ext2 wad still there while the fat was clean.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
thanks everyone i had success with this tutorial
maybe we can sticky this for anyone who needs it here you go
http://forum.xda-developers.com/showthread.php?t=534714
How about just booting into Amon_RA's recovery boot (v 1.6.2) and using "sdparted" ???
Note I said sdparted, not "parted".
Obviously, if you want to save junk from either the FAT or ext[2,3,4] partition on your card beforehand, you need to take steps to do so. (Hint: adb is running when Amon_RA recovery boots, and "adb pull" works recursively, if you want - but you will need enough Linux smarts to mount partitions on the SD card yourself).
Code:
$ adb shell
/ #
/ # sdparted --extsize 0M --swapsize 0
checking script requirements...done
unmounting all partitions...done
to continue, all existing partitions must be removed.
this action will remove all data from your sdcard.
do you want to continue? (Y/n) Y
removing all partitions...done
total size of sdcard=7948MB
the following actions will be performed:
-create 7948MB fat32 partition
do you want to continue? (Y/n) Y
performing selected actions...
creating fat32 partition...done
retrieving current sdcard information...
Model: SD SU08G (sd/mmc)
Disk /dev/block/mmcblk0: 7948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 7948MB 7948MB primary fat32 lba
script log is located @ /data/sdparted.log
bftb0
bftb0 said:
How about just booting into Amon_RA's recovery boot (v 1.6.2) and using "sdparted" ???
Note I said sdparted, not "parted".
Obviously, if you want to save junk from either the FAT or ext[2,3,4] partition on your card beforehand, you need to take steps to do so. (Hint: adb is running when Amon_RA recovery boots, and "adb pull" works recursively, if you want - but you will need enough Linux smarts to mount partitions on the SD card yourself).
Code:
$ adb shell
/ #
/ # sdparted --extsize 0M --swapsize 0
checking script requirements...done
unmounting all partitions...done
to continue, all existing partitions must be removed.
this action will remove all data from your sdcard.
do you want to continue? (Y/n) Y
removing all partitions...done
total size of sdcard=7948MB
the following actions will be performed:
-create 7948MB fat32 partition
do you want to continue? (Y/n) Y
performing selected actions...
creating fat32 partition...done
retrieving current sdcard information...
Model: SD SU08G (sd/mmc)
Disk /dev/block/mmcblk0: 7948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 7948MB 7948MB primary fat32 lba
script log is located @ /data/sdparted.log
bftb0
Click to expand...
Click to collapse
thanks friend but i got thigs all situated thanks to that tutorial i posted right above you i did everything like you said though....i think we should add the info to the stickies
DS36 said:
thanks friend but i got thigs all situated thanks to that tutorial i posted right above you i did everything like you said though....i think we should add the info to the stickies
Click to expand...
Click to collapse
My bad for not reading every post and all links. That one is much more comprehensive, including descriptions of possible errors.
LOL, that thread is written by the maintainer of the script used on Amon_RA's recovery. No wonder it's detailed!
One thing he didn't cover is that the script has a help menu, too; if you give
/ # sdparted --help
a shot, it's plain to see that that script should be easy enough for a noob to use...
..especially since it does protective checks and also does the post-partitioning FS formatting.
bftb0
Specifically, what do I need to install on my gtab so that it can read an sdcard formatted to ext2?
I've already installed Clockworkmod and Vegan-Tab Ginger. Maybe I need a different kernel too? I know very little about kernels - Are they device specific? Are they interchangeable? Can I change the kernel without wiping my files?
Has anyone ever had success with ext2 on the gtab?
deadfraggle said:
Specifically, what do I need to install on my gtab so that it can read an sdcard formatted to ext2?
Click to expand...
Click to collapse
Nothing.
I know very little about kernels - Are they device specific?
Click to expand...
Click to collapse
They have to be--that's their function after all.
Are they interchangeable?
Click to expand...
Click to collapse
They should be. For the gTablet, you can use either the Clemsyn or Pershoot kernels. Both have native extn support.
Can I change the kernel without wiping my files?
Click to expand...
Click to collapse
Yes.
Has anyone ever had success with ext2 on the gtab?
Click to expand...
Click to collapse
ext2/3/4 are all natively supported by the linux kernel, and issuing a mount command will work if you do it on the command line. However, the automounter program, called vold, likes to have ext4 or VFAT (aka FAT32) filesystems on the SD card. If your ext2 formatted SD card is not automatically mounted, format it again as ext4.
Formatted the sdcard to ext4, but still cannot read anything off it.
As for mounting through the terminal, if I use
fdisk -l
it shows nothing, not even an error. Is there another way to list disks so I know what to mount?
What I'm trying to do is use the Debian installer for Android, but the only version I could find is 2 years old. It's probably based on Lenny or earlier which does not have native ext4 support.
deadfraggle said:
Formatted the sdcard to ext4, but still cannot read anything off it.
Click to expand...
Click to collapse
What ROM are you on? Are you running Android or something else?
As for mounting through the terminal, if I use
fdisk -l
it shows nothing, not even an error. Is there another way to list disks so I know what to mount?
Click to expand...
Click to collapse
Code:
$ su
# /system/xbin/fdisk -l /dev/block/mmcblk3
Disk /dev/block/mmcblk3: 16.0 GB, 16097738752 bytes
255 heads, 63 sectors/track, 1957 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk3p1 1 1709 13720703 c Win95 FAT32 (LBA)
/dev/block/mmcblk3p2 1709 1958 1999744+ 83 Linux
Use /dev/block/mmcblk2 for the external SD card. Mount it as:
Code:
$ su
# mount /dev/block/mmcblk2p1 /some/path
or
Code:
$ su
# mount -t ext4 /dev/block/mmcblk2p2 /some/path
rajeevvp said:
What ROM are you on? Are you running Android or something else?
Click to expand...
Click to collapse
Vegan-Tab Ginger edition
rajeevvp said:
Code:
$ su
# /system/xbin/fdisk -l /dev/block/mmcblk3
Click to expand...
Click to collapse
This gives me similar results to yours.
rajeevvp said:
Use /dev/block/mmcblk2 for the external SD card. Mount it as:
Code:
$ su
# mount /dev/block/mmcblk2p1 /some/path
Click to expand...
Click to collapse
My result:
Code:
$ su
# mount /dev/block/mmcblk2p1 /micro
mount: mounting /dev/block/mmcblk2p1 on /micro failed: No Such file or directory
Also tried
mount /dev/block/mmcblk2p2 /micro
with the same result.
rajeevvp said:
or
Code:
$ su
# mount -t ext4 /dev/block/mmcblk2p2 /some/path
Click to expand...
Click to collapse
My result:
Code:
$ su
# mount -t ext4 /dev/block/mmcblk2p2 /micro
mount: mounting /dev/block/mmcblk2p2 on /micro failed: No Such file or directory
Edit:
If I insert a ext2 formatted sdcard, I get a notice that it is being scanned for errors. It goes away after a minute or so.
If I go to /sdcard2 in Root Explorer, the folder is empty but the stats show a correct 2 gb of used space and the correct amount of free space.
(Also in Root Explorer, if I try to create a test file, it says 'successful' but no file is created.)
If someone here owns a gtab and can access a ext2/4 sdcard, please let me know what setup/Rom you are using. Or if you own an extra sdcard you can format to ext2, and use some other aftermarket ROM/different kernel on your gtab, please test and post your results.
The commands I gave were just examples, you'll have to adjust them to suit your system.
deadfraggle said:
If I insert a ext2 formatted sdcard, I get a notice that it is being scanned for errors. It goes away after a minute or so.
Click to expand...
Click to collapse
That looks like the correct behaviour. The external SD card is being fsck'd and then automounted.
If I go to /sdcard2 in Root Explorer, the folder is empty but the stats show a correct 2 gb of used space and the correct amount of free space.
Click to expand...
Click to collapse
This, again, is correct, except that on a newly created filesystem, Root Explorer should've shown a lost+found directory.
(Also in Root Explorer, if I try to create a test file, it says 'successful' but no file is created.)
Click to expand...
Click to collapse
Reformat the filesystem again and try creating a file using the command line:
Code:
$ su
# echo test > /mnt/sdcard2/test.txt
# cat /mnt/sdcard2/test.txt
test
#
My external SD card is formatted as ext3 and I have no problem using Root Explorer. With other file managers, you'll have to be careful because of the standard Unix permissions that come into effect on all extn filesystems. If you want to use file managers other than Root Explorer, just create a new directory on your ext2 filesystem and give that directory a user of "system" and a group of "sdcard_rw", and give (at least) the group "rwx" permissions. Use the user, group and permissions of the /mnt/sdcard directory as a guide:
Code:
$ ls -ld /mnt/sdcard
d---rwxr-x 22 system sdcard_rw 8192 Jan 1 1970 /mnt/sdcard
$ su
# mkdir /mnt/sdcard2/user-dir
# chmod 0775 /mnt/sdcard2/user-dir [I]#or 0075 to exactly match /mnt/sdcard[/I]
# chown system.sdcard_rw /mnt/sdcard2/user-dir
If you don't want to bother with all this, just format the SD card as VFAT, and Android will automatically mount the VFAT filesystem with an owner of "system" and a group of "sdcard_rw". And since (all?) file managers belong to the "sdcard_rw" group, they get automatic read-write permissions to that filesystem. BTW, the Terminal Emulator app also belongs to the "sdcard_rw" group, so you can freely write onto VFAT formatted SD cards on the command line without resorting to the 'su' command (the example above).
Granted, it's been a while since I researched this - but I learned many months ago that the version of VOLD in Froyo does not support anything else but vFAT - so it just won't mount EXT2, or NTFS for that matter.
the mount command would bypass VOLD and we know that NTFS should work, if it's a custom kernel. Conceivably EXT2 should also work, but since it was all manual scripting I just stopped researching it - mainly because I'd still have issues using the card with other devices so it wouldn't really be a portable solution anymore.
As much as I detest FAT32 for its file size limitations, it's still the "standard" between portable devices. The various vendors have yet to figure out a replacement, since they can't seem to agree on anything.
rajeevvp said:
My external SD card is formatted as ext3 and I have no problem using Root Explorer.
Click to expand...
Click to collapse
Figures. Never tried ext3, mainly because it's not a readily available option in Ubuntu. Tried to format to ext3 via the terminal but got a weird error, even after unmounting the drive:
"/dev/sdb is apparently in use by the system; will not make a filesystem here!"
So I booted in to Parted Magic with my netbook, wiped the sdcard, and created a new ext3 partition.
Success!!
The sdcard auto-mounts, and is accessible by Root Explorer, ES File Explorer and File Manager.
Ext3 will suit my purposes just fine. Sorry to make you write all the rest of your post, but it will be a handy reference.
Thank you a million times over!
@ roebeet
I'm humbled this post got your attention. Thanks for the great work!
deadfraggle said:
Figures. Never tried ext3, mainly because it's not a readily available option in Ubuntu.
Click to expand...
Click to collapse
The ext3 format was the default filesystem of Ubuntu, until just recently. It is generally considered better to use ext2 on a SD card. Since a SD card has a limited number of read/writes, a journaling filesystem like ext3/ext4 would use up the limited number of read/writes faster than using ext2. Also, never create a swap partition on a flash drive or SD card.
To format a SD card in Ubuntu, first determine the device name:
Code:
[email protected]:~$ sudo fdisk -l
[sudo] password for paul:
Disk /dev/sda: 64.6 GB, 64609058816 bytes
255 heads, 63 sectors/track, 7854 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000d996
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3890 31246393+ 83 Linux
/dev/sda2 3891 7854 31840830 83 Linux
Disk /dev/sdb: 16.4 GB, 16437477376 bytes
255 heads, 63 sectors/track, 1998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b3366
Device Boot Start End Blocks Id System
/dev/sdb1 1 1998 16048903+ 83 Linux
My EEEPC has a 64 GB hard drive, and a 16 GB SDHC card. So the card I want to format is /dev/sdb1. Use fdisk again for the formatting, here are the steps copied directly from my terminal:
Run commands with root privileges (sudo).
Find the disk:
# sudo fdisk -l
Format the disk (sdb1):
# sudo fdisk /dev/sdb1
Command (m for help):d (delete any existing partitions)
Command (m for help):n (create a new partition)
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4):1
Command (m for help):w (to write the changes to the disk)
Format the card. You may need to unmount it first:
# sudo umount /dev/sdb1
# sudo mkfs -t ext3 /dev/sdb1
How to convert to EXT4 non-destructively from EXT3 for SD-EXT and Dalvik when you have activated A2SD chachesd and A2SD datasd?
EXT3 > EXT4
Easy. Don't convert. Ext4 spoils your card.
Sent from my GT-S5830 using XDA App
http://www.ibm.com/developerworks/linux/library/l-ext4/
is a good resource for this.
http://ext3vsext4.com/2011/06/ext4-compared-to-ext3/
Something else to read
http://gparted.sourceforge.net/
or try this.
Hope it helps.
Baracs said:
http://www.ibm.com/developerworks/linux/library/l-ext4/
is a good resource for this.
http://ext3vsext4.com/2011/06/ext4-compared-to-ext3/
Something else to read
http://gparted.sourceforge.net/
or try this.
Hope it helps.
Click to expand...
Click to collapse
I booted into Ubuntu Linux LiveCD then
Converting ext3 to ext4
If you are upgrading /dev/sda2 that is mounted as /home, from ext3 to ext4, do the following.
umount /dev/sda2
tune2fs -O extents,uninit_bg,dir_index /dev/sda2
e2fsck -pf /dev/sda2
mount /dev/sda2 /home
Again, try all of the above commands only on a test system, where you can afford to lose all your data.
Click to expand...
Click to collapse
from http://www.thegeekstuff.com/2011/05/ext2-ext3-ext4/
Although in Minitool Partition Wizard Home Edition, no matter how many times I refresh it, the EXT4 partition that shows as /dev/sdb2 in GParted always shows as EXT3. Maybe a program limitation?
Why?
consegregate said:
Easy. Don't convert. Ext4 spoils your card
Click to expand...
Click to collapse
Why does it spoil the card? Did it spoil your card with data=writeback (no journalling) mode or without?
Well, I've just had a complete corruption of my ext4 /sd-ext/ *with* journalling, and rebooting into recovery and using e2fsck on the unmounted partition couldn't fix the filesystem:
Code:
e2fsck: Invalid argument passed to ext2 library while rewriting block and inode bitmaps for /dev/block/mmcblk0p2
Not sure why ext2 library error occurs with e2fsck, but no way to fix, had to do a full recover of sd-ext using CWM...
I've not used ext2, but do note that cyanogenmod 7.2 always mounts /sd-ext/ as ext3, I suppose for a reason...
Hi,
i have a new (factory default) microSDHC card preformatted with FAT32 and want to check the block size of the FAT32 format. For ext3/4 there is 'tune2fs -l' but that doesn't work with vfat. Is there any similar tool that extracts/views some detailed informations of vfat partitions (windows or linux tool doesn't matter)?
Hi,
I'm trying to figure out the partitioning on my phone (Acer E2 V370).
With fdisk I have this layout
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1665 2944 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2945 4224 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5825 6592 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8385 110784 819200 83 Linux
/dev/block/mmcblk0p6 257985 64 2145420287+ 83 Linux
This doesn't make a lot of sense. 2145420287 blocks means 1039.something Gigabytes ?
Using parted for my SDCard gives me neatly two partitions with their respective sizes and fstype,
but using it on my internal memory, gives me errors, stating that the partitions can't be outside the disk.
This necessarily doesn't mean anything's wrong though, the phone (used to) boot(s) just fine,
and I noticed other people getting the same error message because they gparted the internal memory by accident
What actually went wrong, is that I reformatted the internal sdcard with ext3 using gparted while my phone was connected by UMS.
Since then it won't mount in android or on my linux box.
The reason I wanted to do this, is to use that internal storage as the location for link2sd.
I accidently wiped pretty much everything on my SD-Card (32Gb)
and the backup from my previous ROM (4.2.2) doesn't restore properly,
so nothing more can go wrong.
I can always repush the images back onto the phone using fastboot, right ?
Can anyone help me out, maybe by posting the results of fdisk -l /dev/block/mmcblk0 ?
oneindelijk said:
Can anyone help me out, maybe by posting the results of fdisk -l /dev/block/mmcblk0 ?
Click to expand...
Click to collapse
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 757760 6062048 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 757761 1003520 1966080 c Win95 FAT32 (LBA)
Partition 2 does not end on cylinder boundary
kalpetros said:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 757760 6062048 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 757761 1003520 1966080 c Win95 FAT32 (LBA)
Partition 2 does not end on cylinder boundary
Click to expand...
Click to collapse
Thanks !
That looks like your sdcard is on mmcblkp0, like I've seen with other devices.
Which device is this ?
It's a Galaxy S I9000.
mmcblk0p8
Hi,
I'm still trying to figure out this whole partition-mess.
I've found out by using parted on each partition in mmcblk0
that mmcblk0p8 is about 1.7 Gb.
This is the partition I'm looking for, but why is fdisk /dev/mmcblk0 only showing 6
(And parted is just throwing an error, because the boundaries are out of bounds...)
Is there a way to make a full backup of my whole device, so I can restore it when messing up ?
(Perhaps dd each partition and the bootsector somehow ?)
oneindelijk said:
Hi,
I'm still trying to figure out this whole partition-mess.
I've found out by using parted on each partition in mmcblk0
that mmcblk0p8 is about 1.7 Gb.
This is the partition I'm looking for, but why is fdisk /dev/mmcblk0 only showing 6
(And parted is just throwing an error, because the boundaries are out of bounds...)
Is there a way to make a full backup of my whole device, so I can restore it when messing up ?
(Perhaps dd each partition and the bootsector somehow ?)
Click to expand...
Click to collapse
Yes you can use the recovery (CWM) to backup your device.
CWM
kalpetros said:
Yes you can use the recovery (CWM) to backup your device.
Click to expand...
Click to collapse
Or TWRP is just as well I suppose ?
I already make several backups, but will these store the size of the partitions as well ?
oneindelijk said:
Or TWRP is just as well I suppose ?
I already make several backups, but will these store the size of the partitions as well ?
Click to expand...
Click to collapse
Yes the size of the partition will be stored.
You can use TWRP too.