yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] harrymarmol:
Problem with gps

Hello friends, i was on Nougat B35 but i have problems with gps, i read in zteforum that it was a error from the B35 rom and maybe the Oreo update will fix it, but then i install this one and the problem persist, i mean the gps actually work for certains apps like google maps or weather, but accuweather or instagram cant get location. Anyone know how to fix this?

I already download the B32 EDL in case i have to downgrade but i have one question, if i flash B32 EDL i must have to unlock the bootloader again? I mean after i flash the b32 i can go directly to install the boot and recovery via edl or i have to unlock bootloader again before that? Thanks and sorry for my english since now.

Greetings from Argentina:good:
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Try the fstab.qcom file I provided and follow DrakenFX's directions installing it.
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
where is it?
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Have you looked at the 1st page Victor setup?

https://xdaforums.com/showpost.php?p=76685288&postcount=47
[ZTE Axon 7 Guides, News, & Discussion] vicyang85:
just tried this and phone does not boot. First boot still shows Axon logo and then restarts by itself. Next time no logo at all.

Edit1: Used the restore tool and the phone boots, clock is centered, but other icons overlap the centred clock. Restored system backup to go back to before.

Is there any way to only remove the carrier text?

Thanks
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
Thanks.
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
Well, [MENTION=3756725]kountry83[/MENTION] I gave 'er a college try. Encryption turns off, but SDcard corrupt. :(

---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------

[MENTION=5334294]raystef66[/MENTION] "ZTE_A2017X_V2.1.0B12_OREO_BootStack_twrp3126_by_raystef66.zip" is not flashing in TWRP. It errors out.

Main difference I could see between B01 bootstack and B12 bootstack that you created was in the updater script:

package_extract_file("ddr.img", "/dev/block/bootdevice/by-name/ddr"); --> working B01 BootStack zip

package_extract_file("firmware-update/ddr.img", "/dev/block/bootdevice/by-name/ddr"); --> not working in B12 BootStack zip

I extracted all the .bin, .mbn, and .img from B12 Bootstack zip and then using 7zip I dropped them into B01 BootStack.zip and "butter", so that's the issue that I could see.

Spidengo
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
Should work though. It's tested on several devices i got feedback from and no issues at all. So, i cannot think of anything that might went wrong.

Hopefully this weekend I'll make one just for the carrier. For B01 and B12.
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
[MENTION=1761257]spideyngo[/MENTION]

Hmm I'm not getting that because the sdcard is set as a footer with vfat and not even touched so it shouldn't of lost format. I just tried it and it worked for me when chmod 0644 the fstab.qcom before pushing it. Might have to write a shell script for it on placing permissions and format.

Thanks
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
Thnx for testing. I'll look into this afternoon. You could be right though because it all goes that fast when creating. Could have missed something. I'll compare and let you know. If you want to test a possible new one, let me know so I can upload it again in case there was something wrong. I keep you updated. Thanks!

Edit : i see the error in your text. The text is wrong about firmware. So put the bootstack aside. I'll make a new one.
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
[MENTION=3756725]kountry83[/MENTION] I ran chmod 0644 so not sure. Let me do a clean install and try again. I guess we're all night owls 'round here.

EDIT1- [MENTION=3756725]kountry83[/MENTION] I ran it again after clean install. Encryption fixed, but it thinks SDcard corrupt (Sandisk 64GB extFat).

EDIT2- [MENTION=3756725]kountry83[/MENTION] I swapped in a Sandisk 16GB Fat32 and it detected it fine. So it is isolated to extFat 64GB+ SDcards.

---------- Post added at 01:13 AM ---------- Previous post was at 01:08 AM ----------

[MENTION=5334294]raystef66[/MENTION] I'll PM you the fixed one. I already did the work my man. Oh, and I put NFound's EN fixed TWRP 3.2.1-6 in it.
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
[MENTION=1761257]spideyngo[/MENTION]

Hmm exfat format must not be playing nice with the table when decrypted. Just a question. Can your zte file manager see the sdcard and explore it with the 16gb?
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
[MENTION=8495959]Victor13f[/MENTION] , can you replace the B12 bootstack from OP with this one : ZTE_A2017X_V2.1.0B12_OREO_BootStack_twrp3126

