yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Are you saying no signature check is done at all. I tried flashing the latest 0925 nightly, and it failed with a signature verification error. Can I just wait for a newer build and try again?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
Is anyone else having problem with their Android Auto? On a refresh install of Official 15.1 and Gapp Micro, it's giving me a

"Something went wrong"

"Google Play services doesn't seems to be working at the moment"

error.... Anyone have any ideas on what might be causing this? Everything other app seems to work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ASiC79:
[MENTION=319057]Oki[/MENTION] Thanks very much buddy for the package. It flashed and booted like charm!

Just one question:

Google Play doesn't work (won't enable contactless). Complaining about "the device is rooted or altered somehow".

Can we do anything to fix this please?

It was working for 14.1 so I'm assuming that the actual OS 15.1 may well be the issue.

But any suggestions will be highly appreciated :)

Cheers
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Did you flash Oki's EDL package?

Did you change your /data and /cache partition to F2FS?

Did you install Pico Gapps?

Did you install Google Gapps AFTER booting the phone?

Those are the only things I did differently than everybody else.

If I disable my lock screen PIN, it doesn't lock the screen when I enable and disable Airplane Mode, the phone just loses signal. Maybe it has something to do with Privacy Guard? I don't know what makes the browsers crash, though.

I'll do a clean flash after the new update comes out and see if it maybe was my fault,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Megagolgoth:
TWRP 3.2.3 doesn't seems to be able decrypting partition, when device encryption is set. Why?

I found this : https://xdaforums.com/axon-7/development/recovery-twrp-3-2-3-0l-labs-mod-zte-t3841978

The best option seems to format /data in EXT4 and choose the encryption ready TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
There are multiple signature checks. I'm saying otasigcheck has been removed in 15.1. If you have a signature verification error, get me a recovery.log and I'll take a look.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anildzs:
Arrow OS GSI Pie

Hi Oki - How is Arrow OS Pie GSI. I had used the AEX extended, but some how , it was giving low audio sound on Axon 7. Havoc OS Oreo so far seems to work fine. Want to upgrade to any stable unofficial Pie ROM.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Why are you posting this here? Nothing you said has anything to do with LOS 15.1.

Please repost here: https://xdaforums.com/axon-7/how-to/summary-best-pie-roms-to-try-to-moment-t3841784/post77606656
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Here's the relevant bit from recovery.log:

Starting TWRP 3.2.3-0-840f04f7 on Mon Feb 9 03:52:29 1970

I:operation_start: 'Flashing'

Installing zip file '/sdcard/lineage-15.1-20180925-nightly-axon7-signed.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

Verifying zip signature...

I:read key e=3 hash=20

I:1 key(s) loaded from /res/keys

I:comment is 1455 bytes; signature 1437 bytes from end

I:failed to verify against RSA key 0

E:failed to verify whole-file signature

I:Zip signature verification failed: 1

Zip signature verification failed!

Error installing zip file '/sdcard/lineage-15.1-20180925-nightly-axon7-signed.zip'
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
This is a different signature than the one I was taking about. But I've never seen TWRP verify the zip signature. Download the file again and verify the md5.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
There's no md5sum listed. There's an sha256 sure, and I verified that. Also pulled the .zip back from my phone and verified that the copy there matches the original.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Are you attempting to flash a Treblized update over a non-Treble ROM?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Yes. Is that not kosher? I thought it was.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Still, I've never known TWRP to verify the zip signature. No idea about that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Hmm. I installed the 'official' TWRP 3.2.3.0 release - not the ...axon one. Somebody here recommended that. Would you suggest a better TWRP version to use?

---------- Post added at 08:54 PM ---------- Previous post was at 08:48 PM ----------

For what it's worth, I'm not quite sure what bootloader I have. I was on the ZTE Oreo beta (B12), and got an EDL from DrakenFX to render the bootloader I had at that point unlockable. My fastboot screen doesn't show a version after BOOTLOADER VERSION -, and it says SECURE BOOT - enabled (in case that might cause TWRP to try to verify a signature...)

Looks like this:

FASTBOOT MODE
PRODUCT_NAME - AILSA_II
VARIANT - MTP eMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (not including in case that's my hardware's #)
SECURE BOOT - enabled
DEVICE STATE - unlocked

---------- Post added at 09:04 PM ---------- Previous post was at 08:54 PM ----------

Do you think (assuming I can get into EDL mode - seems like I can, the red light flashes when I hit the button combination), that I'm likely to be okay flashing OKI's EDL all-in-one thing? Even if some of his mods (f2fs?) seem 'non-standard', I guess EDL is my friend... ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] roisuke:
I actually did none of those things :confused: But to reiterate; airplane mode on and off brings my phone to lockscreen and I lose signal.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
You can always get into EDL mode. Always. No matter what you flash, no matter how badly you screw it up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
So what is Oki talking about when he says his bootloader has been modified to make it able to boot into EDL mode? He seems to imply that the B12-derived loader from DrakenFX can't access EDL mode. Again, I don't know what bootloader I have (except that I got it from DrakenFX) - but holding both volume buttons and hitting power makes the red light blink and the screen stay black (i.e., it sure looks like EDL mode).

Are you just saying there's always a way to access EDL mode - even if your bootloader won't do it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
There are four ways to enter EDL mode:

1. From Android or recovery, "adb reboot edl".

2. From power off, hold both volume keys and apply power.

3. From power off, short USB pin 2 to ground and apply power.

4. From power off, short the special test points on the mother board and apply power.

1 is generally always available but can be disabled on the kernel and it does require a booting device.

2 is implemented in the boot loader (aboot). ZTE has released some boot loaders that support it and some that don't.

3 and 4 are always available and cannot be disabled, ever.

Oki was probably referring to 2.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pnin:
1. & 2. are way more convenient and user friendly than 3. & 4. if you ask me, which makes Oki bootloader mod preferable to the one pointed in OP. My 2c.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
After clean flashing once more to see if I can help at all, I've found one thing.

For the mobile signal being lost after toggling Airplane mode, you can go to

Settings - Network and Internet - Mobile Network - Advanced - Preferred Network Type

..and change it from 'Global' to 'LTE'.

Upon doing so, your signal will come back. You can now switch back to 'Global'. Give it a couple seconds if it doesn't come back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
its always been an option in some setting as far as i remember.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hubird:
My Do not disturb toggle does not work, it will sometimes flash for a split second but goes back to off.

Is anyone ele having this issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
It seems the problem is with the new OpenGapps. I used one from June I have lying around and it works now! For reference in case anyone run into the same problem in the future.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] adriangb:
Any way to get "ok Google" working on any screen (or even screen off)?

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Never been able to get it to work from off screen but by clearing data on the Google app and seeing it up again it worked no problems. Even with the device locked and screen on.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] adriangb:
Interesting, thanks.

