I think X13 non treble is for the B12 bootstack.@Oki Do you think the new Hellsgate X13 non-treble would be a nice addition compared to the included Hellsgate 3.0 on EDL Option 1?
I think X13 non treble is for the B12 bootstack.@Oki Do you think the new Hellsgate X13 non-treble would be a nice addition compared to the included Hellsgate 3.0 on EDL Option 1?
Option 1 uses B32+B10 bootstack. Only Kernels designed for that bootstack will work. The latest one for that bootstack was Hellsgate 3.0. Newer Hellsgate kernels are all designed for B12 bootstack.@Oki Do you think the new Hellsgate X13 non-treble would be a nice addition compared to the included Hellsgate 3.0 on EDL Option 1?
The configuration I have at this moment is Option 2. I have also removed the 800MB djkuz/Nfound's vendor partition from the start of the stock data partition and added it at the end of the system partition. That is the logical splitting configuration. djkuz and NFound developed the other method, but the future of treble seems to be using the last sectors of the system partition to split a vendor partition from it. I am on Option 2 just because I am testing Treble partition configurations. For a daily driver I still prefer and recommend option 1.What version bootstacks are you using @Oki ?
The ones Nfound made or the Lineage ones?
Sounds great!On the other hand I am polishing a little bit my TWRP custom version with the integrated Party tool, vendor support (mount/wipe/backup/restore) and other added functions I missed from TWRP 3.2.1-7. It is not yet ready and some functions are not yet safe for everyone, but it will be eventually released when ready.
I've go an Axon7 A2017G with bootloader unlocker. I always manage to flash it correctly through EDL mode but unfortunately it seems to not work. The first time, I tried to boot on Recovery, but the Smartphone has gone into bootloop. The second time, I boot the phone normally and I reached the Mi Favor... but it has only 4 GB of available spase in the data partition, So I decided to factory reset directly from the ROM and the smartphone has gone another time in Bootloop. Since it was clear that the problem was the recovery, I tried, before loop in the Mi Favor to flash the TWRP with the following guide (https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069) . I executed all the steps correctly, trying to install the TWRP 3.2.1-8 by NFound, but when I tried to boot in recovery the phone suddendly power off. I tried to boot normally and I got another time bootloop.The only pre-requisite is to be bootloader unlocked. Other than that it is just a matter of getting the phone into EDL mode to be flashed.
Thanks is the b12 in the edl the same as the one Nfound made or drakenfx? The reason I ask is because drakenfx fixed cannot write to system but nfound didn't.. I wonder about other differences between the b12 bootstacks.Option 1 uses B32+B10 bootstack. Only Kernels designed for that bootstack will work. The latest one for that bootstack was Hellsgate 3.0. Newer Hellsgate kernels are all designed for B12 bootstack.
The configuration I have at this moment is Option 2. I have also removed the 800MB djkuz/Nfound's vendor partition from the start of the stock data partition and added it at the end of the system partition. That is the logical splitting configuration. djkuz and NFound developed the other method, but the future of treble seems to be using the last sectors of the system partition to split a vendor partition from it. I am on Option 2 just because I am testing Treble partition configurations. For a daily driver I still prefer and recommend option 1.
I am not using Option 1 at this moment since I am now working on making the PARTY tool fully compatible with other devices. On the other hand I am polishing a little bit my TWRP custom version with the integrated Party tool, vendor support (mount/wipe/backup/restore) and other added functions I missed from TWRP 3.2.1-7. It is not yet ready and some functions are not yet safe for everyone, but it will be eventually released when ready.
System write has nothing to do with the bootstack. Just open a terminal and typeThanks is the b12 in the edl the same as the one Nfound made or drakenfx? The reason I ask is because drakenfx fixed cannot write to system but nfound didn't.. I wonder about other differences between the b12 bootstacks.
That's what I thought too but it doesn't work with Nfounds b12. Funnily enough I don't need that command to use system write using the boostack modified by drakenfx. So which did you use in the edl?System write has nothing to do with the bootstack. Just open a terminal and type
reboot disemmcwp
That will DISable the EMMC Write Protect.
Thank you so much for your continuous work for our A7!On the other hand I am polishing a little bit my TWRP custom version with the integrated Party tool, vendor support (mount/wipe/backup/restore) and other added functions I missed from TWRP 3.2.1-7. It is not yet ready and some functions are not yet safe for everyone, but it will be eventually released when ready.
It has the Oki remix B12 bootstack, it is not DrakenFX's, NFound's or A7LOS B12. Test it and if you find a problem with it just let me know. I never had any problem with my bootstack (I am using it now) and I didn't have to disable write protect, I disabled it long ago. There isn't any problem here about write protect, so I assume it is not a problem and both EDL options work for everyone.That's what I thought too but it doesn't work with Nfounds b12. Funnily enough I don't need that command to use system write using the boostack modified by drakenfx. So which did you use in the edl?
BTW I repeated this so many times switching back and forth, changing between bootstacks on different ROMs.
I have noticed that issue with some camera apps, but not with others, probably the use of Camera2 API could make the difference (for the better or the worse). Regarding the B12 ROMs, the best so far is the ope provide with the Option 2 EDL. AEX 2018.7.11 is stable and everything works for everyone. Later treble ROMs are not working fine for everyone. You can try them and stay with them if they work for you, but many people have problems receiving calls when LTE is enabled. It is probably related to the carrier compatibility. I am using T-Mobile US and I have that issue with my unit.Hi Oki, thanks for your efforts on ZTE Axon 7 development and quick responses. The configuration and EDL flash is working really fine for me. However with AEX extended ROM, I noticed Audio sound is little lower than Stock
With RR O Rom, Camera app shutter press is lagging. Hence I am looking for any efficient ROM that is close to B35 Nougat Stock ROM
I installed Nfound Havoc rom and it seems to work OK for now. I would like to know, which would be the best B12 Oreo ROM for ZTE Axon 7. You have lot of knowledge on it.
I do not have the device tree based on the B12 bootstack, required for supporting encryption. So I took the widely available 3.2.3-0 as base. I could try taking the kernel from NFound's 3.2.1-8 using the Oreo Kernel and device tree, and see whether encryption could be supported this way. In such case, ADB won't work.Thank you so much for your continuous work for our A7!
Will your TWRP be based on latest 3.2.3 and will it support encryption on oreo/pie as well?
Hopefully yes...
Hmm... Maybe @NFound - if he is still around here and sees this message - will be so generous to share the required resources in private with you to build a proper 3.2.3 build with all functionality ...I do not have the device tree based on the B12 bootstack, required for supporting encryption. So I took the widely available 3.2.3-0 as base. I could try taking the kernel from NFound's 3.2.1-8 using the Oreo Kernel and device tree, and see whether encryption could be supported this way. In such case, ADB won't work.
Nothing is actually installed. It is a TWRP program that is executed when you try to install it. Nothing is installed, only the partition table is modified and the vendor partition is formatted. So, you can use it and is fully compatible with previous versions.can I install this patch 0.2 over your patch?
https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
There's no problem using your bootstack with writing to system. The problem is when using Nfounds version.It has the Oki remix B12 bootstack, it is not DrakenFX's, NFound's or A7LOS B12. Test it and if you find a problem with it just let me know. I never had any problem with my bootstack (I am using it now) and I didn't have to disable write protect, I disabled it long ago. There isn't any problem here about write protect, so I assume it is not a problem and both EDL options work for everyone.
I have noticed that issue with some camera apps, but not with others, probably the use of Camera2 API could make the difference (for the better or the worse). Regarding the B12 ROMs, the best so far is the ope provide with the Option 2 EDL. AEX 2018.7.11 is stable and everything works for everyone. Later treble ROMs are not working fine for everyone. You can try them and stay with them if they work for you, but many people have problems receiving calls when LTE is enabled. It is probably related to the carrier compatibility. I am using T-Mobile US and I have that issue with my unit.
How did you come to this conclusion? I'm seeing in top that both use 0.0% CPU.Please note that the activation of these features will drain your battery faster since both will use your CPU. Nonetheless the benefits are evident. if you want to fully enjoy the audio capabilities of the Axon 7 you should go ahead and use them.