Related
Ah safetynet, the thorn in the side of every technical android user who wants to use Android Pay.
It's even worse on a xiaomi device, because once you've been granted a bootloader unlock after waiting for days, you don't want to re-lock it for fear of locking yourself out of the device and having to wait another 30 days before you can get a new unlock permission!
There is a lot of old information around about hiding root, custom kernels, installing things in particular orders and I'm pretty sure I've tried them all - including compiling kernels from scratch with a few different versions of the unlocked bootloader hiding patch.... never getting past the dreaded CTS Mismatch
But all of a sudden I happened on a little known secret found by @kyasu that the build fingerprint is also checked : https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Also, conveniently, Magisk (since v9) patches the ro.boot.verifiedbootstate and related props that SafetyNet checks.
This now gives us two options to enable safetynet regardless of bootloader state.
You will need either a kernel with bootloader state hidden OR magisk, as well as a method of changing the build fingerprint.
This also assumes you've got TWRP installed and are comfortable using it.
Tested on Mi5 Lineage OS 14.1-20170206-NIGHTLY-gemini and various xiamoi.eu 7.2.X and 7.3.X versions:
NOTE: Magisk Hide on MIUI currently does not work (21st July 2017)
This has been widely reported and there are a number of open issues:
https://github.com/topjohnwu/Magisk/issues?utf8=✓&q=is:issue is:open miui
A fix may have been found, not ready to test however:
https://github.com/topjohnwu/Magisk/issues/298#issuecomment-316687923
Magisk:
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
From TWRP install Magisk v13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Restart and Magisk Manager app should be installed.
Hit the test safetynet button in Magisk Manager, if it passes stop here! Latest lineage roms don't need my magisk fingerprint module anymore, they just work.
Otherwise, download this magisk module on your phone: https://gitlab.com/alelec/magisk-ge...2bbf9dc8/magisk-gemini-safetynet-props-v3.zip
In Magisk Manager, go to modules and install the magisk-gemini-safetynet-props zip just downloaded. It should prompt to restart to enable module, do so.
After restart, fire up Magisk Manager and "tap to start SafetyNet check", fingers crossed it comes up Green!
Note: After each rom update you will need to reinstall Magisk in twrp, but the safetynet enabling module above should stick just fine and not need reinstall.
Custom Kernel:
I don't test this as often, as I prefer the Magisk method, however this is an option for people who don't want any kind of root on their phones.
I also don't maintain any patched kernel for miui based roms as the one's I've tried are just too buggy.
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
Install gemini-safetynetpass-stable-fingerprint-20170217.zip
this package is based on gemini-safetynetpass-20170213.zip by @kyasu but only changes the build prop fingerprint, the old custom kernel has been removed:
Install a patched kernel, you can either use my autobuild of a patched latest LineageOS kernel for Mi5 (includes fingerprint fix):
https://gitlab.com/alelec/android_kernel_xiaomi_msm8996/tags (LineageOS-gemini-safetynet-kernel_XXXXXX.zip links)
or recent DragonXia kernels appear to be patched
https://forum.xda-developers.com/mi-5/development/kernel-brand-kernel-cm13-alpha-1-0-t3480663 (LineageOS)
https://forum.xda-developers.com/mi-5/development/kernel-dragonxia-kernel-v1-0-t3546619 (MIUI)
Note: Both the kernel and fingerprint zip above will need to be re-installed after each rom update.
On a related note, if you want to use Android Pay on MIUI based roms, make sure the HCE wallet configuration and permissions are set correctly.
See the following for more details: http://en.miui.com/thread-405166-1-1.html
Once you unlock it once, you can unlock it again without waiting. I just unlocked and relocked my Mi5 about 3 times in a couple days.
Sent from my MI 5 using Tapatalk
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
coronafire said:
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
Click to expand...
Click to collapse
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
I'm not sure on kernels, haven't messed with them on Xiaomi devices.
Sent from my MI 5 using Tapatalk
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
the_poolee said:
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
Click to expand...
Click to collapse
Drats. If basic integrity is failing that's something else triggering the issue. Before I changed the fingerprint I only had cts failing, basic was usually fine. Sometimes a replacement kernel would cause it to fail basic, but I never narrowed down exactly what the cause was.
Works on LOS. Anyway my bank doesn't support android pay yet.
Ulver said:
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
Click to expand...
Click to collapse
Looked into it some more to confirm - I'm quite sure you can't re-lock the bootloader if using anything that's not an official xiaomi rom, ie if using lineage, or even the xiaomi.eu rom, you can't lock bootloader without having a bootloop.
And yeah, I've confimed this method doesn't work on xiaomi.eu rom 7.1.20 or 7.2.16 on mi5. It gets both failed basic integritry and failed cts profile match.
I've also tried on Global Stable 8.1.4.0 with unlocked bootloader and had no luck at all, same error.
This was a clean install, factory wipe, install magisk v11.1. Initially the check couldn't work at all, I had to get google play services updated for anything to work. Then the check operates, but fails on both counts.
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Ulver said:
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
As described by @Ulver if you're on official builds, you should be able to re-lock the bootloader and avoid this issue (although without root I guess).
Aside from that, you definitely shouldn't need the zip I made for the build prop change, as you'll already have a stable build fingerprint
It turns out there's lots of versions of official rom that don't pass safetynet even when cleanly flashed with locked bootloader - xiaomi themselves keep breaking it!
A little search finds lots of references, such as this entire thread, and this post in particular: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=273319&pid=7515203
This certainly complicates things....
Turns out you can't always re-unlock....
To test more thoroughly I decided to flashtool wipe and lock my mi5 to stable release that's reported to pass safetynet; global_images_V8.0.2.0.MAAMIDG
My plan is to verify that it passed when locked (it did), then unlock and just install magisk to see if that worked to hide.
Well, MiUnlock has told me I can't unlock, I logged back into unlock web site and it now says my unlock request is rejected (on same account as I originally unlocked on). So now I have a locked device on global stable and have to wait for re-application to unlock.
FWIW I then allowed MIUI to OTA update itself to 8.1.2.0(MAAMIDI) and then safetynet helper originally told me no, fail on both basic and cts.
Ran it a couple more times though and now it's passing. go figure... safetynet is somewhat unreliable.
tl;dr don't re-lock your phone assuming you'll be able to immediately re-unlock it, it clearly works some of the time, not always though.
Good news, I've got SafetyNet pass on xiaomi.eu (MIUI) rom with unlocked bootloader
In the end it's basically the same as the original LOS method except that as we've all seen earlier Magisk v11.1 isn't working for MIUI.
This win was achieved with Magisk v9 and phh-superuser-magisk-r266-2 with the current Magisk Manager (4.2.6)
As per the screenshot I'm running xiaomi.eu MUIU 8.3 7.2.24 in Mi5
My procedure was:
* dirty flash rom to clean up prior attempts (Install) xiaomi.eu_multi_MI5_7.2.24_v8-7.0.zip
* Install gemini-safetynetpass-stable-fingerprint-20170217.zip
* Install Magisk-v9.zip
* Install phh-superuser-magisk-r266-2.zip
* Reboot.
Simple as that, Magisk Manager shows SafetyNet passing (after asking for root privs on first launch)
I've added a new card in Android Pay, haven't tested at a terminal yet though.
If anyone's interested I previously got SafetyNet passing on MIUI with a custom kernel instead of Magisk, this gave SafetyNet green without any kind of root.
The problem with custom kernel's at this stage is the capacitive buttons (back and app switch) have reduced sensitivity / only work well when the phone is charging. AFAIK this is only really a problem on phones with LGD lcd's (what I have), the other ones might work fine.
If anyone wants to try my kernel instead let me know and I'll share it, I found it to be a bit flaky though.
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
rafix96 said:
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
Click to expand...
Click to collapse
Which version of which rom did you try?
coronafire said:
Which version of which rom did you try?
Click to expand...
Click to collapse
I would definitely would like to confirm this on the latest miui official global dev
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
rafix96 said:
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
Click to expand...
Click to collapse
That's annoying, 7.2.24 is what works for me. It's been my daily driver since, and I've used android pay at a terminal no worries.
Do you definitely have Magisk v9 and phh-superuser-magisk-r266-2.zip ?
Magisk v11 cannot be installed else a dirty flash will be needed.
Oh, I just remembered I've also installed the 'phh's SuperUser' app from Play Store. This is probably needed
After that I opened Magisk Manager, which asked for root permissions the first time (which has to be granted).
@coronafire
Yes i tried everything but i have another one idea, when i come back to home i did MiFlash and then install eu 7.2.24 maybe will work.
Wysłane z mojego MI 5 przy użyciu Tapatalka
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
hklam0 said:
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
Click to expand...
Click to collapse
Just to note, this is only for LineageOS, not MIUI.
Personally I find it easier to not need to replace the kernel and just install magisk, if root isn't wanted it can be disabled in the magisk app.
But yes it's true you can replace the kernel with a patched one, avoiding installing any kind of root.
I've experimented with this quite a bit myself, however to update it requires at a minimum applying a patch/commit to a fork of the kernel source you're starting with and compiling it.
I've got a fork of the MIUI kernel from @Shaky156 with the appropriate patch:
https://github.com/andrewleech/Mi5-...mmit/66cbe734eb15d2508a5c80157a8af38d59373535
and example build script:
https://github.com/andrewleech/Mi5-MIUI8-Nougat-Kernel/blob/master/build.sh
Or there's the original patch by @Sultanxda which usually works as well, I did test this on a LineageOS kernel but this is pretty out of date too by now, and I started from a different forked kernel anyway.
https://github.com/andrewleech/andr...mmit/f8314c10146971979ad26c881be9bd17603c1e7d
Note: You can try this with EU ROMs but I'm not sure if it will work, and won't be testing to see if it works, since I see no reason to flash EU ROMs anyways.
I knew this from day 1, but was switching between various LOS ROMs so didn't have much inspiration to make a guide. Now i'm switching back to Stock-based ROMs (due to other roms having no dolby, no voice capture,...), I'll be making a guide
I'm not responsible for bricked device.
This is a guide for those who are facing issues when trying to flash US, EU stock and stock-based ROMs on the chinese axon 7 (no signal, no wifi, worse battery, or simply not booting after splash screen). Since downgrading is also a part of this guide, I will also be covering how to downgrade Nougat 7.1.1 ROMs back to 6.0.1 Marshmallow.
Important thing to note:
You must be on B13, 6.0.1 marshmallow with stock recovery, and please, DO NOT UPDATE TO B10 China NOUGAT or anything above ! This will cause a lot of problem, as from what I've deduced, US B19 is based on the China B09 update, anything above B10 won't be backwards compatible. and will cause problems like not booting, (or no wifi, signal etc after you recover the boot partition through recovery)
Now, if you're already on Nougat and want to try this guide, downgrade back to Marshmallow using EDL. Try this guide:
- Download B13 EDL (credits to djkuz from 4pda), extract it
- Download and install the latest Xiaomi MiFlash (stable or beta)
- Turn off your phone, plug it in to your PC, Hold Power + Vol Up + Vol Down, go to device manager, look for the "Port" section, and you will see something like Qualcomm HS-USB QDLoader 9008., if you see it, proceed down below. If not try again.
- right click , open properties on the Qualcomm HS-USB QDLoader 9008, go to port settings, if you see the speed is at 9600 bits per second (bps), change it to 128000 (you can skip this step, but doing it will increase your flashing speed)
- Open MiFlash, press select and pick the folder you extracted a few steps ago.
- Press refresh, if you see your device appearing on the list, press flash. (if some random errors appear, unplug the device, plug it back and immediately press refresh and press flash)
- After flashing you'll be back on B13 China Marshmallow.
REMEMBER, DON'T OTA UPDATE IF YOU WANT A SMOOTH TRANSITION TO US ROMS:
Now, to the good part:
- Download the B09 China OTA package from here (credits to Demons-77)
- put the package into your EXTERNAL sd card, internal won't do.
- reboot to recovery (Power + Vol Up)
- select the option with the word "sd" on it
- now go and pick the package that you just put in
- It will begin flashing and after that, you will have B09 China Nougat
- reboot to bootloader and install recovery (fastboot flash recovery *your file name*)
- after that you can install any roms you like, no need to backup and restore the boot partition every time you flash a US ROM, and you won't encounter strange issues like no boot, no wifi, etc.
TL;DR for those who already know how to do most of these: go back to China Marshmallow through EDL, update to B09 China Nougat with stock recovery, install TWRP and then flash whatever US stock or stock-based roms you want (just like how you would with a US phone)
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
otaconremo said:
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
Click to expand...
Click to collapse
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
spiwar said:
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
Click to expand...
Click to collapse
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Fuilares said:
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
Click to expand...
Click to collapse
Downgrading IS a part of this operation if you're already on Nougat (you need to go back to MM before you can go B09 Nougat). Why relock your BL though? Magisk root can work with Android Pay, Pokemon Go AFAIK, not sure though (since I don't use any of those apps)
tigrey said:
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Click to expand...
Click to collapse
Yes that stock ROM will be okay. Personally I'm using the latest version of BadBoyz ROM.
No you can't. Because OTA updates requires the stock recovery, and your phone probably won't boot if you flash the US Stock recovery
otaconremo said:
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Click to expand...
Click to collapse
Magisk won't work if you're using B10 Chinese as a base (as mentioned above), if you flash on B10 you'll have to flash the boot portion from the stock Chinese ROM for the US ROMs to even boot, and then you just lose magisk.
I see. Thanks for the tips. But I don't think I'll be coming back to b13 mm for that. I hate restoring data ang all the files in my internal storage.
Hi!
Could you please clarify me a doubt?
To follow this guide, must my device already be rooted?
Thanks!
Well, first part went well. After a lot of effort, because device was recognised as DFU. Anyway, I got it back to B13 with stock recovery.
On second part, when I try installing the FOTA update, it fails, giving me error: status 8. In update history, it says that the system package did not match the phone. Obviously I have A2017.
Any suggestions?
Here is the new B356 EMUI 5.0.1 modified LRS Rom for Honor Note 8
Boot_Insecure_B356_Fix-adb_dm-verity-v3.img (Thanks to Franzroy from Mate 8 Forum,he make the Kernel for us.)
Debloated All China Apps and unnecessary Huawei Apps
Delete Themes (You can Download online)
Root with Magisk
Busybox
Adblocking Adaway
Rootexplorer
Smaler Icons
Disabled Chinaservice in Video and Musicplayer
Integrated Googleapps Playstore,Contact and Calendar sync
Add Xiaomi Mi Browser-can delete in system/priv-app/Browser
ROM OS Version: 7.0 Nougat
ROM Kernel: Linux 4.1.18
Based On: B356/ Edison AL10
Version Information
Status: Stable
Created :02.Juni 2017
Last Updated :20.Nov.2017
Requirements
Unlocked Bootloader
Twrp installed
Installation Instructions:
You must be at least B352 Nougat and not works from Android 6.0 B017/B022/B029 etc...
Boot to recovery
Wipe all,Data with "yes" Dalvik Cache,Cache,Cust,System,Internal Memory,Data
Install Rom (Takes about 5 min)
Reboot (2 min)
The Phone Reboots 2 Time at the first Reboot,this is normal.
Dirty flash I have not tried!
Downloads:
LRS Rom B350 v1.0
LSR Rom B353 v2.0
LSR Rom B356 v2.5.0
Boot_Insecure_B353_Fix-adb_dm-verity-v3.img Thanks to Franzroy from Mate 8 Forum
SuperSUv2.82-forEmiu_5.zip
Twrp 3.0.2-0
or
TWRP 3.1.0-3
TWRP 3.1.1-1 use for B353 and B356
Many Thanks goes to:
Boot_Insecure_Fix-adb_dm-verity-v3.img from Franzroy Mate 8 Forum
Mother of Adblocking
Chainfire´s Supersu and Tecalote for create the Supersu zip to working for Emui 5
YashdSaraf´s Busybox
Sorry for my bad English!
I have created earlier for Lg or HTC devices Roms Lg G Pro2 and Lg G Pad 8.3 AND HTC Droid DNA
I have always used the name LRS and will continue to use LRS for my Roms
Now I have tried to Honor / Huawei and it works.
If you find a bug, just post it.(Except with the full HD resolution)
Have fun with the Rom.
Warning!
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,etc...
Please do some research if you have any concerns about
features included in this ROM before flashing it! YOU are
choosing to make these modifications
Removed Apps in System/app:
BaiduInput_for_Huawei, HwTrustSpace,
BasicDreams, HwVideoEditor,
FindMyPhone, LatinIME,
HiBoard, talkback,
HwMagazine, UserDictionaryProvider,
HwSpeechService, WatchSync,
HwTrustAgent
Removed Apps in priv-app:
HwChrService, PicoTts,
HwIntelligent, Tag,
HwPhoneService
Download Removed Apps from app and priv-app
The file is flashable,flash in Twrp
Download
Download update_data_full_all_cn_B350.zip
Here is the Rest from removed Apps in data,flash in Twrp
Download
Download System,Cust,Boot,Recovery
You can with this Procedur back to Stock.B350
Use Minimal ADB Setup Download
Download the img Files and unpack it,i packed with 7zip.
Copy the Files in your ADB/Fastboot Folder.
Reboot into Bootloader
Use CMD with the Commands:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash cust CUST.img
fastboot flash system SYSTEM.img
fastboot reboot
Download
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I will try it very soon after unlocking the bootloader and instaling TWRP.
I can always get back to stock, right?(how to do so? will it work from the hisuite ?)
this is exactly what I need
thank you so much
just a question: this is a systemless root, right?
what's the difference between the 2 versions of TWRP?
Yes you can back to Stock.
Install B332 via Twrp and make the B350 ota again,or Backup your Stockrom in Trwp before flash this Rom!
Yes systemless root.
Twrp is newer and older version,the newer version can all Backup the older not
adnansarraj1 said:
I will try it very soon after unlocking the bootloader and instaling TWRP.
I can always get back to stock, right?(how to do so? will it work from the hisuite ?)
this is exactly what I need
thank you so much
just a question: this is a systemless root, right?
what's the difference between the 2 versions of TWRP?
Click to expand...
Click to collapse
Or you can flash the System,Cust,Recovery and Boot img from the B350 via fastboot to go back to Stock.
You can use this Procedur only with unlocked Bootloader!
Insdruction coming soon.
i add the removed apps from system and data in the second post to downoad.Flash in Twrp.
add all the img file to flash via fastboot to go back to stock.
Hi letschky,
Just installed this and looking around, so far so good
Whatsapp and the ability to add user accounts both working (both important to me).
I'll play around for a few days and report any bugs/issues if I find any.
Also no need to apologize for your bad English........ It's a hell of a lot better than my Austrian/German
Danke schoen mein freund.
tiggrr1 said:
Hi letschky,
Just installed this and looking around, so far so good
Whatsapp and the ability to add user accounts both working (both important to me).
I'll play around for a few days and report any bugs/issues if I find any.
Also no need to apologize for your bad English........ It's a hell of a lot better than my Austrian/German
Danke schoen mein freund.
Click to expand...
Click to collapse
Ok,good to hear.
Thank you for testing
sorryone question, you know if with this rom i can re-use fly gps or other fake gps with pokemon go?..sorry but with last update honor have created some great problem
crissyx said:
sorryone question, you know if with this rom i can re-use fly gps or other fake gps with pokemon go?..sorry but with last update honor have created some great problem
Click to expand...
Click to collapse
Do you mean,works this rom with Pokemon go?
letschky said:
Do you mean,works this rom with Pokemon go?
Click to expand...
Click to collapse
yes, with b350 honor have change something that create problem with fake gps or other type of similar apps.
if you try to use you see on pokemon go..impossible to find location
crissyx said:
yes, with b350 honor have change something that create problem with fake gps or other type of similar apps.
if you try to use you see on pokemon go..impossible to find location
Click to expand...
Click to collapse
Do you have give permissions in settings?
letschky said:
Do you have give permissions in settings?
Click to expand...
Click to collapse
of course.. the problem was only in firmware, something was change, ad not only with Honor.
I'm going to unlock bootloader Tomorrow, if possible can you test fake gps or other apps similar with your roms to see if ther's not the same problem.
Thank's
Hi! For me your rom is a good rom! only please, its possible to reinsert a logo 3g 4g H+....? and...I forgot a question: i have uninstalled Yellow pages, the yellow pages are all in Chinese language and are useless. and i have uninstalled huawei home launcher because it's very invasive and i have installed nova launcher, the best for me. after this modify, for me this device is perfect, stable and very fast! excuse me for bad english but I don't know this language. I studied English twenty years ago for only 3 years at school .... help meeee
Nice ROM! But there are no Google apps installed. Also whatsapp notifications don't work. When i open Whatsapp i only get all the messagers. Did I do something wrong? On the first boot i had a screen with Chinese and the word GOOGLE in the middle.
I did have it freeze on me a couple of times and refuse to open a couple of games (Boom Beach and Clash of Clans).
I did a full factory reset on Sunday evening and have not as yet had any other problems, Whatsapp is working fine for me, also 3 different google accounts running fine on my phone too :good:
I also can't not open tradetracker, zanox and partners.webmasterplan links. Everytime i get error ERR_CONNECTION_REFUSED
Oké i installed the rom again and now all the Google apps are installed. I think something went wrong on the first install. I'm going to test Whatsapp notifications now.
I still have problems with tradetracker, zanox, webmasterplan and linksynergy links. Everytime i get this error ERR_CONNECTION_REFUSED on every browser (chrome, firefox ect.). Anyone know how to fix this? Because i use this for my work
I have the same problem ERR_CONNECTION_REFUSED. Why? Whithout this problema rom is perfetto.
sbrazzo said:
I have the same problem ERR_CONNECTION_REFUSED. Why? Whithout this problema rom is perfetto.
Click to expand...
Click to collapse
The problem was the hosts file in system/ect. I used the app Adaway and downloaded the latest hosts file. The problem is gone now
Whatsapp notifications also work now, no need to freeze phone manager anymore. Nice rom letschky!
INTRODUCTION
I posted my configuration before inside a couple of threads. After that, I have received a lot of questions about the same issues. I have also been asked to create a thread so newbies could have an easy way of having an Oreo system up and running in the Axon 7. So I am doing it. Newbies will have an easy entry point to the world of custom Oreo ROMs and a single point to clarify any question. We have a healthy and active Axon 7 scene here at XDA. This guide provides a path to have a custom Oreo system with the latest features available for this device requiring a minimum effort. It applies to any of the 3 Axon 7 flavors: A2017 (China), A2017G (Europe) and A2017U (Americas) with any memory and storage capacity. At this time there are 3 groups of ROMs depending on the Bootstack and GSI support:
1. B32+B10 ROMs use the reliable Nougat bootstack. They are very stable and battery efficient. On the other hand, none of them support dual SIM or HDR+ camera. However they support HDR and Camera2 API.
2. B12 without GSI support ROMs use the Oreo beta B12 bootstack. Full support for Camera2 API and HDR+ but very poor battery performance and stability issues.
3. B12 with GSI support ROMs also use the same Oreo beta B12 bootstack. They also require a separated vendor partition. They share the same benefits and limitations of the previous group. So far they are experimental and the Treble ROMs don't support yet all the Axon 7 Hardware when using them along with a GSI image. They are examples of a Work-In-Progress that is yet to be finished.
WHAT THE HECK IS TREBLE AND GSI?
Since Oreo, all the new devices must have a separated vendor partition to fulfill Google's Treble project requirements. This way the OS is structured in two parts:
1. Treble ROM: includes all the device drivers and vendor related files in the vendor and boot partitions. The Treble ROM is owned and updated by the device vendor or a custom ROM developer.
2. Generic System Image (GSI): Includes the Android OS, it is controlled by Google and allow generic and frequent security and system feature updates directly from Google. It uses the system partition.
So far, custom Android distributions such as LineageOS, Resurrection Remix, AOKP, Dirty Unicorns, AEX, etc... had to create specific ROMs for each supported device. This was painful and it all was depending on the willingness of a developer to maintain a version for each device. Thanks to Treble project, now Android distributions just release a single GSI able to be installed in any device using a Treble ROM. This way they can properly maintain all the devices with a single GSI image by focusing on frequent updates of a single GSI. These custom distributions will also deliver the security and feature updates by Google. So a fully Treble ROM for the Axon 7 will open the door to virtually all the Android distribution out there.
@NFound in the AEX ROM thread) is the only one working in developing a Treble ROM for our device. He has released some incomplete Treble ROMs coupled with non-generic system images. Others like @Kranoner in the Hellsgate Kernel thread or @OrdenKrieger in the LineageOS 15.1 are building and kindly sharing unofficial releases of several custom Oreo 8.1 ROMs that are used in the EDL packages below.
@Victor13f has also created guides on how to install the leaked Stock Oreo 8.0 Beta B12 ROM. I really advise to upgrade to any of the current Oreo ROMs since the current unofficial releases work way better than the previous Nougat versions. The custom AOSP Oreo 8.1 ROMs offer a wider spectrum for tweaking for better performance and battery. Custom kernels are adding full featured and optimized drivers for custom ROMs. They support almost everything, including backported drivers from the latest Linux 4.xx official kernel sources.
BACKUP:
Please note that a dirty flash won't work when coming from any non Treblerized Axon 7 (Axon 7 without the vendor partition). So, if you want to keep your information, then you should do a backup of your data before continuing with this guide. You can use the file manager to move your Documents, Downloads, Music, Pictures, Videos, etc... from your internal storage to an external SD card. You can upload them to a cloud service such as Google Drive, One Drive, MEGA, DropBox, etc. Or use the USB connection to move your information to your PC.
DEVICE UNLOCK:
Unlocking your bootloader will trigger a factory reset, and will delete the internal storage along with all the information in your phone. If your Axon 7 bootloader is still locked, you have to follow this guide before proceeding to the rest of this guide. It works for Marshmallow and Nougat stock phones. Please use that thread to ask any question related to unlocking your device.
INSTALLATION INSTRUCTIONS:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES YOUR DEVICE TO BE UNLOCKED, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
In case you get stuck at any point in this guide, do not panic! There is a straightforward way to go back to stock. Just follow this Unbrick/Restore guide. I've tried to make things as easier as possible for everyone, specially newbies not used to deal with the Axon 7. So, I have created stable custom EDL packages. In order to reduce the risk and complexity, this one Stop ROM Shop performs all the following actions in a single flash:
- installs TWRP custom recovery
- installs my customized Bootstack
- removes unlocked bootloader annoying warning message.
- installs custom Oreo ROM.
- installs google apps.
- installs custom kernel.
- installs magisk root
- creates vendor partition to treblerize your phone, this way it will be futureproof.
- formats vendor partition as ext4 filesystem to complete the previous task.
- And the guide also helps you to format data and cache as f2fs in case you haven't done it already. It provides better battery, performance and extends the lifespan of the internal flash.
I provide here 2 basic EDL package options. Both of them include the vendor partition so you won't have to perform any additional formatting and backup when upgrading to treble roms. Both options are this way future proof, just choose one of them:
OPTION 1: B32+B10 based EDL Package if you prefer stability. It includes:
- N+O custom Bootstack (B32+B10)
- TWRP 3.2.1-7 recovery by NFound
- Resurrection Remix Oreo 6.0.0 2018.05.11 ROM By Kranoner
- Google apps (ARM64, 8.1, micro)
- HellsGate v3.0 Kernel by Kranoner
- Magisk root 16.7
OPTION 2: B12 based EDL Package If you require dual SIM or full support for HDR+ camera apps. It includes:
- O custom Bootstack (B12)
- TWRP 3.2.2 recovery
- AEX 5.7 20180711 ROM by NFound
- Google apps (ARM64, 8.1, micro)
- HellsGate X12 GClang Kernel by Kranoner
- Magisk root 16.7
Once you had chosen your preferred option then proceed with these steps:
Download and Un7zip the chosen package to a folder in your computer, ensuring there are no errors. I have an A2017U, so the American modem is the package default. If you have an A2017 or A2017G just copy your modem firmware, from the corresponding provided modem subfolder, to the main folder. Just overwrite the default American modem file.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest Qualcomm drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
While your phone is completely off, press VolUp+VolDn while connecting your phone to your PC.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now, from the main menu > Wipe, select and clean dalvik.
NOTE: If you receive an error while formatting data, then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.
Go to main menu and reboot system.
Complete the setup process so you can continue with the rest of the customizations not included in the basic package:
SOUND EXPERIENCE:
The following steps will provide you with Dolby ATMOS and Viper4Audio pre-processors along with the HiFi DAC output. 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. The steps are:
Download Mixer_AK4490.zip and Dolby-Oreo.zip to your phone.
Open Magisk Manager app, go to the Download section and Download (do not install yet) Ainur Sauron, Viper4Android FX and Audio Modification Library.
Reboot to recovery the same way you did during System installation, press install, navigate to /sdcard/MagiskManager folder and install Ainur Sauron, Viper4Android (I prefer 2.5.0.5 and traditional interface, however it is all up your personal preference) and Audio Modification Library zip files in that order. Do not reboot after flashing these files, just navigate now to the /sdcard/Download folder and flash Dolby-Oreo.zip and Mixer_AK4490.zip
SCREEN COLOR ENHANCEMENT:
Download and install KCAL Color Calibration/enhancement app. I only modify the Saturation to 62 to get amazing vibrant colors from this AMOLED screen, nonetheless this is a very personal configuration. At the end this has to please your own eyes. . This app optional since Kernel Adiutor and EX Kernel Manager apps can also configure Qualcomm SoC Color Control.
AVOID BATTERY DEGRADATION:
Install Battery charge Limit [ROOT] app. Open it and set Limit charge to 85% and recharge below 79%. Do you want to avoid your battery to wear as the time go by? do not miss this guide to understand why this step is so important for the health of your device.
BETTER CAMERA:
+ Snap Camera App
I am using, and heavily recommend the paid version of Snap Camera HDR. It supports Camera2 API with full manual and HDR support. Find recommended settings here.
Testing now GCAM v4.0. Nonetheless so far I am just starting testing.
Bacon Camera is another Camera I am now actively testing.
The next level of this guide will provide with instructions on how to change recovery, ROM, kernels and all the details and options you have. It is late today so I'll finish it later.
Hope it helps. I will be updating this guide in the future as soon my configuration changes or I find new technologies, apps or patches. If you know about a better option just post your suggestions!
Thanks and credits go to @NFound, @Kranoner, @Infy_AsiX, @roisuke, @Skrem339, @djkuz and you too for bringing up issues and valuable solutions.
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
kitcostantino said:
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
Click to expand...
Click to collapse
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
This was actually why:
NFound said:
TWRP Exclusive™
For "U" models pacth cleaning inscriptions bootloader NO BET!
Warning! "Del Inscription" - only for A2017 and A2017G !!!
Click to expand...
Click to collapse
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
kitcostantino said:
This was actually why:
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
Click to expand...
Click to collapse
Well NFound just tried to say that his solution was not tested at that time in an A2017U. Actually the 2017U is unbrickable thanks to the hardware EDL mode of the Qualcomm SOC.
By the way, I have updated the OP. Now it matches my current configuration. I have also mentioned my current testing efforts in the battery and camera areas.
Regards
Hi. Any fix for Dual Sim? I read through XDA and it seems dual sim is still not fixed. I am getting tired with nougat ROMs but without dual sim I have to stick with it...
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Dave_XDA said:
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Click to expand...
Click to collapse
Yes, the guide is valid for any Axon 7 flavor: Chinese, Euro and Americas.
marcdw said:
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Dave_XDA said:
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Click to expand...
Click to collapse
There is no problem as long you have an Oreo Bootloader. Since you are already running a custom Oreo ROM it means you already have a valid bootloader. Thus, you only need to flash the RR-O ROM. Should you find any problem you can just flash the latest bootloader I link in the OP or go back to AEX. It is important to do a clean install when switching Oreo flavors, as you plan, otherwise you will face problems.
Thanks for this. Been running stock since I got the phone, but missing the old phone days where I used to flash something new like once a week. Gonna try this out tonight I think. Really appreciate the concise directions
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
amphi66 said:
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
Click to expand...
Click to collapse
No issues, you can always go back to B35.
Oki said:
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Click to expand...
Click to collapse
Thanks for the info.
Never used/explored TWRP Exclusive's extras really. In my environment I might break something [emoji39] but cool that everything is there.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
How long does the first boot after flashing the bootloader take? I don't seem to get past the ZTE powered by android screen.
Never mind. Just hold Power + Volume Up at boot.
Thanks !! Oreo AND RR together !!
I will flash it tomorrow on my A2017G !!
(maybe you should write the A2017G compatibility on the first page because this :
RR-O-v6.0.0-20180422-axon7-Unofficial.zip
for the ZTE Axon 7(2017U), by Kranoner
on androidfilehost almost made me missed it )
EDIT : Does this ROM+kernel have the dualsim problem ?
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
ashishv said:
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
Click to expand...
Click to collapse
What have you really done my friend? This guide requires a complete cleanup so it is impossible that you had any locksettings after a clean install. If you follow all the steps and follow the guide then you shouldn't have any problem.
The lock settings get corrupted after migrating to f2fs, and you can also find that problem when dirty flashing some roms or kernels. For that reason, to take care of that step, in the f2fs migration link, there is a link to a very detailed way to cleanup the lock settings. You can find that guide here: https://forum.xda-developers.com/axon-7/how-to/guide-access-locked-axon-7-how-to-t3525403 but, it shouldn't happen when following the steps of this guide. By the way, this guide requires RR Oreo ROM, and you mention you are using AEX Oreo...
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Special THANK YOU to @NFound, @raystef66, @DrakenFX, @Oki, @WesTD and to everyone else who has helped with the development of the Axon 7 and with this thread
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlocked bootloader message removal:
Have not found a working method yet.
Always backup your intSD before flashing ROMs and other TWRPs (Recoveries)
Stock user, need to install TWRP?
Flash TWRP 3.2.1-0 https://androidfilehost.com/?fid=673791459329066789 by @raystef66
If you already have TWRP installed, any version will do since the ROM will replace it with TWRP 3.2.1-6 after installation.
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Do a full backup!
Wipe to perform a clean install. Recommended.
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which modem you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM.
Flash the safetynet fix linked below.
Wipe Cache and Dalvik
Reboot
Edit: Changing partitions to ext4 might be necessary for some non-stock users on f2fs.. Still updating
What's not working and how to fix it:
Magisk doesn't pass Safetynet? (ctsProfile: False). Download and flash https://androidfilehost.com/?fid=674106145207489292 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? Go to post #63 by @DrakenFX
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.
Daydream is not working? Check post #23 B12 Thread by @kountry83 Download: Daydream.zip
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
How do I remove the carrier label and center the clock on the status bar? Check thread [PATCH][A2017X V1.3.0B01] Remove Carrier & Center Clock by @raystef66 Download: A2017X_V1.3.0B01_carrier&clock
Remove carrier label only: Check post #342 by @raystef66 Download: A2017X_V1.3.0B01_carrierremover
Need modems, boot or bootstack? Download below by @raystef66
Modems:
ZTE_A2017X_Oreo_V1.30B01_Gmodem
ZTE_A2017X_Oreo_V1.30B01_Umodem
ZTE_A2017X_Oreo_V1.30B01_CNmodem
Boot:
A2017X-O_beta-B01-boot
Bootstack: twrp 3.2.1.6 included
ZTE_A2017X_V1.3.0B01_OREO_BootStack_twrp3216
What's working:
Pretty much everything other than what I wrote above it seems. The ROM is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. Fixed by Jojoc V3.2 by @raystef66. Link above.
Testing Camera...
Working HDR+ Patch by @NFound: : HDR+ for v1.3.0 B01
GCAM: GCAM
Flashed an older version of that HDR+ Patch by @NFound and does your Magisk not pass the safetynet anymore? Flash this safetynet fix by @raystef66: A2017X-V1.30B01_safetynet_fix_HDR
Dual Sims: Fully working
I'll continue updating the thread according to your feedback and my testing.
Victor13f said:
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Thank you @NFound once again for your hard work!
Thank you @Oki for having written https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693 If you need a better guide visit this thread and follow this guide simply using different files and not installing the bootstack separately.
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlock boot message removal:
If you want to remove the unlocked bootloader message at boot, you just need TWRP Exclusive. Just boot to recovery and go to the Advanced Menu -> More -> Del Inscription. You must to do this every time you update the bootloader. Thank you @Oki
Need to install TWRP?
Flash TWRP exclusive by @NFound https://androidfilehost.com/?fid=673956719939822011
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP or ADB: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which bootstack you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM or with TWRP Exclusive go to Advanced -> More -> Root -> Magisk
Wipe Cache and Dalvik
Reboot
What's not working?:
Magisk root doesn't pass Safetynet (ctsProfile: False). Tested with V16.4, V16.0 and V15.3. None of them passes the safetyNet. Have also tried installing the props module to no avail.
Google play store shows as uncertified (yet all the apps are available and install with no restrictions).
Battery charging light turns off when I turn the screen on and turns back on when the screen is off (Maybe it's intended to be like that, not sure)
What's working:
Pretty much everything other than what I wrote above it seems. The rom is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. I haven't tested the dualsims yet but I will soon and I'll post the result here.
Testing Camera...
I'll continue updating the thread according to your feedback and my testing.
Click to expand...
Click to collapse
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Cool, an easy guide to get you started.
Thanks man.
GabbaGandalf42 said:
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Click to expand...
Click to collapse
I belive the link is allowed. A Forum mod said so on NFounds AEX thread.
I didn't snatch anything. I used guides that exist because they work and I gave props to every single person I could think of. I never claimed this was all my work. Just trying to help other people who want to try the ROM or are interested in how it performs.
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Can /system be mounted as RW in this rom?
blackpac said:
Can /system be mounted as RW in this rom?
Click to expand...
Click to collapse
You can edit system just from TWRP.
mickey36736 said:
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Click to expand...
Click to collapse
Didn't work unfortunately. Edited the ro.build.fingerprint and it still failed safetynet check.
SAFETYNET-FIX
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4 and 16.0
raystef66 said:
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4
Click to expand...
Click to collapse
Thank you, it works
all set up and running
Predatorhaze said:
all set up and running
Click to expand...
Click to collapse
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
battery dont know yet,but i dont use any sound mods on stock rom.Didnt try substratum.....i can try,but not gonna use it
GabbaGandalf42 said:
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
Click to expand...
Click to collapse
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Victor13f said:
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Click to expand...
Click to collapse
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Two questions please:
1. would flashing no-verity-opt-encrypt do anything for this ROM? as in, making encryption optional?
2. would it be a good idea to flash FASTBOOT_UNLOCK_EDL_N if I want to change my recovery now that I am no longer on N?
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Substratum works, used swift black theme 8.0 pixel or nexus
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Batterywise, I flashed the jojoc battery module and it's looking a lot better already
Here is working fine but how do I remove the operator name from the status bar?
Battery is absolutely horrible, coming from a beta tester. If you experience terrible battery it isn't a problem on your side, it's the beta rom. At best, I get barely 3 hours of screen on time only browsing Facebook