FORUMS
Remove All Ads from XDA

[TUTORIAL]How to setup SP_Flash_Tool_Linux (MTK/MediaTek Soc)

175 posts
Thanks Meter: 135
 
By Miss Montage, Senior Member on 19th July 2015, 05:17 PM
Post Reply Email Thread
13th August 2015, 11:10 PM |#11  
OP Senior Member
Thanks Meter: 135
 
More
Where did you get the scatter file? Generally this error code means that the partition table is different to the one on your device. This should only be the case - occasionally - if you flash a complete firmware.
(Or replace Android through Ubuntu / vc. vs.)
 
 
13th August 2015, 11:19 PM |#12  
Al3XKOoL's Avatar
Inactive Recognized Developer
Flag Tenerife (Canary Islands, Spain)
Thanks Meter: 1,458
 
Donate to Me
More
Quote:
Originally Posted by Miss Montage

Where did you get the scatter file? Generally this error code means that the partition table is different to the one on your device. This should only be the case - here and then - if you flash a complete firmware.
(Or replace Android through Ubuntu / vc. vs.)

I know this error, so I am surprised
scatter is from my stock rom. Same i used to flash.
13th August 2015, 11:28 PM |#13  
OP Senior Member
Thanks Meter: 135
 
More
Hmm, dunno why that is. Can you compare the scatter.txt to the /proc/emmc file on your phone?
And at what stage do you get the error? Immediately after connecting or later?
14th August 2015, 12:01 AM |#14  
Al3XKOoL's Avatar
Inactive Recognized Developer
Flag Tenerife (Canary Islands, Spain)
Thanks Meter: 1,458
 
Donate to Me
More
Quote:
Originally Posted by Miss Montage

Hmm, dunno why that is. Can you compare the scatter.txt to the /proc/emmc file on your phone?
And at what stage do you get the error? Immediately after connecting or later?

Right now I remembered in windows long ago got the same problem.
This happens if I try to use flash sp tool new versions

In windows:
Quote:

Working: v5.1352.01
Not Working: v5.1512.00.000

The Following User Says Thank You to Al3XKOoL For This Useful Post: [ View ] Gift Al3XKOoL Ad-Free
14th August 2015, 12:07 AM |#15  
OP Senior Member
Thanks Meter: 135
 
More
The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?
14th August 2015, 12:17 AM |#16  
Al3XKOoL's Avatar
Inactive Recognized Developer
Flag Tenerife (Canary Islands, Spain)
Thanks Meter: 1,458
 
Donate to Me
More
Quote:
Originally Posted by Miss Montage

The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?

SP_Flash_Tool_Linux_v5.1452.00.100 tested, same problem.
SP_Flash_Tool_Linux_v5.1436.00.100 also tested and same.

No older versions found
14th August 2015, 12:29 AM |#17  
OP Senior Member
Thanks Meter: 135
 
More
The version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?
14th August 2015, 12:54 AM |#18  
OP Senior Member
Thanks Meter: 135
 
More
Have you also tried the newest version? I just involuntarily re-flashed my UMI Hammer with it... Wanted to choose the twrp only, but too much multi-tasking leads to no good
14th August 2015, 01:01 AM |#19  
Al3XKOoL's Avatar
Inactive Recognized Developer
Flag Tenerife (Canary Islands, Spain)
Thanks Meter: 1,458
 
Donate to Me
More
Quote:
Originally Posted by Miss Montage

The 32bit-version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?

Tested and same.

Here logs
Attached Files
File Type: log QT_FLASH_TOOL.log - [Click for QR Code] (47.3 KB, 82 views)
File Type: log BROM_DLL_V5.log - [Click for QR Code] (445.1 KB, 48 views)
The Following User Says Thank You to Al3XKOoL For This Useful Post: [ View ] Gift Al3XKOoL Ad-Free
14th August 2015, 01:11 AM |#20  
OP Senior Member
Thanks Meter: 135
 
More
Hmm, I will compare these lines to a successful log:
Quote:

08/13/15 23:57:01.942 BROM_DLL[6767][6774]: FlashTool_ReadPartitionInfo(0x7f7b840038a0,0x7f7b8 4013310,0x7f7b00000013): mutex: LOCK ... (mutex.cpp:151)
08/13/15 23:57:01.942 BROM_DLL[6767][6774]: FlashTool_ReadPartitionInfo(0x7f7b840038a0,0x7f7b8 4013310,0x7f7b00000013): mutex: UNLOCK. (mutex.cpp:166)
08/13/15 23:57:01.943 BROM_DLL[6767][6774]: FlashTool_Disconnect(0x840038A0): mutex: LOCK ... (mutex.cpp:151)

The Following User Says Thank You to Miss Montage For This Useful Post: [ View ] Gift Miss Montage Ad-Free
14th August 2015, 01:21 AM |#21  
OP Senior Member
Thanks Meter: 135
 
More
In my case it looks like this:
Quote:

(0x7fec2001a530,0x7fec2002aa00,0x7fec00000013): mutex: UNLOCK. (mutex.cpp:166)
08/14/15 00:47:56.969 BROM_DLL[3537][3543]: FlashTool_ReadPartitionCount(0x7fec2001a530): mutex: LOCK ... (mutex.cpp:151)
08/14/15 00:47:56.994 BROM_DLL[3537][3543]: DEBUG: ReadData(): Part(proinfo), begin_add(0x0000000000080000), len(0x0000000000300000), part_id(8). (partition_table_cmd.cpp:1099)
08/14/15 00:47:56.994 BROM_DLL[3537][3543]: DEBUG: ReadData(): Part(nvram), begin_add(0x0000000000380000), len(0x0000000000500000), part_id(8). (partition_table_cmd.cpp:1099)
08/14/15 00:47:56.994 BROM_DLL[3537][3543]: DEBUG: ReadData(): Part(protect1), begin_add(0x0000000000880000), len(0x0000000000A00000), part_id(8). (partition_table_cmd.cpp:1099)
08/14/15 00:47:56.994 BROM_DLL[3537][3543]: DEBUG: ReadData(): Part(protect2), begin_add(0x0000000001280000), len(0x0000000000A00000), part_id(8). (partition_table_cmd.cpp:1099)

You still might have a connection issue... But in your log the tool shuts down after trying to read the partition count. And it looks at three different block starts for that info. My log only mentions one block start at that stage.
I'm out of my wits...
Which device do you want to flash?
The Following User Says Thank You to Miss Montage For This Useful Post: [ View ] Gift Miss Montage Ad-Free
Post Reply Subscribe to Thread

Tags
2035, flash tool linux, linux, mtk, sp_flash_tool

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes