Database Users

Where is my RAM/ROM?

When I click settings->memory...
I see Storage total = 47.46 MB
Program Total = 44.01MB
I suppose prophet has 128 MB ROM and 64 MB RAM... Where is the remaning storage then?

Formating Internal Memory

I own a SonyEricsson Xperia X1.
According to SKTools Main Storage is formated this way:
It has sectors with 2048 bytes size and 2048 bytes cluster size. So 1 sector per cluster. Also it is formated in FAT32.
On the other hand Storage Card has 512 bytes sector size and 4096 bytes cluster size. So 8 Sector per cluster. Also FAT32.
512 bytes sector is the norm for HardDiskDrives as well. Optical Disk Drives have 2048 bytes sector (i think).
There is going to be a move to 4096 bytes sector for HDDs starting January 2011, which gives more free space and more speed.
Could we do something like that for our phones? 4096 byte sectors and 4096 bytes clusters?

I guess storage cards are diferent Memory arrangements... we have many tweaks to have bigstorage ROMS, search and read bud

[DISCUSSION] 1.5 GB internal storage vs 4 GB - mystery solved ?

The DZ is advertised by HTC as having 1.5 GB internal storage, but the G2 is advertised as having 4 GB. As proved via teardown pictures (see http://forum.xda-developers.com/showthread.php?t=832686 ), the two phones have exactly the same 4 GB storage chip (NAND), but both also report a lot less memory available to the user (2.1 GB seems to be there if you examine the partitioning).
This has led people to try and investigate where the "missing" memory has gone, e.g. what is using it up, can we get access to it, etc.
This "mystery" seems now to have been solved, and has been posted up in the Wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#The_Missing_2GB
A summary of this was kindly posted up by dhkr123 in the G2 forums at http://forum.xda-developers.com/showpost.php?p=9174115&postcount=22 , specifically :
There are 2.1 GB of internal storage addressable by the kernel. This piece of space is divided up into several partitions, for the radio, the SPL, the SYSTEM, the USERDATA, the CACHE, and several other things. All of these partitions are accounted for within the 2.1 GB.
What has been found is that a 1-time write deal to the eMMC is responsible for converting most of the internal storage from MLC (multi-level cell, specifically, 2 bits per cell) into SLC (single-level cell, 1 bit per cell) for the purpose of improving performance and durability.
Specifically, the entire eMMC is 4 GB, and 2.1 GB are accessible, that means that ~200 MB remains MLC, the remaining 3.8 GB is converted into SLC, offering 1.9 GB. 1.9GB + 200MB = 2.1 GB.
Mystery solved, nothing you can do about it.
But understand that it is faster and more reliable like this.
Click to expand...
Click to collapse
So apparently the hardware has been setup so that there is 2.1 GB available for storage for performance and reliability reasons, and it is unlikely this can be changed.

Just found some further explanation and diagrams on this at http://tjworld.net/wiki/Android/HTC/EMMC/UnderstandingUserCapacity

Nice post
Thanks for sharing.
Even with the "hidden" partition, huh... I have installed more apps than never and I still have near-1GB free
And I think the internal mem for process and running system is a great idea since the phone runs smoother than butter
Maybe that's why nobody's talking 'bout apps2sd, which is a common topic @ other phone's fora

How do you have near 1gb free?
CacheMate for me reports 1,078MB (1.07 GB) total data, 338MB used, 760 whatever free, not 2.1GB. Is this with a ROMed DZ, stripped of major components in the system and whatnot? (ie, Sense)

GlitchZero said:
CacheMate for me reports 1,078MB (1.07 GB) total data, 338MB used, 760 whatever free, not 2.1GB.
Click to expand...
Click to collapse
That doesn't sound right at all. But I don't know anything about CacheMate.

It's a root app, clears out the dalvik (I believe) and app caches that have built up, but it shows Total Memory, Memory Used, and Free Memory, and those are my readings, and they are consistent to .01 of a megabyte with what it says in SD & Phone Storage in my Settings.

But there's 2.1 GB total user storage on the phone, so it doesn't sound like it's reporting it correctly ?

Here's the partitioning on a DZ, taken from http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning (duplicate rows deleted, see the link for more details) :
# fdisk -ul /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders, total 4554752 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4554750 2272311 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 137216 3072 4a Unknown
/dev/block/mmcblk0p14 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p15 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p16 145412 163326 8957+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1343486 571391+ 83 Linux
/dev/block/mmcblk0p26 1343488 3577854 1117183+ 83 Linux
/dev/block/mmcblk0p27 3577856 4192254 307199+ 83 Linux
/dev/block/mmcblk0p28 4192256 4234750 21247+ 19 Unknown
/dev/block/mmcblk0p29 4234752 4235263 256 23 Unknown
If you add up the sizes of partitions 4, 25, 26 and 27 (i.e. the big ones) then there is 2.1 GB in total. I wonder if CacheMate is only looking at partition 4 (1.1 GB) and not the rest ? I could be way off though.

[Q&A] [SCRIPT] Fix partition table for Android 4.4

Q&A for [SCRIPT] Fix partition table for Android 4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SCRIPT] Fix partition table for Android 4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

