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!
Related
Hi all,
I just ordered the A2017 from aliexpress.
I have a question : once it arrives, are there any advantages of flashing the US or EU firmware as opposed to staying with Chinese firmware?
Also, I searched and found many threads that say the Chinese version doesn't have capacitive buttons, but the seller claims the phone does have them (it's the 128GB 4GB RAM version) so which one is the right answer?
Thanks a lot.
The 4gb ram 128gb rom has the buttons like the 64gb model. They don't light up.
Also, before flashing any other version of firmware, you MUST unlock your bootloader...
Thanks for letting me know
Yeah thanks, but what are the advantages of flashing another firmware?
None as far as I know, the Chinese version, aside from having Chinese apps included and no google looks to be fairly stable.
The European verion seems to have a few limitations due toregulations there - the most annoying I've seen is the earphone volume limit - and the US seems to have some translation errors (odd they aren't in the Chinese rom) but is the easiest to unlock bootloader and has some developement for.
Ultimately, if you cn unlock your bootloader, make sure you keep a copy of your boot image and recovery in case of problems, you can go to what you want.
Mixing boot images and recovery images is a bad idea however as it seems to cause issues with WIFI and could cause other problems too...
Chinese update
Excuse if I bump this. Bought a mobile in China with data below. Works like a charm, WiFi and GSM is as Galaxy 6. Sound is very good. Camera could be better, especially in dark environment. When I try to update, I get the message that it is already up to date. Are there no more updates for the Chinese version?
Version is zte A2017CTJMV1.0.0BM1
Yes, I have B13...
Go to this thread - http://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
Update to B11 by putting update.zip on sd card. You will probably loose the ability to boot after this so BACKUP everything you want to keep onto an sd card from internal memory.
Update, if you get a message after it restarts asking for a password you'll need to format data (Again, BACKUP 1ST) . Do this in recovery.
You should then be able to update to B13 through update in settings.
Now, you will need to, after 1st reboot, go to ZTE marke and enter "Google Installer". Install gmail, play store and Google Play services.
After installing all these items, find Mi-Assisstant in your apps. Select Auto-run. Tick the above installed google apps . Log into Gmail, it will say you need to update play services. It won't be able to do it for about an hour. Keep trying then you're back to the latest stock rom...
I believe the rom has been altered if it came with Play store and google installed, thats why you can't update...
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
SlickRobie said:
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
Click to expand...
Click to collapse
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Choose an username... said:
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Click to expand...
Click to collapse
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
SlickRobie said:
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
Click to expand...
Click to collapse
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
It may help understanding to know that there are 3 models.
A2017 is the Chinese one, A2017U is the American one and A2017G is multinational/European. There are different telephony frequency bands in use around the world and the Chinese one also has different storage and memory. A bit bummed they held that back from the rest of the world.....
Choose an username... said:
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download [https:// androidfilehost.com/?fid=457095661767137840]this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
Click to expand...
Click to collapse
Thank you for quick response.
Yes, you are correct, warranty is non-issue anyway and I will make sure it is for A2017 (not A2017G/U). Wish I had just checked the back of the phone then I would not have ended up here but it is nice to learn new things, however painful..
Thanks for the heads up on the process as well. There goes my weekend but the boss (wife) is away so it is okay.
I will report if I manage to get it working next week. Wish me luck.
Robie
Update.
I spent the weekend on this and sadly didn't get anywhere. I followed the instructions and download from here:
http://https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873.
Unfortunately, no joy. I can get my phone in EDL mode (drivers downloaded & suetup successfully, COM port is correct, etc) but the following commands just sit forever. They don't respond at all.
axon7backup.exe -p COM# -d
axon7root.exe -p COM# -r
Not sure where to go from here. If anyone has any ideas then please let me know.
Thanks.
Robie
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.
First of all, forgive me for being cognitively impaired when it comes to things like this. I work in marketing and can't code or follow instructions very well.
Here's the deal:
I made the mistake of buying a Chinese Nokia 6 way back, and now I want to flash it with an international ROM before giving it to my niece. Which international ROM it gets doesn't really matter so long as it has Gapps. Since my niece is three years old, she won't care if the phone has Nougat, Oreo, or Pie as she's likely to be more interested in eating those pastries rather than having one as the firmware on her freebie phone.
First of all, I just updated to Android 9 before I began working on this little project. That might have been my first mistake.
Anyway.
I started by following this guide. I wasn't able to get OST LA to work so I gave up.
Then I started following this guide, as it seemed to involve less work.
I downloaded all the relevant files;
renamed them;
put them on my SD card;
went into recovery mode;
installed the update
rebooted the phone and;
installed the firmware.zip
However, after the installation, the phone never goes further than the Nokia-logo. I can reboot all I want, but it's stuck. I can't even get into recovery anymore. I believe this is a bootloop? The main issue here is that I am completely locked out of my phone, and that is really annoying.
Any tips or ideas on how to get away from this unpleasant conundrum would be greatly appreciated.
Ok, an update.
I was able to find a way to access the damn recovery menu after following the steps proposed by viennazar in this thread.
Similarly, I did a wipe as per his instructions, and rebooted the phone after that. Lo and behold, my phone was able to move past the Nokia-logo, and booted up as a TA-1003!
Now, my main issue is that I am unable to move past the initial setup as the phone is checking for updates from Google's servers. That means I am fresh out of luck since I have the great misfortune of residing in the PRC.
That's an entirely different issue though...
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse
UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse