Hovatek Forum MOBILE Android [Please help] SP Flash Tool on BLADE V7 Lite B06
Can't login? Please, reset your password.
Try our Online TWRP Builder..its free


[Please help] SP Flash Tool on BLADE V7 Lite B06

[Please help] SP Flash Tool on BLADE V7 Lite B06

Pages (4): 1 2 3 4 Next
Codu
Codu
Codu
Junior Member
23
08-02-2017, 12:33 AM
#1



Hello,

I have a problem flashing this phone using the latest SP tool. Reading works like a charm, but writing is impossible. I believe there's configuration parameter that must be fixed but I cant figure out where.

Here's the log from the ProgramData, maybe one already has fix-up (the last line is the most important):

00000011] [22:35:08:714409] [Tid0x000000bc] [info] <--[C5] comm_engine::open
[00000012] [22:35:08:715409] [Tid0x000000bc] [debug] -->[C6] boot_rom:Confusedet_transfer_channel #./brom/boot_rom.cpp (line:37)
[00000013] [22:35:08:715409] [Tid0x000000bc] [debug] <--[C6] boot_rom:Confusedet_transfer_channel
[00000014] [22:35:08:715409] [Tid0x000000bc] [debug] -->[C7] boot_rom::connect #./brom/boot_rom.cpp (line:43)
[00000015] [22:35:08:716409] [Tid0x000000bc] [info] start handshake with device.
[00000016] [22:35:08:717409] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[a0 ]
[00000017] [22:35:08:734411] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[52 ]
[00000018] [22:35:08:734411] [Tid0x000000bc] [debug] <-Rx: 0x00000004 Hex[45 41 44 59 ]
[00000019] [22:35:08:735411] [Tid0x000000bc] [info] preloader exist. connect.
[00000020] [22:35:08:736411] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[a0 ]
[00000021] [22:35:08:736411] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[5f ]
[00000022] [22:35:08:737411] [Tid0x000000bc] [debug] send 0xA0. receive 0x5F
[00000023] [22:35:08:738411] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[0a ]
[00000024] [22:35:08:738411] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[f5 ]
[00000025] [22:35:08:739412] [Tid0x000000bc] [debug] send 0x0A. receive 0xF5
[00000026] [22:35:08:740412] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[50 ]
[00000027] [22:35:08:740412] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[af ]
[00000028] [22:35:08:741412] [Tid0x000000bc] [debug] send 0x50. receive 0xAF
[00000029] [22:35:08:742412] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[05 ]
[00000030] [22:35:08:742412] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fa ]
[00000031] [22:35:08:743412] [Tid0x000000bc] [debug] send 0x05. receive 0xFA
[00000032] [22:35:08:743412] [Tid0x000000bc] [debug] <--[C7] boot_rom::connect
[00000033] [22:35:08:744412] [Tid0x000000bc] [info] (2/2)security verify tool and DA.
[00000034] [22:35:08:744412] [Tid0x000000bc] [debug] -->[C19] boot_rom_logic:Confusedecurity_verify_connection #./brom/boot_rom_logic.cpp (line:38)
[00000035] [22:35:08:744412] [Tid0x000000bc] [debug] -->[C20] boot_rom::get_preloader_version #./brom/boot_rom.cpp (line:829)
[00000036] [22:35:08:746412] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fe ]
[00000037] [22:35:08:746412] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[01 ]
[00000038] [22:35:08:747412] [Tid0x000000bc] [info] preloader version: 0x1
[00000039] [22:35:08:747412] [Tid0x000000bc] [debug] <--[C20] boot_rom::get_preloader_version
[00000040] [22:35:08:747412] [Tid0x000000bc] [info] Preloader exist. skip connection verification.
[00000041] [22:35:08:748412] [Tid0x000000bc] [debug] <--[C19] boot_rom_logic:Confusedecurity_verify_connection
[00000042] [22:35:08:748412] [Tid0x000000bc] [debug] <--[C4] connection::connect_brom
[00000043] [22:35:08:748412] [Tid0x000000bc] [info] <--[C3] flashtool_connect_brom
[00000044] [22:35:08:749413] [Tid0x000000bc] [info] -->[C23] flashtool_device_control #./interface/flashtoolex_api.cpp (line:308)
[00000045] [22:35:08:749413] [Tid0x000000bc] [debug] -->[C24] connection::device_control #./logic/connection.cpp (line:585)
[00000046] [22:35:08:750413] [Tid0x000000bc] [info] device control: DEV_GET_CHIP_ID code[0x1]
[00000047] [22:35:08:750413] [Tid0x000000bc] [debug] -->[C25] boot_rom::device_control #./brom/boot_rom.cpp (line:661)
[00000048] [22:35:08:750413] [Tid0x000000bc] [debug] <--[C25] boot_rom::device_control
[00000049] [22:35:08:751413] [Tid0x000000bc] [debug] <--[C24] connection::device_control
[00000050] [22:35:08:751413] [Tid0x000000bc] [error] <ERR_CHECKPOINT>[820][error][0xc0010007]</ERR_CHECKPOINT>flashtool_device_control fail
[00000051] [22:35:08:752413] [Tid0x000000bc] [info] <--[C23] flashtool_device_control
[00000052] [22:35:08:752413] [Tid0x000000bc] [info] -->[C26] flashtool_device_control #./interface/flashtoolex_api.cpp (line:308)
[00000053] [22:35:08:753413] [Tid0x000000bc] [debug] -->[C27] connection::device_control #./logic/connection.cpp (line:585)
[00000054] [22:35:08:753413] [Tid0x000000bc] [info] device control: DEV_GET_CHIP_ID code[0x1]
[00000055] [22:35:08:753413] [Tid0x000000bc] [debug] -->[C28] boot_rom::device_control #./brom/boot_rom.cpp (line:661)
[00000056] [22:35:08:754413] [Tid0x000000bc] [debug] -->[C29] boot_rom::get_chip_id #./brom/boot_rom.cpp (line:109)
[00000057] [22:35:08:754413] [Tid0x000000bc] [info] get chip id
[00000058] [22:35:08:756413] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fd ]
[00000059] [22:35:08:756413] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fd ]
[00000060] [22:35:08:757413] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[03 35 ]
[00000061] [22:35:08:758413] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]
[00000062] [22:35:08:760414] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fc ]
[00000063] [22:35:08:760414] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fc ]
[00000064] [22:35:08:761414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[8a 00 ]
[00000065] [22:35:08:762414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[cb 00 ]
[00000066] [22:35:08:763414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]
[00000067] [22:35:08:764414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]
[00000068] [22:35:08:765414] [Tid0x000000bc] [info] Read lib config file: C:\adb\SP_Flash_Tool_v5.1648_Win\chip.mapping.cfg.xml
[00000069] [22:35:08:766414] [Tid0x000000bc] [info] Chip hw code is intact.
[00000070] [22:35:08:767414] [Tid0x000000bc] [info] chip id: hw_code[0x335] hw_sub_code[0x8A00] hw_version[0xCB00] sw_version[0x0]
[00000071] [22:35:08:767414] [Tid0x000000bc] [debug] <--[C29] boot_rom::get_chip_id
[00000072] [22:35:08:767414] [Tid0x000000bc] [debug] <--[C28] boot_rom::device_control
[00000073] [22:35:08:768414] [Tid0x000000bc] [debug] <--[C27] connection::device_control
[00000074] [22:35:08:768414] [Tid0x000000bc] [info] <--[C26] flashtool_device_control
[00000075] [22:35:08:769415] [Tid0x000000bc] [debug] chip_id: hw_code 0x335, chip_evolution 0
[00000076] [22:35:08:769415] [Tid0x000000bc] [error] chip mismatch! scatter: MT6735P, device: MT0335

The device is powered by a MT6735P (a big thanks to scott for his thread https://www.hovatek.com/forum/thread-11610.html).
I got a FULL backup ans I'm only trying to write the system partition, nothing else.

So, anyone already experienced symptoms like that one ?

Kindly,
Codu.
This post was last modified: 08-02-2017, 03:50 PM by Codu. Edit Reason: text formatting
maxpayne
maxpayne
maxpayne
Contributor
2,873
08-02-2017, 11:35 AM
#2
(08-02-2017, 12:33 AM)Codu Hello,

I have a problem flashing this phone using the latest SP tool. Reading works like a charm, but writing is impossible. I believe there's configuration parameter that must be fixed but I cant figure out where.

Here's the log from the ProgramData, maybe one already has fix-up (the last line is the most important):

00000011] [22:35:08:714409] [Tid0x000000bc] [info] <--[C5] comm_engine::open
[00000012] [22:35:08:715409] [Tid0x000000bc] [debug] -->[C6] boot_rom:Confusedet_transfer_channel #./brom/boot_rom.cpp (line:37)
[00000013] [22:35:08:715409] [Tid0x000000bc] [debug] <--[C6] boot_rom:Confusedet_transfer_channel
[00000014] [22:35:08:715409] [Tid0x000000bc] [debug] -->[C7] boot_rom::connect #./brom/boot_rom.cpp (line:43)
[00000015] [22:35:08:716409] [Tid0x000000bc] [info] start handshake with device.
[00000016] [22:35:08:717409] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[a0 ]
[00000017] [22:35:08:734411] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[52 ]
[00000018] [22:35:08:734411] [Tid0x000000bc] [debug] <-Rx: 0x00000004 Hex[45 41 44 59 ]
[00000019] [22:35:08:735411] [Tid0x000000bc] [info] preloader exist. connect.
[00000020] [22:35:08:736411] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[a0 ]
[00000021] [22:35:08:736411] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[5f ]
[00000022] [22:35:08:737411] [Tid0x000000bc] [debug] send 0xA0. receive 0x5F
[00000023] [22:35:08:738411] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[0a ]
[00000024] [22:35:08:738411] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[f5 ]
[00000025] [22:35:08:739412] [Tid0x000000bc] [debug] send 0x0A. receive 0xF5
[00000026] [22:35:08:740412] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[50 ]
[00000027] [22:35:08:740412] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[af ]
[00000028] [22:35:08:741412] [Tid0x000000bc] [debug] send 0x50. receive 0xAF
[00000029] [22:35:08:742412] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[05 ]
[00000030] [22:35:08:742412] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fa ]
[00000031] [22:35:08:743412] [Tid0x000000bc] [debug] send 0x05. receive 0xFA
[00000032] [22:35:08:743412] [Tid0x000000bc] [debug] <--[C7] boot_rom::connect
[00000033] [22:35:08:744412] [Tid0x000000bc] [info] (2/2)security verify tool and DA.
[00000034] [22:35:08:744412] [Tid0x000000bc] [debug] -->[C19] boot_rom_logic:Confusedecurity_verify_connection #./brom/boot_rom_logic.cpp (line:38)
[00000035] [22:35:08:744412] [Tid0x000000bc] [debug] -->[C20] boot_rom::get_preloader_version #./brom/boot_rom.cpp (line:829)
[00000036] [22:35:08:746412] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fe ]
[00000037] [22:35:08:746412] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[01 ]
[00000038] [22:35:08:747412] [Tid0x000000bc] [info] preloader version: 0x1
[00000039] [22:35:08:747412] [Tid0x000000bc] [debug] <--[C20] boot_rom::get_preloader_version
[00000040] [22:35:08:747412] [Tid0x000000bc] [info] Preloader exist. skip connection verification.
[00000041] [22:35:08:748412] [Tid0x000000bc] [debug] <--[C19] boot_rom_logic:Confusedecurity_verify_connection
[00000042] [22:35:08:748412] [Tid0x000000bc] [debug] <--[C4] connection::connect_brom
[00000043] [22:35:08:748412] [Tid0x000000bc] [info] <--[C3] flashtool_connect_brom
[00000044] [22:35:08:749413] [Tid0x000000bc] [info] -->[C23] flashtool_device_control #./interface/flashtoolex_api.cpp (line:308)
[00000045] [22:35:08:749413] [Tid0x000000bc] [debug] -->[C24] connection::device_control #./logic/connection.cpp (line:585)
[00000046] [22:35:08:750413] [Tid0x000000bc] [info] device control: DEV_GET_CHIP_ID code[0x1]
[00000047] [22:35:08:750413] [Tid0x000000bc] [debug] -->[C25] boot_rom::device_control #./brom/boot_rom.cpp (line:661)
[00000048] [22:35:08:750413] [Tid0x000000bc] [debug] <--[C25] boot_rom::device_control
[00000049] [22:35:08:751413] [Tid0x000000bc] [debug] <--[C24] connection::device_control
[00000050] [22:35:08:751413] [Tid0x000000bc] [error] <ERR_CHECKPOINT>[820][error][0xc0010007]</ERR_CHECKPOINT>flashtool_device_control fail
[00000051] [22:35:08:752413] [Tid0x000000bc] [info] <--[C23] flashtool_device_control
[00000052] [22:35:08:752413] [Tid0x000000bc] [info] -->[C26] flashtool_device_control #./interface/flashtoolex_api.cpp (line:308)
[00000053] [22:35:08:753413] [Tid0x000000bc] [debug] -->[C27] connection::device_control #./logic/connection.cpp (line:585)
[00000054] [22:35:08:753413] [Tid0x000000bc] [info] device control: DEV_GET_CHIP_ID code[0x1]
[00000055] [22:35:08:753413] [Tid0x000000bc] [debug] -->[C28] boot_rom::device_control #./brom/boot_rom.cpp (line:661)
[00000056] [22:35:08:754413] [Tid0x000000bc] [debug] -->[C29] boot_rom::get_chip_id #./brom/boot_rom.cpp (line:109)
[00000057] [22:35:08:754413] [Tid0x000000bc] [info] get chip id
[00000058] [22:35:08:756413] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fd ]
[00000059] [22:35:08:756413] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fd ]
[00000060] [22:35:08:757413] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[03 35 ]
[00000061] [22:35:08:758413] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]
[00000062] [22:35:08:760414] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fc ]
[00000063] [22:35:08:760414] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fc ]
[00000064] [22:35:08:761414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[8a 00 ]
[00000065] [22:35:08:762414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[cb 00 ]
[00000066] [22:35:08:763414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]
[00000067] [22:35:08:764414] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]
[00000068] [22:35:08:765414] [Tid0x000000bc] [info] Read lib config file: C:\adb\SP_Flash_Tool_v5.1648_Win\chip.mapping.cfg.xml
[00000069] [22:35:08:766414] [Tid0x000000bc] [info] Chip hw code is intact.
[00000070] [22:35:08:767414] [Tid0x000000bc] [info] chip id: hw_code[0x335] hw_sub_code[0x8A00] hw_version[0xCB00] sw_version[0x0]
[00000071] [22:35:08:767414] [Tid0x000000bc] [debug] <--[C29] boot_rom::get_chip_id
[00000072] [22:35:08:767414] [Tid0x000000bc] [debug] <--[C28] boot_rom::device_control
[00000073] [22:35:08:768414] [Tid0x000000bc] [debug] <--[C27] connection::device_control
[00000074] [22:35:08:768414] [Tid0x000000bc] [info] <--[C26] flashtool_device_control
[00000075] [22:35:08:769415] [Tid0x000000bc] [debug] chip_id: hw_code 0x335, chip_evolution 0
*[00000076] [22:35:08:769415] [Tid0x000000bc] [error] chip mismatch! scatter: MT6735P, device: MT0335*

The device is powered by a MT6735P (a big thanks to scott for his thread https://www.hovatek.com/forum/thread-11610.html).
I got a FULL backup ans I'm only trying to write the system partition, nothing else.

So, anyone already experienced symptoms like that one ?

Kindly,
Codu.
What is the error message that SP flash tool pops up? a screenshot of it too

Sent from my Infinix X510 using the Hovatek Forum App
Codu
Codu
Codu
Junior Member
23
08-02-2017, 01:00 PM
#3
(08-02-2017, 11:35 AM)maxpayne What is the error message that SP flash tool pops up? a screenshot of it too

Sent from my Infinix X510 using the Hovatek Forum App

Thank you for the replying, I'm @ work, cant do it.

The message box (memory) is a standard MSDN Win32 MessageBox C++ API call with the lpText the message:
Code:

chip mismatch! \n
scatter: MT6735P \n
device: MT0335 \n
\n
[HINT]
and nothing more.

Kindly,
Alin.
maxpayne
maxpayne
maxpayne
Contributor
2,873
08-02-2017, 01:11 PM
#4
(08-02-2017, 01:00 PM)Codu Thank you for the replying, I'm @ work, cant do it.

The message box (memory) is a standard MSDN Win32 MessageBox C++ API call with the lpText the message:
Code:

chip mismatch! \n
scatter: MT6735P \n
device: MT0335 \n
\n
[HINT]
and nothing more.

Kindly,
Alin.

That's a mismatch error.
How was the scatter file created?

Sent from my Infinix X510 using the Hovatek Forum App
Codu
Codu
Codu
Junior Member
23
08-02-2017, 04:07 PM
#5



(08-02-2017, 01:11 PM)maxpayne That's a mismatch error.

Thank you, I'm aware. The big bad question is not what it is, but how can I "patch" SP to overcome this or what can be done to fix it / prevent it.

(08-02-2017, 01:11 PM)maxpayne How was the scatter file created?

Through MiracleBox, when I performed a FULL back-up.
As a side note MB is not very reliable because it returned a MT6735 chip type in the scatter file. The ZTE says it has a MT6735P, hence the fine tuning. of the scatter. Using the original scatter I was getting the INVALID_BB_CHIP_TYPE 1003 error.

As mentioned, this phone returns a 0x0335 instead of 0x6735 in the handshake.
The log of the get chip id is:
Code:

[00000058] [22:35:08:756413] [Tid0x000000bc] [debug] Tx->: 0x00000001 Hex[fd ]
[00000059] [22:35:08:756413] [Tid0x000000bc] [debug] <-Rx: 0x00000001 Hex[fd ]
[00000060] [22:35:08:757413] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[03 35 ]
[00000061] [22:35:08:758413] [Tid0x000000bc] [debug] <-Rx: 0x00000002 Hex[00 00 ]

How can I map this 0x335 to 6735 ?

I also declared a (fake) definition of a MT0335 in the SP's xml settings, changed the scatter accordingly, but it ends up in various errors Smile.

I'm kind of out of ideas...


Kindly,
hovatek
hovatek
hovatek
Administrator
49,570
08-02-2017, 08:10 PM
#6
(08-02-2017, 04:07 PM)Codu Through MiracleBox, when I performed a FULL back-up.
As a side note MB is not very reliable because it returned a MT6735 chip type in the scatter file. The ZTE says it has a MT6735P, hence the fine tuning. of the scatter. Using the original scatter I was getting the INVALID_BB_CHIP_TYPE 1003 error.
....
How can I map this 0x335 to 6735 ?

I also declared a (fake) definition of a MT0335 in the SP's xml settings, changed the scatter accordingly, but it ends up in various errors Smile.

I'm kind of out of ideas...


Kindly,

There are quite a number of issues to clarify in your post (e.g MT6735 vs Mt6735P) but I would like to focus on the most critical.
First off, I would advise you put a hold on tweaking stuff 'just to make this work' because you could end up corrupting the emmc when you 'finally get it to work'.

Now, Miracle Box isn't necessarily wrong to detect your phone as MT6735 (excluding the P). There are certain cases of generalization in scatter file names in which the difference lies not in the name of the scatter but the platform set in the scatter file. So Miracle box will backup and write to your phone correctly despite excluding the P.

Backing up

I presume you backed up using the technique @ https://www.hovatek.com/forum/thread-526.html . If you did readback successfully but are having Chip mismatch problems when writing then you need to look closer at your scatter file you're using

writing

From your post, you modified an existing scatter file. I would like you to attach the scatter file here for me to take a look at

* Note:

Using a scatter file created in Miracle Box (especially older versions) on SP flash tool (certain older versions) could give the mismatch error. This doesn't necessarily mean the MB scatter file is incorrect
This post was last modified: 08-02-2017, 08:13 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Codu
Codu
Codu
Junior Member
23
08-02-2017, 11:01 PM
#7
Thank you for replying.

(08-02-2017, 08:10 PM)hovatek There are quite a number of issues to clarify in your post (e.g MT6735 vs Mt6735P) but I would like to focus on the most critical.
First off, I would advise you put a hold on tweaking stuff 'just to make this work' because you could end up corrupting the emmc when you 'finally get it to work'.
To clarify, I dont change stuff randomly because I dont wanna end up with a fancy shoe stick Tongue. It was trick to bypass the chip-type check.

The phone is a stock ZTE Blade v7 Lite / MT6735P, is only seen as a MT6735.

(08-02-2017, 08:10 PM)hovatek Now, Miracle Box isn't necessarily wrong to detect your phone as MT6735 (excluding the P). There are certain cases of generalization in scatter file names in which the difference lies not in the name of the scatter but the platform set in the scatter file. So Miracle box will backup and write to your phone correctly despite excluding the P.

Totally agree, + MB is not bad, it only returns the wrong platform-type, hence the 'unreliable', but the returned flash chunks are consistent.

(08-02-2017, 08:10 PM)hovatek Backing up

I presume you backed up using the technique @ https://www.hovatek.com/forum/thread-526.html . If you did readback successfully but are having Chip mismatch problems when writing then you need to look closer at your scatter file you're using

Nope,I did this one: https://www.hovatek.com/forum/thread-13347.html
by checking all segments Smile, just in case.

(08-02-2017, 08:10 PM)hovatek writing

From your post, you modified an existing scatter file. I would like you to attach the scatter file here for me to take a look at

* Note:

Using a scatter file created in Miracle Box (especially older versions) on SP flash tool (certain older versions) could give the mismatch error. This doesn't necessarily mean the MB scatter file is incorrect

MB 2.27A made it this evening (I only ticked the system partition this time).

The old one has a P in the platform type (MT6735P)

Kindly,
Codu
Attached Files
.txt
scatter.txt
Size: 9.39 KB / Downloads: 22
hovatek
hovatek
hovatek
Administrator
49,570
09-02-2017, 11:02 AM
#8
(08-02-2017, 11:01 PM)Codu Thank you for replying....
MB 2.27A made it this evening (I only ticked the system partition this time).

The old one has a P in the platform type (MT6735P)

Kindly,
Codu

Now that we're on the same page, I know you're using a scatter file created by MB. This won't work directly on SP flash tool except in newer versions of MB or Infinity CM2 MTK.
You'll need to work with the scatter file created when all partitions were ticked then use the values to manually edit an MT6735P scatter file using the guide @ https://www.hovatek.com/forum/thread-12719.html
Thats one way to make it work in SP flash tool

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Codu
Codu
Codu
Junior Member
23
09-02-2017, 02:42 PM
#9
(09-02-2017, 11:02 AM)hovatek Now that we're on the same page, I know you're using a scatter file created by MB. This won't work directly on SP flash tool except in newer versions of MB or Infinity CM2 MTK.
You'll need to work with the scatter file created when all partitions were ticked then use the values to manually edit an MT6735P scatter file using the guide @ https://www.hovatek.com/forum/thread-12719.html
Thats one way to make it work in SP flash tool

Thank for the hint.

To put it one line, I should try a scatter file built by MTK Droid, all partitions ticked and change the platform accordingly.

Hm, I'll be very surprised if the result wont be the same...

I'll keep you posted.
Codu
Codu
Codu
Junior Member
23
09-02-2017, 09:39 PM
#10



(09-02-2017, 11:02 AM)hovatek Now that we're on the same page, I know you're using a scatter file created by MB. This won't work directly on SP flash tool except in newer versions of MB or Infinity CM2 MTK.
You'll need to work with the scatter file created when all partitions were ticked then use the values to manually edit an MT6735P scatter file using the guide @ https://www.hovatek.com/forum/thread-12719.html
Thats one way to make it work in SP flash tool

Please check the attached files.
Best guess, MTK tool doesn't like this phone either:
- in bootloader mode the application enters an infinite loop
- in normal mode read is ok, but it cant get flash the segments addreses/sizes

I just hope you're not gonna run out of ideas Smile.

Kindly,
Codu.
Attached Files
.jpg
Boot_Mode.jpg
Size: 90.04 KB / Downloads: 9
.jpg
NormalOperation_Mode.jpg
Size: 87.29 KB / Downloads: 7
Pages (4): 1 2 3 4 Next
Users browsing this thread:
 2 Guest(s)
Users browsing this thread:
 2 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram