I just can't flash any custom ROM on ZTE Axon 7 (A2017G).If I try to flash a ROM it says always something about an error 7.I tried to edit the UPDATER.SCRIPT but I just can't edit it,everytime what I've just deleted reapers after a refresh
Please help!
I want to use substratum theme engine
(sorry for my bad English)
ANdREs2208 said:
I just can't flash any custom ROM on ZTE Axon 7 (A2017G).If I try to flash a ROM it says always something about an error 7.I tried to edit the UPDATER.SCRIPT but I just can't edit it,everytime what I've just deleted reapers after a refresh
Please help!
I want to use substratum theme engine
(sorry for my bad English)
Click to expand...
Click to collapse
First update TWRP to latest 3.1.1 Before flashing any rom, you should flash universal botloader . you can find it in lineage OS thread on the first page. Here is link: https://www.androidfilehost.com/?w=files&flid=148464
Same Error on here
i installed universal Bootloader, afterwards TWRP 3.1.1.0
still Error: 7 while trying to flash newest Lineage OS
is there a propper manual, how to fix this ****ty Error: 7?
i can't find a stabil solution in one thread. There are so many pieces of solution in different threads...
##EDIT: NVM. It seems that the wipe didn't cleared data completly... Looks like it will work after X-time wipe cache, dalvik, data, system...
I have the same problem on the American A2017U version. The problem there is that the trustzone in a new bootloader does not match that of the Lineage OS 14.1 installer script. You can see this by looking at the file TZ.mbn and find that QC_IMAGE_VERSION_STRING=TZ.BF.4.0.1-00325, but the installer script shows assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1"). I'm guessing the A2017G may have a similar problem. Any easy way to fix the problem-I'm using Windows 10-is 7-Zip. Open the zip file, find the script and right click the file, select edit, and delete the two assert statements and save-no extraction needed. I'm using the newest bootstack-B32 by DrakenFX.
aivilon said:
Same Error on here
i installed universal Bootloader, afterwards TWRP 3.1.1.0
still Error: 7 while trying to flash newest Lineage OS
is there a propper manual, how to fix this ****ty Error: 7?
i can't find a stabil solution in one thread. There are so many pieces of solution in different threads...
##EDIT: NVM. It seems that the wipe didn't cleared data completly... Looks like it will work after X-time wipe cache, dalvik, data, system...
Click to expand...
Click to collapse
williamthardy said:
I have the same problem on the American A2017U version. The problem there is that the trustzone in a new bootloader does not match that of the Lineage OS 14.1 installer script. You can see this by looking at the file TZ.mbn and find that QC_IMAGE_VERSION_STRING=TZ.BF.4.0.1-00325, but the installer script shows assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1"). I'm guessing the A2017G may have a similar problem. Any easy way to fix the problem-I'm using Windows 10-is 7-Zip. Open the zip file, find the script and right click the file, select edit, and delete the two assert statements and save-no extraction needed. I'm using the newest bootstack-B32 by DrakenFX.
Click to expand...
Click to collapse
Why are you guys using the B32 bootstack? Is it somehow better than the universal bootstack?
Choose an username... said:
Why are you guys using the B32 bootstack? Is it somehow better than the universal bootstack?
Click to expand...
Click to collapse
i'm using universal bootstack
aivilon said:
i'm using universal bootstack
Click to expand...
Click to collapse
Then you reflashed TWRP 3.1.1 after flashing the bootstack? you sure you aren't on N1-1?
Choose an username... said:
Why are you guys using the B32 bootstack? Is it somehow better than the universal bootstack?
Click to expand...
Click to collapse
I assume you're talking about the B15 universal bootstack by DrakenFX. All but two files are different between bootstacks. There have been numerous tweaks in B32 including NON-HLOS.bin -I'm assuming for the better.
williamthardy said:
I assume you're talking about the B15 universal bootstack by DrakenFX. All but two files are different between bootstacks. There have been numerous tweaks in B32 including NON-HLOS.bin -I'm assuming for the better.
Click to expand...
Click to collapse
The universal bootstack is the one that's always been on the LOS thread, the A2017X_B15_Universal_Bootloader. The one that installs TWRP N1-1?
Choose an username... said:
The universal bootstack is the one that's always been on the LOS thread, the A2017X_B15_Universal_Bootloader. The one that installs TWRP N1-1?
Click to expand...
Click to collapse
That's the one I was comparing against plus A2017U_N_Modem. My mistake the files were by Unjustified. I'm using A2017UV1.1.0B32_bootstack_by_DrakenFX.zip on xda that also contains NON-HLOS.bin. Separately flashing TWRP 3.1.1-0.
williamthardy said:
That's the one I was comparing against plus A2017U_N_Modem. My mistake the files were by Unjustified. I'm using A2017UV1.1.0B32_bootstack_by_DrakenFX.zip on xda that also contains NON-HLOS.bin. Separately flashing TWRP 3.1.1-0.
Click to expand...
Click to collapse
my question is still standing tho
Choose an username... said:
my question is still standing tho
Click to expand...
Click to collapse
Indeed. I would also like to know if the b32 bootstack is better, and in which way.
In fact, I didn't think it could be used on the a2017g.
Edit: don't the bootstack zips need to be adapted to the specific model (G, U, Chinese)?
williamthardy said:
That's the one I was comparing against plus A2017U_N_Modem. My mistake the files were by Unjustified. I'm using A2017UV1.1.0B32_bootstack_by_DrakenFX.zip on xda that also contains NON-HLOS.bin. Separately flashing TWRP 3.1.1-0.
Click to expand...
Click to collapse
i used universal an N Modem. but i think the wipe wasnt ok. after restoring, booting, boot in rec and wipe again it worked perfectly
joaste said:
Indeed. I would also like to know if the b32 bootstack is better, and in which way.
In fact, I didn't think it could be used on the a2017g.
Edit: don't the bootstack zips need to be adapted to the specific model (G, U, Chinese)?
Click to expand...
Click to collapse
yeah, and it's most probably not gonna work on the G, but I mean, there's an universal one out there that works just fine. Why would you want to use one that doesn't work if you have another that is tried and true
Edit: I see it worked. alrighty then
Related
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
Hello
I am not a hope in TWRP.
And I wonder if TWRP for nougat can install .img file as it is written install image.
Is it possible to install cust.img, product.img, etc .....?
and how?
Thank you
Chisetdel31260 said:
Hello
I am not a hope in TWRP.
And I wonder if TWRP for nougat can install .img file as it is written install image.
Is it possible to install cust.img, product.img, etc .....?
and how?
Thank you
Click to expand...
Click to collapse
i tried to flash stock boot.img by twrp and it doesn't work, my phone stucks at your bootloader is unlocked ...
simo255 said:
i tried to flash stock boot.img by twrp and it doesn't work, my phone stucks at your bootloader is unlocked ...
Click to expand...
Click to collapse
OK,
I wanted to be on.
Because twrp revolution rc3 shows install image boot and recovery.
And twrp 3.1.0.2 shows boot, recovery, cust, misc, oeminfo, system, vendor, product, version.
But nothing goes. I thought I was hurting him. thank you
Chisetdel31260 said:
OK,
I wanted to be on.
Because twrp revolution rc3 shows install image boot and recovery.
And twrp 3.1.0.2 shows boot, recovery, cust, misc, oeminfo, system, vendor, product, version.
But nothing goes. I thought I was hurting him. thank you
Click to expand...
Click to collapse
yes but they aren't working well
simo255 said:
yes but they aren't working well
Click to expand...
Click to collapse
As you see I am still trying to install b380.
What I managed to do is;
Since rom revolution rc4,
Installs root v5.2 because boot is b380.
Adb flash system.img from b380
Reboot.
It is not broken everything works, but it does not write b380.
Chisetdel31260 said:
As you see I am still trying to install b380.
What I managed to do is;
Since rom revolution rc4,
Installs root v5.2 because boot is b380.
Adb flash system.img from b380
Reboot.
It is not broken everything works, but it does not write b380.
Click to expand...
Click to collapse
trying to install b380? first go back to mm, then upgrade to b380
mjz2cool said:
trying to install b380? first go back to mm, then upgrade to b380
Click to expand...
Click to collapse
Yes, I have already tried, since MM, it started but it writes nrd90m, and the parameters do not go anymore. And it lacks significant appl.
Datafull public installs but it is not complete.
And datafull hw eu does not install error 7.
Not serious I will test again tonight to the calm.
And tomorrow huawei will publish LOL
Chisetdel31260 said:
Yes, I have already tried, since MM, it started but it writes nrd90m, and the parameters do not go anymore. And it lacks significant appl.
Datafull public installs but it is not complete.
And datafull hw eu does not install error 7.
Not serious I will test again tonight to the calm.
And tomorrow huawei will publish LOL
Click to expand...
Click to collapse
if you follow the instructions closely and have the correct oeminfo and firmware all should be fine
So, here, what I could find and install nougat.
Firmware full-ota-mf not pv.
For, full ota mf, there are three files.
_ Update.zip.
_file public.zip.
_file datafull.zip.
Uses huawei extractor to unpack update.app of update.zip and file datafull.zip.
You can find and install.
With adb and flash fastboot
_boot.img
_system.img
With twrp edit hassan install image.
_vendor.img
_ Cust.img
_ Version.img.
On nougat the device works correctly.
Now I am looking for a solution to install product.img
Any help or advice, would be welcome.
thank you
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
gelie68 said:
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
Click to expand...
Click to collapse
I am currently using DarkRom...great battery life and have not encountered any bugs as yet.
gelie68 said:
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
Click to expand...
Click to collapse
LOS is pretty good on both fronts, Pure Fusion seems to be based on AOSP, good battery life; Nuclea was pretty good too.
Read EVERYTHING or you may DFU brick your phone (disassembly required) or even wipe your IMEIs. Remember that your phone model is the one on the back of the phone, NOT NECESSARILY the one that the system says!
For custom ROMs you'll need the UNIVERSAL BOOTLOADER, your corresponding MODEM FILE, an image of TWRP 3.1.1-0, and MAGISK on your phone. Reboot only after flashing everything, and after flashing the Universal Bootloader, select Install Image and select the TWRP image, then flash it to the recovery partition
Choose an username... said:
LOS is pretty good on both fronts, Pure Fusion seems to be based on AOSP, good battery life; Nuclea was pretty good too.
Read EVERYTHING or you may DFU brick your phone (disassembly required) or even wipe your IMEIs. Remember that your phone model is the one on the back of the phone, NOT NECESSARILY the one that the system says!
For custom ROMs you'll need the UNIVERSAL BOOTLOADER, your corresponding MODEM FILE, an image of TWRP 3.1.1-0, and MAGISK on your phone. Reboot only after flashing everything, and after flashing the Universal Bootloader, select Install Image and select the TWRP image, then flash it to the recovery partition
Click to expand...
Click to collapse
i have installed the TWRP 3.1.1.0 and rooted the phone. everything is ok till now!
i don't understand what you mean with the need for the universal bootloader, corresponding modem file.
thanks for your hellp!
gelie68 said:
i have installed the TWRP 3.1.1.0 and rooted the phone. everything is ok till now!
i don't understand what you mean with the need for the universal bootloader, corresponding modem file.
thanks for your hellp!
Click to expand...
Click to collapse
To install any custom ROM you first need to flash the A2017X_Universal_Bootloader.zip, then flash TWRP 3.1.1-0 (the universal bootloader installs an old version of TWRP which will appear after a reboot, you simply overwrite it by flashing the TWRP.img) then the modem file for your own model (for example A2017G_Modem.zip), then the ROM, then Magisk_14.3.zip.
The A2017X_Universal_Bootloader.zip and the modem files are in the LOS thread.
Choose an username... said:
To install any custom ROM you first need to flash the A2017X_Universal_Bootloader.zip, then flash TWRP 3.1.1-0 (the universal bootloader installs an old version of TWRP which will appear after a reboot, you simply overwrite it by flashing the TWRP.img) then the modem file for your own model (for example A2017G_Modem.zip), then the ROM, then Magisk_14.3.zip.
The A2017X_Universal_Bootloader.zip and the modem files are in the LOS thread.
Click to expand...
Click to collapse
i used the Axon7toolkit to flash recovery and root. it says i can use it to flash Roms...
anyway it's a new world to me and i feel lost here.
do you advise i read any beginner guide about Flashing roms and modding?
thanks a lot.
gelie68 said:
i used the Axon7toolkit to flash recovery and root. it says i can use it to flash Roms...
anyway it's a new world to me and i feel lost here.
do you advise i read any beginner guide about Flashing roms and modding?
thanks a lot.
Click to expand...
Click to collapse
Don't know about any guides, but basically read the posts entirely before actually trying to do anything. The axon7toolkit is nice and all but you just shouldn't use it for flashing stuff. If you have TWRP, you can simply forget about the toolkit for pretty much everything.
To install a ROM you have to use the Install button on TWRP. If you have an error 7 it probably means that your TWRP version is old, check that and install the latest TWRP image if that happens.
If the ROM asks for a pin on startup, go to Wipe then Advanced then Format data
I'm on AEX 4.6 and I'd like to know if there's a way to restore stock via TWRP? if so, plz give me the link to download the rom. Unfortunatly, my miflash is crashing and making EDL method not usable. (Sorry for the english)
Arthur Winchest said:
I'm on AEX 4.6 and I'd like to know if there's a way to restore stock via TWRP? if so, plz give me the link to download the rom. Unfortunatly, my miflash is crashing and making EDL method not usable. (Sorry for the english)
Click to expand...
Click to collapse
well, miflash is not the only one, you could also try EDL Tool from right here (ROMs, kernels, development thread).
But yeah, you can. I wonder why you are still in AEX 4.6, but I guess you still haven't got a vendor partition. If that's the case just download a flashable zip of the stock ROM that you want (would've been real handy if you told us what model you have) and flash it away
Arthur Winchest said:
I'm on AEX 4.6 and I'd like to know if there's a way to restore stock via TWRP? if so, plz give me the link to download the rom. Unfortunatly, my miflash is crashing and making EDL method not usable. (Sorry for the english)
Click to expand...
Click to collapse
Dont update to treble ,it will cause problems
Predatorhaze said:
Dont update to treble ,it will cause problems
Click to expand...
Click to collapse
because you think you have problems, i guess?
I wonder who said to update to treble though
Choose an username... said:
well, miflash is not the only one, you could also try EDL Tool from right here (ROMs, kernels, development thread).
But yeah, you can. I wonder why you are still in AEX 4.6, but I guess you still haven't got a vendor partition. If that's the case just download a flashable zip of the stock ROM that you want (would've been real handy if you told us what model you have) and flash it away
Click to expand...
Click to collapse
I've a A2017G, I'm sorry but I didn't get it the vendor part. And another question, will I have to wipe my internal too??
Arthur Winchest said:
I've a A2017G, I'm sorry but I didn't get it the vendor part. And another question, will I have to wipe my internal too??
Click to expand...
Click to collapse
I'm just saying that you are on an ancient ROM. What's that AEX version, Nougat?
Right now I'm on AEX 6.0 Pie. But yeah, i was just curious.
You will probably need to format your internal storage, but maybe you won't need it. Just do this: After installing the ROM (whatever you decide, EDL Tool or TWRP) install Magisk too, BEFORE BOOTING FOR THE FIRST TIME (If EDL Tool, simply flash the ROM, then tell it not to reboot, flash TWRP, enter TWRP, and flash Magisk; if directly from TWRP just flash magisk right away). This will prevent your internal storage from getting encrypted.
Remember to WIPE DATA AND CACHE BEFORE FLASHING
Anyhow if your phone asks you for a password that doesn't really exist when you try to boot, you'll have to format the internal storage
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!