yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
Yup I did and I didnt reinstall the Lineage OS 15 vendor. I followed all the steps with one change: I flashed the No Splash B20 bootstack right after I did the EDL flash (this was by mistake actually) then installed the DotOS rom and it booted. I quit and booted to TWRP and dirty flashed Havoc OS os then restarted TWRP and installed GApps micro and rebooted system and it booted up. But now I still have the same issue. i am unable to access the internal storage from the OS. It can weirdly install apps but no data or information.

I searched google and there were people with similar issues and they never really said how they fixed it. Is there anyone familiar with this or knows of a fix?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
I've also seen people have this issue from time to time in different threads, can't recall if I've ever seen a fix.

Let's try to narrow it down.

After EDL, boot LOS, does internal act as expected?

If so, flash DotOS rom, following same steps, does internal act as expected?

Also try removing MicroSD and leaving out while following all steps and checking internal while in each ROM.

Doing my best here, lol.
[ZTE Axon 7 Guides, News, & Discussion] Predatorhaze:
You need to wipe all partitions,and reflash vendor partition.Use party zip and make sure vendor partition is gone,reboot some times to twrp and flash party zip to make its gone.

EDL flash doesn't fix it always
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
Well I had to go back to AOSP Extended and now it seems I have access to my Internal Storage again. Soon as I fired up Whatsapp a ton of messages came flooding through. Sigh

Anywho I wiped and flashed with the EDL package from before. Then Wiped vendor and everything else excluding the internal storage. Flashed back to 3.2.3 TWRP to flash Lineage OS Vendor. Reflashed Oki's TWRP then flashed the B20 Verequies and the Oreo modem. Rebooted TWRP and flashed DotOS and booted up. No probs no errors. Restarted TWRP but this time I wiped the System rebooted TWRP (dont ask me why I rebooted TWRP so much I was just being cautious I guess). Flashed the AOSP Extended img, restarted TWRP, flashed Gapps micro and then finally one last boot and now I seem to have access. Gonna go through the Magisk install you layed out and see how it works now. If I missed anything let me know.

---------- Post added at 07:06 PM ---------- Previous post was at 07:01 PM ----------

I just started from scratch and went with the AOSP ROM using the same method layed out here instead of installing Havoc. I havent rooted yet cuz its still setting up but if it all works out I'll let you guys know. Maybe we all can figure out how it happened and have a fix for someone else that may run into the same issue.

Thanks a lot for all your responses and help :D
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Yeah, knowing the cause would be nice. But, glad you got it working. :laugh:
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
I swear its always something. So far Ive installed the Props file in Magisk Manager after installing Magisk v17.2. Im using an app called Terminal emulator and I typed in SU and was given super user rights. But when I type in props it says 'sh: props: not found'.

