Database Users

Audio drivers went missing during update

I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736

The problem with the phone is it makes no sounds?

gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms

Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?

Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.

It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.

So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1

Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.

Bluetooth issues - how to solve them?

My new A2017G B08 has no problem finding and connecting with my old LG G2 - but when trying to connect it with my trusty Bluetooth speaker, the Axon doesn't even see it. And while I can find the Axon within just 1-2 seconds from my PC with a BT-Stick, the other way around the Axon doesn't see the PC.
I can life with not finding the PC, but what can I do to make it work with the speaker? The G2 has no issues with that either so the speaker's bluetooth does work.

Go into settings/location and ensure high accuracy is selected. It can improve bluetooth scanning.

RobboW said:
Go into settings/location and ensure high accuracy is selected. It can improve bluetooth scanning.
Click to expand...
Click to collapse
That didn't help. Still, the speaker does not show up when searching for devices.

had the same issue ! b09 fixed it

Mine was fine on B04 and B08 and is still fine on B09 but I don't use any old BT speakers, most devices are fairly new. The car stereo is probably the oldest. It dates back to 2010 with a 2012 firmware update on the BT module.

caesar170988 said:
had the same issue ! b09 fixed it
Click to expand...
Click to collapse
Well, B08 is the latest version I'm getting via OTA update. I guess if nobody else comes up with a solution/tips that might work there's nothing I can do but wait for (hopefully) an Android 8 update that has the issue fixed for my device

Eiion said:
Well, B08 is the latest version I'm getting via OTA update. I guess if nobody else comes up with a solution/tips that might work there's nothing I can do but wait for (hopefully) an Android 8 update that has the issue fixed for my device
Click to expand...
Click to collapse
Don't rely on OTAs... If your bootloader is locked just go to the download center, download the B09 zip, put it in the internal storage and go to the Updates tab, it should appear there

Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it.
Even then, the latest on the Australian web site is B04. I got B08 from Germany and B09 from Switzerland. It's an international ROM. I don't download from anywhere but ZTE websites.
We rely on other XDA members finding the updates and posting here that it's available.

RobboW said:
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it.
Even then, the latest on the Australian web site is B04. I got B08 from Germany and B09 from Switzerland. It's an international ROM. I don't download from anywhere but ZTE websites.
We rely on other XDA members finding the updates and posting here that it's available.
Click to expand...
Click to collapse
The download center is basically all of those but unpacked and uploaded to androidfilehost. And all of that is made by @raystef66 . It's not like you're downloading them from some shady Russian torrent website

RobboW said:
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it. [...]
Click to expand...
Click to collapse
Choose an username... said:
The download center is basically all of those but unpacked and uploaded to androidfilehost. And all of that is made by @raystef66 . It's not like you're downloading them from some shady Russian torrent website [...]
Click to expand...
Click to collapse
Guys, I have no idea how to do that and although I did root my G2 I'm not feeling very comfortable updating to anything but the official version for my German Axon 7. Meaning, if updating to the swiss version I'm pretty sure I'd lose my warranty.
Also, I'd need a very basic step by step instruction without too many technical terms (and a link to where to get the file) to feel save enough to do it. It's just that I cannot afford another phone should something go wrong.
So, I'd totally be interested in doing an update to a new firmware version since that might possibly indeed fix my problem (and possibly 1-2 others I have with the phone) - but I'm scared to brick it/lose warranty. Any thoughts on that?
EDIT: I've just checked the ZTE website for downloads and I'm a bit confused... version B10 was Android 6 and version B08 is Android 7.1? So... version B09 is older than mine? Is that what you were suggesting, going back to an older version? Can I even update backwards? Usually devices say something like "The software installed on your device is already the newest version" or something along those lines whenever trying to install a previous software version.
EDIT 2: Found "AXON 7(ZTE A2017G )SD card software package(344070B1405ZTE A2017GV1.2.0B09)N Version" on the ZTE website - but what does "N version" mean? Mine says on its back "ZTE A2017G".

