Related
Full Tutorial and clean Rom by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
You can search on this thread to find the files for Android 6.0.1
You need to root and install TWRP for flashin Android Marshmallow
I recently bought a ZTE Axon Mini here in Europe. It is a pretty good phone, the only problem is the software part which has some lag and UI problems.
They certainly can be fixed with a custom rom or rooting and doing changes or by ZTE themselves.
Here I will write the problems
1) The touch responsiveness could be more fast and snappy, when scrolling etc.
2) random lag occurs from time to time, Some other lag issues with the background apps closing etc.
3) Notifications sometimes do not show at all even when keeping aps on whitelist (deactivate mi assistant to solve this)
4) Dolby Audio gets deactivated almost every time you use headhones .
5) Marshmallow release anytime soon?
6) the UI is too heavy for the phone, most stock apps have issues
7) You cannot adjust brightness inside camera app on auto mode, the HDR mode is really not good ( too blurry)
Click to expand...
Click to collapse
Most of these issues have been fixed on 6.0.1 Rom (search thread)
Summary and further tweaks by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
Edit 1--------------------------------------------------
Root method has been found and works on all axon mini models Android 5.1.1
Credit for finding @orbitz52 and @Heze85
http://www.mgyun.com:81/thread-48100-1-1.html
Just translate the page on Chrome and follow the instructions
For 6.0.1 Marshmallow Root you need to have custom recovery and flash supersu via recovery
Edit 2--------------------------------------------------------
Notification issue has been solved (read pages 1-3)
!!IMPORTANT NEWS!!
Custom recovery for axon mini by @Bormental
TWRP 3.0.2 for ZTE Axon mini unofficial.
It works in all Axon mini mods (B2015 and B2016 with or without "Force Touch".
Installation manual:
1. ROOT device (see the manual in this thread).
2. Download the archive with TWRP.
3. Unzip twrp.img to phone's internal storage.
4. Install any terminal emulator from Google Play and open it.
5. Paste these lines one by one to terminal:
Code:
su
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/stock_recovery.img
dd of=/dev/block/bootdevice/by-name/recovery if=/sdcard/twrp.img
6. Keep the file stock_recovery.img in safe place. It is your stock recovery image.
7. Now TWRP is installed. You can run it by holding vol+ and power button when phone is off or just reboot your phone while holding the vol+ button.
HOW TO ENTER RECOVERY WHEN ON BOOTLOOP WITHOUT EMPTYING THE BATTERY by @Crisvendetta
1. Hold volume up and power button the whole time of this procedure until the moment said below
2. Keep holding, the first time the device will be stuck on boot logo for 10 seconds and restart
3.Keep holding until the device is stuck on boot loop for 5-6 seconds before powering down.
4. RELEASE BUTTONS AS SOON AS SCREEN SHUTS DOWN ON THE 5 SECOND BOOT
5.Now Device is shut down
6. You can enter recovery normally by holding power plus volume+
What to do if the phone with android 6.0.1 is suddenly switching off during backup, restore, copying heavy files or installing ROM:
CLICK TO HIDE CONTENT
Install aboot image from 5.1.1
Reboot recovery
Make all needed operations
Return back aboot image from 6.0.1 before rebooting to system
Attention! Android will boot only with proper aboot image installed!
WARNING! Your warranty is now void! Any operation with firmware can break your phone!
Special thanks
1) @Bormental
2) @orbitz52
3) @demenicis
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Issues
I have a lot of problems with this phone. Sometimes apps doesn't work. Most of the times I can't recive notifications, sometimes is laggy, some options doesn't work or change to it's inicial configuration, force touch is not accurate.... A lot! Please ZTE do something!. BTW, how can I solve the notification problem?!
Thank you so much
Korgan1983 said:
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Click to expand...
Click to collapse
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Notification
Crisvendetta said:
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Click to expand...
Click to collapse
Yes, the notification part is the worse. It should be solved in the coming days...
ZTE AXON notifications FIX !
Aitex10 said:
Yes, the notification part is the worse. It should be solved in the coming days...
Click to expand...
Click to collapse
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications. Otherwise, disable Mi-Assistant from the settings/apps.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Also remove the accelerator settings inside the mi assistant / software settings
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
I am also on 5.1.1.
Notification works better with enabling autostart and enabling background settings. I have disabled the Accelerator / Mi-Assistant, Android has its own power management.
Hello,
i did not find MI-Assistant, where exctely?
Crisvendetta said:
Also remove the accelerator settings inside the mi assistant / software settings
Click to expand...
Click to collapse
Hi,
where can i finf mi Assistant??????
ridowski said:
Hi,
where can i finf mi Assistant??????
Click to expand...
Click to collapse
Which version of Axon do you have ?
It seems the ZTE Axon A1R doesn't have mi-assitant or even power manger/ background manager, and it's on 5.1.1
Guess no way to get that without unlocking the bootloader?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
hoppi05 said:
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
Click to expand...
Click to collapse
Inside mi assistant remove the auto run on startup and then press exit the mi assistant.
This last few days every notification has shown on time, I did a fresh factory reset and the applied all the settings. Don't know if that would help everyone but I am satisfied until now
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
I was wondering what is the difference between zte b2015 and b2016 models. I have the b2016 but it seems nothing changes with b2015.
My geekbench 3 scores single core 712 multicore 3107
Antutu 38051 .
Korgan1983 said:
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
Click to expand...
Click to collapse
Indeed, disabling Mi-assistant together with the steps mentioned, solves all notification issues
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
What model is that? Sounds like the US version?
Hi Good Day ! I am using smn9508 note 5 duos HK and found a solution on how to still play the game HIT on Play Store. It says "Abnormal gameplay detected. The game will shut down". This sh*t happens when you rooted your phone. and do some changes in your kernel The fix is to download busybox on rails to restore to default the permission on SElinux. I can't post a link so pelase download BUSYBOX ON RAILS on Play Store. It's free.
This will reset all permissions to default you did on different rooted apps you've installed.
Just set to cleanup and install and on normal method or recovery depends on what suites you.
Just wanted to help. :good:
Thank you.
I know this is resurrecting an old thread, but my device is not rooted and I am getting this same error too every time I start up the game. Very annoying. Anyone have a fix?
So, I needed to use my old phone again because my new one went back to the shop for repairs. I spent hours trying to get the LG Optimus 2X to work again. In the current year (tm) there are multiple problems:
Nvidia's Tegra 2 chip, which powers the LG Optimus 2X (P990) smartphone doesn't support NEON code (per Wikipedia: "Tegra 2's Cortex A9 implementation does not include ARM's SIMD extension, NEON.")
During 2017, Google added NEON code to Google Play Services - a background process which is automatically updated when the Google Play Store is active. There are hundreds of complaints about this in the Google Product Forums: https://productforums.google.com/forum/#!topic/play/uX3Xqk2gi_k and going by that thread, https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-11-0-38-release/ is the last good version.
I don't know why, but somehow this is related to massive lag when using Optimus 2X roms like the LG stock ICS rom, and custom roms like TonyP's: https://forum.xda-developers.com/showthread.php?t=2769730 (I tried both kernels). Also the AOSP keyboard started malfunctioning (closing repeatedly when typing).
According to TonyP there is no (theoretical?) reason why NEON code should cause lag (only crashes), see bulletpoint 4 at https://forum.xda-developers.com/showpost.php?p=57920187&postcount=21 - but in practice it does.
Maybe it's related to the fact that Google Play Services now uses 121 MB as opposed to the 4,26 MB of the NEON-less version?
LG Mobile Support servers are down. This means that going back to stock and getting stock LG basebands and firmware is now much harder than it needs to be.
Because this phone is so old, a lot of links in this XDA Developers forum are dead. This includes all links to Gooserver, TonyP's server etc. This is why I will include a mirror for everything.
So after multiple hours of trial and error, here's what worked for me to get basic functionality without lag from this phone again.
Prerequisites:
1. You probably already have them installed, but install the latest LG USB drivers for the phone: https://www.lg.com/uk/support/support-mobile/lg-LGP990
2. Make sure you are on the V30A baseband (that is the latest version for Europe). You are probably on this baseband, but if not you can get it at http://www.handy-faq.de/forum/lg-op...al-firmware-der-provider-t207099/#post1469732 (the thread in XDA Developers forums only has dead links) (you only need LGP990AT-00-V30a-EUR-XXX-NOV-30-2012+0_CP.fls, which I've uploaded for you at Mega.nz). You can flash it using the instructions at step 5 below, using option 7 in the AIO-Toolkit.
Step 1: Get the last Cyanogenmod nightly (filename: cm-10.1-20140216-NIGHTLY-p990.zip) from the Archive.org torrent: https://archive.org/details/cmarchive_nighlies
Mirror: Direct magnet link / Mirror 2: Mega.nz.
Please be aware that Cyanogenmod uses the "old partition loadout" / "old bootloader". This will be relevant later.
Step 2: Get the Non-neon Gapps for Android 4.2 by TonyP, the version that changes the keyboard to a non-neon version, by Luk_Optimus (filename: gapps-jb-20130427-nonneon-tonyp-keyboard.zip). You can download it at https://forum.xda-developers.com/showpost.php?p=42567546&postcount=15 . Mirror: Mega.nz
Step 3: Get the at All-In-One ToolKit v6.0 at https://forum.xda-developers.com/showthread.php?t=2020737 . Mirror: Mega.nz
Step 4: Reboot Windows 10 using the startup option "Disable Driver Signature Enforcement", I used method 2 from https://www.lifewire.com/how-to-access-advanced-startup-options-in-windows-10-or-8-2626229 to show the Advanced Startup Options.
Step 5: Open AIO-Toolkit using the desktop shortcut, and after installing the NVFlash Recovery Drivers (option i), type in option 4 ( 4 - Repartition your device with preferred layout and bootloader ). Follow the instructions. Pick the options for the Old Bootloader and TWRP 2.6.0.0. instead of Clockworkmod. Allow AIO-Toolkit to fix the partition layout (it will ask you if you want to do this at the end).
Step 6: Boot to TWRP recovery. Insert the SDHC card containing Cyanogenmod and Non-Neon Gapps. Use the Install button. Flash both the Cyanogenmod and the Non-Neon Gapps you downloaded above.
Step 7: Boot the LG Optimus 2X. Enjoy. Don't forget to dismiss all dialogs asking you to "upgrade" your version of Google Play Services. For example when installing Whatsapp.
Remaining issues:
EDIT: Google Play Store will still sometimes try to update Google Play Services to version 12.8.74 without your consent. In that case, go to Settings -> Apps -> Downloaded and use the "Remove Updates" button on both Google Play Store and Google Play Services. This will return you to the working Non-Neon Gapps version you installed above.
WhatsApp requires Google Play Services to restore backups. Other applications will just not work: for example, MediaMonkey requires Google Play Services 12.4.51 or later, Tapatalk requires it too. Also, some apps are not compatible with non-Neon devices in their latest versions. I've noticed Firefox, Opera Mini (and its beta), Chrome (and its beta) don't work. So I'm still looking for a better browser than the built-in one.
Note: Sometimes the dev has published a Lite version that has less system requirements. For example: use Messenger Lite instead of Facebook Messenger. Messenger Lite, however, crashed when I tested voice calls. Whatsapp didn't, but the other party couldn't hear me.
Seems like some certificates / trusted Certificate Authorities may be missing, causing network errors when using the browser to visit HTTPS websites? All my other devices work fine on my WLAN.
If anyone needs additional instructions, please leave a reply If you have anything to add, also leave a reply!
Finally unlocked bootloader and installed HavocOS to my Xiaomi with all needed wipes: data, system, cache. However, I've faced an issue with Play Market downloads. When I try to download a large app it goes up to 100% and then starts over, stops at 2% and awaits for wi-fi connection ( though I am connected over Wi-Fi). It is the same for all apps over 1Gb in size (e.g. PUBG, Asphalt 9 and so on). Also tried to clear cache and data for Play Market, Google Play Services and no good too.
I've tried to reinstall ROM, gapps, tried Xiaomi EU Rom (stable) and got the same error there. I guess it has something to do with security, so I've tried different google account - but result was the same.
Please suggest any resolution
Just bought this phone myself. But this my guess based on my experience with other devices.
I suspect that your play store status is uncertified?
I am sure it is!
You need to fix that first, then play store function should return to normal.
The easiest way to resolve this issue without reinstallation to use the Magisk Module : Magiskhide Props Config
Next go to the main page for that module and read the instructions ( Google it)
Note, you must also install Termus and enter commands per instructions on Op page for the module. Trust me it's easy.
Essentially you are changing the fingerprints to a Play Store certified device (It only works as long as the module and Magisk stays installed)
I have attached screenshots from my other phone, where I had the same issue and resolved it.
Sent from my Xiaomi MI 8 using XDA Labs
New method that worked for me (2023/01/21) here. If the below method doesn't work, try it.
----------------------------------------------
After literally a year I have GMS on my P40 Pro again!
What worked was following a tutorial that badmania98 shared (thank youuu)
I didn't see anyone comment about this so here's what I did that actually worked.
First of: My device is a Huawei P40 Pro with EMUI 10 - 10.1.0.176 (C432E8R6P1). I don't know if it works with other EMUIs/devices. It should according with the video tutorial.
Steps:
0 - Some steps won't happen like you see on the video, so read carefully.
1 - Watch the whole tutorial first: The link to the tutorial: www.youtube.com/watch?v=7kGkLsf83Bk
2 - Download the app to your device and the HuaGu PC ADB to you PC.
3 - Turn off wifi and mobile data on your device, turn off the internet on your PC (this is just for security reasons, may not be really necessary. I did it)
4 - Do all the PC stuff you see on the video and also step 1 and 2 on the HuaGu app.
5 - When you reach step 3 of the HuaGu app, you may get stuck on the Restore Backup process. Let it run for a minute, go back, and if the step 3 doesn't have a check, do it again. On my 2nd try I got a check on step 3 and moved on.
6 - Turn on wifi or mobile data on your device.
7 - When doing step 4 of the HuaGu app, it should open the Google Service Assistant (that app with the purple G), gives you a error in Chinese and you won't see the same screen as in the video tutorial. Just got back to the HuaGu. It will give you a hint about not knowing if the Assistant did anything (In my case it appears that did nothing, but the whole thing worked anyway).
8 - Do steps 5, 6, 7, 8 and 9.
9 - Open Google Play Store. You'll get those annoying notifications about the not valide device / certifications / whatever. Press retry, open, close, retry and eventually Google Play Store will open normally even with all the notifications popping up.
10 - Install Google Maps. It's going to be annoying to do because of all the notifications.
11 - Open Google Maps and confirmed that you are logged in to your account. Move around the map a bit.
12 - Leave the device showing notifications for a minute or two.
13 - If you still have the annoying notifications (you probably will), go back to the HuaGu app and press on step 10.
14 - There, press step 0 and go back (I didn't register anything here. Maybe because at one time I had GMS on this device, dunno).
15 - Do all the other steps like it says.
16 - Open Google Play Store and disable automatic updates. Close it.
17 - Reboot again.
18 - Open Google Play Store, open Google Maps. If everything is working and without annoying notifications, uninstall HuaGu, Google Service Assistant and that backup restore app. Also, go to your downloads folder and there should be a bunch of APKs that were used during the tutorial. You can delete those as well. Turn off Developer Settings if you don't use them.
Congrats!!! You should have GMS on your device!! I only tested with Maps because it's the only app I really care about that needs GMS to be work so I can use all its features.
Thank you badmania98 and Average Logs!
so i have to roll back the EMUI from 12 to 10 first right?
XanaRaquel said:
After literally a year I have GMS on my P40 Pro again!
What worked was following a tutorial that badmania98 shared (thank youuu)
I didn't see anyone comment about this so here's what I did that actually worked.
First of: My device is a Huawei P40 Pro with EMUI 10 - 10.1.0.176 (C432E8R6P1). I don't know if it works with other EMUIs/devices. It should according with the video tutorial.
Thank you badmania98 and Average Logs!
Click to expand...
Click to collapse
Is your Google account on phone Settings\Users & accounts\Google ?
I tried about 20 times to do according to this instructions with HuaGu2.
Tried 10 times with HuaGu3.
And every time the same result: after uninstalling MicroG and installing Google Play Services, there is no Google item in Settings, no Google accounts (although there were MicroG accounts) and the Play Market asks to enter.
I have a Huawei P40 EMUI 12 Europe phone. I tried several different firmware, downgraded to EMUI 11 - the result is the same.
Have you come across such cases? What to do?
Not working for me either, same reason. When i uninstall microg, it also uninstalls my google accounts
P40 Pro, 10.1.0.176 (c432)
Any suggestions?
BestAlex said:
I tried about 20 times to do according to this instructions with HuaGu2.
Tried 10 times with HuaGu3.
And every time the same result: after uninstalling MicroG and installing Google Play Services, there is no Google item in Settings, no Google accounts (although there were MicroG accounts) and the Play Market asks to enter.
I have a Huawei P40 EMUI 12 Europe phone. I tried several different firmware, downgraded to EMUI 11 - the result is the same.
Have you come across such cases? What to do?
Click to expand...
Click to collapse
Cheecky2chops said:
Not working for me either, same reason. When i uninstall microg, it also uninstalls my google accounts
P40 Pro, 10.1.0.176 (c432)
Any suggestions?
Click to expand...
Click to collapse
A lower firmware is needed.
EMUI10.1.0.121 or 131 for P40Pro C432.
badmania98 said:
A lower firmware is needed.
EMUI10.1.0.121 or 131 for P40Pro C432.
Click to expand...
Click to collapse
Hi, I tried it 1st a few times on 10.1.0.121, exactly same outcome. The dam thing then auto updated to 176 and tried with that, again, exactly the same outcome.
Cheecky2chops said:
Hi, I tried it 1st a few times on 10.1.0.121, exactly same outcome. The dam thing then auto updated to 176 and tried with that, again, exactly the same outcome.
Click to expand...
Click to collapse
All steps are described on my (closed) thread. See my signature.
badmania98 said:
All steps are described on my (closed) thread. See my signature.
Click to expand...
Click to collapse
Yes, I was going to try that. But when I tried to downgrade via your Dload method (like i did before to get to 121) it wont let me downgrade now. It is now on 230. I've formatted memory stick, put dload folder back on it and tried again but it stays at 230. So why before it let me downgrade but not now? I dont get it.
Cheecky2chops said:
Yes, I was going to try that. But when I tried to downgrade via your Dload method (like i did before to get to 121) it wont let me downgrade now. It is now on 230. I've formatted memory stick, put dload folder back on it and tried again but it stays at 230. So why before it let me downgrade but not now? I dont get it.
Click to expand...
Click to collapse
From 11.0.0.230 to 10.1.0.121 you never ever have to use dload method. I never recommend this.
badmania98 said:
From 11.0.0.230 to 10.1.0.121 you never ever have to use dload method. I never recommend this.
Click to expand...
Click to collapse
Ohhh, sorry, i think im gettibg confused and your repky has helped me remember, thanks!
So i used dload method to get to 230. Then i must of used hisuite proxy to get to 121. Sorry mate, ill try that again later, then the method you used for gms.
XanaRaquel said:
After literally a year I have GMS on my P40 Pro again!
What worked was following a tutorial that badmania98 shared (thank youuu)
I didn't see anyone comment about this so here's what I did that actually worked.
First of: My device is a Huawei P40 Pro with EMUI 10 - 10.1.0.176 (C432E8R6P1). I don't know if it works with other EMUIs/devices. It should according with the video tutorial.
Steps:
0 - Some steps won't happen like you see on the video, so read carefully.
1 - Watch the whole tutorial first: The link to the tutorial: www.youtube.com/watch?v=7kGkLsf83Bk
2 - Download the app to your device and the HuaGu PC ADB to you PC.
3 - Turn off wifi and mobile data on your device, turn off the internet on your PC (this is just for security reasons, may not be really necessary. I did it)
4 - Do all the PC stuff you see on the video and also step 1 and 2 on the HuaGu app.
5 - When you reach step 3 of the HuaGu app, you may get stuck on the Restore Backup process. Let it run for a minute, go back, and if the step 3 doesn't have a check, do it again. On my 2nd try I got a check on step 3 and moved on.
6 - Turn on wifi or mobile data on your device.
7 - When doing step 4 of the HuaGu app, it should open the Google Service Assistant (that app with the purple G), gives you a error in Chinese and you won't see the same screen as in the video tutorial. Just got back to the HuaGu. It will give you a hint about not knowing if the Assistant did anything (In my case it appears that did nothing, but the whole thing worked anyway).
8 - Do steps 5, 6, 7, 8 and 9.
9 - Open Google Play Store. You'll get those annoying notifications about the not valide device / certifications / whatever. Press retry, open, close, retry and eventually Google Play Store will open normally even with all the notifications popping up.
10 - Install Google Maps. It's going to be annoying to do because of all the notifications.
11 - Open Google Maps and confirmed that you are logged in to your account. Move around the map a bit.
12 - Leave the device showing notifications for a minute or two.
13 - If you still have the annoying notifications (you probably will), go back to the HuaGu app and press on step 10.
14 - There, press step 0 and go back (I didn't register anything here. Maybe because at one time I had GMS on this device, dunno).
15 - Do all the other steps like it says.
16 - Open Google Play Store and disable automatic updates. Close it.
17 - Reboot again.
18 - Open Google Play Store, open Google Maps. If everything is working and without annoying notifications, uninstall HuaGu, Google Service Assistant and that backup restore app. Also, go to your downloads folder and there should be a bunch of APKs that were used during the tutorial. You can delete those as well. Turn off Developer Settings if you don't use them.
Congrats!!! You should have GMS on your device!! I only tested with Maps because it's the only app I really care about that needs GMS to be work so I can use all its features.
Thank you badmania98 and Average Logs!
Click to expand...
Click to collapse
I am unable to make a backup with Huagu pc app. And I suspect that is because I have FW10.1.0.121 and data transfer and fast charge is disabled, right?
Help much appreciated. Thx
The guide that I posted on the top doesn't work for me anymore - Device not certificated errors. It stopped working around last November. However, today I found a tutorial that works:
So new Tutorial:
Link here
WHAT I DID DIFFERENTLY:
1 - His version is 10.1.0.134 but I'm still on 10.1.0.176 (superior) and it worked.
2 - Maybe because of that, the process of Backup & Restore doesn't worked. The password isn't "icfix1net" anymore, it's "a12345678" or whatever is in the password tip. Still, couldn't restore. So I skipped opening that chinese app.
3 - Google Play Store didn't installed - said it's already installed (which isn't). I continued anyway.
4 - From this point forward I did everything like the tutorial except the parts that involve Google Play Store and the activation of syncing contacts.
5 - Uninstalled the Backup & Restore app.
6 - Done.
Notes:
- If you want to install apps just use the Aurora Store. It uses the apps from Google Play Store so it's safe. I installed Google Maps from there to do the testing.
- Google Play Store is what actually messes everything up because it updates itself and GMS. Either don't install it or block its access to the Internet (you can do that in the settings or use a firewall or whatever).
- If this doesn't work, try to follow the whole tutorial. Who knows. Like I said in the beginning, this is what worked for me.
- If you need to downgrade there are links in the video description, plus there's a lot of tutorials there on XDA for that.
Side note: If you noticed, he has a P40 Pro with unlocked bootloader. I don't know what's the point since there isn't root or custom ROMs available, but it can be done (probably paying). Mine is NOT and it doesn't make a difference in the process.
Good luck everyone !
EDIT: Late reply to everyone:
- Yes, the Google account is in the Settings.
- This new tutorial doesn't use the PC so try this.
- About all firmware questions I can't really answer. I have 10.1.0.176 and never done a downgrade. I simply never updated after that and always disabled the auto updates.