Every time i get one step closer.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
This usually happens when Magisk can't write to system. You are using the B20 "Splash" version right? The "NoSplash" version will cause this problem with Magisk.
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
The zip I have on my SD card is 'B20_Bootstack_by_Verequies.zip'. I believe thats the Splash version as my phone always boots up with the warning screen that you can use the buttons to enter Fastboot and Recovery and whatnot. That is the right one right? :(
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
That is the NoSplash, which is why you have problems. The Splash one should have ZTE and Android logos, no warning screen.
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
Ooohhhhh! Yes sir you are correct. And I do remember why I picked the NoSplash version because I wanted to keep the 3 button EDL function and the Offline charging. I dont care for the warning screen at all but the other functions are a personal preference. I did however download a zip that enabled offline charging but not sure if it would work as all the bootstacks Ive used still allowed that.

Are there any other methods to getting past the Safety Net check besides Magisk?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
At this point on the Axon the bootstack situation has become a real mess. As I've said before, there is a lot more i need to write about the bootstacks.

However, we are even to this day still learning advantages and disadvantages of the bootstacks that are available. As we have just discovered the Splash bootstack may be causing more problems than suspected.

Other than the two modified bootstacks, the only other ones available are here: https://androidfilehost.com/?w=files&flid=270519

Feel free to see which one works for your situation.

Let me know so i can log the info.

Edit: you can also try keeping the bootstack that comes with Okis EDL. Probably the best B12 one there is actually, but i don't recall it's limitations.
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
OK will do. I wanna get this sorted before I start digging into kernels.

I did try the 'ZTE_A7LOSv1_UniversalBootStack.zip' and I ran into problems with that though Im not sure if it was because of the Havoc or the bootstack itself.
[ZTE Axon 7 Guides, News, & Discussion] clementinox:
I am slightly confused on the DotOS and lineage vendor files.

The guide says the lineage one is optional, could someone explain to me what the difference between the two vendor files is? I am confused why it would be optional.

Thank you.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Question has been asked and answered. Read the first few posts after the OP.

I may actually change the recommended vendor. There have been some recent discussions on compatibility. This setup is meant to give you a stable point to experiment from, with compatibility to try out other offerings in the dev forums. So, having a more universal vendor I think would be better than one that performs slightly better.

Anyways, thanks for testing.
[ZTE Axon 7 Guides, News, & Discussion] blufness:
I have the same problem with the internal storage gone missing.

I've followed all the steps multiple times, but I can't seem to acces the internal memory in a booted android. Havoc will boot, but won't show the internal storage and can't save any info too it. Dotos and Lineage will boot but on startup various apps will crash constantly.

I've tried EDL Oki step 1 numerous of times to adjust the partition layout. I've tried wiping and deleting and adding the vendor partionion multiple times. They don't work. It looks like the data partition is 'seen' as split. Where in TWRP i can see data and can access it, but when in booted android i cannot.

I was on LOS16 which was working ok, but I wanted to switch to DotOs. I tried to install the rom after a wipe but it failed with vendor errors. It seems i used an old method to get treble which placed the vendor image behind the data. I had to correct that with party tool, but it seems it messes up the data partition. I cannot fix this problem.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Follow all of the steps from the beginning, only skip flashing Verequies bootstack, keep Oki's bootstack which is in the EDL. Let me know if this resolves this issue and I will change the guide. Oki's bootstack will be the most universal approach I think. I was avoiding it because it's only available through EDL, but if we never have to touch it again, then it won't really matter.

Be warned of the ugly color of his bootloader splash screen, many have complained ... Lol
[ZTE Axon 7 Guides, News, & Discussion] blufness:
I 'fixed' it with some help but eventually flashing Havoc os. Kept b20 splash. Fix below is copy paste. I'm not sure if it actually solves the problem or that Havoc os just looks at the partition different. Up until the dotos/Los flash it wouldn't work.

With a big thank you [MENTION=7288053]Predatorhaze[/MENTION]

Wipe all your partitions and reboot to twrp. Check if everything is swiped and all partitions are ext4, if this is not the case then do this and reboot again to twrp.

Now install b20 boot stack splash, G oreo modem and then TWRp 3.2.1-8 treble from Nfound (in this order), then reboot in twrp.Connect your phone to your pc / laptop and see if the internal storage is the right size 51 , xxGB. If that is correct then set DotOS or LOS15 (you can also release 16), havocos 2.0 gsi IMG, micro gapps 9.0 on your phone (all at once).

Now install dotos or los15 / 16 zip, then wipe system partition, flash havoc img, flash gapps, reboot system.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Ok, asking if f2fs was going to be my next guess. I think rewiping the partitions as ext4 is what fixed it. There were some people in the LOS 15.1 thread that actually showed ext4, but still had to format to f2fs and then back to ext4 to get the partitions to work.

I'll note this in the guide since now there are multiple people running into this issue with my guide.

Thanks for replying with your steps to fix.
[ZTE Axon 7 Guides, News, & Discussion] AnonVendetta:
Can someone say whether [MENTION=5027381]OrdenKrieger[/MENTION]'s TWRP is compatible with Nougat bootstacks? I'm using B32 bootstack with AOSP Extended N and Nuclear kernel. And unofficial TWRP 3.2.1-7 by [MENTION=5492451]NFound[/MENTION].

Thanks!
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
Is there anyway to get the LOS 16 vendor to flash separately or does it still use the LOS 15 image?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
The one I have linked was modified for treble, even if it does work, i don't see any benefit in using it over NFounds. As far as Nougat is concerned.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
I don't think so, as there is no vendor.img file to extract from the LOS 16 zip. You would have to flash the entire ROM, then flash the GSI. Though I should tell you, the LOS 16 vendor hasn't done well with GSIs in my testing. But feel free to try and experiment.
[ZTE Axon 7 Guides, News, & Discussion] blufness:
Ok thanks for looking into it. I have a working phone now which I need, so I can't fiddle with it too much now to test.
[ZTE Axon 7 Guides, News, & Discussion] tritrancs:
I am using OrdenKrieger's unofficial Los 16, do I need to follow all steps?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
You can skip step one... Just replace it with flashing Okis TWRP and reboot to recovery.

Once in Okis TWRP you can proceed with wiping and following the rest of the guide.
[ZTE Axon 7 Guides, News, & Discussion] amphi66:
So I was able to purchase a supposedly "parts only" A2017U on eBay quite cheaply & was able to restore it using MiFlash. So now I have a great experimental platform w/o risk to my DD still running B35.

Using this fine guide it is 'treble-ized' on Pie and very easily can swap from ROM to ROM, although w/o SIM card.

The dilemma is now choosing the fastest, most stable, and efficent ROM here prior to making the change on the prime phone. Thanks to you (and others) for this work!
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
I am currently using Liquid Remix, it is far superior to this Havoc build in terms of performance and battery. However, the setup it requires is completely different than this one, and this one is still best in terms of compatibly to experiment with other ROMs. So it's still the best home base at the moment.

Another Liquid build should be coming soon, so hopefully it can prove to be the next jumping point and we can leave this old Havoc build behind.
[ZTE Axon 7 Guides, News, & Discussion] amphi66:
Starting with Havoc I found it easy to follow the LiquidR instructions, then simply wiped system and cache & relash an AEX GSI to try it.

I do see a 12-22 Liquid just dropped.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Just wanted to say that I'm having some better luck with Liquid Remix. I've made some tweaks to a beta Hellsgate kernel, and it makes it a lot more usable as a daily driver. The kernel and most of the tweaks were suggestions from the guys in the tg group, so thanks guys you know who you are.

Right now the only thing holding me back from making a guide for it, is that once you are on this Liquid setup, you won't be able to try out different vendors very easily.

If I were to do it, I would have to add another FAQ about the Vendor situation with Liquid. So, let me know if your interested in a guide to this setup. If you are I'll take the time to write up the FAQ and get the guide up.
[ZTE Axon 7 Guides, News, & Discussion] pahoa:
I would be very interested in your setup as I find Liquid Remix the best for daily use.
[ZTE Axon 7 Guides, News, & Discussion] bassguy60:
I would be interested in your instructions. Tried both Havoc and Liquid Remix previously on my 2017U but both were very laggy with random reboots.
[ZTE Axon 7 Guides, News, & Discussion] Gaff_l:
A setup guide would be great, thanks!
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Ok everyone, thanks for the feedback. I wasn't aware anyone was monitoring my guide still. I'll get one posted up this weekend hopefully. Also, there has been another Havoc build recently, thanks to [MENTION=4896610]king1990[/MENTION] ... Currently testing, but switching vendors causes no problems as far as I can see. So, I'll also update this guide with the current Havoc setup.

Update: New Havoc runs great, but limited on vendor options as well, so I am going to leave this guide as is. Again, for it's flexibility, making a good home base. As far as Liquid, I am experiencing an in call issue, I am going to need to resolve it before posting a guide, so that is being delayed, sorry.
[ZTE Axon 7 Guides, News, & Discussion] jonathonsunshine:
Followed the guide successfully, but I'm not real keen on the Havoc rom, mainly because i can't swap the back and recents keys. If I want to try different roms, should i be looking for A roms or AB? Also, can I assume Oreo roms will work fine, i read somewhere in here that someone got the AK4490 DAC working on Treble roms.

Unrelated, I used Magisk 18.0 and it seemed to work fine though all I used it for was VancedYouTube.
[ZTE Axon 7 Guides, News, & Discussion] ttkian:
To switch keys, flash this https://androidfilehost.com/?fid=3700668719832237510

Axon 7 is A rom
[ZTE Axon 7 Guides, News, & Discussion] jonathonsunshine:
Didn't seem to work
[ZTE Axon 7 Guides, News, & Discussion] ttkian:
Try to mount the vendor and system, then flash it.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
The purpose of the guide is to jump to a universal starting point. There are definitely better, more up to date GSI to choose from. The newer ones I've tried support the hifi DAC. You'll have to look for A Only GSI.

I'll be changing the guide today, because I feel LOS based vendors are failing at working with more current GSI.

I recommend changing the vendor to Kranoner's vendor for more compatibility with newer GSI. With the exception of LiquidRemix, NFound 1.1 vendor works best with that one.

Best GSI to try in order of my favorites first:

LiquidRemix

Arrow

PixelDust

AEX

NitrogenOS

Havoc

There is also now a Combifix tool by [MENTION=5334294]raystef66[/MENTION], which makes applying fixes, swapping keys, installing Magisk and passing SafetyNet a whole lot easier. I recommend not using the framework fix, unless you have a problem with brightness levels.

https://xdaforums.com/axon-7/how-to/summary-best-pie-roms-to-try-to-moment-t3841784/post78663373

Make sure to mount vendor and system before using.
[ZTE Axon 7 Guides, News, & Discussion] jonathonsunshine:
Sweet, that worked.

I'm surprised I've never bricked a phone (permanently), I just blindly follow guides on XDA and really have no idea what I'm doing. For all the things I've flashed though, I've never had to "mount" a partition before. Is this some to do with the lab mod of TWRP installed in this guide?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
No, it's just a general precaution, as some fixes that were created do not automatically mount the partitions.
[ZTE Axon 7 Guides, News, & Discussion] jonathonsunshine:
I susp3ct most of my issues with this ROM stem from the now fixed HW keys. I have a Samsung tablet that I use quite often, that order of keys is really engrained deeply.

So, you think liquidremix is the best and needs NFound1.1 vendor partition but all the others need Kranoners?

Any of those ROMs off hand you know support the DAC?

I'll put off flashing another rom for a few days.
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Yes, Kranoners vendor will work best for performance, but with Liquid it breaks a few cosmetic options. If you can live with a few things not working, like the dark and black themes not theming settings menu or not being able to modify power menu buttons. Then use Kranoner vendor.

Otherwise NFound vendor will not have those problems.

Yes, they all have HiFi DAC support.

Update: I was just reminded that the power menu issue was on an older Liquid build, and is no longer an issue when using Kran vendor with the newest build.
[ZTE Axon 7 Guides, News, & Discussion] jonathonsunshine:
Does performance mean snappy responsiveness OR battery life?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Snappiness. There isn't much difference in battery life between Kran and NFound vendor.
[ZTE Axon 7 Guides, News, & Discussion] jonathonsunshine:
You know, this Havoc ROM as is from your original tutorial (is, before you change it later today) is probs the most responsive and snappy this phone has ever been, and I've used RR, AEX, LOS, Full and debloated stock marshmallow, nougat and stock Oreo.

Do you think that is more a reflection Pie or something else?

I found it especially surprising considering all the graphical upgrades there seem to be in the the task switching etc.

---------- Post added at 08:34 PM ---------- Previous post was at 08:20 PM ----------

I would have thought that the DAC would have been more dependant on the vendor partition than the ROM/GSI. My understanding is the Vendor partition is all the hardware drivers, so I would have thought that the vendor partition would set up either the AK4490 _or_ the AK4461 as the audio device. I assume you still won't get a choice like in the stock ROMs?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Yes, it is quite a noticeable difference moving to Pie GSIs which is why I find the sacrifices of some of the stock options acceptable for my usage.

Just because hardware coding is provided in the vendor, doesn't mean it will work. Right now practically all of the GSI are being based off of phhusson's vanilla GSI, as he is working purely on compatibility among devices. So as he adds and changes things at the base, more things tend to start working with newer GSI builds, whether we use an older or newer vendor.

No you can not choose between the DAC like you could in stock.
[ZTE Axon 7 Guides, News, & Discussion] king1990:
Just small correction , not all GSI are based on phh GSI build, instead almost all GSI are based on his work or script, that why phh GSI works in almost all devices while mine for example works with less number of devices.
[ZTE Axon 7 Guides, News, & Discussion] madhits45:
I am still trying to understand why you are suggesting B20 bootstack by DrakenFX that has been modified by Verequies, and why not A2017x LineageOS15.1 UniversalBootstack v2 by DrakenFX? Or is that the version Verequies edited? The bootstacks are very confusing with the axon 7 and I'm glad you have this section in your guide, but I think you should expand it. I am still unclear about the use of the one you linked to? I have been using UniversalBootstack v2 by DrakenFX or OKI B32-B10 combo and I'm not even sure which bootstack drakenFX universal includes, B10, B20, B32 or another? I just know its universal and works with all the roms I have tried. Its also been unclear to me whats the newest bootstack from zte, I think its B32? If so why isnt that one being edited for use with these GSI roms? OKI has used it here, see: https://xdaforums.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693 I am currently use OKI's B32-B10 combo bootstack after switching from drankenFX why arnt you suggesting that one for this guide? Actually its kinda confusing cuz in the OKI guide he does not mention his B32-B10 he made for this custom oreo roms for newbies guide. Is it outdated already? Hope you can clear some of this up?​
[ZTE Axon 7 Guides, News, & Discussion] madhits45:
I got the answer now.. Pie GSI requires B12 or B20 bootstack. You cannot use old B32-B10 bootstack for it because it will not boot the GSI. In-case anyone wanted to know thats why OKI is using B20.
[ZTE Axon 7 Guides, News, & Discussion] cercelcremene:
Thank you very much, NFound, for developing and posting! I also confirmed that ROM works OK with the Speedy vendor.
[ZTE Axon 7 Guides, News, & Discussion] Predatorhaze:
i am using bootleggers gsi with kranoner vendor and b12 bootstack and hellsgate reborn kernel.Everything works.Only thing i miss is dolby atmos.

Now i run bootleggers from nfound with speedy vendor,b12 bootstack and schwifty r5 kernel.No problems here
[ZTE Axon 7 Guides, News, & Discussion] ZxYdR:
Hello. I followed the guide closely with the only difference being that I used a different GSI. (Havoc 2.5) I did it all twice now.

My problem is when I want to flash Gapps (Nano) it always says:

Insufficient storage space available in system partition.

[...]

Error Code: 70

What do I do?
[ZTE Axon 7 Guides, News, & Discussion] runninghamster:
Go to TWRP, and then click on Wipe > Advanced Wipe > Select System partition and go to advanced settings, and click Resize Partition. This will fix the problem, and you'll be able to flash gapps.
[ZTE Axon 7 Guides, News, & Discussion] kitcostantino:
Thank you for this, brother. I finally decided to update one of my Axons to pie and this helps me have a great start.
[ZTE Axon 7 Guides, News, & Discussion] savoirtous:
System and Vendor keep getting unmounted

I followed the instructions from the OP and now when I boot system I am stuck on the ZTE logo after using the Splash version of the bootstack.

Waited for more than 5 minutes still nothing.

Also, system and vendor stay unmounted when I force shut down and reboot to TWRP. Any ideas?
[ZTE Axon 7 Guides, News, & Discussion] runninghamster:
The guide is quite outdated, but all the steps are relatively the same.

If you would like the options on boot where it says "Bootloader is unlocked", and you can select where to boot using the fastboot options, use this bootstack:

https://androidfilehost.com/?fid=11410932744536985259

If you'd rather prefer no bootloader unlocked message, and have the phone boot straight into the os, use this bootstack: https://androidfilehost.com/?fid=11410963190603847301

You can also find latest Havoc 2.6 in the Project Treble forums on XDA. Our phone uses ARM64 A Only.
[ZTE Axon 7 Guides, News, & Discussion] bluenote73:
[MENTION=8456254]EBeatFLA[/MENTION] would you say a few words about what's still applicable in the OP?
[ZTE Axon 7 Guides, News, & Discussion] EBeatFLA:
Steps 1 and 2

Okis guide to flash his EDL to get Trebelized, in Step 1, is still currently the best way to Trebelize the Axon, imo.

As far as bootstack, I still recommend the No Splash by Verequis. Unless offline charging is really important to you, then use Oki's remix bootstack.

Everything else that is current, vendor, GSI, fixes, etc.. can be found in the TG group I've mentioned.