Eiion said:
Guys, I have no idea how to do that and although I did root my G2 I'm not feeling very comfortable updating to anything but the official version for my German Axon 7. Meaning, if updating to the swiss version I'm pretty sure I'd lose my warranty.
Also, I'd need a very basic step by step instruction without too many technical terms (and a link to where to get the file) to feel save enough to do it. It's just that I cannot afford another phone should something go wrong.
So, I'd totally be interested in doing an update to a new firmware version since that might possibly indeed fix my problem (and possibly 1-2 others I have with the phone) - but I'm scared to brick it/lose warranty. Any thoughts on that?
EDIT: I've just checked the ZTE website for downloads and I'm a bit confused... version B10 was Android 6 and version B08 is Android 7.1? So... version B09 is older than mine? Is that what you were suggesting, going back to an older version? Can I even update backwards? Usually devices say something like "The software installed on your device is already the newest version" or something along those lines whenever trying to install a previous software version.
EDIT 2: Found "AXON 7(ZTE A2017G )SD card software package(344070B1405ZTE A2017GV1.2.0B09)N Version" on the ZTE website - but what does "N version" mean? Mine says on its back "ZTE A2017G".
Click to expand...
Click to collapse
You're confusing everything... That is not swiss, it's international. The only thing that COULD void your warranty is unlocking the bootloader, and in some cases people have been able to still claim hardware warranty on their phones by saying that they have not touched the hardware. Also, ZTE provides those updates.
If something happens (it would be basically your fault, such as trying to update with 10% battery or updating with an A2017 or A2017U package) and your phone stops working, just call ZTE and claim warranty. Their update method failed, etc. etc. Although it is borderline impossible to mess up your phone with the stock update method... I think it even tells you that you can't update with less than X% of battery.
The updates are as follows: A2017GV1.0.0B01 to B11 was Marshmallow, and then came A2017GV1.2.0B01 to B09 which is Nougat. I have thought many times that it would have been a lot better if they called them, say, M11 and N09. But this is what we have.
It's not hard at all: Go to the Guides section, there you will find Raystef66's download center. Download the file called A2017G-N-B09 (??), NOT the one under "TWRP flashable Bootstack/Stocksystem images". Those won't work.
After it gets downloaded, connect your phone to the PC. allow MTP transfer from the phone. "Internal Storage" should appear as a folder. If you have an SD card it will appear as another folder beside that on your PC. Open Internal storage. Now that is called the root of the internal storage, where all the folders are located. Just take the zip and throw it there, outside of all the folders (outside of DCIM, Android, and all those).
Then go to the phone, Settings, Update, and select the update.

@RobboW @Choose an username... (thank you very much for writing down all the information on updating the phone!)
Ok, so I did the update directly downloaded from their website. The update worked - indeed though, as somebody else has mentioned elsewhere, the phone now seems slightly slower to react to inputs when scrolling/tapping through the menu. Anyways, that's besides the point.
I tried connecting to the speaker, but still, it does not show up when searching for devices. Interestingly though I tried to make a new connection from my old phone (where I had deleted the connection) and the G2 now also can't find it (although it worked fine when the connection was already set up).
I'm back to trying to get one or the other device connected again. If nothing works, I guess I'm screwed then.

Eiion said:
@[email protected] an username...
Ok, so I did the update directly downloaded from their website - followed their PDF instruction for Update via SD. The update worked - indeed though, as somebody else has mentioned elsewhere, the phone seems slightly slower to react to inputs when scrolling/tapping through the menu. Anyways, that's besides the point.
I tried connecting to the speaker, but still, it does not show up when searching for devices. Interestingly though I tried to make a new connection from my old phone (where I had deleted the connection) and the G2 now also can't find it (although it worked fine when the connection was already set up).
I'm back to trying to get one or the other device connected again. If nothing works, I guess I'm screwed then.
Click to expand...
Click to collapse
Can you find the speaker with your PC?
Did you actually go into the PC's bluetooth settings to allow it to be visible?