Is there any particular reason why it wouldn't work exactly as it would on the first gen Pixels since we have the same SoC and LOS is an AOSP ROM? Is the always listening function run by another chip or is there some type of software device check?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
From my understanding. I believe there is another chip for the mic that we don't have. It is really low power and allows the microphone to stay on 24/7 without draining the battery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
I tried looking at /res/keys, but it doesn't show up when the system is running. I can see it in TWRP, though. Made a copy and included it here. I was thinking I could somehow import the key for LOS (the LOS download page shows one when you click sha256). Or possibly renaming the /res/keys file insine TWRP and seeing if that gets me past the signature verification. That seems pretty dangerous, though. Espe5since the file doesn't appear in the booted system (i. e could TWRP be mounting it from some secure place I shouldn't have access to...)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Ah, an option implies it can be disabled ;) Any idea how?

Yep. It's right there in Settings. I'm gonna charge up my phone and give it a try. Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkQuark:
OK so I have looked through page after page and I have not see any posts on this. I apologize if I missed it. Is there any sort of guide/reference/suggestion on going to 15 official from the last treble rom nFound did? I know the bootloader, modem and TWRP need to be changed but I am highly concerned about bricking the device if I do anything outside of the exact correct order.

Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheWaterBug:
Here's what I would do:

0. Download all files: latest LOS, latest GApps, universal bootloader and device-specific modem, and (if needed) PARTY tool and TWRP of your choice.

1. You should already have a vendor partition, but if not, I'd recommend the PARTY tool. Split 512MB from the end of the system partition.

2. Flash the latest TWRP, the labs mod, or NFound's TWRP for treble. You can install with regular TWRP, but you cannot interact with the vendor partition beyond that. You'd need one of the other two for that.

3. Wipe system, data (excluding internal storage), vendor, and cache. Flash universal bootloader and modem for your device from this thread.

4. Flash LOS, then GApps if you want. It will patch the vendor and system partitions.

5. If you want root, flash latest Magisk, then reboot to system. If not, just reboot.

6. It should take a while, but boot to setup. That's it!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] killacam1989:
How did you do it buddy?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Axebladewarrior:
The easiest method is to use oki' edl package... You can then install the los bootstack and modem from the OP afterwards if you wish
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Still same issue on the new build. Toggling Airplane made on and off locks the screen and makes the phone lose signal.

Every Browser there is still crash on me while browsing on LTE.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
This rom is by far the best one I tried for my Axon 7.

Thanks [MENTION=5027381]OrdenKrieger[/MENTION] [MENTION=1885052]unjust[/MENTION]fied Dev [MENTION=3044858]DrakenFX[/MENTION]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mb0:
same here about phone signal.

i tried on/off for Airplane mode and phone is losing signal.

but i don't have problems with screen lock.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Try loading any webpage with a lot of images/photos and trying to slow down the browser by tapping everywhere. It happens when the phone gets slow.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
Hello!

I have been using this rom for a week and everything is running great so far.

The only constant issue I keep getting is slow GPS positioning lock.

When I open Google MAps, it takes about 2-3 minutes to get my current position. I was outside in open view.

Usually tracking is faster at my house with wifi on but not in this case as well.

I was on treble before but on a different rom and my location tracking was much faster. anyone have an idea what could be the issue?

I tried changing my GPS.conf file to the one i had on the previous rom under vendor/etc/ but still no luck.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Encryption works perfectly, if anyone is wondering; just flash Nfound's 3.2.1-8 recovery before enabling encryption.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] partofthething:
Just to be clear (and I apologize if this is a dumb question), is there a work-around to get a persistent mac address at this point (maybe by going in with root and writing the /persist/wifimac.dat file or something).

(I'm in the same boat as [MENTION=3114972]Arbelzapf[/MENTION] where my Home Assistant home automation system detects my presence based on my mac address and with a random one my security system isn't disarming like it should.)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
Stuck in DFU mode...

Hi guys,

So I got a A2017G, and I followed the install process of the first post, but still managed to brick my phone somehow after the reboot.

I am stuck in the bootloader, telling me that my system is corrupt.

It doesn't boot in normal mode, the recovery mode doesn't work, I can go to the fastboot mode but can't flash anything, and I can go to the DFU mode but not EDL.

I tried the EDL cable method but it still doesn't want to boot up in EDL mode no matter what I try.

Is there anything else I can try without opening it up or sending it back to the technical support?

Thanks ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Have you tried FTM mode? For me the FTM mode was the solution in this situation.

You can enter FTM mode with pressing power on and vol - when phone is off. In FTM mode the phone is reachable via adb and you can enter EDL mode with "adb reboot edl".

See https://xdaforums.com/showpost.php?p=69604257&postcount=7 for details.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
I think u-dev has some code to fix generating wifimac2.dat finally. I had tried to fix it earlier but selinux is being its usual obtuse pain in the backside.

If you want an immediate fix, then yes, go ahead and use root (or recovery) to write /persist/wifimac2.dat with your preferred pseudo-random mac address. The file format is:

wifiaddr: 0x12 0x34 0x56 0x78 0x9a 0xbc

That is, the literal string "wifiaddr" followed by colon and space, then six hex octets prefixed with the literal "0x". (Thanks for the wacky non-standard file format ZTE).

If you read C code, you can look here for the actual implementation, based on code that ZTE actually used in the Nougat wifi module:

https://github.com/LineageOS/androi...mmit/135c8c0eef62fc8ae3d1b475552fff21b0fec02b
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
I forgot to mention, I tried that too, but no luck, it doesn't boot in FTM mode sadly... :'(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amus76:
When you get the scary screen with the red message, push power button once: you'll get a pinguin. Push the button power again and you will boot lineage or recovery.

If possible, go to ADB: adb reboot "dm-verity enforcing"

It's funny how many people get this problem in a short time, including me: i had this problem since yesterday and managed to get the solution from this thread by pure luck.

Best regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
just check the #2 post of this thread
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] partofthething:
Thanks for the info and the link! So I went in with TWRP file manager and copied files in the appropriate format from the internal storage to /persist/wifimac2.dat (and then when that didn't work I tried /persist/wifimac.dat too). Unfortunately it didn't work; I still get random MAC addresses every time I disconnect/reconnect wifi. I'm on yesterday's build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
I also tried that, but it doesn't boot and comes back to the bootloader.

It looks like there was an issue when flashing the recovery, which messed up pretty much everything.

And since this post bootstack don't have a basic edl mode, it sounds like my phone is just a glorified paperweight...

And there I was waiting for the LOS to become official to avoid this kind of problem...

OP should really provide a proper bootstack or a link to the safer method with EDL, giving a method that can brick your phone so easily is just so stupid, and will end up with many people briking their device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amus76:
Did you really try to push the button power when on the red warning sign? no Linux Logo? for sure?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
https://xdaforums.com/showthread.php?p=77755218

Use method 3. I've already explained this several times. You can use the copper wire method or order an edl cable from ebay.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Selinux may be an issue. Can you boot permissive to check?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Don't pay me any attention. But there's a 26th build with all the fixes on gerrit including generating and storing a semi permanent wifimac.

http://files.nwwn.com/~unjust/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
What about the 28th?

And do they include any fix for the GPS?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
There's nothing special about the 28th I doubt lineage made any changes to ROM since they are more active on 9.0 than they are 8.1 now. As far as GPS I didn't even know there was an issue with it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Just someone pleeeeease tell me when the VR works in low persistence mode, so that I don't miss even a day of it, since I've basically bought this phone because it had Daydream but then due to fixation with using Lineage I've never really been able to use it! :D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kripler7:
I'm having the exact same issue. Android auto will not run at all. Any help would be appreciated.

EDIT: Ah I see its an issue withe the latest GAPPS package. Is it possible for anyone to provide me with a slightly dates package that has a working version of android auto? Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
It stops working after some time. A reboot fixes it.

I will try to grab a log
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Hope it helps.

I'm not the only one with the issue, though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Glad you reminded me. What exactly do I need to install and do to reproduce this blur?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
So I looked into the GPS issue. After replacing my GPS.CONF file, nothing really helped.

The only thing that I had really changed other than the rom was was Bootstack and modem to the one currently in OP.

So I reverted back to this bootstack from NFound and it seems to have helped GPS lock so far.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Mmmm

Could be

I'm running draken's bootstack

Will flash that one and try
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Will post an unofficial build that disables Qualcomm location stack apparently we are behind the other 8996 devices in doing so and I went ahead and switched to the Axon Multy blobs from 8.1.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stagnation2:
Thank you for this!

One note: I couldn't get into EDL mode using the button presses and ADB wouldn't find the phone. The way I was able to do it was to install TWRP Labs and then use the Reboot EDL function.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
You need two/three things:

the Google VR Services;

either the Daydream app by Google,

or another Daydream-compatible app that works even without that installed, such as Sites in VR used in VR → Daydream (not Cardboard) mode.

If you go the official Daydream app route, you will be asked to have a Google account on your phone, and to add payment details to it in order to continue (even if you only install free apps). If this is not something you'd like to do, then you can work around it by adding the line

<boolean name="DaydreamSetupComplete" value="true" />

to the file /data/user_de/0/com.google.vr.vrcore/shared_prefs/VrCoreSettings.xml (or possibly /data/data/com.google.vr.vrcore/shared_prefs/VrCoreSettings.xml - I'm not sure if it's the same as in a multi-user setup), and the reboot and start the Daydream app again.

To switch between the "reduce blur mode" and the "reduce flicker mode" (which makes no difference on current builds, but "reduce blur" is the one meant to enable low persistence), go to Settings → Display → Advanced → When device is in VR → Reduce blur (recommended) / Reduce flicker.

There are also several other VR debugging options in the VR Services, which you can access either by going into Settings → VR settings, inside the Daydream app, or by tapping the wheel icon in any other VR app

You would normally notice that the "reduce blur" mode is working because

with a VR headset there would be no noticeable blur when you turn your head, even quickly

if you look at the screen directly and wiggle it a bit, you should notice some flickering

By the way, in theory even older Cardboard apps should automatically take advantage of the low persistence mode when running using Google VR Services on suitable hardware, so if getting Daydream itself to work proves problematic, you should be able to do it also with an app like the Cardboard demo (but not Sites in VR in Cardboard mode, because that uses its own engine).

If any of my instructions turn out to be misleading, I can also be found on freenode and on Matrix with the nickname LjL.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
So low persistence sysfs is written by the light HAL in 14.1 we used stock light HAL which is probably why it worked. In 15.1 there's a few things to be done. Import ZTE VR changes from B32 which is Nougat. Get the VR thermal config running only when in VR mode, and port low persistence support to the current light HAL. We may also be able to steal marlin configuration for thermal while we're at it. Once I get the changes for next week's build merged I'll test this out. I can go get a cheap cardboard today and use my sony as a daydream remote for now.