Official (Beta) Android 8.0.0 V2.10B12 US Version by NFound discussion

Victor13f

Senior Member
Aug 21, 2017
94
128
33
26
Vienna

Need an installation tutorial? Visit the V1.30B01 Thread. Most of the steps should apply, and if they don't I will update the instructions here later on. Do not follow the installation one by one until this line is removed from the thread.​

Thank you again to @NFound for this time releasing the V2.10B12 version of android for our device!


Special THANK YOU AGAIN to @NFound, @raystef66, @DrakenFX, @Oki, @WesTD and to everyone else who has helped with the development of the Axon 7 and with this thread​

Download Link: https://androidfilehost.com/?fid=746163614322267534

What's not working and how to fix it:
Magisk doesn't pass Safetynet? (ctsProfile: False). Download and flash https://androidfilehost.com/?fid=818222786056033454 Thank you @raystef66
Google play store shows as uncertified? The .ZIP above from @raystef66 fixes this as well. Your device is now certified.
How do I disable force encryption? Check post #41 by @spideyngo and check page #5 of this thread for the discussion and for a possible better file by @kountry83
Bad battery life? Flash Jojoc V2.1 or V3.1 module within Magisk or via TWRP V3.2 : https://androidfilehost.com/?fid=962187416754476535 V2.1 : https://androidfilehost.com/?fid=673956719939820457 by @raystef66
AdAway cannot install hosts file: Open Magisk -> Settings and select Systemless hosts.
Need to change location settings? : Download this app https://play.google.com/store/apps/details?id=set.lang.pro or check post #27 by @Dodgexander
Daydream is not working? Check post #23 by @kountry83 Download: Daydream.zip https://drive.google.com/file/d/1Stx5bJh_GXCiY8W2XNkEOkxX5ADO1f3c/view?usp=drivesdk
How do I enable or disable the Navigation bar?: Check thread [A2017G][TWRP-ZIP]NAVIGATION BAR Enabler/Disabler by @raystef66 or Direct Link download for aroma installer
Center clock and remove carrier label: Check post #50 by @raystef66 Download: A2017X_V2.1.0B12_carrier&clock_themer
Remove carrier label only: Check post #87 by @raystef66 Download: A2017X_V2.1.0B12_carrierremover

Need modems, boot or bootstack? Download below by @raystef66

Modems:
ZTE_A2017X_Oreo_V2.10B12_Gmodem
ZTE_A2017X_Oreo_V2.10B12_Umodem
ZTE_A2017X_Oreo_V2.10B12_CNmodem

Boot:
A2017X-O_beta-B12-boot.img

Bootstack: twrp 3.2.1.6 included
ZTE_A2017X_V2.1.0B12_OREO_BootStack_twrp3126


What's working:
Fully working HDR+
GCAM: GCAM
Dual Sims: Fully working

I'll continue updating the thread according to your feedback and my testing.
 
Last edited:

Dodgexander

Senior Member
Mar 31, 2013
622
166
43
What's the difference between them?

I just flashed this version on my U since I thought it would be more suited, coming from the U beta program rather than G.

So far I have noticed out of the box this gcam camera port seems to work whereas on the B01 you need to install Nfounds patch to get even v4.4 of gcam to work.

Biggest negative so far is much the same as the Nougat rom on the U version and something I believe Nfound was trying to work on before he released the ROM; Thats localization issues, you only have a few languages to select from so that means for an app like google maps you can't use an english UK computer voice as the phone thinks you are always in the US. Same if you wanted to use a computer voice to pronounce street names in any language for that matter. Changing the text to speech values in the rom do not affect this as maps uses separate info now.
This has an impact outside of maps too, with some apps defaulting to you being in the US regardless of your current location. It would be lovely if other locales could be added just the same as the Euro B01 ROM.

Apart from that I can't see any differences really, the power manager looks more modern and up to date and there seems to be an option to customise mi-pop, can't remember if that was there before.

I still don't know what to make of this craze right now of HDR+, I've done several tests with the stock camera app and to me when I use HDR+ the image just looks the same without HDR. HDR however looks better. With Gcam and my limited testing its different though, HDR and HDR+ both look better than non-HDR.