partition table doesn' exist
On my mi3 64gb when i flash images of the miui rom, I see the msg "partition table doesn't exist" .... How I can resolve it? Thanks

Repartition Mi3
Xiaomi Mi3W 64gb
Anyone have some idea how I resolve it:
C:\Program Files (x86)\Rayglobe Mi3 One Click Tools>C:\XiaomiTool\Drivers\adb push C:\XiaomiTool\cancro\repartition64.sh /tmp
2991 KB/s (3063 bytes in 0.001s)
C:\Program Files (x86)\Rayglobe Mi3 One Click Tools>C:\XiaomiTool\Drivers\adb shell
chmod 0777 /tmp/repartition64.sh
/tmp/repartition64.sh
~ # chmod 0777 /tmp/repartition64.sh
~ # /tmp/repartition64.sh
check environment
/sbin/mount
/sbin/umount
/sbin/parted
/sbin/tune2fs
/sbin/e2fsck
dump old table
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
unmount partitions
umount: can't umount /system: Invalid argument
umount: can't umount /system1: No such file or directory
umount: can't umount /cache: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /data_root: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /userdata: No such file or directory
change partition table
parted: delete
Error: Partition doesn't exist.
Failed changing table
Please help me, I try the linuxxx tool but nothing! .... I try the manual adb command.... but nothing.....
Did U have other tool ??? any script ??? anything!!! ....

You're on Mi2/S section, why you used this on your Mi3?
Also on Mi3 there's no need to extend partitons.

This formatted my whole phone except sd storage, is this normal? I just restored the back up but was wondering if by doing so the repartitioning doesn't get reversed.

Can I change application storage with this script on my mi2?
Thanks

two stupid question
Sorry guys
I have two stupid question to ask.
first after I boot to CWM and mount sd card，
should I need to wipe user data and cache and davilk for this script？
second if I backup the my rom，
can I restore it in new system partition table？
Thanks guys

The filesystem
I looked into the shell script
The filesystem is ext2
Should I modify to ext4 or just leave it alone

Fresh install of script: 20 GB space lost
My device Mi2S with 32GB was bricked. I managed to install the script and it's working again with MIUI V7
Somehow it lost 20Gb of space? I don't know what to do, or how to mount everything back.
please help
--------------------------
Internal Storage (MMC)
--------------------------
* modem [mmcblk0p1] (/firmware) [vfat]
Used: 50.7 MB, Free: 34.3 MB, Total space: 85 MB
* modem1 [mmcblk0p2] Not mounted
* sbl1 [mmcblk0p3] Not mounted
* sbl2 [mmcblk0p4] Not mounted
* sbl3 [mmcblk0p5] Not mounted
* rpm [mmcblk0p6] Not mounted
* tz [mmcblk0p7] Not mounted
* DDR [mmcblk0p8] Not mounted
* aboot [mmcblk0p9] Not mounted
* misc [mmcblk0p10] Not mounted
* logo [mmcblk0p11] Not mounted
* m9kefs1 [mmcblk0p12] Not mounted
* m9kefs2 [mmcblk0p13] Not mounted
* m9kefsc [mmcblk0p14] Not mounted
* bk1 [mmcblk0p15] Not mounted
* m9kefs3 [mmcblk0p16] Not mounted
* bk2 [mmcblk0p17] Not mounted
* boot [mmcblk0p18] Not mounted
* boot1 [mmcblk0p19] Not mounted
* recovery [mmcblk0p20] Not mounted
* bk3 [mmcblk0p21] Not mounted
* persist [mmcblk0p22] (/persist) [ext4]
Used: 4.3 MB, Free: 3.7 MB, Total space: 8 MB
* System [mmcblk0p23] (/system) [ext4]
Used: 502 MB, Free: 298 MB, Total space: 801 MB
* system1 [mmcblk0p24] Not mounted
* Cache [mmcblk0p25] (/cache) [ext4]
Used: 11.2 MB, Free: 373 MB, Total space: 384 MB
* Data (userdata) [mmcblk0p26] (/data) [ext4]
Used: 2.6 GB, Free: 360 MB, Total space: 2.9 GB
--------------------------
tmpfs mount points
--------------------------
* /dev [tmpfs]
Used: 68 KB, Free: 961 MB, Total space: 962 MB
* /mnt/asec [tmpfs]
Used: 0 B, Free: 962 MB, Total space: 962 MB
* /mnt/obb [tmpfs]
Used: 0 B, Free: 962 MB, Total space: 962 MB
* /storage/emulated [tmpfs]
Used: 0 B, Free: 962 MB, Total space: 962 MB
--------------------------
Memory
--------------------------
* RAM
Used: 1 GB, Free: 873 MB, Total space: 1.9 GB

