Develop Bugs

Can't update CyanogenMod

I'm on the latest TWRP version for my device. When I try to update to the new CyanogenMod nightlies I get the following error.
assert failed getprop ("ro.bootloader) = = "I747UCUEMJ2"
getprop ("ro.bootloader) = = "I747UCUEMJB"
getprop ("ro.bootloader) = = "I747MVLDMF1"
getprop ("ro.bootloader) = = "I747MVLUEMK5"
getprop ("ro.bootloader) = = "I747MUMUEMK3"
E: Error executing updater binary in zip "/sdcard/cmupdater/cm-11-20140215-NIGHTLY-d2att.zip"
Error flashing zip "/sdcard/cmupdater/cm-11-20140215-NIGHTLY-d2att.zip"

DracoAzule said:
I'm on the latest TWRP version for my device. When I try to update to the new CyanogenMod nightlies I get the following error.
assert failed getprop ("ro.bootloader) = = "I747UCUEMJ2"
getprop ("ro.bootloader) = = "I747UCUEMJB"
getprop ("ro.bootloader) = = "I747MVLDMF1"
getprop ("ro.bootloader) = = "I747MVLUEMK5"
getprop ("ro.bootloader) = = "I747MUMUEMK3"
E: Error executing updater binary in zip "/sdcard/cmupdater/cm-11-20140215-NIGHTLY-d2att.zip"
Error flashing zip "/sdcard/cmupdater/cm-11-20140215-NIGHTLY-d2att.zip"
Click to expand...
Click to collapse
Your phone needs to have the latest TWRP or CWM installed and your bootloader must match one of the bootloaders in the list.

audit13 said:
Your phone needs to have the latest TWRP or CWM installed and your bootloader must match one of the bootloaders in the list.
Click to expand...
Click to collapse
What list?

DracoAzule said:
What list?
Click to expand...
Click to collapse
The list in your original post. Those bootloaders are listed in the updater script of the ROM you are trying to install.

Oh so that's a bootloader list?
I have the latest TWRP. Do you know where I can find those bootloaders?

DracoAzule said:
Oh so that's a bootloader list?
I have the latest TWRP. Do you know where I can find those bootloaders?
Click to expand...
Click to collapse
I prefer using a CWM-based recovery because I had problems with the latest TWRP.
Which phone do you have?
Be careful with loading bootloaders, especially the 4.3 bootloader because it can't be downgraded.

audit13 said:
I prefer using a CWM-based recovery because I had problems with the latest TWRP.
Which phone do you have?
Be careful with loading bootloaders, especially the 4.3 bootloader because it can't be downgraded.
Click to expand...
Click to collapse
I have a 16 GB d2att Galaxy S3

DracoAzule said:
I have a 16 GB d2att Galaxy S3
Click to expand...
Click to collapse
Here's a link to Philz Touch: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
You can download the latest zip and flash it in TWRP.
After that, try flashing CM11.

Ok. My phone just happens to be in the middle of a Titanium Backup operation that's going to take a while so I'll try it out tomorrow and get back to you.

Ok. I tried updating with the new recovery. No go. Tried updating the bootloader as well to one of the ones in the list. Still no go.
I got the bootloader from here. http://forum.xda-developers.com/showthread.php?t=1831898

DracoAzule said:
Ok. I tried updating with the new recovery. No go. Tried updating the bootloader as well to one of the ones in the list. Still no go.
I got the bootloader from here. http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Which recovery did you install? Which bootloader did you install? Are you doing a full wipe before installing?

I installed philz touch version 6.15.4 and I installed the modem_CWM_I747UCUEMJB bootloader.
And no I'm not doing full wipes. But what difference would it make? Should I do a full wipe then try installing a new ROM?

DracoAzule said:
I installed philz touch version 6.15.4 and I installed the modem_CWM_I747UCUEMJB bootloader.
And no I'm not doing full wipes. But what difference would it make? Should I do a full wipe then try installing a new ROM?
Click to expand...
Click to collapse
Yes, not wiping can cause the ROM to hang during bootup but usually doesn't cause the ROM not to install.

Well I tried wiping. Still a no go.
I'm going to reflash TWRP and then restore my original ROM backup, then see if I can flash a new CM from there.
EDIT: Actually I just realized the update I downloaded earlier was a radio update, not a bootloader update. TWRP still wouldn't install it. It was giving another weird error I didn't really bother to look at. I reflashed philz touch again and it installed like a charm.
I'll just have to remember not to restore a backup with an older bootloader again. I'll go ahead and make a new 'original' backup with a fresh install of CM.

Error when trying to upgrade in Android 8

Hello,
I am trying to upgrade my Zenfone 3 deluxe in Android 8.
But when I flash the .zip in recovery mode, I obtain thks error :
......
Checking for MD5 file...
Skipping MD5 check : no MD5 file found
Warning : No file_contexts
Device image SKU: WW
OTA image SKU: WW
Please use the right SKU for updating...
Updater process ended with ERROR 7
Error installing zip file ´/sdcard/UL-Z016_1-WW-15.0210.1804.47-user.zip'
My SKU is WW so it should be ok
To update, I flashed tbe .zip on asus official website in recovery mode.
For information, my phone is root and has its bootloader unlock.
Do you know why I have this error ?
Thanks in advance

Hedika- said:
Hello,
I am trying to upgrade my Zenfone 3 deluxe in Android 8.
But when I flash the .zip in recovery mode, I obtain thks error :
......
Checking for MD5 file...
Skipping MD5 check : no MD5 file found
Warning : No file_contexts
Device image SKU: WW
OTA image SKU: WW
Please use the right SKU for updating...
Updater process ended with ERROR 7
Error installing zip file ´/sdcard/UL-Z016_1-WW-15.0210.1804.47-user.zip'
My SKU is WW so it should be ok
To update, I flashed tbe .zip on asus official website in recovery mode.
Do you know why I have this error ?
Thanks in advance
Click to expand...
Click to collapse
Have you tried doing a wipe before flashing ? This fixes the error 7 on my zenfone 2.

Foi-racer said:
Have you tried doing a wipe before flashing ? This fixes the error 7 on my zenfone 2.
Click to expand...
Click to collapse
hello, thanks for your answer.
What kind of wipe are you talking about ? If possible i wouldnt like to erase my data.

Flash the oreo stock recovery with adb and then update. That's the way i updated to oreo

Ryder. said:
Flash the oreo stock recovery with adb and then update. That's the way i updated to oreo
Click to expand...
Click to collapse
Hello, thanks four your answer. What do you mean "then update ?"
For me the update is made when I flash the ROM...

Hedika- said:
Hello, thanks four your answer. What do you mean "then update ?"
For me the update is made when I flash the ROM...
Click to expand...
Click to collapse
Just install the firmware from asus website from recovery or from the notification after reboot

Im running into the same issue. can anyone confirm whether a phone wipe is necessary?

Nucl3arSnake said:
Im running into the same issue. can anyone confirm whether a phone wipe is necessary?
Click to expand...
Click to collapse
Hedika- said:
hello, thanks for your answer.
What kind of wipe are you talking about ? If possible i wouldnt like to erase my data.
Click to expand...
Click to collapse
Sory for the late answer, I don't confirm anything. But I ran into a similar issue with my zenfone 2 and it was a little while ago so I'm not 100% sure but I think it was just a regular factory wipe in twrp. So assuming you have everithing backed up I will sugest you give it a try.

I believe i may have found the solution, although id like to confirm something first, could you please pm me a picture of your Software Information tab inside of Settings > About > Software Information. Im specifically curious about your build number. It looks like Asus' method of catching those that Root/unlock their bootloader of hard coding a build number in when the device is no longer considered stock. so the Assert portion of the updater script will check these build value dates, and if it isnt above the required threshold, it throws Status 7.

E1001: Failed to update system image

Recently I got my Note 5 and have been enjoying it, unlocked and custom ROM and everything with the latest TWRP. But recently I've wanted to flash a different custom ROM and everytime I do so, I get the error message:
E10001: Failed to update system image.
Updater process ended with Error 7: Error installing zip file xxx (xxx is just the filename)
No matter what ROM I flash, whether it is the Xiaomi.eu ROM or any other custom AOSP/LOS ROM, I get the same message.
I need help as I have no idea what to do at all and am worried that the phone might be messed up permanently.

Download notepad++ and 7zip. Unzip the file, go to meta.inf/com/google/android and open updater script with notepad++. Select and delete the assert lines, and make sure to remove the empty space. Zip the file and flash it.

ensure your phone is note 5 pro, not note 5

BlackHawk580 said:
Recently I got my Note 5 and have been enjoying it, unlocked and custom ROM and everything with the latest TWRP. But recently I've wanted to flash a different custom ROM and everytime I do so, I get the error message:
E10001: Failed to update system image.
Updater process ended with Error 7: Error installing zip file xxx (xxx is just the filename)
No matter what ROM I flash, whether it is the Xiaomi.eu ROM or any other custom AOSP/LOS ROM, I get the same message.
I need help as I have no idea what to do at all and am worried that the phone might be messed up permanently.
Click to expand...
Click to collapse
Could you solve the error?

Same issue here. If you updated to the most recent firmware, then it's impossible to flash anything using the TWRP recoveries available. I get the same E1001 error. I don't think it has anything to do with the model or the ROM. Be careful, because trying to reflash a firmware package will result in a hard brick, and you need to use an ARB authorisation bypass to be able to restore your phone.
For now I have to stay on the latest Global ROM, nothing else I can do.
wrathking said:
Download notepad++ and 7zip. Unzip the file, go to meta.inf/com/google/android and open updater script with notepad++. Select and delete the assert lines, and make sure to remove the empty space. Zip the file and flash it.
Click to expand...
Click to collapse
I tried this with the Xiaomi.eu ROM - no luck, same error. It's not about the ID of the device (TWRP reports that my device is indeed whyred), it's something else.

Mi rom
stephendt0 said:
Same issue here. If you updated to the most recent firmware, then it's impossible to flash anything using the TWRP recoveries available. I get the same E1001 error. I don't think it has anything to do with the model or the ROM. Be careful, because trying to reflash a firmware package will result in a hard brick, and you need to use an ARB authorisation bypass to be able to restore your phone.
For now I have to stay on the latest Global ROM, nothing else I can do.
I tried this with the Xiaomi.eu ROM - no luck, same error. It's not about the ID of the device (TWRP reports that my device is indeed whyred), it's something else.
Click to expand...
Click to collapse
Have you tried using miflash tool?

wrathking said:
Have you tried using miflash tool?
Click to expand...
Click to collapse
Yes. This triggers a hard brick.

Hey I have the same issue on a redmi 5 plus; does anyone found a solution for this? I updated to the last firmware too, and the only rom that works now is evolutionX.

i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........

deepinsys said:
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
Click to expand...
Click to collapse
I'm alive

deepinsys said:
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
Click to expand...
Click to collapse
Hi, I'm facing the same issue. Can you help me bro? Thank you.

Check whether you are using latest twrp or Orange fox recovery. If not ,then update it. I guess this should solve the problem.

TRUSTZONE error. Was on Xiaomi.EU 9.3.28, want to flash Havoc 28th March 2019.

any idea how to flash havoc os? TWRP gives error 7
assert failed
whyred.verify_trustzone

orangpelupa said:
any idea how to flash havoc os? TWRP gives error 7
assert failed
whyred.verify_trustzone
Click to expand...
Click to collapse
The only way to go back is first flash fastboot stock rom through miflash, then reunlock the bootloader and flash twrp. By going through this way everything will be solved without any errors or getting the device bricked

01Thesam said:
The only way to go back is first flash fastboot stock rom through miflash, then reunlock the bootloader and flash twrp. By going through this way everything will be solved without any errors or getting the device bricked
Click to expand...
Click to collapse
I did this and got the same error

Flash latest Stable ROM with Mi Flash. Is not necessary to lock the bootloader, with a Clean All is enough.

orangpelupa said:
any idea how to flash havoc os? TWRP gives error 7
assert failed
whyred.verify_trustzone
Click to expand...
Click to collapse
It is due to the latest firmware of miui 10 pie you need to go back and flash miui 8.1 firmware file then this problem will be solved

Downgrade from custom ROM to stock ROM

Can anyone explain or guide me to downgrade from custom ROM to stock ROM.
I'm using Lineage OS and I'm trying to go back to the stock ROM (nougat).

This is the twrp flashable version of the stock ROM
https://drive.google.com/file/d/1FcXyOpBNGaTEhfgdBp3yS7NE8vz3ZeWz/view

Thanks for the file but I wasn’t able to flash it.
Error Message is- “Updater process ended with error 7. Error installing zip file ‘/sdcard/Download/Stock_Rom_-S251-_twrp.zip’ “

1karanvaidya said:
Thanks for the file but I wasn’t able to flash it.
Error Message is- “Updater process ended with error 7. Error installing zip file ‘/sdcard/Download/Stock_Rom_-S251-_twrp.zip’ “
Click to expand...
Click to collapse
l don't know why u have got this error. I have flashed it ok.

Is it because of a specific version of twrp or something like that?

Try this
https://drive.google.com/file/d/1FcXyOpBNGaTEhfgdBp3yS7NE8vz3ZeWz/view?usp=drivesdk