Choose an username... said:
Can you find the speaker with your PC?
Did you actually go into the PC's bluetooth settings to allow it to be visible?
Click to expand...
Click to collapse
Sure, I did that when trying to connect it to the PC.
Anyways, I was trying 10-15 more minutes and don't ask me how or why... I did nothing different from all the times before but I finally was able to find the speaker on the Axon 7 and set up the connection. After that I wanted to connect the Axon 7 to the G2 - and while the G2 found the A7 within a second, the A7 did not see the G2. And after that I also tried to connect the G2 again with the speaker which worked as well.
So, all that's left is connecting the PC to the BT speaker - but I guess that's no topic for this forum.
So, thank you guys for your contribution, without I might have given up a few days ago already. Now I made it and have an updated phone. :good:

Eiion said:
Sure, I did that when trying to connect it to the PC.
Anyways, I was trying 10-15 more minutes and don't ask me how or why... I did nothing different from all the times before but I finally was able to find the speaker on the Axon 7 and set up the connection. After that I wanted to connect the Axon 7 to the G2 - and while the G2 found the A7 within a second, the A7 did not see the G2. After I also tried to connect the G2 again with the speaker and that worked as well.
So, all that's left is connecting the PC to the BT speaker - but I guess that's no topic for this forum.
So, thanks for you guys for your contribution, without I might have given up a few days ago already. Now I made it and have an updated phone. :good:
Click to expand...
Click to collapse
Semi-updated... you on B08?
The latest security patch is Dec. 1 and it's on B09. Just informing if you decide to update again

Choose an username... said:
Semi-updated... you on B08?
The latest security patch is Dec. 1 and it's on B09. Just informing if you decide to update again
Click to expand...
Click to collapse
As I had mentioned I was on B08 before the update. I'm on B09 now.

Good stuff, my next suggestion was going to be if you have an option to reset the speaker. No need now.
Sometimes you could get stuck with too many pairings. It's good to delete un-needed pairings on the phone but on a speaker you generally can only reset.

RobboW said:
Good stuff, my next suggestion was going to be if you have an option to reset the speaker. No need now.
Sometimes you could get stuck with too many pairings. It's good to delete un-needed pairings on the phone but on a speaker you generally can only reset.
Click to expand...
Click to collapse
Yeah, I thought of that too and searched the manual for it - but didn't find anything. Then I tried several button press combinations while on or while turning it on... you know, sometimes they simply don't put every function in the manual. But nothing seemed to do it. Or maybe it did - how would I know, it has no display.
But anyways, it works and that's all that matters

@ Eiion,
Have you fixed your phone's problem? I experience the same problem, so have you try other different PC and Bluetooth?

Delete all synced devices in bluetooth list. Then try to sync your device. Seems to work for me.

Killed P9 Lite instead of getting back to live, maybe there is a last chance?

Hello, short Story before. I got a full Hand of non working mobile phones because being full of a hell of viruses.
5pcs. younger ones.
2 Huaweis and 3 Samsungs.
Well so far 4 PCs. are saved.
Getting into the phone wasn´t possible anymore. Data not important so I resettet over the Buttons to original Status. -> Worked fine.
But one Piece which is a Huawei P9 Lite guess it is a single sim? was the button method not possible cause it wanted a Software update and Installation of WLAN failed (EMUI)
Getting into the phone for any informations was also not possible because of all the viruses and not working right ahead anymore.
Well ok -> will use High Suite for stock Firmware -> this mobile phone is not supported and also couldn´t activate MTP as I am not in the phone. So far.
Next Idea -> ok. will take the C900B300 and go back to Marshmallow. From original HUAWEI site.
Took the European Version in German. Did it over EMUI (hold 3 Buttons) and worked so far but when I turned on I was stucking on the WIFI+. Even pressing the button -> further nothing anymore. So I thought -> maybe another stockfirmware useful.
Again C900B300 and then I think I did the big mistake. Took out the sdcard during it was rebooting (HUAWEI was already visible) and now it is big crap. Stucks at HUAWEI. Turning off not possible. This EMUI is not possible anymore. Just with a trick I am able to get into fastboot. Yeah. But what then? Reading TRWP which I know from Samsungs but putting it on with ODIN. ODIN doesn´t work with Huawei. Do I Need TRWP to get it back to normal Firmware? Mobile phone was never customized or anyhting else. just normal stock was on it and is the wish to get a clean back. Resetting to factory was not possible anymore.
So my questions, even I know it is my fault. Any rescue possible?
What could be the best stock Firmware. I Guess it is a single sim from Austria unlocked and unbranded. Would also take Nougat again. Just wanted to get it back to normal working and now I guess I have a big letter holder. Model from the backside is VNS-L31. More I don´t have.
Thanks a lot for any help for my being an idiot. Samsungs are much more easier than HUAWEIs.