I am a sceptic and my guess would be this, despite the apps having HDR+ they aren't working properly with it. Gcam when you used HDR+ or HDR+ enhanced is just taking a standard HDR picture and the stock camera is broken when using HDR+ and only takes a non-HDR picture whilst using standard HDR on the stock app does work. Maybe someone can help me with my findings?

ZTE Stock Camera
Standard

HDR

HDR Auto


Google Camera

Standard

HDR+

HDR+(enhanced)


What do people think?

Edit# also noticed that each time you first open Magisk it crashes, works second time each time though and passes safety net fine.
Edit2# Magisk v 16 just broke for me after a few reboots, v16.4 seems to work better.

Major issue so far is system isn't writable any more, had this issue a while back with Nougat and back then it was related to the bootsect.

Edit3#
Code:
su
reboot disemmcwp
does not make system writable either, just the same as Nougat with this problem.
 
Last edited:

GodOfPsychos

Senior Member
Mar 15, 2014
497
614
0
26
Solingen
I still don't know what to make of this craze right now of HDR+, I've done several tests with the stock camera app and to me when I use HDR+ the image just looks the same without HDR. HDR however looks better. With Gcam and my limited testing its different though, HDR and HDR+ both look better than non-HDR.

I am a sceptic and my guess would be this, despite the apps having HDR+ they aren't working properly with it. Gcam when you used HDR+ or HDR+ enhanced is just taking a standard HDR picture and the stock camera is broken when using HDR+ and only takes a non-HDR picture whilst using standard HDR on the stock app does work. Maybe someone can help me with my findings?

ZTE Stock Camera
Standard

HDR

HDR+.
Wait what? Stock camera has got a hdr+ mode?
 

romeoh

Senior Member
Jul 16, 2010
158
22
0
Dallas, TX
What's the difference between them?

I just flashed this version on my U since I thought it would be more suited, coming from the U beta program rather than G.

So far I have noticed out of the box this gcam camera port seems to work whereas on the B01 you need to install Nfounds patch to get even v4.4 of gcam to work.

Biggest negative so far is much the same as the Nougat rom on the U version and something I believe Nfound was trying to work on before he released the ROM; Thats localization issues, you only have a few languages to select from so that means for an app like google maps you can't use an english UK computer voice as the phone thinks you are always in the US. Same if you wanted to use a computer voice to pronounce street names in any language for that matter. Changing the text to speech values in the rom do not affect this as maps uses separate info now.
This has an impact outside of maps too, with some apps defaulting to you being in the US regardless of your current location. It would be lovely if other locales could be added just the same as the Euro B01 ROM.

Apart from that I can't see any differences really, the power manager looks more modern and up to date and there seems to be an option to customise mi-pop, can't remember if that was there before.

I still don't know what to make of this craze right now of HDR+, I've done several tests with the stock camera app and to me when I use HDR+ the image just looks the same without HDR. HDR however looks better. With Gcam and my limited testing its different though, HDR and HDR+ both look better than non-HDR.

I am a sceptic and my guess would be this, despite the apps having HDR+ they aren't working properly with it. Gcam when you used HDR+ or HDR+ enhanced is just taking a standard HDR picture and the stock camera is broken when using HDR+ and only takes a non-HDR picture whilst using standard HDR on the stock app does work. Maybe someone can help me with my findings?

ZTE Stock Camera
Standard

HDR

HDR+


Google Camera

Standard

HDR+

HDR+(enhanced)


What do people think?

Edit# also noticed that each time you first open Magisk it crashes, works second time each time though and passes safety net fine.
Edit2# Magisk v 16 just broke for me after a few reboots, v16.4 seems to work better.

Major issue so far is system isn't writable any more, had this issue a while back with Nougat and back then it was related to the bootsect.

Edit3#
does not make system writable either, just the same as Nougat with this problem.
Having the same problem like you bro, and the visual voicemail in the phone app isn't working as the previous version B1
 

Nik2424

Senior Member
Sep 18, 2014
171
63
0
No sorry, it's only HDR auto. I incorrectly said it was HDR+.

Anyone know the difference between HDR plus and HDR plus enhanced?

Ps the system not writable is a known issue.
HDR+ enhanced lowers shutter speed so as to capture more light. Downside is you have to stay still longer while taking the photo as it takes more time to capture it.
HDR+ is almost instant with fast shutter speed. Tradeback is lower quality, noticeable mainly in very low light.

