Hello,
I am trying to create backup of my Lenovo P70 using MtkDroidTools. I cannot create scatter file because when I click Block Map, "Create Scatter File" is grayed out. Please help me as I'm in urgent need of it.
Best Regards
sherazi21st said:
I am trying to create backup of my Lenovo P70 using MtkDroidTools. I cannot create scatter file because when I click Block Map, "Create Scatter File" is grayed out.
Click to expand...
Click to collapse
Do you see all the partitions listed (like recovery, boot, system) after clicking 'Block Map'?
If no, then it means phone is not connected properly.
Sometimes, you have to install drivers like Android CDC Gadget driver, Android VCOM drivers for it to work
GokulNC said:
Do you see all the partitions listed (like recovery, boot, system) after clicking 'Block Map'?
If no, then it means phone is not connected properly.
Sometimes, you have to install drivers like Android CDC Gadget driver, Android VCOM drivers for it to work
Click to expand...
Click to collapse
I See all partitions but their mount point is not there plus create scatter file is grayed out.
sherazi21st said:
I See all partitions but their mount point is not there plus create scatter file is grayed out.
Click to expand...
Click to collapse
Hi,
Same problem with another MT6753 device. Please, can you help for create the scatter file?
sherazi21st said:
I See all partitions but their mount point is not there plus create scatter file is grayed out.
Click to expand...
Click to collapse
manos78 said:
Same problem with another MT6753 device. Please, can you help for create the scatter file?
Click to expand...
Click to collapse
These MTK chips have 64-bit processors..
As of now, the MTK Droid Tools software isn't updated to support these new 64 bit chipsets.
You can try to manually create a scatter file, or check the phone manufacturer's website for complete firmware with a specific tool or XDA Firmware. (That might include a scatter file; IDK)
If you don't find any, better wait till a proper tutorial / update comes.
I think there'll be some solution to this in the Chinese forums..
The Chinese Smart phone companies are highly dependent on the cheap Mediatek chipsets..
So, you can try looking there if you have patience and use Google Translate with Chrome.
manos78 said:
Hi,
Same problem with another MT6753 device. Please, can you help for create the scatter file?
Click to expand...
Click to collapse
Which phone are you using? I've scatter of my phone and I'm able to flash using sp flash tools. If you're using a Lenovo phone then you'll find scatter and flash tool which will do your job.
sherazi21st said:
Which phone are you using? I've scatter of my phone and I'm able to flash using sp flash tools. If you're using a Lenovo phone then you'll find scatter and flash tool which will do your job.
Click to expand...
Click to collapse
Wiko Fever, see: http://forum.xda-developers.com/android/development/root-wiko-fever-t3242640/
GokulNC said:
These MTK chips have 64-bit processors..
As of now, the MTK Droid Tools software isn't updated to support these new 64 bit chipsets.
You can try to manually create a scatter file, or check the phone manufacturer's website for complete firmware with a specific tool
If you don't find any, better wait till a proper tutorial / update comes.
Click to expand...
Click to collapse
I'm doing the initial research/development. No firmware from manufacturer at time. I'm doing all with one unit of the device. I'm creating the scatter file manually using a ROM dump. My problem at time is that my dump isn't a full 16GB dump, only 1.5GB. :crying:
manos78 said:
Wiko Fever, see: http://forum.xda-developers.com/android/development/root-wiko-fever-t3242640/
Click to expand...
Click to collapse
Sorry, don't know about this phone. I've Lenovo and there's a Russian forum which covers almost all Lenovo phones.
Hi,
In the e3 recovery menu is an option for show the bootlog, inside it you can show the PARTION mapping of the device... with all info: partition name, start address, size... you can create the scatter file by hand with this info.
Hello everyone I bring a way to fix this famous error:
"Brom error: s_not_enough_storage_space (1011)" leaves us
when trying to flash flash tools our terminals.
I have concluded that it was something that was wrong with my scatter partitions for example.
So I started to open my scatter and take a look with this tool scatter analyzer and compare it to other scatter another rom
and saw a difference in space.
What I did was open the original scatter with notepad ++ and locate where in the section USR_DATA and partition_size
you resize by one less than it had copied the other scatter, after you tried it in flash tools and this was the result.
I think it will work for any mtk65xx
I hope you serve
A greeting.
Brilliant!! Thanks man!!
I couldn't quite catch what you mean. Can you please make it more precise? A step-by-step guide would be much appreciated.
Can you please upload the scatter file,i have exact same phone and model. MT6572 X410
Im having this issue:
https://i.gyazo.com/ec3606a18990a905a2993b2d72a8d758.png
Only i cant seem to get it to work.
My Rom is Budget X410
Can someone please help me fix my scatter file if this is the issue,or perhaps help me fix this phone another way if it is because of something else. Tried changing the Partition size like the guide suggests on the other thread,but it results in error.
Phone is totally bricked,no recovery menu or access to adb/fastboot. Only way i can fix it is with Sp Flash Tool.
hi there i have to flash tecno k9 now.
i see the same mistake.
In scatter i have the following:
https://ibb.co/yBQsM6r
thanks
edit
Here are 2 scatters:
https://ibb.co/W2t1ZDD
https://ibb.co/59XPnQS
?!
Nobody ?
use miracle box (MOD EDIT: Removed) tool, it does not use scatter details to write firmware
Hi
It has been almost a month that I have been reading and trying different approaches. A frustrating but hugely learning experience. Am so grateful to all the contributors @ xda-developers. _This is a treasure trove of info for newbies like me.
My challenge - A LYF Wind 4 phone ( basically a Haier L 51 ) which I hard bricked. Have managed to dump all the mmcblk partitions as .img files from a similar but functional phone, I had managed to access.
Created a rawprogram0.xml which seems to have worked because I could download to the bricked phone using QFIL. However the phone remains bricked.
Tried single image download using emmcdl and QSaharaServer but not much luck.
Even managed to get a backupemmcfirmware.bin from the similar phone using EFS Pro but not much success.
Realise that I cant use the .img format for sbl1, aboot,tz etc. Tried using tools to convert to .mbn (the required format) but obviously am making mistakes.)
Is there a simple tool to convert .img to .mbn ( Tools like ImgExtractor.exe keep crashing., even with the -conv option) Not sure if ext2simg will give me the .mbn file.
cant switch to DLOAD using emmcswdownload of the QPST tools. Get a msg saying that the phone is not in diagnostic mode. Nor can I restore the qcn file for NV
Cant figure out why after a successful download using prog_emmc_firehose_8909.mbn as the programmer in QFIL , the phone still remains bricked. Yes the phone is based on the Snapdragon 210 SoC.
Have been unsuccesful in creating the right partition_boot.xml to be able to create msimage.mbn and there is no way I can get the MPRG8909.hex. my newbie attempts at using python werent of any use. Even tried dabbling with Linux commands using Ubuntu, but my lack of knowledge in using Linux , slows me down tremendously.
Will be grateful for any pointers to resolve this brick.
T
Did you already get to unbrick your phone?
I want to build a singleimage file for XT1069 and I'm searching for a file called singleimage.py.
rfsanet said:
Did you already get to unbrick your phone?
I want to build a singleimage file for XT1069 and I'm searching for a file called singleimage.py.
Click to expand...
Click to collapse
I've found it
I want to make a full copy of a MTK6580 smartwatch firmware before make changes on it, but MTK droid tools I used before with other MTK devices can´t detect this... please, I need a starting point on how to do it with this device...
Thanks
A starting point:
SP FlashTool, a scatter file of similar device and cat /proc/parti*
Then change the starting addresses and sizes to match yours.
CXZa said:
A starting point:
SP FlashTool, a scatter file of similar device and cat /proc/parti*
Then change the starting addresses and sizes to match yours.
Click to expand...
Click to collapse
THANKS. I am not sure if I can access to /proc/ folder, from the device or the PC, or if partitions will list all addresses, but I wil try. I have scatter (and firmware ) of the same device (other brand, but same hardware) but I don´t know if same hardware with different firmware could have different partition addresses., so I didn´t use it to save my actual firm.
Thanks again this is a good starting point. :good::good:
Worked, I´ve got the /proc/par* addresses. I will try to do the backup now. THANKS
So, some of you may have seen my work from the Android TV Platform, as i have done with AMLogic based devices im in the process of doing the same for MTK based devices, im making a full functional tool to disassemble and reassemble MTK firmware, suprisingly the firmware structure is very similar.
If anyone is interested in learning more about MTK firmware i made a video on manually splitting MTK dumped firmware HERE, so check it out, like and subscribe to my channel for more content!
What i have done
- Made a program to split an MTK firmware dump
- Split the ramdisk header to allow unpacking
- Unpack the kernel/recovery
- Unpack system
- Unpack cache
What i need help with?
i need the following info
- How to make an MTK scatter file manually
- How to repack the system with the proper partition length
- How to unpack logo.bin manually
- How to dump a firmware manually over USB without SP flash tool
Ive done some research already and dug in abit myself with no success, if needed i can provide code, binaries ive built etc to help with this
Ricky Divjakovski said:
So, some of you may have seen my work from the Android TV Platform, as i have done with AMLogic based devices im in the process of doing the same for MTK based devices, im making a full functional tool to disassemble and reassemble MTK firmware, suprisingly the firmware structure is very similar.
What i have done
- Made a program to split an MTK firmware dump
- Split the ramdisk header to allow unpacking
- Unpack the kernel/recovery
- Unpack system
- Unpack cache
What i need help with?
i need the following info
- How to make an MTK scatter file manually
- How to repack the system with the proper partition length
- How to unpack logo.bin manually
- How to dump a firmware manually over USB without SP flash tool
Ive done some research already and dug in abit myself with no success, if needed i can provide code, binaries ive built etc to help with this
Click to expand...
Click to collapse
Hey mate,
Ive gota fair bit of experience with Mediatek,
Scatters can be manually created using notepad +
All you have to do is lay them out correctly, i can upload a few in a zip if youd like ive got variations of scatters from
MT6572 nand & emmc 4 - 5 diff models
MT6737M emmc from 2 models
With taking a backup also i use NCK_MTK_Dongle theres a cracked version aswell that works takes all partitions and backs them up into singular .file format files which depending on the fs layout are as follows
Preloader
Uboot
Bootimg
Recovery
Secro
Logo
Tee1
Tee2
Simlock
Frp
Scatter_File.txt
Just for some examples,
I use mtk extractor to take the boot/recovery/system.imgs apart and repack but its only compatible with ext4 format, can also compile an ext4 system.img from scratch using it aswell, specifically though i use it for the boot and recoveries as its specifically designed to handle the MTK headers, also has a nice pull layout that consists of the kernel as a whole, ramdisk as a whole, boot.img boot_old.img, bootinfo.txt and then initrd folder containing the entire layout of the boot or recovery with init files and fstab etc but ive also noticed it will unpack and repack Qualcomm, SPD & samsung boot.imgs no problem also,
Unpacking your logo.bin also can be done with the program LogoBuilder lastest version that was released is 1.6 you can decompile the logo.bin edit the pictures etc then use the program to recompile it back into a logo.bin
Hope that helps you out a bit
Matty1993 said:
Hey mate,
Ive gota fair bit of experience with Mediatek,
Scatters can be manually created using notepad +
All you have to do is lay them out correctly, i can upload a few in a zip if youd like ive got variations of scatters from
MT6572 nand & emmc 4 - 5 diff models
MT6737M emmc from 2 models
With taking a backup also i use NCK_MTK_Dongle theres a cracked version aswell that works takes all partitions and backs them up into singular .file format files which depending on the fs layout are as follows
Preloader
Uboot
Bootimg
Recovery
Secro
Logo
Tee1
Tee2
Simlock
Frp
Scatter_File.txt
Just for some examples,
I use mtk extractor to take the boot/recovery/system.imgs apart and repack but its only compatible with ext4 format, can also compile an ext4 system.img from scratch using it aswell, specifically though i use it for the boot and recoveries as its specifically designed to handle the MTK headers, also has a nice pull layout that consists of the kernel as a whole, ramdisk as a whole, boot.img boot_old.img, bootinfo.txt and then initrd folder containing the entire layout of the boot or recovery with init files and fstab etc but ive also noticed it will unpack and repack Qualcomm, SPD & samsung boot.imgs no problem also,
Unpacking your logo.bin also can be done with the program LogoBuilder lastest version that was released is 1.6 you can decompile the logo.bin edit the pictures etc then use the program to recompile it back into a logo.bin
Hope that helps you out a bit
Click to expand...
Click to collapse
This info is somewhat useful, however im looking more towards a way of making a scatter file from a dumped firmware from a device, i see /proc/dumchar_info has some decent info, however some info i have no idea how its obtained
would you still be able to upload the scatter files for comparison?
As for the backup, what i wanna do is similar to what SP flash tool does, read from one memory address to another, i dont wanna use 3rd party tools either, i prefer to code them myself
I can unpack all that, and i can also repack the kernel, but the system im not sure how the size is defined, i may just recursively loop until a system.img larger than 2mb is created
Unfortunately that tool doesnt work with my logo.bin, ive tried but its pretty much a distorted image, and id like to code this myself aswell
Thank you for the info, if you can please upload those scatter files and ill keep you posted on the progress
Ricky Divjakovski said:
This info is somewhat useful, however im looking more towards a way of making a scatter file from a dumped firmware from a device, i see /proc/dumchar_info has some decent info, however some info i have no idea how its obtained
would you still be able to upload the scatter files for comparison?
As for the backup, what i wanna do is similar to what SP flash tool does, read from one memory address to another, i dont wanna use 3rd party tools either, i prefer to code them myself
I can unpack all that, and i can also repack the kernel, but the system im not sure how the size is defined, i may just recursively loop until a system.img larger than 2mb is created
Unfortunately that tool doesnt work with my logo.bin, ive tried but its pretty much a distorted image, and id like to code this myself aswell
Thank you for the info, if you can please upload those scatter files and ill keep you posted on the progress
Click to expand...
Click to collapse
Hey mate sorry for late reply im on aus time
Ahh i see what you mean now, im not to sure on how the system is defined to be honest mediatek is some what uniqe to say the least to me compared to everything else ive worked on before, ive noticed that aswell with fuzzy images in logobuilder inparticular on MT6979 the scatter though also had a very strange layout,
Speaking of which ive zipped up a few diff ones for you to use as reference, youll see some of the ways they are layed out is very different to one another as you will see defined within them,
https://drive.google.com/file/d/189H5EXS0ZqNuqn75A7ZNEOLo-Efq0T_h/view?usp=drivesdk
Ill be keen to try your tool once done aswell, are you going GUI based or Terminal command line based with it
Matty1993 said:
Hey mate sorry for late reply im on aus time
Ahh i see what you mean now, im not to sure on how the system is defined to be honest mediatek is some what uniqe to say the least to me compared to everything else ive worked on before, ive noticed that aswell with fuzzy images in logobuilder inparticular on MT6979 the scatter though also had a very strange layout,
Speaking of which ive zipped up a few diff ones for you to use as reference, youll see some of the ways they are layed out is very different to one another as you will see defined within them,
https://drive.google.com/file/d/189H5EXS0ZqNuqn75A7ZNEOLo-Efq0T_h/view?usp=drivesdk
Ill be keen to try your tool once done aswell, are you going GUI based or Terminal command line based with it
Click to expand...
Click to collapse
ah, im in aus time aswell
ill get this together one way or another, might just take a little time
it will be GUI based
Thanks for the upload!
Ricky Divjakovski said:
ah, im in aus time aswell
ill get this together one way or another, might just take a little time
it will be GUI based
Thanks for the upload!
Click to expand...
Click to collapse
All mate good to see another aussie on here
All sweet for things to work it takes time to figure out how they work first before anything is even built then debugged, completely understand im just happy to see some more MTK support happening as most of my tools are 4-5 years old for mtk so i think its great
Ill be waiting patiently cheers
Matty1993 said:
All mate good to see another aussie on here
All sweet for things to work it takes time to figure out how they work first before anything is even built then debugged, completely understand im just happy to see some more MTK support happening as most of my tools are 4-5 years old for mtk so i think its great
Ill be waiting patiently cheers
Click to expand...
Click to collapse
as i was saying most of the unpacking is done, the firmware structure is very similar to AMLogics(split the file from the start address to the file size in bytes), its pretty much just those few things i need, then repacking and i can dig into the GUI, id like to know more about how MTK droid tools creates a scatter file via ADB, it seems it uses some info from /proc/dumchar_info but that doesnt specify much, maybe the parameters are guessed???
ive attached a picture of my basic attempt to programatically create a scatter file, the highlighted lines are lines i dont know where this information comes from, nor do i know if those lines are the same for every MTK device
Ricky Divjakovski said:
as i was saying most of the unpacking is done, the firmware structure is very similar to AMLogics(split the file from the start address to the file size in bytes), its pretty much just those few things i need, then repacking and i can dig into the GUI, id like to know more about how MTK droid tools creates a scatter file via ADB, it seems it uses some info from /proc/dumchar_info but that doesnt specify much, maybe the parameters are guessed???
ive attached a picture of my basic attempt to programatically create a scatter file, the highlighted lines are lines i dont know where this information comes from, nor do i know if those lines are the same for every MTK device
Click to expand...
Click to collapse
I think mtk droid tools also pulls info from
cat proc/mounts & cat proc/partitions
Aswell as cat proc/dumchar_info as ive noticed some mtk devices even MT6737M dont have dumchar_info available if that helps a bit, some mtk structures slightly can differ also in certain areas, will your tool support UBIFS also ? Forgot to ask been trying to find a tool to dissasemble ubifs
Matty1993 said:
I think mtk droid tools also pulls info from
cat proc/mounts & cat proc/partitions
Aswell as cat proc/dumchar_info as ive noticed some mtk devices even MT6737M dont have dumchar_info available if that helps a bit, some mtk structures slightly can differ also in certain areas, will your tool support UBIFS also ? Forgot to ask been trying to find a tool to dissasemble ubifs
Click to expand...
Click to collapse
over time i can only hope the MTK community is like the amlogic community and have people send me devices for testing purposed, with AMLogic it was easy to obtain the info i needed because it resided in the firmware itself, i do however think this may be able to be done because mtk droid tools includes a feature where its able to split the firmware and create a scatter
As for ubifs, link me to the firmware and ill see what i can do, i should be able to do this
I just updated the thread with more information on how to manually split MTK dumped firmware, i will add more when i get around to it
Just an update, tools are coming along good, ive made substantial progress and upacking is done, generating the scatter file is coming together, repacking is almost done aswell, should have a release in about a week
Unpack/Repack Logo.bin https://forum.xda-developers.com/showthread.php?t=1953726
Any advancement with this?
good morning my friends I dedicate myself mainly to hardware I have some phones with dead emmc I want to change it the question the question have you worked with the preloader? For example I have the mt6592 and I want to mount the emmc (emcp) KMRX1000BM-B614 with 3gb of ram and 32gb of rom EMMC NAME: RX1BMB and it is CSD rev: 1.8 (MMC 5.1) it cannot be changed in name, who could edit the preloader.bin