Post Reply

[Q] Need help in changing FS type for int. and ext. SD on MTK6589

13th January 2014, 06:20 AM   |  #1  
OP Junior Member
Flag St. Peterburg
Thanks Meter: 0
 
5 posts
Join Date:Joined: Jan 2014
More
Hello, all!

Trying to customize my new device (Runbo X6: MTK6589T, 2GB RAM, 32GB ROM, Android 4.2.1) I discovered some problems and hope for some help her.

1) Repartitioning
Actually, I successfully edited the partition table in EBR1 and EBR2 and the start addresses in the Scatter file and proofed it multipple times by recalculating, but after flashing, although I get a correct output in system settings and by dumping /proc/emmc, /proc/partitions and /proc/dumchar_info, when I try to push some apps, for ex., above the initial 680MB to /system/app or something similar I get a "disk is full" message. As I was able to find out only the /data and /fat partitions get physically updated by the new sizes, meanwhile the /system and /cache partitions remain physically on the initial state and get updated by the new sizes logical only. Although if after flashing I dump the system image by "cat /dev/block/mmcblk0p5 > /sdcard/system.img" I get an image with a size corresponding to the updated size of the partition.

Initial values:
EBR1

begin /system = 00 18 02 00 (real 00 02 18 00)= 137216 blocks (* 512 bytes + 1024 blocks of 512 bytes) = 70778880 bytes
size /system = 00 50 14 00 (real 00 14 50 00) = 1331200 blocks (* 512 bytes) = 681574400 bytes
begin /cache = 00 68 16 00 = 1468416 blocks = 752353280 bytes
size /cache = 00 F0 03 00 = 258048 blocks = 132120576 bytes
begin /data = 00 58 1A 00 = 1726464 blocks = 884473856 bytes
size /data = 00 00 40 00 = 4194304 blocks = 2147483648 bytes

EBR2
begin /fat = 00 94 58 00 = 5805056 blocks = 2972712960 bytes
size /fat = FF A7 A5 FF = 4289046527 blocks = 2195991821824 bytes

Scatter
ANDROID = 0x4980000 = 77070336 bytes (- 12 * 1024 blocks of 512 bytes; I don't know why even 12, perhaps you can explain...) = 70778880 bytes
CACHE = 0x2d380000 = 758644736 bytes = 752353280 bytes
USRDATA = 0x35180000 = 890765312 bytes = 884473856 bytes
__NODL_FAT = 0xb5180000 = 3038248960 bytes = 3031957504 bytes

My values:
EBR1

begin /system = 00 18 02 00 (real 00 02 18 00)= 137216 blocks = 70778880 bytes
size /system = 00 40 51 00 (real 00 40 51 00) = 5324800 blocks = 2726297600 bytes
begin /cache = 00 58 53 00 = 5462016 blocks = 2797076480 bytes
size /cache = 00 D0 0B 00 = 774144 blocks = 396361728 bytes
begin /data = 00 28 5F 00 = 6236160 blocks = 3193438208 bytes
size /data = 00 00 A0 00 = 10485760 blocks = 5368709120 bytes

EBR2
begin /fat = 00 64 FD 00 = 16606208 blocks = 8502902784 bytes
size /fat = FF 00 D7 FF = 4278245375 blocks = 2190461632000 bytes

Scatter
ANDROID = 0x4980000 = 77070336 bytes = 70778880 bytes
CACHE = 0xa7180000 = 2803367936 bytes = 2797076480 bytes
USRDATA = 0xbeb80000 = 3199729664 bytes = 3193438208 bytes
__NODL_FAT = 0x1feb80000 = 8568438784 bytes = 8502902784 bytes

cat /proc/emmc output
android start = 00 02 00 1c , android size = 00 51 40 00
cache start = 00 53 5c 00 , cache size = 00 00 0b d0
data start = 00 00 5f 2c , data size = 00 a0 00 00
fat start = 00 00 ff 2c , fat size 02 00 a4 2c

cat /proc/partitions output
android start = 2662400 blocks
cache start = 387072 blocks
data start = 5242880 blocks
fat start = 22156800 blocks

cat /proc/dumchar_info output
android start = 04 38 00 00 , android size = a2 80 00 00
cache start = a6 b8 00 00 , cache size = 17 a0 00 00
data start = be 58 00 00 , data size = 01 40 00 00 00
fat start = 01 58 00 00 fe , fat size = 05 48 58 00 00


I also read somewhere that it is also necessary to edit PMT: in that case I tried to flash with original PMT, edited PMT and without PMT, but cuoldn't notice any difference.


2) Mounting the internal memory and external SDcard on system start natively as EXT4 instead of FAT32
Using my old device (Runbo X5: MTK6577) I had success on mounting the internal storage as EXT4 by disassembling recovery.img and editing /etc/recovery.fstab to change the "vfat" value to "ext4" and reformatting the storage after a successful boot with ne recovery, but on Runbo X6 I get no change to the filesystem after reformatting. By the external SDcard I never had success.

Thouthand thanks for any help and advices what I'm doing wrong.
Attached Files
File Type: 7z RECOVERY-ORIG-CWM.7z - [Click for QR Code] (6.58 MB, 9 views)
Last edited by wolk_tambowskij; 16th January 2014 at 04:40 PM. Reason: First problem solved for myself.
14th January 2014, 05:19 PM   |  #2  
OP Junior Member
Flag St. Peterburg
Thanks Meter: 0
 
5 posts
Join Date:Joined: Jan 2014
More
Nobody having a suggestion???
27th January 2014, 10:33 PM   |  #3  
Junior Member
Flag Barcelona
Thanks Meter: 5
 
13 posts
Join Date:Joined: May 2011
More
Maybe this one...
Hello, I just got my X6, and didn't have much time to play with it - plus I don't have your block/partition knowledge :s

So far I found this page http://4pda.ru/forum/index.php?showtopic=520192
there's a rooted rom on it (installed it trough the default recovery) - it works well.

There's also a custom recovery and some tools to install it, but running linux, I was blocked for that part.
Unfortunately, I havn't been able to boot the phone on fastboot to push it (it seems like there's no fastboot on the phone).

have you been able to get the NFC working?
28th January 2014, 03:17 AM   |  #4  
OP Junior Member
Flag St. Peterburg
Thanks Meter: 0
 
5 posts
Join Date:Joined: Jan 2014
More
Hi!
Thank you for the reply!
According to the manufacturer the NFC feature is still not working.
I tried VVL's custom on my old Runbo X5 and it had a lot of bugs... Also I don't think that he has realized the feature with different FS on SD mounting...
Besides that I have now my own custom based on the stock firmware I got with the device and its working perfect. By the way if you need a fully working CWM its provided by latest "MTK Droid and Tools".
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Android Q&A, Help & Troubleshooting by ThreadRank