+- www.chinaphonearena.com (https://www.chinaphonearena.com/forum)
+-- Forum: Phone & Tablet Root, Hack and Develop (https://www.chinaphonearena.com/forum/Forum-Phone-Tablet-Root-Hack-and-Develop)
+--- Forum: *Tech support* General Phone & Tablet Root, Hack and Develop Root IMEI NVRAM CWM TWRP BRICKED (https://www.chinaphonearena.com/forum/Forum-Tech-support-General-Phone-Tablet-Root-Hack-and-Develop-Root-IMEI-NVRAM-CWM-TWRP-BRICKED)
+--- Thread: Scatter Meizu MX4 Error (/Thread-Scatter-Meizu-MX4-Error)
Pages:
1
2
Scatter Meizu MX4 Error - Naphtha - 2015-06-26
I have a problem when i try to open scatter of meizu mx4 on flyme 4.0.2I
RE: Scatter Meizu MX4 Error - cookiedough - 2015-06-26
can you attach the scatter? Also make sure you're using the latest version of SP Flash 5.1516. It can be downloaded in tools section here.
RE: Scatter Meizu MX4 Error - Naphtha - 2015-06-26
(2015-06-26, 12:44)cookiedough Wrote: can you attach the scatter? Also make sure you're using the latest version of SP Flash 5.1516. It can be downloaded in tools section here.
ThanksSame problem with the latest version (SP Flash 5.1516)
RE: Scatter Meizu MX4 Error - cookiedough - 2015-06-26
That scatter isn't for this tool. Not sure what tool its for, but not this one. It came with the ROM?
RE: Scatter Meizu MX4 Error - Naphtha - 2015-06-26
Yes come with the ROMs (4.0.1a or 4.0.2i do the same error)...what a kind of tool i need to use for open it?
RE: Scatter Meizu MX4 Error - cookiedough - 2015-06-26
(2015-06-26, 15:52)Naphtha Wrote: Yes come with the ROMs (4.0.1a or 4.0.2i do the same error)...what a kind of tool i need to use for open it?
I'm not sure. You can try older versions of SP Flash Tool. There are some in the tools section. Maybe try 3.1326. My opinion is that you're playing with fire and just leave your phone alone if there's not full instructions on which tool to use etc...
RE: Scatter Meizu MX4 Error - Naphtha - 2015-06-26
(2015-06-26, 17:39)cookiedough Wrote:(2015-06-26, 15:52)Naphtha Wrote: Yes come with the ROMs (4.0.1a or 4.0.2i do the same error)...what a kind of tool i need to use for open it?
I'm not sure. You can try older versions of SP Flash Tool. There are some in the tools section. Maybe try 3.1326. My opinion is that you're playing with fire and just leave your phone alone if there's not full instructions on which tool to use etc...
I'll consider your advice, thanks.
RE: Scatter Meizu MX4 Error - Bacon_Puffs - 2015-06-26
Yea this looks like an old scatter for older SP tools, but your phone has a newer SoC. If you figure it out, please follow up and let us know.
RE: Scatter Meizu MX4 Error - Naphtha - 2015-06-26
(2015-06-26, 18:21)Bacon_Puffs Wrote: Yea this looks like an old scatter for older SP tools, but your phone has a newer SoC. If you figure it out, please follow up and let us know.
Nothing
RE: Scatter Meizu MX4 Error - Naphtha - 2015-06-27
"Method 2
Using ROM_0 upload from SP Flash Tool
There are already tons of guides doing this so i won't touch on this . . .
What is interesting about this is syserr actually made the discovery & shared his findings since last year ! But i guess nobody discover his thread including myself until i hunt for ways to make backups on the new MT6595 since we have been spoilt by the awesomeness of MTK Droid Tools doing these automatically for us but now it doesn't work on the new MT6595 . . .
As syserr has mentioned on his thread, MTK Droid Tools is actually also using dd command to split the ROM_0 uploaded from SP Flash Tool too.
i have tried it on my old MT6577 & it worked perfectly splitting up all the partitions & generate a perfectly working scatter.txt from dumchar_info too . . . Having said that, however, its not compatible for use with the MT6595 scatter V1.1.2 format.
Complete full output.
Code:
./dice.sh MT6577_Android_scatter_emmc.txt ROM_0 > log.txt
I have modded his script to show as below so we know how it works . . .
Code:
scatter file name = MT6577_Android_scatter_emmc.txt
SP Flash Tool ROM file name = ROM_0
Processing: PRELOADER
start: 0x0
size: 0x40000
(0x0) Size in DEC = 0
(0x40) Size in DEC = 64
dd if=ROM_0 of=raw.partitions/PRELOADER bs=4096 skip=0 count=64
Processing: DSP_BL
start: 0x40000
size: 0x5C0000
(0x40) Size in DEC = 64
(0x5C0) Size in DEC = 1472
dd if=ROM_0 of=raw.partitions/DSP_BL bs=4096 skip=64 count=1472
Processing: MBR
start: 0x600000
size: 0x4000
(0x600) Size in DEC = 1536
(0x4) Size in DEC = 4
dd if=ROM_0 of=raw.partitions/MBR bs=4096 skip=1536 count=4
Processing: EBR1
start: 0x604000
size: 0x4000
(0x604) Size in DEC = 1540
(0x4) Size in DEC = 4
dd if=ROM_0 of=raw.partitions/EBR1 bs=4096 skip=1540 count=4
Processing: PMT
start: 0x608000
size: 0x400000
(0x608) Size in DEC = 1544
(0x400) Size in DEC = 1024
dd if=ROM_0 of=raw.partitions/PMT bs=4096 skip=1544 count=1024
Processing: NVRAM
start: 0xa08000
size: 0x500000
(0xa08) Size in DEC = 2568
(0x500) Size in DEC = 1280
dd if=ROM_0 of=raw.partitions/NVRAM bs=4096 skip=2568 count=1280
Processing: SECCFG
start: 0xf08000
size: 0x20000
(0xf08) Size in DEC = 3848
(0x20) Size in DEC = 32
dd if=ROM_0 of=raw.partitions/SECCFG bs=4096 skip=3848 count=32
Processing: UBOOT
start: 0xf28000
size: 0x60000
(0xf28) Size in DEC = 3880
(0x60) Size in DEC = 96
dd if=ROM_0 of=raw.partitions/UBOOT bs=4096 skip=3880 count=96
Processing: BOOTIMG
start: 0xf88000
size: 0x600000
(0xf88) Size in DEC = 3976
(0x600) Size in DEC = 1536
dd if=ROM_0 of=raw.partitions/BOOTIMG bs=4096 skip=3976 count=1536
Processing: RECOVERY
start: 0x1588000
size: 0x800000
(0x1588) Size in DEC = 5512
(0x800) Size in DEC = 2048
dd if=ROM_0 of=raw.partitions/RECOVERY bs=4096 skip=5512 count=2048
Processing: SEC_RO
start: 0x1d88000
size: 0x400000
(0x1d88) Size in DEC = 7560
(0x400) Size in DEC = 1024
dd if=ROM_0 of=raw.partitions/SEC_RO bs=4096 skip=7560 count=1024
Processing: MISC
start: 0x2188000
size: 0x60000
(0x2188) Size in DEC = 8584
(0x60) Size in DEC = 96
dd if=ROM_0 of=raw.partitions/MISC bs=4096 skip=8584 count=96
Processing: LOGO
start: 0x21e8000
size: 0x300000
(0x21e8) Size in DEC = 8680
(0x300) Size in DEC = 768
dd if=ROM_0 of=raw.partitions/LOGO bs=4096 skip=8680 count=768
Processing: EXPDB
start: 0x24e8000
size: 0x200000
(0x24e8) Size in DEC = 9448
(0x200) Size in DEC = 512
dd if=ROM_0 of=raw.partitions/EXPDB bs=4096 skip=9448 count=512
Processing: ANDROID
start: 0x26e8000
size: 0x19000000
(0x26e8) Size in DEC = 9960
(0x19000) Size in DEC = 102400
dd if=ROM_0 of=raw.partitions/ANDROID bs=4096 skip=9960 count=102400
Processing: CACHE
start: 0x1b6e8000
size: 0x19000000
(0x1b6e8) Size in DEC = 112360
(0x19000) Size in DEC = 102400
dd if=ROM_0 of=raw.partitions/CACHE bs=4096 skip=112360 count=102400
Processing: USRDATA
start: 0x346e8000
size: 0x34300000
(0x346e8) Size in DEC = 214760
(0x34300) Size in DEC = 213760
dd if=ROM_0 of=raw.partitions/USRDATA bs=4096 skip=214760 count=213760
Processing: FAT
start: 0x689e8000
size: 0x976080A8
(0x689e8) Size in DEC = 428520
(0x976080A8) Size in DEC = 2539684008
dd if=ROM_0 of=raw.partitions/FAT bs=4096 skip=428520 count=2539684008
Based on his script output above, below should work on the new MT6595.
Code:
Name Start Size
boot 0x0000000001d20000 0x0000000001000000
Code:
start: 0x1d20000
size: 0x1000000
0x1d20 - Convert to decimal = 7456
0x1000 - Convert to decimal = 4096
dd if=ROM_0 of=boot.img bs=4096 skip=7456 count=4096
You can also use his trim.sh & trimFF.sh to automatically remove all the unused FF & 00 at preloader.bin too . . .
i don't have a MT6595 to confirm all this so owners of the new MT6595 should Trial & Error, more info then study syserr's thread . . .
"
ok... what i need to do? LOL