yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Well, I re-read thru this thread, and didn't see a definitive answer. So then can I surmise that:

Using NFounds treble method omits encryption( don't use it), selinux is permissive, and you are able to flash numerous GSI images once they are debugged & made available.

Using UnDev's version (via the 0810 build and a suitable TWRP), you get a differently implemented Treble, encryption working, selinux enforcing, but can only flash LOS ROMs at this point?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Aviver:
U can use too the lastest Nfound AEX with the Undev treble
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
So you are saying that I could install LOS 0810, and then wipe/flash AEX over it, and it works fine?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Can you pull your ext SD card, add the zips, re insert card & reboot to recovery & use them that way? Also which exact version of TWRP are you running?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Nfound: all ROMs and GSI

Unjustified: all GSI and only los
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
Can't you still use any non-Treble ROM compiled for our devices, regardless of which Treble image you have? In this case it might just overwrite Treble, but why does that matter? It's as easy as just patching the Treble image back in TWRP if you overwrite it if you want to go back. Also, if Treble is in the system partition, you won't touch your data, allowing you to switch between Treble and non-Treble versions of the same ROM without any negative impact. In my opinion, which is better is pretty clear to me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2000impreza:
I ran into the same issue with 3.2.3 not being able to decrypt. Nfound's TWRP 3.2.1-8 can decrypt without issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Does the reset password zip still work?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mistaliu:
I've come from 14.1, installed bootstack, modem and TWRP from the first page. Full wipe (system, data, cache, dalvik), the 0810 zip, stock 8.1 opengapps and magisk 16.7. Every time I reboot I get this message, everything seems to be working. Anyone else getting it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
this is going to be fixed by Udev soon as he stated
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mistaliu:
Thanks, must have missed that, reading is hard sometimes :o
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
[MENTION=4911249]Unjustified Dev[/MENTION]

when you guys going to release the sources.........:confused::confused::rolleyes:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hille2001:
what is the difference between all Roms and GSI?

are GSI universal Roms without Vendor Drivers for our Device?

or is it necessary to flash first a Treble Rom for Axon 7 to get Drivers and then it is possible to flash any GSI Rom?

other Questtion: when Phone is treblerized with nfounds way ,it is possible to use LOS15 Treble or does the last Version from LOS overwrite the Vendor Partition ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NYGorilla:
Hello. I have been using Lineage 15.1, and thank you.

ZTE_A2017G_JPV1.1.0B02_Modem

Will not this modem work in lineage 15.1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] camarate:
Hey guys.

I've been trying to install Oreo versions of all the different ROMS available, EDL or TWRP, and after flashing it, my device goes to boot loop, can't do anything, don't have access to Recovery, and the only way out is using an EDL cable and flash a Full EDL version of 7.1.1.

What am I doing wrong? I have a A2007G.

Thanks for the help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
with all roms i mean all roms that are non treble, example, AEX or RR

Some GSI (at least one for now) require that you have installed another GSI before flashing it. This seems to be an special case.

As I said before, with NFound's treble you can install ANY rom/GSI with no issues. With Unjustified's way, you can only flash his treblerized LOS and GSIs. Neither of those methods overwrite the vendor partition. Once you create it, it stays that way.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
I'm truly sorry, was genuinely worried that you were new to ROM flashing and might brick your phone. Now you can be reassured that I believe that you are not new at all.

About how Magisk survives dirty flashing, there's a feature is LOS and most ROMs nowadays, and that's the 'addon.d' folder found in /system. Here are scripts that back up certain files in /system, and restores them after you reflash/install an OTA update. There's this tool, 'backuptool', found in ROM zips that are run before /system is wiped(each time you flash a ROM, you wipe your /system), doing backups and restoring them, so that after you install the ROM, certain files(not in the ROM zip) are still in /system. Magisk adds a script to this addon.d folder when you install it too, and its script basically re-patches your boot.img after you flash a ROM so that Magisk is preserved. Thus, if you really want to delete Magisk, the easy way is to just extract the boot.img from a ROM zip, and flash it through TWRP(select 'Flash Image'). But you will leave Magisk files in /data. To delete Magisk completely, the easiest way is to flash Magisk's uninstaller zip(find it in the Magisk thread), but you can also choose to do it yourself, by deleting /data/magisk(older Magisk versions) or deleting /data/adb/magisk(newer Magisk versions), and of course flashing a stock boot.img as well. Hope that clarifies. Other mods can do this backup and restore thing too, one common example is Gapps, which you will find remain in /system after you flash a ROM (update), so if you want a clean /system, delete the files in addon.d, and nothing will survive a ROM flash. Or just wipe /system through TWRP lol.

