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!
I recently got a contracted Exynos S10 and have been reading some of the horror stories here after failed root etc
How stable is the S10 after root/unlocking bootloader? magisk is pretty cool , aye
Should I root it?..
Horror stories come from people whom don't do research and follow instructions slowly and carefully, and not confident.
And make it out as its the actual root that's the issue, not them.
I got my s10 plus just 4 weeks ago, i read up for few days, watched videos, understood how root is different slightly to past models.
I found this video which is excellent to help understand about unlocking bootloader and rooting.
https://www.youtube.com/watch?v=o3a8YnWT3yk
Thou i used only how to unlock bootloader from this video, after i downgraded back to pie from ten, then installed a stock with twrp and magisk already patched with superb help from the member, Comsite:-https://forum.xda-developers.com/s10-plus/how-to/root-unsuccessful-everytime-t4042427
Then if you want to get rid of ugly bootloder warnings splash screens, go here:- https://forum.xda-developers.com/galaxy-s10/development/g97xf-soldier9312s-splash-screen-t3929748
Yes rooting is different, but take your time and go for it, so many benefits from rooting for personal reasons :good:
It depends. If you are fine using the phone without Samsung Pay and OTA. Is worth it.
Umbrellaus said:
It depends. If you are fine using the phone without Samsung Pay and OTA. Is worth it.
Click to expand...
Click to collapse
But is it stable. I find the S10 unusable when Ive got too many background apps running or do something else it doesn't like. Nearly every phone Ive owned has been rooted so I know abit about it.
Ok so I wanna root my S10 ,but when I reboot to download mode (OEM unlock checked) I hold volume up but I don't get a prompt to unlock bootloader, also, i can't enter recovery or download manually , bixby + vol down/up & power. Any ideas??
Success!
I tried to install official twrp in the thread. Big mistake. Nearly killed my S10
It wasn't untill I flashed stock including stock ap file from Odin that I could flash magisk, kept saying only official firmware can be flashed to this device or somethin... :silly:
In my personal opinion,
- 5 to 10 years back, rooting has lots of more benefits
- currently, there are many alternative solutions to rooting for ad blocking, freeze apps etc.
I did not root my phones after S8 and now s10+.
Tiongkia said:
In my personal opinion,
- 5 to 10 years back, rooting has lots of more benefits
- currently, there are many alternative solutions to rooting for ad blocking, freeze apps etc.
I did not root my phones after S8 and now s10+.
Click to expand...
Click to collapse
I did not regret rooting my S10 on pie. Themes, magisk modules like viper4android.. it's awesome
I rooted my S10+ Snapdragon (as I have my last 5 phones) first and foremost for Gravitybox and 'Hold back to kill'. After that it was for Afwall+, Edxposed/Magisk, Xprivacy, AppOpps, Greenify, Button Mapper, Icebox, Isolated app storage, and the excellent Maxlock. Samsung warns rooting makes your phone less secure, which is true if u lose it. Password can be bypassed and won't be encrypted, ADB vulnerable etc... So don't root, just let Samsung(among others) run network connections in the background for almost every function you choose
I feel much more secure not being data mined constantly.
fil3s said:
I updated to 10 with magisk 20.3 and it's much better than pie. Awesome
Edit: downloaded with frija this is the ops stock rom I used. 1/3/20 sec patch. Includes already magisk patched ap file :good:
Click to expand...
Click to collapse
https://drive.google.com/file/d/1ZM3vKvtW6J50vya6MxbfLf_U4zn0ekcp/view?usp=drivesdk
Hi
I had unlocked my lg g6 bootloader, and installed custom rom.
After few months with custom rom, I want to get back to the stock lg rom, with dual camera and L1 widevine.
So I tried to install the stock rom and relock bootloader:
Using LG up , downloaded .kdz file, and upercut, I get each time dll problem. The LG up version does not match with the phone version. I tried to place or replace some dll files found online in LGUP/common/LGUP_Common.dll
Nothing happens, I still have this issue.
Then, I tried with LG bridge (update - repair update).
It worked, I installed the stock rom. I still had the bootloader unlocked.
I locked the bootloader with adb and fastboot, and did factory reset.
So why I am posting this message ?
Because now, with the stock rom installed by LG bridge, I have L3 widevine and not L1. And the camera application (and all apps using the camera) does not work.
I think, I need to rewrite properly the original rom with LG up, but I don't know how to make it work properly. I used one time LG up by the past when I soft bricked my phone, and I did not get any dll issues.
Now, I am trying to do it, and nothing works. I tried 2 computers (1 windows, 1 linux+Windows VM) nothing.
kdz problem, dll problem, computer problem ? I don't know...
I really wish someone could help me
Thanks, very much.
If you are coming from Custom ROM to Stock, you need to flash Nougat first. If you dont your camera wont work.
I think that like my old LG L9 the G6 has a PROM/fuse bit which remembers if the bootloader had been unlocked once. This could explain the Widevine issue. Samsung introduced Knox years ago, which also won't ever forget unlocking and prevent further use of certain Samsung applications.
lecorbusier said:
I think that like my old LG L9 the G6 has a PROM/fuse bit which remembers if the bootloader had been unlocked once. This could explain the Widevine issue. Samsung introduced Knox years ago, which also won't ever forget unlocking and prevent further use of certain Samsung applications.
Click to expand...
Click to collapse
Thanks for this response
coco74x said:
Thanks for this response
Click to expand...
Click to collapse
Did you solve?
Cause I did almost same things as you: wanted to go back to stock after experiencing some random reboots with lots of custom roms (which worked till few months ago) and so flashed back the original Pie (H87030b_00_OPEN_EU_OP_1105.kdz) via LGUP but ended up with camera and flash not working at all.
While on custom rom everything works smooth, a part from random reboots
Right now I'm flashing H87011i_00_OPEN_EU_OP_0108.kdz (Nougat) but I'm not sure if it will solve the problem.
Thanks in advance
EDIT: camera is working on Nougat, butnow I have to deal with that damn "moisture" notification
EDIT2: after almost a full day of updates I can use my LG G6 with stock rom, stock camera and be very happy with it ;-) thanks @SkylineDiT for the tip of going back to Nougat, didn't know it.
Hi, i bougth my lg v20 years ago, love the damn phone, but the problem is that i cant seem to have the wifi (and the bluetooth if i install a rom with pie or up) working, i know that dirtysanta works, i can install custom roms but is always the same, on oreo i have no wifi, and anything up i lose wifi and bluetooth, everything else is working fine, i have tried everything, i have flash my phone like 100's of times with all i could find, once i unlock the bootloader with dirtysanta, install twrp and flash the kernel in the post (i need to install the kernel or i have static boot that cant be fixed) i lose wifi even if i dont install anything else, my model (H990T) never had an upgrade to OREO, just 2 .KDZ's of android 7, i have been flashing phones since ICS but i have never been to this kind of problem before.
i have tried:
Using other models .KDZ
Flashing all the roms i could find even if they are not for my model
Flashing all the kernels that i could find even in they are not for my model
Tried all the wifi fixes like misc or WCNSS_qcom_wlan_factory_nv.bin with 0 luck
i have brick the phone and resurect it many times trying this, i love this phone and i want to keep it as my daily driver for many years more, but the throttle on the gpu and cpu is showing his age, if i could just change the thermal config so it could run at his fastest speed that would be cool, even if i have no root or newer android, if anyone could point me in the right direction i would appreciated, i been tempted to learn how to make my own kernel and roms just to fix this, but i dont have the skills necessary for this, but with help i know i can make it.
i know i could just bought a new phone, but this little phone has been with me a long time, and thanks to him im now in the audiophile world.