Hi!
I've got a problem.
I have the Huawei G740 which is in bootloop now and the only solution for me is to flash an old update.zip
The problem is that,the updater-script is looking after things that you modified in /system.
Well,after I edit the updater-script,how can I put it back ?
After puting it normaly(with winrar) the recovery won't flash it..(it says: OTA update,finding update,opening,verifying update,instalation aborted)
Can someone help me please?
I want to make the updater to not look after the systemui.apk(and odex) (but to replace it with the new one ) ,gallery2.apk+odex,HwThemeManager,apk+odex, framework-res.apk+framework-res-hwext.apk+the odex .if i just remove the checks it wont work..
http://www18.zippyshare.com/v/18725542/file.html (the updater)
Related
hello guys. i want crate a .zip file for flash custom file like font but when i want flash it cmw says: aborted. what i do?
You've changed the zip-file? Or not?
Maybe try to redownload the file and try again.
Which rom and kernel are you on now? And which one do you try to flash?
You'll need a updater script and updater binary for your OS version.. Try to get any from one of the many forums
The META-INF Folder already has those files, so in ur case just add ur files into that zip and remove the ones from the existing mods..
Hi everyone,
I want to eventually create an edited ROM for an Android tablet. (Very simple stuff, really. Removing apks, adding build.prop mods)
I have a working update.zip file, which re-installs the image on the tablet, through stock recovery and the install from sdcard option.
But once I unzip it,
and then zip and even re-sign it (with the tool I found by searching the forum),
the recovery says 'installation aborted', when it is verifying the package.
1. How can I avoid this from happening? I get it that closing the update.zip is done wrong. How can I pass the verification section?
2. It IS possible to push such a .zip through stock recovery, right? I want to avoid CWM and TWRP and make it as simple as possible.
Thanks.
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
dxppxd said:
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
Click to expand...
Click to collapse
I tried this, too.
I only deleted one apk from system/app and later I tried again by deleting the apk and its odex file, too.
In both cases, instead of rejecting the update instanlty, it starts the process and then stops after a few seconds.
IS it possible that there is a filesize checker text inside the image?
(or maybe a propery inside the build.prop or updater-script ?)
Any ideas, anyone?
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
iraklisvel said:
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
Click to expand...
Click to collapse
No
Stock recovery doesn't flash custom roms
Get cwm from builder.recovery.com
Press thanks :good: I'd helped :highfive:
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!
Hi guys,
So I started trying to create the custom ROM for an old smartphone, the Wiko Cink Slim following a french tutorial (I'm french ) .
So I encounter a small problem , let me explain: In order to create a flashable zip for CWM recovery , I put in the zip file containing all the system files etc., then the boot.img ( from the stock ROM the wiko cink slim) and the META-INF folder containing the updater script and another file and everything ... provided by the tutorial I follow.
So after the change in the system folder , I decided to flash the custom ROM in the CWM .
When flashing , all goes well , no apparent error. So I restarts after the smartphone and the problem is that it remains blocked on the boot logo ... And it all the time, I even try to flash the zip healthy custom that I had previously copied and even problem ...
So, conclusion, the problem is not from the file system because it does not walk with the healthy zip ( so the system folder had absolutely no changes ) and I guess it does not come from boot.img because it comes directly from the stock rom the same smartphone. I think the problem of blockage at boot comes from the META-INF folder.
What do you think ? I think that the problem is folder META-INF. So, I attach the address of the download of the META-INF folder, and as I do not know code in the updater-script, check any errors.
https://drive.google.com/folderview?id=0B0kPUePrYTtEZHVmWVFPSVQ2Nzg&usp=sharing
And I just think, the meta-inf folder is planned for version 4.2.2 android while I have version 4.1.1 on my Wiko cink slim. The problem is not there?
Thank you in advance,
Bests regards :laugh:
Hello,
I'm using nougat custom rom on my device, (CM/LOS based ) - i.e it is already installed.
I wish to edit the framework.jar internal dex files - AFTER/POST installation of the rom.
I know I can & how to edit the dex & jar, I already made it.
note: I wish to make those change POST rom compiling, since i'm not a rom dev nor know how to compile a rom ( nor need/want to waste time to know how ).
i.e the changes I want to make are to bin/compiled framework.jar that is already installed on the phone.
My problem is that after I replace the orig framework.jar (/system/framework/framework.jar) with the modded one, I get bootloop with errors like:
Code:
Failed to open dex file from oat file. File: /system/framework/framework.jar:classes2.dex Error: Failure to verify dex file '/system/framework/framework.jar:classes2.dex': Bad checksum (0c7053f1, expected 282a531b)
Code:
Could not create image space with image file '/system/framework/boot.art'.
Attempting to fall back to imageless running.
Error was:
Failed to generate image '/data/dalvik-cache/arm/[email protected]@boot.art':
Failed execv(/system/bin/dex2oat --image=/data/dalvik-cache/arm/[email protected]@boot.art --dex-file=/system/framework/core-oj.jar --dex-file=/system/framework/core-libart.jar --dex-file=/system/framework/conscrypt.jar --dex-file=/system/framework/okhttp.jar --dex-file=/system/framework/core-junit.jar --dex-file=/system/framework/bouncycastle.jar --dex-file=/system/framework/ext.jar --dex-file=/system/framework/framework.jar --dex-file=/system/framework/telephony-common.jar --dex-file=/system/framework/voip-common.jar --dex-file=/system/framework/ims-common.jar --dex-file=/system/framework/apache-xml.jar --dex-file=/system/framework/org.apache.http.legacy.boot.jar --dex-file=/system/framework/telephony-ext.jar --dex-file=/system/framework/org.dirtyunicorns.utils.jar --dex-file=/system/framework/telephon
Attempted image: /system/framework/boot.art
after I upload the modded jar I made sure it got 644 permissions & I wipe dalvik&cache from recovery.
I even tried the above + wiping "/data/dalvik-cache/arm/[email protected]@boot.art" - but still got bootloop...
I know i'm really close to success... but I know i'm missing something...
I think that [email protected]@boot.art isn't "regenerate" when I wipe dalvik&cache or when I wipe it manually.
I think also it have something to do with build.prop values like "dalvik.vm.dexopt-data-only=1" or "dalvik.vm.dexopt-flags=m=v,o=y"
if I could only bypass the checksum... everything I guess would work.
I hope someone can help me ( or tell me which sub-forum in xda can help me with this Q ).\
edit:
I understand now that because I hex edit the classes.dex of framework.jar I get that "checksum error" because I should *somehow* "re-calculate" the checksum for that dex file.
I wonder how to do that, without decompiling &recompiling the dex.... anyone ?
I'll appreciate any help,
Thanks.