yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] jrotaetxe:
Hi, otaconremo... (espero que no sea en español....)

In your guide there is a step that confuses me. Is this one:

Step 5 : open your PC's device manager and find out the com port number which your phone is from COM ports & LPT tree.

Code:

Usage: axon7root.exe -p COM4 -b -r

Options:

-p Port number eg: COM8 or 8

-b write boot.img only

-r write recovery.img only

-d dump boot.img and recovery.img from phone(not impl yet)

The step instructs to take note of your com port for further operations but then you put the usage instructions of axon7root that exemplifies the usage with a literal command that would flash boot.img and recovery.img.

Is this command to be executed as step 5 or is a reminder?

Regards
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
hi. Sorry, I haven't noticed you posted in this thread. you should have tagged me so it would notify me.

Have you solved your issue yet? If not, you should issue the command "axon7root.exe -p COM# -b -r" only (replacing the com port number).

I just posted the usage instructions for reference.
[ZTE Axon 7 Guides, News, & Discussion] cc_569:
for axon7backup: http://d-h.st/Ienb is timing out and dead, I have tried as you said by using other browser but it does not work. I don't have vpn installed.

Could you please update this file, also the twpr (download failed after some mb), to google doc or other site ?

Thanks.

In fact, any file loeded in dev host does never work for me!
[ZTE Axon 7 Guides, News, & Discussion] cc_569:
ok I managed to unlock bootloader, install twpr and root from other site.

Thanks and good work for your guide.
[ZTE Axon 7 Guides, News, & Discussion] satish.yarramsetti:
Yes someone please give the file or upload it somewhere else.

---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------

Hey! Can you please give that backup file?
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
I have updated the links to my google drive. you can now download the files needed.
[ZTE Axon 7 Guides, News, & Discussion] cozzysa:
quick question, I have the chinese axon 7 which I just unlocked the bootloader, installed twrp and rooted and im siting on Marshmallow B13.

How would I go about updating to B16?

Does someone have the B16 that I can just flash in TWRP?
[ZTE Axon 7 Guides, News, & Discussion] empat:
Hi!

I would appreciate some help. In trying to root my girlfriends device. It is a Chinese model, bought trough Aliexpress, but it came with a updated firmware. The device is on B15, but I'm not sure if I should consider it a Chinese model or what.

Do any of you know if the method described here will work in my case?

Thanks a lot!
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
You can flash it directly with the latest official chinese version v1.1.0B17 using miflash.

Here's a link on where to get the files, http://4pda.ru/forum/index.php?showtopic=814221&st=1340#entry63517112

Just use chrome or google translate it. You could also search here how to use miflash program for PC.
[ZTE Axon 7 Guides, News, & Discussion] empat:
Thanks!

Just to be clear: I should flash the latest Chinese version, then follow the procedure described here in this post?
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
You can do the steps here only for unlocking the bootloader. But for upgrading to nougat, you use miflash and the file i posted above.

For root, you can check magisk 13.3 thread.

Recap:

1. Enable usb debugging.

2. Unlock bootloader.

3. Upgrade to nougat using miflash.

4. Root using magisk v13.3
[ZTE Axon 7 Guides, News, & Discussion] empat:
Would you please tell me which magisk thread you refer to? I found one directed to version B04, is it this one?

Thanks a lot!
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[ZTE Axon 7 Guides, News, & Discussion] empat:
Hi! Tried to follow the steps:

Instaled Miflash, and trough Miflash tried to unlock bootloader. It was, apparently, successfull. After that, tried to flash B19 rom with TWRP.

Again apparently it was successfull, but it seems this was not the true: after that, for some reason, I was not able to boot into recovery or anything else (I think the bootloader was not truly unlocked).

I had to flash verson B 19 full. It was, however, verson B19 U, american. With that I succesfully booted the device.

In my country, however, this firmware apparently has no coverage for 3g or 4g signal, at last for my carrier.

Any idea of how to proceed? My fisrt intention would be to move to some chinese or european version, with enough coverage, then, if possible, proceed top root the device.

Thanks in advance!
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
You can flash chinese modem to regain your signal.

Is your B19 mm or nougat? Try to search for the nougat modem in LOS thread.
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
I'm stuck in step 6 because I stopped detecting the cell in the device manager of my pc does not already appear the phone I have installed all the drivers of qualcoom in the mobile appears this ...