Blimey mate,
This really just boil down to what partitions were damaged in your case- Most likely your system and data,
however since you are still Technically running unmodified emui you could manage to sort of salvage it.
The logic is this:
Most custom roms for the p9 lite build on top of emui (patching the system image) rather than replacing it (like the way samsung smartphones do)- so you could flash the rom, it would wipe your phone clean of viruses in the process and then proceed to do a hard restore back to emui.
1.) get your phone into fastboot and flash this twrp http://www.meticulus.co.vu/p/forum.html#nabble-td27
2.) Then flash this rom : http://www.meticulus.co.vu/p/ressurection-remix-for-hi6250-devices.html MAKE SURE YOU FOLLOW THE INSTRUCTIONS ON THIS SITE VERY CAREFULLY
3.)Follow this guide to do a hard restore https://forum.xda-developers.com/huawei-p9lite/how-to/tips-revert-custom-rom-to-official-t3668413
good luck!!! if you have any questions hit me up!

Hi
Hi Exiatron00,
thanks a lot for your maybe solution way. Will do it this evening after work and come back.
Hopefully it works cause as mentioned in other threads -> don´t think that the original owner opened the Debugging so that I can work over a tool. FRP locked is in fastboot. This was already mentioned in other posts which I have read here in the forums.
Thanks for your step by step explanation. Will do it. Hopefully it works. I am really pissed of my own that i was unpatient with the sdcard. That´s a mistake which shouldn´t happen. Anyway it did. So i will try to do everything to get back working again. I am from IT so I am not such a DAU but newbie with HUAWEIs. Most are Samsungs.
Will give Feedback.
CU

If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.

Hi,
well adb for flashing not working as device not found. Hi Suite installed. Guess that the USB Debugging is not enabled. hrmpf.
There is a similar thread of somebody with no enabled USB Debugging.
https://forum.xda-developers.com/nexus-4/help/fastboot-recovery-remotely-enable-usb-t2177440
He writes an solution how to enable in fast boot mode with using N4 toolkit.
Search for a p9 lite toolkit and found this
https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
may could work?
Big **** -> as Long as USB Debugging is not enabled as Long I am not able to Flash TWRP over adb.
If I connect to PC Hi Suite opens automatically. So driver should be fine as pc recognize the phone.
hm?

Got it working somehow
Exiatron00 said:
If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.
Click to expand...
Click to collapse
Hi Exiatron00,
got it working somehow!!!!
Bought a 3 day licence for DC Phoenix where you are able to put Firmware even in fastboot with FRB lock and no USB Debugging on.
So I got the IMEI and Fitting Version which is a L11.
Downloaded it original from Huawei as I still want a original stock Rom not customized which was
HUAWEI P9 Lite Firmware (VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU) only wokring one.
BUT the big Problem is that the apk Android System Web View is missing in the ROM. A known Problem by HUAWEI. Yeah now I am stucking in the Setup wizard like this guy who mentioned also the solution whell the reason of this Problem.
https://forum.xda-developers.com/hu...stuck-initial-setup-upgrade-to-t3498097/page2
So my question now. How do I get the apk on the phone still no USB Debugging? Does anyone have this Version original incl. this apk? Maybe an img. from a running working System?
Only way I am able to put the Firmware on is DC-Phoenix. It is valid still two days. Maybe someone can help me? Please?
So an Image of VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU incl. Android System Web View, so that I can go ahead and use the phone again please?
Thanks a lot.
Kind Regards.