Btw, bootstack is without modem. Always flash your appropriate modem from OP.

thnx [MENTION=1761257]spideyngo[/MENTION] for your eagle eye on this
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
[MENTION=3756725]kountry83[/MENTION] yessir it can explore 16GB.
[ZTE Axon 7 Guides, News, & Discussion] Cyrus D.:
I made the mistake of flashing the SafetyNet fix on mine that's on Android 7 and that bricked it. It stays stuck at the Axon boot screen. What do I do from here?
[ZTE Axon 7 Guides, News, & Discussion] ramnkc:
Long press volume down and power button until you see FTM mode. Then use the EDL tools to TWRP 3.2.1.0, then boot into recovery (long press volume up and power) and flash Oreo B12 or B01.

And make sure you format everything including internal storage. Else u need to reflash again.
[ZTE Axon 7 Guides, News, & Discussion] Cyrus D.:
I can still access recovery mode, it just won't boot after the Axon logo appears. So I'm safe just installing the beta Oreo ROM then?

The boot stack in the first post is a dead link, should I use this one instead?: https://androidfilehost.com/?fid=818222786056034386

Also, what specifics should I know about the process so I don't brick it? I remember when updating to Android 7 there were several things which could cause bricks including needing to use some extra command before installing any program for rooting. And in the Android 7 thread there were instructions specifically stating to check "Mount system partition read-only" in TWRP as well.
[ZTE Axon 7 Guides, News, & Discussion] agaethwe:
Many thanks for this! I flashed your patch with TWRP, but it didn't work right away - the Daydream app wouldn't launch. I sideloaded the latest Daydream app from APKMirror, and it worked... well, at least it launched.

I'm having major problems with motion blur and distortion in Daydream... if I keep my head still, everything looks great... but if I move my head, everything smears and distorts... it looks like maybe the left view isn't quite property synced up with the right view. It wasn't like this under Nougat, and almost unusable now. I use Daydream a lot, so it's kind of important. Any ideas on how to fix this? I'm thinking maybe because your patch is "Universal" Daydream is not properly configured for the Axon 7? Thanks so much!
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Big thanks to you on appreciating my work and the donation.

I don't receive it much so when I do it makes me want to help out more.

Try to erase cache and data. If that don't work it's either in the settings of daydream app or developer options in daydream settings to force different graphic options. I've been using it and haven't had a problem yet. Maybe just a little glitch or version of daydream VR app. Sometimes the older versions of apps are better.

Cheers
[ZTE Axon 7 Guides, News, & Discussion] Cyrus D.:
Aaaand I didn't realize the disemmcwp command doesn't work on this ROM so any system changes don't stick after reboot. Is there going to be a solution to this in the near future, as in is anyone working on it?
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
A2017X_V2.1.0B12_carrierremover

Make a full backup in case. Or use the revert zip under ozop
[MENTION=8495959]Victor13f[/MENTION]
[ZTE Axon 7 Guides, News, & Discussion] docentore:
Try to Wipe the sd card in TWRP (not partition, but wipe menu)

I had similar issues with my 128gb SanDisk on B01, all fine now
[ZTE Axon 7 Guides, News, & Discussion] agaethwe:
Thanks for the suggestions.

* I erased cache and data in TWRP, installed the Daydream app again, and it still had the same problem with distortion and motion blur.

* Everything looks good in the Daydream app settings -- the correct headset is selected.

* I tried a couple of older versions of the Daydream app, and the problem is still there. It forces an upgrade to the latest version of Google VR Services during installation, though.

* I played around with the developer options in the Daydream app and nothing helped.

* I also tried both "reduce blur" and "reduce flicker" in Settings/Display/Advanced/When device is in VR. Doesn't help.

Btw, I was wrong when I said before that the problem may be due to left and right views being out of sync -- closing one eye doesn't fix it. I now think it's some sort of a latency issue. Still, it may be due to VR not being properly configured for Axon 7. Any way to fix that?

