I read somewhere that Google has changed the system used for the standard update zip file.
Therefore you have to convert some .dat files to .img files and .img files to a standard readable folder.
This I understand, however how do I reverse the process above to get back to the .dat file and get a lolipop compatible flashable zip?
Related
Hi,
The company Ainol release their latest updates as img files which we than have to flash using a program called livesuit. Does anyone know the process (or have any tips) on converting these img files to clockworkmod zip files?
I can extract the system and kernel files using something similar to this tutorial: http://www.techknow.t0xic.nl/forum/index.php?topic=1679.0
That tutorial explains how to modify the img file and then repack as img. I tried moving the system directory and the kernel & ramdisk over into a clockworkmod zip that i know works and overwrote the files in that with the one i had extracted.
when i try to install it, i get the e: cant open cwmzip.zip
(bad)
any ideas? Maybe i need to get the updater binary from the extracted files somehow?
Trugglepunts said:
Hi,
The company Ainol release their latest updates as img files which we than have to flash using a program called livesuit. Does anyone know the process (or have any tips) on converting these img files to clockworkmod zip files?
I can extract the system and kernel files using something similar to this tutorial: http://www.techknow.t0xic.nl/forum/index.php?topic=1679.0
That tutorial explains how to modify the img file and then repack as img. I tried moving the system directory and the kernel & ramdisk over into a clockworkmod zip that i know works and overwrote the files in that with the one i had extracted.
when i try to install it, i get the e: cant open cwmzip.zip
(bad)
any ideas? Maybe i need to get the updater binary from the extracted files somehow?
Click to expand...
Click to collapse
It really all depends, how many images? What are the images called? What are in each of the images if there is more then one?
thanks for replying, i think i have it right. I ran a log and saw that there was an invalid filename in my zip and sure enough, i looked in the app folder and saw a file with a lot of chinese characters. Deleting this file has sorted this problem
Thanks for replying anyways!
So, my phone recently got soft bricked....
I had the tar file of the XXELK4 leaked firmware and i extracted it, unpacked system.img.
Mounted it as ext4 and extracted the contents.
I want to make a flashable zip file from the system.img contents.
I made a folder called system. In which all app, bin, etc and other folders are.
Then i copied over the boot.img from the tar file...
Now, i need the meta-inf. I tried using some meta-inf from other roms, and removing the aroma functions from them.
Then trying to flash..
I get only a bootloop.
So, could someone provide a clean Meta-inf consisting of only the updater-script and update-binary??
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
Hi,
I build aosp for my Xperia X, the output are 3 .img files, system.img, boot.img, userdata.img.
So I wanted to ask if it's possible to create a flashable zip for those .img files instead of flashing them using fastboot.
If yes, what should the folder structure look like?
Also could I use a META-INF folder from an other rom? (omnirom for example)
Greetings.
hello, i used WindowsLGFirmwareExtractor to extract a kdz file to a dz file. then i merged into a system.img file. then opened that file in ext2explore. there is an app folder with all the apps in it. what i would like to know is first, can i delete the apps i dont want, and second, re-create a kdz file and flash that. and how do i make a new file to flash? would i delete the whole folder, or just the apk inside the folder?