I use HDR+ almost always and HDR+ enhanced in very low light situations. That's the only time where it makes a big difference IMO.

If you always want best quality just pick HDR+ enhanced.
 

sprcreative

Member
May 30, 2018
11
7
0
just installed this rom coming from a non stock non rooted phone.
Having 3 issues
-When the device is rebooted it goes in to an error message "Your device software can't be checked for corruption. please lock the bootloader.","error g+xo/ABH"/ and that it will "boot in 5 seconds if no button is pressed". If volume button is pressed it wil go in TWRP otherwise it will just boot up Android fine. Not sure what I did wrong.
-The onscreen navigation buttons keep appearing, i disabled them in settings -features, most of the time they are not there but they keep coming back
-Cannot find Daydream in the appstore, guessing it does not detect my device as daydream supported
 

skdubg

Senior Member
Feb 9, 2010
1,092
319
103
thats are no issues. all is fine

open bootlader = corrupt message
buttons come back of you swipe up from bottom
no daydream support
 

Victor13f

Senior Member
Aug 21, 2017
94
128
33
26
Vienna
just installed this rom coming from a non stock non rooted phone.
Having 3 issues
-When the device is rebooted it goes in to an error message "Your device software can't be checked for corruption. please lock the bootloader.","error g+xo/ABH"/ and that it will "boot in 5 seconds if no button is pressed". If volume button is pressed it wil go in TWRP otherwise it will just boot up Android fine. Not sure what I did wrong.
-The onscreen navigation buttons keep appearing, i disabled them in settings -features, most of the time they are not there but they keep coming back
-Cannot find Daydream in the appstore, guessing it does not detect my device as daydream supported
The unlocked bootloader message is normal. Still haven't found a working method to remove it. Do not try any flashasble zips for different android versions as they can brick your phone.

The on screen buttons I've never had that problem it I'm running the EU version B01. Can't help you with that one.

Daydream doesn't run on betas therefore not showing on the play store or showing as unsupported. Download the APK from a reputable website and it should work flawlessly.
 
Last edited:

sprcreative

Member
May 30, 2018
11
7
0
VR services was already installed, sideloaded daydream & daydream keyboard but as daydream starts up it says device is unsupported with a link and a close button.
I already found out about the /system/etc/permissions/handheld_core_hardware.xml where you can add lines to make it think that it supports VR but it gets overwritten after reboot back to default.
 

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
just installed this rom coming from a non stock non rooted phone.
Having 3 issues
-When the device is rebooted it goes in to an error message "Your device software can't be checked for corruption. please lock the bootloader.","error g+xo/ABH"/ and that it will "boot in 5 seconds if no button is pressed". If volume button is pressed it wil go in TWRP otherwise it will just boot up Android fine. Not sure what I did wrong.
-The onscreen navigation buttons keep appearing, i disabled them in settings -features, most of the time they are not there but they keep coming back
-Cannot find Daydream in the appstore, guessing it does not detect my device as daydream supported
Try this to enable or disable soft navbar : https://forum.xda-developers.com/axon-7/themes/a2017g-navigation-bar-enabler-disabler-t3740817
Reboot
Do give feedback whether it works and on which version device ;)
 
Last edited:
  • Like
Reactions: jomadeto

Victor13f

Senior Member
Aug 21, 2017
94
128
33
26
Vienna
VR services was already installed, sideloaded daydream & daydream keyboard but as daydream starts up it says device is unsupported with a link and a close button.
I already found out about the /system/etc/permissions/handheld_core_hardware.xml where you can add lines to make it think that it supports VR but it gets overwritten after reboot back to default.
Okay, I didn't know about that. I read somewhere that the only problem was downloading the APK. It could be something as easy to fix as the Magisk not passing safetynet. Let's see if anyone releases a fix.
 

sprcreative

Member
May 30, 2018
11
7
0
Okay, I didn't know about that. I read somewhere that the only problem was downloading the APK. It could be something as easy to fix as the Magisk not passing safetynet. Let's see if anyone releases a fix.
Weird indeed as I saw that someone on the EU version did get daydream to work. I think I will try the EU version.
Just found out something new, the controls from my wired headset is acting up, it only activates voice control instead of controlling next/previous and stop/start music. Not tested yet if I can answer a phone call with those controls.