Resize all the partitions and reflash your rom

[TWRP][UNOFICIAL] 2.7.0.0-dualboot/2.8.2.0 for Xiaomi Mi2s - supports TDB

{
"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"
}
Team Win Recovery Project 2.8, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
The 2.8.2.0 edition is the original one, you won't find dualboot support in it, only f2fs
​
Not working on the 2.7.0.0 edition​
You can't migrate from ext4 to f2fs from the recovery UI ( although there is a script on my folder doing so)
You can't access the sys1 partition
Working on the 2.7.0.0 edition
Formatting either if partition are f2fs or ext4(even if you want explicitly migrate from f2fs to ext4 and vice versa the recovery succeed at formating a f2fs partiion)
Supports TDB.
and all the other stuff of twrp 2.7.0.0
Key Features:
Ability to save custom recovery settings
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times.
​Instructions:​
Boot into the bootloader
fastboot flash recovery PATHTOYOURIMG.img ( linux users will have to use sudo)
done
​Change language:
By default the recovery is in Japanese, however, you can change the default language.
However you can change the language by following those steps
Click on advanced
Click on Theme and language
Choice English in the crap menu
Download
​
XDA:DevDB Information
TWRP 2.7.0.0 for Xiaomi mi2s, Tool/Utility for the Xiaomi Mi 2
Contributors
Khaon, TeamWin(for twrp), sndnvaps for his port
Version Information
Status: Testing
Stable Release Date: 2014-12-16
Current Beta Version: first release
Beta Release Date: 2014-10-29
Created 2014-10-29
Last Updated 2014-12-15

Reserved

I will look when got time to make it english by default.

Switching troubles
I have CWM from M1kka, i use TDB, how can i switch recoveries without any dramas?

NightHeron said:
I have CWM from M1kka, i use TDB, how can i switch recoveries without any dramas?
Click to expand...
Click to collapse
Golden RUle : backup data folder in case of **** happens.
I am using aswell tdb on this one and is working great.

I have recovery bootloops with your build. It's not the case with sndnvaps's (but his recovery definitly wont install anything on sys1). I've also made it flashable through cwm with script deleting install-cm-recovery.sh on both sys. Didn't changed things. I have been able to reboot to recovery only the first time I have flashed it through fastboot. I can't make it bootable since when I have rebooted from second sys (on pac) to recovery. Need your illumination..

we can't format to F2fs is right? Ps, for me recovery starts and working
Hem.. too fast.. recovery bootloop.. LOL for me

No f2fs if khaon didn't already integrated

Indeed I will have to fix few things such correct mounting partitions
For now you install can w/e you want on sys0.
The recovery has been built with this F2fs drivers need to be included otherwise it wont be able to mount your system partition.
If you format a f2fs partition you will see it detects it and use mkfs.f2fs.
What I will do to is port this one to 2.7.0.1 firstly, because it gives to users the possibility to switch from ext4 to f2fs vice versa
i have installed a rom on sys1 with system beein gf2fs

Seems i cant use the download link... it redirect s to homepage...

henry0504 said:
Seems i cant use the download link... it redirect s to homepage...
Click to expand...
Click to collapse
https://www.mediafire.com/folder/ue5d5ae38fabx/Aries
It's his MediaFire account, just click the TWRP folder for the link.

I have corrected the issue with the access to the internal storage, also wiping dalvik doesnt wipe data partition anymore.

original unofficial twrp 2.8.2.0 with f2fs support added.

@Khaon
The 2.8.2.0 edition is the original one, you won't find dualboot support in it, only f2fs
Click to expand...
Click to collapse
Does this mean there's no tdb, or ext4/f2fs migration support in plan?

Beyaz66 said:
@Khaon
Does this mean there's no tdb, or ext4/f2fs migration support in plan?
Click to expand...
Click to collapse
There is the option to migrate from ext4/f2fs, it is located at "wipe"=> "advanced" => "reparir or change fs".
I won't support any dual boot support with lollipop and onwards releases

