Hello!
So, I have a Android Box MXQ 4K and I'm trying to create an update.zip from the latest update (wich I only found in .IMG format).
I know the box can do a update from a update.zip file. So I extracted the files from the IMG, extracted the system.img, and created the update.zip file using instructions that I found here in the forum. But it gave me an error that wasn't a valid package (yes, I signed it). I didn't tried to aply the update.zip direct from the Recovery Menu, because if I stay too much time (30s+) on the recovery menu, it gives me a Green Screen. What are my options?
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!
Hi,
I´m getting software install failed! on my Huawei wile doing an OTA ROM update.
It is an intermediate update so update.app does not have system.img, but rather the update.zip has folders with a patch for the /System.
As of that, I wanted to know what's wrong, so, is there any log file created from the update procedure?
G Play Mini - CHC-U01 Update to V100R001C434B120
OTA URL:
http://update.hicloud.com/TDS/data/files/p3/s15/G854/g104/v29161/f1/full/update.zip
Inside update.zip is update.app (and the folders to patch the /system) which in turn compacts another update.app inside.
So, either "open inside" update.app or extract update.app from update.zip, rename that update.app to update.zip and open the last update.zip to get the update.app that can be opened with HuaweiUpdateExtractor to get the *.img files (exept system.img).
Since I can´t adb in recovery I can´t do a logcat.
Can anyone help me debug the OTA update?
Build Number
This is getting more like a diary...
I found the log file in ./splash2/recovery.log
Now, where is the system getting the information of the build number other than from build.prop, because the info on the "about" menu is different form what is in ro.build.display.id or any other variable on the file.
I'll appreciate any help!
I found that the variable is stored in ./cust/hw/eu/prop/local.prop (on my case the path "eu" is because my CustCVersion is European, on Russian should be .../ru/prop/local.prop").
Unfortunately I didn´t know that CWM doesn´t include cust.img on nandroid backups, so i don´t have the original ./cust structure to replace the original settings.
i have update fail with chc-u01 firmware 6.0.
how cani do?
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 all recently purchased the Mecool KM8 P 2GB/16GB S912 Amlogic, updated the firmware to 7.1 but lost root access. I have managed to find some instructions on a Russian website to root the stock firmware but can't make head nor tale of it and don't want to brick the device.
The google translate version of the instructions reads as follows:
To get root 7 Androide did:
1.Nado SuperSu create a text file without an ending .txt textBOOTIMAGE = / dev / block / boot
2. Flash card throw Recovery for 7 Androyd created Fail SuperSu and SuperSU.zip (5,63 MB)
3. Boot into Recovery with USB there "Advanced" ==> "File Manager" find the file on a flash drive that put his name it .SuperSu in and copy it into the folder / system
3. Without leaving the Recovery go to "Set" and set SuperSU.zip (5,63 MB)
Can someone please help to decipher the above?
Here's the link to the instructions website. The downloads are pinned to the top of the page. Please let me know if you have any success...
http://4pda.ru/forum/index.php?showtopic=807465&st=1100#entry62380504
1. Create a texfile with this content:
BOOTIMAGE = /dev/block/boot
If I am not mistaken then this file should be saved wit the name .SuperSU and no extension.
2. Copy this file and the Supersu.zip onto a SD with a working TWRP recovery.
3. The file .SuperSu is now to be copied into the system folder - it does not specify if the one from the box or the one from the recovery is used - I assume the one on the box. But needs to be tested to be sure.
4. Without ending the recovery session go back and install install SuperSu.
Thing is you need a recovery that works with Nougat to do any of this.
But then again translators suck and someone capable of reading russing could bring some light on it....
Managed to get it to work. Steps in common English are as follows:
To get root on Android 7.1:
1. Create a text file (eg in Notepad) and name it Supersu without an ending .txt with the folowing text BOOTIMAGE = / dev / block / boot
2. On a microsd card copy Recovery.img (TWRP 7), the created SuperSu file (from step 1) and SuperSU.zip (5.63 MB)
3. Insert the card into Boax and boot into Recovery.
4. Using theTWRP recovery got to Advanced" then "File Manager" find the created Supersu file (from step 1) and copy it into the folder / system.
5. Without leaving the Recovery go to "Install" and flash SuperSU.zip (5.63 MB) from the Microsd card
can you post the required Files here?
i dont understand russian so i dont know what they wrote on 4pda.ru
I have found all file and attached at end of the Post
1. decompress km8p.zip to the root of your TF-Card so you have 3 Files on the root of your TF-Card (.SuperSU, SuperSU.zip and recovery.img)
2. power off your KM8P
3. Press Reset and hold it
4. Power your Box on and hold Reset
5. If you see the TWRP-Logo you can stop press Reset
6. On the Screen accept write and modifying Systemfiles
7. go to Advanced" then "File Manager" copy .Supersu file from TF-Card in/ system of your Box
8. then go to "Install" and flash SuperSU.zip (5.63 MB) from the TF-Card
9. Reboot and now you have root installed
MetaIIica said:
I have found all file and attached at end of the Post
Click to expand...
Click to collapse
I think you uploaded the wrong file, as the zip file you uploaded only contain one file (km8p), which has no file extension (it is probably a .zip file).
However it is missing the other files you are talking about, so could you upload the right files?
Thanks for the effort!
afehst said:
I think you uploaded the wrong file, as the zip file you uploaded only contain one file (km8p), which has no file extension (it is probably a .zip file).
However it is missing the other files you are talking about, so could you upload the right files?
Thanks for the effort!
Click to expand...
Click to collapse
I attached the TWRP for Android 7 here, if you still need it.
I have also started a thread on how to root with Magisk instead of supersu, as supersu wouldn't work for me.
https://forum.xda-developers.com/android-stick--console-computers/amlogic/howto-km8-p-2gb-8gb-s912-amlogic-tv-box-t3745937
Got some problem when I tried to flash the stock ROMs on acer A3-A40 tablet.
I have got the files from ACER support web sites, the zip file contains these dir/files :
--
META-INF/
boot.img
file_contexts.bin
lk.bin
preloader_neostra8167_tb_n.bin
scatter.txt
system.new.dat
system.patch.dat
system.transfer.list
type.txt
tz.img
I can boot into Recovery now but from the Recovery menu, it always said "package file not exist" (or not found) when I select "Apply update from SD card".
Should I rename the xxx.zip file to something like 'update.zip' ??
BTW, these are the files I have downloaded now:
--
- OS_Acer_AV0M0.RV03RC04.WW.GEN1_A60M_A.zip
- OS_Acer_RV09RC01.WW.GEN1_A60M_A.zip
- SD_ACer_AV0M0_A3-A40_RV07RC01_WW_GEN1.zip
none of them works for me......
Any advice here?
yes.
Koumeles.
Can someone send me RV07 rom?
RV07RC01
I can't download it anywhere. Everyone saying to download ti from ftp, but I cannot access it.
have about the same problem, during the update the power was turned off and after charging the battery the tablet hung on the Acer screensaver.
1. archives do not need to be unpacked when writing to a memory card.
2.Could you send me an archive - SD_ACer_AV0M0_A3-A40_RV07RC01_WW_GEN1.zip
The service center said that it could not access the FTP site to download this archive.
Look here if you can help firmwarefile_com/acer-iconia-one-10