Your device is corrupt it can not be trusted and will not boot.

Give me menu options

Poweroff

Restart

Recovery

Fastboot

But I gave each one of them and the old legend reappears

The one knows how I can solve this problem
[ZTE Axon 7 Guides, News, & Discussion] rafabrasil85:
See my last posts in this thread. https://xdaforums.com/axon-7/how-to/android-7-1-mifavor-4-2-ota-chinese-t3564288/page23

Maybe it is the same problem that happened to me.
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
yeeeeeeeeeeeeeeeeeeeeeeesssssssssss you are great Tthanks a lot !!! thanks of course to otaconremo !!!

Now I'm going to follow the steps again ... for now only my cell phone appeared but it is more than enough !!!
[ZTE Axon 7 Guides, News, & Discussion] rafabrasil85:
You're welcome. Otaconremo helped me a lot when this happened. Maybe we have to unlock bootloader first? And then write boot and recovery images? I'm still learning too... :D
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
I need another little help after getting it already detects the pc cualcom in my case port 3 I complete step 5 because it is the one that would touch us not? But I do not get it to boot the device installs successfully but after installing I do I continue with step 6 or I turn off and disconnect the phone and I get to step 6 .... because I have had to do 3 times the adb reboot edl for That locate my device I am thick today
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
If it is in qualcomm 9008 in device manager, it is already in edl mode. This is where you use the command axon7root. After it flashes successfully, you should enter twrp. Just long press power and volume up. Hold it until it reboots and let go of the power button if zte logo appears. Continue holding volume up until it opens twrp.
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
thanks for your help, My problem has become much bigger after making the axon7root.exe step -p com3 -b -r and install successfully and do what you have told me has left the blue screen of ZTE with the permanent logo and now the devices manager of Windows does not detect it ... and every combination of keys that I make of volume +/- + power does nothing but restart the phone .... I am desperate ...
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
Try to follow this post and a few posts back.

https://xdaforums.com/showpost.php?p=73414165&postcount=212

Rafa was able to get out of that situation. Also, if you were able to get back your device fine, try axon toolkit instead. Seems like tenfar's tool from my guide is not for everyone.
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
hi,

Thanks I was watching those post before, but without luck, the problem is that the mobile rara vz detects the pc stays with the logo zte restarting again and again does not work in edl mode because it does not recognize the device manager with the mobile off Without turning on the display qusb_bulk without the flashing .... but the axon tools does not recognize me
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
Hold power button+ volume down.

Try running this command in the pc.

"fastboot devices"

If it sees your phone, try restoring your backup files via fastboot with these commands:

fastboot flash boot stock_boot_backup.img

fastboot flash recovery stock_recovery_backup.img
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
I tried that command but it does not do anything it does not recognize the only command that does something and is restart and return to the screen of the zte logo is volume + with power but only restart the axon tools does not recognize neither adb nor fastboot
[ZTE Axon 7 Guides, News, & Discussion] VIFTOKSKY:
I edict myself in case someone has the same problem as me. I got the pc to detect my cell by pressing all the volume +/- + power

The only thing that does not detect neither adb mode nor fastboot only appears the image that I attached as usb with the state qusb_bulk, does anyone know to boot the phone from this state ??

Anything that could be worth a link or something
[ZTE Axon 7 Guides, News, & Discussion] otaconremo:
Maybe try to uninstall and reinstall the drivers. The pc should identify your device as dfu or 9008 mode in that state.
[ZTE Axon 7 Guides, News, & Discussion] Louisthefirst:
Is this method work on zte a2017v2.0.0b13?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Did you use Zadig?

Right-click it, click on Uninstall, tick Delete driver software too. After that hold all 3 keys together (vol and power) until the LED flashes or the device manager detects something. After that your PC should install the driver (maybe not) and the phone will appear under Ports - COM & LPT

If it appears as some 'dfu interface' stuff, you're DFU bricked and you'll have to take your phone apart (follow the 4th category brick repair guide).

If it appears as QDLoader 9008 you might be able to use MiFlash and install the full system on the phone without having to open it up.

