[Please help] SP Flash Tool on BLADE V7 Lite B06
[Please help] SP Flash Tool on BLADE V7 Lite B06
(16-02-2017, 11:36 AM)hovatek If that was the case then Miracle Box shouldn't have been able to identify it as MT6735(P) , read and write correctly to the phone.
I think the problem is from the scatter file or download agent we're using in SP flash tool
(17-02-2017, 09:09 PM)Codu The scatter just provides the info about how stuff is stuffed in the device defined inside.
In this case, the CPUs are all from the same Arm branch:
MT6735 is the fast,
MT6735M is the Medium
MT6735P is the Poor .
Same architecture and I/O = same software runs on the 3, out of the box only at different speeds, and thus, the DA should initialize the 3 of them in the same way, theoretically. In practice, you already saw it doesn't work.
I'll log & compare the handshakes from both softwares (MB vs SPFT) see if they match.
For me, the problem lies in the handshake because I cant see SPFT sending the DA to the phone (see the log in my first post).
Do you have a better idea/approach ?
Kindly,
(18-02-2017, 03:55 PM)hovatek I expect the SP flash tool log to reveal attempts to write to the phone as MT0335Please see log1.zip .
Would like to see the logs anyway
(18-02-2017, 03:55 PM)hovatek On the side, what if we changed all MT6735P in the SP flash tool scatter file to MT0335 to see what SP flash tool would popup
---------------------------
Smart Phone Flash Tool
---------------------------
Platform MT0355 not support on this version.
Please update to latest flashtool and try again.
---------------------------
&OK &Help
---------------------------
<platform name="MT0335_S00"
simple_name="MT0335"
owner_name="Shuai.Zhang"
dl_auto_detect_battery="true"
nand_util_support="false"
image_lock_support="false"
usb_highspeed_support="true"
logical_addr_support="true"
alert_no_com_port="false"
auto_format_support="true"
default_bmt_blocks="80"
firmware_upgrade_enable="true"
default_da_dl_all_hs="true"
is_default_set_format_length="true"
auto_format_all_support = "true"
is_auto_polling_enable="false"
auto_polling_upper_limit="2"
reset_key_configuration ="PH"
/>
<platform name ="MT0335">
<nor type-name = "NOR" is-support = "false" is-support-auto-format = "false" hw-storage-type = "HW_STORAGE_NOR" mem-storage-type = "HW_MEM_NOR" storage-addressing-type = "8"></nor>
<nand type-name = "NAND" is-support = "true" is-support-auto-format = "true" hw-storage-type = "HW_STORAGE_NAND" mem-storage-type = "HW_MEM_NAND" storage-addressing-type = "8"></nand>
<emmc type-name = "EMMC" is-support = "true" is-support-auto-format = "true" hw-storage-type = "HW_STORAGE_EMMC" mem-storage-type = "HW_MEM_EMMC" storage-addressing-type = "16"></emmc>
<sdmmc type-name = "SDMMC" is-support = "true" is-support-auto-format = "false" hw-storage-type = "HW_STORAGE_SDMMC" mem-storage-type = "HW_MEM_SDMMC" storage-addressing-type = "8"></sdmmc>
</platform>
<0x335>0x6735</0x335>
(20-02-2017, 09:17 PM)Codu .....
In this case, the DA is sent to the phone.
And, with the correct type in the scatter (to avoid the error) I got the results in log3.zip.
/!\WARNING:
The ordinal user (or inexperienced engineer) should NOT try this, never ever. This can and will screw up the phone so rapidly, so easily and so hard you won't know what hit you.
Kindly,
(21-02-2017, 12:14 PM)hovatek From the logs, this isn't happening in SP flash tool with what we have ATM.Maybe you are right.
(21-02-2017, 12:14 PM)hovatek I'm currently searching for any scatter ROM for BLADE V7 Lite,Yes, it's like mine, but the guys end up saying the phone is weird .
Came across this thread @ http://4pda.ru/forum/lofiversion/index.p...5-100.html but having trouble translating. Is that close to your device because I see a scatter file and recovery. Maybe the scatter could point us right
(21-02-2017, 12:14 PM)hovatek Another thing
With reference to your post @ https://www.hovatek.com/forum/thread-170...l#pid98645 , did you mean that the Miracle Box scatter file (obtained from full dump) also gave that BB Chip no match error?
(21-02-2017, 05:47 PM)Codu MiracleBox does:
- report the phone as a MT6735
- read & write the flash accordingly
- not report any error during any of the mentioned processing
Kindly,
(22-02-2017, 09:56 AM)hovatek I agree that the phone is weird.If the phone was right, I would have figure out by myself and didn't bothered you guys in the first place.
(22-02-2017, 09:56 AM)hovatek What I'm asking here is when you tried using the Miracle Box scatter file on SP flash tool (without modifying), did it also give the BB Chip Not Match?Yes, it did.
(22-02-2017, 11:07 AM)Codu Yes, it did.
Like I said, I'm kinda familiar with electronics and with enough time and practice, one develops some sort of 6th sense for sht...
Getting back to my 15th post, where the purpose would be to force SPFT to treat the device as a MT6735 even if the chip reports itself as MT0335.
Do you think it's doable or a good/bad idea?
Do you think SPFT may have a "let me flash this phone, disregarding the chip_id_type" mode ?
Kindly,
(10-10-2019, 10:19 AM)vvaaavv Faced this problem 0x335. I tried many versions of SPFT. The problem was solved by parsing the device and viewing the inscription on the processor. CPU MT6737V.Thank you for sharing the information.
The output of such MT0335 (0x335) is MT6737M.