Hallo guys,
I have read a lot of tutorials and how to's about creating a update.zip
After creating and trying my own update.zip I keep getting the error "Verifying update package"
I try downloading some like: http://www.cnx-software.com/2013/02/04/how-to-root-droid-stick-a2-mini-pc/#comment-27515
and this one http://forum.xda-developers.com/showthread.php?t=2146226
My question is: Is it possible to edit a downloaded rooting update.zip
Because I downloaded one extracted and than made some changes to the
updater-script. I than resigned with the Auto-Sign tool, but than it stop on
"Verifying update package" I am trying to root my MX E-M6 TV Box AMLogic AML8726 android 4.2.1
Please help?
hi you guys
i have backup tablet china cpu a13 with dump tool
don't know how to create a livesuite .img file
from the 5 files that fw_dump2 created for me (boot.img.bootloader.img.data.recovery.img and system
but how make file img with dump ??
please help me thanks
i also want to know is there any solution to make the live suite image file from a dump file of uberiser ?
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!
I had been trying to make a custom ROM or porting a ROM for Micromax Canvas A 96. It has only one custom ROM found in 'needrom' site. As the stock ROM is in a format suitable for SP Flashtool , I wanted to make a CWM flashable ROM in zip format, so that porting will be easier. For this purpose I need 'METAINF' Folder with updater script. So, after searching I came across a guide on 'Converting boot.img +system.img' to CWM flashable zip ROM. I followed it and used android kitchen and got a ROM in zip in the output folder which I re-named (during working on 'cygwin' window). Now I checked it by extracting with 'Express zip' windows software, and it says " The zip is corrupted or encrypted or empty or in an incompatible format'. Now, I do not know how to go about it. Please help me.
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?