Issues with flashing LineageOS via TWRP - ZTE Axon 7 Questions & Answers

I am Rooted, bootloader unlocked, have the lastest TWRP installed.
I fallowed this threads guide https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
however, When trying to flash I receive Updater Error 7.
I have an A2017U running the stock ROM rooted B29.
Any ideas what I'm overlooking?

Lots of people having that issue with the latest. Did you read the thread?

lafester said:
Lots of people having that issue with the latest. Did you read the thread?
Click to expand...
Click to collapse
I have been reading, yes.
However, its with every single build.
All the officials weekly's from experimental to now, and all unofficial

Did you make sure to reformat /data as EXT4?

xtermmin said:
Did you make sure to reformat /data as EXT4?
Click to expand...
Click to collapse
yes.
I've tried a combination of all partitions that can be changed in EXT4, and a combination of some in EXT4, and have also tried F2FS in these respects as well.
No dice.

Helo,
i have the same trouble (my post here : https://forum.xda-developers.com/axon-7/help/a2017g-call-impossible-google-lancher-t3559386 )
the complete error is :
Checking for TZ version TZ.BF.4.0.1-00315
assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00315") == 1
Updater process ended with ERROR: 7
I think it's because the firmware isn't for this model of Axon A2017G (that meam ZTE have made 2 or more version of this model with some adjustement)
i have try to force the installation, but the phone doesn't work properly. (no call possible and some Google app crash totally the phone)
how can i help the developper to find where is the difference to make a firmware for this specific model ?
Regards,

Related

[Q] error excecuting updater binary in zip with twrp

hi guys when I try to flash a rom appears the message "error excecuting updater binary in zip" someone know how to solve it?
Sorry for my bad english
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Strephon Alkhalikoi said:
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Click to expand...
Click to collapse
there is no space in the name :\ maybe can be a problem of the recovery's version ?
I mentioned it because the presence of spaces was the reason my copy of Optimized CM12 failed to install. What version of TWRP are you running?
2.8.5.0
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
GDReaper said:
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
Click to expand...
Click to collapse
This problem started when I tried to flash cyano 12 based on 5.1.1 (by AntaresOne) before doing this everything was fine. Maybe the recovery couldn't convert system to F2FS, can be this?
Strephon Alkhalikoi said:
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
Click to expand...
Click to collapse
Thank you, I will try it
eleonora97100 said:
Thank you, I will try it
Click to expand...
Click to collapse
It doesn't necessarily needs to be converted. It can run with the default ext4 too. Problem with converting is that it will wipe your internal storage. So that into account.
I had the binary updater issue occur on a flashable zip I made. The cause? I accidentally deleted the line that told TWRP to mount the system partition. Restoring the line solved the issue, so check the script. The developer may have accidentally missed a line.
thank you guys I upgraded the recovery and now it works fine thank you very much

I get error 7 when i flash lineageos.

Im using twrp 3.0.3-0. i get error 7 When i flash lineageos but other roms dont. How can i fix it?
S7 edge with exynos
did you find the fix?
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter “Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”.
Click to expand...
Click to collapse
More info here: https://forum.xda-developers.com/showthread.php?t=2522762
Ty. I fixed it by wiping everything the second time, tho.
I have seen some people suggesting to update the firmware(bootloader?)(not quite sure) as an alternative to removing the asserts. What is your opinion on that?

Error when installing new rom

So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
cblock said:
So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
Click to expand...
Click to collapse
Please post your question only once https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Please answer some questions:
Which twrp (file name)?
Which xXx rom(file name)?
Decrypted or encrypted storage?
Which rom do you want to install (exact steps)?
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
cblock said:
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
Click to expand...
Click to collapse
Decrypted or encrypted storage? Which rom do you want to install now? Please use latest codeworkx recovery.
Which xXx rom exactly you're coming from(file name)?
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
cblock said:
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
Click to expand...
Click to collapse
Just follow instructions in first post for clean installation, make sure you made backups: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Encryption means, you cannot access your internal storage without entering a pin when starting twrp or accessing the devices memory from outside.
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
cblock said:
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
Click to expand...
Click to collapse
For the error 7 make sure you downloaded the correct files, without download issues(maybe use checksum). have you removed compatibility.zip from the OB22 rom zip with either 7zip or total commander?
For vendor partition error try to mount vendor partition within twrp manually, if there's no checkbox, you need to flash what I suggested you here https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Earlier open betas created this vendor partion. You can try with OB13.
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
yohouse2 said:
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
Click to expand...
Click to collapse
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
cblock said:
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
Click to expand...
Click to collapse
How did you fix it? Can you explain what you mean by codeworx firmware? Could you provide link for file or guide?
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
strongst said:
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
Click to expand...
Click to collapse
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
cblock said:
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
Click to expand...
Click to collapse
Which twrp version and developer? And after this can I flash Pie directly or should I install something before it? Did you dirty flash or did you use clean install? Sorry for too many questions but I tried it many times and am frustrated that it didn't work, but you fixing it gives me hope.
yohouse2 said:
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
Click to expand...
Click to collapse
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
I was able to flash pie directly after updating the firmware.
twrp 3.2.3 should work
strongst said:
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
Click to expand...
Click to collapse
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
yohouse2 said:
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
Click to expand...
Click to collapse
Did you try the firmware link I posted earlier?
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
Will try in just a minute
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
still getting system patching unconditionally
Does it get stuck with an error?
Its suppose to say that

Want to upgrade my OP5 from Oxygen 4.5.10 , Android 7.1.1 to the newest..

Hello
As the titel says..
Its been a few years since ive done anything like this, so dont really know what i need to do now..
Ive flashes newest twrp-3.2.3-0-20180822 and tryed to install OnePlus5Oxygen_23_OTA_052_all_1910082005_adf7221fba833a0.zip but witout any luck
Log in twrp says:
Installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_052_all_1910082005_adf7221fba833a0.zip'
Checking for digest files
Skipping digest check: no digest file found
vendor partition is not existed, exit ota!!
Updater process ended with Error: 7
Error installing zip file
I have no idea if its even possible to do this if i need other updates first ect.
Kinda rookies now haha..
Iv'e searched forum for help dunno if ive searched wrong or not, but couldnt find any help.
You have to install version 5.1.4 based on Oreo 8.1.0 and boot up the phone to enable vendor partition. Then you will be able to flash the latest Pie OS. If you want a faster way, you can use the 9.0.9 EDL package, but you will lose all data
Well i had a friend that said i could just install 9.0.9 firmware, well now ive ended up witj a phone which i cant enter.. Can still open fastmode and twrp but i cant add files on phone.. Any ideas on how to fix this mess?
mummilana said:
Well i had a friend that said i could just install 9.0.9 firmware, well now ive ended up witj a phone which i cant enter.. Can still open fastmode and twrp but i cant add files on phone.. Any ideas on how to fix this mess?
Click to expand...
Click to collapse
Use this EDL guide https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
PierreVicquery02 said:
Use this EDL guide https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
thanks i will try
PierreVicquery02 said:
You have to install version 5.1.4 based on Oreo 8.1.0 and boot up the phone to enable vendor partition. Then you will be able to flash the latest Pie OS. If you want a faster way, you can use the 9.0.9 EDL package, but you will lose all data
Click to expand...
Click to collapse
So they changed the partition layout with Oreo? I am asking because I currently have the exact same problem.
Currently stucking on 7.1.1 with the same errormessage. I will try to upgrade to Oreo first and then move over to Pie. Thanks.
GoodSoul said:
So they changed the partition layout with Oreo? I am asking because I currently have the exact same problem.
Currently stucking on 7.1.1 with the same errormessage. I will try to upgrade to Oreo first and then move over to Pie. Thanks.
Click to expand...
Click to collapse
Yes, with the version 5.1.5 Project Treble was adopted and it requires a new vendor partition. That partition was created with 5.1.4, so if you are on a version lower than 5.1.4 you will need to install that version, boot once (the repartitioning is made during Android boot, not during the install) and then you will be able to upgrade to latest Pie version.
If you want to upgrade in one step, you can use EDL tool, but you lose all your data. Anyway, I advice you to do so because a format is a good operation when upgrading the Android version
PierreVicquery02 said:
[...]That partition was created with 5.1.4, so if you are on a version lower than 5.1.4 you will need to install that version, boot once (the repartitioning is made during Android boot, not during the install) and then you will be able to upgrade to latest Pie version.[...]
Click to expand...
Click to collapse
I assume I can then also move directly to 9.0.xx, right? Sorry, I forgot that the OP5 got Android 10!
GoodSoul said:
I assume I can then also move directly to 9.0.xx, right? Sorry, I forgot that the OP5 got Android 10!
Click to expand...
Click to collapse
You can install the latest ROM ONLY if you are on a version that is 5.1.4 or newer. If you are on an older version, you have to first upgrade to 5.1.4 and then the newer version (Android 10 will be out in the next months)
Feedback: Works great. Moved to that version, rebooted once, upgraded directly to latest OOS (9.xx whatev) with success. Thanks for all your support & comments!
GoodSoul said:
Feedback: Works great. Moved to that version, rebooted once, upgraded directly to latest OOS (9.xx whatev) with success. Thanks for all your support & comments!
Click to expand...
Click to collapse
You're welcome!

LG G6 (H870) Error 7 "An assets failed" when trying flashing

Hi,
I tried flashing PixelExperience and BlissOS but both gave me error 7.
I downloaded the correct version for my model.
Tried with Stock kernel oreo and BeastKernel.
Is there a way to fix this issue?
Kirito821 said:
Hi,
I tried flashing PixelExperience and BlissOS but both gave me error 7.
I downloaded the correct version for my model.
Tried with Stock kernel oreo and BeastKernel.
Is there a way to fix this issue?
Click to expand...
Click to collapse
Hey. While I don't have a rootable G6, I'll help you as best I can. Did you make sure to wipe everything (including Dalvik cache, cache, and firmware)? If not, do that whenever flashing any customROM. You may not run into problems immediately, but they'll show up soon, if you don't.
Tried but gives me the same error
Kirito821 said:
Tried but gives me the same error
Click to expand...
Click to collapse
I'm not sure, then. Sorry, but you might have to wait for someone who has an H870. In the meantime, try and work it out. I wish you the best of luck.
TipTopHiatus said:
I'm not sure, then. Sorry, but you might have to wait for someone who has an H870. In the meantime, try and work it out. I wish you the best of luck.
Click to expand...
Click to collapse
Thanks
what TWRP do you use? For Android Q you need to use OrangeFox for Q. Because Android Q uses system as root. If you try flashing Q ROMs with TWRP for Pie, you will get errors
Flashed OrangeFox but still error 7, idk if I flashed OrangeFox Q

Categories

Resources