I have a Huawei Y536A1 US version. I am attempting to port the Y536A1 Canada Rogers version as it appears to have no carrier apps within it. I installed Cygwin and dsixda' Android Kitchen but the optiuon to extract the system.img file (ext4) does not work. I found the post for installing perl, split_update, ext4 unpacker exe, and huawei finder. Following the steps, I can unpack the system.img and extract the build.prop file. However I am totally lost at how to either edit the Canadian build.prop or how to replace it with the US version. It is simple enough to replace any .img file within the output folder, but I can't figure out how to replace or edit files inside the .img files once they are unpacked into the EXT4 unpacker. Any help would be greatly appreciated. Also, if I am going about this incorrectly, any info on redirecting my efforts to be used with a different tool would also be appreciated.
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!
Hello,
I am having some serious trouble modifying a ROM. I download the entire ROM in the form of an .img, and thanks to a reRepacker am able to unpack the contents of the rom, each part into individual .img files. I then use file ext4 explorer to open system.img, then save as an ext4. I then use ext2 explorer to open the now ext4 system.img, and I save the contents in a file folder within the unpacked folder. I make all of the edits I need, and then use WinRar to "add to archive' the file folder as an .img. Note that it compresses the size of the file bu about 40%. I then throw the dump folder into the repacker and out spits the new "modified" rom ready to be flashed to the device. I then use the batch tool to "flash" the compute stick. Flash being a relative term because it does not get past the boot image. EVEN IF I EDIT NOTHING and just convert to ext4 to ext2 and then to .img it still won't boot. Maybe this is because I am going from an ext2 to an image? When the file is supposed to be ext4? I'm not quite sure, hence why I ask here. Anyone have any ideas?
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 Dears,
I have extracted the partitions from an LG K10 using the method posted here.
Now I got all mmcblk0 partition in bin files format but I can manage how to mount this files or extract the data.
I tried from windows and from linux but no luck.
If I inspect the bin file in linux with an Hex editor I see a lot of data inside but inspecting the same file in windows only 0´s show.
Can someone help me in this ?
Tks.
Before I would appreciate your help
The tools that I could find here in the forum have helped me to extract the firmware files and later extract the files from the system.img and vendor.img from Android 10 down, which I have and thanking them for their great work.
I have downloaded a firmware but it is from the Android 11 version when unzipping it I find the system.img, system_ext.img, vendor.img and vendor_boot.img then when I run the tool to extract the files from the img files it gives me Error the tools from what I see only support the version of Androd 10 so I cannot extract the files
Someone from here has been able to extract the files from these img of android 11 and if so, where can I download the tool to be able to do it from windows thanks for the attention
I have been looking for tools for windows that allow me to extract the files from the file system.img vendor.img and vendor_boot.img since they are android 11 firmware, so someone who can help me how to extract the files, I have android 10 firmware and I can extract the files without any problem