You say Daydream works for you, but maybe you're just less sensitive to this problem then I am. A good way to test is to look at some text in VR and move your head in a circle. For me, the text becomes all distorted with a "seeing double" effect. Also, small bright objects like stars become long streaks when the head is moved.
[ZTE Axon 7 Guides, News, & Discussion] keckek:
My experience is not required to install Safety Net mod. I just intall Magisk 16.4 and everything is ok after checking.
[ZTE Axon 7 Guides, News, & Discussion] Igorperrotta:
I'm having some visual glitches, like static on some apps and in TWRP.
[ZTE Axon 7 Guides, News, & Discussion] 0Kajuna0:
Amazing. Thanks!

Would anyone know how to remove the NFC icon? Maybe the bluetooth one too? Merge the data and mobile signal ones?
[ZTE Axon 7 Guides, News, & Discussion] skdubg:
use systemui tuner
[ZTE Axon 7 Guides, News, & Discussion] Druboo666:
any news on official release other then this ??
[ZTE Axon 7 Guides, News, & Discussion] 0Kajuna0:
Thanks. That's great for hiding many of the annoying icons.

I'm getting wifi and LTE icons at the same time. Pretty sure that was not the case on Nougat. Is it just me?
[ZTE Axon 7 Guides, News, & Discussion] flyer_andy:
In developer options, you can disable persistent mobile data (I think the exact setting is "Mobile data always active"). This setting is likely why you're seeing both the cellular and wifi data icons.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Does disabling encryption fix system not writable?

Seems that all these Oreo roms have problem with not being able to write to system.
[ZTE Axon 7 Guides, News, & Discussion] 0Kajuna0:
You're right, thanks. The fact that it is on by default in Oreo builds appears to be a known bug:

https://www.zdnet.com/article/andro...ing-mobile-data-even-when-wi-fi-is-available/
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
That's a setting in TWRP. Go into TWRP > Mount > UN-check read only system partition option.

Also: you need a tool like "root explorer" from Google play store to then mount System as R/W rather easily. I do it on B12 doing these exact 2 steps.
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
[MENTION=1761257]spideyngo[/MENTION]

Hey bud did you get my message? If so did you try the new mod? It's awesome!
[ZTE Axon 7 Guides, News, & Discussion] wineds:
Are you grounded?
[ZTE Axon 7 Guides, News, & Discussion] Igorperrotta:
Even on battery

If I turn my screen off in TWRP and turn it back on half is static and the other half is normal

In some apps I saw some small details looking like static
[ZTE Axon 7 Guides, News, & Discussion] 0Kajuna0:
Is there a version of xPosed that works with this? I've been unable to find an answer
[ZTE Axon 7 Guides, News, & Discussion] Raffelberger:
Had this too when I dropped my phone once, it's a hardware issue. Pressing on the screen fixes it right? Once I heated up the phone while charging and then pressed everything really hard together and now it's working again, didn't happen in 2 months.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Thanks for your help.

Out of interest, what device, bootstack and magisk version are you using? This didn't help me, I think this setting is for twrp only which is fine accessing system.

But within rom I still can't access system read/write.

This is with A2017U, b12, b12 bootstack and Magisk 16.4.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Just tried this on my A2017U and it doesn't work. I guess you guys aren't using the U model?
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Yes it does work. I'm decrypted right now on A2017U. Try formatting data instead of wiping after you do my steps.

After you do all of the steps disemmcwp your system through TWRP in the reboot menu or use terminal/adb.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
I have no idea what I am doing wrong then because it doesn't work for me, just tried a clean flash and everything.
[ZTE Axon 7 Guides, News, & Discussion] Igorperrotta:
Not really, i just noticed it whne i flashed this rom, and it only happened in twrp and in mi fit app while it was loading. really weird
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
[MENTION=3756725]kountry83[/MENTION] It works to decrypt data. It does work with external 16GB fat32 microSDs. It does

not

work with external 64GB

exfat

XC1 microSDs. I tested 2 brands of exfat 64GB XC1 SDcards: Sanddisk and Silicon Power. Both SDcards appear as corrupt no matter whether: 1. I wipe SDcard in TWRP, 2. format it to exfat in TWRP, 3. format it as fat32 in TWRP, or 4. format it in Android. None of it matters as it is always corrupt. If I just roll back to stock fstab.qcom and reboot, then both 64GB SDcards are auto-magically not corrupt.