Noob looking for pointers to help with upgrade process

Hi. Been waiting a while to post this, and playing around based on what I see, but I the last change I made to my phone hasn't worked out too well and I don't think I have enough of a grip on the process. I am an ex-computer 3rd level tech support so I have reasonable skills around computers etc.
I bought an Axon 7 (A2017G) in Germany but it got flooded one day when it went down the toilet pan, literally. So I replaced it with a 128 Gb model from China, not really thinking about the software versions. Of course it came with A2017, and more importantly, no ability got OTA upgrades from Android 6.
So recently I've been having some battery life issues so I've changed the battery.
Following guides here, I've managed to get it onto a newer A2017 version and it has taken an OTA upgrade to Android 7. The build number is B13. The boot loader is still unlocked. But it's not very stable and Google Play service has now stopped, and I can't be doing with the unreliability. And tbh although it worked, I can't remember exactly which guide or what steps I followed to do it.
So I want to put it onto a stock G version, which I think seems to be possible, based on stuff I've read here. I don't think I need root going forwards (once this is done) and I'm looking for the simplest method. Unfortunately, due to the length of time it's been live, this forum really is information-overload and I've been reading for two days now and made loads of notes but I'm not really very clear about what I need to do.
I'm quite happy to find and read the right guides but would be really grateful if someone could take a few minutes to just tell me exactly which bits are essential to be upgraded and what steps I do need to follow. If I am confused I can come back with any queries.
I'd be happy to root the phone if it's felt that is a really useful thing but I'm not really a "power user" and I'm OK with standard.
Also I'm assuming any upgrade would receive any future Android releases OTA (if there are any for this phone), but if not that's not too vital.
Thanks in advance...
Geoff

But regarding your situation: You have an A2017 with A2017G firmware, right? Can you tell us your firmware version?
Would you be fine with Chinese firmware (MiFavor 5.2, B17) or prefer stock+ (G B01/B02, U B12)?

Thanks for the quick response, really appreciated.
The firmware is still A2017 version AFAIK, but I don't know where to check. If I go to the boot loader screen it says ZTE/P996A03_N/ailsa_ii and on the next line 7.1.1/NMF26V/20170912.013327
I'm thinking I'd do the change from A2017 to A2017G to get round the annoying junk which came with the Chinese version, and also avoid the Google Play Services problem I came across. It may not be do-able but I thought I'd read it was.
I guess in addition to telling me the steps, telling me exactly which file versions to use would help a lot. I promise to keep notes!
I don't mind which firmware, so long as it works reliably and so long as I can preferably put a G version on it.

of course it's doable, the thing is that you'll need to unlock the bootloader in order to.
If you had trouble with Play Services then it's most probably on chinese firmware, finding out would be as easy as going to Settings, then About phone

The boot loader is still unlocked from when I managed to do the previous upgrade. That took me quite some hours, and it was more by luck than judgement that I got a result. This time I want to better understand what I'm doing.
Not sure what I'm looking at for the firmware, isn't it the versions I quoted above? But the menus (mostly) are in Chinese at start up, and I had to load Google Play and Play Services from the ZTEYR store so I'm pretty sure it is on Chinese firmware.
So if it is, do I just need to upgrade the firmware then the ROM (is that the terminology?). If so which versions would I use?
Ta
Geoff
EDIT I missed the kernel version - which is 3.18.31

OK so I've spent more time reading. I'm coming to the conclusion that I don't need TWRP and I don't need to update my Chinese bootloader, does that sound about right?
Is it right that all I need to do is
- find a G firmware zip file <<< may have incorrect terminology here, would appreciate a pointer to a valid download as I have many but not sure they are the right type of file
- put it on an SD card named as update.zip
- boot into recovery mode
- choose "apply update from SD card"
And, assuming I have used a stock version, will it then update to the latest version (hopefully Oreo) once it's started?
Do I need to do any formats or wipes anywhere in the process? I already have a backup of my stuff, done with AXON7Toolkit.
And can you recommend a version of firmware to go to, or does it not really matter as it'll update itself anyway?
UPDATE: MiFavor UI is v5.0