format bad block
I suspect I've bad blocks in the nand on \data or \sdcard0. Can TWRP format \data or \sdcard to detect and fix if there're bad blocks?
Pls advice!

Hi @Khaon
Here's what I did:
Formatted Sys0,Sys1,data,cache with CWM 6.0.5.1
Disabled TDB in CWM
Upgraded to your TWRP 2.8.5
Re-partitionned sys1(=1MB),cache(=150MB),data(4648MB)
Then trying to switch data partition's fs to f2fs through twrp gives error.
¤¤ Is there any problem related to data partition in twrp? What is the "16384" in length and mkfs option?
Log (full log joined)
Code:
17| Renaming regular /etc/recovery.fstab -> /etc/recovery.fstab.bak
18| Moving /etc/twrp.fstab -> /etc/recovery.fstab
[...]
81| /data | /dev/block/mmcblk0p26 | Size: 4287MB Used: 76MB Free: 4210MB Backup Size: 76MB
82| Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Can_Encrypt_Backup Use_Userdata_Encryption
83| Primary_Block_Device: /dev/block/mmcblk0p26
84| Length: -16384
85| Display_Name: Data
86| Storage_Name: Data
87| Backup_Path: /data
88| Backup_Name: data
89| Backup_Display_Name: Data
90| Storage_Path: /data
91| Current_File_System: ext4
92| Fstab_File_System: ext4
93| Backup_Method: files
[...]
418| mkfs.f2fs: invalid option -- r
[...]
435| I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p26 process ended with ERROR=1
436| E:Unable to wipe '/data'.
437| E:Error changing file system.
From recovery.fstab:
Code:
4| /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
Formatting with "mkfs.f2fs /dev/block/mmcblk0p26" + "fsck.f2fs /dev/block/mmcblk0p26" through adb is OK and TWRP shows it as F2FS.
¤¤ I also have difficult to reduce the space reserved by f2fs. "f2fs -o XX" gives me strange overprovision ratios. Here's what a see in TWRP:
Code:
SYSTEM (size 510MB) [RE-FORMATED TO EXT4]
Formatting with TWRP uses: 116 MB
2%: 220 MB
3%: 158 MB
4%: 130 MB
5%: 116 MB
6%: 104 MB
7%: 100 MB
8%: 98 MB [LOWEST]
9%: 98 MB [LOWEST]
10%: 100 MB
11%: 100 MB
13%: 102 MB
15%: 108 MB
20%: 128 MB
ext4 usage: 8 MB
Code:
CACHE (size 141MB)
Formatting with TWRP uses: 97 MB
<3% IMPOSSIBLE
4%: 116 MB
5%: 96 MB
6%: 82 MB
7%: 68 MB
8%: 66 MB
9%: 64 MB
10%: 62 MB
11%: 60 MB
15%: 50 MB [LOWEST]
16%: 52 MB
17%: 50 MB [LOWEST]
18: 52 MB
19%: 52 MB
20%: 54 MB
22%: 50 MB [LOWEST]
23%: 52 MB
24%: 54 MB
25%: 54 MB
30%: 56 MB
40%: 64 MB
50%: 74 MB
ext4 usage: 8 MB
Code:
DATA (size 4432MB)
Formatting with TWRP doesn't work
1%: 454 MB
2%: 298 MB
3%: 274 MB [LOWEST]
4%: 286 MB
5%: 310 MB
6%: 338 MB
7%: 368 MB
8%: 404 MB
9%: 442 MB
10%: 482 MB
15%: 680 MBa
20%: 892 MB
ext4 usage: 96 MB
Why ratios are fluctuating so strangely as they aren't related to a 'min required+percentage of the total size' under a certain value?
Note: Everything is fine when living all partitions in ext4 or all f2fs except system. Booting with f2fs fs on system wasn't a succeed even with xperianrpo's full f2fs supposed rom and many other "tricks".
Many thanks for the job!

