hi i m trying to update my gt540 from cyanogenmod (swiftdroid v2.0 M4) to cyanogenmod (swiftdroid v2.0 M5).this shows error assert failed: write_raw_image("temp/boot.img","boot") .please help .i m wondering what to do???
This is a known bug with M5. The update has installed, but the boot.img hasn't been flashed. Here is what you need to do.
Extract boot.img from the update .zip file. If you can boot into swiftdroid, use YaffsExpert to flash the boot.img.
Hope it helps,
Jack
JackG256 said:
This is a known bug with M5. The update has installed, but the boot.img hasn't been flashed. Here is what you need to do.
Extract boot.img from the update .zip file. If you can boot into swiftdroid, use YaffsExpert to flash the boot.img.
Hope it helps,
Jack
Click to expand...
Click to collapse
is there a version that already has the fix applied? i tried the one on the main thread that was supposed to be fixed, but it still gave this error msg.
Same problem for me.
I don't think the installation completes since the installation seems to abort before system.img is flashed.
I could always try fastboot but I'd wait for a fix.
No it works fine, it aborted at the boot.img. so just reboot and uses the terminal to complete the update.
are you 100% sure? have you tried it? i don't think the phone will boot if the boot.img is corrupt.
nibras_reeza said:
are you 100% sure? have you tried it? i don't think the phone will boot if the boot.img is corrupt.
Click to expand...
Click to collapse
If you were to look at the updater-script file in the update.zip file, the system partition is modified first. Also, the boot.img isn't corrupt, the update script has an error in it which aborts the boot.img flash. But if you flash the boot.img via fastboot or YaffsExpert, it works perfectly.
Jack
For reference's sake, the issue has been fixed I guess.
SwiftDroid v2.0 M5 Fixed
Recovery:http://swift.kulkoff.com/SwiftDroid_v2.0_recovery_M5.zip
Fastboot:http://swift.kulkoff.com/SwiftDroid_v2.0_fastboot_M5.zip
Related
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
normankev said:
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
Click to expand...
Click to collapse
Try toggling script asserts, or re-download the file.
Also, I suggest updating your recovery to 2.5.1.8.
Thanks for the quick reply!
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
I've tried redownloading the file multiple times, even getting earlier versions of the rom to try.
How would I go about updating recovery? I don't have a functional usb cable at the moment unfortunately but if absolutely neccessary I can hack one up.
normankev said:
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
Click to expand...
Click to collapse
I think you should have the asserts disabled to get past the error. (use the extracted zip, which gave you the error 7)
If this does not help, probably best way to go forward is to get a usb cable and try flashing using fastboot
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Is the file modified?
Suman_Auddy said:
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Click to expand...
Click to collapse
Just make sure that you have not modified that file.
Also some people had the same issue and it turned out that they had the file renamed to power.msm8960.so.bak, if so
use a file explorer to rename it back to the original (without .bak), and if that still fails, download the file from the factory image and replace it, then try to flash the zip file.
Suman_Auddy said:
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Click to expand...
Click to collapse
same here but i have "framework-res.apk" has unexpected contents.
In order to use OTA, your system files should be stock and unmodified and it looks like you modified that file, my suggestion, is to download the factory image of your current build of 4.3 from here
https://developers.google.com/android/nexus/images#occam
check what version you have, mine was JWR66Y when I upgraded.
then extract the factory image on your desktop and copy and replace "any" file that you have modded (with TWRPs file manager + ADB), before flashing Kitkat OTA zip, (note: when replacing files make sure that system files you replace have the right permissions e.g. chmod 755)
OR you could flash the Kitkat factory image directly instead of the OTA, ONLY IF you know how to do so without wiping your device's data, remember that this can cause you problems later.
Be careful, I hope you had a nandriod backup, before this happened.
Thanks for all your sugeestions, renaming the file worked for me. Flashing the zip file now via TWRP.
Flashing the zip file failed with error error executing updater binary in zip....any suggestion
Suman_Auddy said:
Flashing the zip file failed with error error executing updater binary in zip....any suggestion
Click to expand...
Click to collapse
Please post the whole error message.
I'm getting this error when trying to flash lollipop roms. I can flash Kitkat roms fine as I'm currently running xdabbeb VS982.5 1.0.0 (G3 rom), but it won't let me flash any lollipop rom. I installed twrp via the autorec program which installs 2.7.0.0 then I updated twrp within twrp with the flashable zip.
Please help
Thank you
Anyone?
Seriously no one knows? What is everyone else using that is flashing the latest 5.0.2 roms?
What am I getting this error?
Please help
Possible Fix
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Thanks for the suggestion. I'll give it a try. If there is no. Md5 what do I do then?
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
I tried resurrection remix and liquid lollipop roms. I had no issues with the initial 5.0 lollipop roms so I'm not sure what changed with 5.0.2.
So the md5 checker generates the .Md5 then you just put that on the SD card with the rom?
Resurrection remix should have an md5 on the download page right below the rom itself.
derekmt95 said:
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
Click to expand...
Click to collapse
Can you point me to the program to use on my computer? Do I just load the .zip file in the program to generate the .md5sum file then put both the zip and the .md5sum file on the sdcard before flashing?
Thanks
derekmt95 said:
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Click to expand...
Click to collapse
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
xxNiradxx said:
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
Click to expand...
Click to collapse
Try to reflash the TWRP.. or maybe is something wrong with the zip file
Use the TWRP compiled by blastagator
Nope, still getting same error with latest twrp.
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
xxNiradxx said:
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
Click to expand...
Click to collapse
How did you downgrade because I cannot seem to find a way to do it.
TheAnonymousButler said:
How did you downgrade because I cannot seem to find a way to do it.
Click to expand...
Click to collapse
just run AutoRec again and you are all set.
LG G2 cm-11 M12 : Error executing updater binary in zip (TWRP)
kashif87 said:
just run AutoRec again and you are all set.
Click to expand...
Click to collapse
Hi, I am having the same problem. Actually my LG G2 was stuck in boot loop with secure boot error. I used SRK tool to flash the partition files as well as TWRP recovery 2.8.6.1. I have wiped everything and there is no OS installed. I am stuck in TWRP recovery screen [cannot downgrade /upgrade]. I am using and OTG cable to flash the cm-11 custom ROM but it is giving me the same error. Can anyone help ?? It has been 10 days I am trying and my phone is dying please help...
Thanks in advance...
before flash 5.1.1 aosp lollipop rom u must to flash first lollipop bootstack
Hi,
I am assuming the reply was for me. Actually I am not installing lollipop. I am going for kitkat but nothing is working now. I have tried cm-10.2, cm-11 M12, cm-11 M7 but all are showing "error executing updater binary in zip". Please if someone can help me out....
Thanks is advance....
@[email protected] i think kk aosp room need jb bootleader
Hello everyone,
I am running a D802 on stock Lollipop and installed TWRP 2.8.6.0 via AutoRec. Now I booted into recovery, wiped System and Cache and got the Error message when installing CrDroid (Marshmallow 6.0.1). Now I tried installing TWRP 3.0.2.0, which succeeded and then downloaded the twrp 2.7.0.0 zip to try that as the ROM still wouldnt install. But it wont install the older TWRP. So I am asking for help to either
1) Install TWRP 2.7.0.0
or
2) Delete the getprop lines from updater-script (after I removed them I get an error 6 so i probably removed too much?)
Thank you in advance
(Guide for Error 7: http://forum.xda-developers.com/showthread.php?t=2522762)
EDIT: Someone said installing another Kernel might allow installation of the ROMs. Which Kernel could work for my phone?
EDIT 2: When flashing TWRP 2.7.0.0 it says "assert failed: run_program("/tmp/loki.sh")==0". So what exactly am I missing on my phone? Is Loki the MM Bootloader?
EDIT 3: Could it be that the build.prop was deleted when I wiped system? Would be weird if that was the cause, but I simply dont know..
Edit: Booted in Downloa Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks
You can't.
flash back a stock recovery.
After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP
did you try?
ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks
Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40
You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).
Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks
You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.
Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA
I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2