Hello!!!
I need to replace a few files from a Firmware update image. I tried two ways ways:
1- editing straight in WinRAR
2- Unzipping, editing and compressing again
In both cases the IMG file looked right. test for problems runs fine, no issues, but when I try to update the device it won't pass on package check and the operation is aborted. I tried to save in both ZIP and IMG extensions, doesn't work in either one.
IMHO it must be related to checksum error. How can it be fixed?
The device is a Geniatech Media Center ARTV1220 running Android 4.2.2
Any clues?
Related
I have Vista Home Premium 64bit and I did download WinRAR 64 bit edition. Whenever I try to install that there claims to be a corrupt file and I have downloaded it a few times from a few sites.
So I go back to the 32 bit version of WinRAR and that installs fine, but reminds me for better performance to use the 64 bit version.
Now, whenever I extract a ZIP or RAR file the Update.exe is missing or I receive a message about the CRC security not matching. AND if and only if I can get the files extracted when I try to install the ROM the Gtab is constantly stating a "status 7" error. I have tried TNT, VEGAn and 1 other ROM and each will not install.
Is there anyone who would be willing to use Skype or some other means to assist me in getting the tablet back up and running something, even if that's the stock ROM?
I do have Clockwork Mod installed already, that was the only thing that seems to have installed correctly.
Thank you in advance,
Brian
If I undertsand correctly: Youre trying to extract the contents of the "update.zip" file that comes as part of the ROM download?
If so.. you dont extract it, you leave it as "update.zip" in your sdcard directory.
I remember seeing a "pictoral" view of what your filesystem should look like in this xda somewhere. Ill try to find it.
No, I am having problem extracting the ROMs from Zip or Rar, so I went and downloaded Memtest86 just to see if there was a RAM problem. That checked out fine after an hour of testing.
Most every Zip or Rar I try to extract have CRC errors, even if it's unrelated to this site. But part of that causes the Update.zip not to extract at all and I only get the "recovery" folder and Command and the Update.zip had an error and doesn't extract.
I then tried it on a laptop with Win7 and I could extract some files then more errors, then I tried a Win XP laptop and that seemed to extract the files fine.
My latest is now the Gtab is bricked, stuck trying to install recovery that never ends. So I looked up for the USB driver and nvflash and the ROM that goes with that and the Gtab doesn't show up as a removable drive so I can transfer the files on there. I have copied them to SDcard but I can't get that to read the data.
So, at this point the Gtab is looping and I cannot get back into Clockwork or get it to show as a drive using the USB drivers and the -Vol and Power button.
Currently when I just power on the tablet in red text I get:
Magic value mismatch:
:"
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
FIXED
PROBLEM FIXED.
I saw another thread stating similar problem, located here http://forum.xda-developers.com/showthread.php?t=1026757 and followed the advice of a few people and now the Gtab is working again. Its stock ROM but the main thing is it's working again.
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 guys!
I was hoping one of you could help me.
Yesterday i modified a build.prop file on my NextBook EBM8000ND (Next800T) tablet, causing it to get stuck in a bootloop every time it's turned on. I've been searching the Internet all day long but it's hard to find support when you have a device which no one in the world uses . It was rooted but I did a factory reset hoping that it would fix it. It didn't and now it's also unrooted. I tried to make a custom update.zip with the backup of the original build.prop file but the stock recovery simply refuses to load any update file. It always stops at verification. I used 7zip with store option. I tried signing the zip, I even edited the updater script to only print some text on the screen but the recovery still wouldn't load it. I tried to find a way to install CWM using sdcard but with no luck. When i tried to use ADB in recovery the device says: "failed to open driver control: No such file or directory". It might be worth mentioning that I found my device's ROM online with boot.img and recovery.img files and a .tar file which contains the original system folder.
Is there any way to make the stock recovery (since installing CWM or TWRP seems impossible) read my update file? Or is there another way to fix this? I only need to replace that single file.
Hoping to get help soon.
Cheers!
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
I was looking to attempt to root a phone (Asus zenfone v520kl) and stumbled upon a problem that I am stuck on and can't find a solid answer to.
Basically, the phone's bootloader is now unlocked and has the WW 3.3 firmware ( https://mega.nz/#!l7wBlQ4B!uB63yH5Rir24GaSfDMWKowqdz-N_sc6SJ-q1WuuGiqM/ ). I was planning on patching the boot.img with MAGISK but 7-Zip does not properly extract boot.img from the .raw file. (boot.img, system.img, cache.img and recovery.img end up with erros and their file size ends up with 0 after extracting. Most of the other img seem to extract just fine.)
So my questions:
1) is there another program that might be able to extract the .raw file. Suggested ways was 7zip or rename extension to .zip and extract which doesn't work either. Also downloading from different websites yield the same problem as they all seem to be the same file. If not,
2) Might there be a way to extract boot.img from the phone itself. (Making matters worse, the phone doesn't have root access and booting to recovery doesn't work. There is also no TWRP for this phone. I did try using TWRP for zenfone 3 deluxe for fun, but that ends up with a black screen.)