Beyaz66 said:
Hi @Khaon
Here's what I did:
Formatted Sys0,Sys1,data,cache with CWM 6.0.5.1
Disabled TDB in CWM
Upgraded to your TWRP 2.8.5
Re-partitionned sys1(=1MB),cache(=150MB),data(4648MB)
Then trying to switch data partition's fs to f2fs through twrp gives error.
¤¤ Is there any problem related to data partition in twrp? What is the "16384" in length and mkfs option?
Log (full log joined)
Code:
17| Renaming regular /etc/recovery.fstab -> /etc/recovery.fstab.bak
18| Moving /etc/twrp.fstab -> /etc/recovery.fstab
[...]
81| /data | /dev/block/mmcblk0p26 | Size: 4287MB Used: 76MB Free: 4210MB Backup Size: 76MB
82| Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Can_Encrypt_Backup Use_Userdata_Encryption
83| Primary_Block_Device: /dev/block/mmcblk0p26
84| Length: -16384
85| Display_Name: Data
86| Storage_Name: Data
87| Backup_Path: /data
88| Backup_Name: data
89| Backup_Display_Name: Data
90| Storage_Path: /data
91| Current_File_System: ext4
92| Fstab_File_System: ext4
93| Backup_Method: files
[...]
418| mkfs.f2fs: invalid option -- r
[...]
435| I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p26 process ended with ERROR=1
436| E:Unable to wipe '/data'.
437| E:Error changing file system.
From recovery.fstab:
Code:
4| /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
Formatting with "mkfs.f2fs /dev/block/mmcblk0p26" + "fsck.f2fs /dev/block/mmcblk0p26" through adb is OK and TWRP shows it as F2FS.
¤¤ I also have difficult to reduce the space reserved by f2fs. "f2fs -o XX" gives me strange overprovision ratios. Here's what a see in TWRP:
Code:
SYSTEM (size 510MB) [RE-FORMATED TO EXT4]
Formatting with TWRP uses: 116 MB
2%: 220 MB
3%: 158 MB
4%: 130 MB
5%: 116 MB
6%: 104 MB
7%: 100 MB
8%: 98 MB [LOWEST]
9%: 98 MB [LOWEST]
10%: 100 MB
11%: 100 MB
13%: 102 MB
15%: 108 MB
20%: 128 MB
ext4 usage: 8 MB
Code:
CACHE (size 141MB)
Formatting with TWRP uses: 97 MB
<3% IMPOSSIBLE
4%: 116 MB
5%: 96 MB
6%: 82 MB
7%: 68 MB
8%: 66 MB
9%: 64 MB
10%: 62 MB
11%: 60 MB
15%: 50 MB [LOWEST]
16%: 52 MB
17%: 50 MB [LOWEST]
18: 52 MB
19%: 52 MB
20%: 54 MB
22%: 50 MB [LOWEST]
23%: 52 MB
24%: 54 MB
25%: 54 MB
30%: 56 MB
40%: 64 MB
50%: 74 MB
ext4 usage: 8 MB
Code:
DATA (size 4432MB)
Formatting with TWRP doesn't work
1%: 454 MB
2%: 298 MB
3%: 274 MB [LOWEST]
4%: 286 MB
5%: 310 MB
6%: 338 MB
7%: 368 MB
8%: 404 MB
9%: 442 MB
10%: 482 MB
15%: 680 MBa
20%: 892 MB
ext4 usage: 96 MB
Why ratios are fluctuating so strangely as they aren't related to a 'min required+percentage of the total size' under a certain value?
Note: Everything is fine when living all partitions in ext4 or all f2fs except system. Booting with f2fs fs on system wasn't a succeed even with xperianrpo's full f2fs supposed rom and many other "tricks".
Many thanks for the job!
Click to expand...
Click to collapse
Ioups yeah the recovery needs to be updated . The length is a space that will be exclusively reserved for the crypto key if your device is encrypted...
No idea indeed, according to the doc its defined as a percentage over the volume size. But apparently from the little doc I have just read
Even though there is a loss in user capacity with over-provisioning, the user does receive two important benefits: better performance and greater endurance. The former is one of the reasons for using flash memory, including in solid state drives (SSDs), while the latter addresses an inherent limitation in flash memory.
Click to expand...
Click to collapse
I will release by tomorrow an updated twrp

Khaon said:
Ioups yeah the recovery needs to be updated . The length is a space that will be exclusively reserved for the crypto key if your device is encrypted...
No idea indeed, according to the doc its defined as a percentage over the volume size. But apparently from the little doc I have just read
I will release by tomorrow an updated twrp
Click to expand...
Click to collapse
After flashing, my Mi2s reboots into into the standard MI recovery.... Where is the trick?
---------- Post added at 06:14 PM ---------- Previous post was at 06:03 PM ----------
Matze001 said:
After flashing, my Mi2s reboots into into the standard MI recovery.... Where is the trick?
Click to expand...
Click to collapse
Now it worked but still unable to mount SD...

http://d-h.st/jP78 The last M1cha's TWRP from MiFlash4Linux packages. v2.8.7.0 for both partitions
Code:
fastboot oem unlock
Code:
fastboot erase recovery
Code:
fastboot flash recovery therecoveryname.img