Also if it appears as DFU you can attempt to drain the battery completely and enter FTM (some people said they could do this). I couldn't, dunno
[LineageOS Questions & Answers] Avelhinha Falera:
It's very disturbing me, audiofx not function, anyone can fix this bug ? I dont like other mod equalizer, just want pure lineage os , thanks for reply :(
[LineageOS Questions & Answers] bcrichster:
I had same problem, any info on the fix??

Edit: Mine was due to a leftover audio_effects.conf for DSP in device tree

Sent from my PAC 6.0 N9515
[LineageOS Questions & Answers] Safal Oraon:
Just suggestion bro!

if audio fx not working and in the most general case if you listen local music then you can try PowerAmp it has one of the best inbuilt equalizer.
[LineageOS Questions & Answers] Boxylisher:
deleted
[LineageOS Questions & Answers] starbright_:
For me (S5 mini) AudioFX is also not functional, at least not in Bluetooth path. Is this a general Lineage issue?
[LineageOS Questions & Answers] Ibuprophen:
There are reports submitted to the Official Lineage's JIRA regarding a few various issues with the AudioFX in the LineageOS.

The following is just one example:

https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-455

Also, some have found little tweaks and workaround fixes while waiting for the AudioFX issues to be addressed.

Here's some links that may be helpful to you.

https://www.reddit.com/r/LineageOS/comments/67zpcu/audiofx_issue/

https://www.reddit.com/r/LineageOS/comments/5xaipz/audiofx_broken/

https://xdaforums.com/oneplus-one/themes-apps/app-maxxaudio-cos13-cm13-t3355120

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[LineageOS Questions & Answers] kayamokid:
i turned on mono audio in accessibility it worked.
[LineageOS Questions & Answers] jolep:
works for me as well.