I don't know bootloaders well either, but I roughly know that Android has multiple 'bootloaders'. There's aboot(I think it's the main bootloader? The one you unlock), and secondary bootloader(SBL). So to boot your phone, aboot starts SBL, then the SBL starts your kernel(boot.img), and from there your ROM. Something like that
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
To clear everything up ZTE is still releasing beta. Are we requesting they publish beta kernel source? It's not fair to ask us to do the same when I'm receiving the same kernel source used in the ZTE beta builds. As before, I have not signed a NDA yet so it's up to you guys. I share everything including my work with beta firmware and kernel and ZTE no longer helps with anything and we have to wait until official releases before we get kernel source or can request kernel source again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Before the walls come tumbling down, just wanted to give a shout of thanks out to UnDev & Orden for this great ROM. Running 7/20 build rock solid & good battery, everything.just.works. :good::highfive:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Nah, just remove the banter and off-topic discussion. This is such an informative and clean thread except for the last page or two ;)

Ditto, that's what I meant :highfive:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
If everything goes right, there will be a new build tonight.

* We are no longer overriding the name and product properties during build. Instead I will use init to set them. This way we can have axon7 in the build.prop but init will force ailsa_ii and P996A01 to match stock device naming. This should fix initializing VR (More on that later)

* The thermal configuration is now moved to vendor (Already merged in my 8/10 build.) This was causing a GSI to lack our device specific thermal profile.

* Camera HAL update (imported from Axon M aka Multy/fujisan 8.1 update from China) Seems to fix flash in Google [emoji328]. You'll have to be the judge, but I think quality and performance has improved. https://imgur.com/a/OCrMKlD
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Az Biker:
* * * Thread Cleaned * * *

Whether or not you agree with Forum Rules, ALL members of Xda need to follow them. Period. This includes posting with respect, not posting off-topic, multiple pages long conversations in development threads.

If you believe there is a GPL violation, or the proper "Source Code" has not been properly linked, given, shared, posted, REPORT the thread and allow Moderation staff to look in to the matter.

Let's ALL get back to commenting on the development of THIS Rom. Not source code, not the philosophy behind posting source, not the validity of needed to post source.

Off-topic is fine (unless the OP states otherwise) until it grows legs and becomes an overwhelming conversation, or leads to other violations like insults, attacks, disrespect, etc.

Please, if you feel a violation has occurred, REPORT it, and move on.

Thank you very much.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
that seems to be an issue for a while now... UDev was working on it, don't know where it stands now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
It's not like that on my test source. OP said it seemed better the way so I stopped picking the commit that made it less intense.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Good to hear that.

well, you can always give it another -sexy- purpose ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Vibration is fine on my end
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Other GSI are working with LOS 15.1 treble rom, but with serious issues. RR-O 6.1 didn't had mobile data for me. But I was testing with a dirty flash.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KevinX8:
No point making reports with dirty flashes, even on pie Mobile data works for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Well, that dirty flash from the old RR-O 6.0 20180511 from kranoner using the same GSI was working fine with the treble released by NFound. It is important also the experiences using dirty flashes. They are not useful for debugging issues, but they provide the ultimate compatibility test. Obviously it is important to identify it as a dirty flash test.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AxonVeezy:
On 10 Aug build and I'd say it's a little strong. Certainly more so than the last non-treble build. I wouldn't say its violent enough to make me drop the phone, but its strong and loud enough that it gets people's attention.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
yes, just wipe data/dalvik/cache and flash the AEX 5.8 zip+gapps+magisk 16.7

---------- Post added at 23:11 ---------- Previous post was at 23:06 ----------

Ensure you have properly unlocked your device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Did you install the Universal B12 Bootloader from this thread? If you flashed 7.1.1 you will need to flash the B12 bootloader again
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
Confused about Treble

I am currently on LOS 15.1 20180720 which is non Treble and I am confused about Treble migration. Will the next LOS 15.1 Udev release repartition my phone automatically or do I have to do manual steps in order to prepare my phone for the next LOS 15.1 build of [MENTION=4911249]Unjustified Dev[/MENTION]? Sorry for the maybe dumb question.

(I have: Universal O bootloader and model specific modem (A2017G) from the OP here and NFound's TWRP 3.2.1-8 for android 8.x (new bootstacks) non treble of course)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
If you flash the treble version of Los, that will create /vendor for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] camarate:
Thanks for the answer.

I believe that it is properly unlocked, I've installed lots of ROMS before, but none of Oreo.

Is there a way to check if the bootloader is "properly" unlucked?

---------- Post added at 10:06 AM ---------- Previous post was at 10:01 AM ----------

Yes I did, several times. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
Anyone else have an issue with the phone randomly crashing to a red notification light, requiring a hard reboot? I assume it may be the display driver crashing, but I'm not really sure. This happens primarily when the phone connected to a charger and in use (in my case with Waze and Audible), but it can also happen at other times, albeit less frequently. I've had this problem since transitioning to Oreo up to the most recent 8/10 build, and can be rather frustrating while driving. This was with a clean flash originally going from 7 to 8, and I do have it encrypted (which was not the default settings).

On the topic of vibration, the setting is good for the 8/10 build, I was missing phone calls and messages with how low it was in the late July builds. Obviously, being able to manually set vibration strength is best, but it's good for now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Sorry, I haven't had those kind of issues. I'm on the 8/10 build as well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Had this also one time when my phone was connected to the charger in my car. It happend while closing some apps for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
Hi all, the download link in the OP points to june versions of this ROM? Where to find latest?

regards

*edit: never mind found it here: https://androidfilehost.com/?w=profile&uid=23032113221599724
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
It's all well saying you shouldn't though, I realise that. Doesn't take away from the fact it ends up being annoying after a while if you can't. No system app remover for example.

All well and good if you have the time and knowledge for magisk but I can't say it's not going to hinder usage whether you should do it or not.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
On the 0711 build my vibration is super weak, for calls, alarms and everything else. Doesn't bother me too much since I don't activate it usually, just wanted to give some feedback. I did dirty flash however, so that might be an issue too ...

On another topic: UDev said there would be a new build soon if everything goes smoothly, so in preparation for that I have a short question:

Would I have to flash Nfounds 3.2.1-8-TREBLE recovery for the LOS Treble build to work, or will the regular 3.2.1-8 work just fine?

It would be highly appreciated if someone who got LOS Treble (20180810) working could just make a super short 'guide', i.e. link all the resources they used and list the order in which to flash / wipe / etc.

I'm sure there will be an 'official' how-to by the Devs once everything is done, but in the meantime there is a lot of confusing info in here about the Treble build :/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
Coming from the July LOS builds, install of the 8/10 build was simple and no impact to my data:

1. Install TWRP 3.2.1-8-TREBLE (for decrypting data) or 3.2.3-0-axon7. Reboot.

2. Wipe system/cache/dalvik cache (and data if not using LOS).

3. Install 8/10 LOS build. This will partition Treble if it does not exist, otherwise I think it'll update it.

4. Install GApps.

5. (optional) Install Magisk 16.7 (SafetyNet fails, but I don't seem to have any issues otherwise).

6. Boot into ROM.

My most frustrating issue is the one I mentioned above, but I have yet to try anything other these LOS builds so far.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Thank you very much :good:

Where can I get the "3.2.3-0-axon7" Recovery tho? Is that a zip or an img file?

The official TWRP site only shows "twrp-3.2.3-0-ailsa_ii.img", and that one causes issues with my /data partition ...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
It's in the first post of this thread:

https://androidfilehost.com/?w=files&flid=274875

However, that version will not decrypt data, so you would have the same issue. Although, there is no reason for decrypting data if you don't plan on backing it up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
I haven't encrypted my data partition, so everything should be fine in that regard. Thanks again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KH_Lionheart:
Tried reading all posts since new Treble implementation from this ROM appeared and even searching but I didn't see anything answering this question

If we used EDL to make the first vendor partition version NFound made and we then flash the latest LOS which uses the new implementation does it merge the extra space back into internal storage somehow without formatting or do we end up with a new/updated vendor, shrunk system and then an unused chunk of data left not attached to anything?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
it skips the vendor part and leaves your vendor untouched, simple flashes the rom and nothing else

if you want to go the UDev's way, you will need to flash a stock rom using EDL and then flashing treble

once its created you can't touch it (although NFound resized his partition from 800 to 500 mb)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
Done. Recovery says '3.2.1-8'

Used that image: https://androidfilehost.com/?fid=5862345805528058637

After second attempt it created /vendor partition

Skipped both as /data was not cleared so gapps and magisk stayed.

On reboot I have fastboot menu...

FASTBOOT_MODE
PRODUCT_NAME - AILSA_II
VARIANT - MTP eMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [redacted 8 hex]
SECURE BOOT - enabled
DEVICE STATE - unlocked

If I go back to recovery and restore 0723 boot/system from backup then phone boots fine.

UPDATE: as [MENTION=9362977]blu3wh0[/MENTION] suggested I reflashed gapps and magisk. 0810 booted ;D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
GApps are installed into /system and Magisk patches the boot image. Both would be erased by installing the ROM, so you do need to run them again. The fastboot menu occurred for me if the boot image was incorrectly patched/modified (like by an earlier Magisk version), in which case just wipe system again and re-install the ROM/GApps/Magisk 16.7. It might be worth letting it boot without Magisk just to make sure it boots.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
Got "vendor image mismatch" at every boot. Will check what is going on other day. Returned to 0723 build for now as I have important trip next days and need working phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AxonVeezy:
On the 10 Aug build, clean install.

Anyone have an issue with touch suddenly not responding? Happened twice last night. Reboot fixed it, but I am just curious if it's a known issue or just a "me" issue.

It's really the only issue I've had with this build so far.

Thanks,

Eric
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
I haven't experienced that before.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Latest build is the 10th of August one right?

Read about one a couple of days ago but didn't see any link so I suppose this is the latest?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
It may be several issues, but you can narrow down some of them. You can replace the kernel just to see if that could solve the issue. Hellsgate X13 CLang works very good with LOS 15.1 8/10. It can also be a hardware issue, overheating can be deadly. Have you monitored the temp of your SoC? Have you also tried to do a TWRP backup of your data partition, do a factory reset, and trying to reproduce the issue?

Just my 2 cents.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] roisuke:
A couple posts back user Zobat posted the link below; Scroll down and it'll be under "new uploads" but for some reason it's not in the ZTE axon 7 section.

https://androidfilehost.com/?w=profile&uid=23032113221599724
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I see thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
awaiting new build from you.everything didn't go well i assume right.........:confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
Thanks, but I've already tried all of this beforehand and overheating is not the issue. Fortunately, I've since narrowed down the issue to what should have been pretty obvious early on, my microSD card. I've never had an issue with it, so it just kind of kept slipping from my mind. I haven't had too much time to use my phone heavily since removing it, but I haven't had this type of crash since. I'll spend some more time later on figuring out what exactly is wrong with my card, but remnant data (mostly empty folders) from all the apps I've used since the original ZTE ROM (!!!) is the obvious suspect.

I'm awaiting for the new build before I do another clean flash before being absolutely sure I've removed all variables. Hopefully, this one will also remove the annoying vendor message at boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Reading the previous discussion here is very interesting.

The big question I have for the [MENTION=5027381]OrdenKrieger[/MENTION] and [MENTION=4911249]Unjustified Dev[/MENTION] is:

Will there ever be a oreo release as good as nougat all round for our phone or is the future too bleak. It seems to me like ZTE have dumped you guys with a beta bootstack and kernel sources which are never going to be great from the ground up with so many things already wrong from the start?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
My biggest question to you is: Why dont you study a little more?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Soon™
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SantiHurtado:
I can only get so erect.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kingo64:
As soon as the audio CPU usage bug gets fixed I'll be at the top end of Mohs hardness scale
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
That audio bug may also use/leak several hundred MB RAM. Haven't seen this neglected issue receive a mention here. Last I installed L15.1 was just to confirm the 50% headphone jack cpu load bug. See https://xdaforums.com/showpost.php?p=77325689&postcount=4785
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
I studied plenty my friend. I just asked a question. Next time something is against your rules I'll try to remember sorry.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hellsbend:
Sadly thats something you have to get used to here on XDA :rolleyes:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Then you will remain soft for a long time, because we depend on ZTE.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
I will definitely look into this. I already have an idea what is causing this.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Holy s**t, it all makes sense now. I was posting in the PowerAmp forum like an idiot, suspecting a bug in the new beta was the cause for the massive battery drain and heat... Nobody was confirming my issue. Well, I guess now I know where that comes from at least :S

Good to hear :D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Anyone having issues with magisk and Google Pay? I can't get it to register my CC to my device and play store says device uncertified. I tried using magisk hide and registering the device id with Google, but no success.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] olus:
great to see it will be a lineage os build! thanks for all your work guys!