All in all, it does not bother me if data is encrypted, at least I can see my 64GB exfat SDcards which are not encrypted. No harm no foul.
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
hmm I formatted my 200gb sd card to fat32 from aparted and it works like a charm.
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
EDL flash one of the B10 or B11 Oreo stacks, but make sure to replace recovery.img with a TWRP 321-6 for oreo img in the EDL folder (rename twrp.img to "recovery.img"). At first boot, make sure to boot into recovery first. Then Wipe data in TWRP and type yes.
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Would anyone be interested in ARCore for our Axon 7?

I'm thinking about implementing it.
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
[MENTION=8495959]Victor13f[/MENTION] You can add it, I linked it in my BKM post with credit to [MENTION=3756725]kountry83[/MENTION]

---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------

<--ditto on my HW/SW. May be a bad system flash? Wipe system and reflash Rom (backup data first). Unchecking read only System should be a persistent setting that carries over into booted Android. Try following my guide to decrypt and install Magisk in post #41. This may be part of the secret formula.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Fresh install followed your steps exactly first with drakenfx fix (linked in your guide) and later the one by [MENTION=3756725]kountry83[/MENTION] and no success.

Now I'm sure there's something I'm doing wrong but usually I am no idiot when it comes to stuff like this :confused:

First time before fresh install i just get stuck on start up with "unable to decrypt" message. Then on second attempt, fresh install i follow instructions and think it works only to boot up and still encrypted.

I will go through steps again.
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
Can you EDL B19 stock and then B19 EDL unlocker?

EDIT: Can you get into TWRP and manually wipe all partitions (except external SC card)? Try flashing the B12 bootloader first. Reboot TWRP, then wipe all partitions, then flash B12 Nfound.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Well I just tried again and this time was the same as before, I successfully follow each step except this time I format the whole of data. I then replace the file in system/vendor/etc and chmod to 0644, afterwards I flash magisk and clear dalvik and cache.

Result: my data partition is ext4 but phone is still encrypted.

What's even stranger is Magisk is nowhere to be found, it installed fine in recovery but it isn't anywhere in the app drawer.

This is all on the back of fresh installing b12 again through TWRP.
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
[MENTION=5199968]Dodgexander[/MENTION]

Format external sd card to Fat32 with Aparted from play store first. Replace fstab and chmod 0644. Then format data. Restart. Then boot back into recovery and install magisk.

If permissions not setting right with chmod 0644 for fstab I can make a flashable zip to replace and set permissions.
[ZTE Axon 7 Guides, News, & Discussion] atakan33:
is format data wipe internal storage ?
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Not whole internal just data partition.
[ZTE Axon 7 Guides, News, & Discussion] atakan33:
twrp file manager didnt see system/vendor only system/usr
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
Make sure in the mount settings system is checked and uncheck system read only
[ZTE Axon 7 Guides, News, & Discussion] gkri:
A flashable Zip will be great! :good::good:
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
[MENTION=3756725]kountry83[/MENTION] I don't think it worked for me, how are you checking phone is Encrypted? I tried what you said and at least Magisk was installed this time.

I go to settings, security & location and here under encryption and credentials it states phone encrypted.

If then enter encryption and credentials it gives me the option to encrypt phone, possible a display error perhaps?

Can't write to system either after a reboot dissencwp
[ZTE Axon 7 Guides, News, & Discussion] blackpac:
Likewise, didn't work for me either, phone encrypted...
[ZTE Axon 7 Guides, News, & Discussion] Igorperrotta:
I managed to recover it. Thanks!

My issue is now another lol
[ZTE Axon 7 Guides, News, & Discussion] 0Kajuna0:
Hi guys, I'm using Ambient Display for notifications. Some times the text shows on top of a black background (inactive pixels) but more often than not, it is displayed over the lock screen background, which makes it really hard to read. Is this a bug? Did I set up something wrong?

Thanks
[ZTE Axon 7 Guides, News, & Discussion] kountry83:
You will know when preserve force encryption is unchecked in magisk and stays unchecked.

---------- Post added at 12:55 PM ---------- Previous post was at 12:53 PM ----------