OK, so there is no real short easy answer to this.
I've used the updates from ZTE since I've had the phone until I soft bricked it.
Zte offer updates similar to this.
Eg: B06 to B08 or B08 to B09 and B09 to B12
The update has to be done in stages.
Some updates you can copy to the internal SD card then go settings > system > update, your phone should detect the updates and tap install.
Some Zip files can be done the same way after changing the file name to update.zip or Ota.zip depending on the instructions.
Some zip files have the update within the Zip so it needs to be extracted.
Make sure you have the correct version software and correct version for your phone.
After the update is done all the data etc will be still in place unless you reset your phone.
All I can say is research, research, research.
Btw if your bootloader is unlocked some updates will fail.
I hope this helps
PS: you can use the method you described as well, just follow the instructions carefully.
In most cases there is no need to wipe or format unless you are using a custom ROM etc.

Excellent, thanks.
Going back a post or two - I re-installed Google Play services but still have problems. Before a reboot it appears in the list of apps, and Play opens, but the sidebar comes straight in and behind there is a message "Error while retrieving information from server [RH-01]" . After a reboot it is no longer in the list of Apps (even when expanded to include System apps), and Play just opens and closes real quick.
So I found a thread which led me look in Settings in Play Store at the Play Protect Certification, which says the device is not certified. So I downloaded the related app and ran it, which gave me a code which I put in web page then entered the stuff into my phone but still no joy. I suspect this is causing the Play problem and I think it'd be due to trying to use Google product on a Chinese firmware (again I'm not sure my terminology is right - I mean whatever the software is which throws up the initial boot screen).
So I think I need to get off the Chinese firmware at the same time as going to a G version, and I'm even less clear on how to replace the firmware than the rest of the process - what files and how it's done.
Going back to the more recent post (Syberclone), as I have already wiped my phone I'm not concerned about keeping data. I understand about doing this is steps - I hadn't thought of doing it that way but it seems very sensible.
I found a post by Raystef66 with loads of links to software - including A2017X_B15_Universal_Bootloader.zip. Does this replace the Chinese firmware and would it work with all zipfiles? How would I apply it? (I was using Axon7ToolKit the other day and that looks quite impressive).
I am still confused over the different types of files and the naming conventions but it's slowly making more sense. Appreciate all advice.
Thanks
Geoff

Personally I use Edl packages much easier imo.
I use Miflash or Edl tool by @djkuz
I have a bad flash help page that explains the process.
The bootstacks etc are mainly for custom ROMs, if you are just looking a factory firmware, Edl's are much easier to install without worrying about bootstacks, twrp etc.
My last Edl update was from Nougat (Chinese Rom)
To Oreo A2017G I had to factory reset after the install though.

Thatnks. Today I've done a fwe more hours reading, literally. This is taking all my time!!
Anyway I decided to follow your advice and found a full EDL of Oreo, which I applied. (ZTE_A2017V3.0.0B17) and the phone is still working, and I've not lost my apps.
However I still have the problem that Play Services won't run. I've upgraded it, followed a few troubleshooting guides, used different versions ( - should I be using the 64 bit one??) but still no joy. If I could only get that going I'd stick with the Chinese firmware. It is looking to me like it can't sync, though whether that's a cause or an outcome I'm not sure. Not unexpectedly, a number of apps will not run as a result.
I haven't done a factory reset yet, I thought I'd ask here first to see if that is likely to fix it or whether anyone has any better ideas.
Despite the time this is taking I'm enjoying learning and am grateful to you all for the responses.

The play store link "device not certified" will happen when you change a ROM from its original.
So I have an A2017G, when I run any other ROM it will show "device not certified" because the link between the phone and the software isnt in sync.
When I was running the beta Oreo from the Chinese my device always had this issue and NFC does not either usually.
There is a play store app version which will work as it should however the certified is still a problem without a work around.
When I installed the G version Oreo to my device the certification is back.
I'm miss some of the Chinese ROM animations tho.
Anyway I hope this helps

