Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
rhodesbauer said:
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
Click to expand...
Click to collapse
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
qwertyu123 said:
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
Click to expand...
Click to collapse
I used Root Explorer to look for both, recovery.img and *.img.
No result.
try this http://forum.xda-developers.com/showthread.php?t=2450045
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
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
Anyone can help me find the KDz for the LG K9, Canadian variant lmx210wm? Bricked it trying to crossbreed firmwares, and now need the original lmx210wm firmware so I can build a working qfil folder.. Any help would be greatly appreciated
****After an extensive search, i came up empty handed in finding firmware for lm-x210wm. the site exists on the LG website, but the firmware isn't downloadable. i would contact LG ... there were some other models listed, but i'm not sure if they're compatible with your system.
no luck in finding anything on 3rd party sites either, sorry****
I used the lg firmware exttaction.tool. lg-firmware-extract-tool ... Not able to post the link bcz of site restrictions.
If available, it should offer the kdz file, a way to extract the dz file and finally the bin files. Merging the system files yields a system.img file.
I didn't have luck w magisk and this file and don't know a way to convert just the boot.bin file to img.
**EDIT: renaming the boot.bin file to boot.img & then using the platform-tools and using the command
fastboot flash:raw boot boot.img (Finanly got my system rooted. supposedly the same method works w/ twrp, but that didn't throw an error and frankly i'm sick of working on this phone ... day 3.) ****
Twrp isn't compatible w my sys and no one click root methods work.
As your model is close to mine, lmx210cm ... I imagine you're going to have the same luck. No custom recovery and just a root.
****EDIT: Good luck and send me a pm if ya can figure out a way to convert bin to img. Hopefully, you will have better luck w the system.img. RESOLVED****
If there are multiple versions, start off w the ver closest to your security update. My info was in about/software.
jonathan dockery said:
****After an extensive search, i came up empty handed in finding firmware for lm-x210wm. the site exists on the LG website, but the firmware isn't downloadable. i would contact LG ... there were some other models listed, but i'm not sure if they're compatible with your system.
no luck in finding anything on 3rd party sites either, sorry****
I used the lg firmware exttaction.tool. lg-firmware-extract-tool ... Not able to post the link bcz of site restrictions.
If available, it should offer the kdz file, a way to extract the dz file and finally the bin files. Merging the system files yields a system.img file.
I didn't have luck w magisk and this file and don't know a way to convert just the boot.bin file to img.
**EDIT: renaming the boot.bin file to boot.img & then using the platform-tools and using the command
fastboot flash:raw boot boot.img (Finanly got my system rooted. supposedly the same method works w/ twrp, but that didn't throw an error and frankly i'm sick of working on this phone ... day 3.) ****
Twrp isn't compatible w my sys and no one click root methods work.
As your model is close to mine, lmx210cm ... I imagine you're going to have the same luck. No custom recovery and just a root.
****EDIT: Good luck and send me a pm if ya can figure out a way to convert bin to img. Hopefully, you will have better luck w the system.img. RESOLVED****
If there are multiple versions, start off w the ver closest to your security update. My info was in about/software.
Click to expand...
Click to collapse
Thank you very much sir. Appreciate all your effort. I'm close now I just have to finish editing the raw program XML file and start trying all these fire hose versions. I'm still not even sure if it's an 8909 or 8917. (
Hey everyone,
Since the v40 firehouse is available and it works with the g7 by flashing the abl bootloader, I'm trying to create a rawprogram0.xml and I seem to can't get it to create one. I tried putting it in the GPTAnalyzer python program and it shoots out zeros on guid or anything uses a numerical value. I've tried different firmwares same result. I've seen a raw program file around here but that one, im not sure how the guy even managed to create it. He was on last a year ago and pretty sure he won't be coming back anytime soon to message him
Anywho If you wanna try creating the rawprogram0.xml and feel brave enough to brick your device and try it, you can find the file in this thread thanks to @Xsavi for leaking it to us https://forum.xda-developers.com/lg...k-lg-v40-via-9008-root-t-mobile-t4042207/amp/
i have rawprogram0.xml from my G710N, but i am not able to try it though because it still needs a firehose file, and i dont have that.