I'll make one tonight.
[ZTE Axon 7 Guides, News, & Discussion] Cyrus D.:
Am I missing something here? When I use disemmcwp through either the terminal or adb it doesn't seem to do anything, I still can't write to system.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
It appears to be broken on these stock roms, encrypted or not. That's why i tried decrypting to see if it works. It doesn't.

So the section in settings is wrong then.
[ZTE Axon 7 Guides, News, & Discussion] 0Kajuna0:
If I disable the ZTE Locker the background is always black. Not an ideal solution, but better than nothing. Now an additional problem is that notifications appear always in portrait, even if I use an app to force landscape orientation
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
For anyone interested I tried the new universal bootstack from the new lineage os release here. As far as i can see it works fine with b12 and system is now writable.

Be sure to read the instructions about the error message the bootstack gives you in the thread I linked.
[ZTE Axon 7 Guides, News, & Discussion] Igorperrotta:
Here is an example for what is happening to me in some apps:

Starbucks is one app showing this too
[ZTE Axon 7 Guides, News, & Discussion] timmtomm8:
Interesting! Did you do something else to get system writable, or just flashing the new universal bootstack changed this?
[ZTE Axon 7 Guides, News, & Discussion] Senny0322:
Will doing the "encryption fix" make changes to system stay after a reboot?
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
I had already disabled encryption and also tried reboot dissencwp but it didn't help.

But as soon as new bootstack was released I installed it and suddenly system was writable.

In my experience previously this problem has always been about the bootstack but I guess it's possible it won't work also without trying those steps first.

Someone will have to try with a clean flash first.

But now we have fully working aex and los with oreo the only reason really to remain on stock now is stock camera or dolby so doubt anyone wants to.
[ZTE Axon 7 Guides, News, & Discussion] spideyngo:
These are usually symptoms of not being bootloader unlocked. Odd. Question, did you flash Oreo B12 bootstack, magisk 16.4, then the B12 ROM?
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
Indeed. Just flash the universal oreo BL and akaik modifications can be done with a simple root explorer now. Works on betaB01 too ;)
[ZTE Axon 7 Guides, News, & Discussion] timmtomm8:
Yes I can confirm that it is working fine on B01 - with the universal bootstack system now is writable, just using fx file explorer with root (Magisk 16).
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Definitely never been bootloader locked. As I said had this problem trying stock roms on Nougat too and the universal bootstack fixed it for me back then too.

Always a result of the bootloaders that are bundled with the stock roms, always fixed by running universal bootloader.

Whether its something to do with running certain devices (A2017U in my case) with different stock versions not sure. I don't remember having system write disabled in B01 but I did have in B12 which was a beta for my device.

As far the steps I followed prior to using B12, I flashed bootloader, then b12 and then Magisk, although rom includes bootloader anyway so it wouldn't make a difference as long as I flashed magisk last.

Anyway, for what its worth the universal bootloader works with the B12 stock rom - in case anyone wants to stay on stock.
[ZTE Axon 7 Guides, News, & Discussion] atakan33:
i flash los bootstack and cant reach twrp.İ push power putton 5 sc screen and 30 sn screen then phone boots but cant reach twrp tried fastboot flash recovery but still cant reach twrp.Tried edl but windows shows device in DFU mode
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
Look out with the universal LOS bl....the first one was made with the [MENTION=5492451]NFound[/MENTION] twrp3216 that's why 'they' made a new one.... BUT, the new one is running on twrp3210, so....when running previous on twrp3216 it will give you a possible mess....format, pin, password...whatever.

Bottemline, be carefull. If running on twrp3216 and you flash the universal, don't reboot and reflash the twrp3216 (if you were on it) !

EDIT : for those who want their system r/w, flash this universal WITHOUT twrp and your twrp will be unchanged. Of course you'll get the 5sec and 30sec warning : A2017X_universal_O_BL_withoutTWRP (credits to Draken for making the base)
[ZTE Axon 7 Guides, News, & Discussion] Vince313:
Yo,

Can you give me the procedure to flash the universal bootloader without getting bricked please?

2017G on Nfound's b12 and I don't want the warning

Should I flash it from adb?

Thanks, Vince