I am using an A2017 ROM on an A2017. I've not changed anything else. Maybe I need to update the boot stuff (firmware?).
What I'm seeing is that Play Services always needs to be manually enabled, and seems to drop out and require re-installation sometimes. So I have an apk on my internal memory for quick access.
I'm not sure that the "device not certified" is a cause or effect really.
So I have an apk on my internal memory for quick access. It's the latest non-beta 64bit version for Android 8 - should I try a specific one, e.g. is there likely to be a specific one which matches the ROM? (An older non 64 bit one seemed to give much the same problem)
I'd put up with the problem except I can't run some Google stuff at all (Play Store for instance), and some other stuff is compromised (e.g. I can't get into Waze on my usual ID, I'm guessing Play Services plays a part in authorizing). And I can't install some stuff I'd like.
And I'd still be interested to know which bits require upgrade to go to a G version, if it is do-able and would run trouble free.

There was a play store app that worked on most ROMs.
You are on Oreo now yes?
There was a link on one of the Android pie ROMs that I used, it worked fine.
If you are still having issues you can use an app called Yalp that works like the play store.
I've used it on custom ROMs when the play store app refuses to work.

Yes, Oreo now.
I've put YALP on and that looks pretty good. I now seem to have most things working, and those that aren't I can probably live without.
I use a network tool called FING which reports my phone details, and I think it's incorrect but it's saying in one place it's a A2017U which I don't think is right. But now I am more comfortable with EDL and stuff I'm going to continue to fix this properly but the urgency is now not there. I was thinking if I couldn't fix this I might have to buy a new phone on black Friday!! So thanks for your help.
I'm still not really quite sure why I get Chinese characters at start up and what files I need to change to out a G firmware on, if that is what is wrong, and if it's do-able. I think if I knew how to do that then I could put on a G firmware and matching ROM and I'd be in business!!
The same page offered me F-DROID which seems to offer a whole load of different free apps. Maybe they don't have ads? Anyway I'll have a look.
Anyway, again - thanks!!
Geoff

Geoff I'm glad I could help
I was running the Chinese Oreo on my phone and after selecting English in setting some parts of the ROM were still in Chinese, even some notifications.
I converted to the A2017G Oreo update when it was released.
I miss some of the features in the Chinese ROM tho.

So... without wishing to prolong this... your phone was Chinese (as mine was) and you are now running a Global version and all you upgraded was the ROM? And are you able to use the Play Store and you don't have any issues running apps I - and can you run, say, Google Maps?). Is your bootloader still unlocked and if so is the menu at boot time still in Chinese?
Or have you upgraded something other than the ROM?

I actually have an Axon 7 A2017G here in Australia.
I soft bricked it when I accidentally made a mistake flashing a ROM.
I searched for a suitable stock firmware but I could only flash the Chinese Oreo Beta. It had to be modified to run on my device until the Oreo package for my A2017G had been uploaded.
I've now running the proper software for this phone.

Thanks.
Another couple of hours and I have made a Major breakthrough! I went back over all my notes and checked what i'd done and one thing I hadn't remembered doing was setting the Pay Store to Autorun. So using the Mi-Assistant I have done this, and most of the stuff which wasn't working now is. I am still working on why OK Google won't work, but the list of things I might have to live without is now quite short!! The one major benefit is that my battery life seems to be greatly increased. Boot time is also much quicker which is a bonus but not critical.

Nice, yes battery life is improved, actually the Chinese Oreo Beta has a better battery life than my current Oreo.
I could get up to 4 days out of the Chinese ROM, my current ROM can manage just over 3 days at best.
I have battery saver mode on but not ultra battery saver.
I hope this has been a good learning experience for you?

"I hope this has been a good learning experience for you?"
For sure it has. Back in the days when I was 3rd level computer techie, the best learning came from other experts and from being thrown in the deep end, rather than what they taught you in the classroom!

No Sim Detected

Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.

I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?

Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.

Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault

The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.

Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?

djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?

Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?

@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.