But if you turn on mono you will get mono sound:(

Strangely enough on my Galaxy S5 running LOS 14.1 audio fx keeps working if I switch mono on, then off again => this way I can get audio fx with stereo sound

that works until I close the music player => on next start I need to toggle the mono switch again to enable audio fx
[LineageOS Questions & Answers] kurtn:
Did you try vanilla music? Seems to have a better compatibility with audioFX. Sad lineageOS team doesn't care to jerry pick.
[LineageOS Questions & Answers] jolep:
Tried it yesterday. Same result, no improvements.

However, in the meantime I found that Audio FX stops working after each song. I always need switching to mono to get it working again.

It's a pity that this remained unfixed up to now. If there's a so simple workaround, it seems to me that the bug might be easy to be fixed.
[LineageOS Questions & Answers] lifesaver38:
I've got same problem. I have always seen painstags painful with the Equalizer AudioFX in Bluetooth, specialy with spotify. It works on the first piece of music, then turns off when I go to the next. AudioFX indicates that it is active, which is wrong, deactivation and reactivation does not change anything. The only way to reactivate audiofx, which works every time, is to pause the piece of music, then read. Well, it's simple to reactivate, but it's really painful!

Is there a solution to this problem ? I hope !
[X Style (Pure) General] zapty:
Moto germany , confirmed the delay in update scheme due to some last minute issues.

http://m.gsmarena.com/motorola_delays_nougat_update_in_germany-news-23150.php
[X Style (Pure) General] ntkhoa:
Very disappointed as the phone is almost two years old but no major update was done. Google may release Android 8.0 by May.
[X Style (Pure) General] quakeaz:
5.1.1 to 6.0 wasn't a major update? I am not thrilled with the delay, but let's not forget how quickly the MXPE received Marshmallow. The Z line is their primary focus now, that's how it goes!
[X Style (Pure) General] iks8:
cool, only 3 months more to get already outdated 7.0 thanks lenovo
[X Style (Pure) General] datchico305:
Yeah I know I love this phone but moving on to the OPO 3T because of this reason
[X Style (Pure) General] abense:
Fixed that for you.

So typical for moto. They're going to wait for us to do all the hardwork for them, and then roll out an update right around the time that its no longer needed by us.
[X Style (Pure) General] strafer69:
As long as lineage keeps updating the phone I will use it until the phone dies but this will definitely be my last Moto phone.
[X Style (Pure) General] autosurgeon:
Everyone is all pissed but Google just ended support at 2 years sharp on the Nexus 6 and Nexus 9. The manufacturers are still in a 2 year support paradigm related to contracts.
[X Style (Pure) General] Tanker Bob:
This is largely why I went to AICP with 7.1.1 and on-time monthly Android security updates. Plus, a lot more functionality and customization. The same was true with LiquidSmooth when Samsung stopped supporting the Galaxy S3 before. Every device ceases to be supported at some point. That's why we hang out here and work together to extend the life of our favorite hardware. I, too, and disappointed that Lenovo dropped meaningful support for the Pure 2015 last year, but AICP has gotten me over the sting.
[X Style (Pure) General] autosurgeon:
I am betting Google's announcement about killing the Google now launcher factors into this. OEMs now have to build their own launcher
[X Style (Pure) General] Sagar_1401:
We could get 7.1.2 directly also... We never know what's gonna happen anyways but now I'm pissed off by this and I'm surely going to buy nokia phone next time... This is such a disgrace...
[X Style (Pure) General] gemtin92:
I would like to use linageos but rom without fully working moto display is not for me, I bought this phone for this function and stereo speakers. Im ok with android 6, I dont feel loosing some functionality.

Tapatapatap Moto X Style
[X Style (Pure) General] dendron007:
what is not working in lineage? what do you mean "not fully working moto display"?

I am at same situation, would like to use Lineage instead of orig. rom. thx
[X Style (Pure) General] ominousnimbus:
IMO the guy who has regularly said he doesn't think we'll ever get Nougat will be vindicated. The MXPE has been a commercial failure and retailers regularly have it on fire sale for $250 or less - they can't get rid of them. There's almost no chance Lenovo will go out of their way to continue spending man hours on the update this spring if they're "having problems" (more likely, they never started working on an update to begin with).

Purchasing this phone is certainly one of my bigger electronics regrets. If I could go back in time, I'd pony up the extra $100 for a 6P, no question. Now the price differential between a used MXPE and 6P is even bigger than that, which says a lot.
[X Style (Pure) General] autosurgeon:
Commercial failure perhaps but that is Lenovo's fault. They incorrectly thought that the Moto name meant they had no need to advertise.
[X Style (Pure) General] BW2003:
Won't wait. Will buy Mate 9
[X Style (Pure) General] jackpollard:
It's always so interesting to see different peoples opinions.

I'm bought the 6P when it came out. It was a great phone, notice I said was. If you hit the XDA forums you will see loads of; bootloop of death, battery issues. It seems the battery is wearing prematurely and causing non repairable failures. This is the majority opinion of the reason for the failure, but again is only opinion. I kept my phone pristine and a few weeks ago got the dreaded BLOD. Huawei did send me a refurbished phone back; it was slightly dinged, but I sent them a 32gb and they sent me a 128gb back. They didn't offer a loaner, so I picked up a MXPE and have to say I like it so much when I got my 6P back and I've not bothered to do much with it.
[X Style (Pure) General] ominousnimbus:
Well, this may be a case of "the grass is always greener" for me. I wasn't aware of widespread 6P issues, but a bit of research indicates they've sprung up over the past few months.

On paper, the 6P is a slightly faster version of the MXPE (plus fingerprint sensor) that still gets regular updates, whereas the MXPE was more or less abandoned in the software department within 6 months of release. The microSD slot was a big factor that swayed me at the time of purchase, but if I'd known how quickly support would be abandoned vs. 2+ years of continuous updates (even monthly security patches) on the 6P, it wouldn't have been enough.

Of course, if you end up with a bricked paperweight 6P, superior software support isn't going to do you much good. Sorry to hear about your experience.

I will add this: the icing on the cake with Lenovo's non-support is that they void your warranty for unlocking the bootloader and trying to stay up-to-date using custom ROMs. Given that I'm already on my second (RMA) MXPE, I don't trust the hardware enough to lose the warranty, so I'm stuck on Marshmallow forever most likely.
[X Style (Pure) General] jackpollard:
Thanks for the well stated response.

I've not been a fan of Lenovo since the Superfish malware and the rest of the crap they install became public knowledge. But I kind of hoped they would of left Motorola somewhat autonomous but I see they did not. The lack of promised updates is inexcusable, it's a lie plain and simple. The whole bootloader thing, while I personally think is wrong, its my damn phone let me do what I want, at least they tell you up front and don't make you guess.

While not nearly as egregious the fact Google discontinued the whole Nexus line and has Pixel exclusive is somewhat annoying. I can almost understand it from a business standpoint, but you could of at least threw the Nexus crowd a crumb and kept say the unlimited photo thing as a Pixel exclusive and give us the Pixel experience. Honestly, the last rom I was running was 100% N and Pixel modded and I'm OK with MM and the Moto voice is pretty good. I did read rumor of N in May for the MXPE, so I hope thats true.

Some guy is on his 5th rma for his 6P! I'm not sure if he is throwing them out the window, but that's pretty sad.

I suppose bottom line is you can't go wrong with either, they both have pros and cons.
[X Style (Pure) General] GretaLewd:
I bought this phone 15 months ago for 4 main reasons :

Larger secreen than my previous phone

stereo front-facing speakers

design

low price

During that time it hasn't given me any problems and has done everything I wanted from it.

So, OK, it hasn't got the very latest Android "upgrade", but if I was really that bothered I'd unlock the bootloader and install a custom ROM. (I'm out of warranty anyway). But why? The phone works perfectly fine.

To put this into context, I bought a £35,000 car last September. The 2017 models will now get Apple Carplay & Android Auto - but this will not be retro rolled out to my car.

And you guys are pissed off at no updates for a $300 smartphone? ;)
[X Style (Pure) General] BW2003:
I bought mine for $500 and generally its not bad device, but:

1. Battery poor - 2pm and its gone

2. Screen failed - it has red dots and artifacts

3. Camera is poor also and its not wide angle enough

4. 32gb memory is out. The fastest SD card makes phone too laggy

5. 7.0 was my only hope note to change it, but I will.

Using motorolla for 5 years and it failed
[X Style (Pure) General] aybarrap1:
I know there is a lot of bash going on, but take a look at other brands:

Samsung Note 7 battery

LG flagship issues with internal solder

Hawaii Nexus 6p various issues

Many flagships have issues and many have been since the inception of the MXPE. I'm disappointed with the lack of updates, but hardware problems is not isolated to Motorola.
[X Style (Pure) General] s27moto:
i hope to see good update not something like XT925 4.1.2 update
[X Style (Pure) General] aybarrap1:
That is something else I consider. A delayed update to resolve an issue is better than one with issues. I'm still disappointed with the update schedule, but at least there it's still some support from Lenovo. Let's hope that they will up their game (I.e. more frequent updates) for new releases. I have always liked Moto phones but they need to convince me to stick with them over the next year or so.
[X Style (Pure) General] s27moto:
i use motorola phones more than 10 years everything it's fine before google and lenovo comes

i think now time to find new brand :rolleyes:
[X Style (Pure) General] techware7:
1. Battery is pretty decent and the quick charge in this thing is mad fast.

2. I bought 3 of these and screens are fine on all of them.

3. Camera is not poor. Matter of fact I went to best buy and tested all of the android phones cameras (except the iPhones) against the MXP and this thing was the sharpest and clearest of them all. Front facing flash for night shots can't even be beat.

4. You should've bought the 64GB version like I did. I have a 200gb SanDisk class 10 microsd with a bunch of apps and is pretty smooth and snappy.

Sent from my XT1575
[X Style (Pure) General] Neez333:
Yea considering this phone came out as a device with Lollipop on it I would have to say Marshmallow was a fairly large update. But that's just me. As for a may Nougat release, I'm not reading too far into that net hype. Unless the Internet somehow changed into a viable news source now without my knowing.
[X Style (Pure) General] D.Spirit:
I already bought another smartphone which is Smartisan M1L, A chinese flagship with better and more adavnced software than moto's AOSP.

I am just waiting for the 7.0 update so I can sell my Moto X Style at a high price.
[X Style (Pure) General] acejavelin:
I have a serious concern that this will be the end of our Nougat update, and it won't happen... Moto/Lenovo will not likely dedicate resources to replacing the launcher as well as updating to Nougat, at least in my opinion.

I really expect to hear from Lenovo that do to the end of Google Now launcher, the Nougat update will be canceled for the Moto X Pure/Style.

Again, my opinion... not fact (yet).