Hi, I have a device with custom recovery that can update ROM using update files, I got a working update file (zip contains system/ and META-INT/), When I'm unzipping it, add files to it and zip it again then flashing it, I get update failed, I even get update failed when I'm just unzipping and zipping without adding files or touching the content in the zip. Does anyone know why it might happen?
Thanks.
Post copied to existing thread:
http://forum.xda-developers.com/android/general/manually-installing-gapps-t3467448
Thread closed.
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!
-This is An edited meta-inf can fix all status errors on all Zip's
-Are you having problem while flashing a zip?
If yes this is the perfect way to get it fixed follow all steps to fix your issue
-I make this threat originally for cm11 but then I downloaded a zip and it won't be flashed so I tried replacing the meta-inf folder and it works
-Method for all zip's:
1.extract the zip , and copy your updater scripts to this directory of my meta-inf. meta-inf/com/Google/android here
2.now but the meta-inf into the zip that you want to flash using Rar for android or winrar on PC
3.now recompile the zip with new meta-inf
4.now just follow the instructions of flashing the file
5.you are done now
-Method for cm11 rc13 update :
i tried flashing this update and I doesn't work I tried replacing the meta inf with the previous method but didn't work too so I created this new method only for cm11 rc13
-this update is a patch and it will work only on a clean rc12 update
If you get an error while verifying or any error after replacing the meta-inf this means that you need to reflash rc12 update without any wipes and then flash the rc13 update and it will work
Credit:
1.God
2. @slimps (this meta-inf is from his modded cm11)
3.finally @madkita (me)
-Downloads:
Rar for android: http://www.apk4fun.com/apps/com.rarlab.rar/
Meta-inf: http://www.d-h.st/5TV
Please subscribe to the threat to get all hot fixes of cm11 RCS or maybe cm12 too
madkita said:
-I am making this threat to help people having issues with cm11 installation
-so here I have uploaded a meta-inf folder witch will make any version of cm11 flash able via cwm 5/6/and philz touch and fix for all status errors
-Note: this meta-inf doesn't have any updater scripts you have to add the cm11 updater scripts by your self which can be founded on the directory /Meta-inf/com/Google/android/ on the ROM package
Just copy it to the same directory of my meta-inf and replace the meta-inf folder inside the package using winrar on PC or Rar on android and now just go to cwm 5/6 or philz touch and flash the update and voilla status errors gone this method is for all RCS from 1-12
-Method for rc13 update :this update is a patch and it will work only on rc12 update without any modification for the system files
If you get an error while verifying build.prop or any error after replacing the meta-inf this means that you need to reflash your ROM without any wipes just flash the ROM zip and then flash the rc13 update and it will work
Tested on:
-Galaxy ace cooper running rc12 and with Philz touch recovery
-Galaxy ace cooperve running rc12 with cwm 5 recovery
-Downloads:
Rar for android: http://www.apk4fun.com/apps/com.rarlab.rar/
Meta-inf: d-h.st/5TV
Click to expand...
Click to collapse
I want to apply this method in other devices. Can you help me?
Just copy the meta-inf of ROM that you want to install to the directory on the guide it will work for all devices
Sent from my GT-S5830 using XDA Free mobile app
Hmm i don't get it
Hey me again.
So I just got an OTA update notification, but since I'm on a custom recovery, I can't install it. Don't suppose anyone would go to the trouble to re-package it as a flashable zip file for TWRP/clockworkmod?
Thanks.
flash recovery on OTA pack
There isn't any recovery and the firmware.zip can't be extracted
I'll have access to a full stock Asia phone that's had the update applied tomorrow. As long as the recovery.log is still in cache I should be able to work out which files where updated and create a TWRP update zip file from it.(If its just stagefright libs being replaced it should be compatible across regional roms)
I can provide the ota from Poland play version
porozex said:
I can provide the ota from Poland play version
Click to expand...
Click to collapse
Have you installed the update? Last time i tried i couldn't do anyrhing with a ota_update zip. But with a twrp /system backup and hopefully a recovery.log file from an updated rom, i think I can work out which files were updated and create twrp compatible update.zip based on that. The asia ota_update was only 87Mb in size and trying to address the stagefright bug from what I've seen. Is that the same for you?
No, I can't install it. Mine was around 38mb
edit: ok i found a solution, if you have a backup of your rom (i got it after got installed twp for first time) open it with winzip or 7zip then navigate to sytem>bin>bebuggerd and copy it to the phone. then with a filemanager with root privileges replace the current one and give proper permissions. thats it
What is the exact zip file format for files to be flashed with TWRP?
I had to change something in a zip file to make it work (https://forum.xda-developers.com/t/missing-options-in-recovery.4256195/). After unzipping and changing the code I have to rezip the file, but then TWRP keeps saying "Invalid zip file format!".
I already analyzed the file using zipdetails and tried several compression methods and programs (winwar, 7zip, ark) without success.
anyone have any idea how to install incremental updates manually? i have an ota incremental package, have even dumped the contents and have the .img files inside but not sure what to do with them as they are not full partition images just the increments(i guess just the parts that need to be changed of the actual partitions) is there any way to merge them or how else should they be used? i tried to use payload dumper with --diff but that just keeps giving me an error that boot image type isnt supported so i can get all the other files and no boot image with it. if anyone has any ideas i would greatly appreciate it. i downloaded the oneplus software updater to try the local upgrade/update and it just keeps telling to put it in the root directory and i have put the zip and the extracted contents in every directory i can think of to no avail. oxygen updater also doesnt support this device (yet)
nvm i found the answer thanks to someone on tg..
encrypt the incremental with ofpflasher and update